Difference between revisions of "Meetings/taas"
< Meetings
| Line 13: | Line 13: | ||
* yamamoto can't attend this week | * yamamoto can't attend this week | ||
* yamamoto plan to cut ocata this week http://lists.openstack.org/pipermail/openstack-dev/2017-February/111653.html | * yamamoto plan to cut ocata this week http://lists.openstack.org/pipermail/openstack-dev/2017-February/111653.html | ||
| − | * A talk for Boston Summit ('''deadline: | + | * A talk for Boston Summit ('''deadline (extended): February 8th at 11:59pm PST (February 9th at 7:59 UTC)''') |
* Open Discussion | * Open Discussion | ||
Revision as of 21:45, 7 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-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)
