Date   
CF BOSH PMC: BOSH Core Europe Call for Nominations

Marco Voelz
 

Dear Friends of BOSH,


I'm rotating into a different role within SAP, which means I'm stepping down from the BOSH Core Europe PM position.

Therefore, the BOSH Core Europe team operating out of Walldorf, Germany, has an opening for its PM. Please send nominations directly to me or in reply to this message no later than 23:59 GMT on Thursday, December 20, 2018.


At the same time, I'd like to stay as BOSH PMC lead. A big part of my new role at SAP is concerned with defining and shaping an opinion about the future of BOSH, which should fit nicely to the PMC lead position. If you have any concerns about this, please don't hesitate to contact me.


If you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know.

Thanks and warm regards
Marco


Re: [CAUTION] [cf-bosh] CF BOSH PMC: BOSH Core Europe Call for Nominations

Marco Voelz
 

Dear Friends of BOSH,

 

SAP is nominating Felix Riegger as PM for the BOSH Europe Team. Felix has been a developer in the team since 2015 and has been pairing with me for the last few weeks to guarantee a smooth transitioning.

 

Please send any other nominations directly to me or in reply to this message no later than 23:59 GMT on Thursday, December 20, 2018.

 

Warm regards

Marco

 

From: <cf-bosh@...> on behalf of Marco Voelz <marco.voelz@...>
Reply-To: "cf-bosh@..." <cf-bosh@...>
Date: Friday, 14. December 2018 at 14:31
To: "cf-bosh@..." <cf-bosh@...>, "Discussions about Cloud Foundry projects and the system overall." <cf-dev@...>
Subject: [CAUTION] [cf-bosh] CF BOSH PMC: BOSH Core Europe Call for Nominations

 

Dear Friends of BOSH,

 

I'm rotating into a different role within SAP, which means I'm stepping down from the BOSH Core Europe PM position.

Therefore, the BOSH Core Europe team operating out of Walldorf, Germany, has an opening for its PM. Please send nominations directly to me or in reply to this message no later than 23:59 GMT on Thursday, December 20, 2018.

 

At the same time, I'd like to stay as BOSH PMC lead. A big part of my new role at SAP is concerned with defining and shaping an opinion about the future of BOSH, which should fit nicely to the PMC lead position. If you have any concerns about this, please don't hesitate to contact me.

 

If you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know.

 

Thanks and warm regards

Marco

 

 

BOSH vision and strategy

Frédéric Desbiens
 

 

Hi BOSH community!


When Marco, Morgan and myself started in our roles in the BOSH project management committee (PMC), one of our primary objectives was to give the community more visibility into our roadmap. It took us a bit more time than expected, but we finally put together a document that explains our vision and strategy for BOSH. It is my pleasure to finally share it with you today. You can access it here: https://docs.google.com/document/d/1pa-d7aC707dK9vvZUYIu9iytYzM9oM8YK-0M4vTp1rA/edit?usp=sharing


By making this document public, we hope to start a conversation with you. We wish to make sure we are building the right features for our users. This will be impossible without your comments and suggestions. Please let us know what you think.  


Priorities evolve over time. A roadmap is never set in stone; we want to evolve ours according to your feedback. We aim to publish new versions of the document on a regular basis to let you know where we are headed.


Thank you for reading this, and for being a part of the BOSH community!


Best Regards,  


Frédéric Desbiens

Product Manager

Project Lead, BOSH Core Toronto project


Re: BOSH vision and strategy

Mike Youngstrom
 

I think this looks great.  Nice work!  +1 for IPv6 support.  Getting iIPv6 into bosh will hopefully help bubble support for that up the stack and into CF.

Mike



On Wed, Dec 19, 2018 at 6:15 AM Frédéric Desbiens <fdesbiens@...> wrote:
 

Hi BOSH community!


When Marco, Morgan and myself started in our roles in the BOSH project management committee (PMC), one of our primary objectives was to give the community more visibility into our roadmap. It took us a bit more time than expected, but we finally put together a document that explains our vision and strategy for BOSH. It is my pleasure to finally share it with you today. You can access it here: https://docs.google.com/document/d/1pa-d7aC707dK9vvZUYIu9iytYzM9oM8YK-0M4vTp1rA/edit?usp=sharing


