Why is bosh_registry a standalone service?

[Dr Nic Williams]

Currently bosh_registry is a standalone HTTP service that bosh_aws_cpi & bosh_openstack_cpi talk to. It has a SQL backend (defaults to sqlite3 in bosh/release/jobs/registry [1]).

Conceptually, could the registry be moved into the CPI libraries so they could be used outside of bosh without requiring a bosh_registry process running?

Is there any other part of bosh that expects a bosh_registry running?

[1] https://github.com/cloudfoundry/bosh/blob/master/release/jobs/registry/templates/registry.yml.erb#L10-L15

--

Dr Nic Williams

Stark & Wayne LLC - consultancy for Cloud Foundry users

http://drnicwilliams.com

http://starkandwayne.com

cell +1 (415) 860-2185

twitter @drnic

[Martin Englund]

The agents also talk to the registry, so it can't be moved into the CPI. 

/M

—
Sent from Mailbox for iPhone

[Dr Nic Williams]

Ok. 

What do the agents talk to the registry for?

--
Dr Nic Williams
Stark & Wayne LLC - the consultancy for Cloud Foundry
http://starkandwayne.com
+1 415 860 2185
twitter: drnic

[Martin Englund]

To get configuration info for the VM. We might be able to do away with it as could have made an incorrect assumption about the security model. 

/M

—
Sent from Mailbox for iPhone

[Alexander Lomov]

Hey, Dr. Nic. 

I've implemented standalone registry for test purposes. If you still need it - https://github.com/Altoros/go-registry