https://wiki.openstack.org/w/api.php?action=feedcontributions&feedformat=atom&user=Yamamoto 2026-06-29T14:45:24Z User contributions MediaWiki 1.28.2 https://wiki.openstack.org/w/index.php?title=Meetings/NeutronDrivers&diff=159182 2018-01-25T11:59:29Z

<p>Yamamoto: /* Agenda */</p> <hr /> <div>The Neutron Drivers Team ([[Neutron Drivers]]) holds public meetings as advertised on [http://eavesdrop.openstack.org/#Neutron_drivers_Meeting OpenStack IRC Meetings Calendar]. If you are unable to attend, please check the most recent [http://eavesdrop.openstack.org/meetings/neutron_drivers/ logs.]<br /> <br /> == Agenda ==<br /> * Ongoing discussions:<br /> ** [https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe-triaged Triaged RFE's]<br /> * To be vetted for discussion:<br /> ** [https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe-confirmed Confirmed RFE's]<br /> * To be screened:<br /> ** [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&amp;field.tag=rfe New RFE's]<br /> * Approved RFE's:<br /> ** [https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe-approved Approved RFE's]<br /> ** [https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z Pending Specs]<br /> ** [https://review.openstack.org/#/q/status:merged+project:openstack/neutron-specs,n,z Merged Specs]<br /> * Other RFE's:<br /> ** [https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe-postponed Postponed RFE's]<br /> ** [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=WONTFIX&amp;field.tag=rfe Rejected RFE's]<br /> ** [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=EXPIRED&amp;field.tag=rfe Expired RFE's]<br /> ** [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=EXPIRED&amp;field.tag=rfe-approved Expired/Approved RFE's]<br /> <br /> == Previous meeting logs ==<br /> * Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/neutron_drivers/ here].</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=155851 2017-08-09T00:47:19Z

<p>Yamamoto: /* Agenda (2017-8-9) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap%2Das%2Da%2Dservice+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap%2Das%2Da%2Dservice%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode%2DReview%3E%3D%2D2%2Cself&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d+branch%3Amaster&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself+branch%3Amaster&amp;Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d+branch%3Amaster&amp;stable%2Focata=branch%3Astable%2Focata&amp;stable%2Fnewton=branch%3Astable%2Fnewton&amp;other+branches=NOT+branch%3Amaster+AND+NOT+branch%3Astable%2Focata+AND+NOT+branch%3Astable%2Fnewton TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> Initial Spec for Stadium report is up :https://review.openstack.org/#/c/454788/<br /> <br /> <br /> === Project Teams Gathering ===<br /> * Denver, CO, USA (Sep., 11-15, 2017)<br /> <br /> <br /> === OpenStack Summit Sydney 2017 ===<br /> * Call for Presentations for OpenStack Summit Sydney: '''Submission deadline: 14th July 2017'''<br /> <br /> == Agenda (2017-8-9) ==<br /> * Pike release<br /> ** (yamamoto) Unless anyone objects, I'll make a release as it is.<br /> ** An open question: Do we want a RC?<br /> * Dashboard<br /> ** (yamamoto) I tried the dashboard. It worked well after fixing a few small things.<br /> ** An open question: Is it ready for pike release?<br /> ** LP bug seems unconfigured. https://bugs.launchpad.net/tap-as-a-service/+bug/1708116<br /> * Review reminder<br /> ** https://review.openstack.org/#/c/349176/ This involves DB changes, thus not backportable. If we want it in Pike, review it right now.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-21) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-14) ==<br /> * (yamamoto) I updated &quot;TaaS Review Inbox&quot; link on the wiki. Please let me know if it has any problem.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-7) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-31) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-17) ==<br /> * Feedback from OpenStack Summit Boston<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-10) ==<br /> * '''Canceled''' (week of OpenStack Summit Boston)<br /> <br /> == Agenda (2017-5-3) ==<br /> * '''Canceled''' (national holiday in Japan)<br /> <br /> == Agenda (2017-4-26) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-19) ==<br /> * Horizon dashboard for neutron stadium projects<br /> ** http://lists.openstack.org/pipermail/openstack-dev/2017-April/115590.html<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-12) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-5) ==<br /> * Open Discussion<br /> <br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/<br /> <br /> == Important Links ==<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> *http://backreference.org/2014/06/17/port-mirroring-with-linux-bridges/<br /> * Slideshare slides<br /> ** https://www.slideshare.net/soichishigeta/designof-traffic-isolationby-using-flow-based-tunneling<br /> ** https://www.slideshare.net/soichishigeta/cannot-observe-ingress-packets<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-the-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-increasing-send-packets</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=155829 2017-08-08T00:52:00Z

<p>Yamamoto: /* Agenda (2017-8-9) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap%2Das%2Da%2Dservice+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap%2Das%2Da%2Dservice%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode%2DReview%3E%3D%2D2%2Cself&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d+branch%3Amaster&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself+branch%3Amaster&amp;Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d+branch%3Amaster&amp;stable%2Focata=branch%3Astable%2Focata&amp;stable%2Fnewton=branch%3Astable%2Fnewton&amp;other+branches=NOT+branch%3Amaster+AND+NOT+branch%3Astable%2Focata+AND+NOT+branch%3Astable%2Fnewton TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> Initial Spec for Stadium report is up :https://review.openstack.org/#/c/454788/<br /> <br /> <br /> === Project Teams Gathering ===<br /> * Denver, CO, USA (Sep., 11-15, 2017)<br /> <br /> <br /> === OpenStack Summit Sydney 2017 ===<br /> * Call for Presentations for OpenStack Summit Sydney: '''Submission deadline: 14th July 2017'''<br /> <br /> == Agenda (2017-8-9) ==<br /> * Pike release<br /> ** (yamamoto) Unless anyone objects, I'll make a release as it is.<br /> ** An open question: Do we want a RC?<br /> * Dashboard<br /> ** (yamamoto) I tried the dashboard. It worked well after fixing a few small things.<br /> ** An open question: Is it ready for pike release?<br /> * Review reminder<br /> ** https://review.openstack.org/#/c/349176/ This involves DB changes, thus not backportable. If we want it in Pike, review it right now.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-21) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-14) ==<br /> * (yamamoto) I updated &quot;TaaS Review Inbox&quot; link on the wiki. Please let me know if it has any problem.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-7) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-31) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-17) ==<br /> * Feedback from OpenStack Summit Boston<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-10) ==<br /> * '''Canceled''' (week of OpenStack Summit Boston)<br /> <br /> == Agenda (2017-5-3) ==<br /> * '''Canceled''' (national holiday in Japan)<br /> <br /> == Agenda (2017-4-26) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-19) ==<br /> * Horizon dashboard for neutron stadium projects<br /> ** http://lists.openstack.org/pipermail/openstack-dev/2017-April/115590.html<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-12) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-5) ==<br /> * Open Discussion<br /> <br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/<br /> <br /> == Important Links ==<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> *http://backreference.org/2014/06/17/port-mirroring-with-linux-bridges/<br /> * Slideshare slides<br /> ** https://www.slideshare.net/soichishigeta/designof-traffic-isolationby-using-flow-based-tunneling<br /> ** https://www.slideshare.net/soichishigeta/cannot-observe-ingress-packets<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-the-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-increasing-send-packets</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=155827 2017-08-07T23:49:45Z

<p>Yamamoto: /* Agenda (2017-8-9) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap%2Das%2Da%2Dservice+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap%2Das%2Da%2Dservice%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode%2DReview%3E%3D%2D2%2Cself&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d+branch%3Amaster&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself+branch%3Amaster&amp;Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d+branch%3Amaster&amp;stable%2Focata=branch%3Astable%2Focata&amp;stable%2Fnewton=branch%3Astable%2Fnewton&amp;other+branches=NOT+branch%3Amaster+AND+NOT+branch%3Astable%2Focata+AND+NOT+branch%3Astable%2Fnewton TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> Initial Spec for Stadium report is up :https://review.openstack.org/#/c/454788/<br /> <br /> <br /> === Project Teams Gathering ===<br /> * Denver, CO, USA (Sep., 11-15, 2017)<br /> <br /> <br /> === OpenStack Summit Sydney 2017 ===<br /> * Call for Presentations for OpenStack Summit Sydney: '''Submission deadline: 14th July 2017'''<br /> <br /> == Agenda (2017-8-9) ==<br /> * Pike release<br /> ** (yamamoto) Unless anyone objects, I'll make a release as it is.<br /> * Dashboard<br /> ** (yamamoto) I tried the dashboard. It worked well after fixing a few small things.<br /> ** An open question: Is it ready for pike release?<br /> * Review reminder<br /> ** https://review.openstack.org/#/c/349176/ This involves DB changes, thus not backportable. If we want it in Pike, review it right now.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-21) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-14) ==<br /> * (yamamoto) I updated &quot;TaaS Review Inbox&quot; link on the wiki. Please let me know if it has any problem.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-7) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-31) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-17) ==<br /> * Feedback from OpenStack Summit Boston<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-10) ==<br /> * '''Canceled''' (week of OpenStack Summit Boston)<br /> <br /> == Agenda (2017-5-3) ==<br /> * '''Canceled''' (national holiday in Japan)<br /> <br /> == Agenda (2017-4-26) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-19) ==<br /> * Horizon dashboard for neutron stadium projects<br /> ** http://lists.openstack.org/pipermail/openstack-dev/2017-April/115590.html<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-12) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-5) ==<br /> * Open Discussion<br /> <br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/<br /> <br /> == Important Links ==<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> *http://backreference.org/2014/06/17/port-mirroring-with-linux-bridges/<br /> * Slideshare slides<br /> ** https://www.slideshare.net/soichishigeta/designof-traffic-isolationby-using-flow-based-tunneling<br /> ** https://www.slideshare.net/soichishigeta/cannot-observe-ingress-packets<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-the-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-increasing-send-packets</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=155826 2017-08-07T23:49:17Z

<p>Yamamoto: /* Agenda (2017-8-9) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap%2Das%2Da%2Dservice+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap%2Das%2Da%2Dservice%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode%2DReview%3E%3D%2D2%2Cself&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d+branch%3Amaster&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself+branch%3Amaster&amp;Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d+branch%3Amaster&amp;stable%2Focata=branch%3Astable%2Focata&amp;stable%2Fnewton=branch%3Astable%2Fnewton&amp;other+branches=NOT+branch%3Amaster+AND+NOT+branch%3Astable%2Focata+AND+NOT+branch%3Astable%2Fnewton TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> Initial Spec for Stadium report is up :https://review.openstack.org/#/c/454788/<br /> <br /> <br /> === Project Teams Gathering ===<br /> * Denver, CO, USA (Sep., 11-15, 2017)<br /> <br /> <br /> === OpenStack Summit Sydney 2017 ===<br /> * Call for Presentations for OpenStack Summit Sydney: '''Submission deadline: 14th July 2017'''<br /> <br /> == Agenda (2017-8-9) ==<br /> * Pike release<br /> ** (yamamoto) Unless anyone objects, I'll make a release as it is.<br /> ** An open question: Is the dashboard ready for a release?<br /> * Dashboard<br /> ** (yamamoto) I tried the dashboard. It worked well after fixing a few small things.<br /> * Review reminder<br /> ** https://review.openstack.org/#/c/349176/ This involves DB changes, thus not backportable. If we want it in Pike, review it right now.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-21) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-14) ==<br /> * (yamamoto) I updated &quot;TaaS Review Inbox&quot; link on the wiki. Please let me know if it has any problem.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-7) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-31) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-17) ==<br /> * Feedback from OpenStack Summit Boston<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-10) ==<br /> * '''Canceled''' (week of OpenStack Summit Boston)<br /> <br /> == Agenda (2017-5-3) ==<br /> * '''Canceled''' (national holiday in Japan)<br /> <br /> == Agenda (2017-4-26) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-19) ==<br /> * Horizon dashboard for neutron stadium projects<br /> ** http://lists.openstack.org/pipermail/openstack-dev/2017-April/115590.html<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-12) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-5) ==<br /> * Open Discussion<br /> <br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/<br /> <br /> == Important Links ==<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> *http://backreference.org/2014/06/17/port-mirroring-with-linux-bridges/<br /> * Slideshare slides<br /> ** https://www.slideshare.net/soichishigeta/designof-traffic-isolationby-using-flow-based-tunneling<br /> ** https://www.slideshare.net/soichishigeta/cannot-observe-ingress-packets<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-the-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-increasing-send-packets</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=155798 2017-08-07T01:39:08Z

<p>Yamamoto: /* Agenda (2017-08-08) */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |-<br /> | 2016-08-23 || || x || ||<br /> |-<br /> | 2016-09-20 || || x || ||<br /> |-<br /> | 2016-12-13 || || x || ||<br /> |}<br /> <br /> == Agenda (2017-08-08) ==<br /> * This meeting has had no useful discussions these days.<br /> * (yamamoto) I'd suggest to officially shut down this meeting. I guess on-demand discussions on IRC or slack work best.<br /> <br /> == Agenda (2016-12-13) ==<br /> <br /> * Announcements<br /> ** stable/newton branch was created<br /> ** 3.0.0 released<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-20) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-06) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=155797 2017-08-07T01:38:33Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |-<br /> | 2016-08-23 || || x || ||<br /> |-<br /> | 2016-09-20 || || x || ||<br /> |-<br /> | 2016-12-13 || || x || ||<br /> |}<br /> <br /> == Agenda (2017-08-08) ==<br /> * This meeting has had no useful discussions these days.<br /> * (yamamoto) I'd suggest to officially shut down this meeting. I guess on-demand discussions on IRC or slack works best.<br /> <br /> == Agenda (2016-12-13) ==<br /> <br /> * Announcements<br /> ** stable/newton branch was created<br /> ** 3.0.0 released<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-20) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-06) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=155796 2017-08-07T01:34:21Z

<p>Yamamoto: /* Agenda (2017-8-9) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap%2Das%2Da%2Dservice+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap%2Das%2Da%2Dservice%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode%2DReview%3E%3D%2D2%2Cself&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d+branch%3Amaster&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself+branch%3Amaster&amp;Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d+branch%3Amaster&amp;stable%2Focata=branch%3Astable%2Focata&amp;stable%2Fnewton=branch%3Astable%2Fnewton&amp;other+branches=NOT+branch%3Amaster+AND+NOT+branch%3Astable%2Focata+AND+NOT+branch%3Astable%2Fnewton TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> Initial Spec for Stadium report is up :https://review.openstack.org/#/c/454788/<br /> <br /> <br /> === Project Teams Gathering ===<br /> * Denver, CO, USA (Sep., 11-15, 2017)<br /> <br /> <br /> === OpenStack Summit Sydney 2017 ===<br /> * Call for Presentations for OpenStack Summit Sydney: '''Submission deadline: 14th July 2017'''<br /> <br /> == Agenda (2017-8-9) ==<br /> * Pike release<br /> ** (yamamoto) Unless anyone objects, I'll make a release as it is.<br /> * Dashboard<br /> ** (yamamoto) I tried the dashboard. It worked well after fixing a few small things.<br /> * Review reminder<br /> ** https://review.openstack.org/#/c/349176/ This involves DB changes, thus not backportable. If we want it in Pike, review it right now.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-21) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-14) ==<br /> * (yamamoto) I updated &quot;TaaS Review Inbox&quot; link on the wiki. Please let me know if it has any problem.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-7) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-31) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-17) ==<br /> * Feedback from OpenStack Summit Boston<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-10) ==<br /> * '''Canceled''' (week of OpenStack Summit Boston)<br /> <br /> == Agenda (2017-5-3) ==<br /> * '''Canceled''' (national holiday in Japan)<br /> <br /> == Agenda (2017-4-26) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-19) ==<br /> * Horizon dashboard for neutron stadium projects<br /> ** http://lists.openstack.org/pipermail/openstack-dev/2017-April/115590.html<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-12) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-5) ==<br /> * Open Discussion<br /> <br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/<br /> <br /> == Important Links ==<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> *http://backreference.org/2014/06/17/port-mirroring-with-linux-bridges/<br /> * Slideshare slides<br /> ** https://www.slideshare.net/soichishigeta/designof-traffic-isolationby-using-flow-based-tunneling<br /> ** https://www.slideshare.net/soichishigeta/cannot-observe-ingress-packets<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-the-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-increasing-send-packets</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=155795 2017-08-07T01:30:54Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap%2Das%2Da%2Dservice+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap%2Das%2Da%2Dservice%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode%2DReview%3E%3D%2D2%2Cself&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d+branch%3Amaster&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself+branch%3Amaster&amp;Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d+branch%3Amaster&amp;stable%2Focata=branch%3Astable%2Focata&amp;stable%2Fnewton=branch%3Astable%2Fnewton&amp;other+branches=NOT+branch%3Amaster+AND+NOT+branch%3Astable%2Focata+AND+NOT+branch%3Astable%2Fnewton TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> Initial Spec for Stadium report is up :https://review.openstack.org/#/c/454788/<br /> <br /> <br /> === Project Teams Gathering ===<br /> * Denver, CO, USA (Sep., 11-15, 2017)<br /> <br /> <br /> === OpenStack Summit Sydney 2017 ===<br /> * Call for Presentations for OpenStack Summit Sydney: '''Submission deadline: 14th July 2017'''<br /> <br /> == Agenda (2017-8-9) ==<br /> * Pike release<br /> ** (yamamoto) Unless anyone objects, I'll make a release as it is.<br /> * Dashboard<br /> ** (yamamoto) I tried the dashboard. It worked well after fixing a few small things.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-21) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-14) ==<br /> * (yamamoto) I updated &quot;TaaS Review Inbox&quot; link on the wiki. Please let me know if it has any problem.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-7) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-31) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-17) ==<br /> * Feedback from OpenStack Summit Boston<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-10) ==<br /> * '''Canceled''' (week of OpenStack Summit Boston)<br /> <br /> == Agenda (2017-5-3) ==<br /> * '''Canceled''' (national holiday in Japan)<br /> <br /> == Agenda (2017-4-26) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-19) ==<br /> * Horizon dashboard for neutron stadium projects<br /> ** http://lists.openstack.org/pipermail/openstack-dev/2017-April/115590.html<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-12) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-5) ==<br /> * Open Discussion<br /> <br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/<br /> <br /> == Important Links ==<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> *http://backreference.org/2014/06/17/port-mirroring-with-linux-bridges/<br /> * Slideshare slides<br /> ** https://www.slideshare.net/soichishigeta/designof-traffic-isolationby-using-flow-based-tunneling<br /> ** https://www.slideshare.net/soichishigeta/cannot-observe-ingress-packets<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-the-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-increasing-send-packets</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=CrossProjectLiaisons&diff=154723 2017-06-16T03:54:58Z

<p>Yamamoto: /* Infra */</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=&quot;wikitable&quot;<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 || Eric Kao || ekcs<br /> |-<br /> | Cue || Min Pae || sputnik13<br /> |-<br /> | Designate || || <br /> |-<br /> | Freezer || Saad Zaher || szaher<br /> |-<br /> | Glance || Dharini Chandrasekar || dharinic<br /> |-<br /> | Heat || Thomas Herve || therve<br /> |-<br /> | Horizon || Rob Cresswell || robcresswell<br /> |-<br /> | I18n || Ian Y. Choi || ianychoi<br /> |-<br /> | Ironic || Rushil Chugh || crushil<br /> |-<br /> | Keystone || Brant Knudson || bknudson<br /> |-<br /> | Manila || Thomas Bechtold || toabctl<br /> |-<br /> | Mistral || Renat Akhmerov || rakhmerov<br /> |-<br /> | Murano || || <br /> |-<br /> | Neutron || James Anziano || janzian<br /> |-<br /> | Nova || || <br /> |-<br /> | [[Octavia]] || Michael Johnson || johnsom<br /> |-<br /> | Rally || Andrey Kurilin || andreykurilin<br /> |-<br /> | Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya<br /> |-<br /> | Senlin || Yanyan Hu || Yanyanhu<br /> |-<br /> <br /> | Swift || || <br /> |-<br /> | Tricircle || Chaoyi Huang || joehuang<br /> |-<br /> | TripleO || Ben Nemec || bnemec<br /> |-<br /> | Trove || Amrith Kumar || amrith<br /> |-<br /> | Zaqar || Flavio Percoco || flaper87<br /> |-<br /> | Zun || Hongbin Lu || hongbin<br /> |-<br /> |}<br /> <br /> == Release management ==<br /> <br /> The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been 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 liaison may further delegate work to other subject matter experts<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Barbican || Dave McCowan || dave-mccowan<br /> |-<br /> | Ceilometer || gordon chung || gordc<br /> |-<br /> | Cinder || Sean McGinnis || smcginnis<br /> |-<br /> | Congress || Eric Kao || ekcs<br /> |-<br /> | Designate || Tim Simmons || timsim<br /> |-<br /> | Documentation || Mariia Zlatkova &amp; Brian Moss || ?? &amp; bmoss<br /> |-<br /> | Freezer || Saad Zaher || szaher<br /> |-<br /> | Glance || Erno Kuvaja || jokke_<br /> |-<br /> | Heat || Thomas Herve || therve<br /> |-<br /> | Horizon || Rob Cresswell || robcresswell<br /> |-<br /> | I18n || Ian Y. Choi || ianychoi<br /> |-<br /> | Ironic || Dmitry Tantsur || dtantsur<br /> |-<br /> | Keystone || Lance Bragstad || lbragstad<br /> |-<br /> | Kolla || Jeffrey Zhang || Jeffrey4l<br /> |-<br /> | Magnum || Spyros Trigazis || strigazi<br /> |-<br /> | Manila || Ben Swartzlander || bswartz<br /> |-<br /> | Mistral || Lingxian Kong || kong<br /> |-<br /> | Monasca || Witek Bedyk || witek<br /> |-<br /> | Murano ||Kirill Zaitsev || kzaitsev_<br /> |-<br /> | Neutron || Armando Migliaccio || armax<br /> |-<br /> | Nova || Sylvain Bauza || bauzas<br /> |-<br /> | OpenStack-Ansible || Jean-Philippe Evrard || evrardjp<br /> |-<br /> | Oslo || Doug Hellmann || dhellmann<br /> |-<br /> | PuppetOpenStack || Alex Schultz || mwhahaha<br /> |-<br /> | Rally || Andrey Kurilin || andreykurilin<br /> |-<br /> | Sahara || Telles Nobrega || tenobreg/tellesnobrega<br /> |-<br /> | Searchlight || Steve McLellan || sjmc7<br /> |-<br /> | Senlin || Qiming Teng || Qiming<br /> |-<br /> | Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong<br /> |-<br /> | Storlets || Eran Rom || eranrom<br /> |-<br /> | Swift || John Dickinson || notmyname<br /> |-<br /> | TripleO || Emilien Macchi || EmilienM<br /> |-<br /> | Trove || Amrith Kumar || amrith<br /> |-<br /> | Watcher || Alexander Chadin || alexchadin<br /> |-<br /> | Winstackers || Claudiu Belu || claudiub<br /> |-<br /> | Zaqar || Fei Long Wang || flwang <br /> |-<br /> | Zun || Hongbin Lu || hongbin <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=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Barbican || Steve Heyman || hockeynut <br /> |-<br /> | Ceilometer || Chris Dent || cdent<br /> |-<br /> | Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne<br /> |-<br /> | Congress || Eric Kao || ekcs<br /> |-<br /> | Freezer || Guillermo Garcia || m3mo<br /> |-<br /> | Glance || Brian Rosmaita || rosmaita<br /> |-<br /> | Heat || Steve Baker || stevebaker<br /> |-<br /> | Horizon || Rob Cresswell || robcresswell<br /> |-<br /> | Ironic || John Villalovos || jlvillal<br /> |-<br /> | Keystone || Rodrigo Duarte || rodrigods<br /> |-<br /> | Manila || Valeriy Ponomaryov || vponomaryov<br /> |-<br /> | Murano || Victor Ryzhenkin || freerunner<br /> |-<br /> | Neutron || Kevin Benton || kevinbenton<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 || Thiago da Silva || tdasilva<br /> |-<br /> | Trove || Craig Vyvial and Nirav Shah || cp16net and nshah<br /> |-<br /> | Zaqar || Fei Long Wang || flwang <br /> |-<br /> | Zun || Hongbin Lu || hongbin <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=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Barbican || Douglas Mendizábal || redrobot <br /> |-<br /> | Ceilometer || Ildiko Vancsa || ildikov<br /> |-<br /> | Cinder || Jay Bryant || jungleboyj <br /> |-<br /> | Congress || Aimee Ukasick || aimeeu<br /> |-<br /> | Designate || Graham Hayes || mugsie<br /> |-<br /> | Freezer || Guillermo Garcia || m3mo<br /> |-<br /> | Glance || Brian Rosmaita || rosmaita<br /> |-<br /> | Heat || Rabi Mishra || ramishra<br /> |-<br /> | Horizon || Rob Cresswell || robcresswell<br /> |-<br /> | I18n || Ian Choi || ianychoi<br /> |-<br /> | Ironic || Julia Kreger || TheJulia<br /> |-<br /> | Keystone || Lance Bragstad || lbragstad<br /> |-<br /> | Kolla || Michal Jastrzebski || inc0<br /> |-<br /> | Magnum || Spyros Trigazis || strigazi<br /> |-<br /> | Manila || Ben Swartzlander || bswartz<br /> |-<br /> | Mistral || Dougal Matthews || d0ugal<br /> |-<br /> | Murano || Kirill Zaitsev || kzaitsev_<br /> |-<br /> | Neutron || Miguel Lavalle || mlavalle<br /> |-<br /> | Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock<br /> |-<br /> | OpenStack-Ansible || Amy Marrich || spotz<br /> |-<br /> | Ops || Robert Starmer || <br /> |-<br /> | Oslo || Doug Hellmann || dhellmann<br /> |-<br /> | Puppet OpenStack || Emilien Macchi || EmilienM<br /> |-<br /> | Rally || Boris Pavlovic || boris-42<br /> |-<br /> | Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford<br /> |-<br /> | Senlin || Cindia Blue || lixinhui<br /> |-<br /> | Swift || John Dickinson || notmyname<br /> |-<br /> | Tripleo || Steven Hardy || shardy<br /> |-<br /> | Trove || Trevor McCasland || trevormc<br /> |-<br /> | Watcher || Prudhvi Rao Shedimbi || pshedimb<br /> |-<br /> | Zaqar || Fei Long Wang || flwang<br /> |-<br /> | Zun || Hongbin Lu || hongbin<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=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Barbican || Dave McCowan || dave-mccowan<br /> |-<br /> | Ceilometer || Eoghan Glynn || eglynn<br /> |-<br /> | Cinder || Jay Bryant || jungleboyj<br /> |-<br /> | Congress || Masahito Muroi || masahito<br /> |-<br /> | Freezer || Saad Zaher || szaher<br /> |-<br /> | Glance || Erno Kuvaja || jokke_<br /> |-<br /> | Heat || Zane Bitter || zaneb<br /> |-<br /> | Horizon || Rob Cresswell || robcresswell <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 || Matthew Oliver || mattoliverau <br /> |-<br /> | Trove || Amrith Kumar || amrith<br /> |-<br /> | Watcher || David Tardivel || dtardivel<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 [https://security.openstack.org/vmt-process.html 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=&quot;wikitable&quot;<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 /> | Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme <br /> |-<br /> | Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil <br /> |-<br /> | Heat || Steve Hardy || shardy<br /> |-<br /> | Horizon || Rob Cresswell || robcresswell<br /> |-<br /> | Ironic || || <br /> |-<br /> | Keystone || Dolph Mathews || dolphm<br /> |-<br /> | Kolla || Michal Jastrzebski || inc0<br /> |-<br /> | Manila || Tom Barron || tbarron<br /> |-<br /> | Murano || Victor Ryzhenkin || freerunner<br /> |-<br /> | Neutron || Kevin Benton || kevinbenton<br /> |-<br /> | Nova || Michael Still || mikal<br /> |-<br /> | Sahara || Telles Nobrega || tellesnobrega<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=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Glance || Erno Kuvaja || jokke_<br /> |-<br /> | Ironic || || <br /> |-<br /> | Oslo || Doug Hellmann || dhellmann<br /> |-<br /> | Nova || John Garbutt || johnthetubaguy<br /> |-<br /> | Murano || ||<br /> |-<br /> | Sahara || Elise 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=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito<br /> |-<br /> | Freezer || Saad Zaher || szaher<br /> |-<br /> | Glance || Brian Rosmaita || rosmaita<br /> |-<br /> | I18n || Ian Y. Choi || ianychoi<br /> |-<br /> | Ironic || Dmitry Tantsur, Vasyl Saienko || dtantsur, vsaienko<br /> |-<br /> | Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts<br /> |-<br /> | Neutron || Ihar Hrachyshka, Armando Migliaccio, YAMAMOTO Takashi || ihrachys, armax, yamamoto<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 || Vitaliy Gridnev || Vitaliy Gridnev<br /> <br /> |-<br /> | Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov<br /> <br /> |-<br /> | Puppet OpenStack || Emilien Macchi, Alex Schultz || EmilienM, mwhahaha<br /> <br /> |-<br /> | TripleO || 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=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Ceilometer ||Krish Ragurham || <br /> |-<br /> | Cinder || Shamail Tahir || shamail<br /> |-<br /> | Congress || Eric Kao || ekcs<br /> |-<br /> | Freezer || Pierre Mathieu || slashme<br /> |-<br /> | Glance || Brian Rosmaita || rosmaita<br /> |-<br /> | Horizon || Carol Barrett || carolbarrett<br /> |-<br /> | Ironic || Yih Leong Sun || leong<br /> |-<br /> | Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR<br /> |-<br /> | Kolla || Yih Leong Sun || leong<br /> |-<br /> | Magnum || Steve Gordon || sgordon<br /> |-<br /> | Manila ||Pete Chadwick || pchadwick<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 /> | QA || Arkady Kanevsky || arkady_kanevsky<br /> |-<br /> | Rally || Arkady Kanevsky || arkady_kanevsky<br /> |-<br /> | Sahara || Elise 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 /> | Watcher || Megan Rossetti || MeganR<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 (or a person who is not a core reviewer but agreed &amp; approved by PTL) 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=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Barbican || || <br /> |-<br /> | Cinder || || <br /> |-<br /> | Designate || Graham Hayes || mugsie<br /> |-<br /> | Glance || || <br /> |-<br /> | Heat || || <br /> |-<br /> | Horizon || Akihiro Motoki || amotoki<br /> |-<br /> | Ironic || || <br /> |-<br /> | Keystone || || <br /> |-<br /> | Magnum || Shu Muto || shu-mutou<br /> |-<br /> | Manila || || <br /> |-<br /> | Monasca || || <br /> |-<br /> | Murano || || <br /> |-<br /> | Neutron || Akihiro Motoki || amotoki<br /> |-<br /> | Nova || Augustina Ragwitz || auggy <br /> |-<br /> | Oslo || || <br /> |-<br /> | Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg<br /> |-<br /> | Senlin || || <br /> |-<br /> | Swift || ||<br /> |-<br /> | Tacker || || <br /> |-<br /> | Telemetry || || <br /> |-<br /> | TripleO || Julie Pichon || jpich<br /> |-<br /> | Trove || || <br /> |-<br /> | Sahara || Chad Roberts || crobertsrh <br /> |-<br /> | Watcher || Yumeng Bao || Yumeng <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=&quot;wikitable&quot;<br /> |-<br /> ! Projects !! Name !! IRC Handle !! Role<br /> |-<br /> | Nova / Neutron || || ||<br /> |-<br /> | || Kevin Benton || kevinbenton || Neutron liaison for Nova<br /> |-<br /> | Nova / Glance || || ||<br /> |-<br /> | || Mike Fedosin || 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 || || ||<br /> |-<br /> | || Jim Rollenhagen || jroll || Ironic liaison for Nova<br /> |-<br /> | Neutron / Ironic || || ||<br /> |-<br /> | || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic<br /> |-<br /> | || Sam Betts || sambetts || 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 /> | || Akihiro Motoki || amotoki || Horizon liaison for i18n<br /> |-<br /> | || TBD || || Heat 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 /> | || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum<br /> |-<br /> | TripleO / Ironic || || ||<br /> |-<br /> | || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO<br /> |-<br /> | Nova / Watcher || || ||<br /> |-<br /> | || Ed Leafe || edleafe || Nova liaison for Watcher<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=&quot;wikitable&quot;<br /> |-<br /> ! Project !! Liaison !! IRC Handle<br /> |-<br /> | Barbican || Douglas Mendizabal || redrobot<br /> |-<br /> | Cinder || Kendall Nelson || diablo_rojo<br /> |-<br /> | Congress || Eric Kao || ekcs<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 || || <br /> |-<br /> | Keystone || Samuel de Medeiros Queiroz || samueldmq<br /> |-<br /> | Kolla || Swapnil Kulkarni || coolsvap<br /> |-<br /> | Kuryr || Gal Sagie || gsagie<br /> |-<br /> | Magnum || Adrian Otto || adrian_otto<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 || Kevin Benton || kevinbenton<br /> |-<br /> | Nova || Chris Dent || cdent<br /> |-<br /> | OpenStack-Ansible || Travis Truman || automagically<br /> |-<br /> | Oslo || Davanum Srinivas || dims<br /> |-<br /> | Puppet OpenStack || Alex Schultz || mwhahaha<br /> |-<br /> | Sahara || Telles Nobrega || tellesnobrega<br /> |-<br /> | Searchlight || Steve McLellan || sjmc7<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 /> | Zun || Hongbin Lu || hongbin<br /> |}</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=154621 2017-06-12T04:00:24Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap%2Das%2Da%2Dservice+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap%2Das%2Da%2Dservice%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode%2DReview%3E%3D%2D2%2Cself&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d+branch%3Amaster&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself+branch%3Amaster&amp;Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT%28reviewerin%3Atap%2Das%2Da%2Dservice%2Dcore+label%3ACode%2DReview%3C%3D%2D1%29+limit%3A50+branch%3Amaster&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d+branch%3Amaster&amp;stable%2Focata=branch%3Astable%2Focata&amp;stable%2Fnewton=branch%3Astable%2Fnewton&amp;other+branches=NOT+branch%3Amaster+AND+NOT+branch%3Astable%2Focata+AND+NOT+branch%3Astable%2Fnewton TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> Initial Spec for Stadium report is up :https://review.openstack.org/#/c/454788/<br /> <br /> == Agenda (2017-6-14) ==<br /> * (yamamoto) I updated &quot;TaaS Review Inbox&quot; link on the wiki. Please let me know if it has any problem.<br /> * Open Discussion<br /> <br /> == Agenda (2017-6-7) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-31) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-17) ==<br /> * Feedback from OpenStack Summit Boston<br /> * Open Discussion<br /> <br /> == Agenda (2017-5-10) ==<br /> * '''Canceled''' (week of OpenStack Summit Boston)<br /> <br /> == Agenda (2017-5-3) ==<br /> * '''Canceled''' (national holiday in Japan)<br /> <br /> == Agenda (2017-4-26) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-19) ==<br /> * Horizon dashboard for neutron stadium projects<br /> ** http://lists.openstack.org/pipermail/openstack-dev/2017-April/115590.html<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-12) ==<br /> * Open Discussion<br /> <br /> == Agenda (2017-4-5) ==<br /> * Open Discussion<br /> <br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/<br /> <br /> == Important Links ==<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> *http://backreference.org/2014/06/17/port-mirroring-with-linux-bridges/<br /> * Slideshare slides<br /> ** https://www.slideshare.net/soichishigeta/designof-traffic-isolationby-using-flow-based-tunneling<br /> ** https://www.slideshare.net/soichishigeta/cannot-observe-ingress-packets<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-the-source-vms-are-increased<br /> ** https://www.slideshare.net/soichishigeta/performance-measurement-when-increasing-send-packets</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=150813 2017-02-07T21:45:32Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> <br /> == Agenda (2017-2-8) ==<br /> * yamamoto can't attend this week<br /> * yamamoto plan to cut ocata this week http://lists.openstack.org/pipermail/openstack-dev/2017-February/111653.html<br /> * A talk for Boston Summit ('''deadline (extended): February 8th at 11:59pm PST (February 9th at 7:59 UTC)''')<br /> * Open Discussion<br /> <br /> == Agenda (2017-2-1) ==<br /> * A talk for Boston Summit ('''deadline: Feb 6th''')<br /> * Open Discussion<br /> <br /> == Agenda (2017-1-25) ==<br /> * Review currently open code ( see TaaS review Inbox )<br /> * Open Discussion<br /> <br /> == Agenda (2017-1-18) ==<br /> * Loop detection of tap flows (cont.)<br /> ** Tap of tap mirrors own traffic but not mirrored traffic. http://lists.openstack.org/pipermail/openstack-dev/attachments/20170118/eea51ee0/attachment-0001.pdf<br /> * Open Discussion<br /> <br /> == Agenda (2017-1-11) ==<br /> * how tap of tap should work? (or should not work?) (cont.)<br /> ** Loop detection of tap flows (to prevent creating a loop)<br /> * Open Discussion<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=150771 2017-02-07T05:27:26Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> <br /> == Agenda (2017-2-8) ==<br /> * yamamoto can't attend this week<br /> * yamamoto plan to cut ocata this week http://lists.openstack.org/pipermail/openstack-dev/2017-February/111653.html<br /> * A talk for Boston Summit ('''deadline: Feb 6th''')<br /> * Open Discussion<br /> <br /> == Agenda (2017-2-1) ==<br /> * A talk for Boston Summit ('''deadline: Feb 6th''')<br /> * Open Discussion<br /> <br /> == Agenda (2017-1-25) ==<br /> * Review currently open code ( see TaaS review Inbox )<br /> * Open Discussion<br /> <br /> == Agenda (2017-1-18) ==<br /> * Loop detection of tap flows (cont.)<br /> ** Tap of tap mirrors own traffic but not mirrored traffic. http://lists.openstack.org/pipermail/openstack-dev/attachments/20170118/eea51ee0/attachment-0001.pdf<br /> * Open Discussion<br /> <br /> == Agenda (2017-1-11) ==<br /> * how tap of tap should work? (or should not work?) (cont.)<br /> ** Loop detection of tap flows (to prevent creating a loop)<br /> * Open Discussion<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> * [[Previous meetings]]<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=145003 2016-12-13T07:05:23Z

<p>Yamamoto: /* Bug deputy */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |-<br /> | 2016-08-23 || || x || ||<br /> |-<br /> | 2016-09-20 || || x || ||<br /> |-<br /> | 2016-12-13 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-12-13) ==<br /> <br /> * Announcements<br /> ** stable/newton branch was created<br /> ** 3.0.0 released<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-20) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-06) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=145001 2016-12-13T06:44:40Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |-<br /> | 2016-08-23 || || x || ||<br /> |-<br /> | 2016-09-20 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-12-13) ==<br /> <br /> * Announcements<br /> ** stable/newton branch was created<br /> ** 3.0.0 released<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-20) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-06) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=144429 2016-12-06T10:40:34Z

