This patch adds a pre-developed Zaqar service role from
Github into the OpenStack-Ansible set of roles.
Governance Review: https://review.openstack.org/292335
Change-Id: Ibcec58212bf02e53034979f76421933d07a9de43
This patch adds a pre-developed Designate service role from
Github into the OpenStack-Ansible set of roles.
Governance Review: https://review.openstack.org/292335
Change-Id: Icd3810574b72f98da8f51c26e46c527bdd89680b
The Synergy project extends OpenStack capabilities by providing new
functionalities, such as a new scheduler.
The Synergy project is built around a core service and pluggable extensions
called managers.
In this commit we add:
- synergy-scheduler-manager: the main Synergy manager. It provides new
scheduling mechanisms for OpenStack. It uses a fairshare algorithm that aims
to maximize the overall resource usage.
- synergy-service: the core service needed by the aforementioned manager to
interoperate with OpenStack.
Change-Id: I5c2be2c7c3330b4fcd24a3a55990985f3f28e048
Performa is distributed scenario runner, results processor and
report generator. It is designed to be a default tool for executing
test plans from performance-docs.
Change-Id: I326fb0194f1ec3e275e9292722fc954be868b401
By default if patch with Closes-Bug tag gets merged, bot changes bug
status to Fix Released.
We need a 'delay-release' option, so that bug will be moved to Fix
Commited state and then will be verified manually.
Change-Id: I90ced5a0643eaf9b9a2c2df530c25ed3b098c4a7
The charm-* projects currently have a release cadence of every
3 months. Current consumers of these projects are used to
following the bug status (e.g. Fix Committed/Fix Released)
in order to determine when fixes are available and injested in
the Charm Store itself.
Update options for all charm-* projects to specify they use
a delay-release model.
Change-Id: I708b1b67cde3a87efbf1d86adc52a3a8c83042b8
python-tackerclient has a separate LP account. So avoid placing
tackerclient into main tacker group. Change references to tacker
project name to be consistent.
Change-Id: I7d883ba225cfb0f47e6cde04f2090cf8f5d4cb2c
It looks like manila-image-elements was setup to inherit
ACLs from manila, but unlike the manila project,
manila-image-elements is not release managed and does not
have stable branches. Tagging should be done by the
manila-release group rather than the formal release process.
Change-Id: I5402978a9c95d58f8e1a62b732ce92234a2bcd5b
Add a glance-reviewbot group with permission to abandon changes or
mark them work in progress (workflow -1). This will be used by the
Glance team's "glancebot" account to service their stale change
review policy.
Change-Id: I7879496be316aae7c4c5a66b3fdbdc83e730a871
IoTronic is an Internet of Things resource management service for OpenStack clouds.
In this commit, we add the iotronic conductor and REST API dealing with registration, removal, listing, and detailing of IoT resources.
Change-Id: I913c6e6dda6b98701a2a20d72760afffff799db6
Puppet OpenStack team expressed the need to have a puppet-neutron-core
Gerrit group to manage puppet-neutron project, where some people
highly involved in this project would be in.
Change-Id: Idcda97be3457341450c84f17f0fd31371177f6f2
The bug tracker for the OpenStack charms is part of the 'charms'
distro on launchpad - as a result the bug_target_name used by
jeepyb to determine bug closure is of the format:
<charm-name> (Juju Charms Collection)
Update groups for all charm-* projects so that bug comments and
closure work.
Change-Id: If171161b70e7c6ced76e79f391e430a817afef03
- Allow create branches, push tags for Fuel release
- Allow put the verified for fuel-ci bot
- Require Opnestack CLA as we moved the Noop framework's code and
docs in the repo as well
Change-Id: I51abdfa7a6ef2054994b23afc2ce9dc811b4fe89
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>