Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 7 Feb 2017 22:01:41 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13016689.1477937903000.21692.1486504901706@Atlassian.JIRA>
In-Reply-To: <JIRA.13016689.1477937903000@Atlassian.JIRA>
References: <JIRA.13016689.1477937903000@Atlassian.JIRA> <JIRA.13016689.1477937903679@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9574) Redesign storage views
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Feb 2017 22:01:58 -0000


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

ASF GitHub Bot commented on CLOUDSTACK-9574:
--------------------------------------------

Github user rafaelweingartner commented on the issue:

    https://github.com/apache/cloudstack/pull/1747
  
    @nvazquez, @serg38, before checking code any deeper a have a more high-level question.
    
    This PR will change the response of an API method, right? It will remove some data that today is being delivered to users. 
    
    If I understood it properly, this data (storage tags) will be delivered/retrieved using another method. This may break compatibility with current clients that may use this information. If so, this break in compatibility has to be properly documented. Do you guys know how we could do this? Is there a protocol for this? Some alert on the release notes? Or maybe something on documentation pages?


> Redesign storage views
> ----------------------
>
>                 Key: CLOUDSTACK-9574
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, UI
>            Reporter: Nicolas Vazquez
>            Assignee: Nicolas Vazquez
>         Attachments: PS-DETAILS.PNG, PS.PNG
>
>
> h2. Part 1: Redesign storage tags
> h3. Actual behavior
> Primary storage tags are being saved as an entry on {{storage_pool_details}} with:
> * name = TAG_NAME
> * value = "true"
> When a boolean property is defined in {{storage_pool_details}} and has value = "true", it is displayed as a tag.
> !https://issues.apache.org/jira/secure/attachment/12836196/PS-DETAILS.PNG!
> !https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG!
> h3. Goal
> Redesign {{Storage Tags}} for Primary Storage view, to list only tags, as it is done in Host Tags (Hosts view).
> h2. Part 2: Remove details from listImageStores API call response and UI
> h3. Description
> In Secondary Storage view we propose removing Details field, as Setting tab list details for a given image store. We also remove details from response on listImageStores API method


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)