This patch formally creates a separate Placement project. It started out
as a sub-project of Nova, but the plan all along was to eventually have
it exist on its own.
Change-Id: I53be2614fe19aa27f47a1dd9901a21d691386db6
Ensure that the charter rule that formal-vote items stay open at least
7 days is applied. This change interprets that rule to mean that if
the majority votes in favor of a change within the 7 day period, the 3
day waiting period will include any of the remaining 7 days. So if the
majority is reached on day 1, the patch must stay open 7 days and if
the majority is reached on day 7 the patch must stay open an
additional 3 days.
Change-Id: I48841570ff19b779b2e35de8218a8f56b408df92
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
openstack-dev was still listed, must have been missed somewhere
along the way. This corrects it to openstack-discuss.
Change-Id: I12486244c8507a943ef039443bb36b5f3518dc28
We'll miss you but it's ok, we got you replaced by something cooler.
Depends-On: I96556f82182a6d147e20bfac6debf361309f2038
Change-Id: Ibd4020c0ec347afd372ab54ed139ff2414ba0a87
When the Ubuntu and CentOS were added in the PTI as "supported
distros", SUSE was already one of the most-popular distros [1],
and therefore deserves listing here.
I don't believe the PTI should refer to "popular" term for distros,
as this isn't a popularity contest. Instead, we should allow any
distribution where community effort is provided.
In this case, openSUSE images are present in infra, and SUSE contributors
are using devstack on openSUSE. Next to that, deployment projects like
openstack-ansible or openstack-helm are making use of openSUSE.
Last, but not least, some projects already take into account openSUSE
in their regular work (for example, when the nova team contacts the
distributions at the beginning of the cycle to know their latest
supported libvirt [2]).
I believe all these arguments are enough to warrant the addition of
openSUSE in the list of distributions.
[1]: SUSE was ranked 4th in that survey (with SLES), after RHEL (3rd).
[2]: http://lists.openstack.org/pipermail/openstack-dev/2018-September/135007.html
Change-Id: I1ac3b7477b5d4cb4af75c319b4232d20b4b4b284
This patch aims to add os_mistral to the OpenStack-Ansible
project.
Depends-On: Ic5cab9cfbdc7b396d23d836224e38ffb5e3af3ba
Change-Id: I82d372d7b93e87c41531f6483473ed223b2058f8
According to zaneb on IRC:
"I'm not sure what heat-cfnclient is still used for...
I suspect just testing. It's in the openstack-dev namespace.
If it's never been released I wouldn't start now..."
Change-Id: Ia6981a5a52a4eaec46b9bf398a063ef6f0ab6cd4
Feedback on this section from a couple of different sources reveals that
the current description fails to make clear that the design goals
represent capabilities that we want OpenStack to present to
applications, and aren't necessarily descriptive of the OpenStack
service implementations themselves. Tweak the wording to help readers
interpret the goals in the correct context.
Change-Id: I5e2fe12dca016f0e9039cdf4290060ed51bc10ce
This patch adds two Ansible roles used to manage client software for
Hardware Security Modules (HSMs). These roles are used in TripleO
to install HSM client software on controller nodes to enable the
PKCS#11 backend for Barbican.
Change-Id: I9195626ea987606400f2e68bfe43ab917b4191dd
Depends-On: Ifd7a46da84fb81eeff7ce2e935cc39007dddbf76
This was the intent when the repo was imported in
I96f3600b32ca87ffbcac45f44238ba515ed0bccb but the governance change
was not proposed.
Change-Id: I70df74bc0fb78d0acddbd434995bb4bae8b65d35
The Election repo need to collect governance data at a specific tag.
Allow this for remote (governance) repos. We don't need to do this for
a local (governance) review as we can just ``git checkout`` the tag.
Change-Id: Ib94d5f0c3df8538af753b3b46c6a11ceff8fef53
Those modules were part of an angular transition that was never
completed. Ignore them in release management, until they are
fully retired.
Change-Id: I55859dfadf56477f05b81d174225f4215c04f496
django_openstack_auth's function was merged into other deliverables,
so it is no longer released, but the repository is still kept
around for maintained branches.
Mark it as release-management:deprecated so that we no longer
expect (or track the absence of) any release for it.
Change-Id: I5c98446c6ba9c745e30ff3f1ab0485b1a8154dd1
As discussed at the Technical Vision session at the OpenStack Forum
in Berlin, make sure the interoperability guidance in the vision
calls out avoiding leakage of backend implementation details and
configuration choices into the end user experience (particularly
when it comes to altering API methods and their behaviors).
Change-Id: Ib15f7c20b4fc3f85dd90172373175b2b179d492e
Helping the TC stay up to date with the board's work is just as
important as helping the board stay up to date with the TC's work.
Change-Id: I2326e1e304600350d295c41ff78787d2c83cdd1b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
In Sphinx, it seems not possible to map a named link to a :ref:
object, so just directly embed it into the prose instead. This fixes
a 404 in the rendered version of the site. Thanks to n00balert in
the #openstack IRC channel for pointing this out.
Change-Id: Ice4d8235209645ca5ad1bb62906edbc72f793861
