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

Mike Tutkowski resolved CLOUDSTACK-6045.
----------------------------------------

    Resolution: Fixed

Seif has completed this work.

> [GSoC] Create GUI to add primary storage based on plug-ins
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-6045
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6045
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: UI
>    Affects Versions: 4.4.0
>         Environment: All browsers that CloudStack supports
>            Reporter: Mike Tutkowski
>            Assignee: Seif Eddine Jemli
>              Labels: gsoc, gsoc2014
>             Fix For: 4.4.0
>
>
> At the time being, if an admin wants to add primary storage to CloudStack 
> that is NOT based on the default storage plug-in, the admin must invoke the 
> addStoragePool API outside of the CloudStack GUI.
> It would be beneficial to CloudStack admins if they could add this kind of 
> primary storage to CloudStack via its standard GUI.
> This project will require a degree of usability work in that the designer 
> must analyze CloudStack's GUI sufficiently to come up with a plan for where 
> the necessary information can be input.
> Once a GUI prototype has been developed (one could use a tool like PowerPoint 
> for this purpose), then the developer must analyze the necessary HTML and 
> JavaScript logic to add the proposed support.
> This project could take the form of an optional GUI plug-in.
> It is possible this project may add one or more parameters to the 
> addStoragePool API. If so, then this will require Java changes on the backend.
> It is likely the developer will have to create a new CloudStack API: One to 
> retrieve the list of installed storage plug-ins.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to