Skip to content
Snippets Groups Projects

Resolve "TNC improvements"

Merged Resolve "TNC improvements"
74-tnc-improvements into master
Merged Vojdan Kjorveziroski requested to merge 74-tnc-improvements into master
Viewing commit 8c74a24c
Prev Next
Show latest version
1 file
+ 15
− 17
Compare changes
  • Side-by-side
  • Inline
docs/managed-nmaas/nmaas-playground-instance.md
+ 15
− 17
# NMaaS Playground Instance
# nmaas Playground Instance
## Introduction
NMaaS Playground is an NMaaS central installation that can be used by anyone interested in testing latest versions of NMaaS.
The nmaas Playground is a central installation that can be used by anyone interested in testing latest versions of the nmaas Platform.
It is available at [https://nmaas.geant.org](https://nmaas.geant.org).
NMaaS Playground is deployed on GÉANT's infrastructure and is maintained by the NMaaS Team.
The nmaas Playground is deployed on GÉANT's infrastructure and is maintained by the nmaas Team.
Any questions or requests related with using the NMaaS Playground should be directed to [nmaas@lists.geant.org](mailto:nmaas@lists.geant.org).
Any questions or requests related with using the nmaas Playground should be directed to [nmaas@lists.geant.org](mailto:nmaas@lists.geant.org).
It is important to note that the NMaaS Playground is tailored to enable users to browse and deploy NMaaS tools right away without any unnecessary overhead. However, this implies that the user isolation, access and data security rules applied on this NMaaS installation are not so strict as in the case of the official NMaaS production service (e.g. no dedicated VPNs are deployed).
It is important to note that the nmaas Playground is tailored to enable users to browse and deploy nmaas tools right away without any unnecessary overhead. However, this implies that the user isolation, access and data security rules applied on this nmaas installation are not so strict as in the case of the official nmaas Virtual NOC production service (e.g. no dedicated VPNs are deployed).
!!! warning Usage Disclaimer
NMaaS Playground should be used only for testing purposes and not for monitoring of actual user equipment
The nmaas Playground should be used only for testing purposes and not for monitoring of actual user equipment.
For any information on how to use NMaaS refer the official NMaaS User Guide.
For any information on how to use nmaas refer the official [nmaas User Guide](../guides/user-guide.md).
## Accessing the Playground
## Accessing the nmaas Playground
In order to use the Playground a new user should either fill in the registration form to create a local account in the system or use the Federated login option.
In order to use the nmaas Playground a new user should either fill in the registration form to create a local account in the system or use the Federated login option.
In both cases, the system administrator will have to manually add the new user to a Test domain that is pre-configured in the system.
NMaaS domain corresponds to an institution, team or project (e.g. NREN, end institution, team within the GÉANT Project) whose users will be able to deploy instances of tools available in the NMaaS portfolio in order to manage and/or monitor the equipment within that domain.
An nmaas domain corresponds to an institution, team or project (e.g. NREN, end-institution, team within the GÉANT Project) whose users will be able to deploy instances of tools available in the nmaas portfolio in order to manage and/or monitor the equipment within that domain.
## Deploying NMaaS Tools
## Deploying nmaas Tools
The main purpose of using the NMaaS Playground is to deploy and access test instances of NMaaS Tools. From more information about the tools currently supported by NMaaS refer to [the application list](../nmaas-applications/application-list.md).
The main purpose of using the nmaas Playground is to deploy and access test instances of nmaas Tools. From more information about the tools currently supported by nmaas refer to [the application list](../nmaas-applications/application-list.md).
Running a network management tool without any equipment that can be monitored would not present the full potential of NMaaS. Therefore a virtual user network with various types of devices has been deployed and connected to the Test domain.
Running a network management tool without any equipment that can be monitored would not present the full potential of nmaas. Therefore a virtual user network with various types of devices has been deployed and connected to the Test domain.
While deploying a tool in the NMaaS Playground users can choose any subset of available devices to be monitored.
While deploying a tool in the nmaas Playground users can choose any subset of available devices to be monitored.
The following table presents all the equipment available in the virtual user network together with any relevant information that later on needs to be provided in the configuration wizard during deployment of particular tool.
@@ -39,12 +39,10 @@ For example when deploying new instance of the Oxidized application, the user wi
| Device Identifier | Device Type | IP Address/URL | SSH Username/Password | SNMP Version/Community |
|-------------------|---------------------------|----------------|---------------------------|------------------------|
| ... | ... | ... | ... | ... |
| vmx-31 | Virtual Juniper MX Router | 10.0.0.31 | `geant` / `geant123` | v2c / `nmaas-public` |
| vmx-c1 | Virtual Juniper MX Router | 10.0.0.1 | `geant` / `geant123` | v2c / `nmaas-public` |
| vmx-c2 | Virtual Juniper MX Router | 10.0.0.2 | `geant` / `geant123` | v2c / `nmaas-public` |
## Demo Instances of NMaaS Applications
## Demo Instances of nmaas Applications
A set of tools have been deployed by default in the Test domain and configured to monitor the resources of the virtual user network and servers.