<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1448234009;
mso-list-template-ids:1370650016;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353">Hi,<o:p></o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353"><o:p> </o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353">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?<o:p></o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353"><o:p> </o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353">I agree the terminology can be confusing.
<o:p></o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353"> I intended the term ‘Service VM’ to mean the virtual machine that hosts one or more ‘Service Instances’, as Sumit points out is distinguished from the Neutron Logical (XaaS) Service.
So a Neutron Logical Service may schedule a Service Instance on a new (or existing) Service VM.<o:p></o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353"><o:p> </o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353"> Greg<o:p></o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:#535353"><o:p> </o:p></span></p>
<p class="MsoNormal" style="border:none;padding:0in"><b><span style="color:#535353"><o:p> </o:p></span></b></p>
</div>
<p class="MsoNormal"><b><span style="color:#535353"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:#535353">Sumit Naiksatam</span></b><span style="color:#535353">
<a href="mailto:openstack-dev%40lists.openstack.org?Subject=Re%3A%20%5Bopenstack-dev%5D%20%5BNeutron%5D%20Service%20VM%20discussion%20-%20Use%20Cases&In-Reply-To=%3CCAMWrLvhZtyc2v%2Bbh-98aVjhTw1kYek5MpCMPDWYWjGG1g-C1Pg%40mail.gmail.com%3E" title="[openstack-dev] [Neutron] Service VM discussion - Use Cases">
sumitnaiksatam at gmail.com </a><br>
<i>Wed Oct 9 21:03:39 UTC 2013</i> <o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="color:#535353;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Previous message: <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-October/016238.html">
[openstack-dev] [Neutron] Service VM discussion - Use Cases </a><o:p></o:p></li><li class="MsoNormal" style="color:#535353;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Next message: <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-October/016252.html">
[openstack-dev] [Neutron] Service VM discussion - Use Cases </a><o:p></o:p></li><li class="MsoNormal" style="color:#535353;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<b>Messages sorted by:</b> <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-October/date.html#16306">
[ date ]</a> <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-October/thread.html#16306">
[ thread ]</a> <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-October/subject.html#16306">
[ subject ]</a> <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-October/author.html#16306">
[ author ]</a> <o:p></o:p></li></ul>
<pre><span style="color:#535353">Hi Harshad,<o:p></o:p></span></pre>
<pre><span style="color:#535353"><o:p> </o:p></span></pre>
<pre><span style="color:#535353">I agree with you that the "service instance" terminology might be a little<o:p></o:p></span></pre>
<pre><span style="color:#535353">confusing here. The way it was phrased in the original email, I believe it<o:p></o:p></span></pre>
<pre><span style="color:#535353">was meant to suggest an association with the corresponding Neutron logical<o:p></o:p></span></pre>
<pre><span style="color:#535353">service (the XaaS to be precise).<o:p></o:p></span></pre>
<pre><span style="color:#535353"><o:p> </o:p></span></pre>
<pre><span style="color:#535353">That said (and to your point on service templates, which I do agree is a<o:p></o:p></span></pre>
<pre><span style="color:#535353">helpful feature), we are not trying to introduce new tenant-facing<o:p></o:p></span></pre>
<pre><span style="color:#535353">abstractions in this blueprint. The work in this blueprint was envisioned<o:p></o:p></span></pre>
<pre><span style="color:#535353">to be a library module that will help service plugins to realize the<o:p></o:p></span></pre>
<pre><span style="color:#535353">service on VMs.<o:p></o:p></span></pre>
<pre><span style="color:#535353"><o:p> </o:p></span></pre>
<pre><span style="color:#535353">Thanks,<o:p></o:p></span></pre>
<pre><span style="color:#535353">~Sumit.<o:p></o:p></span></pre>
<pre><span style="color:#535353"><o:p> </o:p></span></pre>
<pre><span style="color:#535353"><o:p> </o:p></span></pre>
<pre><span style="color:#535353">On Tue, Oct 8, 2013 at 4:16 PM, Harshad Nakil <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">hnakil at contrailsystems.com</a>>wrote:<o:p></o:p></span></pre>
<pre><span style="color:#535353"><o:p> </o:p></span></pre>
<pre><span style="color:#535353">><i> Hello Greg,<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i><o:p> </o:p></i></span></pre>
<pre><span style="color:#535353">><i> Blueprint you have put together is very much in line what we have done in<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> openContrail virtual services implementation.<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i><o:p> </o:p></i></span></pre>
<pre><span style="color:#535353">><i> One thing that we have done is "Service instance" is a single type of<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> service provided by virtual appliance.<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> e.g. firewall or load-balancer etc<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> "Service instance" itself can be made up one or more virtual machines.<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> This will usually be case when you need to scale out services for<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> performance reasons<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i><o:p> </o:p></i></span></pre>
<pre><span style="color:#535353">><i> Another thing that we have done is introduced a concept of service<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> template. Service template describes how the service can be deployed. Image<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> specified in the template can also be snapshot of VM with cookie cutter<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> configuration.<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i><o:p> </o:p></i></span></pre>
<pre><span style="color:#535353">><i> service templates can be created by admins.Service instances are created<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> by tenants (if allowed) using a service templates.<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i><o:p> </o:p></i></span></pre>
<pre><span style="color:#535353">><i> So a a single firewall instance from vendor can be packaged as transparent<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> L2 firewall in one template and in network L3 firewall in another template.<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i><o:p> </o:p></i></span></pre>
<pre><span style="color:#535353">><i> Regards<o:p></o:p></i></span></pre>
<pre><span style="color:#535353">><i> -Harshad<o:p></o:p></i></span></pre>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>