Date   
[cf-dev] Cloud Foundry Summit Goes Cloud Native

Swarna Podila
 

Sharing this with you all.

TL;DR: 
Please don’t hesitate to post your question here or reach out to me or @chipchilders directly (slack or email) if you have any questions/suggestions/feedback.  Please read Chip's email below for more details.

-- Swarna Podila (she/her)
Senior
 Director
, Community
 | Cloud Foundry Foundation

You can read more about pronouns here, or please ask if you'd like to find out more.


---------- Forwarded message ---------
From: Chip Childers <cchilders@...>
Date: Thu, Apr 23, 2020 at 9:19 AM
Subject: [cf-dev] Cloud Foundry Summit Goes Cloud Native
To: CF Developers Mailing List <cf-dev@...>


It’s official, folks: Cloud Foundry Summit is going virtual. We’ve moved the Austin, Texas, event online to keep you — our fantastic community — safe and healthy during this unforeseen time. What was initially a one-day Summit will now be two half-days devoted to our developer and contributor communities so you can comfortably engage with presentations without spending the entire day in front of your computer.

We know this is a sea change for a community so fiercely devoted to quality in-person discussion. I look forward to our Summits every year, and I am also disappointed that I won’t get to see you all in person. But we remain committed to providing you with the same opportunities for collaboration and education that we’ve offered at all of our in-person Summits, even if the setting is your home office (or kitchen table).

We are working with our inimitable events team to design a virtual Summit that caters not only to the specific interests of our community, but to the abnormal circumstances in which we find ourselves. Cloud Foundry Virtual Summit will take place on Wednesday, June 24th and Thursday, June 25th for several hours each day, with sessions abbreviated to keep you engaged and networking opportunities meant to mimic the beloved “hallway track” at Summit. You’ll find special events like the Diversity Luncheon, Hands-on labs and Community Awards scheduled as usual — just in a different format than you’ve previously experienced. 

Contributors can register here for free using this code: CFNA20CON 

You’ll also notice that we’ve reopened the CFP now that Summit is going virtual, as the format will be a bit different. Check out the CFP submission process here and note that the new deadline is Friday, May 1st. You can submit a talk to the Developer Experience track, the Contributor track or the Diversity track. Feel free to reach out for CFP guidance by tagging @cfp-help in #summit on Cloud Foundry slack.

I imagine this news may not come as a surprise given how many events have moved online for the next few months, but I know it’s still a disappointment for our tight-knit community. I want to make sure that you get to shape this event to be exactly what you need it to be as we venture together into unknown territory. What features do you want to see in a virtual event? What pieces from Cloud Foundry Summit are a must-have? What tools have you used at online events that you loved, and what types of sessions most engaged you? This is feedback we need and want to make sure we make this new virtual summit the best possible experience for you — our community. Please email me or send me a DM on Cloud Foundry slack @chipchilders to share your learnings from other events and how we can serve you.

In the meantime, I hope you are staying safe at home and doing what you need to feel mentally, emotionally and physically healthy during this time. I appreciate your flexibility and understanding around this decision, and I look forward to seeing you from a safe distance at Summit!


Chip Childers
Executive Director
Cloud Foundry Foundation

Re: [cf-push] Deploying spring-music twice will throw lots of warnings

Daniel Mikusa
 

Running `gradle clean` isn't sufficient. That only cleans out your project folder. It speed up builds Gradle/Maven will download JAR dependencies and cache them outside of your project folder. These essentially sit there forever. If there is a problem downloading a JAR dependency and it's corrupted, the corrupted JAR will sit there forever. You need to manually clean it out.

>For Maven, you just have to wipe out the offending files under ~/.m2/repository (or delete everything under that folder). I'm not as familiar with Gradle, but SO says it stores them under ~/.gradle/caches/modules-2/files-2.1, https://stackoverflow.com/a/33196481. The solution should be the same. Delete the offending files or just delete everything. Then run `gradle clean` and `gradle assemble` again. You should see it download the files again. Make sure you're on the network & able to access the files it's trying to download.

Dan


On Tue, Apr 21, 2020 at 2:32 AM "何贵民(箫竹) <guimin.hgm@...> wrote:

Hello Daniel, 

Thanks for your feedback. I have run the `gradle clean` and `gradle assemble`, but unfortunately, after that, the issue still exist. Is there any more ideas? It is important for our customers and us, I am looking forward to your help eagerly. Thanks for in advance.

Thanks and warm regards
Guimin, He

Re: [cf-push] Deploying spring-music twice will throw lots of warnings

"何贵民(箫竹)
 

Hello Daniel, 

Thanks for your feedback. I have run the `gradle clean` and `gradle assemble`, but unfortunately, after that, the issue still exist. Is there any more ideas? It is important for our customers and us, I am looking forward to your help eagerly. Thanks for in advance.

Thanks and warm regards
Guimin, He

Re: [cf-push] Deploying spring-music twice will throw lots of warnings

