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

Multiple FabNetExt services for the same site do not trigger a validation error #187

Closed
kthare10 opened this issue Jun 20, 2023 · 3 comments
Assignees
Labels
1.6 For release 1.6

Comments

@kthare10
Copy link
Collaborator

Create a slice with 2 VMs
Add 2 FabNetv4Ext services at the same site
Slice can be created despite the validation rule of allowing one FabNet service per site

@ibaldin ibaldin added the 1.6 For release 1.6 label Jul 11, 2023
@ibaldin ibaldin self-assigned this Jul 11, 2023
@ibaldin
Copy link
Contributor

ibaldin commented Sep 15, 2023

  • In ASM we expect a single L3 service (FABNetv4[Ext] or FABNetv6[Ext]) per site. These services connect interfaces of the nodes within the site in ASM.
  • In ARMs there is a FABNetv4[Ext] or FABNetv6[Ext] attached to each site switch.
  • Current validation rules have no limit on the number of instances.

@ibaldin ibaldin mentioned this issue Nov 8, 2023
@ibaldin
Copy link
Contributor

ibaldin commented Nov 9, 2023

Fixed by 8d4b095 on #194

@ibaldin ibaldin closed this as completed Nov 9, 2023
@ibaldin
Copy link
Contributor

ibaldin commented Nov 12, 2023

Modified the structure of validation for network services to include a section that validates network services in the entire model (thus e.g. counting how many instances of a particular service type per site there are).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.6 For release 1.6
Projects
None yet
Development

No branches or pull requests

2 participants