[GitHub] [cloudstack-documentation] Spaceman1984 opened a new pull request #226: Quick install guide update

[GitBox]

Spaceman1984 opened a new pull request #226:
URL: https://github.com/apache/cloudstack-documentation/pull/226


   Updated quick install guide to be in line with latest Cloudstack version


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] Spaceman1984 commented on a change in pull request #223: Host ha and multiple management server internal load balancing

[GitBox]

Spaceman1984 commented on a change in pull request #223:
URL: 
https://github.com/apache/cloudstack-documentation/pull/223#discussion_r662089830



##
File path: source/adminguide/reliability.rst
##
@@ -78,25 +156,8 @@ HA features work with iSCSI or NFS primary storage. HA with 
local
 storage is not supported.
 
 
-HA for Hosts
-
-
-The user can specify a virtual machine as HA-enabled. By default, all

Review comment:
   The title says HA for Hosts, but the content that followed was a 
duplication of the previous section.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] Spaceman1984 commented on a change in pull request #223: Host ha and multiple management server internal load balancing

[GitBox]

Spaceman1984 commented on a change in pull request #223:
URL: 
https://github.com/apache/cloudstack-documentation/pull/223#discussion_r662091009



##
File path: source/adminguide/reliability.rst
##
@@ -61,6 +61,84 @@ still available but the system VMs will not be able to 
contact the
 management server.
 
 
+Multiple Management Servers Support on agents
+-
+
+In a Cloudstack environment with multiple management servers, an agent can be
+configured, based on an algorithm, to which management server to connect to.
+This can be useful as an internal loadbalancer or for high availability.
+An administrator is responsible for setting the list of management servers and
+choosing a sorting algorithm using global settings.
+The management server is responsible for propagating the settings to the
+connected agents.
+
+Examples of an agent includes, the process responsible for communication to the

Review comment:
   I am trying to describe what I mean by the word "agent". Cloudstack has 
a few things that are called as such.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] Spaceman1984 commented on a change in pull request #223: Host ha and multiple management server internal load balancing

[GitBox]

Spaceman1984 commented on a change in pull request #223:
URL: 
https://github.com/apache/cloudstack-documentation/pull/223#discussion_r662091511



##
File path: source/adminguide/reliability.rst
##
@@ -126,6 +187,150 @@ that you want to dedicate to HA-enabled VMs.
a crash.
 
 
+HA-Enabled Hosts
+
+
+The user can specify a host as HA-enabled, In the event of a host 
+failure, attemps will be made to recover the failed host by first 
+issuing some OOBM commands. If the host recovery fails the host will be
+fenced and placed into maintenance mode. To restore the host to normal 
+operation, manual intervention would then be required.
+
+Out of band management is a requirement of HA-Enabled hosts and has to be 
+confiured on all intended participating hosts.
+(see `“Out of band management” `_).
+
+Host-HA has granular configuration on a host/cluster/zone level. In a large 
+environment, some hosts from a cluster can be HA-enabled and some not, 
+
+Host-HA uses a state machine design to manage the operations of recovering
+and fencing hosts. The current status of a host is reported when quering a 
+specific host.
+
+Timely health investigations are done on HA-Enabled hosts to monitor for
+any failures. Specific thersholds can be set for failed investigations,
+only when it’s exceeded, will the host transition to a different state.
+
+Host-HA uses both health checks and activity checks to make decisions on 
+recovering and fencing actions. Once determined that the host is in faulty 
+state (health checks failed) it runs activity checks to figure out if there is 
+any disk activity on the VMs running on the specific host.
+
+HA Resource Management Service
+~~

Review comment:
   ok, I'll remove the heading.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] Spaceman1984 commented on a change in pull request #223: Host ha and multiple management server internal load balancing

[GitBox]

Spaceman1984 commented on a change in pull request #223:
URL: 
https://github.com/apache/cloudstack-documentation/pull/223#discussion_r662092780



##
File path: source/adminguide/reliability.rst
##
@@ -61,6 +61,84 @@ still available but the system VMs will not be able to 
contact the
 management server.
 
 
