[openstack-dev] [Neutron] Service VM discussion - Use Cases

Rudra Rugge rrugge at juniper.net
Tue Oct 8 22:48:10 UTC 2013


Hi Greg,

Is there any discussion so far on the scaling of VMs as in launching multiple VMs
for the same service. It would also have impact on the VIF scheme.

How can we plug these services into different networks - is that still being worked
on?

Thanks,
Rudra

On Oct 8, 2013, at 2:48 PM, "Regnier, Greg J" <greg.j.regnier at intel.com<mailto:greg.j.regnier at intel.com>> wrote:

Hi,

Re: blueprint:  https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms
Before going into more detail on the mechanics, would like to nail down use cases.
Based on input and feedback, here is what I see so far.

Assumptions:


- a 'Service VM' hosts one or more 'Service Instances'

- each Service Instance has one or more Data Ports that plug into Neutron networks

- each Service Instance has a Service Management i/f for Service management (e.g. FW rules)

- each Service Instance has a VM Management i/f for VM management (e.g. health monitor)


Use case 1: Private Service VM

Owned by tenant

VM hosts one or more service instances

Ports of each service instance only plug into network(s) owned by tenant


Use case 2: Shared Service VM

Owned by admin/operator

VM hosts multiple service instances

The ports of each service instance plug into one tenants network(s)

Service instance provides isolation from other service instances within VM



Use case 3: Multi-Service VM

Either Private or Shared Service VM

Support multiple service types (e.g. FW, LB, …)


-          Greg
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131008/61eea2fe/attachment.html>


More information about the OpenStack-dev mailing list