cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wido den Hollander (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-450) Controlling System VMs should not happen through SSH
Date Mon, 06 Feb 2017 12:26:41 GMT

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

Wido den Hollander closed CLOUDSTACK-450.
-----------------------------------------
    Resolution: Fixed

No longer valid since we use a local socket to the SSVM.

> 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
>    Affects Versions: pre-4.0.0, 4.0.0, 4.1.0, 4.2.0
>            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 was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message