Open Stack

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131002/2fa8f0f3/attachment.html>