Date   
Feedback requested: More than one service possible with the same name

Jennifer Spinney
 

Hi cf-dev,


As part of the work to support different service brokers being able to provide services and service plans with the same name (See “Improving Service Access in Cloud Foundry” [1]), we came across an Cloud Controller API change we’d like to make that has the potential to be disruptive to current clients, depending what assumptions they’re making.

The list services endpoint (i.e., GET /v2/services) allows a client to specify a service name as a query parameter (i.e., GET /v2/services?q=label:<service-name>). This endpoint always returns an array, even though today that array can only consist of 1 or 0 elements, since service names are globally unique across the entire platform.


In the future we plan to allow different services to have the same name, as long as the services are being provided by different brokers, which leads to the possibility of this request returning an array with two or more elements.

Our concern is that some clients might be currently relying on the fact that today’s response, while an array, can only respond with at most one service. Hence if two (or more) services are being returned such a client might pick the first one without realizing it might be the wrong service.


We’d like to know if anyone is using this endpoint in that way and whether they’d be affected by this query now possibly returning more than one service in the returned array.

Thanks,
Services API (SAPI) Team


Re: [cf-bosh] Xenial stemcells now available: migration plan

Dr Nic Williams
 

Frédéric, when will Xenial stemcells move from X to X.Y version numbering with less regular updates of the major version X? This will help compiled releases to not have to update as often.

Nic

 


From: 30461002200n behalf of
Sent: Wednesday, July 11, 2018 7:02 am
To: cf-bosh@...; cf-dev@...
Subject: [cf-bosh] Xenial stemcells now available: migration plan
 

Hi everyone.


My name is Frédéric. I joined the BOSH team as a product manager recently, and work from Pivotal's Toronto office. Nice to meet you all!


A few weeks ago, the BOSH team introduced a new stemcell line based on Ubuntu 16.04 (Xenial Xerus) on bosh.io. For the time being, this line will be maintained in parallel with the previous ones, based on Ubuntu 14.04 (Trusty Tahr).


Canonical will provide security updates for Trusty until April 2019 per their official support lifecycle policy. Because Canonical will no longer provide security updates for Trusty after April 2019, we strongly recommend users start migrating towards the Xenial-based stemcell line now.


The BOSH team will continue to support the current 3586.x line of Trusty-based stemcells with upstream security patches until the CFAR migration to Xenial is complete. We do not plan on releasing any new major versions of Trusty-based stemcells, unless consumers have a specific request for a new major, and instead will focus on Xenial going forward.


We are currently evaluating when we will retire the Trusty-based stemcells, and are looking for feedback from the community about technical blockers that could impede the adoption of Xenial stemcells. If you are a release author, please take the time to verify your software on Xenial-based stemcells at the earliest opportunity. As a reminder, operators using cf-deployment must keep in mind that the repository will switch to Xenial-based stemcells well before April 2019 and should plan accordingly (more details on this can be found here).


    Frédéric Desbiens
    Product Manager | Pivotal Cloud Foundry BOSH

Xenial stemcells now available: migration plan

Frédéric Desbiens
 

Hi everyone.


My name is Frédéric. I joined the BOSH team as a product manager recently, and work from Pivotal's Toronto office. Nice to meet you all!


A few weeks ago, the BOSH team introduced a new stemcell line based on Ubuntu 16.04 (Xenial Xerus) on bosh.io. For the time being, this line will be maintained in parallel with the previous ones, based on Ubuntu 14.04 (Trusty Tahr).


Canonical will provide security updates for Trusty until April 2019 per their official support lifecycle policy. Because Canonical will no longer provide security updates for Trusty after April 2019, we strongly recommend users start migrating towards the Xenial-based stemcell line now.


The BOSH team will continue to support the current 3586.x line of Trusty-based stemcells with upstream security patches until the CFAR migration to Xenial is complete. We do not plan on releasing any new major versions of Trusty-based stemcells, unless consumers have a specific request for a new major, and instead will focus on Xenial going forward.


We are currently evaluating when we will retire the Trusty-based stemcells, and are looking for feedback from the community about technical blockers that could impede the adoption of Xenial stemcells. If you are a release author, please take the time to verify your software on Xenial-based stemcells at the earliest opportunity. As a reminder, operators using cf-deployment must keep in mind that the repository will switch to Xenial-based stemcells well before April 2019 and should plan accordingly (more details on this can be found here).


    Frédéric Desbiens
    Product Manager | Pivotal Cloud Foundry BOSH

