You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rohit Vavaldas (JIRA)" <ji...@apache.org> on 2018/02/16 17:07:00 UTC

[jira] [Commented] (CLOUDSTACK-10262) create an API driven System VM upgrade posibility

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-10262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367593#comment-16367593 ] 

Rohit Vavaldas commented on CLOUDSTACK-10262:
---------------------------------------------

Hi [~dahn], I would like to work on this issue as part of GSOC2018. 

Can you give specific details on what the API should do, I understand that the current flow of updating system VM template is to first register newer version of system VM template using registertemplate API and then invoke preparetemplate on the above registered template. So as part of this, you like to call a single API that would do the functionality of both these APIs.

> create an API driven System VM upgrade posibility
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-10262
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10262
>             Project: CloudStack
>          Issue Type: Wish
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Daan Hoogland
>            Priority: Major
>              Labels: gsoc2018
>
> As a cloud admin I want a single call API to upgrade/upload a new System VM template. The System VM template upgrade procedure is now largely manual and error prone. An one ring to bind them all API call to replace the current template for system VMs would help cloud admins world wide.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)