Thanks a million for the suggestion .. I was able to work around this though, by modifying the preceed files and creating matching KVM network (yeah, forgot to mention I am using KVM) ..
BTW, I have finally managed to get it fully functional .. after umpteenth attempts .. ;-) .. Have actually deployed a couple of openstack nodes and dhcp/pxe/dns worked fine to support that process .. The final significant change I made was in changing the admin network to nat instead of routed .. but keeping the public network routed .. So, what is the quickest way to get to grips with how the system is supposed to work? .. (I mean beyond documents describing general architect .. ) .. for instance, how to ensure we can start segments of the service? Where to authoritatively check for signs of issues, etc? Thanks again for the suggestion .. I have to say though, the ease with which I provisioned these 2 nodes is amazing and has made the hassles worthwhile .. On 20 November 2013 23:50, Shane Gibson <[email protected]> wrote: > Chux, > > See below - I¹m only referencing that which I can actually help you with. > Someone else will have to chime in on the other stuffŠ > > > On 11/20/13, 2:27 PM, "Chux Uzoeto" <[email protected]> wrote: > > > assumptions made by the admin server in terms of network, ubuntu folks > >also hardcoded a network of 192.168.1.0 (instead of 192.168.124.0) .. and > >again, this created issues with bringing up > an admin node VM .. > > > I currently modify the Admin ISO image extra/common_install.sh script at > the very end to wire up the admin node with it¹s correct (for me) IP > address. > > If you modify files, don¹t forget to either update the sha1sums in the > root of the ISO, or simply delete that line item from the sha1sums file. > > ~~shane > > >
_______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
