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

IP address configuration support for interfaces in south-ocnos #72

Open
pedrosouzajr opened this issue Dec 19, 2022 · 5 comments
Open
Labels
enhancement New feature or request

Comments

@pedrosouzajr
Copy link

pedrosouzajr commented Dec 19, 2022

This issue discusses how to support the IP address configuration when we have the OcNOS available.
The proposal to support this configuration considers adding a module called goldstone-ocnos making an augment of the goldstone-interfaces module as displayed below:

module: goldstone-ocnos
  augment /gs-if:interfaces/gs-if:interface:

    +--rw ipv4
       +--rw addresses
       |  +--rw address* [ip]
       |     +--rw ip        -> ../config/ip
       |     +--rw config
       |     |  +--rw ip?              inet:ipv4-address
       |     |  +--rw prefix-length?   uint8
       |     +--ro state
       |        +--ro ip?              inet:ipv4-address
       |        +--ro prefix-length?   uint8
       |        +--ro origin?          ip-address-origin
       +--rw config
       +--ro state

Please, notice that neighbors container inside goldstone-ipv4 is not considered in this first step.

@ishidawataru
Copy link
Contributor

Do we need to consider if we can assign an IPv4 address to an interface when the interface belongs to one or more VLANs?

@ishidawataru ishidawataru added the enhancement New feature or request label Dec 20, 2022
@ipi-claytonpascoal
Copy link

Do we need to consider if we can assign an IPv4 address to an interface when the interface belongs to one or more VLANs?

Thank you for pointing that out.
Yes, on OcNOS an interface is either a switch port or a router port so it is not allowed to assign an IP address to an interface belonging to a VLAN
Kindly asking @pedrosouzajr to consider adding a constraint to cover this case.

@pedrosouzajr
Copy link
Author

pedrosouzajr commented Dec 22, 2022

Thank you all for pointing that out.
So, to attend to this constraint which was suggested the goldstone-ocnos.yang was changed to add a 'must' statement for this purpose.
Please, consider this new version: goldstone-ocnos.yang

@ipi-claytonpascoal
Copy link

@ishidawataru @anazawa-kazuya
Please notice that we are not willing to support /gs-if:interfaces/interface/gs-ocnos:ipv4/neighbors in this first step.
Can we move on and create a pull request including the goldstone-ocnos module as proposed in this discussion?

@KazuyaAnazawa
Copy link
Contributor

@pedrosouzajr @ipi-claytonpascoal I think we can proceed with the model you proposed (though we may need to fix or add some minor parts during actual implementation of south-ocnos). Then, we can finalize the model while implementing south-ocnos as comments here.
Also, let's create and submit a PR of goldstone-ocnos.yang with actual implementation of IP handler part of south-ocnos after we completed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants