OK, so if I interpreted your question correctly, you have a couple of things here to think about.
Firstly: it seems that you are being confused by the new network interface naming nomenclature introduced in CentOS 7. In theory, this nomenclature is actually more predictable than the previous one (just a bit less intuitive/readable).
The naming works as follows (from the Red Hat documentation):
Two character prefixes based on the type of interface:
en -- ethernet
sl -- serial line IP (slip)
wl -- wlan
ww -- wwan
Type of names:
b<number> -- BCMA bus core number
ccw<name> -- CCW bus group name
o<index> -- on-board device index number
s<slot>[f<function>][d<dev_port>] -- hotplug slot index number
x<MAC> -- MAC address
-- PCI geographical location
-- USB port number chain
So, you should actually be able to predict the interface name based on knowledge of the board (or to be more basic - if you're using the same board every time, you could just deploy once and see what the interface(s) in question are named to, and use that.
Secondly, you can actually disable this new nomenclature if you so choose, which is actually something which has been covered before in this context here on SF:
You may use the bootloader section in the kickstart file to suppress
predictable network interface names.
Adding net.ifnames=0 and [if needed] biosdevname=0 to the --append
should do what you're asking.
bootloader --location=mbr --append="net.ifnames=0 biosdevname=0"
However, this is of course just a workaround - it might be a good opportunity to take this prompt to just familiarise yourself with the new nomenclature and how it works.