<p>Yamamoto: /* Agenda (2016-12-07) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> <br /> == Agenda (2016-12-07) ==<br /> * spec<br /> ** we should finialize the current spec https://review.openstack.org/#/c/256210/<br /> ** extension: dragonflow wants tap-flow &quot;position&quot; parameter. ditto for midonet.<br /> ** how tap of tap should work? (or should not work?)<br /> *** we need some clear semantics<br /> **** a) prevent it at plugin level?<br /> **** b) mirror all traffic on the port, including mirrored traffic?<br /> **** c) mirror the port's own traffic but not mirrored traffic?<br /> *** current state of implementations<br /> **** i don't think it currently works for the reference implementation.<br /> **** midonet is b) above (it just work, with a hardcoded limit for infinite loop avoidance)<br /> **** dragonflow is under discussion: https://review.openstack.org/#/c/396307/<br /> <br /> == Agenda (2016-11-30) ==<br /> * L2 Extension Migration for TaaS : Status = in progress : Review = https://review.openstack.org/401258<br /> * OSC Support for TaaS: Status = in progress: Review = https://review.openstack.org/398767<br /> * Horizon Support for TaaS: Status = in progress: Review = https://review.openstack.org/396022<br /> * Migration to neutron-lib : Tracked by : https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:master+topic:bp/neutron-lib<br /> * do we want to create stable/newton branch? http://lists.openstack.org/pipermail/openstack-dev/2016-November/107892.html<br /> <br /> == Agenda (2016-11-23) ==<br /> Canceled (because of national holiday in Japan)<br /> <br /> == Agenda (2016-11-16) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-09) ==<br /> * Feedback from Barcelona Summit<br /> ** Action Items and Next Step: https://etherpad.openstack.org/p/BCN-tap-as-a-service-1<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-02) ==<br /> skipped<br /> <br /> == Agenda (2016-10-26) ==<br /> Will be skipped (Barcelona Summit)<br /> <br /> == Agenda (2016-10-19) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-10-12) ==<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-10-05) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** Adding TaaS to Ocata Design Summit Ideas?<br /> *** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-28) ==<br /> * Inclusion in Governance and Neutron Stadium<br /> * Adding TaaS to Ocata Design Summit Ideas? http://lists.openstack.org/pipermail/openstack-dev/2016-September/104668.html<br /> ** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-21) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** (kaz) Performance measurement (progress report) [[Media:Increasing_Send_Packets20160921.png]]<br /> * Medium<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-14) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-07) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160906.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-31) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160831.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-17) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-10) ==<br /> * Bug: not capturing ingress traffic from VM on same host<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-03) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-27) ==<br /> * (kaz) Performance measurement (corrected edition) http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/04c7bcbc/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling (cont.)<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> ** Session voting for Barcelona Summit: https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/<br /> <br /> == Agenda (2016-07-20) ==<br /> * (kaz) Performance measurement: http://lists.openstack.org/pipermail/openstack-dev/attachments/20160518/724a5f6d/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling [[Media:flow_based_tunneling-20160720-r1.png]]<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-13) ==<br /> * High<br /> ** '''Finalize and Submit''' Presentation in Barcelona Summit ('''Submission Deadline = Today''')<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-07-06) ==<br /> * Canceled since some of the team members are planning to attend OpenStack Days in Tokyo<br /> <br /> == Agenda (2016-06-29) ==<br /> <br /> * Preparation for Barcelona Summit (TaaS presentation): '''Submission Deadline: Wednesday, 13th, Jul'''<br /> ** Title, Speakers, Abstract: [[Media:Draft_20160629-01.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-22) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka? http://lists.openstack.org/pipermail/openstack-dev/2016-June/097727.html<br /> * High<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> ** gate blocker https://review.openstack.org/#/c/326231/<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=144428 2016-12-06T10:38:49Z

<p>Yamamoto: /* Agenda (2016-12-07) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> <br /> == Agenda (2016-12-07) ==<br /> * spec<br /> ** we should finialize the current spec<br /> ** extension: dragonflow wants tap-flow &quot;position&quot; parameter. ditto for midonet.<br /> ** how tap of tap should work? (or should not work?)<br /> *** we need some clear semantics<br /> **** a) prevent it at plugin level?<br /> **** b) mirror all traffic on the port, including mirrored traffic?<br /> **** c) mirror the port's own traffic but not mirrored traffic?<br /> *** current state of implementations<br /> **** i don't think it currently works for the reference implementation.<br /> **** midonet is b) above (it just work, with a hardcoded limit for infinite loop avoidance)<br /> **** dragonflow is under discussion: https://review.openstack.org/#/c/396307/<br /> <br /> == Agenda (2016-11-30) ==<br /> * L2 Extension Migration for TaaS : Status = in progress : Review = https://review.openstack.org/401258<br /> * OSC Support for TaaS: Status = in progress: Review = https://review.openstack.org/398767<br /> * Horizon Support for TaaS: Status = in progress: Review = https://review.openstack.org/396022<br /> * Migration to neutron-lib : Tracked by : https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:master+topic:bp/neutron-lib<br /> * do we want to create stable/newton branch? http://lists.openstack.org/pipermail/openstack-dev/2016-November/107892.html<br /> <br /> == Agenda (2016-11-23) ==<br /> Canceled (because of national holiday in Japan)<br /> <br /> == Agenda (2016-11-16) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-09) ==<br /> * Feedback from Barcelona Summit<br /> ** Action Items and Next Step: https://etherpad.openstack.org/p/BCN-tap-as-a-service-1<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-02) ==<br /> skipped<br /> <br /> == Agenda (2016-10-26) ==<br /> Will be skipped (Barcelona Summit)<br /> <br /> == Agenda (2016-10-19) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-10-12) ==<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-10-05) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** Adding TaaS to Ocata Design Summit Ideas?<br /> *** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-28) ==<br /> * Inclusion in Governance and Neutron Stadium<br /> * Adding TaaS to Ocata Design Summit Ideas? http://lists.openstack.org/pipermail/openstack-dev/2016-September/104668.html<br /> ** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-21) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** (kaz) Performance measurement (progress report) [[Media:Increasing_Send_Packets20160921.png]]<br /> * Medium<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-14) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-07) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160906.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-31) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160831.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-17) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-10) ==<br /> * Bug: not capturing ingress traffic from VM on same host<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-03) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-27) ==<br /> * (kaz) Performance measurement (corrected edition) http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/04c7bcbc/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling (cont.)<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> ** Session voting for Barcelona Summit: https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/<br /> <br /> == Agenda (2016-07-20) ==<br /> * (kaz) Performance measurement: http://lists.openstack.org/pipermail/openstack-dev/attachments/20160518/724a5f6d/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling [[Media:flow_based_tunneling-20160720-r1.png]]<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-13) ==<br /> * High<br /> ** '''Finalize and Submit''' Presentation in Barcelona Summit ('''Submission Deadline = Today''')<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-07-06) ==<br /> * Canceled since some of the team members are planning to attend OpenStack Days in Tokyo<br /> <br /> == Agenda (2016-06-29) ==<br /> <br /> * Preparation for Barcelona Summit (TaaS presentation): '''Submission Deadline: Wednesday, 13th, Jul'''<br /> ** Title, Speakers, Abstract: [[Media:Draft_20160629-01.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-22) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka? http://lists.openstack.org/pipermail/openstack-dev/2016-June/097727.html<br /> * High<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> ** gate blocker https://review.openstack.org/#/c/326231/<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=144427 2016-12-06T10:34:10Z

<p>Yamamoto: /* Agenda (2016-12-07) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> <br /> == Agenda (2016-12-07) ==<br /> * spec<br /> ** we should finialize the current spec<br /> ** extension: dragonflow wants tap-flow &quot;position&quot; parameter. ditto for midonet.<br /> ** how tap of tap should work? (or should not work?)<br /> *** we need some clear semantics<br /> **** i don't think it currently works for the reference implementation.<br /> **** midonet has no limitation (it just work, with a hardcoded limit for infinite loop avoidance)<br /> **** dragonflow is under discussion: https://review.openstack.org/#/c/396307/<br /> <br /> == Agenda (2016-11-30) ==<br /> * L2 Extension Migration for TaaS : Status = in progress : Review = https://review.openstack.org/401258<br /> * OSC Support for TaaS: Status = in progress: Review = https://review.openstack.org/398767<br /> * Horizon Support for TaaS: Status = in progress: Review = https://review.openstack.org/396022<br /> * Migration to neutron-lib : Tracked by : https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:master+topic:bp/neutron-lib<br /> * do we want to create stable/newton branch? http://lists.openstack.org/pipermail/openstack-dev/2016-November/107892.html<br /> <br /> == Agenda (2016-11-23) ==<br /> Canceled (because of national holiday in Japan)<br /> <br /> == Agenda (2016-11-16) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-09) ==<br /> * Feedback from Barcelona Summit<br /> ** Action Items and Next Step: https://etherpad.openstack.org/p/BCN-tap-as-a-service-1<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-02) ==<br /> skipped<br /> <br /> == Agenda (2016-10-26) ==<br /> Will be skipped (Barcelona Summit)<br /> <br /> == Agenda (2016-10-19) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-10-12) ==<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-10-05) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** Adding TaaS to Ocata Design Summit Ideas?<br /> *** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-28) ==<br /> * Inclusion in Governance and Neutron Stadium<br /> * Adding TaaS to Ocata Design Summit Ideas? http://lists.openstack.org/pipermail/openstack-dev/2016-September/104668.html<br /> ** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-21) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** (kaz) Performance measurement (progress report) [[Media:Increasing_Send_Packets20160921.png]]<br /> * Medium<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-14) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-07) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160906.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-31) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160831.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-17) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-10) ==<br /> * Bug: not capturing ingress traffic from VM on same host<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-03) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-27) ==<br /> * (kaz) Performance measurement (corrected edition) http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/04c7bcbc/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling (cont.)<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> ** Session voting for Barcelona Summit: https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/<br /> <br /> == Agenda (2016-07-20) ==<br /> * (kaz) Performance measurement: http://lists.openstack.org/pipermail/openstack-dev/attachments/20160518/724a5f6d/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling [[Media:flow_based_tunneling-20160720-r1.png]]<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-13) ==<br /> * High<br /> ** '''Finalize and Submit''' Presentation in Barcelona Summit ('''Submission Deadline = Today''')<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-07-06) ==<br /> * Canceled since some of the team members are planning to attend OpenStack Days in Tokyo<br /> <br /> == Agenda (2016-06-29) ==<br /> <br /> * Preparation for Barcelona Summit (TaaS presentation): '''Submission Deadline: Wednesday, 13th, Jul'''<br /> ** Title, Speakers, Abstract: [[Media:Draft_20160629-01.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-22) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka? http://lists.openstack.org/pipermail/openstack-dev/2016-June/097727.html<br /> * High<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> ** gate blocker https://review.openstack.org/#/c/326231/<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=144426 2016-12-06T10:32:15Z

<p>Yamamoto: /* Agenda (2016-12-07) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> <br /> == Agenda (2016-12-07) ==<br /> * spec<br /> ** we should finialize the current spec<br /> ** extension: dragonflow wants tap-flow &quot;position&quot; parameter. ditto for midonet.<br /> ** how tap of tap should work? (or should not work?)<br /> *** i don't think it works for the reference implementation.<br /> *** midonet has no limitation (it just work, with a hardcoded limit for infinite loop avoidance)<br /> *** dragonflow is in discussion: https://review.openstack.org/#/c/396307/<br /> <br /> == Agenda (2016-11-30) ==<br /> * L2 Extension Migration for TaaS : Status = in progress : Review = https://review.openstack.org/401258<br /> * OSC Support for TaaS: Status = in progress: Review = https://review.openstack.org/398767<br /> * Horizon Support for TaaS: Status = in progress: Review = https://review.openstack.org/396022<br /> * Migration to neutron-lib : Tracked by : https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:master+topic:bp/neutron-lib<br /> * do we want to create stable/newton branch? http://lists.openstack.org/pipermail/openstack-dev/2016-November/107892.html<br /> <br /> == Agenda (2016-11-23) ==<br /> Canceled (because of national holiday in Japan)<br /> <br /> == Agenda (2016-11-16) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-09) ==<br /> * Feedback from Barcelona Summit<br /> ** Action Items and Next Step: https://etherpad.openstack.org/p/BCN-tap-as-a-service-1<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-02) ==<br /> skipped<br /> <br /> == Agenda (2016-10-26) ==<br /> Will be skipped (Barcelona Summit)<br /> <br /> == Agenda (2016-10-19) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-10-12) ==<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-10-05) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** Adding TaaS to Ocata Design Summit Ideas?<br /> *** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-28) ==<br /> * Inclusion in Governance and Neutron Stadium<br /> * Adding TaaS to Ocata Design Summit Ideas? http://lists.openstack.org/pipermail/openstack-dev/2016-September/104668.html<br /> ** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-21) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** (kaz) Performance measurement (progress report) [[Media:Increasing_Send_Packets20160921.png]]<br /> * Medium<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-14) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-07) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160906.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-31) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160831.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-17) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-10) ==<br /> * Bug: not capturing ingress traffic from VM on same host<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-03) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-27) ==<br /> * (kaz) Performance measurement (corrected edition) http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/04c7bcbc/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling (cont.)<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> ** Session voting for Barcelona Summit: https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/<br /> <br /> == Agenda (2016-07-20) ==<br /> * (kaz) Performance measurement: http://lists.openstack.org/pipermail/openstack-dev/attachments/20160518/724a5f6d/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling [[Media:flow_based_tunneling-20160720-r1.png]]<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-13) ==<br /> * High<br /> ** '''Finalize and Submit''' Presentation in Barcelona Summit ('''Submission Deadline = Today''')<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-07-06) ==<br /> * Canceled since some of the team members are planning to attend OpenStack Days in Tokyo<br /> <br /> == Agenda (2016-06-29) ==<br /> <br /> * Preparation for Barcelona Summit (TaaS presentation): '''Submission Deadline: Wednesday, 13th, Jul'''<br /> ** Title, Speakers, Abstract: [[Media:Draft_20160629-01.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-22) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka? http://lists.openstack.org/pipermail/openstack-dev/2016-June/097727.html<br /> * High<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> ** gate blocker https://review.openstack.org/#/c/326231/<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=143729 2016-12-01T08:46:46Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> <br /> == Agenda (2016-12-07) ==<br /> * spec<br /> ** we should finialize the current spec<br /> ** extension: dragonflow wants tap-flow &quot;position&quot; parameter. ditto for midonet.<br /> <br /> == Agenda (2016-11-30) ==<br /> * L2 Extension Migration for TaaS : Status = in progress : Review = https://review.openstack.org/401258<br /> * OSC Support for TaaS: Status = in progress: Review = https://review.openstack.org/398767<br /> * Horizon Support for TaaS: Status = in progress: Review = https://review.openstack.org/396022<br /> * Migration to neutron-lib : Tracked by : https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:master+topic:bp/neutron-lib<br /> * do we want to create stable/newton branch? http://lists.openstack.org/pipermail/openstack-dev/2016-November/107892.html<br /> <br /> == Agenda (2016-11-23) ==<br /> Canceled (because of national holiday in Japan)<br /> <br /> == Agenda (2016-11-16) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-09) ==<br /> * Feedback from Barcelona Summit<br /> ** Action Items and Next Step: https://etherpad.openstack.org/p/BCN-tap-as-a-service-1<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-02) ==<br /> skipped<br /> <br /> == Agenda (2016-10-26) ==<br /> Will be skipped (Barcelona Summit)<br /> <br /> == Agenda (2016-10-19) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-10-12) ==<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-10-05) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** Adding TaaS to Ocata Design Summit Ideas?<br /> *** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-28) ==<br /> * Inclusion in Governance and Neutron Stadium<br /> * Adding TaaS to Ocata Design Summit Ideas? http://lists.openstack.org/pipermail/openstack-dev/2016-September/104668.html<br /> ** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-21) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** (kaz) Performance measurement (progress report) [[Media:Increasing_Send_Packets20160921.png]]<br /> * Medium<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-14) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-07) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160906.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-31) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160831.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-17) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-10) ==<br /> * Bug: not capturing ingress traffic from VM on same host<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-03) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-27) ==<br /> * (kaz) Performance measurement (corrected edition) http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/04c7bcbc/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling (cont.)<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> ** Session voting for Barcelona Summit: https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/<br /> <br /> == Agenda (2016-07-20) ==<br /> * (kaz) Performance measurement: http://lists.openstack.org/pipermail/openstack-dev/attachments/20160518/724a5f6d/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling [[Media:flow_based_tunneling-20160720-r1.png]]<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-13) ==<br /> * High<br /> ** '''Finalize and Submit''' Presentation in Barcelona Summit ('''Submission Deadline = Today''')<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-07-06) ==<br /> * Canceled since some of the team members are planning to attend OpenStack Days in Tokyo<br /> <br /> == Agenda (2016-06-29) ==<br /> <br /> * Preparation for Barcelona Summit (TaaS presentation): '''Submission Deadline: Wednesday, 13th, Jul'''<br /> ** Title, Speakers, Abstract: [[Media:Draft_20160629-01.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-22) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka? http://lists.openstack.org/pipermail/openstack-dev/2016-June/097727.html<br /> * High<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> ** gate blocker https://review.openstack.org/#/c/326231/<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=143310 2016-11-29T09:55:23Z

<p>Yamamoto: /* Agenda (2016-11-30) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> === Announcement ===<br /> * #vBrownBag Tech Talk at OpenStack Summit Barcelona<br /> ** [https://www.youtube.com/watch?v=C3w8YOuLNDQ&amp;feature=youtu.be &quot;Design and Performance Characteristics of Tap-as-a-Service&quot;]<br /> ** [https://www.youtube.com/watch?v=egAvOHlWqas&amp;feature=youtu.be &quot;Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA&quot;]<br /> <br /> == Agenda (2016-11-30) ==<br /> * L2 Extension Migration for TaaS : Status = in progress : Review = https://review.openstack.org/401258<br /> * OSC Support for TaaS: Status = in progress: Review = https://review.openstack.org/398767<br /> * Horizon Support for TaaS: Status = in progress: Review = https://review.openstack.org/396022<br /> * Migration to neutron-lib : Tracked by : https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:master+topic:bp/neutron-lib<br /> * do we want to create stable/newton branch? http://lists.openstack.org/pipermail/openstack-dev/2016-November/107892.html<br /> <br /> == Agenda (2016-11-23) ==<br /> Canceled (because of national holiday in Japan)<br /> <br /> == Agenda (2016-11-16) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-09) ==<br /> * Feedback from Barcelona Summit<br /> ** Action Items and Next Step: https://etherpad.openstack.org/p/BCN-tap-as-a-service-1<br /> * Open Discussion<br /> <br /> == Agenda (2016-11-02) ==<br /> skipped<br /> <br /> == Agenda (2016-10-26) ==<br /> Will be skipped (Barcelona Summit)<br /> <br /> == Agenda (2016-10-19) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-10-12) ==<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-10-05) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** Adding TaaS to Ocata Design Summit Ideas?<br /> *** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Medium<br /> ** Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?<br /> *** ex) 0530 UTC, Wednesday -&gt; 0630 UTC, Wednesday<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-28) ==<br /> * Inclusion in Governance and Neutron Stadium<br /> * Adding TaaS to Ocata Design Summit Ideas? http://lists.openstack.org/pipermail/openstack-dev/2016-September/104668.html<br /> ** Etherpad: https://etherpad.openstack.org/p/ocata-neutron-summit-ideas<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-21) ==<br /> * High<br /> ** Inclusion in Governance and Neutron Stadium<br /> ** (kaz) Performance measurement (progress report) [[Media:Increasing_Send_Packets20160921.png]]<br /> * Medium<br /> ** Open Discussion<br /> <br /> == Agenda (2016-09-14) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-07) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160906.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-31) ==<br /> * (kaz) Performance measurement (progress report) [[Media:Increasing_Source_VMs-20160831.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-24) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-17) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-10) ==<br /> * Bug: not capturing ingress traffic from VM on same host<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-03) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-27) ==<br /> * (kaz) Performance measurement (corrected edition) http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/04c7bcbc/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling (cont.)<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> ** Session voting for Barcelona Summit: https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/<br /> <br /> == Agenda (2016-07-20) ==<br /> * (kaz) Performance measurement: http://lists.openstack.org/pipermail/openstack-dev/attachments/20160518/724a5f6d/attachment-0001.pdf<br /> * (kaz) Design of traffic isolation by using flow based tunneling [[Media:flow_based_tunneling-20160720-r1.png]]<br /> * (kaz) Can not capture the packet, if the two VM on the same host [[Media:ingress_packet-20160720-r1.png]]<br /> ** reference: http://lists.openstack.org/pipermail/openstack-dev/2016-July/098606.html<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-13) ==<br /> * High<br /> ** '''Finalize and Submit''' Presentation in Barcelona Summit ('''Submission Deadline = Today''')<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-07-06) ==<br /> * Canceled since some of the team members are planning to attend OpenStack Days in Tokyo<br /> <br /> == Agenda (2016-06-29) ==<br /> <br /> * Preparation for Barcelona Summit (TaaS presentation): '''Submission Deadline: Wednesday, 13th, Jul'''<br /> ** Title, Speakers, Abstract: [[Media:Draft_20160629-01.png]]<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-22) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka? http://lists.openstack.org/pipermail/openstack-dev/2016-June/097727.html<br /> * High<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> ** gate blocker https://review.openstack.org/#/c/326231/<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=133257 2016-09-20T07:03:40Z

<p>Yamamoto: /* Bug deputy */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |-<br /> | 2016-08-23 || || x || ||<br /> |-<br /> | 2016-09-20 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-09-20) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-06) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=133256 2016-09-20T06:45:02Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |-<br /> | 2016-08-23 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-09-20) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-09-06) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=131561 2016-08-23T07:05:35Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |-<br /> | 2016-08-23 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-09-06) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=129940 2016-08-09T07:32:11Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-08-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=129939 2016-08-09T07:22:32Z

<p>Yamamoto: /* Bug deputy */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |-<br /> | 2016-08-09 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=129938 2016-08-09T07:00:10Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-08-09) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=127936 2016-07-12T06:35:21Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-07-12) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.2<br /> *** https://blog.midonet.org/midonet-5-2-0-release/<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596414<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1596423<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1600770<br /> * Open Discussion<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=127067 2016-06-21T06:37:25Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> == Agenda (2016-06-22) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka? http://lists.openstack.org/pipermail/openstack-dev/2016-June/097727.html<br /> * High<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> ** gate blocker https://review.openstack.org/#/c/326231/<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=126786 2016-06-15T05:13:03Z

<p>Yamamoto: /* Agenda (2016-06-15) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> ** gate blocker https://review.openstack.org/#/c/326231/<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=126709 2016-06-14T07:42:21Z

<p>Yamamoto: /* Bug deputy */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |-<br /> | 2016-06-14 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=126707 2016-06-14T04:15:55Z

<p>Yamamoto: /* Agenda (2016-06-14) */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate issues<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1591932<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1589876<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1585460<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/ML2&diff=126706 2016-06-14T04:12:50Z

