Child pages
  • TAPI Contributions and Presentations

Version 1.0 - 7 May 2020

Purpose of this document is to list the differences between YANG modules automatically generated from TAPI 2.1.3 and TAPI Next Major Release / Edge version.

 

213: TAPI version 2.1.3

E: Edge or Next Major Release, where to perform the modification

resourceSpec removed from Edge, unclear how GlobalClass is inherited. Broken!

Local class is explicitly “used” in Edge: Rule, CSEP, Route, Switch

E.g. SIP does not have the “uses global-class”, but in UML diagram there is inheritance. Note that Edge SIP has an “interface realization” while 213 SIP inherits ResourceSpec.

1        Tapi Common

  1. E: copy streaming augment (i.e. copy the 123 thing into Edge)
  2. 213: copy admin state pac comments
  3. 213: copy lifecycle state pac comments
  4. 213: copy global class comments
  5. 213: copy operational state pac comments
  6. E: copy key “uuid” to grouping tapi-context/list SIP but models seem equal!

    grouping tapi-context {

        list service-interface-point {

            key 'uuid';

            uses service-interface-point;

            description "none";

        }

  1. 213: delete resource and service spec
    1. Resource-spec in 213 is used by SIP, Link, Node, Topology, NEP, InterRuleGroup, NodeRuleGroup, CEP, SwitchControl,  Connection
    2. Service-spec im 213 is used by: NetworkTopologyService, ConnectivityService
  2. 213: grouping service-interface-point, copy comments
  3. 213: grouping termination-pac, copy comments
  4. E: copy to 213, no because is enum in 213 .

    identity OBJECT_TYPE {

        description "none";

    }

    identity OBJECT_TYPE_SERVICE_INTERFACE_POINT {

        base OBJECT_TYPE;

        description "none";

    }

  1. 213: lifecycle-state copy comments
  2. E:  grouping bandwidth-profile and bandwidth-profile-type were defined in 213, correctly removed from E.
  3. 213: add the following types:

   typedef mac-address {

        type string;

        description "pattern '[0-9a-fA-F]{2}(-[0-9a-fA-F]{2}){5}'

            description

            'The mac-address type represents a MAC address in the canonical

            format and hexadecimal format specified by IEEE Std 802. The

            hexidecimal representation uses uppercase characters.'";

    }

    typedef binary {

        type string;

        description "Represents any binary data, i.e., a sequence of octets.

            A binary type can be restricted by a length which defines the number of octets it contains.";

    }

    typedef timeticks {

        type string;

        description "type uint32

            The timeticks type represents a non-negative integer that represents the time, modulo 2^32 (4294967296 decimal), in hundredths of a second between two epochs.";

    }

    typedef object-type {

        type identityref {

            base OBJECT_TYPE;

        }

        description "The list of TAPI Common Object types/classes.";

    }

  1. 213, rpc get/updated sip, copy UUID comments

2        Tapi Topology

  1. E: copy streaming augment (i.e. copy the 123 thing into Edge)
  2. 213: copy admin state pac comments
  3. 213: copy lifecycle state pac
  4. E: missing key ‘uuid’: List NEP, NodeRuleGroup, Node, Link but models seem equal!
  5. 213: does not have topology/boundary-node-edge-point
  6. 213: copy comment of transitioned-layer-protocol-name
  7. E: copy inter-rule-group, node-rule-group, grouping-rule comments (class+attrs)
  8. E: copy PortRoleRule type from 213, while in E there is TopologyObjectType
  9. E: latency-characteristic, set the config false on attrs
  10. E: copy forwarding-rule and rule-type comments
  11. E: copy grouping connection-spec-reference
  12. E: NEP/availableCepLayerProtocol is richer than simple 213 supportedLayers
  13. E: copy signal-property-value-rule type
  14. E: all rpcs have comment on uuid

3        Tapi Connectivity

  1. E: connection/CEP list config false
  2. 213: copy connection/bounding-node
  3. E: connection/list switchControl add key uuid

        list switch-control {

            key 'uuid'; missing from edge, but UML seems equal

            config false;

            uses switch-control;

            description "none";

        }

  1. E: copy container connection-spec-reference?
  2. 213: CEP/list CepRole (a string plus connection-spec-reference) while E: protection-role
    1. CepRole and ConnectionSpecReference not defined in Edge.
  3. E: ConnectivityConstraint, service-layer in 213, not in Edge.
  4. 213: copy service-level comment
  5. E: ConnectivityConstraint, connectivity-direction in 213, not in Edge.
  6. E: ConnectivityService, all references (connectivity-constraint; routing-constraint; topology-constraint; uses resilience-constraint) are StrictComposite , 213 are ExtendedComposite , no change needed

        container connectivity-constraint {

            uses connectivity-constraint;

            description "none";

        }

  uses connectivity-constraint;

  1. E: Note that with local-id the key is mapped:

        list topology-constraint {

            key 'local-id';

            uses tapi-path-computation:topology-constraint;

            description "none";

        }

  1. 213: copy ConnectivityService/direction and layerProtocolName
  2. E: add Resilience Route Pac
  3. E: connectivity-context/list connectivity-service and list connection, missing key ‘uuid’
  4. E: config false on switch/selected-route, selected-cep
  5. 213: Selection control is in switch class, while in Edge is in ResilienceConstraint class
  6. 213: add fault-condition-determination to ResilienceConstraint class, plus related type
  7. Cep-list, without key ‘uuid’ in Edge.
  8. ConnectivityObjectType not defined in 213 no change possible
  9. E: all rpcs have comment on uuid – in Edge we may either remove all rpcs or enhance .
  10. create-connectivity-service, Edge adds input params: no need to change 213
    1. uuid
    2. name
    3. layer protocol name
    4. topology constraint becomes a list

 

 

  1. update-connectivity-service, Edge adds input params:
    1. uuid
    2. name
    3. topology constraint becomes a list
  2. 213: full hierarchy (see below), while in Edge just uuid. No need to change

    rpc get-connection-end-point-details {

        description "none";

        input {

            leaf topology-id-or-name {

                type string;

                description "none";

            }

            leaf node-id-or-name {

                type string;

                description "none";

            }

            leaf nep-id-or-name {

                type string;

                description "none";

            }

            leaf cep-id-or-name {

                type string;

            }

        }

4        Tapi Equipment

No differences

 

5        Tapi OAM

Moved some definitions to TapiEth