<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle">P {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p>The blueprint currently seems libvirt specific to me? Is there a common - perhaps abstracted - interface that we can provide through Nova / image meta-data which will be implemented by each driver in their own way?</p>
<p>Otherwise I can see a bigger mess of metadata values where libvirt uses enable_unix_channels, Xen uses enable_cross_domain_channel - each with their corresponding and custom ways of configuring the behaviour.</p>
<p> </p>
<p>Bob</p>
<p> </p>
<div style="FONT-SIZE: 16px; FONT-FAMILY: Times New Roman; COLOR: #000000">
<hr tabindex="-1">
<div id="divRpF54133" style="DIRECTION: ltr"><font color="#000000" size="2" face="Tahoma"><b>From:</b> Ravi Chunduru [ravivsn@gmail.com]<br>
<b>Sent:</b> 02 October 2013 19:07<br>
<b>To:</b> Daniel P. Berrange; OpenStack Development Mailing List<br>
<b>Subject:</b> Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">Hi Daniel,
<div> I will modify the blueprint as per your suggestions. Actually, we can use state_path in nova.conf if set or the default location.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>-Ravi.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Oct 1, 2013 at 1:57 AM, Daniel P. Berrange <span dir="ltr">
<<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">On Mon, Sep 30, 2013 at 02:25:30PM -0700, Ravi Chunduru wrote:<br>
> Alessandro,<br>
> I agree with you. I created a Blueprint. Let us collaborate and achieve<br>
> this on all types of hypervisors.<br>
><br>
> All,<br>
><br>
> Here is the link for the BP as discussed.<br>
> <a href="https://blueprints.launchpad.net/nova/+spec/appliance-communication-channel" target="_blank">
https://blueprints.launchpad.net/nova/+spec/appliance-communication-channel</a><br>
<br>
</div>
That needs to be expanded to describe more about the intended usage<br>
of the setup, and consider any security issues. IMHO we really do<br>
not want this exposed to end users - particularly not whuen you are<br>
proposing the ability to set arbitrary file paths for the UNIX<br>
sockets against images. That woudl be a security flaw as proposed<br>
in that doc.<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
Daniel<br>
--<br>
|: <a href="http://berrange.com" target="_blank">http://berrange.com</a> -o- <a href="http://www.flickr.com/photos/dberrange/" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
|: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o-
<a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> :|<br>
|: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o-
<a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
|: <a href="http://entangle-photo.org" target="_blank">http://entangle-photo.org</a> -o-
<a href="http://live.gnome.org/gtk-vnc" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
<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>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
Ravi<br>
</div>
</div>
</div>
</div>
</body>
</html>