It seems that "supports-upgrade" is the standard tag but Fuel
used a misspelled version of that assertion "supports-upgrades"
Change-Id: I0312302387cc1a1c0019ca75cf4bd6c26aa2a132
Add repo group 'fuel-lcm' under the Fuel project.
Add repositories fuel-octane and tuning-box to
fuel-lcm group.
Move repository fuel-upgrade under fuel-lcm group.
Change-Id: I6e78aa205591dd673968f887d24d834cb98a2dec
Depends-on: I6de0d46be49de9e2453df8aa2fefc8bd605029a4
Blueprint: serialized-facts-nailgun-api
The new horizon panels have not shipped yet, and bundling them
in with neutron, when it's just a neutron api consumer, doesn't
seem to quite make sense to me. Add it with octavia, the reference
for lbaas.
Change-Id: I0ee9e7a60a8c92d8f70e61d62fb69af678eb803e
networking-ovn is a project part of OpenStack Neutron:
http://docs.openstack.org/developer/networking-ovn/readme.html
"OVN provides virtual networking for Open vSwitch and is a component of
the Open vSwitch project. This project provides integration between
OpenStack Neutron and OVN."
Red Hat started to work on a Puppet module that installs & configures OVN
services, on top of Open-vSwitch:
https://github.com/redhat-cip/puppet-ovn
We would like to move it to OpenStack under Puppet OpenStack tent.
Why not deploying OVN with puppet-vswitch?
OVN is a part of the OVS project. It's even in the same git repo as OVS
right now.
OVN consists of some new daemons and databases. It's optional components
that you may enable on top of OVS.
But openstack/puppet-vswitch abstracts away the vswitch details in its
interface, so puppet-ovn would likely consume puppet-vswitch.
Change-Id: Idd8dc346b8368c926a5f2fc5c2cc8c34376f30f5
Neill has significantly co-authored a few patches, but my
understanding is that solely being listed as a co-author will not
grant ATC status. I think Neill's contributions are significant to
warrant ATC status in Horizon.
Change-Id: Iac91fa56dcce900111d6a81b1b5451c61b6c0160
This has the advantage of including the service type in the list of projects
which gives readers some extra context in an otherwise potentially bewildering
list of names.
Change-Id: Icf6a644d283368f957b978fa4321800d15f38f3e
Denis Cavalcante worked on the install guide for Manila
and deserves to be recognized as part of the community.
Change-Id: Ib94af359f770a97092ec52349d523b1ee554c059
See-Also: I686bdda2ee27de4e5c43bb8d95c0126c8c300558
Congrats to Congress, Release management, Telemetry,
Infrastructure, OpenStackAnsible and Freezer for having
increased the diversity of affiliations in their teams !
Change-Id: Icdc08c126d5ecf86bfbc2f6f62304c21e1010d3e
Horizon plug-ins, while technically delivered as a Python
"library", are not considered a library as far as release
management deadlines are concerned. A few of them still
had the type:library tag, though, so let's fix that.
NB: we may want to introduce a type:horizon-plugin tag at
some point to designate those.
Change-Id: Idedf14a488372d7c2d4120f0637af7b05938b0b8
This adjusts the Mistral and Designate deliverables contents
to match how they are actually released:
openstack/mistral-dashboard and openstack/mistral-extra are
released as part of the general "mistral" deliverable:
https://review.openstack.org/#/c/287690/
openstack/designate-dashboard is released as part of the
general "designate" deliverable:
https://review.openstack.org/#/c/287736
Change-Id: Ic0baae6470601bffa240a58968eb11a0a417fb88
This project has been mostly abandoned, and as such likely won't be
getting any releases. Drop it from ironic deliverable list to indicate
this.
Change-Id: Idbf06758cba50c8cfcc1f8fa785f8bbb6651d286
django-openstack-auth-kerberos is a stable plugin for
django_openstack_auth it will be updated infrequently.
independent is a better fitting release model rather
than the present cycle-with-intermediary. Additionally,
the use of stable-branches is unnecessary.
Change-Id: Icf398bfa848805f95f8fa85da0861e243e4105e8
This patch updates governance for new repositories implemented
in the OpenStack-Ansible Project which implement the remaining
OpenStack projects currently supported.
Change-Id: I3f209979e965f21c021a8c4dedbe76270307b9cb
Depends-On: I791d6c7721ed1e7ca2ae8631699fca24a1f917cf