+Multiple Management Servers Support on agents
+-
+
+In a Cloudstack environment with multiple management servers, an agent can be
+configured, based on an algorithm, to which management server to connect to.
+This can be useful as an internal loadbalancer or for high availability.
+An administrator is responsible for setting the list of management servers and
+choosing a sorting algorithm using global settings.
+The management server is responsible for propagating the settings to the
+connected agents.
+
+Examples of an agent includes, the process responsible for communication to the
+management server, running inside of the Secondary Storage Virtual Machine
+(SSVM), Console Proxy Virtual Machine (CPVM) or the cloudstack-agent running on
+a KVM host.
+
+The three global settings that need to be configured are the following:
+
+- hosts: a comma seperated list of management server IP addresses
+- indirect.agent.lb.algorithm: The algorithm for the indirect agent LB
+- indirect.agent.lb.check.interval: The preferred host check interval
+  for the agent's background task that checks and switches to an agent's
+  preferred host.
+
+These settings can be configured from the global settings page in the UI or
+using the updateConfiguration API call.
+
+The indirect.agent.lb.algorithm setting supports following algorithm options:
+
+- static: Use the list of management server IP addresses as provided.
+- roundrobin: Evenly spread hosts across management servers, based on the
+  host's id.
+- shuffle: Pseudo Randomly sort the list (this is not recommended for
+  production).
+
+Any changes to the global settings - `indirect.agent.lb.algorithm` and
+`host` does not require restarting of the management server(s) and the
+agents. A change in these global settings will be propagated to all connected
+agents.
+
+The comma-separated management server list is propagated to agents in
+following cases:
+- An addition of an agent (including ssvm, cpvm system VMs).
+- Connection or reconnection of an agent to a management server.
+- After an administrator changes the 'host' and/or the
+'indirect.agent.lb.algorithm' global settings.
+
+On the agent side, the 'host' setting is saved in its properties file as:
+`host=@`.
+
+From the agent's perspective, the first address in the propagated list
+will be considered the preferred host. A new background task can be
+activated by configuring the `indirect.agent.lb.check.interval` which is
+a cluster level global setting from CloudStack and adminitrators can also
+override this by configuring the 'host.lb.check.interval' in the
+`agent.properties` file.
+
+When an agent gets a host and algorithm combination, the host specific
+background check interval is also sent and is dynamically reconfigured
+in the background task without need to restart agents.
+
+Note: The 'static' and 'roundrobin' algorithms, strictly checks for the

Review comment:
   ok




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] alexandremattioli commented on pull request #225: Networking update and config drive

[GitBox]

alexandremattioli commented on pull request #225:
URL: 
https://github.com/apache/cloudstack-documentation/pull/225#issuecomment-872169571


   LGTM


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #226: Quick install guide update

[GitBox]

andrijapanicsb commented on pull request #226:
URL: 
https://github.com/apache/cloudstack-documentation/pull/226#issuecomment-87214


   @blueorangutan docbuild


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #226: Quick install guide update

[GitBox]

blueorangutan commented on pull request #226:
URL: 
https://github.com/apache/cloudstack-documentation/pull/226#issuecomment-872178203


   @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

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #226: Quick install guide update

[GitBox]

blueorangutan commented on pull request #226:
URL: 
https://github.com/apache/cloudstack-documentation/pull/226#issuecomment-872179066


   Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/226. 
(SL-JID 106)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-kubernetes-provider] rhtyd commented on pull request #32: Update Kubernetes version to 1.20.6

[GitBox]

rhtyd commented on pull request #32:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/pull/32#issuecomment-872179535


   Okay removing from 1.0 milestone


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [DISCUSS] Rocky 8.4 and CloudStack

[David Jumani]

Good idea Rohit, +1 on creating symlinks for el7, el8
I've also created a PR to support binary compatible variants of RHEL8. I'd 
appreciate feedback / testing from the community
I've tested it agianst Rocky & Alma and it seems to work just like C8 does

https://github.com/apache/cloudstack/pull/5158

