[
https://issues.apache.org/jira/browse/CLOUDSTACK-9777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873654#comment-15873654
]
Rohit Yadav commented on CLOUDSTACK-9777:
-----------------------------------------
Thanks [~rajanik], I've been actually refactoring UI codebase in this regard
though my intentions were not explicit, for example we got the JSP dependency
decoupled and removed. Now UI codebase is actually free to be installed/served
by a separate server, though here are some things we'll need to discuss and
solve in order to achieve this:
- How to decouple CloudStack version specific feature/changes that are required
in the UI, i.e. UI is or may be coupled with what that specific version of
CloudStack has to offer. Without solving for this, it would be hard to move UI
codebase to its separate repo.
- Make all parts of CloudStack UI to use listApis (or API discovery) to show
certain parts (widgets/sections?). This will actually help to dynamically
show/hide parts of the UI based on allowed list of APIs for a user account role
(i.e. make dynamic roles effect the UI).
- Finally fix the packaging system to introduce a cloudstack-ui package that
installs the assets/html/js/css etc
> decouple cloudstack UI
> ----------------------
>
> Key: CLOUDSTACK-9777
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9777
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rajani Karuturi
> Labels: gsoc2017
>
> just like cloudmonkey, decouple cloudstack UI to a separate project.
> It should be able to talk to any cloudstack endpoint
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
