BOSH.next - 2012-05

[skaar]

BOSH.next - 2012-05

What is the BOSH team on to next?

- Release Composition: We want to be able to re-use jobs and packages across
releases and use different releases in the same deployment manifest.

- Job Co-Location: BOSH currently mandates one Job per VM, which makes sense
where you have few contraints on how you use IaaS resources. We know from the
AWS CPI that the IaaS might have limitations such that it is better to
co-locate some jobs in a single VM (e.g. a normal AWS account supports 20 VMs,
where the current CloudFoundry release at a minimum uses 40+ VMs)i.

- Disk handling: Early stage design and initial implementation of some
improvements to how we handle disks in BOSH. We have candidate areas, such as
support for different disk flavors (e.g. FC vs SATA drives), support for
multiple persistent disks, possible use of LVM. We expect to work on some
subset of this in the immediate future.

- We will continue to support community efforts, such as the OpenStack CPI
coming out of Piston (https://github.com/piston/openstack-bosh-cpi.git) and
other initiatives.

If you have any questions, please let us know. We will do our best to
send planning
notes like this every so often to keep everyone up to date.

Thanks,
The BOSH Team

[Dr Nic Williams]

Thanks skaar & co!

Cheers
Nic


Dr Nic Williams - VP Developer Evangelism
Engine Yard
The Leading Platform as a Service
Mobile: +1 415 860 2185
Skype: nicwilliams
Twitter: @drnic

[ferdy]

Thanks for sharing with us your planning notes!

- Ferdy