Re: Some details about CPI development

Guillaume Berche


Besides the great CPI V1 doc (for which I proposed refinements in [4]), I
notice you have planned a future page "Interactions between CPIs and BOSH
Agent" in the TOC.

I have few questions that might relate to this future page:

- In which cases should the cpi update the agent settings in the registry
(e.g. as AWS cpi is doing during create_vm [1]) w.r.t. letting bosh
director updating the registry from the returned cloud ids (as mentionned
into [2]) ?

- Examples of agent settings in [3] are great, where can the reference
specs/tests of the agent settings be found ? I wasn't able to spot them yet
in the bosh-agent repo. Are those settings called bootstrap settings and
saved into settings.json as mentionned into [5]? Same question for start up
settings (agent.json) which format seems different from bootstrap settings
( with ex in in [6] and [7].

Would it make sense to publish bosh-agent test result as a spec for the
agent settings (eg ginko verbose output), possibly in bosh ci (it seems to
only have test suite summary now [8])

- Where can be learned more about a bosh agent bootstraping typical process
(read agent.json bundled in the stemcell, then get an IP through dhcp, then
pull from meta-data server the agentid and registry, then pull complete
network config from remote bosh directory registry, then ready to receive
pings from director through ?), similar to [2] with more details ? In which
case is an ssh tunnel to serve the config registry to the agent is
necessary (is that limited to the deprecated micro-bosh mechanism ?)

Thanks again,


[2] "example component
interaction" section

On Mon, Jun 29, 2015 at 1:04 PM, Guillaume Berche <bercheg(a)> wrote:

Thanks a lot Dmitriy, this is very useful to have this addtional level of


On Sat, Jun 27, 2015 at 2:52 AM, Dmitriy Kalinin <dkalinin(a)>

Hey all,

I just published two documents that describe some details on how to build
a CPI:


As usual feel free to contribute to docs at


cf-bosh mailing list

Join to automatically receive all group messages.