Re: [openstack-dev] [Nova] Automatic evacuate

2014-10-21 Thread Géza Gémes
On 10/21/2014 07:53 PM, David Vossel wrote: - Original Message - -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: October 21, 2014 15:07 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Automatic evacuate On 10/21/2014 06:44

Re: [openstack-dev] [Nova] Automatic evacuate

2014-10-25 Thread Géza Gémes
On 10/22/2014 10:05 PM, David Vossel wrote: - Original Message - On 10/21/2014 07:53 PM, David Vossel wrote: - Original Message - -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: October 21, 2014 15:07 To: openstack-dev@lists.openstack.org

Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

2015-05-25 Thread Géza Gémes
. Thanks, Kevin * * *From:* Géza Gémes *Sent:* Sunday, May 24, 2015 1:07:01 AM *To:* openstack-dev@lists.openstack.org *Subject:* Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment libvirt/xen or xenapi

[openstack-dev] [nova] usefulness of device parameter at volumeAttachment

2015-05-23 Thread Géza Gémes
Hi, When someone calls nova volume-attach or the block-device-mapping parameter at boot, it is possible to specify a device name for the guest. However I couldn't find any guest OS which would honor this. E.g. with libvirt/kvm, if the guest has two virtio disks already (vda and vdb),

Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

2015-05-24 Thread Géza Gémes
libvirt/xen or xenapi? PVM or HVM? Thank you! Geza On 05/23/2015 02:21 PM, Fox, Kevin M wrote: I believe xen supports it. Thanks, Kevin * * *From:* Géza Gémes *Sent:* Saturday, May 23, 2015 2:00:32 AM *To:* OpenStack

Re: [openstack-dev] [NOVA] How boot an instance on specific compute with provider-network: physnet1

2016-08-17 Thread Géza Gémes
On 08/17/2016 05:38 PM, Rick Jones wrote: On 08/17/2016 08:25 AM, Kelam, Koteswara Rao wrote: Hi All, I have two computes Compute node 1: 1. physnet3:br-eth0 2. physnet2: br-eth2 Compute node 2: 1. physnet3:br-eth0 2. physnet1:br-eth1 3. physnet2:br-eth2 When I boot an instance with a