On Tue, Jun 19, 2012 at 10:46:43AM -0700, Joshua Harlow wrote:
Interesting,
So the issue i think with using libvirt is that we want to use netcf inside
a VM, not on the outside where we might have libvirt support and could do
such an action (this involves file injection which is yucky), ideally we'd
use this tool called cloud-init which does first time boot-like
initialization (among other things). OpenStack would then write this
network information + other metadata (say in the agonistic netcf format)
then during first time booting cloud-init would pick that data back up, and
write out the VM specific format (among other things it can do). Since we
can't guarantee that the VM image that contains cloud-init has libvirt
(thats a large dependency) it would be nice if we could just use the python
interface (cloud-init is in python) and use the network writing
functionality of netcf to do this writing (without libvirt).
That seems doable?
Ok, yes, if you're looking for something to use from inside the
VM with cloud-init or similar, then using netcf directly would
make some sense.
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 :|