Creating Asset Groups via CSV Upload

Owned by Steve Baer (Unlicensed)
Last updated: May 08, 2024 by Shoyeb Shaikh
4 min read

Overview

Using Cloudamize precloud customers can calculate and compare TCO across AWS, Azure, and Google Cloud Platform; automatically discover all applications and their dependencies; determine which applications to migrate and when; identify their optimal instances and storage options; design a phased migration plan; and gain clear visibility into cloud costs for better control. Armed with deep analysis and insights, customers can make informed decisions at each stage.

Additionally the customer can create a predefined or custom resource grouping. User can use the Pre-Cloud Settings section to create Groups and Assets. Users can then chose instances and move them across Groups and Assets. Alternatively a Pre-Cloud user should be able to download the inventory into a CSV, make desired changes to the CSV and upload it back to the system. This should trigger the updating of inventory groupings as specified in the modified CSV.

It's important to note this feature is meant for use prior to starting the assessment. Once an assessment is started the Asset Groups are 'locked' for purposes of data processing.

Goals

Cloudamize Customer can download the inventory as a CSV file, make changes to various attributes of an instance and reload it back to the system. User should be allowed to change the following.

  1. Asset Name

  2. Assessment Scope

  3. CPU Type

  • Asset Name

    • Changing of the Asset Name in the CSV, will move the instance into the Asset specified in that row.

    • If the Asset Name do not exist, the system will create a new Asset with that name and move it to that Asset.

  • Assessment Scope

    • Accept "Included" or "Excluded"  as values to this column.

    • If this column is used - check that nodes monitored is still less than nodes purchased, otherwise apply other changes and include in error report that there are not enough licenses available to include additional machines in scope

  • CPU Type

    • The number of cores allocated to the machine is necessary and will be specified as a positive integer in the column after CPU Type

Workflow

  1. Login to the Pre-Cloud platform @ https://console.cloudamize.com

  2. This will take us to the Landing Screen on the Pre-Cloud application. Choose “Settings” from the Top Right “User Actions” Tray from the Landing Screen.

    image-20240321-045342.png

     

  3. This will take the user to the “Instance Settings“ page of the Inventory Settings Section. On the Instance Settings page, click “Upload Inventory Settings“ to initiate the feature.

    image-20240320-073518.png

     

  4. Clicking on “Upload Inventory Settings“ will open up the “Upload Inventory Settings to Control Inventory Settings“ pop-up. For the first-time user, it would be advisable to download the Sample CSV, by clicking the “Download Template CSV“ button on the pop-up. Sample CSV is essentially the listing of the entire Inventory for the chosen Infrastructure. This downloaded file is also a template for the CSV to be uploaded.

     

  5. Below is a screenshot of the downloaded Sample file. User can make changes to the records (Asset Name, Assessment Scope, CPU Type) in the CSV and upload it back to the system. It should be noted that user should not make any changes to the header’s or columns of the CSV. This will result in the CSV being invalidated.

    Infrastructure_Settings

     

  6. Once the desired changes are made to the records user can upload the CSV back to the system. The user will need to carry out the following actions to upload the file.

    1. Click the “Inventory Settings File“ button to choose a file from the file system.

    2. Once the correct file is chosen click the “Upload“ button to upload it back to the system.

       

  7. The upload process will validate the file format, if the format is found to be valid it will start processing the records in the file, and identify the changes, and update the system. After the entire process is complete it will show a result pop-up which will list all the validation errors the system encountered in the file and list it down on the pop-up window, all other records will be processed successfully.

     

  8. If all the records are processed without any validation errors, the system will display a success message.

     

  9. The changes made via CSV will now be reflected in the instance settings grid.