Schema library v2 #75

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
Open
BaptisteGi wants to merge 30 commits into main from bgi-schema-library-v2
.metadata.yml
            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -41,7 +41,7 @@ experimental/infiniband:
  
    experimental/optical_transport:

      dependencies:

        - base

        - extensions/modules

        - extensions/device_module

        - extensions/cable

      description: >

        Comprehensive optical transport network schemas for DWDM/WDM systems (ADVA FSP 3000 and similar

    @@ -61,7 +61,7 @@ experimental/location_extended:
  
    experimental/modules_linecards:

      dependencies:

        - base

        - extensions/modules

        - extensions/device_module

      description:

        This schema extension allows you to capture Linecard related information

        like the version. You can insert the Linecard into a Dcim Physical Device and

    @@ -71,7 +71,7 @@ experimental/modules_linecards:
  
    experimental/modules_routing_engine:

      dependencies:

        - base

        - extensions/modules

        - extensions/device_module

      description:

        This schema extension allows you to capture Routing Engine related

        information like the version. You can insert the Routing Engine into a Dcim Physical

    @@ -87,14 +87,6 @@ experimental/security:
  
        - base

      description: This schema extension contains models for implementing detailed security.

      name: Security

    experimental/tenancy:

      dependencies:

        - base

        - extensions/circuit

      description:

        This schema extension introduces tenancy for some of the schema nodes

        (circuits...)

      name: Tenancy

    experimental/topology:

      dependencies:

        - base

    @@ -109,6 +101,14 @@ experimental/vlan-translation:
  
        This schema extension is based on Juniper VLAN MAP, and not yet test

        out for other vendors.

      name: VLAN Translation

    extensions/aggregate:

      dependencies:

        - base

      description:

        This schema extension contains models to capture IP aggregates assigned by

        a Regional Internet Registry (RIR). It introduces an Aggregate node (top-level IPv4/IPv6

        prefix) and an RIR node (registry or private entity managing address space).

      name: Aggregate

    extensions/cable:

      dependencies:

        - base

    @@ -163,7 +163,7 @@ extensions/dwdm:
  
        channel number but via the wavelength and/or the frequency. This model provides

        a unique entry in Infrahub for those.

      name: DWDM

    extensions/firewall_policer:

    experimental/firewall_policer:

      dependencies:

        - base

      description:

    @@ -203,6 +203,14 @@ extensions/location_minimal:
  
        This schema extension is minimal but will provide you with basic items

        to store location related data.

      name: Location Minimal

    extensions/location_site:

      dependencies:

        - base

      description: >-

        This schema extension introduces a standalone Location.Site node (with facility,

        physical address, timezone, and status). It defines the same Site node as

        extensions/location_minimal, so load one or the other, not both.

      name: Location Site

    extensions/mlag:

      dependencies:

        - base

    @@ -219,14 +227,21 @@ extensions/mlag:
  
        - Add support for layer 3 overlay for MLAG interfaces (loopback, peer address ...)

        - Create virtual relationship so MLAG interfaces can be seen on the devices in the domain

      name: MLAG

    extensions/modules:

    extensions/device_module:

      dependencies:

        - base

      description: |

        This schema extension allows you to capture Device Modules related information like the serial number or the status. You can insert the Module into a Dcim Physical Device.

        This schema extension lets you capture module bays on a Dcim Physical Device and the modules installed into them (e.g. fan trays, line cards). A device can have any number of module bays, and each bay can optionally hold one module.

        NOTE: This extension doesn't contain any Nodes, you can use the extension module_linecards or modules_routing_engine to use it

      name: Modules

        NOTE: This extension ships a standard Module/ModuleType node pair ready to use, alongside the generic Module/ModuleType you can build your own flavors on top of (see the device_psu_module, modules_linecards, or modules_routing_engine extensions).

      name: Device Modules

    extensions/device_psu_module:

      dependencies:

        - base

        - extensions/device_module

      description: |

        This schema extension adds a PSU (Power Supply Unit) flavor on top of the generic Module/ModuleType from extensions/device_module, so you can track power supplies installed in a device's module bays alongside PSU-specific attributes like wattage and hot-swap capability.

      name: Device PSU Module

    extensions/patch_panel:

      dependencies:

        - base

    @@ -241,6 +256,8 @@ extensions/peering_ixp:
  
        - extensions/routing

        - extensions/routing_bgp

        - extensions/routing_bgp_community

        - extensions/routing_policies

        - extensions/routing_policies_bgp

      description:

        This schema extension contains all you need to model anything revolving

        around internet peering (Exchange points ...)!

    @@ -253,6 +270,15 @@ extensions/physical_disk:
  
        NOTE: This extension is compatible with all sort of device. You can apply the generic "DeviceWithPhysicalDisks" to particular model to enable disks tracking. You might also link that schema to location for instance to capture spares.

      name: Physical Disk

    extensions/rack:

      dependencies:

        - base

        - extensions/location_minimal

      description:

        This schema extension introduces a Rack model representing a physical equipment

        rack installed at a site. Racks can be placed at a LocationSite and can host devices

        and other equipment.

      name: Rack

    extensions/qinq:

      dependencies:

        - base

    @@ -383,13 +409,15 @@ extensions/snmp:
  
        Clients. As you can see this extension is not linked to Tenancy or Device, as

        you could decide to link the Community to different models based on your use case.

      name: SNMP

    extensions/topology:

    extensions/tenancy:

      dependencies:

        - base

      description:

        This schema extension introduces abstract network pods and services

        running in the pods, such as MPLS and EVPN.

      name: Topology

        This schema extension introduces a Tenant node that can own devices, IP

        prefixes/addresses, and hosting locations. See the comment at the bottom of

        `tenancy.yml` for an example of how to extend tenancy onto optional extension

        nodes such as `DcimCircuit`.

      name: Tenancy

    extensions/users:

      dependencies:

        - base
Navigation Menu

Uh oh!

Schema library v2 #75

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!

Uh oh!

Uh oh!

Schema library v2 #75

Are you sure you want to change the base?

Uh oh!

Schema library v2 #75

Uh oh!

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!

Uh oh!
