|
Re: tcp-routing in Lattice
Marco Nicosia
Hi Jack,
toggle quoted messageShow quoted text
In addition to Atul's suggestions, could you please give us the exact command lines which you used to launch the two apps? The CLI arguments are tricky, we may be able to see something about the way you've tried to configure the routes by looking at how you've launched the apps. -- Marco Nicosia Product Manager Pivotal Software, Inc. mnicosia(a)pivotal.io c: 650-796-2948
On Wed, Sep 9, 2015 at 2:32 PM, Jack Cai <greensight(a)gmail.com> wrote:
I'm playing around with the tcp-routing feature in the latest Lattice
|
|
|
|
Important changes in CF v217
Amit Kumar Gupta
This release introduces significant improvements to the security of the
consul cluster, however the operator must introduce these changes over the course of multiple deployments. If you are not running any consul servers as part of your deployment, you can ignore these instructions. Otherwise, please do the following: 1. Scale the number of consul servers in your existing deployment down to 1 instance. The consul.agent.servers.lan property must be updated to reflect this; this should happen for free if you are using the standard tooling for manifest generation. If you are deploying Diego alongside CF, you must redeploy Diego as well to pick up the consul.agent.servers.lan change; again, this should happen for free if using the standard manifest generation tooling. 2. Generate SSL certificates, keys, and a separate encryption key for the gossip protocol used by consul (instructions: https://docs.cloudfoundry.org/deploying/consul-security.html). Upload the v217 release and generate your manifest for CF (and then Diego, if also deploying Diego). 3. Deploy CF (and then Diego, if also deploying Diego). 4. Scale the number of consul servers back up to whatever you had it at before. Regenerate all relevant manifests and deploy. Best, Amit
|
|
|
|
Re: tcp-routing in Lattice
Atul Kshirsagar
Its possible that HAProxy was not properly configured. Can you provide output of `ltc status <app name>`? This will tell if tcp route has been configured for the app.
Some things you can try: 1) You can then try doing `ltc update --tcp-route externalport:containerport` and see if that fixes the problem (this will result in reconfiguring HAProxy again). 2) If that doesn't work too...then try vagrant reload to make sure all the processes in lattice brain are restarted to rule out the problem that HAproxy is not in bad state.
|
|
|
|
Re: v3 cc api style guide feedback requested
Dieu Cao <dcao@...>
Thanks Guillaume!
toggle quoted messageShow quoted text
On Wed, Sep 9, 2015 at 2:33 PM, Guillaume Berche <bercheg(a)gmail.com> wrote:
Hi Dieu,
|
|
|
|
Re: v3 cc api style guide feedback requested
Hi Dieu,
toggle quoted messageShow quoted text
Here are corresponding issues/comments submitted https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/46 https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/47 https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/48 https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/49 https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/41#issuecomment-139050180 https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/41#issuecomment-139051114 Guillaume.
On Wed, Sep 9, 2015 at 10:39 AM, Dieu Cao <dcao(a)pivotal.io> wrote:
Hi Guillaume,
|
|
|
|
tcp-routing in Lattice
Jack Cai
I'm playing around with the tcp-routing feature in the latest Lattice
release. I started two node.js applications in the pushed image (listening on two ports), one mapped to an http route and the other to a tcp route. I can connect to the http route successfully in the browser, but when I try to connect to the tcp port in the browser, I got connection refused. It looks like the mapped public tcp port on 192.168.11.11 is not open at all. Any advice on how to diagnose this? Thanks in advance! Jack
|
|
|
|
Re: Loggregator not accessible, errors in the logs
Rohit Kumar
Answers to your questions:
toggle quoted messageShow quoted text
1. That error might be caused if your doppler servers aren't healthy and therefore not listed in etcd. The traffic-controller polls etcd to discover dopplers. 2. You do need metron and dopplers to access logs via "cf logs". The logs are emitted by the DEA agent to metron, which forwards them to doppler servers. Doppler servers deal with buffering logs (so that they are accessible via the "cf logs --recent" command) and also deal with syslog forwarding. Thanks, Rohit
On Wed, Sep 9, 2015 at 2:33 PM, kyle havlovitz <kylehav(a)gmail.com> wrote:
I'm seeing this message repeating over and over in the traffic controller
|
|
|
|
Loggregator not accessible, errors in the logs
kyle havlovitz <kylehav@...>
I'm seeing this message repeating over and over in the traffic controller
logs: {"timestamp":1441830145.719944000,"process_id":32413,"source":"loggregator trafficcontroller","log_level":"debug","message":"ServerAddressList.Run: Unable to recursively find keys with prefix /healthstatus/doppler","data":null,"file":"/opt/cloudfoundry/cf-release/src/loggregator/src/ github.com/cloudfoundry/loggregatorlib/servicediscovery/servicediscovery.go ","line":78,"method":" github.com/cloudfoundry/loggregatorlib/servicediscovery.(*serverAddressList).DiscoverAddresses "} Here's my config: "EtcdUrls" : ["http://localhost:4001"], "EtcdMaxConcurrentRequests" : 10, "WSMessageBufferSize": 100, "OutgoingDropsondePort": 8082, "DopplerPort": 8082, "IncomingPort": 3456, "OutgoingPort": 9090, "SkipCertVerify": true, "Index": 0, "MaxRetainedLogMessages": 100, "SharedSecret": "secret", "Host": "0.0.0.0", "SystemDomain": "local.example.com", "ApiHost": "http://127.0.0.1:8181", "NatsHosts": ["127.0.0.1"], "NatsPort": 4222, "NatsUser": "nats", "NatsPass": "password", "VarzUser": "varz", "VarzPass": "password", "VarzPort": 8888, "MetronPort": 3457, "Syslog" : "", "Zone": "CRAZY_TOWN", "UaaHost": "http://localhost:8080", "UaaClientId": "doppler", "UaaClientSecret": "tokensecret" } I have all the components running locally, using cf-release 215. I have two questions: 1. what's causing this error? 2. if all I want out of the system are logs (via cf logs command), can I get away with just having a traffic controller and dea agent running or do I need metron and doppler?
|
|
|
|
Re: Cloud Foundry NodeJS 4 support and release schedule
Shawn Nielsen
Thanks for the quick feedback on this, we appreciate your responsiveness.
toggle quoted messageShow quoted text
We'll continue to follow the issue in the pivotal tracker.
On Wed, Sep 9, 2015 at 12:36 PM, Mike Dalessio <mdalessio(a)pivotal.io> wrote:
Hi Shawn,
|
|
|
|
consolidated routing api
Shannon Coen
We currently have two routing APIs in CF.
1. HTTP Routing API in cf-release: https://github.com/cloudfoundry-incubator/routing-api 2. TCP Routing API in cf-routing-release: https://github.com/cloudfoundry-incubator/cf-routing-release The TCP Routing API is quite basic and we want to extend it for high availability, authentication, etc. However, instead of enhancing the existing TCP Routing API, we plan to add support for TCP route registration to the Routing API in cf-release, as it already supports many of the desired features. We'll get rid of the current API in cf-routing-release and submodule in the Routing API from cf-release. Eventually we'll move the Routing API (along with GoRouter and HAProxy) from cf-release into cf-routing-release and submodule them into cf-release. This consolidation, along with our not having any API consumer besides GoRouter yet, gives us the opportunity to consider a common behavior for routing API endpoints. We welcome your comments in our design doc: https://docs.google.com/document/d/1v941oy3Y7RRI80gmLfhPZlaahElK_Q0C3pCQewK8Z3g/edit?usp=sharing Thank you, Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.
|
|
|
|
Re: Cloud Foundry NodeJS 4 support and release schedule
Mike Dalessio
Hi Shawn,
toggle quoted messageShow quoted text
Great question, thanks for asking it. The Buildpacks team has a Tracker story in its backlog to work on Node 4: https://www.pivotaltracker.com/story/show/102941608 Generally our turnaround time on vanilla version updates is less than a day; however, Node 4 isn't just a regular version update, as it comes from io.js lineage which we haven't ever officially supported; and so we're going to proceed carefully. The story I linked to has some specific acceptance criteria: * Does the binary build with our current tooling? If not, we'll have to update our tooling. * Does the binary dynamically link openssl? (This was a specific use case we've had to work around in the past.) If not, we'll have to make sure it does, so that rootfs updates will be sufficient to address openssl CVEs. * Does the binary avoid statically linking any other rootfs libraries? If not, see above. * Does the binary pass BRATs? If not, we'll have to fix BRATs. Only when all of the above look good will we ship; and since we haven't worked with io.js and family before, I don't want to make any promises about delivery. If things go well, it could ship as early as tomorrow, though that's probably overly optimistic. Additionally I'll likely delay committing it into cf-release until we have positive feedback from the community. I'm happy to keep this thread updated with our progress; or you can follow along at the Tracker story. Cheers, -mike
On Wed, Sep 9, 2015 at 11:33 AM, Shawn Nielsen <sknielse(a)gmail.com> wrote:
NodeJS version 4 was released yesterday to the community.
|
|
|
|
Re: Cloud Foundry NodeJS 4 support and release schedule
James Thomas <jthomas.uk@...>
I was playing around this morning using the Heroku Node.js binaries for v4
with the existing CF Node.js buildpack. https://github.com/jthomas/nodejs-v4-buildpack/commit/e2b6887638af1be2e472f989b3d005a0e33fb787 It worked perfectly with my test app. On 9 September 2015 at 17:16, Juan Antonio Breña Moral < bren(a)juanantonio.info> wrote: Nice news! -- Regards, James Thomas
|
|
|
|
Business Contacts
Adam Park <adam.park@...>
Hi,
Would you be interested acquiring business databases for your sales and marketing initiatives? I hope you are the right person to discuss about this in your company? If not please refer me to the right person to discuss further about our services. Acquire Databases in excel spread sheet format: All Business Executives Retail Executives Pharma Executives Biotech Users E-commerce Users Technology Key Decision Makers Travel & Transportation Users Oil and Gas Databases Insurance Agents and Brokers Hospital Databases Doctors and Physicians Manufacturing Databases and Many more... Let me know target specifications such as targeted Geographies, Industries, Titles/job roles, Company Size (Revenue/Employees), etc & I will get back to you with counts & pricing for the same. Thanks and looking forward to hearing from you! Best Regards, Adam Park Business Development Note: You were specifically sent this email based upon your company profile. If for some reason this was sent in error or you wish not to receive any further messages from us please reply with subject line as "Exclude" or click here to UNSUBSCRIBE <mailto:infyunsubscribe(a)gmail.com?subject=UNSUBSCRIE> to exclude from all future mailings.
|
|
|
|
Re: Cloud Foundry NodeJS 4 support and release schedule
Juan Antonio Breña Moral <bren at juanantonio.info...>
Nice news!
In my side, I am working on a Node Client for Cloud foundry: https://github.com/jabrena/cf-nodejs-client and a webApp to deploy in a easy way applications: https://github.com/prosociallearnEU/cf-nodejs-dashboard Regards Juan Antonio
|
|
|
|
Cloud Foundry NodeJS 4 support and release schedule
Shawn Nielsen
NodeJS version 4 was released yesterday to the community.
Generally speaking, what is the typical release schedule for buildpack binaries after new runtime releases are announced? More specifically, I'd be curious if you have information on release schedule of the NodeJS 4 buildpack binaries.
|
|
|
|
Re: Application only starts when a bogus service is attached
Amit Kumar Gupta
Okay, great!
toggle quoted messageShow quoted text
Thanks, Amit
On Wed, Sep 9, 2015 at 4:35 AM, Fabien LEBRERE <yop190(a)gmail.com> wrote:
Hi Amit,
|
|
|
|
cf push hanged in after package donwload
Xiao
Hi expert,my env:cf 213 vsphere 5.5
After redeploy CF in a new environment, testing spring-music as the first app. When run cf push, get below issue:------------------------------------ $ cf pushUsing manifest file /home/david/spring-music-master/manifest.yml Creating app spring-ca in org pivotal / space space01 as admin...OK Creating route spring-ca-1234.192.168.2.33.xip.io...OK Binding spring-ca-1234.192.168.2.33.xip.io to spring-ca...OK Uploading spring-ca...Uploading app files from: /home/david/spring-music-master/build/libs/spring-music.warUploading 576.9K, 90 filesDone uploadingOK Starting app spring-ca in org pivotal / space space01 as admin...-----> Downloaded app package (22M) FAILEDspring-ca failed to stage within 15.000000 minutes--------------------------------------$ cf logs app spring-ca --recent dose not show valuable info ------------------------------------- DEA config as below:dea_next: advertise_interval_in_seconds: 5 allow_host_access: null allow_networks: [] default_health_check_timeout: 60 deny_networks: [] directory_server_protocol: https disk_mb: 30480 disk_overcommit_factor: 2 evacuation_bail_out_time_in_seconds: 600 heartbeat_interval_in_seconds: 10 instance_disk_inode_limit: 200000 kernel_network_tuning_enabled: true logging_level: debug memory_mb: 10240 memory_overcommit_factor: 3 rlimit_core: 0 staging_disk_inode_limit: 200000 staging_disk_limit_mb: 10000 staging_memory_limit_mb: 10240 description: Cloud Foundry sponsored by Pivotal disk_quota_enabled: true--------------------------------------------------thanksDavid
|
|
|
|
Utilities PMC - 2015-09-09 Notes
Mike Dalessio
Hello CF Community,
Apologies for the lapse in sending timely Utilities PMC notes (see comments below). These notes are permanently available at: https://github.com/cloudfoundry/pmc-notes/blob/master/Utilities/2015-09-09-utilities.md -mike --- # Utilities PMC Notes 2015-09-09 ## Table of Contents 1. Update on "Offline" PMC Discussion 2. CLI 3. Java Utilities ## Update on "Offline" PMC Discussions In the previous PMC meeting, held on 2015-07-28, the Utilities PMC agreed to tentatively stop conducting regular synchronous meetings, and instead move to an "offline" model where discussions and, if necessary, voting would be conducted on the public cf-dev@ mailing list. As part of this change, the PMC Lead (that's me!) committed to sending regular status updates to the mailing list in lieu of meeting notes. In this aspect, I failed over the last month, and I apologize for the resulting lack of transparency. Going forward, I'll return to a two-week cycle of email updates for this PMC. Please reach out to me or Chip if you have concerns over continuing the "offline" model for the Utilities PMC. ## CLI [CLI v6.12.3][] was released on August 31st, which notably includes many community PRs and remove of codegangsta in preparation for an epic to revamp `cf help`. [CLI v6.12.3]: https://github.com/cloudfoundry/cli/releases/tag/v6.12.3 CLI has scheduled an inception on 2015-09-09 in San Francisco, Greg Oehmen will be sending out details later this week. ## Java Utilities Work continues on moving the Eclipse tools for Cloud Foundry to the Eclipse Foundation. Immediate goal is inclusion in the Luna SR1 release. The team is planning an inception for "v2" of `cf-java-client`. Immediate goals will include support for CCv3 and to improve upon decisions made during the initial implementation. We expect the inception planning process to take some time, while some high-level design work is done to build abstractions on top of a large number of API endpoints.
|
|
|
|
Re: UAA restart invalidates a valid token
Filip Hanik
After the fix, having override: true should not revoke the tokens. If it
toggle quoted messageShow quoted text
still does, then it's a bug and we would like to know. thanks
On Wed, Sep 9, 2015 at 8:37 AM, Kayode Odeyemi <dreyemi(a)gmail.com> wrote:
Awesome.
|
|
|
|
Re: UAA restart invalidates a valid token
Paul Bakare
Awesome.
toggle quoted messageShow quoted text
option 2 is definitely the cause of the problem. Thank you very much.
On Wed, Sep 9, 2015 at 4:32 PM, Filip Hanik <fhanik(a)pivotal.io> wrote:
We introduced a feature called 'revokable tokens'. A token would
|
|
|