Difference between revisions of "Meetings/taas"
< Meetings
Line 11: | Line 11: | ||
=== OpenStack Summit === | === OpenStack Summit === | ||
* [https://www.openstack.org/summit/sydney-2017/ Sydney, Australia (Nov., 6-8, 2017)] | * [https://www.openstack.org/summit/sydney-2017/ Sydney, Australia (Nov., 6-8, 2017)] | ||
+ | |||
+ | == Agenda (2017-10-18) == | ||
+ | * Open Discussion | ||
== Agenda (2017-10-11) == | == Agenda (2017-10-11) == |
Revision as of 10:32, 16 October 2017
Contents
- 1 Neutron Tap as a Service (TaaS) Meeting
- 2 Agenda (2017-10-18)
- 3 Agenda (2017-10-11)
- 4 Agenda (2017-10-4)
- 5 Agenda (2017-9-27)
- 6 Agenda (2017-9-20)
- 7 Agenda (2017-9-13)
- 8 Agenda (2017-9-6)
- 9 Agenda (2017-8-23)
- 10 Agenda (2017-8-16)
- 11 Agenda (2017-8-9)
- 12 Meetbot commands
- 13 Previous meeting logs
- 14 Important Links
Neutron Tap as a Service (TaaS) Meeting
http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting
Announcement
Initial Spec for Stadium report is up :https://review.openstack.org/#/c/454788/
OpenStack Summit
Agenda (2017-10-18)
- Open Discussion
Agenda (2017-10-11)
- Open Discussion
Agenda (2017-10-4)
- Action Items for Stadium inclusion
- we need to write meaningful scenario tests
- Open Discussion
Agenda (2017-9-27)
- Forum in OpenStack Summit Sydney
- Open Discussion
Agenda (2017-9-20)
- Feedback report from the PTG in Denver
- Open Discussion
Agenda (2017-9-13)
- Canceled: because of the week of PTG
Agenda (2017-9-6)
- Open Discussion
Agenda (2017-8-23)
- Open Discussion
Agenda (2017-8-16)
- skipped (summer vacation)
Agenda (2017-8-9)
- Pike release
- (yamamoto) Unless anyone objects, I'll make a release as it is.
- An open question: Do we want a RC?
- Dashboard
- (yamamoto) I tried the dashboard. It worked well after fixing a few small things.
- An open question: Is it ready for pike release?
- LP bug seems unconfigured. https://bugs.launchpad.net/tap-as-a-service/+bug/1708116
- Review reminder
- https://review.openstack.org/#/c/349176/ This involves DB changes, thus not backportable. If we want it in Pike, review it right now.
- 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)
Previous meeting logs
- http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/
- http://eavesdrop.openstack.org/meetings/taas/
Important Links
- #vBrownBag Tech Talk at OpenStack Summit Barcelona
- http://backreference.org/2014/06/17/port-mirroring-with-linux-bridges/
- Slideshare slides
- https://www.slideshare.net/soichishigeta/designof-traffic-isolationby-using-flow-based-tunneling
- https://www.slideshare.net/soichishigeta/cannot-observe-ingress-packets
- https://www.slideshare.net/soichishigeta/performance-measurement-when-source-vms-are-increased
- https://www.slideshare.net/soichishigeta/performance-measurement-when-the-source-vms-are-increased
- https://www.slideshare.net/soichishigeta/performance-measurement-when-increasing-send-packets