On Thu, Sep 25, 2014 at 05:23:22PM +0200, Pasquale Porreca wrote: > This is correct Daniel, except that that it is done by the virtual > firmware/BIOS of the virtual machine and not by the OS (not yet installed at > that time). > > This is the reason we thought about UUID: it is yet used by the iPXE client > to be included in Bootstrap Protocol messages, it is taken from the <uuid> > field in libvirt template and the <uuid> in libvirt is set by OpenStack; the > only missing passage is the chance to set the UUID in OpenStack instead to > have it randomly generated. > > Having another user defined tag in libvirt won't help for our issue, since > it won't be included in Bootstrap Protocol messages, not without changes in > the virtual BIOS/firmware (as you stated too) and honestly my team doesn't > have interest in this (neither the competence). > > I don't think the configdrive or metadata service would help either: the OS > on the instance is not yet installed at that time (the target if the network > boot is exactly to install the OS on the instance!), so it won't be able to > mount it.
Ok, yes, if we're considering the DHCP client inside the iPXE BIOS blob, then I don't see any currently viable options besides UUID. There's no mechanism for passing any other data into iPXE that I am aware of, though if there is a desire todo that it could be raised on the QEMU mailing list for discussion. Regards, 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
