Date   

Re: Call for Nominations: Cloud Foundry Foundation Technical Oversight Committee Election

Chip Childers
 

Of course there's a type in one of the embedded links... <facepalm>.


@Eric Malm was kind enough to point out that "voders" is not a thing.

Chip Childers
Executive Director
Cloud Foundry Foundation


On Tue, May 11, 2021 at 1:53 PM Chip Childers <cchilders@...> wrote:

Call for Nominations: Cloud Foundry Foundation Technical Oversight Committee Election


(TL;DR - we are holding an election to create a TOC… members of the CFF technical community need to take a couple of actions. Check the “TODO” list at the bottom of this post.)


Overview:


As many members of the community are aware, a working group has been meeting regularly to propose changes to our community governance structure. Last week, the first major milestone in this work was reached when the Foundation’s Governing Board (GB) voted in favor of establishing a Technical Oversight Committee (TOC) to take the place of the PMC Council.


With that change now approved, we are kicking off the first TOC election cycle today.


This is the first step of what I expect to be a fairly complex realignment of how our technical community works day to day. There are many decisions still left to be made, but I am confident that a democratic election of the TOC will bring together community leaders that will be responsive and thoughtful when making these choices.


Why Change?


The Cloud Foundry Foundation was created after a long and difficult negotiation process amongst the founding member organizations. Many, many things have changed in our ecosystem in the (over) six years since that negotiation took place, but our community’s approach to decision making has stayed roughly the same. 


When I took on the role as Executive Director in early 2020, my primary goal was to help the Foundation’s membership and the project’s community restructure how everyone works together. At the end of 2020, the Foundation completed a set of changes to the corporate structure that supports the technical community’s efforts. Today, we are taking a major step on the community side.


The community members that have been participating in this process have grounded their thinking on three key guiding principles: Transparency, Clarity and Inclusivity. Every change proposed is tied back to those principles, and every change going forward should do the same. I encourage everyone to take a moment to read more about what we mean by these principles.


Put simply, it is time to make participation in the project easier for everyone.


What’s this TOC Thing?


A Technical Oversight Committee will take the place of the PMC Council, but that is where the similarity ends. The CFF TOC will be a democratically elected group of community members that represent you, the community.


The TOC is responsible for the oversight, direction, and delivery of technical aspects of the Cloud Foundry projects and working groups. Most importantly, the role of the TOC should be to enable the community to do good work in an open and transparent way, while helping to maintain the integrity of the project used by so many organizations around the world.


The first TOC election will be structured to elect five TOC members. Using the results of the election, the two nominees with the highest number of votes will have two year terms. The next three nominees, by number of votes, will have an initial term of one year.


The second TOC election will be held a year after the initial election. During that second election cycle, the three TOC members with initial one year terms will be at the end of their initial terms. Those TOC seats will be up for election during that second TOC election. An election will be held every year after that, with either two or three TOC seats being up for election each cycle.


The work of the TOC should become easier over time, but this first TOC will be asked to continue the hard work transforming how technical collaboration happens.


Who Gets To Participate?


TOC Eligibility:


The rules for eligibility to be a member of the TOC include specific community roles, which don’t exist yet. As such, eligibility to be nominated for the TOC during the first election will be:


Community members who are currently PMC Leads, Project Leads or committers within any PMC or project. Each member organization of the CFF can also nominate one additional person not meeting these criteria as a candidate for the first TOC election.


Eligible Voters:


If you are a member of the Cloud Foundry technical community, you have a role to play here. Any individual who has contributed to CFF projects or technical working groups in the twelve months prior to the election is eligible to vote in the TOC election.


Contributions include, but are not limited to, opening PRs, reviewing and commenting on PRs, opening and commenting on issues, writing design docs, commenting on design docs, participating in mailing list discussions and participating in working groups.


Timeline:


  • May 11 - Announcement of Election and Call for Nominations

  • May 11 through May 28 - Candidate nomination period

  • June 1 - Election Begins via email ballots

  • June 15 - Election Closes

  • June 17 - Results Announced


