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

XML schema comparation according to Openconfig models. #125

Open
danielhbar opened this issue Feb 4, 2021 · 2 comments
Open

XML schema comparation according to Openconfig models. #125

danielhbar opened this issue Feb 4, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request Medium Priority to do.

Comments

@danielhbar
Copy link
Collaborator

danielhbar commented Feb 4, 2021

Date: 02/10/2020

Username: Daniel Hernández

Issue: XML Schema comparison according to Openconfig models. #125

As a:

Currently, we don't have a tool to compare any OC standards models with the vendor implementation.

Each network equipment has yang files charged in a folder, each yang files corresponding with the vendor implementation of OC models.

For example, there is an OC model (openconfig-routing-policy.yang) and the vendor implementation is (oc-routing-policy.yang).

At this moment we must review manually the correct standard compliance (paths of the parameters, parameters mandatories, value types) and compare with the corresponding OC model.

And determine the implementation deviation percentage of each vendor with their details and knows which one's parameters it does not support.

I want:

A tool that compares the OC Models standard with the implementation vendors OC, introducing both model's paths and generate an excel report with the below information:

  • Deviation percentage according to differences like a (paths of parameters, parameters mandatories, and value types).

  • List of differences (path of parameters, parameters mandatories, and value types.) showing which one is the correct path and the incorrect path, correct parameters mandatories and incorrect parameters mandatories, correct value types, and incorrect value types.

  • Which parameters are missing in the OC model implementation of the vendor.

This must compare with the standard OC models.

So that:

It will permit, that we will know the real support percentage of vendors per model and determine which parameters are supported or has any deviation to make the XML and YML according to this information. Other benefits without a doubt are the time that we must spend looking for parameter deviations.

Accept Criteria:

Testing tool.

@sbarguil sbarguil assigned sbarguil and danielhbar and unassigned sbarguil Feb 10, 2021
@sbarguil
Copy link
Owner

@ Daniel enhance issue description.

@danielhbar
Copy link
Collaborator Author

Done, changed for user history.

@danielhbar danielhbar added enhancement New feature or request Medium Priority to do. labels Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Medium Priority to do.
Projects
None yet
Development

No branches or pull requests

2 participants