Re: How CPI versions and modifications are deployed in the BOSH director
I suppose you use bosh-init  to deploy MicroBOSH . MicroBOSH is a
full functional BOSH installation in bounds of one instance, still has its
limitations. It is a common way to deploy MicroBOSH first and to use it to
deploy full functional BOSH cluster. After this, you can use MicroBOSH to
manage BOSH cluster, to update its CPI and another components. This BOSH
cluster is used to deploy and manage CF.
As far as I know bosh-init is not yet able to perform "smart" re-deploys,
where it updates only packages that have newer versions.
When you run `bosh releases` you see release that are uploaded to MicroBOSH
instance blobstore, not actual releases that was used to deploy MicroBOSH.
The version of release that runs inside MicroBOSH is the same version that
you specified in the manifest file that you used to deploy MicroBOSH.
Talking about questions:
a) yes, release version is specified by manifest file that you used to
deploy MicroBOSH. `bosh upload release` provides MicroBOSH with releases
that will be used lately by deployments performed by MicroBOSH. You can
define link to release in manifest file, but still this release will be
uploaded. `bosh upload release` was used before you can put link to release
into manifest file and makes it possible to perform this operation manually.
b) the easiest way is to re-deploy. Another option is to change config
files inside of MicroBOSH director manually and restart it.
*Altoros* — Cloud Foundry deployment, training and integration
*Twitter:* @code1n <https://twitter.com/code1n> *GitHub:* @allomov
On Thu, Jul 9, 2015 at 8:06 PM, Daniele Santoro <