Open APIs

  • 1.  Resource status and state fields in TMF639 & TMF702

    TM Forum Member
    Posted 25 days ago
    TMF639 (& TMF702) defines 4 status/state fields for a resource, including possible values:
    • usageState
    • administrativeState
    • operationalState
    • resourceStatus
    Can someone shed some light on the precise meanings of those fields, as well as the enumerations proposed by the standard?

    Apologies if this has been addressed elsewhere, but all the threads that I found relate to the resource lifecycle model used by previous releases.



    ------------------------------
    Roland Leners
    SATEC GROUP
    ------------------------------


  • 2.  RE: Resource status and state fields in TMF639 & TMF702

    TM Forum Member
    Posted 24 days ago
    usageState comes from the SID Resource ABE
    administrativeState is in ManagedHardware, SID Hardware ABE
    The SID also has various state enums.
    @Kamal Maghsoudlou? @Vance Shipley​​?

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 3.  RE: Resource status and state fields in TMF639 & TMF702

    TM Forum Member
    Posted 24 days ago
    Thanks Jonathan. I will spend some time investigating SID.

    ------------------------------
    Roland Leners
    SATEC GROUP
    ------------------------------



  • 4.  RE: Resource status and state fields in TMF639 & TMF702

    TM Forum Member
    Posted 24 days ago
    Roland,

    The usageState attribute indicates (read only) the current usage of the Resource: idle | active | busy

    The resourceStatus attribute indicates (read only) the status of the Resource: standby | alarm | available | reserved | unknown | suspended

    The operationalState attributes controls (write) whether the Resource may be used in operations: enabled | disabled

    The administrativeState attributes controls (write), for administrative reasons, whether an otherwise operational Resource is available: lockedunlockedshutdown

    ------------------------------
    Vance Shipley
    SigScale
    ------------------------------



  • 5.  RE: Resource status and state fields in TMF639 & TMF702

    TM Forum Member
    Posted 24 days ago
    Vance,

    Thanks for the clarification. The "read only" or "write" rights are viewed from which perspective? Especially the resourceStatus values seem a mix of values related to a network state (e.g. alarm) or a provisioning process (e.g. reserved) i.e. I infer that different applications could set those values.

    The use case that I contemplate is a fulfillment one whereby a resource is created or updated in various ODA components.

    ------------------------------
    Roland Leners
    SATEC GROUP
    ------------------------------



  • 6.  RE: Resource status and state fields in TMF639 & TMF702

    TM Forum Member
    Posted 24 days ago
    Roland,

    In a 639 Resource Inventory context usageState and resourceStatus may not be appropriate unless you have a facility to keep the inventory in sync with the Resource state. Which ever process is responsible for updating the Resource in the inventory would obviously then need to write those attributes.

    In a Resource (Function) Activation (702/664) context, where you are instantiating a Resource, it doesn't make sense to try and tell the orchestrator what the usageState is, nor would you try and tell it that a Resource should be created with resourceStatus=alarm. It does make sense to instantiate a Resource into a state where it will be staged before being available for production, for example operationalState=disabled.


    ------------------------------
    Vance Shipley
    SigScale
    ------------------------------