TODO (What you need to do):


  1. Check the voter list: Each election cycle, we will use automated reporting to try to gather a list of eligible voters. The reporting will be imperfect, given the definition of eligibility being so broad. If you want to vote, or if you want to nominate someone for the TOC, please check for your name in the list. If you are not on the list, just submit an issue using this template. The deadline is May 28th to be added to the voter list.


  1. Nominate TOC candidates: Every eligible voter can nominate candidates for the TOC, and we encourage you to do so. If you are eligible to serve on the TOC, you can self nominate! If you want to nominate someone else, do so as well! You can nominate someone for the TOC by submitting an issue using this template. The deadline is May 28th to be nominated (and for the nominee to indicate acceptance).


More information on the election process can be found in the 2021 TOC election guide.


Final Thoughts:


This will be our first time running this process as a community, so please bear with us if there are any hiccups or issues. The CFF staff will be here to make the process as smooth as possible, and will err on the side of “get it right” vs. “get it done on schedule”. I also expect that we will change the operational processes we use to support the election after this first cycle. As we always share with Cloud Foundry end users, plan to iterate. :)


I know that I speak for everyone that has been involved in the technical governance process over the last several months when I say that this should be an exciting time for the community. We have come very far over the years, but have so much further to go.


Feel free to reach out directly to me if you have any questions, concerns or issues.


Thanks!



Chip Childers
Executive Director
Cloud Foundry Foundation


Call for Nominations: Cloud Foundry Foundation Technical Oversight Committee Election

Chip Childers
 

Call for Nominations: Cloud Foundry Foundation Technical Oversight Committee Election


(TL;DR - we are holding an election to create a TOC… members of the CFF technical community need to take a couple of actions. Check the “TODO” list at the bottom of this post.)


Overview:


As many members of the community are aware, a working group has been meeting regularly to propose changes to our community governance structure. Last week, the first major milestone in this work was reached when the Foundation’s Governing Board (GB) voted in favor of establishing a Technical Oversight Committee (TOC) to take the place of the PMC Council.


With that change now approved, we are kicking off the first TOC election cycle today.


This is the first step of what I expect to be a fairly complex realignment of how our technical community works day to day. There are many decisions still left to be made, but I am confident that a democratic election of the TOC will bring together community leaders that will be responsive and thoughtful when making these choices.


Why Change?


The Cloud Foundry Foundation was created after a long and difficult negotiation process amongst the founding member organizations. Many, many things have changed in our ecosystem in the (over) six years since that negotiation took place, but our community’s approach to decision making has stayed roughly the same. 


When I took on the role as Executive Director in early 2020, my primary goal was to help the Foundation’s membership and the project’s community restructure how everyone works together. At the end of 2020, the Foundation completed a set of changes to the corporate structure that supports the technical community’s efforts. Today, we are taking a major step on the community side.


The community members that have been participating in this process have grounded their thinking on three key guiding principles: Transparency, Clarity and Inclusivity. Every change proposed is tied back to those principles, and every change going forward should do the same. I encourage everyone to take a moment to read more about what we mean by these principles.


Put simply, it is time to make participation in the project easier for everyone.


What’s this TOC Thing?


A Technical Oversight Committee will take the place of the PMC Council, but that is where the similarity ends. The CFF TOC will be a democratically elected group of community members that represent you, the community.


The TOC is responsible for the oversight, direction, and delivery of technical aspects of the Cloud Foundry projects and working groups. Most importantly, the role of the TOC should be to enable the community to do good work in an open and transparent way, while helping to maintain the integrity of the project used by so many organizations around the world.


The first TOC election will be structured to elect five TOC members. Using the results of the election, the two nominees with the highest number of votes will have two year terms. The next three nominees, by number of votes, will have an initial term of one year.


The second TOC election will be held a year after the initial election. During that second election cycle, the three TOC members with initial one year terms will be at the end of their initial terms. Those TOC seats will be up for election during that second TOC election. An election will be held every year after that, with either two or three TOC seats being up for election each cycle.


The work of the TOC should become easier over time, but this first TOC will be asked to continue the hard work transforming how technical collaboration happens.


Who Gets To Participate?


TOC Eligibility:


The rules for eligibility to be a member of the TOC include specific community roles, which don’t exist yet. As such, eligibility to be nominated for the TOC during the first election will be:


Community members who are currently PMC Leads, Project Leads or committers within any PMC or project. Each member organization of the CFF can also nominate one additional person not meeting these criteria as a candidate for the first TOC election.


Eligible Voters:


If you are a member of the Cloud Foundry technical community, you have a role to play here. Any individual who has contributed to CFF projects or technical working groups in the twelve months prior to the election is eligible to vote in the TOC election.


