I guess technically a deployment is just a bunch of rows in the bosh Postgres database; if
you move them them to another bosh then that bosh will think it owns those VMs.
At the same time, initially the VMs will still be listening to the original bosh nats
But perhaps on the new bosh you do a recreate of all vms in the deployment and it will
replace all the settings on each vms so that they call home to the new bosh.
Somewhere above you'd remove the same rows from the old bosh director Postgres DB
New bosh would need the blobs - the releases and compiled packages - but I guess they
could be recreated if you did a "bosh deploy" rather than a "bosh
Conceptually it should be possible - it's just rows in a database and some blobs; and
some VMs who need an attitude adjustment about who's the boss.
On Mon, Feb 27, 2017 at 7:25 PM +1000, "Grifalconi, Michael"
I would just bring to your attention the discussion I opened on GitHub
I am looking for the best way to achieve that or the most valid reason why I should not
even try it :)
Thanks and regards,