Date
1 - 4 of 4
Migrating a full-stack bosh deployment to bosh-init
Allan Espinosa
Hi,
We currently have a binary bosh [1] setup. However we would like to transition to bosh-init to prevent having to manage multiple bosh deployments. I'm looking at how to regenerate the state file described in [2]. I can find my VM CID from "bosh vms bosh-meta --details" but can't get the other information from the director. Is there other places to retrieve the information? Or do I have to poke things below the cpi (vSphere in our case). We're using the vsphere cpi for our deployment. Thanks Allan [1] https://blog.starkandwayne.com/2014/07/10/resurrecting-bosh-with-binary-boshes/ [2] https://bosh.io/docs/using-bosh-init.html#recover-deployment-state |
|
Gwenn Etourneau
disk id should be present on the IaaS layer, so I guess if you look into
Vsphere you should find it. If I remember should be the form disk-some-uuid, vcenter>yourvm>editsetting>yourdisk and should be in the first field (/disk-some-uui.vmdk). But I don't have any vcenter to check now ... On Wed, Jun 3, 2015 at 11:47 AM, Espinosa, Allan | Allan | OPS < allan.espinosa(a)rakuten.com> wrote: Hi, |
|
Dmitriy Kalinin
Unfortunately we do not show persistent disk IDs in any of the CLI commands
*yet*. You can either look at the vsphere settings for the VM for which disk is attached or look at the /var/vcap/bosh/settings.json on the VM that has the disk attached. On Tue, Jun 2, 2015 at 10:37 PM, Gwenn Etourneau <getourneau(a)pivotal.io> wrote: disk id should be present on the IaaS layer, so I guess if you look into |
|
Allan Espinosa
Thanks Gwenn, Dmitry
toggle quoted message
Show quoted text
I'll try this out. -----Original Message----- |
|