Contributions include, but are not limited to, opening PRs, reviewing and commenting on PRs, opening and commenting on issues, writing design docs, commenting on design docs, participating in mailing list discussions and participating in working groups.


Timeline:


  • May 11 - Announcement of Election and Call for Nominations

  • May 11 through May 28 - Candidate nomination period

  • June 1 - Election Begins via email ballots

  • June 15 - Election Closes

  • June 17 - Results Announced


TODO (What you need to do):


  1. Check the voter list: Each election cycle, we will use automated reporting to try to gather a list of eligible voters. The reporting will be imperfect, given the definition of eligibility being so broad. If you want to vote, or if you want to nominate someone for the TOC, please check for your name in the list. If you are not on the list, just submit an issue using this template. The deadline is May 28th to be added to the voter list.


  1. Nominate TOC candidates: Every eligible voter can nominate candidates for the TOC, and we encourage you to do so. If you are eligible to serve on the TOC, you can self nominate! If you want to nominate someone else, do so as well! You can nominate someone for the TOC by submitting an issue using this template. The deadline is May 28th to be nominated (and for the nominee to indicate acceptance).


More information on the election process can be found in the 2021 TOC election guide.


Final Thoughts:


This will be our first time running this process as a community, so please bear with us if there are any hiccups or issues. The CFF staff will be here to make the process as smooth as possible, and will err on the side of “get it right” vs. “get it done on schedule”. I also expect that we will change the operational processes we use to support the election after this first cycle. As we always share with Cloud Foundry end users, plan to iterate. :)


I know that I speak for everyone that has been involved in the technical governance process over the last several months when I say that this should be an exciting time for the community. We have come very far over the years, but have so much further to go.


Feel free to reach out directly to me if you have any questions, concerns or issues.


Thanks!



Chip Childers
Executive Director
Cloud Foundry Foundation


Re: [cf-dev] Update regarding Bionic Stemcells: Version 1.1 released for GA!

Eric Malm
 

Congratulations, Marco and everyone else who has contributed to the Bionic stemcell effort! Great to see the new line get all the way to GA!

Best,
Eric


From: cf-bosh@... <cf-bosh@...> on behalf of Daniel Jones via lists.cloudfoundry.org <daniel.jones=engineerbetter.com@...>
Sent: Friday, May 7, 2021 9:37 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Cc: cf-bosh@... <cf-bosh@...>; Paul Warren <warrenpa@...>
Subject: Re: [cf-bosh] [cf-dev] Update regarding Bionic Stemcells: Version 1.1 released for GA!
 
Congrats all. Government and enterprise users of OSS CF owe y'all a beverage!

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


On Fri, 7 May 2021 at 08:33, Marco Voelz via lists.cloudfoundry.org <marco.voelz=sap.com@...> wrote:

Dear Cloud Foundry community,

 

We've released Bionic 1.1 and removed the 'beta' flag on https://bosh.io/stemcells/ – this means: The Bionic stemcells are officially GA now!

 

This is a huge step for us, achieved under immense time pressure. A big thank you to everyone involved in this project: without this multi-company effort with people contributing what they can this would not have been possible and/or taken much, much longer. This community continues to amaze me and you're all excellent people!

 

What's next?

As announced earlier, Bionic is not part of the official CFF security advisories, but the team around @Paul Warren will start to prioritze the necessary work for this. Note that this "only" impacts the way how you receive notifications about new stemcells you should be applying. We already have automation in place to release new stemcells when Canonical releases an important CVE fix for Bionic! So for the time being: watch out for new stemcells on https://bosh.io/stemcells/ and make sure to bring them into production soon.

 

For all outstanding and ongoing work around the Bionic stemcells, I'd like to refer you again to https://github.com/orgs/cloudfoundry/projects/4. Raise issues if you find Bionic related problems in your Cloud Foundries, help us prioritize the outstanding work, and help us getting it done by collaborating!

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh-bionic on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Warm regards

Marco


Re: [cf-dev] Update regarding Bionic Stemcells: Version 1.1 released for GA!

Daniel Jones
 

Congrats all. Government and enterprise users of OSS CF owe y'all a beverage!

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


On Fri, 7 May 2021 at 08:33, Marco Voelz via lists.cloudfoundry.org <marco.voelz=sap.com@...> wrote:

Dear Cloud Foundry community,

 

We've released Bionic 1.1 and removed the 'beta' flag on https://bosh.io/stemcells/ – this means: The Bionic stemcells are officially GA now!

 

This is a huge step for us, achieved under immense time pressure. A big thank you to everyone involved in this project: without this multi-company effort with people contributing what they can this would not have been possible and/or taken much, much longer. This community continues to amaze me and you're all excellent people!

 

What's next?

As announced earlier, Bionic is not part of the official CFF security advisories, but the team around @Paul Warren will start to prioritze the necessary work for this. Note that this "only" impacts the way how you receive notifications about new stemcells you should be applying. We already have automation in place to release new stemcells when Canonical releases an important CVE fix for Bionic! So for the time being: watch out for new stemcells on https://bosh.io/stemcells/ and make sure to bring them into production soon.

 

For all outstanding and ongoing work around the Bionic stemcells, I'd like to refer you again to https://github.com/orgs/cloudfoundry/projects/4. Raise issues if you find Bionic related problems in your Cloud Foundries, help us prioritize the outstanding work, and help us getting it done by collaborating!

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh-bionic on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Warm regards

Marco


Update regarding Bionic Stemcells: Version 1.1 released for GA!

Marco Voelz
 

Dear Cloud Foundry community,

 

We've released Bionic 1.1 and removed the 'beta' flag on https://bosh.io/stemcells/ – this means: The Bionic stemcells are officially GA now!

 

This is a huge step for us, achieved under immense time pressure. A big thank you to everyone involved in this project: without this multi-company effort with people contributing what they can this would not have been possible and/or taken much, much longer. This community continues to amaze me and you're all excellent people!

 

What's next?

As announced earlier, Bionic is not part of the official CFF security advisories, but the team around @Paul Warren will start to prioritze the necessary work for this. Note that this "only" impacts the way how you receive notifications about new stemcells you should be applying. We already have automation in place to release new stemcells when Canonical releases an important CVE fix for Bionic! So for the time being: watch out for new stemcells on https://bosh.io/stemcells/ and make sure to bring them into production soon.

 

For all outstanding and ongoing work around the Bionic stemcells, I'd like to refer you again to https://github.com/orgs/cloudfoundry/projects/4. Raise issues if you find Bionic related problems in your Cloud Foundries, help us prioritize the outstanding work, and help us getting it done by collaborating!

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh-bionic on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Warm regards

Marco


Re: [cf-dev] Update regarding Bionic Stemcells: Production readiness

Guillaume Berche
 

Great news, thanks Chip for the update, and thanks to the community's vulnerability management team for their continued work on bionic stemcells vulns.

Guillaume.


On Mon, May 3, 2021 at 3:31 PM Chip Childers <cchilders@...> wrote:
The community's vulnerability management team was just discussing that last week, and I believe plans to coordinate with the Bionic stemcell folks to make that happen. +Paul Warren who has been leading the vuln mgmt team to confirm.

Chip Childers
Executive Director
Cloud Foundry Foundation


On Sun, May 2, 2021 at 4:42 PM Guillaume Berche <bercheg@...> wrote:
Thanks Marco for the update and to all contributors for their efforts to reach production readiness for bionic stemcell. I wonder whether the security advisories shared at [1] would in the future similarly be shared with the cloud foundry community for bionic based stemcell vulnerabilities (in addition to the existing current bionic-based rootfs vulnerabilities).

On Wed, Apr 28, 2021 at 5:43 PM Marco Voelz via lists.cloudfoundry.org <marco.voelz=sap.com@...> wrote:

Dear Cloud Foundry community,

 

End of April is approaching fast so here's your update regarding production readiness of Bionic stemcells.

 

TL;DR Bionic 0.28 is considered production ready for selected IaaS layers and will be the basis for a 1.x release of the stemcell.

 

Context

We've created a GitHub project providing more transparency and insight into the current community stemcell process: https://github.com/orgs/cloudfoundry/projects/4 Follow this if you're interested in more detailed progress and want to get involved.

 

What is the current state?

  • We at SAP consider Bionic 0.28 is production ready: We're rolling it out to all our production envs right now. There's one caveat, though: We can only vouch for production readiness on the IaaS layers we're running ourselves: AWS, GCP, Azure, AliCloud. Please note there are no issues known to us preventing you from using this stemcell on other IaaS layers, so our recommendation similar to the situation two weeks ago: please test the stemcell in your CF installations and provide feedback!
  • We're moving stemcell pipelines from infrastructure managed by VMware to a community owned GCP project. Shoutout to our colleagues at VMware for maintaining this so long on behalf of the community and helping us to transfer this!
  • Bionic 0.28 is essentially the base for a 1.x release of the stemcell. Currently there are no functional changes planned before promoting, the necessary work is mostly dealing with pipeline internals. The GitHub issue for the road towards 1.x is https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/157

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh-bionic on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Warm regards

