Hi Sumit,

I also got confused with service VM and service instance definition. I assumed 
both being the same and hence the networks question.

Rudra

On Oct 9, 2013, at 1:54 PM, Sumit Naiksatam 
<sumitnaiksa...@gmail.com<mailto:sumitnaiksa...@gmail.com>>
 wrote:

Hi Rudra,

We tried to separate policy from mechanism for this blueprint, and are trying 
to address the latter. I believe the logic for scaling, and or clustering 
multiple service VMs to map to a logical service instance would lie in the 
service plugin which realizes the logical service instance.

Can you please elaborate on the service/use-case where you would need to plug 
the VM into different networks?

Thanks,
~Sumit.


On Tue, Oct 8, 2013 at 3:48 PM, Rudra Rugge 
<rru...@juniper.net<mailto:rru...@juniper.net>> wrote:
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.regn...@intel.com<mailto:greg.j.regn...@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@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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


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

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to