Ceph credentials should be the same across all nova-compute charm apps
to allow live-migration of VMs booted from image (and stored in ceph
via use of libvirt-image-backend=rbd config) to succeed.
Related-bug: #2028559
Change-Id: If73469af2a372c0afbdbf338677782d475fd02e2
File "/.../charm-specs/doc/source/redirect.py",
line 24, in process_redirect_file
parent_path = path.replace(app.builder.srcdir, app.builder.outdir)
TypeError: replace() argument 1 must be str, not _StrPath
Change-Id: Id650151fcb2d4832afc5a196636ad584aa04d0ef
This spec proposes a new, better, but alternative means for maintaining
and releasing OpenStack charms in a world with a new charm store
(charmhub.io) which provides richer mechanisms for charm delivery.
Change-Id: If5719ad54c52d46dc001da4df91caa4b00af256f
The Ceph Dashboard should be available for enablement and configuration
as a new subordinate charm, mainly intended to be used with the ceph-mon charm.
Change-Id: I36984386fd029478e7a213d5acd04c453d27f7b4
Move Victoria approved spces to implemented.
Move anything else ahead to Wallaby backlog.
Fix minor lint in ceph-benchmarking and cinder-ceph-replication
specs.
Change-Id: I49027bdbf23ef2a498fd1f2b3bf1b1770544f8f8
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
Switch to openstackdocstheme 2.2.1 version. Using
this version 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: I0b21a468b8952c6189764b8f17bb2ffc057aefec
Switch to "modern" way of docs building in OpenStack:
* Use sphinx-build
* Use openstackdocstheme instead of old oslosphinx
* Adjust settings for openstackdocstheme
* Fix build errors:
- There's no priorities folder in this repo,
so remove non-existing links.
- There's no backlog file, remove link.
- remove links in specs that don't exist
- fix RST link formatting
- Fix RST errors
Change-Id: I0d1d1c866957e7dbd5d4e394b0368a0a5250b00b
Carry forward any backlog specs to Ussuri.
Carry forward any approved but still inflight specs to Ussuri.
Move implemented specs for Train to implemented folder.
Misc tidy of line lengths and missing titles in a couple of specs.
Run unit tests in gate under Python 3.
Change-Id: I23a8823568f1ac594982a37095f3e1c532b5ab53
Our feature delivery planning process revolves around specs and
we rarely use blueprints anymore. Remove reference to blueprints
from the documentation.
Change-Id: I818b26188958212dca7397f47c03433b9978d694
Mark any queens specs that have been implemented.
Move queens/{approved,backlog} -> rocky
Tidy misc formatting issues which for some reason managed
to get through gate checks.
Change-Id: Ib37f5cc45ae4f745e7beb7d39743e69d79e1323f
Tidy specs from Ocata, create directories for Pike and
move over un-implemented specs from Ocata to Pike backlog.
Change-Id: I6da093f8d1a7f0d12fd564ea758f32cdfcd260bf
Review and mark as implemented specs in Newton.
Move unimplemented specs to Ocata backlog or approved.
Setup for Ocata aligned specs.
Change-Id: I7008085871e3418cff0887e63cb8037b8ffdccb9
Rodrigo Barbieri