Date
1 - 4 of 4
bosh-init + the registry job
|
Geoff Franks <geoff@...>
Looking at the example manifests for bosh-init on AWS (https://bosh.io/docs/init-aws.html <https://bosh.io/docs/init-aws.html>) + vSphere (https://bosh.io/docs/init-vsphere.html <https://bosh.io/docs/init-vsphere.html>), we found that the registry job is applied in AWS and not in vSphere. Is this intentional, and there's something about the vSphere CPI that obviates the need for the registry? If not, should it be in both examples, or is it no longer necessary for any BOSH?
|
|
|
|
Dmitriy Kalinin
It's intentional. vSphere CPI does not need registry and uses CDROM drive
for bootstrapping. AWS CPI does use it to keep some state for bootstrapping. On Tue, Dec 8, 2015 at 11:14 AM, Geoff Franks <geoff(a)starkandwayne.com> wrote: Looking at the example manifests for bosh-init on AWS (
|
|
|
|
Geoff Franks <geoff@...>
Cool, thanks for the info!
toggle quoted messageShow quoted text
On Dec 8, 2015, at 2:23 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:
|
|
|
|
William C Penrod
I have this same question.
Here is an example of our registry setup in our aws bosh-init deployed director: jobs: templates: - {name: registry, release: bosh} properties: registry: address: <bound_network_address> host: <bound_network_address> db: <db_info> http: {user: user, password: password, port: 25777} username: user password: password port: 25777 Deployed with bosh 208, aws_cpi 36. This diagram helped me understand the purpose of the registry: https://bosh.io/docs/bosh-components.html On Tue, Dec 8, 2015 at 12:14 PM, Geoff Franks <geoff(a)starkandwayne.com> wrote: Looking at the example manifests for bosh-init on AWS (
|
|
|