Re: CF Application Runtime PMC - CF Networking Project Lead Call for Nominations

Dieu Cao <dcao@...>
 

Hello all,

Pivotal is nominating Preethi Varambally for the CF Networking Project Lead in the Application Runtime PMC.

Any other nominations should be sent to me/in reply by end of day July 3rd, 2018.

Preethi previously worked as a technical product owner and business analyst at a GIS company on a customer facing web application. Here, along with managing the product, she also worked on designing application layer data flow architecture for efficiently getting data from various source systems.

Prior to this, she worked as an engineer, building data tracking and reporting tools using MVC framework and gradually moved to a product owner role managing a team of onshore and offshore engineers.

Preethi holds a Masters degree in Computer Science from University of Texas, Dallas. 

-Dieu Cao

On Mon, Jul 2, 2018 at 11:45 AM Dieu Cao <dcao@...> wrote:
Hello All,

Usha Ramachandran, the Project Lead for the CF Networking team within the Application Runtime PMC, is rotating into a role internal to Pivotal. We thank her for her time serving as the CF Networking Project Lead.

The CF Networking team, split between San Francisco and Santa Monica, now has an opening for its project lead. Project leads must be nominated by a Cloud Foundry Foundation member.

Please send nominations to me/in reply to this posting by end of day July 11th, 2018.

If you have any questions about the role/process, please let me know.
These are described in the CFF governance documents. [1]

-Dieu Cao

CF Application Runtime PMC Lead

cf-deployment transition to Xenial stemcell

Josh Collins
 

CF-Deployment default to Ubuntu 16.04 (Xenial Xerus) BOSH stemcells in late-Fall/early-Winter 2018.


Canonical will stop providing security updates for the current Ubuntu 14.04 (Trusty Tahr), the current cf-deployment default, in April 2019 per their official support lifecycle policy.


CF-Deployment plans to transition to the fully-supported Xenial stemcell lines well before April 2019 and we’ll need each component team to validate the Xenial stemcell against their components before making the switch.


If each component's features are confirmed compatible before the end of September 2018, we should be able to hit our intended target for the transition.


CF-D/Xenial Status to-date:

  • The CF-Deployment Release Integration team (RelInt) began testing Xenial in cf-deployment via experimental ops files on June 8th 2018 (in cf-deployment release v1.40.0).
  • From June 8th forward, RelInt has been running cf-acceptance-tests (CATs) against our experimental pipeline with Xenial enabled.
  • We have observed no discernible effect on the CATs failure rate before/after transitioning to Xenial.


This message is a gentle invitation to begin/continue validating your component against Xenial.


Note that RelInt validates releases via CATs. The scope of CATs is purposely limited to validating core cf workflows.

The stability of cf-deployment releases assumes each component team executes a much deeper level of component-specific testing before integrating into cf-deployment.

For this reason, we don't/won't recommend using Xenial for production installs of cf-deployment nor make Xenial default in CF-D until each component team has validated that all its supported features are compatible with the Xenial stemcell.


We've proven Xenial can be run in a pipeline and CATs will pass so now's the time.

Please do due diligence and let us know when you've completed your validation.


And as always, please feel free to reach out to RelInt with any questions, issues, comments or suggestions you may have.

Thanks so much!

Josh Collins
Release Integration PM

Service Plan Descriptions

Alexander Blease <ablease@...>
 

Hi Everyone,


The Services API team is thinking about limiting the size of service plan descriptions to 10,000 characters, upon registering a service broker in Cloud Foundry. We would be keen to hear from people who have specific use cases for descriptions that are longer than 10,000 chars.


If we imposed this limit, would you strongly object to this change, and why?


If you have thoughts, queries, concerns, please contact us on the #sapi channel on the Cloud Foundry Slack, or respond directly to this email.


Cheers,


Alex + Niki



Re: New PM for CF AutoScaler project [Re: PM Vacancy for Auto-Scaler]

Marco Nicosia
 

Welcome to the project, Bo!


On Thu, Jul 5, 2018 at 07:38 Michael Maximilien <maxim@...> wrote:
Hi, all,

Please welcome Bo Yang (on cc:) of IBM as PM for CF App AutoScaler Extensions project [0].


You can keep up with the project’s monthly drumbeat as well as other CF Extensions updates here [1].


Welcome Bo, I look forward to working with you.


Best,




On Jun 25, 2018, at 1:02 PM, Michael Maximilien <maxim@...> wrote:

Hi, all,

We have a PM vacancy for the AutoScaler project and the team has nominated Bo Yang from IBM (one of the lead engineers for the initial project) as replacement.

Please suggest any other nominations before July 2nd. We will decide after if a vote is necessary.

Thanks for your time. Best,

dr.max
ibm ☁ 
silicon valley, ca


--
You received this message because you are subscribed to the Google Groups "PMC Council" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pmc-council+unsubscribe@....
To post to this group, send email to pmc-council@....
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/pmc-council/OFCD4858D1.8DFC287A-ON002582B7.006E06D5-1529956907534%40notes.na.collabserv.com.

--
--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: 650-796-2948

Re: cf-deployment 3.0

Franks, Geoff
 

How long will 1.x, and 2.x cf-deployments be maintained with security patches? Without that, it sounds like there’s potential for a lot of organizations to be faced with breaking changes and instability every time they upgrade (if upgrade cycles internally take a month or two, and major versions are coming out as often or more), not to mention the difficulties of jumping multiple major versions at once.

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Tuesday, July 3, 2018 at 6:16 PM
To: cf-eng <cf-eng@...>, cf-pm <cf-pm@...>, "cf-dev@..." <cf-dev@...>, CF Dev <cf-dev-eng@...>
Subject: [External] [cf-dev] cf-deployment 3.0

 

Hey Y'all,

 

Cf-deployment 3.0 is around the corner. 

We're going to go 3.0 in 2-3 weeks.

 

We released cf-deployment 2.0 on June 18th and included 'breaking' changes.

 

Breaking changes in the context of cf-d are changes which would require special attention from operators for the deployment to succeed. Executing the same bosh deploy command/args run used in the previous deployment may fail depending on which ops files and features operators had deployed with in the past.

 

Going forward, we'd like to introduce a more regular (~monthly) cadence to major point releases of cf-deployment.

 

The goal is two-fold and in-order-of-importance:

  1. provide a reliable mechanism for cf component teams to integrate and release major  changes
  2. mitigate fear of major point releases in the minds of operators/cf-consumers

 

As of today, we've got one PR that includes breaking changes and I'm putting out a call to y'all.

If you've got what you'd consider to be a breaking change that warrants going out in a major point release of cf-deployment, please submit your PRs and reach out to the RelInt team as soon as you're able to so we can come up to speed and support you!

 

Cheers,

 

Josh

 

 

 

 

 

New PM for CF AutoScaler project [Re: PM Vacancy for Auto-Scaler]

Michael Maximilien
 

Hi, all,

Please welcome Bo Yang (on cc:) of IBM as PM for CF App AutoScaler Extensions project [0].


You can keep up with the project’s monthly drumbeat as well as other CF Extensions updates here [1].


Welcome Bo, I look forward to working with you.


Best,




On Jun 25, 2018, at 1:02 PM, Michael Maximilien <maxim@...> wrote:

Hi, all,

We have a PM vacancy for the AutoScaler project and the team has nominated Bo Yang from IBM (one of the lead engineers for the initial project) as replacement.

Please suggest any other nominations before July 2nd. We will decide after if a vote is necessary.

Thanks for your time. Best,

dr.max
ibm ☁ 
silicon valley, ca


--
You received this message because you are subscribed to the Google Groups "PMC Council" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pmc-council+unsubscribe@....
To post to this group, send email to pmc-council@....
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/pmc-council/OFCD4858D1.8DFC287A-ON002582B7.006E06D5-1529956907534%40notes.na.collabserv.com.

Re: [CAUTION] Re: [cf-dev] Proposed BOSH logging interface

Marco Voelz
 

Dear Jesse,

 

did anything come out of this proposal? Did you end up picking up this track of work?

 

Warm regards

Marco

 

From: <cf-dev@...> on behalf of Marco Voelz <marco.voelz@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Tuesday, 8. May 2018 at 10:08
To: "cf-dev@..." <cf-dev@...>, Dmitriy Kalinin <dkalinin@...>
Subject: [CAUTION] Re: [cf-dev] Proposed BOSH logging interface

 

Dear Jesse,

 

Thanks for putting this proposal out there. We would be happy to see an automated logfile forwarding mechanism. Here's a couple of comments on your initial points:

* Including the filename in the syslog metadata is very useful and something we'd really like to have. Currently it is something we're working around a bit.

* The appname/tag field should probably contain the release's name as well as a prefix. My proposal here is `<deployment name>.<instance group name>.<job name>`. wdyt?

* We haven't made any particular use of the priority field, so losing control over this field wouldn't matter for out use-cases. Severity is usually something that the actual log message needs to contain, as the logger's severity can only be set on its initial creation, afaik.

* Restricting the depth of recursion seems reasonable. So far, I don't think we're using bosh releases which have more than 1 folder below their /var/vcap/sys/log/<job name>/ folder.

 

Concerning the requirements about permissions on the logfiles you'd want to forward: Did you talk to Dmitriy/the BOSH team about this? With stemcell series 3541.x the permissions on the standard folders below /var/vcap were tightened a bit, so just wanted to make sure that your assumptions are in line with the upcoming changes in the stemcells.

 

Warm regards

Marco


From: cf-dev@... <cf-dev@...> on behalf of Jesse T. Alford <jalford@...>
Sent: Tuesday, April 3, 2018 12:55:38 AM
To: cf-dev@...
Subject: [cf-dev] Proposed BOSH logging interface

 

Hello! We're the CF Platform Logging team. We maintain `syslog-release` and have been working to improve and regularize platform logging behavior.

 

This is a proposal intended to establish reasonable expectations about what should be logged and what should be forwarded in bosh-deployed cloud systems.

 

Historically, it has been up to each release to provide for their log forwarding, if any. We intend `syslog-release` to provide a consistent interface useful enough to replace all other provisions for the forwarding of logs from bosh jobs.

 

## Proposed Interface

If log forwarding is enabled, some files in `/var/vcap/sys/log` (and its subdirectories, recursively), will have any line written to them forwarded as the MSG portion of an RFC5424 compliant syslog message. Which files are forwarded is governed first by file extension, and secondarily by file permissions.

 

`syslog-release` attempts to read any file ending in `.log`.

(This allows us to avoid forwarding rotated logs, swapfiles, etc.)

It will forward from such files if either of the following are true:

- it is world-readable

- it is readable to the `vcap` group

 

In particular, this means that logs will not be forwarded from files where:

- user and group are root:root

- user and group are vcap:root or vcap:none

- user and group are vcap:vcap, but it is not group-readable

 

…unless they are world-readable.

 

We think that this interface will allow us to avoid running a log forwarder with elevated permissions, while also allowing jobs to, for instance, write DEBUG or similar logs to a file that is not group-readable, thus improving their security and reducing the load on the logging system while still making them available on the ephemeral disk for debugging purposes.

 

## Questions

There are a couple of things around this interface we're especially interested in feedback on, in addition to the obvious "will this be a problem for you" overall question.

 

We may have to have a proviso that the depth of this is not unlimited. This depends somewhat on what is inexpensive to implement and maintain, and is an area we'd appreciate feedback on. Is three levels deep from `/var/vcap/sys/log` (i.e. `/var/vcap/sys/log/jobname/processname/*`) enough? Would four be?

 

In the old way of doing things, more control over the PRI information and other syslog fields was available to release authors. Logs forwarded from files currently all come out as PRI 14, which translates to Facility: User, Severity: Info. Additionally, the appname/tag field is set to the name of the directory containing the log file. Is this enough/good info? If we were to include the filename, too, would that be useful? Sufficient?

 

## Testing with the Proposed Interface

We have recently implemented a feature to help release authors evaluate the proposed interface. If you set `syslog.respect_file_permissions: true`, blackbox will not be run with elevated capabilities, and you'll be able to see what is and isn't forwarded under the proposed interface.

Re: Free to Migrate to BPM

Krannich, Bernd
 

Hi Josh,

 

This is great news, thanks for sharing!

 

So essentially, cf-deployment at some point in time will run containerized processes, even on “plain VMs”, excellent.

 

This coincides with the mail from Cornelius (https://lists.cloudfoundry.org/g/cf-dev/message/8120) around Containerizing CF. When discussing the Containerizing proposal, our hope was always that BPM adoption would pick up so that converting into Kubernetes artifacts could benefit from the BPM metadata.

 

Seems like all of this is now nicely falling in place.

 

Thanks,

Bernd

 

Bernd Krannich

SAP Cloud Platform

SAP SE

Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

 

bernd.krannich@...

 

Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum

 

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

 

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.

 

 

From: <cf-dev@...> on behalf of Josh Collins <jcollins@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Tuesday, 3. July 2018 at 21:20
To: cf-pm <cf-pm@...>, "cf-dev@..." <cf-dev@...>, CF Dev <cf-dev-eng@...>
Subject: [cf-dev] Free to Migrate to BPM

 

Hey Y'all,

 

You may know this already, but I wanted to send out a broad communication to make sure you're in the know and to build a shared understanding about the process for migrating to BPM going forward.

 

As of cf-deployment v1.40.0, BPM is colocated on all instance groups in cf-d.

 

It's available for every component team to adopt when validated against their component's features.

 

To-date, teams that have completed validation have enabled BPM by including logic within their jobs to rely on BPM based on whether the `bpm.enabled` property is set to true for their jobs. And adding an entry to `operations/experimental/enable-bpm.yml` to set that property/value to true in the deployment manifest.

 

The following jobs currently have entries in enable-bpm.yml:

  • uaa
  • route-emitter
  • rep
  • bbs
  • auctioneer
  • ssh-proxy
  • file-server

Now that BPM is on each VM by default you can validate your components in your pipelines by enabling BPM directly within your job(s).

 

And when ready to publish your bpm-enablement changes in a release, please... 

 

For each team that has a component/job that's already validated against BPM, it would be great if you could enable it directly as per above and, if appropriate, submit a PR which removes the entry from `enable-bpm.yml.` 

 

At some point in the relatively near future, I'll delete `enable-bpm.yml,` but only after all components listed have enabled it and I've heard folk's pipelines no longer rely on it's existence.

 

Thank you for reading this through and thanks very much in advance for replying with any questions, feedback, or suggestions and issues related to this communique.

 

Cheers,

 

Josh

 

 

 

 

 

cf-deployment 3.0

Josh Collins
 

Hey Y'all,

Cf-deployment 3.0 is around the corner. 
We're going to go 3.0 in 2-3 weeks.

We released cf-deployment 2.0 on June 18th and included 'breaking' changes.

Breaking changes in the context of cf-d are changes which would require special attention from operators for the deployment to succeed. Executing the same bosh deploy command/args run used in the previous deployment may fail depending on which ops files and features operators had deployed with in the past.

Going forward, we'd like to introduce a more regular (~monthly) cadence to major point releases of cf-deployment.

The goal is two-fold and in-order-of-importance:
  1. provide a reliable mechanism for cf component teams to integrate and release major  changes
  2. mitigate fear of major point releases in the minds of operators/cf-consumers

As of today, we've got one PR that includes breaking changes and I'm putting out a call to y'all.
If you've got what you'd consider to be a breaking change that warrants going out in a major point release of cf-deployment, please submit your PRs and reach out to the RelInt team as soon as you're able to so we can come up to speed and support you!

Cheers,

Josh





Free to Migrate to BPM

Josh Collins
 

Hey Y'all,

You may know this already, but I wanted to send out a broad communication to make sure you're in the know and to build a shared understanding about the process for migrating to BPM going forward.

As of cf-deployment v1.40.0, BPM is colocated on all instance groups in cf-d.

It's available for every component team to adopt when validated against their component's features.

To-date, teams that have completed validation have enabled BPM by including logic within their jobs to rely on BPM based on whether the `bpm.enabled` property is set to true for their jobs. And adding an entry to `operations/experimental/enable-bpm.yml` to set that property/value to true in the deployment manifest.

The following jobs currently have entries in enable-bpm.yml:
  • uaa
  • route-emitter
  • rep
  • bbs
  • auctioneer
  • ssh-proxy
  • file-server
Now that BPM is on each VM by default you can validate your components in your pipelines by enabling BPM directly within your job(s).

And when ready to publish your bpm-enablement changes in a release, please... 

For each team that has a component/job that's already validated against BPM, it would be great if you could enable it directly as per above and, if appropriate, submit a PR which removes the entry from `enable-bpm.yml.` 

At some point in the relatively near future, I'll delete `enable-bpm.yml,` but only after all components listed have enabled it and I've heard folk's pipelines no longer rely on it's existence.

Thank you for reading this through and thanks very much in advance for replying with any questions, feedback, or suggestions and issues related to this communique.

Cheers,

Josh





Incubation proposal: CF Containerization

Cornelius Schumacher <cschum@...>
 

Hi all,

We would like to propose the CF Containerization effort for incubation in the
BOSH PMC.

The full proposal can be found here:
https://docs.google.com/document/d/1_IvFf-cCR4_Hxg-L7Z_R51EKhZfBqlprrs5NgC2iO2w/edit

As a first step towards this, we are proposing the Fissile code base as a
starting point, with the goal of transforming it in the direction of the above
proposal. Fissile is a tool that allows developers to convert existing BOSH
releases to docker images and deploy them to Kubernetes. Fissile is currently
used in SUSE CAP (https://www.suse.com/products/cloud-application-platform)
and IBM Cloud Foundry Enterprise Environment (https://console.bluemix.net/
docs/cloud-foundry/).

Fissile is fully open source and can currently be found on GitHub at
https://github.com/SUSE/fissile

The project would follow a distributed committer model.

Project Lead: Vlad Iovanov
Initial Committers:
- Jan Dubois (SUSE)
- Mark Yen (SUSE)
- Mario Manno (SUSE)
- Enrique Encalada (IBM)
- Matthias Diester (IBM)
- Gong (Grace) Zhang (IBM)

SAP is also currently evaluating additional staffing.

We are looking forward to your questions and comments.

Best Regards,
Cornelius

--
Cornelius Schumacher <cschum@...>

Re: (action requested) cf app display changes

Abby Chau
 

Hi all,

Thank you to everyone who gave us feedback on changing  the `cf app` display summary information. We really appreciate your input. 

We've taken your feedback into consideration and have decided to move forward with app display option #2 - see below [1]. Since option #3 (being able to provide a `--process` specific flag) was also popular, we are open to supporting this feature in the future as we receive more feedback about usage of procfiles and multiple processes. 

See this document for a summary of upcoming changes, and please do not hesitate to reach out if you have any additional questions. 

Best,

Abby

[1]  



On Fri, Jun 22, 2018 at 9:40 AM, Abby Chau <achau@...> wrote:
Here is the link to the survey: https://goo.gl/forms/5lHCbAIEiQf03G1g2. Thanks!

On Fri, Jun 22, 2018 at 9:36 AM, Abby Chau <achau@...> wrote:
Hi everyone,

The CF CLI team sent out a two minute survey recently to gather feedback on changes [1] to the `cf app` display summary information. Please have your say on how the `cf app` summary will change in a future release. Thanks!

Best,

Abby Chau and the CLI team
CF Product Manager, CF CLI


[1]  Based on your feedback recently, we've decided to change the `cf app` to default to the v3 app endpoint. What this means is: 
  • users on CC API 3.27.0 or higher, the `cf app app-name` display will change in an upcoming CF CLI release - how the display will change is largely based on your feedback above 
  • for users on CC API 3.27.0 or lower, you will continue to see the current `cf app app-name` display; you will not see the new v3 display unless you upgrade to CC API 3.27.0 or higher (and you have the latest version of the CF CLI)


CF Application Runtime PMC - CF Networking Project Lead Call for Nominations

Dieu Cao <dcao@...>
 

Hello All,

Usha Ramachandran, the Project Lead for the CF Networking team within the Application Runtime PMC, is rotating into a role internal to Pivotal. We thank her for her time serving as the CF Networking Project Lead.

The CF Networking team, split between San Francisco and Santa Monica, now has an opening for its project lead. Project leads must be nominated by a Cloud Foundry Foundation member.

Please send nominations to me/in reply to this posting by end of day July 11th, 2018.

If you have any questions about the role/process, please let me know.
These are described in the CFF governance documents. [1]

-Dieu Cao

CF Application Runtime PMC Lead

Re: Quick (2 min) survey for the Cloud Foundry Community!

Chris Clark
 

All you CF contributors and community folks out there, please take a quick 2 minutes and compete this survey, if you would!  This will help us get a sense of the makeup of the Cloud Foundry Community, and it's super fast.  Thank you!

On Wed, Jun 20, 2018 at 4:33 PM, Chris Clark <cclark@...> wrote:
***note, if you are a dedicated Cloud Foundry committer, this is identical to a survey we sent out to you in January.  If you completed that survey, you can ignore this***

- Do you work on Cloud Foundry?
- Have you submitted a pull request or an issue to a Cloud Foundry project?
- Have you written, edited or updated cf-docs?
- Have you participated in a discussion that materialized into a project/update?
- Have you helped champion Cloud Foundry at a Meetup, CF Summit, or an industry event?
- Have you shared your enthusiasm and inspired folks to join the Cloud Foundry community?
Answered Yes to any of the above? Then please take this survey and help us measure our community’s diversity.

Thank you!

- The Cloud Foundry Foundation



--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation

Re: CF CLI: how do you use `no-start` with `cf push`

Dr Nic Williams
 

I use no-start because ‘cf push’ doesn’t have flags to set env vars/service bindings.

If the response to that is “use manifest.yml” then perhaps get rid off all the push flags and force ppl to use manifest.yml. As it stands now, we can cf push most attributes of the manifest.yml, except env vars and service bindings.


From: cf-dev@... <cf-dev@...> on behalf of Hjortshoj, Julian <Julian.Hjortshoj@...>
Sent: Friday, June 29, 2018 3:06:03 AM
To: cf-dev@...
Subject: Re: [cf-dev] CF CLI: how do you use `no-start` with `cf push`
 
We have not tried the v3 api, but yes, that sounds correct to me, and v3-create-app seems like a reasonable substitute.

From: cf-dev@... [cf-dev@...] on behalf of Zach Robinson [zrobinson@...]
Sent: Wednesday, June 27, 2018 4:58 PM
To: cf-dev@...
Subject: Re: [cf-dev] CF CLI: how do you use `no-start` with `cf push`

thanks to all that have replied.

i'd like to ask a clarifying question.  it sounds like most of these use-cases are "set up some environment for the app".  this implies to me that these workflows are for new apps and not for updating existing ones.  does that sound right?  are their use-cases for "no-start" when updating an app?

thanks!
-zach

On Wed, Jun 27, 2018 at 4:30 PM Abby Chau <achau@...> wrote:
Hey Bernd and Julian,

Many thanks for your responses. 

Wondering if you folks have tried using the `v3-create-app` command as Mike has pointed out (and Zach elsewhere). The command is basically the equivalent of `cf push test --no-start` in that it creates an app, leaves it in a `stopped` state, and users can then apply configurations, bind services, set-groups, enable ssh, etc. This command appears to be a workaround for your use cases, but please let us know if that's incorrect. 

Best,

Abby

On Wed, Jun 27, 2018 at 3:04 PM, Hjortshoj, Julian <Julian.Hjortshoj@...> wrote:
+1 to that last use case.  In particular, if a service requires bind configuration, then it's not possible to put the binding in an app manifest (because manifests don't support service binding configuration) so it is very helpful to keep your app from starting until the service is bound.

Adding the ability to specify bind configuration in an application manifest might be a reasonable mitigation if --no-start were to disappear.

HTH,
-Julian

From: cf-dev@... [cf-dev@...] on behalf of Krannich, Bernd [bernd.krannich@...]
Sent: Wednesday, June 27, 2018 9:55 AM
To: cf-dev@...
Subject: Re: [cf-dev] CF CLI: how do you use `no-start` with `cf push`

Hi Abby,

 

Thank you very much for reaching out. Indeed, we are frequent users of the `no-start` flag. A couple of use cases:

 

  • After a `cf ssh-enable APP_NAME`, you’ll need to restart your app to be able to SSH in. To prevent starting the app twice in that process, people do a `cf push --no-start` and then an explicit `cf start APP_NAME` afterwards.
  • The same applies for changes of security groups which also require an app restart.
  • Lastly, and maybe most importantly, people use `no-start` for pushing an app to which they want to bind services. They push the app with “no-start”, “cf create-service” their services, “cf bind-service” them to the app, and only then start the app.

 

So, I guess in summary, for all operations changing the app environment, doing those changes with the app not yet started is a common use case for us.

 

Regards,

Bernd

 

Bernd Krannich

SAP Cloud Platform

SAP SE

Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

 

bernd.krannich@...

 

Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum

 

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

 

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.

 

 

From: <cf-dev@...> on behalf of Abby Chau <achau@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Wednesday, 27. June 2018 at 18:18
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev@...>
Subject: [cf-dev] CF CLI: how do you use `no-start` with `cf push`

 

Hi everyone,

 

The CF CLI is soliciting feedback on how you use the `no-start` flag: 

  • what are your specific use cases? 
  • if the flag was no longer available, how might that affect you? (Would you strongly object to such a change, and why?) would you have a sensible workaround?

 

Feedback

 

Please contact us on the #cli channel on Cloud Foundry Slack. Alternatively, respond directly to this email.



Best,



Abby Chau

CF Product Manager, CF CLI



 

Note: The CF CLI team is currently working on updating the `cf v3-push` command to use the server side manifest work we've completed (with the Capi team), and to update the command such that it has as much feature parity with the current `cf-push` as possible. The eventual goal is to make the `cf push` command default to the enhanced v3-push command for users (on cc api 3.27 or higher). Since there is more granular control options in v3, `no-start` is a more nebulous flag.


Removing varz support for Routing components

Shubha Anjur Tupil
 

Hi, 

To walk down memory lane a bit, the varz endpoints were replaced with the firehose more than two years ago. The relevant threads are


In the interest of code maintenance for the routing components we are considering removing the code to support the varz endpoints. All users should have transitioned to using the firehose nozzle. Let us know if and why this might be a problem. 

Regards, 
Shubha


Re: CF CLI: how do you use `no-start` with `cf push`

Hjortshoj, Julian <Julian.Hjortshoj@...>
 

We have not tried the v3 api, but yes, that sounds correct to me, and v3-create-app seems like a reasonable substitute.

From: cf-dev@... [cf-dev@...] on behalf of Zach Robinson [zrobinson@...]
Sent: Wednesday, June 27, 2018 4:58 PM
To: cf-dev@...
Subject: Re: [cf-dev] CF CLI: how do you use `no-start` with `cf push`

thanks to all that have replied.

i'd like to ask a clarifying question.  it sounds like most of these use-cases are "set up some environment for the app".  this implies to me that these workflows are for new apps and not for updating existing ones.  does that sound right?  are their use-cases for "no-start" when updating an app?

thanks!
-zach

On Wed, Jun 27, 2018 at 4:30 PM Abby Chau <achau@...> wrote:
Hey Bernd and Julian,

Many thanks for your responses. 

Wondering if you folks have tried using the `v3-create-app` command as Mike has pointed out (and Zach elsewhere). The command is basically the equivalent of `cf push test --no-start` in that it creates an app, leaves it in a `stopped` state, and users can then apply configurations, bind services, set-groups, enable ssh, etc. This command appears to be a workaround for your use cases, but please let us know if that's incorrect. 

Best,

Abby

On Wed, Jun 27, 2018 at 3:04 PM, Hjortshoj, Julian <Julian.Hjortshoj@...> wrote:
+1 to that last use case.  In particular, if a service requires bind configuration, then it's not possible to put the binding in an app manifest (because manifests don't support service binding configuration) so it is very helpful to keep your app from starting until the service is bound.

