Date   
Re: (action requested) Changing CF App Display

Abby Chau
 

Hi all,

We've analyzed the `cf app` survey results; thanks again to those who responded. Here's our findings and actions steps:

Based on your feedback, we have decided to change `cf app` to default to the v3 app endpoint:
  • what this means is that for users on CC API 3.27.0 or higher, the `cf app app-name` display will change in an upcoming CF CLI release 
  • 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)
Survey Results

Please see the image below for results of the survey. Only 6.3% of respondents said they would strongly object to changing the current `cf app app-name` display to default to the v3 app endpoint. 

Next Steps:
  • the v3 app endpoint treats processes as a first class citizen, and as such we want to display this in the most user-friendly way possible. As such, the CLI team is soliciting feedback on changing the UX design of the `cf app appname` to take advantage of v3 capabilities: Please complete this very short survey if you want to vote on the new UX. Voting ends on Tuesday, June . 26th. 
Feedback

If you have questions or concerns, please contact us on the #cli channel on Cloud Foundry Slack. Alternatively, respond directly to this email.

Please do not hesitate to reach out if you have any feedback or questions. Thanks again. 

Best, 

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


app_display_results.png




On Mon, Jun 11, 2018 at 9:49 AM Abby Chau <achau@...> wrote:
Hello cf-dev,

Thanks to those who have taken the short survey; we very much appreciate your feedback. If you haven't had a chance to take the survey, please take a look and give us your feedback on the cf app display.

Best,

Abby


On Tue, Jun 5, 2018 at 6:49 PM, Abby Chau <achau@...> wrote:
Hello cf-dev,

In order to provide a better user experience, the Cloud Foundry CLI team is considering changing the   cf app app-name  key-value and table display information. Towards this effort, we are asking the community to complete a short survey. 

Actions: Please fill out this short survey [1] to help us understand how you use the cf app app-name command display, and your thoughts on changing the display to default to the V3-app version of the command. The survey will close by end of day, June 15th. 

Thanks in advance for your time and participation.

Best,

Abby Chau
CF Product Manager - CLI


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

Chris Clark
 

***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

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

Brandon Hudlemeyer
 



On Wed, Jun 20, 2018, 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

(action requested) cf app display changes

Abby Chau
 

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)

Re: (action requested) cf app display changes

Abby Chau
 

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)

Action Required: Deprecating the built-in garden aufs filesystem driver ("garden-shed")

Julz Friedman
 

Hi cf-developnauts!

I wanted to quickly remind y'all, and seek any remaining feedback, about our plans to deprecate the garden-shed filesystem driver in an upcoming garden release

We previously communicated about this here [0], the tl;dr is we have a new filesystem driver implementation, named grootfs, which has been running in production for a while now. At the start of the year we made this the default in garden [1], with an opt-out property to temporarily re-enable the old implementation, in case of problems. It's now coming up on 6 months later.

As far as we know - and this is where you come in! - all remaining bugs, issues and blockers requiring people to opt out of the new driver are resolved, and we are therefore planning to remove the deprecated garden-shed driver, and corresponding config option, in an upcoming garden release. 

