As discussed in the upstream meeting, update the placement bug tracker,
link from storyboard to launchpad, so new bugs should be reported in
launchpad instead storyboad.
Whats not updated:
- all links of storyboard which do not point to bugs
- links of existing stories, features, docs etc
Change-Id: I64b9d6feb4fb35f36c5a290b8b79d9b78736efd2
We made a mistake and not added resource_providers.can_host to the new
DB schema of Placement when Placement was split out of Nova. This patch
documents that as can_host is not in the DB model it is safe to drop it
from the DB to remove the schema inconsistency.
Related-Bug: #1978549
Change-Id: Icfe83313e86969b0b9d34c19b6b82a47d685d4d7
The new microversion adds support for the ``in:`` syntax in the ``required``
query parameter in the ``GET /resource_providers`` API as well as to the
``required`` and ``requiredN`` query params of the
``GET /allocation_candidates`` API. Also adds support for repeating the
``required`` and ``requiredN`` parameters in the respective APIs. So
required=in:T3,T4&required=T1,!T2
is supported and it means T1 and not T2 and (T3 or T4).
Story: 2005345
Story: 2005346
Change-Id: I66543c0c5509739d1461af2fb2c327a003202d74
This is a reproposal of a nova spec to placement, originally
proposed in I9695f0cb2c0263cd0e8ca552d3a9dd720690e466.
Previously-Approved: Stein
Story: 2005345
Task: 30295
Change-Id: Ibada21dcabbb3824c8d9fdb7584d45abf844be68
This is a reproposal of a nova spec to placement, originally
proposed in I57c5611d7443070c176d213118857261b37eca0c
Change-Id: I0e47b654d5bdae1125737cf54d9c301bdba3236f
Previously-Approved: Stein
Story: 2005346
Task: 30296
Mistakenly the computing team merged two specs in nova that actually
targeting the placement service. Placement has its own specs directory
to store these. So this patch adds the these specs to the placement
repository.
The only change in the two specifications compared the ones approved in
nova-specs repository is the removal of the note from the top that they
are targeting placement service as it is now obvious.
Change-Id: Ie0d4df94ae16de60394438878e5a1568e29e03a5
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: Ia7365cc3ae09e2ff916ab9f9ff0ba4fef0dc446b
[placement]/policy_file config option is deprecated since Train
release in favor of ``[oslo_policy]/policy_file`` config option.
In wallaby cycle, default value of ``[oslo_policy]/policy_file``
is going to change to 'policy.yaml' so it is better to remove
the old deprecated config option to avoid confusion for operator.
Change-Id: I427f1f5a82dc1b2e27fa29b68db9ab549df92289
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.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
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: I4e3fe772adffbd70d55ce1b73d9161a6de5b9c11
The --skip-locks flag can be used along with --migrate in
deployments where table locking operations can't be performed.
For example, Percona XtraDB Cluster only has experimental support
for explicit table locking operations and attempts to use locking
will result in errors when PXC Strict Mode is set to ENFORCING.
Change-Id: I3df5686d13c1ce0cc38402a1317acb661ad74cec
Story: #2006670
Commit 3f1a89c7dd changed most of the
install docs to use "Default" instead of "default" for project/user
domain names according to the keystone docs, but the install doc for
PyPI has been missed. This patch fixes it accordingly.
Change-Id: I2e92730ff5819bf49cf1b286356870fdb9c6ece5
Story: #2006652
Task: #36894
This reminds people that they must first switch to Stein extracted
placement and explains the upgrade status and db sync steps.
Change-Id: I1383e845aaa7caf15b0e2f36038b4b612cffca5b
The contibutor document had subpages section on the top, but it was
weird (especially in pdf) that subpages were before sections of
"overview" and "big picture".
This patch sorts it out creating a new section of "architecture".
Change-Id: Iea2307774e7f6f778c72f5b07b526fad18dc4cc5
In the top index page of the document, some sections had actual
contents and some had only links to the contents. However, this
makes it difficult for readers to get what is in the document and
what isn't at a glance.
This patch cleans it up to simplify the top index. This patch also
renames some of the directories to follow the doc layout rules[1].
[1] https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
Note that the following ToDo is left for further cleanup:
* Publish the api guide and move the microversion history to
the `/api-guide` directory
Change-Id: Ideb1d5e7c74d1d564d07bac1a1e7c86c55ede873
In the document source, we had a hidden toctree to avoid an error
when creating an html document. However, the contents in the hidden
toctree appears explicitly as actual subsections. This resulted in
having wrong subsection structures when creating a pdf document.
This patch fixes it by adding explicit sections for the contents
in the (previously) hidden toctree.
Change-Id: I8420835c19856953c65513914362bf402ff0f08b
Story: 2006110
Task: 35398
This follows the instructions [1] in an attempt to build pdf docs.
Several doc/source/conf.py changes are required to get this to work.
The most important one is
'maxlistdepth': '10',
which prevents the build process from stalling out and dropping the
caller into an interactive session.
[1] https://etherpad.openstack.org/p/train-pdf-support-goal
Change-Id: Icf7c22bf9d1de6fb2a74a756c370930d4c00b0b9
Story: 2006110
Task: 35398
root_member_of was not implemented (as we thought it might not be).
The spec is updated to make this explicit.
Change-Id: I2a60bff04b0837bcac7037d766c675ef3896692f
The migration scripts have moved, gitea doesn't handle the redirects
properly, so update the links to point to the correct locations
directly.
Change-Id: I73a47c862606fa27158e0b7af9f111b5df8a065d
Sphinx 2.2.0 gets upset when a directory it is configured for does
not exist.
The _static directory is only used for automatically generated
configuration and policy sample files.
Change-Id: I5ee07a2cb118e5c9b16aefee73c9274ecace1d44
The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: Iccddd4356b5d7c28977ad954654d0875972dae97
This patch adds usage documents for the new `same_subtree` queryparam
in `Modeling with Provider Trees` page.
Change-Id: I52a48692aa7069eb16ce4f078cc671fe38728729
Story: 2005575
Task: 30784
Use whereto to test that the redirect rules do what we expect.
Change-Id: Id3a8f3b9f372ebe9176f1df917f7a6aac30a8e92
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Forbidden aggregates was added in microversion 1.32 (part of Train)
and allocation candidates mappings was added in 1.34 so those specs
have been moved to implemented.
An _extra/.htaccess is added to redirect the approved spec to the
implemented spec. If we're experiencing enough volume of specs to
warrant automating this, it should be easy to do, but at this point
we don't have, nor intend to have, large numbers of specs.
While doing that I noticed the management of spec documents can be
simplified somewhat by moving placeholders and templates to a
non-release specific location. The placeholder can then be used
as a symlink when in approved or implemented when those are first
created or otherwise empty (an empty directory when doing a table of
contents glob is an error so some kind of file is needed).
Contribution docs are updated to reflect the location of the
template.rst file. The template.rst file is updated to be release
generic.
Change-Id: Icb886d5062a52bfc757ed7bbe36ed8a63abe1387
fprzewozn