By making this document public, we hope to start a conversation with you. We wish to make sure we are building the right features for our users. This will be impossible without your comments and suggestions. Please let us know what you think.  


Priorities evolve over time. A roadmap is never set in stone; we want to evolve ours according to your feedback. We aim to publish new versions of the document on a regular basis to let you know where we are headed.


Thank you for reading this, and for being a part of the BOSH community!


Best Regards,  


Frédéric Desbiens

Product Manager

Project Lead, BOSH Core Toronto project


Moving BPM out of Incubation

Christopher Brown
 

Hi everyone,

We'd like to propose moving the BPM project from the incubator into general availability during the next BOSH PMC meeting. 

bpm-release version 1.0 was released in November last year and is being used by many releases to provide a consistent and isolated sandbox environment for BOSH jobs.

What do you think?

Thanks,
Christopher

Unconference in Philadelphia - Talks Please!

Daniel Jones
 

Hi lovely CF peeps,

We're seeking short talk proposals for the CF Summit NA 2019 Unconference. If you've got something cool, off-the-wall, or maybe that didn't quite fit the main conference criteria, then please make a proposal! 

We want to have a couple of scheduled talks so that potential attendees have some certainty about what knowledge will be imparted upon them. Other than that, we'll be allowing plenty of time for open space discussions (more than in Basel!).

In Basel last year a whopping 20% of all summit attendees came to the Unconference, so it's a great opportunity to engage your peers in conversation and learn from each other. Whilst SAP are already sponsors, we're looking for more - so if you want a way to reach a large portion of the summit audience directly, please get in touch.

We're also bringing the Cloud Foundry Pub Quiz to North America for the first time - expect beer, rubbish jokes, obscure trivia, and lively debates about whether the questions make sense!



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

Re: Unconference in Philadelphia - Talks Please!

Dr Nic Williams
 

Hurray for the Unconference!

Nic

 


From: cf-bosh@... on behalf of Daniel Jones <daniel.jones@...>
Sent: Thursday, January 24, 2019 10:11 am
To: Discussions about Cloud Foundry projects and the system overall.; Discussions about the Cloud Foundry BOSH project.
Subject: [cf-bosh] Unconference in Philadelphia - Talks Please!
 
Hi lovely CF peeps,

We're seeking short talk proposals for the CF Summit NA 2019 Unconference. If you've got something cool, off-the-wall, or maybe that didn't quite fit the main conference criteria, then please make a proposal! 

We want to have a couple of scheduled talks so that potential attendees have some certainty about what knowledge will be imparted upon them. Other than that, we'll be allowing plenty of time for open space discussions (more than in Basel!).

In Basel last year a whopping 20% of all summit attendees came to the Unconference, so it's a great opportunity to engage your peers in conversation and learn from each other. Whilst SAP are already sponsors, we're looking for more - so if you want a way to reach a large portion of the summit audience directly, please get in touch.

We're also bringing the Cloud Foundry Pub Quiz to North America for the first time - expect beer, rubbish jokes, obscure trivia, and lively debates about whether the questions make sense!



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

Re: Moving BPM out of Incubation

Marco Voelz
 

Dear Christopher,

 

Thanks for the proposal! Sorry for not following up on this sooner. A question which currently comes to my mind given the proposed transition to an 'active' project is: How active is BPM nowadays? What does the current BPM team look like and how much time do the team members spend on BPM?

 

I'll reach out to the individual PMC members and get their vote on the issue in the next week.

 

Thanks and warm regards

Marco

 

From: <cf-bosh@...> on behalf of Christopher Brown <cbrown@...>
Reply-To: "cf-bosh@..." <cf-bosh@...>
Date: Thursday, 17. January 2019 at 20:32
To: "Discussions about the Cloud Foundry BOSH project." <cf-bosh@...>
Cc: aram price <aprice@...>, James Myers <jmyers@...>
Subject: [cf-bosh] Moving BPM out of Incubation

 

Hi everyone,

 

We'd like to propose moving the BPM project from the incubator into general availability during the next BOSH PMC meeting. 

 

bpm-release version 1.0 was released in November last year and is being used by many releases to provide a consistent and isolated sandbox environment for BOSH jobs.

 

What do you think?

 

Thanks,

Christopher

Re: Moving BPM out of Incubation

Christopher Brown
 

I work on it 1-2 days per week. BPM v1 is pretty much feature complete and I anticipate that most of the work from now on will be refinements.

At some point we'll start seriously considering what the next steps for v2 are. At that point I expect the time spent on it and the feature work to ramp back up again.

Thanks and all the best,
Christopher

Reminder about our CoC and a change to the slack configuration

Chip Childers
 

All,

Over the weekend, there were several reports of inappropriate content being shared within the CF community's slack team in various channels. These messages have been removed and the accounts that posted them have been disabled.

We'd like to take this opportunity to remind everyone that we take breaches of our code of conduct very seriously. Our code of conduct can be found here: https://www.cloudfoundry.org/code-of-conduct/ 

While these occurrences were likely caused by people outside of our community taking advantage of the fact that our slack instance is open to everyone, it's important for community members to help ensure that we have a welcoming and inclusive environment.

If you see any inappropriate content posted to slack or have any code of conduct concerns, we ask that you reach out to the CFF via conduct@...We also ask that those that have administrative access to the slack team help with policing when / if they see something. If you do have administrative access and see inappropriate content, please help by (1) deleting the messages, (2) capturing a screenshot of the offending content and (3) notifying the CFF staff at conduct@....

Also note: due to reports of similar activity in other community slack teams having included tagging @channel and @here in postings of inappropriate content, we have disabled the use of those for non-admin users. This is to reduce the impact of any bad actor's actions.

Please reach out to me directly (cchilders@...) or the conduct@ email address if you have any questions or concerns.

Chip Childers, CTO
Cloud Foundry Foundation

Which OpenStack version is supported by Cloud Foundry?

R M
 

Folks,

I am trying to determine which version of OpenStack is supported by Cloud Foundry.  As per https://bosh.io/docs/init-openstack/ it mentions Liberty/Mikata/Newton as being supported and actively tested.  Does this still hold as all of the mentioned releases are EOL?

As per https://github.com/cloudfoundry/bosh-openstack-cpi-release#supported-openstack-versions - it mentions upstream OpenStack policy which seems to contradict with what is listed on bosh.io.

Thanks for any insight you can provide.


Re: Which OpenStack version is supported by Cloud Foundry?

Marco Voelz
 

Hey,

 

Thanks for pointing out that the docs at per https://bosh.io/docs/init-openstack/ are outdated. We will fix that hopefully soon and link to the correct documents.

The information at  https://github.com/cloudfoundry/bosh-openstack-cpi-release#supported-openstack-versions is correct: we test against the officially supported versions of OpenStack.

 

Let me know if you have further questions.

 

Warm regards

Marco

 

 

From: <cf-bosh@...> on behalf of R M <rishi.investigate@...>
Reply-To: "cf-bosh@..." <cf-bosh@...>
Date: Friday, 8. February 2019 at 23:31
To: "cf-bosh@..." <cf-bosh@...>
Subject: [cf-bosh] Which OpenStack version is supported by Cloud Foundry?

 

Folks,

 

I am trying to determine which version of OpenStack is supported by Cloud Foundry.  As per https://bosh.io/docs/init-openstack/ it mentions Liberty/Mikata/Newton as being supported and actively tested.  Does this still hold as all of the mentioned releases are EOL?

 

As per https://github.com/cloudfoundry/bosh-openstack-cpi-release#supported-openstack-versions - it mentions upstream OpenStack policy which seems to contradict with what is listed on bosh.io.

 

Thanks for any insight you can provide.

 

 

Can't renew bosh-director certificate

Jan-Henrik Christophersen
 

Hello all,

we failed to renew our director and mbus certificate before they expired and wanted to do that now by using the create-env command. I removed the "director_ssl" and "mbus_bootstrap_ssl" sections and used bosh int with the --vars-store flag to regenerate them. I've manually checked that the certificates are valid for another year.
To deploy this change, I ran the bosh create-env command but I am now running into this issue:

Command:
```
bosh create-env bosh-director/bosh.yml
    --state=xxx/state.json
    --vars-store=xxx/credentials.yml
    -o bosh-director/cpi.yml
    -v access_key_id=xxxxxxx
    -v secret_access_key=xxxxxxx
    -v director_name=bosh-director 
    -v director_instance_profile=xxx
    -v internal_cidr=10.118.132.0/24 
    -v internal_dns=10.118.128.2 
    -v internal_gw=10.118.132.1 
    -v internal_ip=10.118.132.9 
    -v subnet_id=subnet-04a2xxx
    -v region=eu-central-1 
    -v az=eu-central-1a 
    -v default_key_name=bosh
    -v default_security_groups=sg-e88axxx
    -v concourse_security_group=sg-679xxx
    -v concourse_elb=elb
    --ca-cert (interpolated ca cert) # tried with and without this parameter
    --var-file private_key=xxxxxxx.pem
```

Output:
```
Started validating
  Downloading release 'bosh'... Skipped [Found in local cache] (00:00:00)
  Validating release 'bosh'... Finished (00:00:00)
  Downloading release 'bosh-aws-cpi'... Skipped [Found in local cache] (00:00:00)
  Validating release 'bosh-aws-cpi'... Finished (00:00:00)
  Validating cpi release... Finished (00:00:00)
  Validating deployment manifest... Finished (00:00:00)
  Downloading stemcell... Skipped [Found in local cache] (00:00:00)
  Validating stemcell... Finished (00:00:00)
Finished validating (00:00:00)
 
Started installing CPI
  Compiling package 'ruby_aws_cpi/c6ba8a1e1b53b94ee9caf13d2d749c40cecfa038'... Finished (00:00:00)
  Compiling package 'bosh_aws_cpi/137cfc70652337ff1d3fca795e6d9ddd6e7e68dd'... Finished (00:00:00)
  Installing packages... Finished (00:00:01)
  Rendering job templates... Finished (00:00:00)
  Installing job 'aws_cpi'... Finished (00:00:00)
Finished installing CPI (00:00:02)
 
Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3421.9'... Skipped [Stemcell already uploaded] (00:00:00)
 
Started deploying
  Waiting for the agent on VM 'i-099931a2d9xxxxx'... Failed (00:00:00)
  Deleting VM 'i-099931a2d9xxxxx'... Finished (00:00:41)
  Creating VM for instance 'bosh/0' from stemcell 'ami-f7349398 light'... Finished (00:00:38)
  Waiting for the agent on VM 'i-07711bc8a06xxxxx' to be ready...
channel 2: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
...
 Failed (00:00:34)
Failed deploying (00:02:05)
 
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Deploying:
  Creating instance 'bosh/0':
    Waiting until instance is ready:
      Post https://mbus:<redacted>@10.118.132.9:6868/agent: x509: certificate has expired or is not yet valid
```

bosh-director/bosh.yml
```
---
name: bosh
 
releases:
- name: bosh
  version: "262.3"
  url: https://s3.amazonaws.com/bosh-compiled-release-tarballs/bosh-262.3-ubuntu-trusty-3421.9-20170706-183731-831697577-20170706183736.tgz?versionId=7GmwKfufgb5JwWhJ.cwIWLnejOtm2Hu4
  sha1: 1eae3f06282417e54ebb199656458f9d6c38e2af
 
resource_pools:
- name: vms
  network: default
  env:
    bosh:
      password: '*'
      mbus:
        cert: ((mbus_bootstrap_ssl))
 
disk_pools:
- name: disks
  disk_size: 32_768
 
networks:
- name: default
  type: manual
  subnets:
  - range: ((internal_cidr))
    gateway: ((internal_gw))
    static: [((internal_ip))]
    dns: [((internal_dns))]
 
instance_groups:
- name: bosh
  instances: 1
  jobs:
  - {name: nats, release: bosh}
  - {name: postgres-9.4, release: bosh}
  - {name: blobstore, release: bosh}
  - {name: director, release: bosh}
  - {name: health_monitor, release: bosh}
  resource_pool: vms
  persistent_disk_pool: disks
  networks:
  - name: default
    static_ips: [((internal_ip))]
  properties:
    nats:
      address: 127.0.0.1
      user: nats
      password: ((nats_password))
    postgres: &db
      listen_address: 127.0.0.1
      host: 127.0.0.1
      user: postgres
      password: ((postgres_password))
      database: bosh
      adapter: postgres
    blobstore:
      address: ((internal_ip))
      port: 25250
      provider: dav
      director:
        user: director
        password: ((blobstore_director_password))
      agent:
        user: agent
        password: ((blobstore_agent_password))
    director:
      address: 127.0.0.1
      name: ((director_name))
      db: *db
      flush_arp: true
      enable_post_deploy: true
      generate_vm_passwords: true
      enable_dedicated_status_worker: true
      enable_nats_delivered_templates: true
      workers: 4
      events:
        record_events: true
      ssl:
        key: ((director_ssl.private_key))
        cert: ((director_ssl.certificate))
      user_management:
        provider: local
        local:
          users:
          - name: admin
            password: ((admin_password))
          - name: hm
            password: ((hm_password))
    hm:
      director_account:
        user: hm
        password: ((hm_password))
        ca_cert: ((director_ssl.ca))
      resurrector_enabled: true
    ntp: &ntp
    - time1.google.com
    - time2.google.com
    - time3.google.com
    - time4.google.com
    agent:
      mbus: nats://nats:((nats_password))@((internal_ip)):4222
 
cloud_provider:
  mbus: https://mbus:((mbus_bootstrap_password))@((internal_ip)):6868
  cert: ((mbus_bootstrap_ssl))
  properties:
    agent: {mbus: "https://mbus:((mbus_bootstrap_password))@0.0.0.0:6868"}
    blobstore: {provider: local, path: /var/vcap/micro_bosh/data/cache}
    ntp: *ntp
 
variables:
- name: admin_password
  type: password
- name: blobstore_director_password
  type: password
- name: blobstore_agent_password
  type: password
- name: hm_password
  type: password
- name: mbus_bootstrap_password
  type: password
- name: nats_password
  type: password
- name: postgres_password
  type: password
- name: default_ca
  type: certificate
  options:
    is_ca: true
    common_name: ca
- name: mbus_bootstrap_ssl
  type: certificate
  options:
    ca: default_ca
    common_name: ((internal_ip))
    alternative_names: [((internal_ip))]
- name: director_ssl
  type: certificate
  options:
    ca: default_ca
    common_name: ((internal_ip))
    alternative_names: [((internal_ip))]
```

Can anyone point out what I am doing wrong here? I only have limited experience with bosh and didn't have to regenerate certificates before. The person who originally deployed this is also not around.

Thanks,
Jan

Re: Can't renew bosh-director certificate

Jan-Henrik Christophersen
 

Turns out I didn't regenerate the "default_ca". After regenerating all of them the deployment worked. I'll leave this up hoping it will help someone else if they encounter this.

upload custom windows stemcell issue

Atil Sensalduz
 

Hi folks,

When I was trying upload custom windows server 2012R2 stemcell I got the error like this: image-tar: disk1.vmdk: wrote only 7680 of 10240 bytes.
My stemcell tar file size is 12 GB. I have increased client_mac_body_size in the ngnx.conf and blobstore.conf at the director. Which did I stick in the limitation?

best regards

Re: upload custom windows stemcell issue

Danny Berger
 

Hi,

Without seeing the full error message, you may want to start by making sure that the ephemeral disk of your director is sufficiently large enough to receive the large stemcell file (+ some overhead, and it might store an additional copy of the image on disk while it's processing).

If increasing the size of ephemeral disk doesn't help, can you please provide the full error message that you're seeing?

Danny


On Sun, Feb 17, 2019 at 10:54 AM Atil Sensalduz <atil.sensalduz@...> wrote:
Hi folks,

When I was trying upload custom windows server 2012R2 stemcell I got the error like this: image-tar: disk1.vmdk: wrote only 7680 of 10240 bytes.
My stemcell tar file size is 12 GB. I have increased client_mac_body_size in the ngnx.conf and blobstore.conf at the director. Which did I stick in the limitation?

best regards



--
Danny Berger

Seeking Nominations: Community Awards

Swarna Podila
 

Dear Cloud Foundry Community,
It is that time of Summit again where we seek your help to nominate yourself or your peers for the Community Awards that will be presented at Cloud Foundry Summit in Philadelphia next month.

This year, the nomination categories are:
  • The Quiet Achiever
  • The Advocate
  • The Coolest User Story
More details on each of these categories can be found in this blog [1] and the nomination form can be found here [2].

Nominations close at 11:59 PM on March 14, 2019.  If you have any questions, please do not hesitate to contact me via email or slack.

Thank you,
Swarna.


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


Ask for CF Community Process of building light stemcell

"李冰(张嶷) <zhangyi.lb@...>
 

Dear BOSH team,


I am seeking for helps on how to get Alibaba Cloud Light Stemcell Builder and Stemcell CIs integrated with the CF community process of building light stemcells.

 

I have the following questions and sorry for asking them in one batch, so adding #number for easy tracking.

 

1)      Do we need a Cloud Foundry active project for AliCloud light stemcell builder in GitHub CF org, like this one https://github.com/cloudfoundry/bosh-aws-light-stemcell-builder? Or can we just use AliCloud light stemcell builder in Aliyun org, like this one https://github.com/aliyun/bosh-alicloud-light-stemcell-builder/tree/dev

 

2)      There is one step in Stemcell CI pipeline to upload full stemcell to an object storage bucket. In our case, we need to upload it to an AliCloud OSS bucket. The question is that who should be the owner of this OSS bucket. Is it owned by AliCloud BOSH team or CF Community? This is about how to fetch the Access Key (AK).

 

3)      After the step of light stemcell verification in Stemcell CI pipeline, if passed, it’s about to publish this light stemcell to S3 bucket then generate a meta4 file. For this S3 bucket, is it owned by CF Community?

 

4)      Once the meta4 file is generated, what is the process to update it into bosh.io/stemcells-cpi-index (https://github.com/bosh-io/stemcells-cpi-index)?

 

5)      At the end, AliCloud will make the custom image public available, however, there is a manual process sitting behind. Is it acceptable? If not, we’d better to know any best practices to automatically make a custom image public.

 

6)      Finally, how to publish light stemcell to bosh.io? Assume someone from CF community will make it happen, right?


Thanks for your time and looking forward to your feedback.


李冰(Bing LI)

电话:+86 13691202002

邮箱:zhangyi.lb@alibaba-inc.com


Two questions about BOSH CPI Certification

"李冰(张嶷) <zhangyi.lb@...>
 

Dear BOSH team.


I have another topic about BOSH CPI Certification. We aim to get Alibaba Cloud BOSH CPI passed BOSH CPI Certification (https://github.com/cloudfoundry-incubator/bosh-cpi-certification). Now we are still in development, but assume very soon we will submit a PR to include Alibaba Cloud directory into this repo, and corresponding pipeline yml file and CI tasks will be there.


Now, I have two questions regarding the integration process.

 

1)      At the beginning of certification, CI will run Terraform to build network environment. The question is about who owns the IaaS infrastructure, saying Alibaba Cloud BOSH team will own the account or CF community should own the account

 

2)      Per our understanding, a new CPI release (bosh-cpi-release) will trigger BOSH CPI Certification CI. If CI failed, what is the follow up procedures to get CPI release roll-back or be fixed?


Thank you in advance.


李冰(Bing LI)

电话:+86 13691202002

邮箱:zhangyi.lb@alibaba-inc.com


Announcement: Regular BOSH PMC meetings

Marco Voelz
 

[cross-posting lists for visibility]

 

Dear Friends of BOSH,

 

We are about to have our first BOSH PMC meeting!

 

When?

Thursday, March 21st, 8AM Pacific Time

Afterwards: Every third Thursday of the month in the same timeslot.

 

Where?

http://zoom.bosh.io

 

What is this all about?

Similarly to the existing PMC meetings, the BOSH PMC meeting is for announcements, updates, and outlook for all active projects within the BOSH PMC [1]. After a meeting, you can find the meeting minutes in pmc-notes/bosh on github [2]. If you want to see topics discussed at the meeting, we appreciate a heads-up a few days before the meeting, either via mail on cf-bosh@... or by making a pull request to the agenda document.

 

According to the Cloud Foundry Foundation's Governance documents, all companies with at least one full-time contributor on an active project get a vote to be issued by a representative. Others can join, but not vote on decisions, such as incubating new projects or promoting a project from incubation to active.

For more information on the organization within a Cloud Foundry PMC, please refer to the official Cloud Foundry Foundation Governance Documents [3].

 

Warm regards

Marco

 

[1] https://docs.google.com/a/pivotal.io/spreadsheets/d/1hg0EA3aB9wiCq8SgCU90ft4qrHvczsUjK0W_31APWxM

[2] https://github.com/cloudfoundry/pmc-notes/tree/master/Bosh

[3] https://www.cloudfoundry.org/wp-content/uploads/2015/09/CFF_Development_Governance.pdf