Date   

Re: [cf-dev] BOSH projects adopting distributed committer model

Shatarupa Nandi <snandi@...>
 

Dear Cloud Foundry Community,


We would like to address some feedback we received from last week’s email about changes to BOSH stemcell patching cadence. Low and medium CVEs in stemcells will be patched every 3 weeks, instead of the previously proposed cadence of every 6 weeks. We remain committed to supporting our OSS BOSH users for the foreseeable future and will address feedback as best as we can.


As a reminder, we are still seeking help from other members of the Cloud Foundry community to help with ongoing maintenance of the BOSH projects in the following ways:

  • Please help your friends in the community by answering questions on #bosh and other BOSH channels

  • If you would like to contribute to adding Bionic support and/or start publishing Bionic stemcells on bosh.io, we would welcome PRs and will be happy to work with you to review and merge them. If you are interested in forming an OSS team to build Bionic stemcells and add support for Bionic to Cloud Foundry components, please reach out to Marco Voelz or Shatarupa Nandi.

  • If you would like improvements in BOSH and/or the CPIs, please consider contributing the feature directly via PRs to the various repos

  • If you notice a buildup of features / fixes that warrant a release being cut, ping the team via cf-bosh@...

  • If you would like to be a Project Lead for any of these projects, please reach out to Shatarupa Nandi and/or Nadja Conklin.


Please reach out to Nadja Conklin and/or Shatarupa Nandi if you have any feedback or questions.


Thank you!


On Tue, Mar 31, 2020 at 4:44 PM Shatarupa Nandi <snandi@...> wrote:

Dear Cloud Foundry Community,


Over the last year, we have seen the industry shift towards deploying software on top of Kubernetes. As a result, we have all chosen to invest heavily in building on top of Kubernetes. Separately, we have also observed that BOSH has reached a point of stability and maturity, such that there aren’t lots of incoming feature requests and enhancements to add.


We continue to view BOSH as an important project and are still fully committed to supporting our OSS users using BOSH for the next couple years . However, in light of these changes, several BOSH PMC projects[1] will be shifting from the pairing model to the distributed committer model (for more information about distributed committer vs pairing models, see the CFF Development Operations Policy [2], section IV.B.). Shatarupa Nandi (snandi@..., @rupa on CFF Slack) and Nadja Conklin (nconklin@..., @Nadja Conklin on CFF Slack) will temporarily step in as Project Leads. 


We are moving away from having a full time team working on each of the projects. Instead, we will have 6-8 engineers who will dedicate a portion of their time on a regular basis for ongoing support and maintenance of the BOSH projects. This will likely result in the following changes:

  • A reduced cadence of cutting new stemcells and patching existing stemcells for low and medium severity CVEs. Presently, we aim to cut new stemcell patches every 2 weeks. We will now be doing the same every 6 weeks. We will maintain the status quo for high and critical CVEs and will patch those as soon as possible.

  • We will pause working on Bionic stemcells and will not be cutting a new line of Bionic stemcells. We are aware that Xenial stemcells are supported until April 2021. This is an area where we are seeking help from the CFF community. Please see the end of the email. We may pick up this work during the 2nd half of the year, depending on cf-for-k8s adoption and our level of staffing on BOSH.

  • A reduced cadence of new releases of BOSH PMC projects[1]. Since there will be little active development, we will move to cutting releases ad-hoc when there are enough changes built up.

  • We will pause active development on the various CPIs (including OpenStack CPI, Azure CPI, GCP CPI, and AWS CPI.) We will continue to patch critical bugs, backwards incompatible IaaS API changes, and high severity CVEs. However, we will not be adding features to extend the capabilities of the CPIs.

  • While we will continue to answer questions about BOSH, we will likely be less responsive than before. We still hope to answer questions on these Slack channels within a reasonable time. We will be most active in #bosh. Other BOSH Slack channels (for example, #bosh-core-dev) will see reduced activity and will be deprecated over time.

  • The committers are all on cf-bosh@..., and will continue to engage with the community of users and contributors via the mailing lists. 