Daniel Mikusa
 

This has happened to me in the past when Maven/Gradle fails to download a JAR dependency and it gets stuck in the local cache on my laptop's filesystem. The actual file is some error, not a JAR file, which is why you get messages about invalid JAR files.

For Maven, you just have to wipe out the offending files under ~/.m2/repository (or delete everything under that folder). I'm not as familiar with Gradle, but SO says it stores them under ~/.gradle/caches/modules-2/files-2.1, https://stackoverflow.com/a/33196481. The solution should be the same. Delete the offending files or just delete everything. Then run `gradle clean` and `gradle assemble` again. You should see it download the files again. Make sure you're on the network & able to access the files it's trying to download.

Hope that helps!


On Mon, Apr 13, 2020 at 11:08 PM "何贵民(箫竹) <guimin.hgm@...> wrote:
Dear Cloud Foundry Community,

I am Alibaba Cloud developer and I am working on integrating Alibaba Cloud with CloudFoundry. Now, I happened an issue when I deploy app spring-music: https://github.com/cloudfoundry-samples/spring-music, and I need your help.

The issue as following:
when I run command cf push to deploy spring-music firstly, it can be deployed successfully;
when I run command cf push again, it throw many warnings, as following:
Staging app and tracing logs...
Downloading binary_buildpack...
Downloading staticfile_buildpack...
Downloading java_buildpack...
Downloading ruby_buildpack...
Downloaded ruby_buildpack
Downloading dotnet_core_buildpack...
Downloaded staticfile_buildpack
Downloading nodejs_buildpack...
Downloaded java_buildpack
Downloading go_buildpack...
Downloaded binary_buildpack
Downloading python_buildpack...
Downloaded nodejs_buildpack
Downloading php_buildpack...
Downloaded dotnet_core_buildpack
Downloading nginx_buildpack...
Downloaded go_buildpack
Downloading r_buildpack...
Downloaded python_buildpack
Downloaded r_buildpack
Downloaded nginx_buildpack
Downloaded php_buildpack
Cell ae633763-c016-4a05-90c3-89494ac040e7 creating container for instance 700500a8-5455-4bba-b438-116f09231b82
Cell ae633763-c016-4a05-90c3-89494ac040e7 successfully created container for instance 700500a8-5455-4bba-b438-116f09231b82
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (42.1M)
Downloaded app package (62.4M)
warning [/tmp/app/BOOT-INF/lib/spring-web-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/hibernate-core-5.2.16.Final.jar]: 6291456 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/jackson-databind-2.9.5.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-commons-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-mongodb-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-boot-autoconfigure-2.0.1.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/lettuce-core-5.0.3.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/aspectjweaver-1.8.13.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-core-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-context-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/h2-1.4.197.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-cloud-cloudfoundry-connector-2.0.1.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/hibernate-validator-6.0.9.Final.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/tomcat-embed-core-8.5.29.jar]: 2097152 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-redis-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/reactor-core-3.1.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/mongodb-driver-core-3.6.3.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-web-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/hibernate-core-5.2.16.Final.jar]: 6291456 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/jackson-databind-2.9.5.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-commons-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-mongodb-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-boot-autoconfigure-2.0.1.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/lettuce-core-5.0.3.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/aspectjweaver-1.8.13.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-core-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-context-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/h2-1.4.197.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-cloud-cloudfoundry-connector-2.0.1.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/hibernate-validator-6.0.9.Final.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/tomcat-embed-core-8.5.29.jar]: 2097152 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-redis-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile

My cf cli version is  6.51.0+2acd15650.2020-04-07.

In addition, about this issue, I have asked help in several days ago by slack cf-deployment channel: https://cloudfoundry.slack.com/archives/C2U7KA7M4/p1586335015016800 and capi channel: https://cloudfoundry.slack.com/archives/C07C04W4Q/p1586480456093000 , but there are no any reply.

Looking forward to your help.

Thanks and warm regards
Guimin, He

[cf-push] Deploying spring-music twice will throw lots of warnings

"何贵民(箫竹)
 

Dear Cloud Foundry Community,

I am Alibaba Cloud developer and I am working on integrating Alibaba Cloud with CloudFoundry. Now, I happened an issue when I deploy app spring-music: https://github.com/cloudfoundry-samples/spring-music, and I need your help.

The issue as following:
when I run command cf push to deploy spring-music firstly, it can be deployed successfully;
when I run command cf push again, it throw many warnings, as following:
Staging app and tracing logs...
Downloading binary_buildpack...
Downloading staticfile_buildpack...
Downloading java_buildpack...
Downloading ruby_buildpack...
Downloaded ruby_buildpack
Downloading dotnet_core_buildpack...
Downloaded staticfile_buildpack
Downloading nodejs_buildpack...
Downloaded java_buildpack
Downloading go_buildpack...
Downloaded binary_buildpack
Downloading python_buildpack...
Downloaded nodejs_buildpack
Downloading php_buildpack...
Downloaded dotnet_core_buildpack
Downloading nginx_buildpack...
Downloaded go_buildpack
Downloading r_buildpack...
Downloaded python_buildpack
Downloaded r_buildpack
Downloaded nginx_buildpack
Downloaded php_buildpack
Cell ae633763-c016-4a05-90c3-89494ac040e7 creating container for instance 700500a8-5455-4bba-b438-116f09231b82
Cell ae633763-c016-4a05-90c3-89494ac040e7 successfully created container for instance 700500a8-5455-4bba-b438-116f09231b82
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (42.1M)
Downloaded app package (62.4M)
warning [/tmp/app/BOOT-INF/lib/spring-web-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/hibernate-core-5.2.16.Final.jar]: 6291456 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/jackson-databind-2.9.5.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-commons-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-mongodb-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-boot-autoconfigure-2.0.1.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/lettuce-core-5.0.3.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/aspectjweaver-1.8.13.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-core-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-context-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/h2-1.4.197.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-cloud-cloudfoundry-connector-2.0.1.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/hibernate-validator-6.0.9.Final.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/tomcat-embed-core-8.5.29.jar]: 2097152 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-redis-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/reactor-core-3.1.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/mongodb-driver-core-3.6.3.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-web-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/hibernate-core-5.2.16.Final.jar]: 6291456 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/jackson-databind-2.9.5.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-commons-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-mongodb-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-boot-autoconfigure-2.0.1.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/lettuce-core-5.0.3.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/aspectjweaver-1.8.13.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-core-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-context-5.0.5.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/h2-1.4.197.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-cloud-cloudfoundry-connector-2.0.1.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/hibernate-validator-6.0.9.Final.jar]: 1048576 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/tomcat-embed-core-8.5.29.jar]: 2097152 extra bytes at beginning or within zipfile
(attempting to process anyway)
warning [/tmp/app/BOOT-INF/lib/spring-data-redis-2.0.6.RELEASE.jar]: 1048576 extra bytes at beginning or within zipfile

My cf cli version is  6.51.0+2acd15650.2020-04-07.

In addition, about this issue, I have asked help in several days ago by slack cf-deployment channel: https://cloudfoundry.slack.com/archives/C2U7KA7M4/p1586335015016800 and capi channel: https://cloudfoundry.slack.com/archives/C07C04W4Q/p1586480456093000 , but there are no any reply.

Looking forward to your help.

Thanks and warm regards
Guimin, He

Re: [cf-dev] BOSH projects adopting distributed committer model

Shatarupa Nandi <snandi@...>
 

Dear Cloud Foundry Community,


We would like to address some feedback we received from last week’s email about changes to BOSH stemcell patching cadence. Low and medium CVEs in stemcells will be patched every 3 weeks, instead of the previously proposed cadence of every 6 weeks. We remain committed to supporting our OSS BOSH users for the foreseeable future and will address feedback as best as we can.


As a reminder, we are still seeking help from other members of the Cloud Foundry community to help with ongoing maintenance of the BOSH projects in the following ways:

  • Please help your friends in the community by answering questions on #bosh and other BOSH channels

  • If you would like to contribute to adding Bionic support and/or start publishing Bionic stemcells on bosh.io, we would welcome PRs and will be happy to work with you to review and merge them. If you are interested in forming an OSS team to build Bionic stemcells and add support for Bionic to Cloud Foundry components, please reach out to Marco Voelz or Shatarupa Nandi.

  • If you would like improvements in BOSH and/or the CPIs, please consider contributing the feature directly via PRs to the various repos

  • If you notice a buildup of features / fixes that warrant a release being cut, ping the team via cf-bosh@...

  • If you would like to be a Project Lead for any of these projects, please reach out to Shatarupa Nandi and/or Nadja Conklin.


Please reach out to Nadja Conklin and/or Shatarupa Nandi if you have any feedback or questions.


Thank you!


On Tue, Mar 31, 2020 at 4:44 PM Shatarupa Nandi <snandi@...> wrote:

Dear Cloud Foundry Community,


Over the last year, we have seen the industry shift towards deploying software on top of Kubernetes. As a result, we have all chosen to invest heavily in building on top of Kubernetes. Separately, we have also observed that BOSH has reached a point of stability and maturity, such that there aren’t lots of incoming feature requests and enhancements to add.


We continue to view BOSH as an important project and are still fully committed to supporting our OSS users using BOSH for the next couple years . However, in light of these changes, several BOSH PMC projects[1] will be shifting from the pairing model to the distributed committer model (for more information about distributed committer vs pairing models, see the CFF Development Operations Policy [2], section IV.B.). Shatarupa Nandi (snandi@..., @rupa on CFF Slack) and Nadja Conklin (nconklin@..., @Nadja Conklin on CFF Slack) will temporarily step in as Project Leads. 


We are moving away from having a full time team working on each of the projects. Instead, we will have 6-8 engineers who will dedicate a portion of their time on a regular basis for ongoing support and maintenance of the BOSH projects. This will likely result in the following changes:

  • A reduced cadence of cutting new stemcells and patching existing stemcells for low and medium severity CVEs. Presently, we aim to cut new stemcell patches every 2 weeks. We will now be doing the same every 6 weeks. We will maintain the status quo for high and critical CVEs and will patch those as soon as possible.

  • We will pause working on Bionic stemcells and will not be cutting a new line of Bionic stemcells. We are aware that Xenial stemcells are supported until April 2021. This is an area where we are seeking help from the CFF community. Please see the end of the email. We may pick up this work during the 2nd half of the year, depending on cf-for-k8s adoption and our level of staffing on BOSH.

  • A reduced cadence of new releases of BOSH PMC projects[1]. Since there will be little active development, we will move to cutting releases ad-hoc when there are enough changes built up.

  • We will pause active development on the various CPIs (including OpenStack CPI, Azure CPI, GCP CPI, and AWS CPI.) We will continue to patch critical bugs, backwards incompatible IaaS API changes, and high severity CVEs. However, we will not be adding features to extend the capabilities of the CPIs.

  • While we will continue to answer questions about BOSH, we will likely be less responsive than before. We still hope to answer questions on these Slack channels within a reasonable time. We will be most active in #bosh. Other BOSH Slack channels (for example, #bosh-core-dev) will see reduced activity and will be deprecated over time.

  • The committers are all on cf-bosh@..., and will continue to engage with the community of users and contributors via the mailing lists. 


We would like to seek help from other members of the Cloud Foundry community to help with ongoing maintenance of the BOSH projects. Here are some ways in which you can help us:

  • Please help your friends in the community by answering questions on #bosh

  • If you would like to contribute to adding Bionic support and/or start publishing Bionic stemcells on bosh.io, we would welcome PRs and will be happy to work with you to review and merge them. If you are interested in forming an OSS team to build Bionic stemcells and add support for Bionic to Cloud Foundry components, please reach out to Marco Voelz or Shatarupa Nandi.

  • If you would like improvements in BOSH and/or the CPIs, please consider contributing the feature directly via PRs to the various repos

  • If you notice a buildup of features / fixes that warrant a release being cut, ping the team via cf-bosh@...

  • If you would like to be a Project Lead for any of these projects, please reach out to Shatarupa Nandi and/or Nadja Conklin.


Thank you for your help and support!


[1] This includes the following repos: bosh, bosh-agent, bosh-dns-release, bosh-linux-stemcell-builder, bosh-deployment, bosh-cli, bbl, bosh.io github org, docs-bosh, bpm-release, bosh-google-cpi-release, bosh-azure-cpi-release, bosh-openstack-cpi-release, bosh-aws-cpi-release, bosh-lite, bosh-utils, bosh-s3cli, bosh-acceptance-tests, jumpbox-deployment, os-conf-release.


[2] https://www.cloudfoundry.org/wp-content/uploads/2017/01/CFF-DEV-OPS-POLICY.pdf

Re: Leadership Changes at the Cloud Foundry Foundation

Chip Childers
 

Quick follow up! I mistakenly stated that the AMA is on Thursday April 8th... which does not exist this year. The AMA is on Thursday April 9th. See you on Slack!

Chip Childers
Executive Director
Cloud Foundry Foundation


On Tue, Apr 7, 2020 at 9:10 AM Chip Childers <cchilders@...> wrote:

Cloud Foundry Community,


First and foremost, I truly hope that each of you is doing as well as can be expected in these extraordinary times.


As you may have seen, we announced a leadership change this morning. I am stepping into the role of Executive Director of the Cloud Foundry Foundation. Abby Kearns has accepted an executive role with another organization, to be announced. This is a very exciting opportunity for Abby, and all of us on the foundation’s staff and directors are extremely happy for her. Abby has been leading the foundation for several years through quite a bit of change in our project, our community, and the broader market. She’s not going far, but she will be missed.


We also announced that Paul Fazzone, SVP Tanzu R&D at VMware, has been elected to chair the board of directors. Paul has been a strong advocate and supporter of the foundation, having served as Treasurer for the foundation and as a director for several years now. Paul is taking over the role of chair from John Roese, who has been a steady hand from the organization’s inception. I am looking forward to working much more closely with Paul as we push the organization forward into the future. 


Our focus as a community has always been to make developers’ lives easier, and each of you has played a part in the long list of user success stories. Even today, as society grapples with the incredible challenge of a global pandemic, I am reminded of the incredible value of the work this community does. Organizations from around the world that have adopted Cloud Foundry are using it to respond in these trying times, each in their own way. National governments have used the Cloud Foundry platform to rapidly build, deploy and scale software that is helping their citizens get information and register for economic support. Countless corporations are using Cloud Foundry to both support their customers in new ways and do their part for the greater good. These responses have required actions measured in days and hours, not weeks and months. In short, this community’s efforts over the years have built something worthing being truly proud of.


This community is also one that has managed to continuously evolve the architecture of the platform through several major cycles of change. Today is no different, as we have come together on the shared mission of bringing the Cloud Foundry developer experience to Kubernetes clusters everywhere


As the ancient Greek philosopher, Heraclitus said, “Change is the only constant in life.” Our community embraces that way of thinking, both for the Cloud Foundry project itself and when considering how to continue to enhance the developer experience provided by the platform. Ultimately, the core Cloud Foundry function cf-push will remain well into the future, and its architecture will continue to evolve.


I’m sure many of you have questions about these changes, and I welcome the opportunity to answer them. Feel free to email me directly ( cchilders@... ), or join us for a slack-based AMA this Thursday, April 8th, from 8-10 AM PST on the Cloud Foundry community’s slack instance in the #cff-forum channel. I will be happy to discuss the transition, the future of the Foundation and respond to any comments or questions you may have.


-chip



Chip Childers
Executive Director
Cloud Foundry Foundation

Leadership Changes at the Cloud Foundry Foundation

Chip Childers
 

Cloud Foundry Community,


First and foremost, I truly hope that each of you is doing as well as can be expected in these extraordinary times.


As you may have seen, we announced a leadership change this morning. I am stepping into the role of Executive Director of the Cloud Foundry Foundation. Abby Kearns has accepted an executive role with another organization, to be announced. This is a very exciting opportunity for Abby, and all of us on the foundation’s staff and directors are extremely happy for her. Abby has been leading the foundation for several years through quite a bit of change in our project, our community, and the broader market. She’s not going far, but she will be missed.


We also announced that Paul Fazzone, SVP Tanzu R&D at VMware, has been elected to chair the board of directors. Paul has been a strong advocate and supporter of the foundation, having served as Treasurer for the foundation and as a director for several years now. Paul is taking over the role of chair from John Roese, who has been a steady hand from the organization’s inception. I am looking forward to working much more closely with Paul as we push the organization forward into the future. 


Our focus as a community has always been to make developers’ lives easier, and each of you has played a part in the long list of user success stories. Even today, as society grapples with the incredible challenge of a global pandemic, I am reminded of the incredible value of the work this community does. Organizations from around the world that have adopted Cloud Foundry are using it to respond in these trying times, each in their own way. National governments have used the Cloud Foundry platform to rapidly build, deploy and scale software that is helping their citizens get information and register for economic support. Countless corporations are using Cloud Foundry to both support their customers in new ways and do their part for the greater good. These responses have required actions measured in days and hours, not weeks and months. In short, this community’s efforts over the years have built something worthing being truly proud of.


This community is also one that has managed to continuously evolve the architecture of the platform through several major cycles of change. Today is no different, as we have come together on the shared mission of bringing the Cloud Foundry developer experience to Kubernetes clusters everywhere


As the ancient Greek philosopher, Heraclitus said, “Change is the only constant in life.” Our community embraces that way of thinking, both for the Cloud Foundry project itself and when considering how to continue to enhance the developer experience provided by the platform. Ultimately, the core Cloud Foundry function cf-push will remain well into the future, and its architecture will continue to evolve.


I’m sure many of you have questions about these changes, and I welcome the opportunity to answer them. Feel free to email me directly ( cchilders@... ), or join us for a slack-based AMA this Thursday, April 8th, from 8-10 AM PST on the Cloud Foundry community’s slack instance in the #cff-forum channel. I will be happy to discuss the transition, the future of the Foundation and respond to any comments or questions you may have.


-chip



Chip Childers
Executive Director
Cloud Foundry Foundation

Re: Stemcell Bump Cadence

Maya Rosecrance
 

I realized I beat Rupa to posting this information by only a few hours. If you have feedback on this change, please reach out on the other thread: https://lists.cloudfoundry.org/g/cf-bosh/message/2707 

CF Summit NA 2020: Announcing CFP Extension and Program Chairs

Swarna Podila
 

Dear Community,
Given the circumstances, we felt that keeping the CFP open for a bit longer will be useful.  Please read this post [1] announcing program co-chairs and CFP extension.

Please do not hesitate to ask a question in #summit channel on CF slack or ping any of us at the Foundation directly.  Please stay healthy and safe. 

-
--
-- Swarna Podila
Senior Director, Community | Cloud Foundry Foundation
spodila@...
@skpodila

[cf-dev] BOSH projects adopting distributed committer model

Shatarupa Nandi <snandi@...>
 

Dear Cloud Foundry Community,


Over the last year, we have seen the industry shift towards deploying software on top of Kubernetes. As a result, we have all chosen to invest heavily in building on top of Kubernetes. Separately, we have also observed that BOSH has reached a point of stability and maturity, such that there aren’t lots of incoming feature requests and enhancements to add.


We continue to view BOSH as an important project and are still fully committed to supporting our OSS users using BOSH for the next couple years . However, in light of these changes, several BOSH PMC projects[1] will be shifting from the pairing model to the distributed committer model (for more information about distributed committer vs pairing models, see the CFF Development Operations Policy [2], section IV.B.). Shatarupa Nandi (snandi@..., @rupa on CFF Slack) and Nadja Conklin (nconklin@..., @Nadja Conklin on CFF Slack) will temporarily step in as Project Leads. 


We are moving away from having a full time team working on each of the projects. Instead, we will have 6-8 engineers who will dedicate a portion of their time on a regular basis for ongoing support and maintenance of the BOSH projects. This will likely result in the following changes:

  • A reduced cadence of cutting new stemcells and patching existing stemcells for low and medium severity CVEs. Presently, we aim to cut new stemcell patches every 2 weeks. We will now be doing the same every 6 weeks. We will maintain the status quo for high and critical CVEs and will patch those as soon as possible.

  • We will pause working on Bionic stemcells and will not be cutting a new line of Bionic stemcells. We are aware that Xenial stemcells are supported until April 2021. This is an area where we are seeking help from the CFF community. Please see the end of the email. We may pick up this work during the 2nd half of the year, depending on cf-for-k8s adoption and our level of staffing on BOSH.

  • A reduced cadence of new releases of BOSH PMC projects[1]. Since there will be little active development, we will move to cutting releases ad-hoc when there are enough changes built up.

  • We will pause active development on the various CPIs (including OpenStack CPI, Azure CPI, GCP CPI, and AWS CPI.) We will continue to patch critical bugs, backwards incompatible IaaS API changes, and high severity CVEs. However, we will not be adding features to extend the capabilities of the CPIs.

  • While we will continue to answer questions about BOSH, we will likely be less responsive than before. We still hope to answer questions on these Slack channels within a reasonable time. We will be most active in #bosh. Other BOSH Slack channels (for example, #bosh-core-dev) will see reduced activity and will be deprecated over time.

  • The committers are all on cf-bosh@..., and will continue to engage with the community of users and contributors via the mailing lists. 


We would like to seek help from other members of the Cloud Foundry community to help with ongoing maintenance of the BOSH projects. Here are some ways in which you can help us:

  • Please help your friends in the community by answering questions on #bosh

  • If you would like to contribute to adding Bionic support and/or start publishing Bionic stemcells on bosh.io, we would welcome PRs and will be happy to work with you to review and merge them. If you are interested in forming an OSS team to build Bionic stemcells and add support for Bionic to Cloud Foundry components, please reach out to Marco Voelz or Shatarupa Nandi.

  • If you would like improvements in BOSH and/or the CPIs, please consider contributing the feature directly via PRs to the various repos

  • If you notice a buildup of features / fixes that warrant a release being cut, ping the team via cf-bosh@...

  • If you would like to be a Project Lead for any of these projects, please reach out to Shatarupa Nandi and/or Nadja Conklin.


Thank you for your help and support!


[1] This includes the following repos: bosh, bosh-agent, bosh-dns-release, bosh-linux-stemcell-builder, bosh-deployment, bosh-cli, bbl, bosh.io github org, docs-bosh, bpm-release, bosh-google-cpi-release, bosh-azure-cpi-release, bosh-openstack-cpi-release, bosh-aws-cpi-release, bosh-lite, bosh-utils, bosh-s3cli, bosh-acceptance-tests, jumpbox-deployment, os-conf-release.


[2] https://www.cloudfoundry.org/wp-content/uploads/2017/01/CFF-DEV-OPS-POLICY.pdf

Stemcell Bump Cadence

Maya Rosecrance
 

Hello community,
In order to reduce engineering toil we're changing the periodic bump schedule of stemcells from every 2 weeks to every 6 weeks. Critical CVE's should still see a new stemcell patch created within a few days.
Bosh team

CFNASummit 2020: CFP Extended!

Swarna Podila
 

Dear Cloud Foundry Community,
Please note that the deadline to submit your speaking proposals for Cloud Foundry Summit North America 2020 has been extended. 

Here is the new timeline:
CFP Deadline: 11:59pm (US Pacific) April 3, 2020
Schedule Announcement: April 22, 2020

You can find a more detailed timeline here [1].  Please also stay tuned to this page [2] as we post updates around the event plan, given the times we are in now.  If you have any questions, please drop me a note or post it on #summit on CF Slack.

During these times, if anyone wants informal community calls where we just hangout on zoom to socialize, please drop me a note here or on slack.

Please stay healthy.
Bleiben Sie gesund. 

-- 

-- Swarna Podila (she/her)
Senior
 Director
, Community
 | Cloud Foundry Foundation

You can read more about pronouns here, or please ask if you'd like to find out more.

Re: Statement from the Cloud Foundry Foundation regarding COVID-19

Marco Voelz
 

Thanks Chip!

 

