|
PCF_DEV_USER_PROVIDED_SERVICE
harneet chugga <harneet.chugga@...>
Hello all, I am trying to create user provided service of postgres running on my local machine. I want to bind postgres service to my app running on PCF_DEV. I have created the user and db on postgres. Please provide step by step to proceed forward. Regards, Harneet
|
|
|
|
Re: Proposal for Incubation in the Extensions PMC: CF Dev
Hjortshoj, Julian <Julian.Hjortshoj@...>
Is it too late to change the name? I suspect that folks might not instantly understand that cf-dev and CF Dev are two entirely different things.
From: <cf-dev@...> on behalf of Stephen Levine <slevine@...>
Reply-To: "cf-dev@..." <cf-dev@...> Date: Friday, February 23, 2018 at 12:20 PM To: "cf-dev@..." <cf-dev@...> Cc: "Sisil, Scott (Pivotal)" <ssisil@...>, "Casey, Emily (Pivotal)" <ecasey@...>, Chip Childers <cchilders@...>, Michael Maximilien <maxim@...> Subject: [cf-dev] Proposal for Incubation in the Extensions PMC: CF Dev Hi All, Pivotal is proposing CF Dev for inclusion in the Extensions PMC as a new incubating project. CF Dev is a deployment of BOSH and cf-deployment that runs locally in Garden containers. It uses native hypervisors to start quickly with zero external dependencies. It also provides a fully functional BOSH director. CF Dev is currently available on Github [1]. I would also like to introduce everyone to Scott Sisil, who is joining me as Co-PM on Pivotal's local and community developer initiatives. Please reach out to Scott and/or myself for questions about CF Dev. Details: Project Name: CF Dev Project Proposal: See [2], and attached. Proposed Project Leads: Stephen Levine, Pivotal & Scott Sisil Pivotal Proposed Contributors: Emily Casey, Pivotal; Dave Protasowski, Pivotal; Stephen Hiehn, Pivotal Proposed Scope: See [2], and attached. Development Operating Model: Pairing (local + remote) Technical Approach: CF CLI plugin that starts a VM using the OS native hypervisor. Please let us know if you have any questions or feedback. [1] https://github.com/pivotal-cf/cfdev [2] https://docs.google.com/document/d/1QBTstRXN-1MmINZr1b1G5K6cM6bptQRvsafg_nyP8I8/edit#
|
|
|
|
A Cloud Foundry API Client for Python
#cf
adamjasojr@...
This is a Cloud Foundry python client I've been working on for a while. It supports authentication with UAA, all Cloud Controller endpoints, allows usage with both v2 and v3 of the Cloud Controller API, supports connecting to the logging firehose, and several other features. It also implements `cf push` for CF application manifests in pure python using the v2 API.
Github: https://github.com/hsdp/python-cf-api PyPI: https://pypi.python.org/pypi/cf_api ReadTheDocs: https://cf-api.readthedocs.io/en/latest/
|
|
|
|
Re: Proposal for Incubation in the Extensions PMC: CF Dev
Michael Maximilien
Moving others to bcc: to avoid too many emails. I’ll make sure to leave some feedback and would ask everyone to spend some time looking at Stephen’s proposal and leave your comments. Finally, let’s also discuss when you want to present this at an up coming CAB call. Have a great weekend all. Best, dr.max ibm ☁ silicon valley, ca dr.max ibm ☁ silicon valley, ca
On Feb 23, 2018, at 12:20 PM, Stephen Levine <slevine@...> wrote:
|
|
|
|
Re: Proposal for Incubation in the Extensions PMC: CF Dev
Julz Friedman
\o/
toggle quoted messageShow quoted text
Yassss. Nice.
On Fri, 23 Feb 2018 at 12:34, Amit Kumar Gupta <agupta@...> wrote:
|
|
|
|
Re: Proposal for Incubation in the Extensions PMC: CF Dev
Amit Kumar Gupta
YES!!! Thank you, Steven & team! > In progress: One command to have BOSH+CF running on macOS native hypervisor 🤩 Amit
On Fri, Feb 23, 2018 at 12:23 PM Stephen Levine <slevine@...> wrote:
|
|
|
|
Proposal for Incubation in the Extensions PMC: CF Dev
Stephen Levine
Hi All, Pivotal is proposing CF Dev for inclusion in the Extensions PMC as a new incubating project. CF Dev is a deployment of BOSH and cf-deployment that runs locally in Garden containers. It uses native hypervisors to start quickly with zero external dependencies. It also provides a fully functional BOSH director. CF Dev is currently available on Github [1]. I would also like to introduce everyone to Scott Sisil, who is joining me as Co-PM on Pivotal's local and community developer initiatives. Please reach out to Scott and/or myself for questions about CF Dev. Details: Project Name: CF Dev Project Proposal: See [2], and attached. Proposed Project Leads: Stephen Levine, Pivotal & Scott Sisil Pivotal Proposed Contributors: Emily Casey, Pivotal; Dave Protasowski, Pivotal; Stephen Hiehn, Pivotal Proposed Scope: See [2], and attached. Development Operating Model: Pairing (local + remote) Technical Approach: CF CLI plugin that starts a VM using the OS native hypervisor. Please let us know if you have any questions or feedback. [1] https://github.com/pivotal-cf/cfdev [2] https://docs.google.com/document/d/1QBTstRXN-1MmINZr1b1G5K6cM6bptQRvsafg_nyP8I8/edit#
|
|
|
|
REMINDER: CF-Extensions PMC February 2018 zoom call is Monday 02/26 @ 11a PST
Michael Maximilien
CC: cf-dev for those in broader community wishing to join and listen in. FYI... CF-Extensions project leads, please join us for the second *optional* zoom monthly call next week Monday 02/26 @ 11a PST As I said before, you do not have to attend. However, it is compulsory to share your project's drumbeat (few lines of status and highlights). Reply here or PR to link below. ------- I'll summarize everything in the February PMC notes, here: https://github.com/cloudfoundry/pmc-notes/blob/master/Extensions/2018/02-26-2018.md <= that I will share with community. Thanks for your time and zoom soon if you can join. Best, ------ dr.max ibm cloud labs silicon valley, ca maximilien.org
|
|
|
|
CF CLI install error using 'apt-get' for Ubuntu users
Sebastian Vidrio <svidrio@...>
Hello Ubuntu users of the CF CLI, Future versions of 'apt-get' might enforce https over http for updating sources. This affects the CF CLI install process. It seems that the most recent version of 'apt-get' was breaking our install procedure for Ubuntu 16.04. We believe that due to the library changes, it may also affect other versions of Ubuntu in the future. We recommend updating your installation procedure based on our updated documentation. Thanks, The CF CLI Team
|
|
|
|
Re: Announcing cf-release end of life
Mike Youngstrom <youngm@...>
Yes, congratulations. Now to begin the process of moving our custom templating to cf-deployment. Sigh. :) Mike
On Tue, Feb 20, 2018 at 11:30 AM, David Sabeti <dsabeti@...> wrote:
|
|
|
|
Re: Announcing cf-release end of life
Dieu Cao <dcao@...>
Hooray! A very long time coming. Congrats to the Release Integration team on getting this through!
|
|
|
|
Re: Noisy Neighbor Nozzle CLI - Quickly Determine High Volume Log Producers
#loggregator
kurt.kellner@...
With CF Top plugin there are two fields "LOG_OUT" and "LOG_ERR" which gives the total logged messages since cf top has been running. Although it doesn't give you a rate of messages per minute, it can quickly identify chatty apps. If you have "doppler.firehose" scope it will show logging totals for all apps, if not it will only show apps you have authority to see. You can sort by any column, so sorting on "LOG_OUT" column will show the top loggers.
|
|
|
|
Re: HTTP error code when route not found
Shannon Coen
Hello John, The root of the issue is that because Gorouter receives configuration for both container scheduling and routing from Diego, it can't tell the difference between an app that is crashing and one that is deleted or unmapped from the route. Achieving a more intuitive behavior has required a significant architectural change that we have put off in favor of features with higher benefit-to-cost ratio. Our integration with Istio gives us the opportunity redesign how the routing subsystem receives config from the rest of the platform. We intend that Envoy will return a 503 when an app is stopped or crashing. For details, see https://docs.google.com/document/d/1VldkvgWPUh13o5RCNjSvzoPFhbY9BtLqBDdk2k0z9fw/edit. Gorouter currently returns a 502 when it has backends for a route in its routing table, but it cannot establish a TCP connection to one of them after three tries. We will likely persist this behavior in our integration with Envoy. Best, Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.
On Tue, Feb 20, 2018 at 10:27 AM, Dieu Cao <dcao@...> wrote:
|
|
|
|
Re: Announcing cf-release end of life
Dr Nic Williams <drnicwilliams@...>
Long live cf-release!
|
|
|
|
Announcing cf-release end of life
David Sabeti
Hi cf-dev, I'm happy to announce the end of support for cf-release. A few weeks ago, we cut cf-release v287 -- the final version of cf-release. Last week, the Release Integration team shut down the last pipelines pertaining to cf-release and moved the repo to the Cloud Foundry attic. Some fun facts about cf-release:
Any operators still using cf-release should move to cf-deployment as the basis for their deployment manifest. We'll test the transition from cf-release to cf-deployment for another week or two. Thanks to all the teams and community members that worked on splitting out their code into new releases, built pipelines with cf-deployment when it was still prickly and new, and gave us feedback on the new tooling. Lastly, feel free to reach out to the Release Integration team in the #release-integration Slack channel, or open a Github issue on the cf-deployment repo. Thanks! David Sabeti & CF Release Integration
|
|
|
|
Re: HTTP error code when route not found
Dieu Cao <dcao@...>
The routing team I believe is considering this use case in the new routing control plane proposal as outlined in https://lists.cloudfoundry.org/g/cf-dev/message/7717 -Dieu
On Fri, Feb 16, 2018 at 9:26 AM, Mike Youngstrom <youngm@...> wrote:
|
|
|
|
Re: FINAL REMINDER: CAB call for February is Wednesday 02/21 @ 8a PST
Michael Maximilien
Community Advisory Board... Definitely community though not really a board per se. However, it’s absolutely the place to have your voice in the community be heard; and a monthly chance to zoom with the leaders of the different core and incubating projects. It’s fun. Ask Wayne from Stark & Wayne. Join us. Cheers, Max
On Tue, Feb 20, 2018 at 10:04 AM Jay Badenhope <jbadenhope@...> wrote:
-- dr.max
Sent from my iPhone
http://maximilien.org
|
|
|
|
Re: FINAL REMINDER: CAB call for February is Wednesday 02/21 @ 8a PST
Community Advisory Board.
On Tue, Feb 20, 2018 at 10:04 AM Jay Badenhope <jbadenhope@...> wrote:
-- -- Swarna Podila Senior Director, Community | Cloud Foundry Foundation
|
|
|
|
Re: FINAL REMINDER: CAB call for February is Wednesday 02/21 @ 8a PST
Jay Badenhope <jbadenhope@...>
Hey Max, What does "CAB" stand for? Jay
On Tue, Feb 20, 2018 at 9:38 AM, Michael Maximilien <maxim@...> wrote:
|
|
|
|
Re: Noisy Neighbor Nozzle CLI - Quickly Determine High Volume Log Producers
#loggregator
I can see that overlap, but there is an important scope difference to point out here. The Noisy Neighbor Nozzle requires Operator scope to read from the firehose and is intended for Platform wide monitoring, where as CF Top can be used by app developers to monitor the applications within their space. This is important because apps from one space can effect other spaces--although I can see the appeal of also adding this to the information app developers have access to.
|
|
|