We would like to seek help from other members of the Cloud Foundry community to help with ongoing maintenance of the BOSH projects. Here are some ways in which you can help us:

  • Please help your friends in the community by answering questions on #bosh

  • If you would like to contribute to adding Bionic support and/or start publishing Bionic stemcells on bosh.io, we would welcome PRs and will be happy to work with you to review and merge them. If you are interested in forming an OSS team to build Bionic stemcells and add support for Bionic to Cloud Foundry components, please reach out to Marco Voelz or Shatarupa Nandi.

  • If you would like improvements in BOSH and/or the CPIs, please consider contributing the feature directly via PRs to the various repos

  • If you notice a buildup of features / fixes that warrant a release being cut, ping the team via cf-bosh@...

  • If you would like to be a Project Lead for any of these projects, please reach out to Shatarupa Nandi and/or Nadja Conklin.


Thank you for your help and support!


[1] This includes the following repos: bosh, bosh-agent, bosh-dns-release, bosh-linux-stemcell-builder, bosh-deployment, bosh-cli, bbl, bosh.io github org, docs-bosh, bpm-release, bosh-google-cpi-release, bosh-azure-cpi-release, bosh-openstack-cpi-release, bosh-aws-cpi-release, bosh-lite, bosh-utils, bosh-s3cli, bosh-acceptance-tests, jumpbox-deployment, os-conf-release.


[2] https://www.cloudfoundry.org/wp-content/uploads/2017/01/CFF-DEV-OPS-POLICY.pdf


Re: Leadership Changes at the Cloud Foundry Foundation

Chip Childers
 

Quick follow up! I mistakenly stated that the AMA is on Thursday April 8th... which does not exist this year. The AMA is on Thursday April 9th. See you on Slack!

Chip Childers
Executive Director
Cloud Foundry Foundation


On Tue, Apr 7, 2020 at 9:10 AM Chip Childers <cchilders@...> wrote:

Cloud Foundry Community,


First and foremost, I truly hope that each of you is doing as well as can be expected in these extraordinary times.


As you may have seen, we announced a leadership change this morning. I am stepping into the role of Executive Director of the Cloud Foundry Foundation. Abby Kearns has accepted an executive role with another organization, to be announced. This is a very exciting opportunity for Abby, and all of us on the foundation’s staff and directors are extremely happy for her. Abby has been leading the foundation for several years through quite a bit of change in our project, our community, and the broader market. She’s not going far, but she will be missed.


We also announced that Paul Fazzone, SVP Tanzu R&D at VMware, has been elected to chair the board of directors. Paul has been a strong advocate and supporter of the foundation, having served as Treasurer for the foundation and as a director for several years now. Paul is taking over the role of chair from John Roese, who has been a steady hand from the organization’s inception. I am looking forward to working much more closely with Paul as we push the organization forward into the future. 


Our focus as a community has always been to make developers’ lives easier, and each of you has played a part in the long list of user success stories. Even today, as society grapples with the incredible challenge of a global pandemic, I am reminded of the incredible value of the work this community does. Organizations from around the world that have adopted Cloud Foundry are using it to respond in these trying times, each in their own way. National governments have used the Cloud Foundry platform to rapidly build, deploy and scale software that is helping their citizens get information and register for economic support. Countless corporations are using Cloud Foundry to both support their customers in new ways and do their part for the greater good. These responses have required actions measured in days and hours, not weeks and months. In short, this community’s efforts over the years have built something worthing being truly proud of.


This community is also one that has managed to continuously evolve the architecture of the platform through several major cycles of change. Today is no different, as we have come together on the shared mission of bringing the Cloud Foundry developer experience to Kubernetes clusters everywhere


As the ancient Greek philosopher, Heraclitus said, “Change is the only constant in life.” Our community embraces that way of thinking, both for the Cloud Foundry project itself and when considering how to continue to enhance the developer experience provided by the platform. Ultimately, the core Cloud Foundry function cf-push will remain well into the future, and its architecture will continue to evolve.


