Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show child device's interfaces in parent device #823

Closed
hsychla opened this issue Jan 20, 2017 · 1 comment
Closed

Show child device's interfaces in parent device #823

hsychla opened this issue Jan 20, 2017 · 1 comment
Labels
status: duplicate This issue has already been raised

Comments

@hsychla
Copy link

hsychla commented Jan 20, 2017

We have a lot of network appliances that have a bay to add additional interfaces (like http://www.lannerinc.com/products/x86-network-appliances/rackmount/fw-8758).

We currently define the parent device type (fw-8758) with its GB-interfaces and a bay for the interface card.
We then define a child device type for the interface card which is then added to parent device's bay.

The problem is: after instantiating parent- and child-device and "inserting" the child device into the parent, I can not connect an interface or assign an IP to an interface of the interface card when looking at the parent device's page.

IMHO, by inserting the interface card into the parent device, the interfaces become interfaces of the parent device and hence should be configurable from the parent device's page.

@jeremystretch
Copy link
Member

Device bays are only meant to house discrete, autonomous devices (for example, a chassis of blade servers). Components which do not provide their own control plane (for example, a line card in a chassis switch) should be installed as modules.

Incidentally, #824 was just opened to foster detailed discussion around this concept, so I'm going to mark this as a duplicate of that issue. Please feel free to share any additional thoughts there.

@jeremystretch jeremystretch added the status: duplicate This issue has already been raised label Jan 20, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised
Projects
None yet
Development

No branches or pull requests

2 participants