Make sure that the deliverables in legacy.yaml are all associative
arrays, just like in projects.yaml.
Also merge the earlier openstack/shotgun and openstack/fuel-mirror
repos into the later fuel deliverable retirement, and earlier
openstack/fuel-upgrade repo into the later fuel-lcm deliverable
retirement. The legacy.yaml schema doesn't lend itself to tracking
partial retirement of deliverables (further suggesting that the
model of multiple repos to a single deliverable is misaligned with
how the community operates). Add comments for the repos from the
previous partial entries indicating their effective retirement dates
for posterity, as the current data model does not provide a clean
solution for tracking them.
Change-Id: I7ca3c9294d325085ce9139f3a86b55e5b31c79c7
Add the new Gnocchi charm and supporting charm interfaces to
the OpenStack Charms project.
Change-Id: I8029883cabe875060487e0a731d3c3f44af645dc
Depends-On: Ibcb7ebd25ed5f646aaf1323beeb9acc87a8d07f6
In the Pike document structure installguide
is merged into the doc folder and handled by the
project cookiecutter [1].
There is no need for an installguide specific
cookiecutter anymore.
[1]: https://review.openstack.org/#/c/482504/
Change-Id: I25ea1338bdc2ed652b550a7dccdf64cc53aab9ed
Signed-off-by: csatari <gergely.csatari@nokia.com>
This updates the numbers on unit tests and adds the
completion artifact for nova, which I'm going to say
is when gate-tempest-dsvm-py35-ubuntu-xenial was
made voting.
Change-Id: Ia5ddf501a52851311c97e8c3adb93612014303ee
Octavia completed this work as part of our new API endpoint in Pike.
This patch provides the links to the final patch in the chain implementing
the goal and the associated documentation.
Change-Id: Ifc6f5369ba4e3e53f351635c1ba88b76167d739e
Those people are OpenStack Foundation members and also
active translators from 2017-01-06 to 2017-06-30.
The name list was made by querying Zanata translators statistic API
and Foundation membership was validated with
openstackid-resources.openstack.org REST API.
It is necessary to grant those people ATCs in order to make them
voters for PTL in I18n as APCs and TC seats.
Note that detail stats are available at
: https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics
Change-Id: I8ede84492685c6963ccd7823a3fa33c401f48f80
The deb-mistral-dashboard deliverable was added to the Packaging-Deb
team at its inception via I73b64c4bc0497a1d42b6308a038daabab258ede8
but the repository openstack/deb-mistral-dashboard does not and has
never existed nor is there any open change to create it. Remove the
deliverable.
Change-Id: I0feca731ee0c99c3cd5f170ce4da21524236b53e
Add new charm deployment guide for the OpenStack Charms
project.
Change-Id: I2307f9bfa39c92422bad8ca94917d5be414c5b61
Depends-On: Ic48e3e6a487303fdd126501206ab76d69e6801fa
The os_tacker repository is now curated by the OpenStack-Ansible
community.
Change-Id: I6e594309b3e62597e08f56dfe793b3eaa6c2598a
Depends-On: I111d829c0a4ee698d5f927972f1d3c5e6cda5819
Mention that Lance Bragstad and Chandan Kumar each volunteered
to champion one of the Queens goals. Many thanks to them !
Change-Id: Iec144867681654db26beb8a851cb2dcd39fc8ad7
The mission of Blazar project[1] is to provide resource reservations
in OpenStack clouds for virtual resouces and physical resources.
Blazar ensures cloud users can deploy their resources during specific time
frames, using reservations. Blazar creates reservations when it recieves
requests from cloud users about future usages of resources. It finds
out if the clouds can accommodate the usage requests in the reservation
time frame. A request can define reservations of various kinds of
resources, such as virtual resources (Nova instances or Cinder volumes)
as well as physical resources (Nova hypervisor or Cinder storage).
The features of Blazar are interesting varied kind of OpenStack clouds users,
such as Scientific WGs and Enterprise as well as OPNFV Promise. The active
team members are coming from each area, and its development cycle is
neutral for all area. Additionally, Blazar tends to solve some problems
described in the user story[2] defined by the Product WGs.
The development cycle of the team is following OpenStack patterns.
The team think operator feedbacks are much important to improve Blazar
project and its community. So the priorities for each cycle have been
decided based on not only development requests but operator feedbacks.
The Blazar code is not implemented from scratch by the current active
members. Blazar project was founded at the Icehouse cycle, but inactive
between Kilo and Newton. At Barcelona Summit, the current members,
some are the real users of Blazar in production and others are operators
of NFV who need Blazar, gathered and started to revive Blazar project.
Blazar project and the team follow the 4 opens:
* Open Source:
The Blazar source code[3], specifications[4] and documentation[5] are
completely open source. All are released under the Apache 2.0 licence.
* Open Design:
The team openly works for all activities. For release milestones, the team
discussed problems Blazar was facing, work items the team was targeting,
and project's priorities in etherpad[6], [7]. Additionally, the team had
meetings in both PTG[7] and Boston Summit[8].
* Open Development:
All Blazar code is reviewed and hosted in OpenStack CI[9]. The CI
supports unit tests and Tempest scenario test. All blueprint and bugs
are tracked by Launchpad[10].
* Open Community:
All new design and bugs are open in Blazar Launchpad[10]. The team
weekly IRC meeting[11] is held in a IRC channel for OpenStack projects
and #openstack-blazar channel is open to everyone who want to discuss
Blazar-related topics.
1. https://wiki.openstack.org/wiki/Blazar
2. http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/capacity_management.html
3. https://github.com/openstack/blazar
4. https://github.com/openstack/blazar/tree/master/doc/source/devref
5. http://blazar.readthedocs.io/en/latest/
6. https://etherpad.openstack.org/p/Blazar_status_2016
7. https://etherpad.openstack.org/p/blazar-ptg-pike
8. https://etherpad.openstack.org/p/blazar-boston-summit
9. https://review.openstack.org/#/q/status:open+blazar
10. https://launchpad.net/blazar
11. http://eavesdrop.openstack.org/#Blazar_Team_Meeting
Change-Id: I7473dc15b553195dbbe2665ade9ecf6a8bc21839
We want to make it clear that the vision document is a point-in-time
document, and not meant to be updated as a living document. We will
produce new visions in the future.
Change-Id: I34117506468a78c42968acc8dacb7bfc40a8e613
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Tricircle has completed both Python35 and WSGI goals,
it's time to mark it in the governance repo.
Change-Id: Iaeba7e470be2691f53311294d27322ab5852184c
Signed-off-by: joehuang <joehuang@huawei.com>