Adding the ability to specify bind configuration in an application manifest might be a reasonable mitigation if --no-start were to disappear.

HTH,
-Julian

From: cf-dev@... [cf-dev@...] on behalf of Krannich, Bernd [bernd.krannich@...]
Sent: Wednesday, June 27, 2018 9:55 AM
To: cf-dev@...
Subject: Re: [cf-dev] CF CLI: how do you use `no-start` with `cf push`

Hi Abby,

 

Thank you very much for reaching out. Indeed, we are frequent users of the `no-start` flag. A couple of use cases:

 

  • After a `cf ssh-enable APP_NAME`, you’ll need to restart your app to be able to SSH in. To prevent starting the app twice in that process, people do a `cf push --no-start` and then an explicit `cf start APP_NAME` afterwards.
  • The same applies for changes of security groups which also require an app restart.
  • Lastly, and maybe most importantly, people use `no-start` for pushing an app to which they want to bind services. They push the app with “no-start”, “cf create-service” their services, “cf bind-service” them to the app, and only then start the app.

 

So, I guess in summary, for all operations changing the app environment, doing those changes with the app not yet started is a common use case for us.

 

Regards,

Bernd

 

Bernd Krannich

SAP Cloud Platform

SAP SE

Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

 

bernd.krannich@...

 

Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum

 

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

 

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.

 

 

From: <cf-dev@...> on behalf of Abby Chau <achau@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Wednesday, 27. June 2018 at 18:18
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev@...>
Subject: [cf-dev] CF CLI: how do you use `no-start` with `cf push`

 

Hi everyone,

 

The CF CLI is soliciting feedback on how you use the `no-start` flag: 

  • what are your specific use cases? 
  • if the flag was no longer available, how might that affect you? (Would you strongly object to such a change, and why?) would you have a sensible workaround?

 

Feedback

 

Please contact us on the #cli channel on Cloud Foundry Slack. Alternatively, respond directly to this email.



Best,



Abby Chau

CF Product Manager, CF CLI



 

Note: The CF CLI team is currently working on updating the `cf v3-push` command to use the server side manifest work we've completed (with the Capi team), and to update the command such that it has as much feature parity with the current `cf-push` as possible. The eventual goal is to make the `cf push` command default to the enhanced v3-push command for users (on cc api 3.27 or higher). Since there is more granular control options in v3, `no-start` is a more nebulous flag.