Anuket Project

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »


Target Phase of Cloud-Lifecycle:

Pre-Deployment of VIM (Openstack or Kubernetes)

Cloud Deployment – Real-World Workflow.

  • Hardware Delivery.
  • Racking / Stacking
  • Power On.
  • Hardware configuration and (Validation – handled by CIRV-HDV).
  • [N/W Configuration]
  • Cloud Deployment (Multiple Installer projects - Airship, Triple-O, Fuel, Kuberef, etc.)


Project description

In the real-world cloud deployment, network device configuration always takes a lot time. So to reduce the time for cloud deployment, we need an automation tool to configure network devices.

In order to do that, we will need define common architecture configuration requirements reference for network devices, and a flexible automation tool which will take user network configuration requirements/preference and network planning as input. 

Scope

The scope of this project will including 2 parts: specification and implementation 

Specification-RI:

Define common network device topology, which will including router, SDN GW, EOR, and TOR all network devices in Access layer, aggregation layer, and outgoing layer, both SDN and Non-SDN

Define the common network device configuration requirements, like

VRF configuration reference to separate different network

M-LAG, LACP, STP, OSPF and other protocol  reference, Link aggregation configuration reference

Security reference

etc


Implementation:

We expecting this tool could be highly flexible and scalable, the tool should be able to configure network devices based on the users inputs, including configuration requirements/preference and network planning.

define the standard user preference model

define the standard network planning model

then the tool will generate the transcript of configuration items, and then configure network devices according to Network device description file.

Dependency

PDF(Pod Description File). The description file should includes information for all network device : name, IP, location, login info, role, port-mapping table


Implementation

Technology:

Ansible

  • Ansible Network is in very matured stated.
    • Especially true for Tier-1 switch vendors.
    • Multiple connections and Numerous Modules

Ansible -Roles:

Verb-First, Vendor-Next

Verbs: Gather Facts and Capabilities (mandatory), Update Firmware (optional), Update Config (Mandatory)

For Each Verb:  Multiple Switch Vendor specific ansible tasks.

Input:

Cloud IP-Planning as Input



People Interested to contribute:

Jie Niu (mainly work on specification)

Liang CHEN

Sridhar Rao (Implementation Only)



  • No labels