<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi Sumit,
<div><br>
</div>
<div>Please see inline.</div>
<div><br>
</div>
<div><br>
<div>
<div>On Oct 9, 2013, at 2:03 PM, Sumit Naiksatam <<a href="mailto:sumitnaiksatam@gmail.com">sumitnaiksatam@gmail.com</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">Hi Harshad,
<div><br>
</div>
<div>I agree with you that the "service instance" terminology might be a little confusing here. The way it was phrased in the original email, I believe it was meant to suggest an association with the corresponding Neutron logical service (the XaaS to be precise).</div>
<div><br>
</div>
<div>That said (and to your point on service templates, which I do agree is a helpful feature), we are not trying to introduce new tenant-facing abstractions in this blueprint. The work in this blueprint was envisioned to be a library module that will help
service plugins to realize the service on VMs.</div>
<div><br>
</div>
</div>
</blockquote>
<div>[Rudra] How do we handle interdependency between services within a service VM. </div>
<div>Since the ordering of services is often in the same order in most deployments (inbound </div>
<div>firewall/VPN, LB, gateway, outbound FW) it would be better if the template specifies most</div>
<div>of this information. Services in the pipeline may be turned on or off. </div>
<div><br>
</div>
<div>Based on the blueprint we already have the insertion modes: L2, routed, tap etc. The</div>
<div>interface count and interface connections to networks should be specified here. In </div>
<div>addition if a service plugin needs scaling then its not convenient for the plugin to</div>
<div>launch another service VM and manage the networking aspects.</div>
<div><br>
</div>
<div>Hence a template model can contain most of the information (image info, services offered,</div>
<div>service ordering, interface count and names, scaling, insertion mode etc). Launching of</div>
<div>service VMs (containing services) is then associated to template definition.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Rudra</div>
<div><br>
</div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>Thanks,</div>
<div>~Sumit.<br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Oct 8, 2013 at 4:16 PM, Harshad Nakil <span dir="ltr">
<<a href="mailto:hnakil@contrailsystems.com" target="_blank">hnakil@contrailsystems.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hello Greg,
<div><br>
</div>
<div>Blueprint you have put together is very much in line what we have done in openContrail virtual services implementation.</div>
<div><br>
</div>
<div>One thing that we have done is "Service instance" is a single type of service provided by virtual appliance.</div>
<div>e.g. firewall or load-balancer etc</div>
<div>"Service instance" itself can be made up one or more virtual machines. This will usually be case when you need to scale out services for performance reasons</div>
<div><br>
</div>
<div>Another thing that we have done is introduced a concept of service template. Service template describes how the service can be deployed. Image specified in the template can also be snapshot of VM with cookie cutter configuration.</div>
<div><br>
</div>
<div>service templates can be created by admins.Service instances are created by tenants (if allowed) using a service templates.</div>
<div><br>
</div>
<div>So a a single firewall instance from vendor can be packaged as transparent L2 firewall in one template and in network L3 firewall in another template.</div>
<div><br>
</div>
<div>Regards</div>
<div>-Harshad</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Oct 8, 2013 at 2:48 PM, Regnier, Greg J <span dir="ltr">
<<a href="mailto:greg.j.regnier@intel.com" target="_blank">greg.j.regnier@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Hi,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Re: blueprint: <a href="https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms" target="_blank">
https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms</a><u></u><u></u></p>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Before going into more detail on the mechanics, would like to nail down use cases.
<u></u><u></u></span></div>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Based on input and feedback, here is what I see so far.
<u></u><u></u></span></div>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></div>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Assumptions:<u></u><u></u></span></div>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <u></u><u></u></span></div>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">- a 'Service VM' hosts one or more 'Service Instances'<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">- each Service Instance has one or more Data Ports that plug into Neutron networks<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">- each Service Instance has a Service Management i/f for Service management (e.g. FW rules)<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">- each Service Instance has a VM Management i/f for VM management (e.g. health monitor)<u></u><u></u></span></p>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <u></u><u></u></span></div>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Use case 1: Private Service VM
<u></u><u></u></span></div>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Owned by tenant<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">VM hosts one or more service instances<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Ports of each service instance only plug into network(s) owned by tenant<u></u><u></u></span></p>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <u></u><u></u></span></div>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Use case 2: Shared Service VM<u></u><u></u></span></div>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Owned by admin/operator<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">VM hosts multiple service instances<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">The ports of each service instance plug into one tenants network(s)<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Service instance provides isolation from other service instances within VM<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <u></u><u></u></span></p>
<div style="margin: 0in 0in 0.0001pt; "><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Use case 3: Multi-Service VM<u></u><u></u></span></div>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Either Private or Shared Service VM<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:27.0pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Support multiple service types (e.g. FW, LB, …)<span><font color="#888888"><u></u><u></u></font></span></span></p>
<span><font color="#888888">
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin-left:.75in"><u></u><span>-<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Greg<u></u><u></u></p>
</font></span></div>
</div>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>