New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource Manager #41

Open
IanKruger opened this Issue Jul 25, 2018 · 0 comments

Comments

2 participants
@IanKruger
Member

IanKruger commented Jul 25, 2018

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:updated <update>, the resource usage is updated.

When designing a :ref:service <services>, the chosen YANG models are scanned for type definitions. Certain types can be linked to resource pools. For example, the RFC 6991 type definition of ipv4-address is linked to IPv4 resource pools. As such, the resource pools can be associated to those entries in the YANG models so that the entries can be automatically assigned from the next available resource in the pool when a :ref:Service is requested <service_request>.

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:service <services>.

@IanKruger IanKruger added this to the Netrino Beta milestone Jul 25, 2018

@IanKruger IanKruger added this to To Do in Orchestrator via automation Jul 25, 2018

@cfrademan cfrademan moved this from To Do to In Progress in Orchestrator Aug 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment