OpenNSA development wiki
| Table of Contents | ||
|---|---|---|
|
Useful links
Installation Guide
...
Documentation of features and configuration
...
Development descriptions
Geant OpenNSA GIT repository
Web front end link: https://code.geant.net/stash/projects/CCS/repos/opennsa/browse
...
- All new features should be developed in their own branch based on master !
- When the feature will be in testing ready state, it should be done also with domain aggregate feature. Until domainagg will be merged into master, such testing has to be done by creating new branch based on domainagg and then merge the feature branch into it and make tests.
- When new feature is tested. It should be sent upstream to Nordunet (to Henrik) for validation. When/If accepted, Henrik will merge it into the stock OpenNSA repo and then we can pull it from there to our local master (and domainagg, until merged into master).
Tracking the work in JIRA
Currently developed features and bug fixes are track using JIRA tickets here: https://issues.geant.net/jira/projects/JRA2CCS/summary/statistics
Development lab environment
| Resource | Where it is. | Access | Description/Notes |
|---|---|---|---|
| Junos SPACE |
| 10. |
| 0. |
| 20. |
| 3 |
Web GUI on public IP.
TODO add link
TODO add credentials to the table in restricted page.
Access credential can be found on this page protected page. |
with same credentials. | Use this for any Junos SPACE testing. | ||
| OpenNSA dev. VMs default and testing | 10.0.20.10 | Only default, when providing clone to others ... change the password. | |
| OpenNSA "E-Line" | 10.0.20.11 | User: taas ; password or restricted page | |
| OpenNSA dev for use with Junos SPACE | 10.0.20.17 | User: taas ; password or restricted page | |
| OpenNSA - Docker | 10.0.20.13 | User: taas ; password or restricted page | For Jan von Oorschot |
| OpenNSA - Ciena | 10.0.20.14 | User: taas ; password or restricted page | For Bjarke |
Laboratory routers port allocation
Lab1.MX80
| Port range | Porpose | Note |
|---|---|---|
| Ge-1/0/0-4 | GTS links and VPLS on Lab1.Compute0 | VPLS on ge-1/0/0 |
| ge-1/0/5-10 | OpenNSA and CCS development | |
| ge-1/0/11 - 1/1/0 | Pavle's testbed | |
| xe-0/0/0 | link to lab2.mx80 | |
| xe-0/0/1-3 | GTS Corsa and BMS | |
Lab2.MX80
| Port range | Porpose | Note |
|---|---|---|
| Ge-1/0/0-4 | GTS links and VPLS on Lab1.Compute0 | VPLS on ge-1/0/0 |
| ge-1/0/5-10 | OpenNSA and CCS development | |
| ge-1/0/11 - 1/1/0 | Pavle's testbed | |
| xe-0/0/0 | link to lab2.mx80 | |
| xe-0/0/1-3 | GTS Corsa and BMS | |
Junos SPACE backend development
Junos SPACE backend is being developed for the use in GEANT production network. Currently the first naive prototype is being used and improvements are under the development. Assignee Jan Kundrát .
Development VM is listed in table above (at 10.0.20.17).
The setup is done as follows:
The aggragator is deployed at 10.0.20.17:9443 (network id: nsi.eline.test ) with two uPAs underneath.
The first uPA is at 10.0.20.17:9444 (network id: upa1.nsi.eline.test ), the second is being deployed and will be at 10.0.20.17:9445 (network id: upa2.nsi.eline.test ). Both uPAs are using junosspace backend and are configured against lab Junos SAPCE at 10.0.20.3 (https://10.0.20.3/api/space) using the user "super".
OpenNSA branch domainagg.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
[junosspace]
space_user=super
space_password=PASSWORD_IN_RESTRICTED_PAGE
space_api_url=https://10.0.20.3/api/space
configlet_activate_local=328159
configlet_activate_remote=328147
configlet_deactivate_local=328124
configlet_deactivate_remote=328137
routers=upa1.nsi.eline.test:131091:10.0.16.1
upa2.nsi.eline.test:131097:10.0.16.2 |
Topology of uPA1:
| Code Block | ||
|---|---|---|
| ||
ethernet port9 - vlan:10-100 1000 ge-1/0/9 - |
ONSA cli tool config and ussage:
| Code Block | ||
|---|---|---|
| ||
bandwidth=250
host=10.0.20.17
port=7080
starttime=+20
endtime=+6020
nsa=main,nsi.eline.test:nsa,http://10.0.20.17:9443/NSI/services/CS2 |
| Code Block | ||
|---|---|---|
| ||
# For activate the link on the lab1 router (the crossconnect hairpinned on single interface in this example).
onsa reserveprovision -v -p main -s upa1.nsi.eline.test:topology:port9#vlan=20 -d upa1.nsi.eline.test:topology:port9#vlan=21
#The activation will return the link ID which identifies the service.
#For termination of the service use the following
onsa terminate -v -p main -c LINK_ID
|
OpenNSA Docker environment
Jan van Oorschot TODO: describe it here....