Re: [PR] project: note on project roles [cloudstack-documentation]
shwstppr commented on PR #403: URL: https://github.com/apache/cloudstack-documentation/pull/403#issuecomment-2154144603 @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
Re: [PR] project: note on project roles [cloudstack-documentation]
vishesh92 commented on code in PR #403: URL: https://github.com/apache/cloudstack-documentation/pull/403#discussion_r1630687547 ## source/adminguide/projects.rst: ## @@ -288,6 +288,16 @@ to add members in CloudStack, but only one way is enabled at a time: the UI. +Working with Project Roles +-- +CloudStack allows adding project members with a desired project role. A +project role will be assigned to the member in addition to their base +account role. Project Roles are retrictive in nature and can be used to +further restrict certain API access to the members within the project. +Project roles can be created or managed using `Project roles` tab in the +project details UI. Review Comment: @shwstppr Just added the below line to be more clear. ``` It is important to note that a project role cannot be used to elevate an existing user's permissions. ``` -- 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: [PR] project: note on project roles [cloudstack-documentation]
vishesh92 commented on code in PR #403: URL: https://github.com/apache/cloudstack-documentation/pull/403#discussion_r1630686861 ## source/adminguide/projects.rst: ## @@ -288,6 +288,16 @@ to add members in CloudStack, but only one way is enabled at a time: the UI. +Working with Project Roles +-- +CloudStack allows adding project members with a desired project role. A +project role will be assigned to the member in addition to their base +account role. Project Roles are retrictive in nature and can be used to +further restrict certain API access to the members within the project. +Project roles can be created or managed using `Project roles` tab in the +project details UI. Review Comment: ```suggestion further restrict certain API access to the members within the project. It is important to note that a project role cannot be used to elevate an existing user's permissions. Project roles can be created or managed using `Project roles` tab in the project details UI. ``` -- 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: [PR] project: note on project roles [cloudstack-documentation]
shwstppr commented on code in PR #403: URL: https://github.com/apache/cloudstack-documentation/pull/403#discussion_r1630679591 ## source/adminguide/projects.rst: ## @@ -288,6 +288,16 @@ to add members in CloudStack, but only one way is enabled at a time: the UI. +Working with Project Roles +-- +CloudStack allows adding project members with a desired project role. A +project role will be assigned to the member in addition to their base +account role. Project Roles are retrictive in nature and can be used to +further restrict certain API access to the members within the project. +Project roles can be created or managed using `Project roles` tab in the +project details UI. Review Comment: I don't have any example. IMO, I don't see any utility of project roles in its current form. So, I just added what was informed to me. Happy to accept changes or close the PR for better changes. -- 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: [PR] project: note on project roles [cloudstack-documentation]
vishesh92 commented on code in PR #403: URL: https://github.com/apache/cloudstack-documentation/pull/403#discussion_r1630663862 ## source/adminguide/projects.rst: ## @@ -288,6 +288,16 @@ to add members in CloudStack, but only one way is enabled at a time: the UI. +Working with Project Roles +-- +CloudStack allows adding project members with a desired project role. A +project role will be assigned to the member in addition to their base +account role. Project Roles are retrictive in nature and can be used to +further restrict certain API access to the members within the project. +Project roles can be created or managed using `Project roles` tab in the +project details UI. Review Comment: IMO, this seems a little confusing. It will be good to add an example to explain this. -- 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
[PR] project: note on project roles [cloudstack-documentation]
shwstppr opened a new pull request, #403: URL: https://github.com/apache/cloudstack-documentation/pull/403 Addresses https://github.com/apache/cloudstack/issues/9071 -- 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: [PR] Update documentation for strict host tags [cloudstack-documentation]
andrijapanicsb commented on PR #398: URL: https://github.com/apache/cloudstack-documentation/pull/398#issuecomment-2151803819 I think it makes more sense now, yes. Thanks Vishesh. -- 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: [PR] Update documentation for strict host tags [cloudstack-documentation]
vishesh92 commented on PR #398: URL: https://github.com/apache/cloudstack-documentation/pull/398#issuecomment-2151503904 @andrijapanicsb I have updated the documentation. Please review again. -- 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: [PR] instance: note on metadata [cloudstack-documentation]
blueorangutan commented on PR #402: URL: https://github.com/apache/cloudstack-documentation/pull/402#issuecomment-2149709115 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/402. (QA-JID 235) -- 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: [PR] instance: note on metadata [cloudstack-documentation]
blueorangutan commented on PR #402: URL: https://github.com/apache/cloudstack-documentation/pull/402#issuecomment-2149707256 @shwstppr 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
Re: [PR] instance: note on metadata [cloudstack-documentation]
shwstppr commented on PR #402: URL: https://github.com/apache/cloudstack-documentation/pull/402#issuecomment-2149705374 @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
Re: [PR] instance: note on metadata [cloudstack-documentation]
shwstppr commented on code in PR #402: URL: https://github.com/apache/cloudstack-documentation/pull/402#discussion_r1627662512 ## source/adminguide/virtual_machines.rst: ## @@ -205,6 +205,19 @@ following techniques: updateVirtualMachine API. After installing the tools and updating the Instance, stop and start the Instance. +Instance Metdata + + +CloudStack provides different means for controlling an instance's metadata. + +- 'extraconfig' parameter of 'deployVirtualMachine' or 'updateVirtualMachine' API methods + can be used for setting different metadata parameters for an instance. +- Global configurations - 'vm.metadata.manufacturer' and 'vm.metadata.product' can be used Review Comment: ```suggestion - Zone-level configurations - 'vm.metadata.manufacturer' and 'vm.metadata.product' can be used ``` -- 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
[PR] instance: note on metadata [cloudstack-documentation]
shwstppr opened a new pull request, #402: URL: https://github.com/apache/cloudstack-documentation/pull/402 Related to https://github.com/apache/cloudstack/pull/9163 -- 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: [PR] Implicit host tags on KVM [cloudstack-documentation]
rohityadavcloud merged PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392 -- 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
[PR] import-vm: remove username, password request params for vm import [cloudstack-documentation]
shwstppr opened a new pull request, #401: URL: https://github.com/apache/cloudstack-documentation/pull/401 Based on https://github.com/apache/cloudstack/issues/8414 -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
blueorangutan commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2123887995 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/395. (QA-JID 234) -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
blueorangutan commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2123887125 @abh1sar 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
Re: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2123886437 @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
Re: [PR] Migrate VMware VM to KVM improvement documentation [cloudstack-documentation]
andrijapanicsb commented on code in PR #388: URL: https://github.com/apache/cloudstack-documentation/pull/388#discussion_r1596569789 ## source/adminguide/virtual_machines/importing_vmware_vms_into_kvm.rst: ## @@ -108,8 +108,9 @@ Converting and importing a VMware VM When importing a Virtual Machine from VMware to KVM, CloudStack performs the following actions: -- Cloning the Source Virtual Machine on the selected VMware Datacenter: The source Virtual Machine will be cloned in the original state (running or stopped for Linux VMs, or stopped for Windows VMs). The recommended state is the stopped state to prevent data inconsistencies or loss when cloning the virtual machine. -- Converting the Cloned Virtual Machine to KVM using virt-v2v: CloudStack (or the administrator) selects a running and Enabled KVM host to perform the conversion from VMware to KVM using **virt-v2v**. If the binary is not installed, then the host will fail the migration. In case it is installed it will perform the conversion into a temporary location (which can be selected by the administrator) to store the converted QCOW2 disks of the virtual machine. The disks are then moved into the destination storage pools for the virtual machine. The conversion is a long-lasting process which can be set to time out by the global setting 'convert.vmware.instance.to.kvm.timeout'. The conversion processes take a long time because virt-v2v creates a temporary virtual machine to inspect the source VM and generate the converted disks with the correct drivers. Additionally, it needs to copy the converted disks into the temporary location. +- Clones the Source Virtual Machine on the selected VMware Datacenter: The source Virtual Machine will be cloned in the original state (running or stopped for Linux VMs, or stopped for Windows VMs). The recommended state is the stopped state to prevent data inconsistencies or loss when cloning the virtual machine. +- Exports the OVA from the Cloned Virtual Machine to a temporary location (which can be selected by the administrator). +- Converts the OVA on the temporary location to KVM using virt-v2v: CloudStack (or the administrator) selects a running and Enabled KVM host to perform the conversion from VMware to KVM using **virt-v2v**. If the binary is not installed, then the host will fail the migration. In case it is installed it will perform the conversion into the temporary location to store the converted QCOW2 disks of the virtual machine. The disks are then moved into the destination storage pools for the virtual machine. The conversion is a long-lasting process which can be set to time out by the global setting 'convert.vmware.instance.to.kvm.timeout'. The conversion processes takes a long time because virt-v2v creates a temporary virtual machine to inspect the source VM and generate the converted disks with the correct drivers. Additionally, it needs to copy the converted disks into the temporary location. Review Comment: "selects a running and Enabled KVM host to perform the conversion" This comment comes after some consultancy work, hopefully not too late... @sureshanaparti are there checks for this - i.e. do we support a scenario where cloud operator might have many Ubuntu 22.04 hosts, but want to use a (few) EL9 host (which has a much newer virt-v2v version than the Ubuntu 22.04, and thus much better conversion success than virt-v2v on Ubuntu hosts) for the conversion while ensuring that new VMs are not being regularly deployed on those EL9 hosts? (i.e. it would be good that admin can choose even a disabled host, or at least a host (Enabled, EL9), which exists in a DISABLED CLUSTER - is this possible?) -- 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
[PR] Minor corrections [cloudstack-documentation]
andrijapanicsb opened a new pull request, #400: URL: https://github.com/apache/cloudstack-documentation/pull/400 (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: [PR] notes on purging expunged resources [cloudstack-documentation]
shwstppr commented on code in PR #397: URL: https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1593441415 ## source/adminguide/tuning.rst: ## @@ -143,3 +143,76 @@ Article <http://support.citrix.com/article/CTX126531>`_.The article refers to XenServer 5.6, but the same information applies to XenServer 6 +Purging Expunged Resources +-- + +.. note:: + Currently only available for Instances and their linked resources. + +Over the time there are chances of piling up of millions of database records +for the removed or expunged resources. The presence of a lot of useless +records in the database can also affect the performance of cloud so it is Review Comment: ```suggestion records in the database can also affect the performance of the cloud so it is ``` -- 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: [PR] notes on purging expunged resources [cloudstack-documentation]
shwstppr commented on code in PR #397: URL: https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1593430757 ## source/adminguide/tuning.rst: ## @@ -143,3 +143,76 @@ Article <http://support.citrix.com/article/CTX126531>`_.The article refers to XenServer 5.6, but the same information applies to XenServer 6 +Purging Expunged Resources +-- + +..note:: + Currently only available for Instances and their linked resources. + +Over the time there are chances of piling up of millions of database records +for the removed or expunged resources. The presence of a lot of useless +records in the database can also affect the performance of cloud so it is +needed to purge such entries in a systematic way. +CloudStack provides the following methods to allow purging of the expunged +resources and their database records: + +Using background task +~ + +A background task will run at regular intervals. The interval for the task and +other parameters for it such as resource types, start and end date and batch size +can also be controlled with the help of global settings. + +The following new global settings have been introduced which would allow +configuring background task for purging the expunged resources: + +.. cssclass:: table-striped table-bordered table-hover + + === +Global setting Default values Description + === +expunged.resources.purge.enabled false Whether to run a background task to purge the expunged resources. +expunged.resources.purge.resources (empty)A comma-separated list of resource types that will be considered by the background task to purge the expunged resources. Currently only VirtualMachine is supported. An empty "value will result in considering all resource types for purging. +expunged.resources.purge.interval 86400 Interval (in seconds) for the background task to purge the expunged resources. +expunged.resources.purge.delay 300Initial delay (in seconds) to start the background task to purge the expunged resources task. +expunged.resources.purge.batch.size50 Batch size to be used during expunged resources purging. +expunged.resources.purge.start.time(empty)Start time to be used by the background task to purge the expunged resources. Use format -MM-dd or -MM-dd HH:mm:ss. +expunged.resources.purge.keep.past.days30 The number of days in the past from the execution time of the background task to purge the expunged resources for which the expunged resources must not be purged. To enable purging expunged resource till the execution of the background task, set the value to zero. Review Comment: I guess the complete sentence makes sense as it is, ``` The number of days in the past from the execution time of the background task to purge the expunged resources for which the expunged resources must not be purged ``` If needed, we can rephrase the whole statement -- 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: [PR] notes on purging expunged resources [cloudstack-documentation]
sureshanaparti commented on code in PR #397:
URL:
https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1593391833
##
source/adminguide/tuning.rst:
##
@@ -143,3 +143,76 @@ Article
<http://support.citrix.com/article/CTX126531>`_.The article
refers to XenServer 5.6, but the same information applies to XenServer 6
+Purging Expunged Resources
+--
+
+..note::
+ Currently only available for Instances and their linked resources.
+
+Over the time there are chances of piling up of millions of database records
+for the removed or expunged resources. The presence of a lot of useless
+records in the database can also affect the performance of cloud so it is
+needed to purge such entries in a systematic way.
+CloudStack provides the following methods to allow purging of the expunged
+resources and their database records:
+
+Using background task
+~
+
+A background task will run at regular intervals. The interval for the task and
+other parameters for it such as resource types, start and end date and batch
size
+can also be controlled with the help of global settings.
+
+The following new global settings have been introduced which would allow
+configuring background task for purging the expunged resources:
+
+.. cssclass:: table-striped table-bordered table-hover
+
+
===
+Global setting Default values
Description
+
===
+expunged.resources.purge.enabled false Whether
to run a background task to purge the expunged resources.
+expunged.resources.purge.resources (empty)A
comma-separated list of resource types that will be considered by the
background task to purge the expunged resources. Currently only VirtualMachine
is supported. An empty "value will result in considering all resource types for
purging.
+expunged.resources.purge.interval 86400 Interval
(in seconds) for the background task to purge the expunged resources.
+expunged.resources.purge.delay 300Initial
delay (in seconds) to start the background task to purge the expunged resources
task.
+expunged.resources.purge.batch.size50 Batch
size to be used during expunged resources purging.
+expunged.resources.purge.start.time(empty)Start
time to be used by the background task to purge the expunged resources. Use
format -MM-dd or -MM-dd HH:mm:ss.
+expunged.resources.purge.keep.past.days30 The
number of days in the past from the execution time of the background task to
purge the expunged resources for which the expunged resources must not be
purged. To enable purging expunged resource till the execution of the
background task, set the value to zero.
+
===
+
+
+Using API
+~
+
+An admin-only API `purgeExpungedResources` allows purging the expunged
resources
+with desired parameters. It will allow passing the following parameters -
+resourcetype, batchsize, startdate, enddate. An example of
purgeExpungedResources
+API call is shown below:
+
+
+.. parsed-literal::
+
+ > purge expungedresources startdate=2024-04-15 enddate=2024-04-20
resourcetype=VirtualMachine
+ {
+ "purgeexpungedresourcesresponse": {
+ "resourcecount": 6
+ }
+ }
+
+
+Using configuration in offerings
+
+..note::
+ Available only for service offerings
+
+_purgeresources_ configuration for offerings can be used to allow immediately
+purging a resource when it is expunged. The configuration can be set to true or
+false _purgeresources_ parameter while creating the correspoding offerings. The
Review Comment:
```suggestion
false _purgeresources_ parameter while creating the corresponding offerings.
The
```
--
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: [PR] notes on purging expunged resources [cloudstack-documentation]
sureshanaparti commented on code in PR #397: URL: https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1593391508 ## source/adminguide/tuning.rst: ## @@ -143,3 +143,76 @@ Article <http://support.citrix.com/article/CTX126531>`_.The article refers to XenServer 5.6, but the same information applies to XenServer 6 +Purging Expunged Resources +-- + +..note:: + Currently only available for Instances and their linked resources. + +Over the time there are chances of piling up of millions of database records +for the removed or expunged resources. The presence of a lot of useless +records in the database can also affect the performance of cloud so it is +needed to purge such entries in a systematic way. +CloudStack provides the following methods to allow purging of the expunged +resources and their database records: + +Using background task +~ + +A background task will run at regular intervals. The interval for the task and +other parameters for it such as resource types, start and end date and batch size +can also be controlled with the help of global settings. + +The following new global settings have been introduced which would allow +configuring background task for purging the expunged resources: + +.. cssclass:: table-striped table-bordered table-hover + + === +Global setting Default values Description + === +expunged.resources.purge.enabled false Whether to run a background task to purge the expunged resources. +expunged.resources.purge.resources (empty)A comma-separated list of resource types that will be considered by the background task to purge the expunged resources. Currently only VirtualMachine is supported. An empty "value will result in considering all resource types for purging. +expunged.resources.purge.interval 86400 Interval (in seconds) for the background task to purge the expunged resources. +expunged.resources.purge.delay 300Initial delay (in seconds) to start the background task to purge the expunged resources task. +expunged.resources.purge.batch.size50 Batch size to be used during expunged resources purging. +expunged.resources.purge.start.time(empty)Start time to be used by the background task to purge the expunged resources. Use format -MM-dd or -MM-dd HH:mm:ss. +expunged.resources.purge.keep.past.days30 The number of days in the past from the execution time of the background task to purge the expunged resources for which the expunged resources must not be purged. To enable purging expunged resource till the execution of the background task, set the value to zero. Review Comment: ```suggestion expunged.resources.purge.keep.past.days30 The number of days in the past from the execution time of the background task to keep the expunged resources for which the expunged resources must not be purged. To enable purging expunged resource till the execution of the background task, set the value to zero. ``` -- 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: [PR] notes on purging expunged resources [cloudstack-documentation]
sureshanaparti commented on code in PR #397: URL: https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1593390218 ## source/adminguide/service_offerings.rst: ## @@ -319,6 +319,12 @@ To create a new compute offering: - **Storage Policy**: Name of the storage policy defined at vCenter, this is applicable only for VMware. When a specific Zone is selected, one of the storage policies can be selected from the list box. + - **Purge Resources**: Whether to cleanup instance and its associated resource from + database upon expunge. When set to true, the database records for the offering instances and its Review Comment: ```suggestion database upon expunge. When set to true, the database records for the instances with the offering and its ``` -- 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: [PR] notes on purging expunged resources [cloudstack-documentation]
sureshanaparti commented on code in PR #397: URL: https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1593390218 ## source/adminguide/service_offerings.rst: ## @@ -319,6 +319,12 @@ To create a new compute offering: - **Storage Policy**: Name of the storage policy defined at vCenter, this is applicable only for VMware. When a specific Zone is selected, one of the storage policies can be selected from the list box. + - **Purge Resources**: Whether to cleanup instance and its associated resource from + database upon expunge. When set to true, the database records for the offering instances and its Review Comment: ```suggestion database upon expunge. When set to true, the database records for the instances and its ``` -- 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: [PR] notes on purging expunged resources [cloudstack-documentation]
sureshanaparti commented on code in PR #397: URL: https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1593389810 ## source/adminguide/service_offerings.rst: ## @@ -319,6 +319,12 @@ To create a new compute offering: - **Storage Policy**: Name of the storage policy defined at vCenter, this is applicable only for VMware. When a specific Zone is selected, one of the storage policies can be selected from the list box. + - **Purge Resources**: Whether to cleanup instance and its associated resource from Review Comment: ```suggestion - **Purge Resources**: Whether to cleanup instance and its associated resources from ``` -- 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: [PR] Update documentation for strict host tags [cloudstack-documentation]
andrijapanicsb commented on code in PR #398: URL: https://github.com/apache/cloudstack-documentation/pull/398#discussion_r1592322542 ## source/adminguide/host_and_storage_tags.rst: ## @@ -49,6 +49,37 @@ To explain the behavior of host tags, some examples will be demonstrated with tw * Offering: h3 None of the hosts have compatible tags and it will not be possible to deploy a VM with the offering. However, CloudStack ignores this behavior when a host is manually selected. +.. _strict-host-tags: +Strict Host Tags +- +During certain operations, like changing compute offering, and starting or live +migrating an instance to a specific host, CloudStack will ignore the host tags, +which can lead to issues where a instance starts on an undesired host. + +To avoid a mismatch of tags, tags which must always match during any operation +can be defined in `vm.strict.host.tags`. If the tags which doesn't match are Review Comment: explain this is global configuration, it doesn't say it's a global config 'vm.strict.host.tags' -- 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: [PR] Update documentation for strict host tags [cloudstack-documentation]
andrijapanicsb commented on code in PR #398: URL: https://github.com/apache/cloudstack-documentation/pull/398#discussion_r1592321513 ## source/adminguide/host_and_storage_tags.rst: ## @@ -49,6 +49,37 @@ To explain the behavior of host tags, some examples will be demonstrated with tw * Offering: h3 None of the hosts have compatible tags and it will not be possible to deploy a VM with the offering. However, CloudStack ignores this behavior when a host is manually selected. +.. _strict-host-tags: +Strict Host Tags +- +During certain operations, like changing compute offering, and starting or live +migrating an instance to a specific host, CloudStack will ignore the host tags, +which can lead to issues where a instance starts on an undesired host. Review Comment: We should (?) reword this to explain that "ignoring tags" is mostly (or only?) done when Admin does some operations (and this is by design/desired in most cases) - however we are adding an add-on feature to force tags checks by this global setting. -- 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
[PR] Bump jinja2 from 3.1.3 to 3.1.4 [cloudstack-documentation]
dependabot[bot] opened a new pull request, #399: URL: https://github.com/apache/cloudstack-documentation/pull/399 Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.3 to 3.1.4. Release notes Sourced from https://github.com/pallets/jinja/releases;>jinja2's releases. 3.1.4 This is the Jinja 3.1.4 security release, which fixes security issues and bugs but does not otherwise change behavior and should not result in breaking changes. PyPI: https://pypi.org/project/Jinja2/3.1.4/;>https://pypi.org/project/Jinja2/3.1.4/ Changes: https://jinja.palletsprojects.com/en/3.1.x/changes/#version-3-1-4;>https://jinja.palletsprojects.com/en/3.1.x/changes/#version-3-1-4 The xmlattr filter does not allow keys with / solidus, greater-than sign, or = equals sign, in addition to disallowing spaces. Regardless of any validation done by Jinja, user input should never be used as keys to this filter, or must be separately validated first. GHSA-h75v-3vvj-5mfj Changelog Sourced from https://github.com/pallets/jinja/blob/main/CHANGES.rst;>jinja2's changelog. Version 3.1.4 Released 2024-05-05 The xmlattr filter does not allow keys with / solidus, greater-than sign, or = equals sign, in addition to disallowing spaces. Regardless of any validation done by Jinja, user input should never be used as keys to this filter, or must be separately validated first. :ghsa:h75v-3vvj-5mfj Commits https://github.com/pallets/jinja/commit/dd4a8b5466d8790540c181590b14db4d4d889d57;>dd4a8b5 release version 3.1.4 https://github.com/pallets/jinja/commit/0668239dc6b44ef38e7a6c9f91f312fd4ca581cb;>0668239 Merge pull request from GHSA-h75v-3vvj-5mfj https://github.com/pallets/jinja/commit/d655030770081e2dfe46f90e27620472a502289d;>d655030 disallow invalid characters in keys to xmlattr filter https://github.com/pallets/jinja/commit/a7863ba9d3521f1450f821119c50d19d7ecea329;>a7863ba add ghsa links https://github.com/pallets/jinja/commit/b5c98e78c2ee7d2bf0aa06d29ed9bf7082de9cf4;>b5c98e7 start version 3.1.4 https://github.com/pallets/jinja/commit/da3a9f0b804199845fcb76f2e08748bdaeba93ee;>da3a9f0 update project files (https://redirect.github.com/pallets/jinja/issues/1968;>#1968) https://github.com/pallets/jinja/commit/0ee5eb41d1a2d7d9a05a02dc26dd70e63aaaeeb1;>0ee5eb4 satisfy formatter, linter, and strict mypy https://github.com/pallets/jinja/commit/20477c63575175196bfc8103f223cc9f5642595d;>20477c6 update project files (https://redirect.github.com/pallets/jinja/issues/5457;>#5457) https://github.com/pallets/jinja/commit/e491223739dedbb1f4fc6a71340c1484e149d947;>e491223 update pyyaml dev dependency https://github.com/pallets/jinja/commit/36f98854c721f98ba103f97f65a8a098da5af0d7;>36f9885 fix pr link Additional commits viewable in https://github.com/pallets/jinja/compare/3.1.3...3.1.4;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo
Re: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
blueorangutan commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2095286200 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/396. (QA-JID 233) -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
blueorangutan commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2095285171 @sureshanaparti 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
Re: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
sureshanaparti commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2095283558 @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
Re: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
abh1sar commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2092929366 @blueorangutan builddoc -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
sureshanaparti commented on code in PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#discussion_r1588872064 ## source/adminguide/storage.rst: ## @@ -237,6 +238,74 @@ templates, and ISOs. .. note:: If files or folders are not associated with a cloudstack resource, it doesn't mean that they are not used by cloudstack. + +Setting NFS Mount Options on the Storage Pool + + +NFS mount options can be added while creating an NFS storage pool for +KVM hosts. When the storage pool is mounted on the KVM hypervisor host, +these options will be used. Options currently tested and supported are +`vers` and `nconnect`. + +Although it depends on the NFS server, but commonly supported `vers` values +are `3` for NFSv3 and minor versions `4.0, 4.1 and 4.2` for NFSv4. +`nconnect` values can range from 1 to 16. + +Administrator can give the NFS mount options while adding a Primary Storage +from the Create Zone Wizard as well as the Add Primary Storage form. +|nfs-mount-options-create-zone-wizard.png| +|nfs-mount-options-add-primary-storage.png| + +NFS mount options can be changed on a pre-existing Storage Pool in maintenance +mode using the Edit Primary Storage form. Running VMs using volumes in the +Storage Pool will either be stopped or the volumes would be migrated to other +available pools upon enabling maintenance mode. +Storage Pool will be unmounted and mounted again on the KVM hosts using the +new options upon cancelling the maintenance mode. +|nfs-mount-options-edit-primary-storage.png| + +Mount failing due to an incorrect Mount Option +^^ +Add Storage Pool will fail with the error ``An incorrect mount option was specified``. + +In the Update storage pool case, cancel maintenance will throw the above error. +The Administrator has to repeat the process of enabling maintenance mode, Review Comment: not need to enable maintenance mode again as pool would be in maintenance already, admin has to change the mount options to the correct one and then retry cancel the maintenance mode. -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
sureshanaparti commented on code in PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#discussion_r1588872064 ## source/adminguide/storage.rst: ## @@ -237,6 +238,74 @@ templates, and ISOs. .. note:: If files or folders are not associated with a cloudstack resource, it doesn't mean that they are not used by cloudstack. + +Setting NFS Mount Options on the Storage Pool + + +NFS mount options can be added while creating an NFS storage pool for +KVM hosts. When the storage pool is mounted on the KVM hypervisor host, +these options will be used. Options currently tested and supported are +`vers` and `nconnect`. + +Although it depends on the NFS server, but commonly supported `vers` values +are `3` for NFSv3 and minor versions `4.0, 4.1 and 4.2` for NFSv4. +`nconnect` values can range from 1 to 16. + +Administrator can give the NFS mount options while adding a Primary Storage +from the Create Zone Wizard as well as the Add Primary Storage form. +|nfs-mount-options-create-zone-wizard.png| +|nfs-mount-options-add-primary-storage.png| + +NFS mount options can be changed on a pre-existing Storage Pool in maintenance +mode using the Edit Primary Storage form. Running VMs using volumes in the +Storage Pool will either be stopped or the volumes would be migrated to other +available pools upon enabling maintenance mode. +Storage Pool will be unmounted and mounted again on the KVM hosts using the +new options upon cancelling the maintenance mode. +|nfs-mount-options-edit-primary-storage.png| + +Mount failing due to an incorrect Mount Option +^^ +Add Storage Pool will fail with the error ``An incorrect mount option was specified``. + +In the Update storage pool case, cancel maintenance will throw the above error. +The Administrator has to repeat the process of enabling maintenance mode, Review Comment: not need to enable maintenance mode again, admin has to change the mount options to the correct one and then cancel the maintenance mode. -- 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: [PR] notes on purging expunged resources [cloudstack-documentation]
DaanHoogland commented on code in PR #397: URL: https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1587394782 ## source/adminguide/tuning.rst: ## @@ -143,3 +143,76 @@ Article <http://support.citrix.com/article/CTX126531>`_.The article refers to XenServer 5.6, but the same information applies to XenServer 6 +Purging Expunged Resources +-- + +..note:: Review Comment: ```suggestion .. note:: ``` I think, not sure but the doc show the literal `..note::` -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
blueorangutan commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2089722181 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/396. (QA-JID 232) -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
blueorangutan commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2089721126 @abh1sar 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
Re: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
abh1sar commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2089720242 @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
Re: [PR] Update documentation for strict host tags [cloudstack-documentation]
blueorangutan commented on PR #398: URL: https://github.com/apache/cloudstack-documentation/pull/398#issuecomment-2088781142 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/398. (QA-JID 231) -- 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: [PR] Update documentation for strict host tags [cloudstack-documentation]
blueorangutan commented on PR #398: URL: https://github.com/apache/cloudstack-documentation/pull/398#issuecomment-2088779929 @vishesh92 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
Re: [PR] Update documentation for strict host tags [cloudstack-documentation]
vishesh92 commented on PR #398: URL: https://github.com/apache/cloudstack-documentation/pull/398#issuecomment-2088778482 @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
[PR] Update documentation for strict host tags [cloudstack-documentation]
vishesh92 opened a new pull request, #398: URL: https://github.com/apache/cloudstack-documentation/pull/398 Related PR: https://github.com/apache/cloudstack/pull/9017 -- 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: [PR] feature: webhooks [cloudstack-documentation]
blueorangutan commented on PR #385: URL: https://github.com/apache/cloudstack-documentation/pull/385#issuecomment-2088393256 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/385. (QA-JID 230) -- 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: [PR] feature: webhooks [cloudstack-documentation]
blueorangutan commented on PR #385: URL: https://github.com/apache/cloudstack-documentation/pull/385#issuecomment-2088392405 @shwstppr 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
Re: [PR] feature: webhooks [cloudstack-documentation]
shwstppr commented on PR #385: URL: https://github.com/apache/cloudstack-documentation/pull/385#issuecomment-2088391149 @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
Re: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
blueorangutan commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2087973044 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/395. (QA-JID 229) -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
blueorangutan commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2087972520 @abh1sar 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
Re: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2087972107 @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
[PR] notes on purging expunged resources [cloudstack-documentation]
shwstppr opened a new pull request, #397: URL: https://github.com/apache/cloudstack-documentation/pull/397 Feature PR: https://github.com/apache/cloudstack/pull/8999 -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
sureshanaparti commented on code in PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#discussion_r1579411396 ## source/adminguide/storage.rst: ## @@ -237,6 +238,66 @@ templates, and ISOs. .. note:: If files or folders are not associated with a cloudstack resource, it doesn't mean that they are not used by cloudstack. + +Setting NFS Mount Options on the Storage Pool + + +NFS mount options can be added while creating an NFS storage pool for +KVM hosts. When the storage pool is mounted on the KVM hypervisor host, +these options will be used. Options currently tested and supported are +`vers` and `nconnect`. + +Although it depends on the NFS server, but commonly supported `vers` values +are `3` for NFSv3 and minor versions `4.0, 4.1 and 4.2` for NFSv4. +`nconnect` values can range from 1 to 16. + +Administrator can give the NFS mount options while adding a Primary Storage +from the Create Zone Wizard as well as the Add Primary Storage form. +|nfs-mount-options-create-zone-wizard.png| +|nfs-mount-options-add-primary-storage.png| + +NFS mount options can be changed on a pre-existing Storage Pool using the +Edit Primary Storage form. Storage Pool needs to be unmounted and mounted +again on the KVM host using the new options. Running VMs using volumes +in the Storage Pool either need to be stopped or the volumes migrated. +So the NFS Mount Options field below is only shown if the Storage Pool Review Comment: I think, this and below 2 lines may not be required after updated with above suggestions -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
sureshanaparti commented on code in PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#discussion_r1579409393 ## source/adminguide/storage.rst: ## @@ -237,6 +238,66 @@ templates, and ISOs. .. note:: If files or folders are not associated with a cloudstack resource, it doesn't mean that they are not used by cloudstack. + +Setting NFS Mount Options on the Storage Pool + + +NFS mount options can be added while creating an NFS storage pool for +KVM hosts. When the storage pool is mounted on the KVM hypervisor host, +these options will be used. Options currently tested and supported are +`vers` and `nconnect`. + +Although it depends on the NFS server, but commonly supported `vers` values +are `3` for NFSv3 and minor versions `4.0, 4.1 and 4.2` for NFSv4. +`nconnect` values can range from 1 to 16. + +Administrator can give the NFS mount options while adding a Primary Storage +from the Create Zone Wizard as well as the Add Primary Storage form. +|nfs-mount-options-create-zone-wizard.png| +|nfs-mount-options-add-primary-storage.png| + +NFS mount options can be changed on a pre-existing Storage Pool using the +Edit Primary Storage form. Storage Pool needs to be unmounted and mounted +again on the KVM host using the new options. Running VMs using volumes +in the Storage Pool either need to be stopped or the volumes migrated. Review Comment: ```suggestion in the Storage Pool either need to be stopped or the volumes would be migrated to other available pools upon enabling maintenance. ``` -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
sureshanaparti commented on code in PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#discussion_r1579407561 ## source/adminguide/storage.rst: ## @@ -237,6 +238,66 @@ templates, and ISOs. .. note:: If files or folders are not associated with a cloudstack resource, it doesn't mean that they are not used by cloudstack. + +Setting NFS Mount Options on the Storage Pool + + +NFS mount options can be added while creating an NFS storage pool for +KVM hosts. When the storage pool is mounted on the KVM hypervisor host, +these options will be used. Options currently tested and supported are +`vers` and `nconnect`. + +Although it depends on the NFS server, but commonly supported `vers` values +are `3` for NFSv3 and minor versions `4.0, 4.1 and 4.2` for NFSv4. +`nconnect` values can range from 1 to 16. + +Administrator can give the NFS mount options while adding a Primary Storage +from the Create Zone Wizard as well as the Add Primary Storage form. +|nfs-mount-options-create-zone-wizard.png| +|nfs-mount-options-add-primary-storage.png| + +NFS mount options can be changed on a pre-existing Storage Pool using the +Edit Primary Storage form. Storage Pool needs to be unmounted and mounted +again on the KVM host using the new options. Running VMs using volumes Review Comment: ```suggestion again on the KVM host using the new options upon cancelling the maintenance. Running VMs using volumes ``` -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
sureshanaparti commented on code in PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#discussion_r1579406891 ## source/adminguide/storage.rst: ## @@ -237,6 +238,66 @@ templates, and ISOs. .. note:: If files or folders are not associated with a cloudstack resource, it doesn't mean that they are not used by cloudstack. + +Setting NFS Mount Options on the Storage Pool + + +NFS mount options can be added while creating an NFS storage pool for +KVM hosts. When the storage pool is mounted on the KVM hypervisor host, +these options will be used. Options currently tested and supported are +`vers` and `nconnect`. + +Although it depends on the NFS server, but commonly supported `vers` values +are `3` for NFSv3 and minor versions `4.0, 4.1 and 4.2` for NFSv4. +`nconnect` values can range from 1 to 16. + +Administrator can give the NFS mount options while adding a Primary Storage +from the Create Zone Wizard as well as the Add Primary Storage form. +|nfs-mount-options-create-zone-wizard.png| +|nfs-mount-options-add-primary-storage.png| + +NFS mount options can be changed on a pre-existing Storage Pool using the Review Comment: ```suggestion NFS mount options can be changed on a pre-existing Storage Pool in maintenance mode, using the ``` -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
blueorangutan commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2076326698 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/396. (QA-JID 228) -- 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: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
shwstppr commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2076325435 @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
Re: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
blueorangutan commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2076326010 @shwstppr 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
Re: [PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
abh1sar commented on PR #396: URL: https://github.com/apache/cloudstack-documentation/pull/396#issuecomment-2076323546 @sureshanaparti @rohityadavcloud @shwstppr @harikrishna-patnala please review -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
blueorangutan commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2075540039 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/395. (QA-JID 227) -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
blueorangutan commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2075538481 @abh1sar 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
Re: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2075536576 @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
Re: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on code in PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#discussion_r1578312560 ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- +Storage Provider combinations: + +- KVM - NFS - Default Primary + +- KVM - CEPH/RBD - Default Primary Review Comment: Done ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- +Storage Provider combinations: + +- KVM - NFS - Default Primary + +- KVM - CEPH/RBD - Default Primary + +- VMWare - NFS - Default Primary Review Comment: Done -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on code in PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#discussion_r1578312265 ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- Review Comment: Done ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- +Storage Provider combinations: Review Comment: Done ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- +Storage Provider combinations: + +- KVM - NFS - Default Primary Review Comment: Done -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on code in PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#discussion_r1578304752 ## source/_static/images/change-storage-pool-scope-to-zone.png: ## Review Comment: Yes, updated the image. -- 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
[PR] Documentation for adding NFS mount options to storage pool [cloudstack-documentation]
abh1sar opened a new pull request, #396: URL: https://github.com/apache/cloudstack-documentation/pull/396 Documentation PR for https://github.com/apache/cloudstack/pull/8947 -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
andrijapanicsb commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2074981410 I made a few proposals to make it more readable from the end user (user doesn't necessarily care about "protocol" and "provider" - simply saying "KVM with NFS" is enough - again - just a proposal from my side, to simplify it. -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
andrijapanicsb commented on code in PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#discussion_r1577912290 ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- Review Comment: ```suggestion This feature is tested and supported for the following Hypervisor and storage combinations: ``` -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
andrijapanicsb commented on code in PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#discussion_r1577912290 ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- Review Comment: ```suggestion This feature is tested and supported for the following Hypervisor and storage combinations ``` ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- +Storage Provider combinations: Review Comment: ```suggestion ``` ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VMs on such hosts using this +Storage Pool, it cannot be disconnected from the hosts. In this case the Scope +change operation will error out. Such VMs need to be stopped or migrated first. + +This feature is tested and supported for the following Hypervisor-Protocol- +Storage Provider combinations: + +- KVM - NFS - Default Primary Review Comment: ```suggestion - KVM with NFS ``` ## source/adminguide/storage.rst: ## @@ -185,6 +185,38 @@ ensure that the protocol is set to "Filesystem". |adding-local-pool-via-ui.png| +Changing the Scope of the Primary Storage +~ +Scope of a Primary Storage can be changed from Zone-wide to Cluster-wide +and vice versa when the Primary Storage is in Disabled state. +An action button is displayed in UI for each Primary Storage in Disabled state. + +|change-storage-pool-scope-via-ui.png| + +Scope change from Cluster to Zone will connect the Primary Storage to all Hosts +of the zone running the same hypervisor as set on the storage pool. + +|change-storage-pool-scope-to-zone.png| + +Scope change from Zone to Cluster will disconnect the Primary Storage from all +Hosts that were previously connected to the Primary Storage and are not a part +of the specified Cluster. So, if there are running VM
Re: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
blueorangutan commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2074756774 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/395. (QA-JID 226) -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
andrijapanicsb commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2074756067 I don't see the other image, but I've asked BO to build docs again, and if both images are visible, I'm LGTM with the rest, nice explanation. -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
blueorangutan commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2074755107 @andrijapanicsb 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
Re: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
andrijapanicsb commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2074754055 @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
Re: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
shwstppr commented on code in PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#discussion_r1577648386 ## source/_static/images/change-storage-pool-scope-to-zone.png: ## Review Comment: Do we need to update this image if the dialog has changed? -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2072985540 @weizhouapache resolved conflicts and added Cluster->Zone UI screenshot -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
weizhouapache commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2072471699 > > @abh1sar can you add a screenshot of cluster->zone change ? > > @weizhouapache you mean the cluster->zone change scope form in the adminguide? > >  @abh1sar looks good, can you add this image as well ? -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
weizhouapache commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2072472908 @abh1sar there are conflicts -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2072427539 @andrijapanicsb please review -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2072424218 > @abh1sar can you add a screenshot of cluster->zone change ? @weizhouapache you mean the cluster->zone change scope form in the adminguide?  -- 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: [PR] Add doc for importing and unmanaging volumes [cloudstack-documentation]
DaanHoogland merged PR #390: URL: https://github.com/apache/cloudstack-documentation/pull/390 -- 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: [PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
weizhouapache commented on PR #395: URL: https://github.com/apache/cloudstack-documentation/pull/395#issuecomment-2072155588 @abh1sar can you add a screenshot of cluster->zone change ? -- 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
[PR] Detail on changing primary storage scope added to adminguide and concepts [cloudstack-documentation]
abh1sar opened a new pull request, #395: URL: https://github.com/apache/cloudstack-documentation/pull/395 Documentation for Feature PR : https://github.com/apache/cloudstack/pull/8875 -- 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: [PR] Add doc for importing and unmanaging volumes [cloudstack-documentation]
weizhouapache commented on code in PR #390: URL: https://github.com/apache/cloudstack-documentation/pull/390#discussion_r1572690092 ## source/adminguide/storage.rst: ## @@ -1011,6 +1011,60 @@ Following is the example for checkVolume API usage and the result in the volume }, } + +Importing and Unmanaging Volumes from Storage Pools +~~ + +Since Apache CloudStack 4.19.1.0, importing and unmanaging volumes from primary storage pools are supported. + +.. note:: + Currenty the supported storage types are: NFS, Ceph and Local storage for KVM hypervisor. + +#. Log in to the CloudStack UI as an administrator. + +#. In the left navigation bar, click *Tools > Import DATA Volumes* section. + +#. Select the scope of the storage pool (Zone, Cluster, Host). + +#. Select the zone/pod/cluster/host of the storage pool. + +#. Select the storage pool. + +#. The unmanaged volumes on the storage pool are listed on the left panel. + +#. The managed volumes on the storage pool are listed on the right panel. + +|list-unmanaged-managed-volumes.png| + +To import a volume: + +#. select a unmanaged volume from the left panel, click "Import Volume" icon. + +#. In the Import Volume pop-up, select the Account Type, Domain/Account/Project and a disk offering. + +#. Click OK. + +|import-volume.png| + +.. note:: + The volume to be imported must be placed in the root directory of the storage pool. + The format of the volume should be QCOW2 on NFS/Local storage, and RAW on Ceph storage. + Encrypted volumes cannot be unmanaged or imported. Review Comment: ```suggestion The following volumes cannot be unmanaged or imported: (1) volume is encrypted; (2) volume is locked; (3) volume has a backing file. ``` -- 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: [PR] Implicit host tags on KVM [cloudstack-documentation]
weizhouapache commented on code in PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392#discussion_r1572679724 ## source/adminguide/host_and_storage_tags.rst: ## @@ -23,6 +23,18 @@ Host tags - Host tags are responsible for directing VMs to compatible hosts. They are validated with the host tags informed in the compute offerings or in the system offerings. +There are two types of host tags: + +- (Explicit) host tags: the host tags are managed by CloudStack, including the flexible host tags. Cloud operator can set, update, and delete host tags via CloudStack API or GUI. +- Implicit host tags: the host tags are not managed by CloudStack API. Review Comment: ```suggestion - Implicit host tags: the host tags are not managed by CloudStack API. Cloud operator cannot use both implicit host tags and flexible host tags. ``` ## source/adminguide/host_and_storage_tags.rst: ## @@ -23,6 +23,18 @@ Host tags - Host tags are responsible for directing VMs to compatible hosts. They are validated with the host tags informed in the compute offerings or in the system offerings. +There are two types of host tags: + +- (Explicit) host tags: the host tags are managed by CloudStack, including the flexible host tags. Cloud operator can set, update, and delete host tags via CloudStack API or GUI. +- Implicit host tags: the host tags are not managed by CloudStack API. + +.. note:: + Currently the implicit host tags are only configurable on KVM hosts. Review Comment: ```suggestion Cloud operator can easily set the implicit host tags per host based on server configurations, for example hardware devices (GPU type, disk type, network card type, etc). Currently the implicit host tags are only configurable on KVM hosts. ``` -- 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: [PR] Implicit host tags on KVM [cloudstack-documentation]
weizhouapache commented on PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392#issuecomment-2066816129 > @weizhouapache It would be good to have a note explaining that flexible tags must always be explicit added @JoaoJandre -- 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: [PR] Implicit host tags on KVM [cloudstack-documentation]
weizhouapache commented on code in PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392#discussion_r1572529561 ## source/adminguide/host_and_storage_tags.rst: ## @@ -23,6 +23,18 @@ Host tags - Host tags are responsible for directing VMs to compatible hosts. They are validated with the host tags informed in the compute offerings or in the system offerings. +There are two types of host tags: + +- (Explicit) host tags: the host tags are managed by CloudStack. Cloud operator can set, update, and delete host tags via CloudStack API or GUI. Review Comment: ```suggestion - (Explicit) host tags: the host tags are managed by CloudStack, including the flexible host tags. Cloud operator can set, update, and delete host tags via CloudStack API or GUI. ``` -- 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: [PR] Implicit host tags on KVM [cloudstack-documentation]
JoaoJandre commented on PR #392: URL: https://github.com/apache/cloudstack-documentation/pull/392#issuecomment-2066727316 @weizhouapache It would be good to have a note explaining that flexible tags must always be explicit -- 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: [PR] Add doc for importing and unmanaging volumes [cloudstack-documentation]
andrijapanicsb commented on code in PR #390: URL: https://github.com/apache/cloudstack-documentation/pull/390#discussion_r1572314144 ## source/adminguide/storage.rst: ## @@ -1011,6 +1011,60 @@ Following is the example for checkVolume API usage and the result in the volume }, } + +Importing and Unmanaging Volumes from Storage Pools +~~ + +Since Apache CloudStack 4.19.1.0, importing and unmanaging volumes from primary storage pools are supported. + +.. note:: + Currenty the supported storage types are: NFS, Ceph and Local storage for KVM hypervisor. + +#. Log in to the CloudStack UI as an administrator. + +#. In the left navigation bar, click *Tools > Import DATA Volumes* section. + +#. Select the scope of the storage pool (Zone, Cluster, Host). + +#. Select the zone/pod/cluster/host of the storage pool. + +#. Select the storage pool. + +#. The unmanaged volumes on the storage pool are listed on the left panel. + +#. The managed volumes on the storage pool are listed on the right panel. + +|list-unmanaged-managed-volumes.png| + +To import a volume, Review Comment: ```suggestion To import a volume: ``` -- 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: [PR] Add doc for importing and unmanaging volumes [cloudstack-documentation]
andrijapanicsb commented on code in PR #390: URL: https://github.com/apache/cloudstack-documentation/pull/390#discussion_r1572312874 ## source/adminguide/storage.rst: ## @@ -1011,6 +1011,60 @@ Following is the example for checkVolume API usage and the result in the volume }, } + +Importing and Unmanaging Volumes from Storage Pools +~~ + +Since Apache CloudStack 4.19.1.0, importing and unmanaging volumes from primary storage pools are supported. + +.. note:: + Currenty the supported storage types are: NFS, Ceph and Local storage for KVM hypervisor. + +#. Log in to the CloudStack UI as an administrator. + +#. In the left navigation bar, click *Tools > Import DATA Volumes* section. + +#. Select the scope of the storage pool (Zone, Cluster, Host). + +#. Select the zone/pod/cluster/host of the storage pool. + +#. Select the storage pool. + +#. The unmanaged volumes on the storage pool are listed on the left panel. + +#. The managed volumes on the storage pool are listed on the right panel. + +|list-unmanaged-managed-volumes.png| + +To import a volume, + +#. select a unmanaged volume from the left panel, click "Import Volume" icon. + +#. In the Import Volume pop-up, select the Account Type, Domain/Account/Project and a disk offering. + +#. Click OK. + +|import-volume.png| + +.. note:: + The volume to be imported must be placed in the root directory of the storage pool. + The format of the volume should be QCOW2 on NFS/Local storage, and RAW on Ceph storage. + Encrypted volumes cannot be unmanaged or imported. + +.. note:: + By default, the volume is imported for the caller if Domain/Account/Project are not set. By default, the imported volumes use the default disk offering "Default Custom Offering for Volume Import" + (on Shared storages) or "Default Custom Offering for Volume Import - Local" (on Local storages). + +To unmanage volume(s), Review Comment: ```suggestion To unmanage volume(s): ``` -- 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: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
JoaoJandre commented on PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#issuecomment-2066449225 > Cheers @JoaoJandre I see the tag and docs are live now, the website is updated too. I think only thing remaining is the ML announcement for you to draft/send. @rohityadavcloud Thanks, the announcement is already drafted, only waiting for the reviews: https://lists.apache.org/thread/hz3d737ok1s6ydnky54c4clsjddlkpfg -- 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: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
rohityadavcloud commented on PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#issuecomment-2065676667 Cheers @JoaoJandre I see the tag and docs are live now, the website is updated too. I think only thing remaining is the ML announcement for you to draft/send. -- 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: [PR] Add build to the .readthedocs.yaml [cloudstack-documentation]
JoaoJandre merged PR #394: URL: https://github.com/apache/cloudstack-documentation/pull/394 -- 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
[PR] Add build to the .readthedocs.yaml [cloudstack-documentation]
JoaoJandre opened a new pull request, #394: URL: https://github.com/apache/cloudstack-documentation/pull/394 Add build section to the .readthedocs.yaml to fix the build -- 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: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
JoaoJandre merged PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393 -- 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: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
rohityadavcloud commented on PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#issuecomment-2064656918 @JoaoJandre done, I've added you as a maintainer/admin on https://readthedocs.org/projects/cloudstack-documentation/ you should get receive an invite. After you log in, the steps to publishing a git tag is easy; (a) merge this PR and create a git push on this repo, (b) go to https://readthedocs.org/projects/cloudstack-documentation/ and under version or admin enable the version (4.18.2.0) and check (c) it should start the build and pass successfully, (d) edit the release/tag and make it public, that's it. -- 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: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
JoaoJandre commented on PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#issuecomment-2064596843 > LGTM - minor concerns raised, good to go. @JoaoJandre let me know if you have access of readthedocs, https://readthedocs.org/accounts/login/ - if not create an account and share your username. Alternatively, once this PR and git tag is ready we can hit publish for you too. cc @DaanHoogland @weizhouapache @rohityadavcloud I don't have admin access to the readthedocs, could you give me access? my username is: `JoaoJandre`. -- 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: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
blueorangutan commented on PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#issuecomment-2064593543 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/393. (QA-JID 225) -- 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: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
blueorangutan commented on PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#issuecomment-2064590467 @JoaoJandre 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
Re: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
JoaoJandre commented on PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#issuecomment-2064585892 @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
Re: [PR] Update docs for 4.18.2.0 [cloudstack-documentation]
JoaoJandre commented on code in PR #393: URL: https://github.com/apache/cloudstack-documentation/pull/393#discussion_r1571104966 ## source/releasenotes/changes.rst: ## @@ -14,7 +14,425 @@ under the License. -Changes in |release| since 4.18.0.0 +Changes in |release| since 4.18.1.0 +=== + +Apache CloudStack uses GitHub https://github.com/apache/cloudstack/milestone/29?closed=1 +to track its issues. + +.. cssclass:: table-striped table-bordered table-hover + + ++-+--+---+--++ +| Version | Github | Type | Priority | Description | Review Comment: done -- 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
