[
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482323#comment-16482323
]
ASF subversion and git services commented on CLOUDSTACK-10290:
--------------------------------------------------------------
Commit acc5fdcdbd613bedfcd0ca867123e2cd3ba8d5c6 in cloudstack's branch
refs/heads/master from [~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=acc5fdc ]
CLOUDSTACK-10290: allow config drives on primary storage for KVM (#2651)
This introduces a new global setting `vm.configdrive.primarypool.enabled` to
toggle creation/hosting of config drive iso files on primary storage, the
default will be false causing them to be hosted on secondary storage. The
current support is limited from hypervisor resource side and in current
implementation limited to `KVM` only. The next big change is that config drive
is created at a temporary location by management server and shipped to either
KVM or SSVM agent via cmd-answer pattern, the data of which is not logged in
logs. This saves us from adding genisoimage dependency on cloudstack-agent pkg.
The APIs to reset ssh public key, password and user-data (via update VM API)
requires that VM should be shutdown. Therefore, in the refactoring I removed
the case of updation of existing ISO. If there are objections I'll re-put the
strategy to detach+attach new config iso as a way of updation. In the
refactored implementation, the folder name is changed to lower-cased
configdrive. And during VM start, migration or shutdown/removal if primary
storage is enable for use, the KVM agent will handle cleanup tasks otherwise
SSVM agent will handle them.
Signed-off-by: Rohit Yadav <[email protected]>
> Config drive - only supported for secondary storage
> ---------------------------------------------------
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.11.0.0
> Reporter: Rohit Yadav
> Assignee: Daan Hoogland
> Priority: Major
>
> Userdata disk looks like this:
> <disk type='file' device='cdrom'>
> <driver name='qemu' type='raw' cache='none'/>
> <source
> file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
> <backingStore/>
> <target dev='hdd' bus='ide'/>
> <readonly/>
> <alias name='ide0-1-1'/>
> <address type='drive' controller='0' bus='1' target='0' unit='1'/>
> </disk>
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
> Filesystem 1K-blocks
> Used Available Use% Mounted on
> some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM 66391040 2973696
> 63417344 5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>
> issue: where to find a primary storage for a VM that is not yet deployed. The
> configdrive is created before a storage is assigned. This order of execution
> must be reversed for this to work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
