| 2018-10-04 10:47:03 |
Dmitrii Shcherbakov |
bug |
|
|
added bug |
| 2018-10-04 10:48:30 |
Dmitrii Shcherbakov |
bug task added |
|
charm-neutron-openvswitch |
|
| 2018-10-04 10:49:11 |
Dmitrii Shcherbakov |
bug task added |
|
charm-neutron-gateway |
|
| 2018-10-04 10:58:52 |
Dmitrii Shcherbakov |
information type |
Private |
Public |
|
| 2018-10-04 10:59:33 |
James Page |
description |
Currently default_availability_zone in nova is set to "nova" regardless of a charm config called default-availability-zone.
For charm-neutron-openvswitch the availability_zone config for DHCP agents is set to a config value propagated from the nova charm (which is always set to "nova"). This prevents using AZ-aware scheduling of DHCP agents which is a customer requirement.
Proposed solutions:
1) use JUJU_AVAILABILITY_ZONE for agents configured by neutron-openvswitch charm if set, otherwise use a value propagated from a nova charm config;
2) use JUJU_AVAILABILITY_ZONE for nova-compute charm unless it is overridden by the default-availability-zone charm config.
More info:
~~~
There are two AZ-related nova configs:
default_availability_zone (default AZ for a compute host if it has not been added to an aggregate with an assigned AZ)
https://github.com/openstack/nova/blob/stable/queens/nova/conf/availability_zone.py#L30-L39
https://github.com/openstack/nova/blob/stable/queens/nova/availability_zones.py#L71-L100
default_schedule_zone (a default zone used by Nova API if a user request does not contain an AZ)
https://github.com/openstack/nova/blob/stable/queens/nova/conf/availability_zone.py#L43-L59
https://github.com/openstack/nova/blob/stable/queens/nova/compute/api.py#L488-L489
Neutron has its own concept of an availability zone for per-agent AZs which is important for cases like HA DHCP.
https://blueprints.launchpad.net/neutron/+spec/add-availability-zone (mitaka)
https://review.openstack.org/#/c/246107/
https://github.com/openstack/neutron/blob/stable/queens/neutron/conf/agent/common.py#L142-L147
~~
Charm behavior:
neutron-openvswitch simply receives a default config from nova-compute primary
https://github.com/openstack/charm-nova-compute/blob/stable/18.08/hooks/nova_compute_hooks.py#L442-L445
'default_availability_zone': config('default-availability-zone')
https://github.com/openstack/charm-neutron-openvswitch/blob/stable/18.08/hooks/neutron_ovs_context.py#L208-L214
availability_zone = relation_get(
'default_availability_zone', |
Currently default_availability_zone in nova is set to "nova" regardless of a charm config called default-availability-zone.
For charm-neutron-openvswitch the availability_zone config for DHCP agents is set to a config value propagated from the nova charm (which is always set to "nova"). This prevents using AZ-aware scheduling of DHCP agents which is an operator requirement.
Proposed solutions:
1) use JUJU_AVAILABILITY_ZONE for agents configured by neutron-openvswitch charm if set, otherwise use a value propagated from a nova charm config;
2) use JUJU_AVAILABILITY_ZONE for nova-compute charm unless it is overridden by the default-availability-zone charm config.
More info:
~~~
There are two AZ-related nova configs:
default_availability_zone (default AZ for a compute host if it has not been added to an aggregate with an assigned AZ)
https://github.com/openstack/nova/blob/stable/queens/nova/conf/availability_zone.py#L30-L39
https://github.com/openstack/nova/blob/stable/queens/nova/availability_zones.py#L71-L100
default_schedule_zone (a default zone used by Nova API if a user request does not contain an AZ)
https://github.com/openstack/nova/blob/stable/queens/nova/conf/availability_zone.py#L43-L59
https://github.com/openstack/nova/blob/stable/queens/nova/compute/api.py#L488-L489
Neutron has its own concept of an availability zone for per-agent AZs which is important for cases like HA DHCP.
https://blueprints.launchpad.net/neutron/+spec/add-availability-zone (mitaka)
https://review.openstack.org/#/c/246107/
https://github.com/openstack/neutron/blob/stable/queens/neutron/conf/agent/common.py#L142-L147
~~
Charm behavior:
neutron-openvswitch simply receives a default config from nova-compute primary
https://github.com/openstack/charm-nova-compute/blob/stable/18.08/hooks/nova_compute_hooks.py#L442-L445
'default_availability_zone': config('default-availability-zone')
https://github.com/openstack/charm-neutron-openvswitch/blob/stable/18.08/hooks/neutron_ovs_context.py#L208-L214
availability_zone = relation_get(
'default_availability_zone', |
|
| 2018-10-04 11:08:59 |
James Page |
charm-neutron-gateway: status |
New |
Triaged |
|
| 2018-10-04 11:09:00 |
James Page |
charm-neutron-openvswitch: status |
New |
Triaged |
|
| 2018-10-04 11:09:02 |
James Page |
charm-nova-compute: status |
New |
Triaged |
|
| 2018-10-04 11:09:04 |
James Page |
charm-neutron-gateway: importance |
Undecided |
Wishlist |
|
| 2018-10-04 11:09:06 |
James Page |
charm-neutron-openvswitch: importance |
Undecided |
Wishlist |
|
| 2018-10-04 11:09:08 |
James Page |
charm-nova-compute: importance |
Undecided |
Wishlist |
|
| 2018-10-04 17:07:16 |
Dmitrii Shcherbakov |
charm-nova-compute: assignee |
|
Dmitrii Shcherbakov (dmitriis) |
|
| 2018-10-04 17:07:23 |
Dmitrii Shcherbakov |
charm-nova-compute: status |
Triaged |
In Progress |
|
| 2018-10-05 00:56:35 |
Dmitrii Shcherbakov |
charm-neutron-gateway: assignee |
|
Dmitrii Shcherbakov (dmitriis) |
|
| 2018-10-05 00:56:39 |
Dmitrii Shcherbakov |
charm-neutron-gateway: status |
Triaged |
In Progress |
|
| 2018-10-05 00:57:16 |
Dmitrii Shcherbakov |
description |
Currently default_availability_zone in nova is set to "nova" regardless of a charm config called default-availability-zone.
For charm-neutron-openvswitch the availability_zone config for DHCP agents is set to a config value propagated from the nova charm (which is always set to "nova"). This prevents using AZ-aware scheduling of DHCP agents which is an operator requirement.
Proposed solutions:
1) use JUJU_AVAILABILITY_ZONE for agents configured by neutron-openvswitch charm if set, otherwise use a value propagated from a nova charm config;
2) use JUJU_AVAILABILITY_ZONE for nova-compute charm unless it is overridden by the default-availability-zone charm config.
More info:
~~~
There are two AZ-related nova configs:
default_availability_zone (default AZ for a compute host if it has not been added to an aggregate with an assigned AZ)
https://github.com/openstack/nova/blob/stable/queens/nova/conf/availability_zone.py#L30-L39
https://github.com/openstack/nova/blob/stable/queens/nova/availability_zones.py#L71-L100
default_schedule_zone (a default zone used by Nova API if a user request does not contain an AZ)
https://github.com/openstack/nova/blob/stable/queens/nova/conf/availability_zone.py#L43-L59
https://github.com/openstack/nova/blob/stable/queens/nova/compute/api.py#L488-L489
Neutron has its own concept of an availability zone for per-agent AZs which is important for cases like HA DHCP.
https://blueprints.launchpad.net/neutron/+spec/add-availability-zone (mitaka)
https://review.openstack.org/#/c/246107/
https://github.com/openstack/neutron/blob/stable/queens/neutron/conf/agent/common.py#L142-L147
~~
Charm behavior:
neutron-openvswitch simply receives a default config from nova-compute primary
https://github.com/openstack/charm-nova-compute/blob/stable/18.08/hooks/nova_compute_hooks.py#L442-L445
'default_availability_zone': config('default-availability-zone')
https://github.com/openstack/charm-neutron-openvswitch/blob/stable/18.08/hooks/neutron_ovs_context.py#L208-L214
availability_zone = relation_get(
'default_availability_zone', |
Currently default_availability_zone in nova is set to "nova" regardless of a charm config called default-availability-zone.
For charm-neutron-openvswitch the availability_zone config for DHCP agents is set to a config value propagated from the nova charm (which is always set to "nova"). This prevents using AZ-aware scheduling of DHCP agents which is an operator requirement.
Proposed solutions:
1) use JUJU_AVAILABILITY_ZONE for agents configured by neutron-openvswitch charm if set, otherwise use a value propagated from a nova charm config;
2) use JUJU_AVAILABILITY_ZONE for nova-compute charm unless it is overridden by the default-availability-zone charm config.
More info:
~~~
There are two AZ-related nova configs:
default_availability_zone (default AZ for a compute host if it has not been added to an aggregate with an assigned AZ)
https://github.com/openstack/nova/blob/stable/queens/nova/conf/availability_zone.py#L30-L39
https://github.com/openstack/nova/blob/stable/queens/nova/availability_zones.py#L71-L100
default_schedule_zone (a default zone used by Nova API if a user request does not contain an AZ)
https://github.com/openstack/nova/blob/stable/queens/nova/conf/availability_zone.py#L43-L59
https://github.com/openstack/nova/blob/stable/queens/nova/compute/api.py#L488-L489
Neutron has its own concept of an availability zone for per-agent AZs which is important for cases like HA DHCP.
https://blueprints.launchpad.net/neutron/+spec/add-availability-zone (mitaka)
https://review.openstack.org/#/c/246107/
https://github.com/openstack/neutron/blob/stable/queens/neutron/conf/agent/common.py#L142-L147
~~
Charm behavior:
neutron-openvswitch simply receives a default config from nova-compute primary
https://github.com/openstack/charm-nova-compute/blob/stable/18.08/hooks/nova_compute_hooks.py#L442-L445
'default_availability_zone': config('default-availability-zone')
https://github.com/openstack/charm-neutron-openvswitch/blob/stable/18.08/hooks/neutron_ovs_context.py#L208-L214
availability_zone = relation_get(
'default_availability_zone',
Reviews:
https://review.openstack.org/#/q/topic:bug/1796068+(status:open+OR+status:merged) |
|
| 2018-10-08 14:57:21 |
Dmitrii Shcherbakov |
bug |
|
|
added subscriber Canonical Field High |
| 2018-10-09 13:27:30 |
OpenStack Infra |
charm-neutron-gateway: status |
In Progress |
Fix Committed |
|
| 2018-10-09 15:24:00 |
OpenStack Infra |
charm-nova-compute: status |
In Progress |
Fix Committed |
|
| 2018-11-20 00:29:36 |
David Ames |
charm-nova-compute: milestone |
|
19.04 |
|
| 2018-11-20 00:29:40 |
David Ames |
charm-neutron-gateway: milestone |
|
19.04 |
|
| 2018-11-20 05:34:18 |
Dmitrii Shcherbakov |
charm-nova-compute: status |
Fix Committed |
Fix Released |
|
| 2018-11-20 05:34:35 |
Dmitrii Shcherbakov |
charm-nova-compute: milestone |
19.04 |
18.11 |
|
| 2018-11-20 05:34:47 |
Dmitrii Shcherbakov |
charm-neutron-gateway: status |
Fix Committed |
Fix Released |
|
| 2018-11-20 05:34:59 |
Dmitrii Shcherbakov |
charm-neutron-gateway: milestone |
19.04 |
18.11 |
|
| 2018-12-03 09:22:24 |
James Page |
charm-neutron-openvswitch: status |
Triaged |
Invalid |
|
| 2019-01-18 08:16:20 |
Dmitrii Shcherbakov |
bug task added |
|
charm-neutron-api |
|
| 2019-01-21 13:30:27 |
Dmitrii Shcherbakov |
charm-neutron-api: milestone |
|
19.04 |
|
| 2019-01-21 13:30:48 |
Dmitrii Shcherbakov |
charm-neutron-api: status |
New |
Triaged |
|
| 2019-01-21 13:30:58 |
Dmitrii Shcherbakov |
charm-neutron-api: importance |
Undecided |
High |
|
| 2019-01-25 11:47:39 |
OpenStack Infra |
charm-neutron-api: status |
Triaged |
Fix Committed |
|
| 2019-04-11 02:49:56 |
Yoshi Kadokawa |
bug |
|
|
added subscriber Yoshi Kadokawa |
| 2019-04-17 21:56:04 |
David Ames |
charm-neutron-api: status |
Fix Committed |
Fix Released |
|
