Discussion about MicroBOSH release in every stemcell.

[Alexander Lomov]

Hey, all.

For a long time I meet incomprehension at the fact that MicroBOSH release is build into stemcell. I know that there are clear reasons for it, but I always want to know if there are any plans to extract it to some other place. This is a slightly bit irrational thing to have MicroBOSH release in filesystem of every VM you deploy to a cloud. What do you think about it?

Thank you, 

Alex L. 

[Dr Nic Williams]

The new bosh-micro-cli will work differently. You can investigate it now though it's now formally released.

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

[Dmitriy Kalinin]

This will be solved by the new micro CLI since it requires user to provide cpi and bosh releases to install on the first VM. Once we publish this work it will be a matter of time when we start producing stemcells only when sec vulnerabilities and agent updates are needed. Exciting times and good question!

Sent from my iPhone

[Alexander Lomov]

Thank you for answer. Yes, I liked the way bosh-micro-cli works. 

But as far as I see it still relies on BOSH release that is build into stemcell. It takes bosh release as a parameter just to run BOSH components on the host where bosh-micro-cli command is run. So I don't think it is going to change things with stemcell.

------------------------

Alex Lomov

Altoros — Cloud Foundry deployment, training and integration

Twitter: @code1n GitHub: @allomov

[Dr Nic Williams]

The new bosh-micro doesn't even need to deploy bosh. Last night I took the community redis release and deployed it into a VM with bosh-micro 

What's required on the stemcell is the agent & micro.