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

YANG model for current SnabbNFV configuration #911

Merged
merged 29 commits into from Nov 7, 2016

Conversation

eugeneia
Copy link
Member

@eugeneia eugeneia commented May 3, 2016

Initial YANG model for program.snabbnfv.nfvconfig. The namespace is imaginary obviously.

Cc @lukego

nfvconfig

range "0..max";
}

description "Gigabytes per second.";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be interpreted as Gigabits per second and not bytes. Why not use bps ?

typedef bps {
  type uint64;
  unit "bps";
  description "bits per second";
}

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, it should indeed say Gigabits.

@eugeneia
Copy link
Member Author

eugeneia commented May 4, 2016

This spec reflects the reality of SnabbNFV (literally a one-to-one translation from the API) and I would like to keep it that way. E.g. the (completely legitimate) issues pointed out here (except for my bits/bytes blunder) are really bugs in SnabbNFV imho.

This is a first win for YANG as it showcased the bad configuration of SnabbNFV. I will continue by fixing these issues in SnabbNFV and update the YANG spec accordingly, probably all in this PR since it tracks the bugs nicely.

@plajjan
Copy link
Contributor

plajjan commented May 4, 2016

Ok, understood :)

FYI, YANG is very strict when it comes to making modifications between revisions so for example you can't rename a leaf if you are to follow the rules. We might want to discuss how to deal with versioning (simple way is to put version in the name, like my-model-v1.yang).

@eugeneia
Copy link
Member Author

eugeneia commented May 5, 2016

I guess we should mark this PR as WIP and only merge a YANG spec once we are satisfied with it / SnabbNFV has a reasonable configuration API.

@eugeneia eugeneia changed the title YANG model for current SnabbNFV configuration [wip] YANG model for current SnabbNFV configuration May 5, 2016
Timo Buhrmester and others added 15 commits August 25, 2016 16:15
…re sophisticated approach without duplicating packets/copying data in the normal (non-resync) code paths
  - move all resync logic into resync method
  - use self.aes_128_gcm.auth_buf for packet regeneration
  - remember to free temporary packet used in resync
  - move auditing code into audit method
  - make auditing configurable as specified in RFC 4303
  - only log audits for packets that were actually rejected
  - update docs and comments
@eugeneia eugeneia changed the title [wip] YANG model for current SnabbNFV configuration YANG model for current SnabbNFV configuration Oct 27, 2016
eugeneia added a commit that referenced this pull request Nov 2, 2016
@eugeneia eugeneia merged commit 1ada400 into snabbco:master Nov 7, 2016
dpino pushed a commit to dpino/snabb that referenced this pull request Aug 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants