This is a proposal to create a new driver implementation which communicates
RPC client and server directly over HTTP without messaging queue.
Change-Id: I563e6455deca9a95f814541a7f2a6a6353b1a858
This spec introduces a local Unix socket driver to enable notifications
to be consumed on the same host where they are produced.
Change-Id: I865ec512066588a1da144548b606905a7446a436
* Remove .testr.conf as there is no tests dir and update .gitignore
accordingly
* Use 3.18.0 as the minversion for tox in order to use
allowlist_externals option
Signed-off-by: HeroicHitesh <email.hiteshkumar@gmail.com>
Change-Id: I0efdc4dd0ce658cc13c543946c6af1da867e6d4b
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I41ca7856d5900ff1805bce017ede4d08528f1e7a
A combination of factors has resulted in problems with deprecating policies.
We need to make some changes in order to allow policy deprecation without
causing pain to OpenStack deployers.
Change-Id: Ic213601b6e9406970fc5b83e53e02213ae236106
Switch to openstackdocstheme 2.2.0. Using this versions
will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Remove reno, it's not used in this repo.
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.
Set openstackdocs_auto_version to not auto-version the documents.
Depends-On: https://review.opendev.org/728938
Change-Id: If1e4ca76901ec5528969f4d7c706fc840f02562b
oslo-incubator is no longer a thing and any new library proposals
should be using the new library template anyway.
Change-Id: Ic05552e762c9e72e7cc7fc388c1a67d76c63fc5b
These changes are extracted from oslo's projects contribution guide
`CONTRIBUTING.rst`, it could be more relevant to move them here and in a
second time to remove similar sentences on oslo.*.
Centralize it here will avoid to us to send patch over ~40 projects if
updated are needed on this part in the future.
Change-Id: Ia5cd75427ab72f6fc05308c726b7523bad69c1e6
This is the first step of completing the contributor doc goal[0] from
the Ussuri cycle. It adds a contributing.rst policy which uses the
cookiecutter template created for the goal.
The expectation is that this is a central location for all of this
information, and the contributing.rst in each Oslo project will
simply refer to it so we aren't maintaining it in 40+ repos.
0: https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-contrib-docs.html
Change-Id: I3347d553b50a52ae96186e60b729360b159d8df5
There are three different templates people may need to use when
opening an oslo spec. We should explain that in the readme.
Change-Id: I720bab01196469a7759c9fa01e59c9735b12e628
Incubator hasn't been a thing for a long time now. There are no more
graduations happening, so we don't need this template.
Change-Id: Ic90eb209291db40c9fe58747bf00b6b6d67a10bd
This is a change in the previous process for handling the end of the
cycle. Before, we would do the final releases and then wait a few
weeks for the release team to branch everything. We don't need to
wait though, so let's update the policy to say that the branching
request should be done at the same time as the final releases.
Change-Id: I9ae0288bee7f9f491d964121cdfdb43787d975f4
Since Oslo is composed of a large number of repos, this seems like
the most sensible place to document our project-specific PTL details.
I expect this to be a living document that evolves as new PTLs come
up with new best practices and tips.
Change-Id: Idea654584a7f45e6567f066b2f7a3df27c51f65b
This project is not a Python project and doesn't need packaging. Remove
it.
Change-Id: Id8d3be8830908f8e7cffdccc8b8ab09690db8481
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Now that we are using gitea the contents of our README.rst are
more prominently displayed. Starting it with a "Team and repository
tags" title is a bit confusing. This change makes it start with the
name of the project instead.
Change-Id: Iad18df4b717e373250fe071de40bf60df60ac091
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: Idec07bdb441a2f30351267686f2f74888655a6df
Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
Change-Id: Iab2b9caa0f36dbe3df55622ef25f26ae66cf5480
Closes-Bug: #1831407
As far as I can tell this is actually a Keystone thing, and it
certainly isn't an Oslo policy. In talking with the Keystone team,
it sounds like this was never implemented so I propose that we
remove the spec to avoid confusion. If someone wants to resurrect
the work in the future the document will still be available in the
spec repo git history.
Change-Id: Ib07f7ad2a685b296afcdde567c07d3b7004be207
oslosphinx has been unmaintained for multiple cycles and we shouldn't
be using it anymore.
Some minor changes to the specs were necessary because the newer
sphinx introduced some warnings that were making the doc build fail.
Change-Id: I4d053e39a8859854b7f56bcf654071b7d950297b