Re: Resend: Anaconda modifying network files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bryan Kearney wrote:


Michael DeHaan wrote:
As far as I'm aware the "appliancey" way to reuse disk images is to login in and fix all this once you fire the machines up. This is something you could possibly
make firstboot do.

So.. each boot would need to do this, since in theory the mac address could change between launches.

(Hmm, thought I replied to this, if so, apologize for the double-post).

No, the MAC address should travel with the VM config.


The approach we took with Virt-Factory is to not use disk images, but start the install fresh every time, and use config management to push
changes down.

In a controlled environment, or once koan takes over the world, I would agree. However... this will not work in all cases (e.g. demo applliances, or operating systems with no public tree)

In demo-ware, you shouldn't care about the MAC being persistant and DHCP should be your friend. As for no public tree cases, well, we're talking images, aren't we? If so, it's not /really/ kickstart-list anymore... you have the opportunity to log in, fix them up right, before redistribution, no?



_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list

_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list

[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux