On Fri, Nov 20, 2015, at 01:25 PM, Dusty Mabe wrote: > See attached patch for making atomic host have eth0 be the interface by > default: So this is something like the addition of dracut-network by default for PXE-to-Live got us networking in the initramfs, which in turn broke the ifnames change? Your link was only talking about Vagrant, but this change will affect *all* uses of the cloud image, such as EC2, OpenStack, etc. Now, we were clearly *intending* to do this for a long time, going back to what (I believe) mattdm did with the original Fedora Cloud image. That said, while clearly a number of people just do cloud instances with one NIC and hence predictable = eth0 is fine, it's really quite valid to use multiple NICs in any kind of nontrivial situation. And once one does that, the rationale for PIN becomes apparent. I admit I'm only a light EC2 user, so I can't comment on this patch from that angle. From an OpenStack (specifically KVM) point of view, one really important thing to note is that recently virtio-net enumeration order was declared stable: https://github.com/systemd/systemd/commit/54683f0f9b97a8f88aaf4fbb45b4d729057b101c Which definitely affects upgrades. It's worth noting that *currently* on KVM on Fedora 23 one gets PIN due to that change, and this would revert it. I'd like to explore this vagrant issue more to understand how PIN is breaking it. _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
