https://wiki.openstack.org/w/api.php?action=feedcontributions&user=John+Garbutt&feedformat=atomOpenStack - User contributions [en]2024-03-19T07:21:39ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=PTG/Train/Etherpads&diff=169793PTG/Train/Etherpads2019-05-02T14:49:13Z<p>John Garbutt: /* SIG/Theme/Other */</p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering for the Train release in Denver, 2019. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
For what's happening '''right now''' (during the event), see the [http://ptg.openstack.org/ptg.html ptgbot page].<br />
<br />
=== Projects ===<br />
* Blazar - https://etherpad.openstack.org/p/blazar-ptg-train<br />
* Charms - https://etherpad.openstack.org/p/charms-train-ptg<br />
* Cinder - https://etherpad.openstack.org/p/cinder-train-ptg-planning<br />
* Cyborg - https://etherpad.openstack.org/p/cyborg-ptg-train<br />
* Docs/I18n - https://etherpad.openstack.org/p/docs-i18n-ptg-train<br />
* Fenix<br />
** Fenix general - https://etherpad.openstack.org/p/DEN2019-fenix-PTG<br />
** Fenix - ETSI NFV - https://etherpad.openstack.org/p/DEN2019-fenix-ETSI-NFV-PTG<br />
* Glance - https://etherpad.openstack.org/p/Glance-Train-PTG-planning<br />
* Heat - https://etherpad.openstack.org/p/DEN-Train-Heat<br />
* Horizon - https://etherpad.openstack.org/p/horizon-train-ptg<br />
* Ironic - https://etherpad.openstack.org/p/DEN-train-ironic-ptg<br />
* Keystone - https://etherpad.openstack.org/p/keystone-train-ptg<br />
* Magnum - https://etherpad.openstack.org/p/magnum-train-ptg<br />
* Manila<br />
** Planning: https://etherpad.openstack.org/p/manila-denver-train-ptg-planning<br />
** Minutes/Proceedings: https://etherpad.openstack.org/p/manila-ptg-train<br />
* Monasca - https://etherpad.openstack.org/p/monasca-ptg-train<br />
* Neutron - https://etherpad.openstack.org/p/openstack-networking-train-ptg<br />
* Nova - https://etherpad.openstack.org/p/nova-ptg-train<br />
* Octavia - https://etherpad.openstack.org/p/octavia-train-ptg<br />
* OpenStackAnsible - https://etherpad.openstack.org/p/osa-train-ptg<br />
* Oslo - https://etherpad.openstack.org/p/oslo-train-topics<br />
* Placement - https://etherpad.openstack.org/p/placement-ptg-train<br />
* QA<br />
** Schedule: https://ethercalc.openstack.org/Train-PTG-QA-Schedule<br />
** Etherpad: https://etherpad.openstack.org/p/qa-train-ptg<br />
* Release Team - https://etherpad.openstack.org/p/relmgmt-train-ptg<br />
* Swift - https://etherpad.openstack.org/p/swift-ptg-train<br />
* Tripleo <br />
** Schedule: https://etherpad.openstack.org/p/tripleo-ptg-train<br />
** Topic Planning: https://etherpad.openstack.org/p/tripleo-train-topics<br />
* Vitrage - https://etherpad.openstack.org/p/vitrage-train-ptg<br />
<br />
=== Cross-Project ===<br />
* Nova/Cinder - https://etherpad.openstack.org/p/ptg-train-xproj-nova-cinder<br />
* Nova/Cyborg - https://etherpad.openstack.org/p/ptg-train-xproj-nova-cyborg<br />
* Nova/Ironic - https://etherpad.openstack.org/p/ptg-train-xproj-nova-ironic<br />
* Nova/Keystone - https://etherpad.openstack.org/p/ptg-train-xproj-nova-keystone<br />
* Nova/Neutron - https://etherpad.openstack.org/p/ptg-train-xproj-nova-neutron<br />
* Nova/Placement - https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement<br />
* Cyborg/Ironic - https://etherpad.openstack.org/p/ptg-train-xproj-ironic-cyborg<br />
<br />
=== SIG/Theme/Other ===<br />
* API SIG - https://etherpad.openstack.org/p/api-sig-ptg-train<br />
* Technical Committee - https://etherpad.openstack.org/p/tc-train-ptg<br />
* Scientific SIG - https://etherpad.openstack.org/p/scientific-sig-ptg-train<br />
* Self-healing SIG - https://etherpad.openstack.org/p/DEN-self-healing-SIG<br />
* Security SIG - https://etherpad.openstack.org/p/security-sig-ptg-train<br />
* Public Cloud SIG - https://etherpad.openstack.org/p/DEN-public-cloud-SIG<br />
* Autoscaling SIG - https://etherpad.openstack.org/p/DEN-auto-scaling-SIG<br />
* Upgrades SIG - https://etherpad.openstack.org/p/upgrade-sig-ptg-train<br />
* Scientific SIG - https://etherpad.openstack.org/p/DEN-scientific-SIG<br />
<br />
=== Pilot Projects ===<br />
* Airship - https://etherpad.openstack.org/p/airship-ptg-train<br />
* StarlingX - https://etherpad.openstack.org/p/stx-ptg-agenda<br />
<br />
=== Other ===</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=LibvirtDistroSupportMatrix&diff=165100LibvirtDistroSupportMatrix2018-09-24T12:57:36Z<p>John Garbutt: /* Distro minimum versions */</p>
<hr />
<div>== Libvirt OS distribution support matrix ==<br />
<br />
This page documents the libvirt versions present in the various distro versions that OpenStack Nova aims to be deployable with. <br />
<br />
=== Libvirt min version change policy ===<br />
<br />
At the start of each Nova development cycle this matrix will be consulted to determine if it is viable to drop support for any end-of-life or otherwise undesired distro versions. Based on this distro evaluation, it may be possible to increase the min required version of libvirt in Nova, and thus drop some compatibility code for older versions.<br />
<br />
When a decision to update the minimum required libvirt version is made, there must be a warning issued for one cycle. This is achieved by editting nova/virt/libvirt/driver.py to set<br />
<br />
NEXT_MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
This causes a deprecation warning to be printed when Nova starts up warning the admin that the version of libvirt they are on will be dropped in the subsequent release.<br />
<br />
After a version has been listed in NEXT_MIN_LIBVIRT_VERSION for one release cycle, the corresponding actual min required libvirt can be updated by setting<br />
<br />
MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
At this point of course, an even newer version might be set in NEXT_MIN_LIBVIRT_VERSION to repeat the process....<br />
<br />
There is more background on the rationale used for picking minimum versions in the operators mailing list thread here:<br />
<br />
http://lists.openstack.org/pipermail/openstack-operators/2015-May/007012.html<br />
<br />
=== QEMU min version change policy ===<br />
<br />
After deciding the minimum libvirt version, the minimum QEMU version is determined by looking for the lowest QEMU version from all the distros that support the decided libvirt version<br />
<br />
=== Nova release min version ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Nova version<br />
! Current min libvirt<br />
! Next min libvirt<br />
! Current min QEMU<br />
! Next min QEMU<br />
<br />
|-<br />
! Havana<br />
| 0.9.6<br />
| 0.9.6<br />
<br />
|-<br />
! Icehouse<br />
| 0.9.6<br />
| 0.9.11<br />
<br />
|-<br />
! Juno<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Kilo<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Liberty<br />
| 0.9.11<br />
| 0.10.2<br />
<br />
|-<br />
! Mitaka<br />
| 0.10.2<br />
| 1.2.1<br />
<br />
|-<br />
! Newton<br />
| 1.2.1<br />
| 1.2.1<br />
| 1.5.3<br />
| 1.5.3<br />
<br />
|-<br />
! Ocata<br />
| 1.2.1<br />
| 1.2.9<br />
| 1.5.3<br />
| 2.1.0<br />
<br />
|-<br />
! Pike<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Queens<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Rocky<br />
| 1.3.1<br />
| 3.0.0<br />
| 2.5.0<br />
| 2.8.0<br />
<br />
|-<br />
! Stein (draft)<br />
| ? 3.0.0<br />
| ? 4.0.0<br />
| ? 2.8.0<br />
| ? 2.11.0<br />
<br />
|-<br />
! T (draft)<br />
| ?<br />
| ?<br />
| ?<br />
| ?<br />
<br />
|}<br />
<br />
=== Distro minimum versions ===<br />
<br />
This table provides information on a representative sample of OS distros and the version of libirt/qemu/libguestfs that they ship. This is *NOT* intended to be an exhaustive list of distros where OpenStack Nova can run - it is intended to run on any Linux distro which can satisfy the minimum required software versions. This table merely aims to help identify when min required versions can be reasonably updated without losing support for important OS distros.<br />
<br />
When NEXT_MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be changed to have <strike>strikethrough</strike> format.<br />
<br />
When MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be deleted from this table<br />
<br />
{| class="wikitable"<br />
|-<br />
! OS Distro<br />
! GA date<br />
! Libvirt<br />
! QEMU/KVM<br />
! libguestfs<br />
<br />
|-<br />
! Debian !! !!<br />
<br />
|-<br />
| Stretch<br />
| 2017-06-17<br />
| 3.0.0<br />
| 2.8.0<br />
| 1.34.6<br />
<br />
|-<br />
| Buster/Sid<br />
| checked on 2018-04-05<br />
| 4.1.0<br />
| 2.11<br />
| 1.36.13<br />
<br />
|-<br />
! Fedora !! !!<br />
<br />
|-<br />
| 26<br />
| 2017-07-11<br />
| 3.2.1<br />
| 2.9.0 <br />
| 1.36.4<br />
<br />
|-<br />
| 27<br />
| 2017-11-14<br />
| 3.7.0<br />
| 2.10.0<br />
| 1.37.29<br />
<br />
|-<br />
| 28<br />
| 2018-05-01<br />
| 4.1.0<br />
| 2.11.1<br />
| 1.38.0<br />
<br />
|-<br />
! KVM for IBM z Systems !! !!<br />
<br />
|-<br />
| 1.1.0<br />
| <br />
| 1.2.13<br />
| 2.3.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.1<br />
| <br />
| 1.2.21<br />
| 2.4.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.2<br />
| 2016-11-11 ([https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=OC&subtype=NA&htmlfid=897/ENUS5648-KVM&appname=totalstorage#lifecycl discontinued support on 2018-03-31])<br />
| 1.3.3<br />
| 2.6.0<br />
| N/A<br />
<br />
|-<br />
! openSUSE !! !!<br />
<br />
|-<br />
| Leap 42.2<br />
| 2016-11-16<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 42.3<br />
| 2017-07<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 15.0<br />
| 2018-05<br />
| 4.0.0<br />
| 2.11.1<br />
| 1.38.0<br />
<br />
|-<br />
! Oracle Linux * !! !!<br />
<br />
|-<br />
| 7<br />
|<br />
| 3.10.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
! RHEL * !! !!<br />
<br />
|-<br />
| 7.1<br />
| 2015-03-05<br />
| 1.2.8<br />
| 2.1.2<br />
| 1.28.1<br />
<br />
|-<br />
| 7.2<br />
| 2015-11-19<br />
| 1.2.17<br />
| 2.3.0<br />
| 1.28.1<br />
<br />
|-<br />
| 7.3<br />
| 2016-11-03<br />
| 2.0.0<br />
| 2.6.0<br />
| 1.32.7<br />
<br />
|-<br />
| 7.4<br />
| 2017-08-01<br />
| 3.2.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
<br />
! SLES !! !!<br />
<br />
|-<br />
| 12<br />
|<br />
| 1.2.5<br />
| 2.0.2<br />
| 1.26.9<br />
<br />
|-<br />
| 12SP1<br />
| 2016-01-12<br />
| 1.2.18<br />
| 2.3.1<br />
| 1.26.10<br />
<br />
|-<br />
| 12SP2<br />
| 2016-11<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| 12SP3<br />
| 2017-09<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
! Ubuntu !! !!<br />
<br />
|-<br />
| 14.04 (Trusty LTS)<br />
|<br />
| 1.2.2<br />
| 2.0.0<br />
| 1.24.5<br />
<br />
|-<br />
| 16.04 (Xenial LTS)<br />
|<br />
| 1.3.1<br />
| 2.5.0<br />
| 1.32.2<br />
<br />
|-<br />
| 18.04 (Bionic LTS)<br />
| 2018-04-26<br />
| 4.0.0<br />
| 2.11<br />
| 1.36.13<br />
|}<br />
<br />
NB: maintain alphabetical ordering of distros, followed by oldest released versions first<br />
<br />
NB2: RHEL versions of QEMU refer to the qemu-kvm-rhev RPM, '''not''' the qemu-kvm RPM, since the former is what is intended for use with OpenStack<br />
<br />
NB3: Oracle Linux versions for QEMU and libvirt refer to those used in the docker containers supplied with Oracle OpenStack 4.0. Newer versions will likely be adopted in subsequent releases of Oracle OpenStack. Versions bundled in the OS are aligned with RHEL (i.e. old). Whilst vanilla OpenStack on Oracle Linux is not supported, recent versions of QEMU and libvirt RPMs may be found in the "developer_UEKR5" YUM repository.</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=LibvirtDistroSupportMatrix&diff=165098LibvirtDistroSupportMatrix2018-09-24T12:41:08Z<p>John Garbutt: /* Distro minimum versions */</p>
<hr />
<div>== Libvirt OS distribution support matrix ==<br />
<br />
This page documents the libvirt versions present in the various distro versions that OpenStack Nova aims to be deployable with. <br />
<br />
=== Libvirt min version change policy ===<br />
<br />
At the start of each Nova development cycle this matrix will be consulted to determine if it is viable to drop support for any end-of-life or otherwise undesired distro versions. Based on this distro evaluation, it may be possible to increase the min required version of libvirt in Nova, and thus drop some compatibility code for older versions.<br />
<br />
When a decision to update the minimum required libvirt version is made, there must be a warning issued for one cycle. This is achieved by editting nova/virt/libvirt/driver.py to set<br />
<br />
NEXT_MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
This causes a deprecation warning to be printed when Nova starts up warning the admin that the version of libvirt they are on will be dropped in the subsequent release.<br />
<br />
After a version has been listed in NEXT_MIN_LIBVIRT_VERSION for one release cycle, the corresponding actual min required libvirt can be updated by setting<br />
<br />
MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
At this point of course, an even newer version might be set in NEXT_MIN_LIBVIRT_VERSION to repeat the process....<br />
<br />
There is more background on the rationale used for picking minimum versions in the operators mailing list thread here:<br />
<br />
http://lists.openstack.org/pipermail/openstack-operators/2015-May/007012.html<br />
<br />
=== QEMU min version change policy ===<br />
<br />
After deciding the minimum libvirt version, the minimum QEMU version is determined by looking for the lowest QEMU version from all the distros that support the decided libvirt version<br />
<br />
=== Nova release min version ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Nova version<br />
! Current min libvirt<br />
! Next min libvirt<br />
! Current min QEMU<br />
! Next min QEMU<br />
<br />
|-<br />
! Havana<br />
| 0.9.6<br />
| 0.9.6<br />
<br />
|-<br />
! Icehouse<br />
| 0.9.6<br />
| 0.9.11<br />
<br />
|-<br />
! Juno<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Kilo<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Liberty<br />
| 0.9.11<br />
| 0.10.2<br />
<br />
|-<br />
! Mitaka<br />
| 0.10.2<br />
| 1.2.1<br />
<br />
|-<br />
! Newton<br />
| 1.2.1<br />
| 1.2.1<br />
| 1.5.3<br />
| 1.5.3<br />
<br />
|-<br />
! Ocata<br />
| 1.2.1<br />
| 1.2.9<br />
| 1.5.3<br />
| 2.1.0<br />
<br />
|-<br />
! Pike<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Queens<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Rocky<br />
| 1.3.1<br />
| 3.0.0<br />
| 2.5.0<br />
| 2.8.0<br />
<br />
|-<br />
! Stein (draft)<br />
| ? 3.0.0<br />
| ? 4.0.0<br />
| ? 2.8.0<br />
| ? 2.11.0<br />
<br />
|}<br />
<br />
=== Distro minimum versions ===<br />
<br />
This table provides information on a representative sample of OS distros and the version of libirt/qemu/libguestfs that they ship. This is *NOT* intended to be an exhaustive list of distros where OpenStack Nova can run - it is intended to run on any Linux distro which can satisfy the minimum required software versions. This table merely aims to help identify when min required versions can be reasonably updated without losing support for important OS distros.<br />
<br />
When NEXT_MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be changed to have <strike>strikethrough</strike> format.<br />
<br />
When MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be deleted from this table<br />
<br />
{| class="wikitable"<br />
|-<br />
! OS Distro<br />
! GA date<br />
! Libvirt<br />
! QEMU/KVM<br />
! libguestfs<br />
<br />
|-<br />
! Debian !! !!<br />
<br />
|-<br />
| Stretch<br />
| 2017-06-17<br />
| 3.0.0<br />
| 2.8.0<br />
| 1.34.6<br />
<br />
|-<br />
| Buster/Sid<br />
| checked on 2018-04-05<br />
| 4.1.0<br />
| 2.11<br />
| 1.36.13<br />
<br />
|-<br />
! Fedora !! !!<br />
<br />
|-<br />
| 26<br />
| 2017-07-11<br />
| 3.2.1<br />
| 2.9.0 <br />
| 1.36.4<br />
<br />
|-<br />
| 27<br />
| 2017-11-14<br />
| 3.7.0<br />
| 2.10.0<br />
| 1.37.29<br />
<br />
|-<br />
| 28<br />
| 2018-05-01<br />
| 4.1.0<br />
| 2.11.1<br />
| 1.38.0<br />
<br />
|-<br />
! KVM for IBM z Systems !! !!<br />
<br />
|-<br />
| 1.1.0<br />
| <br />
| 1.2.13<br />
| 2.3.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.1<br />
| <br />
| 1.2.21<br />
| 2.4.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.2<br />
| <br />
| 1.3.3<br />
| 2.6.0<br />
| N/A<br />
<br />
|-<br />
! openSUSE !! !!<br />
<br />
|-<br />
| Leap 42.2<br />
| 2016-11-16<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 42.3<br />
| 2017-07<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 15.0<br />
| 2018-05<br />
| 4.0.0<br />
| 2.11.1<br />
| 1.38.0<br />
<br />
|-<br />
! Oracle Linux * !! !!<br />
<br />
|-<br />
| 7<br />
|<br />
| 3.10.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
! RHEL * !! !!<br />
<br />
|-<br />
| 7.1<br />
| 2015-03-05<br />
| 1.2.8<br />
| 2.1.2<br />
| 1.28.1<br />
<br />
|-<br />
| 7.2<br />
| 2015-11-19<br />
| 1.2.17<br />
| 2.3.0<br />
| 1.28.1<br />
<br />
|-<br />
| 7.3<br />
| 2016-11-03<br />
| 2.0.0<br />
| 2.6.0<br />
| 1.32.7<br />
<br />
|-<br />
| 7.4<br />
| 2017-08-01<br />
| 3.2.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
<br />
! SLES !! !!<br />
<br />
|-<br />
| 12<br />
|<br />
| 1.2.5<br />
| 2.0.2<br />
| 1.26.9<br />
<br />
|-<br />
| 12SP1<br />
| 2016-01-12<br />
| 1.2.18<br />
| 2.3.1<br />
| 1.26.10<br />
<br />
|-<br />
| 12SP2<br />
| 2016-11<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| 12SP3<br />
| 2017-09<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
! Ubuntu !! !!<br />
<br />
|-<br />
| 14.04 (Trusty LTS)<br />
|<br />
| 1.2.2<br />
| 2.0.0<br />
| 1.24.5<br />
<br />
|-<br />
| 16.04 (Xenial LTS)<br />
|<br />
| 1.3.1<br />
| 2.5.0<br />
| 1.32.2<br />
<br />
|-<br />
| 18.04 (Bionic LTS)<br />
| 2018-04-26<br />
| 4.0.0<br />
| 2.11<br />
| 1.36.13<br />
|}<br />
<br />
NB: maintain alphabetical ordering of distros, followed by oldest released versions first<br />
<br />
NB2: RHEL versions of QEMU refer to the qemu-kvm-rhev RPM, '''not''' the qemu-kvm RPM, since the former is what is intended for use with OpenStack<br />
<br />
NB3: Oracle Linux versions for QEMU and libvirt refer to those used in the docker containers supplied with Oracle OpenStack 4.0. Newer versions will likely be adopted in subsequent releases of Oracle OpenStack. Versions bundled in the OS are aligned with RHEL (i.e. old). Whilst vanilla OpenStack on Oracle Linux is not supported, recent versions of QEMU and libvirt RPMs may be found in the "developer_UEKR5" YUM repository.</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=LibvirtDistroSupportMatrix&diff=165097LibvirtDistroSupportMatrix2018-09-24T12:40:43Z<p>John Garbutt: /* Distro minimum versions */</p>
<hr />
<div>== Libvirt OS distribution support matrix ==<br />
<br />
This page documents the libvirt versions present in the various distro versions that OpenStack Nova aims to be deployable with. <br />
<br />
=== Libvirt min version change policy ===<br />
<br />
At the start of each Nova development cycle this matrix will be consulted to determine if it is viable to drop support for any end-of-life or otherwise undesired distro versions. Based on this distro evaluation, it may be possible to increase the min required version of libvirt in Nova, and thus drop some compatibility code for older versions.<br />
<br />
When a decision to update the minimum required libvirt version is made, there must be a warning issued for one cycle. This is achieved by editting nova/virt/libvirt/driver.py to set<br />
<br />
NEXT_MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
This causes a deprecation warning to be printed when Nova starts up warning the admin that the version of libvirt they are on will be dropped in the subsequent release.<br />
<br />
After a version has been listed in NEXT_MIN_LIBVIRT_VERSION for one release cycle, the corresponding actual min required libvirt can be updated by setting<br />
<br />
MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
At this point of course, an even newer version might be set in NEXT_MIN_LIBVIRT_VERSION to repeat the process....<br />
<br />
There is more background on the rationale used for picking minimum versions in the operators mailing list thread here:<br />
<br />
http://lists.openstack.org/pipermail/openstack-operators/2015-May/007012.html<br />
<br />
=== QEMU min version change policy ===<br />
<br />
After deciding the minimum libvirt version, the minimum QEMU version is determined by looking for the lowest QEMU version from all the distros that support the decided libvirt version<br />
<br />
=== Nova release min version ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Nova version<br />
! Current min libvirt<br />
! Next min libvirt<br />
! Current min QEMU<br />
! Next min QEMU<br />
<br />
|-<br />
! Havana<br />
| 0.9.6<br />
| 0.9.6<br />
<br />
|-<br />
! Icehouse<br />
| 0.9.6<br />
| 0.9.11<br />
<br />
|-<br />
! Juno<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Kilo<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Liberty<br />
| 0.9.11<br />
| 0.10.2<br />
<br />
|-<br />
! Mitaka<br />
| 0.10.2<br />
| 1.2.1<br />
<br />
|-<br />
! Newton<br />
| 1.2.1<br />
| 1.2.1<br />
| 1.5.3<br />
| 1.5.3<br />
<br />
|-<br />
! Ocata<br />
| 1.2.1<br />
| 1.2.9<br />
| 1.5.3<br />
| 2.1.0<br />
<br />
|-<br />
! Pike<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Queens<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Rocky<br />
| 1.3.1<br />
| 3.0.0<br />
| 2.5.0<br />
| 2.8.0<br />
<br />
|-<br />
! Stein (draft)<br />
| ? 3.0.0<br />
| ? 4.0.0<br />
| ? 2.8.0<br />
| ? 2.11.0<br />
<br />
|}<br />
<br />
=== Distro minimum versions ===<br />
<br />
This table provides information on a representative sample of OS distros and the version of libirt/qemu/libguestfs that they ship. This is *NOT* intended to be an exhaustive list of distros where OpenStack Nova can run - it is intended to run on any Linux distro which can satisfy the minimum required software versions. This table merely aims to help identify when min required versions can be reasonably updated without losing support for important OS distros.<br />
<br />
When NEXT_MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be changed to have <strike>strikethrough</strike> format.<br />
<br />
When MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be deleted from this table<br />
<br />
{| class="wikitable"<br />
|-<br />
! OS Distro<br />
! GA date<br />
! Libvirt<br />
! QEMU/KVM<br />
! libguestfs<br />
<br />
|-<br />
! Debian !! !!<br />
<br />
|-<br />
| Stretch<br />
| 2017-06-17<br />
| 3.0.0<br />
| 2.8.0<br />
| 1.34.6<br />
<br />
|-<br />
| Buster/Sid<br />
| checked on 2018-04-05<br />
| 4.1.0<br />
| 2.11<br />
| 1.36.13<br />
<br />
|-<br />
! Fedora !! !!<br />
<br />
|-<br />
| 26<br />
| 2017-07-11<br />
| 3.2.1<br />
| 2.9.0 <br />
| 1.36.4<br />
<br />
|-<br />
| 27<br />
| 2017-11-14<br />
| 3.7.0<br />
| 2.10.0<br />
| 1.37.29<br />
<br />
|-<br />
| 28<br />
| 2018-05-01<br />
| 4.1.0<br />
| 2.11.1<br />
| 1.37.29<br />
<br />
|-<br />
! KVM for IBM z Systems !! !!<br />
<br />
|-<br />
| 1.1.0<br />
| <br />
| 1.2.13<br />
| 2.3.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.1<br />
| <br />
| 1.2.21<br />
| 2.4.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.2<br />
| <br />
| 1.3.3<br />
| 2.6.0<br />
| N/A<br />
<br />
|-<br />
! openSUSE !! !!<br />
<br />
|-<br />
| Leap 42.2<br />
| 2016-11-16<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 42.3<br />
| 2017-07<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 15.0<br />
| 2018-05<br />
| 4.0.0<br />
| 2.11.1<br />
| 1.38.0<br />
<br />
|-<br />
! Oracle Linux * !! !!<br />
<br />
|-<br />
| 7<br />
|<br />
| 3.10.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
! RHEL * !! !!<br />
<br />
|-<br />
| 7.1<br />
| 2015-03-05<br />
| 1.2.8<br />
| 2.1.2<br />
| 1.28.1<br />
<br />
|-<br />
| 7.2<br />
| 2015-11-19<br />
| 1.2.17<br />
| 2.3.0<br />
| 1.28.1<br />
<br />
|-<br />
| 7.3<br />
| 2016-11-03<br />
| 2.0.0<br />
| 2.6.0<br />
| 1.32.7<br />
<br />
|-<br />
| 7.4<br />
| 2017-08-01<br />
| 3.2.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
<br />
! SLES !! !!<br />
<br />
|-<br />
| 12<br />
|<br />
| 1.2.5<br />
| 2.0.2<br />
| 1.26.9<br />
<br />
|-<br />
| 12SP1<br />
| 2016-01-12<br />
| 1.2.18<br />
| 2.3.1<br />
| 1.26.10<br />
<br />
|-<br />
| 12SP2<br />
| 2016-11<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| 12SP3<br />
| 2017-09<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
! Ubuntu !! !!<br />
<br />
|-<br />
| 14.04 (Trusty LTS)<br />
|<br />
| 1.2.2<br />
| 2.0.0<br />
| 1.24.5<br />
<br />
|-<br />
| 16.04 (Xenial LTS)<br />
|<br />
| 1.3.1<br />
| 2.5.0<br />
| 1.32.2<br />
<br />
|-<br />
| 18.04 (Bionic LTS)<br />
| 2018-04-26<br />
| 4.0.0<br />
| 2.11<br />
| 1.36.13<br />
|}<br />
<br />
NB: maintain alphabetical ordering of distros, followed by oldest released versions first<br />
<br />
NB2: RHEL versions of QEMU refer to the qemu-kvm-rhev RPM, '''not''' the qemu-kvm RPM, since the former is what is intended for use with OpenStack<br />
<br />
NB3: Oracle Linux versions for QEMU and libvirt refer to those used in the docker containers supplied with Oracle OpenStack 4.0. Newer versions will likely be adopted in subsequent releases of Oracle OpenStack. Versions bundled in the OS are aligned with RHEL (i.e. old). Whilst vanilla OpenStack on Oracle Linux is not supported, recent versions of QEMU and libvirt RPMs may be found in the "developer_UEKR5" YUM repository.</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=LibvirtDistroSupportMatrix&diff=165096LibvirtDistroSupportMatrix2018-09-24T12:36:35Z<p>John Garbutt: /* Nova release min version */</p>
<hr />
<div>== Libvirt OS distribution support matrix ==<br />
<br />
This page documents the libvirt versions present in the various distro versions that OpenStack Nova aims to be deployable with. <br />
<br />
=== Libvirt min version change policy ===<br />
<br />
At the start of each Nova development cycle this matrix will be consulted to determine if it is viable to drop support for any end-of-life or otherwise undesired distro versions. Based on this distro evaluation, it may be possible to increase the min required version of libvirt in Nova, and thus drop some compatibility code for older versions.<br />
<br />
When a decision to update the minimum required libvirt version is made, there must be a warning issued for one cycle. This is achieved by editting nova/virt/libvirt/driver.py to set<br />
<br />
NEXT_MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
This causes a deprecation warning to be printed when Nova starts up warning the admin that the version of libvirt they are on will be dropped in the subsequent release.<br />
<br />
After a version has been listed in NEXT_MIN_LIBVIRT_VERSION for one release cycle, the corresponding actual min required libvirt can be updated by setting<br />
<br />
MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
At this point of course, an even newer version might be set in NEXT_MIN_LIBVIRT_VERSION to repeat the process....<br />
<br />
There is more background on the rationale used for picking minimum versions in the operators mailing list thread here:<br />
<br />
http://lists.openstack.org/pipermail/openstack-operators/2015-May/007012.html<br />
<br />
=== QEMU min version change policy ===<br />
<br />
After deciding the minimum libvirt version, the minimum QEMU version is determined by looking for the lowest QEMU version from all the distros that support the decided libvirt version<br />
<br />
=== Nova release min version ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Nova version<br />
! Current min libvirt<br />
! Next min libvirt<br />
! Current min QEMU<br />
! Next min QEMU<br />
<br />
|-<br />
! Havana<br />
| 0.9.6<br />
| 0.9.6<br />
<br />
|-<br />
! Icehouse<br />
| 0.9.6<br />
| 0.9.11<br />
<br />
|-<br />
! Juno<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Kilo<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Liberty<br />
| 0.9.11<br />
| 0.10.2<br />
<br />
|-<br />
! Mitaka<br />
| 0.10.2<br />
| 1.2.1<br />
<br />
|-<br />
! Newton<br />
| 1.2.1<br />
| 1.2.1<br />
| 1.5.3<br />
| 1.5.3<br />
<br />
|-<br />
! Ocata<br />
| 1.2.1<br />
| 1.2.9<br />
| 1.5.3<br />
| 2.1.0<br />
<br />
|-<br />
! Pike<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Queens<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Rocky<br />
| 1.3.1<br />
| 3.0.0<br />
| 2.5.0<br />
| 2.8.0<br />
<br />
|-<br />
! Stein (draft)<br />
| ? 3.0.0<br />
| ? 4.0.0<br />
| ? 2.8.0<br />
| ? 2.11.0<br />
<br />
|}<br />
<br />
=== Distro minimum versions ===<br />
<br />
This table provides information on a representative sample of OS distros and the version of libirt/qemu/libguestfs that they ship. This is *NOT* intended to be an exhaustive list of distros where OpenStack Nova can run - it is intended to run on any Linux distro which can satisfy the minimum required software versions. This table merely aims to help identify when min required versions can be reasonably updated without losing support for important OS distros.<br />
<br />
When NEXT_MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be changed to have <strike>strikethrough</strike> format.<br />
<br />
When MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be deleted from this table<br />
<br />
{| class="wikitable"<br />
|-<br />
! OS Distro<br />
! GA date<br />
! Libvirt<br />
! QEMU/KVM<br />
! libguestfs<br />
<br />
|-<br />
! Debian !! !!<br />
<br />
|-<br />
| Stretch<br />
| 2017-06-17<br />
| 3.0.0<br />
| 2.8.0<br />
| 1.34.6<br />
<br />
|-<br />
| Buster/Sid<br />
| checked on 2018-04-05<br />
| 4.1.0<br />
| 2.11<br />
| 1.36.13<br />
<br />
|-<br />
! Fedora !! !!<br />
<br />
|-<br />
| 26<br />
| 2017-07-11<br />
| 3.2.1<br />
| 2.9.0 <br />
| 1.36.4<br />
<br />
|-<br />
| 27<br />
| 2017-11-14<br />
| 3.7.0<br />
| 2.10.0<br />
| 1.37.29<br />
<br />
|-<br />
! KVM for IBM z Systems !! !!<br />
<br />
|-<br />
| 1.1.0<br />
| <br />
| 1.2.13<br />
| 2.3.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.1<br />
| <br />
| 1.2.21<br />
| 2.4.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.2<br />
| <br />
| 1.3.3<br />
| 2.6.0<br />
| N/A<br />
<br />
|-<br />
! openSUSE !! !!<br />
<br />
|-<br />
| Leap 42.2<br />
| 2016-11-16<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 42.3<br />
| 2017-07<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 15.0<br />
| 2018-05<br />
| 4.0.0<br />
| 2.11.1<br />
| 1.38.0<br />
<br />
|-<br />
! Oracle Linux * !! !!<br />
<br />
|-<br />
| 7<br />
|<br />
| 3.10.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
! RHEL * !! !!<br />
<br />
|-<br />
| 7.1<br />
| 2015-03-05<br />
| 1.2.8<br />
| 2.1.2<br />
| 1.28.1<br />
<br />
|-<br />
| 7.2<br />
| 2015-11-19<br />
| 1.2.17<br />
| 2.3.0<br />
| 1.28.1<br />
<br />
|-<br />
| 7.3<br />
| 2016-11-03<br />
| 2.0.0<br />
| 2.6.0<br />
| 1.32.7<br />
<br />
|-<br />
| 7.4<br />
| 2017-08-01<br />
| 3.2.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
<br />
! SLES !! !!<br />
<br />
|-<br />
| 12<br />
|<br />
| 1.2.5<br />
| 2.0.2<br />
| 1.26.9<br />
<br />
|-<br />
| 12SP1<br />
| 2016-01-12<br />
| 1.2.18<br />
| 2.3.1<br />
| 1.26.10<br />
<br />
|-<br />
| 12SP2<br />
| 2016-11<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| 12SP3<br />
| 2017-09<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
! Ubuntu !! !!<br />
<br />
|-<br />
| 14.04 (Trusty LTS)<br />
|<br />
| 1.2.2<br />
| 2.0.0<br />
| 1.24.5<br />
<br />
|-<br />
| 16.04 (Xenial LTS)<br />
|<br />
| 1.3.1<br />
| 2.5.0<br />
| 1.32.2<br />
<br />
|-<br />
| 18.04 (Bionic LTS)<br />
| 2018-04-26<br />
| 4.0.0<br />
| 2.11<br />
| 1.36.13<br />
|}<br />
<br />
NB: maintain alphabetical ordering of distros, followed by oldest released versions first<br />
<br />
NB2: RHEL versions of QEMU refer to the qemu-kvm-rhev RPM, '''not''' the qemu-kvm RPM, since the former is what is intended for use with OpenStack<br />
<br />
NB3: Oracle Linux versions for QEMU and libvirt refer to those used in the docker containers supplied with Oracle OpenStack 4.0. Newer versions will likely be adopted in subsequent releases of Oracle OpenStack. Versions bundled in the OS are aligned with RHEL (i.e. old). Whilst vanilla OpenStack on Oracle Linux is not supported, recent versions of QEMU and libvirt RPMs may be found in the "developer_UEKR5" YUM repository.</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=LibvirtDistroSupportMatrix&diff=165095LibvirtDistroSupportMatrix2018-09-24T12:31:33Z<p>John Garbutt: /* Nova release min version */</p>
<hr />
<div>== Libvirt OS distribution support matrix ==<br />
<br />
This page documents the libvirt versions present in the various distro versions that OpenStack Nova aims to be deployable with. <br />
<br />
=== Libvirt min version change policy ===<br />
<br />
At the start of each Nova development cycle this matrix will be consulted to determine if it is viable to drop support for any end-of-life or otherwise undesired distro versions. Based on this distro evaluation, it may be possible to increase the min required version of libvirt in Nova, and thus drop some compatibility code for older versions.<br />
<br />
When a decision to update the minimum required libvirt version is made, there must be a warning issued for one cycle. This is achieved by editting nova/virt/libvirt/driver.py to set<br />
<br />
NEXT_MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
This causes a deprecation warning to be printed when Nova starts up warning the admin that the version of libvirt they are on will be dropped in the subsequent release.<br />
<br />
After a version has been listed in NEXT_MIN_LIBVIRT_VERSION for one release cycle, the corresponding actual min required libvirt can be updated by setting<br />
<br />
MIN_LIBVIRT_VESION = (X, Y, Z)<br />
<br />
At this point of course, an even newer version might be set in NEXT_MIN_LIBVIRT_VERSION to repeat the process....<br />
<br />
There is more background on the rationale used for picking minimum versions in the operators mailing list thread here:<br />
<br />
http://lists.openstack.org/pipermail/openstack-operators/2015-May/007012.html<br />
<br />
=== QEMU min version change policy ===<br />
<br />
After deciding the minimum libvirt version, the minimum QEMU version is determined by looking for the lowest QEMU version from all the distros that support the decided libvirt version<br />
<br />
=== Nova release min version ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! Nova version<br />
! Current min libvirt<br />
! Next min libvirt<br />
! Current min QEMU<br />
! Next min QEMU<br />
<br />
|-<br />
! Havana<br />
| 0.9.6<br />
| 0.9.6<br />
<br />
|-<br />
! Icehouse<br />
| 0.9.6<br />
| 0.9.11<br />
<br />
|-<br />
! Juno<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Kilo<br />
| 0.9.11<br />
| 0.9.11<br />
<br />
|-<br />
! Liberty<br />
| 0.9.11<br />
| 0.10.2<br />
<br />
|-<br />
! Mitaka<br />
| 0.10.2<br />
| 1.2.1<br />
<br />
|-<br />
! Newton<br />
| 1.2.1<br />
| 1.2.1<br />
| 1.5.3<br />
| 1.5.3<br />
<br />
|-<br />
! Ocata<br />
| 1.2.1<br />
| 1.2.9<br />
| 1.5.3<br />
| 2.1.0<br />
<br />
|-<br />
! Pike<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Queens<br />
| 1.2.9<br />
| 1.3.1<br />
| 2.1.0<br />
| 2.5.0<br />
<br />
|-<br />
! Rocky<br />
| 1.3.1<br />
| 3.0.0<br />
| 2.5.0<br />
| 2.8.0<br />
<br />
|-<br />
! Stein (draft)<br />
| <br />
| <br />
| ?<br />
| ?<br />
<br />
|}<br />
<br />
=== Distro minimum versions ===<br />
<br />
This table provides information on a representative sample of OS distros and the version of libirt/qemu/libguestfs that they ship. This is *NOT* intended to be an exhaustive list of distros where OpenStack Nova can run - it is intended to run on any Linux distro which can satisfy the minimum required software versions. This table merely aims to help identify when min required versions can be reasonably updated without losing support for important OS distros.<br />
<br />
When NEXT_MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be changed to have <strike>strikethrough</strike> format.<br />
<br />
When MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be deleted from this table<br />
<br />
{| class="wikitable"<br />
|-<br />
! OS Distro<br />
! GA date<br />
! Libvirt<br />
! QEMU/KVM<br />
! libguestfs<br />
<br />
|-<br />
! Debian !! !!<br />
<br />
|-<br />
| Stretch<br />
| 2017-06-17<br />
| 3.0.0<br />
| 2.8.0<br />
| 1.34.6<br />
<br />
|-<br />
| Buster/Sid<br />
| checked on 2018-04-05<br />
| 4.1.0<br />
| 2.11<br />
| 1.36.13<br />
<br />
|-<br />
! Fedora !! !!<br />
<br />
|-<br />
| 26<br />
| 2017-07-11<br />
| 3.2.1<br />
| 2.9.0 <br />
| 1.36.4<br />
<br />
|-<br />
| 27<br />
| 2017-11-14<br />
| 3.7.0<br />
| 2.10.0<br />
| 1.37.29<br />
<br />
|-<br />
! KVM for IBM z Systems !! !!<br />
<br />
|-<br />
| 1.1.0<br />
| <br />
| 1.2.13<br />
| 2.3.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.1<br />
| <br />
| 1.2.21<br />
| 2.4.0<br />
| N/A<br />
<br />
|-<br />
| 1.1.2<br />
| <br />
| 1.3.3<br />
| 2.6.0<br />
| N/A<br />
<br />
|-<br />
! openSUSE !! !!<br />
<br />
|-<br />
| Leap 42.2<br />
| 2016-11-16<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 42.3<br />
| 2017-07<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
| Leap 15.0<br />
| 2018-05<br />
| 4.0.0<br />
| 2.11.1<br />
| 1.38.0<br />
<br />
|-<br />
! Oracle Linux * !! !!<br />
<br />
|-<br />
| 7<br />
|<br />
| 3.10.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
! RHEL * !! !!<br />
<br />
|-<br />
| 7.1<br />
| 2015-03-05<br />
| 1.2.8<br />
| 2.1.2<br />
| 1.28.1<br />
<br />
|-<br />
| 7.2<br />
| 2015-11-19<br />
| 1.2.17<br />
| 2.3.0<br />
| 1.28.1<br />
<br />
|-<br />
| 7.3<br />
| 2016-11-03<br />
| 2.0.0<br />
| 2.6.0<br />
| 1.32.7<br />
<br />
|-<br />
| 7.4<br />
| 2017-08-01<br />
| 3.2.0<br />
| 2.9.0<br />
| 1.36.3<br />
<br />
|-<br />
<br />
! SLES !! !!<br />
<br />
|-<br />
| 12<br />
|<br />
| 1.2.5<br />
| 2.0.2<br />
| 1.26.9<br />
<br />
|-<br />
| 12SP1<br />
| 2016-01-12<br />
| 1.2.18<br />
| 2.3.1<br />
| 1.26.10<br />
<br />
|-<br />
| 12SP2<br />
| 2016-11<br />
| 2.0.0<br />
| 2.6.1<br />
| 1.32.4<br />
<br />
|-<br />
| 12SP3<br />
| 2017-09<br />
| 3.3.0<br />
| 2.9.0<br />
| 1.32.4<br />
<br />
|-<br />
! Ubuntu !! !!<br />
<br />
|-<br />
| 14.04 (Trusty LTS)<br />
|<br />
| 1.2.2<br />
| 2.0.0<br />
| 1.24.5<br />
<br />
|-<br />
| 16.04 (Xenial LTS)<br />
|<br />
| 1.3.1<br />
| 2.5.0<br />
| 1.32.2<br />
<br />
|-<br />
| 18.04 (Bionic LTS)<br />
| 2018-04-26<br />
| 4.0.0<br />
| 2.11<br />
| 1.36.13<br />
|}<br />
<br />
NB: maintain alphabetical ordering of distros, followed by oldest released versions first<br />
<br />
NB2: RHEL versions of QEMU refer to the qemu-kvm-rhev RPM, '''not''' the qemu-kvm RPM, since the former is what is intended for use with OpenStack<br />
<br />
NB3: Oracle Linux versions for QEMU and libvirt refer to those used in the docker containers supplied with Oracle OpenStack 4.0. Newer versions will likely be adopted in subsequent releases of Oracle OpenStack. Versions bundled in the OS are aligned with RHEL (i.e. old). Whilst vanilla OpenStack on Oracle Linux is not supported, recent versions of QEMU and libvirt RPMs may be found in the "developer_UEKR5" YUM repository.</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=PTG/Stein/Etherpads&diff=164623PTG/Stein/Etherpads2018-09-09T12:00:34Z<p>John Garbutt: Add scientific sig</p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering in Denver, 2018. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
For what's happening '''right now''' (during the event), see the [http://ptg.openstack.org/ptg.html ptgbot page].<br />
<br />
'''Projects:''' <br />
* Blazar - https://etherpad.openstack.org/p/blazar-ptg-stein<br />
* Barbican - https://etherpad.openstack.org/p/barbican-stein-ptg<br />
* Charms - https://etherpad.openstack.org/p/charms-stein-ptg<br />
* Cinder - https://etherpad.openstack.org/p/cinder-ptg-planning-denver-9-2018<br />
* Cyborg - https://etherpad.openstack.org/p/cyborg-ptg-stein<br />
* Docs/I18n - https://etherpad.openstack.org/p/docs-i18n-ptg-stein<br />
* Glance - https://etherpad.openstack.org/p/stein-ptg-glance-planning<br />
* Heat - https://etherpad.openstack.org/p/2018-Denver-PTG-Heat<br />
* Horizon - https://etherpad.openstack.org/p/horizon-ptg-planning-denver-2018<br />
* Ironic - https://etherpad.openstack.org/p/ironic-stein-ptg<br />
* Infrastructure - https://etherpad.openstack.org/p/infra-ptg-denver-2018<br />
* Keystone - https://etherpad.openstack.org/p/keystone-stein-ptg<br />
* Kolla - https://etherpad.openstack.org/p/kolla-stein-ptg-planning<br />
* Manila - https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018<br />
* Masakari - https://etherpad.openstack.org/p/masakari-ptg-stein<br />
* Monasca - https://etherpad.openstack.org/p/monasca-ptg-stein<br />
* Neutron - https://etherpad.openstack.org/p/neutron-stein-ptg<br />
* Nova - https://etherpad.openstack.org/p/nova-ptg-stein<br />
* Octavia - https://etherpad.openstack.org/p/octavia-stein-ptg<br />
* Openstack-Ansible - https://etherpad.openstack.org/p/osa-stein-ptg<br />
* OpenStack-Helm - https://etherpad.openstack.org/p/openstack-helm-ptg-stein<br />
* Oslo - https://etherpad.openstack.org/p/oslo-stein-ptg-planning<br />
* QA - https://etherpad.openstack.org/p/qa-stein-ptg<br />
* Release Management - https://etherpad.openstack.org/p/relmgt-stein-ptg<br />
* Requirements - https://etherpad.openstack.org/p/stein-PTG-requirements<br />
* Sahara - https://etherpad.openstack.org/p/sahara-stein-ptg<br />
* Searchlight - https://etherpad.openstack.org/p/searchlight-stein-ptg<br />
* Swift - https://etherpad.openstack.org/p/swift-ptg-planning-denver-2018<br />
* Tacker - https://etherpad.openstack.org/p/Tacker-PTG-Stein<br />
* TripleO - https://etherpad.openstack.org/p/tripleo-ptg-stein<br />
* Puppet - https://etherpad.openstack.org/p/puppet-ptg-stein<br />
* Watcher - https://etherpad.openstack.org/p/stein-watcher-ptg<br />
<br />
<br />
'''SIG/Theme/Other:'''<br />
* API-SIG - https://etherpad.openstack.org/p/api-sig-stein-ptg<br />
* FC-SIG - https://etherpad.openstack.org/p/FC_SIG_ptg_stein<br />
* Interop WG - https://etherpad.openstack.org/p/InteropRefstackPTGDenver_2018<br />
* K8s-SIG - https://etherpad.openstack.org/p/sig-k8s-2018-denver-ptg<br />
* Ops Meetup - https://etherpad.openstack.org/p/ops-meetup-ptg-denver-2018<br />
* Public Cloud WG - https://etherpad.openstack.org/p/publiccloud-wg-stein-ptg<br />
* Scientific SIG - https://etherpad.openstack.org/p/scientific-sig-denverptg2018<br />
* Self-healing SIG - https://etherpad.openstack.org/p/self-healing-sig-stein-ptg<br />
* Storyboard - https://etherpad.openstack.org/p/sb-stein-ptg-planning<br />
* Technical Committee - https://etherpad.openstack.org/p/tc-stein-ptg<br />
* Upgrade SIG - https://etherpad.openstack.org/p/upgrade-sig-ptg-stein<br />
* User Committee - https://etherpad.openstack.org/p/uc-stein-ptg<br />
<br />
<br />
'''Strategic Projects:'''<br />
* Airship - https://etherpad.openstack.org/p/AirshipPTG4<br />
* Edge Computing Group - https://etherpad.openstack.org/p/EdgeComputingGroupPTG4<br />
* StarlingX - https://etherpad.openstack.org/p/stx-PTG-agenda<br />
<br />
<br />
'''Other:'''<br />
* Future of PTGs / Event feedback session - https://etherpad.openstack.org/p/ptg-future-and-ptg4-feedback</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Upstream_Working_Groups&diff=156411Upstream Working Groups2017-09-01T10:43:27Z<p>John Garbutt: /* List */</p>
<hr />
<div>= Upstream Working Groups =<br />
<br />
Upstream work in OpenStack is organized under official [https://governance.openstack.org/tc/reference/projects/index.html project teams], but also more informal groups of people working in the same area with a common goal. Those '''working groups''' grow naturally and organically, and no permission is needed to create a working group. Just add them to this page to make your group easier to find. Workgroups should use OpenStack open communication media, including discussions on the openstack-dev mailing-list.<br />
<br />
Note: most of those working groups are expected to become [[OpenStack_SIGs]] soon.<br />
<br />
=== List ===<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Working Group !! Goal !! Status !! Chair(s) !! Meeting<br />
|-<br />
| [https://git.openstack.org/cgit/openstack/arch-wg/tree/doc/source/index.rst Architecture Working Group] || Be the recognized forum of expertise on the design and architecture of OpenStack and provide guidance and resources to the Technical Committee and the entire OpenStack community on architectural matters. || Inactive || - || -<br />
|-<br />
| [[Meetings/SWGMeeting|Stewardship Working Group]] || Provide resources, expertise, and a forum for discussion on leadership, communication and decision making processes in the entire OpenStack community, as well as recommendations to the TC on improvements in these areas.|| Inactive || - || -<br />
|-<br />
| [[VM & BM Working Group]] || Building a strong feedback loop between developers, users and operators to help improve the user experience and operator experience when using Nova, Ironic, Cinder, Neutron and Keystone together. || Active || John Garbutt and Lance Bragstad || (trying none)<br />
|-<br />
| [[Deployment]] || Encourage cross-team discussions around deployment (and upgrade) workflow for OpenStack, open collaboration around the tools available. || Active || Steve Hardy, Andy McCrae, Emilien Macchi || (trying none)<br />
|}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=VM_%26_BM_Working_Group&diff=156410VM & BM Working Group2017-09-01T10:42:49Z<p>John Garbutt: /* How to Join */</p>
<hr />
<div>The Virtual Machine and Baremetal working group are building a strong feedback loop between developers, users and operators to help improve the user experience and operator experience when using Nova, Ironic, Cinder, Neutron and Keystone together.<br />
<br />
More news coming soon.<br />
<br />
== How to Join ==<br />
<br />
The kick start of this group is planned for this Forum session:<br />
<br />
* http://forumtopics.openstack.org/cfp/details/10<br />
* https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform<br />
<br />
We are also planning a PTG session to work out why nothing has happened recently:<br />
<br />
* https://etherpad.openstack.org/p/queens-PTG-vmbm</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=PTG/Queens/Etherpads&diff=155953PTG/Queens/Etherpads2017-08-14T12:44:40Z<p>John Garbutt: /* Monday -> Tuesday */</p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering in Denver. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
=== Whole Week ===<br />
* Infra: https://etherpad.openstack.org/p/infra-ptg-queens<br />
* QA: https://etherpad.openstack.org/p/qa-queens-ptg<br />
<br />
=== Monday -> Tuesday ===<br />
* Docs: https://etherpad.openstack.org/p/denver-doc-PTG<br />
* Horizon: https://etherpad.openstack.org/p/horizon-ptg-queens<br />
* i18n: https://etherpad.openstack.org/p/denver-i18n-PTG<br />
* OpenStackClient: https://etherpad.openstack.org/p/osc-queens-ptg<br />
* Oslo: https://etherpad.openstack.org/p/oslo-ptg-queens<br />
* Refstack: https://etherpad.openstack.org/p/InteropDenver2017PTG<br />
* Requirements: https://etherpad.openstack.org/p/queens-PTG-requirements<br />
* Stable: https://etherpad.openstack.org/p/queens-PTG-stable<br />
* VM and BM SIG: https://etherpad.openstack.org/p/queens-PTG-vmbm<br />
<br />
=== Wednesday -> Thursday ===<br />
* Barbican: https://etherpad.openstack.org/p/barbican-ptg-queens<br />
* Charms: https://etherpad.openstack.org/p/ptg-queens-charms<br />
* Congress: https://etherpad.openstack.org/p/congress-ptg-queens<br />
* Freezer: https://etherpad.openstack.org/p/freezer-ptg-queens<br />
* Glare: https://etherpad.openstack.org/p/glare-ptg-queens<br />
* Heat: https://etherpad.openstack.org/p/heat-queens-ptg<br />
* Mistral: https://etherpad.openstack.org/p/mistral-ptg-queens<br />
* Puppet: https://etherpad.openstack.org/p/puppet-queens-ptg <br />
* Sahara: https://etherpad.openstack.org/p/sahara-queens-ptg<br />
* Trove: https://etherpad.openstack.org/p/trove-queens-ptg<br />
<br />
=== Wednesday -> Friday ===<br />
* Ansible: https://etherpad.openstack.org/p/osa-denver-PTG-planning<br />
* Cinder: https://etherpad.openstack.org/p/cinder-ptg-queens<br />
* Glance: https://etherpad.openstack.org/p/glance-queens-ptg-planning <br />
* Ironic: https://etherpad.openstack.org/p/ironic-queens-ptg<br />
* Keystone: https://etherpad.openstack.org/p/keystone-queens-ptg<br />
* Kolla: https://etherpad.openstack.org/p/kolla-queens-ptg-planning<br />
* Neutron: https://etherpad.openstack.org/p/neutron-queens-ptg<br />
* Nova: https://etherpad.openstack.org/p/nova-ptg-queens<br />
* Octavia: https://etherpad.openstack.org/p/octavia-ptg-queens<br />
* Swift: https://etherpad.openstack.org/p/swift-ptg-queens<br />
* TripleO: https://etherpad.openstack.org/p/tripleo-ptg-queens</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153872Forum/Boston20172017-05-05T09:17:12Z<p>John Garbutt: /* Thursday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.<br />
<br />
<br />
'''See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]'''<br />
<br />
'''See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]'''<br />
<br />
'''See also - [https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms Hacking Rooms Schedule]'''<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
= Monday =<br />
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal<br />
* [11:15am-12:45pm] - Nova - Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding<br />
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us - <br />
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
* [4:40pm-5:20pm] - Should we kill Stackalytics? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics<br />
* [5:30pm-6:10pm] - Using Searchlight to list instances across cells in nova-api - https://etherpad.openstack.org/p/BOS-forum-using-searchlight-to-list-instances<br />
<br />
= Tuesday =<br />
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages<br />
* [12:05pm-12:45pm] LCOO Roadmap Working Session - https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session<br />
* [2:00pm-3:30pm] Barbican and Security Projects Onboarding - https://etherpad.openstack.org/p/BOS-forum-barbican-onboarding<br />
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage<br />
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations<br />
* [9:50am-10:30am] Vitrage Usability and New Insights: Where Do We Go Next? - https://etherpad.openstack.org/p/BOS-forum-vitrage-usability-and-new-insights<br />
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal<br />
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback<br />
* [2:40pm-3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [2:40pm-3:20pm] Key Management Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-key-management<br />
* [3:30pm-4:10pm] Compute Instance/Volume Affinity for HPC - https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinity-hpc<br />
* [4:30pm-5:10pm] Moving Resource Claims from nova-compute to nova-scheduler - https://etherpad.openstack.org/p/BOS-forum-move-claims-from-compute-to-scheduler<br />
* [5:20pm-6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements<br />
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins<br />
* [9:50am-10:30am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal<br />
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds<br />
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications<br />
<br />
<br />
==Thursday Afternoon session sign-up==<br />
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
* 1:30-2:10 MR102 - available<br />
* 2:20-3:00 MR102 - available<br />
* 3:10-3:50 MR102 - available<br />
* 3:50-4:10 MR102 - available<br />
* 4:10-4:50 MR102 - available<br />
* 5:00-5:40 MR102 - available<br />
* 1:30-2:10 MR103 - available<br />
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]<br />
* 3:10-3:50 MR103 - available<br />
* 3:50-4:10 MR103 - available<br />
* 4:10-4:50 MR103 - available<br />
* 5:00-5:40 MR103 - available<br />
* 1:30-2:10 MR104 - available<br />
* 2:20-3:00 MR104 - available<br />
* 3:10-3:50 MR104 - available<br />
* 3:50-4:10 MR104 - available<br />
* 4:10-4:50 MR104 - available<br />
* 5:00-5:40 MR104 - [https://etherpad.openstack.org/p/pike-forum-tc-gathering TC members open gathering]<br />
</div><br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153733Forum/Boston20172017-05-02T17:14:49Z<p>John Garbutt: /* Wednesday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.<br />
<br />
<br />
<br />
<b>See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]</b><br />
<br />
<b> See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]</b><br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
<br />
#REDIRECT [[Target page name]]<br />
= Monday =<br />
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal<br />
* [11:15am-12:45pm] - Nova - Project Onboarding - <br />
* [11:15am-12:45pm] - Solum- Project Onboarding - <br />
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us - <br />
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
* [4:40pm-5:20pm] - Should we kill Stackalytics ? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics<br />
<br />
= Tuesday =<br />
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session<br />
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage<br />
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations<br />
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal<br />
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback<br />
* [2:40pm - 3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [5:20pm - 6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements<br />
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins<br />
* [11:15am-11:55am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal<br />
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds<br />
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications<br />
<br />
<br />
==Thursday Afternoon session sign-up==<br />
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
* 1:30-2:10 MR102 - available<br />
* 2:20-3:00 MR102 - available<br />
* 3:10-3:50 MR102 - available<br />
* 3:50-4:10 MR102 - available<br />
* 4:10-4:50 MR102 - available<br />
* 5:00-5:40 MR102 - available<br />
* 1:30-2:10 MR103 - available<br />
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]<br />
* 3:10-3:50 MR103 - available<br />
* 3:50-4:10 MR103 - available<br />
* 4:10-4:50 MR103 - available<br />
* 5:00-5:40 MR103 - available<br />
* 1:30-2:10 MR104 - available<br />
* 2:20-3:00 MR104 - available<br />
* 3:10-3:50 MR104 - available<br />
* 3:50-4:10 MR104 - available<br />
* 4:10-4:50 MR104 - available<br />
* 5:00-5:40 MR104 - TC members gathering (reflect back on the week, define next steps and discuss shared understandings)<br />
</div><br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153732Forum/Boston20172017-05-02T17:14:36Z<p>John Garbutt: /* Monday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.<br />
<br />
<br />
<br />
<b>See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]</b><br />
<br />
<b> See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]</b><br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
<br />
#REDIRECT [[Target page name]]<br />
= Monday =<br />
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal<br />
* [11:15am-12:45pm] - Nova - Project Onboarding - <br />
* [11:15am-12:45pm] - Solum- Project Onboarding - <br />
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us - <br />
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
* [4:40pm-5:20pm] - Should we kill Stackalytics ? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics<br />
<br />
= Tuesday =<br />
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session<br />
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage<br />
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations<br />
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operation-vm-and-baremetal<br />
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback<br />
* [2:40pm - 3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [5:20pm - 6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements<br />
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins<br />
* [11:15am-11:55am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal<br />
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds<br />
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications<br />
<br />
<br />
==Thursday Afternoon session sign-up==<br />
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
* 1:30-2:10 MR102 - available<br />
* 2:20-3:00 MR102 - available<br />
* 3:10-3:50 MR102 - available<br />
* 3:50-4:10 MR102 - available<br />
* 4:10-4:50 MR102 - available<br />
* 5:00-5:40 MR102 - available<br />
* 1:30-2:10 MR103 - available<br />
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]<br />
* 3:10-3:50 MR103 - available<br />
* 3:50-4:10 MR103 - available<br />
* 4:10-4:50 MR103 - available<br />
* 5:00-5:40 MR103 - available<br />
* 1:30-2:10 MR104 - available<br />
* 2:20-3:00 MR104 - available<br />
* 3:10-3:50 MR104 - available<br />
* 3:50-4:10 MR104 - available<br />
* 4:10-4:50 MR104 - available<br />
* 5:00-5:40 MR104 - TC members gathering (reflect back on the week, define next steps and discuss shared understandings)<br />
</div><br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153730Forum/Boston20172017-05-02T17:13:29Z<p>John Garbutt: /* Thursday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.<br />
<br />
<br />
<br />
<b>See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]</b><br />
<br />
<b> See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]</b><br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
<br />
#REDIRECT [[Target page name]]<br />
= Monday =<br />
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operation-vm-and-baremetal<br />
* [11:15am-12:45pm] - Nova - Project Onboarding - <br />
* [11:15am-12:45pm] - Solum- Project Onboarding - <br />
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us - <br />
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
* [4:40pm-5:20pm] - Should we kill Stackalytics ? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics<br />
<br />
= Tuesday =<br />
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session<br />
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage<br />
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations<br />
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operation-vm-and-baremetal<br />
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback<br />
* [2:40pm - 3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [5:20pm - 6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements<br />
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins<br />
* [11:15am-11:55am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal<br />
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds<br />
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications<br />
<br />
<br />
==Thursday Afternoon session sign-up==<br />
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
* 1:30-2:10 MR102 - available<br />
* 2:20-3:00 MR102 - available<br />
* 3:10-3:50 MR102 - available<br />
* 3:50-4:10 MR102 - available<br />
* 4:10-4:50 MR102 - available<br />
* 5:00-5:40 MR102 - available<br />
* 1:30-2:10 MR103 - available<br />
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]<br />
* 3:10-3:50 MR103 - available<br />
* 3:50-4:10 MR103 - available<br />
* 4:10-4:50 MR103 - available<br />
* 5:00-5:40 MR103 - available<br />
* 1:30-2:10 MR104 - available<br />
* 2:20-3:00 MR104 - available<br />
* 3:10-3:50 MR104 - available<br />
* 3:50-4:10 MR104 - available<br />
* 4:10-4:50 MR104 - available<br />
* 5:00-5:40 MR104 - TC members gathering (reflect back on the week, define next steps and discuss shared understandings)<br />
</div><br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153729Forum/Boston20172017-05-02T17:12:13Z<p>John Garbutt: /* Wednesday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.<br />
<br />
<br />
<br />
<b>See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]</b><br />
<br />
<b> See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]</b><br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
<br />
#REDIRECT [[Target page name]]<br />
= Monday =<br />
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operation-vm-and-baremetal<br />
* [11:15am-12:45pm] - Nova - Project Onboarding - <br />
* [11:15am-12:45pm] - Solum- Project Onboarding - <br />
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us - <br />
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
* [4:40pm-5:20pm] - Should we kill Stackalytics ? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics<br />
<br />
= Tuesday =<br />
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session<br />
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage<br />
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations<br />
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operation-vm-and-baremetal<br />
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback<br />
* [2:40pm - 3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [5:20pm - 6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements<br />
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins<br />
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds<br />
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications<br />
<br />
<br />
==Thursday Afternoon session sign-up==<br />
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
* 1:30-2:10 MR102 - available<br />
* 2:20-3:00 MR102 - available<br />
* 3:10-3:50 MR102 - available<br />
* 3:50-4:10 MR102 - available<br />
* 4:10-4:50 MR102 - available<br />
* 5:00-5:40 MR102 - available<br />
* 1:30-2:10 MR103 - available<br />
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]<br />
* 3:10-3:50 MR103 - available<br />
* 3:50-4:10 MR103 - available<br />
* 4:10-4:50 MR103 - available<br />
* 5:00-5:40 MR103 - available<br />
* 1:30-2:10 MR104 - available<br />
* 2:20-3:00 MR104 - available<br />
* 3:10-3:50 MR104 - available<br />
* 3:50-4:10 MR104 - available<br />
* 4:10-4:50 MR104 - available<br />
* 5:00-5:40 MR104 - TC members gathering (reflect back on the week, define next steps and discuss shared understandings)<br />
</div><br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=153728Forum/Boston20172017-05-02T17:09:45Z<p>John Garbutt: /* Monday */</p>
<hr />
<div>The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.<br />
<br />
<br />
<br />
<b>See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]</b><br />
<br />
<b> See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]</b><br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__NOTOC__<br />
</div><br />
<br />
= Event intro/closure =<br />
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101<br />
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback<br />
<br />
<br />
#REDIRECT [[Target page name]]<br />
= Monday =<br />
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operation-vm-and-baremetal<br />
* [11:15am-12:45pm] - Nova - Project Onboarding - <br />
* [11:15am-12:45pm] - Solum- Project Onboarding - <br />
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us - <br />
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap<br />
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey<br />
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management<br />
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone<br />
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy<br />
* [4:40pm-5:20pm] - Should we kill Stackalytics ? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics<br />
<br />
= Tuesday =<br />
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages<br />
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality<br />
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session<br />
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading<br />
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage<br />
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds<br />
<br />
= Wednesday =<br />
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware<br />
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration <br />
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations<br />
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification<br />
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack<br />
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement<br />
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback<br />
* [2:40pm - 3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session<br />
* [5:20pm - 6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks<br />
<br />
= Thursday =<br />
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements<br />
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins<br />
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals<br />
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds<br />
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications<br />
<br />
<br />
==Thursday Afternoon session sign-up==<br />
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
* 1:30-2:10 MR102 - available<br />
* 2:20-3:00 MR102 - available<br />
* 3:10-3:50 MR102 - available<br />
* 3:50-4:10 MR102 - available<br />
* 4:10-4:50 MR102 - available<br />
* 5:00-5:40 MR102 - available<br />
* 1:30-2:10 MR103 - available<br />
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]<br />
* 3:10-3:50 MR103 - available<br />
* 3:50-4:10 MR103 - available<br />
* 4:10-4:50 MR103 - available<br />
* 5:00-5:40 MR103 - available<br />
* 1:30-2:10 MR104 - available<br />
* 2:20-3:00 MR104 - available<br />
* 3:10-3:50 MR104 - available<br />
* 3:50-4:10 MR104 - available<br />
* 4:10-4:50 MR104 - available<br />
* 5:00-5:40 MR104 - TC members gathering (reflect back on the week, define next steps and discuss shared understandings)<br />
</div><br />
<br />
<br />
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░<br />
<br />
==(old) Brainstorming==<br />
Below here were the etherpads used during the agenda brainstorming process...<br />
<br />
====Catch-alls====<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
====Project Teams====<br />
<br />
=====Barbican=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
=====Cinder=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming<br />
<br />
=====Freezer=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming<br />
<br />
=====Glance=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
=====Heat=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming<br />
<br />
=====I18n=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
=====Ironic=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming<br />
<br />
=====Keystone=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming<br />
<br />
=====Nova=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
=====Oslo=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming<br />
<br />
=====Watcher=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming<br />
<br />
=====QA=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming<br />
<br />
=====Swift=====<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
====UC Working Groups ====<br />
<br />
<br />
<br />
=====Telecom/NFV Requirements=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
=====Scientific WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
=====Massively Distributed (Fog/Edge) WG=====<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
=====Public Cloud WG=====<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
====Other Working Groups====<br />
<br />
=====VM and Bare-metal platform group=====<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Stewardship_Working_Group&diff=153384Stewardship Working Group2017-04-19T12:10:16Z<p>John Garbutt: /* Collect and share best practices around being globally inclusive community */</p>
<hr />
<div>== Scope ==<br />
<br />
The [https://governance.openstack.org/tc OpenStack Technical Committee] adopted a [https://governance.openstack.org/tc/resolutions/20160705-stewardship.html resolution] to setup the Stewardship Working Group (SWG).<br />
<br />
It was the stated intent in establishing this working group that the community would benefit from establishing a small group to review the leadership, communication, and decision making processes of the TC and OpenStack projects as a whole, and propose a set of improvements based on the the concepts of "Servant Leadership" and "Stewardship". The SWG will be responsible for producing actionable recommendations and improvements that the TC can then consider for adoption and roll out to the OpenStack community. Anyone interested in leadership, stewardship, and OpenStack is welcome to join the working group. The SWG is an advisory body. Final decisions about any changes proposed by the SWG will be made by the TC.<br />
<br />
In particular, the SWG is interested in tackling:<br />
* How to improve the Technical Committee: write a vision, adopt consensus-based decision making, create distraction-free venues for TC discussion<br />
* What tools in the servant leadership could be used in OpenStack: look into building visions, using the bottom-line change framework, communicate more about servant leadership<br />
* Develop better leaders for OpenStack: expand training opportunities<br />
* Explore options to be more inclusive: Support non-native speakers, weird timezones, different cultures, non full-time contributors, first contributors<br />
* Address papercuts: facilitate keeping up with incoming information, address the difficulty to get ACKs on actions, make IRC more friendly<br />
<br />
<br />
== How to play ==<br />
<br />
Join us on the '''#openstack-swg''' channel on Freenode. Start threads (marked with "[swg]" subject prefix) on openstack-dev@lists.openstack.org.<br />
<br />
<br />
== Initiatives ==<br />
<br />
==== Build a vision for the TC ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Colette Alexander (gothicmindfood)<br />
; Goal<br />
: Create a two-year vision for the Technical Committee (based on Zingerman's visioning framework) to help drive decisions<br />
; Current state<br />
: Draft vision was built in an in-person workshop in Boston, then refined and posted for comments at [https://review.openstack.org/#/c/453262/].<br />
; Next steps/actions<br />
: Collect feedback and brainstorm needed modifications until the Boston summit<br />
: Presentation at the summit (gothicmindfood, johnthetubaguy, ttx)<br />
: Post second draft shortly after<br />
<br />
<br />
==== Develop an alternative to weekly meetings ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Flavio Percoco (flaper87) and Thierry Carrez (ttx)<br />
; Goal<br />
: Drop meetings for the SWG as an experiment, and develop alternatives (status whiteboard, async discussions...)<br />
; Current state<br />
: SWG dropped meetings but hasn't moved much since. Posted a status tracking wikipage (this page) as a way to keep track of progress<br />
; Next steps/actions/notes<br />
: ACTION: Try to get momentum around this status page (ttx)<br />
: ACTION: Explore solutions for the TC itself (flaper87)<br />
: (johnthetubaguy) I prefer some kind of rhythm to things, a weekly status email that points to this page could be a good start for SWG<br />
<br />
<br />
==== Collect and share best practices around being a globally inclusive community ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: John Garbutt (johnthetubaguy)<br />
; Goal<br />
: Make it easy for all parts of the community to be inclusive to contributors from across the globe<br />
: Share current best practices to help spark ideas on how we improve<br />
; Current state<br />
: Docs team have merged some great guidance: https://docs.openstack.org/contributor-guide/non-native-english-speakers.html<br />
; Next steps/actions/notes<br />
: ACTION: Prepare a project team guide patch to help discuss current best practices https://review.openstack.org/#/c/441923 (johnthetubaguy)<br />
: ACTION: Prepare governance patch around decisions at in person meetings (TBC)<br />
: ACTION: Debate around frequency of in-person meetings (TBC)</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Stewardship_Working_Group&diff=153383Stewardship Working Group2017-04-19T12:09:58Z<p>John Garbutt: /* Collect and share best practices around being globally inclusive community */</p>
<hr />
<div>== Scope ==<br />
<br />
The [https://governance.openstack.org/tc OpenStack Technical Committee] adopted a [https://governance.openstack.org/tc/resolutions/20160705-stewardship.html resolution] to setup the Stewardship Working Group (SWG).<br />
<br />
It was the stated intent in establishing this working group that the community would benefit from establishing a small group to review the leadership, communication, and decision making processes of the TC and OpenStack projects as a whole, and propose a set of improvements based on the the concepts of "Servant Leadership" and "Stewardship". The SWG will be responsible for producing actionable recommendations and improvements that the TC can then consider for adoption and roll out to the OpenStack community. Anyone interested in leadership, stewardship, and OpenStack is welcome to join the working group. The SWG is an advisory body. Final decisions about any changes proposed by the SWG will be made by the TC.<br />
<br />
In particular, the SWG is interested in tackling:<br />
* How to improve the Technical Committee: write a vision, adopt consensus-based decision making, create distraction-free venues for TC discussion<br />
* What tools in the servant leadership could be used in OpenStack: look into building visions, using the bottom-line change framework, communicate more about servant leadership<br />
* Develop better leaders for OpenStack: expand training opportunities<br />
* Explore options to be more inclusive: Support non-native speakers, weird timezones, different cultures, non full-time contributors, first contributors<br />
* Address papercuts: facilitate keeping up with incoming information, address the difficulty to get ACKs on actions, make IRC more friendly<br />
<br />
<br />
== How to play ==<br />
<br />
Join us on the '''#openstack-swg''' channel on Freenode. Start threads (marked with "[swg]" subject prefix) on openstack-dev@lists.openstack.org.<br />
<br />
<br />
== Initiatives ==<br />
<br />
==== Build a vision for the TC ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Colette Alexander (gothicmindfood)<br />
; Goal<br />
: Create a two-year vision for the Technical Committee (based on Zingerman's visioning framework) to help drive decisions<br />
; Current state<br />
: Draft vision was built in an in-person workshop in Boston, then refined and posted for comments at [https://review.openstack.org/#/c/453262/].<br />
; Next steps/actions<br />
: Collect feedback and brainstorm needed modifications until the Boston summit<br />
: Presentation at the summit (gothicmindfood, johnthetubaguy, ttx)<br />
: Post second draft shortly after<br />
<br />
<br />
==== Develop an alternative to weekly meetings ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Flavio Percoco (flaper87) and Thierry Carrez (ttx)<br />
; Goal<br />
: Drop meetings for the SWG as an experiment, and develop alternatives (status whiteboard, async discussions...)<br />
; Current state<br />
: SWG dropped meetings but hasn't moved much since. Posted a status tracking wikipage (this page) as a way to keep track of progress<br />
; Next steps/actions/notes<br />
: ACTION: Try to get momentum around this status page (ttx)<br />
: ACTION: Explore solutions for the TC itself (flaper87)<br />
: (johnthetubaguy) I prefer some kind of rhythm to things, a weekly status email that points to this page could be a good start for SWG<br />
<br />
<br />
==== Collect and share best practices around being globally inclusive community ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: John Garbutt (johnthetubaguy)<br />
; Goal<br />
: Make it easy for all parts of the community to be inclusive to contributors from across the globe<br />
: Share current best practices to help spark ideas on how we improve<br />
; Current state<br />
: Docs team have merged some great guidance: https://docs.openstack.org/contributor-guide/non-native-english-speakers.html<br />
; Next steps/actions/notes<br />
: ACTION: Prepare a project team guide patch to help discuss current best practices https://review.openstack.org/#/c/441923 (johnthetubaguy)<br />
: ACTION: Prepare governance patch around decisions at in person meetings (TBC)<br />
: ACTION: Debate around frequency of in-person meetings (TBC)</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Stewardship_Working_Group&diff=153382Stewardship Working Group2017-04-19T12:06:58Z<p>John Garbutt: /* Initiatives */</p>
<hr />
<div>== Scope ==<br />
<br />
The [https://governance.openstack.org/tc OpenStack Technical Committee] adopted a [https://governance.openstack.org/tc/resolutions/20160705-stewardship.html resolution] to setup the Stewardship Working Group (SWG).<br />
<br />
It was the stated intent in establishing this working group that the community would benefit from establishing a small group to review the leadership, communication, and decision making processes of the TC and OpenStack projects as a whole, and propose a set of improvements based on the the concepts of "Servant Leadership" and "Stewardship". The SWG will be responsible for producing actionable recommendations and improvements that the TC can then consider for adoption and roll out to the OpenStack community. Anyone interested in leadership, stewardship, and OpenStack is welcome to join the working group. The SWG is an advisory body. Final decisions about any changes proposed by the SWG will be made by the TC.<br />
<br />
In particular, the SWG is interested in tackling:<br />
* How to improve the Technical Committee: write a vision, adopt consensus-based decision making, create distraction-free venues for TC discussion<br />
* What tools in the servant leadership could be used in OpenStack: look into building visions, using the bottom-line change framework, communicate more about servant leadership<br />
* Develop better leaders for OpenStack: expand training opportunities<br />
* Explore options to be more inclusive: Support non-native speakers, weird timezones, different cultures, non full-time contributors, first contributors<br />
* Address papercuts: facilitate keeping up with incoming information, address the difficulty to get ACKs on actions, make IRC more friendly<br />
<br />
<br />
== How to play ==<br />
<br />
Join us on the '''#openstack-swg''' channel on Freenode. Start threads (marked with "[swg]" subject prefix) on openstack-dev@lists.openstack.org.<br />
<br />
<br />
== Initiatives ==<br />
<br />
==== Build a vision for the TC ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Colette Alexander (gothicmindfood)<br />
; Goal<br />
: Create a two-year vision for the Technical Committee (based on Zingerman's visioning framework) to help drive decisions<br />
; Current state<br />
: Draft vision was built in an in-person workshop in Boston, then refined and posted for comments at [https://review.openstack.org/#/c/453262/].<br />
; Next steps/actions<br />
: Collect feedback and brainstorm needed modifications until the Boston summit<br />
: Presentation at the summit (gothicmindfood, johnthetubaguy, ttx)<br />
: Post second draft shortly after<br />
<br />
<br />
==== Develop an alternative to weekly meetings ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Flavio Percoco (flaper87) and Thierry Carrez (ttx)<br />
; Goal<br />
: Drop meetings for the SWG as an experiment, and develop alternatives (status whiteboard, async discussions...)<br />
; Current state<br />
: SWG dropped meetings but hasn't moved much since. Posted a status tracking wikipage (this page) as a way to keep track of progress<br />
; Next steps/actions/notes<br />
: ACTION: Try to get momentum around this status page (ttx)<br />
: ACTION: Explore solutions for the TC itself (flaper87)<br />
: (johnthetubaguy) I prefer some kind of rhythm to things, a weekly status email that points to this page could be a good start for SWG<br />
<br />
<br />
==== Collect and share best practices around being globally inclusive community ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: John Garbutt (johnthetubaguy)<br />
; Goal<br />
: Make it easy for all parts of the community to be inclusive to contributors from across the globe<br />
: Share current best practices to help spark ideas on how we improve<br />
; Current state<br />
: Docs team have merged some great guidance: https://docs.openstack.org/contributor-guide/non-native-english-speakers.html<br />
; Next steps/actions/notes<br />
: ACTION: Prepare a project team guide patch to help discuss current best practices https://review.openstack.org/#/c/441923 (johnthetubaguy)</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Stewardship_Working_Group&diff=153381Stewardship Working Group2017-04-19T12:05:08Z<p>John Garbutt: /* Initiatives */</p>
<hr />
<div>== Scope ==<br />
<br />
The [https://governance.openstack.org/tc OpenStack Technical Committee] adopted a [https://governance.openstack.org/tc/resolutions/20160705-stewardship.html resolution] to setup the Stewardship Working Group (SWG).<br />
<br />
It was the stated intent in establishing this working group that the community would benefit from establishing a small group to review the leadership, communication, and decision making processes of the TC and OpenStack projects as a whole, and propose a set of improvements based on the the concepts of "Servant Leadership" and "Stewardship". The SWG will be responsible for producing actionable recommendations and improvements that the TC can then consider for adoption and roll out to the OpenStack community. Anyone interested in leadership, stewardship, and OpenStack is welcome to join the working group. The SWG is an advisory body. Final decisions about any changes proposed by the SWG will be made by the TC.<br />
<br />
In particular, the SWG is interested in tackling:<br />
* How to improve the Technical Committee: write a vision, adopt consensus-based decision making, create distraction-free venues for TC discussion<br />
* What tools in the servant leadership could be used in OpenStack: look into building visions, using the bottom-line change framework, communicate more about servant leadership<br />
* Develop better leaders for OpenStack: expand training opportunities<br />
* Explore options to be more inclusive: Support non-native speakers, weird timezones, different cultures, non full-time contributors, first contributors<br />
* Address papercuts: facilitate keeping up with incoming information, address the difficulty to get ACKs on actions, make IRC more friendly<br />
<br />
<br />
== How to play ==<br />
<br />
Join us on the '''#openstack-swg''' channel on Freenode. Start threads (marked with "[swg]" subject prefix) on openstack-dev@lists.openstack.org.<br />
<br />
<br />
== Initiatives ==<br />
<br />
==== Build a vision for the TC ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Colette Alexander (gothicmindfood)<br />
; Goal<br />
: Create a two-year vision for the Technical Committee (based on Zingerman's visioning framework) to help drive decisions<br />
; Current state<br />
: Draft vision was built in an in-person workshop in Boston, then refined and posted for comments at [https://review.openstack.org/#/c/453262/].<br />
; Next steps/actions<br />
: Collect feedback and brainstorm needed modifications until the Boston summit<br />
: Presentation at the summit (gothicmindfood, johnthetubaguy, ttx)<br />
: Post second draft shortly after<br />
<br />
<br />
==== Develop an alternative to weekly meetings ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Flavio Percoco (flaper87) and Thierry Carrez (ttx)<br />
; Goal<br />
: Drop meetings for the SWG as an experiment, and develop alternatives (status whiteboard, async discussions...)<br />
; Current state<br />
: SWG dropped meetings but hasn't moved much since. Posted a status tracking wikipage (this page) as a way to keep track of progress<br />
; Next steps/actions/notes<br />
: ACTION: Try to get momentum around this status page (ttx)<br />
: ACTION: Explore solutions for the TC itself (flaper87)<br />
: (johnthetubaguy) I prefer some kind of rhythm to things, a weekly status email that points to this page could be a good start for SWG<br />
<br />
==== Collect and share best practices around being globally inclusive community ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: John Garbutt (johnthetubaguy)<br />
; Goal<br />
: Make it easy for all parts of the community to be inclusive to contributors from across the globe<br />
: Share current best practices to help spark ideas on how we improve<br />
; Current state<br />
: Docs team have merged some great guidance: https://docs.openstack.org/contributor-guide/non-native-english-speakers.html<br />
; Next steps/actions/notes<br />
: ACTION: Prepare a project team guide patch to help discuss current best practices https://review.openstack.org/#/c/441923 (johnthetubaguy)</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Stewardship_Working_Group&diff=153380Stewardship Working Group2017-04-19T11:57:33Z<p>John Garbutt: /* Develop an alternative to weekly meetings */</p>
<hr />
<div>== Scope ==<br />
<br />
The [https://governance.openstack.org/tc OpenStack Technical Committee] adopted a [https://governance.openstack.org/tc/resolutions/20160705-stewardship.html resolution] to setup the Stewardship Working Group (SWG).<br />
<br />
It was the stated intent in establishing this working group that the community would benefit from establishing a small group to review the leadership, communication, and decision making processes of the TC and OpenStack projects as a whole, and propose a set of improvements based on the the concepts of "Servant Leadership" and "Stewardship". The SWG will be responsible for producing actionable recommendations and improvements that the TC can then consider for adoption and roll out to the OpenStack community. Anyone interested in leadership, stewardship, and OpenStack is welcome to join the working group. The SWG is an advisory body. Final decisions about any changes proposed by the SWG will be made by the TC.<br />
<br />
In particular, the SWG is interested in tackling:<br />
* How to improve the Technical Committee: write a vision, adopt consensus-based decision making, create distraction-free venues for TC discussion<br />
* What tools in the servant leadership could be used in OpenStack: look into building visions, using the bottom-line change framework, communicate more about servant leadership<br />
* Develop better leaders for OpenStack: expand training opportunities<br />
* Explore options to be more inclusive: Support non-native speakers, weird timezones, different cultures, non full-time contributors, first contributors<br />
* Address papercuts: facilitate keeping up with incoming information, address the difficulty to get ACKs on actions, make IRC more friendly<br />
<br />
<br />
== How to play ==<br />
<br />
Join us on the '''#openstack-swg''' channel on Freenode. Start threads (marked with "[swg]" subject prefix) on openstack-dev@lists.openstack.org.<br />
<br />
<br />
== Initiatives ==<br />
<br />
==== Build a vision for the TC ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Colette Alexander (gothicmindfood)<br />
; Goal<br />
: Create a two-year vision for the Technical Committee (based on Zingerman's visioning framework) to help drive decisions<br />
; Current state<br />
: Draft vision was built in an in-person workshop in Boston, then refined and posted for comments at [https://review.openstack.org/#/c/453262/].<br />
; Next steps/actions<br />
: Collect feedback and brainstorm needed modifications until the Boston summit<br />
: Presentation at the summit (gothicmindfood, johnthetubaguy, ttx)<br />
: Post second draft shortly after<br />
<br />
<br />
==== Develop an alternative to weekly meetings ====<br />
; Status<br />
: Active<br />
; Contact(s)<br />
: Flavio Percoco (flaper87) and Thierry Carrez (ttx)<br />
; Goal<br />
: Drop meetings for the SWG as an experiment, and develop alternatives (status whiteboard, async discussions...)<br />
; Current state<br />
: SWG dropped meetings but hasn't moved much since. Posted a status tracking wikipage (this page) as a way to keep track of progress<br />
; Next steps/actions/notes<br />
: ACTION: Try to get momentum around this status page (ttx)<br />
: ACTION: Explore solutions for the TC itself (flaper87)<br />
: (johnthetubaguy) I prefer some kind of rhythm to things, a weekly status email that points to this page could be a good start for SWG</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=VM_%26_BM_Working_Group&diff=152597VM & BM Working Group2017-03-22T10:57:38Z<p>John Garbutt: /* VM & BM Working Group */</p>
<hr />
<div>The Virtual Machine and Baremetal working group are building a strong feedback loop between developers, users and operators to help improve the user experience and operator experience when using Nova, Ironic, Cinder, Neutron and Keystone together.<br />
<br />
More news coming soon.<br />
<br />
== How to Join ==<br />
<br />
The kick start of this group is planned for this Forum session:<br />
<br />
* http://forumtopics.openstack.org/cfp/details/10<br />
* https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=VM_%26_BM_Working_Group&diff=152596VM & BM Working Group2017-03-22T10:56:28Z<p>John Garbutt: Created page with "== VM & BM Working Group == We are working to build a strong feedback loop between developers, users and operators to help improve the user experience and operator experience..."</p>
<hr />
<div>== VM & BM Working Group ==<br />
<br />
We are working to build a strong feedback loop between developers, users and operators to help improve the user experience and operator experience when using Nova, Ironic, Cinder, Neutron and Keystone together.<br />
<br />
Kick start of this group is planned for this Forum session:<br />
<br />
* http://forumtopics.openstack.org/cfp/details/10<br />
* https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform<br />
<br />
More news coming soon.</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Upstream_Working_Groups&diff=152595Upstream Working Groups2017-03-22T10:54:24Z<p>John Garbutt: /* List */</p>
<hr />
<div>=== Definition ===<br />
<br />
Upstream work in OpenStack is organized around groups of people working in the same area. Those grow naturally and organically, and no permission is needed to create a working group. Just add them to this page to make your group easier to find. Workgroups should generally discuss on the openstack-dev mailing-list and hold IRC meetings.<br />
<br />
=== List ===<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Working Group !! Goal !! Status !! Chair(s) !! IRC Meeting<br />
|-<br />
| [[API Working Group]] || To improve the developer experience of API users by converging the OpenStack API to a consistent and pragmatic RESTful design. The working group creates guidelines that all OpenStack projects should follow for new development, and promotes convergence of new APIs and future versions of existing APIs. || Active || Chris Dent, Ed Leafe, Michael McCune || [http://eavesdrop.openstack.org/#API_Working_Group]<br />
|-<br />
| [https://git.openstack.org/cgit/openstack/arch-wg/tree/doc/source/index.rst Architecture Working Group] || Be the recognized forum of expertise on the design and architecture of OpenStack and provide guidance and resources to the Technical Committee and the entire OpenStack community on architectural matters. || Active || Clint Byrum || [http://eavesdrop.openstack.org/#Architecture_Working_Group]<br />
|-<br />
| [[Meetings/SWGMeeting|Stewardship Working Group]] || Review the leadership, communication, and decision making processes of the TC and OpenStack projects as a whole, and propose a set of improvements. || Active || Colette Alexander || (trying none)<br />
|-<br />
| [[VM & BM Working Group]] || Building a strong feedback loop between developers, users and operators to help improve the user experience and operator experience when using Nova, Ironic, Cinder, Neutron and Keystone together. || Active || John Garbutt and Jim Rollenhagen || (trying none)<br />
|}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Forum/Boston2017&diff=152150Forum/Boston20172017-03-14T21:13:07Z<p>John Garbutt: /* Working Groups */</p>
<hr />
<div>__NOTOC__<br />
The grand list of all of the Boston Forum etherpads. Please include the name of the team that started the pad.<br />
<br />
==Catch-alls==<br />
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]<br />
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]<br />
<br />
==Project Teams==<br />
<br />
===Nova===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming<br />
<br />
===Glance===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming<br />
<br />
===Swift===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming<br />
<br />
===I18n===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming<br />
<br />
===Barbican===<br />
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming<br />
<br />
==UC Working Groups ==<br />
<br />
<br />
<br />
===Telecom/NFV Requirements===<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV<br />
<br />
===Scientific WG===<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg<br />
<br />
===Massively Distributed (Fog/Edge) WG===<br />
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge<br />
<br />
===Public Cloud WG===<br />
https://etherpad.openstack.org/p/publiccloud-boston-forum-session<br />
<br />
==Other Working Groups==<br />
<br />
===VM and Bare-metal platform group===<br />
<br />
Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.<br />
<br />
https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=PTG/Pike/Etherpads&diff=150165PTG/Pike/Etherpads2017-01-19T14:54:34Z<p>John Garbutt: /* Only Monday */</p>
<hr />
<div>__NOTOC__<br />
<br />
This is the list of etherpads for the Projects Team Gathering in Atlanta. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.<br />
<br />
For more details on the event, see the [https://www.openstack.org/ptg/ event website].<br />
<br />
=== Only Monday ===<br />
<br />
* Stewardship workgroup: https://etherpad.openstack.org/p/AtlantaPTG-SWG<br />
<br />
=== Monday -> Tuesday ===<br />
<br />
* Community App Catalog<br />
* Documentation / I18n: https://etherpad.openstack.org/p/docs-i18n-ptg-pike<br />
* Horizon: https://etherpad.openstack.org/p/horizon-ptg-pike<br />
* Infrastructure: https://etherpad.openstack.org/p/infra-ptg-pike<br />
* Kolla<br />
* OpenStackAnsible: https://etherpad.openstack.org/p/osa-ptg-pike<br />
* OpenStackClient: https://etherpad.openstack.org/p/osc-ptg-pike<br />
* OpenStack Charms<br />
* Oslo: https://etherpad.openstack.org/p/oslo-ptg-pike<br />
* Packaging RPM<br />
* Quality Assurance: https://etherpad.openstack.org/p/qa-ptg-pike<br />
* Rally / Performance workgroup: https://etherpad.openstack.org/p/ptg-performance-team<br />
* RefStack / Interop workgroup<br />
* Release Goal #1 (tbd)<br />
* Release Goal #2 (tbd)<br />
* Release Mgmt / Stable maint / Requirements<br />
* Security: https://etherpad.openstack.org/p/ptg-security-team<br />
<br />
=== Only Tuesday ===<br />
<br />
* Architecture workgroup<br />
<br />
=== Wednesday -> Thursday ===<br />
<br />
* Congress: https://etherpad.openstack.org/p/congress-ptg-pike<br />
* Dragonflow<br />
* Karbor: https://etherpad.openstack.org/p/karbor-ptg-pike<br />
* Manila: https://etherpad.openstack.org/p/manila-pike-ptg-topics<br />
* Sahara https://etherpad.openstack.org/p/sahara-ptg-pike<br />
* Storlets: https://etherpad.openstack.org/p/storlets-pike-design-summit<br />
* Tricircle: https://etherpad.openstack.org/p/tricircle-pike-design-topics<br />
* Trove: https://etherpad.openstack.org/p/trove-pike-ptg-topics<br />
* Watcher<br />
<br />
=== Wednesday -> Friday ===<br />
<br />
* Barbican: https://etherpad.openstack.org/p/ptg-barbican-pike<br />
* Cinder: https://etherpad.openstack.org/p/ATL-cinder-ptg-planning<br />
* Glance: https://etherpad.openstack.org/p/glance-pike-ptg-planning<br />
* Heat: https://etherpad.openstack.org/p/heat-pike-ptg-sessions<br />
* Ironic: https://etherpad.openstack.org/p/ironic-pike-ptg<br />
* Keystone: https://etherpad.openstack.org/p/keystone-pike-ptg<br />
* Magnum<br />
* Mistral: https://etherpad.openstack.org/p/mistral-ptg-pike<br />
* Neutron: https://etherpad.openstack.org/p/neutron-ptg-pike<br />
* Nova: https://etherpad.openstack.org/p/nova-ptg-pike<br />
* Octavia: https://etherpad.openstack.org/p/octavia-ptg-pike<br />
* Swift<br />
* TripleO: https://etherpad.openstack.org/p/tripleo-ptg-pike</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Design_Summit/Ocata/Etherpads&diff=135290Design Summit/Ocata/Etherpads2016-10-20T17:00:22Z<p>John Garbutt: /* Cross Project Sessions */</p>
<hr />
<div>[[Category:Summit]]<br />
[[Category:Ocata]]<br />
[[Category:Etherpad]]<br />
<br />
The grand list of all the Ocata Design Summit sessions. Please include Date, Time, and links to etherpads when adding new content.<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__TOC__<br />
</div><br />
<br />
== Event intro/closure ==<br />
* Tue Oct 26 11:25am - Design Summit 101 - https://etherpad.openstack.org/p/ocata-design-summit-101<br />
* Fri Oct 29 12:30pm - Barcelona feedback session - https://etherpad.openstack.org/p/BCN-summit-feedback<br />
<br />
<br />
==Architecture Working Group==<br />
<br />
'''Wednesday, October 26'''<br />
* 11:25am-12:05pm - Cross Project workshops: Architecture Working Group Fishbowl - https://etherpad.openstack.org/p/ocata-summit-arch-wg<br />
<br />
==Barbican==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Barbican<br />
<br />
'''Thursday, October 27'''<br />
* 11:00am-11:40am - (128) Barbican: User and Operator Feedback Fishbowl - https://etherpad.openstack.org/p/barbican-ocata-summit-roadmap<br />
* 11:50am-12:30pm - (Montjuic) Barbican: Work Session (Roadmap) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:50pm-02:30pm - (130) Barbican: Work Session (Cross Project)- https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
<br />
'''Friday, October 28'''<br />
* 09:00am-09:40am - (129) Barbican: Work Session (Security) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 09:50am-10:30am - (129) Barbican: Work Session (TBD) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:00am-11:40am - (129) Barbican: Work Session (Resources) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:50am-12:30pm - (129) Barbican: Work Session (Planning) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
<br />
==Cinder==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cinder<br />
<br />
'''Wednesday October 26'''<br />
* 3:05pm-3:45pm - Cinder Test Working Group progress and status - https://etherpad.openstack.org/p/Cinder-testing<br />
* 3:55-4:35 - Driver bug fixes for unsupported OpenStack releases - https://etherpad.openstack.org/p/ocata-cinder-summit-stabledriverfixes<br />
* 5:05-5:45 - Stand alone Cinder service - https://etherpad.openstack.org/p/ocata-cinder-summit-standalonecinder<br />
* 5:55-6:35 - Pike (and beyond) planning - https://etherpad.openstack.org/p/ocata-cinder-summit-pikeplanning<br />
'''Thursday October 27'''<br />
* 9:00-9:40 - Replication - https://etherpad.openstack.org/p/ocata-cinder-summit-replication<br />
* 9:50-10:30 - Cinder-Nova API changes - https://etherpad.openstack.org/p/ocata-cinder-summit-attachdetach<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Nova/Cinder cross-project session - https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session<br />
* 11:00am-11:40am - NFS snapshots - https://etherpad.openstack.org/p/ocata-cinder-summit-nfssnapshots<br />
* 11:50am-12:30pm - Cinder backup improvements - https://etherpad.openstack.org/p/ocata-cinder-summit-backupimprovements<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-cinder-summit-meetup<br />
<br />
==Cross Project Sessions==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cross+Project<br />
<br />
'''Tuesday October 25'''<br />
<br />
* 3:55 PM - 4:35 PM -- Experiences with Project Decomposition, Scaling Review Teams and Subsystem Maintainers (Part 1) -- https://etherpad.openstack.org/p/ocata-summit-xp-scaling-review-teams<br />
* 3.55PM - 4.35 PM -- Cross-Service Communication -- https://etherpad.openstack.org/p/ocata-xp-cross-service-communication<br />
* 5:05 PM - 5:45 PM -- Discuss Community-Wide Release Goals -- https://etherpad.openstack.org/p/ocata-summit-xp-community-wide-goals <br />
* 5:05 PM - 5:45 PM -- Unified Capabilities Discovery API -- https://etherpad.openstack.org/p/ocata-xp-unified-capabilities-api<br />
* 5:55 PM - 6:35 PM -- Python 3 Integration Testing -- https://etherpad.openstack.org/p/ocata-python-3<br />
* 5:55 PM - 6:35 PM -- Where to Draw the Line for Proprietary Code with Drivers -- https://etherpad.openstack.org/p/ocata-xp-proprietary-drivers<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 11:25 AM - 12:05 PM -- Architecture Working Group Fishbowl -- https://etherpad.openstack.org/p/ocata-xp-architecture-working-group<br />
* 11:25 AM - 12:05 PM -- Ocata goal: Remove Incubated Oslo Code -- https://etherpad.openstack.org/p/ocata-goal-oslo<br />
* 12:15 PM - 12:55 PM -- "Re-Inventing the TC", the Stewardship Working Group Discussion -- https://etherpad.openstack.org/p/ocata-xp-stewardship<br />
* 12:15 PM - 12:55 PM -- Rolling Upgrades, and the Road to Zero-Downtime -- https://etherpad.openstack.org/p/ocata-xp-upgrades<br />
* 2:15 PM - 2:55 PM -- Experiences with project decomposition, scaling review teams and subsystem maintainers (part 2) -- https://etherpad.openstack.org/p/ocata-summit-xp-scaling-review-teams<br />
* 2:15 PM - 2:55 PM -- Driver Log Validation -- https://etherpad.openstack.org/p/driverlog-validation<br />
<br />
==Documentation==<br />
<br />
See these and more documentation sessions in schedule: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Documentation<br />
<br />
'''Wednesday, October 26'''<br />
* 5:05pm-5:45pm - User Guides Working Group - https://etherpad.openstack.org/p/BCN-Docs-UserGuidesWG<br />
'''Thursday October 27'''<br />
* 2:40pm-3:20pm - Newton Retrospective - https://etherpad.openstack.org/p/BCN-Docs-NewtonRetro <br />
* 3:30pm-4:10pm - Social Things - https://etherpad.openstack.org/p/BCN-Docs-Social <br />
* 4:40pm-5:20pm - Training Labs - https://etherpad.openstack.org/p/BCN-Docs-Training <br />
* 5:30pm-6:10pm - Toolchain - https://etherpad.openstack.org/p/BCN-Docs-Toolchain <br />
'''Friday October 28'''<br />
* 11:00am-11:40am - API Working Group - https://etherpad.openstack.org/p/BCN-Docs-APIWG <br />
* 11:50am-12:30pm - Ocata Planning Working Group - https://etherpad.openstack.org/p/BCN-Docs-OcataPlanningWG <br />
* 2:00pm-6:00pm - Contributors Meetup - no etherpad<br />
<br />
== Gluon ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Gluon%3A<br />
<br />
Fri 28, 9:50am-10:30am: Gluon Work Session https://etherpad.openstack.org/p/ocata-gluon-work-plan<br />
<br />
==Heat==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Heat<br />
<br />
'''Thursday October 27'''<br />
<br />
* 11:00am-11:40am - Convergence Phase 1 - What worked, What didn't - https://etherpad.openstack.org/p/heat-ocata-convergence-phase-1<br />
* 11:50am-12:30pm - Performance Scalability Improvements - I (Issues with very large stacks) - https://etherpad.openstack.org/p/heat-ocata-performance-scalability-1<br />
* 2:40pm-3:20pm - Performance Scalability Improvements - II - https://etherpad.openstack.org/p/heat-ocata-performance-scalability-2<br />
* 3:30pm-4:10pm - Convergence Phase 2 - https://etherpad.openstack.org/p/heat-ocata-convergence-phase-2<br />
* 4:40pm-5:20pm - Validation Improvements - https://etherpad.openstack.org/p/heat-ocata-validation-improvements<br />
<br />
'''Friday October 28'''<br />
<br />
* 9:00am-9:40am - RPC versioning and hitless upgrades - https://etherpad.openstack.org/p/heat-ocata-hitless-upgrades<br />
* 9:50am-10:30am - API Microversions - https://etherpad.openstack.org/p/heat-ocata-api-microversions<br />
* 11:00am-11:40am - Heat Integration tests, Tempest and test candidates for DefCore Interop Testing - https://etherpad.openstack.org/p/heat-ocata-test-coverage<br />
* 11:50am-12:30pm - Improve maturity of heat - https://etherpad.openstack.org/p/heat-ocata-improve-maturity<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-heat-contributor-meetup<br />
<br />
<br />
==Horizon==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Horizon%3A<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 16:55-17:35 - Cross-project meeting with Horizon and Keystone - https://etherpad.openstack.org/p/ocata-keystone-horizon<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00-09:40 - Operator/ Plugin feedback - https://etherpad.openstack.org/p/horizon-ocata-feedback<br />
* 09:50-10:30 - Newton retrospective, Ocata timeline, Dependencies, Testing!! and Selenium :-( - https://etherpad.openstack.org/p/horizon-ocata-planning<br />
* 16:40-17:20 - Cross-project topics; Glance, Identity, K2K Federation, Quotas - https://etherpad.openstack.org/p/horizon-ocata-cross-project<br />
* 17:30-18:10 - AngularJS state of play (where we're going, status of panels, what CORS means, do we want a thin service proxy, deprecations, etc.) -https://etherpad.openstack.org/p/horizon-ocata-angularjs<br />
<br />
'''Friday October 28'''<br />
<br />
* 11:50-12:30 - Priority setting (and TODO review if we have time) - https://etherpad.openstack.org/p/horizon-ocata-priorities<br />
* 14:00-18:00 - General project discussion (Newton retrospective, how to improve our organisation and use of tooling)<br />
<br />
== I18n ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=I18n%3A<br />
<br />
'''Friday October 28'''<br />
<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/barcelona-i18n-meetup<br />
<br />
==Infrastructure==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Infrastructure%3A<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 3:05pm-3:45pm: ''Work Session: Firehose'' in AC Hotel - P3 - Montjuic<br />
** https://etherpad.openstack.org/p/ocata-infra-firehose<br />
<br />
'''Thursday October 27'''<br />
<br />
* 2:40pm-3:20pm: ''Fishbowl: Status update and plans for task tracking'' in AC Hotel - P1 - Salon Barcelona<br />
** https://etherpad.openstack.org/p/ocata-infra-community-task-tracking<br />
<br />
'''Friday October 28'''<br />
<br />
All the sessions on Friday are taking place at CCIB - Centre de Convencions Internacional de Barcelona - P1<br />
<br />
* 9:00am-9:40am: ''Work Session: Next steps for infra-cloud'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-infra-cloud<br />
* 9:50am-10:30am: ''Work Session: Interactive infra-cloud debugging'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-infra-cloud-debugging<br />
* 11:00am-11:40am: ''Work Session: Test environment expectations'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-test-env-expectations<br />
* 11:50am-12:30pm: ''Work Session: Xenial jobs transition for stable/newton'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-xenial-stable-newton<br />
* 2:00pm-6:00pm: ''Contributors Meetup'' in Room 121<br />
** https://etherpad.openstack.org/p/ocata-infra-contributors-meetup<br />
<br />
==Ironic==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ironic:<br />
<br />
'''Wednesday October 26'''<br />
* 5ː05pm-5ː45pm - API Evolution - https://etherpad.openstack.org/p/ironic-ocata-summit-api-evolution<br />
* 5:55pm-6:35pm - Deploy-time RAID and Advanced Partitioning (w/ Nova) - https://etherpad.openstack.org/p/ironic-ocata-summit-deploy-time-raid<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - Task Framework - https://etherpad.openstack.org/p/ironic-ocata-summit-task-framework<br />
* 9:50am-10:30am - QA/CI - https://etherpad.openstack.org/p/ironic-ocata-summit-qa<br />
* 1:50pm-2:30pm - Synchronizing Events with Neutron - https://etherpad.openstack.org/p/ironic-ocata-summit-neutron-events<br />
* 2:40pm-3:20pm - Ocata Priorities - https://etherpad.openstack.org/p/ironic-ocata-summit-priorities<br />
'''Friday October 28'''<br />
* 11:00am-11:40am - VNC Console - https://etherpad.openstack.org/p/ironic-ocata-summit-vnc-console<br />
* 11:50am-12:30pm - Unblocking Priority Features - https://etherpad.openstack.org/p/ironic-ocata-summit-unblock-priorities<br />
* 2:00pm-6:00pm - Contributors Meetup - https://etherpad.openstack.org/p/ironic-ocata-summit-contributor-meetup<br />
<br />
== Keystone ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Keystone%3A<br />
<br />
Wed 26, 4:05pm-4:45pm<br />
Keystone: Newton retrospective (Fishbowl)<br />
https://etherpad.openstack.org/p/keystone-newton-retrospective<br />
<br />
Wed 26, 4:55pm-5:35pm<br />
Keystone: keystone/horizon integration<br />
https://etherpad.openstack.org/p/ocata-keystone-horizon<br />
<br />
Thu 27, 12:00pm-12:40pm<br />
Keystone: Unconference (Fishbowl)<br />
https://etherpad.openstack.org/p/ocata-keystone-unconference<br />
<br />
Thu 27, 12:50pm-1:30pm<br />
Keystone: Ocata priorities (Fishbowl)<br />
https://etherpad.openstack.org/p/ocata-keystone-priorities<br />
<br />
Thu 27, 2:50pm-3:30pm<br />
Keystone: Work session (Federation)<br />
https://etherpad.openstack.org/p/ocata-keystone-federation<br />
<br />
Thu 27, 3:40pm-4:20pm<br />
Keystone: Work session (Testing)<br />
https://etherpad.openstack.org/p/ocata-keystone-testing<br />
<br />
Thu 27, 4:30pm-5:10pm<br />
Keystone: Work session (Documentation)<br />
https://etherpad.openstack.org/p/ocata-keystone-documentation<br />
<br />
Fri 28, 10:00am-10:40am<br />
Keystone: Work session (Authorization)<br />
https://etherpad.openstack.org/p/ocata-keystone-authorization<br />
<br />
Fri 28, 10:50am-11:30am<br />
Keystone: Work session (Authentication)<br />
https://etherpad.openstack.org/p/ocata-keystone-authentication<br />
<br />
Fri 28, 12:00pm-12:40pm<br />
Keystone: Work session (Scaling and Performance)<br />
https://etherpad.openstack.org/p/ocata-keystone-scaling<br />
<br />
Fri 28, 12:50pm-1:30pm<br />
Keystone: Work session (Integration)<br />
https://etherpad.openstack.org/p/ocata-keystone-integration<br />
<br />
Fri 28, 3:00pm-7:00pm<br />
Keystone: Contributors meetup<br />
(No etherpad)<br />
<br />
== Kolla ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Kolla%3A<br />
<br />
Kolla Ocata Summit Master Etherpad - https://etherpad.openstack.org/p/kolla-o-summit-schedule<br />
<br />
'''Wed October 26'''<br />
<br />
* 3:55pm - 4:35pm - Operator experiences - https://etherpad.openstack.org/p/kolla-o-summit-op-experiences<br />
* 5:05pm - 5:45pm - Community roadmap planning for O - https://etherpad.openstack.org/p/kolla-o-summit-community-planning<br />
* 5:55pm - 6:35pm - Goals for Ocata - https://etherpad.openstack.org/p/kolla-o-summit-roadmap<br />
<br />
'''Thu October 27'''<br />
<br />
* 9:00am - 9:40am - Kolla-Kubernetes Architecture - https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-architecture<br />
* 9:50am - 10:30am - High availability - https://etherpad.openstack.org/p/kolla-o-summit-high-availability<br />
* 1:50pm - 2:30pm - 3rd Party Plugins - https://etherpad.openstack.org/p/kolla-o-summit-3rd-party-plugins<br />
* 2:40pm - 3:20pm - Improving the CI system - https://etherpad.openstack.org/p/kolla-o-summit-improving-ci<br />
* 3:30pm - 4:10pm - Distro requirements, deprecation, levels of support - https://etherpad.openstack.org/p/kolla-o-summit-support-and-deprecation<br />
<br />
'''Fri April 28'''<br />
<br />
* 9:00am - 9:40am - Documentation - https://etherpad.openstack.org/p/kolla-o-summit-documentation<br />
* 9:50am - 10:30am - OSIC review - https://etherpad.openstack.org/p/kolla-o-summit-OSIC-review<br />
* 11:00am - 11:40am - Kolla-Kubernetes Roadmap - https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-road-map<br />
* 11:50am - 12:30pm - Security VMT threat - https://etherpad.openstack.org/p/kolla-ocata-summit-threat-analysis<br />
* 2:00pm - 6:00pm - Afternoon Contributor Meetup - https://etherpad.openstack.org/p/kolla-ocata-summit-contrib-meetup<br />
<br />
==Manila==<br />
<br />
'''Thu October 27'''<br />
<br />
* 11:00 - 11:40 - Race Conditions (FB) - https://etherpad.openstack.org/p/ocata-manila-race-conditions<br />
* 11:50 - 12:30 - Data Service Jobs Table (FB) - https://etherpad.openstack.org/p/ocata-manila-data-service-jobs-table<br />
* 14:40 - 15:20 - High Availability (WS) - https://etherpad.openstack.org/p/ocata-manila-high-availability<br />
<br />
'''Fri April 28'''<br />
<br />
* 11:00 - 11:40 - Access Rules (WS) - https://etherpad.openstack.org/p/ocata-manila-access-rules<br />
* 11:50 - 12:30 - Tempest Direction (WS) - https://etherpad.openstack.org/p/ocata-manila-tempest-direction<br />
* 14:00 - 18:00 - Contributor Meetup (CM) - https://etherpad.openstack.org/p/ocata-manila-contributor-meetup<br />
<br />
==Neutron==<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 17:05 - 17:45 - Nova/Neutron cross-project session Nova - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
* 17:55 - 18:35 - LBaaS retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-octavia-lbaas-session<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00 - 09:40 - Completing the Newton backlog - https://etherpad.openstack.org/p/ocata-neutron-core-newton-backlog<br />
* 09:50 - 10:30 - Upstream and dowstream CI and testing efforts - https://etherpad.openstack.org/p/ocata-neutron-testing<br />
* 11:00 - 11:40 - End user and operator feedback - https://etherpad.openstack.org/p/ocata-neutron-end-user-operator-feedback<br />
* 11:50 - 12:30 - Neutronclient retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-client<br />
* 17:30 - 18:10 - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
<br />
'''Friday October 28'''<br />
<br />
* 09:00 - 09:40 (Sagrada Familia) Fishbowl Neutron: Neutron-lib retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-lib-next-steps<br />
* 09:50 - 10:30 (Sagrada Familia) Fishbowl Neutron: Neutron server: retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-server-next<br />
* 11:00 - 11:40 (Sagrada Familia) Fishbowl Neutron: Neutron agents: retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-agents<br />
* 11:50 - 12:30 (Sagrada Familia) Fishbowl Neutron: Stadium update - https://etherpad.openstack.org/p/ocata-nova-neutron-stadium<br />
* 14:00 - 18:00 (Room 114) Meetup Neutron: Contributors meetup - https://etherpad.openstack.org/p/ocata-neutron-contributor-meetup<br />
<br />
==Nomad==<br />
<br />
https://etherpad.openstack.org/p/nomad-ocata-design-session<br />
<br />
== Nova ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Nova%3A<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-5:45pm - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - Newton placement service retrospective - https://etherpad.openstack.org/p/ocata-nova-summit-placement-retrospective<br />
* 9:50am-10:30am - Scheduler / resource providers (quantitative) - https://etherpad.openstack.org/p/ocata-nova-summit-resource-providers-quantitative<br />
* '''Break'''<br />
* 11:00am-11:40am - Scheduler / resource provider traits (qualitative) - https://etherpad.openstack.org/p/ocata-nova-summit-resource-providers-qualitative<br />
* 11:50am-12:30pm - Organizing API work for Ocata - https://etherpad.openstack.org/p/ocata-nova-summit-api<br />
* '''Lunch'''<br />
* 1:50pm-2:30pm - Unconference - https://etherpad.openstack.org/p/ocata-nova-summit-unconference<br />
* 2:40pm-3:20pm - Cells v2 (scheduler, searchlight, multi-cell support) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler<br />
* 3:30pm-4:10pm - Cells v2 (quotas) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-quotas<br />
* '''Break'''<br />
* 4:40pm-5:20pm - Completing vendordata v2 - https://etherpad.openstack.org/p/ocata-nova-summit-vendoradatav2<br />
* 5:30pm-6:10pm - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Nova/Cinder cross-project session - https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session<br />
* 9:50am-10:30am - Security specs and testing - https://etherpad.openstack.org/p/ocata-nova-summit-security<br />
* '''Break'''<br />
* 11:00am-11:40am - Planning the libvirt imagebackend refactor work - https://etherpad.openstack.org/p/ocata-nova-summit-libvirt-imagebackend<br />
* 11:50am-12:30pm - Ocata priorities and schedule - https://etherpad.openstack.org/p/ocata-nova-summit-priorities<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-nova-summit-meetup<br />
<br />
== OpenStack-Ansible ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=openstackansible%3A<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-6:35pm - OpenStack-Ansible prioritization/work discussion - https://etherpad.openstack.org/p/ocata-osa-summit-work-prioritization<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - OpenStack-Ansible Newton cycle overview & Ocata preview- https://etherpad.openstack.org/p/ocata-osa-summit-overview<br />
* 9:50am-10:30am - How to get involved in OpenStack-Ansible - https://etherpad.openstack.org/p/ocata-osa-summit-onboarding<br />
* '''Break'''<br />
* 11:00am-12:30am - Upgrade improvements and discussion - https://etherpad.openstack.org/p/ocata-osa-summit-upgrades<br />
* '''Lunch'''<br />
* '''Break'''<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Ongoing work-items for OpenStack-Ansible - https://etherpad.openstack.org/p/ocata-osa-summit-currentwork<br />
* 9:50am-10:30am - Testing/gating discussion - https://etherpad.openstack.org/p/ocata-osa-summit-testing<br />
* '''Break'''<br />
* 11:00am-11:40am - Inventory improvements/discussion - https://etherpad.openstack.org/p/ocata-osa-summit-inventory<br />
* 11:50am-12:30pm - Configuration/role discussion and improvements - https://etherpad.openstack.org/p/ocata-osa-summit-config<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-osa-summit-contributors-meetup<br />
<br />
== Release Management ==<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 5:55 PM - 6:35 PM -- Work session -- https://etherpad.openstack.org/p/ocata-relmgt-plan<br />
<br />
'''Thursday October 27'''<br />
<br />
* 1:50 PM - 2:30 PM -- Newton Retrospective & Ocata Schedule -- https://etherpad.openstack.org/p/ocata-release-fishbowl<br />
<br />
'''Friday October 28'''<br />
<br />
* 2:00 PM - 6:00 PM -- Contributors Meetup -- https://etherpad.openstack.org/p/ocata-relmgt-plan<br />
<br />
== Searchlight ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Searchlight<br />
<br />
'''Thursday October 27'''<br />
* 9:50 - 10:30 - Fishbowl: Adding service plugins to Searchlight and what it can add to UIs - https://etherpad.openstack.org/p/ocata-searchlight-summit-plugins-fishbowl<br />
* 11:00 - 11:40 - Improving ease of use for searching - https://etherpad.openstack.org/p/ocata-searchlight-summit-working-sessions<br />
* 11:50 - 12:30 - Error handling during notifications - https://etherpad.openstack.org/p/ocata-searchlight-summit-working-sessions<br />
* 2:40pm-3:20pm - Cells v2 (scheduler, searchlight, multi-cell support) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler<br />
<br />
== Senlin ==<br />
<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Senlin work session: policy/profile versioning - https://etherpad.openstack.org/p/ocata-summit-senlin-profile-policy-versioning<br />
* 9:50am-10:30am - Senlin work session: versioned everything - https://etherpad.openstack.org/p/ocata-summit-senlin-versioned-everything<br />
* '''Break'''<br />
* 11:00am-11:40am - Senlin work session: container cluster - https://etherpad.openstack.org/p/ocata-summit-senlin-container-cluster<br />
* 11:50am-12:30am - Senlin work session: HA - https://etherpad.openstack.org/p/ocata-summit-senlin-HA<br />
<br />
== Stewardship Working Group ==<br />
<br />
'''Wed October 26'''<br />
<br />
*12:15pm - 12:55pm - Cross Project workshops: "Re-inventing the TC", the Stewardship Working Group discussion - https://etherpad.openstack.org/p/Barcelona-SWG-cp<br />
<br />
== Tricircle ==<br />
<br />
Venue: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=tricircle%3A<br />
<br />
ideas: https://etherpad.openstack.org/p/ocata-tricircle-sessions-planning<br />
<br />
'''Thu October 27'''<br />
<br />
* 5:30pm - 6:10pm - Cross Neutron networking automation: feature review and what's to do in Ocata : https://etherpad.openstack.org/p/ocata-tricircle-feature-review-priorities-roadmap<br />
<br />
'''Fri April 28'''<br />
<br />
* 9:00am - 9:40am - Ocata work session: https://etherpad.openstack.org/p/ocata-tricircle-work-session<br />
* 9:40am - 12:00am - Tricricle contributors meetup<br />
<br />
== TripleO ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=tripleo%3A<br />
<br />
https://etherpad.openstack.org/p/ocata-tripleo<br />
<br />
===== TripleO: Containers - Current Status and Roadmap =====<br />
Wed 26 3:55pm-4:35pm<br />
https://etherpad.openstack.org/p/ocata-tripleo-containers<br />
<br />
=====TripleO: Work Session - Growing the team=====<br />
Wed 26 5:05pm-5:45pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-team-growing<br />
<br />
===== TripleO: Work Session - CI - current status and roadmap=====<br />
Wed 26 5:55pm-6:35pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-ci<br />
<br />
===== TripleO: Upgrades - current status and roadmap=====<br />
Thu 27 1:50pm-2:30pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-upgrades<br />
<br />
===== TripleO: Work Session - Composable Undercloud deployment with Heat=====<br />
Fri 28 9:00am-9:20am -<br />
https://etherpad.openstack.org/p/tripleo-composable-undercloud<br />
<br />
===== TripleO: Work Session - GUI, CLI, Validations current status, roadmap, requirements=====<br />
Fri 28 9:20am-9:40am -<br />
https://etherpad.openstack.org/p/gui-ocata<br />
<br />
===== TripleO: Work Session - Multiple topics=====<br />
Fri 28 9:50am-10:30am -<br />
Blueprints, specs, tools and Ocata summary.<br />
See bottom of https://etherpad.openstack.org/p/ocata-tripleo<br />
<br />
== Trove ==<br />
<br />
https://etherpad.openstack.org/p/trove-barcelona-sessions <br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Trove<br />
<br />
==Watcher==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Watcher<br />
<br />
'''Wed October 26'''<br />
<br />
* 5.55pm - 6.35pm - [https://etherpad.openstack.org/p/watcher-ocata-design-session Existing & new infrastructure optimization strategies]<br />
<br />
'''Thu October 27'''<br />
<br />
* 9.50am - 10.30am - [https://etherpad.openstack.org/p/watcher-ocata-design-session Watcher Newton retrospective]<br />
<br />
'''Fri April 28'''<br />
<br />
* 11am - 12.30am - [https://etherpad.openstack.org/p/watcher-ocata-design-session Ocata priorities & roadmap]<br />
* 2pm - 6pm - [https://etherpad.openstack.org/p/watcher-ocata-design-session Contributors meetup]<br />
<br />
==Zaqar==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Zaqar<br />
<br />
'''Thursday, October 27'''<br />
<br />
9:50am-10:30am [https://etherpad.openstack.org/p/zaqar-ocata-performance Zaqar's profile and performance gate]<br />
<br />
4:40pm-5:00pm [https://etherpad.openstack.org/p/zaqar-ocata-notification-delivery-policy Notification delivery policy]<br />
<br />
5:00pm-5:20pm [https://etherpad.openstack.org/p/zaqar-ocata-purge-queue Purge queue]<br />
<br />
5:30pm-6:10pm [https://etherpad.openstack.org/p/zaqar-ocata-subscription-confirmation-email Subscription Confirmation - Email]<br />
...</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Design_Summit/Ocata/Etherpads&diff=135277Design Summit/Ocata/Etherpads2016-10-20T14:30:22Z<p>John Garbutt: /* Cross Project Sessions */ add missing etherpads</p>
<hr />
<div>[[Category:Summit]]<br />
[[Category:Ocata]]<br />
[[Category:Etherpad]]<br />
<br />
The grand list of all the Ocata Design Summit sessions. Please include Date, Time, and links to etherpads when adding new content.<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__TOC__<br />
</div><br />
<br />
== Event intro/closure ==<br />
* Tue Oct 26 11:25am - Design Summit 101 - https://etherpad.openstack.org/p/ocata-design-summit-101<br />
* Fri Oct 29 12:30pm - Barcelona feedback session - https://etherpad.openstack.org/p/BCN-summit-feedback<br />
<br />
<br />
==Architecture Working Group==<br />
<br />
'''Wednesday, October 26'''<br />
* 11:25am-12:05pm - Cross Project workshops: Architecture Working Group Fishbowl - https://etherpad.openstack.org/p/ocata-summit-arch-wg<br />
<br />
==Barbican==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Barbican<br />
<br />
'''Thursday, October 27'''<br />
* 11:00am-11:40am - (128) Barbican: User and Operator Feedback Fishbowl - https://etherpad.openstack.org/p/barbican-ocata-summit-roadmap<br />
* 11:50am-12:30pm - (Montjuic) Barbican: Work Session (Roadmap) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:50pm-02:30pm - (130) Barbican: Work Session (Cross Project)- https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
<br />
'''Friday, October 28'''<br />
* 09:00am-09:40am - (129) Barbican: Work Session (Security) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 09:50am-10:30am - (129) Barbican: Work Session (TBD) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:00am-11:40am - (129) Barbican: Work Session (Resources) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:50am-12:30pm - (129) Barbican: Work Session (Planning) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
<br />
==Cinder==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cinder<br />
<br />
'''Wednesday October 26'''<br />
* 3:05pm-3:45pm - Cinder Test Working Group progress and status - https://etherpad.openstack.org/p/Cinder-testing<br />
* 3:55-4:35 - Driver bug fixes for unsupported OpenStack releases - https://etherpad.openstack.org/p/ocata-cinder-summit-stabledriverfixes<br />
* 5:05-5:45 - Stand alone Cinder service - https://etherpad.openstack.org/p/ocata-cinder-summit-standalonecinder<br />
* 5:55-6:35 - Pike (and beyond) planning - https://etherpad.openstack.org/p/ocata-cinder-summit-pikeplanning<br />
'''Thursday October 27'''<br />
* 9:00-9:40 - Replication - https://etherpad.openstack.org/p/ocata-cinder-summit-replication<br />
* 9:50-10:30 - Cinder-Nova API changes - https://etherpad.openstack.org/p/ocata-cinder-summit-attachdetach<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Nova/Cinder cross-project session - https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session<br />
* 11:00am-11:40am - NFS snapshots - https://etherpad.openstack.org/p/ocata-cinder-summit-nfssnapshots<br />
* 11:50am-12:30pm - Cinder backup improvements - https://etherpad.openstack.org/p/ocata-cinder-summit-backupimprovements<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-cinder-summit-meetup<br />
<br />
==Cross Project Sessions==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cross+Project<br />
<br />
'''Tuesday October 25'''<br />
<br />
* 3:55 PM - 4:35 PM -- Experiences with Project Decomposition, Scaling Review Teams and Subsystem Maintainers (Part 1) -- https://etherpad.openstack.org/p/ocata-summit-xp-scaling-review-teams<br />
* 3.55PM - 4.35 PM -- Cross-Service Communication -- https://etherpad.openstack.org/p/ocata-xp-cross-service-communication<br />
* 5:05 PM - 5:45 PM -- Discuss Community-Wide Release Goals -- https://etherpad.openstack.org/p/community-goals<br />
* 5:05 PM - 5:45 PM -- Unified Capabilities Discovery API -- https://etherpad.openstack.org/p/ocata-xp-unified-capabilities-api<br />
* 5:55 PM - 6:35 PM -- Python 3 Integration Testing -- https://etherpad.openstack.org/p/ocata-python-3<br />
* 5:55 PM - 6:35 PM -- Where to Draw the Line for Proprietary Code with Drivers -- https://etherpad.openstack.org/p/ocata-xp-proprietary-drivers<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 11:25 AM - 12:05 PM -- Architecture Working Group Fishbowl -- https://etherpad.openstack.org/p/ocata-xp-architecture-working-group<br />
* 11:25 AM - 12:05 PM -- Ocata goal: Remove Incubated Oslo Code -- https://etherpad.openstack.org/p/ocata-goal-oslo<br />
* 12:15 PM - 12:55 PM -- "Re-Inventing the TC", the Stewardship Working Group Discussion -- https://etherpad.openstack.org/p/ocata-xp-stewardship<br />
* 12:15 PM - 12:55 PM -- Rolling Upgrades, and the Road to Zero-Downtime -- https://etherpad.openstack.org/p/ocata-xp-upgrades<br />
* 2:15 PM - 2:55 PM -- Experiences with project decomposition, scaling review teams and subsystem maintainers (part 2) -- https://etherpad.openstack.org/p/ocata-summit-xp-scaling-review-teams<br />
* 2:15 PM - 2:55 PM -- Driver Log Validation -- https://etherpad.openstack.org/p/driverlog-validation<br />
<br />
==Documentation==<br />
<br />
See these and more documentation sessions in schedule: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Documentation<br />
<br />
'''Wednesday, October 26'''<br />
* 5:05pm-5:45pm - User Guides Working Group - https://etherpad.openstack.org/p/BCN-Docs-UserGuidesWG<br />
'''Thursday October 27'''<br />
* 2:40pm-3:20pm - Newton Retrospective - https://etherpad.openstack.org/p/BCN-Docs-NewtonRetro <br />
* 3:30pm-4:10pm - Social Things - https://etherpad.openstack.org/p/BCN-Docs-Social <br />
* 4:40pm-5:20pm - Training Labs - https://etherpad.openstack.org/p/BCN-Docs-Training <br />
* 5:30pm-6:10pm - Toolchain - https://etherpad.openstack.org/p/BCN-Docs-Toolchain <br />
'''Friday October 28'''<br />
* 11:00am-11:40am - API Working Group - https://etherpad.openstack.org/p/BCN-Docs-APIWG <br />
* 11:50am-12:30pm - Ocata Planning Working Group - https://etherpad.openstack.org/p/BCN-Docs-OcataPlanningWG <br />
* 2:00pm-6:00pm - Contributors Meetup - no etherpad<br />
<br />
== Gluon ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Gluon%3A<br />
<br />
Fri 28, 9:50am-10:30am: Gluon Work Session https://etherpad.openstack.org/p/ocata-gluon-work-plan<br />
<br />
==Heat==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Heat<br />
<br />
'''Thursday October 27'''<br />
<br />
* 11:00am-11:40am - Convergence Phase 1 - What worked, What didn't - https://etherpad.openstack.org/p/heat-ocata-convergence-phase-1<br />
* 11:50am-12:30pm - Performance Scalability Improvements - I (Issues with very large stacks) - https://etherpad.openstack.org/p/heat-ocata-performance-scalability-1<br />
* 2:40pm-3:20pm - Performance Scalability Improvements - II - https://etherpad.openstack.org/p/heat-ocata-performance-scalability-2<br />
* 3:30pm-4:10pm - Convergence Phase 2 - https://etherpad.openstack.org/p/heat-ocata-convergence-phase-2<br />
* 4:40pm-5:20pm - Validation Improvements - https://etherpad.openstack.org/p/heat-ocata-validation-improvements<br />
<br />
'''Friday October 28'''<br />
<br />
* 9:00am-9:40am - RPC versioning and hitless upgrades - https://etherpad.openstack.org/p/heat-ocata-hitless-upgrades<br />
* 9:50am-10:30am - API Microversions - https://etherpad.openstack.org/p/heat-ocata-api-microversions<br />
* 11:00am-11:40am - Heat Integration tests, Tempest and test candidates for DefCore Interop Testing - https://etherpad.openstack.org/p/heat-ocata-test-coverage<br />
* 11:50am-12:30pm - Improve maturity of heat - https://etherpad.openstack.org/p/heat-ocata-improve-maturity<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-heat-contributor-meetup<br />
<br />
<br />
==Horizon==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Horizon%3A<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 16:55-17:35 - Cross-project meeting with Horizon and Keystone - https://etherpad.openstack.org/p/ocata-keystone-horizon<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00-09:40 - Operator/ Plugin feedback - https://etherpad.openstack.org/p/horizon-ocata-feedback<br />
* 09:50-10:30 - Newton retrospective, Ocata timeline, Dependencies, Testing!! and Selenium :-( - https://etherpad.openstack.org/p/horizon-ocata-planning<br />
* 16:40-17:20 - Cross-project topics; Glance, Identity, K2K Federation, Quotas - https://etherpad.openstack.org/p/horizon-ocata-cross-project<br />
* 17:30-18:10 - AngularJS state of play (where we're going, status of panels, what CORS means, do we want a thin service proxy, deprecations, etc.) -https://etherpad.openstack.org/p/horizon-ocata-angularjs<br />
<br />
'''Friday October 28'''<br />
<br />
* 11:50-12:30 - Priority setting (and TODO review if we have time) - https://etherpad.openstack.org/p/horizon-ocata-priorities<br />
* 14:00-18:00 - General project discussion (Newton retrospective, how to improve our organisation and use of tooling)<br />
<br />
== I18n ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=I18n%3A<br />
<br />
'''Friday October 28'''<br />
<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/barcelona-i18n-meetup<br />
<br />
==Infrastructure==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Infrastructure%3A<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 3:05pm-3:45pm: ''Work Session: Firehose'' in AC Hotel - P3 - Montjuic<br />
** https://etherpad.openstack.org/p/ocata-infra-firehose<br />
<br />
'''Thursday October 27'''<br />
<br />
* 2:40pm-3:20pm: ''Fishbowl: Status update and plans for task tracking'' in AC Hotel - P1 - Salon Barcelona<br />
** https://etherpad.openstack.org/p/ocata-infra-community-task-tracking<br />
<br />
'''Friday October 28'''<br />
<br />
All the sessions on Friday are taking place at CCIB - Centre de Convencions Internacional de Barcelona - P1<br />
<br />
* 9:00am-9:40am: ''Work Session: Next steps for infra-cloud'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-infra-cloud<br />
* 9:50am-10:30am: ''Work Session: Interactive infra-cloud debugging'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-infra-cloud-debugging<br />
* 11:00am-11:40am: ''Work Session: Test environment expectations'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-test-env-expectations<br />
* 11:50am-12:30pm: ''Work Session: Xenial jobs transition for stable/newton'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-xenial-stable-newton<br />
* 2:00pm-6:00pm: ''Contributors Meetup'' in Room 121<br />
** https://etherpad.openstack.org/p/ocata-infra-contributors-meetup<br />
<br />
==Ironic==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ironic:<br />
<br />
'''Wednesday October 26'''<br />
* 5ː05pm-5ː45pm - API Evolution - https://etherpad.openstack.org/p/ironic-ocata-summit-api-evolution<br />
* 5:55pm-6:35pm - Deploy-time RAID and Advanced Partitioning (w/ Nova) - https://etherpad.openstack.org/p/ironic-ocata-summit-deploy-time-raid<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - Task Framework - https://etherpad.openstack.org/p/ironic-ocata-summit-task-framework<br />
* 9:50am-10:30am - QA/CI - https://etherpad.openstack.org/p/ironic-ocata-summit-qa<br />
* 1:50pm-2:30pm - Synchronizing Events with Neutron - https://etherpad.openstack.org/p/ironic-ocata-summit-neutron-events<br />
* 2:40pm-3:20pm - Ocata Priorities - https://etherpad.openstack.org/p/ironic-ocata-summit-priorities<br />
'''Friday October 28'''<br />
* 11:00am-11:40am - VNC Console - https://etherpad.openstack.org/p/ironic-ocata-summit-vnc-console<br />
* 11:50am-12:30pm - Unblocking Priority Features - https://etherpad.openstack.org/p/ironic-ocata-summit-unblock-priorities<br />
* 2:00pm-6:00pm - Contributors Meetup - https://etherpad.openstack.org/p/ironic-ocata-summit-contributor-meetup<br />
<br />
== Keystone ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Keystone%3A<br />
<br />
Wed 26, 4:05pm-4:45pm<br />
Keystone: Newton retrospective (Fishbowl)<br />
https://etherpad.openstack.org/p/keystone-newton-retrospective<br />
<br />
Wed 26, 4:55pm-5:35pm<br />
Keystone: keystone/horizon integration<br />
https://etherpad.openstack.org/p/ocata-keystone-horizon<br />
<br />
Thu 27, 12:00pm-12:40pm<br />
Keystone: Unconference (Fishbowl)<br />
https://etherpad.openstack.org/p/ocata-keystone-unconference<br />
<br />
Thu 27, 12:50pm-1:30pm<br />
Keystone: Ocata priorities (Fishbowl)<br />
https://etherpad.openstack.org/p/ocata-keystone-priorities<br />
<br />
Thu 27, 2:50pm-3:30pm<br />
Keystone: Work session (Federation)<br />
https://etherpad.openstack.org/p/ocata-keystone-federation<br />
<br />
Thu 27, 3:40pm-4:20pm<br />
Keystone: Work session (Testing)<br />
https://etherpad.openstack.org/p/ocata-keystone-testing<br />
<br />
Thu 27, 4:30pm-5:10pm<br />
Keystone: Work session (Documentation)<br />
https://etherpad.openstack.org/p/ocata-keystone-documentation<br />
<br />
Fri 28, 10:00am-10:40am<br />
Keystone: Work session (Authorization)<br />
https://etherpad.openstack.org/p/ocata-keystone-authorization<br />
<br />
Fri 28, 10:50am-11:30am<br />
Keystone: Work session (Authentication)<br />
https://etherpad.openstack.org/p/ocata-keystone-authentication<br />
<br />
Fri 28, 12:00pm-12:40pm<br />
Keystone: Work session (Scaling and Performance)<br />
https://etherpad.openstack.org/p/ocata-keystone-scaling<br />
<br />
Fri 28, 12:50pm-1:30pm<br />
Keystone: Work session (Integration)<br />
https://etherpad.openstack.org/p/ocata-keystone-integration<br />
<br />
Fri 28, 3:00pm-7:00pm<br />
Keystone: Contributors meetup<br />
(No etherpad)<br />
<br />
== Kolla ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Kolla%3A<br />
<br />
Kolla Ocata Summit Master Etherpad - https://etherpad.openstack.org/p/kolla-o-summit-schedule<br />
<br />
'''Wed October 26'''<br />
<br />
* 3:55pm - 4:35pm - Operator experiences - https://etherpad.openstack.org/p/kolla-o-summit-op-experiences<br />
* 5:05pm - 5:45pm - Community roadmap planning for O - https://etherpad.openstack.org/p/kolla-o-summit-community-planning<br />
* 5:55pm - 6:35pm - Goals for Ocata - https://etherpad.openstack.org/p/kolla-o-summit-roadmap<br />
<br />
'''Thu October 27'''<br />
<br />
* 9:00am - 9:40am - Kolla-Kubernetes Architecture - https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-architecture<br />
* 9:50am - 10:30am - High availability - https://etherpad.openstack.org/p/kolla-o-summit-high-availability<br />
* 1:50pm - 2:30pm - 3rd Party Plugins - https://etherpad.openstack.org/p/kolla-o-summit-3rd-party-plugins<br />
* 2:40pm - 3:20pm - Improving the CI system - https://etherpad.openstack.org/p/kolla-o-summit-improving-ci<br />
* 3:30pm - 4:10pm - Distro requirements, deprecation, levels of support - https://etherpad.openstack.org/p/kolla-o-summit-support-and-deprecation<br />
<br />
'''Fri April 28'''<br />
<br />
* 9:00am - 9:40am - Documentation - https://etherpad.openstack.org/p/kolla-o-summit-documentation<br />
* 9:50am - 10:30am - OSIC review - https://etherpad.openstack.org/p/kolla-o-summit-OSIC-review<br />
* 11:00am - 11:40am - Kolla-Kubernetes Roadmap - https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-road-map<br />
* 11:50am - 12:30pm - Security VMT threat - https://etherpad.openstack.org/p/kolla-ocata-summit-threat-analysis<br />
* 2:00pm - 6:00pm - Afternoon Contributor Meetup - https://etherpad.openstack.org/p/kolla-ocata-summit-contrib-meetup<br />
<br />
==Manila==<br />
<br />
'''Thu October 27'''<br />
<br />
* 11:00 - 11:40 - Race Conditions (FB) - https://etherpad.openstack.org/p/ocata-manila-race-conditions<br />
* 11:50 - 12:30 - Data Service Jobs Table (FB) - https://etherpad.openstack.org/p/ocata-manila-data-service-jobs-table<br />
* 14:40 - 15:20 - High Availability (WS) - https://etherpad.openstack.org/p/ocata-manila-high-availability<br />
<br />
'''Fri April 28'''<br />
<br />
* 11:00 - 11:40 - Access Rules (WS) - https://etherpad.openstack.org/p/ocata-manila-access-rules<br />
* 11:50 - 12:30 - Tempest Direction (WS) - https://etherpad.openstack.org/p/ocata-manila-tempest-direction<br />
* 14:00 - 18:00 - Contributor Meetup (CM) - https://etherpad.openstack.org/p/ocata-manila-contributor-meetup<br />
<br />
==Neutron==<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 17:05 - 17:45 - Nova/Neutron cross-project session Nova - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
* 17:55 - 18:35 - LBaaS retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-octavia-lbaas-session<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00 - 09:40 - Completing the Newton backlog - https://etherpad.openstack.org/p/ocata-neutron-core-newton-backlog<br />
* 09:50 - 10:30 - Upstream and dowstream CI and testing efforts - https://etherpad.openstack.org/p/ocata-neutron-testing<br />
* 11:00 - 11:40 - End user and operator feedback - https://etherpad.openstack.org/p/ocata-neutron-end-user-operator-feedback<br />
* 11:50 - 12:30 - Neutronclient retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-client<br />
* 17:30 - 18:10 - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
<br />
'''Friday October 28'''<br />
<br />
* 09:00 - 09:40 (Sagrada Familia) Fishbowl Neutron: Neutron-lib retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-lib-next-steps<br />
* 09:50 - 10:30 (Sagrada Familia) Fishbowl Neutron: Neutron server: retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-server-next<br />
* 11:00 - 11:40 (Sagrada Familia) Fishbowl Neutron: Neutron agents: retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-agents<br />
* 11:50 - 12:30 (Sagrada Familia) Fishbowl Neutron: Stadium update - https://etherpad.openstack.org/p/ocata-nova-neutron-stadium<br />
* 14:00 - 18:00 (Room 114) Meetup Neutron: Contributors meetup - https://etherpad.openstack.org/p/ocata-neutron-contributor-meetup<br />
<br />
==Nomad==<br />
<br />
https://etherpad.openstack.org/p/nomad-ocata-design-session<br />
<br />
== Nova ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Nova%3A<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-5:45pm - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - Newton placement service retrospective - https://etherpad.openstack.org/p/ocata-nova-summit-placement-retrospective<br />
* 9:50am-10:30am - Scheduler / resource providers (quantitative) - https://etherpad.openstack.org/p/ocata-nova-summit-resource-providers-quantitative<br />
* '''Break'''<br />
* 11:00am-11:40am - Scheduler / resource provider traits (qualitative) - https://etherpad.openstack.org/p/ocata-nova-summit-resource-providers-qualitative<br />
* 11:50am-12:30pm - Organizing API work for Ocata - https://etherpad.openstack.org/p/ocata-nova-summit-api<br />
* '''Lunch'''<br />
* 1:50pm-2:30pm - Unconference - https://etherpad.openstack.org/p/ocata-nova-summit-unconference<br />
* 2:40pm-3:20pm - Cells v2 (scheduler, searchlight, multi-cell support) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler<br />
* 3:30pm-4:10pm - Cells v2 (quotas) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-quotas<br />
* '''Break'''<br />
* 4:40pm-5:20pm - Completing vendordata v2 - https://etherpad.openstack.org/p/ocata-nova-summit-vendoradatav2<br />
* 5:30pm-6:10pm - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Nova/Cinder cross-project session - https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session<br />
* 9:50am-10:30am - Security specs and testing - https://etherpad.openstack.org/p/ocata-nova-summit-security<br />
* '''Break'''<br />
* 11:00am-11:40am - Planning the libvirt imagebackend refactor work - https://etherpad.openstack.org/p/ocata-nova-summit-libvirt-imagebackend<br />
* 11:50am-12:30pm - Ocata priorities and schedule - https://etherpad.openstack.org/p/ocata-nova-summit-priorities<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-nova-summit-meetup<br />
<br />
== OpenStack-Ansible ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=openstackansible%3A<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-6:35pm - OpenStack-Ansible prioritization/work discussion - https://etherpad.openstack.org/p/ocata-osa-summit-work-prioritization<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - OpenStack-Ansible Newton cycle overview & Ocata preview- https://etherpad.openstack.org/p/ocata-osa-summit-overview<br />
* 9:50am-10:30am - How to get involved in OpenStack-Ansible - https://etherpad.openstack.org/p/ocata-osa-summit-onboarding<br />
* '''Break'''<br />
* 11:00am-12:30am - Upgrade improvements and discussion - https://etherpad.openstack.org/p/ocata-osa-summit-upgrades<br />
* '''Lunch'''<br />
* '''Break'''<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Ongoing work-items for OpenStack-Ansible - https://etherpad.openstack.org/p/ocata-osa-summit-currentwork<br />
* 9:50am-10:30am - Testing/gating discussion - https://etherpad.openstack.org/p/ocata-osa-summit-testing<br />
* '''Break'''<br />
* 11:00am-11:40am - Inventory improvements/discussion - https://etherpad.openstack.org/p/ocata-osa-summit-inventory<br />
* 11:50am-12:30pm - Configuration/role discussion and improvements - https://etherpad.openstack.org/p/ocata-osa-summit-config<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-osa-summit-contributors-meetup<br />
<br />
== Release Management ==<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 5:55 PM - 6:35 PM -- Work session -- https://etherpad.openstack.org/p/ocata-relmgt-plan<br />
<br />
'''Thursday October 27'''<br />
<br />
* 1:50 PM - 2:30 PM -- Newton Retrospective & Ocata Schedule -- https://etherpad.openstack.org/p/ocata-release-fishbowl<br />
<br />
'''Friday October 28'''<br />
<br />
* 2:00 PM - 6:00 PM -- Contributors Meetup -- https://etherpad.openstack.org/p/ocata-relmgt-plan<br />
<br />
== Searchlight ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Searchlight<br />
<br />
'''Thursday October 27'''<br />
* 9:50 - 10:30 - Fishbowl: Adding service plugins to Searchlight and what it can add to UIs - https://etherpad.openstack.org/p/ocata-searchlight-summit-plugins-fishbowl<br />
* 11:00 - 11:40 - Improving ease of use for searching - https://etherpad.openstack.org/p/ocata-searchlight-summit-working-sessions<br />
* 11:50 - 12:30 - Error handling during notifications - https://etherpad.openstack.org/p/ocata-searchlight-summit-working-sessions<br />
* 2:40pm-3:20pm - Cells v2 (scheduler, searchlight, multi-cell support) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler<br />
<br />
== Senlin ==<br />
<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Senlin work session: policy/profile versioning - https://etherpad.openstack.org/p/ocata-summit-senlin-profile-policy-versioning<br />
* 9:50am-10:30am - Senlin work session: versioned everything - https://etherpad.openstack.org/p/ocata-summit-senlin-versioned-everything<br />
* '''Break'''<br />
* 11:00am-11:40am - Senlin work session: container cluster - https://etherpad.openstack.org/p/ocata-summit-senlin-container-cluster<br />
* 11:50am-12:30am - Senlin work session: HA - https://etherpad.openstack.org/p/ocata-summit-senlin-HA<br />
<br />
== Stewardship Working Group ==<br />
<br />
'''Wed October 26'''<br />
<br />
*12:15pm - 12:55pm - Cross Project workshops: "Re-inventing the TC", the Stewardship Working Group discussion - https://etherpad.openstack.org/p/Barcelona-SWG-cp<br />
<br />
== Tricircle ==<br />
<br />
Venue: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=tricircle%3A<br />
<br />
ideas: https://etherpad.openstack.org/p/ocata-tricircle-sessions-planning<br />
<br />
'''Thu October 27'''<br />
<br />
* 5:30pm - 6:10pm - Cross Neutron networking automation: feature review and what's to do in Ocata : https://etherpad.openstack.org/p/ocata-tricircle-feature-review-priorities-roadmap<br />
<br />
'''Fri April 28'''<br />
<br />
* 9:00am - 9:40am - Ocata work session: https://etherpad.openstack.org/p/ocata-tricircle-work-session<br />
* 9:40am - 12:00am - Tricricle contributors meetup<br />
<br />
== TripleO ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=tripleo%3A<br />
<br />
https://etherpad.openstack.org/p/ocata-tripleo<br />
<br />
===== TripleO: Containers - Current Status and Roadmap =====<br />
Wed 26 3:55pm-4:35pm<br />
https://etherpad.openstack.org/p/ocata-tripleo-containers<br />
<br />
=====TripleO: Work Session - Growing the team=====<br />
Wed 26 5:05pm-5:45pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-team-growing<br />
<br />
===== TripleO: Work Session - CI - current status and roadmap=====<br />
Wed 26 5:55pm-6:35pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-ci<br />
<br />
===== TripleO: Upgrades - current status and roadmap=====<br />
Thu 27 1:50pm-2:30pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-upgrades<br />
<br />
===== TripleO: Work Session - Composable Undercloud deployment with Heat=====<br />
Fri 28 9:00am-9:20am -<br />
https://etherpad.openstack.org/p/tripleo-composable-undercloud<br />
<br />
===== TripleO: Work Session - GUI, CLI, Validations current status, roadmap, requirements=====<br />
Fri 28 9:20am-9:40am -<br />
https://etherpad.openstack.org/p/gui-ocata<br />
<br />
===== TripleO: Work Session - Multiple topics=====<br />
Fri 28 9:50am-10:30am -<br />
Blueprints, specs, tools and Ocata summary.<br />
See bottom of https://etherpad.openstack.org/p/ocata-tripleo<br />
<br />
== Trove ==<br />
<br />
https://etherpad.openstack.org/p/trove-barcelona-sessions <br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Trove<br />
<br />
==Watcher==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Watcher<br />
<br />
'''Wed October 26'''<br />
<br />
* 5.55pm - 6.35pm - [https://etherpad.openstack.org/p/watcher-ocata-design-session Existing & new infrastructure optimization strategies]<br />
<br />
'''Thu October 27'''<br />
<br />
* 9.50am - 10.30am - [https://etherpad.openstack.org/p/watcher-ocata-design-session Watcher Newton retrospective]<br />
<br />
'''Fri April 28'''<br />
<br />
* 11am - 12.30am - [https://etherpad.openstack.org/p/watcher-ocata-design-session Ocata priorities & roadmap]<br />
* 2pm - 6pm - [https://etherpad.openstack.org/p/watcher-ocata-design-session Contributors meetup]<br />
<br />
==Zaqar==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Zaqar<br />
<br />
'''Thursday, October 27'''<br />
<br />
9:50am-10:30am [https://etherpad.openstack.org/p/zaqar-ocata-performance Zaqar's profile and performance gate]<br />
<br />
4:40pm-5:00pm [https://etherpad.openstack.org/p/zaqar-ocata-notification-delivery-policy Notification delivery policy]<br />
<br />
5:00pm-5:20pm [https://etherpad.openstack.org/p/zaqar-ocata-purge-queue Purge queue]<br />
<br />
5:30pm-6:10pm [https://etherpad.openstack.org/p/zaqar-ocata-subscription-confirmation-email Subscription Confirmation - Email]<br />
...</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Design_Summit/Ocata/Etherpads&diff=135276Design Summit/Ocata/Etherpads2016-10-20T14:25:46Z<p>John Garbutt: /* Cross Project Sessions */</p>
<hr />
<div>[[Category:Summit]]<br />
[[Category:Ocata]]<br />
[[Category:Etherpad]]<br />
<br />
The grand list of all the Ocata Design Summit sessions. Please include Date, Time, and links to etherpads when adding new content.<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__TOC__<br />
</div><br />
<br />
== Event intro/closure ==<br />
* Tue Oct 26 11:25am - Design Summit 101 - https://etherpad.openstack.org/p/ocata-design-summit-101<br />
* Fri Oct 29 12:30pm - Barcelona feedback session - https://etherpad.openstack.org/p/BCN-summit-feedback<br />
<br />
<br />
==Architecture Working Group==<br />
<br />
'''Wednesday, October 26'''<br />
* 11:25am-12:05pm - Cross Project workshops: Architecture Working Group Fishbowl - https://etherpad.openstack.org/p/ocata-summit-arch-wg<br />
<br />
==Barbican==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Barbican<br />
<br />
'''Thursday, October 27'''<br />
* 11:00am-11:40am - (128) Barbican: User and Operator Feedback Fishbowl - https://etherpad.openstack.org/p/barbican-ocata-summit-roadmap<br />
* 11:50am-12:30pm - (Montjuic) Barbican: Work Session (Roadmap) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:50pm-02:30pm - (130) Barbican: Work Session (Cross Project)- https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
<br />
'''Friday, October 28'''<br />
* 09:00am-09:40am - (129) Barbican: Work Session (Security) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 09:50am-10:30am - (129) Barbican: Work Session (TBD) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:00am-11:40am - (129) Barbican: Work Session (Resources) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
* 11:50am-12:30pm - (129) Barbican: Work Session (Planning) - https://etherpad.openstack.org/p/barbican-ocata-design-summit<br />
<br />
==Cinder==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cinder<br />
<br />
'''Wednesday October 26'''<br />
* 3:05pm-3:45pm - Cinder Test Working Group progress and status - https://etherpad.openstack.org/p/Cinder-testing<br />
* 3:55-4:35 - Driver bug fixes for unsupported OpenStack releases - https://etherpad.openstack.org/p/ocata-cinder-summit-stabledriverfixes<br />
* 5:05-5:45 - Stand alone Cinder service - https://etherpad.openstack.org/p/ocata-cinder-summit-standalonecinder<br />
* 5:55-6:35 - Pike (and beyond) planning - https://etherpad.openstack.org/p/ocata-cinder-summit-pikeplanning<br />
'''Thursday October 27'''<br />
* 9:00-9:40 - Replication - https://etherpad.openstack.org/p/ocata-cinder-summit-replication<br />
* 9:50-10:30 - Cinder-Nova API changes - https://etherpad.openstack.org/p/ocata-cinder-summit-attachdetach<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Nova/Cinder cross-project session - https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session<br />
* 11:00am-11:40am - NFS snapshots - https://etherpad.openstack.org/p/ocata-cinder-summit-nfssnapshots<br />
* 11:50am-12:30pm - Cinder backup improvements - https://etherpad.openstack.org/p/ocata-cinder-summit-backupimprovements<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-cinder-summit-meetup<br />
<br />
==Cross Project Sessions==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cross+Project<br />
<br />
'''Tuesday October 25'''<br />
<br />
* 3:55 PM - 4:35 PM -- Experiences with Project Decomposition, Scaling Review Teams and Subsystem Maintainers (Part 1) -- https://etherpad.openstack.org/p/ocata-summit-xp-scaling-review-teams<br />
* 3.55PM - 4.35 PM -- Cross-Service Communication<br />
* 5:05 PM - 5:45 PM -- Discuss Community-Wide Release Goals -- https://etherpad.openstack.org/p/community-goals<br />
* 5:05 PM - 5:45 PM -- Unified Capabilities Discovery API<br />
* 5:55 PM - 6:35 PM -- Python 3 Integration Testing -- https://etherpad.openstack.org/p/ocata-python-3<br />
* 5:55 PM - 6:35 PM -- Where to Draw the Line for Proprietary Code with Drivers<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 11:25 AM - 12:05 PM -- Architecture Working Group Fishbowl<br />
* 11:25 AM - 12:05 PM -- Ocata goal: Remove Incubated Oslo Code -- https://etherpad.openstack.org/p/ocata-goal-oslo<br />
* 12:15 PM - 12:55 PM -- "Re-Inventing the TC", the Stewardship Working Group Discussion<br />
* 12:15 PM - 12:55 PM -- Rolling Upgrades, and the Road to Zero-Downtime<br />
* 2:15 PM - 2:55 PM -- Experiences with project decomposition, scaling review teams and subsystem maintainers (part 2) -- https://etherpad.openstack.org/p/ocata-summit-xp-scaling-review-teams<br />
* 2:15 PM - 2:55 PM -- Driver Log Validation -- https://etherpad.openstack.org/p/driverlog-validation<br />
<br />
==Documentation==<br />
<br />
See these and more documentation sessions in schedule: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Documentation<br />
<br />
'''Wednesday, October 26'''<br />
* 5:05pm-5:45pm - User Guides Working Group - https://etherpad.openstack.org/p/BCN-Docs-UserGuidesWG<br />
'''Thursday October 27'''<br />
* 2:40pm-3:20pm - Newton Retrospective - https://etherpad.openstack.org/p/BCN-Docs-NewtonRetro <br />
* 3:30pm-4:10pm - Social Things - https://etherpad.openstack.org/p/BCN-Docs-Social <br />
* 4:40pm-5:20pm - Training Labs - https://etherpad.openstack.org/p/BCN-Docs-Training <br />
* 5:30pm-6:10pm - Toolchain - https://etherpad.openstack.org/p/BCN-Docs-Toolchain <br />
'''Friday October 28'''<br />
* 11:00am-11:40am - API Working Group - https://etherpad.openstack.org/p/BCN-Docs-APIWG <br />
* 11:50am-12:30pm - Ocata Planning Working Group - https://etherpad.openstack.org/p/BCN-Docs-OcataPlanningWG <br />
* 2:00pm-6:00pm - Contributors Meetup - no etherpad<br />
<br />
== Gluon ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Gluon%3A<br />
<br />
Fri 28, 9:50am-10:30am: Gluon Work Session https://etherpad.openstack.org/p/ocata-gluon-work-plan<br />
<br />
==Heat==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Heat<br />
<br />
'''Thursday October 27'''<br />
<br />
* 11:00am-11:40am - Convergence Phase 1 - What worked, What didn't - https://etherpad.openstack.org/p/heat-ocata-convergence-phase-1<br />
* 11:50am-12:30pm - Performance Scalability Improvements - I (Issues with very large stacks) - https://etherpad.openstack.org/p/heat-ocata-performance-scalability-1<br />
* 2:40pm-3:20pm - Performance Scalability Improvements - II - https://etherpad.openstack.org/p/heat-ocata-performance-scalability-2<br />
* 3:30pm-4:10pm - Convergence Phase 2 - https://etherpad.openstack.org/p/heat-ocata-convergence-phase-2<br />
* 4:40pm-5:20pm - Validation Improvements - https://etherpad.openstack.org/p/heat-ocata-validation-improvements<br />
<br />
'''Friday October 28'''<br />
<br />
* 9:00am-9:40am - RPC versioning and hitless upgrades - https://etherpad.openstack.org/p/heat-ocata-hitless-upgrades<br />
* 9:50am-10:30am - API Microversions - https://etherpad.openstack.org/p/heat-ocata-api-microversions<br />
* 11:00am-11:40am - Heat Integration tests, Tempest and test candidates for DefCore Interop Testing - https://etherpad.openstack.org/p/heat-ocata-test-coverage<br />
* 11:50am-12:30pm - Improve maturity of heat - https://etherpad.openstack.org/p/heat-ocata-improve-maturity<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-heat-contributor-meetup<br />
<br />
<br />
==Horizon==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Horizon%3A<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 16:55-17:35 - Cross-project meeting with Horizon and Keystone - https://etherpad.openstack.org/p/ocata-keystone-horizon<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00-09:40 - Operator/ Plugin feedback - https://etherpad.openstack.org/p/horizon-ocata-feedback<br />
* 09:50-10:30 - Newton retrospective, Ocata timeline, Dependencies, Testing!! and Selenium :-( - https://etherpad.openstack.org/p/horizon-ocata-planning<br />
* 16:40-17:20 - Cross-project topics; Glance, Identity, K2K Federation, Quotas - https://etherpad.openstack.org/p/horizon-ocata-cross-project<br />
* 17:30-18:10 - AngularJS state of play (where we're going, status of panels, what CORS means, do we want a thin service proxy, deprecations, etc.) -https://etherpad.openstack.org/p/horizon-ocata-angularjs<br />
<br />
'''Friday October 28'''<br />
<br />
* 11:50-12:30 - Priority setting (and TODO review if we have time) - https://etherpad.openstack.org/p/horizon-ocata-priorities<br />
* 14:00-18:00 - General project discussion (Newton retrospective, how to improve our organisation and use of tooling)<br />
<br />
== I18n ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=I18n%3A<br />
<br />
'''Friday October 28'''<br />
<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/barcelona-i18n-meetup<br />
<br />
==Infrastructure==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Infrastructure%3A<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 3:05pm-3:45pm: ''Work Session: Firehose'' in AC Hotel - P3 - Montjuic<br />
** https://etherpad.openstack.org/p/ocata-infra-firehose<br />
<br />
'''Thursday October 27'''<br />
<br />
* 2:40pm-3:20pm: ''Fishbowl: Status update and plans for task tracking'' in AC Hotel - P1 - Salon Barcelona<br />
** https://etherpad.openstack.org/p/ocata-infra-community-task-tracking<br />
<br />
'''Friday October 28'''<br />
<br />
All the sessions on Friday are taking place at CCIB - Centre de Convencions Internacional de Barcelona - P1<br />
<br />
* 9:00am-9:40am: ''Work Session: Next steps for infra-cloud'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-infra-cloud<br />
* 9:50am-10:30am: ''Work Session: Interactive infra-cloud debugging'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-infra-cloud-debugging<br />
* 11:00am-11:40am: ''Work Session: Test environment expectations'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-test-env-expectations<br />
* 11:50am-12:30pm: ''Work Session: Xenial jobs transition for stable/newton'' in Room 115<br />
** https://etherpad.openstack.org/p/ocata-infra-xenial-stable-newton<br />
* 2:00pm-6:00pm: ''Contributors Meetup'' in Room 121<br />
** https://etherpad.openstack.org/p/ocata-infra-contributors-meetup<br />
<br />
==Ironic==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ironic:<br />
<br />
'''Wednesday October 26'''<br />
* 5ː05pm-5ː45pm - API Evolution - https://etherpad.openstack.org/p/ironic-ocata-summit-api-evolution<br />
* 5:55pm-6:35pm - Deploy-time RAID and Advanced Partitioning (w/ Nova) - https://etherpad.openstack.org/p/ironic-ocata-summit-deploy-time-raid<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - Task Framework - https://etherpad.openstack.org/p/ironic-ocata-summit-task-framework<br />
* 9:50am-10:30am - QA/CI - https://etherpad.openstack.org/p/ironic-ocata-summit-qa<br />
* 1:50pm-2:30pm - Synchronizing Events with Neutron - https://etherpad.openstack.org/p/ironic-ocata-summit-neutron-events<br />
* 2:40pm-3:20pm - Ocata Priorities - https://etherpad.openstack.org/p/ironic-ocata-summit-priorities<br />
'''Friday October 28'''<br />
* 11:00am-11:40am - VNC Console - https://etherpad.openstack.org/p/ironic-ocata-summit-vnc-console<br />
* 11:50am-12:30pm - Unblocking Priority Features - https://etherpad.openstack.org/p/ironic-ocata-summit-unblock-priorities<br />
* 2:00pm-6:00pm - Contributors Meetup - https://etherpad.openstack.org/p/ironic-ocata-summit-contributor-meetup<br />
<br />
== Keystone ==<br />
<br />
View online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Keystone%3A<br />
<br />
Wed 26, 4:05pm-4:45pm<br />
Keystone: Newton retrospective (Fishbowl)<br />
https://etherpad.openstack.org/p/keystone-newton-retrospective<br />
<br />
Wed 26, 4:55pm-5:35pm<br />
Keystone: keystone/horizon integration<br />
https://etherpad.openstack.org/p/ocata-keystone-horizon<br />
<br />
Thu 27, 12:00pm-12:40pm<br />
Keystone: Unconference (Fishbowl)<br />
https://etherpad.openstack.org/p/ocata-keystone-unconference<br />
<br />
Thu 27, 12:50pm-1:30pm<br />
Keystone: Ocata priorities (Fishbowl)<br />
https://etherpad.openstack.org/p/ocata-keystone-priorities<br />
<br />
Thu 27, 2:50pm-3:30pm<br />
Keystone: Work session (Federation)<br />
https://etherpad.openstack.org/p/ocata-keystone-federation<br />
<br />
Thu 27, 3:40pm-4:20pm<br />
Keystone: Work session (Testing)<br />
https://etherpad.openstack.org/p/ocata-keystone-testing<br />
<br />
Thu 27, 4:30pm-5:10pm<br />
Keystone: Work session (Documentation)<br />
https://etherpad.openstack.org/p/ocata-keystone-documentation<br />
<br />
Fri 28, 10:00am-10:40am<br />
Keystone: Work session (Authorization)<br />
https://etherpad.openstack.org/p/ocata-keystone-authorization<br />
<br />
Fri 28, 10:50am-11:30am<br />
Keystone: Work session (Authentication)<br />
https://etherpad.openstack.org/p/ocata-keystone-authentication<br />
<br />
Fri 28, 12:00pm-12:40pm<br />
Keystone: Work session (Scaling and Performance)<br />
https://etherpad.openstack.org/p/ocata-keystone-scaling<br />
<br />
Fri 28, 12:50pm-1:30pm<br />
Keystone: Work session (Integration)<br />
https://etherpad.openstack.org/p/ocata-keystone-integration<br />
<br />
Fri 28, 3:00pm-7:00pm<br />
Keystone: Contributors meetup<br />
(No etherpad)<br />
<br />
== Kolla ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Kolla%3A<br />
<br />
Kolla Ocata Summit Master Etherpad - https://etherpad.openstack.org/p/kolla-o-summit-schedule<br />
<br />
'''Wed October 26'''<br />
<br />
* 3:55pm - 4:35pm - Operator experiences - https://etherpad.openstack.org/p/kolla-o-summit-op-experiences<br />
* 5:05pm - 5:45pm - Community roadmap planning for O - https://etherpad.openstack.org/p/kolla-o-summit-community-planning<br />
* 5:55pm - 6:35pm - Goals for Ocata - https://etherpad.openstack.org/p/kolla-o-summit-roadmap<br />
<br />
'''Thu October 27'''<br />
<br />
* 9:00am - 9:40am - Kolla-Kubernetes Architecture - https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-architecture<br />
* 9:50am - 10:30am - High availability - https://etherpad.openstack.org/p/kolla-o-summit-high-availability<br />
* 1:50pm - 2:30pm - 3rd Party Plugins - https://etherpad.openstack.org/p/kolla-o-summit-3rd-party-plugins<br />
* 2:40pm - 3:20pm - Improving the CI system - https://etherpad.openstack.org/p/kolla-o-summit-improving-ci<br />
* 3:30pm - 4:10pm - Distro requirements, deprecation, levels of support - https://etherpad.openstack.org/p/kolla-o-summit-support-and-deprecation<br />
<br />
'''Fri April 28'''<br />
<br />
* 9:00am - 9:40am - Documentation - https://etherpad.openstack.org/p/kolla-o-summit-documentation<br />
* 9:50am - 10:30am - OSIC review - https://etherpad.openstack.org/p/kolla-o-summit-OSIC-review<br />
* 11:00am - 11:40am - Kolla-Kubernetes Roadmap - https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-road-map<br />
* 11:50am - 12:30pm - Security VMT threat - https://etherpad.openstack.org/p/kolla-ocata-summit-threat-analysis<br />
* 2:00pm - 6:00pm - Afternoon Contributor Meetup - https://etherpad.openstack.org/p/kolla-ocata-summit-contrib-meetup<br />
<br />
==Manila==<br />
<br />
'''Thu October 27'''<br />
<br />
* 11:00 - 11:40 - Race Conditions (FB) - https://etherpad.openstack.org/p/ocata-manila-race-conditions<br />
* 11:50 - 12:30 - Data Service Jobs Table (FB) - https://etherpad.openstack.org/p/ocata-manila-data-service-jobs-table<br />
* 14:40 - 15:20 - High Availability (WS) - https://etherpad.openstack.org/p/ocata-manila-high-availability<br />
<br />
'''Fri April 28'''<br />
<br />
* 11:00 - 11:40 - Access Rules (WS) - https://etherpad.openstack.org/p/ocata-manila-access-rules<br />
* 11:50 - 12:30 - Tempest Direction (WS) - https://etherpad.openstack.org/p/ocata-manila-tempest-direction<br />
* 14:00 - 18:00 - Contributor Meetup (CM) - https://etherpad.openstack.org/p/ocata-manila-contributor-meetup<br />
<br />
==Neutron==<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 17:05 - 17:45 - Nova/Neutron cross-project session Nova - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
* 17:55 - 18:35 - LBaaS retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-octavia-lbaas-session<br />
<br />
'''Thursday October 27'''<br />
<br />
* 09:00 - 09:40 - Completing the Newton backlog - https://etherpad.openstack.org/p/ocata-neutron-core-newton-backlog<br />
* 09:50 - 10:30 - Upstream and dowstream CI and testing efforts - https://etherpad.openstack.org/p/ocata-neutron-testing<br />
* 11:00 - 11:40 - End user and operator feedback - https://etherpad.openstack.org/p/ocata-neutron-end-user-operator-feedback<br />
* 11:50 - 12:30 - Neutronclient retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-client<br />
* 17:30 - 18:10 - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
<br />
'''Friday October 28'''<br />
<br />
* 09:00 - 09:40 (Sagrada Familia) Fishbowl Neutron: Neutron-lib retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-lib-next-steps<br />
* 09:50 - 10:30 (Sagrada Familia) Fishbowl Neutron: Neutron server: retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-server-next<br />
* 11:00 - 11:40 (Sagrada Familia) Fishbowl Neutron: Neutron agents: retrospective and next steps - https://etherpad.openstack.org/p/ocata-neutron-agents<br />
* 11:50 - 12:30 (Sagrada Familia) Fishbowl Neutron: Stadium update - https://etherpad.openstack.org/p/ocata-nova-neutron-stadium<br />
* 14:00 - 18:00 (Room 114) Meetup Neutron: Contributors meetup - https://etherpad.openstack.org/p/ocata-neutron-contributor-meetup<br />
<br />
==Nomad==<br />
<br />
https://etherpad.openstack.org/p/nomad-ocata-design-session<br />
<br />
== Nova ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Nova%3A<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-5:45pm - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - Newton placement service retrospective - https://etherpad.openstack.org/p/ocata-nova-summit-placement-retrospective<br />
* 9:50am-10:30am - Scheduler / resource providers (quantitative) - https://etherpad.openstack.org/p/ocata-nova-summit-resource-providers-quantitative<br />
* '''Break'''<br />
* 11:00am-11:40am - Scheduler / resource provider traits (qualitative) - https://etherpad.openstack.org/p/ocata-nova-summit-resource-providers-qualitative<br />
* 11:50am-12:30pm - Organizing API work for Ocata - https://etherpad.openstack.org/p/ocata-nova-summit-api<br />
* '''Lunch'''<br />
* 1:50pm-2:30pm - Unconference - https://etherpad.openstack.org/p/ocata-nova-summit-unconference<br />
* 2:40pm-3:20pm - Cells v2 (scheduler, searchlight, multi-cell support) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler<br />
* 3:30pm-4:10pm - Cells v2 (quotas) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-quotas<br />
* '''Break'''<br />
* 4:40pm-5:20pm - Completing vendordata v2 - https://etherpad.openstack.org/p/ocata-nova-summit-vendoradatav2<br />
* 5:30pm-6:10pm - Nova/Neutron cross-project session - https://etherpad.openstack.org/p/ocata-nova-neutron-session<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Nova/Cinder cross-project session - https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session<br />
* 9:50am-10:30am - Security specs and testing - https://etherpad.openstack.org/p/ocata-nova-summit-security<br />
* '''Break'''<br />
* 11:00am-11:40am - Planning the libvirt imagebackend refactor work - https://etherpad.openstack.org/p/ocata-nova-summit-libvirt-imagebackend<br />
* 11:50am-12:30pm - Ocata priorities and schedule - https://etherpad.openstack.org/p/ocata-nova-summit-priorities<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-nova-summit-meetup<br />
<br />
== OpenStack-Ansible ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=openstackansible%3A<br />
<br />
'''Wednesday October 26'''<br />
* 5:05pm-6:35pm - OpenStack-Ansible prioritization/work discussion - https://etherpad.openstack.org/p/ocata-osa-summit-work-prioritization<br />
'''Thursday October 27'''<br />
* 9:00am-9:40am - OpenStack-Ansible Newton cycle overview & Ocata preview- https://etherpad.openstack.org/p/ocata-osa-summit-overview<br />
* 9:50am-10:30am - How to get involved in OpenStack-Ansible - https://etherpad.openstack.org/p/ocata-osa-summit-onboarding<br />
* '''Break'''<br />
* 11:00am-12:30am - Upgrade improvements and discussion - https://etherpad.openstack.org/p/ocata-osa-summit-upgrades<br />
* '''Lunch'''<br />
* '''Break'''<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Ongoing work-items for OpenStack-Ansible - https://etherpad.openstack.org/p/ocata-osa-summit-currentwork<br />
* 9:50am-10:30am - Testing/gating discussion - https://etherpad.openstack.org/p/ocata-osa-summit-testing<br />
* '''Break'''<br />
* 11:00am-11:40am - Inventory improvements/discussion - https://etherpad.openstack.org/p/ocata-osa-summit-inventory<br />
* 11:50am-12:30pm - Configuration/role discussion and improvements - https://etherpad.openstack.org/p/ocata-osa-summit-config<br />
* '''Lunch'''<br />
* 2:00pm-6:00pm - Contributors meetup - https://etherpad.openstack.org/p/ocata-osa-summit-contributors-meetup<br />
<br />
== Release Management ==<br />
<br />
'''Wednesday October 26'''<br />
<br />
* 5:55 PM - 6:35 PM -- Work session -- https://etherpad.openstack.org/p/ocata-relmgt-plan<br />
<br />
'''Thursday October 27'''<br />
<br />
* 1:50 PM - 2:30 PM -- Newton Retrospective & Ocata Schedule -- https://etherpad.openstack.org/p/ocata-release-fishbowl<br />
<br />
'''Friday October 28'''<br />
<br />
* 2:00 PM - 6:00 PM -- Contributors Meetup -- https://etherpad.openstack.org/p/ocata-relmgt-plan<br />
<br />
== Searchlight ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Searchlight<br />
<br />
'''Thursday October 27'''<br />
* 9:50 - 10:30 - Fishbowl: Adding service plugins to Searchlight and what it can add to UIs - https://etherpad.openstack.org/p/ocata-searchlight-summit-plugins-fishbowl<br />
* 11:00 - 11:40 - Improving ease of use for searching - https://etherpad.openstack.org/p/ocata-searchlight-summit-working-sessions<br />
* 11:50 - 12:30 - Error handling during notifications - https://etherpad.openstack.org/p/ocata-searchlight-summit-working-sessions<br />
* 2:40pm-3:20pm - Cells v2 (scheduler, searchlight, multi-cell support) - https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler<br />
<br />
== Senlin ==<br />
<br />
'''Friday October 28'''<br />
* 9:00am-9:40am - Senlin work session: policy/profile versioning - https://etherpad.openstack.org/p/ocata-summit-senlin-profile-policy-versioning<br />
* 9:50am-10:30am - Senlin work session: versioned everything - https://etherpad.openstack.org/p/ocata-summit-senlin-versioned-everything<br />
* '''Break'''<br />
* 11:00am-11:40am - Senlin work session: container cluster - https://etherpad.openstack.org/p/ocata-summit-senlin-container-cluster<br />
* 11:50am-12:30am - Senlin work session: HA - https://etherpad.openstack.org/p/ocata-summit-senlin-HA<br />
<br />
== Stewardship Working Group ==<br />
<br />
'''Wed October 26'''<br />
<br />
*12:15pm - 12:55pm - Cross Project workshops: "Re-inventing the TC", the Stewardship Working Group discussion - https://etherpad.openstack.org/p/Barcelona-SWG-cp<br />
<br />
== Tricircle ==<br />
<br />
Venue: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=tricircle%3A<br />
<br />
ideas: https://etherpad.openstack.org/p/ocata-tricircle-sessions-planning<br />
<br />
'''Thu October 27'''<br />
<br />
* 5:30pm - 6:10pm - Cross Neutron networking automation: feature review and what's to do in Ocata : https://etherpad.openstack.org/p/ocata-tricircle-feature-review-priorities-roadmap<br />
<br />
'''Fri April 28'''<br />
<br />
* 9:00am - 9:40am - Ocata work session: https://etherpad.openstack.org/p/ocata-tricircle-work-session<br />
* 9:40am - 12:00am - Tricricle contributors meetup<br />
<br />
== TripleO ==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=tripleo%3A<br />
<br />
https://etherpad.openstack.org/p/ocata-tripleo<br />
<br />
===== TripleO: Containers - Current Status and Roadmap =====<br />
Wed 26 3:55pm-4:35pm<br />
https://etherpad.openstack.org/p/ocata-tripleo-containers<br />
<br />
=====TripleO: Work Session - Growing the team=====<br />
Wed 26 5:05pm-5:45pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-team-growing<br />
<br />
===== TripleO: Work Session - CI - current status and roadmap=====<br />
Wed 26 5:55pm-6:35pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-ci<br />
<br />
===== TripleO: Upgrades - current status and roadmap=====<br />
Thu 27 1:50pm-2:30pm -<br />
https://etherpad.openstack.org/p/ocata-tripleo-upgrades<br />
<br />
===== TripleO: Work Session - Composable Undercloud deployment with Heat=====<br />
Fri 28 9:00am-9:20am -<br />
https://etherpad.openstack.org/p/tripleo-composable-undercloud<br />
<br />
===== TripleO: Work Session - GUI, CLI, Validations current status, roadmap, requirements=====<br />
Fri 28 9:20am-9:40am -<br />
https://etherpad.openstack.org/p/gui-ocata<br />
<br />
===== TripleO: Work Session - Multiple topics=====<br />
Fri 28 9:50am-10:30am -<br />
Blueprints, specs, tools and Ocata summary.<br />
See bottom of https://etherpad.openstack.org/p/ocata-tripleo<br />
<br />
== Trove ==<br />
<br />
https://etherpad.openstack.org/p/trove-barcelona-sessions <br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Trove<br />
<br />
==Watcher==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Watcher<br />
<br />
'''Wed October 26'''<br />
<br />
* 5.55pm - 6.35pm - [https://etherpad.openstack.org/p/watcher-ocata-design-session Existing & new infrastructure optimization strategies]<br />
<br />
'''Thu October 27'''<br />
<br />
* 9.50am - 10.30am - [https://etherpad.openstack.org/p/watcher-ocata-design-session Watcher Newton retrospective]<br />
<br />
'''Fri April 28'''<br />
<br />
* 11am - 12.30am - [https://etherpad.openstack.org/p/watcher-ocata-design-session Ocata priorities & roadmap]<br />
* 2pm - 6pm - [https://etherpad.openstack.org/p/watcher-ocata-design-session Contributors meetup]<br />
<br />
==Zaqar==<br />
<br />
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Zaqar<br />
<br />
'''Thursday, October 27'''<br />
<br />
9:50am-10:30am [https://etherpad.openstack.org/p/zaqar-ocata-performance Zaqar's profile and performance gate]<br />
<br />
4:40pm-5:00pm [https://etherpad.openstack.org/p/zaqar-ocata-notification-delivery-policy Notification delivery policy]<br />
<br />
5:00pm-5:20pm [https://etherpad.openstack.org/p/zaqar-ocata-purge-queue Purge queue]<br />
<br />
5:30pm-6:10pm [https://etherpad.openstack.org/p/zaqar-ocata-subscription-confirmation-email Subscription Confirmation - Email]<br />
...</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Meetings/Nova&diff=134606Meetings/Nova2016-10-11T14:47:21Z<p>John Garbutt: /* Agenda for next meeting */</p>
<hr />
<div><br />
= Weekly Nova team meeting =<br />
'''MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-meeting)'''<br />
<br />
This meeting is a weekly gathering of developers working on [[Nova|OpenStack Compute (Nova)]]. We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.<br />
<br />
NOTE: this wiki page should be 'emptied' at the end of each meeting.<br />
<br />
== Agenda for next meeting ==<br />
<br />
Next meetings scheduled for:<br />
* October 6th 2016 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161006T140000)<br />
* October 13th 2016 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161013T210000)<br />
<br><br />
<br />
Where you see "?" feel free to just edit the wiki and add your item.<br />
<br />
Here is the agenda for the next meeting:<br />
* Release News<br />
** #link Newton release should happen today.<br />
** #link Draft Ocata release schedule: https://wiki.openstack.org/wiki/Nova/Ocata_Release_Schedule<br />
* Summit planning<br />
** #link Nova Ocata design summit draft schedule: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Nova%3A<br />
** Questions for ops folks welcome for the Nova & Ops: https://etherpad.openstack.org/p/BCN-ops-nova<br />
* Bugs (stuck/critical)<br />
** [https://bugs.launchpad.net/nova/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress Critical bugs]<br />
*** none<br />
** Gate status<br />
*** #link check queue gate status http://status.openstack.org/elastic-recheck/index.html<br />
** 3rd party CI status<br />
*** http://ci-watch.tintri.com/project?project=nova&time=7+days<br />
* Reminders<br />
** (auggy): DocImpact tag reminder to reviewers! Changes with DocImpact tags create a bug; make sure there's a description of what documentation is needed!<br />
** #help https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty Volunteers for 1 week of bug skimming duty?<br />
* Stable branch status: https://etherpad.openstack.org/p/stable-tracker<br />
** #info There was a stable/liberty patch release last week. Requesting a stable/mitaka release this week. We'll do a stable/newton patch release next week.<br />
** stable/newton: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/newton,n,z<br />
** stable/mitaka: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/mitaka,n,z<br />
** stable/liberty: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/liberty,n,z<br />
* Subteam Highlights<br />
** Cells v2 (alaski)<br />
** Scheduler (edleafe/jaypipes)<br />
** Live Migration (PaulMurray)<br />
** API (sdague/alex_xu)<br />
** SR-IOV/PCI (moshele)<br />
** Notification (gibi)<br />
* Stuck Reviews<br />
** Please note "stuck review" means a review where there is some disagreement that needs resolving. Its not for reviews that just haven't had attention, except for exceptional cases. Where you see "?" feel free to just edit the wiki and add your item.<br />
** Any stuck code reviews to discuss:<br />
*** (peter-hamilton): Would like to discuss ways forward for https://review.openstack.org/#/c/357151/ . Related to: https://blueprints.launchpad.net/nova/+spec/nova-support-image-signing<br />
* Open discussion<br />
** (mriedem): Start thinking about PTG attendance, February 20-2. Mon/Tues are cross-project, Wed-Fri are vertical team meetup-style. Mon and Fri would be 'optional'.<br />
** (hferenc): Unifying image and flavor metadata (https://bugs.launchpad.net/nova/+bug/1582693)<br />
** (jroll): Ironic portgroups BP, can we approve or does it need a spec? https://blueprints.launchpad.net/nova/+spec/ironic-portgroups-support<br />
<br />
== Sub-teams ==<br />
<br />
There are also some Nova subteam meetings. See [[Nova#Active_Sub-teams:]] for details.<br />
<br />
== Previous meetings ==<br />
<br />
* [http://eavesdrop.openstack.org/meetings/nova/ All other meetings are here]<br />
<br />
[[category: compute]]<br />
[[category: meetings]]</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Stewardship_Working_Group&diff=132944Stewardship Working Group2016-09-14T10:26:22Z<p>John Garbutt: /* Stewardship Working Group (SWG) Meetings */</p>
<hr />
<div>= Stewardship Working Group (SWG) Meetings =<br />
<br />
The [https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee OpenStack Technical Committee] adopted a [https://review.openstack.org/#/c/337895/ resolution] [http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-07-12-20.01.html on July 12 2016] to setup the Stewardship Working Group (SWG):<br />
https://governance.openstack.org/resolutions/20160705-stewardship.html<br />
<br />
It was the stated intent in establishing this working group that the community would benefit from establishing a small group to review the leadership, communication, and decision making processes of the TC and OpenStack projects as a whole, and propose a set of improvements based on the the concepts of "Servant Leadership" and "Stewardship". The SWG will be responsible for producing actionable recommendations and improvements that the TC can then consider for adoption and roll out to the OpenStack community. Anyone interested in leadership, stewardship, and OpenStack is welcome to join the working group. <br />
<br />
The SWG is an advisory body. Final decisions about any changes proposed by the SWG will be made by the TC.<br />
<br />
== Courtesy Ping List ==<br />
<Please append your irc nick at the tail of the list><br />
<br />
amrith, dhellmann, gothicmindfood, ttx, jroll, johnthetubaguy, sdague, mordred, carolbarrett, nikhil, mugsie, thingie,<br />
<br />
== Tuesday, September 13th 1500 UTC ==<br />
WHERE: openstack-meeting-3 <br />
<br />
'''1 Review Action items from last week'''<br />
<br />
<br />
* everyone to continue to review https://etherpad.openstack.org/p/BarcelonaSWGMagic with a goal of having comments and updates in by end of this week<br />
* nikhil to tinker with the vision and update etherpad<br />
* everyone to review this https://review.openstack.org/#/c/357260/ and update with comments<br />
<br />
'''1 Take a pass through the 'short list' and update items as required'''<br />
<br />
[https://etherpad.openstack.org/p/swg-short-list-deliverables Etherpad]<br />
<br />
'''2 Discuss any documents that are available for review'''<br />
<br />
'''3 Open Discussion'''<br />
<br />
<br />
<br />
[[Meetings/SWGMeeting-AgendaHistory|Meeting Agenda History]]</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Nova/BugTriage&diff=128100Nova/BugTriage2016-07-14T14:11:04Z<p>John Garbutt: /* Nova Bug Triage */</p>
<hr />
<div>= Nova Bug Triage =<br />
<br />
Track how we are doing: http://45.55.105.55:8082/bugs-dashboard.html or here: http://45.55.105.55:3000/dashboard/db/openstack-bugs<br />
<br />
The triage of Nova bugs follows the OpenStack-wide process documented on [[BugTriage]].<br />
<br />
There is an open group you need to join to get permissions to set bug priorities: https://launchpad.net/~nova-bugs<br />
<br />
There is also a weekly Nova bug meeting here: [[Meetings/Nova/BugsTeam]]<br />
<br />
= Tags =<br />
<br />
All new bugs should be tagged to reflect which part of Nova they are related to. The current list of tags can be found below. Note that it is fine for a bug to receive more than one tag if appropriate. Launchpad Query: [https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW Untriaged Bugs Without Tags]<br />
<br />
Once new bugs have been tagged, they should be triaged as described on [[BugTriage]]. To help make sure that the triage queue stays under control, the following table lists the people that have committed to regularly triaging bugs for a given tag. The official (and inofficial) tags are at: https://bugs.launchpad.net/nova/+manage-official-tags<br />
<br />
== Tag Owner List ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Bug tag !! Description !! Owner(s) !! Untriaged Query !! All Query<br />
|-<br />
| api || Bugs related to the compute REST API implementation || sdague || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+ All]<br />
|-<br />
| availability-zones || Issues when segregating resources with availability zones. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=availability-zones+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=availability-zones+ All]<br />
|-<br />
| cells || Bugs with Nova cells || alaski || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+ All]<br />
|-<br />
| ceph || Bugs related to the ceph storage solution || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ceph+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ceph+ All]<br />
|-<br />
| cinder || Bugs related to the nova-cinder interaction. If the bug is determined to be in the upstream cinder source, the cinder project should also be added to the "Affects" list || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=cinder+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cinder+ All]<br />
|-<br />
| compute || Bugs in the nova-compute service that are not specific to a virt driver. || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+ All]<br />
|-<br />
| conductor || Bugs in the nova-conductor service || dansmith || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+ All]<br />
|-<br />
| config || All bugs related to the config options || [https://launchpad.net/~mzoeller markus_z] || [https://bugs.launchpad.net/nova/+bugs?field.tag=config+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=config+ All]<br />
|-<br />
| console || Bugs in the nova-console service (including nova-consoleauth, novncproxy, etc) || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+ All]<br />
|-<br />
| doc || Bugs which should affect the manuals project or nova internal docs || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=doc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=doc+ All]<br />
|-<br />
| db || Database (datastore) issues, including migrations || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+ All]<br />
|-<br />
| ec2 || Issues specific to EC2 API support. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ec2+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ec2+ All]<br />
|-<br />
| gate-failure || Bug reports which are used to categorize failures in the gate || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure+ All]<br />
|-<br />
| hyper-v || Problems specific to the hyper-v driver || alexpilotti || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+ All]<br />
|-<br />
| i18n || Issues with internationalization || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=i18n+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=i18n+ All]<br />
|-<br />
| ironic || Problems specific to the ironic driver || jlvillal / mrda / devananda (Ironic PTL) || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+ All]<br />
|-<br />
| kilo-backport-potential || Fixes to those bugs should potentially be backported to Kilo bug. If a bug was reported against Kilo, use this tag. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-backport-potential+ All]<br />
|-<br />
| kilo-rc-potential || Blocks (potentially) the release of (another) Kilo release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential+ All]<br />
|-<br />
| liberty-backport-potential || Fixes to those bugs should potentially be backported to Liberty || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-backport-potential+ All]<br />
|-<br />
| liberty-rc-potential || Blocks (potentially) the release of (another) Liberty release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential+ All]<br />
|-<br />
| libvirt || Problems specific to the libvirt (kvm or qemu) driver || kashyapc || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+ All]<br />
|-<br />
| live-migration || Problems specific when doing live migration. || PaulMurray || [https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+ All]<br />
|-<br />
| low-hanging-fruit || Should be an easy goal for new contributors || free for all || [https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit+ All]<br />
|-<br />
| lxc || Issues specific to LXC virtualization support || [https://launchpad.net/~thomas-maddox thomasem] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+ All]<br />
|-<br />
| mitaka-backport-potential || Fixes to those bugs should potentially be backported to Mitaka. If a bug was reported against Mitaka, use this tag. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-backport-potential+ All]<br />
|-<br />
| mitaka-rc-potential || Blocks (potentially) the release of (another) Mitaka release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential+ All]<br />
|-<br />
| needs-attention || Bugs which came up during the bug skimming duty and further steps are unclear. || [https://launchpad.net/~mzoeller markus_z] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-attention+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-attention+ All]<br />
|-<br />
| needs-functional-test || We need a functional test for this to avoid regression. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-functional-test+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-functional-test+ All]<br />
|-<br />
| network || Issues in nova-network ||(maybe dansmith?) || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+ All]<br />
|-<br />
| neutron || Issues with the nova-neutron-interaction. If the bug is determined to be in the upstream neutron source, the neutron project should also be added to the "Affects" list || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=neutron+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=neutron+ All]<br />
|-<br />
| nova-manage || Bugs in the nova-manage utility ([http://docs.openstack.org/developer/nova/man/nova-manage.html docs]) || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+ All]<br />
|-<br />
| numa || Issues where NUMA is involved || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=numa+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=numa+ All]<br />
|-<br />
| novaclient || novaclient bugs exist in their own project on launchpad, python-novaclient. They are not tagged bugs in the nova project. However, we still need one or more people signed up to make sure novaclient bugs get triaged and looked after. || melwitt || [https://bugs.launchpad.net/python-novaclient/+bugs?search=Search&field.status=New Untriaged] || [https://bugs.launchpad.net/python-novaclient All]<br />
|-<br />
| ops || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ops+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ops+ All]<br />
|-<br />
| oslo || Bugs related to Oslo integration (oslo-incubator or Oslo libraries). If the bug is determined to be in the upstream oslo source, the oslo project should also be added to the "Affects" list. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+ All]<br />
|-<br />
| pci || Bugs regarding pci-devices (includes "pci-passthrough") || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+ All]<br />
|-<br />
| postgresql || PostgreSQL specific bugs. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+ All]<br />
|-<br />
| quotas || Bugs related to restricting access to resources with quotas || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=quotas+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=quotas+ All]<br />
|-<br />
| race-condition || Issues which are hard to reproduce due to race conditions. Probably only useful in combination with other tags. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=race-condition+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=race-condition+ All]<br />
|-<br />
| resource-tracker || Issues with the tracking when and where we claim resources. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=resource-tracker+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=resource-tracker+ All]<br />
|-<br />
| rootwrap || Problems with run-as-root commands or the rootwrap framework. || ttx || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+ All]<br />
|-<br />
| scheduler || Bugs in the nova-scheduler service || bauzas || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+ All]<br />
|-<br />
| security || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=security+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=security+ All]<br />
|-<br />
| security-groups || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=security-groups+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=security-groups+ All]<br />
|-<br />
| testing || Bugs related to testing (unit tests, tempest integration) || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+ All]<br />
|-<br />
| unified-objects || Bugs related to the unified-objects work || [https://launchpad.net/~danms dansmith] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+ All]<br />
|-<br />
| upgrades || Issues with upgrades from one release to another. Those are usually critical bugs! || [https://launchpad.net/~danms dansmith] || [https://bugs.launchpad.net/nova/+bugs?field.tag=upgrades+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=upgrades+ All]<br />
|-<br />
| vmware || Issues specific to VMware virtualization support. || tjones || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+ All]<br />
|-<br />
| volumes || Issues related to volume support (Cinder integration) || ndipanov || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+ All]<br />
|-<br />
| xen || Issues with the libvirt+xen driver || [https://launchpad.net/~anthony-perard anthonyper], openstack-ci@xenproject.org || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen All]<br />
|-<br />
| xenserver || Issues specific to XenServer/XenAPI virtualization support || [https://launchpad.net/~bob-ball BobBall] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver All]<br />
|}<br />
<br />
== How to Subscribe to Tags ==<br />
[[File:Bugs-lp-subscription-new.png|800px|thumbnail|center|How to add a new subscription to bug reports which match certain tags. ]]<br />
[[File:Bugs-lp-subscription-list.png|800px|thumbnail|center|How to list and manage bug report subscriptions. ]]<br />
<br />
= Weekly bug skimming duty =<br />
<br />
Nova gets a lot of new bug reports each day. Each bug report needs to be skimmed if it is a valid report, if crucial information is missing and so on. The weekly bug skimming duty should spread the knowledge and effort of that task to multiple people. <br />
<br />
'''Newton Cycle'''<br />
{| class="wikitable"<br />
<br />
|-<br />
! from !! to !! (IRC) names<br />
|-<br />
| 2016-07-18 || 2016-07-22 || <your-name-here><br />
|-<br />
| 2016-07-11 || 2016-07-15 || johnthetubaguy, siva_krishnan, pumaranikar<br />
|-<br />
| 2016-07-04 || 2016-07-08 || ---<br />
|-<br />
| 2016-06-27 || 2016-07-01 || ---<br />
|-<br />
| 2016-06-20 || 2016-06-24 || ---<br />
|-<br />
| 2016-06-13 || 2016-06-17 || aunnam, sneti<br />
|-<br />
| 2016-06-06 || 2016-06-10 || takashin<br />
|-<br />
| 2016-05-30 || 2016-06-03 || pumaranikar, siva_krishnan <br />
|-<br />
| 2016-05-23 || 2016-05-27 || raj_singh, macsz<br />
|-<br />
| 2016-05-16 || 2016-05-20 || aunnam, sneti<br />
|-<br />
| 2016-05-16 || 2016-05-17 || andrearosa<br />
|-<br />
| 2016-04-28 || 2016-05-05 || pumaranikar<br />
|-<br />
| 2016-04-21 || 2016-04-28 || lyarwood<br />
|-<br />
| 2016-04-07 || 2016-04-14 || cihand<br />
|-<br />
|}<br />
<br />
'''The duty includes:'''<br />
* Switch the bug to "incomplete" when crucial information is missing and ask the reporter to provide more information. This includes:<br />
** steps to reproduce<br />
** the version of Nova and the novaclient (or os-client)<br />
** logs (on debug level)<br />
** environment details depending on the bug<br />
*** libvirt/kvm versions, VMWare version, ...<br />
*** storage type (ceph, LVM, GPFS, ...) <br />
*** network type (nova-network or neutron)<br />
* Close as "invalid" if it is a support request or feature request.<br />
* Switch to "confirm" if you could reproduce the described issue or can otherwise say that this bug report seems valid. This is not always possible for you because of missing resources like a ceph storage or something like that. <br />
* Add a tag (or more tags) if the report allows you to narrow down the area which potentially contains the issue. This should be the entry point for subteams to dig deeper to find the root cause and potential solutions.<br />
* Bring critical bugs to the attention of the other contributors. The #openstack-nova channel and/or a ML post is useful.<br />
<br />
<br />
In short, do as much as possible before the expertise of the subteams is needed. Also, if you spot potential critical bugs, shout out in the #openstack-nova channel (for markus_z or one of the core reviewers).<br />
<br />
'''Misc'''<br />
<br />
A bug report template can be found at [[Nova/BugsTeam/BugReportTemplate|BugReportTemplate]]<br />
<br />
= FAQ =<br />
<br />
Below are the most frequently asked questions about the bug triage. Please attend the [[Meetings/Nova/BugsTeam|nova bugs team meeting]] if you have more questions.<br />
<br />
'''Q:''' ''What's the goal of the bug skimming duty?'' <br/><br />
'''A:''' In short, reduce the amount of work other developers have to spent to do a proper root cause analysis (and later fix) of bug reports. For this, close the obviously invalid bug reports, confirm the obviously valid bug reports, ask questions if things are unclear.<br />
<br />
'''Q:''' ''Do I need to <u>prove</u> that a bug report is valid/invalid before I can set it to <code>Confirmed</code>/<code>Invalid</code> ?'' <br/><br />
'''A:''' No. Sometimes it's not even possible because you don't have the resources. Looking at the code and tests often enables you to make an educated guess. Citing your sources in a comment helps the discussion.<br />
<br />
'''Q:''' ''What's the best status to close a bug report if its issue cannot be reproduced?'' <br/><br />
'''A:''' Definitively <code>Invalid</code>. Note: The status <code>Incomplete</code> is an open state and means "more information is necessary".<br />
<br />
'''Q:''' ''How do I handle open bug reports which are <code>Incomplete</code> for too long?'' <br/><br />
'''A:''' If it is in this state for more than 30 days and no answers to the open questions are given, close it with <code>Won't Fix</code>.<br />
<br />
'''Q:''' ''How do I handle dependencies to other bugs or TBD features in other projects? For example, I can fix a bug in Nova but I need that a feature in Cinder gets implemented before.'' <br/><br />
'''A:''' Leave a comment in the Nova bug report which explains this dependency and leave a link to the blueprint or bug report of the other project you depend on.<br />
<br />
'''Q:''' ''Do I have to double-check bug reports which are <code>New</code> and have an assignee?'' <br/><br />
'''A:''' Usually not. This bug report has an inconsistent state though. If a bug report has an assignee, it should be <code>In Progress</code> and have an importance set.<br />
<br />
'''Q:''' ''question?'' <br/><br />
'''A:'''</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Nova/BugTriage&diff=127843Nova/BugTriage2016-07-08T14:41:24Z<p>John Garbutt: /* Nova Bug Triage */</p>
<hr />
<div>= Nova Bug Triage =<br />
<br />
Track how we are doing: http://45.55.105.55:8082/bugs-dashboard.html<br />
<br />
The triage of Nova bugs follows the OpenStack-wide process documented on [[BugTriage]].<br />
<br />
There is an open group you need to join to get permissions to set bug priorities: https://launchpad.net/~nova-bugs<br />
<br />
There is also a weekly Nova bug meeting here: [[Meetings/Nova/BugsTeam]]<br />
<br />
= Tags =<br />
<br />
All new bugs should be tagged to reflect which part of Nova they are related to. The current list of tags can be found below. Note that it is fine for a bug to receive more than one tag if appropriate. Launchpad Query: [https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW Untriaged Bugs Without Tags]<br />
<br />
Once new bugs have been tagged, they should be triaged as described on [[BugTriage]]. To help make sure that the triage queue stays under control, the following table lists the people that have committed to regularly triaging bugs for a given tag. The official (and inofficial) tags are at: https://bugs.launchpad.net/nova/+manage-official-tags<br />
<br />
== Tag Owner List ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Bug tag !! Description !! Owner(s) !! Untriaged Query !! All Query<br />
|-<br />
| api || Bugs related to the compute REST API implementation || sdague || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+ All]<br />
|-<br />
| availability-zones || Issues when segregating resources with availability zones. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=availability-zones+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=availability-zones+ All]<br />
|-<br />
| cells || Bugs with Nova cells || alaski || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+ All]<br />
|-<br />
| ceph || Bugs related to the ceph storage solution || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ceph+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ceph+ All]<br />
|-<br />
| cinder || Bugs related to the nova-cinder interaction. If the bug is determined to be in the upstream cinder source, the cinder project should also be added to the "Affects" list || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=cinder+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cinder+ All]<br />
|-<br />
| compute || Bugs in the nova-compute service that are not specific to a virt driver. || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+ All]<br />
|-<br />
| conductor || Bugs in the nova-conductor service || dansmith || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+ All]<br />
|-<br />
| config || All bugs related to the config options || [https://launchpad.net/~mzoeller markus_z] || [https://bugs.launchpad.net/nova/+bugs?field.tag=config+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=config+ All]<br />
|-<br />
| console || Bugs in the nova-console service (including nova-consoleauth, novncproxy, etc) || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+ All]<br />
|-<br />
| doc || Bugs which should affect the manuals project or nova internal docs || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=doc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=doc+ All]<br />
|-<br />
| db || Database (datastore) issues, including migrations || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+ All]<br />
|-<br />
| ec2 || Issues specific to EC2 API support. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ec2+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ec2+ All]<br />
|-<br />
| gate-failure || Bug reports which are used to categorize failures in the gate || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure+ All]<br />
|-<br />
| hyper-v || Problems specific to the hyper-v driver || alexpilotti || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+ All]<br />
|-<br />
| i18n || Issues with internationalization || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=i18n+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=i18n+ All]<br />
|-<br />
| ironic || Problems specific to the ironic driver || jlvillal / mrda / devananda (Ironic PTL) || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+ All]<br />
|-<br />
| kilo-backport-potential || Fixes to those bugs should potentially be backported to Kilo bug. If a bug was reported against Kilo, use this tag. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-backport-potential+ All]<br />
|-<br />
| kilo-rc-potential || Blocks (potentially) the release of (another) Kilo release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential+ All]<br />
|-<br />
| liberty-backport-potential || Fixes to those bugs should potentially be backported to Liberty || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-backport-potential+ All]<br />
|-<br />
| liberty-rc-potential || Blocks (potentially) the release of (another) Liberty release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential+ All]<br />
|-<br />
| libvirt || Problems specific to the libvirt (kvm or qemu) driver || kashyapc || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+ All]<br />
|-<br />
| live-migration || Problems specific when doing live migration. || PaulMurray || [https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+ All]<br />
|-<br />
| low-hanging-fruit || Should be an easy goal for new contributors || free for all || [https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit+ All]<br />
|-<br />
| lxc || Issues specific to LXC virtualization support || [https://launchpad.net/~thomas-maddox thomasem] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+ All]<br />
|-<br />
| mitaka-backport-potential || Fixes to those bugs should potentially be backported to Mitaka. If a bug was reported against Mitaka, use this tag. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-backport-potential+ All]<br />
|-<br />
| mitaka-rc-potential || Blocks (potentially) the release of (another) Mitaka release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential+ All]<br />
|-<br />
| needs-attention || Bugs which came up during the bug skimming duty and further steps are unclear. || [https://launchpad.net/~mzoeller markus_z] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-attention+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-attention+ All]<br />
|-<br />
| needs-functional-test || We need a functional test for this to avoid regression. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-functional-test+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-functional-test+ All]<br />
|-<br />
| network || Issues in nova-network ||(maybe dansmith?) || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+ All]<br />
|-<br />
| neutron || Issues with the nova-neutron-interaction. If the bug is determined to be in the upstream neutron source, the neutron project should also be added to the "Affects" list || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=neutron+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=neutron+ All]<br />
|-<br />
| nova-manage || Bugs in the nova-manage utility ([http://docs.openstack.org/developer/nova/man/nova-manage.html docs]) || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+ All]<br />
|-<br />
| numa || Issues where NUMA is involved || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=numa+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=numa+ All]<br />
|-<br />
| novaclient || novaclient bugs exist in their own project on launchpad, python-novaclient. They are not tagged bugs in the nova project. However, we still need one or more people signed up to make sure novaclient bugs get triaged and looked after. || melwitt || [https://bugs.launchpad.net/python-novaclient/+bugs?search=Search&field.status=New Untriaged] || [https://bugs.launchpad.net/python-novaclient All]<br />
|-<br />
| ops || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ops+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ops+ All]<br />
|-<br />
| oslo || Bugs related to Oslo integration (oslo-incubator or Oslo libraries). If the bug is determined to be in the upstream oslo source, the oslo project should also be added to the "Affects" list. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+ All]<br />
|-<br />
| pci || Bugs regarding pci-devices (includes "pci-passthrough") || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+ All]<br />
|-<br />
| postgresql || PostgreSQL specific bugs. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+ All]<br />
|-<br />
| quotas || Bugs related to restricting access to resources with quotas || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=quotas+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=quotas+ All]<br />
|-<br />
| race-condition || Issues which are hard to reproduce due to race conditions. Probably only useful in combination with other tags. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=race-condition+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=race-condition+ All]<br />
|-<br />
| resource-tracker || Issues with the tracking when and where we claim resources. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=resource-tracker+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=resource-tracker+ All]<br />
|-<br />
| rootwrap || Problems with run-as-root commands or the rootwrap framework. || ttx || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+ All]<br />
|-<br />
| scheduler || Bugs in the nova-scheduler service || bauzas || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+ All]<br />
|-<br />
| security || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=security+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=security+ All]<br />
|-<br />
| security-groups || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=security-groups+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=security-groups+ All]<br />
|-<br />
| testing || Bugs related to testing (unit tests, tempest integration) || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+ All]<br />
|-<br />
| unified-objects || Bugs related to the unified-objects work || [https://launchpad.net/~danms dansmith] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+ All]<br />
|-<br />
| upgrades || Issues with upgrades from one release to another. Those are usually critical bugs! || [https://launchpad.net/~danms dansmith] || [https://bugs.launchpad.net/nova/+bugs?field.tag=upgrades+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=upgrades+ All]<br />
|-<br />
| vmware || Issues specific to VMware virtualization support. || tjones || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+ All]<br />
|-<br />
| volumes || Issues related to volume support (Cinder integration) || ndipanov || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+ All]<br />
|-<br />
| xen || Issues with the libvirt+xen driver || [https://launchpad.net/~anthony-perard anthonyper], openstack-ci@xenproject.org || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen All]<br />
|-<br />
| xenserver || Issues specific to XenServer/XenAPI virtualization support || [https://launchpad.net/~bob-ball BobBall] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver All]<br />
|}<br />
<br />
== How to Subscribe to Tags ==<br />
[[File:Bugs-lp-subscription-new.png|800px|thumbnail|center|How to add a new subscription to bug reports which match certain tags. ]]<br />
[[File:Bugs-lp-subscription-list.png|800px|thumbnail|center|How to list and manage bug report subscriptions. ]]<br />
<br />
= Weekly bug skimming duty =<br />
<br />
Nova gets a lot of new bug reports each day. Each bug report needs to be skimmed if it is a valid report, if crucial information is missing and so on. The weekly bug skimming duty should spread the knowledge and effort of that task to multiple people. <br />
<br />
'''Newton Cycle'''<br />
{| class="wikitable"<br />
<br />
|-<br />
! from !! to !! (IRC) names<br />
|-<br />
| 2016-07-11 || 2016-07-15 || johnthetubaguy<br />
|-<br />
| 2016-07-04 || 2016-07-08 || <your-name-here><br />
|-<br />
| 2016-06-27 || 2016-07-01 || <your-name-here><br />
|-<br />
| 2016-06-20 || 2016-06-24 || ---<br />
|-<br />
| 2016-06-13 || 2016-06-17 || aunnam, sneti<br />
|-<br />
| 2016-06-06 || 2016-06-10 || takashin<br />
|-<br />
| 2016-05-30 || 2016-06-03 || pumaranikar, siva_krishnan <br />
|-<br />
| 2016-05-23 || 2016-05-27 || raj_singh, macsz<br />
|-<br />
| 2016-05-16 || 2016-05-20 || aunnam, sneti<br />
|-<br />
| 2016-05-16 || 2016-05-17 || andrearosa<br />
|-<br />
| 2016-04-28 || 2016-05-05 || pumaranikar<br />
|-<br />
| 2016-04-21 || 2016-04-28 || lyarwood<br />
|-<br />
| 2016-04-07 || 2016-04-14 || cihand<br />
|-<br />
|}<br />
<br />
'''The duty includes:'''<br />
* Switch the bug to "incomplete" when crucial information is missing and ask the reporter to provide more information. This includes:<br />
** steps to reproduce<br />
** the version of Nova and the novaclient (or os-client)<br />
** logs (on debug level)<br />
** environment details depending on the bug<br />
*** libvirt/kvm versions, VMWare version, ...<br />
*** storage type (ceph, LVM, GPFS, ...) <br />
*** network type (nova-network or neutron)<br />
* Close as "invalid" if it is a support request or feature request.<br />
* Switch to "confirm" if you could reproduce the described issue or can otherwise say that this bug report seems valid. This is not always possible for you because of missing resources like a ceph storage or something like that. <br />
* Add a tag (or more tags) if the report allows you to narrow down the area which potentially contains the issue. This should be the entry point for subteams to dig deeper to find the root cause and potential solutions.<br />
* Bring critical bugs to the attention of the other contributors. The #openstack-nova channel and/or a ML post is useful.<br />
<br />
<br />
In short, do as much as possible before the expertise of the subteams is needed. Also, if you spot potential critical bugs, shout out in the #openstack-nova channel (for markus_z or one of the core reviewers).<br />
<br />
'''Misc'''<br />
<br />
A bug report template can be found at [[Nova/BugsTeam/BugReportTemplate|BugReportTemplate]]<br />
<br />
= FAQ =<br />
<br />
Below are the most frequently asked questions about the bug triage. Please attend the [[Meetings/Nova/BugsTeam|nova bugs team meeting]] if you have more questions.<br />
<br />
'''Q:''' ''What's the goal of the bug skimming duty?'' <br/><br />
'''A:''' In short, reduce the amount of work other developers have to spent to do a proper root cause analysis (and later fix) of bug reports. For this, close the obviously invalid bug reports, confirm the obviously valid bug reports, ask questions if things are unclear.<br />
<br />
'''Q:''' ''Do I need to <u>prove</u> that a bug report is valid/invalid before I can set it to <code>Confirmed</code>/<code>Invalid</code> ?'' <br/><br />
'''A:''' No. Sometimes it's not even possible because you don't have the resources. Looking at the code and tests often enables you to make an educated guess. Citing your sources in a comment helps the discussion.<br />
<br />
'''Q:''' ''What's the best status to close a bug report if its issue cannot be reproduced?'' <br/><br />
'''A:''' Definitively <code>Invalid</code>. Note: The status <code>Incomplete</code> is an open state and means "more information is necessary".<br />
<br />
'''Q:''' ''How do I handle open bug reports which are <code>Incomplete</code> for too long?'' <br/><br />
'''A:''' If it is in this state for more than 30 days and no answers to the open questions are given, close it with <code>Won't Fix</code>.<br />
<br />
'''Q:''' ''How do I handle dependencies to other bugs or TBD features in other projects? For example, I can fix a bug in Nova but I need that a feature in Cinder gets implemented before.'' <br/><br />
'''A:''' Leave a comment in the Nova bug report which explains this dependency and leave a link to the blueprint or bug report of the other project you depend on.<br />
<br />
'''Q:''' ''Do I have to double-check bug reports which are <code>New</code> and have an assignee?'' <br/><br />
'''A:''' Usually not. This bug report has an inconsistent state though. If a bug report has an assignee, it should be <code>In Progress</code> and have an importance set.<br />
<br />
'''Q:''' ''question?'' <br/><br />
'''A:'''</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Nova/BugTriage&diff=127835Nova/BugTriage2016-07-08T13:28:25Z<p>John Garbutt: /* Weekly bug skimming duty */</p>
<hr />
<div>= Nova Bug Triage =<br />
<br />
The triage of Nova bugs follows the OpenStack-wide process documented on [[BugTriage]].<br />
<br />
There is an open group you need to join to get permissions to set bug priorities: https://launchpad.net/~nova-bugs<br />
<br />
There is also a weekly Nova bug meeting here: [[Meetings/Nova/BugsTeam]]<br />
<br />
= Tags =<br />
<br />
All new bugs should be tagged to reflect which part of Nova they are related to. The current list of tags can be found below. Note that it is fine for a bug to receive more than one tag if appropriate. Launchpad Query: [https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW Untriaged Bugs Without Tags]<br />
<br />
Once new bugs have been tagged, they should be triaged as described on [[BugTriage]]. To help make sure that the triage queue stays under control, the following table lists the people that have committed to regularly triaging bugs for a given tag. The official (and inofficial) tags are at: https://bugs.launchpad.net/nova/+manage-official-tags<br />
<br />
== Tag Owner List ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Bug tag !! Description !! Owner(s) !! Untriaged Query !! All Query<br />
|-<br />
| api || Bugs related to the compute REST API implementation || sdague || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=api+ All]<br />
|-<br />
| availability-zones || Issues when segregating resources with availability zones. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=availability-zones+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=availability-zones+ All]<br />
|-<br />
| cells || Bugs with Nova cells || alaski || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cells+ All]<br />
|-<br />
| ceph || Bugs related to the ceph storage solution || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ceph+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ceph+ All]<br />
|-<br />
| cinder || Bugs related to the nova-cinder interaction. If the bug is determined to be in the upstream cinder source, the cinder project should also be added to the "Affects" list || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=cinder+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=cinder+ All]<br />
|-<br />
| compute || Bugs in the nova-compute service that are not specific to a virt driver. || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=compute+ All]<br />
|-<br />
| conductor || Bugs in the nova-conductor service || dansmith || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=conductor+ All]<br />
|-<br />
| config || All bugs related to the config options || [https://launchpad.net/~mzoeller markus_z] || [https://bugs.launchpad.net/nova/+bugs?field.tag=config+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=config+ All]<br />
|-<br />
| console || Bugs in the nova-console service (including nova-consoleauth, novncproxy, etc) || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=console+ All]<br />
|-<br />
| doc || Bugs which should affect the manuals project or nova internal docs || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=doc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=doc+ All]<br />
|-<br />
| db || Database (datastore) issues, including migrations || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=db+ All]<br />
|-<br />
| ec2 || Issues specific to EC2 API support. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ec2+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ec2+ All]<br />
|-<br />
| gate-failure || Bug reports which are used to categorize failures in the gate || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure+ All]<br />
|-<br />
| hyper-v || Problems specific to the hyper-v driver || alexpilotti || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=hyper-v+ All]<br />
|-<br />
| i18n || Issues with internationalization || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=i18n+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=i18n+ All]<br />
|-<br />
| ironic || Problems specific to the ironic driver || jlvillal / mrda / devananda (Ironic PTL) || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ironic+ All]<br />
|-<br />
| kilo-backport-potential || Fixes to those bugs should potentially be backported to Kilo bug. If a bug was reported against Kilo, use this tag. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-backport-potential+ All]<br />
|-<br />
| kilo-rc-potential || Blocks (potentially) the release of (another) Kilo release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential+ All]<br />
|-<br />
| liberty-backport-potential || Fixes to those bugs should potentially be backported to Liberty || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-backport-potential+ All]<br />
|-<br />
| liberty-rc-potential || Blocks (potentially) the release of (another) Liberty release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential+ All]<br />
|-<br />
| libvirt || Problems specific to the libvirt (kvm or qemu) driver || kashyapc || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=libvirt+ All]<br />
|-<br />
| live-migration || Problems specific when doing live migration. || PaulMurray || [https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=live-migration+ All]<br />
|-<br />
| low-hanging-fruit || Should be an easy goal for new contributors || free for all || [https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit+ All]<br />
|-<br />
| lxc || Issues specific to LXC virtualization support || [https://launchpad.net/~thomas-maddox thomasem] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=lxc+ All]<br />
|-<br />
| mitaka-backport-potential || Fixes to those bugs should potentially be backported to Mitaka. If a bug was reported against Mitaka, use this tag. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-backport-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-backport-potential+ All]<br />
|-<br />
| mitaka-rc-potential || Blocks (potentially) the release of (another) Mitaka release || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential+ All]<br />
|-<br />
| needs-attention || Bugs which came up during the bug skimming duty and further steps are unclear. || [https://launchpad.net/~mzoeller markus_z] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-attention+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-attention+ All]<br />
|-<br />
| needs-functional-test || We need a functional test for this to avoid regression. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-functional-test+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=needs-functional-test+ All]<br />
|-<br />
| network || Issues in nova-network ||(maybe dansmith?) || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=network+ All]<br />
|-<br />
| neutron || Issues with the nova-neutron-interaction. If the bug is determined to be in the upstream neutron source, the neutron project should also be added to the "Affects" list || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=neutron+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=neutron+ All]<br />
|-<br />
| nova-manage || Bugs in the nova-manage utility ([http://docs.openstack.org/developer/nova/man/nova-manage.html docs]) || melwitt || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=nova-manage+ All]<br />
|-<br />
| numa || Issues where NUMA is involved || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=numa+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=numa+ All]<br />
|-<br />
| novaclient || novaclient bugs exist in their own project on launchpad, python-novaclient. They are not tagged bugs in the nova project. However, we still need one or more people signed up to make sure novaclient bugs get triaged and looked after. || melwitt || [https://bugs.launchpad.net/python-novaclient/+bugs?search=Search&field.status=New Untriaged] || [https://bugs.launchpad.net/python-novaclient All]<br />
|-<br />
| ops || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=ops+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=ops+ All]<br />
|-<br />
| oslo || Bugs related to Oslo integration (oslo-incubator or Oslo libraries). If the bug is determined to be in the upstream oslo source, the oslo project should also be added to the "Affects" list. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=oslo+ All]<br />
|-<br />
| pci || Bugs regarding pci-devices (includes "pci-passthrough") || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=pci+ All]<br />
|-<br />
| postgresql || PostgreSQL specific bugs. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=postgresql+ All]<br />
|-<br />
| quotas || Bugs related to restricting access to resources with quotas || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=quotas+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=quotas+ All]<br />
|-<br />
| race-condition || Issues which are hard to reproduce due to race conditions. Probably only useful in combination with other tags. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=race-condition+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=race-condition+ All]<br />
|-<br />
| resource-tracker || Issues with the tracking when and where we claim resources. || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=resource-tracker+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=resource-tracker+ All]<br />
|-<br />
| rootwrap || Problems with run-as-root commands or the rootwrap framework. || ttx || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=rootwrap+ All]<br />
|-<br />
| scheduler || Bugs in the nova-scheduler service || bauzas || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler+ All]<br />
|-<br />
| security || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=security+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=security+ All]<br />
|-<br />
| security-groups || ? || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=security-groups+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=security-groups+ All]<br />
|-<br />
| testing || Bugs related to testing (unit tests, tempest integration) || ? || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=testing+ All]<br />
|-<br />
| unified-objects || Bugs related to the unified-objects work || [https://launchpad.net/~danms dansmith] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=unified-objects+ All]<br />
|-<br />
| upgrades || Issues with upgrades from one release to another. Those are usually critical bugs! || [https://launchpad.net/~danms dansmith] || [https://bugs.launchpad.net/nova/+bugs?field.tag=upgrades+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=upgrades+ All]<br />
|-<br />
| vmware || Issues specific to VMware virtualization support. || tjones || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=vmware+ All]<br />
|-<br />
| volumes || Issues related to volume support (Cinder integration) || ndipanov || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=volumes+ All]<br />
|-<br />
| xen || Issues with the libvirt+xen driver || [https://launchpad.net/~anthony-perard anthonyper], openstack-ci@xenproject.org || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xen All]<br />
|-<br />
| xenserver || Issues specific to XenServer/XenAPI virtualization support || [https://launchpad.net/~bob-ball BobBall] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver+&field.status%3Alist=NEW Untriaged] || [https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver All]<br />
|}<br />
<br />
== How to Subscribe to Tags ==<br />
[[File:Bugs-lp-subscription-new.png|800px|thumbnail|center|How to add a new subscription to bug reports which match certain tags. ]]<br />
[[File:Bugs-lp-subscription-list.png|800px|thumbnail|center|How to list and manage bug report subscriptions. ]]<br />
<br />
= Weekly bug skimming duty =<br />
<br />
Nova gets a lot of new bug reports each day. Each bug report needs to be skimmed if it is a valid report, if crucial information is missing and so on. The weekly bug skimming duty should spread the knowledge and effort of that task to multiple people. <br />
<br />
'''Newton Cycle'''<br />
{| class="wikitable"<br />
<br />
|-<br />
! from !! to !! (IRC) names<br />
|-<br />
| 2016-07-11 || 2016-07-15 || johnthetubaguy<br />
|-<br />
| 2016-07-04 || 2016-07-08 || <your-name-here><br />
|-<br />
| 2016-06-27 || 2016-07-01 || <your-name-here><br />
|-<br />
| 2016-06-20 || 2016-06-24 || ---<br />
|-<br />
| 2016-06-13 || 2016-06-17 || aunnam, sneti<br />
|-<br />
| 2016-06-06 || 2016-06-10 || takashin<br />
|-<br />
| 2016-05-30 || 2016-06-03 || pumaranikar, siva_krishnan <br />
|-<br />
| 2016-05-23 || 2016-05-27 || raj_singh, macsz<br />
|-<br />
| 2016-05-16 || 2016-05-20 || aunnam, sneti<br />
|-<br />
| 2016-05-16 || 2016-05-17 || andrearosa<br />
|-<br />
| 2016-04-28 || 2016-05-05 || pumaranikar<br />
|-<br />
| 2016-04-21 || 2016-04-28 || lyarwood<br />
|-<br />
| 2016-04-07 || 2016-04-14 || cihand<br />
|-<br />
|}<br />
<br />
'''The duty includes:'''<br />
* Switch the bug to "incomplete" when crucial information is missing and ask the reporter to provide more information. This includes:<br />
** steps to reproduce<br />
** the version of Nova and the novaclient (or os-client)<br />
** logs (on debug level)<br />
** environment details depending on the bug<br />
*** libvirt/kvm versions, VMWare version, ...<br />
*** storage type (ceph, LVM, GPFS, ...) <br />
*** network type (nova-network or neutron)<br />
* Close as "invalid" if it is a support request or feature request.<br />
* Switch to "confirm" if you could reproduce the described issue or can otherwise say that this bug report seems valid. This is not always possible for you because of missing resources like a ceph storage or something like that. <br />
* Add a tag (or more tags) if the report allows you to narrow down the area which potentially contains the issue. This should be the entry point for subteams to dig deeper to find the root cause and potential solutions.<br />
* Bring critical bugs to the attention of the other contributors. The #openstack-nova channel and/or a ML post is useful.<br />
<br />
<br />
In short, do as much as possible before the expertise of the subteams is needed. Also, if you spot potential critical bugs, shout out in the #openstack-nova channel (for markus_z or one of the core reviewers).<br />
<br />
'''Misc'''<br />
<br />
A bug report template can be found at [[Nova/BugsTeam/BugReportTemplate|BugReportTemplate]]<br />
<br />
= FAQ =<br />
<br />
Below are the most frequently asked questions about the bug triage. Please attend the [[Meetings/Nova/BugsTeam|nova bugs team meeting]] if you have more questions.<br />
<br />
'''Q:''' ''What's the goal of the bug skimming duty?'' <br/><br />
'''A:''' In short, reduce the amount of work other developers have to spent to do a proper root cause analysis (and later fix) of bug reports. For this, close the obviously invalid bug reports, confirm the obviously valid bug reports, ask questions if things are unclear.<br />
<br />
'''Q:''' ''Do I need to <u>prove</u> that a bug report is valid/invalid before I can set it to <code>Confirmed</code>/<code>Invalid</code> ?'' <br/><br />
'''A:''' No. Sometimes it's not even possible because you don't have the resources. Looking at the code and tests often enables you to make an educated guess. Citing your sources in a comment helps the discussion.<br />
<br />
'''Q:''' ''What's the best status to close a bug report if its issue cannot be reproduced?'' <br/><br />
'''A:''' Definitively <code>Invalid</code>. Note: The status <code>Incomplete</code> is an open state and means "more information is necessary".<br />
<br />
'''Q:''' ''How do I handle open bug reports which are <code>Incomplete</code> for too long?'' <br/><br />
'''A:''' If it is in this state for more than 30 days and no answers to the open questions are given, close it with <code>Won't Fix</code>.<br />
<br />
'''Q:''' ''How do I handle dependencies to other bugs or TBD features in other projects? For example, I can fix a bug in Nova but I need that a feature in Cinder gets implemented before.'' <br/><br />
'''A:''' Leave a comment in the Nova bug report which explains this dependency and leave a link to the blueprint or bug report of the other project you depend on.<br />
<br />
'''Q:''' ''Do I have to double-check bug reports which are <code>New</code> and have an assignee?'' <br/><br />
'''A:''' Usually not. This bug report has an inconsistent state though. If a bug report has an assignee, it should be <code>In Progress</code> and have an importance set.<br />
<br />
'''Q:''' ''question?'' <br/><br />
'''A:'''</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=127775ConfigOptionsConsistency2016-07-07T12:27:26Z<p>John Garbutt: /* Maintaining consistency for Config options */</p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
You can track progress here: http://45.55.105.55:8082/config-options.html<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
# Omit this section if it is only duplicating the machine readable<br />
# info in the option definition, such as for all boolean settings,<br />
# unless the true/false values need describing for some reason.<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If there is nothing interesting, just omit this section.<br />
<br />
""")<br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be in a group, lets move that into the group. We do that by using the deprecated group and name as required. Don't forget the reno note!<br />
<br />
Every option group should have a good title and help text set. For cases where there are lots of required options in the group, dependent on a particular setting like the virt driver setting, be sure to describe that in the group configuration help.<br />
<br />
Check the type of the option, link Int or IP, and make sure you use things like string option choices, and int min values. For more info see: http://docs.openstack.org/developer/oslo.config/opts.html<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
=== Future stuff ===<br />
<br />
==== mutable ====<br />
<br />
In a similar way we should look at the mutable=true flag, which says its safe to reload the configuration value when the service is sent a SIG_HUP. To be safe, an option must be rechecked each time. It cannot be cached, EG in a local var outside a long-running loop, or used to set something up. The former case can easily be fixed by checking the option direct from CONF each time around the loop. The latter case requires the use of a mutation hook, registered by CONF.register_mutate_hook, which repeats the setup. Examples:<br />
<br />
* https://review.openstack.org/#/c/319203 - check CONF in the loop<br />
* https://review.openstack.org/#/c/254821 - use a mutation hook to redo setup</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=127774ConfigOptionsConsistency2016-07-07T12:26:58Z<p>John Garbutt: </p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
You can track progress here: http://45.55.105.55:8082/config-options.html<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
# Omit this section if it is only duplicating the machine readable<br />
# info in the option definition, such as for all boolean settings,<br />
# unless the true/false values need describing for some reason.<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If there is nothing interesting, just omit this section.<br />
<br />
""")<br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be in a group, lets move that into the group. We do that by using the deprecated group and name as required. Don't forget the reno note!<br />
<br />
Every option group should have a good title and help text set. For cases where there are lots of required options in the group, dependent on a particular setting like the virt driver setting, be sure to describe that in the group configuration help.<br />
<br />
Check the type of the option, link Int or IP, and make sure you use things like string option choices, and int min values. For more info see: http://docs.openstack.org/developer/oslo.config/opts.html<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
=== Future stuff ===<br />
<br />
==== mutable ====<br />
<br />
In a similar way we should look at the mutable=true flag, which says its safe to reload the configuration value when the service is sent a SIG_HUP. To be safe, an option must be rechecked each time. It cannot be cached, EG in a local var outside a long-running loop, or used to set something up. The former case can easily be fixed by checking the option direct from CONF each time around the loop. The latter case requires the use of a mutation hook, registered by CONF.register_mutate_hook, which repeats the setup. Examples:<br />
<br />
* https://review.openstack.org/#/c/319203 - check CONF in the loop<br />
* https://review.openstack.org/#/c/254821 - use a mutation hook to redo setup</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=127473ConfigOptionsConsistency2016-06-29T14:37:53Z<p>John Garbutt: </p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
# Omit this section if it is only duplicating the machine readable<br />
# info in the option definition, such as for all boolean settings,<br />
# unless the true/false values need describing for some reason.<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If there is nothing interesting, just omit this section.<br />
<br />
""")<br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be in a group, lets move that into the group. We do that by using the deprecated group and name as required. Don't forget the reno note!<br />
<br />
Every option group should have a good title and help text set. For cases where there are lots of required options in the group, dependent on a particular setting like the virt driver setting, be sure to describe that in the group configuration help.<br />
<br />
Check the type of the option, link Int or IP, and make sure you use things like string option choices, and int min values. For more info see: http://docs.openstack.org/developer/oslo.config/opts.html<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
=== Future stuff ===<br />
<br />
==== mutable ====<br />
<br />
In a similar way we should look at the mutable=true flag, which says its safe to reload the configuration value when the service is sent a SIG_HUP. To be safe, an option must be rechecked each time. It cannot be cached, EG in a local var outside a long-running loop, or used to set something up. The former case can easily be fixed by checking the option direct from CONF each time around the loop. The latter case requires the use of a mutation hook, registered by CONF.register_mutate_hook, which repeats the setup. Examples:<br />
<br />
* https://review.openstack.org/#/c/319203 - check CONF in the loop<br />
* https://review.openstack.org/#/c/254821 - use a mutation hook to redo setup</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=127472ConfigOptionsConsistency2016-06-29T14:37:09Z<p>John Garbutt: /* check_opt_group_and_type */</p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
# Omit this section if it is only duplicating the machine readable<br />
# info in the option definition, such as for all boolean settings,<br />
# unless the true/false values need describing for some reason.<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If there is nothing interesting, just omit this section.<br />
<br />
""")<br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be in a group, lets move that into the group. We do that by using the deprecated group and name as required. Don't forget the reno note!<br />
<br />
Every option group should have a good title and help text set. For cases where there are lots of required options in the group, dependent on a particular setting like the virt driver setting, be sure to describe that in the group configuration help.<br />
<br />
Check the type of the option, link Int or IP, and make sure you use things like string option choices, and int min values. For more info see: http://docs.openstack.org/developer/oslo.config/opts.html<br />
<br />
=== Future stuff ===<br />
<br />
==== mutable ====<br />
<br />
In a similar way we should look at the mutable=true flag, which says its safe to reload the configuration value when the service is sent a SIG_HUP. To be safe, an option must be rechecked each time. It cannot be cached, EG in a local var outside a long-running loop, or used to set something up. The former case can easily be fixed by checking the option direct from CONF each time around the loop. The latter case requires the use of a mutation hook, registered by CONF.register_mutate_hook, which repeats the setup. Examples:<br />
<br />
* https://review.openstack.org/#/c/319203 - check CONF in the loop<br />
* https://review.openstack.org/#/c/254821 - use a mutation hook to redo setup<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=127352ConfigOptionsConsistency2016-06-27T16:03:47Z<p>John Garbutt: /* fix_opt_description */</p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
# Omit this section if it is only duplicating the machine readable<br />
# info in the option definition, such as for all boolean settings,<br />
# unless the true/false values need describing for some reason.<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If there is nothing interesting, just omit this section.<br />
<br />
""")<br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be part of an option group, such as a libvirt specific option that is in the default group, we should move that option into the group, using the deprecated group and name as required.<br />
<br />
In a similar way we should look at the mutable=true flag, which says its safe to reload the configuration value when the service is sent a SIG_HUP. To be safe, an option must be rechecked each time. It cannot be cached, EG in a local var outside a long-running loop, or used to set something up. The former case can easily be fixed by checking the option direct from CONF each time around the loop. The latter case requires the use of a mutation hook, registered by CONF.register_mutate_hook, which repeats the setup. Examples:<br />
<br />
* https://review.openstack.org/#/c/319203 - check CONF in the loop<br />
* https://review.openstack.org/#/c/254821 - use a mutation hook to redo setup<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=127266ConfigOptionsConsistency2016-06-24T10:30:16Z<p>John Garbutt: /* fix_opt_description */</p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
# Omit this section if it is only duplicating the machine readable<br />
# info in the option definition, such as for all boolean settings,<br />
# unless the true/false values need describing for some reason.<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If it stand solely on its own, use "None"<br />
<br />
""")<br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be part of an option group, such as a libvirt specific option that is in the default group, we should move that option into the group, using the deprecated group and name as required.<br />
<br />
In a similar way we should look at the mutable=true flag, which says its safe to reload the configuration value when the service is sent a SIG_HUP. To be safe, an option must be rechecked each time. It cannot be cached, EG in a local var outside a long-running loop, or used to set something up. The former case can easily be fixed by checking the option direct from CONF each time around the loop. The latter case requires the use of a mutation hook, registered by CONF.register_mutate_hook, which repeats the setup. Examples:<br />
<br />
* https://review.openstack.org/#/c/319203 - check CONF in the loop<br />
* https://review.openstack.org/#/c/254821 - use a mutation hook to redo setup<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=126886ConfigOptionsConsistency2016-06-16T12:49:41Z<p>John Garbutt: /* fix_opt_description */</p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
# Omit this section if it is only duplicating the machine readable<br />
# info in the option definition, such as for all boolean settings,<br />
# unless the true/false values need describing for some reason.<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If it stand solely on its own, use "None"<br />
<br />
""")<br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be part of an option group, such as a libvirt specific option that is in the default group, we should move that option into the group, using the deprecated group and name as required.<br />
<br />
In a similar way we should look at the mutable=true flag, which says its safe to reload the configuration value when the service is sent a SIG_HUP. To be safe, an option must be rechecked each time. It cannot be cached, EG in a local var outside a long-running loop, or used to set something up. The former case can easily be fixed by checking the option direct from CONF each time around the loop. The latter case requires the use of a mutation hook, registered by CONF.register_mutate_hook, which repeats the setup. Examples:<br />
<br />
* https://review.openstack.org/#/c/319203 - check CONF in the loop<br />
* https://review.openstack.org/#/c/254821 - use a mutation hook to redo setup<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=126515ConfigOptionsConsistency2016-06-09T10:44:28Z<p>John Garbutt: /* check_opt_group_and_type */</p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If it stand solely on its own, use "None"<br />
<br />
""") <br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be part of an option group, such as a libvirt specific option that is in the default group, we should move that option into the group, using the deprecated group and name as required.<br />
<br />
In a similar way we should look at the mutable=true flag, which says its safe to reload the configuration value when the service is sent a SIG_HUP.<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=ConfigOptionsConsistency&diff=126394ConfigOptionsConsistency2016-06-07T10:37:58Z<p>John Garbutt: Updated a few of the empty sections</p>
<hr />
<div>== Maintaining consistency for Config options ==<br />
<br />
This page explains the set of tasks we need to do to ensure the consistency for centralizing config options. Every file in nova/conf starts<br />
with the following comments at the top:<br />
<br />
# needs:fix_opt_description<br />
# needs:check_deprecation_status<br />
# needs:check_opt_group_and_type<br />
# needs:fix_opt_description_indentation<br />
# needs:fix_opt_registration_consistency<br />
<br />
For review purposes, you should ideally submit 1 review per step per file.<br />
<br />
=== fix_opt_description ===<br />
<br />
'''"Services which consume this"''' section should be dropped from the opt description<br />
since this is going to be hard to maintain, and hard to review check.<br />
<br />
Below template should be followed for opt description.<br />
<br />
help="""#A short description what it does. If it is a unit (e.g. timeout) <br />
# describe the unit which is used (seconds, megabyte, mebibyte, ...)<br />
<br />
# A long description what the impact and scope is. The operators should<br />
# know the expected change in the behavior of Nova if they tweak this.<br />
<br />
Possible values:<br />
<br />
# description of possible values. Especially if this is an option<br />
# with numeric values (int, float), describe the edge cases (like the<br />
# min value, max value, 0, -1).<br />
<br />
Related options:<br />
<br />
# Which other config options have to be considered when I change this<br />
# one? If it stand solely on its own, use "None"<br />
<br />
""") <br />
<br />
=== check_deprecation_status ===<br />
<br />
For options that are already deprecated, check if we are ready to remove them (at least one cycle, and at least three months of deprecation).<br />
<br />
We need to look for configuration options that should be deprecated. For example, things that allow the loading of arbitry driver code should be moved to stevedoor extensions. Some configuration variables may be no longer used, and should be removed.<br />
<br />
=== check_opt_group_and_type ===<br />
<br />
If an option should really be part of an option group, such as a libvirt specific option that is in the default group, we should move that option into the group, using the deprecated group and name as required.<br />
<br />
=== fix_opt_description_indentation ===<br />
<br />
Positive Example: Check enabled_opt in https://github.com/openstack/nova/blob/master/nova/conf/serial_console.py for opt description indentation.<br />
<br />
Note: * should be to iterate items after a headline.<br />
<br />
The best way to check the indentation is to look at the generated sample configuration file, and check it renders correctly, i.e. without any excessive indentation.<br />
<br />
=== fix_opt_registration_consistency ===<br />
<br />
* '''Multiple options should be grouped into lists, not every option named.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/availability_zone.py. <br />
<br />
* '''One register_opts call per group, to match list_opts.'''<br />
<br />
Example: https://review.openstack.org/#/c/321470/1/nova/conf/api.py<br />
<br />
* '''ALL_OPTS created by composing lots of lists.'''<br />
<br />
Lists should be concatenated using using + for consistency. Some config files use list(itertools.chain to concatenate lists. This should be changed.<br />
<br />
Example: Check ALL_OPTS in https://github.com/openstack/nova/blob/master/nova/conf/api.py <br />
<br />
* '''Using string keys in list_opts until the oslo bug is fixed.'''<br />
<br />
String keys for groups should be used in list_opts().<br />
<br />
Example: https://github.com/openstack/nova/blob/master/nova/conf/neutron.py<br />
<br />
NEUTRON_GROUP = 'neutron'<br />
def list_opts():<br />
return {<br />
neutron_group: ALL_OPTS + _gen_opts_from_plugins()<br />
}<br />
<br />
This should be changed to:<br />
<br />
def list_opts():<br />
return {<br />
"neutron": ALL_OPTS + _gen_opts_from_plugins()<br />
}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=125910CrossProjectLiaisons2016-05-26T08:25:16Z<p>John Garbutt: /* Documentation */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Lin Tan || lintan<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachyshka<br />
|-<br />
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Huichun Lu, Ethan Gafford || huichun, egafford<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Flavio Percoco || nikhil<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Magnum || Hongbin lu || hongbin<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || David Stanek || dstanek<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs <br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Randall Burt || randallburt<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Dustin Schoenbrun || dustins<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Edgar Magana || emagana <br />
|-<br />
| Nova || Michael Still and Sean Dague (api-ref and api-guide) || mikal and sdague<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || || <br />
|-<br />
| Sahara || Chad Roberts, Michael Ionkin || crobertsrh mionkin<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || || <br />
|-<br />
| Tripleo || || <br />
|-<br />
| Trove || Laurel Michaels || laurelm<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Lin Hua Cheng || lhcheng <br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || Nikolay Starodubtsev || Nikolay_St<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || barrett1<br />
|-<br />
| Keystone || || <br />
|-<br />
| Kolla || Carol Barrett || barrett1<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manilla ||Pete Chadwick || <br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Doug Fish / Akihiro Motoki || doug-fish / amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || Tetiana Lashchova || tlashchova<br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Nikita Konovalov || NikitaKonovalov<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean M. Collins || sc68cal || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Jim Rollenhagen || jroll || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Sahara / Trove || || ||<br />
|-<br />
| || Ethan Gafford || egafford || Sahara liaison for Trove<br />
|-<br />
| || Amrith Kumar || amrith || Trove liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Hongbin Lu || hongbin<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=125909CrossProjectLiaisons2016-05-26T08:23:58Z<p>John Garbutt: /* Documentation */</p>
<hr />
<div>Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.<br />
<br />
== Oslo ==<br />
<br />
There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.<br />
<br />
* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.<br />
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.<br />
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.<br />
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || Julien Danjou || jd__<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Saad Zaher || szaher<br />
|-<br />
| Glance || Flavio Percoco || flaper87<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Ironic || Lin Tan || lintan<br />
|-<br />
| Keystone || Brant Knudson || bknudson<br />
|-<br />
| Manila || Thomas Bechtold || toabctl<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachyshka<br />
|-<br />
| Nova || ChangBo Guo <glongwave@gmail.com> || gcb<br />
|-<br />
| [[Octavia]] || Michael Johnson || johnsom<br />
|-<br />
| Sahara || Huichun Lu, Ethan Gafford || huichun, egafford<br />
|-<br />
| Senlin || Yanyan Hu || Yanyanhu<br />
|-<br />
<br />
| Swift || || <br />
|-<br />
| TripleO || Ben Nemec || bnemec<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Flavio Percoco || flaper87<br />
|-<br />
|}<br />
<br />
== Release management ==<br />
<br />
The Release Management Liaison is responsible for communication with the Release Management team, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. That task has been [[PTL_Guide#Interactions_with_the_Release_team|traditionally filled by the PTL]], but they may now delegate this task if they wish.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Release Management Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot<br />
|-<br />
| Ceilometer || gordon chung || gordc<br />
|-<br />
| Cinder || Sean McGinnis || smcginnis<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Glance || Flavio Percoco || nikhil<br />
|-<br />
| Heat || Thomas Herve || therve<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Steve Martinelli || stevemar<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Magnum || Hongbin lu || hongbin<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Lingxian Kong || kong<br />
|-<br />
| Murano ||Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Sylvain Bauza || bauzas<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== QA ==<br />
<br />
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.<br />
<br />
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Steve Heyman || hockeynut <br />
|-<br />
| Ceilometer || Chris Dent || cdent<br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Steve Baker || stevebaker<br />
|-<br />
| Horizon || Timur Sufiev || tsufiev<br />
|-<br />
| Ironic || John Villalovos || jlvillal<br />
|-<br />
| Keystone || David Stanek || dstanek<br />
|-<br />
| Manila || Valeriy Ponomaryov || vponomaryov<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Matt Riedemann || mriedem<br />
|-<br />
| Oslo || Davanum Srinivas || dims <br />
|-<br />
| Sahara || Luigi Toscano || tosky<br />
|-<br />
| Senlin || Haiwei Xu || haiwei-xu<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|}<br />
<br />
== Documentation ==<br />
<br />
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal || redrobot <br />
|-<br />
| Ceilometer || Ildiko Vancsa || ildikov<br />
|-<br />
| Cinder || Sean Mcginnis || smcginnis <br />
|-<br />
| Congress || Tim Hinrichs || thinrichs <br />
|-<br />
| Designate || || <br />
|-<br />
| Freezer || Guillermo Garcia || m3mo<br />
|-<br />
| Glance || Brian Rosmaita || rosmaita<br />
|-<br />
| Heat || Randall Burt || randallburt<br />
|-<br />
| Horizon || Rob Cresswell || robcresswell<br />
|-<br />
| I18n || KATO Tomoyuki || katomo<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || Lance Bragstad || lbragstad<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Magnum || Spyros Trigazis || strigazi<br />
|-<br />
| Manila || Dustin Schoenbrun || dustins<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || || <br />
|-<br />
| Neutron || Edgar Magana || emagana <br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Rally || || <br />
|-<br />
| Sahara || Chad Roberts, Michael Ionkin || crobertsrh mionkin<br />
|-<br />
| Senlin || Cindia Blue || lixinhui<br />
|-<br />
| Swift || || <br />
|-<br />
| Tripleo || || <br />
|-<br />
| Trove || Laurel Michaels || laurelm<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|}<br />
<br />
== Stable Branch ==<br />
<br />
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports<br />
are reviewed. They are also the contact point for stable branch release managers around point release times.<br />
<br />
* By default, the liaison will be the PTL.<br />
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.<br />
* The liaison may further delegate work to other subject matter experts<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer || Eoghan Glynn || eglynn<br />
|-<br />
| Cinder || Jay Bryant || jungleboyj<br />
|-<br />
| Congress || Masahito Muroi || masahito<br />
|-<br />
| Freezer || Pierre Mathieu || slashme<br />
|-<br />
| Heat || Zane Bitter || zaneb<br />
|-<br />
| Horizon || Matthias Runge || mrunge <br />
|-<br />
| Ironic || Dmitry Tantsur || dtantsur <br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Ihar Hrachyshka || ihrachys<br />
|-<br />
| Nova || Matt Riedemann || mriedem <br />
|-<br />
| Sahara || Vitaly Gridnev || vgridnev <br />
|-<br />
| Senlin|| Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
|-<br />
|}<br />
<br />
== Vulnerability management ==<br />
<br />
The [[Vulnerability Management]] Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [[Vulnerability Management]] process and embargo rules, and have a good grasp of security issues in software design.<br />
<br />
* The liaison should be a core reviewer for the project, but does not need to be the PTL.<br />
* By default, the liaison will be the PTL.<br />
* The liaison is the first line of contact for the Vulnerability Management team members<br />
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL<br />
* The liaison may further delegate work to other subject matter experts<br />
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill<br />
|-<br />
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc <br />
|-<br />
| Cinder || || <br />
|-<br />
| Congress || Masahito Muroi || masahito <br />
|-<br />
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br />
|-<br />
| Heat || Steve Hardy || shardy<br />
|-<br />
| Horizon || Lin Hua Cheng || lhcheng <br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Dolph Mathews || dolphm<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Neutron || Salvatore Orlando || salv-orlando<br />
|-<br />
| Nova || Michael Still || mikal<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || || <br />
|-<br />
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik <br />
|-<br />
| Zaqar || Fei Long Wang || flwang <br />
|-<br />
|}<br />
<br />
== API Working Group ==<br />
<br />
The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.<br />
<br />
The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.<br />
<br />
== Logging Working Group ==<br />
<br />
The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Erno Kuvaja || jokke_<br />
|-<br />
| Oslo || Doug Hellmann || dhellmann<br />
|-<br />
| Nova || John Garbutt || johnthetubaguy<br />
|-<br />
| Murano || Nikolay Starodubtsev || Nikolay_St<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|}<br />
<br />
== Infra ==<br />
<br />
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Glance || Flavio Percoco, Nikhil Komawar|| flaper87, nikhil<br />
|-<br />
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || pbourke, sdake are primary contacts<br />
|-<br />
| Neutron || Kyle Mestery, Armando Migliaccio, Doug Wiegley|| mestery, armax, dougwig<br />
|-<br />
| Documentation || Andreas Jaeger|| AJaeger<br />
<br />
|-<br />
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik<br />
<br />
|-<br />
| Murano || Victor Ryzhenkin || freerunner<br />
<br />
|-<br />
| Sahara || Sergey Lukjanov || SergeyLukjanov<br />
<br />
|-<br />
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br />
<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|}<br />
<br />
== Product Working Group ==<br />
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies. <br />
<br />
More information about the team can be found on the [[ProductTeam|Product WG wiki]].<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Ceilometer ||Krish Ragurham || <br />
|-<br />
| Cinder || Shamail Tahir || shamail<br />
|-<br />
| Glance || Nate Ziemann || nate_zman<br />
|-<br />
| Horizon || Carol Barrett || barrett1<br />
|-<br />
| Keystone || || <br />
|-<br />
| Kolla || Carol Barrett || barrett1<br />
|-<br />
| Magnum || Steve Gordon || sgordon<br />
|-<br />
| Manilla ||Pete Chadwick || <br />
|-<br />
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7<br />
|-<br />
| Nova || Hugh Blemings || hughhalf <br />
|-<br />
| OSClient || Megan Rossetti || MeganR<br />
|-<br />
| Stable Release|| Rochelle Grober || rockig<br />
|-<br />
| Sahara || Ethan Gafford || egafford<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Swift || Phil Williams || philipw<br />
|-<br />
| Tempest || Arkady Kanevsky || arkady_kanevsky<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
|}<br />
<br />
== I18n ==<br />
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages. <br />
<br />
If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.<br />
<br />
* The liaison should be a core reviewer for the project and understand i18n status of the project.<br />
* The liaison should understand project release schedule very well.<br />
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.<br />
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara || || <br />
|-<br />
| Barbican || || <br />
|-<br />
| Cinder || || <br />
|-<br />
| Designate || Graham Hayes || mugsie<br />
|-<br />
| Glance || || <br />
|-<br />
| Heat || || <br />
|-<br />
| Horizon || Doug Fish / Akihiro Motoki || doug-fish / amotoki<br />
|-<br />
| Ironic || || <br />
|-<br />
| Keystone || || <br />
|-<br />
| Magnum || Shu Muto || shu-mutou<br />
|-<br />
| Manila || || <br />
|-<br />
| Monasca || || <br />
|-<br />
| Murano || Tetiana Lashchova || tlashchova<br />
|-<br />
| Neutron || Akihiro Motoki || amotoki<br />
|-<br />
| Nova || Augustina Ragwitz || auggy <br />
|-<br />
| Oslo || || <br />
|-<br />
| Sahara || Nikita Konovalov || NikitaKonovalov<br />
|-<br />
| Senlin || || <br />
|-<br />
| Swift || ||<br />
|-<br />
| Tacker || || <br />
|-<br />
| Telemetry || || <br />
|-<br />
| Trove || || <br />
|-<br />
| Sahara || Chad Roberts || crobertsrh <br />
|-<br />
| Zaqar || || <br />
|-<br />
|}<br />
<br />
== Inter-project Liaisons ==<br />
<br />
In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Projects !! Name !! IRC Handle !! Role<br />
|-<br />
| Nova / Neutron || || ||<br />
|-<br />
| || Sean M. Collins || sc68cal || Neutron liaison for Nova<br />
|-<br />
| Nova / Glance || || ||<br />
|-<br />
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova<br />
|-<br />
| || Jay Pipes || jaypipes || Nova liaison for Glance<br />
|-<br />
| Nova / Cinder || || ||<br />
|-<br />
| || Scott DAngelo || scottda || Cinder liaison for Nova<br />
|-<br />
| || Matt Riedemann || mriedem || Nova liason for Cinder<br />
|-<br />
| Nova / Ironic || John Villalovos || jlvillal || Ironic liaison for Nova<br />
|-<br />
| || Michael Davies || mrda || Ironic liaison for Nova<br />
|-<br />
| Neutron / Ironic || || ||<br />
|-<br />
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br />
|-<br />
| || Jim Rollenhagen || jroll || Ironic liaison for Neutron<br />
|-<br />
| Murano / Glance || || ||<br />
|-<br />
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance<br />
|-<br />
| Horizon / i18n || || ||<br />
|-<br />
| || Doug Fish || doug-fish || Horizon liaison for i18n<br />
|-<br />
| || TBD || || Heat liaison for Sahara<br />
|-<br />
| Sahara / Trove || || ||<br />
|-<br />
| || Ethan Gafford || egafford || Sahara liaison for Trove<br />
|-<br />
| || Amrith Kumar || amrith || Trove liaison for Sahara<br />
|-<br />
| Fuel / Puppet || || ||<br />
|-<br />
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet<br />
|-<br />
| Fuel / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Fuel liaison for Ironic<br />
|-<br />
| Bareon / Ironic || || ||<br />
|-<br />
| || Evgeny L || evgenyl || Bareon liaison for Ironic<br />
|-<br />
| Magnum / Kuryr || || ||<br />
|-<br />
| || Ton Ngo || tango || Magnum liaison for Kuryr<br />
|}<br />
<br />
=== Etherpads ===<br />
<br />
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.<br />
<br />
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron<br />
<br />
== Cross-Project Spec Liaisons ==<br />
<br />
The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Liaison !! IRC Handle<br />
|-<br />
| Astara|| Ryan Petrello || ryanpetrello<br />
|-<br />
| Barbican || Douglas Mendizabal || redrobot<br />
|-<br />
| Cinder || Kendall Nelson || diablo_rojo<br />
|-<br />
| Congress || Tim Hinrichs || thinrichs<br />
|-<br />
| Cue || Min Pae || sputnik13<br />
|-<br />
| Designate || Graham hayes || mugsie<br />
|-<br />
| Dragonflow || Gal Sagie || gsagie<br />
|-<br />
| Freezer || Pierre Mahieu || slashme<br />
|-<br />
| Fuel || Andrew Woodward || xarses<br />
|-<br />
| Glance || Nikhil Komawar || nikhil<br />
|-<br />
| Heat || Rico Lin || ricolin<br />
|-<br />
| Horizon || David Lyle || david-lyle<br />
|-<br />
| Infrastructure || Matthew Wagoner || olaph<br />
|-<br />
| Ironic || Jim Rollenhagen || jroll<br />
|-<br />
| Keystone || Samuel de Medeiros Queiroz || samueldmq<br />
|-<br />
| Kolla || Steven Dake || sdake<br />
|-<br />
| Kuryr || Gal Sagie || gsagie<br />
|-<br />
| Magnum || Hongbin Lu || hongbin<br />
|-<br />
| Manila || Ben Swartzlander || bswartz<br />
|-<br />
| Mistral || Renat Akhmerov || rakhmerov<br />
|-<br />
| Monasca || Roland Hochmuth || rhochmuth<br />
|-<br />
| Murano || Kirill Zaitsev || kzaitsev_<br />
|-<br />
| Neutron || Armando Migliaccio || armax<br />
|-<br />
| Nova || Chris Dent || cdent<br />
|-<br />
| OpenStack-Ansible || Travis Truman || automagically<br />
|-<br />
| Oslo || Davanum Srinivas || dims<br />
|-<br />
| Puppet OpenStack || Emilien Macchi || EmilienM<br />
|-<br />
| Sahara || Michael McCune, Vitaly Gridnev || elmiko vgridnev<br />
|-<br />
| Searchlight || Travis Tripp || TravT<br />
|-<br />
| Senlin || Qiming Teng || Qiming<br />
|-<br />
| Solum || Devdatta Kulkarni || devkulkarni<br />
|-<br />
| Swift || John Dickinson || notmyname<br />
|-<br />
| Tacker || Sridhar Ramaswamy || sridhar_ram<br />
|-<br />
| Telemetry || Gordon Chung || gordc<br />
|-<br />
| Trove || Amrith Kumar || amrith<br />
|-<br />
| Watcher || Susanne Balle || sballe <br />
|-<br />
| Zaqar || Fei Long Wang || flwang<br />
<br />
|}</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Meetings/NovaAPI&diff=125378Meetings/NovaAPI2016-05-17T10:52:43Z<p>John Garbutt: /* Next Meeting */</p>
<hr />
<div>= Weekly OpenStack Nova API Meeting =<br />
<br />
This is a weekly meeting to discuss the Nova API. It's intended as a forum for:<br />
<br />
* People to keep up with what work is going on with the Nova API and where it is headed<br />
* Cloud providers, SDK maintainers and direct users of the REST API to provide feedback about the API and what they want out of it<br />
* Help coordinate ongoing development work on the API<br />
<br />
== Meetings ==<br />
<br />
* Meeting Time: Weekly, Wednesday at 13:00 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code><br />
* Chaired by: Alex Xu (alex_xu)<br />
<br />
=== Next Meeting ===<br />
Wednesday 2016/03/22 at 1300 UTC<br />
<br />
==== Agenda ====<br />
Please feel free to add items to the Agenda under Open Discussion<br />
<br />
Standing Agenda<br />
* API Priorities<br />
** API policy discovery: https://review.openstack.org/290155, https://review.openstack.org/289405, https://review.openstack.org/305026<br />
** API Ref: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:wip_api_docs2<br />
** Remove legacy v2 API https://review.openstack.org/#/q/topic:bp/remove-legacy-v2-api-code<br />
** Deprecated API Proxy https://review.openstack.org/#/c/312209/<br />
* Open Discussion<br />
** modern microversion spec and code need eyes:<br />
*** https://review.openstack.org/#/c/305800/<br />
*** https://review.openstack.org/#/c/300077/<br />
** Add support for user defined stop instance:<br />
*** previously approved https://review.openstack.org/#/c/89650/ but not actually finished.<br />
*** We contacted the author and want to do it again as we have user demands: https://review.openstack.org/#/c/293790/<br />
*** POC code already up: https://review.openstack.org/#/c/298221/<br />
** Tasks background work<br />
*** https://review.openstack.org/#/c/248248/<br />
*** might be too much to start chewing on this right away though?<br />
<br />
=== Previous Meetings (most recent first) ===<br />
* 2016: http://eavesdrop.openstack.org/meetings/nova_api/2016/<br />
* 2015: http://eavesdrop.openstack.org/meetings/nova_api/2015/<br />
* 2014: http://eavesdrop.openstack.org/meetings/nova_api/2014/</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Meetings/TechnicalCommittee&diff=123659Meetings/TechnicalCommittee2016-04-08T09:15:45Z<p>John Garbutt: /* Apologies for Absence */</p>
<hr />
<div>__NOTOC__<br />
<br />
The [[Governance/Foundation/TechnicalCommittee|OpenStack Technical Committee]] is one of the [[Governance|governing bodies]] of the OpenStack project. You can find more information about it, such as the list of its [http://governance.openstack.org current members] or its [http://governance.openstack.org/reference/charter.html governance charter], on the OpenStack governance website at http://governance.openstack.org . It meets weekly in an open meeting in the <code>#openstack-meeting</code> IRC channel on Freenode.<br />
<br />
<br />
=== Next Meeting ===<br />
<br />
* April 12th, 20:00 UTC<br />
* Chair: Thierry Carrez (ttx)<br />
<br />
<br />
==== Agenda ====<br />
(First meeting for the Newton TC membership)<br />
<br />
* Welcome Newton TC members<br />
** Update member roster [https://review.openstack.org/303119], -tc ML rights (in progress) and Gerrit rights (done)<br />
** Select chair [https://review.openstack.org/303308] (please propose alternate candidates with similar patches)<br />
** Confirmation of change approval rules & agenda buildup process<br />
** Austin reminders: Joint Board/TC meeting (Sunday 2:30pm) and Dinner with the BoD, UC, Gold Member Reps and Foundation Staff (Saturday 7pm)<br />
* Propose topics for Joint board / TC meeting agenda<br />
* Tidy of item 5 of the vulnerability:managed tag [https://review.openstack.org/300698]<br />
* Cross-project workshops at the Austin summit (sdague)<br />
* Video design summit moderator advice (ttx)<br />
* Open discussion<br />
** What would you like to achieve during the coming 6 months ?<br />
<br />
<br />
==== Backlog ====<br />
These items have been proposed, but are not put on the agenda just yet. Could be that they have not been discussed on openstack-dev for the time mandated by our charter yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:<br />
<br />
* Call out GPL style licenses in testing/validation. [https://review.openstack.org/293140] (pending an update)<br />
* type:packaging and type:deployment tags (pending iterations on the reviews)<br />
** Introduce type:deployment tag [https://review.openstack.org/295528]<br />
** Introduce a type:packaging tag [https://review.openstack.org/295971]<br />
** Modify asserts for upgrades to include deployment [https://review.openstack.org/295529]<br />
** Add type:deployment to release:cycle_with_miestones [https://review.openstack.org/298278]<br />
<br />
<br />
==== Apologies for Absence ====<br />
<br />
* dhellmann 5 Apr and 12 Apr<br />
* johnthetubaguy 12 Apr<br />
<br />
=== Proposing discussion topics, motions or other governance changes before the TC ===<br />
<br />
Motions need to be presented before Friday 0800 UTC to be added to the next Tuesday meeting agenda for discussion. They should either be posted as a proposed change to the [http://git.openstack.org/cgit/openstack/governance/ governance] repository (on review.openstack.org) or as a "[tc]" thread to openstack-dev@lists.openstack.org, with a pointer to that thread should be posted to openstack-tc@lists.openstack.org to make sure it gets the required attention from TC members. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.<br />
<br />
Before being finally voted on, motions will have to be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change. As mandated by our charter, the vote on motions won't be closed until we spent a minimum of 4 business days of public discussions, to give a chance to our wider community to chime in on proposed changes.<br />
<br />
Additions of code repositories to existing project teams, as well as other instances of governance repository housekeeping, do not constitute a "motion". Those will be approved a week after being proposed, if they have the required approvals (PTLs in the case of a repository addition) and no TC member -1 vote. A -1 vote will result in the proposed change to be reviewed at the next TC meeting.<br />
<br />
<br />
=== Past meetings logs ===<br />
<br />
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc<br />
<br />
[[Category: meetings]]</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Meetings/Nova&diff=122478Meetings/Nova2016-03-17T15:22:39Z<p>John Garbutt: /* Agenda for next meeting */</p>
<hr />
<div><br />
= Weekly Nova team meeting =<br />
'''MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-meeting)'''<br />
<br />
This meeting is a weekly gathering of developers working on [[Nova|OpenStack Compute (Nova)]]. We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.<br />
<br />
NOTE: this wiki page should be 'emptied' at the end of each meeting.<br />
<br />
== Agenda for next meeting ==<br />
<br />
Next meetings scheduled for:<br />
* March 17th 2016 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160317T210000)<br />
* March 24th 2016 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160324T140000)<br />
<br />
Add your IRC nick to this list to be pinged at the start of the meeting:<br />
<code><br />
<br>adrian_otto akuriata alevine alexpilotti aloga andreykurilin anteaya artom auggy<br />
<br>bauzas belliott belmoreira bobball cburgess claudiub danpb dguitarbite _diana_<br />
<br>diana_clarke dims duncant edleafe efried flip214 funzo garyk gcb gjayavelu<br />
<br>irina_pov jaypipes jcookekhugen jgrimm jichen jlvillal jroll kashyap klindgren<br />
<br>krtaylor lbeliveau lxsli macsz markus_z mdorman med_ mikal mjturek mnestratov<br />
<br>moshele mrda nagyz ndipanov neiljerram nic Nisha PaulMurray raildo rgeragnov<br />
<br>sc68cal scottda sdague sileht sorrison swamireddy thomasem thorst tjones tonyb<br />
<br>tpatil tpatzig xyang rdopiera<br />
</code><br />
<br />
Please note "stuck review" means a review where there is some disagreement that needs resolving.<br />
Its not for reviews that just haven't had attention, except for exceptional cases.<br />
Where you see "?" feel free to just edit the wiki and add your item.<br />
<br />
Here is the agenda for the next meeting:<br />
* Release Status<br />
** RC1 released, Hard String Freeze, open master for Newton<br />
*** http://lists.openstack.org/pipermail/openstack-dev/2016-March/089554.html<br />
** Apr 4-8, Release week<br />
*** http://docs.openstack.org/releases/schedules/mitaka.html<br />
** Looking out for release critical bugs, potential release blocker: https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential<br />
** New review focus list: https://etherpad.openstack.org/p/newton-nova-priorities-tracking<br />
* Bugs (stuck/critical)<br />
** Gate status<br />
*** http://status.openstack.org/elastic-recheck/index.html<br />
** 3rd party CI status<br />
*** http://ci-watch.tintri.com/project?project=nova&time=7+days<br />
** Critical bugs<br />
*** ?<br />
** Reminders:<br />
*** http://lists.openstack.org/pipermail/openstack-dev/2016-March/088205.html Looking out for release critical bugs, use mitaka-rc-potential, if agreed target at milestone, usually high priority or higher<br />
*** https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty Volunteers for 1 week of bug skimming duty?<br />
** Stable branch status: https://etherpad.openstack.org/p/stable-tracker<br />
*** stable/liberty: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/liberty,n,z<br />
*** stable/kilo: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo,n,z<br />
* Stuck Reviews<br />
** Please note "stuck review" means a review where there is some disagreement that needs resolving. Its not for reviews that just haven't had attention, except for exceptional cases. Where you see "?" feel free to just edit the wiki and add your item.<br />
** Any stuck code reviews to discuss:<br />
*** ?<br />
* Open discussion<br />
** Austin Design Summit ideas: https://etherpad.openstack.org/p/newton-nova-summit-ideas<br />
** ?<br />
<br />
== Sub-teams ==<br />
<br />
There are also some Nova subteam meetings. See [[Nova#Active_Sub-teams:]] for details.<br />
<br />
== Previous meetings ==<br />
<br />
* [http://eavesdrop.openstack.org/meetings/nova/ All other meetings are here]<br />
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-21.01.html 2012-08-16]<br />
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-21.00.html 2012-08-09]<br />
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-21.40.html 2012-08-02]<br />
<br />
[[category: compute]]<br />
[[category: meetings]]</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=Meetings/Nova&diff=122175Meetings/Nova2016-03-14T14:43:35Z<p>John Garbutt: /* Agenda for next meeting */</p>
<hr />
<div><br />
= Weekly Nova team meeting =<br />
'''MEETING TIME: Thursdays alternating 14:00 UTC (#openstack-meeting) and 21:00 UTC (#openstack-meeting)'''<br />
<br />
This meeting is a weekly gathering of developers working on [[Nova|OpenStack Compute (Nova)]]. We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.<br />
<br />
NOTE: this wiki page should be 'emptied' at the end of each meeting.<br />
<br />
== Agenda for next meeting ==<br />
<br />
Next meetings scheduled for:<br />
* March 17th 2016 2100 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160317T210000)<br />
* March 24th 2016 1400 UTC, #openstack-meeting (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160324T140000)<br />
<br />
Add your IRC nick to this list to be pinged at the start of the meeting:<br />
<code><br />
<br>adrian_otto akuriata alevine alexpilotti aloga andreykurilin anteaya artom auggy<br />
<br>bauzas belliott belmoreira bobball cburgess claudiub danpb dguitarbite _diana_<br />
<br>diana_clarke dims duncant edleafe efried flip214 funzo garyk gcb gjayavelu<br />
<br>irina_pov jaypipes jcookekhugen jgrimm jichen jlvillal jroll kashyap klindgren<br />
<br>krtaylor lbeliveau lxsli macsz markus_z mdorman med_ mikal mjturek mnestratov<br />
<br>moshele mrda nagyz ndipanov neiljerram nic Nisha PaulMurray raildo rgeragnov<br />
<br>sc68cal scottda sdague sileht sorrison swamireddy thomasem thorst tjones tonyb<br />
<br>tpatil tpatzig xyang rdopiera<br />
</code><br />
<br />
Please note "stuck review" means a review where there is some disagreement that needs resolving.<br />
Its not for reviews that just haven't had attention, except for exceptional cases.<br />
Where you see "?" feel free to just edit the wiki and add your item.<br />
<br />
Here is the agenda for the next meeting:<br />
* Release Status<br />
** Mar 14-18, RC1 target week, Hard String Freeze, open master for Newton<br />
** Apr 4-8, Release week<br />
*** http://docs.openstack.org/releases/schedules/mitaka.html<br />
** Looking out for release critical bugs, potential release blocker: https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential<br />
** Review focus list: https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking<br />
*** new section "Mitaka-RC blockers" has a gerrit query for mitaka blocker patches<br />
* Bugs (stuck/critical)<br />
** Gate status<br />
*** http://status.openstack.org/elastic-recheck/index.html<br />
** 3rd party CI status<br />
*** http://ci-watch.tintri.com/project?project=nova&time=7+days<br />
** Critical bugs<br />
*** ?<br />
** Reminders:<br />
*** http://lists.openstack.org/pipermail/openstack-dev/2016-March/088205.html Looking out for release critical bugs, use mitaka-rc-potential, if agreed target at milestone, usually high priority or higher<br />
*** https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty Volunteers for 1 week of bug skimming duty?<br />
** Stable branch status: https://etherpad.openstack.org/p/stable-tracker<br />
*** stable/liberty: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/liberty,n,z<br />
*** stable/kilo: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo,n,z<br />
* Stuck Reviews<br />
** Please note "stuck review" means a review where there is some disagreement that needs resolving. Its not for reviews that just haven't had attention, except for exceptional cases. Where you see "?" feel free to just edit the wiki and add your item.<br />
** Any stuck code reviews to discuss:<br />
*** ?<br />
* Open discussion<br />
** Austin Design Summit ideas: https://etherpad.openstack.org/p/newton-nova-summit-ideas<br />
** ?<br />
<br />
== Sub-teams ==<br />
<br />
There are also some Nova subteam meetings. See [[Nova#Active_Sub-teams:]] for details.<br />
<br />
== Previous meetings ==<br />
<br />
* [http://eavesdrop.openstack.org/meetings/nova/ All other meetings are here]<br />
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-21.01.html 2012-08-16]<br />
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-21.00.html 2012-08-09]<br />
* [http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-21.40.html 2012-08-02]<br />
<br />
[[category: compute]]<br />
[[category: meetings]]</div>John Garbutthttps://wiki.openstack.org/w/index.php?title=StringFreeze&diff=121761StringFreeze2016-03-07T15:24:24Z<p>John Garbutt: /* Exception procedure */</p>
<hr />
<div>=== (Soft) String Freeze ===<br />
<br />
String Freeze usually happens at the same time as Feature Freeze.<br />
<br />
Once SF kicks in, you are no longer allowed to accept proposed changes containing modifications in user-facing strings. Such changes should be rejected by the review team and postponed until the next series development opens (which should happen when RC1 is published).<br />
<br />
What's OK:<br />
* Adding log messages<br />
* Adding a missing description to a config option<br />
* Translation team may update strings if they find string mistakes or translation issues<br />
<br />
<br />
What's not OK:<br />
* Adding or Changing user-visible API error messages, unless really needed<br />
* Changing existing strings, unless really needed<br />
** For example: log messages, config option name or existing description<br />
** Please note, there can also be a doc impact from some of the above changes, which should be avoided if possible<br />
<br />
=== Hard String Freeze ===<br />
<br />
This happens usually when RC1 is tagged.<br />
<br />
At this point, ideally no strings are changed, to give translator time to finish up their efforts. Ideally at least 10 working days later, another release will be made to include all the extra translated strings since the hard Freeze.<br />
<br />
=== Rationale ===<br />
<br />
SF ensures that the documentation and translation teams have a relatively-stable universe to produce documentation and translations for.<br />
<br />
Its annoying to update a string just after its been translated. Adding an extra string to translate is less frustrating for them.<br />
<br />
For log messages, its better to have an untranslated log message, rather than a hidden error condition.<br />
<br />
=== Hard Freeze Exception procedure ===<br />
<br />
If you want to propose a change containing a user-facing string modification (that you believe fixes an important issue) for merging into the release under development after SF, follow those steps:<br />
<br />
* Mention the need for a string freeze exception on the review<br />
* Provide links to appropriate bugs<br />
* Raise a thread to discuss the proposed change on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n openstack-i18n mailing-list]<br />
* Lazy consensus should be preferred, but the affected project PTLs has final say on what's acceptable or not.<br />
<br />
<br />
[[Category: ContribDocs]]</div>John Garbutt