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

Element Manager API #20

Closed
cfrademan opened this Issue Apr 18, 2018 · 0 comments

Comments

3 participants
@cfrademan
Member

cfrademan commented Apr 18, 2018

Netrino has two reasons for communicating with devices. One is for information gathering, the other for configuring. Different devices have different methods and protocols available for these purposes. The aim for Netrino is to be as flexible as possible (thus allowing multiple methods to communicate to devices, and providing the option to choose which) and as extensible as possible (allowing for future-proofing by catering for the seamless addition of new methods).

The devices on which Netrino has to orchestrate services, are referred to as elements. Netrino needs to store a list of these elements, for the purpose of making them available as options when services are to be provisioned on them.

Typically, elements will have an IP address associated, which is used for communicating with the device. However, it is foreseen that Netrino is to know about devices which it can not communicate with. An example would be a cabinet in which devices are mounted. For this reason, an IP address is not a required value when storing an element's details.

Elements should have at least a name. For servers and network devices like routers, this would eg. be the hostname. The primary key used to reference elements is a UUID, which allows one to change an element's IP and/or hostname without losing any back references.

Netrino communicates with devices through what is known as South-bound Interfaces, just referred to here as "interfaces". These interfaces are python modules. They register themselves as python entry points called netrino_interfaces to make their presence known to Netrino. Netrino comes with a couple of built-in interfaces (netconf, ansible, snmp, openstack, contrail) but also provides the ability to easily add new interfaces.

@cfrademan cfrademan added this to To Do in NFV Automation via automation Apr 18, 2018

@cfrademan cfrademan self-assigned this Apr 18, 2018

@cfrademan cfrademan added this to To Do in Orchestrator via automation Apr 18, 2018

@cfrademan cfrademan moved this from To Do to Priority in NFV Automation Apr 18, 2018

@cfrademan cfrademan moved this from To Do to In Progress in Orchestrator Apr 18, 2018

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

cfrademan added a commit to cfrademan/netrino that referenced this issue Aug 6, 2018

cfrademan added a commit that referenced this issue Aug 6, 2018

@cfrademan cfrademan moved this from Priority to In Progress in NFV Automation Aug 6, 2018

cfrademan added a commit to cfrademan/netrino that referenced this issue Aug 6, 2018

cfrademan added a commit that referenced this issue Aug 6, 2018

cfrademan added a commit to cfrademan/netrino that referenced this issue Aug 8, 2018

cfrademan added a commit that referenced this issue Aug 8, 2018

@cfrademan cfrademan closed this Aug 8, 2018

NFV Automation automation moved this from In Progress to Completed Aug 8, 2018

Orchestrator automation moved this from In Progress to Completed Aug 8, 2018

cfrademan added a commit to cfrademan/netrino that referenced this issue Aug 8, 2018

cfrademan added a commit that referenced this issue Aug 8, 2018

cfrademan added a commit to cfrademan/luxon that referenced this issue Aug 13, 2018

Element Manager API TachyonicProject#20
TachyonicProject/netrino#20

Resolved issues with crypto. Keys / IV in binary only.

cfrademan added a commit to cfrademan/netrino that referenced this issue Aug 13, 2018

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