<p>Yamamoto: /* Meeting June 15, 2016 */</p> <hr /> <div>'''Weekly on Wednesdays at 1600 UTC on #openstack-meeting-alt'''<br /> <br /> Tracking ML2 Subgroup Reviews: [https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews here]<br /> <br /> ==Agenda==<br /> <br /> === Meeting June 15, 2016 ===<br /> <br /> * Announcements<br /> <br /> * Open Discussion<br /> ** https://review.openstack.org/#/c/320657/1/neutron/db/ipam_backend_mixin.py &lt;- Should this be fixed? Question from Rossella.<br /> ** driver api &quot;feature requests&quot;<br /> *** https://bugs.launchpad.net/neutron/+bug/1273730 MechanismDriverError hides original exception<br /> *** https://bugs.launchpad.net/neutron/+bug/1583096 ml2 supported extensions list is inaccurate<br /> *** https://bugs.launchpad.net/neutron/+bug/1587401 Helper method to change status of port to abnormal state is needed in ml2.<br /> *** https://bugs.launchpad.net/neutron/+bug/1592238 [RFE] ml2: needs a way for MD to pass data from precommit to postcommit<br /> <br /> === Meeting June 8, 2016 ===<br /> <br /> * Announcements<br /> <br /> * Open Discussion<br /> <br /> === Meeting June 1, 2016 ===<br /> <br /> * Announcements<br /> ** N-1 is *this* week<br /> ** http://releases.openstack.org/newton/schedule.html<br /> <br /> * Manila-ML2 integration <br /> ** https://bugs.launchpad.net/neutron/+bug/1573197<br /> <br /> * Security Groups Discussion<br /> <br /> * Open Discussion<br /> ** Some routed networks stuff (carl_baldwin)<br /> *** https://review.openstack.org/#/c/317358 - Enabling create / delete of segments directly<br /> *** https://review.openstack.org/#/c/321152 - ML2 bug doesn't allow return of IP allocation in port update.<br /> <br /> === Meeting May 25, 2016 ===<br /> <br /> * Today's meeting was cancelled - we will meet next week<br /> <br /> * Announcements<br /> ** N-1 is next week<br /> ** http://releases.openstack.org/newton/schedule.html<br /> <br /> * Manila-ML2 integration <br /> ** https://bugs.launchpad.net/neutron/+bug/1573197<br /> <br /> * Security Groups Discussion<br /> <br /> * Open Discussion<br /> <br /> === Meeting May 18, 2016 ===<br /> <br /> * Announcements<br /> <br /> * Bugs<br /> <br /> * Open Discussion<br /> <br /> === Meeting May 11, 2016 ===<br /> <br /> (carl_baldwin) Will there be a meeting this week? - Yes<br /> <br /> * Announcements<br /> <br /> * Newton charter for ML2 <br /> ** Trunked ports integration with ML2 <br /> ** Integration of Segments service plugin with ML2 (see below)<br /> <br /> * Bugs<br /> ** Missing ML2 config options in config reference: https://bugs.launchpad.net/openstack-manuals/+bug/1567792<br /> <br /> * Open Discussion<br /> ** Some routed networks topics<br /> *** creating and deleting segments on existing network through new segment API<br /> **** Any cases it should be forbidden?<br /> *** Integrating the segments service plugin with ML2<br /> <br /> <br /> === Meeting May 4, 2016 ===<br /> <br /> * Announcements<br /> <br /> * Discussion on the charter for ML2 for Newton<br /> ** Some of the discussion during summit - https://etherpad.openstack.org/p/newton-neutron-unplugged-track<br /> <br /> * Bugs<br /> ** Missing ML2 config options in config reference: https://bugs.launchpad.net/openstack-manuals/+bug/1567792<br /> <br /> * Open Discussion<br /> <br /> === Meeting April 20, 2016 ===<br /> <br /> * Announcements<br /> ** rkukura cannot attend today<br /> ** Austin Summit Next week<br /> ** No meeting next week (4/27)<br /> <br /> * Neutron Austin Design sessions schedule<br /> ** https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Neutron%3A<br /> <br /> * Bugs<br /> ** Missing ML2 config options in config reference: https://bugs.launchpad.net/openstack-manuals/+bug/1567792<br /> <br /> * Open Discussion<br /> ** Nova-Neutron Porbinding Migration issues (+ macvtap migration, cross l2 agent migration) <br /> *** Cannot attend today, so here a brief update (scheuran, 2016-04-13)<br /> *** Started discussion on the ML http://lists.openstack.org/pipermail/openstack-dev/2016-April/092073.html<br /> *** In a lengthy chat with kevinbenton today we agreed to follow up the multiple port binding thing<br /> *** I started rebasing Bobs patches https://review.openstack.org/#/c/189410 - it will take a while, as I'm learning a lot on the way ;)<br /> *** And a BP + spec is required for the API changes that externalize multiple bindings per port, also still TBD<br /> <br /> === Meeting April 13, 2016 ===<br /> <br /> * Announcements<br /> ** Newton is now open for business<br /> ** Networking Guide ML2 section merged: http://docs.openstack.org/mitaka/networking-guide/config-ml2-plug-in.html (scheuran)<br /> <br /> * Neutron Austin Design sessions schedule<br /> ** https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Neutron%3A<br /> <br /> * Bugs<br /> ** Missing ML2 config options in config reference: https://bugs.launchpad.net/openstack-manuals/+bug/1567792<br /> <br /> * Open Discussion<br /> ** Nova-Neutron Porbinding Migration issues (+ macvtap migration, cross l2 agent migration) <br /> *** Cannot attend today, so here a brief update (scheuran, 2016-04-13)<br /> *** Started discussion on the ML http://lists.openstack.org/pipermail/openstack-dev/2016-April/092073.html<br /> *** In a lengthy chat with kevinbenton today we agreed to follow up the multiple port binding thing<br /> *** I started rebasing Bobs patches https://review.openstack.org/#/c/189410 - it will take a while, as I'm learning a lot on the way ;)<br /> *** And a BP + spec is required for the API changes that externalize multiple bindings per port, also still TBD<br /> <br /> === Meeting April 6, 2016 ===<br /> <br /> * Announcements<br /> ** Mitaka release is this week<br /> <br /> * Neutron Austin Design summit Ideas <br /> ** Link - https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> <br /> * port binding discussion on migration (scheuran) - continuation from previous week<br /> <br /> * Open Discussion<br /> <br /> === Meeting March 30, 2016 ===<br /> <br /> * Announcements<br /> ** Mitaka RC2 in the works<br /> <br /> * Neutron Austin Design summit Ideas <br /> ** Link - https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> <br /> * port binding discussion on migration (scheuran)<br /> ** In case distributed ports would be needed, old (currently abandoned, but worth revisiting) effort to cleanup DVR's distributed port implementation as a precursor to generalizing it is here:<br /> *** https://bugs.launchpad.net/neutron/+bug/1367391<br /> *** https://review.openstack.org/#/c/189410/<br /> <br /> * Open Discussion<br /> <br /> === Meeting March 23, 2016 ===<br /> <br /> * Announcements<br /> <br /> * Neutron Austin Design summit Ideas <br /> ** Link - https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> <br /> * port binding discussion on migration (scheuran)<br /> <br /> * Open Discussion<br /> <br /> === Meeting March 16, 2016 ===<br /> <br /> * Announcements<br /> <br /> * Docs ML2 configuration section update<br /> ** Documentation - https://review.openstack.org/#/c/282349<br /> <br /> * Routed networks discussion<br /> ** https://review.openstack.org/#/c/225384/<br /> <br /> * port binding with port owned by router<br /> <br /> * Simulate portbinding on migration target host (scheuran)<br /> ** Use Case: Migration cross l2 agents, migration with macvtap l2 agent --&gt; In both cases nova needs to know the portbinding information that should be used on the migration target before migration has started (in nova pre_live_migration) and before port has been bound. This information is required to trigger the correct vif-plug action on the target and to modify the libvirt domain.xml accordingly<br /> ** Approach: Some new api call is required, which simulates the portbinding for the target host and returns this information<br /> ** This is just as a heads up - I try to come up with more details in the next meeting (23rd of March)<br /> <br /> * Open Discussion<br /> <br /> === Meeting March 9, 2016 ===<br /> <br /> * Announcements<br /> ** rkukura cannot attend today<br /> <br /> * Modular L2 agent update<br /> ** Documentation - https://review.openstack.org/#/c/282349<br /> <br /> * Routed networks discussion<br /> ** https://review.openstack.org/#/c/225384/<br /> <br /> * Open Discussion<br /> <br /> === Meeting March 2, 2016 ===<br /> <br /> * Announcements<br /> ** Mitaka-3 is this week<br /> <br /> * Modular L2 agent update<br /> ** Documentation - https://review.openstack.org/#/c/282349<br /> <br /> * Routed networks discussion<br /> ** https://review.openstack.org/#/c/225384/<br /> <br /> * Open Discussion<br /> <br /> === Meeting February 24, 2016 ===<br /> <br /> * Announcements<br /> ** neutron mid-cycle this week - https://etherpad.openstack.org/p/neutron-mitaka-midcycle<br /> <br /> * Open Agenda - based upon interest<br /> <br /> * Modular L2 agent update<br /> <br /> * Routed networks discussion<br /> ** https://review.openstack.org/#/c/225384/<br /> <br /> * Open Discussion<br /> <br /> <br /> === Meeting February 17, 2016 ===<br /> <br /> * Announcements<br /> ** rkukura on PTO this week<br /> <br /> * Open Agenda - based upon interest<br /> <br /> * limited-portsec implementation<br /> ** https://review.openstack.org/#/c/250036/<br /> <br /> * Modular L2 agent update<br /> <br /> * Routed networks discussion<br /> ** https://review.openstack.org/#/c/225384/<br /> <br /> * Open Discussion<br /> <br /> === Meeting February 10, 2016 ===<br /> <br /> * Announcements<br /> ** Do not forget to vote on sessions for Austin Summit<br /> *** https://www.openstack.org/summit/austin-2016/vote-for-speakers<br /> <br /> * limited-portsec implementation<br /> ** https://review.openstack.org/#/c/250036/<br /> <br /> * Modular L2 agent update<br /> <br /> * Routed networks discussion<br /> ** https://review.openstack.org/#/c/225384/<br /> <br /> * Open Discussion<br /> <br /> === Meeting February 3, 2016 ===<br /> <br /> * Announcements<br /> <br /> * limited-portsec implementation<br /> ** https://review.openstack.org/#/c/250036/<br /> <br /> * Modular L2 agent update<br /> <br /> * Routed networks discussion<br /> ** https://review.openstack.org/#/c/225384/<br /> <br /> * Open Discussion<br /> <br /> === Meeting January 27, 2016 ===<br /> <br /> * Announcements<br /> ** Austin (Newton) Summit session proposal deadline is Monday<br /> *** https://www.openstack.org/summit/austin-2016/call-for-speakers<br /> <br /> * limited-portsec implementation<br /> ** https://review.openstack.org/#/c/250036/<br /> <br /> * Open Discussion<br /> <br /> === Meeting January 20, 2016 ===<br /> <br /> * Announcements<br /> <br /> * Driver API for SecurityGroup <br /> ** https://bugs.launchpad.net/neutron/+bug/1518087<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> <br /> * limited-portsec implementation<br /> ** https://review.openstack.org/#/c/250036/<br /> <br /> * Any topics of interest to ML2 - Open Agenda based upon the interest<br /> * Open Discussion<br /> <br /> <br /> === Meeting January 13, 2016 ===<br /> <br /> * Announcements<br /> ** M2 is next week<br /> <br /> * Driver API for SecurityGroup <br /> ** https://bugs.launchpad.net/neutron/+bug/1518087<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> <br /> * limited-portsec implementation<br /> ** https://review.openstack.org/#/c/250036/<br /> <br /> * Any topics of interest to ML2 - Open Agenda based upon the interest<br /> * Open Discussion<br /> <br /> === Meeting January 6, 2016 ===<br /> * Announcements<br /> ** M2 Mid Jan<br /> <br /> * Driver API for SecurityGroup - good discussion on the bug<br /> ** https://bugs.launchpad.net/neutron/+bug/1518087<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> <br /> * Trunk port binding for VLAN-awere VMs - pretty much ready to go<br /> ** Spec - https://review.openstack.org/#/c/243786/<br /> <br /> * limited-portsec implementation<br /> ** https://review.openstack.org/#/c/250036/<br /> <br /> * Any topics of interest to ML2 - Open Agenda based upon the interest<br /> <br /> * Open Discussion<br /> <br /> === Meeting December 30, 2015 ===<br /> <br /> * No meeting<br /> <br /> === Meeting December 23, 2015 ===<br /> <br /> * No meeting<br /> <br /> === Meeting December 16, 2015 ===<br /> <br /> * Announcements<br /> ** Sukhdev is off for next two weeks, rkukura is off week after next<br /> ** no meeting 12/30<br /> ** quick poll - meet next week (12/23)?<br /> <br /> * Driver API for SecurityGroup - yamamoto<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> ** https://bugs.launchpad.net/neutron/+bug/1518087<br /> <br /> * Driver status coalescing/visibility<br /> ** John Joyce, Isaku Yamahata and Arvind Somya agreed to discuss and create a proposal<br /> <br /> * Trunk port binding for VLAN-awere VMs (and baremetal?)<br /> ** BP: https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms<br /> ** Spec - https://review.openstack.org/#/c/243786/<br /> ** How does port binding work for this?<br /> <br /> * Modular l2 agent &amp; macvtap<br /> ** Update from scheuran (can't attend today 12/09)<br /> ** This patch needs to go in first, then we're ready to do the split of the lb agent: https://review.openstack.org/250542<br /> ** Split of the lb agent: Will be updated after above went in: https://review.openstack.org/#/c/246318/<br /> ** Moving the code to a separate file [WIP] https://review.openstack.org/#/c/248138/<br /> ** Also had a discussion with kevinbenton and ajo if arp spoofing stuff could be modelled as agent extension. Could not convince them, so we agreed to go on with the current design and keep that in the back of our minds for the future.<br /> <br /> * Physical Topology Discussion<br /> ** Update from shivharis<br /> <br /> * limited-portsec Discussion<br /> ** if the limited-portsec depend on port-sec extension, there maybe code in limited-portsec to extend the dict of port-sec.<br /> ** https://review.openstack.org/#/c/250036/ , difficult to handle the dependency in these extensions.<br /> <br /> * Open Discussion<br /> <br /> === Meeting December 9, 2015 ===<br /> <br /> * Announcements<br /> ** Sukhdev is off for next three weeks<br /> <br /> * Driver API for SecurityGroup - yamamoto<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> ** https://bugs.launchpad.net/neutron/+bug/1518087<br /> <br /> * Driver status coalescing/visibility<br /> ** John Joyce, Isaku Yamahata and Arvind Somya agreed to discuss and create a proposal<br /> <br /> * Trunk port binding for VLAN-awere VMs (and baremetal?)<br /> ** BP: https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms<br /> ** Spec - https://review.openstack.org/#/c/243786/<br /> ** How does port binding work for this?<br /> <br /> * Modular l2 agent &amp; macvtap<br /> ** Update from scheuran (can't attend today 12/09)<br /> ** This patch needs to go in first, then we're ready to do the split of the lb agent: https://review.openstack.org/250542<br /> ** Split of the lb agent: Will be updated after above went in: https://review.openstack.org/#/c/246318/<br /> ** Moving the code to a separate file [WIP] https://review.openstack.org/#/c/248138/<br /> ** Also had a discussion with kevinbenton and ajo if arp spoofing stuff could be modelled as agent extension. Could not convince them, so we agreed to go on with the current design and keep that in the back of our minds for the future.<br /> <br /> * Physical Topology Discussion<br /> ** Update from shivharis<br /> <br /> * limited-portsec Discussion<br /> ** if the limited-portsec depend on port-sec extension, there maybe code in limited-portsec to extend the dict of port-sec.<br /> ** https://review.openstack.org/#/c/250036/<br /> <br /> * Open Discussion<br /> ** Discussion on passing network ID to the type drivers - enhancement is needed to three methods as follows:<br /> *** def allocate_tenant_segment(self, session, network_id=None):<br /> *** def reserve_provider_segment(self, session, segment, network_id=None):<br /> *** def release_segment(self, session, segment, network_id=None):<br /> <br /> === Meeting December 2, 2015 ===<br /> * Announcements<br /> <br /> * Driver API for SecurityGroup - yamamoto<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> ** https://bugs.launchpad.net/neutron/+bug/1518087<br /> <br /> * Driver status coalescing/visibility<br /> ** John Joyce, Isaku Yamahata and Arvind Somya agreed to discuss and create a proposal<br /> <br /> * Trunk port binding for VLAN-awere VMs (and baremetal?)<br /> ** BP: https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms<br /> ** Spec - https://review.openstack.org/#/c/243786/<br /> ** How does port binding work for this?<br /> <br /> * Modular l2 agent &amp; macvtap<br /> ** Update from scheuran<br /> ** https://review.openstack.org/#/c/246318/<br /> ** https://review.openstack.org/#/c/248138/<br /> <br /> * Physical Topology Discussion<br /> ** Update from shivharis<br /> <br /> * Open Discussion<br /> <br /> <br /> === Meeting November 25, 2015 ===<br /> * Announcements<br /> ** M1 is due next week<br /> <br /> * Driver API for SecurityGroup - yamamoto<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> <br /> * Driver status coalescing/visibility<br /> ** John Joyce, Isaku Yamahata and Arvind Somya agreed to discuss and create a proposal<br /> <br /> * Trunk port binding for VLAN-awere VMs (and baremetal?)<br /> ** Bence Romsics discussed with ML2 subteam at summit<br /> ** BP: https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms<br /> ** How does port binding work for this?<br /> <br /> * Modular l2 agent &amp; macvtap<br /> ** Update from scheuran<br /> <br /> * Physical Topology Discussion<br /> ** Update from shivharis<br /> <br /> * Open Discussion<br /> <br /> <br /> === Meeting November 18, 2015 ===<br /> * Announcements<br /> ** M1 is due in first week of Dec<br /> <br /> * Driver API for SecurityGroup - yamamoto<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> <br /> * Driver status coalescing/visibility<br /> ** John Joyce, Isaku Yamahata and Arvind Somya agreed to discuss and create a proposal<br /> <br /> * Trunk port binding for VLAN-awere VMs (and baremetal?)<br /> ** Bence Romsics discussed with ML2 subteam at summit<br /> ** BP: https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms<br /> ** How does port binding work for this?<br /> <br /> * Modular l2 agent &amp; macvtap<br /> ** Update from scheuran<br /> <br /> * Physical Topology Discussion<br /> ** Update from shivharis<br /> <br /> * Open Discussion<br /> <br /> <br /> === Meeting November 11, 2015 ===<br /> * Announcements<br /> ** Welcome back from the summit and our week off!<br /> ** Mitaka-1 December 1: https://launchpad.net/neutron/+milestone/mitaka-1<br /> <br /> * Mitaka Design Summit recap<br /> ** Etherpads: https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Neutron<br /> <br /> * Driver API for SecurityGroup - yamamoto<br /> ** spec review: https://review.openstack.org/#/c/240356/<br /> <br /> * Driver status coalescing/visibility<br /> ** John Joyce, Isaku Yamahata and Arvind Somya agreed to discuss and create a proposal<br /> <br /> * Trunk port binding for VLAN-awere VMs (and baremetal?)<br /> ** Bence Romsics discussed with ML2 subteam at summit<br /> ** BP: https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms<br /> ** How does port binding work for this?<br /> <br /> * Modular l2 agent &amp; macvtap<br /> ** Update from scheuran<br /> <br /> * Physical Topology Discussion<br /> ** Update from shivharis<br /> <br /> * Open Discussion<br /> <br /> === Meeting October 21, 2015 ===<br /> * Announcements<br /> ** Mitaka summit is next week<br /> ** No ML2 IRC meeting during summit<br /> <br /> * Mitaka Design Summit<br /> ** Neutron Design Summit schedule - https://www.openstack.org/summit/tokyo-2015/schedule/design-summit<br /> <br /> * ML2 pre-cycle sprint recap<br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> ** email summaries - TBD<br /> <br /> * Driver API for SecurityGroup - yamamoto<br /> ** problems<br /> *** it currently assumes RPC+agent based implementation<br /> *** no sane way for mech drivers to hook SG operations like create_security_group<br /> ** the existing practice: use callbacks<br /> *** eg. https://github.com/openstack/networking-midonet/blob/master/midonet/neutron/ml2/sg_callback.py<br /> *** works but ugly<br /> ** bug: https://bugs.launchpad.net/neutron/+bug/1444112<br /> <br /> * Modular l2 agent &amp; macvtap<br /> ** Update from scheuran<br /> ** sc68cal and scheuran are refactoring the lb agent to look more like ovs and transforming it to a plugable interface (that can take both, lb and macvtap)<br /> ** see https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z<br /> <br /> * Physical Topology Discussion<br /> ** Update from shivharis<br /> <br /> * Open Discussion<br /> <br /> === Meeting October 14, 2015 ===<br /> <br /> * Meeting cancelled due to low attendance<br /> <br /> === Meeting October 7, 2015 ===<br /> <br /> * No meeting - ML2 pre-cycle sprint<br /> <br /> === Meeting Sept 30, 2015 ===<br /> * Announcements<br /> ** Neutron has a new PTL for Mitaka - congratulations to armax and many thanks to mestery!<br /> ** ML2 pre-cycle sprint is next week<br /> ** No ML2 IRC meeting next week<br /> <br /> * ML2 pre-cycle sprint<br /> ** Sprint announcement - http://lists.openstack.org/pipermail/openstack-dev/2015-September/073927.html<br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> ** Logistics<br /> ** Prep<br /> <br /> * Mitaka Design Summit proposals for ML2 - discussion <br /> ** Neutron Mitaka Design Summit proposals - https://etherpad.openstack.org/p/neutron-mitaka-designsummit<br /> <br /> * Driver API for SecurityGroup - yamamoto<br /> ** problems<br /> *** it currently assumes RPC+agent based implementation<br /> *** no sane way for mech drivers to hook SG operations like create_security_group<br /> ** the existing practice: use callbacks<br /> *** eg. https://github.com/openstack/networking-midonet/blob/master/midonet/neutron/ml2/sg_callback.py<br /> *** works but ugly<br /> ** bug: https://bugs.launchpad.net/neutron/+bug/1444112<br /> <br /> * Modular l2 agent &amp; macvtap<br /> ** I (scheuran) will not join todays meeting, so here a short update:<br /> ** sc68cal and scheuran are refactoring the lb agent to look more like ovs and transforming it to a plugable interface (that can take both, lb and macvtap)<br /> ** see https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z<br /> ** I (scheuran) will be out a for a few weeks, so you won't see much process until midst of September<br /> <br /> * Physical Topology Discussion<br /> ** Update from shivharis<br /> <br /> * Open Discussion<br /> <br /> === Meeting Sept 23, 2015 ===<br /> * Announcements<br /> ** Liberty RC1 contents - https://launchpad.net/neutron/+milestone/liberty-rc1<br /> ** PTL election is this week - https://wiki.openstack.org/wiki/PTL_Elections_September_2015<br /> <br /> * ML2 late-cycle plan<br /> ** Sprint announcement - http://lists.openstack.org/pipermail/openstack-dev/2015-September/073927.html<br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * Mitaka Design Summit proposals for ML2 - discussion <br /> ** Nutron Mitaka Design Summit proposals - https://etherpad.openstack.org/p/neutron-mitaka-designsummit<br /> <br /> * driver API for SecurityGroup - yamamoto<br /> ** problems<br /> *** it currently assumes RPC+agent based implementation<br /> *** no sane way for mech drivers to hook SG operations like create_security_group<br /> ** the existing practice: use callbacks<br /> *** eg. https://github.com/openstack/networking-midonet/blob/master/midonet/neutron/ml2/sg_callback.py<br /> *** works but ugly<br /> ** bug: https://bugs.launchpad.net/neutron/+bug/1444112<br /> <br /> * modular l2 agent &amp; macvtap<br /> ** I (scheuran) will not join todays meeting, so here a short update:<br /> ** sc68cal and scheuran are refactoring the lb agent to look more like ovs and transforming it to a plugable interface (that can take both, lb and macvtap)<br /> ** see https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z<br /> ** I (scheuran) will be out a for a few weeks, so you won't see much process until midst of September<br /> <br /> * Physical Topology Discussion<br /> <br /> * Open Discussion<br /> <br /> === Meeting Sept 16, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty RC1 contents - https://launchpad.net/neutron/+milestone/liberty-rc1<br /> <br /> * ML2 late-cycle plan<br /> ** Sprint announcement - http://lists.openstack.org/pipermail/openstack-dev/2015-September/073927.html<br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * Mitaka Design Summit proposals for ML2 - discussion <br /> ** Nutron Mitaka Design Summit proposals - https://etherpad.openstack.org/p/neutron-mitaka-designsummit<br /> <br /> * driver API for SecurityGroup - yamamoto<br /> ** problems<br /> *** it currently assumes RPC+agent based implementation<br /> *** no sane way for mech drivers to hook SG operations like create_security_group<br /> ** the existing practice: use callbacks<br /> *** eg. https://github.com/openstack/networking-midonet/blob/master/midonet/neutron/ml2/sg_callback.py<br /> *** works but ugly<br /> ** bug: https://bugs.launchpad.net/neutron/+bug/1444112<br /> <br /> * modular l2 agent &amp; macvtap<br /> ** I (scheuran) will not join todays meeting, so here a short update:<br /> ** sc68cal and scheuran are refactoring the lb agent to look more like ovs and transforming it to a plugable interface (that can take both, lb and macvtap)<br /> ** see https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z<br /> ** I (scheuran) will be out a for a few weeks, so you won't see much process until midst of September<br /> <br /> * Physical Topology Discussion<br /> <br /> * Open Discussion<br /> <br /> === Meeting Sept 9, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty-3 contents - https://launchpad.net/neutron/+milestone/liberty-3<br /> ** Liberty RC1 contents - https://launchpad.net/neutron/+milestone/liberty-rc1<br /> <br /> * ML2 late-cycle plan<br /> ** Sprint announcement - http://lists.openstack.org/pipermail/openstack-dev/2015-September/073927.html<br /> <br /> * Mitaka Design Summit proposals for ML2 - discussion <br /> ** Brainstorm ideas for the Mitaka ML2 design summit ideas<br /> ** Nutron Mitaka Design Summit proposals - https://etherpad.openstack.org/p/neutron-mitaka-designsummit<br /> <br /> * driver API for SecurityGroup - yamamoto<br /> ** problems<br /> *** it currently assumes RPC+agent based implementation<br /> *** no sane way for mech drivers to hook SG operations like create_security_group<br /> ** the existing practice: use callbacks<br /> *** eg. https://github.com/openstack/networking-midonet/blob/master/midonet/neutron/ml2/sg_callback.py<br /> *** works but ugly<br /> ** bug: https://bugs.launchpad.net/neutron/+bug/1444112<br /> <br /> * modular l2 agent &amp; macvtap<br /> ** I (scheuran) will not join todays meeting, so here a short update:<br /> ** sc68cal and scheuran are refactoring the lb agent to look more like ovs and transforming it to a plugable interface (that can take both, lb and macvtap)<br /> ** see https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z<br /> ** I (scheuran) will be out a for a few weeks, so you won't see much process until midst of September<br /> <br /> * Physical Topology Discussion<br /> <br /> * Open Discussion<br /> <br /> === Meeting Sept 2, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty FF is this week (or early next week)<br /> <br /> * ML2 late-cycle plan<br /> ** Meeting will take place in the week of 10/5. The host is Yahoo (tentative) <br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> ** Task Flow Document<br /> *** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * driver API for SecurityGroup - Do we want to come up with a plan for Design session in Tokyo for this? <br /> ** problems<br /> *** it currently assumes RPC+agent based implementation<br /> *** no sane way for mech drivers to hook SG operations like create_security_group<br /> ** the existing practice: use callbacks<br /> *** eg. https://github.com/openstack/networking-midonet/blob/master/midonet/neutron/ml2/sg_callback.py<br /> *** works but ugly<br /> ** bug: https://bugs.launchpad.net/neutron/+bug/1444112<br /> <br /> * modular l2 agent &amp; macvtap<br /> ** I (scheuran) will not join todays meeting, so here a short update:<br /> ** sc68cal and scheuran are refactoring the lb agent to look more like ovs and transforming it to a plugable interface (that can take both, lb and macvtap)<br /> ** see https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z<br /> ** I (scheuran) will be out a for a few weeks, so you won't see much process until midst of September<br /> <br /> * Physical Topology Discussion<br /> <br /> * Open Discussion<br /> <br /> === Meeting August 26, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty FF is next week<br /> <br /> * Action Items from previous weeks:<br /> ** rkukura to work with others to finalize the venue for the ML2 late-cycle sprint<br /> <br /> * ML2 late-cycle plan<br /> ** Meeting will take place in the week of 10/5. The host is TBD. <br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * driver API for SecurityGroup<br /> ** problems<br /> *** it currently assumes RPC+agent based implementation<br /> *** no sane way for mech drivers to hook SG operations like create_security_group<br /> ** the existing practice: use callbacks<br /> *** eg. https://github.com/openstack/networking-midonet/blob/master/midonet/neutron/ml2/sg_callback.py<br /> *** works but ugly<br /> ** bug: https://bugs.launchpad.net/neutron/+bug/1444112<br /> <br /> * Physical Topology Discussion<br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * modular l2 agent &amp; macvtap<br /> ** I (scheuran) will not join todays meeting, so here a short update:<br /> ** sc68cal and scheuran are refactoring the lb agent to look more like ovs and transforming it to a plugable interface (that can take both, lb and macvtap)<br /> ** see https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z<br /> ** I (scheuran) will be out a for a few weeks, so you won't see much process until midst of September<br /> <br /> * Open Discussion<br /> <br /> === Meeting August 19, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty FF is two weeks away<br /> <br /> * Action Items from previous weeks:<br /> ** rkukura and Sukhdev to re-organize weekly meeting agenda around goals for upcoming Mitaka cycle as well as anything needed to wrap up for liberty<br /> ** rkukura to work with others to finalize the venue for the ML2 late-cycle sprint<br /> <br /> * ML2 late-cycle plan<br /> ** Meeting will take place in the week of 10/5. The host is TBD. <br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * L3 Blueprints - https://launchpad.net/neutron/+milestone/liberty-3<br /> ** couple of Blueprints may be of interest to ML2 team<br /> <br /> * Physical Topology Discussion<br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * driver API for SecurityGroup<br /> ** problems<br /> *** it currently assumes RPC+agent based implementation<br /> *** no sane way for mech drivers to hook SG operations like create_security_group<br /> ** the existing practice: use callbacks<br /> *** eg. https://github.com/openstack/networking-midonet/blob/master/midonet/neutron/ml2/sg_callback.py<br /> *** works but ugly<br /> ** bug: https://bugs.launchpad.net/neutron/+bug/1444112<br /> <br /> * modular l2 agent &amp; macvtap<br /> ** I (scheuran) will not join todays meeting, so here a short update:<br /> ** sc68cal and scheuran are refactoring the lb agent to look more like ovs and transforming it to a plugable interface (that can take both, lb and macvtap)<br /> ** see https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1468803,n,z<br /> ** I (scheuran) will be out a for a few weeks, so you won't see much process until midst of September<br /> <br /> <br /> * Open Discussion<br /> <br /> === Meeting August 12, 2015 ===<br /> <br /> * Announcements<br /> <br /> * ML2 late-cycle plan<br /> ** Meeting will take place in the week of 10/5. The host is TBD. <br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * L3 Blueprints - https://launchpad.net/neutron/+milestone/liberty-3<br /> ** couple of Blueprints may be of interest to ML2 team<br /> <br /> * L2 Modular Agent discussion<br /> ** macvtap agent and ML2 discussion. Feel free to express your opinion - http://lists.openstack.org/pipermail/openstack-dev/2015-August/071207.html<br /> <br /> * Physical Topology Discussion<br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> <br /> === Meeting August 5, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty FF is end of August<br /> <br /> * ML2 late-cycle plan<br /> ** Meeting will take place in the week of 10/5. The host is TBD. <br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * L3 Blueprints - https://launchpad.net/neutron/+milestone/liberty-3<br /> ** couple of Blueprints may be of interest to ML2 team<br /> <br /> * L2 Modular Agent discussion<br /> ** macvtap agent and ML2 discussion. Feel free to express your openion - http://lists.openstack.org/pipermail/openstack-dev/2015-August/071207.html<br /> <br /> * Physical Topology Discussion<br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> <br /> === Meeting July 29, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty-2 is this week<br /> ** Liberty-3 is end of August<br /> <br /> * ML2 late-cycle plan<br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * L2 Modular Agent discussion<br /> <br /> * Place for Macvtap agent (scheuran) - Putting this right after l2-agent, as it is related to it<br /> ** Planning a ml2 driver + l2 agent for macvtap attachments (independent from sriov). But where should it land?<br /> *** 1) own openstack repo networking-macvtap (already some discussion there: https://review.openstack.org/#/c/195907/)<br /> *** 2) in neutron tree as new reference, own agent (duplicating code)<br /> *** 3) In neutron tree, Integrated into linuxbridge agent (reusing about 500 lines of code, mostly main loop, detecting new devices,...); Extracting superclass out of linuxbridge agent that can be subclassed. Having config option to either run agent in lb or in macvtap mode. fully functional prototype (macvtap stuff tested): https://github.com/scheuran/networking-macvtap/commit/36a068cf3d3d6930ab9330efb099cd95a84ca785<br /> *** 4) modular l2 agent, but as long it is being discussed go with #1<br /> *** 5) Prototyping modular layer 2 agent ( #a in separate repo vs. #b together with lb)<br /> ** Anyhow there will be a separate ml2 driver which will either land in tree or in the networking-macvtap repo<br /> ** Spec on github (assuming it will land in a separate repo): https://github.com/scheuran/networking-macvtap/commit/bc239419398ec039da35ec949a14691280733bf6<br /> ** Has been discussed in yesterdays neutron meeting where I was asked to evaluate agent-extension used for qos - but that can not be used: http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-07-28-14.01.log.html<br /> <br /> <br /> * Physical Topology Discussion<br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> ** request for patch review:<br /> *** https://review.openstack.org/#/c/202357/ l3_db: it updates port attribute without L2 plugin<br /> *** https://review.openstack.org/#/c/202358/ l3_db: not use L2 plugin _get_port unnecessarily<br /> *** https://review.openstack.org/#/c/202359/ l3: not use L2 plugin _get_subnet unnecessarily<br /> <br /> === Meeting July 22, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty-2 is next week<br /> **Liberty Release Schedule - https://wiki.openstack.org/wiki/Liberty_Release_Schedule<br /> <br /> * Action Items<br /> ** rkukura to finalize the plan for ML2 sprint<br /> *** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * L2 Modular Agent discussion<br /> * Physical Topology Discussion<br /> * Ironic/Neutron-ML2 integration discussion<br /> ** https://wiki.openstack.org/wiki/Meetings/Ironic-neutron<br /> <br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> <br /> === Meeting July 15, 2015 ===<br /> <br /> * Announcements<br /> ** Liberty-2 is fast approaching - end of July<br /> **Liberty Release Schedule - https://wiki.openstack.org/wiki/Liberty_Release_Schedule<br /> <br /> * Action Items<br /> ** rkukura to finalize the plan for ML2 sprint<br /> *** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> * L2 Modular Agent discussion<br /> * Physical Topology Discussion<br /> * Ironic/Neutron-ML2 integration discussion<br /> ** https://wiki.openstack.org/wiki/Meetings/Ironic-neutron<br /> ** ML2 based test framework for Ironic - call for discussion/Ideas<br /> <br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> <br /> === Meeting July 8, 2015 ===<br /> <br /> * Announcements<br /> <br /> * Action Items<br /> ** rkukura and manishg to finalize the ML2 sprint plans and put together an etherpad for sprint<br /> *** Etherpad started: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> ** asomya and shivharis to add Physical Topology to the ML2 charter for Liberty<br /> <br /> * ML2 Mid-cycle sprint - decide on the date <br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> <br /> ** Following participants are available - please add your name, if you can participate<br /> *** Sukhdev K<br /> *** Bob K<br /> *** Arvind S<br /> *** Manish G<br /> *** Kevin B<br /> *** Josh <br /> * L2 Modular Agent discussion<br /> * Physical Topology Discussion<br /> * Ironic/Neutron-ML2 integration discussion<br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> <br /> === Meeting July 1, 2015 ===<br /> <br /> * Announcements<br /> <br /> * Action Items<br /> ** rkukura and manishg to finalize the ML2 sprint plans and put together an etherpad for sprint<br /> *** Etherpad started: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> ** banix to discuss Modular L2 agents topic in Neutron core team and drive the priority<br /> ** asomya and shivharis to add Physical Topology to the ML2 charter for Liberty<br /> <br /> * Neutron Mid-cycle sprint recap (Sukhdev)<br /> <br /> * ML2 Mid-cycle sprint<br /> ** Etherpad: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint<br /> ** July 13-17 seems like the earliest possible week<br /> ** Following participants are available - please add your name, if you can participate<br /> *** Sukhdev K<br /> *** Bob K<br /> *** Arvind S<br /> *** Manish G<br /> *** Josh <br /> ** Task Flow Document<br /> *** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Discussion on binding_profile_type to facilitate filtering of Ironic ports or using device_owner (Sukhdev)<br /> <br /> * Open Discussion<br /> <br /> === Meeting June 24, 2015 ===<br /> <br /> * No meeting - Neutron mid-cycle sprint<br /> <br /> === Meeting June 17, 2015 ===<br /> <br /> * Announcements<br /> ** VLAN aware VMs meeting 6-15-2015<br /> *** https://etherpad.openstack.org/p/YVR-neutron-vlan-trunk<br /> <br /> * Action Items<br /> ** banix to discuss Modular L2 agents topic in Neutron core team and drive the priority<br /> ** asomya and shivharis to add Physical Topology to the ML2 charter for Liberty<br /> ** manishg to propose two or three time slots for mid-cycle sprint for task flow<br /> *** Proposing a few dates here (we will probably need 2 days but just proposing a range)<br /> **** Jul/8 - Jul/10<br /> **** Jul/13 - Jul/15<br /> **** Sep/9 - Sep/11<br /> **** Sep/16 - Sep/18<br /> **** Sep/23 - Sep/25<br /> <br /> * Neutron Mid-Cycle Sprint Discussion <br /> ** https://etherpad.openstack.org/p/neutron-liberty-mid-cycle <br /> *** July 13-17 seems like the earliest possible week<br /> ** Following participants are available - please add your name, if you can participate<br /> *** Sukhdev K<br /> *** Bob K<br /> *** Manish G<br /> *** Josh <br /> <br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> === Meeting June 10, 2015 ===<br /> *Absence: <br /> ** banix. I will be away. Will follow up on my AI by next week.<br /> <br /> * Announcements<br /> ** New RFE process - to be followed after Liberty 1<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> ** Core-vendor decomp - Phase II<br /> *** https://review.openstack.org/#/c/187267<br /> <br /> * Action Items<br /> ** rkukura to discuss with QoS implications with ajo on ML2<br /> ** banix to discuss Modular L2 agents topic in Neutron core team and drive the priority<br /> ** asomya and shivharis to add Physical Topology to the ML2 charter for Liberty<br /> ** manishg to propose two or three time slots for mid-cycle sprint for task flow<br /> *** Proposing a few dates here (we will probably need 2 days but just proposing a range)<br /> **** Jul/8 - Jul/10<br /> **** Jul/13 - Jul/15<br /> **** Sep/9 - Sep/11<br /> **** Sep/16 - Sep/18<br /> **** Sep/23 - Sep/25<br /> <br /> * Neutron Mid-Cycle Sprint Discussion <br /> ** I have removed Task Flow item from etherpad for Ft. Collins mid-cycle. <br /> ** https://etherpad.openstack.org/p/neutron-liberty-mid-cycle <br /> ** Discussion on the time frame that works for people to have an ML2 mid-cycle in the Bay Area<br /> *** July 13-17 seems like the earliest possible week<br /> ** Following participants are available - please add your name, if you can participate<br /> *** Sukhdev K<br /> *** Bob K<br /> *** Manish G<br /> *** Josh <br /> <br /> * Task Flow Document<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> <br /> === Meeting June 3, 2015 ===<br /> <br /> * Announcements<br /> ** Ironic-Neutron integration weekly meetings was kicked off this week - Lots of interest in this topic . Anybody interested in this topic, please join us next week and every week after that.<br /> *** https://wiki.openstack.org/wiki/Meetings/Ironic-neutron<br /> ** New Spec process<br /> *** https://github.com/openstack/neutron/blob/master/doc/source/policies/blueprints.rst<br /> ** Core-vendor decomp - Phase II<br /> *** https://review.openstack.org/#/c/187267<br /> <br /> * Charter of ML2 sub-team for Liberty Cycle<br /> ** Task Flow<br /> ** Decomposition phase -2<br /> <br /> * Neutron Mid-Cycle Sprint Discussion <br /> ** Key players for the Task Flow can not make the sprint. Possibilities are to hold mid-cycle sprint in Bay Area. Who is interested? Who can make it? <br /> ** https://etherpad.openstack.org/p/neutron-liberty-mid-cycle <br /> <br /> * Task Flow Discussion<br /> ** We lost opportunity to discuss it in Vancouver<br /> ** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> <br /> * Open Discussion<br /> <br /> === Meeting May 27, 2015 ===<br /> <br /> * No meeting - recovering from summit<br /> <br /> === Meeting May 20, 2015 ===<br /> <br /> * No meeting - Liberty Summit<br /> <br /> === Meeting May 13, 2015 ===<br /> <br /> *Announcements<br /> ** No meeting next two weeks. Next week everybody is at summit, following week to recover from travels<br /> <br /> *Task Flow Discussion<br /> *** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> *** midonet plugin (not done - will take care of it this week) (manishg)<br /> <br /> *Liberty Design Summit Discussion<br /> **https://wiki.openstack.org/wiki/Summit/Liberty/Etherpads#Neutron<br /> ** Contributor Meetup Friday (at Summit): https://etherpad.openstack.org/p/YVR-neutron-contributor-meetup<br /> <br /> *ML2 on Neutron Mid-Cycle Sprint <br /> **https://etherpad.openstack.org/p/neutron-liberty-mid-cycle (see item 4)<br /> <br /> * Liberty BP<br /> ** converting address-pair and security-group into extension driver. <br /> *** https://review.openstack.org/#/c/169223/3/specs/liberty/ml2-extension-driver-convert.rst<br /> <br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> * Open Discussion<br /> <br /> ** Discussion on Port to network relationship - N:M relationship - is it allowed in our current design? <br /> *** Can one port attach to multiple networks? <br /> *** Can a (v)NIC attach to multiple networks? <br /> *** Can one network attach to multiple ports of same instance/node?<br /> <br /> === Meeting May 6, 2015 ===<br /> <br /> *Announcements<br /> ** Kilo was released last week - congratulations to everybody<br /> <br /> *Task Flow Discussion<br /> *** https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document<br /> *** midonet plugin (not done - will take care of it this week) (manishg)<br /> <br /> *Liberty Design Summit Discussion<br /> **https://wiki.openstack.org/wiki/Summit/Liberty/Etherpads#Neutron<br /> **ML2 topics are in Fishbowl room discussions - lets update it<br /> **Lightening talks are here - http://libertydesignsummit.sched.org/event/213da02952470483dfd8b2765aa88485#.VUmpcGRVhHw<br /> <br /> *ML2 on Neutron Mid-Cycle Sprint <br /> **https://etherpad.openstack.org/p/neutron-liberty-mid-cycle (see item 4)<br /> <br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> * Open Discussion<br /> === Meeting April 29, 2015 ===<br /> *Announcements<br /> ** Kilo RC3 is due any day<br /> ** Starting with Liberty Spec process for new features is being abandoned in favor of light weight RFE is being implemented<br /> ***https://review.openstack.org/#/c/177342/<br /> ** Changes to Driver team - Doug and Maru replacing Salvatore and Mark <br /> <br /> *Action Items from Last week<br /> **manishg to document task flow discussions and look into the midonet plugin<br /> *** [https://docs.google.com/document/d/1aSgTVB7nW_v7lHH0Z0DUgfymEsx0O16k1Jgu7QFXkFA/edit?usp=sharing document] (manishg)<br /> *** midonet plugin (not done - will take care of it this week) (manishg)<br /> <br /> *Ironic (bare metal) integration through ML2 Mech Drivers (discussion)<br /> **There is a tremendous interest by many vendors, as well as Ironic team for this. I have requested a summit session for this. see item 63 on etherpad<br /> **https://etherpad.openstack.org/p/liberty-neutron-summit-topics<br /> <br /> *ML2 on Neutron Mid-Cycle Sprint <br /> **https://etherpad.openstack.org/p/neutron-liberty-mid-cycle (see item 4)<br /> <br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> * Open Discussion<br /> <br /> === Meeting April 22, 2015 ===<br /> *Announcements<br /> ** Kilo RC2 is due any day<br /> ** Networking Guide Doc Day Sprint it tomorrow. Please contact Edgar, if you want to participate/contribute<br /> *** Here is agenda for the sprint - https://etherpad.openstack.org/p/networking-guide<br /> <br /> *Action Items from Last week<br /> **Sukhdev to discuss with mestery about task flow during mid-cycle sprint<br /> **Document the discussion point related to ML2 Sync (Manish)<br /> **shivharis to find the information about release notes for Kilo and share with the team<br /> ***https://wiki.openstack.org/wiki/ReleaseNotes/Kilo<br /> <br /> *ML2 on Neutron Mid-Cycle Sprint <br /> **https://etherpad.openstack.org/p/neutron-liberty-mid-cycle (see item 4)<br /> <br /> * ML2 summit sessions<br /> ** Design summit session etherpad: https://etherpad.openstack.org/p/liberty-neutron-summit-topics<br /> <br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> * Open Discussion<br /> <br /> === Meeting April 15, 2015 ===<br /> *Announcements<br /> ** Absence: Manish (Jury Duty)<br /> ** Absence next week: rkukura (PTO - college tour)<br /> ** Kilo RC is out<br /> <br /> *Action Items from Last week<br /> **Add next steps for the Drivers decomposition to summit topic etherpad - shivharis<br /> **shivharis to find the information about release notes for Kilo and share with the team<br /> **rkukura and Sukhdev to discuss with mestery about task flow during mid-cycle sprint<br /> **Document the discussion point related to ML2 Sync (Manish)<br /> <br /> * Finalize recommendations to mestery on ML2 summit sessions<br /> ** Design summit session etherpad: https://etherpad.openstack.org/p/liberty-neutron-summit-topics<br /> <br /> * Quick update on DVR UT/fix/cleanup work (rkukura)<br /> <br /> * portsecurity tests: unit, functional and scenario<br /> <br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> * Open Discussion<br /> <br /> === Meeting April 8, 2015 ===<br /> <br /> *Announcements<br /> ** RC's are April 9-23 and Kilo release on April 30<br /> ** Liberty mid-cycle sprint announced. <br /> *** June 24-26 in Fort Collins, CO (at HP)<br /> *** Topics to be decided after Vancouver summit - https://etherpad.openstack.org/p/neutron-liberty-mid-cycle<br /> <br /> *Action Items from Last week<br /> **Add next steps for the Drivers decomposition to summit topic etherpad - shivharis<br /> *** Design summit session etherpad: https://etherpad.openstack.org/p/liberty-neutron-summit-topics<br /> **ML2 sync and error handling to summit topic etherpad (rkukura)<br /> **Document the discussion point related to ML2 Sync (Manish)<br /> <br /> * Mechanism drivers and DVR discussion (rkukura)<br /> ** Have made good (but slow) progress on DVR port binding schema and logic cleanup<br /> *** https://bugs.launchpad.net/neutron/+bug/1367391<br /> *** Will miss kilo, hopefully merge early in liberty, cannot back-port to kilo due to schema changes<br /> ** Discovered no current unit tests cover critical DVR port binding logic, so adding them as separate patch against current code, then will ensure they don't break in dependent cleanup patch<br /> *** Extending test_port_binding to exercise update_dvr_port_binding, get_device_details, etc. for DVR ports, utilizing existing PortContext state asserts in mechanism_test MD<br /> *** Hoped to get at least the new UTs into kilo, but probably too late, but can back-port to kilo<br /> ** Discovered several issues (inconsistencies in per-host vs. host-independent state in PortContext) that would seem to break ToR switch MDs that need to track binding state per host:<br /> *** When committing DVR port binding, PortContext passed to update_port methods has new binding:vif_type and binding:vif_details for the bound host, but shows 'distributed' for previous binding:vif_type instead of 'unbound' like for normal ports, and empty strings for current or previous binding:host_id - propose to make these work like for non-DVR ports<br /> *** When updating DVR port's status, PortContext currently shows 'distributed' for binding:vif_type and empty string for host, but has binding_levels, etc., for the specific host - could change this to reflect host-specific state, or to only be called when port's status changes and reflect non-host-specific state<br /> ** Issues to discuss<br /> *** Has anyone tested their MDs with DVR?<br /> *** Has anyone run into these (or other) issues?<br /> *** Is back-porting these sorts of behavioral fixes to kilo acceptable?<br /> *** Do we have consensus on making update_port methods reflect per-host state when committing DVR port binding?<br /> *** Do we prefer to make update_port methods reflect per-host state or only host-independent state when changing DVR port status, or do we need separate updates for each?<br /> <br /> * ML2 Drivers decomposition discussion<br /> **https://github.com/openstack/neutron/blob/master/doc/source/devref/contribute.rst#how-to<br /> <br /> * ML2 Sync and error handling (Task Flow)<br /> **https://review.openstack.org/#/c/154333/<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> === Meeting April 1, 2015 ===<br /> <br /> *Announcements<br /> ** RC's are April 9-23 and Kilo release on April 30<br /> ** Design summit session etherpad: https://etherpad.openstack.org/p/liberty-neutron-summit-topics<br /> *Action Items from Last week<br /> **Document the discussion point related to ML2 Sync (Manish)<br /> **Create an etherpad for driver decomposition discussion at Vancouver Summit<br /> * ML2 Drivers decomposition discussion<br /> **https://github.com/openstack/neutron/blob/master/doc/source/devref/contribute.rst#how-to<br /> * ML2 Sync and error handling (Task Flow)<br /> **https://review.openstack.org/#/c/154333/<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> === Meeting March 25, 2015 ===<br /> <br /> *Announcements<br /> ** RC's are April 9-23 and Kilo release on April 30<br /> ** RC1 content is here - https://launchpad.net/neutron/+milestone/kilo-rc1<br /> * ML2 Drivers decomposition discussion<br /> **https://github.com/openstack/neutron/blob/master/doc/source/devref/contribute.rst#how-to<br /> * ML2 Sync and error handling (Task Flow)<br /> **https://review.openstack.org/#/c/154333/<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> === Meeting March 18, 2015 ===<br /> <br /> *Announcements<br /> **L2 Gateway API is ready for consumption by everybody. Give it a test drive and provide feedback to the team. <br /> **See wiki here - https://wiki.openstack.org/wiki/Neutron/L2-GW<br /> ** K3 content is here - https://launchpad.net/neutron/+milestone/kilo-3<br /> * ML2 Drivers decomposition discussion<br /> **https://github.com/openstack/neutron/blob/master/doc/source/devref/contribute.rst#how-to<br /> * ML2 Sync and error handling (Task Flow)<br /> **https://review.openstack.org/#/c/154333/<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> <br /> === Meeting March 11, 2015 ===<br /> <br /> *Announcements<br /> * ML2 Drivers decomposition discussion<br /> **https://github.com/openstack/neutron/blob/master/doc/source/devref/contribute.rst#how-to<br /> * ML2 Sync and error handling (Task Flow)<br /> **https://review.openstack.org/#/c/154333/<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> <br /> <br /> === Meeting March 4, 2015 ===<br /> <br /> *Announcements<br /> ** Kilo Feature Freeze is tomorrow (March 5th)<br /> * ML2 Drivers decomposition discussion<br /> **https://github.com/openstack/neutron/blob/master/doc/source/devref/contribute.rst#how-to<br /> * ML2 Sync and error handling (Task Flow)<br /> **https://review.openstack.org/#/c/154333/<br /> * portsecurity patches<br /> ** https://review.openstack.org/#/c/126552/<br /> ** https://review.openstack.org/#/c/160051/<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron/+bug/1328991<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> === Meeting February 25, 2015 ===<br /> <br /> *Announcements<br /> ** shivharis: under the weather<br /> * ML2 Drivers decomposition discussion<br /> ** How are distributions packaging decomposed drivers?<br /> * ML2 Sync and error handling (Task Flow)<br /> **https://review.openstack.org/#/c/154333/<br /> *Few BPs being worked on may have impact on ML2 <br /> **https://blueprints.launchpad.net/neutron/+spec/nfv-vlan-trunks<br /> **https://blueprints.launchpad.net/neutron/+spec/restructure-l2-agent<br /> * ML2 Extension Driver API enhancements <br /> ** https://review.openstack.org/#/c/152759/ - ready to merge<br /> ** https://review.openstack.org/#/c/129178/ - coming along well<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> === Meeting February 18, 2015 ===<br /> <br /> *Announcements<br /> * ML2 Drivers decomposition discussion<br /> ** How are distributions packaging decomposed drivers?<br /> * ML2 Sync and error handling (Task Flow)<br /> * ML2 Extension Driver API enhancements<br /> ** Needed for PortSecurity extension driver<br /> ** https://review.openstack.org/#/c/152759/<br /> ** https://review.openstack.org/#/c/129178/<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> === Meeting February 11, 2015 ===<br /> <br /> *Announcements<br /> **K2 is already out<br /> **Feature proposal freeze for Kilo is March 5<br /> * ML2 Drivers decomposition discussion<br /> * ML2 Sync and error handling (Task Flow) - Follow on from previous week (manishg)<br /> ** PoC: https://review.openstack.org/#/c/154333/<br /> * ML2 Extension Driver API enhancements<br /> ** Needed for PortSecurity extension driver<br /> ** https://review.openstack.org/#/c/152759/<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> === Meeting February 4, 2015 ===<br /> <br /> *Announcements<br /> **Kilo-2 is this week week<br /> *** https://launchpad.net/neutron/+milestone/kilo-2<br /> * ML2 Drivers decomposition discussion<br /> * ML2 Sync and error handling (Task Flow) - manishg<br /> * Blueprint list consolidation - updated link is here: <br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Open Discussion<br /> <br /> === Meeting January 28, 2015 ===<br /> <br /> *Announcements<br /> **Kilo-2 is next week<br /> *** https://launchpad.net/neutron/+milestone/kilo-2<br /> * ML2 Drivers decomposition discussion<br /> * ML2 Sync and error handling (Task Flow) - update manishg<br /> * Blueprint list consolidation (shivharis and manishg)<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> **https://bugs.launchpad.net/neutron/+bug/1415526<br /> * Open Discussion<br /> <br /> === Meeting January 21, 2015 ===<br /> <br /> *Announcements<br /> **Kilo-2 is on Feb 5th<br /> *** https://launchpad.net/neutron/+milestone/kilo-2<br /> * ML2 Drivers decomposition discussion<br /> * ML2 Sync and error handling (Task Flow) - update manishg<br /> * Blueprint list consolidation (shivharis and manishg)<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> ** https://bugs.launchpad.net/neutron/+bug/1179223 (romilg)<br /> ** Review patch set for the bug/1179223 https://review.openstack.org/#/c/136106/<br /> ** https://bugs.launchpad.net/neutron/+bug/1367391 (matrohon)<br /> * Open Discussion<br /> <br /> === Meeting January 14, 2015 ===<br /> <br /> *Announcements<br /> **Kilo-2 is few weeks away<br /> *** https://launchpad.net/neutron/+milestone/kilo-2<br /> * ML2 Drivers decomposition discussion<br /> * ML2 Sync and error handling (Task Flow)<br /> * Blueprint list consolidation (shivharis and manishg)<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> ** https://review.openstack.org/#/c/113999/<br /> * Open Discussion<br /> <br /> === Meeting January 7, 2015 ===<br /> <br /> *Announcements<br /> **Kilo-2 is in one month<br /> *** https://wiki.openstack.org/wiki/Kilo_Release_Schedule<br /> * L2 Gateway update<br /> ** Team plans to meet every other week initially - goal is to have an API within Kilo cycle<br /> **See details here: https://wiki.openstack.org/wiki/Meetings#Networking_L2_Gateway_meeting<br /> * ML2 Drivers decomposition discussion<br /> * Blueprint list consolidation (shivharis and manishg)<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> * Open Discussion<br /> <br /> === Meeting December 31, 2014 ===<br /> <br /> * No meeting - holiday break<br /> <br /> === Meeting December 24, 2014 ===<br /> <br /> * No meeting - holiday break<br /> <br /> === Meeting December 17, 2014 ===<br /> <br /> *Announcements<br /> <br /> **Kilo-1 is due this week<br /> *** Here is the content of the release https://launchpad.net/neutron/+milestone/kilo-1<br /> <br /> ** Neutron Mid-cycle report<br /> *** https://etherpad.openstack.org/p/neutron-mid-cycle-sprint-dec-2014<br /> ***http://lists.openstack.org/pipermail/openstack-dev/2014-December/052715.html<br /> <br /> * Discussion about the ML2 Drivers decomposition<br /> * Blueprint list consolidation (shivharis and manishg)<br /> ** Needs further split of drivers<br /> <br /> * Bugs<br /> ** We are closing in on K-1 release<br /> ** High priority bugs:<br /> ** https://bugs.launchpad.net/neutron/+bug/1179223 (romilg)<br /> ** https://bugs.launchpad.net/neutron/+bug/1367391 (rkukura)<br /> ** https://bugs.launchpad.net/neutron/+bug/1378732 (markmacclain, bug was critical at one point)<br /> ** https://bugs.launchpad.net/neutron/+bug/1381536 (Eugene)<br /> ** Other bugs:<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> * Open Discussion<br /> <br /> === Meeting December 10, 2014 ===<br /> <br /> * No meeting today due to Neutron Mid-cycle sprint<br /> <br /> === Meeting December 3, 2014 ===<br /> * Announcements<br /> ** Mid-cycle meetup: https://wiki.openstack.org/wiki/Sprints/NeutronKiloSprint<br /> ** Sub-teams charter https://wiki.openstack.org/wiki/NeutronSubteamCharters<br /> ** Kilo release schedule: https://wiki.openstack.org/wiki/Kilo_Release_Schedule<br /> <br /> *Action Items from previous Week<br /> ** None<br /> <br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> ** Total of 56 bugs, many in medium and low state<br /> ** Many vendor specific bugs<br /> ** Should we continue working on this (almost done) or abandon it: https://review.openstack.org/#/c/113999/<br /> <br /> * Spec Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> * ML2 driver repository discussion - We did not get to cover it last week<br /> ** It seems ML2 vendor drivers will likely be moving out of the main neutron git repository<br /> *** https://review.openstack.org/#/c/134680/<br /> ** Any vendor can use their own private repository (stackforge?)<br /> ** Do we want a common repository for ML2 vendor drivers?<br /> *** Merges reviewed/approved by an ML2 core team?<br /> *** Pros<br /> **** Reviews maintain consistent quality, style, functionality, etc.<br /> **** Help ensure drivers can coexist in heterogeneous deployments<br /> **** Changes to driver API can update all drivers in common repo in single merge<br /> **** Distributions can package entire set of vendor drivers rather than having to interact with each vendor separately<br /> *** Cons<br /> **** Reviews and approval needed to merge<br /> **** Vendors don't control release cycle for their own drivers<br /> **** Not a level playing field for vendors who chose to use their own repositories<br /> *** Formal poll coming?<br /> <br /> * Modular L2 agent<br /> ** Separate task force?<br /> ** Relationship to ML2?<br /> <br /> *Open Discussion<br /> ** https://blueprints.launchpad.net/neutron/+spec/network-settings-support-vnic-type<br /> <br /> === Meeting November 26, 2014 ===<br /> * Announcements<br /> ** Mid-cycle meetup: https://wiki.openstack.org/wiki/Sprints/NeutronKiloSprint<br /> ** Kilo release schedule: https://wiki.openstack.org/wiki/Kilo_Release_Schedule<br /> <br /> *Action Items from previous Week<br /> ** Discuss rate limiting (throughput limiting)<br /> ** Discuss port security<br /> <br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> * Spec Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> * ML2 Subteam Charter<br /> ** https://etherpad.openstack.org/p/ML2_Subteam_Charter<br /> <br /> * ML2 driver repository discussion<br /> ** It seems ML2 vendor drivers will likely be moving out of the main neutron git repository<br /> *** https://review.openstack.org/#/c/134680/<br /> ** Any vendor can use their own private repository (stackforge?)<br /> ** Do we want a common repository for ML2 vendor drivers?<br /> *** Merges reviewed/approved by an ML2 core team?<br /> *** Pros<br /> **** Reviews maintain consistent quality, style, functionality, etc.<br /> **** Help ensure drivers can coexist in heterogeneous deployments<br /> **** Changes to driver API can update all drivers in common repo in single merge<br /> **** Distributions can package entire set of vendor drivers rather than having to interact with each vendor separately<br /> *** Cons<br /> **** Reviews and approval needed to merge<br /> **** Vendors don't control release cycle for their own drivers<br /> **** Not a level playing field for vendors who chose to use their own repositories<br /> *** Formal poll coming?<br /> <br /> * Modular L2 agent<br /> ** Separate task force?<br /> ** Relationship to ML2?<br /> <br /> *Open Discussion<br /> ** https://blueprints.launchpad.net/neutron/+spec/network-default-setting-ext<br /> <br /> === Meeting November 19, 2014 ===<br /> * Announcements<br /> ** Mid-cycle meetup: https://wiki.openstack.org/wiki/Sprints/NeutronKiloSprint<br /> <br /> * Bugs<br /> ** Move postcommit ops out of transaction for bulk https://review.openstack.org/#/c/113999/<br /> <br /> * Spec Reviews<br /> ** ML2: portsecurity extension support https://review.openstack.org/#/c/99873/<br /> <br /> * ML2 Subteam Charter<br /> ** Should the ML2 subteam continue to exist, meet, etc.? <br /> ** If so, it needs a charter by next week's neutron IRC meeting.<br /> ** Draft at https://etherpad.openstack.org/p/ML2_Subteam_Charter<br /> <br /> * ML2 driver repository discussion<br /> ** It seems ML2 vendor drivers will likely be moving out of the main neutron git repository<br /> ** Any vendor can use their own private repository (stackforge?)<br /> ** Do we want a common repository for ML2 vendor drivers?<br /> *** Merges reviewed/approved by an ML2 core team?<br /> *** Pros<br /> **** Reviews maintain consistent quality, style, functionality, etc.<br /> **** Help ensure drivers can coexist in heterogeneous deployments<br /> **** Changes to driver API can update all drivers in common repo in single merge<br /> **** Distributions can package entire set of vendor drivers rather than having to interact with each vendor separately<br /> *** Cons<br /> **** Reviews and approval needed to merge<br /> **** Vendors don't control release cycle for their own drivers<br /> **** Not a level playing field for vendors who chose to use their own repositories<br /> *** Formal poll coming?<br /> <br /> * Modular L2 agent<br /> ** Separate task force?<br /> ** Relationship to ML2?<br /> <br /> *Open Discussion<br /> <br /> === Meeting November 12, 2014 ===<br /> <br /> *No meeting this week due to people still traveling and/or recovering.<br /> <br /> === Meeting November 5, 2014 ===<br /> <br /> *No meeting this week due to Paris Summit.<br /> <br /> === Meeting October 29, 2014 ===<br /> <br /> *Announcements<br /> **Absent excuse: banix<br /> **Summit is next week!<br /> <br /> *Action Items from previous Week<br /> **None<br /> <br /> *Bugs:<br /> ** Move postcommit ops out of transaction for bulk https://bugs.launchpad.net/neutron?field.searchtext=ml2 <br /> <br /> *Specs for Kilo<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Kilo Design Summit <br /> **Sessions<br /> ***https://etherpad.openstack.org/p/kilo-neutron-summit-topics-distilled<br /> **Pod Discussions<br /> <br /> *Open Discussion<br /> <br /> === Meeting October 22, 2014 ===<br /> <br /> *Announcements<br /> **Absent excuse: banix, rkukura<br /> **Juno release is out<br /> ***https://launchpad.net/neutron/juno/2014.2<br /> <br /> *Action Items from previous Week<br /> **None<br /> <br /> *Task Flow discussion at Yahoo (Manish, Sukhdev, Bob, Josh)<br /> **http://docs.openstack.org/developer/taskflow/index.html<br /> <br /> *Bugs:<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Specs deferred to Kilo from Juno<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Kilo Design Summit <br /> **Kilo Summit topics for Neutron<br /> ***https://etherpad.openstack.org/p/kilo-neutron-summit-topics-distilled<br /> **ML2 Kilo Themes Discussion (Continuation from last week) <br /> *** What do we want to accomplish in ML2 during Kilo? <br /> ***Lets identify priorities first, then figure out how we can best make use of whatever summit time is available.<br /> *** https://etherpad.openstack.org/p/ML2_Kilo_Themes<br /> <br /> *Open Discussion<br /> <br /> === Meeting October 15, 2014 ===<br /> <br /> *Announcements<br /> **Absent excuse: banix <br /> **Juno release is scheduled for later this week<br /> ***Juno feature content - https://wiki.openstack.org/wiki/ReleaseNotes/Juno#OpenStack_Network_Service_.28Neutron.29<br /> <br /> *Action Items from previous Week<br /> **None<br /> <br /> *Bugs/Reviews<br /> **Bug/Patchsets needing reviews:<br /> *** https://review.openstack.org/126360<br /> *** https://review.openstack.org/124917<br /> **Bugs:<br /> ***https://bugs.launchpad.net/neutron/+bug/1377346 (manishg: is this already fixed?)<br /> ***https://bugs.launchpad.net/neutron/+bug/1224978 (fixed above?)<br /> <br /> * https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Specs deferred to Kilo from Juno<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Kilo Design Summit <br /> **Kilo Summit topics for Neutron<br /> ***https://etherpad.openstack.org/p/kilo-neutron-summit-topics<br /> **ML2 Kilo Themes Discussion (Continuation from last week) <br /> *** What do we want to accomplish in ML2 during Kilo? <br /> ***Lets identify priorities first, then figure out how we can best make use of whatever summit time is available.<br /> ***Moved ideas list to etherpad: https://etherpad.openstack.org/p/ML2_Kilo_Themes<br /> <br /> *Open Discussion<br /> <br /> === Meeting October 8, 2014 ===<br /> <br /> *Announcements<br /> **Absent excuse: banix <br /> **Juno RC1<br /> ***Release content - https://launchpad.net/neutron/+milestone/juno-rc1<br /> ***Release notes - https://wiki.openstack.org/wiki/ReleaseNotes/Juno#OpenStack_Network_Service_.28Neutron.29<br /> **Neutron Driver Team<br /> ***https://wiki.openstack.org/wiki/Neutron-drivers<br /> <br /> *Action Items from previous Week<br /> **None<br /> <br /> *Bugs<br /> *** https://bugs.launchpad.net/neutron/+bug/1179223 (romilg: needs milestone)<br /> *** https://bugs.launchpad.net/neutron/+bug/1367391 (rkukura: needs milestone)<br /> *** https://bugs.launchpad.net/neutron/+bug/1224978 romilg: needs milestone)<br /> *** https://bugs.launchpad.net/neutron/+bug/1236127 (chuckc: merged?, more needed?)<br /> *** https://bugs.launchpad.net/neutron/+bug/1311470 (kevinbenton: if no issues, please close, fixed with docs)<br /> *** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Specs deferred to Kilo from Juno<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Kilo Design Summit <br /> **Kilo Summit topics for Neutron<br /> ***https://etherpad.openstack.org/p/kilo-neutron-summit-topics<br /> **ML2 Kilo Themes Discussion<br /> *** What do we want to accomplish in ML2 during Kilo? <br /> ***Lets identify priorities first, then figure out how we can best make use of whatever summit time is available.<br /> ***Ideas<br /> **** Cleanup/generalize DVR's distributed port support<br /> ***** See https://bugs.launchpad.net/neutron/+bug/1367391 regarding cleanup<br /> ***** Generalize for DHCP, other services?<br /> **** Complete hierarchical port binding<br /> ***** See https://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding<br /> **** Solve the postcommit backend sync / error handling situation<br /> *****ML2 Sync proposal - https://docs.google.com/document/d/17fATwZkJEonH0pIb1-mPD0UB5RKnJzcHYqkBesJhirE/edit<br /> **** Complete the bulk ops support<br /> **** Revisit/cleanup/improve DB transaction usage, eliminating with_lockmode('update') and semaphore locking<br /> **** Move currently built-in extensions to extension drivers where practical<br /> **** Implement extension driver semantics enforcement<br /> ***** See https://docs.google.com/a/noironetworks.com/document/d/14T-defRnFl6M2xR5ZNFGYD6aIiAVWdd1Al9BnjV_JOs<br /> **** Modular L2 agent<br /> **** Do drivers belong in-tree and/or out-of-tree?<br /> **** Improved test coverage and efficiency<br /> **** Improve performance, robustness, and scalability<br /> <br /> *Open Discussion<br /> <br /> === Meeting October 1, 2014 ===<br /> <br /> *Announcements<br /> **Kilo is now open for new specs<br /> **Kilo Summit topics for Neutron<br /> ***https://etherpad.openstack.org/p/kilo-neutron-summit-topics<br /> ** Absent excuse: shivharis (traveling)<br /> *Action Items from previous Week<br /> **banix to work with mlavalle and the team to figure out best testing strategy for bulk operations<br /> **shivharis to follow up with mestery regarding ML2 RC1 bugs<br /> <br /> *Bugs<br /> *** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Specs deferred to Kilo from Juno<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *ML2 Kilo Themes Discussion<br /> ** What do we want to accomplish in ML2 during Kilo? <br /> ** Lets identify priorities first, then figure out how we can best make use of whatever summit time is available.<br /> ** Ideas<br /> *** Cleanup/generalize DVR's distributed port support<br /> **** See https://bugs.launchpad.net/neutron/+bug/1367391 regarding cleanup<br /> **** Generalize for DHCP, other services?<br /> *** Complete hierarchical port binding<br /> **** See https://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding<br /> *** Solve the postcommit backend sync / error handling situation<br /> ****ML2 Sync proposal - https://docs.google.com/document/d/17fATwZkJEonH0pIb1-mPD0UB5RKnJzcHYqkBesJhirE/edit<br /> *** Complete the bulk ops support<br /> *** Revisit/cleanup/improve DB transaction usage, eliminating with_lockmode('update') and semaphore locking<br /> *** Move currently built-in extensions to extension drivers where practical<br /> *** Implement extension driver semantics enforcement<br /> **** See https://docs.google.com/a/noironetworks.com/document/d/14T-defRnFl6M2xR5ZNFGYD6aIiAVWdd1Al9BnjV_JOs<br /> *** Modular L2 agent<br /> *** Do drivers belong in-tree and/or out-of-tree?<br /> *** Improved test coverage and efficiency<br /> *** Improve performance, robustness, and scalability<br /> <br /> *Open Discussion<br /> <br /> === Meeting September 24, 2014 ===<br /> <br /> *Announcements<br /> ** Juno RC-1<br /> ***https://launchpad.net/neutron/+milestone/juno-rc1<br /> **Kilo Summit topics for Neutron<br /> ***https://etherpad.openstack.org/p/kilo-neutron-summit-topics<br /> <br /> *Action Items from previous Week<br /> **banix to work with mlavalle and others to define scenario test for Bulk Ops testing<br /> ***We agreed to propose to the team to implement a special mechanism driver that will fail in predictable ways (e.g. every other post commit op or every 4th one) to enable a tempest script to confirm that, when failure occurs, all the bulk operations are rolled back<br /> <br /> *Bugs<br /> *** https://review.openstack.org/#/c/113999 (banix, in reviews)<br /> *** All ML2 &amp; RC1 bugs<br /> *** https://bugs.launchpad.net/neutron/+bug/1179223 (romilg)<br /> *** https://bugs.launchpad.net/neutron?field.searchtext=ml2&amp;field.milestone%3Alist=67382<br /> *** ML2 bugs<br /> *** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Specs deferred to Kilo from Juno<br /> **https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> *Open Discussion<br /> <br /> === Meeting September 17, 2014 ===<br /> <br /> *Announcements<br /> ** Juno RC-1<br /> ***https://launchpad.net/neutron/+milestone/juno-rc1<br /> **Kilo Summit topics for Neutron<br /> ***https://etherpad.openstack.org/p/kilo-neutron-summit-topics<br /> <br /> *Action Items from previous Week<br /> **banix to talk with tempest folks about bulk create testing<br /> **Sukhdev to update Subgroup review wiki<br /> ***https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> **rkukura to create etherpad for ML2-related design summit ideas, including this async postcommit processing topic<br /> <br /> *Bugs/Reviews<br /> **Jenkins failure is affecting some merges, it is still unassigned, see if you can add information to this<br /> ***https://bugs.launchpad.net/neutron/+bug/1370347<br /> ** Reviews needed:<br /> *** https://review.openstack.org/#/c/113999 (own: banix, review: amotoki, Sukhdev, shivharis)<br /> *** &lt;s&gt;https://review.openstack.org/#/c/116612 (own: irenab, talk to core, amotoki took care)&lt;/s&gt;<br /> *** https://review.openstack.org/#/c/105514 (own: rcurran, cant do much, jenkins failed)<br /> *** &lt;s&gt;https://review.openstack.org/#/c/89982 (own: romilg, nit by cedric, need core) (now merged)&lt;/s&gt;<br /> *** &lt;s&gt;https://review.openstack.org/#/c/119940 (own: shegde, garyk took care)&lt;/s&gt;<br /> **Bugs<br /> *** High priority bugs<br /> *** https://bugs.launchpad.net/neutron/+bug/1367391<br /> *** https://bugs.launchpad.net/neutron/+bug/1370077 (not ml2, but for plugins other than ml2)<br /> *** All ML2 &amp; RC1 bugs<br /> *** https://bugs.launchpad.net/neutron?field.searchtext=ml2&amp;field.milestone%3Alist=67382<br /> <br /> *Open Discussion<br /> <br /> === Meeting September 10, 2014 ===<br /> <br /> *Announcements<br /> ** Juno FFE candidates for RC-1<br /> ***https://launchpad.net/neutron/+milestone/juno-rc1<br /> <br /> *Action Items from previous Week<br /> ** rkukura to work on getting FFE for port binding BP - Completed, but denied<br /> ** rkukura to enter bugs for DVR ML2 issues he’s identified - Entered most important one: https://bugs.launchpad.net/neutron/+bug/1367391<br /> <br /> *Bugs<br /> ** FF -&gt; RC1 focus shifts to bugs<br /> ** https://bugs.launchpad.net/neutron/+bug/1193861<br /> ** https://review.openstack.org/#/c/113999/ (Updated to include all bulk ops for networks, subnets, and ports.)<br /> ** https://bugs.launchpad.net/neutron/+bug/1367391 (tracking)<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> ** Anyone needs help in progress with their bugs/reviews please raise your hand<br /> <br /> *Code Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Open Discussion<br /> <br /> === Meeting September 3, 2014 ===<br /> <br /> *Announcements<br /> ** Juno feature freeze deadline is over<br /> <br /> *Action Items from previous Week<br /> **rkukura to enter bugs for DVR ML2 issues he’s identified<br /> **nlahouti and rkukura to keep after markmclain to remove his -2 on https://review.openstack.org/#/c/89211/, or explain why its not being removed - Completed<br /> <br /> *Code Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Bugs<br /> ** https://bugs.launchpad.net/neutron/+bug/1359416 (status: high - j3, akihiro?)<br /> ** https://review.openstack.org/#/c/113999/<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Open Discussion<br /> <br /> === Meeting August 27, 2014 ===<br /> <br /> *Announcements<br /> ** Juno feature freeze deadline is 9/4<br /> <br /> *Action Items from previous Week<br /> **Sukhdev or rkukura to follow up with DVR team regarding Neutron OVS based Distributed Virtual Router - rkukura took care of this<br /> <br /> *Bugs<br /> ** https://review.openstack.org/#/c/113999/<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Code Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Open Discussion<br /> <br /> === Meeting August 20, 2014 ===<br /> <br /> *Announcements<br /> ** Juno feature proposal deadline is August 21<br /> **Third Party Test System requirements for Juno<br /> ***https://wiki.openstack.org/wiki/NeutronThirdPartyTesting<br /> ** Absent excuse: banix, shivharis<br /> <br /> *Action Items from previous Week<br /> **rkukura to add comment to https://bugs.launchpad.net/neutron/+bug/1311470 suggesting we check at init for segments without configured drivers - Done<br /> **emagana to file doc bug corresponding to https://bugs.launchpad.net/neutron/+bug/1311470<br /> *** (emagana) It is already fixed by this commit: https://bugs.launchpad.net/openstack-manuals/+bug/1307133<br /> **banix to add priority column to code review table in https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews - Done<br /> <br /> *Bugs<br /> ** https://review.openstack.org/#/c/113999/ (banix: I may not be able to attend the meeting; please review; I will update and complete the fix accordingly)<br /> <br /> *Code Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Open Discussion<br /> <br /> === Meeting August 13, 2014 ===<br /> <br /> *Announcements<br /> ** Juno feature proposal deadline is August 21 - week from tomorrow<br /> <br /> *Action Items from previous Week<br /> **rkukura to add comments to https://bugs.launchpad.net/neutron/+bug/1311470 (comments added by rkukura)<br /> **shivharis to track bug https://bugs.launchpad.net/neutron/+bug/1352801 (carl baldwin added comments)<br /> **shivharis: to track bug https://bugs.launchpad.net/neutron/+bug/1224978 (unit tests have been added, now need reviewers)<br /> <br /> *Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> ** (skip this time to allocate more time to Code Reviews - will gain more urgency next time)<br /> <br /> *Code Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> * Support for network adaptors that do not allow promiscuous mode (relevant for flat &amp; vlan networking)<br /> ** Extend openvswitch neutron agent<br /> ** Introduce macvtap (modifications to novas libvirt driver and linuxbridge plugin/agent)<br /> <br /> *Open Discussion<br /> <br /> === Meeting August 6, 2014 ===<br /> <br /> *Announcements<br /> ** https://launchpad.net/neutron/+milestone/juno-3<br /> ** Absent excuse: shivharis<br /> <br /> *Action Items from previous Week<br /> **Sukhdev and banix to update https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews with deferred specs and for tracking code reviews for approved specs<br /> **rkukura to add comments to https://bugs.launchpad.net/neutron/+bug/1311470<br /> <br /> *Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Spec Reviews<br /> ** No more spec reviews. We have moved into code review phase<br /> <br /> *Code Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> <br /> *ML2 Hierarchical Port Binding and Dynamic Segments<br /> <br /> *Open Discussion<br /> <br /> === Meeting July 30, 2014 ===<br /> <br /> *Announcements<br /> <br /> *Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> ** https://bugs.launchpad.net/neutron/+bugs?field.tag=ml2<br /> ** https://bugs.launchpad.net/neutron/+bug/1327127 (needs owner)<br /> ** &lt;s&gt;https://bugs.launchpad.net/neutron/+bug/1246737 (please close, havana?)&lt;/s&gt;<br /> ** &lt;s&gt;https://bugs.launchpad.net/neutron/+bug/1338202 (needs review to make it to J2)&lt;/s&gt;<br /> ** https://bugs.launchpad.net/neutron/+bug/1311470 (status)<br /> ** Any others bugs needing reviews for J3 milestone<br /> <br /> *Spec Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> <br /> *ML2 Hierarchical Port Binding and Dynamic Segments<br /> <br /> *Open Discussion<br /> <br /> === Meeting July 23, 2014 ===<br /> <br /> *Announcements<br /> <br /> **Juno-2 is tomorrow<br /> **https://launchpad.net/neutron/+milestone/juno-2<br /> **Spec/BP approvals for Juno is passed<br /> **Name of the K-release is Kilo<br /> **Several of our spces got approved and merged <br /> <br /> *Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> ** https://bugs.launchpad.net/neutron/+bug/1327127 (needs owner)<br /> ** https://bugs.launchpad.net/neutron/+bug/1246737 (please close, havana?)<br /> ** https://bugs.launchpad.net/neutron/+bug/1338202 (needs review to make it to J2)<br /> ** https://bugs.launchpad.net/neutron/+bug/1311470 (status)<br /> ** Any others bugs needing reviews for J2 milestone<br /> <br /> *Spec Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> <br /> *ML2 Sync<br /> ** https://docs.google.com/document/d/17fATwZkJEonH0pIb1-mPD0UB5RKnJzcHYqkBesJhirE/edit<br /> <br /> *Open Discussion<br /> <br /> === Meeting July 16, 2014 ===<br /> *Announcements<br /> **Spec approval deadline is July 20th. <br /> **Third party CI to be operational by July 24th. <br /> **Name the K-release https://www.surveymonkey.com/s/openstack-k-naming<br /> **Live migration of VMs from Nova Network to Neutron in MN - <br /> https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo <br /> <br /> *Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> ** https://bugs.launchpad.net/neutron/+bug/1331857 (status)<br /> ** https://bugs.launchpad.net/neutron/+bug/1246737 (status)<br /> ** https://bugs.launchpad.net/neutron/+bug/1311470 (status, kevinbenton?)<br /> ** https://bugs.launchpad.net/neutron/+bug/1332719 (review needed)<br /> ** https://bugs.launchpad.net/neutron/+bug/1337787 (review needed)<br /> <br /> *Spec Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> <br /> *ML2 Sync<br /> ** https://docs.google.com/document/d/17fATwZkJEonH0pIb1-mPD0UB5RKnJzcHYqkBesJhirE/edit<br /> <br /> * Provide node specific information to ML2 plugin<br /> ** [http://lists.openstack.org/pipermail/openstack-dev/2014-July/thread.html#39755 Email thread]<br /> <br /> *Open Discussion<br /> <br /> === Meeting July 9, 2014 ===<br /> * Meeting cancelled due to mid-cycle sprint<br /> <br /> === Meeting July 2, 2014 ===<br /> * Announcements<br /> ** Nova/Neutron Parity Sprint next week in Minneapolis, MN<br /> *** https://etherpad.openstack.org/p/lOiqsLmizl<br /> ** DVR Demo<br /> ***https://www.youtube.com/watch?v=p4BwAjLHd0M<br /> ** Update on Friday's meeting to discuss ML2 Bulk Operations and ML2 Sync<br /> *** https://bugs.launchpad.net/neutron/+bug/1193861<br /> ** Absent excuse: shivharis<br /> * Action items from last week<br /> ** None<br /> <br /> *Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> <br /> *Spec Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> ** https://etherpad.openstack.org/p/modular-l2-agent-outline<br /> *** Specs ready for core reviews<br /> <br /> *Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> ** https://review.openstack.org/#/c/99187/<br /> <br /> * Third Party Test System requirements<br /> ** https://wiki.openstack.org/wiki/NeutronThirdPartyTesting<br /> *Open Discussion<br /> <br /> === Meeting June 25, 2014 ===<br /> * Announcements<br /> * Action items from last week<br /> ** banix to re-organize the wiki to categorize the specs and add a column for code reviews<br /> * Modular L2 agent: <br /> ** [https://etherpad.openstack.org/p/modular-l2-agent-outline Schematic diagram]<br /> ** [https://review.openstack.org/#/c/99187/ Code sketch]<br /> ** [http://lists.openstack.org/pipermail/openstack-dev/2014-June/thread.html#37195 Email thread]<br /> *Bugs<br /> ** Need owner: https://bugs.launchpad.net/neutron/+bug/1204456<br /> ** J2: https://bugs.launchpad.net/neutron/+bug/1276391<br /> ** Serious bug, need some sort of closure: https://bugs.launchpad.net/neutron/+bug/1224978<br /> ** We should close bugs that affect others by J2 so others have time to work on their stuff by J3<br /> ** Any bugs that are ready and awaiting reviews?<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> *Spec Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> ** Ready for core approvals<br /> *** https://review.openstack.org/#/c/89728/<br /> *** https://review.openstack.org/#/c/91811/ <br /> *** which others? <br /> *Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> * Third Party Test System requirements<br /> ** https://wiki.openstack.org/wiki/NeutronThirdPartyTesting<br /> *Open Discussion<br /> <br /> === Meeting June 18, 2014 ===<br /> * Announcements<br /> * Action items from last week<br /> ** banix to consolidate info from spec tracking etherpad into https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews<br /> ** banix to investigate https://launchpad.net/bugs/1193861<br /> * Modular L2 agent: <br /> ** [https://etherpad.openstack.org/p/modular-l2-agent-outline Schematic diagram]<br /> ** [https://review.openstack.org/#/c/99187/ Code sketch]<br /> ** [http://lists.openstack.org/pipermail/openstack-dev/2014-June/thread.html#37195 Email thread]<br /> *Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> *Spec Reviews<br /> ** https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review<br /> ** Ready for core approvals<br /> *** https://review.openstack.org/#/c/89728/<br /> *** https://review.openstack.org/#/c/91811/ Is this ready? <br /> *** which others? <br /> *Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> * Third Party Test System requirements<br /> ** https://wiki.openstack.org/wiki/NeutronThirdPartyTesting<br /> *Open Discussion<br /> <br /> === Meeting June 11, 2014 ===<br /> * Announcements<br /> ** Juno-1 being cut today<br /> *** Trying to get APIC L3 patch merged 1st<br /> ** See https://wiki.openstack.org/wiki/NeutronJunoProjectPlan for Juno-2,3 plans<br /> *** Need to get ML2 high and medium priority items into plan<br /> ** 3rd party CI needs to be working properly for ML2 drivers to stay in tree<br /> *** mestery will send email with deadlines<br /> *** see https://wiki.openstack.org/wiki/NeutronThirdPartyTesting<br /> * Action items from last week<br /> ** rkukura to put priorities in specs etherpad (rkukura) [ from last week, close? ]<br /> ** rkukura to talk to mestery for blueprint priorities<br /> ** Sukhdev to investigate bug 1193861<br /> ** rkukura to discuss with Mark regarding taskflow and provide feedback<br /> * Bugs<br /> ** juno-1 in a few hours, nothing glaring for us<br /> ** https://bugs.launchpad.net/neutron/+bug/1305800 (j1 -&gt; j2)<br /> * Spec Reviews<br /> ** https://etherpad.openstack.org/p/Neutron_ML2_Juno_Spec_Tracking<br /> ** Support for extensions in ML2 Mechanism Drivers<br /> *** review: https://review.openstack.org/#/c/89208/<br /> *** etherpad: https://etherpad.openstack.org/p/ML2_MD_extensions<br /> *** issue: How to support extended attributes on core resources<br /> **** Current proposal: Pass input attributes to MDs and let MDs persist data and modify dictionaries<br /> **** Alternative 1: Fix NeutronDbPluginV2 base class to alway not set process_extensions=False when creating dictionaries<br /> **** Alternative 2: Add ExtensionDriver to ML2, with extend_*_dict, process_*_create, process_*_update methods<br /> * Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> * Modular L2 agent: https://review.openstack.org/#/c/99187/<br /> * Open Discussion<br /> <br /> === Meeting June 04, 2014 ===<br /> * Announcements<br /> ** https://wiki.openstack.org/wiki/NeutronPolicies (Neutron Policies)<br /> * Action items from last week<br /> ** banix to recruit folks interested in Moduler L2 agent implementation<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron/+bug/1276391 (rkukura: status)<br /> ** &lt;s&gt;https://bugs.launchpad.net/neutron/+bug/1227336 (banix to update status)&lt;/s&gt;<br /> ** https://bugs.launchpad.net/neutron/+bug/1193861 (will this be covered by sukhdev's sync?)<br /> ** https://bugs.launchpad.net/neutron/+bug/1246737 (oleg: havana backport)<br /> ** https://bugs.launchpad.net/neutron/+bug/1260598 (isaku: status on unit test?)<br /> ** https://bugs.launchpad.net/neutron/+bug/1236127 (needs slightly more unit test coverage, according to Kyle, need new owner)<br /> ** (still working on the bugs section - shiv)<br /> * Spec Reviews<br /> ** https://etherpad.openstack.org/p/Neutron_ML2_Juno_Spec_Tracking<br /> *** If priority is assigned, you may add your name as subteam-reviewer<br /> ** Modular L2 agent (banix, blueprint)<br /> *** Have started putting the code together. Will have it posted before the next meeting (June 11) for comment. Will also update the ether pad below to provide more information accordingly.<br /> *** https://etherpad.openstack.org/p/modular-l2-agent-outline<br /> ** Status on sync implementation (sukhdev)<br /> *** some bugs were closed as this will now be the holy grail<br /> <br /> === Meeting May 28, 2014 ===<br /> * Announcements<br /> ** none<br /> * Action items from last week<br /> ** shivharis to scan all the bugs and tag them and prioritize them<br /> ** rkukura to move all the specs from Agenda to an ehterpad<br /> ** banix to send an email regarding ML2 Modular agent plan and seek interested parties<br /> * ovs-firewall-driver discussion: blueprint obstacles https://review.openstack.org/#/c/89712/<br /> * Modular L2 agent: planning<br /> ** Initial outline for discussion [https://etherpad.openstack.org/p/modular-l2-agent-outline here]<br /> ** possible interaction with upcoming &quot;hierarchical binding&quot; and &quot;unified get_device_details&quot;<br /> * Bugs (today we will only address these bugs)<br /> ** https://bugs.launchpad.net/neutron/+bug/1276391 (rkukura: status)<br /> ** https://bugs.launchpad.net/neutron/+bug/1227336 (banix to update status)<br /> ** https://bugs.launchpad.net/neutron/+bug/1246737 (oleg: havana backport)<br /> ** https://bugs.launchpad.net/neutron/+bug/1224978 (romilg: status?, priority?)<br /> ** https://bugs.launchpad.net/neutron/+bug/1260598 (isaku: status on unit test?)<br /> ** There are many bugs under the &quot;need unit tests&quot; [ NEED OWNERS ]<br /> *** what is the general plan for this?<br /> *** do MDs need specific tests or they are covered by the general ML2 plugin testing framework?<br /> * Spec Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z<br /> ** https://etherpad.openstack.org/p/Neutron_ML2_Juno_Spec_Tracking<br /> * Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> * Open Discussion<br /> <br /> === Meeting May 21, 2014 ===<br /> * Announcements<br /> ** Mid-cycle code sprint scheduled July 9-11<br /> *** Cisco office in Bloomington, Minnesota<br /> *** logistics, signup: https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting<br /> * Action items from last week<br /> ** banix to organize single etherpad for Modular L2 Agents session - done<br /> ** rkukura to flesh out single etherpad for ML2 Roadmap session - done<br /> * ML2 design summit sessions post-mortem<br /> ** https://etherpad.openstack.org/p/ML2_Juno_Roadmap<br /> ** https://etherpad.openstack.org/p/ML2_mechanismdriver_extensions_support<br /> ** https://etherpad.openstack.org/p/juno-neutron-modular-l2-agent<br /> ** https://etherpad.openstack.org/p/hierarchical_network_topology<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Spec reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z<br /> ** Merged<br /> *** ML2 Mechanism Driver for the Cisco APIC - https://review.openstack.org/#/c/89305/ - HenryG<br /> *** ML2 Mechanism Driver for SR-IOV NIC switching - https://review.openstack.org/#/c/89763/ - irenab<br /> ** In review<br /> *** Add spec for ML2 mechanism driver for SDN-VE - https://review.openstack.org/#/c/88101/ - banix<br /> *** VDP support in OVS Neutron Agent - https://review.openstack.org/#/c/89728/ - nlahouti<br /> *** ML2 Type drivers refactor to allow extensiblity - https://review.openstack.org/#/c/91811/ - asomya<br /> *** physical-network-topology extension spec - https://review.openstack.org/#/c/91275/ - Isaku Yamahata<br /> *** GW API: L2 bridging API - Piece 1: Basic use cases - https://review.openstack.org/#/c/93613/ - Racha Ben Ali<br /> *** Neutron QoS API Extension - https://review.openstack.org/#/c/88599/ - sc68cal<br /> *** Allow partial specification of Provider Network attributes - https://review.openstack.org/#/c/91540/ - zzelle<br /> *** Open vSwitch-based Security Groups: OVS FirewallDriver - https://review.openstack.org/#/c/89712/ - asadoughi<br /> *** Adding spec for fsl-sdn-os-mech-driver - https://review.openstack.org/#/c/88190/ - Trinath Somanchi<br /> *** Support for extensions in ML2 Mechanism Drivers - https://review.openstack.org/#/c/89208/ - nlahouti<br /> *** Add spec for neutron-external-ports blueprint - https://review.openstack.org/#/c/87825/ - kevinbenton<br /> *** ML2 Mechanism Driver for Cisco DFA - https://review.openstack.org/#/c/89740/ - nlahouti<br /> *** Neutron OVS based Distributed Virtual Router - https://review.openstack.org/#/c/89934/ - Swaminathan Vasudevan<br /> *** VLAN aware VMs - https://review.openstack.org/#/c/94612/ - Erik Moe<br /> ** Planned<br /> *** ML2 Hierarchical Port Binding - rkukura<br /> * Code reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> * Open discussion<br /> <br /> === Meeting May 7, 2014 ===<br /> * Announcements<br /> ** Juno Summit next week, so no IRC meeting<br /> ** Mid-cycle meeting being planned - https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting<br /> * Action items from last week<br /> ** rkukura to create etherpads for each summit session as soon as schedule is finalized<br /> *** rkukura added https://etherpad.openstack.org/p/ML2_Juno_Roadmap, but still needs to link BPs and spec to discuss<br /> *** etherpads have been added for other sessions by others<br /> *** Single etherpad per session, vs. etherpad per proposal?<br /> * ML2 Design Summit Sessions<br /> ** Neutron schedule - http://junodesignsummit.sched.org/overview/type/neutron<br /> ** Three sessions mainly focused on ML2<br /> *** ML2 Roadmap - http://junodesignsummit.sched.org/event/685fded37958784c0337681aa120568c<br /> *** Agent - http://junodesignsummit.sched.org/event/4205f2c4084e8a0c3bd8d420803ddf02<br /> *** Hierarchical Network Topologies - http://junodesignsummit.sched.org/event/1d5c2a1cc40bb6ffa539c19e8e5471b2<br /> ** etherpads - https://wiki.openstack.org/wiki/Summit/Juno/Etherpads#Neutron<br /> ** neutron pod at summit<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Spec Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z<br /> * Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> * Open Discussion<br /> <br /> === Meeting Cancelled April 30, 2014 ===<br /> * OpenStack vacation week!<br /> === Meeting April 23, 2014 ===<br /> * Announcements<br /> ** Neutron design summit runs through Friday - check your travel plans<br /> ** New BP review process is up and running<br /> * Action items from last week<br /> ** None<br /> * Design Summit Sessions<br /> ** http://summit.openstack.org/<br /> ** mestery is finalizing schedule, combining sessions<br /> *** ML2 Roadmap<br /> *** Agent<br /> *** Hierarchical Network Topologies<br /> ** neutron pod at summit<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron?field.searchtext=ml2<br /> * Spec Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z<br /> * Code Reviews<br /> ** https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z<br /> * Open Discussion<br /> <br /> === Meeting April 16, 2014 ===<br /> * Announcements<br /> * Action items from last week:<br /> * TypeDriver Refactoring: asomya<br /> * ovs-firewall-driver update: asadoughi<br /> * design summit session proposals - deadline Sunday 4/20<br /> ** https://etherpad.openstack.org/p/juno_ml2_session_ideas<br /> <br /> === Meeting April 9, 2014 ===<br /> * Action items from last week:<br /> ** mestery to start etherpad for Juno Summit Sessions<br /> *** https://etherpad.openstack.org/p/juno_ml2_session_ideas<br /> ** asomya to present his TypeDriver Refactoring<br /> * TypeDriver Refactoring<br /> ** asomya<br /> * ovs-firewall-driver update: asadoughi<br /> <br /> === Meeting April 2, 2014 ===<br /> * Action items from last week<br /> ** banix to push patch to call remaining MDs after postcommit exception<br /> *** Please see: https://review.openstack.org/#/c/83217/ (Note that besides the unit tests and the updated comments this patch simply adds three lines.)<br /> * Reviews being tracked<br /> ** Bind ports outside of transactions (rkukura): https://review.openstack.org/#/c/82945/<br /> ** Error handling for update ops - https://bugs.launchpad.net/neutron/+bug/1227336<br /> *** Marked this as WORKINPROGRESS pending further discussion (perhaps at the summit). See the Action items section above for a stopgap measure. <br /> *** https://review.openstack.org/#/c/69792/ - in review<br /> *** Needs ML2 and core reviews<br /> *** Consensus that undoing operation makes sense if postcommit() ops fail?<br /> *** Do only drivers already called before failure see undo?<br /> * Design Summit Session Ideas<br /> ** Juno planning for ML2 should start now<br /> ** Ideas for summit sessions<br /> <br /> === Meeting March 26, 2014 ===<br /> * Action items from last week:<br /> ** None<br /> * Migration BP<br /> ** migration - FFE - https://review.openstack.org/#/c/76533/ - merged<br /> * Other Bugs:<br /> * Bugs for icehouse<br /> ** Port binding details - https://bugs.launchpad.net/neutron/+bug/1276395<br /> *** partial fix (add new properties) - https://review.openstack.org/#/c/76363/ - merged<br /> *** remainder (binding details in delete_port_*commit() ops) - https://review.openstack.org/#/c/79511/ - merged<br /> ** bind_port() called in transaction - https://bugs.launchpad.net/neutron/+bug/1276391<br /> *** partial fix (remove validate_port_binding() and unbind_port() ops) - https://review.openstack.org/#/c/79511/ - merged<br /> *** remainder (move binding outside transaction) - https://review.openstack.org/#/c/82945/ - WIP<br /> **** Required minor fixes to mechanism drivers and tests - see REVISIT comments<br /> **** Update later today with cleanups, record locking, etc.<br /> **** Not clear if it will make icehouse<br /> ** Error handling for update ops - https://bugs.launchpad.net/neutron/+bug/1227336<br /> *** https://review.openstack.org/#/c/69792/ - in review<br /> *** Needs ML2 and core reviews<br /> *** Consensus that undoing operation makes sense if postcommit() ops fail?<br /> *** Do only drivers already called before failure see undo?<br /> *** Defer to juno?<br /> ** Binding failed - https://bugs.launchpad.net/neutron/+bug/1244255 - closed<br /> ** VIF security - https://bugs.launchpad.net/nova/+bug/1112912 - in review<br /> *** Resistance to merging nova side - just control via nova config?<br /> *** Email thread and IRC discussion<br /> *** Nachi suggested discussion on #openstack-neutron after this meeting<br /> <br /> === Meeting March 19, 2014 ===<br /> * Action items from last week:<br /> ** None<br /> * Migration BP<br /> ** migration - FFE - https://review.openstack.org/#/c/76533/<br /> *** (marun) Updated to support LB, please review.<br /> * Other Bugs:<br /> * Bugs for icehouse<br /> ** Port binding details - https://bugs.launchpad.net/neutron/+bug/1276395<br /> *** partial fix (add new properties) - https://review.openstack.org/#/c/76363/ - merged<br /> *** remainder (binding details in delete_port_*commit() ops) - https://review.openstack.org/#/c/79511/ - approved<br /> ** bind_port() called in transaction - https://bugs.launchpad.net/neutron/+bug/1276391<br /> *** partial fix (remove validate_port_binding() and unbind_port() ops) - https://review.openstack.org/#/c/79511/ - approved<br /> *** remainder (move binding outside transaction) - in progress, hopefully in review today<br /> ** Error handling for update ops - https://bugs.launchpad.net/neutron/+bug/1227336<br /> *** https://review.openstack.org/#/c/69792/ - in review<br /> *** Needs ML2 and core reviews<br /> *** Consensus that undoing operation makes sense if postcommit() ops fail?<br /> ** VIF security - https://bugs.launchpad.net/nova/+bug/1112912 - in review<br /> ** Binding failed - https://bugs.launchpad.net/neutron/+bug/1244255 - unassigned?<br /> *** Will https://review.openstack.org/#/c/80829/ help?<br /> * Final mechanism driver status for icehouse:<br /> ** cisco apic - deferred - https://review.openstack.org/#/c/73355/, https://review.openstack.org/#/c/73372/<br /> ** cisco ucs - deferred<br /> ** freescale - deferred - https://review.openstack.org/#/c/78092/ (former reviews: https://review.openstack.org/#/c/71868/, https://review.openstack.org/#/c/73985/, https://review.openstack.org/#/c/70089/)<br /> ** huawei - deferred<br /> ** SRIOV mech driver - deferred - https://review.openstack.org/#/c/74464/<br /> <br /> === Meeting March 12, 2014 ===<br /> * Action items from last week:<br /> ** None<br /> * Final mechanism driver status for icehouse<br /> ** bigswitch - merged - https://review.openstack.org/#/c/64944/<br /> ** brocade - merged - https://review.openstack.org/#/c/60129/<br /> ** cisco apic - deferred - https://review.openstack.org/#/c/73355/, https://review.openstack.org/#/c/73372/<br /> ** cisco ucs - deferred<br /> ** freescale - deferred - https://review.openstack.org/#/c/78092/ (former reviews: https://review.openstack.org/#/c/71868/, https://review.openstack.org/#/c/73985/, https://review.openstack.org/#/c/70089/)<br /> ** huawei - deferred<br /> ** mellanox - merged - https://review.openstack.org/#/c/72854/<br /> ** open daylight (odl) - merged - https://review.openstack.org/#/c/69775/<br /> ** openflow agent - merged - https://review.openstack.org/#/c/71791/<br /> ** SRIOV mech driver - deferred - https://review.openstack.org/#/c/74464/<br /> * Other BPs for icehouse<br /> ** migration - FFE - https://review.openstack.org/#/c/76533/<br /> *** (marun) Updated to support LB, please review.<br /> ** partial specs - deferred - https://review.openstack.org/#/c/71904/, https://review.openstack.org/#/c/74055/<br /> * Bugs for icehouse<br /> ** Port binding details - https://bugs.launchpad.net/neutron/+bug/1276395<br /> *** partial fix (add new properties) - https://review.openstack.org/#/c/76363/ - merged<br /> *** remainder (binding details in delete_port_*commit() ops) - will be addressed in update to https://review.openstack.org/#/c/79511/ today - in progress<br /> ** bind_port() called in transaction - https://bugs.launchpad.net/neutron/+bug/1276391<br /> *** partial fix (remove validate_port_binding() and unbind_port() ops) - https://review.openstack.org/#/c/79511/ - in review, update today<br /> *** remainder (move binding outside transaction) - in progress, hopefully in review today<br /> ** Error handling for update ops - https://bugs.launchpad.net/neutron/+bug/1227336<br /> *** https://review.openstack.org/#/c/69792/ - in review<br /> *** Needs ML2 and core reviews<br /> *** Consensus that undoing operation makes sense if postcommit() ops fail?<br /> ** VIF security - https://bugs.launchpad.net/nova/+bug/1112912 - in review<br /> ** Binding failed - https://bugs.launchpad.net/neutron/+bug/1244255 - unassigned?<br /> ** Agent model migration - https://bugs.launchpad.net/neutron/+bug/1260224 - in review<br /> ** L2-pop live migration - https://bugs.launchpad.net/neutron/+bug/1237841 - review abandoned?<br /> *** here is the good review : https://review.openstack.org/#/c/61767/ (will be rebased asap)<br /> * Distributed Virtual Router<br /> ** L2 plugin changes needed to enable DVR. See the DVR section of [[Meetings/Neutron-L3-Subteam|L3 subteam page]] for details.<br /> ** [https://docs.google.com/document/d/1depasJSnGZPOnRLxEC_PYsVLcGVFXZLqP52RFTe21BE/edit#heading=h.5w7clq272tji Here is the document specifically about L2 changes]<br /> * Juno design summit session proposals<br /> ** Submit and read proposals at http://summit.openstack.org/<br /> ** I'll submit a general ML2 update/planning/catch-all session<br /> ** Unfinished items from icehouse?<br /> ** Brainstorm?<br /> * Open Discussion<br /> <br /> === Meeting March 5, 2014 ===<br /> * Action items from last week:<br /> ** None<br /> * Mechanism driver status for icehouse<br /> ** bigswitch - merged - https://review.openstack.org/#/c/64944/<br /> ** brocade - approved - https://review.openstack.org/#/c/60129/<br /> ** cisco apic - deferred? - https://review.openstack.org/#/c/73355/, https://review.openstack.org/#/c/73372/<br /> ** cisco ucs - deferred<br /> ** freescale - deferred - https://review.openstack.org/#/c/78092/ (former reviews: https://review.openstack.org/#/c/71868/, https://review.openstack.org/#/c/73985/, https://review.openstack.org/#/c/70089/)<br /> ** huawei - deferred<br /> ** mellanox - merged - https://review.openstack.org/#/c/72854/<br /> ** open daylight (odl) - FFE - https://review.openstack.org/#/c/69775/<br /> ** openflow agent - merged - https://review.openstack.org/#/c/71791/<br /> ** SRIOV mech driver: https://review.openstack.org/#/c/74464/<br /> * Other BPs for icehouse<br /> ** migration - FFE - https://review.openstack.org/#/c/76533/<br /> *** (marun) Updated to support LB, please review.<br /> ** partial specs - deferred? - https://review.openstack.org/#/c/71904/, https://review.openstack.org/#/c/74055/<br /> * Bugs for icehouse<br /> ** https://bugs.launchpad.net/neutron/+bug/1276395, https://review.openstack.org/#/c/76363/ - approved<br /> ** https://bugs.launchpad.net/neutron/+bug/1276391 - in progress<br /> ** https://review.openstack.org/#/c/69792/ Deals with fails in update-*-postcommit ops <br /> * Distributed Virtual Router<br /> ** L2 plugin changes needed to enable DVR. See the DVR section of [[Meetings/Neutron-L3-Subteam|L3 subteam page]] for details.<br /> ** [https://docs.google.com/document/d/1depasJSnGZPOnRLxEC_PYsVLcGVFXZLqP52RFTe21BE/edit#heading=h.5w7clq272tji Here is the document specifically about L2 changes]<br /> * Open Discussion<br /> <br /> === Meeting February 26, 2014 ===<br /> * Action items from last week:<br /> ** ML2 team to review Port Binding document and comment inline<br /> *** https://docs.google.com/document/d/1k8tAqfQr8Ujzx5TzpXTYEUaym-0U-pE3YL9wjrS8cDg/edit#heading=h.cpck9ip3dbdv<br /> ** marun and rkukura to proceed with migration BP and get an extension from markmcclain<br /> *** Initial patch posted for review, please take a look! https://review.openstack.org/#/c/76533/<br /> **** [marun]: I'm afraid I can't attend the meeting but will be back online later today. <br /> ** All ML2 MechanismDrivers which bind ports should ensure they look to make sure the binding:vnic_type attribute is something they handle.<br /> * Port binding bug fixes which may affect MDs:<br /> ** https://bugs.launchpad.net/neutron/+bug/1276395<br /> ** https://bugs.launchpad.net/neutron/+bug/1276391<br /> * Open Discussion<br /> <br /> === Meeting February 19, 2014 ===<br /> * Action items from last week:<br /> ** rkukura to move port binding discussion into Google Doc<br /> ** matrohon to file BP for multi-node testing and bring this up in the infra meeting<br /> * Migration tool<br /> ** BP: https://blueprints.launchpad.net/neutron/+spec/ml2-deprecated-plugin-migration<br /> ** marun volunteered to own this working with rkukura<br /> * SR-IOV BPs in review:<br /> ** https://blueprints.launchpad.net/neutron/+spec/ml2-binding-profile<br /> ** https://blueprints.launchpad.net/neutron/+spec/ml2-request-vnic-type<br /> ** https://blueprints.launchpad.net/neutron/+spec/vif-details<br /> ** https://review.openstack.org/#/c/21946/<br /> ** https://bugs.launchpad.net/neutron/+bug/1274034<br /> ** https://review.openstack.org/#/c/44596/<br /> * Port binding bug fixes which may affect MDs:<br /> ** https://bugs.launchpad.net/neutron/+bug/1276395<br /> ** https://bugs.launchpad.net/neutron/+bug/1276391<br /> * Proposed patch to ML2 to move away from providernet extension into the multi-provider extension with arbitrary attributes<br /> ** https://review.openstack.org/#/c/37893/<br /> <br /> === Meeting February 12, 2014 ===<br /> * Action items from last week:<br /> ** rkukura to put result of binding changes email discussion into a wiki or google doc<br /> ** rkukura to change priorities of all new 3rd party MD BPs to low if they do not already have jenkins job in place<br /> *** https://blueprints.launchpad.net/neutron/+spec/brocade-ml2-mechanism-driver - medium, approved, in review, have jenkins<br /> *** https://blueprints.launchpad.net/neutron/+spec/bsn-ml2-mechanism-driver - medium, approved, no review, no jenkins?<br /> *** https://blueprints.launchpad.net/neutron/+spec/huawei-ml2-mechanism-driver - medium, approved, in review, no jenkins?<br /> *** https://blueprints.launchpad.net/neutron/+spec/ml2-cisco-apic-mechanism-driver - medium, approved, no review, have jenkins?<br /> *** https://blueprints.launchpad.net/neutron/+spec/ml2-opendaylight-mechanism-driver - medium, approved, in review, have jenkins?<br /> *** https://blueprints.launchpad.net/neutron/+spec/ml2-ucs-manager-mechanism-driver - medium, approved, no review, have jenkins?<br /> *** https://blueprints.launchpad.net/neutron/+spec/mlnx-ml2-support - medium, approved, in review, have jenkins<br /> *** https://blueprints.launchpad.net/neutron/+spec/ryu-ml2-driver - medium, approved, in review, have jenkins<br /> *** https://blueprints.launchpad.net/neutron/+spec/bigswitch-ml2-driver - low, approved, in review, no jenkins?, relationship to bsn-ml2-mechanism-driver?<br /> *** https://blueprints.launchpad.net/neutron/+spec/fsl-sdn-os-mech-driver - low, approved, in review, no jenkins?<br /> *** https://blueprints.launchpad.net/neutron/+spec/huawei-ml2-evs-mechanism-driver - low, approved, no review, no jenkins, relationship to huawei-ml2-mechanism-driver?<br /> *** https://blueprints.launchpad.net/neutron/+spec/netron-ml2-mechnism-driver-for-cisco-dfa-support - deferred to juno<br /> * ML2 Exceptions to UserSpace<br /> ** https://bugs.launchpad.net/neutron/+bug/1273730<br /> * BPs<br /> ** Provider network partial specs: zzelle@irc<br /> ** https://wiki.openstack.org/wiki/Provider-network-partial-specs<br /> ** https://review.openstack.org/71904<br /> * Blueprints<br /> ** https://blueprints.launchpad.net/neutron?searchtext=ml2<br /> ** 3 high, 13 medium, 3 low, 13 undefined priorities<br /> ** 19 not yet approved for icehouse<br /> ** all MDs should probably be same priority<br /> ** Which should we approve for icehouse, drop from icehouse or adjust priority?<br /> * Bugs<br /> ** https://bugs.launchpad.net/neutron/+bugs?field.tag=ml2<br /> * ovs-firewall security group update: asadoughi<br /> * Tests<br /> ** Add the capabality to test core MD (l2-pop, ovs, lb) by the gate<br /> <br /> ===Previous Agenda===<br /> * ML2 Sessions Etherpads from Icehouse summit:<br /> ** Extensibility of ML2 (Wednesday 4:40PM): https://etherpad.openstack.org/p/ML2_Extensibility<br /> ** ML2 QoS and Deprecated Plugin Migration (Wednesday 5:30PM): https://etherpad.openstack.org/p/neutron-qos-hk and https://etherpad.openstack.org/p/ML2_Deprecated_Plugin_Migration<br /> ** ML2 Multiple Backend Support (Friday 9:50AM)<br /> ** ML2 Mechanism Drivers and Modular Agents (Friday 1:30PM)<br /> * devstack ML2 patches<br /> ** Default devstack to ML2: https://bugs.launchpad.net/devstack/+bug/1220745<br /> ** Correctly set L3 service plugin for ML2: https://review.openstack.org/#/c/48522/<br /> * Documentation<br /> ** Need to focus on this now<br /> ** Documentation BP link: https://blueprints.launchpad.net/openstack-manuals/+spec/neutron-ml2-docs<br /> ** ML2 documentation bugs link: https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=ml2<br /> ** Need to document ML3 with ML2<br /> * Testing and bug fixes<br /> ** Testing of ML2 by everyone would be appreciated<br /> ** We need to find and fix any bugs in the next couple of weeks<br /> <br /> * Icehouse Design Summit Topic ideas<br /> ** RPC handling in ML2 for Type and Mechanism Drivers<br /> ** More extensible TypeDrivers for controller-based MechanismDrivers<br /> ** Monolithic Plugin vs. ML2 MechanismDriver - current and future plugins<br /> ** Future Directions for ML2 (orchestration, deployment, management, ...)<br /> ** Migration from deprecated Plugins (openvswitch, linuxbridge) to ML2 - automation?<br /> ** Add support for VXLAN multicast to the OVS agent with newer versions of OVS and Linux kernel.<br /> ** Multi-segment provider network implementations in MechanismDrivers, specifically OVS.<br /> ** Additional provider network attributes for controller-based plugins such as ODL for networks created outside of Neutron.<br /> <br /> === Icehouse ML2 work for reference ===<br /> * ML2 TypeDriver Extra Port Info<br /> ** https://blueprints.launchpad.net/neutron/+spec/ml2-typedriver-extra-port-info<br /> * Campus Network Blueprint and ML2 integration<br /> ** https://blueprints.launchpad.net/neutron/+spec/campus-network<br /> * OpenDaylight Driver<br /> ** https://blueprints.launchpad.net/quantum/+spec/ml2-opendaylight-mechanism-driver<br /> <br /> === Questions? ===<br /> <br /> == Previous Meeting Logs ==<br /> * Available here: [http://eavesdrop.openstack.org/meetings/networking_ml2/ ML2 Meeting Logs]<br /> <br /> == General ML2 Information ==<br /> Here are the current ml2-specific blueprints for havana:<br /> <br /> * https://blueprints.launchpad.net/quantum/+spec/ml2-gre<br /> * https://blueprints.launchpad.net/quantum/+spec/ml2-mechanism-drivers<br /> * https://blueprints.launchpad.net/quantum/+spec/ml2-portbinding<br /> * https://blueprints.launchpad.net/quantum/+spec/ml2-vxlan<br /> * https://blueprints.launchpad.net/quantum/+spec/ml2-multi-segment-api<br /> <br /> <br /> These tunnel-related blueprints effect the openvswitch and/or<br /> linuxbridge agents, and the features should also (or exclusively) be<br /> supported (using both agents simultaneously where applicable) by the ml2<br /> plugin:<br /> <br /> * https://blueprints.launchpad.net/quantum/+spec/ovs-vxlan-lisp-tunnel<br /> * https://blueprints.launchpad.net/quantum/+spec/openvswitch-kernel-vxlan<br /> * https://blueprints.launchpad.net/quantum/+spec/vxlan-linuxbridge<br /> * https://blueprints.launchpad.net/quantum/+spec/ovs-tunnel-partial-mesh<br /> * https://blueprints.launchpad.net/quantum/+spec/l2-population<br /> <br /> <br /> These blueprints involve the ml2 MechanismDriver API:<br /> <br /> * https://blueprints.launchpad.net/quantum/+spec/tailf-ncs<br /> * https://blueprints.launchpad.net/quantum/+spec/ovsplugin-hardware-devices<br /> <br /> [[Category: Meetings]]</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=126506 2016-06-09T02:17:45Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> == Agenda (2016-06-15) ==<br /> <br /> * Cont. from the previous meeting<br /> ** do we still aim to make a release compatible with mitaka?<br /> * High<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> ** State transition model for TaaS objects (Service, Flow)<br /> ** [[media:Status_Flow_Chart.png]]<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/MidoNet&diff=126384 2016-06-07T06:13:45Z

