[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #339: Polish
blueorangutan commented on PR #339: URL: https://github.com/apache/cloudstack-documentation/pull/339#issuecomment-1677498995 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/339. (QA-JID 112) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #339: Polish
blueorangutan commented on PR #339: URL: https://github.com/apache/cloudstack-documentation/pull/339#issuecomment-1677496475 @vladimirpetrov a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] vladimirpetrov commented on pull request #339: Polish
vladimirpetrov commented on PR #339: URL: https://github.com/apache/cloudstack-documentation/pull/339#issuecomment-1677493238 @blueorangutan docbuild -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #318: added example to generate the kubernetes iso
blueorangutan commented on PR #318: URL: https://github.com/apache/cloudstack-documentation/pull/318#issuecomment-1677104270 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/318. (QA-JID 111) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #318: added example to generate the kubernetes iso
blueorangutan commented on PR #318: URL: https://github.com/apache/cloudstack-documentation/pull/318#issuecomment-1677103066 @kiranchavala a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] rohityadavcloud merged pull request #340: storage: clarify volume and snapshot deletion behaviour
rohityadavcloud merged PR #340: URL: https://github.com/apache/cloudstack-documentation/pull/340 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] kiranchavala commented on pull request #318: added example to generate the kubernetes iso
kiranchavala commented on PR #318: URL: https://github.com/apache/cloudstack-documentation/pull/318#issuecomment-1677101639 @blueorangutan docbuild -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #340: storage: clarify volume and snapshot deletion behaviour
andrijapanicsb commented on PR #340: URL: https://github.com/apache/cloudstack-documentation/pull/340#issuecomment-1677075998 LGTM -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] rohityadavcloud commented on pull request #340: storage: clarify volume and snapshot deletion behaviour
rohityadavcloud commented on PR #340: URL: https://github.com/apache/cloudstack-documentation/pull/340#issuecomment-1676998962 https://qa.cloudstack.cloud/builds/docs-build/pr/340/adminguide/storage.html#volume-deletion-and-garbage-collection -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #340: storage: clarify volume and snapshot deletion behaviour
blueorangutan commented on PR #340: URL: https://github.com/apache/cloudstack-documentation/pull/340#issuecomment-1676995223 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/340. (QA-JID 110) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #340: storage: clarify volume and snapshot deletion behaviour
blueorangutan commented on PR #340: URL: https://github.com/apache/cloudstack-documentation/pull/340#issuecomment-1676993888 @rohityadavcloud a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] rohityadavcloud commented on pull request #340: storage: clarify volume and snapshot deletion behaviour
rohityadavcloud commented on PR #340: URL: https://github.com/apache/cloudstack-documentation/pull/340#issuecomment-1676993292 @blueorangutan docbuild -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] rohityadavcloud opened a new pull request, #340: storage: clarify volume and snapshot deletion behaviour
rohityadavcloud opened a new pull request, #340: URL: https://github.com/apache/cloudstack-documentation/pull/340 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [DISCUSS] Simplifying constructs and UX
Rohit, I either agree or have no strong opinion on points 2 through 6, but I do not think point 1 is a good idea. Users in some cases rely heavily on projects and/or sharing domains and accounts. The two constructs both have earned their right to existence in production environments. €0,02 On Mon, Aug 14, 2023 at 10:48 AM Kiran Chavala wrote: > 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 > Date: Friday, 11 August 2023 at 9:44 PM > To: dev@cloudstack.apache.org > Cc: 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. > > > > > > -- Daan
Re: [DISCUSS] Simplifying constructs and UX
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 Date: Friday, 11 August 2023 at 9:44 PM To: dev@cloudstack.apache.org Cc: 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.
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #335: AutoScaling: add reset data of vm instances
blueorangutan commented on PR #335: URL: https://github.com/apache/cloudstack-documentation/pull/335#issuecomment-1676919140 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/335. (QA-JID 109) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #335: AutoScaling: add reset data of vm instances
blueorangutan commented on PR #335: URL: https://github.com/apache/cloudstack-documentation/pull/335#issuecomment-1676917901 @borisstoyanov a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-documentation] borisstoyanov commented on pull request #335: AutoScaling: add reset data of vm instances
borisstoyanov commented on PR #335: URL: https://github.com/apache/cloudstack-documentation/pull/335#issuecomment-1676916402 @blueorangutan docbuild -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-terraform-provider] fabiomatavelli opened a new pull request, #70: Adds dependabot
fabiomatavelli opened a new pull request, #70: URL: https://github.com/apache/cloudstack-terraform-provider/pull/70 This PR will add Dependabot configuration to keep dependencies updated. After merging #64, the CI will run the acceptance test that will improve de Dependabot changes tests, before merge. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
