Re: [openstack-dev] [qa] host aggregate's availability zone

2014-12-23 Thread Sylvain Bauza 


Le 23/12/2014 15:42, Robert Li (baoli) a écrit :

Hi Danny,

check this link out.
https://wiki.openstack.org/wiki/Scheduler_Filters

Add the following into your /etc/nova/nova.conf before starting the 
nova service.


scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, 
RamFilter, ComputeFilter, ComputeCapabilitiesFilter, 
ImagePropertiesFilter, ServerGroupAntiAffinityFilter, 
ServerGroupAffinityFilter, AvailabilityZoneFilter


Or, You can do so in your local.conf
[[post-config|$NOVA_CONF]]
[DEFAULT]
pci_alias={"name":"cisco","vendor_id":"8086","product_id":"10ed"}
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, 
RamFilter, ComputeFilter, ComputeCapabilitiesFilter, 
ImagePropertiesFilter, ServerGroupAntiAffinityFilter, 
ServerGroupAffinityFilter, AvailabilityZoneFilter





That's weird because the default value for scheduler_default_filters is :

cfg.ListOpt('scheduler_default_filters',
default=[
  'RetryFilter',
  'AvailabilityZoneFilter',
  'RamFilter',
  'ComputeFilter',
  'ComputeCapabilitiesFilter',
  'ImagePropertiesFilter',
  'ServerGroupAntiAffinityFilter',
  'ServerGroupAffinityFilter',
  ],

The AZ filter is present, so I suspect something is wrong elsewhere.


Could you maybe paste your log files for the nova-scheduler log ?

Also, please stop posting to the -dev ML, I think it's more appropriate 
to the openstack@ ML.

We need more details before creating a bug.

-Sylvain



—Robert

On 12/22/14, 9:53 AM, "Danny Choi (dannchoi)" <mailto:dannc...@cisco.com>> wrote:


Hi Joe,

No, I did not.  I’m not aware of this.

Can you tell me exactly what needs to be done?

Thanks,
Danny

--

Date: Sun, 21 Dec 2014 11:42:02 -0600
From: Joe Cropper mailto:cropper@gmail.com>>
    To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [qa] host aggregate's availability zone
Message-ID: mailto:b36d2234-bee0-4c7b-a2b2-a09cc9098...@gmail.com>>
Content-Type: text/plain; charset="utf-8"

Did you enable the AvailabilityZoneFilter in nova.conf that the
scheduler uses?  And enable the FilterScheduler?  These are two
common issues related to this.

- Joe

On Dec 21, 2014, at 10:28 AM, Danny Choi (dannchoi)
mailto:dannc...@cisco.com>> wrote:
Hi,
I have a multi-node setup with 2 compute hosts, qa5 and qa6.
I created 2 host-aggregate, each with its own availability
zone, and assigned one compute host:
localadmin@qa4:~/devstack$ nova aggregate-details
host-aggregate-zone-1

++---+---+---+--+
| Id | Name  | Availability Zone | Hosts |
Metadata |

++---+---+---+--+
| 9  | host-aggregate-zone-1 | az-1  | 'qa5' |
'availability_zone=az-1' |

++---+---+---+--+
localadmin@qa4:~/devstack$ nova aggregate-details
host-aggregate-zone-2

++---+---+---+--+
| Id | Name  | Availability Zone | Hosts |
Metadata |

++---+---+---+--+
| 10 | host-aggregate-zone-2 | az-2  | 'qa6' |
'availability_zone=az-2' |
++---+---+---+?+
My intent is to control at which compute host to launch a VM
via the host-aggregate?s availability-zone parameter.
To test, for vm-1, I specify --availiability-zone=az-1, and
--availiability-zone=az-2 for vm-2:
localadmin@qa4:~/devstack$ nova boot --image
cirros-0.3.2-x86_64-uec --flavor 1 --nic
net-id=5da9d715-19fd-47c7-9710-e395b5b90442
--availability-zone az-1 vm-1

+--++
| Property |
Value  |

+--++
| OS-

Re: [openstack-dev] [qa] host aggregate's availability zone

2014-12-23 Thread Robert Li (baoli) 
Hi Danny,

check this link out.
https://wiki.openstack.org/wiki/Scheduler_Filters

Add the following into your /etc/nova/nova.conf before starting the nova 
service.

scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, 
ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, 
ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter, AvailabilityZoneFilter

Or, You can do so in your local.conf
[[post-config|$NOVA_CONF]]
[DEFAULT]
pci_alias={"name":"cisco","vendor_id":"8086","product_id":"10ed"}
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, 
ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, 
ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter, AvailabilityZoneFilter


—Robert

On 12/22/14, 9:53 AM, "Danny Choi (dannchoi)" 
mailto:dannc...@cisco.com>> wrote:

Hi Joe,

No, I did not.  I’m not aware of this.

Can you tell me exactly what needs to be done?

Thanks,
Danny

--

Date: Sun, 21 Dec 2014 11:42:02 -0600
From: Joe Cropper mailto:cropper@gmail.com>>
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [qa] host aggregate's availability zone
Message-ID: 
mailto:b36d2234-bee0-4c7b-a2b2-a09cc9098...@gmail.com>>
Content-Type: text/plain; charset="utf-8"

Did you enable the AvailabilityZoneFilter in nova.conf that the scheduler uses? 
 And enable the FilterScheduler?  These are two common issues related to this.

- Joe

On Dec 21, 2014, at 10:28 AM, Danny Choi (dannchoi) 
mailto:dannc...@cisco.com>> wrote:
Hi,
I have a multi-node setup with 2 compute hosts, qa5 and qa6.
I created 2 host-aggregate, each with its own availability zone, and assigned 
one compute host:
localadmin@qa4:~/devstack$ nova aggregate-details host-aggregate-zone-1
++---+---+---+--+
| Id | Name  | Availability Zone | Hosts | Metadata 
|
++---+---+---+--+
| 9  | host-aggregate-zone-1 | az-1  | 'qa5' | 
'availability_zone=az-1' |
++---+---+---+--+
localadmin@qa4:~/devstack$ nova aggregate-details host-aggregate-zone-2
++---+---+---+--+
| Id | Name  | Availability Zone | Hosts | Metadata 
|
++---+---+---+--+
| 10 | host-aggregate-zone-2 | az-2  | 'qa6' | 
'availability_zone=az-2' |
++---+---+---+?+
My intent is to control at which compute host to launch a VM via the 
host-aggregate?s availability-zone parameter.
To test, for vm-1, I specify --availiability-zone=az-1, and 
--availiability-zone=az-2 for vm-2:
localadmin@qa4:~/devstack$ nova boot --image cirros-0.3.2-x86_64-uec --flavor 1 
--nic net-id=5da9d715-19fd-47c7-9710-e395b5b90442 --availability-zone az-1 vm-1
+--++
| Property | Value  
|
+--++
| OS-DCF:diskConfig| MANUAL 
|
| OS-EXT-AZ:availability_zone  | nova   
|
| OS-EXT-SRV-ATTR:host | -  
|
| OS-EXT-SRV-ATTR:hypervisor_hostname  | -  
|
| OS-EXT-SRV-ATTR:instance_name| instance-0066  
|
| OS-EXT-STS:power_state   | 0  
|
| OS-EXT-STS:task_state| -  
|
| OS-EXT-STS:vm_state  | building   
|
| OS-SRV-USG:launched_at   | -  
|
| OS-SRV-USG:terminated_at | -  
|
| accessIPv4   |
|
| accessIPv6   |
|
| adminPass| kxot3ZBZcBH6

Re: [openstack-dev] [qa] host aggregate's availability zone

2014-12-22 Thread Danny Choi (dannchoi) 
Hi Joe,

No, I did not.  I’m not aware of this.

Can you tell me exactly what needs to be done?

Thanks,
Danny

--

Date: Sun, 21 Dec 2014 11:42:02 -0600
From: Joe Cropper mailto:cropper@gmail.com>>
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [qa] host aggregate's availability zone
Message-ID: 
mailto:b36d2234-bee0-4c7b-a2b2-a09cc9098...@gmail.com>>
Content-Type: text/plain; charset="utf-8"

Did you enable the AvailabilityZoneFilter in nova.conf that the scheduler uses? 
 And enable the FilterScheduler?  These are two common issues related to this.

- Joe

On Dec 21, 2014, at 10:28 AM, Danny Choi (dannchoi) 
mailto:dannc...@cisco.com>> wrote:
Hi,
I have a multi-node setup with 2 compute hosts, qa5 and qa6.
I created 2 host-aggregate, each with its own availability zone, and assigned 
one compute host:
localadmin@qa4:~/devstack$ nova aggregate-details host-aggregate-zone-1
++---+---+---+--+
| Id | Name  | Availability Zone | Hosts | Metadata 
|
++---+---+---+--+
| 9  | host-aggregate-zone-1 | az-1  | 'qa5' | 
'availability_zone=az-1' |
++---+---+---+--+
localadmin@qa4:~/devstack$ nova aggregate-details host-aggregate-zone-2
++---+---+---+--+
| Id | Name  | Availability Zone | Hosts | Metadata 
|
++---+---+---+--+
| 10 | host-aggregate-zone-2 | az-2  | 'qa6' | 
'availability_zone=az-2' |
++---+---+---+?+
My intent is to control at which compute host to launch a VM via the 
host-aggregate?s availability-zone parameter.
To test, for vm-1, I specify --availiability-zone=az-1, and 
--availiability-zone=az-2 for vm-2:
localadmin@qa4:~/devstack$ nova boot --image cirros-0.3.2-x86_64-uec --flavor 1 
--nic net-id=5da9d715-19fd-47c7-9710-e395b5b90442 --availability-zone az-1 vm-1
+--++
| Property | Value  
|
+--++
| OS-DCF:diskConfig| MANUAL 
|
| OS-EXT-AZ:availability_zone  | nova   
|
| OS-EXT-SRV-ATTR:host | -  
|
| OS-EXT-SRV-ATTR:hypervisor_hostname  | -  
|
| OS-EXT-SRV-ATTR:instance_name| instance-0066  
|
| OS-EXT-STS:power_state   | 0  
|
| OS-EXT-STS:task_state| -  
|
| OS-EXT-STS:vm_state  | building   
|
| OS-SRV-USG:launched_at   | -  
|
| OS-SRV-USG:terminated_at | -  
|
| accessIPv4   |
|
| accessIPv6   |
|
| adminPass| kxot3ZBZcBH6   
|
| config_drive |
|
| created  | 2014-12-21T15:59:03Z   
|
| flavor   | m1.tiny (1)
|
| hostId   |
|
| id   | 854acae9-b718-4ea5-bc28-e0bc46378b60   
|
| image| cirros-0.3.2-x86_64-uec 
(61409a53-305c-4022-978b-06e55052875b) |
| key_name | -  
|
| metadata | {} 
|
| name

Re: [openstack-dev] [qa] host aggregate's availability zone

2014-12-21 Thread Joe Cropper 
Did you enable the AvailabilityZoneFilter in nova.conf that the scheduler uses? 
 And enable the FilterScheduler?  These are two common issues related to this.

- Joe

> On Dec 21, 2014, at 10:28 AM, Danny Choi (dannchoi)  
> wrote:
> 
> Hi,
> 
> I have a multi-node setup with 2 compute hosts, qa5 and qa6.
> 
> I created 2 host-aggregate, each with its own availability zone, and assigned 
> one compute host:
> 
> localadmin@qa4:~/devstack$ nova aggregate-details host-aggregate-zone-1
> ++---+---+---+--+
> | Id | Name  | Availability Zone | Hosts | Metadata   
>   |
> ++---+---+---+--+
> | 9  | host-aggregate-zone-1 | az-1  | 'qa5' | 
> 'availability_zone=az-1' |
> ++---+---+---+--+
> localadmin@qa4:~/devstack$ nova aggregate-details host-aggregate-zone-2
> ++---+---+---+--+
> | Id | Name  | Availability Zone | Hosts | Metadata   
>   |
> ++---+---+---+--+
> | 10 | host-aggregate-zone-2 | az-2  | 'qa6' | 
> 'availability_zone=az-2' |
> ++---+---+---+—+
> 
> My intent is to control at which compute host to launch a VM via the 
> host-aggregate’s availability-zone parameter.
> 
> To test, for vm-1, I specify --availiability-zone=az-1, and 
> --availiability-zone=az-2 for vm-2:
> 
> localadmin@qa4:~/devstack$ nova boot --image cirros-0.3.2-x86_64-uec --flavor 
> 1 --nic net-id=5da9d715-19fd-47c7-9710-e395b5b90442 --availability-zone az-1 
> vm-1
> +--++
> | Property | Value
>   |
> +--++
> | OS-DCF:diskConfig| MANUAL   
>   |
> | OS-EXT-AZ:availability_zone  | nova 
>   |
> | OS-EXT-SRV-ATTR:host | -
>   |
> | OS-EXT-SRV-ATTR:hypervisor_hostname  | -
>   |
> | OS-EXT-SRV-ATTR:instance_name| instance-0066
>   |
> | OS-EXT-STS:power_state   | 0
>   |
> | OS-EXT-STS:task_state| -
>   |
> | OS-EXT-STS:vm_state  | building 
>   |
> | OS-SRV-USG:launched_at   | -
>   |
> | OS-SRV-USG:terminated_at | -
>   |
> | accessIPv4   |  
>   |
> | accessIPv6   |  
>   |
> | adminPass| kxot3ZBZcBH6 
>   |
> | config_drive |  
>   |
> | created  | 2014-12-21T15:59:03Z 
>   |
> | flavor   | m1.tiny (1)  
>   |
> | hostId   |  
>   |
> | id   | 854acae9-b718-4ea5-bc28-e0bc46378b60 
>   |
> | image| cirros-0.3.2-x86_64-uec 
> (61409a53-305c-4022-978b-06e55052875b) |
> | key_name | -
>   |
> | metadata | {}   
>   |
> | name | vm-1 
>   |
> | os-extended-volumes:volumes_attached | []   
>   |
> | progress | 0
>   |
> | security_groups  | default  
>   |
> | status   | BUILD

[openstack-dev] [qa] host aggregate's availability zone

2014-12-21 Thread Danny Choi (dannchoi) 
Hi,

I have a multi-node setup with 2 compute hosts, qa5 and qa6.

I created 2 host-aggregate, each with its own availability zone, and assigned 
one compute host:


localadmin@qa4:~/devstack$ nova aggregate-details host-aggregate-zone-1

++---+---+---+--+

| Id | Name  | Availability Zone | Hosts | Metadata 
|

++---+---+---+--+

| 9  | host-aggregate-zone-1 | az-1  | 'qa5' | 
'availability_zone=az-1' |

++---+---+---+--+

localadmin@qa4:~/devstack$ nova aggregate-details host-aggregate-zone-2

++---+---+---+--+

| Id | Name  | Availability Zone | Hosts | Metadata 
|

++---+---+---+--+

| 10 | host-aggregate-zone-2 | az-2  | 'qa6' | 
'availability_zone=az-2' |

++---+---+---+—+


My intent is to control at which compute host to launch a VM via the 
host-aggregate’s availability-zone parameter.


To test, for vm-1, I specify --availiability-zone=az-1, and 
--availiability-zone=az-2 for vm-2:


localadmin@qa4:~/devstack$ nova boot --image cirros-0.3.2-x86_64-uec --flavor 1 
--nic net-id=5da9d715-19fd-47c7-9710-e395b5b90442 --availability-zone az-1 vm-1

+--++

| Property | Value  
|

+--++

| OS-DCF:diskConfig| MANUAL 
|

| OS-EXT-AZ:availability_zone  | nova   
|

| OS-EXT-SRV-ATTR:host | -  
|

| OS-EXT-SRV-ATTR:hypervisor_hostname  | -  
|

| OS-EXT-SRV-ATTR:instance_name| instance-0066  
|

| OS-EXT-STS:power_state   | 0  
|

| OS-EXT-STS:task_state| -  
|

| OS-EXT-STS:vm_state  | building   
|

| OS-SRV-USG:launched_at   | -  
|

| OS-SRV-USG:terminated_at | -  
|

| accessIPv4   |
|

| accessIPv6   |
|

| adminPass| kxot3ZBZcBH6   
|

| config_drive |
|

| created  | 2014-12-21T15:59:03Z   
|

| flavor   | m1.tiny (1)
|

| hostId   |
|

| id   | 854acae9-b718-4ea5-bc28-e0bc46378b60   
|

| image| cirros-0.3.2-x86_64-uec 
(61409a53-305c-4022-978b-06e55052875b) |

| key_name | -  
|

| metadata | {} 
|

| name | vm-1   
|

| os-extended-volumes:volumes_attached | [] 
|

| progress | 0  
|

| security_groups  | default
|

| status   | BUILD  
|

| tenant_id| 84827057a7444354b0bff11566ccb80b   
|

| updated  | 2014-12-21T15:59:03Z   
|

| user_id  | 9d5fd9947d154a2db396fce177f1f83c