Versions Compared

Old Version 12

changes.mady.by.user AMMAR ALBETAR

Saved on

compared with

New Version 13

changes.mady.by.user AMMAR ALBETAR

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expand
titleArchitecture

SDNC Modeling Process (via Controller Design Studio UI).

  1. Heat Mapping: Start by the HEAT environment file as final product required for Openstack spin up. Then for each cloud parameter we define the following:
    1. Cloud parameters assignment type (Default, Input, Capability)
    2. Resources ruleset (Assignment logic : Recipe, ingredients, Models vs Custom logic)
    3. Assignment Capabilities: (microServices vs DG, DG-Driven vs Policy-Driven..etc)

  2. Data Dictionaries: Define the SDNC model used to resolve resource values from various systems.
    1. Define source type (default. Input, DB, A&AI, mS…etc)
    2. Define model used to retrieve the resource value from the various sub-systems (input-key-mapping, output-key-mapping, url, path)
    3. Define DD’s name, type, complex data type (if sub-system supports a list of complex data structure)

  3. Controller Blueprint: Create SDNC model and all associated capabilities, artifact templates, Data Dictionaries
    1. model Identifier: (model name, version, author…etc)
    2. Capabilities ( Resource-Assignment, Artifact-template)
    3. Template Instance (Upload Artifact Templates)
      1. Edit/View each Artifact Template
      2. Upload Artifact Template JSON file
      3. Load template and Auto-Map to Data Dictionaries
      4. Review Mapping Table and Edit DDs, Default values, DD Source

                                                         

Expand
titlenetbox mS Capability [ccsdk]
Expand
titlenetbox mS Capability [HELM Chart]


Expand
titlenetbox mS Capability [IPAM DB Creation SDN-C]
TableColumns 
ipam_ip_poolipam_serial_pool_idcreate_dateprefixprefix_idaddress_family(v4/v6)prefix_status:Pending, Activate, Deletedescription (vfw-protect, or vfw-unprotected)region (RegionOne, RegionTwo)  
ipam_ip_assignmentipam_serial_ip_assignment_idcreate_dateservice_instance_idvf_module_idip_adressip_address_type (vip, fixed, floating etc..) prefix_id (string)ip_address_id (string)ip_statusip_response



Expand
titlenetbox mS Capability [pre-provisioning scripts]





ActionVerbURIJSON payload (Bare minimal)ParamsTypeCommentsJSON responseNote
Create PrefixPOST/api/ipam/prefixes/{
  "prefix": "192.168.10.0/24",
  "is_pool": true,
  "description": "IP Pool for private network - vFW"
}		prefixStringPv4 or IPv6 network with mask{
    "id": 10,
     "prefix": "10.10.10.0/24",
    "site": null,
    "vrf": null,
    "tenant": null,
    "vlan": null,
    "status": 1,
    "role": null,
    "is_pool": true,
    "description": "IP Pool for private network - vFW",
    "created": "2018-06-08",
    "last_updated": "2018-06-08T14:46:07.417407Z"
}		There is a possibility to hook the prefix with the following notion: site, vft, tenant, vlan. For now, I kept things very simplistic.


Casablanca:
Robot to create the prefix.
Robot to delete the prefix.
is_poolBooleanAll IP addresses within this prefix are considered usable
descriptionString (100) 
   

...