Difference between revisions of "Meetings/taas"
< Meetings
(→Agenda (2017-3-1)) |
|||
Line 18: | Line 18: | ||
** Plan for running on production OpenStack environment. | ** Plan for running on production OpenStack environment. | ||
*** Tried with https://launchpad.net/ubuntu/+source/neutron-taas/0.0.0+git20160926.675af77-0ubuntu1 and dependent packages on http://paste.openstack.org/show/598935/, installation successful but not test worthy because of clash of the packages installed for TaaS vs the dependent packages required by the base release [Newton] | *** Tried with https://launchpad.net/ubuntu/+source/neutron-taas/0.0.0+git20160926.675af77-0ubuntu1 and dependent packages on http://paste.openstack.org/show/598935/, installation successful but not test worthy because of clash of the packages installed for TaaS vs the dependent packages required by the base release [Newton] | ||
+ | ** Common Flow Classifier, which can be looked into from the Tap-as-a-Service perspective: https://review.openstack.org/#/c/333993 | ||
* Open Discussion | * Open Discussion | ||
Revision as of 17:07, 28 February 2017
Contents
Neutron Tap as a Service (TaaS) Meeting
http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting
Announcement
- #vBrownBag Tech Talk at OpenStack Summit Barcelona
Agenda (2017-3-1)
- Work items to get merged into Neutron Stadium
- http://docs.openstack.org/developer/neutron/stadium/governance.html#when-is-a-project-considered-part-of-the-stadium
- http://docs.openstack.org/developer/neutron/stadium/governance.html#checklist
- Discuss various failure/error situations that need to be addressed.
- Discuss additional support for Legal Intercept.
- Plan for running on production OpenStack environment.
- Tried with https://launchpad.net/ubuntu/+source/neutron-taas/0.0.0+git20160926.675af77-0ubuntu1 and dependent packages on http://paste.openstack.org/show/598935/, installation successful but not test worthy because of clash of the packages installed for TaaS vs the dependent packages required by the base release [Newton]
- Common Flow Classifier, which can be looked into from the Tap-as-a-Service perspective: https://review.openstack.org/#/c/333993
- Open Discussion
Agenda (2017-2-22)
- Canceled because of the week of OpenStack PTG
Agenda (2017-2-15)
- Work items to get merged into Neutron Stadium
- http://docs.openstack.org/developer/neutron/stadium/governance.html#when-is-a-project-considered-part-of-the-stadium
- http://docs.openstack.org/developer/neutron/stadium/governance.html#checklist
- Discuss various failure/error situations that need to be addressed.
- Discuss additional support for Legal Intercept.
- Plan for running on production OpenStack environment.
- Tried with https://launchpad.net/ubuntu/+source/neutron-taas/0.0.0+git20160926.675af77-0ubuntu1 and dependent packages on http://paste.openstack.org/show/598935/, installation successful but not test worthy because of clash of the packages installed for TaaS vs the dependent packages required by the base release [Newton]
- Open Discussion
Agenda (2017-2-8)
- yamamoto can't attend this week
- yamamoto plan to cut ocata this week http://lists.openstack.org/pipermail/openstack-dev/2017-February/111653.html
- A talk for Boston Summit (deadline (extended): February 8th at 11:59pm PST (February 9th at 7:59 UTC))
- Open Discussion
Agenda (2017-2-1)
- A talk for Boston Summit (deadline: Feb 6th)
- Open Discussion
Agenda (2017-1-25)
- Review currently open code ( see TaaS review Inbox )
- Open Discussion
Agenda (2017-1-18)
- Loop detection of tap flows (cont.)
- Tap of tap mirrors own traffic but not mirrored traffic. http://lists.openstack.org/pipermail/openstack-dev/attachments/20170118/eea51ee0/attachment-0001.pdf
- Open Discussion
Agenda (2017-1-11)
- how tap of tap should work? (or should not work?) (cont.)
- Loop detection of tap flows (to prevent creating a loop)
- Open Discussion
Meetbot commands
- #startmeeting taas
- "taas" part is used for the log URL
- #endmeeting
- 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)