Marco

 

PS If you're lacking context on what this mail is all about, see https://lists.cloudfoundry.org/g/cf-dev/message/9290


Re: [cf-dev] Update regarding Bionic Stemcells: Production readiness

Chip Childers
 

The community's vulnerability management team was just discussing that last week, and I believe plans to coordinate with the Bionic stemcell folks to make that happen. +Paul Warren who has been leading the vuln mgmt team to confirm.

Chip Childers
Executive Director
Cloud Foundry Foundation


On Sun, May 2, 2021 at 4:42 PM Guillaume Berche <bercheg@...> wrote:
Thanks Marco for the update and to all contributors for their efforts to reach production readiness for bionic stemcell. I wonder whether the security advisories shared at [1] would in the future similarly be shared with the cloud foundry community for bionic based stemcell vulnerabilities (in addition to the existing current bionic-based rootfs vulnerabilities).

On Wed, Apr 28, 2021 at 5:43 PM Marco Voelz via lists.cloudfoundry.org <marco.voelz=sap.com@...> wrote:

Dear Cloud Foundry community,

 

End of April is approaching fast so here's your update regarding production readiness of Bionic stemcells.

 

TL;DR Bionic 0.28 is considered production ready for selected IaaS layers and will be the basis for a 1.x release of the stemcell.

 

Context

We've created a GitHub project providing more transparency and insight into the current community stemcell process: https://github.com/orgs/cloudfoundry/projects/4 Follow this if you're interested in more detailed progress and want to get involved.

 

What is the current state?

  • We at SAP consider Bionic 0.28 is production ready: We're rolling it out to all our production envs right now. There's one caveat, though: We can only vouch for production readiness on the IaaS layers we're running ourselves: AWS, GCP, Azure, AliCloud. Please note there are no issues known to us preventing you from using this stemcell on other IaaS layers, so our recommendation similar to the situation two weeks ago: please test the stemcell in your CF installations and provide feedback!
  • We're moving stemcell pipelines from infrastructure managed by VMware to a community owned GCP project. Shoutout to our colleagues at VMware for maintaining this so long on behalf of the community and helping us to transfer this!
  • Bionic 0.28 is essentially the base for a 1.x release of the stemcell. Currently there are no functional changes planned before promoting, the necessary work is mostly dealing with pipeline internals. The GitHub issue for the road towards 1.x is https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/157

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh-bionic on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Warm regards

Marco

 

PS If you're lacking context on what this mail is all about, see https://lists.cloudfoundry.org/g/cf-dev/message/9290


Re: Update regarding Bionic Stemcells: Production readiness

Marco Voelz
 

Dear Benjamin,

 

Thanks for the update on the prometheus release. Your work on ensuring compatibility with the Bionic stemcells is highly appreciated!

 

Warm regards

Marco

 

From: cf-bosh@... <cf-bosh@...> on behalf of bguttmann via lists.cloudfoundry.org <bguttmann=anynines.com@...>
Date: Thursday, 29. April 2021 at 10:11
To: cf-bosh@... <cf-bosh@...>
Subject: Re: [cf-bosh] Update regarding Bionic Stemcells: Production readiness

Hi Marco,

thanks for the update.
Just if someone is interested we adjusted the prometheus-bosh-release to fix some minor grafana issues we saw with bionic stemcell. Afterwards we were able to successfully run concourse-bosh-release + prometheus-bosh-release with bionic stemcell. 

Greetings,
Benjamin


Re: [cf-dev] Update regarding Bionic Stemcells: Production readiness

Guillaume Berche
 

Thanks Marco for the update and to all contributors for their efforts to reach production readiness for bionic stemcell. I wonder whether the security advisories shared at [1] would in the future similarly be shared with the cloud foundry community for bionic based stemcell vulnerabilities (in addition to the existing current bionic-based rootfs vulnerabilities).


On Wed, Apr 28, 2021 at 5:43 PM Marco Voelz via lists.cloudfoundry.org <marco.voelz=sap.com@...> wrote:

