cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Maximus (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9813) Use configdrive for userdata, metadata & password
Date Mon, 24 Jul 2017 16:07:00 GMT


Frank Maximus commented on CLOUDSTACK-9813:

One of the reasons why we chose to use secondary storage, was that we then could use the ssvm
to do the generation of the iso on a hypervisor agnostic way.
Otherwise for VMware the generation would have to happen on the management server, as there
is no agent.
And that would also require an rpm/deb dependency to genisoimage in management server.

In the implementation on the PR, generation the iso is offloaded, in the same way as downloading
images from the internet.
It is based upon the work of [~jayapal]. 

I acknowledge the issues with the approach we took,
but would have preferred this kind of feedback 4 months ago, 
when we posted the design document.

> Use configdrive for userdata, metadata & password 
> --------------------------------------------------
>                 Key: CLOUDSTACK-9813
>                 URL:
>             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

View raw message