I’m sure many of you have questions about these changes, and I welcome the opportunity to answer them. Feel free to email me directly ( cchilders@... ), or join us for a slack-based AMA this Thursday, April 8th, from 8-10 AM PST on the Cloud Foundry community’s slack instance in the #cff-forum channel. I will be happy to discuss the transition, the future of the Foundation and respond to any comments or questions you may have.


-chip



Chip Childers
Executive Director
Cloud Foundry Foundation


Leadership Changes at the Cloud Foundry Foundation

Chip Childers
 

Cloud Foundry Community,


First and foremost, I truly hope that each of you is doing as well as can be expected in these extraordinary times.


As you may have seen, we announced a leadership change this morning. I am stepping into the role of Executive Director of the Cloud Foundry Foundation. Abby Kearns has accepted an executive role with another organization, to be announced. This is a very exciting opportunity for Abby, and all of us on the foundation’s staff and directors are extremely happy for her. Abby has been leading the foundation for several years through quite a bit of change in our project, our community, and the broader market. She’s not going far, but she will be missed.


We also announced that Paul Fazzone, SVP Tanzu R&D at VMware, has been elected to chair the board of directors. Paul has been a strong advocate and supporter of the foundation, having served as Treasurer for the foundation and as a director for several years now. Paul is taking over the role of chair from John Roese, who has been a steady hand from the organization’s inception. I am looking forward to working much more closely with Paul as we push the organization forward into the future. 


Our focus as a community has always been to make developers’ lives easier, and each of you has played a part in the long list of user success stories. Even today, as society grapples with the incredible challenge of a global pandemic, I am reminded of the incredible value of the work this community does. Organizations from around the world that have adopted Cloud Foundry are using it to respond in these trying times, each in their own way. National governments have used the Cloud Foundry platform to rapidly build, deploy and scale software that is helping their citizens get information and register for economic support. Countless corporations are using Cloud Foundry to both support their customers in new ways and do their part for the greater good. These responses have required actions measured in days and hours, not weeks and months. In short, this community’s efforts over the years have built something worthing being truly proud of.


This community is also one that has managed to continuously evolve the architecture of the platform through several major cycles of change. Today is no different, as we have come together on the shared mission of bringing the Cloud Foundry developer experience to Kubernetes clusters everywhere


As the ancient Greek philosopher, Heraclitus said, “Change is the only constant in life.” Our community embraces that way of thinking, both for the Cloud Foundry project itself and when considering how to continue to enhance the developer experience provided by the platform. Ultimately, the core Cloud Foundry function cf-push will remain well into the future, and its architecture will continue to evolve.


I’m sure many of you have questions about these changes, and I welcome the opportunity to answer them. Feel free to email me directly ( cchilders@... ), or join us for a slack-based AMA this Thursday, April 8th, from 8-10 AM PST on the Cloud Foundry community’s slack instance in the #cff-forum channel. I will be happy to discuss the transition, the future of the Foundation and respond to any comments or questions you may have.


-chip



Chip Childers
Executive Director
Cloud Foundry Foundation


Re: Stemcell Bump Cadence

Maya Rosecrance
 

I realized I beat Rupa to posting this information by only a few hours. If you have feedback on this change, please reach out on the other thread: https://lists.cloudfoundry.org/g/cf-bosh/message/2707 


CF Summit NA 2020: Announcing CFP Extension and Program Chairs

Swarna Podila <spodila@...>
 

Dear Community,
Given the circumstances, we felt that keeping the CFP open for a bit longer will be useful.  Please read this post [1] announcing program co-chairs and CFP extension.

Please do not hesitate to ask a question in #summit channel on CF slack or ping any of us at the Foundation directly.  Please stay healthy and safe. 

-
--
-- Swarna Podila
Senior Director, Community | Cloud Foundry Foundation
spodila@...
@skpodila


[cf-dev] BOSH projects adopting distributed committer model

Shatarupa Nandi <snandi@...>
 

