-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
SDNC Dublin Spr 3 3/11 - 3/29
Scope: Global configuration, Interface configuration routing configuration.
Backend impacts: YANG templates will be triggered based on the inputs via SO, scripts.
VNF à Netconf.
Uses YANG template
Use -> YANG conf.
South bound interface is Netcong
North bound interface is REST API
YANG supports – VNF
If he configuration is using CLIs, SSH, scripts, etc. Use YANG model, mapping of common data model to a specific model.
For the routers, use the following
- CLI commands
- automate the process and run scripts
- N/W element access point is CLI
- config. File (vendor agnostic)
Data structure – XML, JSON, etc
Interface – Netconf, REST API
All are on VNF functionality
SDN-C will use YANG, directed GRAPH. SDNC does not use TOSCA templates
The different modes of collecting configuration is via CLI interface, script interface, For YANG and Netconf we can use API interface. Configuration is standard across all product types for a particular vendor. The scripts are developed to configure the YANG model into respective ( router, etc) configuration. Once the configuration scripts are run, the underlying interface is built per VNF. The SDN-C is invoked from the North bound interface and is provided with the YANG model/ and or directed graph template. The common data model mapping shall be used to provide the configuration irrespective of which network element type is used. The standard protocol conversion formats will be used.
North Bound interface should have a pre defined set of commands. The different types of APIs used will be
Update configuration
Upgrade configuration
Backup configuration
For the meta data, find out which VNF needs to be upgraded.
For south bound interface, it should be YANG, Netconf compatable.
Acceptance Criteria: As an SDN user, I should be able to configure the basic config. On the third party VNF.