I recently read https://deniseyu.io/2020/03/07/remote-collaboration.html written by Denise Yu and found it to be a very good collection of hardware, software, and process – in case someone is looking for some general advice on how to foster collaboration/pairing when working remote.

 

Everybody stay safe and healthy!

 

Warm regards

Marco

 

From: <cf-bosh@...> on behalf of Chip Childers <cchilders@...>
Reply to: "cf-bosh@..." <cf-bosh@...>
Date: Monday, 16. March 2020 at 17:55
Subject: [cf-bosh] Statement from the Cloud Foundry Foundation regarding COVID-19

 

To our community and members,

 

We recognize the global emergency caused by COVID-19 is impacting all of us. Our thoughts are with our community, members, friends, and colleagues as we approach this new challenge together. 

 

As many parts of the world are implementing social distancing and, in many cases, urging or even requiring citizens to stay at home, many of us are privileged to be able to work from home. Some of our project teams have significant experience working and pairing remotely. For those of you that are new to working from home, please reach out to the larger community for support and or best practices. If you have experience working remotely, we encourage you to share your best practices with others -- both in the community and more broadly (in the form of blog posts, podcasts, tweets). Now is the time for our community to show its support for each other in any way possible.

 

As we near our June 25th Cloud Foundry Summit North America, please know that we are actively monitoring the situation as it evolves and will be adjusting plans as necessary to ensure the safety and health of our community. As of today, we remain hopeful we will have the opportunity to come together in person. On Friday, we updated the event’s novel coronavirus update page. We will keep you updated on any future changes to the event plans, and remind everyone to continue to check for updates on that page. 

 

It is important to remember that each of us will experience the impact of this outbreak in different ways. Our community is a global network of individuals who genuinely care about each other. In this time of uncertainty, let us demonstrate that kindness to each other by remaining flexible and supportive - in the Cloud Foundry community and in your local community. Help where you can. Be patient, be safe, and remember to take care of yourself. We will all get through this together.

 

In the meantime, please don’t hesitate to reach out to us, at the Foundation, if there is anything we can do to better support you during this time.

 

 

Chip Childers, CTO

Cloud Foundry Foundation

Statement from the Cloud Foundry Foundation regarding COVID-19

Chip Childers
 

To our community and members,


We recognize the global emergency caused by COVID-19 is impacting all of us. Our thoughts are with our community, members, friends, and colleagues as we approach this new challenge together. 


As many parts of the world are implementing social distancing and, in many cases, urging or even requiring citizens to stay at home, many of us are privileged to be able to work from home. Some of our project teams have significant experience working and pairing remotely. For those of you that are new to working from home, please reach out to the larger community for support and or best practices. If you have experience working remotely, we encourage you to share your best practices with others -- both in the community and more broadly (in the form of blog posts, podcasts, tweets). Now is the time for our community to show its support for each other in any way possible.


As we near our June 25th Cloud Foundry Summit North America, please know that we are actively monitoring the situation as it evolves and will be adjusting plans as necessary to ensure the safety and health of our community. As of today, we remain hopeful we will have the opportunity to come together in person. On Friday, we updated the event’s novel coronavirus update page. We will keep you updated on any future changes to the event plans, and remind everyone to continue to check for updates on that page. 


It is important to remember that each of us will experience the impact of this outbreak in different ways. Our community is a global network of individuals who genuinely care about each other. In this time of uncertainty, let us demonstrate that kindness to each other by remaining flexible and supportive - in the Cloud Foundry community and in your local community. Help where you can. Be patient, be safe, and remember to take care of yourself. We will all get through this together.


In the meantime, please don’t hesitate to reach out to us, at the Foundation, if there is anything we can do to better support you during this time.



Chip Childers, CTO
Cloud Foundry Foundation

Re: Not able to list the teams in concourse, using API /api/v1/teams

arutsudar.a95@...
 

Hi Daniel,

Thank you for your suggestions.

Regards,
Arutsudar

BOSH OpenStack CPI maintenance

Riegger, Felix
 

Dear Friends of OpenStack,

 

SAP announced in August 2019 [1] to stop the maintenance of the BOSH OpenStack CPI and related projects by the end of 2019. Pivotal/VMware jumped in to take over the maintenance of the CPI. The handover has been completed and Pivotal/VMware now officially maintains the BOSH OpenStack CPI [2]. To get support please reach out to #bosh [6] or #bosh-core-dev [7] Slack channels.

 

The CF OpenStack validator [3] and bosh-openstack-environment-templates [4] are now unmaintained and will be moved to the cloudfoundy-attic [5] organization after a short grace period.

 

Kind regards,

Morgan and Felix

 

 

[1] https://lists.cloudfoundry.org/g/cf-bosh/message/2651

[2] https://github.com/cloudfoundry/bosh-openstack-cpi-release

[3] https://github.com/cloudfoundry-incubator/cf-openstack-validator

