You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Marcus Sorensen (JIRA)" <ji...@apache.org> on 2012/11/07 16:39:13 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13492433#comment-13492433 ] 

Marcus Sorensen commented on CLOUDSTACK-450:
--------------------------------------------

Could it be done in stages? For example, API on system vm first (which for now just calls the existing shell scripts as-is), then move all of the code out of the agent into the server.  

Also, wouldn't we still need to inject a key or shared secret for the API to authenticate us? 

Should we create a list of things that this buys us so we know it's worth the effort?  I can think of two things at the moment. Controlling system VMs would become platform agnostic for most things, if not all. We currently have to have a Xen version of setting static NAT and a KVM version of it for example, since it relies on the host capabilities. The other thing is just cleaner code/implementation in not calling shell scripts.

Is there a reason why this wasn't done in the first place? Do these functions need to stay with the agent for example, or is it simply more secure to not be able to directly touch a system VM remotely?
                
> 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
>          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: http://www.atlassian.com/software/jira