* Update governance from branch 'master'
- Merge "Doug Hellmann nomination for Chair"
- Doug Hellmann nomination for Chair
I would be honored to serve as chair for the TC for this session.
With Thierry stepping down as chair, this session will be the first
time the TC as it stands today is chaired by someone from outside of
the Foundation staff. This is an important step for us, to show not
only that our principle of Changes in Leadership are Good applies to
the TC, but that our leaders can and will place the needs of the
community first. Over the 6 years I have been contributing to
OpenStack and the 4+ years I have served on the TC, I have been
employed by 3 separate companies. I hope my history of service within
the community reassures everyone of my continued impartiality.
The nature of the TC and the issues it has had to address have changed
in significant ways several times while I have been involved.
When the TC addressed fundamental questions about what types of
projects should be included in the community, and OpenStack expanded
from a simple IaaS project to our current mission of producing the
ubiquitous Open Source Cloud Computing platform, I helped navigate
that change, first as a member of the Ceilometer team (one of the
first teams to be added to OpenStack without being spawned from an
existing project), and later as a TC member drafting early versions of
the Big Tent resolution.
When our community went through a period of intensive growth, as
companies joined and brought new features and formed new projects, I
helped organize the Oslo and release teams to cope with that growth by
implementing the liaison system and driving more use of automation.
More recently, as we have seen some leveling off, or even reduction,
of contributors, I worked with the documentation and requirements
teams to accommodate the contraction by shifting documentation from a
central location into team-owned repositories and by simplifying the
way we manage dependency settings in each project. These changes
reduced the friction for contributors to those projects.
Those experiences have prepared me to help us through this next
transition, as well.
My goals for this session are to have a smooth transition and to help
the TC work together as a team to achieve our shared objectives. I
have a few things I would like to change about the way we organize
ourselves based on patterns we have seen work well elsewhere,
including using sub-teams of TC members to manage our recurring
responsibilities more actively.
I look forward to talking with you about the future of the TC over the
next few weeks.
Change-Id: I35a4b1501b0019e79b34cc92f83af38ea4a41c26
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* Update governance from branch 'master'
- Merge "Add os_masakari to OpenStack-Ansible"
- Add os_masakari to OpenStack-Ansible
The os_masakari role is necessary for some deployers, so we
want to include this new role to get new contributions. This will
be as a separate deliverable as the main openstack-ansible project,
like others extra roles before it.
Depends-On: I8e2d90d36ff726f29cee99dd2b975bfeeaf4b8f4
Change-Id: I1ee01895903cd17374801356e244738624f9af4a
* Update governance from branch 'master'
- Merge "Add openstack-dns (Designate) to Chef OpenStack"
- Add openstack-dns (Designate) to Chef OpenStack
The openstack-dns is necessary for some deployers. We want to include
this cookbook to foster contribution. This will be a deliverable treated
as other maintained cookbooks in Chef OpenStack.
Depends-On: I499c2a8fdf0d82bc80a8d7ac6aa61d24328930c9
Change-Id: I7c9dee068b1685ae5ea05664be18ca9fb5835704
* Update governance from branch 'master'
- Members update following Apr 2018 election
This updates the roster after the April 2018 election:
https://governance.openstack.org/election/results/rocky/tc.html
Chair will be designated in a subsequent patch.
Change-Id: Ic5a53468bb3a8d54ace62b35917b0be8c502485d
* Update governance from branch 'master'
- Import ansible-role-container-registry in tripleo
This role has to replace the puppet code that used to deploy and
configure Docker and Docker Registry.
We aim to make a generic role that can be re-used by the community.
Depends-On: Ie23e36bfa8451275e460100ab4776bf5aa8efa54
Change-Id: Ife3934bbb2686fca94eb28b5591c36567b90b58c
* Update governance from branch 'master'
- Merge "Adjust TC election target to 6 weeks before summit"
- Adjust TC election target to 6 weeks before summit
The existing 3 weeks prior to summit target for TC elections can be
problematic for travel planning for candidates who might only go to
summit if they win their election, or might plan a different length
of trip depending on their role(s) in the community. This change
makes the target for the election to be six weeks prior to summit
to ease that planning.
In addition to helping with travel concerns, it also means that any
newly elected TC members will be more involved in planning for the
forum at the summit.
If approved this change would go in effect for the second election
in 2018. The first election of 2018 is already scheduled.
Change-Id: Ie1a7d9bae28864fb7413d8df2daa67abc5c70778
* Update governance from branch 'master'
- Merge "Update docs job info to match current PTI"
- Update docs job info to match current PTI
Our doc requirements have been updated to run documentation builds
using sphinx-build instead of calling tox. The PTI reference for
Python code still contained old recommendations to use
[build_sphinx] in setup.cfg. This updates this Python recommendation
to match what is stated in the full PTI with additions for making
local runs easier through using tox.
Change-Id: Ibdaeefdac6b6bbeef544778d2fa5c3972d180cb8
* Update governance from branch 'master'
- Merge "Add puppet-senlin to Puppet OpenStack"
- Add puppet-senlin to Puppet OpenStack
"Senlin is a clustering service for OpenStack clouds. It creates and operates
clusters of homogeneous objects exposed by other OpenStack services. The
goal is to make the orchestration of collections of similar objects easier.
Senlin provides RESTful APIs to users so that they can associate various
policies to a cluster. Sample policies include placement policy, load
balancing policy, health policy, scaling policy, update policy and so on.
Senlin is designed to be capable of managing different types of objects. An
object's lifecycle is managed using profile type implementations, which are
themselves plugins."
More information about Senlin project:
https://wiki.openstack.org/wiki/Senlin
We started to work on the Puppet senlin module that installs and
configures Senlin services.
Change-Id: I53b62c6874da44215a89b56f57c44f954aeab057
Depends-On: Ic4272d28016b95006f6c31c41f60c9111ebb2c91
* Update governance from branch 'master'
- Merge "Create tripleo-ha-utils project"
- Create tripleo-ha-utils project
As described in the spec [1] merged recently, this project aims to
contain all the tools, ansible playbooks and documentation to proper
test and verify all the specific HA bits of a TripleO deployment.
[1] a021956fb8
Depends-On: Ic2c0e036a35a02dd1fe40046047ff7bbad165ebe
Change-Id: I7d6c3fdd2d1f17cd8c128a971c9d765032c48fe3
* Update governance from branch 'master'
- Merge "Add vulnerability:managed to keystonemiddleware"
- Add vulnerability:managed to keystonemiddleware
keystonemiddleware was reviewed by the Security SIG for threat
analysis[0], which meets #5 under the list of requirements for
vulnerabiltity managment[1], which is one of the main requirements for
achieving this tag.
[0] https://review.openstack.org/#/c/447139/
[1] https://governance.openstack.org/tc/reference/tags/vulnerability_managed.html#requirements
Depends-On: I2e7a96f46879586a372b71ebcaa8bfdd8faf7e39
Change-Id: I266bc32165dfa433cdaa416b59d4dd5f4c6e88d8
* Update governance from branch 'master'
- Merge "Official projects should not keep tagging rights"
- Official projects should not keep tagging rights
Release management of official projects is handled by
the Release Management team through the openstack/releases
repository. Set the expectation early on that official
projects will have to drop direct tagging (or branching)
rights in their Gerrit ACLs once they are made official.
Needed-By: https://review.openstack.org/557733
Change-Id: Iade3f85d133892464e4c9f21ce2977ca0dd8930d
* Update governance from branch 'master'
- Merge "fix tox to allow building docs locally"
- fix tox to allow building docs locally
Recent changes in sphinx and pbr make it easier to just invoke
sphinx-build directly instead of going through setup.py.
Change-Id: Ic5c4f397fd45d9978c630ff03dcff7bf6b4d05e4
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* Update governance from branch 'master'
- Merge "Retire puppet-ganesha"
- Retire puppet-ganesha
An announcement was done on openstack-dev. This project is not
useful anymore. Let's retire it and do some cleanup.
Change-Id: I2d495f77c2b6a0923b83468c5340cc2a5a5bc09d
Depends-On: https://review.openstack.org/#/c/556696/
* Update governance from branch 'master'
- Merge "Resolution for minimal SIG governance"
- Resolution for minimal SIG governance
We have been operating SIGs for some time now with a very loose
governance model. We took this approach on purpose to give folks
space and opportunity to decide what they believed constituted
a SIG in hopes of learning how we can apply SIGs to our community
needs.
However at this point there is some confusion and concern regarding
SIG governance. Since SIGs explicitly do not sit below any existing
governance structure, there is no default solution to fall back on.
We need to define a clear way to address issues before any conflict
arises. As was the case elsewhere, we expect the mere existence of
a clear decision-making structure to prevent most conflicts from
happening.
This resolution proposes a minimal, simple governance model to
address such cases, introducing a SIGs admin group. The group
is initially formed of the Meta SIG co-leads: Melvin Hillsman
as UC representative and Thierry Carrez as TC representative.
The committees are of course free to choose new members whenever
they see fit.
A similar resolution was proposed to the User Committee, which
approved it:
http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-03-12-14.05.log.html#l-74
Change-Id: Ibc2336980739db38f64a42b8ba2adeacff000a13
Co-Authored-By: Melvin Hillsman <mrhillsman@gmail.com>
* Update governance from branch 'master'
- Merge "Update new projects reference WRT IRC meetings."
- Update new projects reference WRT IRC meetings.
In I631e2597bf818c5e4b2f813da14764d2cb55d0ce the TC passed
resolutions/20170718-allow-scheduling-meetings-on-team-channels which
allows teams to host meetings in per-project IRC channels.
However the new-projects-requirements still stated that meeting needed
to be held in one of the central meeting channels. This change updates
that document in light of the resolution.
Change-Id: Ib8febcc6b80bc36833f2040b1cc1c5eb15841655
* Update governance from branch 'master'
- Add python_venv_build ansible role to OSA deliverables
In OpenStack-Ansible python venvs are built, packaged
and consumed at run-time. Currently this uses the same
code across multiple roles. This role will be used by
OpenStack-Ansible to replace the duplicated code in
every OSA role but could also be used by any other
project who may wish to.
The role is registered as an independent deliverable as
it is not expected to require frequent releasing.
Depends-On: https://review.openstack.org/553392
Change-Id: Ic4bad4c0cebe018c4a27e0cc79faf9186b7707de
* Update governance from branch 'master'
- Merge "Add systemd roles to OpenStack-Ansible"
- Add systemd roles to OpenStack-Ansible
The systemd_mount and systemd_service roles are a way for
OpenStack-Ansible to not repeat ourselves in the code.
It can also be used by other members of the openstack community,
and is therefore not mapped to our main deliverable.
We are still curating it in our group: these roles will be important
for deploying a cloud with openstack-ansible.
Depends-On: https://review.openstack.org/#/c/552861
Change-Id: I098ccc03ff2e4a4bcb65e1f376f2c712b10c9c25
* Update governance from branch 'master'
- Merge "Create a new project called oslo.limit"
- Create a new project called oslo.limit
This commit creates a new oslo library called oslo.limit to help
services enforce quota based on limit information stored in keystone.
Depends-On: I1bdb05189fa0346426cb36d4a3d5fe458eb69871
Change-Id: I46d5d16f29a4a613c96f01023c89e94b39abf2dd
* Update governance from branch 'master'
- Merge "Apply supports-rolling-upgrade tag for heat project"
- Apply supports-rolling-upgrade tag for heat project
We like to apply supports-rolling-upgrade tag for heat since heat right
now already fulfill fallowing targets:
* The project is already tagged as type:service
* Tag with supports-upgrade
* allows operators to roll out new code to subsets of service
* Full stack integration testing with services arranged, right now
we have an experimental job for multi-node grenade job with tests
runs before and after upgrade. Which is green and stable. and works
for ocata to pike and pike to master.
With above works, this patch propose to add supports-rolling-upgrade tag
for heat service.
Change-Id: I70295ece435357af3ecae575233e1d09096f461a
* Update governance from branch 'master'
- Merge "Rename and clarify PowerStackers"
- Rename and clarify PowerStackers
This change renames PowerStackers and clarifies mission statement added
in I1b709623df535b662871e9db2bac59b6f55f5277
The project team name and the mission are in disagreement in that the
name and mission cover all POWER CPU implementations but it's clear from
the make up of the group that it refers only to the PowerVM hypervisor.
Change-Id: I95f76f90fa65d0f54fed69b75cb575575976b33e
* Update governance from branch 'master'
- Merge "Fix stray ',' in trademark test location resolution"
- Fix stray ',' in trademark test location resolution
The typo was identified during voting, but did not want to ruin the
votes for this fix. So doing so in this follow up.
Change-Id: I9d4b9fc9f7b57155d7e4f5eba046ce1a0a5faded
* Update governance from branch 'master'
- Merge "Clarify testing for interop programs"
- Clarify testing for interop programs
This provides an alternative to
I91315c3c42b8a329d1763f9de80aa3d0270ac044 to provide simplified
guidance on use of plugins for trademark tests. The coauthors below
represents the people who were activce in the creating and refining
these ideas.
Change-Id: I2e68c8e855e7c6c1e4f985f38a0a38de451407a3
Co-Authored-By: Graham Hayes <gr@ham.ie>
Co-Authored-By: Zane Bitter <zbitter@redhat.com>
Co-Authored-By: Andrea Frittoli <andrea.frittoli@gmail.com>
Co-Authored-By: Mark T. Voelker <mvoelker@vmware.com>
Co-Authored-By: Jim Rollenhagen <jim@jimrollenhagen.com>
Co-Authored-By: ricolin <rico.lin@easystack.cn>
* Update governance from branch 'master'
- Merge "Add a resolution about stable branch EOL and "extended maintenance""
- Add a resolution about stable branch EOL and "extended maintenance"
We've talked about this for years, and talked some more at the
Rocky PTG. This adds a resolution to try and document / summarize
the outcomes of the Sydney summit and Rocky PTG.
Change-Id: I94b0421d8a489026300789b61b0293dd2e61726d
* Update governance from branch 'master'
- Merge "Remove Zuul from OpenStack governance"
- Remove Zuul from OpenStack governance
Zuul is becoming a top-level project under the OpenStack Foundation,
so remove it from OpenStack project governance.
Nodepool and the other repos in this change are considered constituent
projects of Zuul.
Change-Id: I28319b621989ad660ae18fdc176462fb840aecc0
* Update governance from branch 'master'
- Merge "Remove ironic-inspector-tempest-plugin"
- Remove ironic-inspector-tempest-plugin
ironic and ironic-inspector both use ironic-tempest-plugin, so
ironic-inspector-tempest-plugin is not needed, nor was it ever used
(the git repo only has a .gitreview file in it).
This removes the ironic-inspector-tempest-plugin project.
This mostly follows the instructions at
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project.
Depends-On: https://review.openstack.org/550537
Change-Id: I30580f4d05636e3fc980ffefec64097627aea0dd
* Update governance from branch 'master'
- Merge "Add config_template to OpenStack-Ansible"
- Add config_template to OpenStack-Ansible
The config_template is curated by the OpenStack-Ansible group
until we find out a better place, or there are more people
interested by it.
Depends-On: https://review.openstack.org/#/c/546678/
Change-Id: I7cbf22fff1c483f23c59cae4d9e6669f4c857f04
* Update governance from branch 'master'
- Merge "Update IRC nickname for Samuel Cassiba"
- Update IRC nickname for Samuel Cassiba
Samuel Cassiba can now be found on IRC as scas.
Change-Id: I6bfb3a0a3bdfbf9a747f3f84de08f86367d7e417
* Update governance from branch 'master'
- Add xstatic-** to horizon project
To remove all embedded js copies from heat-dashboard, we need these
xstatic packages projects.
Change-Id: I404ec19472f1ede2c3d9c1d41eabd5710ffb21cd
Depends-On: I4ed1ba3686e6e26aaf570980072344ce40977db4
* Update governance from branch 'master'
- Merge "Include ansible-role-redhat-subscription into tripleo"
- Include ansible-role-redhat-subscription into tripleo
ansible-role-redhat-subscription is an Ansible role mainly maintained by
people working on TripleO now.
We would like to use OpenStack release management, so the project needs
to be part of OpenStack, so we'll include it in TripleO.
Change-Id: I9762658117bc0081482996a6387fabdd224311c6
* Update governance from branch 'master'
- Merge "Fix the invalid url in page"
- Fix the invalid url in page
Change-Id: Id1c1fd4cc2a2e993b196a566d0feba5704687533
* Update governance from branch 'master'
- Merge "Add PowerStackers project"
- Add PowerStackers project
The nova-powervm, networking-powervm, and ceilometer-powervm
deliverables have been around for a while, but only
ceilometer-powervm was under governance (as part of the Telemetry
project). This creates a new project under governance where we can
include all of the *-powervm projects, so that they will all be
under governance together.
Change-Id: I1b709623df535b662871e9db2bac59b6f55f5277
* Update governance from branch 'master'
- Merge "Add Glance completion info for policy in code goal"
- Add Glance completion info for policy in code goal
Glance did not complete the goal during the Queens cycle, this
explains why.
Change-Id: If0cdfa5a05a12af36867b47ea7481e67294bb530
* Update governance from branch 'master'
- Merge "Add roles into openstack-ansible deliverable"
- Add roles into openstack-ansible deliverable
Molteniron, octavia, and Tacker are delivered by default with
OpenStack-Ansible. They follow the same delivery model, and should
therefore be included into the openstack-ansible deliverable,
instead of being independant.
This is in-line with our "aggregated release" vision.
Change-Id: I56940c1ad57d13408e3c708c12cb10dccccd84e7
* Update governance from branch 'master'
- Merge "Add openstack-ansible-os_panko to OSA deliverable"
- Add openstack-ansible-os_panko to OSA deliverable
The new openstack-ansible-os_panko repository is included
as an OSA deliverable as it is curated and delivered by
the community.
Depends-On: I75c19ae8f87f193c8f4d40454b113f78016fa834
Change-Id: I564d75d57f059b64cc6bb010def6fb28fcea0f96
* Update governance from branch 'master'
- Merge "Add openstack-ansible-nspawn.* to OpenStack-Ansible"
- Add openstack-ansible-nspawn.* to OpenStack-Ansible
The nspawn.* repositories are now curated by the
OpenStack-Ansible community.
Depends-On: https://review.openstack.org/#/c/546075/
Change-Id: I9340f14437254ec0f7871c5995df0db99c80502a
* Update governance from branch 'master'
- Merge "[rally] Add a separate repo for OpenStack plugins"
- [rally] Add a separate repo for OpenStack plugins
Depends-On: I4269ae2cae08ef7784ca1d5c107cace101a1209e
Change-Id: Ib6ac80994cbc72af5b1a85a17e22431cc0821311
* Update governance from branch 'master'
- Merge "Update status of 'API deployed in uwsgi' goal"
- Update status of 'API deployed in uwsgi' goal
The Pike release of Glance contained a release note indicating
the Glance should not be deployed under uwsgi in production. That
same advice is being given for Queens. Add a note to the goal
completion section for that goal so that people who don't read the
release notes are aware of this.
Change-Id: Iab7310751874392c8cf787b6cd748aa55a7b7477
* Update governance from branch 'master'
- Merge "replace tracking sections with storyboard links for rocky goals"
- replace tracking sections with storyboard links for rocky goals
We agreed to use storyboard stories and tasks to track goals this
cycle, so replace the in-page list of artifact information with the
links to the relevant stories.
Change-Id: I8c55e1e9490123eb00dd99e638035f1c182c328b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* Update governance from branch 'master'
- Merge "Retire horizon-cisco-ui project"
- Retire horizon-cisco-ui project
The horizon-cisco-ui project has been retired. This completes step 5
of the retirement process:
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
Change-Id: Ice73c045abad2eef1790a62281979e16d4407250
* Update governance from branch 'master'
- Merge "Add resolution about CI for external projects"
- Add resolution about CI for external projects
This resolution is to establish agreement that we think extending
Zuul to run integration tests and report on non-OpenStack projects
(e.g., Ansible, kubernetes, etc.) is in the interest of the community,
and what the scope of such an effort should be. I plan to follow
it up with specific instructions in the infra-manual describing
the process to set up such testing.
Change-Id: Ia7dc06cade7e436a4df64f4f0d55327ea6c78b81
* Update governance from branch 'master'
- Merge "Add naming poll info for S release"
- Add naming poll info for S release
As for the release before, let's use the location of the upcoming
Berlin summit to help name the S release. We've selected the state of
Berlin as our region!
Change-Id: I294ad5c5bb405e36aa3784d9baf13398b60422d4
Signed-off-by: Paul Belanger <pabelanger@redhat.com>