[4] https://github.com/cloudfoundry-incubator/bosh-openstack-environment-templates

[5] https://github.com/cloudfoundry-attic/

[6] https://cloudfoundry.slack.com/archives/C02HPPYQ2

[7] https://cloudfoundry.slack.com/archives/C094QRLEQ

Cloud Foundry Community Workroom at Kubecon/CloudnativeCon EU 2020

Swarna Podila
 

Dear Cloud Foundry Community,
For those of you attending Kubecon/CloudnativeCon EU 2020, please note that F002/F003 room is available for the cloud foundry community.  This is to foster the cross-community collaboration onsite.

This room is an "open-for-cf-community" workroom with no prior reservation required.  This room will be equipped with tables and chairs along with a whiteboard and some markers.  

Please do not hesitate to reach out to me (prior to the event) or the events team onsite, if you have any questions.

-- Swarna Podila (she/her)
Senior
 Director
, Community
 | Cloud Foundry Foundation

You can read more about pronouns here, or please ask if you'd like to find out more.

[cf-dev] Call for Help with Vulnerability Management for CFF projects

Swarna Podila
 

For those of you who are not on cf-dev mailing list.

-- Swarna Podila (she/her)
Senior
 Director
, Community
 | Cloud Foundry Foundation

You can read more about pronouns here, or please ask if you'd like to find out more.


---------- Forwarded message ---------
From: Dieu Cao <dcao@...>
Date: Wed, Feb 26, 2020 at 11:42 AM
Subject: [cf-dev] Call for Help with Vulnerability Management for CFF projects
To: cf-dev <cf-dev@...>


All,

The CF community is looking for a handful of volunteers to help reconstitute a multi-member vulnerability management team for CFF projects. Recently, the task has fallen to the Pivotal/VMware security team alone. However, the whole community has a stake in this process.

We're looking for individuals that either: (1) have past experience managing security reports responsibly within either a commercial or open source setting, or (2) are willing and capable of learning by doing. One of the keys to success here will be for the volunteers to have a true sense of being responsible for this process.

Don't worry if you're not a security expert. You do have to be willing to spend a few hours a week helping manage the process.

If interested, reply here or contact me directly. Once we get a reasonable group of volunteers, we'll setup the appropriate meetings to get started.

Thanks,
Dieu Cao
CFF PMC Council Chair

Re: Not able to list the teams in concourse, using API /api/v1/teams

Daniel Jones
 

Hi Aratsudar,

A better place to look for help would be the Concourse forums: https://discuss.concourse-ci.org/

You may also like to consider Control Tower if you want a simpler way to deploy Concourse via BOSH: https://github.com/EngineerBetter/control-tower

Regards,
Daniel 'Deejay' Jones - CTO
+44 (0)79 8000 9153
EngineerBetter Ltd - More than cloud platform specialists


On Wed, 19 Feb 2020 at 08:49, <arutsudar.a95@...> wrote:

I am using concourse v4.2.1 deployed using bosh on AWS.

When I hit the API endpoint /api/v1/info (in Postman, with Basic auth), I am able to get the response as below

{
    "version": "4.2.1",
    "worker_version": "2.1"
}

When I try to hit the API endpoint /api/v1/teams (in Postman, with Basic auth), I am getting Status 200 OK with an empty response like below.

[]

I am able to see the teams using fly command or also in the web UI, but not through API.

  • Should I enable basic authentication for hitting API endpoints of concourse?
  • Why am I not able to list the teams in concourse using the API /api/v1/teams? What am I missing?


Additional Info:

Referred to this concourse-bosh-deployment github repo for deploying concourse.

The sample command used to deploy concourse is given below:

bosh -e boshconcoursedir deploy -d boshconcourse concourse.yml \
  -l ../versions.yml \
  --vars-store cluster-creds.yml  \
  -o operations/static-web.yml  \
  --var web_ip=<<REDACTED>>   \
  --var network_name=default  \
  --var web_vm_type=<<REDACTED>>  \
  --var db_vm_type=<<REDACTED>>   \
  --var db_persistent_disk_type=<<REDACTED>> \
   --var worker_vm_type=<<REDACTED>> \
    --var deployment_name=boshconcourse \
    --var external_url=https://<<REDACTED>> \
    -o operations/add-local-users.yml \
    --var main_team_local_users=[admin] \
    --var add_local_users=[admin:<<REDACTED>>,myid@...:<<REDACTED>>]

Today I added the below line to the deployment command and deployed again, and still failed to get the teams from the API

  -o operations/basic-auth.yml \

After logging in as admin in fly, I am able to list the teams as below.

fly -t admin login -c https://something.com -u admin -p <<REDACTED>>
logging in to team 'main'


target saved

fly -t admin teams
name
team-1 
team-2
main 

I am not sure if this is the right place to ask this issue. Sorry if it is not. (Also posted a similar question in StackOverflow). Kindly assist me in resolving this issue.

Regards,
Arut