Dear Cloud Foundry community,

 

End of April is approaching fast so here's your update regarding production readiness of Bionic stemcells.

 

TL;DR Bionic 0.28 is considered production ready for selected IaaS layers and will be the basis for a 1.x release of the stemcell.

 

Context

We've created a GitHub project providing more transparency and insight into the current community stemcell process: https://github.com/orgs/cloudfoundry/projects/4 Follow this if you're interested in more detailed progress and want to get involved.

 

What is the current state?

  • We at SAP consider Bionic 0.28 is production ready: We're rolling it out to all our production envs right now. There's one caveat, though: We can only vouch for production readiness on the IaaS layers we're running ourselves: AWS, GCP, Azure, AliCloud. Please note there are no issues known to us preventing you from using this stemcell on other IaaS layers, so our recommendation similar to the situation two weeks ago: please test the stemcell in your CF installations and provide feedback!
  • We're moving stemcell pipelines from infrastructure managed by VMware to a community owned GCP project. Shoutout to our colleagues at VMware for maintaining this so long on behalf of the community and helping us to transfer this!
  • Bionic 0.28 is essentially the base for a 1.x release of the stemcell. Currently there are no functional changes planned before promoting, the necessary work is mostly dealing with pipeline internals. The GitHub issue for the road towards 1.x is https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/157

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh-bionic on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Warm regards

Marco

 

PS If you're lacking context on what this mail is all about, see https://lists.cloudfoundry.org/g/cf-dev/message/9290


Re: Update regarding Bionic Stemcells: Production readiness

bguttmann@...
 

Hi Marco,

thanks for the update.
Just if someone is interested we adjusted the prometheus-bosh-release to fix some minor grafana issues we saw with bionic stemcell. Afterwards we were able to successfully run concourse-bosh-release + prometheus-bosh-release with bionic stemcell. 

Greetings,
Benjamin


Re: Update regarding Bionic Stemcells: Production readiness

Chip Childers
 



On Wed, Apr 28, 2021 at 1:56 PM Dr Nic Williams <drnicwilliams@...> wrote:
I concur — thanks Pivotal/VMWare for having sponsored the stemcell pipelines for so many years!


+1 to that, and congratulations to the team on the amazing progress on the new stemcells!
 


Re: Update regarding Bionic Stemcells: Production readiness

Dr Nic Williams
 

I concur — thanks Pivotal/VMWare for having sponsored the stemcell pipelines for so many years!

Dr Nic

On Thu, 29 Apr 2021 at 1:43 am, Marco Voelz via lists.cloudfoundry.org <marco.voelz=sap.com@...> wrote:

Dear Cloud Foundry community,

 

End of April is approaching fast so here's your update regarding production readiness of Bionic stemcells.

 

TL;DR Bionic 0.28 is considered production ready for selected IaaS layers and will be the basis for a 1.x release of the stemcell.

 

Context

We've created a GitHub project providing more transparency and insight into the current community stemcell process: https://github.com/orgs/cloudfoundry/projects/4 Follow this if you're interested in more detailed progress and want to get involved.

 

What is the current state?

  • We at SAP consider Bionic 0.28 is production ready: We're rolling it out to all our production envs right now. There's one caveat, though: We can only vouch for production readiness on the IaaS layers we're running ourselves: AWS, GCP, Azure, AliCloud. Please note there are no issues known to us preventing you from using this stemcell on other IaaS layers, so our recommendation similar to the situation two weeks ago: please test the stemcell in your CF installations and provide feedback!
  • We're moving stemcell pipelines from infrastructure managed by VMware to a community owned GCP project. Shoutout to our colleagues at VMware for maintaining this so long on behalf of the community and helping us to transfer this!
  • Bionic 0.28 is essentially the base for a 1.x release of the stemcell. Currently there are no functional changes planned before promoting, the necessary work is mostly dealing with pipeline internals. The GitHub issue for the road towards 1.x is https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/157

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh-bionic on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Warm regards

Marco

 

PS If you're lacking context on what this mail is all about, see https://lists.cloudfoundry.org/g/cf-dev/message/9290

--
Dr Nic Williams
+61 437 276 076
twitter @drnic


Update regarding Bionic Stemcells: Production readiness

Marco Voelz
 

Dear Cloud Foundry community,

 

End of April is approaching fast so here's your update regarding production readiness of Bionic stemcells.

 

TL;DR Bionic 0.28 is considered production ready for selected IaaS layers and will be the basis for a 1.x release of the stemcell.

 

Context

We've created a GitHub project providing more transparency and insight into the current community stemcell process: https://github.com/orgs/cloudfoundry/projects/4 Follow this if you're interested in more detailed progress and want to get involved.

 

What is the current state?

  • We at SAP consider Bionic 0.28 is production ready: We're rolling it out to all our production envs right now. There's one caveat, though: We can only vouch for production readiness on the IaaS layers we're running ourselves: AWS, GCP, Azure, AliCloud. Please note there are no issues known to us preventing you from using this stemcell on other IaaS layers, so our recommendation similar to the situation two weeks ago: please test the stemcell in your CF installations and provide feedback!
  • We're moving stemcell pipelines from infrastructure managed by VMware to a community owned GCP project. Shoutout to our colleagues at VMware for maintaining this so long on behalf of the community and helping us to transfer this!
  • Bionic 0.28 is essentially the base for a 1.x release of the stemcell. Currently there are no functional changes planned before promoting, the necessary work is mostly dealing with pipeline internals. The GitHub issue for the road towards 1.x is https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/157

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh-bionic on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Warm regards

Marco

 

PS If you're lacking context on what this mail is all about, see https://lists.cloudfoundry.org/g/cf-dev/message/9290


Vision for CF on Kubernetes

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

Hello everyone,

 

Over the past couple of months, we have heard questions from many of you about the future of Cloud Foundry on Kubernetes, and have been raising those questions amongst ourselves too.

 

During that time, we have been arriving at an initial proposal for a common way forward to present for discussion with all of you in the community. The result is the following document articulating our perspective, including the opportunities we see, the challenges with the status quo, and the refined direction we propose:

 

https://docs.google.com/document/d/1rG814raI5UfGUsF_Ycrr8hKQMo1RH9TRMxuvkgHSdLg/edit?usp=sharing

 

We invite everyone in the community to comment on it, and especially to give their feedback and criticism, with the goal of achieving a common vision for our whole community.

 

We hope that the document and the ensuing discussion will set an exciting direction for Cloud Foundry on Kubernetes for the entire Cloud Foundry ecosystem and beyond.

 

Thanks,

Jens Huesken (SAP), Richard Johnson (IBM), Emile Kfouri (VMware), Bernd Krannich (SAP), Eric Malm (VMware), Simon Moser (IBM)

 

 

 

---

 

Bernd Krannich

SAP BTP Foundational Plane Cloud Foundry and Core Experience

SAP SE

Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

 

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


Update regarding Bionic Stemcells

Marco Voelz
 

Dear Cloud Foundry community,

 

TL;DR: Bionic stemcells are on their way to GA. Xenial stemcells in open-source will not receive security updates after the end of April 2021. Act now and test your bosh releases and plan for migrating your systems, we’re doing it as well. Read on for context, open issues and migration caveats.

 

Context:

As part of an earlier mail to the cf-bosh and cf-dev mailing lists, there was an announcement around work to create a BOSH stemcell for Ubuntu 18.04 (code-named “Bionic Beaver”). The background is that Ubuntu 16.04 (code-named “Xenial Xerus”) runs out of standard support by the end of April 2021. We are already publishing beta versions of Bionic stemcells on bosh.io.

 

As announced earlier, VMware decided to continue to support Xenial-based stemcells for their commercial distribution and is therefore transferring all open-source stemcell related work to the community – a team currently staffed by IBM and SAP. We’re stepping in to ensure that there will be a continuously maintained Bionic stemcell available for the open-source community.

 

What does this mean for you as users of open-source Cloud Foundry?

  • You need to plan for switching to Bionic stemcells before the end of April 2021. Xenial stemcells will not get any security related updates after this date!
  • Test your bosh-releases! We found a few things that needed to be changed in existing releases to make them ready for Bionic – you should do the same
  • You will get a continuously maintained Bionic stemcell, for which Canonical offers standard support until the end of April 2023

 

What is the current state?

 

How do you migrate from Xenial to Bionic?

  • Upload the new stemcell to your BOSH director in addition to the existing Xenial stemcell
  • Add the new stemcell to your cloud-config
  • Update your runtime-config in case you’re using the stemcell key in the placement rules to ensure addons are installed on the new stemcell as well
  • Switch the referenced stemcell for each deployment manifest and re-deploy
  • Deploy bosh itself with the new stemcell. If you’re using bosh-deployment, there are cpi-specific ops-files for this available 

 

