×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

 

This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.
Remedy IT Service Management Suite 8.1 ... Key concepts Comprehensive Change and Release Management

Change Management for Virtual and Cloud Environments use case

Each use case has a UML robustness diagram associated with it. A robustness diagram depicts the core components of a system and how the components communicate or collaborate with one another to satisfy a use case. Arrows between the components indicate the flow of information between the components.

The following symbols are used:

Symbol

Meaning

Actor — User role that interacts with a component in the system

Boundary — Component that represents an interface with which Actors interact

Entity — Domain objects within the system that typically present a persisted state of that object

Control — Components that connect Boundary and Entity components and implement some logic to manage the interaction between them

The goal of the Change Management for Virtual and Cloud Environments use case is to illustrate how BMC Change Management supports BMC Cloud Lifecycle Management version 1.x.

This use case has the following steps:

  1. The cloud end user submits requests to provision new virtual machines (VMs) through the Cloud End User Portal, a component of BMC Cloud Lifecycle Management.
  2. A list of VM Guest Packages that can be requested is returned via integration to BMC BladeLogic Server Automation through BMC Atrium Orchestrator.
  3. The Service Fulfillment Engine invokes BMC Atrium Orchestrator provisioning workflows.
  4. BMC Atrium Orchestrator workflows coordinate changes and change tasks, and invoke BMC BladeLogic Server Automation through the BladeLogic Command Line utility (BLCLI) to create new VMs.
  5. Different tasks can be invoked during provisioning, including creating additional software packages after the VM has been provisioned, and applying compliance monitoring and performance monitoring agents.
  6. BMC Atrium Orchestrator workflows also add the new VM to the CMDB.
  7. Throughout the process execution, the end user can view the status of the provisioning through the Cloud End User Portal.
  8. After all provisioning activities are completed, all change tasks are closed and the service request status is set to completed.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Last modified by Kathryn Sheridan on Aug 30, 2011
use_cases reference

Comments

Log in or register to comment.

Release Lifecycle Automation use case
Business value
© Copyright 1996 - 2018 BMC Software, Inc. © Copyright 1996 - 2018 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.