On May 3, 2012, at 4:50 PM, Mark Moseley wrote: > > * What is the right way to stop/start a persistent instance? So far > I've been using 'nova boot' to start and 'nova delete' to stop. E.g.: > >> nova boot --flavor=1 --image c5cecc17-295c-4ebc-9019-2ccc222d3f52 >> --key_name=key3 --nic >> net-id=63743ee0-f8a1-45f8-888a-cce38d09cca2,v4-fixed-ip=192.168.1.2 >> --block_device_mapping vda=11 --block_device_mapping vdb=12 >> --nic=net-id=63743ee0-f8a1-45f8-888a-cce38d09cca2 myvm1
You might try nova suspend/resume (does a hypervisor-level suspend where all memory is written to disk and the vm is stopped) or nova pause/unpause (stops emulation of the vm or api.openstack.org -- stop/start (this one is not exposed to novaclient, but it will shutdown the instance but not delete any files) > > * Not really a question, but if I'm using persistent storage, it'd be > nice if I didn't have to specify "--image", since I'm not actually > using the image. the image should only be necessary for the initial boot > > > * Is there a way to add an interface, but without Nova trying to > configure it? That is, add an eth1 to the vm but do nothing else (yes, > I realize I'll have to muck with ebtables/iptables on the compute > node). Our imaging process will take care of the network > configuration, so it'd be one less thing to add to Nova's management > overhead. I can probably accomplish the same thing with a dummy > network on the VM's eth1, since it's not actually being injected. not now > > > * Any plans to add a mac= subarg to the "--nic" option in 'nova boot'? this was discussed at some point, but no active development that i know of _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
