#openstack-meeting-alt: telcowg

Meeting summary

1. roll call (sgordon, 14:03:49)
   1. https://etherpad.openstack.org/p/nfv-meeting-agenda (sgordon, 14:03:55)
   
   
2. action items from last week (sgordon, 14:04:25)
   1. amitry to cross reference ops mid-cycle signups with telco wg participants to determine crossover (sgordon, 14:04:39)
   2. ACTION: amitry to cross reference ops mid-cycle signups with telco wg participants to determine crossover (sgordon, 14:05:06)
   3. https://etherpad.openstack.org/p/PHL-ops-meetup (amitry, 14:06:21)
   4. https://etherpad.openstack.org/p/PHL-ops-meetup (sgordon, 14:06:29)
   5. steveg was to send out a brief survey monkey to the list and we select one to review at next week's meeting in detail (sgordon, 14:07:23)
   
   
3. virtual IMS use case discussion (sgordon, 14:08:50)
   1. https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases#Virtual_IMS_Core (sgordon, 14:08:55)
   2. implemented as a series of N+k compute pools; meeting a given SLA requires being able to limit the impact of a single host failure (sgordon, 14:13:36)
   3. potentially a scheduler gap here: affinity/anti-affinity can be expressed pair-wise between VMs, which is sufficient for a 1:1 active/passive architecture, but an N+k pool needs a concept equivalent to "group anti-affinity" i.e. allowing the NFV orchestrator to assign each VM in a pool to one of X buckets, and requesting OpenStack to ensure no single host failure can affect more than one bucket (sgordon, 14:13:43)
   4. Require a reference HA design for OpenStack services for critical NFV such as vIMS (sgordon, 14:19:38)
   5. http://docs.openstack.org/high-availability-guide/content/index.html (sgordon, 14:21:29)
   6. http://lists.openstack.org/pipermail/openstack-operators/2014-August/004987.html (sgordon, 14:23:36)
   7. https://blueprints.launchpad.net/heat/+spec/multi-region-support (sgordon, 14:32:23)
   8. ACTION: mkoderer to take a stab at documenting use for multi-site (sgordon, 14:33:57)
   9. possible commonalities around HA and multi-site requirements to identify as we progress through use cases (sgordon, 14:53:12)
   10. need more flexibility from Availability Zone and Host Aggregate placement, along with more flexible placement rules for the scheduler (sgordon, 14:54:00)
   11. general agreement to focus on use cases in the context of single site deployment first (sgordon, 14:55:28)
   12. Is gerrit a better mechanism for use case review? (sgordon, 14:56:01)
   13. https://etherpad.openstack.org/p/kKIqu2ipN6 (sgordon, 15:00:25)
   14. http://lists.openstack.org/pipermail/openstack-dev/2015-January/053915.html (sgordon, 15:02:10)

Action items

1. amitry to cross reference ops mid-cycle signups with telco wg participants to determine crossover
2. mkoderer to take a stab at documenting use for multi-site

Action items, by person

1. amitry
   1. amitry to cross reference ops mid-cycle signups with telco wg participants to determine crossover
2. mkoderer
   1. mkoderer to take a stab at documenting use for multi-site

People present (lines said)

1. sgordon (138)
2. ybabenko (32)
3. cloudon (26)
4. vks (25)
5. mkoderer (23)
6. adrian-hoban (14)
7. imendels (10)
8. aveiga (9)
9. amitry (3)
10. openstack (3)
11. gmatefi1 (2)
12. DaSchab (2)
13. ajo (1)
14. smazziotta (1)