This new NFV API will list the current running
Strategy type and its state.
Test Plan:
PASSED: On a DX system, Create a strategy of any type.
API should return the strategy type and state.
PASSED: On a DX system, there are no existing strategies.
API returns none.
PASSED: Create a Strategy of any type, use REST API
to get the current active strategy(sample output in
comments section).
PASSED: Orchestrated k8s upgrade with the changes,
(sample output in the comments section).
PASSED: Performed three consecutive k8s upgrade
v1.24.4 - v1.25.3 - v1.26.1 - v1.27.5
Story: 2011045
Task: 49580
Change-Id: I2e367ccb5f9ff42aa0d912598fb1617a4a7ae0ee
Signed-off-by: Vanathi.Selvaraju <vanathi.selvaraju@windriver.com>
This commit adds VIM orchestration for system config update to drive the
host swact/lock/unlock once these operations are expected to update the
system config.
CLI: sw-manager kube-rootca-update-strategy
apply create delete show
Test plan:
1. Create a system config udpate strategy successfully. --passed
2. Create a system config update strategy failed if the host resource
doesn't exist. --passed
3. Create a system config update strategy failed if an unexpected alarm
exists and the strategy alarm restrictions is set as strict. --passed
4. Create a system config update strategy successfully if an unexpected
alarm exists and the strategy alarm restrictions is set as relax.
--passed
5. Create a system config update strategy failed if a controller offline
in a DX system. --passed
6. Create a system config update strategy failed if a storage offline in
a standard system. --passed
7. Create a system config update strategy successfully if a worker
offline in a standard system. --passed
8. Apply a system config update strategy successfully. --passed
9. Apply a system config update strategy failed if a host failed to
lock. --passed
10. Delete a system config update strategy successful if a the strategy
is complete or failed. --passed
11. Create a system config update strategy with strategy not required
for the host in k8s, verify the host is excluded from the strategy.
Story: 2010719
Task: 47910
Change-Id: I052bc5b2004f17de870a81c523d0a1f4e422a902
Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com>
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Id78ccc70601800cb3843029f8c90350ef6571a5f
This update adds firmware update orchestration support to
the VIM for host device fpga images as described in the
'N3000 FPGA device image update orchestration' feature
specification. See https://review.opendev.org/#/c/713302/
The firmware update orchestration strategy added to the VIM
is modeled after the VIM's existing patch orchestration
and includes strategy create/apply/show/abort/delete.
The strategy can be managed through the existing sw-manager
tool via the VIM's REST API.
Only unlocked hosts with the worker function are included
in the strategy.
The strategy includes a stage for each host or group of hosts
with ordered step sequences of firmware update followed by a
lock and unlock of each updated host.
Change-Id: I4eea7ca3f00782d27cdbb5d5615c6a255ac6966e
Story: 2006740
Task: 39145
Signed-off-by: Eric MacDonald <eric.macdonald@windriver.com>
- Use updated project name in titles/text
- Correct text for link to Storyboard (docs)
- Correct capitalization in section headings
- Correct formatting for section headings
- Update project name in link to release notes, api-ref
- Update project name in config for docs/releasenotes/api-ref
Story:2007193
Task:38346
Change-Id: I15af375869bb03120fed052ecc5ce070a5581125
Signed-off-by: Kristal Dale <kristal.dale@intel.com>
doc index.rst:
1. Update intro sentence to read as a complete sentence
2. Remove unused toctree
3. Correct heading levels (impacting side nav and correct rendering of content)
4. Remove "Indices and Tables" section: genindex page not used, search searches
only index (not useful here)
api-ref index.rst:
1. Update intro sentence to read as a complete sentence
2. Update text around search link for consistency (move to follow intro)
3. Add heading before toctree for consistency with other pages
releasenotes index.rst:
1. Standardize page title reST markup
2. Remove search (make consistent with other openstack release note pages)
Change-Id: Ia12c5b865f3e4c973a7f403bbf787e7c91bf34a3
Signed-off-by: Kristal Dale <kristal.dale@intel.com>
Update misc compute references to worker
Tests Performed:
Non-containerized deployment
AIO-SX: Sanity and Nightly automated test suite
AIO-DX: Sanity and Nightly automated test suite
2+2 System: Sanity and Nightly automated test suite
2+2 System: Horizon Patch Orchestration
Kubernetes deployment:
AIO-SX: Create, delete, reboot and rebuild instances
2+2+2 System: worker nodes are unlock enable and no alarms
Story: 2004022
Task: 27013
Depends-On: https://review.openstack.org/#/c/624452/
Change-Id: I7b2de5c7202f2e86b55f5343c8d79d50e3a072a2
Signed-off-by: Tao Liu <tao.liu@windriver.com>
* Add pointers in the main doc to api-ref and releasenotes pages
* Add publish-stx-api-ref and publish-stx-releasenotes jobs
* Add search at bottom of api-ref and relnotes pages to trigger the jobs
Change-Id: If82fe40b570c43c4ac7b25e5bff5d3d72484677f
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
I added the api-ref-nfv-vim-v1.rst file, which is content for
the API reference manual to the api-ref/source dir. This
represents the converted old-style files to the newer
OpenStack supported RST files.
I updated the index.rst file to include the new .rst file
so that the api-ref document can build.
Change-Id: I8848b541a9983e63c48cbbc60fbdd42595c81655
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Baseline changes to comply with OpenStack API documentation
from OpenStack Documentation Contributor Guide [0]:
- [1] How to document your OpenStack API service
- Add SPDX-License-Identifier: Apache-2.0
[0] https://docs.openstack.org/doc-contrib-guide
[1] https://docs.openstack.org/doc-contrib-guide/api-guides.html
Story: 2002712
Task: 26671
Change-Id: Ia16194f531328f2e936b296a489b936b384addb5
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
Vanathi.Selvaraju