ACTION REQUIRED: If you were opting-out of grootfs for any reason, please urgently try again and report any bugs or blockers to us (via GitHub issues, #garden slack, or Tracker) so we can fix them! As of right now we believe everyone is fine for us to delete garden-shed, and we plan to do that soon unless we hear otherwise!

Thanks!
Julz, on behalf of the gardenandgroot team,

PM Vacancy for Auto-Scaler

Michael Maximilien
 

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


CF Application Runtime PMC - Release Integration Project Lead Call for Nominations

Dieu Cao
 

Hello All,

David Sabeti, the Project Lead for the Release Integration team within the Application Runtime PMC, is transitioning back to engineering. We thank him for his time serving as the Release Integration Project Lead.

The Release Integration team, primarily located in San Francisco, 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 3rd, 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

Feedback request - Polyglot service discovery for C2C networking

Preethi Varambally
 

Hi,


Polyglot service discovery has been available since early 2018. This feature provides DNS-based service discovery that lets apps find each others’ internal addresses. If you are using this feature, please fill out this form [1] to let us know your feedback on the feature.


[1] https://docs.google.com/forms/d/e/1FAIpQLSfOMI8YmO9HL5mnF30V38_yDjYMKtFOfdipr_Q51qKR_uQtTA/viewform?c=0&w=1


Thanks,

CF Networking team



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

Michael Maximilien
 

Hi, Dieu, David, and teams,

Let me personally (and on behalf of IBM’s CF team) thank David Sabeti for an outstanding job transitioning us all to cf-deployment.

In the process, also making CF releases, in general, easier to manage and deploy.

Well done and look forward to having him in other engineering roles.

Best,

Max

On Mon, Jun 25, 2018 at 5:15 PM Dieu Cao <dcao@...> wrote:
Hello All,

David Sabeti, the Project Lead for the Release Integration team within the Application Runtime PMC, is transitioning back to engineering. We thank him for his time serving as the Release Integration Project Lead.

The Release Integration team, primarily located in San Francisco, 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 3rd, 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

--
dr.max Sent from my iPhone http://maximilien.org

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

Dieu Cao
 

Hello all,

Pivotal is nominating Josh Collins for the Release Integration Project Lead in the Application Runtime PMC.  He is currently serving as Interim Project Lead for the Release Integration team.

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

Josh was previously the director of product management for a personalized products company and subsequently he managed the A/B testing and optimization efforts for a B2C career development company. Early in his career, Josh worked with a team of three to design and launch the flagship product of what is now a successful company in the backup and disaster recovery space. 

In a previous life, Josh worked for the Berkeley Unified School District as a middle-school teacher and supplemented his income selling foraged wild mushrooms to local restaurants in Berkeley and Oakland. While working as a teacher he ran the school's computer lab and began his journey into networking, graphic design,  web development and beyond. His early successes moonlighting on tech gigs changed his trajectory and ultimately leading to his current employment at  Pivotal.

Josh joined Pivotal R&D in March 2017.

Josh holds a BA in Art from the University of California, Santa Cruz and an MA in Education from University Washington Seattle.

-Dieu Cao


On Mon, Jun 25, 2018 at 3:15 PM Dieu Cao <dcao@...> wrote:
Hello All,

David Sabeti, the Project Lead for the Release Integration team within the Application Runtime PMC, is transitioning back to engineering. We thank him for his time serving as the Release Integration Project Lead.

The Release Integration team, primarily located in San Francisco, 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 3rd, 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 CLI: how do you use `no-start` with `cf push`

Abby Chau
 

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.

UAA.yaml envvar substitution

Szerdahelyi, Andras (GE Digital)
 

Hi cf-dev,

i am trying to bootstrap UAA 4.6.1 with an admin user password from the environment. i tried providing the entire scim.users array item and just the password in the pipe-delimited string in said array item, with zero success.

when a complete scim.users item is coming from an envvar ( - ${ADMIN_USER} ), i get a “password cannot be empty” exception and uaa fails to deploy in the container. When i place only the password token ( - admin|${ADMIN_PASSWORD}|... ) i simply can not authenticate with $ADMIN_PASSWORD.

hardcoding an scim.users value works without a problem.

my question then would be this: is envvar substitution allowed for an array item ( - $ITEM ) and/or is envvar substitution allowed/enabled in a string in an array item ( - foo..${BAR} ) ?

thanks,
Andras

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

Lee Porte
 

Hi, 

We use it when setting env vars that we don't want to commit. Or when committing then would harm the reuse of our code by others.


On Wed, 27 Jun 2018, 17:18 Abby Chau, <achau@...> wrote:
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.

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

Mike Youngstrom
 

We mostly use it to do things to an application before starting it that cannot be done in a manifest.  For example, setting computed environment variables, or binding services that need service-parameters.  I think "--no-start" can be removed and we could use v3-create-app instead.

Mike

On Wed, Jun 27, 2018 at 10:18 AM Abby Chau <achau@...> wrote:
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.

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

Zach Robinson
 

Hi Lee,

Have you seen the new variable substitution feature for manifests?  It might really help your use-case.


-Zach

On Wed, Jun 27, 2018 at 10:09 AM Mike Youngstrom <youngm@...> wrote:
We mostly use it to do things to an application before starting it that cannot be done in a manifest.  For example, setting computed environment variables, or binding services that need service-parameters.  I think "--no-start" can be removed and we could use v3-create-app instead.

Mike

On Wed, Jun 27, 2018 at 10:18 AM Abby Chau <achau@...> wrote:
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.

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

Krannich, Bernd <bernd.krannich@...>
 

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.

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

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

+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.

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

Abby Chau
 

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.


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

Zach Robinson
 

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.