Date
1 - 4 of 4
bosh rename job
|
Geoff Franks <geoff@...>
`bosh rename job` used to be a thing, but it appears to no longer be a command in v1.3117.1. Is there a new way to safely rename a VM, and keep the persistent disks associated with the newly named VMs?
|
|
|
|
Dmitriy Kalinin
it was removed since it may have behaved incorrectly in certain conditions.
we do have a new migrated_from feature; however, it only works with cloud-config enabled deployments. no one really uses them yet, since majority of CF ecosystem did not yet start migrating. Example of how migrated_from feature works: prev manifest: jobs: - name: my-old-job instances: 2 persistent_disk: 1000 ... networks: - {name: net1} renamed job manifest: jobs: - name: my-new-job instances: 2 persistent_disk: 1000 ... networks: - {name: net1} migrated_from: - {name: my-old-job} On Thu, Feb 11, 2016 at 1:23 PM, Geoff Franks <geoff(a)starkandwayne.com> wrote: `bosh rename job` used to be a thing, but it appears to no longer be a |
|
|
|
Geoff Franks <geoff@...>
Is there any solution for non-cloud config enabled deployments running a bosh director >= v246, and current CLI?
toggle quoted message
Show quoted text
On Feb 11, 2016, at 5:16 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: |
|
|
|
Geoff Franks <geoff@...>
I guess the answer is "no". I'm sad that this feature was removed, and replaced with something that only a minority of the ecosystem can make use of. The new feature definitely sounds better, but the way it was rolled out feels like a suboptimal user experience.
toggle quoted message
Show quoted text
On Feb 11, 2016, at 5:35 PM, Geoff Franks <geoff(a)starkandwayne.com> wrote: |
|
|