This update clarifies some of the implementation
details that were being questioned. This may require
more detail going forward.
Change-Id: Ia9d6eb06717dee013deff3a050ba8f09301957be
This more-accurately reflects the realities that:
- the primary developers for these projects are Swift developers and
- the primary consumer of these projects is Swift
Change-Id: I333393e0304844e30983f89c82eabcad11487be2
We don't currently do any linting at all for the legacy projects,
this patch adds some basic linting.
Change-Id: If1173779525d0c247b3d3367f0e14de27ad2985e
This is to:
1. Remove the dead cross-project specification-liaison team link
2. Fix the inaccurate support phases link.
Change-Id: Iefab661bbc2aff4118b7f21708bae5fda45b3f2f
Charm-vault has been an official member of the OpenStack Charms
project for some time, but was left out of governance in the past
for a few reasons. These reasons have recently been re-evaluated
by the team and the conclusion has been to include this charm in
governance.
Change-Id: I5b147d2845d27d982c97abf18275fcff798a516d
When running tox, it creates the .eggs folder and leaves the repo
reporting that it's in a non-clean state.
Change-Id: If09fda47af1be8bd34434d82e31a4b7fb7d86e83
Update the nodeJS version that we should use for javascript based testing
in openstack.
Change-Id: I1a594acc8f430c95d3a32f767e5508d0fcc65ac9
Signed-off-by: Graham Hayes <gr@ham.ie>
If there is a project-update change where we have a -1 code review,
we should probably put that into account as it might mean that it's
not the good time to land it.
Change-Id: If95af41005a0b328ffbda74f6b56b00d68a98eea
The infrastructure team no longer runs a cloud, therefore, let's
update the documentation appropriately.
Change-Id: I74d0465f61277d03d9f95fcbf1446c407a7e4728
The original IPv6 community goal is laudable, but misleading. It
behooves us to avoid incorrectly implying that we lack solid IPv6
support. We've provided solutions for IPv6 connectivity to user
resources for a very long time and even have users successfully
deploying OpenStack environments with IPv6 control planes. What we
can't demonstrate with confidence yet is that OpenStack is usable in
IPv6-only environments (those with no traditional IPv4 addressing),
so we should clarify that the goal is about taking that next step.
Change-Id: Ic657850a06ec70dedf153ac754cfa707dbee2b90