<p>Yamamoto: /* MidoNet Meeting */</p> <hr /> <div>== MidoNet Meeting ==<br /> <br /> '''MidoNet meetings are currently not being held. Please do not attend until announced otherwise.'''<br /> <br /> == Apologies for Absence ==<br /> <br /> * ryu_ishimoto will be absent from 2015-12-29 to 2016-01-10<br /> * kitsuneninetails (micucci) will be absent from 2015-12-27 to 2016-01-04<br /> <br /> == Announcements ==<br /> <br /> Meetings on 12/29/15 and 1/5/16 are cancelled.<br /> <br /> == Bugs ==<br /> <br /> Stats for the current cycle, starting Dec-1-2015:<br /> <br /> * Dec-1-2015 to Dec-8-2015 (accumulated total in parenthesis):<br /> ** Total reports: '''3''' (3)<br /> *** [https://midonet.atlassian.net/browse/MNA-1112?jql=project%20%3D%20MidoNet%20and%20issuetype%20%3D%20Bug%20AND%20createdDate%20%3E%3D%20%272015%2F12%2F1%27%20and%20createdDate%20%3C%20%272015%2F12%2F8%27 JIRA]<br /> *** Unassigned: '''3''' (3)<br /> **** Proposed/Ready: '''3''' (3)<br /> **** Reopened: '''0''' (0)<br /> * Dec-9-2015 to Dec-15-2015 (accumulated total in parenthesis):<br /> ** Total reports: '''0''' (3)<br /> *** [https://midonet.atlassian.net/issues/?jql=project%20%3D%20MNA%20AND%20issuetype%20%3D%20bug%20AND%20createdDate%20%3E%3D%202015-12-09%20AND%20createdDate%20%3C%3D%202015-12-15 JIRA]<br /> *** Unassigned: '''0''' (3)<br /> **** Proposed/Ready: '''0''' (3)<br /> **** Reopened: '''0''' (0)<br /> * Dec-15-2015 to Dec-22-2015 (accumulated total in parenthesis):<br /> ** Total reports: '''0''' (1)<br /> *** [https://midonet.atlassian.net/browse/MNA-1114?jql=project%20%3D%20MNA%20AND%20issuetype%20%3D%20Bug%20AND%20created%20%3E%3D%202015-12-15%20AND%20created%20%3C%3D%202015-12-22 JIRA]<br /> *** Unassigned: '''0''' (3)<br /> **** Proposed/Ready: '''0''' (3)<br /> **** Reopened: '''0''' (0)<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu25 !! kitsuneninetails !! xavileon !! jfjoly !! joe-6<br /> |-<br /> | 2015-12-08 || x || || || ||<br /> |-<br /> | 2015-12-15 || || x || || ||<br /> |-<br /> | 2015-12-22 || || || x || ||<br /> |-<br /> | 2015-12-29 || x || || || ||<br /> |-<br /> | 2016-1-5 || || || || x ||<br /> |-<br /> | 2016-1-12 || || || || || x<br /> |}<br /> <br /> == Agenda (2016-1-12) ==<br /> <br /> * Announcements<br /> <br /> * Bugs<br /> <br /> * Open Discussion<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting midonet<br /> ** &quot;midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=126382 2016-06-07T05:24:41Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-06-14) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=126275 2016-06-03T09:33:45Z

<p>Yamamoto: /* Agenda (2016-06-08) */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> ** check &quot;TaaS Review Inbox&quot; link on the wiki<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=126274 2016-06-03T09:32:41Z

<p>Yamamoto: /* Neutron Tap as a Service (TaaS) Meeting */</p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> [https://review.openstack.org/#/dashboard/?title=tap-as-a-service+Review+Inbox&amp;foreach=%28project%3Aopenstack%2Ftap-as-a-service%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode-Review%3E%3D-2%2Cself+branch%3Amaster&amp;Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D2+age%3A5d&amp;You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=reviewer%3Aself&amp;Needs+final+%2B2=label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Passed+Jenkins%2C+No+Negative+Core+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT%28reviewerin%3Atap-as-a-service-core+label%3ACode-Review%3C%3D-1%29+limit%3A50&amp;Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode-Review%3C%3D2+age%3A2d TaaS Review Inbox]<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=126272 2016-06-03T09:26:38Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> == Agenda (2016-06-08) ==<br /> * High<br /> ** do we still aim to make a release compatible with mitaka?<br /> * Medium<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-06-01) ==<br /> * Medium<br /> ** Provide Asynchronous API<br /> *** (kaz) Add &quot;status&quot; field in API: I will submit a patch set in a few days.<br /> * Low<br /> ** Open Discussion<br /> <br /> == Agenda (2016-05-25) ==<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-18) ==<br /> *Medium<br /> ** (kaz) Performance measurement : http://lists.openstack.org/pipermail/openstack-dev/2016-May/095303.html<br /> *Low<br /> ** Open discussion<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=125364 2016-05-17T07:13:51Z

<p>Yamamoto: /* Bug deputy */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |-<br /> | 2016-05-17 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=125362 2016-05-17T06:20:11Z

<p>Yamamoto: /* Agenda (2016-05-17) */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> ** make this meeting every two weeks?<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=125360 2016-05-17T05:03:51Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-05-17) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate blocker https://bugs.launchpad.net/devstack/+bug/1582119<br /> * Open Discussion<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=124911 2016-05-09T01:27:26Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> == Agenda (2016-05-11) ==<br /> *High:<br /> ** gate blocking issue: https://review.openstack.org/#/c/306390/<br /> *Medium:<br /> *Low:<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=124687 2016-05-04T01:38:52Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> == Agenda (2016-05-04) ==<br /> <br /> Cancelled (austin summit, japanese holiday)<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=124361 2016-04-23T01:20:02Z

<p>Yamamoto: /* Agenda (2016-05-03) */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released https://github.com/midonet/midonet/wiki/Midonet-5.0.2-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/taas&diff=124269 2016-04-21T04:13:31Z

<p>Yamamoto: </p> <hr /> <div>== Neutron Tap as a Service (TaaS) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting<br /> <br /> == Agenda (2016-04-27) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-20) ==<br /> * High<br /> # TaaS demo session in Austin summit<br /> # TaaS meet up in Austin? (date/time/place)<br /> * Medium<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-13) ==<br /> * High<br /> # Preparation status for the summit, and what are our AI<br /> * Medium<br /> # The start time of weekly TaaS IRC (make it one hour earlier)<br /> #* https://review.openstack.org/#/c/304383/<br /> # Open Discussion<br /> <br /> == Agenda (2016-04-06) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #TaaS Dashboard discussion<br /> *Medium:<br /> # Update on TaaS traffic testing.<br /> #Open Discussion:<br /> *Low:<br /> #midonet implementation (crude but working)<br /> #* https://review.openstack.org/#/c/301843/<br /> #* https://review.gerrithub.io/#/q/status:open+project:midonet/midonet+branch:master+topic:taas<br /> <br /> == Agenda (2016-03-30) ==<br /> *High:<br /> #Summit planning schedule finalization , and what are our AI for the summit<br /> #* Neutron Etherpad: https://etherpad.openstack.org/p/newton-neutron-summit-ideas<br /> #Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> #TaaS Dashboard discussion:<br /> #*[announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #*Possible movement in the next version to Horizon/Liberty<br /> #Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> *Medium:<br /> # Migration of TaaS to OSC<br /> #Open Discussion:<br /> <br /> == Agenda (2016-03-23) ==<br /> * High:<br /> # Summit planning schedule finalization<br /> # Async Calls: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html<br /> # TaaS Dashboard discussion:<br /> #* [announcement] source code of TaaS Dashboard (work in progress) : https://review.openstack.org/#/c/295735/2<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> #* http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Spec Discussion completion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> * Medium:<br /> # Open Discussion:<br /> <br /> == Agenda (2016-03-16) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion:<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089330.html<br /> ## http://lists.openstack.org/pipermail/openstack-dev/2016-March/089446.html<br /> # Discussion over Summit presentation ( how to co-ordinate, timing, matter for presentation et. al.)<br /> <br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> # Study up ML2 extension :http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions.html<br /> <br /> == Agenda (2016-03-09) ==<br /> * High:<br /> # Spec Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html<br /> # Dashboard Discussion: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088735.html<br /> * Medium:<br /> # Issue Observed for Empty Tap-service/Tap-flow listing: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088454.html<br /> # Announcement: New Core Reviewers ( Soichi and Yamamoto )<br /> <br /> == Agenda (2016-03-02) ==<br /> * Open discussion<br /> <br /> == Agenda (2016-02-24) ==<br /> * HIGH <br /> ** vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML <br /> ** Results from the test code executed by anil_rao<br /> * MEDIUM : https://review.openstack.org/#/c/275888 and https://review.openstack.org/#/c/278025/ have been merged, now the review focus should be put on https://review.openstack.org/#/c/229869/ for inclusion of Taas into Governance/Neutron, and respin of https://review.openstack.org/#/c/256210<br /> * LOW<br /> * (kaz) Proposal of Dashboard for TaaS (v0.2): [[Media: DashboardForTaaS_20160224-01.pdf]]<br /> <br /> * Action Items for next week<br /> <br /> == Agenda (2016-02-17) ==<br /> * tap-service-create -- specify destination port vs. create destination port<br /> <br /> == Agenda (2016-02-10) ==<br /> *HIGH<br /> ** l2-agent-extensions-agent-api<br /> *** https://review.openstack.org/#/c/267591/<br /> *** please review requirements: https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> ** Projecting TaaS into Governance https://review.openstack.org/#/c/229869/<br /> *MEDIUM<br /> ** Proposal for Two +2 voting system<br /> *LOW<br /> ** Session proposal submitted, voting has begun : https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8529<br /> <br /> * Action Items<br /> * vnyyad, anil_rao to propose new core reviewers in the openstack-dev ML (HIGH)<br /> * anil_rao to run the latest code, and get back with what features are missing and need to be added for Mitaka Release (CRITICAL)<br /> * fawadkhaliq to share some of the documents used in L2 gateway, for implementation of TaaS as a Neutron L2 extension ( MEDIUM:Done)<br /> http://lists.openstack.org/pipermail/openstack-dev/2016-February/086635.html<br /> * fawadkhaliq: revert TaaS spec to the original state.But keep the updates in a separate section( HIGH:Done)<br /> * review https://review.openstack.org/#/c/278025/ and see how it syncs up with TaaS (HIGH)<br /> <br /> == Agenda (2016-02-03) ==<br /> * spec discussion https://review.openstack.org/#/c/256210/ --&gt; Please refer https://review.openstack.org/#/c/275888/5, chances are TaaS may be a different project with connections to Neutron.<br /> * l2-agent-extensions-agent-api https://review.openstack.org/#/c/267591/<br /> * Summit Presentation: https://www.openstack.org/summit/austin-2016/call-for-speakers/manage/8529/<br /> * Action Items from Last meetings:<br /> # fawadkhaliq update the spec with use cases <br /> # reedip, vyadav : start work on L2 extension for TaaS<br /> # reedip, yamamoto_ : discuss testing related scenarios<br /> # anil_rao, vyadav: take a call on two +2 rule for Gerrit<br /> # vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS<br /> * (kaz) Performance measurement. [[Media: Performance_Evaluation_20160203-01.pdf]]<br /> <br /> == Agenda (2016-01-27) ==<br /> * spec updated https://review.openstack.org/#/c/256210/<br /> <br /> == Agenda (2016-01-20) ==<br /> * (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review<br /> Done : http://lists.openstack.org/pipermail/openstack-dev/2016-January/084627.html<br /> * (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.<br /> * (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> * (reedip) Is an IRC channel needed for TaaS?<br /> * (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed<br /> * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?<br /> * (kaz) Update for https://review.openstack.org/#/c/248043/<br /> <br /> == Agenda (2015-12-16) ==<br /> * (yamamoto) end of year and new year holidays?<br /> * (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/<br /> * (yamamoto) we ought to maintain &quot;two +2s to merge&quot; rule<br /> ** currently we are doing &quot;one +2 to merge&quot;<br /> * (yamamoto) have a dedicated irc channel?<br /> * (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)<br /> * (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion<br /> <br /> == Agenda (2015-12-09) ==<br /> * neutron ovs-agent deletes taas flows<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-December/081709.html {openstack-dev}{neutron}{taas} neutron ovs-agent deletes taas flows]<br /> * gate-tempest-dsvm-tap-as-a-service is now voting<br /> <br /> == Agenda (2015-12-02) ==<br /> * finish usecase and API discussion<br /> ** have a subproject spec?<br /> * What do you say to adding +1 for creating dashboard repository for neutron subprojects?<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html {openstack-dev}{Horizn}{Neutron} dashboard repository for neutron]<br /> * port security setting<br /> ** link: [http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html {openstack-dev}{neutron}{taas} discussion about port security setting]<br /> <br /> == Agenda (2015-11-25) ==<br /> * leftovers from the previous agenda<br /> ** More Core Reviewers needed<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]] (cont.)<br /> ** [[Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf]]<br /> ** [https://review.openstack.org/248043 We submitted our source code.] <br /> *** Current implementation has several restrictions:<br /> **** Multiple monitoring VMs are not supported.<br /> **** IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)<br /> <br /> == Agenda (2015-11-18) ==<br /> * Isolation of production and mirrored traffics. [[Media: TrafficIsolation_20151116-01.pdf]]<br /> * Supporting operations from the dashboard. [[Media: OperationsFromGUI_20151116-01.pdf]]<br /> * More Core Reviewers needed<br /> <br /> == Agenda (2015-11-11) ==<br /> * Short introduction - participants, their position and interest in TaaS<br /> * Current status of the project<br /> * Blueprint clarifications + reviving the blueprint (?)<br /> * The Neutron big tent - the missing parts from being part of it and division of tasks<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting taas<br /> ** &quot;taas&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/<br /> * http://eavesdrop.openstack.org/meetings/taas/</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=124268 2016-04-21T04:12:09Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-05-03) ==<br /> <br /> * Announcements<br /> ** MidoNet 5.0.2 was released<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-26) ==<br /> <br /> Cancelled (austin summit)<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=124129 2016-04-19T07:06:01Z

<p>Yamamoto: /* Bug deputy */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |-<br /> | 2016-04-19 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=124127 2016-04-19T05:24:50Z

<p>Yamamoto: /* Agenda (2016-04-19) */</p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> ** cancel the next meeting (austin summit)<br /> * Bugs<br /> ** gate failure https://bugs.launchpad.net/networking-midonet/+bug/1571486<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto https://wiki.openstack.org/w/index.php?title=Meetings/NetworkingMidoNet&diff=124040 2016-04-16T09:52:09Z

<p>Yamamoto: </p> <hr /> <div>== Neutron MidoNet plugin (networking-midonet) Meeting ==<br /> <br /> http://eavesdrop.openstack.org/#Networking_Midonet_meeting<br /> <br /> == Apologies for Absence ==<br /> <br /> == Bug deputy ==<br /> <br /> Use this section to keep track of who volunteers for the 'bug deputy' role. This is usually edited at the end of the IRC Meeting.<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |-<br /> ! Date !! ryu_ishimoto !! yamamoto !! joemi !!<br /> |-<br /> | 2015-12-08 || x || || ||<br /> |-<br /> | 2015-12-15 || || x || ||<br /> |-<br /> | 2016-01-12 || || || x ||<br /> |-<br /> | 2016-01-19 || || x || ||<br /> |-<br /> | 2016-01-26 || || x || ||<br /> |-<br /> | 2016-02-02 || || x || ||<br /> |-<br /> | 2016-02-09 || || x || ||<br /> |-<br /> | 2016-02-16 || || x || ||<br /> |-<br /> | 2016-02-23 || x || || ||<br /> |-<br /> | 2016-03-01 || || x || ||<br /> |-<br /> | 2016-03-08 || || x || ||<br /> |-<br /> | 2016-03-15 || || x || ||<br /> |-<br /> | 2016-03-22 || || x || ||<br /> |-<br /> | 2016-03-29 || || x || ||<br /> |-<br /> | 2016-04-05 || || x || ||<br /> |-<br /> | 2016-04-12 || || x || ||<br /> |}<br /> <br /> == Agenda (2016-04-19) ==<br /> <br /> * Announcements<br /> ** networking-midonet-coverage job has been moved from post to check<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-12) ==<br /> <br /> * Announcements<br /> ** Mitaka is out<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-04-05) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * extra top-level package (midonet.neutron instead of eg. networking_midonet)<br /> ** it occasionally yields extra work. the recent example: https://review.openstack.org/#/c/300351/<br /> ** why do we have the structure?<br /> ** do we want to keep it?<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-29) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-22) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** tempest jobs have been broken due to recent vm image switch and webob 1.6.0<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-15) ==<br /> <br /> * Announcements<br /> ** https://github.com/midonet/midonet/wiki/Midonet-5.1.0-Release-Notes<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate has been fixed<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** gate is currently broken<br /> * Open Discussion<br /> <br /> == Agenda (2016-03-01) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-23) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * make tempest jobs voting?<br /> * what to do for stadium concept discussion?<br /> ** https://review.openstack.org/#/c/281628/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-09) ==<br /> <br /> * Announcements<br /> ** icehouse and juno are now EOL<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-02-02) ==<br /> <br /> * Announcements<br /> ** EOL'ing icehouse and juno https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Removal of old non-standard branches<br /> ** gerrit/refs/tags/2014.1.4+1.0<br /> ** gerrit/refs/tags/2014.2.2+1.0<br /> ** kilo_legacy<br /> ** kilo_v2<br /> ** release/2014.1.3<br /> ** release/2014.1.4<br /> ** release/2014.2.2<br /> ** release/kilo<br /> ** release/kilo_legacy<br /> ** stable/kilo_legacy<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-26) ==<br /> <br /> * Announcements<br /> ** all fix-committed bugs were marked fix-released<br /> *** cf. http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html<br /> ** EOL'ing icehouse https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1537969 critical, but a backend bug https://midonet.atlassian.net/browse/MNA-1118<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-19) ==<br /> <br /> * Announcements<br /> ** a new kilo release is available<br /> *** https://pypi.python.org/pypi/networking-midonet/2015.1.4<br /> ** icehouse and juno branch are going to be retired<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1535201<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2016-01-12) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> ** Critical<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1533047<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-15) ==<br /> <br /> * Announcements<br /> ** we are going to make 2015.1.2 release<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1525809<br /> *** https://bugs.launchpad.net/networking-midonet/+bug/1507651<br /> * end of year/new year holidays<br /> ** (yamamoto) I propose to skip the next 3 meetings (Dec 22, Dec 29, Jan 5)<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> <br /> == Agenda (2015-12-08) ==<br /> <br /> * Announcements<br /> * Bugs<br /> ** https://bugs.launchpad.net/networking-midonet/<br /> * Open Discussion<br /> ** do we want rfe bugs for open discussions for features? blueprints are not convenient for discussions.<br /> *** http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements<br /> <br /> == Meetbot commands ==<br /> <br /> * #startmeeting networking_midonet<br /> ** &quot;networking_midonet&quot; part is used for the log URL<br /> * #endmeeting<br /> ** To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)<br /> <br /> == Previous meeting logs ==<br /> <br /> * http://eavesdrop.openstack.org/meetings/networking_midonet</div>

Yamamoto