Dear Cloud Foundry Community,


Over the last year, we have seen the industry shift towards deploying software on top of Kubernetes. As a result, we have all chosen to invest heavily in building on top of Kubernetes. Separately, we have also observed that BOSH has reached a point of stability and maturity, such that there aren’t lots of incoming feature requests and enhancements to add.


We continue to view BOSH as an important project and are still fully committed to supporting our OSS users using BOSH for the next couple years . However, in light of these changes, several BOSH PMC projects[1] will be shifting from the pairing model to the distributed committer model (for more information about distributed committer vs pairing models, see the CFF Development Operations Policy [2], section IV.B.). Shatarupa Nandi (snandi@..., @rupa on CFF Slack) and Nadja Conklin (nconklin@..., @Nadja Conklin on CFF Slack) will temporarily step in as Project Leads. 


We are moving away from having a full time team working on each of the projects. Instead, we will have 6-8 engineers who will dedicate a portion of their time on a regular basis for ongoing support and maintenance of the BOSH projects. This will likely result in the following changes:

  • A reduced cadence of cutting new stemcells and patching existing stemcells for low and medium severity CVEs. Presently, we aim to cut new stemcell patches every 2 weeks. We will now be doing the same every 6 weeks. We will maintain the status quo for high and critical CVEs and will patch those as soon as possible.

  • We will pause working on Bionic stemcells and will not be cutting a new line of Bionic stemcells. We are aware that Xenial stemcells are supported until April 2021. This is an area where we are seeking help from the CFF community. Please see the end of the email. We may pick up this work during the 2nd half of the year, depending on cf-for-k8s adoption and our level of staffing on BOSH.

  • A reduced cadence of new releases of BOSH PMC projects[1]. Since there will be little active development, we will move to cutting releases ad-hoc when there are enough changes built up.

  • We will pause active development on the various CPIs (including OpenStack CPI, Azure CPI, GCP CPI, and AWS CPI.) We will continue to patch critical bugs, backwards incompatible IaaS API changes, and high severity CVEs. However, we will not be adding features to extend the capabilities of the CPIs.

  • While we will continue to answer questions about BOSH, we will likely be less responsive than before. We still hope to answer questions on these Slack channels within a reasonable time. We will be most active in #bosh. Other BOSH Slack channels (for example, #bosh-core-dev) will see reduced activity and will be deprecated over time.

  • The committers are all on cf-bosh@..., and will continue to engage with the community of users and contributors via the mailing lists. 


We would like to seek help from other members of the Cloud Foundry community to help with ongoing maintenance of the BOSH projects. Here are some ways in which you can help us:

  • Please help your friends in the community by answering questions on #bosh

  • If you would like to contribute to adding Bionic support and/or start publishing Bionic stemcells on bosh.io, we would welcome PRs and will be happy to work with you to review and merge them. If you are interested in forming an OSS team to build Bionic stemcells and add support for Bionic to Cloud Foundry components, please reach out to Marco Voelz or Shatarupa Nandi.

  • If you would like improvements in BOSH and/or the CPIs, please consider contributing the feature directly via PRs to the various repos

  • If you notice a buildup of features / fixes that warrant a release being cut, ping the team via cf-bosh@...

  • If you would like to be a Project Lead for any of these projects, please reach out to Shatarupa Nandi and/or Nadja Conklin.


Thank you for your help and support!


[1] This includes the following repos: bosh, bosh-agent, bosh-dns-release, bosh-linux-stemcell-builder, bosh-deployment, bosh-cli, bbl, bosh.io github org, docs-bosh, bpm-release, bosh-google-cpi-release, bosh-azure-cpi-release, bosh-openstack-cpi-release, bosh-aws-cpi-release, bosh-lite, bosh-utils, bosh-s3cli, bosh-acceptance-tests, jumpbox-deployment, os-conf-release.


[2] https://www.cloudfoundry.org/wp-content/uploads/2017/01/CFF-DEV-OPS-POLICY.pdf


Stemcell Bump Cadence

