I asked for further details in IRC, which started a discussion there. To sum up, most folks agree migrations within a zone won't require a new instance ID. Nothing changes except the compute host it's running on. Migrations outside of a zone would require a new instance ID, but this should be fine, since other things would also change (such as IP, available volumes, ...). A cross-zone migration will be more of a copy+delete than a proper move.
-Eric On Wed, Mar 23, 2011 at 06:14:31PM +0000, Sandy Walsh wrote: > Pvo brought up a good use case for naming a little while ago: Migrations. > > If we use the instance id (assume UNC) to provide hints to the target zone, > this means the instance id would need to change should the instance move > locations. That's a no-no by everyone's measure. > > So, now I'm thinking more about Justin's comment about an external registry. > > Perhaps a glance-like entry with metadata that can change? > > Confidentiality Notice: This e-mail message (including any attached or > embedded documents) is intended for the exclusive and confidential use of the > individual or entity to which this message is addressed, and unless otherwise > expressly indicated, is confidential and privileged information of Rackspace. > Any dissemination, distribution or copying of the enclosed material is > prohibited. > If you receive this transmission in error, please notify us immediately by > e-mail > at ab...@rackspace.com, and delete the original message. > Your cooperation is appreciated. > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp