NSO on GitHub
Share code on NSO GitHub.
Last updated
Was this helpful?
Share code on NSO GitHub.
Last updated
Was this helpful?
We have created a public organization on GitHub to ensure we have one common place to share code for all of us working with NSO.
Since the NSO Developer is a public GitHub everyone can fork and read the uploaded code. By using a pull request everyone can also contribute to existing projects.
If you want to contribute to a new project, please read the instructions below.
The license tells you what rights you have that are provided by the copyright holder. It is important that the contributor fully understands what rights they are licensing and agrees to them. Sometimes the copyright holder isn't the contributor, such as when the contributor is doing work on behalf of a company.
To ensure that the criteria in the license are met, there is a need for a Developer Certificate of Origin (DCO) sign-off on all contributions. More information about that can be found below.
Create an account on github.com.
Create your own repository on github.com.
Make sure that your project fulfills all the criteria listed below (under “Requirements on your project”).
That’s it! When the move is done, your repository is now part of the NSO developer. Keep hacking on your project, you will still have owner privileges, and as such you can decide to give others write access for example.
Users of your repository can use Issues to report bugs and suggest new features, and Pull Requests to contribute code.
When using packages from the library you can expect the following:
The code you find is provided “as is” and when you use it you get to keep it. If it breaks, you get to keep all the pieces.
If you extend a project or fix bugs, please contribute back in the form of pull requests.
When contributing you can expect:
The code you contribute is made available to everyone in source form “as is”.
Your code might be used to: teach others about NSO, build new products, and provide a starting point for customer projects.
At the very minimum, your contribution should have a title and a short README.md explaining what it does, see the full list of requirements here
You are not required to support your contributed code, but please consider pull requests and try to answer questions in the project wiki
Only contribute code for which you own the IPR
Do not include explicit references to customers (be it customer names, network configuration/templates, or otherwise)
Before your project can be accepted as a repository of the NSO Developer it needs to fulfill the following criteria.
When using the NSO-develop-hub every commit needs to be signed off (git commit –s) by the contributor that he or she has the right to submit it. The -s flag adds a line with the text 'Signed-off-by' followed by the same email address as the contributor. E.g.:
It is important that the git config user.name and user.email is configured correctly.
When creating a pull request every commit in that pull request will be checked for DCO, if you haven’t signed all commits the checks will fail and the pull request will be denied.
Therefore it is a good idea to sign all commits before doing the pull request.
Sure, it could be a cool YANG plugin too - but it should at least be relevant to NSO development.
Choose a name. A good name. A catchy name, a nerdy name, a happy name - you decide. This is especially important if your contribution is a tool or a reusable library. In that case, it doesn’t even have to be descriptive. Better YxT than “YANG Extension Tool”. Don’t pick “generic-tool”, “misc-template”…
If your contribution is more of a demo or example, then a more descriptive name could be in order, perhaps even pre- or postfixed with a demo or example. For example: l3-vpn-demo or example-stacked-service.
Add a README.md. Your README must include:
A brief explanation of what your project does.
List dependencies (build and runtime, for example, compilers, libraries, operating system).
Instructions on how to build it.
If your project contains any copies of code derived from open source you need to explicitly list which projects.
The whole point of the NSO Developer space is to share code to the NSO ecosystem, as such we don’t want to make it “private”. However, that means that anyone can access the NSO Developer repositories, which requires us to approve the open access and ensure that no private information is included.
The information in the README.md file will be displayed on the Cisco NSO DevNet site.
Add test cases and instructions on how to run them. Why not use Lux to automate your tests? NSO uses it!
Packaging makes one repository for every stand-alone project. But don’t make a lot of small repositories of things that actually belong together, it just makes the space cluttered and it will be harder to find your project.
The naming convention for YANG modules. For a demo or example the module name and namespace does not matter that much (you can use example.com/... as a namespace). But if your project is a reusable piece, then consider using the URL of the project the namespace (as in: github.com/NSO-developer/PACKAGE-NAME/MODULE-NAME).
If you make some kind of release, consider tagging the releases and using a Changes file / Release Notes document.
All material on the NSO Developer space on GitHub is under the . The license is used to ensure a balance between open contribution and allowing you to use the software as you like to.
Send an email to the NSO Developer librarians with a link to your repository ().
You will be added as an outside collaborator to a new repository on the and will be asked to contribute your code there.
.
When/if you do not have time to keep your project up to date (fix issues, accept pull requests, etc.) - please say so. Write a line in the README.md, as well as an email to - we will try to help you find a new maintainer of the code, or retire it from the library if it appears abandoned for a long time.
[user] name = Aron Aronsson email =
In short, you are signing off that you have the right to submit the code to the developer hub, and that you understand that it will be public. The full text can be found at and also here:
