incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wido den Hollander (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-450) Controlling System VMs should not happen through SSH
Date Thu, 08 Nov 2012 08:28:12 GMT


Wido den Hollander commented on CLOUDSTACK-450:

Yes, I think we should build the API first indeed and do it in steps.

This issue is also a "brain dump" about what has to be done.

It's clear I think that the System VMs need some work, since the current way we do stuff is
not maintainable.

The main point for the API is indeed to make it platform agnostic. We still need to figure
out a way to inject a shared secret and set the network configuration for the System VM since
DHCP is not available for them.
> Controlling System VMs should not happen through SSH
> ----------------------------------------------------
>                 Key: CLOUDSTACK-450
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>          Components: Management Server
>            Reporter: Wido den Hollander
> 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:

View raw message