What about also allowing a specific service to request a port to be created on a requested server for an arbitrary service like a physical machine?
I think we should think more in terms of s/VM/Instance where instance can really be either a VM or a Physical host since it really doesn't matter.. Endre 2013/10/9 Bob Melander (bmelande) <bmela...@cisco.com> > For use case 2, ability to "pin" an admin/operator owned VM to a > particular tenant can be useful. > I.e., the service VMs are owned by the operator but a particular service > VM will only allow service instances from a single tenant. > > Thanks, > Bob > > From: <Regnier>, Greg J <greg.j.regn...@intel.com> > Reply-To: OpenStack Development Mailing List < > openstack-dev@lists.openstack.org> > Date: tisdag 8 oktober 2013 23:48 > To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org > > > Subject: [openstack-dev] [Neutron] Service VM discussion - Use Cases > > 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 > 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
