Add ancestry NICs and allow interfaces with same MAC
Virtual interfaces can have same MAC addresses so we should validate uniqueness only for physical interfaces. I'll add ancestry to NICs table, parents will be physical interfaces.
Fixes #6444 - add support for virtual NICs
Extend additional interface details refs #2240
NIC facts parsing change and we create interfaces in Foreman according
to facts we recieve.
Subclasses does not define their own attributes and serialize them to
attrs hash. All BMC attributes are extracted to separate columns so it's
possible to search NICs by those attributes. Attrs can still be used for
custom attributes (e.g. coming from facts).
NIC form was ajaxified which means that we redraw the form for
particular interface class. We can easily define custom forms for
various interfaces types.
Added support for virtual and physical interfaces. Initial support for bridges
(to keep tests green). New attributes can be set via UI as well.
IPMI facts parsing and BMC NIC creation based on custom facts that are
present in discovery image.
NIC orchestration is now optional and can be set for every interface.
All created interfaces based on facts (BMC or Managed) are not
Store and update primary interface identifier in host.
Allow subnet selection without domain for NIC so we can use DHCP only.
Suggest IP addresses even without proxy by Foreman itself. Foreman finds
first free IP on a particular Subnet based on records in database.
#3 Updated by Marek Hulán about 6 years ago
I don't think it's a good idea to turn off validation. At least it will let you know that you may have some conflicting device. On the other hand, our validation may be to strict for NICs belonging to different subnets. If you think it's and issue, could you please open another issue?