...
Resource descriptor: to get more information about how it works, you can use this link.
Resources states
A resource is in a set of states which it permits do or not a set of operations. This picture describes these states:
Mainly, a resource will activate all its capabilities if it is started. For this reason, the next step will be start our resource:
| Code Block |
|---|
resource:start router:junos20
|
Adding protocols
Each resource has to be linked to the necessary protocols which are used to connect with the physical device (the real router which we want to virtualize). In this case, we will use a netconf protocol to connect with the router:
| Code Block |
|---|
protocols:context router:junos20 junos20 netconf ssh://myuser:mypassword@193.1.190.254:22/netconf |
Description of the connection parameters:
- router:junos20 - specify resource type (router) and resource name (junos20). It specifies what resource will use this protocol
- netconf - name to describe which protocol it will be used
- ssh://myuser:mypassword@1.1.1.1:22/netconf - URI to describe connection parameters.
Panel
...
The
...
format
...
is:
...
transport://user:password@ip:port/subsystemThe parameters are quite easy to understand. The subsystem param specifics any extra necessary parameter to specify in the connection.
Resources states
A resource is in a set of states which it permits do or not a set of operations. This picture describes these states:
Mainly, a resource will activate all its capabilities if it is started. For this reason, the next step will be start our resource:
| Code Block |
|---|
resource:start router:junos20
\]_
The parameters are quite easy to understand. The subsystem param specifics any extra necessary parameter to specify in the connection. |
Doing operations with the resource
...