Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

yes Of course you can. it is called the InstanceLocalityFilter for the cinder scheduler.

In order for this to work: - At least one physical host should run both nova-compute and cinder-volume services. - The Extended Server Attributes extension needs to be active in Nova (this is by default), so that the 'OS-EXT-SRV-ATTR:host' property is returned when requesting instance info. - The user making the call needs to have sufficient rights for the property to be returned by Nova. This can be achieved either by changing Nova's policy.json (the 'extended_server_attributes' option), or by setting an account with privileged rights in Cinder conf.

Let me know if this helps.

Regards, Karthik Prabhu

yes Of course you can. it is called the InstanceLocalityFilter for the cinder scheduler.

In order for this to work: -

  1. At least one physical host should run both nova-compute and and cinder-volume services. - services. The Extended Server Attributes extension needs to be active in Nova Nova (this is by default), so that the 'OS-EXT-SRV-ATTR:host' property is property is returned when requesting instance info. - info.

  2. The user making the call needs to have sufficient rights for the the property to be returned by Nova. This can be achieved either by changing Nova's policy.json (the 'extended_server_attributes' 'extended_server_attributes' option), or by setting an account with privileged rights in Cinder conf.

Let me know if this helps.

Regards, Karthik Prabhu

yes Of course you can. it is called the InstanceLocalityFilter for the cinder scheduler.

In order for this to work: -

  1. At least one physical host should run both nova-compute and cinder-volume services. The Extended Server Attributes extension needs to be active in Nova (this is by default), so that the 'OS-EXT-SRV-ATTR:host' property is returned when requesting instance info.

  2. The user making the call needs to have sufficient rights for the property to be returned by Nova. This can be achieved either by changing Nova's policy.json (the 'extended_server_attributes' option), or by setting an account with privileged rights in Cinder conf.

$nova list

You need to create a volume of size 1 like

$cinder create --hint local_to_instance=<instance-id> 1

For more information, you can follow bug: https://bugs.launchpad.net/openstack-manuals/+bug/1408387

Let me know if this helps.

Regards, Karthik Prabhu