How can you help?

There are a number of ways you can get involved:

  • Depending on your configuration of Cloud Foundry, the open issues listed above might be blockers for you or not. Please help us prioritizing this with the teams if your migration to Bionic is blocked by any of these issues by commenting on the issue – except for the garden-runc issue, I’m not aware of any work on resolving them right now
  • Test your bosh-releases and provide feedback on things that work or don’t. Please note: the fact that you’re finding things we didn’t find in our tests most likely means that we’re requiring contributions from your side to successfully fix things
  • Scanning of stemcells (nessus, malware, etc) is something which quite often comes up in certifications. Setting this up in the open-source community would benefit everyone to check some boxes without investing in their own setup. Any help with getting this done in the community is highly appreciated!

 

Feedback?

Please reply to this mail on the list and/or send us a message in #bosh on Cloud Foundry slack. Don’t hesitate to DM me or send me a mail if you want to reach out privately.

 

Thanks in advance,

Marco

 

 


CFF Technical Governance Working Group - Call for participation

Chip Childers
 

Hello CF community!

Earlier in the year, the CFF's board of directors asked a small group of past and current technical community contributors to do an assessment of how our open source community was operating and to make recommendations for improvements to the governance process. That group has been meeting for a couple of months, and saw an opportunity to build a healthier and more dynamic open governance environment for the projects by rethinking the PMC Council / PMC / Project structure, and approaching governance closer to the Kubernetes, Istio and KNative community models.

The time has come to take the small group's initial ideas and open up the discussion to anyone in the community that cares to participate. You can find the work here: https://github.com/cloudfoundry/community

There are two ways that anyone can get involved in this effort:
  • The work is centered in GitHub, so feel free to review everything, comment on PRs and issues, propose your own PRs, open issues, etc... as the work continues to progress.
  • We welcome anyone with an interest in helping to evolve the CF community's project level decision making to join a weekly call on Friday's at 4PM GMT (11 AM US Eastern, 8 AM US Pacific). I have put the meeting on the CFF community calendar, and you can join us for the first call on Friday, December 4th!
We're looking forward to hearing from all of you or seeing you during the calls.

Thanks!

Chip Childers
Executive Director
Cloud Foundry Foundation


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

Blaine Forbush
 

Maya,

Thank you for clarifying the stemcell update roadmap. It is very exciting to hear that work on a Bionic stemcell is resuming! We've been trying to decide when to start adopting cf-for-k8s and a Bionic stemcell would give us more wiggle room to plan our transition while cf-for-k8s matures.

Blaine

On Wed, Sep 9, 2020 at 10:55 AM Maya Rosecrance <mrosecrance@...> wrote:
Thanks for pointing this out, I've clarified the docs. Canonical (the company behind Ubuntu) stops free Xenial support on April 2021. There is an option for people to purchase Ubuntu's ESM support and create their own stemcells which will be patched until April 2023 but that isn't something that will be released on bosh.io. We are restarting work on Bionic and you can follow that work by searching our public backlog for stories with the "bionic" tag. https://www.pivotaltracker.com/n/projects/956238


Re: Stemcell Bump Cadence

Maya Rosecrance
 

On Thu, Apr 2, 2020 at 01:07 PM, Maya Rosecrance wrote:
https://lists.cloudfoundry.org/g/cf-bosh/message/2707
Closing the loop on this thread. At the moment we're releasing at a 3 week cadence.


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

Maya Rosecrance
 

Thanks for pointing this out, I've clarified the docs. Canonical (the company behind Ubuntu) stops free Xenial support on April 2021. There is an option for people to purchase Ubuntu's ESM support and create their own stemcells which will be patched until April 2023 but that isn't something that will be released on bosh.io. We are restarting work on Bionic and you can follow that work by searching our public backlog for stories with the "bionic" tag. https://www.pivotaltracker.com/n/projects/956238


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

Blaine Forbush
 

Hi BOSH Team,

Can you clarify what the support plan is for the Ubuntu Xenial stemcell? You've stated here that Xenial support runs out in April 2021 but on bosh.io, it states that support will continue till April 2023 (See https://bosh.io/docs/ubuntu-os/#ubuntu-xenial). Which date is correct?

Blaine

1 - 20 of 2740