Cloud image/ kernel/OVS followup

[Robyn Bergeron]

----- Original Message -----
> From: "Robert Collins (Converged Cloud)" <rbtcollins at hp.com>
> To: "Fedora Cloud SIG" <cloud at lists.fedoraproject.org>
> Sent: Wednesday, January 22, 2014 11:50:58 AM
> Subject: RE: Cloud image/ kernel/OVS followup
> 
> TripleO isn't nested virt: The lower layer cloud is nova-baremetal or Ironic,
> so your hypervisor hosts are running on bare metal, and they need ovs etc
> indeed.

Okay! I stand corrected. Perhaps my nested virt comment was more like "a similarity".. or not.. anyway. :)

> 
> Note that for Fedora based deploys we *start* with a fedora cloud image, so
> if it's not possible to install ovs and physical hardware drivers into those
> images, it won't be possible to deploy OpenStack using TripleO w/Fedora.

When you say "for Fedora based deploys we start with a fedora cloud image" - this is *just* for the TripleO case, or is this for a "regular" (SingleO, hah) deploy as well? 

Sorry if I'm being confusing (or if I'm just confused) :) I just know there are plenty of projects out there who are developing new tech rather rapidly and not everyone in the cloud SIG is intimately involved in all of them. Until we get clones. Working on that. :) But "additional feedback" never hurts.

Thanks!

-robyn

> 
> Cheers,
> Rob
> 
> Robert Collins <rbtcollins at hp.com>
> Distinguished Technologist
> HP Converged Cloud
> 
> _______________________________________________
> cloud mailing list
> cloud at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>