|
(No subject)
Arbi Akhina
I'm pushing the app from the directory that contain both my manifest.yml
toggle quoted messageShow quoted text
and modules.jar Here is the size on disk of the extracted jar : $ du -hs heavenize-modules-2.5-M1-SNAPSHOT-jar-with-dependencies 572M heavenize-modules-2.5-M1-SNAPSHOT-jar-with-dependencies but when I used windows properties window I see: Size: 347 MB Size on disk: 575 MB Contains: 93 334 Files, 5 567 Folders
On Tue, Jun 9, 2015 at 1:39 PM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:
On Tue, Jun 9, 2015 at 5:54 AM, Arbi Akhina <arbi.akhina(a)gmail.com> wrote:FYI the jar is 155M but when pushing I see Téléchargement de 299M, 98585Did you set the `path` attribute correctly? It should be the relative
|
|
|
|
Re: UAA SAML2 Federation
Daniel Mikusa
On Tue, Jun 9, 2015 at 4:45 AM, Pablo Alonso Rodriguez <palonsoro(a)gmail.com>
wrote: Good morning.I don't think so, I think that's a limitation of SAML. Check out this thread for some more info on this. http://cf-dev.70369.x6.nabble.com/cf-dev-UAA-SAML-and-LDAP-questions-td62.html Dan
|
|
|
|
(No subject)
Daniel Mikusa
On Tue, Jun 9, 2015 at 5:54 AM, Arbi Akhina <arbi.akhina(a)gmail.com> wrote:
FYI the jar is 155M but when pushing I see Téléchargement de 299M, 98585Did you set the `path` attribute correctly? It should be the relative path to your JAR or WAR file. Also, how many files are in your JAR? Does that match the number listed here? What if you extract the files from the JAR? Does the size match up? Dan
|
|
|
|
(No subject)
Daniel Mikusa
On Tue, Jun 9, 2015 at 5:05 AM, Arbi Akhina <arbi.akhina(a)gmail.com> wrote:
Hi, thanks for the hint, I tried to add to the manifest the followingThe Java build pack does not put Java on the path, which is what you're seeing in the error below. I will usually run `CF_TRACE=true cf app <app-name> | grep "detected_start_command"` which shows the command the build pack detected and then just copy & paste that into my custom command.
|
|
|
|
(No subject)
Arbi Akhina
FYI the jar is 155M but when pushing I see Téléchargement de 299M, 98585
toggle quoted messageShow quoted text
fichiers
On Tue, Jun 9, 2015 at 11:05 AM, Arbi Akhina <arbi.akhina(a)gmail.com> wrote:
Hi, thanks for the hint, I tried to add to the manifest the following
|
|
|
|
(No subject)
Arbi Akhina
Hi, thanks for the hint, I tried to add to the manifest the following entry:
toggle quoted messageShow quoted text
command: sleep 2 && java -jar modules.jar but it looks like it's not appropriate as I see in the logs: 2015-06-08T05:34:03.71+0200 [App/0] ERR bash: java: command not found
On Mon, Jun 8, 2015 at 6:32 PM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:
On Mon, Jun 8, 2015 at 12:03 PM, Arbi Akhina <arbi.akhina(a)gmail.com>
|
|
|
|
UAA SAML2 Federation
Pablo Alonso Rodriguez <palonsoro@...>
Good morning.
Recently, we have successfully federated the UAA to an external identity provider via SAML2. However, we are only able to log in via cf login --sso, so that we can get a temporary code by loging in the idp web page. Is there any way to directly pass the credentials to the identity provider from the cf cli? Thank you in advance.
|
|
|
|
CF CAB call on Wednesday, June 10th, 2015 @ 8a PDT
Michael Maximilien
Hi, all,
It's been about a month since CF summit 2015 and two months since the last CAB call. Please make plan to join the call this Wednesday as we surely will have a jam pack update from all teams and from community at large. ------------ Agenda (working): https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI/edit# CF community call @ 8AM PDT USA, Canada, and Mexico: 1-888-426-6840 or USA 1-215-861-6239 All other countries can find dial-in numbers here: http://goo.gl/RnNfc1 Participant code: 1985291 ------------ If you are a PM then make sure to update your highlights on the appropriate section in the doc above. If you are not a PM and have something to share, then add to agenda in Others section or send to us by replying to this email. Talk to you all soon. Best, Chip, James, and Max ------ dr.max ibm cloud labs silicon valley, ca maximilien.org
|
|
|
|
Re: Adding second domain to API endpoint
James Bayer
guillaume, you're right. the CNAME approach won't work if the host header
toggle quoted messageShow quoted text
doesn't match the route advertised from the CCs.
On Mon, Jun 8, 2015 at 2:08 PM, Guillaume Berche <bercheg(a)gmail.com> wrote:
James, would'nt a second domain (even if resolving to the same IP than the --
Thank you, James Bayer
|
|
|
|
Re: Adding second domain to API endpoint
James, would'nt a second domain (even if resolving to the same IP than the
toggle quoted messageShow quoted text
primary domain, thanks to a CNAME), still be mentionned in http requests in their original "Host:", header and would therefore be unknown to the CF gorouter, returning a 404 as a response ? I wonder whether the routing-api [1] indeed currently returns a wildcard route to the CC IP/port, and could then be used to advertise a new wildcard route in a second domain. This would require custom development into a distinct bosh jobs (that would periodically renew the new domain before its TTL expires) Guillaume. [1] https://github.com/cloudfoundry-incubator/routing-api#usage
On Sat, Jun 6, 2015 at 6:38 PM, James Bayer <jbayer(a)pivotal.io> wrote:
it appears as though the cloud controller only supports advertising a
|
|
|
|
Announcing cf-mysql-release v20
Marco Nicosia
Hi There!
On behalf of the CF Core Services team I am pleased to announce v20 of cf-mysql-release <https://github.com/cloudfoundry/cf-mysql-release>. -- cf-mysql-release <https://github.com/cloudfoundry/cf-mysql-release> is a BOSH release that delivers a database-as-a-service for Cloud Foundry users. Through Cloud Foundry, users can provision databases and deliver unique credentials to bound applications. v20 expands on the AWS support introduced in v18. (v19 was a small update release that hardly merited an e-mail to this list.) The major changes in v20 are that we've restructured the templates used to generate BOSH manifests for Amazon Web Services. These templates now split the three major functions of our software, proxy, mysql and the service broker, across separate AWS Availability Zones. The mysql job has been split to run across three AZs, one instance each. Proxy and Service Broker are deployed in an HA configuration across two Availability Zones. If you've already deployed a version of cf-mysql-release on AWS, you'll need to follow the upgrade instructions very carefully to re-deploy across zones while retaining your data. Please see the release notes for v20 <https://github.com/cloudfoundry/cf-mysql-release/releases/tag/v20>. A neat side-effect of making this change is that we've given each job its own Bosh resource pool <https://bosh.io/docs/deployment-manifest.html#resource-pools> per Availability Zone! With the new templates, the Operator can specify different instance types per job. We've changed the defaults to save AWS users a little cash: MySQL instances remain m3.larges while Brokers and Proxies drop down to m3.mediums. You can find documentation on how to modify your instance sizes on the deployment resources <https://github.com/cloudfoundry/cf-mysql-release/blob/v20/docs/deployment-resources.md> page. Amidst other upgrades and improvements (we re-wrote the Quota Enforcer), we've also upgraded MariaDB to version 10.0.17, Galera to 25.3.9, and Xtrabackup to 2.2.10. Note that in combination with Bosh, MariaDB Galera cluster upgrades are performed without downtime <http://galeracluster.com/documentation-webpages/upgrading.html#id1>! If you'd like to know more, detailed release notes can be found on GitHub <https://github.com/cloudfoundry/cf-mysql-release/releases/tag/v20> and bosh.io <http://bosh.io/releases/github.com/cloudfoundry/cf-mysql-release?version=20>. If you'd like to know even more than that, each line contains a link to the original story under which a feature was commissioned. As always, we'd love to hear if you're having any problems with this version of the software. Please open a GitHub issue <https://github.com/cloudfoundry/cf-mysql-release/issues>. If you're willing, we're always very happy to receive a Pull Request <https://github.com/cloudfoundry/cf-mysql-release/pulls>. -- Marco Nicosia Product Manager Pivotal Software, Inc. mnicosia(a)pivotal.io c: 650-796-2948
|
|
|
|
(No subject)
Daniel Mikusa
On Mon, Jun 8, 2015 at 12:03 PM, Arbi Akhina <arbi.akhina(a)gmail.com> wrote:
I'm trying to push an executable JAR to a bosh-lite instance, on the logsThere's a known issue that occurs when an app starts and fails in rapid succession and results in the log entries being missed. If you add a couple second pause into the app, it will give the system enough time to attach the logger and you'll see the output generated by the crashing app. You can do this with a custom start command `cf push -c 'sleep 2 && <normal-cmd>'` or with a `.profile.d` script that sleeps for a couple seconds. Dan
|
|
|
|
(No subject)
Arbi Akhina
I'm trying to push an executable JAR to a bosh-lite instance, on the logs I
see CF trying many times to restart the app and eventually fail. I can't find out why the app crashes as there is no app logs returned by CF. I tried to remotely debug the app (as described in [1]) but nothing happens on eclipse. Any hint to solve this issue is appreciated. 1. I'm launching the app with: *cf push -t 180* 2. Here is the manifest.yml content: --- applications: - name: modules memory: 4G instances: 1 host: modules-${random-word} path: modules.jar buildpack: https://github.com/cloudfoundry/java-buildpack env: JAVA_OPTS: "$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address= 192.168.2.8:8000" 3. Here is the log: Connecté, le dumping journaux récents pour application modules en org heavenize / espace dev comme admin... 2015-06-07T12:05:15.69+0200 [API] OUT Created app with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:05:16.10+0200 [API] OUT Updated app with guid 1fbf3378-6512-46de-bae4-02ee30275464 ({"route"=>"68e27d8d-4ff6-443b-a3e0-416c40d325d3"}) 2015-06-07T12:12:21.55+0200 [DEA] OUT Got staging request for app with id 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:12:25.40+0200 [API] OUT Updated app with guid 1fbf3378-6512-46de-bae4-02ee30275464 ({"state"=>"STARTED"}) 2015-06-07T12:12:38.08+0200 [STG] OUT -----> Downloaded app package (163M) 2015-06-07T12:13:40.93+0200 [STG] ERR Cloning into '/tmp/buildpacks/java-buildpack'... 2015-06-07T12:14:01.67+0200 [STG] OUT -----> Java Buildpack Version: c862ac8 | https://github.com/cloudfoundry/java-buildpack#c862ac8 2015-06-07T12:14:13.89+0200 [STG] OUT -----> Downloading Open Jdk JRE 1.8.0_45 from https://download.run.pivotal.io/openjdk/lucid/x86_64/openjdk-1.8.0_45.tar.gz (11.6s) 2015-06-07T12:14:15.34+0200 [STG] OUT Expanding Open Jdk JRE to .java-buildpack/open_jdk_jre (1.4s) 2015-06-07T12:14:15.89+0200 [STG] OUT -----> Downloading Open JDK Like Memory Calculator 1.1.1_RELEASE from https://download.run.pivotal.io/memory-calculator/lucid/x86_64/memory-calculator-1.1.1_RELEASE (0.5s) 2015-06-07T12:14:15.90+0200 [STG] OUT Memory Settings: -XX:MaxMetaspaceSize=419430K -XX:MetaspaceSize=419430K -Xss1M -Xmx3G -Xms3G 2015-06-07T12:15:43.44+0200 [STG] OUT -----> Uploading droplet (151M) 2015-06-07T12:16:07.51+0200 [DEA] OUT Starting app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:16:29.66+0200 [API] OUT App instance exited with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload: {"cc_partition"=>"default", "droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464", "version"=>"703f793c-e388-41ac-b1f1-c564b301ca70", "instance"=>"9d55c5f791324d358bffb4c961a4c7ee", "index"=>0, "reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to start", "crash_timestamp"=>1433672189} 2015-06-07T12:17:14.18+0200 [DEA] OUT Starting app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:17:31.10+0200 [API] OUT App instance exited with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload: {"cc_partition"=>"default", "droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464", "version"=>"703f793c-e388-41ac-b1f1-c564b301ca70", "instance"=>"2ae0c26f33864f40989ee870a1b9e3db", "index"=>0, "reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to start", "crash_timestamp"=>1433672251} 2015-06-07T12:17:38.48+0200 [DEA] OUT Removing crash for app with id 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:17:38.48+0200 [DEA] OUT Stopping app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:17:38.48+0200 [DEA] OUT Stopped app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:17:55.31+0200 [DEA] OUT Starting app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:18:11.82+0200 [API] OUT App instance exited with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload: {"cc_partition"=>"default", "droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464", "version"=>"703f793c-e388-41ac-b1f1-c564b301ca70", "instance"=>"dc872d38f3324af481c82ba67f0e216c", "index"=>0, "reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to start", "crash_timestamp"=>1433672291} 2015-06-07T12:18:18.69+0200 [DEA] OUT Removing crash for app with id 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:18:18.69+0200 [DEA] OUT Stopping app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:18:18.69+0200 [DEA] OUT Stopped app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:18:34.06+0200 [DEA] OUT Starting app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:18:50.98+0200 [API] OUT App instance exited with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload: {"cc_partition"=>"default", "droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464", "version"=>"703f793c-e388-41ac-b1f1-c564b301ca70", "instance"=>"623c3af7e3e84801b6fd44eeee9c0a12", "index"=>0, "reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to start", "crash_timestamp"=>1433672330} 2015-06-07T12:18:58.80+0200 [DEA] OUT Removing crash for app with id 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:18:58.80+0200 [DEA] OUT Stopping app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:18:58.80+0200 [DEA] OUT Stopped app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:19:34.08+0200 [DEA] OUT Starting app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:19:50.36+0200 [API] OUT App instance exited with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload: {"cc_partition"=>"default", "droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464", "version"=>"703f793c-e388-41ac-b1f1-c564b301ca70", "instance"=>"40727eea293146948af197e13443843c", "index"=>0, "reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to start", "crash_timestamp"=>1433672390} 2015-06-07T12:19:59.01+0200 [DEA] OUT Removing crash for app with id 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:19:59.01+0200 [DEA] OUT Stopping app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:19:59.01+0200 [DEA] OUT Stopped app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:21:04.12+0200 [DEA] OUT Starting app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:21:20.61+0200 [API] OUT App instance exited with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload: {"cc_partition"=>"default", "droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464", "version"=>"703f793c-e388-41ac-b1f1-c564b301ca70", "instance"=>"f7ffff55692a418c847f4f37be574ddf", "index"=>0, "reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to start", "crash_timestamp"=>1433672480} 2015-06-07T12:21:29.43+0200 [DEA] OUT Removing crash for app with id 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:21:29.43+0200 [DEA] OUT Stopping app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:21:29.47+0200 [DEA] OUT Stopped app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:23:34.16+0200 [DEA] OUT Starting app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:23:49.97+0200 [API] OUT App instance exited with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload: {"cc_partition"=>"default", "droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464", "version"=>"703f793c-e388-41ac-b1f1-c564b301ca70", "instance"=>"4581e97c6b0f4504b8d64a5c69d6787b", "index"=>0, "reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to start", "crash_timestamp"=>1433672629} 2015-06-07T12:23:50.29+0200 [DEA] OUT Removing crash for app with id 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:23:50.29+0200 [DEA] OUT Stopping app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:23:50.29+0200 [DEA] OUT Stopped app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:28:14.24+0200 [DEA] OUT Starting app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:28:29.82+0200 [API] OUT App instance exited with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload: {"cc_partition"=>"default", "droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464", "version"=>"703f793c-e388-41ac-b1f1-c564b301ca70", "instance"=>"f98749490a6743598f57d3848eb06177", "index"=>0, "reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to start", "crash_timestamp"=>1433672909} 2015-06-07T12:28:31.73+0200 [DEA] OUT Removing crash for app with id 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:28:31.73+0200 [DEA] OUT Stopping app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 2015-06-07T12:28:31.73+0200 [DEA] OUT Stopped app instance (index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464 [1] http://docs.cloudfoundry.org/buildpacks/java/java-tips.html#debugging
|
|
|
|
Re: What ports will be needed to support hm and loggregator
Erik Jasiak <ejasiak@...>
Loggregator listens for the "old"[1], loggregator message format on 3456,
toggle quoted messageShow quoted text
and the newer dropsonde messages on 3457. We're actively working to mark the old loggregatorlib as deprecated. "Do you know why 3457 is used when the incoming listening port for loggregator is specified as 3456?" - I found in our Bosh Manifest readme example that this was incorrect, and someone is fixing that now. Did you read it anywhere else we need to update? Thanks, Erik [1] https://github.com/cloudfoundry/loggregatorlib/tree/master/logmessage
On Sat, Jun 6, 2015 at 8:29 AM, Jason Huang <jasonxs.huang(a)gmail.com> wrote:
Yes he also listens to udp4. By allowing udp 3456 and 3457, it worked.
|
|
|
|
R: Re: Log connections from security groups - bosh lite
Michael Grifalconi <michael.grifalconi@...>
Hello, I post some more info:
toggle quoted messageShow quoted text
Kernel logging is enabled because inside the DEA, i can see: cat /etc/rsyslog.conf [...] $IncludeConfig /etc/rsyslog.d/*.conf cat /etc/rsyslog.d/enable-kernel-logging.conf $ModLoad imklog after pushing an app, I see on the DEA the correct rules: -A warden-i-18nvgifiemi -p tcp -m tcp --dport 80 -g warden-i-18nvgifiemi-log -A warden-i-18nvgifiemi-log -p tcp -m conntrack --ctstate INVALID,NEW,UNTRACKED -j LOG --log-prefix "warden-i-18nvgifiemi " but on /var/log/messages I only get: Jun 8 07:03:26 localhost kernel: [ 3256.433021] IPv6: ADDRCONF(NETDEV_CHANGE): w-18nvgifiemg-0: link becomes ready the php application pushed: xx(a)boshClient:~/myPhpApp$ cat index.php <html> <head> <title>PHP Test</title> </head> <body> <?php echo '<p>Hello PHP from the server at:</p>'; echo $_SERVER['SERVER_ADDR']; echo '<p>hi from hostname:</p>'; $curl = curl_init(); curl_setopt($curl, CURLOPT_URL, 'http://xxxxxxx'); $result = curl_exec($curl); echo gethostname(); ?> </body> </html> When I browse this application page, I see the page from the webserver on xxxx called from curl, but I don't get ant log. bosh stemcells +---------------------------------------------+---------+--------------------------------------+ | Name | Version | CID | +---------------------------------------------+---------+--------------------------------------+ | bosh-warden-boshlite-ubuntu-trusty-go_agent | 2776* | c5ac6590-13ec-4ba2-6fa9-e78cf553c4e6 | +---------------------------------------------+---------+--------------------------------------+ -------------------------------------------------------------------- xx(a)boshClient:~$ cf security-groups Getting security groups as admin OK Name Organization Space #0 public_networks #1 dns #2 logging myOrg myDevSpace xx(a)boshClient:~$ cf security-group logging Getting info for security group logging as admin OK Name logging Rules [ { "destination": "0.0.0.0/0", "log": true, "ports": "80", "protocol": "tcp" } ] Organization Space #0 myOrg myDevSpace tried with protocol: all and :tcp and the port where my local apache server on LAN is listening. Any suggestion is appreciated! Regards, Michael
Il 06/06/15 09:25, Dieu Cao <dcao(a)pivotal.io> ha scritto:
|
|
|
|
Is there any officail Chinese docs?
tan_bw@...
I can't open the Chinese doc website http://cndocs.cloudfoundry.com.Is this website closed?Is there any other substitute?
|
|
|
|
Re: Adding second domain to API endpoint
James Bayer
it appears as though the cloud controller only supports advertising a
single domain: https://github.com/cloudfoundry/cf-release/blob/master/jobs/cloud_controller_ng/spec#L62-L63 i wonder if a CNAME would work for this as a work-around? On Sat, Jun 6, 2015 at 9:19 AM, Vinicius Carvalho < viniciusccarvalho(a)gmail.com> wrote: Hi there, how can I add a second domain to my API endpoint? I know how to -- Thank you, James Bayer
|
|
|
|
Adding second domain to API endpoint
Vinicius Carvalho <viniciusccarvalho@...>
Hi there, how can I add a second domain to my API endpoint? I know how to
add a shared domain for apps. But looking at the router /routes, the api.<domain> maps directly to the cloudcontroller. How can I add a second route using a different domain already mapped on my DNS? Regards -- The intuitive mind is a sacred gift and the rational mind is a faithful servant. We have created a society that honors the servant and has forgotten the gift.
|
|
|
|
Re: What ports will be needed to support hm and loggregator
Jason Huang
Yes he also listens to udp4. By allowing udp 3456 and 3457, it worked.
toggle quoted messageShow quoted text
Do you know why 3457 is used when the incoming listening port for loggregator is specified as 3456? Sent from my iPhone
On Jun 5, 2015, at 1:58 AM, Lev Berman <lev.berman(a)altoros.com> wrote:
We found the loggregator was listening on port 3456 and 3457 with upd6.He also probably listens for udp4 connections. Have you tried to allow udp4 traffic to ports 3456-3457 and check if loggregator collects the logs after it?On Fri, Jun 5, 2015 at 4:17 AM, Meng, Xiangyi <xiangyi.meng(a)emc.com> wrote:
|
|
|
|
Re: Log connections from security groups - bosh lite
Dieu Cao <dcao@...>
Yes, I do recall that the feature did not work on bosh-lite but that was
toggle quoted messageShow quoted text
when kernel logging was disabled on the trusty stemcell. Michael, could you send the json for the application security group you've applied to the space you're looking at? -Dieu CF Runtime PM
On Fri, Jun 5, 2015 at 5:48 PM, James Bayer <jbayer(a)pivotal.io> wrote:
i seem to remember something about app security group logging having an
|
|
|