1. cf-dev@lists.cloudfoundry.org
  2. Messages
   Date   
Re: [cf-bosh] [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: 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: Update regarding Bionic Stemcells: Production readiness

Chip Childers <cchilders@...>
 

Awesome to see end user testing results being reported back to the wider community here, and I hope that this inspires others to do the same... :)

Many thanks Aaron!

Chip Childers
Executive Director
Cloud Foundry Foundation


On Thu, May 6, 2021 at 2:56 PM Aaron Huber <aaron.m.huber@...> wrote:
We have fully tested the 0.28 stemcell using the vSphere CPI with the following deployments/releases and everything appears to be fully functioning:

cf-deployment
logsearch-boshrelease
logsearch-for-cloudfoundry
prometheus-boshrelease

We still need a new release of smb-volume-release to fix https://github.com/cloudfoundry/smb-volume-release/issues/16 but I've updated the notes with our temporary work-around and we'll go to production with a dev release for now.  Thanks to everyone involved for keeping the open source version of CF secure.

Aaron

Re: Update regarding Bionic Stemcells: Production readiness

Aaron Huber
 

We have fully tested the 0.28 stemcell using the vSphere CPI with the following deployments/releases and everything appears to be fully functioning:

cf-deployment
logsearch-boshrelease
logsearch-for-cloudfoundry
prometheus-boshrelease

We still need a new release of smb-volume-release to fix https://github.com/cloudfoundry/smb-volume-release/issues/16 but I've updated the notes with our temporary work-around and we'll go to production with a dev release for now.  Thanks to everyone involved for keeping the open source version of CF secure.

Aaron
Bi-weekly Round-Up: Technical + Ecosystem Updates from Cloud Foundry 5.4.21

Chris Clark
 

Hi folks! Reminder: Cloud Foundry Summit CFP closes May 21st.


From the Last Few Weeks:


Notable Releases:

  • cf-for-k8s
    • v3.1.0
      • Docs have been moved to the cf-for-k8s.io website.
      • Istio has been upgraded to an in-support version, with an additional upgrade to follow.
    • v4.0.0
      • The config block resource_validator_certificate for Eirini has been removed. It was introduced in v3.1.0 via the Eirini bump, so this is regarded as a breaking change.
      • This release supports mitigating the previously introduced interface change and preparation for an additional Istio update.
    • v4.1.0
      • Istio bump
      • Note: Istio does not support jump upgrades, so you MUST upgrade to v4.0 before upgrading to v4.1
  • BOSH v271.8.0
  • gosigar v1.2.0
  • diego-release v2.50.0
  • cf-networking-release v2.36.0
  • quarks-operator v7.2.3 and v7.2.4

Dates To Remember (All times US Pacific):

  • CF Technical Governance meeting – May 7 at 8 am
  • Bi-weekly Runtime PMC meeting – May 11 at 10:30 am
  • Office Hours: CAPI – May 12 at 9 am
  • CF Technical Governance meeting – May 14 at 8 am
  • Office Hours: Logging and Metrics – May 14 at 10:30 am
  • CF-for-K8s SIG meeting – May 18 at 8:30 am
  • May CAB call – May 19 at 8 am
  • CF Summit CFP closes – May 21 at 11:59 pm 
  • CF Summit – July 21-22

 

Check the community calendar for updates and meeting details.


Ecosystem and General News:

 


--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation
Re: 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: Update regarding Bionic Stemcells: Production readiness

Chip Childers <cchilders@...>
 

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

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

IMPORTANT NOTICE: [dotnet-core-buildpack] End of support for Node.js versions 10.x.x after 2021-05-27

Elliott Shanks <shankse@...>
 

The default version of Node.js in the .NET Core buildpack will change from the latest 10.x.x version to the latest 14.x.x version in the first release of the .NET Core buildpack after May 27, 2021. Due to the end of upstream support for Node.js 10.x.x, all buildpack users should ensure that their .NET Core apps run on a minimum buildpack supported version of Node.js 14.x.x or later.

