-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 23 Nov 2014 10:57:51 -0500
Colin Walters <walters(a)verbum.org> wrote:
I do not remember the exact details but link was not working for some
reason. we can change rawhide but should not change f21 at this point.
Longer story:
I tried the CentOS 7 GenericCloud image:
http://cloud.centos.org/centos/7/devel/
and it didn't have networking on boot. Let's look at the actors:
- A base cloud image: Fedora 20, Fedora 21, CentOS 7
- Network configuration: As specified in the kickstart
- A network driver: virtio-net, rtl8139
- virt-install guest autodetection: Determines whether or not you
get virtio-net
- network system (or NetworkManager, or systemd-networkd)
- systemd:
http://lists.freedesktop.org/archives/systemd-devel/2014-July/020906.html
- Anaconda/kickstart behavior
First, let's look at the current F20:
https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-cloud-b...
It hardcodes eth0. And the version of systemd there uses eth0 for
virtio-net.
Now, let's look at some changes Dennis committed in the F21 cycle:
ens3:
https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&i...
link:
https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&i...
eth0 (but only for atomic):
https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&i...
These were committed because things kept changing in the guests. it was
all break fix. which is the only time I touch the non arm kickstarts.
Sending patches slows down the testing process and is not tenable. you
should watch the commits on spin-kickstarts list where all commits are
sent if you care to follow the changes.
(Dennis and others, can you send patches to the list for review?
This issue would have been more obvious if I'd noticed the changes
going by)
A really critical variable here is whether or not libvirt guest
autodetection works. Currently:
libvirt automatically provides virtio-net: Fedora 20, Fedora 21
Generic libvirt gives you rtl8193: Fedora 21 Atomic, CentOS 7
It took me a while to figure out here that the reason the CentOS 7
image wasn't working was becuase of the libvirt autodetection.
the network autodetection is broken and systemd's predictable naming
actually makes it unpredicatable in the cloud/vm use cases.we probably
should explicitly turn it off in the boot arguments.
I have this utterly trivial "create-cloud-vm.sh" script
I've been
using:
https://gist.github.com/cgwalters/a366c14b2fc58e0f7367
It does work if I specify --os-variant rhel7 for CentOS7. Which I'm
now going to start doing by default in my script (I don't use it to
boot anything else).
But...the change to do DHCP on all links by default is also an
important change. One we should highlight in the release notes.
_______________________________________________ cloud mailing list
cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct:
http://fedoraproject.org/code-of-conduct
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJUcnEAAAoJEH7ltONmPFDRMXkP/2zD0j5gVbPsFQR4MF6ESI0t
Du5TZO9irv0cPncuOTtM4gR14SiwGH7x18NHcKkM0QzT2ZiSBm8hoypA6tNLsDRe
PPenleXDP1wWhssbtiiILrj481xHGR4MFzLQOLRHY2L/LmmmZQUInAcGNmvkZZjT
WxWUT1JfDGObxDAjTmwFIa+HWUkNP/j+lWiyBlkeFrpJcEkuoJsLD3232vOAljRA
aZyGAcvETRHJtxnvEDtmxOY9K6TUB/ISV4F46+ebLhZISe8HxidEA3a2nGYwzg6L
Pn9LDGQsF2cireFqxSE74zi+aINpp87xEG2cTV3/KAAPOITJ05ptQNbCF5aLR+Vx
xEDqvEHDOCzr+xOkVrU5vxncsPEyU6ucazDC/pfbVEjXxiYgh7iuIA/QQ+LjvmjR
WlyfqQC1hX+EULdpytqV4DGRewkg+23PYE2e2hyWSF0On6igcpvX8GVDd0jsdrQ9
tFxo1L6yCKjmWN8gFNA3Pwmb/uKfvg5jx/J7BtdJBwfJ7oR1yNH4HVBrv8wMYjhg
ONrTwMijbjyt+W+KaTpTb0Mj96qQfp5GpzKTqGFWLA1R2itNdf9K2z926H0Jbjxl
f0Lhkq+KL4ragVU1s++JZIrjZzLq5kaqDjaQziqkUc/McXZ/N/oIELTU621ZXHSD
ZmHntXuFmW/PldX60Yd/
=ai5U
-----END PGP SIGNATURE-----