From: Rohit Yadav 
Sent: Monday, June 28, 2021 4:32 PM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: Re: [DISCUSS] Rocky 8.4 and CloudStack

Great thanks all for the discussion, so what we mostly agree on are:

  *   CentOS8, Rocky Linux 8 and other initiatives may all be binary compatible
  *   We can host all el8 repos which these distros may use
  *   The community may help validate the CloudStack el8 pkgs among one or more 
clear winner with time

As an immediate action, let's us publish all "centos8" or "rocky8" package 
repos under generic "el8" repos? For example, 
http://download.cloudstack.org/testing/nightly/latest/ we can add symlink or 
rename dirs as "el8", "el7".


Regards.


From: n...@li.nux.ro 
Sent: Thursday, June 24, 2021 21:12
To: dev@cloudstack.apache.org 
Cc: Nathan McGarvey 
Subject: Re: [DISCUSS] Rocky 8.4 and CloudStack

That's a very good suggestion, I'm sure we can sort out something.

Regards,
Lucian





 

On 2021-06-24 14:40, Nathan McGarvey wrote:
> Nux,
> Also agree regarding EL8.
>
> I wonder if it is possible to build on a RHEL "development" license
> where builds and smoke tests and such can be done without licensing
> cost.
> (https://developers.redhat.com/articles/faqs-no-cost-red-hat-enterprise-linux,
> https://developers.redhat.com/terms-and-conditions)
>
> I'm not a lawyer and the terms seem murky as to how an Open-Source
> project like CloudStack would interact with those terms, even in a
> non-production sense. Do any other ASF projects use RHEL for build/test
> servers or anything like that?
>
>
> Thanks,
> -Nathan McGarvey
>
>
>
> On 6/24/21 8:17 AM, Sven Vogel wrote:
>> @nux
>>
>> „Might be then worth going for supporting "EL8" and by that include
>> any
>> of Rocky, Alma, OtherClone etc.“
>>
>> Agree
>>
>> __
>>
>> Sven Vogel
>> Senior Manager Research and Development - Cloud and Infrastructure
>>
>> EWERK DIGITAL GmbH
>> Brühl 24, D-04109 Leipzig
>> P +49 341 42649 - 99
>> F +49 341 42649 - 98
>> s.vo...@ewerk.com
>> www.ewerk.com
>>
>> Geschäftsführer:
>> Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
>> Registergericht: Leipzig HRB 9065
>>
>> Support:
>> +49 341 42649 555
>>
>> Zertifiziert nach:
>> ISO/IEC 27001:2013
>> DIN EN ISO 9001:2015
>> DIN ISO/IEC 2-1:2018
>>
>> ISAE 3402 Typ II Assessed
>>
>> EWERK-Blog |
>> LinkedIn |
>> Xing |
>> Twitter |
>> Facebook
>>
>>
>> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>>
>> Disclaimer Privacy:
>> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien)
>> ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht
>> der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
>> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
>> informieren Sie in diesem Fall unverzüglich den Absender und löschen
>> Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem
>> System. Vielen Dank.
>>
>> The contents of this e-mail (including any attachments) are
>> confidential and may be legally privileged. If you are not the
>> intended recipient of this e-mail, any disclosure, copying,
>> distribution or use of its contents is strictly prohibited, and you
>> should please notify the sender immediately and then delete it
>> (including any attachments) from your system. Thank you.
>>
>> 
>> Von: n...@li.nux.ro 
>> Gesendet: Thursday, June 24, 2021 2:57:24 PM
>> An: dev@cloudstack.apache.org 
>> Betreff: Re: [DISCUSS] Rocky 8.4 and CloudStack
>>
>> Point taken. Good find with gdm, wonder if there are others.
>> I'm hoping this kind of problems disappear in time as the machine gets
>> "oiled" better.
>>
>> What I wanted to underline is that the situation is sort of like this:
>> Updates -> QA -> Stream -> RHEL
>>
>> Might be then worth going for supporting "EL8" and by that include any
>> of Rocky, Alma, OtherClone etc.
>>
>>
>>
>> On 2021-06-23 19:03, Nathan McGarvey wrote:
>>> Nux,
>>> Overall, I agree that it should be possible to use any other
>>> clone
>>> as they should be binary compatible.
>>>
>>> I don't quite understand your "pass through QA" and "basically
>>> RHEL
>>> packages" comment. There are already instances of breaking changes in
>>> CentOS 8 Stream that didn't make it into RHEL or CentOS non-stream.
>>> CentOS Stream is the only one where you *don't* know exactly what you
>>

