The use cases defined (so far) cover these cases:
Single service instance in a single service VM (agree this
avoids complexity pointed out by Harshad)
Multiple service instances on a single service VM (provides
flexibility, extensibility)
Not explicitly covered i
Hi,
The original use cases I called out include multiple service instances within a
single VM, but not your use case of a single logical service spread across
multiple VMs for scale-out. Have you identified requirements for these VMs
that might be specified within the scope of this blueprint?
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 Insta
RE: vlan trunking support for network tunnels
Copying to dev mailing list.
- Greg
-Original Message-
From: Kyle Mestery (kmestery) [mailto:kmest...@cisco.com]
Sent: Thursday, October 03, 2013 6:33 AM
To: Bob Melander (bmelande)
Cc: Regnier, Greg J
Subject: Re: Service VM
