Migrating to a new hardware type model without Fix scriptOverview Hardware types are configuration items (CI)s that represent pre-defined virtual machine types provided by cloud vendors. Cloud vendors provide several hundreds of out-of-box types. In most cases, customers are using the out-of-box types(Example- t2.nano, t2.micro, t2.large in AWS). Old Hardware Type Model This model uses the class cmdb_ci_compute_template (label: Hardware Type). This class is a dependent class on cmdb_ci_logical_datacenter.The result of this modeling is that each out-of-box hardware type is modeled in the CMDB N times where N = number of service accounts * number of logical datacenters.Customers with hundreds of service accounts end up discovering millions of hardware type records in the CMDB. This slows down discovery and other related flows that can cause performance issues.Hence, customers are puzzled by the fact that hundreds of hardware types present in the cloud (AWS, AZURE, GCP) result in millions of records being persisted in the CMDB. New Hardware Type Model This model reduces the number of hardware type records in the CMDB.Hardware types are populated in cmdb_ci_cloud_hardware_type (label: Cloud Hardware Type). This is an independent class. It will create one record for each hardware type irrespective of the Service account and data center.This will reduce the millions of hardware type records to hundreds of records. Release This feature is available in the following release. Release Version - June 2023 1.6.0(i.e. Next version after 1.3.0) Two new patterns "Amazon AWS - Cloud Hardware Type (LP)" and "Azure - Cloud Hardware Type (LP)" are introduced in the Release version of June 2023 (1.6.0) Prerequisites Before migrating to the new model, the following criteria should be met: For AWS/ Azure Customers, this new model is relevant who have already migrated from CAPI to Patterns( AWS, Azure) -Migrate CAPI to pattern.If Cloud Provisioning and Governance(CPG) plugin is active then CPG is supporting this feature from San Diego family releases or beyond. If Cloud Insights store app is active then Cloud insights is supporting this feature from plugin version 2.2.0 or later. Existing Solution 1.3.0 and before versions, followed KB0955939 to Migrate to a hardware type model. New Solution To migrate to a new hardware type model, set the System Property "sn_itom_pattern.use a single hardware type for cloud data centers" to true. To do this, Navigate to Filter Navigator -> enter sys_properties.list -> Search for sn_itom_pattern.use a single hardware type for cloud data centers To Delete old model Hardware type records, import the update set in Global Scope and commit it. Once the update set has been committed, follow the steps below: Navigate from the Filter Navigator -> System Definition -> Scheduled Jobs -> Search for job Named "Old Hardware Types Model records Mark as Absent"Activate the Scheduled job by clicking on "Active" and then click on "Update"This Schedule Job will periodically update the old model(cmdb_ci_compute_template) cis status as Absent. Table cleaner will clean the Absent records in cmdb_ci_compute_template table. Note: 1. If you haven't deleted old model hardware type records, migrated to a new model and run cloud discovery, you may observe both old and new model records and relations in CMDB. 2. You can adjust the repeat interval and follow system property values to optimize the performance. delete_old_hardware_type_job_count - The number of Jobs run at a time. The default value is 10delete_old_hardware_type_batch_size - The number records each Job process. The default value is 10000 Note: 1. Starting from June 2023 and later releases, It is advised not to apply the update set specified in KB0955939. 2. Release version June 2023 onwards, "Amazon AWS - Hardware Type (LP)" and "Azure - Hardware Type (LP)" won't get future updates. 3. Changing the System property "sn_itom_pattern.use a single hardware type for cloud data centers" from true to false by flipping it is not supported (It means New model to Old model). Flow Diagram ***** END ******