Additionally, the .NET Core buildpack will temporarily include support for both Node.js versions 10.x.x and 14.x.x to allow .NET Core applications to build on 14.x.x prior to the removal of support for Node.js 10.x.x.

For more information about Node.js 10.x or LTS timelines for 10.x, refer to: https://github.com/nodejs/Release

For more information about supported Node.js versions in the .NET Core buildpack, refer to: https://buildpacks.cloudfoundry.org/#/buildpacks

 

Thanks,

Elliott Shanks, Buildpacks
IMPORTANT NOTICE: [ruby-buildpack] End of support for Node.js versions 10.x.x after 2021-05-27

Elliott Shanks <shankse@...>
 

The default version of Node.js in the Ruby buildpack will change from the latest 10.x.x version to the latest 14.x.x version in the first release of the Ruby buildpack after May 27, 2021. Due to the end of upstream support for Node.js 10.x.x, all buildpack users should ensure that their Ruby apps run on a minimum buildpack supported version of Node.js 14.x.x or later.

Additionally, the Ruby buildpack will temporarily include support for both Node.js versions 10.x.x and 14.x.x to allow Ruby applications to build on 14.x.x prior to the removal of support for Node.js 10.x.x.

For more information about Node.js 10.x or LTS timelines for 10.x, refer to: https://github.com/nodejs/Release

For more information about supported Node.js versions in the Ruby buildpack, refer to: https://buildpacks.cloudfoundry.org/#/buildpacks

 

Thanks,

Elliott Shanks, Buildpacks
IMPORTANT NOTICE: [nodejs-buildpack] End of Support for Node versions 10.x.x after 2021-05-27

Elliott Shanks <shankse@...>
 

The first release of the Node.js buildpack after May 27, 2021 will no longer include Node versions 10.x.x. These Node.js versions will no longer be supported upstream.[1] Please migrate your Node.js apps to supported versions of Node.js before that time.


Note: As 10.x.x is the current default version of Node.js in the buildpack, the default Node.js version will be updated to 14.x.x as a part of this removal. If you’d like to use a different Node.js version, please configure your application to select that version[2].


As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel.


[1] - https://github.com/nodejs/Release 

[2] - https://docs.cloudfoundry.org/buildpacks/node/node-tips.html#buildpack 


Thanks,

Elliott Shanks, Buildpacks
Re: [cf-bosh] Update regarding Bionic Stemcells: Production readiness

Chip Childers <cchilders@...>
 



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: [cf-bosh] Update regarding Bionic Stemcells: Production readiness

Dr Nic Williams <drnicwilliams@...>
 

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

Re: CF Application Runtime PMC: Logging and Metrics Project Lead Call for Nominations

Eric Malm
 

Hi, everyone,

VMware is nominating Benjamin Fuller for the Logging and Metrics Project Lead in the Application Runtime PMC.

Benjamin has been working for Pivotal and VMware since 2017. He has approached logging and metrics from many angles: in addition to maintaining the core Loggregator and BOSH logging and metrics systems, he has also written tools and services that process and distribute logs and metrics coming from the Loggregator APIs and has worked on logging and metric systems on Kubernetes.

Thanks,
Eric Malm

From: cf-dev@... <cf-dev@...> on behalf of Eric Malm via lists.cloudfoundry.org <emalm=vmware.com@...>
Sent: Tuesday, April 27, 2021 11:22 AM
To: cf-dev@... <cf-dev@...>
Subject: [cf-dev] CF Application Runtime PMC: Logging and Metrics Project Lead Call for Nominations
 
Hi, everyone,

Jesse Weaver, the lead for the Logging and Metrics project within the Application Runtime PMC, is stepping down from the project, as he is now focused on responsibilities internal to VMware. We thank him for his service.

The Logging and Metrics project now has an opening for its lead. Project leads must be nominated by a Cloud Foundry Foundation member. Please send nominations directly to me or in reply to this message no later than 11:59 PM PDT on Tuesday, May 11, 2021.

Also, if you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know.

Thanks,
Eric Malm, CF Application Runtime PMC Lead
CF Application Runtime PMC: Logging and Metrics Project Lead Call for Nominations

Eric Malm
 

Hi, everyone,

Jesse Weaver, the lead for the Logging and Metrics project within the Application Runtime PMC, is stepping down from the project, as he is now focused on responsibilities internal to VMware. We thank him for his service.

The Logging and Metrics project now has an opening for its lead. Project leads must be nominated by a Cloud Foundry Foundation member. Please send nominations directly to me or in reply to this message no later than 11:59 PM PDT on Tuesday, May 11, 2021.

Also, if you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know.

Thanks,
Eric Malm, CF Application Runtime PMC Lead
Bi-weekly Round-Up: Technical + Ecosystem Updates from Cloud Foundry 4.20.21

Chris Clark
 



From the Last Few Weeks:


Notable Releases:

    • Some Configmap properties have new default values to work with cf-for-k8s out of the box.
    • KubeCF-specific components have been removed.
    • numerous other features and breaking changes
  • cf-k8s-logging v0.7.0
  • cf-k8s-networking vv0.5.0 (draft)
  • cf-networking-release v2.36.0 and silk release v2.36.0
  • metric-proxy v1.3.0
  • UAA v75.1.0
  • haproxy-boshrelease v10.5.0
  • quarks-operator v7.2.2

Dates To Remember (All times US Pacific):

  • April CAB call – April 21 at 8 am
  • Livestream: “Cloud Native CI/CD Pipelines on Kubernetes with Tekton and Paketo” – April 21 at 9:30 am
  • CF Technical Governance meeting – April 23 at 8 am
  • Bi-weekly Runtime PMC meeting – April 27 at 10:30 am
  • CF Technical Governance meeting – April 30 at 8 am
  • CF-for-K8s SIG meeting – May 4 at 8:30 am
  • Bi-weekly Runtime PMC meeting – May 11 at 10:30 am
  • Office Hours: CAPI – May 12 at 9 am
  • Office Hours: Logging and Metrics – May 14 at 10:30 am
  • Summit CFP closes May 21 
  • CF Summit – July 21-22

Check the community calendar for updates and meeting details!


Ecosystem and General News:


--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation
Office Hours: CAPI

Seth Boyles
 

Hi all,

Starting this Wednesday, April 14th, the CAPI team will be hosting monthly office hours at 9am PDT.  You can find the event on the CFF Community Calendar on the second Wednesday of every month.  Here is a link to this week's office hours. 

Please join us with your questions and contributions!

- Seth
Re: CF Application Runtime PMC: CAPI and CLI Project Leads Call for Nominations

Zach Robinson <zrobinson@...>
 

Thanks Dr Nic and Bernd! It's been great working with y'all and the rest of the community in this space.

From: cf-dev@... <cf-dev@...> on behalf of Krannich, Bernd <bernd.krannich@...>
Sent: Tuesday, April 6, 2021 11:05 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] CF Application Runtime PMC: CAPI and CLI Project Leads Call for Nominations
 

+1 – thank you very much, Zach!

 

Regards,

Bernd

 

From: cf-dev@... <cf-dev@...> on behalf of Dr Nic Williams <drnicwilliams@...>
Date: Tuesday, 6. April 2021 at 22:48
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] CF Application Runtime PMC: CAPI and CLI Project Leads Call for Nominations

Thanks Zach for everything over so many years!!

 

Dr Nic

 

On Wed, 7 Apr 2021 at 1:34 am, Eric Malm <emalm@...> wrote:

Hi, everyone,

 

Zach Robinson, the lead for both the CAPI and the CLI projects within the Application Runtime PMC, has stepped down from the projects, as he is taking on other projects inside of VMware. We thank him for his many years of leadership and service to the Cloud Foundry community.

 

The CAPI and CLI teams now each have an opening for their project leads. Project leads must be nominated by a Cloud Foundry Foundation member. Please send nominations directly to me or in reply to this message no later than 11:59 PM PDT on Tuesday, April 20, 2021.

 

Also, if you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know.

 

Thanks,

Eric Malm, CF Application Runtime PMC Lead

--

Dr Nic Williams

+61 437 276 076

twitter @drnic
81 - 100 of 9398