You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kris Sterckx (JIRA)" <ji...@apache.org> on 2017/09/03 22:38:02 UTC

[jira] [Comment Edited] (CLOUDSTACK-9813) Use configdrive for userdata, metadata & password

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150687#comment-16150687 ] 

Kris Sterckx edited comment on CLOUDSTACK-9813 at 9/3/17 10:37 PM:
-------------------------------------------------------------------

Hi [~serverchief][~mlsorensen][~widodh]

Pls refer to [CopyingISOtoPrimaryStorage|https://cwiki.apache.org/confluence/display/CLOUDSTACK/Using+ConfigDrive+for+Metadata%2C+Userdata+and+Password#UsingConfigDriveforMetadata,UserdataandPassword-CopyingISOtoPrimaryStorage] for the proposed approach of copying the iso to primary storage after generation on secondary storage (when available).

At this stage the design assumes the iso staying on the secondary storage (i.e. we are *copying*, not *moving*) for easier support of VM migration and other scenario's, without need for orchestrating copy operations from A to B to C and so-forth (in casu of VM migration, primary to secondary + secondary to primary).  We understand it is potentially an increment towards where we want to be eventually, but it lowers initial complexity and effort.

I would like also to call out that at Nuage we are no storage experts and also don't have all the infrastructure to test all the possible permutations (e.g. to start with, as we have no customers using XenServer, we don't have such infrastructure at hand in our lab). I would like to make the call for setting up a multi-disciplinary virtual team to finish off this Feature.  We can discuss this more in the dev call on Wednesday.

All upfront feedback welcome.
cheers,
Kris


was (Author: krissterckx):
Hi [~serverchief][~mlsorensen][~widodh]

Pls refer to https://cwiki.apache.org/confluence/display/CLOUDSTACK/Using+ConfigDrive+for+Metadata%2C+Userdata+and+Password#UsingConfigDriveforMetadata,UserdataandPassword-CopyingISOtoPrimaryStorage for the proposed approach of copying the iso to primary storage after generation on secondary storage (when available).

At this stage the design assumes the iso staying on the secondary storage (i.e. we are *copying*, not *moving*) for easier support of VM migration and other scenario's, without need for orchestrating copy operations from A to B to C and so-forth (in casu of VM migration, primary to secondary + secondary to primary).  We understand it is potentially an increment towards where we want to be eventually, but it lowers initial complexity and effort.

I would like also to call out that at Nuage we are no storage experts and also don't have all the infrastructure to test all the possible permutations (e.g. to start with, as we have no customers using XenServer, we don't have such infrastructure at hand in our lab). I would like to make the call for setting up a multi-disciplinary virtual team to finish off this Feature.  We can discuss this more in the dev call on Wednesday.

All upfront feedback welcome.
cheers,
Kris

> Use configdrive for userdata, metadata & password 
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-9813
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9813
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM, Network Controller, Secondary Storage, SystemVM, VMware
>    Affects Versions: Future
>            Reporter: Eric Waegeman
>            Assignee: Kris Sterckx
>
> To avoid the use of an extra VM for the virtual router we implement configdrive for userdata, metadata & password. 
> The configdrive ISO is created on the secondary store and the KVM & VMware plugins are adapted to accept the configdrive ISO as second cdrom.
> Is applicable for isolated, VPC and shared networks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)