Hi Rohit Good Ideas !, Please find my feedback inline
1. Does it make sense to simply the Default View as a Project which cannot be deleted and primary space for the Account. Essentially, the default view is the logged in account/user's project with no other collaborators Kiran> I prefer to keep the Default view as there should be some differentiation Projects is a feature (like grouping) through which a user can organize his resources in Cloudstack. Other public cloud providers uses the concept of resource groups to organize a account resources May be it could be useful is future as more integrations are added to Cloudstack 2. Migrate all isolated network constructs as VPC with a single tier. Kiran> +1 for this All other public cloud providers by default deploy a vpc network along with the vm deployment Do you mean by default Cloudstack, should create a vpc network , instead of isolated network ? Currently isolated network is created by default during vm creation 3. Simplify templates/isos that are listed in deploy VM form: as a user, the template/iso section of the deploy VM form is complicated, would it make sense to simplify the template/iso shown as groups of guest OS family (like several other portals) and templates uploaded/registered by the account separately. Kiran> +1 for this Also I believe the community and shared filter can be merged into one as it simplifies 4. Remove data disk from VM deploy form, or hide it by default (show a button - add volume): Currently, the deploy VM form only supports one data disk, however API can multiple disks. One can always still use APIs, but deploy VM and later attach more disks; or deploy vm but not start it, attach as many data disks as we want and then start it. Kiran> I believe the data disk should be present in the vm deploy form, as the user should have the option to select large disk for his use case Also when deploying a vm from ISO, a data disk offering is a mandatory feild 5. Show user-data and affinity (placement) groups as a first-class step, not hidden under advanced menu. Kiran> +1, as user-data(cloud-init) is widely used in automation as it helps in bringing up the vm with the required configuration +1 also for shifting the affinity groups from advanced menu 6. Offering groups or bundles: introduce way to group/bundle compute/data offerings; for example, I want to see CPU optimised offerings, memory optimiised offerings, specialised offerings (say GPU) etc. Kiran> +1, for this Regards Kiran From: Rohit Yadav <rohit.ya...@shapeblue.com> Date: Friday, 11 August 2023 at 9:44 PM To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Cc: us...@cloudstack.apache.org <us...@cloudstack.apache.org> Subject: [DISCUSS] Simplifying constructs and UX All, Request for comments on following ideas, largely in the UI: 1. Does it make sense to simply the Default View as a Project which cannot be deleted and primary space for the Account. Essentially, the default view is the logged in account/user's project with no other collaborators 2. Migrate all isolated network constructs as VPC with a single tier. 3. Simplify templates/isos that are listed in deploy VM form: as a user, the template/iso section of the deploy VM form is complicated, would it make sense to simplify the template/iso shown as groups of guest OS family (like several other portals) and templates uploaded/registered by the account separately. 4. Remove data disk from VM deploy form, or hide it by default (show a button - add volume): Currently, the deploy VM form only supports one data disk, however API can multiple disks. One can always still use APIs, but deploy VM and later attach more disks; or deploy vm but not start it, attach as many data disks as we want and then start it. 5. Show user-data and affinity (placement) groups as a first-class step, not hidden under advanced menu. 6. Offering groups or bundles: introduce way to group/bundle compute/data offerings; for example, I want to see CPU optimised offerings, memory optimiised offerings, specialised offerings (say GPU) etc. Regards.
