From: "Chris Clark" <cclark@...>
To: cf-bosh@...
Cc: "cf-dev@..." <cf-dev@...>
Date: 20/12/2019 18:57
Subject: [EXTERNAL] Re: [cf-dev] [cf-bosh] Project Quarks CF Operator 1.0
Sent by: cf-dev@...
Congrats Vlad and the rest of the Quarks team! That's great news.
On Fri, Dec 20, 2019 at 9:45 AM Vlad Iovanov <VIovanov@...> wrote:
Hello everyone,
On behalf of the Quarks team, I'd like to introduce Cloud Foundry Operator v1.0.0.
https://github.com/cloudfoundry-incubator/cf-operator/releases/tag/v1.0.0
This is our first stable release. Feedback is most welcome.
Please stay tuned for a corresponding Kube CF release.
Many thanks to everyone that's been testing and working with us to make this happen.
Beginning of next year, we’re planning to improve docs, publish some tutorials and use some of the new features in Kube CF.
Happy holidays!
Thanks,
The Quarks team
--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation
And here’s a blog post to save the date!
https://www.cloudfoundry.org/blog/where-in-the-world-are-cloud-foundry-summits-2020/
As a reminder: the Cloud Foundry Foundation is closed for the holidays from Monday December 23 to Friday January 3. We wish you all a restful, happy, healthy holiday time filled with love and peace. Talk to you all in January!
-- Swarna Podila (she/her)
Senior Director, Community | Cloud Foundry Foundation
You can read more about pronouns here, or please ask if you'd like to find out more.
From: "cf-dev@..." <cf-dev@...> on behalf of "Swarna Podila via Lists.Cloudfoundry.Org" <spodila=cloudfoundry.org@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Monday, December 16, 2019 at 10:06 AM
To: cf-dev <cf-dev@...>, cf-bosh <cf-bosh@...>
Subject: [cf-dev] FW: From the Desk of the Executive Director - December 2019
Hi Everyone,
As Abby shared in the update from “Desk of the Executive Director” here, Cloud Foundry Summits in 2020 will be slightly different.
Cloud Foundry Summits in 2020 will be collocated with Open Source Summit in North America (Austin, TX in June) and Europe (Dublin, Ireland in October) and will be hosted as a one-day event at both of these locations. The Summits will have breakout sessions, Diversity Luncheon, User Day, and Contributor Summit. Please stay tuned for additional details (CFP, registration, sponsorship, unconference, etc.).
If your organization is a Cloud Foundry Foundation member, you can join the AMA call tomorrow (Dec 17 at 8AM US Pacific; see zoom info in Abby’s email below) and get any/all of your Summit-related question answered. If you would like to submit a question prior to the call, please do so here. We will make sure your question is answered.
If you have any questions, please do not hesitate to reach out to us via email or slack.
-- Swarna Podila (she/her)
Senior Director, Community | Cloud Foundry Foundation
You can read more about pronouns here, or please ask if you'd like to find out more.
From: "Abby Kearns, Executive Director Cloud Foundry" <akearns@...>
Reply-To: "Abby Kearns, Executive Director Cloud Foundry" <akearns@...>
Date: Monday, December 16, 2019 at 6:59 AM
To: "spodila@..." <spodila@...>
Subject: From the Desk of the Executive Director - December 2019
Foundation updates from Executive Director Abby Kearns
|
|
Hello everyone,
On behalf of the Quarks team, I'd like to introduce Cloud Foundry Operator v1.0.0.
https://github.com/cloudfoundry-incubator/cf-operator/releases/tag/v1.0.0
This is our first stable release. Feedback is most welcome.
Please stay tuned for a corresponding Kube CF release.
Many thanks to everyone that's been testing and working with us to make this happen.
Beginning of next year, we’re planning to improve docs, publish some tutorials and use some of the new features in Kube CF.
Happy holidays!
Thanks,
The Quarks team
Hello everyone,
On behalf of the Quarks team, I'd like to introduce Cloud Foundry Operator v1.0.0.
https://github.com/cloudfoundry-incubator/cf-operator/releases/tag/v1.0.0
This is our first stable release. Feedback is most welcome.
Please stay tuned for a corresponding Kube CF release.
Many thanks to everyone that's been testing and working with us to make this happen.
Beginning of next year, we’re planning to improve docs, publish some tutorials and use some of the new features in Kube CF.
Happy holidays!
Thanks,
The Quarks team
Dear friends of BOSH,
I just cancelled the BOSH PMC meeting for December, which was originally scheduled on December 19th. I have updated the CFF calendar accordingly and deleted the event.
Happy holidays to all of you and see you in 2020!
Warm regards
Marco
Hi Everyone,
As Abby shared in the update from “Desk of the Executive Director” here, Cloud Foundry Summits in 2020 will be slightly different.
Cloud Foundry Summits in 2020 will be collocated with Open Source Summit in North America (Austin, TX in June) and Europe (Dublin, Ireland in October) and will be hosted as a one-day event at both of these locations. The Summits will have breakout sessions, Diversity Luncheon, User Day, and Contributor Summit. Please stay tuned for additional details (CFP, registration, sponsorship, unconference, etc.).
If your organization is a Cloud Foundry Foundation member, you can join the AMA call tomorrow (Dec 17 at 8AM US Pacific; see zoom info in Abby’s email below) and get any/all of your Summit-related question answered. If you would like to submit a question prior to the call, please do so here. We will make sure your question is answered.
If you have any questions, please do not hesitate to reach out to us via email or slack.
-- Swarna Podila (she/her)
Senior Director, Community | Cloud Foundry Foundation
You can read more about pronouns here, or please ask if you'd like to find out more.
From: "Abby Kearns, Executive Director Cloud Foundry" <akearns@...>
Reply-To: "Abby Kearns, Executive Director Cloud Foundry" <akearns@...>
Date: Monday, December 16, 2019 at 6:59 AM
To: "spodila@..." <spodila@...>
Subject: From the Desk of the Executive Director - December 2019
Foundation updates from Executive Director Abby Kearns
We’re ending one chapter and beginning another soon: 2020 is not just a new year but a new decade. The Foundation will be closed December 23rd through January 5th, so please reach out to me or our team if you need anything beforehand. I wish you the most pleasant holiday season.
Cloud Foundry Events in 2020
In 2020, we will be revamping our events strategy to ensure we continue to meet the needs of our community. We are purposely limiting the size and scope of our Summits to better serve contributors and end users with content tailored to their specific needs.Cloud Foundry Summits will be one-day events co-located with Open Source Summits in North America and Europe to provide visibility and engagement with broader open source communities, including the larger Linux universe. These more intimate events will enable our committed community of contributors and end users to get together to foster collaboration, share best practices, and have lively discussions.
In addition to Summits, we will rely on our strong member and end user community to host Cloud Foundry Days around the world. We encourage Cloud Foundry Day organizers to reach out to enterprise developers who are not yet Cloud Foundry users and facilitate more opportunities for connection within our global community. We will be supporting this effort by rolling out an updated CF Days Kit in early 2020 to your marketing teams.
Members Only!
- Ask Me Anything: Our last AMA of 2019 is tomorrow, Tuesday, December 17th at 8:00 AM PST. Join my Zoom to discuss what the future holds for Cloud Foundry.
A Few Articles Worth Sharing
- Medium: 2020, Open Source is Driving the Future
- Dev Insider: Cloud Agnostic Software Development, Part 2 Resilience with Cloud Foundry
- JAXenter: Bringing cf push to Kubernetes Kubernetes backend Eirini hits 1.0 milestone
- Linux magazin: Survey among service provider cloud providers
- Manage It: An open source business model does not exist
- JDN: The open source economic model does not exist
- Programmez: Developers have more and more weight and we have to take them into account
Happy Holidays to all of you and see you in 2020!
Abby Kearns
Executive Director | Cloud Foundry Foundation
This email was sent to spodila@...
why did I get this? unsubscribe from this list update subscription preferences
Cloud Foundry · One Letterman Drive Building D · Suite D4700 · San Francisco, CA 94129 · USA
Hi Everyone,
As Abby shared in the update from “Desk of the Executive Director” here, Cloud Foundry Summits in 2020 will be slightly different.
Cloud Foundry Summits in 2020 will be collocated with Open Source Summit in North America (Austin, TX in June) and Europe (Dublin, Ireland in October) and will be hosted as a one-day event at both of these locations. The Summits will have breakout sessions, Diversity Luncheon, User Day, and Contributor Summit. Please stay tuned for additional details (CFP, registration, sponsorship, unconference, etc.).
If your organization is a Cloud Foundry Foundation member, you can join the AMA call tomorrow (Dec 17 at 8AM US Pacific; see zoom info in Abby’s email below) and get any/all of your Summit-related question answered. If you would like to submit a question prior to the call, please do so here. We will make sure your question is answered.
If you have any questions, please do not hesitate to reach out to us via email or slack.
-- Swarna Podila (she/her)
Senior Director, Community | Cloud Foundry Foundation
You can read more about pronouns here, or please ask if you'd like to find out more.
From: "Abby Kearns, Executive Director Cloud Foundry" <akearns@...>
Reply-To: "Abby Kearns, Executive Director Cloud Foundry" <akearns@...>
Date: Monday, December 16, 2019 at 6:59 AM
To: "spodila@..." <spodila@...>
Subject: From the Desk of the Executive Director - December 2019
Foundation updates from Executive Director Abby Kearns
|
|
------
dr.max
ibm ☁
silicon valley, ca
maximilien.org
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
/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
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
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.
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.
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
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/
[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
Can you help to check the message https://lists.cloudfoundry.org/g/cf-bosh/topic/32740528#2663 and https://lists.cloudfoundry.org/g/cf-bosh/topic/32740555#2661 ? Thanks in advance.
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 yetHi 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/releasesLet me know if you have any questions,JimOn 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 regardsGuimin, He
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 regardsGuimin, He