Maya Rosecrance
 

Hello community,
In order to reduce engineering toil we're changing the periodic bump schedule of stemcells from every 2 weeks to every 6 weeks. Critical CVE's should still see a new stemcell patch created within a few days.
Bosh team


CFNASummit 2020: CFP Extended!

Swarna Podila <spodila@...>
 

Dear Cloud Foundry Community,
Please note that the deadline to submit your speaking proposals for Cloud Foundry Summit North America 2020 has been extended. 

Here is the new timeline:
CFP Deadline: 11:59pm (US Pacific) April 3, 2020
Schedule Announcement: April 22, 2020

You can find a more detailed timeline here [1].  Please also stay tuned to this page [2] as we post updates around the event plan, given the times we are in now.  If you have any questions, please drop me a note or post it on #summit on CF Slack.

During these times, if anyone wants informal community calls where we just hangout on zoom to socialize, please drop me a note here or on slack.

Please stay healthy.
Bleiben Sie gesund. 

-- 

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


Re: Statement from the Cloud Foundry Foundation regarding COVID-19

Marco Voelz
 

Thanks Chip!

 

I recently read https://deniseyu.io/2020/03/07/remote-collaboration.html written by Denise Yu and found it to be a very good collection of hardware, software, and process – in case someone is looking for some general advice on how to foster collaboration/pairing when working remote.

 

Everybody stay safe and healthy!

 

Warm regards

Marco

 

From: <cf-bosh@...> on behalf of Chip Childers <cchilders@...>
Reply to: "cf-bosh@..." <cf-bosh@...>
Date: Monday, 16. March 2020 at 17:55
Subject: [cf-bosh] Statement from the Cloud Foundry Foundation regarding COVID-19

 

To our community and members,

 

We recognize the global emergency caused by COVID-19 is impacting all of us. Our thoughts are with our community, members, friends, and colleagues as we approach this new challenge together. 

 

As many parts of the world are implementing social distancing and, in many cases, urging or even requiring citizens to stay at home, many of us are privileged to be able to work from home. Some of our project teams have significant experience working and pairing remotely. For those of you that are new to working from home, please reach out to the larger community for support and or best practices. If you have experience working remotely, we encourage you to share your best practices with others -- both in the community and more broadly (in the form of blog posts, podcasts, tweets). Now is the time for our community to show its support for each other in any way possible.

 

As we near our June 25th Cloud Foundry Summit North America, please know that we are actively monitoring the situation as it evolves and will be adjusting plans as necessary to ensure the safety and health of our community. As of today, we remain hopeful we will have the opportunity to come together in person. On Friday, we updated the event’s novel coronavirus update page. We will keep you updated on any future changes to the event plans, and remind everyone to continue to check for updates on that page. 

 

It is important to remember that each of us will experience the impact of this outbreak in different ways. Our community is a global network of individuals who genuinely care about each other. In this time of uncertainty, let us demonstrate that kindness to each other by remaining flexible and supportive - in the Cloud Foundry community and in your local community. Help where you can. Be patient, be safe, and remember to take care of yourself. We will all get through this together.

 

In the meantime, please don’t hesitate to reach out to us, at the Foundation, if there is anything we can do to better support you during this time.

 

 

Chip Childers, CTO

Cloud Foundry Foundation


Statement from the Cloud Foundry Foundation regarding COVID-19

Chip Childers
 

To our community and members,


We recognize the global emergency caused by COVID-19 is impacting all of us. Our thoughts are with our community, members, friends, and colleagues as we approach this new challenge together. 


As many parts of the world are implementing social distancing and, in many cases, urging or even requiring citizens to stay at home, many of us are privileged to be able to work from home. Some of our project teams have significant experience working and pairing remotely. For those of you that are new to working from home, please reach out to the larger community for support and or best practices. If you have experience working remotely, we encourage you to share your best practices with others -- both in the community and more broadly (in the form of blog posts, podcasts, tweets). Now is the time for our community to show its support for each other in any way possible.


