[openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver

Ravi Chunduru ravivsn at gmail.com
Wed Oct 2 22:46:36 UTC 2013


Hi Bob,
 Are we talking about naming convention, if so - I am open to suggestions.
 We are defining  metadata for Image - Based on it, virt drivers can
consume it appropriately.

Thanks,
-Ravi.


On Wed, Oct 2, 2013 at 3:17 PM, Bob Ball <bob.ball at citrix.com> wrote:

>  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?
>
> 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.
>
>
>
> Bob
>
>
>  ------------------------------
> *From:* Ravi Chunduru [ravivsn at gmail.com]
> *Sent:* 02 October 2013 19:07
> *To:* Daniel P. Berrange; OpenStack Development Mailing List
>
> *Subject:* Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for
> Nova libvirt driver
>
>   Hi Daniel,
>   I will modify the blueprint as per your suggestions. Actually, we can
> use state_path in nova.conf if set or the default location.
>
>  Thanks,
> -Ravi.
>
>
> On Tue, Oct 1, 2013 at 1:57 AM, Daniel P. Berrange <berrange at redhat.com>wrote:
>
>> On Mon, Sep 30, 2013 at 02:25:30PM -0700, Ravi Chunduru wrote:
>> > Alessandro,
>> >  I agree with you. I created a Blueprint. Let us collaborate and achieve
>> > this on all types of hypervisors.
>> >
>> > All,
>> >
>> > Here is the link for the BP as discussed.
>> >
>> https://blueprints.launchpad.net/nova/+spec/appliance-communication-channel
>>
>>  That needs to be expanded to describe more about the intended usage
>> of the setup, and consider any security issues. IMHO we really do
>> not want this exposed to end users - particularly not whuen you are
>> proposing the ability to set arbitrary file paths for the UNIX
>> sockets against images. That woudl be a security flaw as proposed
>> in that doc.
>>
>>
>> Daniel
>> --
>> |: http://berrange.com      -o-
>> http://www.flickr.com/photos/dberrange/ :|
>> |: http://libvirt.org              -o-
>> http://virt-manager.org :|
>> |: http://autobuild.org       -o-
>> http://search.cpan.org/~danberr/ :|
>> |: http://entangle-photo.org       -o-
>> http://live.gnome.org/gtk-vnc :|
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
>  --
> Ravi
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Ravi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131002/9656d94a/attachment.html>


More information about the OpenStack-dev mailing list