GitHub user rashmidixit opened a pull request:

    https://github.com/apache/cloudstack/pull/1889

    CLOUDSTACK-9718: Revamp the dropdown showing lists of hosts available for 
migration in a Zone

    Refer to 
[CLOUDSTACK-9718](https://issues.apache.org/jira/browse/CLOUDSTACK-9718) for 
more details.
    
    Problem: All the hosts suitable for VM Migration are not shown in the UI. 
This could
    confuse the user as the target host might never be shown in the UI.
    
    Root Cause: The API (findHostsForMigration) always returned page 1 results 
which would
    be always <= default.page.size global parameter. Therefore, in case of large
    no. of hosts where the result can map to multiple pages, this issue would 
arise.
    
    Solution: 1. Replace drop-down with listView widget.
    2. Allow lazy-loading of records on listView's scroll.
    3. Show additional parameters (CPU/Memory used) to assist admin in decision 
making.
    4. Provide 'Search by host name' to limit the results.
    
    Conflicts:
        client/WEB-INF/classes/resources/messages.properties
        client/WEB-INF/classes/resources/messages_ja_JP.properties
        client/WEB-INF/classes/resources/messages_zh_CN.properties
        ui/css/cloudstack3.css
        ui/dictionary2.jsp

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9718

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1889.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1889
    
----
commit dfb595bdfebc38ae1561584030e62c40cdbd46a5
Author: radhika grover <radhika_gro...@accelerite.com>
Date:   2016-05-06T12:57:41Z

    CLOUDSTACK-9718: Revamp the dropdown showing lists of hosts available for 
migration in a Zone
    
    Reviewed-By: Rashmi Dixit
    
    Problem: All the hosts suitable for VM Migration are not shown in the UI. 
This could
    confuse the user as the target host might never be shown in the UI.
    
    Root Cause: The API (findHostsForMigration) always returned page 1 results 
which would
    be always <= default.page.size global parameter. Therefore, in case of large
    no. of hosts where the result can map to multiple pages, this issue would 
arise.
    
    Solution: 1. Replace drop-down with listView widget.
    2. Allow lazy-loading of records on listView's scroll.
    3. Show additional parameters (CPU/Memory used) to assist admin in decision 
making.
    4. Provide 'Search by host name' to limit the results.
    
    Conflicts:
        client/WEB-INF/classes/resources/messages.properties
        client/WEB-INF/classes/resources/messages_ja_JP.properties
        client/WEB-INF/classes/resources/messages_zh_CN.properties
        ui/css/cloudstack3.css
        ui/dictionary2.jsp

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to