[GitHub] [cloudstack-cloudmonkey] shwstppr opened a new issue #81: Unable to use new syncStoragePool API

[GitBox]

shwstppr opened a new issue #81:
URL: https://github.com/apache/cloudstack-cloudmonkey/issues/81


   Newly added `syncStoragePool` API doesn't work with Cloudmonkey 6.1.0. 
Instead of firing API it synchronizes API cache. Even while trying to get docs 
for the API it does the same.
   
   
![cmk-sync](https://user-images.githubusercontent.com/153340/124229531-6638b080-db2b-11eb-9205-4dd3381fcccf.gif)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-cloudmonkey] harikrishna-patnala commented on issue #81: Unable to use new syncStoragePool API

[GitBox]

harikrishna-patnala commented on issue #81:
URL: 
https://github.com/apache/cloudstack-cloudmonkey/issues/81#issuecomment-872754758


   @shwstppr here the auto completion API works fine, but when we actually run 
the command, it is ignoring the parameters after 'sync'
   
   If we run the API with full name it works fine,
   (localcloud) SBCM5> > **syncStoragePool** 
id=37cf387a-ea2f-3456-a98a-03bc282072fd
   {
 "storagepool": {
   "clusterid": "0c29f733-575b-4e6c-b7ff-9d595fc5bfb1",
   "clustername": "p1-c1",
   "created": "2021-05-11T15:51:13+",
   "disksizeallocated": 0,
   "disksizetotal": 2197949513728,
   "disksizeused": 1538292695040,
   "id": "37cf387a-ea2f-3456-a98a-03bc282072fd",
   "ipaddress": "10.0.32.142",
   "name": "DC",
   "overprovisionfactor": "2.0",
   "path": "/Trillian/DC",
   "podid": "d67d81d9-0235-4fb4-961e-0bd276776363",
   "podname": "Pod1",
   "provider": "DefaultPrimary",
   "scope": "CLUSTER",
   "state": "Up",
   "type": "DatastoreCluster",
   "zoneid": "4d21cd93-2bf4-46ab-99ed-d4e9d723591b",
   "zonename": "ref-trl-873-v-M7-vladimir-petrov"
 }
   }
   
   But yes, we need to fix 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

Re: [VOTE] Apache CloudStack 4.15.1.0 (RC3)

[Suresh Anaparti]

+1

Performed some manual tests for VMs, Volumes, Templates, ISOs, Isolated  
Networks, Volume Snapshots & VM Snapshots, in fresh installation (MS: CentOS 7 
+ KVM Hosts: CentOS 7).

Regards,
Suresh

On 30/06/21, 11:38 AM, "Rohit Yadav"  wrote:

+1 (binding) based on automated smoketests results with CentOS7 based mgmt 
server and CentOS7 KVM, XenServer 7.1, and Vmware 6.5/6.7.


Regards.


From: Boris Stoyanov 
Sent: Wednesday, June 30, 2021 10:30
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC3)

+1 (binding), considering the latest changes, I’ve did a quick test and 
checked the smoketests results, all looking good.

Bobby.

From: Rohit Yadav 
Date: Monday, 28 June 2021, 13:58
To: dev@cloudstack.apache.org , 
us...@cloudstack.apache.org 
Subject: [VOTE] Apache CloudStack 4.15.1.0 (RC3)
Hi All,

I've created a 4.15.1.0 release, with the following artifacts up for a vote:

Git Branch:
https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210628T1527
Commit SHA:
379454caae76279329c52aa6ae3eea389741d935

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/

PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open this week until 2 July 2021.

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

