Get started with CI Lifecycle Management

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read

    • Follow these high level steps to get started and to track activities of the CI Lifecycle Management module of the CMDB application.

    Before you begin

    Role required: none

    Procedure

    1. Activate the base system CI Lifecycle Management - Restore Internal State Management Tables scheduled job that continuously checks and maintains data integrity of all internal CI Lifecycle Management tables.
    2. Define CI actions.
    3. Define compatible CI actions rules.
      Navigate to All > Configuration > CI Lifecycle Management > CMDB CI Actions to display currently active/inactive CI actions in the CMDB.
    4. Define not-allowed CI actions rules.
    5. Define not-allowed operational state transitions rules.
    6. Define new operational states by modifying the operational_status field in the [cmdb_ci] table in the system dictionary.
      Navigate to All > Configuration > CI Lifecycle Management > View Internal Operational States to display available operational states set by each requestor.
    7. Set priority for operational states.
    8. Call APIs to apply CI actions.
      Navigate to All > Configuration > CI Lifecycle Management > CMDB CI Actions to display which actions were submitted and thier active/inactive state in the CMDB.
    9. Navigate to All > Configuration > CI Lifecycle Management > View CI State Registered Users to display currently registered operators that were registered via the registerOperator API.
    10. Review Renew Lease tasks and extend leases as needed: Navigate to All > Configuration > CI Lifecycle Management > Renew Lease Tasks. These tasks are created automatically by the CI Lifecycle Management - Restore Internal State Management Tables scheduled job for CI action records in which the lease for a valid requester has expired. The Requestor should use the lifecycle management API ExtendCIActionLease to extend the lease. Otherwise, if the lease remains expired for a specified grace period, the CI Lifecycle Management - Restore Internal State Management Tables scheduled job marks the respective CI action record as ‘inactive'.
      The grace period for expired lease time is configurable by the system property glide.cmdb.statemgmt.max_lease_expired_days.
    11. Navigate to All > Configuration > CI Lifecycle Management > State Management Logs to display logs of CI Lifecycle Management operations.