This is an old revision of the document!
Minutes of Technical Community Discussion on March 19, 2015
Date and Time: UTC 13:00, Thursday March 19, 2015Convenor: Bin Hu (AT&T)Participants:- Al Morton (AT&T)
- Avinash S (Huawei)
- Bryan Sullivan (AT&T)
- Charlie Hale (IBM)
- Chaudhry Usama
- Christoph Meyer (Ericsson)
- Dave Neary (Redhat)
- Dick Chen (ZTE)
- Frank Zdarsky (Redhat)
- Gerald Kunzmann (DoCoMo)
- Howard Huang (Huawei)
- Iben Rodriguez (Spirent)
- Jie Hu (ZTE)
- Joe Huang (Huawei)
- John McNamara (Intel)
- John Messenger
- Julien Zhang (ZTE)
- Manuel Rebellon (Sandvine)
- Marc Szczesniak (Casa)
- Maria Toeroe (Ericsson)
- Maryam Tahhan (Intel)
- Mike Young (Huawei)
- Narinder Gupta (Canonical)
- Nauman Ahad
- Prakash Ramchandran (Huawei)
- Praveen Kumar
- Raymond Nugent (Huawei)
- Ruan He (Orange)
- Ryota Mibu (NEC)
- Steve Gordon (Redhat)
- Stuart Mackie (Juniper)
- Tomi Juvonen (Nokia)
- Trevor Cooper (Intel)
- Ulrich Kleber (Huawei)
- Wei Su
- Xinyu (Jerry) Zhao (Huawei)
- Yuri Yuan (ZTE)
- IRC Log available
- Draft Blueprints Discussion - 30 minutes
- Event Publisher for Alarm from Doctor project
- Notification-driven Alarm Evaluator from Doctor project
Ryota from NEC presented Ceilometer BP drafts from Doctor project. He primarily introduced fault management scenario, implementation plan in OpenStack, Ceilometer architecture, and how Event Publisher for Alarm and Notification-driven Alarm Evaluator will fill in the gaps in Ceilometer.
The questions focused on technical approach in messaging system. Bryan (AT&T) asked what is the concept of listening, waiting for a response, or subscribed to a channel? Ryota clarified that it meant the subscription to AMQP/RabbitMQ message queue. Bryan indicated that the message queue will not be only internal to OpenStack, and that the technology choice is important for scalability. Ryota clarified that in this context, he is talking about Ceilometer listening internally for events, not external clients consuming events from the OpenStack platform. Bryan emphasized that choice of technology for "listener" is important as this will affect the scalability. we have to consider a variety of dimensions in a generic event notification system for use inside openstack as well as to outside event consumers - TPS is just one, e.g. # of connections, variety of subscribed events, overload protection, etc.
Dave Neary (Redhat) asked how Ryota plans to co-operate with ETSI NFV, and when we can see an updated draft of the blueprint. Ryota confirmed that once the plan is agreed in OPNFV, he would update the blueprint in OpenStack.
- Project Proposal Discussion - 30 minutes
- Discussion of Requirement project proposals
- Discussion of Collaborative Development project proposals
Postponed
Postponed
Postponed
Postponed
- Discussion of Integration and Testing project proposals:
None
- Discussion of Documentation project proposals
None
- Discussion of other projects
None
Note: Testbed, SR and CI have their own conference calls to discuss relevant details.
Meeting adjourned
