I18n team contribute to OpenStack translations through a translation tool.
Currently it's www.transifex.com, which will be moved to an openstack infra
owned website: https://translate.openstack.org/ in Liberty release.
All the translations are saved and managed by the translation tool. At the
same time, the translated po files are committed to each project repo by
automatic jobs.
The translators contributions could be measured in translated words by the
report function in the translation tool.
Currently it's https://www.transifex.com/organization/openstack/reports/.
After it's moved to translate.openstack.org, Zanata (the new tool)
supports the translators statistics report too.
Change-Id: Ie564c1bc377b1d981259263238f71d8980acbbc7
The apps.openstack.org Web site is moving into our community
infrastructure hosting, so we need a new repo to contain its Puppet
module.
Change-Id: Iaa05177fdcdbeaed61acdc6e57c246c77949834d
Depends-On: Ia4c96d3c6ef5a9fffe587bd8b6f00748d5372f40
On the Summit we decided to rename ironic-discoverd to avoid
controversial term "discovery" which ironic-discoverd actually
does not conduct as per upstream definition.
Also proposed is new repository to split away client library
from ironic-discoverd/inspector tree.
Also notes that ironic-inspector has stable branches (named
stable/MAJ.MIN).
Change-Id: I3fed2fd7999cc7e8c81015b789d9efcebf22e770
Add new puppet module to manage phabricator to Infrastructure project.
Change-Id: I3befc49c5f2eab109c3f93234170d21799d2f4dc
Depends-On: I2faba446729aa3965549961ec495c54eca87802a
The networking-bgpvpn repository, currently in stackforge, is a Neutron service plugin
for interconnecting Neutron networks and BGP-based VPNs.
https://github.com/stackforge/networking-bgpvpn
Following discussions during the summit, the identified next-step is to move this proposal
under the Neutron "big tent" (related docs about adding repositories like this to Neutron
can be found here: https://review.openstack.org/175952 ).
The implementation is an early implementation of specifications initially proposed for
the Neutron main repo for Liberty release. The specs will move in this new project and
the implementation will be updated to reflect comments made on the spec:
https://review.openstack.org/#/c/177740/
This implementation is designed to delegate the actual implementation work to
drivers, targeting for instance such or such "SDN controller". A lightweight
implementation based on bagpipe-bgp [1] is already provided and suitable for running
CI tests.
Change-Id: I6817d63e489409edf382eba2f947f3451d9bd5fe
The TC has a subgroup working on documentation for project teams
as OpenStack grows to encompass more projects. This is a repo to
host that documentation.
Change-Id: Ib4f9934ca6d0946ca3f633f95c9336227bd6de28
Depends-On: I46292749d645f5f8e99c4f52c975c79bb446c6db
Based off JJB, grafyaml is a tool to build Grafana dashboards from yaml
files. This allows for the same automation we see with Jenkins, but for
Grafana.
Change-Id: I5d6dfe128bc7ce3c6dec798ab0748f057983f2e5
Depends-On: I91bde2c88788d3b3e65f6a28caed4d35ce45a463
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This was recently approved at:
https://review.openstack.org/#/c/141961/
So adding it to the oslo program as a new sub-project.
Change-Id: Ie2cc9a7fe12dafb3635c153c257aec9187dcf514
Feedback from operators in a user committee session pointed out which
projects a tag is applied to is one of the most useful things on each
tag's page. So move the 'application to current projects' section up in
the page so it is easier to find.
Change-Id: Ib7b0aa250f950398e0abd20d35a1ea252b057d4c
Identify Monty Taylor as the election coordinator for the M release
naming poll and establish the dates for the election.
Change-Id: I169fcb3bf488862488006b556ee4c0bbf4977101
This is a repo which the transparency committee will use to draft
proposed changes to the OpenStack Foundation Transparency Policy,
before each individual change is approved by a board vote.
See also:
http://lists.openstack.org/pipermail/transparency/2015-May/000029.html
Change-Id: Idcfa3162514fb4d02a49f20efbe43a8163f9b162
The http://ci.openstack.org/ documentation site has been deprecated,
replaced by redirects to corresponding paths within
http://docs.openstack.org/infra/ where other Project Infrastructure
documentation already resides.
Change-Id: I6998b599f48566902c291bb5543d171ebc97129f
This was recently approved at:
https://review.openstack.org/#/c/179890/
So adding it to the oslo program as a new sub-project.
Change-Id: I9ceb0da33bcfa1c51e3bec5c8c2987f206d722a0
We use UTC for timekeeping, let's acknowledge that.
Change-Id: I79aa1f08de57526c7626c34e30d08fa4102ec744
Co-Authored-By: Doug Hellmann <doug@doughellmann.com>
According to procedure defined in [1], this patch proposes Neutron
to embrace dragonflow within its fold.
Same as patches [2], [3] and [4].
Dragonflow is a L3 DVR implementation using SDN framework (Ryu)
which eliminate the need for using namespaces or local agents in the compute
node.
It uses Openflow to build packet pipeline and in the future can be used
to distribute north-south traffic and also eliminate L2 agent in compute node.
Currently Dragonflow is build on top of Neutron reference "legacy" L3 implementation
and can "fallback" to it in case of controller downtime.
(leverage current HA implementation)
[1] https://github.com/openstack/neutron/blob/master/doc/source/devref/sub_projects.rst
[2] https://review.openstack.org/#/c/179454/1
[3] https://review.openstack.org/#/c/179457/
[4] https://review.openstack.org/#/c/175954/
Change-Id: I079033207fc89b6ba3af547adda26ecaa917641c
According to procedure defined in [1], this patch proposes Neutron
to embrace networking-vsphere within its fold. This project is about
adding Neutron support to the vsphere hypervisor technology using
opensource management/control/data plane elements like OVS.
[1] https://github.com/openstack/neutron/blob/master/doc/source/devref/sub_projects.rst
Change-Id: Ia66799cda81f952c8fa244fdc23e17b9593e08ad
According to procedure defined in [1], this patch proposes Neutron
to embrace networking-l2gw within its fold. This project is about
bridging virtual deployments with physical ones, and it is implemented
leveraging OVS and OVSDB.
[1] https://github.com/openstack/neutron/blob/master/doc/source/devref/sub_projects.rst
Change-Id: I50051be2bba2460e7163903c165a158f11917729
Similar to Russell's OVN patch, the Octavia repository is a backend for
neutron's lbaas, targeted to be the new reference implementation in
Liberty.
For more information on Octavia:
https://github.com/stackforge/octavia/tree/master/doc/source
And related docs about adding repositories like this to Neutron can
be found here:
https://review.openstack.org/175952
Change-Id: If705f04986de92d386bc7f10a94a5c14eeed7697
Ran tools/validate_tags.py and update projects.yaml based on the results
* openstack/manila-ui should have the tag 'release:has-stable-branches'
* openstack/oslo.cache should not have the tag 'release:has-stable-branches'
Ignoring since oslo.cache is a new library and will have stable
branches (intent).
* openstack/pylockfile should not have the tag 'release:has-stable-branches'
* openstack/requirements should have the tag 'release:has-stable-branches'
* Trove should not have the tag 'team:diverse-affiliation'
Two organizations represent >80% (80.70%) of any of the sum of all
reviews done by core reviewers against patches submitted to any of the
git repositories managed by the team
* openstack/python-keystoneclient-kerberos should not have the tag 'release:has-stable-branches'
* openstack/python-keystoneclient-saml2 should not have the tag 'release:has-stable-branches'
* Manila should have the tag 'team:diverse-affiliation'
* openstack/os-brick should not have the tag 'release:has-stable-branches'
* Infrastructure should not have the tag 'team:diverse-affiliation'
51.32% (>50%) of reviews in past 6 months were from HP.
* openstack/congress should have the tag 'release:has-stable-branches'
* openstack/openstack-manuals should not have the tag 'release:has-stable-branches'
Ignored since has stable/juno just not Kilo
* openstack/python-openstackclient should have the tag 'release:has-stable-branches'
Raw output: http://paste.openstack.org/show/213948/
Change-Id: I4ffccbf3bd78ccc6c13ef8b8782f3f5aa5c8defe
Use stackalytics start_date option along with setting release to all to
collect data for the past 6 months.
http://stackalytics.readthedocs.org/en/latest/userdoc/api_v1.0.html
Update note at the bottom of the page to point to validate_tags now that
it is in tree and used to apply the team:diverse-affiliation tag.
Change-Id: Id60feb69704e0569873108a18a39e7787c7ab4eb
