There's one less service with nova-network disabled, meaning the host
indexes are off by one. We just use a regex sub to avoid needing to
change this.
Change-Id: I5c8496f7287634a0db50f4545c43aeba33b75e6b
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Since we already worked on the NeutronFixture to return security groups
in change Ibbee7fd11c1aa254e399d302adbae69126e98262, this now just
works.
Change-Id: I16215c4bfddf874c9705d4746f911dfeaac624f6
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Another case of there being no nova-network host.
Change-Id: I51df797df4e1b77f70fe3dd87374737e650c27d9
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Three tests require modification to specifically request an API that our
NeutronFixture provides. The rest just work (TM).
Change-Id: I423b7ab5c98ea9d559caefec0b49271e28a140fa
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Since we already worked on the NeutronFixture to return security groups
in change Ibbee7fd11c1aa254e399d302adbae69126e98262, this now just
works.
Change-Id: Ia9456055bc4defaefa98cfa82484b9ce5c8792e0
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
For our immediate purposes, this should always return something so we
modify the mock to do just that. That requires some modifications to
existing tests but is otherwise pretty simple. A future change will
address the TODO contained within to properly mock the neutron API.
Change-Id: Ibbee7fd11c1aa254e399d302adbae69126e98262
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This one is long because network quotas aren't a thing when using
neutron, which means we need to remove them from all the samples.
Change-Id: I9cb2fb1b3817797a53c1331d666750399a7f5f87
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This is pretty simple - a nova-network host obviously won't be present
in nova-network is disabled.
Change-Id: I4872f0bcaabb8e1cf1aad297a1c55993f2a3fe6e
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This information was mistakenly removed when references to the
nova-consoleauth service were removed from the docs in change
Ie96e18ea7762b93b4116b35d7ebcfcbe53c55527.
Closes-Bug: #1846401
Change-Id: I08fa4650d190114775993e8094efbf46b984dfdc
With the fix for bug 1781286 for reschedules during server
create and resize/migrate, we can update the cells v2 docs
saying the up-call issue for that big is now fixed.
Change-Id: I9ff116de8b63c0fbfb880008718b1386178b1d1a
Related-Bug: #1781286
This builds on change Ia50c5f4dd2204f1cafa669097d1e744479c4d8c8
to use the Selection.availability_zone value when rescheduling
during a resize or cold migrate so that the cell conductor does not
have to make an up-call to the aggregates table in the API DB
which will fail if the cell conductor is not configured to use
the API DB.
The functional test added in Ic6926eecda1f9dd7183d66c67f04f308f6a1799d
is updated to show the failure is gone and we get the AZ from the
Selection object during the reschedule.
For the case that the availability_zone field is not in the Selection
object, there are existing unit tests in
nova.tests.unit.conductor.tasks.test_migrate which will make sure we
are not unconditionally trying to access the Selection.availability_zone
field.
Change-Id: I103d5023d3a3a7c367c7eea7fb103cb8ec52accf
Closes-Bug: #1781286
This builds on change Ia50c5f4dd2204f1cafa669097d1e744479c4d8c8
to use the Selection.availability_zone value when rescheduling
during initial server create so that the cell conductor does not
have to make an up-call to the aggregates table in the API DB
which will fail if the cell conductor is not configured to use
the API DB.
The functional test added in I62179d6b93ea1a23c4906477ee19b422bfcb72a2
is updated to show the failure is gone and we get the AZ from the
Selection object during the reschedule.
For the case that the availability_zone field is not in the Selection
object, test_build_reschedule_get_az_error still covers that.
Change-Id: I1f1c25cb4de924a1d6c3a979b758efd736bdbff0
Partial-Bug: #1781286
This adds an availability_zone field to the Selection object,
using the same type and nullable value as the same field in the
Instance object. This will be used to store the service_host
AZ to pass from the superconductor layer to the compute and cell
conductor layer to avoid an up-call to get the host AZ information
from the API DB during a reschedule.
Note that the field is nullable because a host may not be in an
AZ and CONF.default_availability_zone can technically be set to
None though it defaults to "nova".
Change-Id: Ia50c5f4dd2204f1cafa669097d1e744479c4d8c8
Related-Bug: #1781286
