diff --git a/spec/ControllerDomainManager+forwardings.yaml b/spec/ControllerDomainManager+forwardings.yaml index c8de1ac..31eea6e 100644 --- a/spec/ControllerDomainManager+forwardings.yaml +++ b/spec/ControllerDomainManager+forwardings.yaml @@ -117,13 +117,13 @@ forwardings: - server-name: /v1/list-mediator-instance-managers uuid: mm-1-0-0-op-s-is-003 - server-name: /v1/provide-netconf-interface - uuid: mm-1-0-0-op-s-is-004 + uuid: mm-1-0-0-op-s-is-004 - server-name: /v1/dismantle-netconf-instances uuid: mm-1-0-0-op-s-is-005 - server-name: /v1/create-mediator-vm-template uuid: mm-1-0-0-op-s-is-000 - server-name: /v1/delete-mediator-vm-template - uuid: mm-1-0-0-op-s-is-001 + uuid: mm-1-0-0-op-s-is-001 - server-name: /v1/list-mediator-vm-templates uuid: mm-1-0-0-op-s-is-002 consequent-requests: @@ -282,7 +282,7 @@ forwardings: operation-client-deletion: initiating-requests: - server-name: /v1/dispose-remainders-of-deregistered-application - uuid: mm-1-0-0-op-s-bm-013 + uuid: mm-1-0-0-op-s-bm-013 - server-name: /v1/disregard-mediator-instance-manager uuid: mm-1-0-0-op-s-im-002 consequent-requests: @@ -339,7 +339,7 @@ forwardings: operation-client-deletion: initiating-requests: - server-name: /v1/end-subscription - uuid: mm-1-0-0-op-s-bm-004 + uuid: mm-1-0-0-op-s-bm-004 - server-name: /v1/disregard-mediator-instance-manager uuid: mm-1-0-0-op-s-im-002 consequent-requests: @@ -490,12 +490,12 @@ forwardings: uuid: mm-1-0-0-op-s-im-002 operation-client-deletion: initiating-requests: - - server-name: ControllerDomainManager://v1/create-mediator-vm-template - uuid: mm-1-0-0-op-s-is-000 - - server-name: ControllerDomainManager://v1/provide-netconf-interface - uuid: mm-1-0-0-op-s-is-004 - - server-name: ControllerDomainManager://v1/dismantle-netconf-interface - uuid: mm-1-0-0-op-s-is-003 + - server-name: ControllerDomainManager://v1/create-mediator-vm-template + uuid: mm-1-0-0-op-s-is-000 + - server-name: ControllerDomainManager://v1/provide-netconf-interface + uuid: mm-1-0-0-op-s-is-004 + - server-name: ControllerDomainManager://v1/dismantle-netconf-interface + uuid: mm-1-0-0-op-s-is-003 consequent-requests: - client-name: ExecutionAndTraceLog://v1/record-service-request uuid: mm-1-0-0-op-c-bs-eatl-2-1-2-000 @@ -514,7 +514,7 @@ forwardings: consequent-requests: - client-name: ConnectionPreparation://v1/prepare-connections uuid: mm-1-0-0-op-c-is-cc-1-1-0-000 - + - forwarding-name: provideNetconfInterfaceManagesExistingMediatorInstances.ListMediatorInstances uuid: mm-1-0-0-op-fc-is-002 forwarding-type: ProcessSnippet diff --git a/spec/ControllerDomainManager+profileInstances.yaml b/spec/ControllerDomainManager+profileInstances.yaml index 44ba4f2..7a46661 100644 --- a/spec/ControllerDomainManager+profileInstances.yaml +++ b/spec/ControllerDomainManager+profileInstances.yaml @@ -105,4 +105,4 @@ profile-instances: description: 'Represents the first entry in the list of releases' datatype: string configuration: - value-reference: '/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-http-s-000/layer-protocol=0/http-server-interface-1-0:http-server-interface-pac/http-server-interface-capability/release-list=0/changes' \ No newline at end of file + value-reference: '/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-http-s-000/layer-protocol=0/http-server-interface-1-0:http-server-interface-pac/http-server-interface-capability/release-list=0/changes' diff --git a/spec/ControllerDomainManager+services.yaml b/spec/ControllerDomainManager+services.yaml index 099f724..bde3eda 100644 --- a/spec/ControllerDomainManager+services.yaml +++ b/spec/ControllerDomainManager+services.yaml @@ -62,150 +62,149 @@ servers: # Administration # - operation-name: /v1/list-functions - uuid: + uuid: - operation-name: /v1/update-function - uuid: + uuid: - operation-name: /v1/list-validation-sequences - uuid: + uuid: - operation-name: /v1/update-validation-sequence - uuid: + uuid: - operation-name: /v1/list-pulsers - uuid: + uuid: - operation-name: /v1/update-pulser - uuid: + uuid: - operation-name: /v1/list-error-codes - uuid: + uuid: - operation-name: /v1/update-error-code - uuid: - + uuid: - operation-name: /v1/provide-domain-controller-dump - uuid: + uuid: # # Interpretation # - operation-name: /v1/create-management-domain-interface-template - uuid: + uuid: - operation-name: /v1/delete-management-domain-interface-template - uuid: + uuid: - operation-name: /v1/list-configured-management-domain-interface-templates - uuid: + uuid: - operation-name: /v1/provide-config-of-management-domain-interface-template - uuid: + uuid: - operation-name: /v1/update-management-domain-interface-template - uuid: + uuid: - operation-name: /v1/create-load-balancer-template - uuid: + uuid: - operation-name: /v1/delete-load-balancer-template - uuid: + uuid: - operation-name: /v1/list-configured-load-balancer-templates - uuid: + uuid: - operation-name: /v1/provide-config-of-load-balancer-template - uuid: + uuid: - operation-name: /v1/update-load-balancer-template - uuid: + uuid: - operation-name: /v1/create-controller-template - uuid: + uuid: - operation-name: /v1/delete-controller-template - uuid: + uuid: - operation-name: /v1/list-configured-controller-templates - uuid: + uuid: - operation-name: /v1/provide-config-of-controller-template - uuid: + uuid: - operation-name: /v1/update-controller-template - uuid: + uuid: - operation-name: /v1/create-mount-point-template - uuid: + uuid: - operation-name: /v1/delete-mount-point-template - uuid: + uuid: - operation-name: /v1/list-configured-mount-point-templates - uuid: + uuid: - operation-name: /v1/provide-config-of-mount-point-template - uuid: + uuid: - operation-name: /v1/update-mount-point-template - uuid: + uuid: - operation-name: /v1/regard-management-domain-interface - uuid: + uuid: - operation-name: /v1/disregard-management-domain-interface - uuid: + uuid: - operation-name: /v1/list-configured-management-domain-interfaces - uuid: + uuid: - operation-name: /v1/provide-config-of-management-domain-interface - uuid: + uuid: - operation-name: /v1/regard-load-balancer - uuid: + uuid: - operation-name: /v1/disregard-load-balancer - uuid: + uuid: - operation-name: /v1/list-configured-load-balancers - uuid: + uuid: - operation-name: /v1/list-configured-forwardings - uuid: + uuid: - operation-name: /v1/provide-config-of-forwarding - uuid: + uuid: - operation-name: /v1/provide-status-of-forwarding - uuid: + uuid: - operation-name: /v1/regard-controller - uuid: + uuid: - operation-name: /v1/disregard-controller - uuid: + uuid: - operation-name: /v1/list-configured-controllers - uuid: + uuid: - operation-name: /v1/list-configured-mount-points - uuid: + uuid: - operation-name: /v1/provide-config-of-mount-point - uuid: + uuid: - operation-name: /v1/provide-status-of-mount-point - uuid: + uuid: - operation-name: /v1/establish-management-domain - uuid: + uuid: - operation-name: /v1/dismantle-management-domain - uuid: + uuid: - operation-name: /v1/establish-controller-in-management-domain - uuid: + uuid: - operation-name: /v1/dismantle-controller-from-management-domain - uuid: + uuid: - operation-name: /v1/list-configured-management-domains - uuid: + uuid: - operation-name: /v1/provide-config-of-management-domain # Auf sinnvolles gegenseitiges Ergänzen mit den Informationen über die Komponenten achten - uuid: + uuid: - operation-name: /v1/provide-status-of-management-domain # Auf sinnvolles gegenseitiges Ergänzen mit den Informationen über die Komponenten achten - uuid: + uuid: - operation-name: /v1/mediate-netconf-client-update - uuid: + uuid: - operation-name: /v1/establish-management-domain-connection - uuid: + uuid: - operation-name: /v1/dismantle-management-domain-connection - uuid: + uuid: - operation-name: /v1/list-configured-management-domain-connections - uuid: + uuid: - operation-name: /v1/provide-status-of-management-domain-connection - uuid: + uuid: - operation-name: /v1/establish-management-plane-transport - uuid: + uuid: - operation-name: /v1/dismantle-management-plane-transport - uuid: + uuid: - operation-name: /v1/list-configured-management-plane-transports - uuid: + uuid: - operation-name: /v1/provide-config-of-management-plane-transport - uuid: + uuid: - operation-name: /v1/provide-status-of-management-plane-transport - uuid: + uuid: - operation-name: /v1/list-alarms-at-management-plane-transport - uuid: + uuid: # # Validation @@ -215,58 +214,57 @@ servers: # Measurement # - operation-name: /p1/measurement-orchestrator - uuid: + uuid: - operation-name: /p1/measure-management-domain-interface - uuid: + uuid: - operation-name: /p1/measure-list-of-forwardings - uuid: + uuid: - operation-name: /p1/measure-list-of-mount-points - uuid: + uuid: - operation-name: /p1/measure-links - uuid: + uuid: - operation-name: /p1/measure-routes - uuid: + uuid: - operation-name: /p1/measure-management-plane-transport - uuid: + uuid: # # Monitoring # - operation-name: /p1/monitoring-orchestrator - uuid: + uuid: - operation-name: /p1/monitor-management-plane-transport - uuid: + uuid: - operation-name: /p1/monitor-management-domain-interface - uuid: + uuid: - operation-name: /p1/monitor-forwarding - uuid: + uuid: - operation-name: /p1/monitor-mount-point - uuid: + uuid: - operation-name: /p1/monitor-load-balancer - uuid: + uuid: - operation-name: /p1/monitor-controller - uuid: + uuid: # # Implementation # - operation-name: /p1/implementation-orchestrator - uuid: + uuid: - operation-name: /p1/reconstruct-management-domain-interface - uuid: + uuid: - operation-name: /p1/construct-forwarding - uuid: + uuid: - operation-name: /p1/destruct-forwarding - uuid: + uuid: - operation-name: /p1/reconstruct-forwarding - uuid: + uuid: - operation-name: /p1/construct-mount-point - uuid: + uuid: - operation-name: /p1/destruct-mount-point - uuid: + uuid: - operation-name: /p1/reconstruct-mount-point - uuid: - + uuid: http-server: @@ -440,4 +438,3 @@ clients: service: basic: individual: - diff --git a/spec/ControllerDomainManager.yaml b/spec/ControllerDomainManager.yaml index a370f6e..b878e09 100644 --- a/spec/ControllerDomainManager.yaml +++ b/spec/ControllerDomainManager.yaml @@ -469,8 +469,8 @@ paths: description: 'Supported device kinds of the Mediator vm that shall be added to the {$mediator-vm-template-name} in APPdata' type: array items: - type: string - engineering-limit: + type: string + engineering-limit: description: 'Number of instances supported by the Mediator vm that shall be added to the {$mediator-vm-template-name} in APPdata' type: integer # Forwarding shall be introduced to delete instances (random mountpoints shall be considered) @@ -491,7 +491,7 @@ paths: 'operation to list the existing mediator instances that shall be added to the {$mediator-vm-template-name} in APPdata' example: mediator-vm-template-name: 'EricssonMLTemplate' - supported-device-kind-list: ['MLTN','ML6600'] + supported-device-kind-list: ['MLTN', 'ML6600'] engineering-limit: 3600 provide-mediator-instance-operation-name: '/v1/provide-mediator-instance' dismantle-mediator-instance-operation-name: '/v1/dismantle-mediator-instance' @@ -579,7 +579,7 @@ paths: type: string minLength: 6 description: > - 'Name of a precreated mediator vm template find in the APPData. + 'Name of a precreated mediator vm template find in the APPData. Request shall be rejected with 400 BadRequest if the template is not available. {$mediator-instance-name}' shall be mapped to the {$mediator-vm-template-name} in the APPData. mediator-instance-manager-protocol: @@ -619,7 +619,7 @@ paths: example: mediator-instance-name: 'EricssonMediatorManager' mediator-instance-release-number: '1.0.1' - mediator-vm-template-name: + mediator-vm-template-name: mediator-instance-manager-protocol: 'HTTP' mediator-instance-manager-ip-address: ip-address: @@ -670,7 +670,7 @@ paths: $ref: '#/components/responses/responseForErroredServiceRequests' default: $ref: '#/components/responses/responseForErroredServiceRequests' - + /v1/create-mediator-vm-template: parameters: - $ref: '#/components/parameters/user' @@ -709,8 +709,8 @@ paths: description: 'Supported device kinds of the Mediator vm that shall be added to the {$mediator-vm-template-name} in APPdata' type: array items: - type: string - engineering-limit: + type: string + engineering-limit: description: 'Number of instances supported by the Mediator vm that shall be added to the {$mediator-vm-template-name} in APPdata' type: integer provide-mediator-instance-operation: @@ -730,7 +730,7 @@ paths: 'operation to list the existing mediator instances that shall be added to the {$mediator-vm-template-name} in APPdata' example: mediator-vm-template-name: 'EricssonMLTemplate' - supported-device-kind-list: ['MLTN','ML6600'] + supported-device-kind-list: ['MLTN', 'ML6600'] engineering-limit: 3600 provide-mediator-instance-operation-name: '/v1/provide-mediator-instance' dismantle-mediator-instance-operation-name: '/v1/dismantle-mediator-instance' @@ -882,7 +882,7 @@ paths: description: 'Mediator deleted' headers: x-correlator: - schema: + schema: type: string example: '550e8400-e29b-11d4-a716-446655440000' description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request' @@ -994,7 +994,7 @@ paths: required: - code - message - - conflicting-mediator-instance-manager-list + - conflicting-mediator-instance-manager-list properties: code: type: integer @@ -1082,13 +1082,13 @@ paths: description: 'Supported device kind of the Mediator vm that shall be retrieved from the APPdata' type: array items: - type: string + type: string paired-mediator-manager-vm-list: description: 'Associated mediator vm list that shall be retrieved from the APPdata' type: array items: - type: string - engineering-limit: + type: string + engineering-limit: description: 'Number of instances supported by the Mediator vm that shall be retrieved from the APPdata' type: integer provide-mediator-instance-operation-name: @@ -1109,50 +1109,50 @@ paths: example: - mediator-vm-template-name: 'EricssonMLTemplate' vendor-name: 'Ericsson' - supported-device-kind-list: ['MLTN','ML6600'] + supported-device-kind-list: ['MLTN', 'ML6600'] engineering-limit: 3600 provide-mediator-instance-operation-name: '/v1/provide-mediator-instance' dismantle-mediator-instance-operation-name: '/v1/dismantle-mediator-instance' list-mediator-instance-operation-name: '/v1/list-mediator-instances' - paired-mediator-manager-vm-list : ['EricssonVM'] + paired-mediator-manager-vm-list: ['EricssonVM'] - mediator-vm-template-name: 'SIAEAGSTemplate' vendor-name: 'SIAE' - supported-device-kind-list: ['AGS20','AGS20L'] + supported-device-kind-list: ['AGS20', 'AGS20L'] engineering-limit: 3600 provide-mediator-instance-operation-name: '/v1/provide-mediator-instance' dismantle-mediator-instance-operation-name: '/v1/dismantle-mediator-instance' list-mediator-instance-operation-name: '/v1/list-mediator-instances' - paired-mediator-manager-vm-list : ['SiaeVM'] + paired-mediator-manager-vm-list: ['SiaeVM'] headers: - x-correlator: - schema: - type: string - example: '550e8400-e29b-11d4-a716-446655440000' - description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request' - exec-time: - schema: - type: integer - example: 1100 - description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds' - backend-time: - schema: - type: integer - example: 850 - description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds' - life-cycle-state: - schema: - type: string - enum: - - 'EXPERIMENTAL' - - 'OPERATIONAL' - - 'DEPRECATED' - - 'OBSOLETE' - - 'UNKNOWN' - - 'NOT_YET_DEFINED' - example: 'EXPERIMENTAL' - description: > - 'Life cycle state of the consumed service - from [/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-op-s-is-002/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-configuration/life-cycle-state]' + x-correlator: + schema: + type: string + example: '550e8400-e29b-11d4-a716-446655440000' + description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request' + exec-time: + schema: + type: integer + example: 1100 + description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds' + backend-time: + schema: + type: integer + example: 850 + description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds' + life-cycle-state: + schema: + type: string + enum: + - 'EXPERIMENTAL' + - 'OPERATIONAL' + - 'DEPRECATED' + - 'OBSOLETE' + - 'UNKNOWN' + - 'NOT_YET_DEFINED' + example: 'EXPERIMENTAL' + description: > + 'Life cycle state of the consumed service + from [/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-op-s-is-002/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-configuration/life-cycle-state]' '400': $ref: '#/components/responses/responseForErroredServiceRequests' '401': @@ -1165,7 +1165,7 @@ paths: $ref: '#/components/responses/responseForErroredServiceRequests' default: $ref: '#/components/responses/responseForErroredServiceRequests' - + /v1/regard-mediator-instance-manager: parameters: - $ref: '#/components/parameters/user' @@ -1210,7 +1210,7 @@ paths: minLength: 6 # Thorsten: I would like the mediatorVm being handled like an application. pattern: '^([a-z]{2,6})$' # Thorsten: This pattern is required for automatically generating the UUID of the mediatorVm description: > - 'find the name of a pre-created mediator vm template in the APPData. + 'find the name of a pre-created mediator vm template in the APPData. {$mediator-instance-name}' shall be associated to the {$mediator-vm-template-name} in the APPData. create or update [/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-op-c-is-*-1-0-0-000/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]' for the {$mediator-vm-template-name#list-mediator-instance-operation-name} in APPData. create or update [/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-op-c-is-*-1-0-0-001/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]' for the {$mediator-vm-template-name#provide-mediator-instance-operation-name} in APPData. @@ -1252,7 +1252,7 @@ paths: example: mediator-instance-name: 'EricssonMediatorManager' mediator-instance-release-number: '1.0.1' - mediator-vm-template-name: + mediator-vm-template-name: mediator-instance-manager-protocol: 'HTTP' mediator-instance-manager-address: ip-address: @@ -1302,7 +1302,7 @@ paths: '500': $ref: '#/components/responses/responseForErroredServiceRequests' default: - $ref: '#/components/responses/responseForErroredServiceRequests' + $ref: '#/components/responses/responseForErroredServiceRequests' /v1/disregard-mediator-instance-manager: parameters: - $ref: '#/components/parameters/user' @@ -1764,7 +1764,7 @@ paths: find [/core-model-1-4:control-construct/forwarding-domain=xmim-0-0-1-op-fd-0000/forwarding-construct=xmim-0-0-1-meth-fc-*/name=ForwardingName/name]' responses: '204': - description: 'Mediator deleted' + description: 'Mediator deleted' headers: x-correlator: schema: @@ -2096,7 +2096,7 @@ paths: description: 'Mediator deleted' headers: x-correlator: - schema: + schema: type: string example: '550e8400-e29b-11d4-a716-446655440000' description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request' @@ -2267,7 +2267,7 @@ paths: - device-name - mediator-instance-ip-address properties: - device-name: + device-name: type: string pattern: ^(?:\d{3}(?:25|27)\d{4}|\d{3}55\d{4}[AB])$ description: 'Identifier of the device at the Controller' @@ -2396,7 +2396,7 @@ paths: '500': $ref: '#/components/responses/responseForErroredServiceRequests' default: - $ref: '#/components/responses/responseForErroredServiceRequests' + $ref: '#/components/responses/responseForErroredServiceRequests' PingTestOnDevice: #requestBody#mount-name#device-ip description: 'Ping test shall be performed on the device-ip of the identified mediator instance of the {$RequestBody#mount-name}' DeletesMediatorInstances: #[/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-tcp-c-*mim-1-0-0-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]://[/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-tcp-c-*mim-1-0-0-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address or /core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-tcp-c-*mim-1-0-0-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name]:[/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-tcp-c-*mim-1-0-0-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port][/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-op-c-is-*mim-1-0-0-002/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name] @@ -2429,7 +2429,7 @@ paths: description: 'Mediator deleted' headers: x-correlator: - schema: + schema: type: string example: '550e8400-e29b-11d4-a716-446655440000' description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request' @@ -2468,7 +2468,7 @@ paths: $ref: '#/components/responses/responseForErroredServiceRequests' default: $ref: '#/components/responses/responseForErroredServiceRequests' - + ######################################################################################################################## # Service Layer - Basic Part ######################################################################################################################## @@ -3342,7 +3342,7 @@ paths: schema: type: string example: '222250001' - description: > + description: > 'The mountName of the device that is addressed by the request from cyclic processing of NEP deviceList' - name: fields @@ -3350,7 +3350,7 @@ paths: required: false schema: type: string - description: > + description: > 'Query parameter to filter ressources according to RFC8040 fields filter spec from string profile instance mm-1-0-0-string-p-000' responses: @@ -3435,10 +3435,10 @@ paths: type: string manufacturer-identifier: type: string - # + # logical-termination-point: type: array - description: > + description: > 'LTPs with no relevant data can be filtered out, before data is written to NEP cache. I.e. only keep LTPs for the following interfaces: air-interface, ethernet-container, wire-interface' items: @@ -3582,7 +3582,7 @@ paths: properties: ses: type: integer - es: + es: type: integer unavailability: type: integer @@ -3669,136 +3669,136 @@ paths: example: # example shows data like received from MWDI before filtering and processing on NEP side is applied core-model-1-4:control-construct: - - equipment-augment-1-0:control-construct-pac: - device-model-name: 'SomeDeviceType' - external-label: '100250001' - equipment-augment-1-0:protocol-collection: - protocol: - - uuid: 'PC-LLDP-5' - lldp-1-0:lldp-pac: - local-system-data: - system-name: 'System xyz' - logical-termination-point: - - uuid: 'SYNC-1234567891' - operational-state: 'core-model-1-4:OPERATIONAL_STATE_ENABLED' - layer-protocol: - - local-id: '1234567891' - administrative-state: 'core-model-1-4:ADMINISTRATIVE_STATE_UNLOCKED' - ltp-augment-1-0:ltp-augment-pac: - original-ltp-name: 'E1 1/7/4D' - - uuid: 'ETH-3456789123' - operational-state: 'core-model-1-4:OPERATIONAL_STATE_ENABLED' - layer-protocol: - - local-id: '3456789123' - ethernet-container-2-0:ethernet-container-pac: - ethernet-container-status: - interface-status: 'ethernet-container-2-0:INTERFACE_STATUS_TYPE_UP' - ethernet-container-historical-performances: - historical-performance-data-list: - - granularity-period: 'ethernet-container-2-0:GRANULARITY_PERIOD_TYPE_PERIOD-15-MIN' - period-end-time: '2025-01-07T22:00:00+01:00' - performance-data: - total-frames-input: -1 - total-bytes-input: 75120 - total-bytes-output: 15000 - total-frames-output: -1 - errored-frames-input: 0 - dropped-frames-input: 900 - dropped-frames-output: 0 - errored-frames-output: 0 - history-data-id: 'History Data ID not defined.' - ethernet-container-configuration: - interface-name: '10PN1234_M2-2' - bundling-is-on: false - administrative-state: 'core-model-1-4:ADMINISTRATIVE_STATE_UNLOCKED' - ltp-augment-1-0:ltp-augment-pac: - original-ltp-name: 'LAN 1/5/3' - - uuid: 'RF-2223335555' - operational-state: 'core-model-1-4:OPERATIONAL_STATE_ENABLED' - layer-protocol: - - local-id: '2223335555' - air-interface-2-0:air-interface-pac: - air-interface-configuration: - transmission-mode-min: '56000-16-v0' - transmitter-is-on: true - transmission-mode-max: '56000-256-v0' - xpic-is-on: false - power-is-on: true - air-interface-status: - interface-status: 'air-interface-2-0:INTERFACE_STATUS_TYPE_UP' - air-interface-historical-performances: - historical-performance-data-list: - - granularity-period: 'air-interface-2-0:GRANULARITY_PERIOD_TYPE_PERIOD-15-MIN' - period-end-time: '2025-01-07T08:30:00+01:00' - history-data-id: 'History Data ID not defined.' - performance-data: - es: 5 - xpd-max: -99 - tx-level-max: 12 - ses: 10 - rx-level-max: -50 - snir-min: 40 - snir-avg: -99 - rx-level-avg: 99 - unavailability: 20 - time-xstates-list: - - time: 901 - transmission-mode: '56000-32-v0' - - time: 0 - transmission-mode: '56000-64-v0' - - time: 0 - transmission-mode: '56000-4-v0' - - time: 0 - transmission-mode: '56000-16-v0' - rx-level-min: -50 - xpd-min: -99 - xpd-avg: -99 - tx-level-min: 8 - tx-level-avg: 99 - snir-max: 41 - air-interface-capability: - transmission-mode-list: - - transmission-mode-name: '56000-32-v0' - symbol-rate-reduction-factor: 1 - channel-bandwidth: 56000 - xpic-is-avail: true - modulation-scheme-name-at-lct: '32 QAM' - modulation-scheme: 32 - code-rate: 97 - type-of-equipment: 'RAU2 XYZ' - administrative-state: 'core-model-1-4:ADMINISTRATIVE_STATE_UNLOCKED' - - uuid: 'ETY-8888999912' - operational-state: 'core-model-1-4:OPERATIONAL_STATE_ENABLED' - layer-protocol: - - local-id: '8888999912' - wire-interface-2-0:wire-interface-pac: - wire-interface-status: - interface-status: 'wire-interface-2-0:INTERFACE_STATUS_TYPE_UP' - pmd-kind-cur: '1000BASE_FD' - wire-interface-configuration: - interface-name: '123790001A_ge2/0' - fixed-pmd-kind: '1000BASE_FD' - wire-interface-capability: - supported-pmd-kind-list: - - pmd-name: '1000BASE_FD' - duplex: 'wire-interface-2-0:DUPLEX_TYPE_FULL_DUPLEX' - speed: '1000Mbit/s' - administrative-state: 'core-model-1-4:ADMINISTRATIVE_STATE_UNLOCKED' - ltp-augment-1-0:ltp-augment-pac: - original-ltp-name: 'LAN 1/9/5' - equipment: - - uuid: '1919191919' - - uuid: '1929394959' - actual-equipment: - manufactured-thing: - equipment-type: - version: 'R1C' - description: 'Removable Memory Module' - model-identifier: 'RMM' - part-type-identifier: 'RYS 110 243/1' - type-name: 'RMM' - manufacturer-properties: - manufacturer-name: 'SomeVendor' + - equipment-augment-1-0:control-construct-pac: + device-model-name: 'SomeDeviceType' + external-label: '100250001' + equipment-augment-1-0:protocol-collection: + protocol: + - uuid: 'PC-LLDP-5' + lldp-1-0:lldp-pac: + local-system-data: + system-name: 'System xyz' + logical-termination-point: + - uuid: 'SYNC-1234567891' + operational-state: 'core-model-1-4:OPERATIONAL_STATE_ENABLED' + layer-protocol: + - local-id: '1234567891' + administrative-state: 'core-model-1-4:ADMINISTRATIVE_STATE_UNLOCKED' + ltp-augment-1-0:ltp-augment-pac: + original-ltp-name: 'E1 1/7/4D' + - uuid: 'ETH-3456789123' + operational-state: 'core-model-1-4:OPERATIONAL_STATE_ENABLED' + layer-protocol: + - local-id: '3456789123' + ethernet-container-2-0:ethernet-container-pac: + ethernet-container-status: + interface-status: 'ethernet-container-2-0:INTERFACE_STATUS_TYPE_UP' + ethernet-container-historical-performances: + historical-performance-data-list: + - granularity-period: 'ethernet-container-2-0:GRANULARITY_PERIOD_TYPE_PERIOD-15-MIN' + period-end-time: '2025-01-07T22:00:00+01:00' + performance-data: + total-frames-input: -1 + total-bytes-input: 75120 + total-bytes-output: 15000 + total-frames-output: -1 + errored-frames-input: 0 + dropped-frames-input: 900 + dropped-frames-output: 0 + errored-frames-output: 0 + history-data-id: 'History Data ID not defined.' + ethernet-container-configuration: + interface-name: '10PN1234_M2-2' + bundling-is-on: false + administrative-state: 'core-model-1-4:ADMINISTRATIVE_STATE_UNLOCKED' + ltp-augment-1-0:ltp-augment-pac: + original-ltp-name: 'LAN 1/5/3' + - uuid: 'RF-2223335555' + operational-state: 'core-model-1-4:OPERATIONAL_STATE_ENABLED' + layer-protocol: + - local-id: '2223335555' + air-interface-2-0:air-interface-pac: + air-interface-configuration: + transmission-mode-min: '56000-16-v0' + transmitter-is-on: true + transmission-mode-max: '56000-256-v0' + xpic-is-on: false + power-is-on: true + air-interface-status: + interface-status: 'air-interface-2-0:INTERFACE_STATUS_TYPE_UP' + air-interface-historical-performances: + historical-performance-data-list: + - granularity-period: 'air-interface-2-0:GRANULARITY_PERIOD_TYPE_PERIOD-15-MIN' + period-end-time: '2025-01-07T08:30:00+01:00' + history-data-id: 'History Data ID not defined.' + performance-data: + es: 5 + xpd-max: -99 + tx-level-max: 12 + ses: 10 + rx-level-max: -50 + snir-min: 40 + snir-avg: -99 + rx-level-avg: 99 + unavailability: 20 + time-xstates-list: + - time: 901 + transmission-mode: '56000-32-v0' + - time: 0 + transmission-mode: '56000-64-v0' + - time: 0 + transmission-mode: '56000-4-v0' + - time: 0 + transmission-mode: '56000-16-v0' + rx-level-min: -50 + xpd-min: -99 + xpd-avg: -99 + tx-level-min: 8 + tx-level-avg: 99 + snir-max: 41 + air-interface-capability: + transmission-mode-list: + - transmission-mode-name: '56000-32-v0' + symbol-rate-reduction-factor: 1 + channel-bandwidth: 56000 + xpic-is-avail: true + modulation-scheme-name-at-lct: '32 QAM' + modulation-scheme: 32 + code-rate: 97 + type-of-equipment: 'RAU2 XYZ' + administrative-state: 'core-model-1-4:ADMINISTRATIVE_STATE_UNLOCKED' + - uuid: 'ETY-8888999912' + operational-state: 'core-model-1-4:OPERATIONAL_STATE_ENABLED' + layer-protocol: + - local-id: '8888999912' + wire-interface-2-0:wire-interface-pac: + wire-interface-status: + interface-status: 'wire-interface-2-0:INTERFACE_STATUS_TYPE_UP' + pmd-kind-cur: '1000BASE_FD' + wire-interface-configuration: + interface-name: '123790001A_ge2/0' + fixed-pmd-kind: '1000BASE_FD' + wire-interface-capability: + supported-pmd-kind-list: + - pmd-name: '1000BASE_FD' + duplex: 'wire-interface-2-0:DUPLEX_TYPE_FULL_DUPLEX' + speed: '1000Mbit/s' + administrative-state: 'core-model-1-4:ADMINISTRATIVE_STATE_UNLOCKED' + ltp-augment-1-0:ltp-augment-pac: + original-ltp-name: 'LAN 1/9/5' + equipment: + - uuid: '1919191919' + - uuid: '1929394959' + actual-equipment: + manufactured-thing: + equipment-type: + version: 'R1C' + description: 'Removable Memory Module' + model-identifier: 'RMM' + part-type-identifier: 'RYS 110 243/1' + type-name: 'RMM' + manufacturer-properties: + manufacturer-name: 'SomeVendor' headers: x-correlator: schema: diff --git a/spec/Elements/ADM/adm.yaml b/spec/Elements/ADM/adm.yaml index b5f9092..055ca6f 100644 --- a/spec/Elements/ADM/adm.yaml +++ b/spec/Elements/ADM/adm.yaml @@ -59,42 +59,42 @@ paths: remote-ip-address: type: string description: 'Remote IP address at the TcpClient of the LTP identified by the managementDomain from OperationalDS' - remote-port: + remote-port: type: integer description: 'Remote TCP port at the TcpClient of the LTP identified by the managementDomain from OperationalDS' example: remote-ip-address: '127.0.0.1' remote-port: 4711 headers: - x-correlator: - schema: - type: string - example: '550e8400-e29b-11d4-a716-446655440000' - description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request' - exec-time: - schema: - type: integer - example: 1100 - description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds' - backend-time: - schema: - type: integer - example: 850 - description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds' - life-cycle-state: - schema: - type: string - enum: - - 'EXPERIMENTAL' - - 'OPERATIONAL' - - 'DEPRECATED' - - 'OBSOLETE' - - 'UNKNOWN' - - 'NOT_YET_DEFINED' - example: 'EXPERIMENTAL' - description: > - 'Life cycle state of the consumed service - from [/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-op-s-is-002/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-configuration/life-cycle-state]' + x-correlator: + schema: + type: string + example: '550e8400-e29b-11d4-a716-446655440000' + description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request' + exec-time: + schema: + type: integer + example: 1100 + description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds' + backend-time: + schema: + type: integer + example: 850 + description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds' + life-cycle-state: + schema: + type: string + enum: + - 'EXPERIMENTAL' + - 'OPERATIONAL' + - 'DEPRECATED' + - 'OBSOLETE' + - 'UNKNOWN' + - 'NOT_YET_DEFINED' + example: 'EXPERIMENTAL' + description: > + 'Life cycle state of the consumed service + from [/core-model-1-4:control-construct/logical-termination-point=mm-1-0-0-op-s-is-002/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-configuration/life-cycle-state]' '400': $ref: '#/components/responses/responseForErroredServiceRequests' '401': @@ -153,7 +153,7 @@ paths: description: > 'New value of the remote IP address at the TcpClient of the LTP identified by the managementDomain from [CDM://p1/reconstruct-management-domain-interface$request.body#remote-ip-address]' - remote-port: + remote-port: type: integer description: > 'New value of the remote TCP port at the TcpClient of the LTP identified by the managementDomain diff --git a/spec/Elements/OpenDaylight/OpenDaylight.yaml b/spec/Elements/OpenDaylight/OpenDaylight.yaml index 7fcf6a9..95dd416 100644 --- a/spec/Elements/OpenDaylight/OpenDaylight.yaml +++ b/spec/Elements/OpenDaylight/OpenDaylight.yaml @@ -38,7 +38,7 @@ paths: type: string description: > 'deviceName defined by Telefonica planing department - Invariant value defined during creation of the MountPoint' + Invariant value defined during creation of the MountPoint' netconf-node-topology:available-capabilities: type: object description: > @@ -151,7 +151,7 @@ paths: type: string description: > 'Status - Changes from connected to connecting whenever some keep alive packet has not been answered by the MediatorProcess/device + Changes from connected to connecting whenever some keep alive packet has not been answered by the MediatorProcess/device Changes from connecting to unable-to-connect whenever the number unanswered keep alive packets is exceeding the max-connection-attempts' netconf-node-topology:session-id: type: integer @@ -377,7 +377,7 @@ paths: type: string description: > 'deviceName defined by Telefonica planing department - Invariant value defined during creation of the MountPoint' + Invariant value defined during creation of the MountPoint' netconf-node-topology:host: type: string description: > diff --git a/spec/Elements/nginx/nginx.yaml b/spec/Elements/nginx/nginx.yaml index 11d9b0d..de79997 100644 --- a/spec/Elements/nginx/nginx.yaml +++ b/spec/Elements/nginx/nginx.yaml @@ -10,8 +10,6 @@ paths: ######################################################################################################################## - - ######################################################################################################################## # Common Components ######################################################################################################################## diff --git a/spec/Functions/Implementation/ImplementationFunctions.md b/spec/Functions/Implementation/ImplementationFunctions.md index 8513c49..1d3d8f1 100644 --- a/spec/Functions/Implementation/ImplementationFunctions.md +++ b/spec/Functions/Implementation/ImplementationFunctions.md @@ -22,6 +22,13 @@ Managed Elements and associated ImplementationFunctions: - Update MountPoint - /p1/reconstruct-mount-point +**date-of-next-attempt-to-fix:** +After attempting to transfer the target state from the RunningDS onto the Elements, the ImplementationFunctions have to document the outcome into the CurrentAlarms. +This includes determining when the next attempt should be made. +The two parameters for the minimum and maximum wait times (tmin and tmax) can be configured individually for each ImplementationFunction. +The formula for calculating the time for the next attempt is identical for all ImplementationFunctions: + +FormulaWaitTime ## ManagementDomainInterface diff --git a/spec/Functions/diagrams/CategoriesOfFunctions.pptx b/spec/Functions/diagrams/CategoriesOfFunctions.pptx index fbd37da..1010b3a 100644 Binary files a/spec/Functions/diagrams/CategoriesOfFunctions.pptx and b/spec/Functions/diagrams/CategoriesOfFunctions.pptx differ diff --git a/spec/Functions/diagrams/FormulaWaitTime.png b/spec/Functions/diagrams/FormulaWaitTime.png new file mode 100644 index 0000000..940fc1b Binary files /dev/null and b/spec/Functions/diagrams/FormulaWaitTime.png differ diff --git a/spec/InformationStructure/initialData/_02_FunctionData.yaml b/spec/InformationStructure/initialData/_02_FunctionData.yaml index e302434..783e324 100644 --- a/spec/InformationStructure/initialData/_02_FunctionData.yaml +++ b/spec/InformationStructure/initialData/_02_FunctionData.yaml @@ -37,49 +37,69 @@ function: - function-name: 'p1ReconstructManagementDomainInterface' function-description: parameter: - - parameter-name: 'waitTimeBetweenAttempts' - parameter-value: '30000' - parameter-definition: 'The wait time (in ms) before again attempting to fix the error.' + - parameter-name: 'tmin' + parameter-value: '2' + parameter-definition: 'Minimum wait time (in s) before again attempting to fix the error.' + - parameter-name: 'tmax' + parameter-value: '43000' + parameter-definition: 'Maximum wait time (in s) before again attempting to fix the error.' - function-name: 'p1ConstructForwarding' function-description: parameter: - - parameter-name: 'waitTimeBetweenAttempts' - parameter-value: '30000' - parameter-definition: 'The wait time (in ms) before again attempting to fix the error.' + - parameter-name: 'tmin' + parameter-value: '2' + parameter-definition: 'Minimum wait time (in s) before again attempting to fix the error.' + - parameter-name: 'tmax' + parameter-value: '43000' + parameter-definition: 'Maximum wait time (in s) before again attempting to fix the error.' - function-name: 'p1DestructForwarding' function-description: parameter: - - parameter-name: 'waitTimeBetweenAttempts' - parameter-value: '30000' - parameter-definition: 'The wait time (in ms) before again attempting to fix the error.' + - parameter-name: 'tmin' + parameter-value: '2' + parameter-definition: 'Minimum wait time (in s) before again attempting to fix the error.' + - parameter-name: 'tmax' + parameter-value: '43000' + parameter-definition: 'Maximum wait time (in s) before again attempting to fix the error.' - function-name: 'p1ReconstructForwarding' function-description: parameter: - - parameter-name: 'waitTimeBetweenAttempts' - parameter-value: '30000' - parameter-definition: 'The wait time (in ms) before again attempting to fix the error.' + - parameter-name: 'tmin' + parameter-value: '2' + parameter-definition: 'Minimum wait time (in s) before again attempting to fix the error.' + - parameter-name: 'tmax' + parameter-value: '43000' + parameter-definition: 'Maximum wait time (in s) before again attempting to fix the error.' - function-name: 'p1ConstructMountPoint' function-description: parameter: - - parameter-name: 'waitTimeBetweenAttempts' - parameter-value: '30000' - parameter-definition: 'The wait time (in ms) before again attempting to fix the error.' + - parameter-name: 'tmin' + parameter-value: '2' + parameter-definition: 'Minimum wait time (in s) before again attempting to fix the error.' + - parameter-name: 'tmax' + parameter-value: '43000' + parameter-definition: 'Maximum wait time (in s) before again attempting to fix the error.' - function-name: 'p1DestructMountPoint' function-description: parameter: - - parameter-name: 'waitTimeBetweenAttempts' - parameter-value: '30000' - parameter-definition: 'The wait time (in ms) before again attempting to fix the error.' + - parameter-name: 'tmin' + parameter-value: '2' + parameter-definition: 'Minimum wait time (in s) before again attempting to fix the error.' + - parameter-name: 'tmax' + parameter-value: '43000' + parameter-definition: 'Maximum wait time (in s) before again attempting to fix the error.' - function-name: 'p1ReconstructMountPoint' function-description: parameter: - - parameter-name: 'waitTimeBetweenAttempts' - parameter-value: '30000' - parameter-definition: 'The wait time (in ms) before again attempting to fix the error.' - + - parameter-name: 'tmin' + parameter-value: '2' + parameter-definition: 'Minimum wait time (in s) before again attempting to fix the error.' + - parameter-name: 'tmax' + parameter-value: '43000' + parameter-definition: 'Maximum wait time (in s) before again attempting to fix the error.' diff --git a/spec/InformationStructure/initialData/_03_ValidationSequenceData.yaml b/spec/InformationStructure/initialData/_03_ValidationSequenceData.yaml index 4eeaacb..032ac77 100644 --- a/spec/InformationStructure/initialData/_03_ValidationSequenceData.yaml +++ b/spec/InformationStructure/initialData/_03_ValidationSequenceData.yaml @@ -1,7 +1,7 @@ validation-sequence: -# See the following entries as examples -# Exact validations sequences are to be defined by ApplicationOwner -# (Please, delete this comment after reading) + # See the following entries as examples + # Exact validations sequences are to be defined by ApplicationOwner + # (Please, delete this comment after reading) - _trigger-function: 'v1-create-controller-template' sequence: diff --git a/spec/InformationStructure/schemas/05_ErrorCode.yaml b/spec/InformationStructure/schemas/05_ErrorCode.yaml index 08d9a1a..d9706fd 100644 --- a/spec/InformationStructure/schemas/05_ErrorCode.yaml +++ b/spec/InformationStructure/schemas/05_ErrorCode.yaml @@ -12,7 +12,7 @@ error-code: type: integer description: > 'Code for identifying the finding (value must be unique and invariant) - Values between 600 and 999 can be freely used and without harmonization + Values between 600 and 999 can be freely used and without harmonization for expressing findings by the MeasurementFunctions, respectively for triggering ImplementationFunctions' description: type: string diff --git a/spec/InformationStructure/schemas/06_CurrentAlarm.yaml b/spec/InformationStructure/schemas/06_CurrentAlarm.yaml index dc1f01d..751981f 100644 --- a/spec/InformationStructure/schemas/06_CurrentAlarm.yaml +++ b/spec/InformationStructure/schemas/06_CurrentAlarm.yaml @@ -1,7 +1,7 @@ affected-management-plane-transport: type: array x-key: _affected-management-plane-transport - description: > + description: > 'List of ForwardingConstructs that have problems All references (_affected-management-plane-transport, _affected-cc, _affected-ltp) relate to objects in RunningDS' items: diff --git a/spec/InformationStructure/schemas/22_Forwarding.yaml b/spec/InformationStructure/schemas/22_Forwarding.yaml index 82b21db..5a1f0e1 100644 --- a/spec/InformationStructure/schemas/22_Forwarding.yaml +++ b/spec/InformationStructure/schemas/22_Forwarding.yaml @@ -36,7 +36,7 @@ logical-termination-point: description: > 'IP address of the LogicalController (if applicable: IP address of the Forwarding inside the LoadBalancer) candidate: from [CDM://v1/establish-management-domain$request.body# ... ] - [Thorsten] Based on input of CDM://v1/establish-management-domain, either the IP address of a single ODL or the IP address of a to be created Forwarding inside a LoadBalancer is to be used here + [Thorsten] Based on input of CDM://v1/establish-management-domain, either the IP address of a single ODL or the IP address of a to be created Forwarding inside a LoadBalancer is to be used here running: from candidate operational: set by [/network-control-domain=running/profile=[_template]/list-forwardings-service]' local-port: @@ -44,7 +44,7 @@ logical-termination-point: description: > 'TCP port of the LogicalController (if applicable: TCP port of the Forwarding inside the LoadBalancer) candidate: from [CDM://v1/establish-management-domain$request.body#local-port-at-logical-controller] - [Thorsten] Based on input of CDM://v1/establish-management-domain, either the TCP Port of a single ODL or the TCP Port of a to be created Forwarding inside a LoadBalancer is to be used here + [Thorsten] Based on input of CDM://v1/establish-management-domain, either the TCP Port of a single ODL or the TCP Port of a to be created Forwarding inside a LoadBalancer is to be used here running: from candidate operational: set by [/network-control-domain=running/profile=[_template]/list-forwardings-service]' - description: 'tcpClient' diff --git a/spec/InformationStructure/schemas/35_MountPointTemplate.yaml b/spec/InformationStructure/schemas/35_MountPointTemplate.yaml index 3892378..652a50b 100644 --- a/spec/InformationStructure/schemas/35_MountPointTemplate.yaml +++ b/spec/InformationStructure/schemas/35_MountPointTemplate.yaml @@ -87,4 +87,3 @@ profile: 'Configuration Time to wait for the ODL to send another keep alive packet to the MediatorProcess/device CDM is reading this value from a MountPointTemplate and configuring it into every new instance of MountPoint' -