CloudFoundry BOSH

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 ... [More] slack or ping any of us at the Foundation directly.  Please stay healthy and safe.  - 1. https://www.cloudfoundry.org/blog/cloud-foundry-summit-cfp-extension-program-committee-announced/ -- -- Swarna PodilaSenior Director, Community | Cloud Foundry Foundationspodila@...@skpodila [Less]

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 ... [More] slack or ping any of us at the Foundation directly.  Please stay healthy and safe.  - 1. https://www.cloudfoundry.org/blog/cloud-foundry-summit-cfp-extension-program-committee-announced/ -- -- Swarna PodilaSenior Director, Community | Cloud Foundry Foundationspodila@...@skpodila [Less]

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 ... [More] 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 [Less]

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 ... [More] 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 [Less]

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

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 ... [More] 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.  --  1. https://www.cloudfoundry.org/events/summit/austin-2020/call-for-proposals/ 2. https://www.cloudfoundry.org/events/summit/austin-2020/novel-coronavirus-update/ -- Swarna Podila (she/her) Senior Director, Community | Cloud Foundry Foundation [email protected] @ skpodila You can read more about pronouns here, or please ask if you'd like to find out more. [Less]