Difference between revisions of "Meetings/InfraTeamMeeting"
< Meetings
(→Agenda for next meeting) |
Pabelanger (talk | contribs) (→Agenda for next meeting) |
||
Line 27: | Line 27: | ||
** https://review.openstack.org/211703 | ** https://review.openstack.org/211703 | ||
** https://review.openstack.org/211294 | ** https://review.openstack.org/211294 | ||
− | |||
** https://review.openstack.org/186619 | ** https://review.openstack.org/186619 | ||
* Normally there are no infra-roots in Europe, some of us want to volunteer for it (yolanda) | * Normally there are no infra-roots in Europe, some of us want to volunteer for it (yolanda) |
Revision as of 17:56, 18 August 2015
Contents
Weekly Project Infrastructure team meeting
The OpenStack Project Infrastructure Team holds public weekly meetings in #openstack-meeting
, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.
Please feel free to add agenda items (and your IRC nick in parenthesis).
Agenda for next meeting
- Announcements
- Actions from last meeting
- Specs approval
- Schedule Project Renames
- Priority Efforts
- Swift logs
- Nodepool DIB
- Migration to Zanata
- Downstream Puppet
- Upgrading Gerrit
- Docs publishing
- Holding pattern while Swift logs issues get ironed out
- Restore from backup test (jeblair)
- Fedora 22 snapshots and / or DIBs feedback (pabelanger)
- Normally there are no infra-roots in Europe, some of us want to volunteer for it (yolanda)
- puppet-pip vs puppet-python (rcarrillocruz)
- Puppet-pip module is supposedly for installing pip and managing pip.conf.
- Puppet-python (aka stankevich-python) module manages python, pip, virtualenv and gunicorn virtual hosts
- I suggest we either repurpose puppet-pip to puppet-pip-settings to manage pip.conf or we deprecate and upstream the pip.conf handling to stankevich-python. Thoughts?
- Nodepool REST API spec (rcarrillocruz)
- https://review.openstack.org/#/c/141016/
- I would appreciate suggestions on the authentication part, the spec has been around for a while and would like to push it forward
- Open discussion
Upcoming Project Renames
(any additions should mention original->new full names and link to the corresponding change in Gerrit)
- stackforge/os-ansible-deployment{,-specs} -> openstack/openstack-ansible{,-specs} https://review.openstack.org/200730
- stackforge/{solum, python-solumclient, solum-specs, solum-dashboard, solum-infra-guestagent} -> openstack/{solum, python-solumclient, solum-specs, solum-dashboard, solum-infra-guestagent} https://review.openstack.org/#/c/201287/
- stackforge/{magnetodb, python-magnetodbclient, magnetodb-specs} -> openstack/{magnetodb, python-magnetodbclient, magnetodb-specs} https://review.openstack.org/#/c/203524/
- stackforge/kolla -> openstack/kolla https://review.openstack.org/#/c/209343/
- stackforge/neutron-powervm -> openstack/networking-powervm https://review.openstack.org/#/c/206662/
-
stackforge/{compass-adaptors,compass-core,compass-specs,compass-web} -> openstack/{compass-adaptors,compass-core,compass-specs,compass-web} https://review.openstack.org/196916The TC decided these are not ready yet.
Previous meetings
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/