For users convenience, the packages from this release candidate and 4.15.1
systemvmtemplates are available here:
https://download.cloudstack.org/testing/4.15.1.0-RC3/
https://download.cloudstack.org/systemvm/4.15/

Documentation is not published yet, but the following may be referenced for
upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
registered prior to upgrade)

https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade

Regards.








 

[GitHub] [cloudstack-documentation] sureshanaparti commented on a change in pull request #225: Networking update and config drive

[GitBox]

sureshanaparti commented on a change in pull request #225:
URL: 
https://github.com/apache/cloudstack-documentation/pull/225#discussion_r662776264



##
File path: source/adminguide/api.rst
##
@@ -87,4 +87,93 @@ is also supported.) For metadata type, use one of the 
following:
 
 -  instance-id. The instance name of the VM
 
+User Data and Meta Data via Config Drive
+
 
+The user-data service on a Shared or L2 Network can be provided through the
+Virtual Router or through an attached iso called the Config drive.

Review comment:
   may be this ^^^ you can keep with heading 'User Data and Meta Data', and 
sub-heading 'via Virtual Router' and 'via Config Drive'




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] sureshanaparti commented on a change in pull request #225: Networking update and config drive

[GitBox]

sureshanaparti commented on a change in pull request #225:
URL: 
https://github.com/apache/cloudstack-documentation/pull/225#discussion_r662776264



##
File path: source/adminguide/api.rst
##
@@ -87,4 +87,93 @@ is also supported.) For metadata type, use one of the 
following:
 
 -  instance-id. The instance name of the VM
 
+User Data and Meta Data via Config Drive
+
 
+The user-data service on a Shared or L2 Network can be provided through the
+Virtual Router or through an attached iso called the Config drive.

Review comment:
   may be this ^^^ you can keep with heading 'User Data and Meta Data', and 
sub-headings 'via Virtual Router' and 'via Config Drive'




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] sureshanaparti commented on a change in pull request #225: Networking update and config drive

[GitBox]

sureshanaparti commented on a change in pull request #225:
URL: 
https://github.com/apache/cloudstack-documentation/pull/225#discussion_r662781872



##
File path: source/adminguide/api.rst
##
@@ -87,4 +87,93 @@ is also supported.) For metadata type, use one of the 
following:
 
 -  instance-id. The instance name of the VM
 
+User Data and Meta Data via Config Drive
+
 
+The user-data service on a Shared or L2 Network can be provided through the
+Virtual Router or through an attached iso called the Config drive.
+
+Config drive is an ISO file that is mounted as a cd-rom on a user VM and
+contains the user VM related userdata, metadata (incl. ssh-keys) and
+password files.
+
+Enable config drive
+~~~
+To use the config drive the network offering must have the “ConfigDrive”
+provider selected for the userdata service.
+
+If the networkoffering uses ConfigDrive for userdata and the template is
+password enabled, the password string for the VM is placed in the
+vm_password.txt file and it is included in the ISO.
+
+ConfigDrive availability
+
+At VM start the config drive ISO is attached on the 2nd cd/dvd drive of the
+user instance, such that any other ISO image (e.g. boot image or vmware tools)
+is mounted on 1st cd/dvd drive. This means existing functionality of
+supporting 1 cd rom drive is still available.
+
+At Password reset or update of user data, Secondary Storage VM will rebuild the
+ConfigDrive ISO image. That is the existing ISO is mounted on a temporary 
directory,
+password, userdata or ssh-keys are updated and a new ISO is built from the
+updated directory structure.
+
+In case of a password reset, the new password will be picked-up at VM start.
+To access the updated userdata, the user needs to remount the config drive ISO.
+
+When a VM is stopped, the ConfigDrive network element will trigger the
+Secondary Storage VM to remove the ISO from the secondary storage.
+
+Since the ISO is available on secondary storage, there is no need for an extra
+implementation in case of migration.

Review comment:
   @Spaceman1984 can you check the setting 
"vm.configdrive.primarypool.enabled", and see if it can be updated here. When 
this setting is enabled, config drive is hosted from primary storage (for KVM 
hypervisor).




-- 
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