Date   
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: 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.

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

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

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. 

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

"何贵民(箫竹)
 

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. 

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

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
 
 

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

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#

Re: cluster auto-scale with bosh

Maya Rosecrance
 

Bosh does not have an autoscale feature at this time. We have heard of people using metrics to trigger bosh events to scale and we have an open issue that I'd encourage you to chime in on: https://github.com/cloudfoundry/bosh/issues/1652

Re: How to prevent compilation VMs from being deleted?

R M
 

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.

Re: How to prevent compilation VMs from being deleted?

Conor Nosal
 

`keep_unreachable_vms` is unrelated to compilation. Unreachable means that the bosh agent on the VM never connected to the director.

To keep compilation VMs, you want to set `reuse_compilation_vms` to true in the cloud config. https://bosh.io/docs/cloud-config/#compilation

On Tue, Jul 30, 2019 at 11:04 AM R M <rishi.investigate@...> wrote:
Hi there,

Is there any way of preventing compilation VMs from being destroyed if components fail to compile? I would like to be able to look into compilation VMs for troubleshooting the failures.

I tried following https://starkandwayne.com/blog/how-to-lock-vcap-password-for-bosh-vms/ but wasn't sure where to put following section wrt `cf-deploy`:

bosh -e bosh-1 -d cf deploy cf-deployment.yml -v system_domain=abc.com  --vars-store=/tmp/cloud-foundry/bosh/director-creds.yml

Thanks for any pointers ...

instance_groups:
- name: bosh
  properties:
    director:
      debug: 
        keep_unreachable_vms: true

How to prevent compilation VMs from being deleted?

R M
 

Hi there,

Is there any way of preventing compilation VMs from being destroyed if components fail to compile? I would like to be able to look into compilation VMs for troubleshooting the failures.

I tried following https://starkandwayne.com/blog/how-to-lock-vcap-password-for-bosh-vms/ but wasn't sure where to put following section wrt `cf-deploy`:

bosh -e bosh-1 -d cf deploy cf-deployment.yml -v system_domain=abc.com  --vars-store=/tmp/cloud-foundry/bosh/director-creds.yml

Thanks for any pointers ...

instance_groups:
- name: bosh
  properties:
    director:
      debug: 
        keep_unreachable_vms: true

cluster auto-scale with bosh

dhensel@...
 

Hello,

 

Does bosh have an auto-scale feature that can be used with VMWare in a K8S deployment ? I know K8S has auto-scaling but from my understanding it is not available for VMWare.

 

Thanks,

 

-Doug

 

Removal of Power DNS from BOSH

Morgan Fine
 

Hi BOSH Friends,

PowerDNS has existed in BOSH for a long time to support service discovery of BOSH deployments. More recently, BOSH DNS has been available as the recommended way of doing service discovery. 

The BOSH Director team would like to remove Power DNS from the BOSH Director in an effort to formally make BOSH DNS the supported and recommended way of doing service discovery. 

If you have any feedback or concerns with this approach, please let me know.

Thanks,
Morgan Fine
PM of BOSH Director Team

BOSH PMC meeting for June cancelled

Marco Voelz
 

Dear friends of BOSH,

 

I just cancelled the BOSH PMC meeting for June, which was originally scheduled on June 20th, as I am on vacation. I have updated the CFF calendar accordingly and deleted the event.

See you for the next BOSH PMC meeting in July!

 

Warm regards

Marco