As we near our June 25th Cloud Foundry Summit North America, please know that we are actively monitoring the situation as it evolves and will be adjusting plans as necessary to ensure the safety and health of our community. As of today, we remain hopeful we will have the opportunity to come together in person. On Friday, we updated the event’s novel coronavirus update page. We will keep you updated on any future changes to the event plans, and remind everyone to continue to check for updates on that page. 


It is important to remember that each of us will experience the impact of this outbreak in different ways. Our community is a global network of individuals who genuinely care about each other. In this time of uncertainty, let us demonstrate that kindness to each other by remaining flexible and supportive - in the Cloud Foundry community and in your local community. Help where you can. Be patient, be safe, and remember to take care of yourself. We will all get through this together.


In the meantime, please don’t hesitate to reach out to us, at the Foundation, if there is anything we can do to better support you during this time.



Chip Childers, CTO
Cloud Foundry Foundation


Re: Not able to list the teams in concourse, using API /api/v1/teams

arutsudar.a95@...
 

Hi Daniel,

Thank you for your suggestions.

Regards,
Arutsudar


BOSH OpenStack CPI maintenance

Riegger, Felix
 

Dear Friends of OpenStack,

 

SAP announced in August 2019 [1] to stop the maintenance of the BOSH OpenStack CPI and related projects by the end of 2019. Pivotal/VMware jumped in to take over the maintenance of the CPI. The handover has been completed and Pivotal/VMware now officially maintains the BOSH OpenStack CPI [2]. To get support please reach out to #bosh [6] or #bosh-core-dev [7] Slack channels.

 

The CF OpenStack validator [3] and bosh-openstack-environment-templates [4] are now unmaintained and will be moved to the cloudfoundy-attic [5] organization after a short grace period.

 

Kind regards,

Morgan and Felix

 

 

[1] https://lists.cloudfoundry.org/g/cf-bosh/message/2651

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

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

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

[5] https://github.com/cloudfoundry-attic/

[6] https://cloudfoundry.slack.com/archives/C02HPPYQ2

[7] https://cloudfoundry.slack.com/archives/C094QRLEQ


Cloud Foundry Community Workroom at Kubecon/CloudnativeCon EU 2020

Swarna Podila <spodila@...>
 

Dear Cloud Foundry Community,
For those of you attending Kubecon/CloudnativeCon EU 2020, please note that F002/F003 room is available for the cloud foundry community.  This is to foster the cross-community collaboration onsite.

This room is an "open-for-cf-community" workroom with no prior reservation required.  This room will be equipped with tables and chairs along with a whiteboard and some markers.  

Please do not hesitate to reach out to me (prior to the event) or the events team onsite, if you have any questions.

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


[cf-dev] Call for Help with Vulnerability Management for CFF projects

Swarna Podila <spodila@...>
 

For those of you who are not on cf-dev mailing list.

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


---------- Forwarded message ---------
From: Dieu Cao <dcao@...>
Date: Wed, Feb 26, 2020 at 11:42 AM
Subject: [cf-dev] Call for Help with Vulnerability Management for CFF projects
To: cf-dev <cf-dev@...>


All,

The CF community is looking for a handful of volunteers to help reconstitute a multi-member vulnerability management team for CFF projects. Recently, the task has fallen to the Pivotal/VMware security team alone. However, the whole community has a stake in this process.

We're looking for individuals that either: (1) have past experience managing security reports responsibly within either a commercial or open source setting, or (2) are willing and capable of learning by doing. One of the keys to success here will be for the volunteers to have a true sense of being responsible for this process.

Don't worry if you're not a security expert. You do have to be willing to spend a few hours a week helping manage the process.

If interested, reply here or contact me directly. Once we get a reasonable group of volunteers, we'll setup the appropriate meetings to get started.

Thanks,
Dieu Cao
CFF PMC Council Chair


Re: Not able to list the teams in concourse, using API /api/v1/teams

Daniel Jones
 

Hi Aratsudar,

A better place to look for help would be the Concourse forums: https://discuss.concourse-ci.org/

You may also like to consider Control Tower if you want a simpler way to deploy Concourse via BOSH: https://github.com/EngineerBetter/control-tower

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


On Wed, 19 Feb 2020 at 08:49, <arutsudar.a95@...> wrote:

I am using concourse v4.2.1 deployed using bosh on AWS.

When I hit the API endpoint /api/v1/info (in Postman, with Basic auth), I am able to get the response as below

{
    "version": "4.2.1",
    "worker_version": "2.1"
}

When I try to hit the API endpoint /api/v1/teams (in Postman, with Basic auth), I am getting Status 200 OK with an empty response like below.

[]

I am able to see the teams using fly command or also in the web UI, but not through API.

  • Should I enable basic authentication for hitting API endpoints of concourse?
  • Why am I not able to list the teams in concourse using the API /api/v1/teams? What am I missing?


Additional Info:

Referred to this concourse-bosh-deployment github repo for deploying concourse.

The sample command used to deploy concourse is given below:

bosh -e boshconcoursedir deploy -d boshconcourse concourse.yml \
  -l ../versions.yml \
  --vars-store cluster-creds.yml  \
  -o operations/static-web.yml  \
  --var web_ip=<<REDACTED>>   \
  --var network_name=default  \
  --var web_vm_type=<<REDACTED>>  \
  --var db_vm_type=<<REDACTED>>   \
  --var db_persistent_disk_type=<<REDACTED>> \
   --var worker_vm_type=<<REDACTED>> \
    --var deployment_name=boshconcourse \
    --var external_url=https://<<REDACTED>> \
    -o operations/add-local-users.yml \
    --var main_team_local_users=[admin] \
    --var add_local_users=[admin:<<REDACTED>>,myid@...:<<REDACTED>>]

Today I added the below line to the deployment command and deployed again, and still failed to get the teams from the API

  -o operations/basic-auth.yml \

After logging in as admin in fly, I am able to list the teams as below.

fly -t admin login -c https://something.com -u admin -p <<REDACTED>>
logging in to team 'main'


target saved

fly -t admin teams
name
team-1 
team-2
main 

I am not sure if this is the right place to ask this issue. Sorry if it is not. (Also posted a similar question in StackOverflow). Kindly assist me in resolving this issue.

Regards,
Arut


Re: BOSH PMC meeting series cancelled

Marco Voelz
 

Re sending this


From: Voelz, Marco <marco.voelz@...>
Sent: Wednesday, February 19, 2020 9:49:09 AM
To: cf-bosh@... <cf-bosh@...>
Subject: BOSH PMC meeting series cancelled
 

Dear friends of BOSH,

 

I just cancelled the series of BOSH PMC meetings due to inactivity. I have updated the CFF calendar accordingly and deleted the event.

If there's a topic you'd like to discuss around BOSH, please drop in #bosh on slack, write a mail to this list or to me personally.

 

Warm regards

Marco

 


BOSH PMC meeting series cancelled

Marco Voelz
 

Dear friends of BOSH,

 

I just cancelled the series of BOSH PMC meetings due to inactivity. I have updated the CFF calendar accordingly and deleted the event.

If there's a topic you'd like to discuss around BOSH, please drop in #bosh on slack, write a mail to this list or to me personally.

 

Warm regards

Marco

 


Re: Deprecating global compiled package cache

Marco Voelz
 

Dear Maya,

 

From my point of view the removal certainly makes sense. The global compiled package cache has severe issues, which to my knowledge have never been fixed [1,2,3]. I'd be interested in existing use-cases that people have for this, but my assumption is this feature doesn't live up to the expectations we had back in 2013 when it was added ;)

 

+1 for removing this, thanks for bringing this up!

 

Warm regards

Marco

 

[1] https://github.com/cloudfoundry/bosh/issues/1478

[2] https://github.com/cloudfoundry/bosh/issues/1300

[3] https://github.com/cloudfoundry/bosh/issues/1353

 

 

From: <cf-bosh@...> on behalf of Maya Rosecrance <mrosecrance@...>
Reply to: "cf-bosh@..." <cf-bosh@...>
Date: Tuesday, 18. February 2020 at 23:30
To: "cf-bosh@..." <cf-bosh@...>
Subject: [cf-bosh] Deprecating global compiled package cache

 

Hi Everyone,

I'm considering removing the global compiled package cache. It was a feature that made a lot of sense in a world before compiled releases where users with multiple directors wanted to only compile on one director then share that artifact with the others. Currently, when the BOSH director searches for a compiled package, it first searches the blobstore for any exact or fuzzy (for floating stemcell lines) compiled package matches before checking the global package cache. My hope is that as more and more BOSH release authors have adopted compiled releases, the need for the global package cache has become minimal to none as most compiled packages have been 'pre-seeded' to the blobstore. 

 

For users still ingesting source releases, we've since made manual workarounds to avoid the compilation time hit. Namely anyone can export a release and upload that artifact to any number of directors.

 

Please reach out if you have any use cases that might be broken by this change.


Not able to list the teams in concourse, using API /api/v1/teams

arutsudar.a95@...
 

I am using concourse v4.2.1 deployed using bosh on AWS.

When I hit the API endpoint /api/v1/info (in Postman, with Basic auth), I am able to get the response as below

{
    "version": "4.2.1",
    "worker_version": "2.1"
}

When I try to hit the API endpoint /api/v1/teams (in Postman, with Basic auth), I am getting Status 200 OK with an empty response like below.

[]

I am able to see the teams using fly command or also in the web UI, but not through API.

  • Should I enable basic authentication for hitting API endpoints of concourse?
  • Why am I not able to list the teams in concourse using the API /api/v1/teams? What am I missing?


Additional Info:

Referred to this concourse-bosh-deployment github repo for deploying concourse.

The sample command used to deploy concourse is given below:

bosh -e boshconcoursedir deploy -d boshconcourse concourse.yml \
  -l ../versions.yml \
  --vars-store cluster-creds.yml  \
  -o operations/static-web.yml  \
  --var web_ip=<<REDACTED>>   \
  --var network_name=default  \
  --var web_vm_type=<<REDACTED>>  \
  --var db_vm_type=<<REDACTED>>   \
  --var db_persistent_disk_type=<<REDACTED>> \
   --var worker_vm_type=<<REDACTED>> \
    --var deployment_name=boshconcourse \
    --var external_url=https://<<REDACTED>> \
    -o operations/add-local-users.yml \
    --var main_team_local_users=[admin] \
    --var add_local_users=[admin:<<REDACTED>>,myid@...:<<REDACTED>>]

Today I added the below line to the deployment command and deployed again, and still failed to get the teams from the API

  -o operations/basic-auth.yml \

After logging in as admin in fly, I am able to list the teams as below.

fly -t admin login -c https://something.com -u admin -p <<REDACTED>>
logging in to team 'main'


target saved

fly -t admin teams
name
team-1 
team-2
main 

I am not sure if this is the right place to ask this issue. Sorry if it is not. (Also posted a similar question in StackOverflow). Kindly assist me in resolving this issue.

Regards,
Arut


Deprecating global compiled package cache

Maya Rosecrance
 

Hi Everyone,
I'm considering removing the global compiled package cache. It was a feature that made a lot of sense in a world before compiled releases where users with multiple directors wanted to only compile on one director then share that artifact with the others. Currently, when the BOSH director searches for a compiled package, it first searches the blobstore for any exact or fuzzy (for floating stemcell lines) compiled package matches before checking the global package cache. My hope is that as more and more BOSH release authors have adopted compiled releases, the need for the global package cache has become minimal to none as most compiled packages have been 'pre-seeded' to the blobstore. 

For users still ingesting source releases, we've since made manual workarounds to avoid the compilation time hit. Namely anyone can export a release and upload that artifact to any number of directors.

Please reach out if you have any use cases that might be broken by this change.

41 - 60 of 2752