Date   
Re: Docs Bosh for Alibaba Cloud CPI has not been merged yet

"何贵民(箫竹)
 

HI Chip and Mukesh,

At present, the bosh-deployment has supported alibaba cloud, but the docs-bosh PR  https://github.com/cloudfoundry/docs-bosh/pull/667  has not been merged yet. Is there any progress on it?

Re: Bosh AlibabaCloud CPI release has not had community version yet

"何贵民(箫竹)
 

HI Chip and Mukesh,

At present, the bosh-deployment has supported alibaba cloud, but the alibaba cloud bosh cpi https://github.com/cloudfoundry-incubator/bosh-alicloud-cpi-release has not been published in the bosh.io. Is there any plan for it? Thanks in advance.

Thanks and warm regards
Guimin, He

Re: Bosh AlibabaCloud CPI Certification has not been merged yet

"何贵民(箫竹)
 

HI Chip and Mukesh,

Currently, the PR https://github.com/cloudfoundry-incubator/bosh-cpi-certification/pull/15 and https://github.com/cloudfoundry/bosh-acceptance-tests/pull/40 have been merged and the issue https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/98 also has been fixed. But, the issue https://github.com/cloudfoundry/bosh-linux-stemcell-builder/issues/97  is still in opened. At present, I have submitted a PR https://github.com/cloudfoundry/bosh-linux-stemcell-builder/pull/101 to fix the issue #97. After that, the test-stemcell-ubuntu-xenial can always be success.
Now, the PR #101 has been submitted in 5 days ago, but there is no any reply on it, and its story https://www.pivotaltracker.com/n/projects/2238419/stories/168192167 is still in Unscheduled. Can you push it? Thanks in advance.

Thanks and warm regards
Guimin, He

Re: Bosh AlibabaCloud CPI release has not had community version yet

James Myers
 

Hi Guimin,

We can't actually publish the bosh-alicloud-cpi-release to bosh.io until the release is reproducibly creatable from the BOSH release directory. The current issue is that the release uses the "local" blobstore configuration for the release blobs. This means that final releases are not creatable as there is no publicly accessible location for us to grab the release assets. You need to ensure that `bosh create-release releases/bosh-alicloud-cpi/bosh-alicloud-cpi-<version>.yml` works on machines that have freshly cloned the repository. I have left more details on this topic here: https://github.com/cloudfoundry/bosh-deployment/pull/175#issuecomment-525052322.

Once you have fixed these issues, you can add the bosh-alicloud-cpi-release to the releases index through a pull request here: https://github.com/bosh-io/releases 

Let me know if you have any questions,

Jim

On Tue, Sep 3, 2019 at 8:13 AM <guimin.hgm@...> wrote:
HI Chip and Mukesh,

At present, the bosh-deployment has supported alibaba cloud, but the alibaba cloud bosh cpi https://github.com/cloudfoundry-incubator/bosh-alicloud-cpi-release has not been published in the bosh.io. Is there any plan for it? Thanks in advance.

Thanks and warm regards
Guimin, He

回复: [cf-bosh] Bosh AlibabaCloud CPI release has not had community version yet

"何贵民(箫竹)
 

Hi Jim,
Thanks for your reply and I will fix Above issue asap.





来自钉钉专属商务邮箱

------------------------------------------------------------------
发件人:James Myers<jmyers@...>
日 期:2019年09月04日 00:04:44
收件人:<cf-bosh@...>
主 题:Re: [cf-bosh] Bosh AlibabaCloud CPI release has not had community version yet

Hi Guimin,

We can't actually publish the bosh-alicloud-cpi-release to bosh.io until the release is reproducibly creatable from the BOSH release directory. The current issue is that the release uses the "local" blobstore configuration for the release blobs. This means that final releases are not creatable as there is no publicly accessible location for us to grab the release assets. You need to ensure that `bosh create-release releases/bosh-alicloud-cpi/bosh-alicloud-cpi-<version>.yml` works on machines that have freshly cloned the repository. I have left more details on this topic here: https://github.com/cloudfoundry/bosh-deployment/pull/175#issuecomment-525052322.

Once you have fixed these issues, you can add the bosh-alicloud-cpi-release to the releases index through a pull request here: https://github.com/bosh-io/releases 

Let me know if you have any questions,

Jim

On Tue, Sep 3, 2019 at 8:13 AM <guimin.hgm@...> wrote:
HI Chip and Mukesh,

At present, the bosh-deployment has supported alibaba cloud, but the alibaba cloud bosh cpi https://github.com/cloudfoundry-incubator/bosh-alicloud-cpi-release has not been published in the bosh.io. Is there any plan for it? Thanks in advance.

Thanks and warm regards
Guimin, He


Re: 回复: [cf-bosh] Bosh AlibabaCloud CPI release has not had community version yet

"何贵民(箫竹)
 

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

Morgan Fine
 

Hi All,

