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: I595b8c7cad7bb02486c8f0dd29fdc40789fc8e50
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_auto_name to use 'project' 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.
Remove docs requirements from lower-constraints, they are not
needed during install or test but only for docs building.
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: Ie623e7a2389c292ffc71a285f0fc2d4bb9820c3f
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: Ia47f486c79a108f6d4ffa419c59b91ad1199c718
ostestr is deprecated and projects should now be using stestr directly
for running tests.
Change-Id: Iad8911d6eb352c6e5b3b9fdcda6e9280b7efb5de
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
There are a few issues causing all gate runs to fail that are addressed
in this patch.
Update constraints to match global requirements:
There are a few local requirements that conflict with what is now in
upstream global-requirements. This updates sphinx to match the
constrained versions due to incompatibility with py2 and uncaps
jsonschema.
Update handling for falcon 2.0.0 behavior changes:
The 2.0.0 release of falcon changed the default values for two request
query parsing options that would cause failures due to unexpected
results. This sets those options to their previous defaults to maintain
compatibility across 2.0.0 and pre-2.0.0 versions of the package.
Lower constraint version raised to 1.1.0 where the options were
introduced.
There are additional integration test failures with Falcon 2.0.0 that
were due to changes in the subscription URL path.
Closes-bug: #1830903
Requirements and upper constraints not enforced in some tox targets:
The docs and api-ref tox targets were not setting the right dependencies
or the upper constraints to use for pip installs. Also updates the
constraints to the newer preferred static redirect URL maintained by the
release team.
Co-authored-by: wanghao <sxmatch1986@gmail.com>
Change-Id: I19c5363878c629a04e1be902c865ee7cea92dcd9
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
There are many references to review.openstack.org, and while the
redirect should work, we can also go ahead and fix them.
Change-Id: Ia40bcfa37709963ba84e78843ca27f153034c748
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I116cf26bfd65f0f45f64115678bc3f34d12d0d62
This adds basic framework for zaqar-status upgrade
check commands. For now it has only "check_placeholder"
check implemented.
Real checks can be added to this tool in the future.
Change-Id: I855b4b72284df308c3bb250fd3a3f0fc643b4abf
Story: 2003657
Task: 26165
openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: I115c89897b5afa687b4f4a1cea6257b5ee2419c6
This is the openstack governance goal that the config files should
be merged into one folder to make the code to be better understood
and managed.
Change-Id: I33dd85145d9f5b0384323ffa51b4d68de0aeb5b7
This commit going to remove --ignore D000 which had raised
alot of issues, such as:
- "D000 Cannot analyze code. Pygments package not found."
- Cannot check LOG which have '_' symbol in code-base.
And they also fixed in https://review.openstack.org/#/c/568729/
Change-Id: Ic5258e0262c11b9f878d867a3354aa7d1f6e67b4
Now when running functional and unit tests, if user wants
to use a custom MongoDB instance, he needs to set
two environment variables: "ZAQAR_TEST_MONGODB_URL" and
"ZAQAR_TEST_MONGODB".
Change-Id: I98fe958bfb4fb7f3913de0d0bdc2490f3b441f1b
Beginning with the Queens release, the keystone install guide
recommends running all interfaces on the same port.So this patch
updates the install guide to reflect that change.
Change-Id: I8b1c290c9dcfb721946b6052da4c14f5bf00378e
Option auth_uri from group keystone_authtoken is deprecated[1].
Use option www_authenticate_uri from group keystone_authtoken.
[1]https://review.openstack.org/#/c/508522/
Change-Id: Ieff5b69018e3824074b5a528a7b9d2a00dd7fb2e
zuulv3 has been replaced by zuul so the document should be updated
in file:
doc/source/contributor/jenkins.rst
Change-Id: I38d7b843718d5d3a6e6c3881fa3016c54913ed59
Curly quotes usually input from Chinese input method.
When read from english context, it makes some confusion.
Change-Id: I7224650e2a52e813077bb84ad3ceddb9d87f934e
According to "code conventions" [1], do not use "-y" option.
Instead, use apt-get install package, yum install package,
or zypper install package.
[1] https://docs.openstack.org/doc-contrib-guide/writing-style/
code-conventions.html
Change-Id: I58d11d0bb8976941ceda56a95112783090d211bf
This patch introduces more retry backoff function the delivery
retry policy into Zaqar. It will work when Zaqar failed to send
the notification to the subscriber. Users can define the retry
backoff function in the options of subscription or metadata
of queue.
Change-Id: I0bffd9249f8a0d466ecea1ac36d8adc37b742238
Implement: blueprint support-more-backoff-functions
Fix for typo in zaqar documentation -:
* Ref doc link - Doc Link - https://docs.openstack.org/project-install-guide/messaging/newton/verify.html
* There is typo in string "X-Auth-ToKen:
* Instead it should be "X-Auth-Token:
* This patch fixes the typo for letter k in string Token
Change-Id: I6644b2601754914166d29cf1e1af98f8e8f265e8
Closes-Bug: #1718414
Fixes the zaqar documentation
* Ref to Doc Url - URL: https://docs.openstack.org/zaqar/latest/install/install-ubuntu.html
* It is not spelled to copy the files on /etc/zaqar
* Later on it is mentioend to copy the sample policy.json file to /etc/zaqar
* Adding the root folder path for it on the string "sample file to the directory etc/zaqar/:"
* It is mentioned to make a directory but the directory name and path is missing.
* As per the above we have to create the directory "/etc/zaqar"
* This patch would update the missing folder path on the documentation.
Change-Id: Ib538857ef0abef9617d44e3f803b4bcd191bc546
Closes-Bug: #1718366
doc8 is a linter for documents and used in openstack-manuals. It is better to
enforce document linters for simple checking.
The current rules are really simple like:
- line length check (80 chars)
- new line at the end of file
- Trailing whitespace
Change-Id: I328e2b2b82739696b95eca4a4130ca347893b0dc
niuke