Date   
CFF SIG Lifecycle

Marco Voelz
 

[cross-post for visibility on cf-bosh and cf-dev. Sorry for the spam if you're reading both lists. Future posts about this will be sent to cf-bosh only.]

 

Dear Friends of BOSH,

 

As the kubernetes community keeps growing and getting more traction and attention, we, the CF community, align more closely with the tools and community in the k8s ecosystem. Examples in the Runtime PMC are project Eirini and the ongoing efforts to leverage istio features for routing in CF, etc. Effectively, it seems that we're rebasing CF on top of a new abstraction, which is cool, because it allows us to do new cool things!

 

Within the BOSH PMC, there are also efforts towards installing CF on top of k8s, entirely without BOSH, called project Quarks. Especially when installing a complex and large distributed system like CF, issues with the current state of lifecycle management in the k8s ecosystem become apparent. Even more so if you're used to BOSH, which solves many issues for its users better than most other tools out there. Therefore, we're trying to bring some of the lessons we've learned by working on and with BOSH to the k8s ecosystem.

 

We have established a Lifecycle SIG and wrote down our ideas and opinions in the past few weeks [1]. While this document isn't done, we are at a point, we would like to open the discussion for everyone. If you're interested in participating in the conversation, please read the document and let us know what your think!

 

We appreciate your comments, thoughts, feedback and suggestions! You can reply on the cf-bosh mailing list or reach out in the ways described in the 'contact' section in the document.

 

Thanks and warm regards

Marco for the CFF SIG Lifecycle

 

[1] https://docs.google.com/document/d/1T1ZrwSV9aXWmF1tmUoMyo9M9EvWd07f-Uv5IO7nSmtY/edit#

Bosh AlibabaCloud CPI release has not had community version yet

"何贵民(箫竹)
 

Dear Friends of BOSH,
 
As the major Cloud Provider, we, Alibaba Cloud, align more closely with the Bosh and CF community. In the past two year, we have got great results, like providing Bosh AlibabaCloud CPI,  bosh-linux-stemcell-builder supports building AlibabaCloud xenial stemcell, cf-deployment supports AlibabaCloud cloud-config and so on. Besides, there also have more results needs us to achieve, like providing light stemcell, official CPI releases, CPI certification CI and others.
 
With the integration progress, there also needs CF's efforts to help us to accelerate and finish integration Alibaba Cloud with CloudFoundry.
 
Currently, we have provided the latest CPI codes in the https://github.com/cloudfoundry-incubator/bosh-alicloud-cpi-release and we has published several custom version to help our customer to deploy Bosh and CF. But, for our customers and us, we more need its community version. like AlibabaCloud full stemcell community version. 
 
In order to validate the CPI availability, I built my concourse pipeline to run the CPI CI, and the results as the following:

 
If there are any issues, please let us know by github or slack, and we will fix them asap.
 
We appreciate your comments, thoughts, feedback and suggestions! You can reply on the cf-bosh mailing list or reach out in the ways described in the 'contact' section in the document.
 
Thanks and warm regards
Guimin, He

Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

"何贵民(箫竹)
 

Dear Friends of BOSH,

Same as message #2640, importing bosh-alicloud-light-stemcell still needs your help.

In order to provide AlibabaCloud light stemcell community version, according to community requirements, I provided the bosh-alicloud-light-stemcell-builder: https://github.com/cloudfoundry-incubator/bosh-alicloud-light-stemcell-builder to build the latest light stemcell when there is a new full stemcell published. After that, the light stemcell meta info will be uploaded into https://github.com/cloudfoundry-incubator/stemcells-alicloud-index. Now, the builder has published three light stemcells, but them have not been published in the bosh.io.


The following is bosh-alicloud-light-stemcell-builder's result:




If there are any issues, please let us know by github or slack, and we will fix them asap.

 

We appreciate your comments, thoughts, feedback and suggestions! You can reply on the cf-bosh mailing list or reach out in the ways described in the 'contact' section in the document.



Thanks and warm regards

Guimin, He

 

Bosh AlibabaCloud CPI Certification has not been merged yet

"何贵民(箫竹)
 

Dear Friends of BOSH,
 
Same as message #2640, merging bosh Alibaba Cloud cpi certification still needs your help.

In order to validate the Bosh CPI, according to community requirements, I implemented the bosh-cpi-certification for AlibabaCloud and the codes has been submitted to PR: https://github.com/cloudfoundry-incubator/bosh-cpi-certification/pull/15 and https://github.com/cloudfoundry/bosh-acceptance-tests/pull/40. But, so far, them have not been merged yet.


The following is bosh-cpi-certification result:



The failed job came from two issues:  https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/97 and https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/98.
Currently, I have no idea on the issues, and can you give me some help?

Thanks and warm regards

 

Guimin, He

Bosh Deployment on Alibaba Cloud has not been merged yet

"何贵民(箫竹)
 

Dear Friends of BOSH,
 
Same as message #2640, in order to help developers to deploy bosh director, we provided the bosh-deployment CPI manifest by the PR: https://github.com/cloudfoundry/bosh-deployment/pull/175 and it has been opened more than one year, and still has not been merged.

If there are any issues, please let us know by github or slack, and we will fix them asap.
 
We appreciate your comments, thoughts, feedback and suggestions! You can reply on the cf-bosh mailing list or reach out in the ways described in the 'contact' section in the document.
 
Thanks and warm regards
Guimin, He
 
 

Docs Bosh for Alibaba Cloud CPI has not been merged yet

"何贵民(箫竹)
 

Dear Friends of BOSH,
 
Same as message #2640, in order integration, we provided the latest docs for bosh AlibabaCloud CPI by PR: https://github.com/cloudfoundry/docs-bosh/pull/429, but now this PR has been closed and I also have resubmitted: https://github.com/cloudfoundry/docs-bosh/pull/667 . I want to know, is there any ETA or plan to review it?

If there are any issues, please let us know by github or slack, and we will fix them asap.
 
We appreciate your comments, thoughts, feedback and suggestions! You can reply on the cf-bosh mailing list or reach out in the ways described in the 'contact' section in the document.
 
Thanks and warm regards
Guimin, He

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

"何贵民(箫竹)
 

This issue has been talked for a long time in the slack https://cloudfoundry.slack.com/archives/C02HPPYQ2/p1565144830091600?thread_ts=1557828465.233200&cid=C02HPPYQ2, but now it is still not fixed. 

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

Chip Childers
 

+Voelz, Marco ... Marco - think that the BOSH PMC can prioritize this appropriately?

Chip Childers, CTO
Cloud Foundry Foundation


On Wed, Aug 7, 2019 at 12:33 AM <guimin.hgm@...> wrote:
This issue has been talked for a long time in the slack https://cloudfoundry.slack.com/archives/C02HPPYQ2/p1565144830091600?thread_ts=1557828465.233200&cid=C02HPPYQ2, but now it is still not fixed. 

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

Mukesh Gadiya
 

Hi Alicloud folks,

The story for publishing on bosh.io is prioritized in the backlog. 
Please watch this story - https://www.pivotaltracker.com/story/show/167410186. When it's delivered, the alicloud stemcells will be available on bosh.io

Cheers,
Mukesh 

On Wed, Aug 7, 2019 at 7:09 AM Chip Childers <cchilders@...> wrote:
+Voelz, Marco ... Marco - think that the BOSH PMC can prioritize this appropriately?

Chip Childers, CTO
Cloud Foundry Foundation


On Wed, Aug 7, 2019 at 12:33 AM <guimin.hgm@...> wrote:
This issue has been talked for a long time in the slack https://cloudfoundry.slack.com/archives/C02HPPYQ2/p1565144830091600?thread_ts=1557828465.233200&cid=C02HPPYQ2, but now it is still not fixed. 

Reminder: BOSH PMC meeting for August tomorrow!

Marco Voelz
 

Dear friends of BOSH,

 

This is your friendly reminder that the BOSH PMC meeting for August will happen tomorrow, Aug 15th at 8:00 AM PST/17:00 CEST.

 

The current preliminary agenda is located at https://github.com/cloudfoundry/pmc-notes/blob/master/Bosh/2019-08-15-bosh.md, if you'd like to bring your own topic, please PR the agenda doc or let us know at the beginning of the call tomorrow.

 

Looking forward to seeing many of you!

 

Warm regards

Marco

 

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

"何贵民(箫竹)
 

HI Mukesh, I noticed this story is still in Unstarted and is there any ETA for it? It is very important for our customers and us. Thanks in advance.

Regards,
Guimin

Re: How to prevent compilation VMs from being deleted?

Benjamin Gandon
 

The point is to debug the compile scripts in the VM where they are running.
There is a way of dealing with VMs being destroyed after the compile script fail :

  1. Include a pause 10000 statement at the top of your compile script.
  2. bosh ssh to the compilation VM when it’s stuck on this pause 10000.
  3. Make a copy of the failing compile script with the pause 10000 removed.
  4. Run this copy with bash -x to inspect its behavior.
  5. Debug your script, fix it with an editor like vim, and iterate to step #4.
  6. When your compile script is working, quit the bosh ssh session and bosh scp it to your local machine, for inclusion in your BOSH Release.


Le 30 juil. 2019 à 18:02, R M <rishi.investigate@...> a écrit :

Thanks Conor - I already have `reuse_compilation_vms` set but I believe it is intended to be re-used for compilation.  BOSH seems to delete it anyway once the compilation job finishes/fails.

BOSH OpenStack CPI: planned end of maintenance by end of 2019

Marco Voelz
 

Dear Friends of OpenStack,

 

Since 2015, the BOSH OpenStack CPI [1] is maintained by the BOSH team Europe at SAP. Historically, this made sense, because SAP was a large user of OpenStack, but in the meantime our focus as a company has shifted.

 

Consequently, we would like to announce that our team at SAP will stop maintaining the BOSH OpenStack CPI and a few related projects like CF OpenStack validator [2] and bosh-openstack-environment-templates [3] *by the end of 2019*. Already starting right now, we are stopping feature work on the BOSH OpenStack CPI. From 2020 on, we will not release any new versions of the CPI, be it for fixing CVEs, ensuring support of new OpenStack versions, or other reasons.

 

If there is anybody in the community with interest to continue maintenance and development of the BOSH OpenStack CPI and potentially the related projects as well, we're happy to transfer the ownership of projects and CI pipelines. If no maintainer is found for a project,  the regular course of action would be to move it to the cloudfoundry-attic organization.

 

If this is a topic you'd like to talk about, please reach out to us by replying to this mail or contacting me directly.

 

Warm regards

Marco

 

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

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

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

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

"何贵民(箫竹)
 

HI Chip and Mukesh, I am sorry for the bothering again.
I noticed this story https://www.pivotaltracker.com/story/show/167410186 is still in Unstarted and I am very anxious for the story and it is very important for our customers. Is there any ETA for it? Can push up its priority?

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

Mukesh Gadiya
 

Unfortunately, we have been resource constrained and were not able to get to it. Given it's smaller scope, I just moved it to the top of the backlog so that we get to it as soon as possible. 



On Wed, Aug 21, 2019 at 9:32 AM <guimin.hgm@...> wrote:
HI Chip and Mukesh, I am sorry for the bothering again.
I noticed this story https://www.pivotaltracker.com/story/show/167410186 is still in Unstarted and I am very anxious for the story and it is very important for our customers. Is there any ETA for it? Can push up its priority?

Re: BOSH OpenStack CPI: planned end of maintenance by end of 2019

Daniel Jones
 

Hi all,

I should imagine there must be enough very large consumers of the OpenStack CPI to make it commercially viable for a small team to be funded that could maintain it, were all said consumers to pull together and contribute what I should imagine would be a small sliver of their total CF expenditure.

If any OpenStack CPI users want to talk to EngineerBetter about funded development, we'd be happy to have that conversation as we're doing some similar EOL work for other CF projects. 

Similarly, if our chums at Anynines, Altoros, S&W, GrapeUp, EVoila, GStack, Armakuni, Novatec or others want to work together on this, we'd be open to that. I can also imagine that some chunk of Pivotal's revenue depends on this CPI, so perhaps some of our teal friends might be interested too? It could be like one of those Marvel films (that I don't watch) where we all team up to vanquish the evil villain of abandoned software. 

Marco - how many pairs were working on these streams of work, and do you have a feel for the balance of vital maintenance, tech debt, new features, and quality-of-life improvements in the backlog?

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


On Wed, 21 Aug 2019 at 09:38, Marco Voelz <marco.voelz@...> wrote:

Dear Friends of OpenStack,

 

Since 2015, the BOSH OpenStack CPI [1] is maintained by the BOSH team Europe at SAP. Historically, this made sense, because SAP was a large user of OpenStack, but in the meantime our focus as a company has shifted.

 

Consequently, we would like to announce that our team at SAP will stop maintaining the BOSH OpenStack CPI and a few related projects like CF OpenStack validator [2] and bosh-openstack-environment-templates [3] *by the end of 2019*. Already starting right now, we are stopping feature work on the BOSH OpenStack CPI. From 2020 on, we will not release any new versions of the CPI, be it for fixing CVEs, ensuring support of new OpenStack versions, or other reasons.

 

If there is anybody in the community with interest to continue maintenance and development of the BOSH OpenStack CPI and potentially the related projects as well, we're happy to transfer the ownership of projects and CI pipelines. If no maintainer is found for a project,  the regular course of action would be to move it to the cloudfoundry-attic organization.

 

If this is a topic you'd like to talk about, please reach out to us by replying to this mail or contacting me directly.

 

Warm regards

Marco

 

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

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

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

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

"何贵民(箫竹)
 

HI Mukesh, Thanks a lot for your effort. 

HI Chip, can you help to accelerate the story https://www.pivotaltracker.com/n/projects/2238419/stories/167410186 ? It is really very very very important for us and it have blocked our customer's work. Thanks in advance.

Re: BOSH OpenStack CPI: planned end of maintenance by end of 2019

Marco Voelz
 

Hi everyone, hi Daniel,

 

Thanks for the interest in the BOSH OpenStack CPI, I'm happy to give you some perspective on what we had been doing in the past and what the current status is.

 

* We've automated pretty much everything in terms of regular maintenance. This includes updates of the dependencies like rubygems [1], and consumption of the ruby-release in bosh packages [2]. We have automated the update of ruby-release itself, such that ruby, rubygems, etc are automatically updated.

* All PRs are tested against the supported set of OpenStack APIs by using the cf-openstack-validator to run a base set of API interactions with OpenStack [3]. We're using OpenLab [4] to provide virtualized OpenStack environments for us. Adding a new one is only a few lines of yml [5]

* New versions of bosh, a stemcell, or the cpi are automatically tested in a pipeline using BATs and e2e tests. While this pipeline currently runs against an SAP provided OpenStack, it is easy to set this up against a different OpenStack

* There are very few issues open (currently 7 issues and 3 of those are feature requests)

* There isn't really left-over work for now: Our backlog contains 37 open stories tagged with 'cpi' [6]. Quite a few are crossed out (we decided not to do them, but keep them for future reference to document decisions), or even about different CPIs like AWS and GCP.

* The biggest pain point in the past have been fog-openstack and excon. Updates of these two libraries are always a gamble, they don't seem to be well-tested and introduced quite some annoyances over the last few years. One example is how the individual OpenStack projects adopted microversions in their APIs and how fog-openstack selects which version to use. More recently, this didn't have much impact – it mostly matters when you're trying to use functionality that isn't present below a certain microversion or has been removed starting from a version.

* We have been trying to support the community with their OpenStack issues in #openstack and #bosh on CF Slack. Interrupts don't come on a daily basis, but there is a need for looking at community questions.

* We tried to improve the ecosystem with projects like cf-openstack-validator [9], better OpenStack support in bbl [10], and .tf templates for OpenStack [11]. Also maintaining the OpenStack part of the docs on bosh.io

 

Overall, I guess the amount of work you would need to put into the OpenStack CPI depends on what you're trying to do with it. My guess is that a pair of engineers is sufficient to address some of the more recent feature requests and keep the system alive and healthy.

 

Let me know if you need more information to get a feeling for what it means to take over this work. I'm happy to talk about individual aspects some more, if it helps.

 

Warm regards

Marco

 

[1] https://github.com/cloudfoundry/bosh-openstack-cpi-release/pull/212

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

[3] https://github.com/cloudfoundry/bosh-openstack-cpi-release/pull/212#issuecomment-518850649

[4] https://openlabtesting.org/

[5] https://github.com/cloudfoundry/bosh-openstack-cpi-release/commit/3c613ad99c574bcf741a796de9c1c9557480c5c5

[6] https://www.pivotaltracker.com/n/projects/1456570/search?q=label%3A%22cpi%22

[7] https://github.com/cloudfoundry/bosh-openstack-cpi-release/issues/186

[8] https://github.com/cloudfoundry/bosh-openstack-cpi-release/issues/211

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

[10] https://github.com/cloudfoundry/bosh-bootloader/pull/431

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

 

 

 

 

From: <cf-bosh@...> on behalf of Daniel Jones <daniel.jones@...>
Reply to: "cf-bosh@..." <cf-bosh@...>
Date: Thursday, 22. August 2019 at 15:52
To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh@...>
Cc: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-bosh] BOSH OpenStack CPI: planned end of maintenance by end of 2019

 

Hi all,

 

I should imagine there must be enough very large consumers of the OpenStack CPI to make it commercially viable for a small team to be funded that could maintain it, were all said consumers to pull together and contribute what I should imagine would be a small sliver of their total CF expenditure.

 

If any OpenStack CPI users want to talk to EngineerBetter about funded development, we'd be happy to have that conversation as we're doing some similar EOL work for other CF projects. 

 

Similarly, if our chums at Anynines, Altoros, S&W, GrapeUp, EVoila, GStack, Armakuni, Novatec or others want to work together on this, we'd be open to that. I can also imagine that some chunk of Pivotal's revenue depends on this CPI, so perhaps some of our teal friends might be interested too? It could be like one of those Marvel films (that I don't watch) where we all team up to vanquish the evil villain of abandoned software. 

 

Marco - how many pairs were working on these streams of work, and do you have a feel for the balance of vital maintenance, tech debt, new features, and quality-of-life improvements in the backlog?


Regards,

Daniel 'Deejay' Jones - CTO

+44 (0)79 8000 9153

EngineerBetter Ltd - More than cloud platform specialists

 

 

On Wed, 21 Aug 2019 at 09:38, Marco Voelz <marco.voelz@...> wrote:

Dear Friends of OpenStack,

 

Since 2015, the BOSH OpenStack CPI [1] is maintained by the BOSH team Europe at SAP. Historically, this made sense, because SAP was a large user of OpenStack, but in the meantime our focus as a company has shifted.

 

Consequently, we would like to announce that our team at SAP will stop maintaining the BOSH OpenStack CPI and a few related projects like CF OpenStack validator [2] and bosh-openstack-environment-templates [3] *by the end of 2019*. Already starting right now, we are stopping feature work on the BOSH OpenStack CPI. From 2020 on, we will not release any new versions of the CPI, be it for fixing CVEs, ensuring support of new OpenStack versions, or other reasons.

 

If there is anybody in the community with interest to continue maintenance and development of the BOSH OpenStack CPI and potentially the related projects as well, we're happy to transfer the ownership of projects and CI pipelines. If no maintainer is found for a project,  the regular course of action would be to move it to the cloudfoundry-attic organization.

 

If this is a topic you'd like to talk about, please reach out to us by replying to this mail or contacting me directly.

 

Warm regards

Marco

 

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

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

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

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

Mukesh Gadiya
 

Story is accepted and I can see the alicloud light stemcells on bosh.io. Let me know if you need any other help.


On Thu, Aug 22, 2019 at 7:03 PM <guimin.hgm@...> wrote:
HI Mukesh, Thanks a lot for your effort. 

HI Chip, can you help to accelerate the story https://www.pivotaltracker.com/n/projects/2238419/stories/167410186 ? It is really very very very important for us and it have blocked our customer's work. Thanks in advance.

Re: Bosh AlibabaCloud light stemcell has not been imported to provide community version yet

"何贵民(箫竹)
 

HI Mukesh, Thanks a lot for your effort. Light stemcell is accepted is very important for us.

Yes, except for light stemcell, there also have other important things for us and our customers:

1. rotate the wtmp/btmp logs timeout
    When running the bosh-linux-stemcell-builder CI, I always happened an error: "rotate the wtmp/btmp logs timeout" and this error prevent my CI going green. And then, it will block our customers to use our stemcell and bosh CPI. Can you have a look in the github: https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/97

2. Bosh AlibabaCloud CPI release has not had community version yet
    At present, we provided stemcells, cf-deployment, bosh-alicloud-cpi and so on. But the CPI is still missing in the bosh.io. Can you build a story to push it? See message: https://lists.cloudfoundry.org/g/cf-bosh/message/2640 ?

3. bosh-deployment and docs-bosh for alibaba cloud still need story
    We have submitted bosh-deployment PR https://github.com/cloudfoundry/bosh-deployment/pull/175 for a long time, but it is still in not-merged. Can you build a story to push it? See message: https://lists.cloudfoundry.org/g/cf-bosh/message/2643 ?
    Still applies for docs-bosh, See message: https://lists.cloudfoundry.org/g/cf-bosh/message/2644 ?

I need your more help and ideas. Please let me know if there have any issues. Thanks in advance.