Steps to introduce a new Cloud Provider in the Cloud Discovery Schedule Creation UI

[srikanthnelapud]

Cloud Discovery Unification (CDU) UI / Cloud Discovery UI / Cloud Schedule UI talks about the feature introduced in New York to support the Cloud Discovery Schedule creation via a guided UI involving 4 Stages - Account Validation, Datacenter Discovery, Deep Discovery Choice (Optional), Schedule Frequency.

Attached the Image for a better idea.

Since New York, the feature went through various enhancements to align with the new features provided by the Cloud Providers. this CDU UI is also enabled or tailored in such a way that, one can introduce or create a new Cloud Provider at ease and mostly with some configuration changes and 0 script-related changes.

Below are steps to introduce a new Cloud Provider and leverage the same in CDU to create Cloud Schedules further.

(Following the below order is most important and to understand let's assume we wanted to support Cloud called 'ABC')

1. Ensure to create the table that extends the "Logical Datacenter" table i.e., Example: cmdb_ci_abc_datacenter
2. Add an entry in the Cloud Provider (sn_capi_provider) table with Name = ABC and Datacenter class is the above. **** Please add all the necessary mappings i.e., Cloud Product and Cloud Resource Type for each product. Take any existing Cloud Provider for reference
3. Go to the mid server and select any that has cloud capability if the mid server(s) are configured specifically to Cloud Provider(s) then go to Capabilities and Add respective Cloud Provider and Update i.e., Example: Select 'ABC'
4. Create a table that extends the "Credentials" table i.e., Example: abc_credentials
5. Add entry in the Discovery Cloud Providers (discovery_cloud_provider) table whose Provider = ABC and Credentials is the above
6. Go for the Service Accounts Field Options (service_account_field_options) table and add entries for the new Cloud provided added in the above step.  **** Please make sure that when adding the entries - the value provided in the NAME is what goes behind the framework so you need to strictly follow the case as it's case-sensitive so the names - "accountId", "discoveryCredentials", "name", datacenterURL". Whereas the value provided in the LABEL is what shown in the UI so anything can be given depending on the Cloud Provider we're adding.
7. Create necessary patterns in the Discovery Patterns (sn_discovery_patterns) table whose type is "Infrastructure" and CI type mapped to Cloud Service Account (cmdb_ci_cloud_service_account) table. **** Please make sure to write the patterns for the functionality - Account Validation, Datacenter Discovery, Sub Account Discovery (If applicable)
8. Add entries in the Cloud Discovery Topology Pattern (sa_cloud_topology_discovery_pattern) table for each phase and pointing to specific patterns accordingly created above.
9. Go to the CDU UI via Discovery module => Home => View Schedule (Card) => Add Schedules (Top right side of the UI) => Add Cloud Schedule.

You should be able to leverage the new Cloud Provider with the above steps now but of course, with all the necessary Mid Script Includes to handle the API requests done by the Patterns.

For more information, especially debugging, please take a look at the below article -

Useful Logs to find more information during Cloud Discovery Schedule creation