You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/03/23 19:09:16 UTC

[jira] [Updated] (CLOUDSTACK-450) Controlling System VMs should not happen through SSH

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasanna Santhanam updated CLOUDSTACK-450:
------------------------------------------

    Fix Version/s: Future
    
> Controlling System VMs should not happen through SSH
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-450
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-450
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Wido den Hollander
>             Fix For: Future
>
>
> Currently we SSH into the System VMs to control them.
> This is not doable on the longer run, it causes problems already, like injecting the SSH keys into the System VM ISO which is not reliable.
> Inside the System VM there should be an API running which the management server(s) can talk to to inject DHCP entries, add loadbalancing settings to HA proxy, have the SSVM download a template/ISO, etc, etc.
> This would mean a complete rewrite of the System VMs, but it will make them more robust over time.
> The exact spec for this improvement still has to be written, this issue is just here to identify the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira