The Host Hardware Profiles for creating re-usable configuration
templates for hosts are no longer maintained or supported and should be
removed from code. Including : CPU, Interface, Storage and Memory
profiles.
profile categories:
* cpu
* memory
* storage
* interfaces
topics:
* remove objects
* update models
* update documentation
* remove import/export profile apis
* remove and update unit tests
* new version script for migration upgrade
Test Plan / Failure Path:
PASS: Verify profile feature is removed on system upgrade
without existing previous profiles.
PASS: Verify profile feature is removed on system upgrade
with existing previous profiles.
PASS: Verify profile feature is removed on fresh install.
Regression:
PASS: Verify that the Horizon GUI remains navigable.
PASS: Verify non-affected system commands remains listed.
Story: 2009163
Task: 43159
Signed-off-by: Pablo Bovina <pablo.bovina@windriver.com>
Depends-On: https://review.opendev.org/c/starlingx/config/+/806800
Change-Id: Id828365920ce179e347acf0de5d3ed6af09efcbd
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: I952b87de1d14b9c83dd0d7df8ab5d2ed0b30c555
- 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:38336
Change-Id: Ia01582558ab27accb68ccdf00d492f5e79689f04
Signed-off-by: Kristal Dale <kristal.dale@intel.com>
Update conf.py for release notes to include the project
variable, set to the project name. This is so the string
above the left nav renders the project name.
Story: 2004900
Task: 29225
Change-Id: I845a1f1ca9c1e19db075a8e5a3cfaf3a4a8eba01
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
release notes:
1. Standardize page title reST markup
2. Remove search (make consistent with other openstack release note pages)
Change-Id: I0bbd0812f4f2132193724feb9b18910389dc85f4
Signed-off-by: Kristal Dale <kristal.dale@intel.com>
Rewrote various areas for better presentation and use of
grammar.
Change-Id: I4a96b9896aced0c62b93a4e4c61bbd8d69d1ffd7
Signed-off-by: Scott Rifenbark <srifenbark@gmail.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: I6286efb94cab686c978b9d3924bcd621250107f6
Signed-off-by: Dean Troyer <dtroyer@gmail.com>
Also set the theme to alabaster until starlingxdocs is ready
Change-Id: I538f2f6ceda9b4401308b3daf9722ffe2e64cf11
Signed-off-by: Dean Troyer <dtroyer@gmail.com>
Baseline changes to comply with Release Notes Management
based in Reno [0]:
* Use build-openstack-releasenotes job for release notes
(We can't use the OpenStack releasenotes template as it includes
publish jobs, stx needs its own)
* Add newnote tox environment as convenience for creating new release
notes, re-using the releasenotes venv.
* Remove the unused 'true' tox environment if it exists.
[0] https://docs.openstack.org/reno/latest/
Story: 2003101
Task: 26514
Change-Id: I7fda1f84d336940dc8851eb053d451981e36bf4d
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
Pablo Bovina