BMC Helix Discovery End-to-End Process
Introduction
BMC Helix Discovery gives you the relations across multiple resources and classifies these resources into various Business Services.
There are lot of synergies between Helix Discovery and Helix CloudOps platform and these two products compliment each other very well. While both of them scans for Cloud Resources, CloudOps shows the security and Cost posture of the Resources while Discovery lets customers understand the overall topology and Business service grouping. We would like to get this Business Service information from Discovery and show various CloudOps KPIs in context of the already defined Business Services.
One of the key aspects of Discovery integration is supporting RSSO. That will be covered in another SDD.
Terminologies
Comments |
|---|
An IT service that directly supports a business process. For example, financial services, online banking services delivered by banks to its customers, or Human Resource (HR) services delivered by an HR department. In IT organizations, business services are supported by different components, such as servers, applications, and databases. A user selects all the resources of a business service, creates an application model and publishes it as a Business Application Instance BMC Discovery enables you to add manually selected nodes to a group. Groups and subgroups enable you to collect all items that make up an application and divide them into subgroups to help you understand the structure and operation of an application. In Discovery, any business application instance, models, resources can be tagged using Manual Group. TSCO and TSCCC uses this manual group to identify the Business Service. Its syntax is Service::<Business Service Name> |
SaaS version of Discovery |
On-Premise version of Discovery? |
Group of resources based on a dynamic filter condition in CloudOps |
It performs a specific business function within a business service. It contains multiple technology tiers, such as web, app, and database. A user can select all the resources that constitute a business service and can create an application model. Once the model is published, it is saved as a Business Application Instance |
Templates that are used to deploy cloud resources are shown as Deployment model in Discovery |
Design
The work is divided in multiple phases -
Phases | Work Items |
|---|---|
Phase 1 | Discovery Connector Auto creating Resource Pools from Discovery Business Services and tagging Resources under these Services in CloudOps Cross Launch from specific resource types from Cloud Ops to Discovery RSSO integration |
Phase 2 | Sync all Resources even if it is not part of any business Service |
Phase 3 | Support multiple Discovery Connectors. |