<div dir="ltr">Alessandro,<div> I agree with you. I created a Blueprint. Let us collaborate and achieve this on all types of hypervisors.</div><div><br>All,</div><div><br></div><div>Here is the link for the BP as discussed. </div>
<div><a href="https://blueprints.launchpad.net/nova/+spec/appliance-communication-channel">https://blueprints.launchpad.net/nova/+spec/appliance-communication-channel</a><br></div><div><br></div><div>Thanks,</div><div>-Ravi.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 30, 2013 at 12:56 PM, Alessandro Pilotti <span dir="ltr"><<a href="mailto:apilotti@cloudbasesolutions.com" target="_blank">apilotti@cloudbasesolutions.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px">Hi
all,</span></div>
<div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><br>
</span></div>
<div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px">A
host / guest communication channel can be useful in a lot of scenarios. What about thinking on a common interface to be implemented on other hypervisors as well and not only on KVM?</span></div>
<div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px">We're
planning to start working on something similar for Hyper-V and there were some chats about ideas related to XenServer as well (John?).</span></div>
<div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><br>
</span></div>
<div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px">Each
hypervisor provides different ways of achieving this goal, but IMO it'd be fairly easy to define a common adapter interface.</span></div><span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><br>
</span></div>
<div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px">Alessandro<br>
</span><br>
</div></font></span><div><div class="h5">
<br>
<div>
<div>On Sep 30, 2013, at 20:21 , Daniel P. Berrange <<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>> wrote:</div>
<br>
<blockquote type="cite">On Mon, Sep 30, 2013 at 09:46:02AM -0700, Ravi Chunduru wrote:<br>
<blockquote type="cite">Let me present an use case.<br>
Today Nova enables to launch guests of different types. For real<br>
deployments we would need appliances from various vendors to run as<br>
instances. Appliances can be Loadbalancer, Firewall, IPsec, Routers or<br>
UTM etc.,<br>
<br>
These appliances can be tied up with Neutron Services and would need<br>
configuration from various services like FWaaS, LBaaS, VPNaaS etc.,<br>
One way to configure these appliances from Neutron Agents is by opening up<br>
the so needed virtio unix channel socket and reach the configuration daemon<br>
in the appliance.<br>
Other approach is by having a separate network for management activities<br>
and having agent to communicate to a daemon in netns to reach out to<br>
appliance.<br>
</blockquote>
<br>
Thanks, this is the kind of usage information I was asking for, wrt<br>
host integration. This shows the use case for virtio-serial is as a<br>
mechanism for integration between infrastructure pieces controlled by<br>
the cloud admin, not as something that is targetted towards end users<br>
of the cloud.<br>
<br>
I think we need to have a detailed blueprint for this, describing the<br>
use case(s) to be addressed and proposing some possible design(s).<br>
<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>
</blockquote>
</div>
<br>
</div></div></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><br clear="all"><div><br></div>-- <br>Ravi<br>
</div>