Map instances to new Cell1 takes excessive amounts of time to run on upgraded cloud
Bug #1729661 reported by
Logan V
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Map instances to new Cell1 runs unconditionally every time the nova role is run. On a prod environment upgrading from Newton, this is taking 6+ minutes each run. I think running the "cell_v2 map_instances" is probably a one time migration? So we could maybe set a local fact to skip it after it has migrated the instances into the cellsv2 successfully one time.
Changed in openstack-ansible: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in openstack-ansible: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/547072 /git.openstack. org/cgit/ openstack/ openstack- ansible- os_nova/ commit/ ?id=6321cf90304 023c20dc6abb87e 2fa20107b7051d
Committed: https:/
Submitter: Zuul
Branch: master
commit 6321cf90304023c 20dc6abb87e2fa2 0107b7051d
Author: Jimmy McCrory <email address hidden>
Date: Thu Feb 22 08:55:06 2018 -0800
Rearrange cell mapping tasks
Existing instances can be mapped to a newly created cell immediately
after the cell is created and by the same conductor host that created
the cell.
After a new compute host is built, it will need to mapped to a cell
through the 'discover_hosts' command of nova-manage. This command will
still need to be run against a host that has direct database access, but
the command is able to handle mapping of all compute hosts that do not
currently belong to the cell so it only needs to be run once per play.
There can be a short delay in the time between a compute service
starting and becoming available to be discovered and mapped but, for
most deployments, compute host discovery will be handled automatically
as a periodic task.
Change-Id: I4f7328e1aff79e b94f278999b97fb ad8f44c6a3e
Closes-Bug: 1749037
Related-Bug: 1729661
Related-Bug: 1752540