Project

General

Custom queries

Profile

Actions

Feature #6444

closed

Add ancestry NICs and allow interfaces with same MAC

Added by Marek Hulán almost 11 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Network
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

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.


Related issues 4 (2 open2 closed)

Related to Foreman - Bug #6787: Turn off the validation on ip addressesNew07/26/2014Actions
Related to Foreman - Tracker #2409: NetworkingNew

Actions
Related to Foreman - Bug #7344: unable to import interface facts for certiain network configurationClosedMarek Hulán09/03/2014Actions
Blocked by Foreman - Refactor #6560: Extract puppet specific fact parsing logic to isolated classClosedMarek Hulán07/10/2014Actions
Actions #1

Updated by Lukas Zapletal almost 11 years ago

Since Foreman now uses tokens by default, I wonder if we can turn the uniquess off completely.

Actions #2

Updated by Marek Hulán almost 11 years ago

  • Status changed from Assigned to Ready For Testing
Actions #3

Updated by Marek Hulán almost 11 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?

Actions #7

Updated by Marek Hulán almost 11 years ago

  • Status changed from Ready For Testing to Assigned

We should add also some UI to define various network types. Also we should parse facts and create/update interfaces. Hence changing back to assigned.

Actions #14

Updated by Marek Hulán over 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF