Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Resource Manager #41
In order to provide a service, one typically requires resources. For example, this could be things like IP address, VLAN number, device port or BGP community such as a route-target. These are collectively referred to as resources.
Netrino has a built-in resource manager for which the idea is to eventually cater for both for green field and brown field scenarios.
When creating a resource pool, it is given a type (eg. IPv4) and a range. The actual resource usage is stored in a different table that references this pool. In the brown-fields scenario, whenever an element is :ref:
When designing a :ref:
Resource pools thus have an optional associated list of YANG type definitions.
Resource pools can be globally significant (e.g. public IPv4's) or element-significant (eg. VLANS on a switch). Unless specified otherwise, global is assumed. If locally significant is specified during the creation/updating of a resource pool, then the element or element tag has to be specified that this resource pool is linked to.
Elements can also be resources. When elements are to be auto-allocated, an element tag must be associated to the specific YANG model in the :ref: