Also disabling the nfv devstack jobs. These jobs are failing
after the recent repo restructuring due to failures in the
FM devstack setup. The jobs can be re-enabled in the future
(after the issues are fixed), if there is some value in
doing so.
Change-Id: Ib443edc76ca636c83331945de74d875ffb3592ac
Story: 2004515
Task: 36579
Signed-off-by: Bart Wensley <barton.wensley@windriver.com>
Use templates instead of individual jobs so that these
can be changed in one place.
Depends-On: https://review.opendev.org/677606
Change-Id: I1b81f71977bcaa52e60566b9a64bffe6ffdab7d6
When the VIM detects the nova compute service is down on a
worker host, it attempts to migrate instances off that host
(by "disabling" the host). However, this isn't possible if
the compute service is down. The VIM then fails the instances,
which will eventually result in their evacuation (if the host
goes offline) or a reboot of the instance (if the compute
service recovers).
In the containers world, when the libvirt pod is restarted
(e.g. when stx-openstack application is re-applied), nova
reports that the compute service is down (for a short period
of time), which causes the undesirable behaviour described
above. The VIM is being updated to not disable the host in
this case and instead just raise an alarm to indicate that
the compute service has failed.
Change-Id: I186d8d76bbcd87405bafec47deb92ec24580640e
Closes-Bug: 1833096
Signed-off-by: Bart Wensley <barton.wensley@windriver.com>
The VIM's host audit will fail instances on any host that is
"not enabled". That includes hosts where the operational state
is unknown.
Updating the check to ensure the host is "disabled" not that it
is "not enabled" to avoid failing instances on a host where we
don't know the operational state.
Change-Id: I68d3e9f63695de721c10fb1dd2b7ac5917cb50fa
Closes-Bug: 1840176
Signed-off-by: Bart Wensley <barton.wensley@windriver.com>
When we execute pep8 locally, we find there is
DEPRECATION WARNING, This warning will be an error
in tox4 and above, this change is to fix this.
Change-Id: Iaebe8ffe3aa1b92956403c679600fad0098d8329
Partial-Bug: #1835386
Signed-off-by: junboli <junbo85.li@gmail.com>
The storyboard and gerrit doc link are error, and git library
redirect to the correct one, this change is to correct all them.
Change-Id: I1ab75cb43ee80d356993162013f9947dff7535fe
Partial-Bug: #1835207
Signed-off-by: junboli <junbo85.li@gmail.com>
This updates the upper-constraints.txt used by tox for
installing python modules to reference the stable/stein
constraints.
Change-Id: If3880fba415ce3023e497ff557efae1b2b65ccff
Partial-Bug: 1834216
Signed-off-by: Don Penney <don.penney@windriver.com>
When a host goes offline unexpectedly (e.g. spontaneous reboot or
power failure), it takes a while before kubernetes detects that
the node is unavailable and sets the node to be not ready, which
causes the pods on the node to be set to not ready as well. Until
that happens, the endpoints for the pods are still in use, which
can lead to message loss.
In StarlingX, our maintenance component detects that a node is
offline faster than kubernetes does. To improve the time taken
to react, the VIM is updated to set the status of the pods on
an offline node to not ready when it is informed by maintenance
that a node is offline.
Change-Id: I1a20707981c5517e0d305fd9551bc5e69c0282cd
Story: 2002843
Task: 33695
Signed-off-by: Bart Wensley <barton.wensley@windriver.com>
if the entity_type of alarms/logs "instance", they
are related to VM instance and should be managed by
openstack. So we need to raise/clear them by restful
api of fm services in pods.
changes:
1. point vim webserver to fm in pods
2. change alarm/log interface of nfvi
3. change nfvi alarm/log configure file
add param "fault_management_pod_disabled" with 'True' as
the default value into config file to disable nfvi raise
alarms to containerized fm. it will be removed in future
Depends-On: https://review.opendev.org/658740/
Depends-On: https://review.opendev.org/648814/
Story: 2004008
Task: 28876
Change-Id: I373f1f8cd6a69b96f70c99c46e6580002c09efc0
Signed-off-by: SidneyAn <ran1.an@intel.com>
after fm containerization, nfvi would raise openstack
alarms to the fm in pods. while retrieve both platform
and openstack alarms are still required.
So here we add NFVFaultMgmtAPI to get alarms from fm
in pods and gather all alarms in vim strategy steps.
add param "fault_management_pod_disabled" with 'True' as
the default value into config file to disable nfvi get
alarms from containerized fm. it will be removed in future
Depends-On: https://review.opendev.org/658972/
Depends-On: https://review.opendev.org/662896/
Story: 2004008
Task: 30930
Change-Id: I79e0010f556f99923df25f355e554f43283d26f2
Signed-off-by: SidneyAn <ran1.an@intel.com>
Rename the stx-* repo references to drop the stx prefix.
Change-Id: I8d68a8250b7dff68b1e93fe79c005b566579f790
Signed-off-by: Don Penney <don.penney@windriver.com>
With the StarlingX move to supporting pure upstream OpenStack, the
majority of the SDK Modules are related to functionality no longer
supported. The remaining SDK Modules will be moved to StarlingX
documentation.
Story: 2005275
Task: 30545
Depends-On: https://review.openstack.org/#/c/653521
Change-Id: I842596dab79bff79313671e3e0b7aa7e4a93c493
Signed-off-by: Kristine Bujold <kristine.bujold@windriver.com>
If a network agent goes down in the middle of processing
a reschedule/rebalance operation, abort the current operation
so as not to schedule resources onto a down agent. This is
necessary as the reschedule/rebalance operations may take a
fair amount of time, and users may lock hosts (bringing
down the network agents) at any time.
Change-Id: Ie933b517e4e4cea3beb7d00e3c65d2f538f14e5c
Story: 2003857
Task: 30500
Signed-off-by: Kevin Smith <kevin.smith@windriver.com>
Add fix to ignore down agents in rescheduling.
Change-Id: I5d06bd489f2d67be996e55608b77e31c1ed85114
Closes-Bug: #1824027
Signed-off-by: Kevin Smith <kevin.smith@windriver.com>
When /etc/nova/openrc was removed from the controller
these scenario tests were not updated and therefore were
unable to run.
Verified that the tests are able to get further.
Story: 2004764
Task: 30370
Change-Id: I4206f850957afdd551f9932b9c452d58aee893e9
Signed-off-by: Al Bailey <Al.Bailey@windriver.com>
This update removes pike and master wheel and/or image files,
as these have been replaced with stable/dev.
Change-Id: Iefc8cbc8a03e8891fb4d240d16ba10cf1b0fcc64
Story: 2005248
Task: 30326
Signed-off-by: Don Penney <don.penney@windriver.com>
When a host goes disabled, move the networks off of the dhcp agent
of that host, distributing them amongst the other available dhcp agents.
When a host goes enabled, rebalance the networks on the available
dhcp agents, moving some to the newly enabled host.
Story: 2003857
Task: 26665
Depends-On: Id7597300cf668d7cd49213b0c799407d04c93f7b
Change-Id: I5f67637ce13a3412500ec98240c6c90dd2cda49a
Signed-off-by: Kevin Smith <kevin.smith@windriver.com>
with STX_INST_DIR changed to /usr/local in default, we need remove
the local in path, to avoid duplicated local in path.
Test:
Pass stack.sh execution with stx-nfv services enabled
Depends-On: https://review.openstack.org/#/c/649169/
Change-Id: I69b2b8d25d2f94c835154310284045fd9611af1d
Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
In nfvi_compute_api.py file, initialize() function.
We need exchange the place of action change function and state change
function below.
self._rpc_listener.add_message_handler(
nova.RPC_MESSAGE_TYPE.NOVA_SERVER_STATE_CHANGE,
nova.rpc_message_server_action_change_filter,
self.instance_action_change_handler)
self._rpc_listener.add_message_handler(
nova.RPC_MESSAGE_TYPE.NOVA_SERVER_ACTION_CHANGE,
nova.rpc_message_server_state_change_filter,
self.instance_state_change_handler)
Story: 2004812
Task: 28975
Depends-on: https://review.openstack.org/#/c/648896/
Change-Id: I22d15ee37301cf1d997625d47e517d71c7a3636e
Signed-off-by: zhipengl <zhipengs.liu@intel.com>
* Remove guest-host related code because this component has been
removed from stx-nfv repo.
* Add an environment variable "UBUNTU_BIONIC" for guest-agent
Story: 2003163
Task: 30275
Depends-On: https://review.openstack.org/#/c/648896/
Change-Id: I83e240c5bbf075dbf2f0391f3bad01d620285dc0
Signed-off-by: Yi Wang <yi.c.wang@intel.com>
nfv requires fm-rest-api, and fm-rest-api requires cgtsclient in
stx-config.
Add stx-config and cgtsclient to jobs to fix the dependency issue.
Try adding WSME in fm-rest-api setup...
Depends-On: https://review.openstack.org/649321
Depends-On: https://review.openstack.org/#/c/649169/
Change-Id: I6ee1cad6aa400f5b763a77e588da40c9332f4acd
Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
Remove guest-agent from centos_pkg_dirs.
With the StarlingX move to supporting pure upstream OpenStack, the
majority of the SDK Modules are related to functionality no longer
supported. The remaining SDK Modules will be moved to StarlingX
documentation.
Story: 2005275
Task: 30170
Change-Id: Ib21f61bfafef8497b50b94168259392ecd8a16e9
Signed-off-by: Kristine Bujold <kristine.bujold@windriver.com>
With the StarlingX move to supporting pure upstream OpenStack, the
majority of the SDK Modules are related to functionality no longer
supported. The remaining SDK Modules will be moved to StarlingX
documentation.
Story: 2005275
Task: 30205
Change-Id: Ic0365f07297f0094b46c59d0fc6a62130c681f1e
Signed-off-by: Kristine Bujold <kristine.bujold@windriver.com>
nova api proxy is built as a container and
does not need to be included in the ISO.
Story: 2004764
Task: 30106
Depends-On: Ifa0171b06e23fd77d373983d644df3f56ae4e2de
Change-Id: I97d717897d41694ff9c7e616d5d4f2fa4194c600
Signed-off-by: Al Bailey <Al.Bailey@windriver.com>
Rename stx-devstack-nfv to flock-devstack-nfv
and inherit from flock-devstack-base-min
Change-Id: Ib8aca1dcc09f489b3597daa78b60d39f3ffc54d5
Signed-off-by: Dean Troyer <dtroyer@gmail.com>
Add REST API calls to the tox unit tests and add fully
randomized tests. A few small robustness improvements
added as well.
Change-Id: Idaa6bde281989ac3442d3060750ae07f352066c7
Story: 2003857
Task: 30163
Signed-off-by: Kevin Smith <kevin.smith@windriver.com>
With the StarlingX move to supporting pure upstream OpenStack, the
majority of the SDK Modules are related to functionality no longer
supported. The remaining SDK Modules will be moved to StarlingX
documentation.
Story: 2005275
Task: 30170
Change-Id: I319937c933a493f2a5ba13523dbfee945540be1c
Signed-off-by: Kristine Bujold <kristine.bujold@windriver.com>
This update supports the migration to stable/dev build streams by
setting up the stable/dev wheels.inc and image build files.
Change-Id: I61e0cde00ae17f4530202cf86b7f75be6c418459
Story: 2005248
Task: 30104
Depends-On: Ib5dc9a7c1d8c37368d073e28d83eeb883766ee3f
Signed-off-by: Don Penney <don.penney@windriver.com>
When a host goes disabled, move the routers off of the l3 agent
of that host, distributing them amongst the other available L3 agents.
When a host goes enabled, rebalance the routers on the available
l3 agents, moving some to the newly enabled host.
Change-Id: I50fb3900ada74dd645ec38e1e681bd25ef951d54
Story: 2003857
Task: 26664
Depends-On: I710a698ebb31d48060903fb3966fa379b56ad190
Signed-off-by: Kevin Smith <kevin.smith@windriver.com>
There are scenarios (e.g. host lock) where the VIM and the
maintenance component process aspects of the operation in
parallel. The VIM also periodically audits the host state
from maintenance. This opens up a window where the VIM can
get outdated state information from maintenance and then
reverse an operation that is in progress.
The solution is to update the VIM to ignore any audit
responses for hosts that have recently changed state. The
host audit is a non-critical audit that runs approximately
once a minute to ensure the VIM's state matches the
maintenance state and there will be no harm in ignoring
audits that occur shortly after a state change.
As added robustness, the VIM is also updated to apply the
a NoExecute taint to locked hosts when the host is
disabled outside an actual lock operation. This will
catch any cases where the host flips between the enabled
and disabled states while it is locked (e.g. due to the
scenario above).
Change-Id: I228a72956a4057c768c7cea12b63d967233e556d
Closes-Bug: 1820105
Signed-off-by: Bart Wensley <barton.wensley@windriver.com>
Bart Wensley