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
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
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
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
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
openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: I233aface881d38953244c40d3a871fbe4947ab2b
Use a Secret Management Store to
protect plaintext values in the
OpenStack Services.
Change-Id: Ib2811960b40fe56ac09a48ac4c7658ffb9ee78b9
Implements: bp protect-plaintext-passwords
This spec outlines this mechanism to generate
new suitable config file for new release automatically.
This is our presentation related to this topic [1].
Patch set code: I0a14a4a462e04e485049c9b8c40a7a01e4cdab88
Co-Authored-By: Nam Nguyen Hoai <namnh@vn.fujitsu.com>
[1] https://www.openstack.org/summit/sydney-2017/summit-schedule/events/19296/
Change-Id: I851628c095cd75e0694a7886e222f3a2202ee961
The spec proposes a model for getting configuration/option
settings/values from environment variables in the execution
environment.
blueprint config-from-environment
Change-Id: I56acd64a29dc4eb1c4aeb82669b537efedcbe556
The feature freeze policy has fallen somewhat out of date due to
changes in the OpenStack release process and in Oslo itself. This
updates the policy to better reflect the current state of releases.
Change-Id: Ie6637a3eeaa9e04acc86e25b3c1f0b8dcb68a2a5
Apparently pip 10 dropped the options for allowing external and
insecure packages. We shouldn't need those anyway.
Remove the index pages within each series directory, since the specs are
linked using a glob pattern in the main table of contents. This removes
all of the "$series Release" entries from the main table of contents.
Add the rocky directory specs to the master toctree
Change-Id: Ic8714c42f31a98020dfb70e65e9b2d9240fcf41b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This change explains the reasoning behind creating a new library to
help other services consume unified limit information in keystone.
Change-Id: Idcc719a5c92f865eabae76dd0b40c327380238b8