Question about bosh-lite, bosh-init and microbosh

[王天青]

Hi all,

I'm a new guy to bosh. I'm a little confused about the relationship of bosh-lite, bosh-init and microbosh (is microbosh renamed to bosh-init), could someone explain a little bit to me?

For example, I want to deploy a Diego CF/Lattice on OpenStack JUNO environment, I need to download Diego release (https://github.com/cloudfoundry-incubator/diego-release), stemcell and create a manifest, then what should I do? 

Thanks.

[James Bayer]

bosh-init is the new name for the "bosh micro plugin". it's a cli tool that let's you install a single VM bosh release somewhere. the standard reason to use this is to deploy microbosh.

microbosh is a single VM installation of BOSH.

bosh-lite is a single VM installation of BOSH that creates containers in place of VMs on an iaas. it's typically used for development purposes because it's much faster to create and manage containers than VMs.

if your goal is to deploy lattice on openstack juno for development and evaluation use cases, then i would start by looking at the lattice Vagrantfile [1] and performing similar steps on an Ubuntu Trusty VM on Openstack.

if you want a production grade lattice environment with BOSH, then you'll need to deploy both cf-release and diego-release components co-located in a single deployment. this is an advanced bosh use case and i'd recommend starting with simpler BOSH scenarios first, like deploying redis with bosh [2].

[1] https://github.com/cloudfoundry-incubator/lattice/blob/master/Vagrantfile

[2] https://github.com/cloudfoundry-community/redis-boshrelease

To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+...@cloudfoundry.org.

--

Thank you,

James Bayer

[王天青]

Thanks James, I will try the easier one before jumping to the battlefield :)

James Bayer <jba...@pivotal.io>于2015年4月21日周二 上午4:11写道：