Pivotal plans to take over support of the Openstack CPI at the end of 2019 when our SAP friends move away from it. I believe closer to the end of the year we would like to pair to make sure the transition is successful.

Additionally, if there are other companies teams out there that are interested in helping to support it, we'd be more than happy to collaborate on it.

Best,
Morgan

On Fri, Aug 23, 2019 at 2:25 AM Marco Voelz <marco.voelz@...> wrote:

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

Project Quarks Alpha Release

Vlad Iovanov <VIovanov@...>
 

Hello everyone,

 

On behalf of the Quarks team, I'd like to introduce Cloud Foundry Operator v0.4.2.

https://github.com/cloudfoundry-incubator/cf-operator/releases/tag/v0.4.2

 

This is our first alpha release. Post CF Summit EU, we gathered feedback and made some bugfixes.

Many thanks to everyone that's been testing and working with us to make this happen.

 

Getting started is really easy, you can try the snippets below. For detailed requirements and advanced usage, please find us on slack (#quarks-dev).

There are many cool things to learn and experiment with, including Eirini.

 

kubectl create namespace scf

 

helm install --namespace cf-operator \

     --name cf-operator \

     --set operator.watchNamespace=scf \

     https://s3.amazonaws.com/cf-operators/release/helm-charts/cf-operator-v0.4.2%2B0.g604925f0.tgz

 

helm install \

    --namespace scf \

    --name scf \

    --set "system_domain=scf.suse.dev" \

    https://scf-v3.s3.amazonaws.com/scf-3.0.0-2f83620.tgz

 

Contributors are welcome!

 

Thanks,

The Quarks team

 

Re: [cf-dev] Project Quarks Alpha Release

Dr Nic Williams
 

Well done to all the teams involved!

For anyone at SpringOne, a demo of SCF/cf-operator will appear in Matthias and my talk tomorrow at 10:30 in 18AB “Platforms Demystified”

Nic
--
Dr Nic Williams
Stark & Wayne LLC
+61 437 276 076
twitter @drnic

SIG Meeting: Cloud Foundry for Kubernetes

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

Hello all,

 

In a set of conversations before, at, and after CF Summit in The Hague, people from IBM, Pivotal, SAP and Suse (cc’d) came to the conclusion that it would be a good idea to suggest a “revival” of the Cloud Foundry for Kubernetes Special Interest Group meetings. The goal is to create an open forum for bringing up and discussing topics around moving Cloud Foundry on top of Kubernetes.

 

The first meeting of the SIG will be on October 15th, 8:30 AM PST and the next instance of the recurring meeting is on October 29th, two weeks later. Please see the Cloud Foundry community calendar [1] for the invites and dial-in. Additionally, Swarna has kindly created a Google doc [2] to collect meeting minutes and to collect topics that people want to discuss in this forum – so, please add the topics you would like to discuss to the Google doc. Additionally, we would like to record the meetings.

 

So, our call to the community is to join these calls if the topic of Cloud Foundry on top of Kubernetes is of interest for you. Looking forward to talking to you.

 

Thanks,

Julian Friedman (IBM), Simon Moser (IBM), Dieu Cao (Pivotal), Eric Malm (Pivotal), Jeff Hobbs (Suse), Troy Topnik (Suse), Jens Huesken (SAP), Bernd Krannich (SAP)

 

P.S.: This call does not replace but complement the existing CFF SIG Lifecycle Marco Voelz has announced earlier.

 

[1] https://www.cloudfoundry.org/community-calendar/

[2] https://docs.google.com/document/d/1ULNBEjlrNAgn3ko9y8ZJfwI7mw5-oofYdjl-dhkEoDA/edit#

[3] https://lists.cloudfoundry.org/g/cf-bosh/message/2639

 

Bernd Krannich

SAP Cloud Platform

SAP SE

Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

 

T +49 6227 7-66220, F +49 6227 78-23923, 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.

Re: SIG Meeting: Cloud Foundry for Kubernetes

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

Forgot to mention it: We are also “reviving” the corresponding Slack channel #cf-for-k8s on Cloud Foundry Slack (https://www.cloudfoundry.org/community/ à Cloud Foundry Slack).

 

From: Bernd Krannich <bernd.krannich@...>
Date: Thursday, 10. October 2019 at 15:59
To: "cf-dev@..." <cf-dev@...>, "cf-bosh@..." <cf-bosh@...>
Cc: Julz Friedman <julz.friedman@...>, Simon Moser <sdmoser@...>, Dieu Cao <dcao@...>, Eric Malm <emalm@...>, Jeff Hobbs <jeff.hobbs@...>, Troy Topnik <troy.topnik@...>, Jens Huesken <jens.huesken@...>, Swarna Podila <spodila@...>, Chip Childers <cchilders@...>
Subject: SIG Meeting: Cloud Foundry for Kubernetes

 

Hello all,

 

In a set of conversations before, at, and after CF Summit in The Hague, people from IBM, Pivotal, SAP and Suse (cc’d) came to the conclusion that it would be a good idea to suggest a “revival” of the Cloud Foundry for Kubernetes Special Interest Group meetings. The goal is to create an open forum for bringing up and discussing topics around moving Cloud Foundry on top of Kubernetes.

 

The first meeting of the SIG will be on October 15th, 8:30 AM PST and the next instance of the recurring meeting is on October 29th, two weeks later. Please see the Cloud Foundry community calendar [1] for the invites and dial-in. Additionally, Swarna has kindly created a Google doc [2] to collect meeting minutes and to collect topics that people want to discuss in this forum – so, please add the topics you would like to discuss to the Google doc. Additionally, we would like to record the meetings.

 

So, our call to the community is to join these calls if the topic of Cloud Foundry on top of Kubernetes is of interest for you. Looking forward to talking to you.

 

Thanks,

Julian Friedman (IBM), Simon Moser (IBM), Dieu Cao (Pivotal), Eric Malm (Pivotal), Jeff Hobbs (Suse), Troy Topnik (Suse), Jens Huesken (SAP), Bernd Krannich (SAP)

 

P.S.: This call does not replace but complement the existing CFF SIG Lifecycle Marco Voelz has announced earlier.

 

[1] https://www.cloudfoundry.org/community-calendar/

[2] https://docs.google.com/document/d/1ULNBEjlrNAgn3ko9y8ZJfwI7mw5-oofYdjl-dhkEoDA/edit#

[3] https://lists.cloudfoundry.org/g/cf-bosh/message/2639

 

Bernd Krannich

SAP Cloud Platform

SAP SE

Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany

 

T +49 6227 7-66220, F +49 6227 78-23923, 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.

Reminder: BOSH PMC Meeting for November tomorrow

Marco Voelz
 

Dear friends of BOSH,
This is your friendly reminder that the BOSH PMC meeting for November will happen tomorrow, Nov 21st 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-11-21-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

Resurrecting VMs with local volumes

Prajakta.Belgundi@...
 

Hello Bosh Team,

 

I have a question about an issue we are running into when deploying our application on bosh VMs.

 

This application needs to use local volumes for performance reasons and all volumes including the “root disk” are mounted on local disks.

We’re able run the application successfully.

However, when a VM does down (or we delete it to check DR), the bosh resurrector tries to bring it back up but this fails, because it is not able to mount back the local drives correctly.

 

Is VM resurrection is expected to work for VMs with local volumes, on bosh?

Is that supported? Is there a way to get this to work?

 

-Thanks,

Prajakta

 

Re: Resurrecting VMs with local volumes

Benjamin Gandon
 

Hi Prajakta,

Root disk in BOSH semantics are typically ephemeral storage (as well as the extra ephemeral storage that can be mounted on /var/vcap/data), as opposed to the persistent storage that can be mounted on /var/vcap/store.

If your underlying IaaS infrastructure (you didn’t mention which one it is) is supporting persistent storage backed by local volumes, then check your BOSH CPI documentation to verify if this feature is supported.

You can find more information at https://bosh.io/docs/persistent-disks/

Best,
/Benjamin GANDON


Le 29 nov. 2019 à 07:43, Prajakta.Belgundi@... a écrit :

Hello Bosh Team,
 
I have a question about an issue we are running into when deploying our application on bosh VMs.
 
This application needs to use local volumes for performance reasons and all volumes including the “root disk” are mounted on local disks.
We’re able run the application successfully.
However, when a VM does down (or we delete it to check DR), the bosh resurrector tries to bring it back up but this fails, because it is not able to mount back the local drives correctly.
 
Is VM resurrection is expected to work for VMs with local volumes, on bosh?
Is that supported? Is there a way to get this to work?
 
-Thanks,
Prajakta
 

Upcoming changes to bosh-linux-stemcell-builder

Aakash Shah <ashah@...>
 

Hey all,
In an effort to have the bosh-linux-stemcell-builder be more maintainable for the bosh team, we are hoping to remove build targets not explicitly maintained by the bosh team. These include the following:

* OpenSuse
* PhotonOS
* Red Hat Enterprise Linux (RHEL)
* CentOS
* Ubuntu Trusty
* PowerPC

The work of removing support for these targets is currently happening on "wip/reduce-build-targets", with the goal of bringing it into the "master" branch. This only impacts forward development, and should not impact past branches. For any consumers of the above build targets, we'd love to hear from you in the #bosh-core-dev channel in Cloud Foundry slack.

We will continue cutting releases for ubuntu-xenial lines and centos 3763.x, per our standard support policy.

Context:
Feature work has been difficult on the bosh-linux-stemcell-builder repository as it's housed so much logic. Maintaining compatibility across all of the build targets has made stages (written in bash) very complicated. As we explore making bigger improvements to the builder, we're looking to lessen the builder's responsibility

- Aakash, bosh team