Feature #841
oZones GUI forms should be more user friendly
| Status: | Closed | Start date: | 09/28/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Hector Sanjuan | % Done: | 100% | |
| Category: | - | |||
| Target version: | Release 3.2 - S1 | |||
| Resolution: | fixed | Pull request: |
Description
For instance, form of Zone creation should split the endpoint for ONE_XMLRPC in server and port, and don't bother with RPC2. Also, default values pre filled could be a good idea.
Also, in the VDC template we should have:
- Link to sunstone endpoint (http://ozones-server/subnstone_MyVDC)
- The ONE_XMLRPC variable for the CLI (http://ozones-server/MyVDC) -> to cream it, can be a clickable text field that copies to the clipboard the "export ONE_XMLRPC=http://ozones-server/MyVDC")
Associated revisions
Feature #841: Make oZones more user friedly.
This commit makes the following improvements to the oZones GUI:
- The zone creation dialog has some default values.
- Protocol and /RPC2 tail are added by default to the endpoint data, which has been divided in host and port, with default values.
- Sunstone endpoint field has been divided in protocol,host,port,subdir. Default values provided.
- VDCs extended information contains a link to the Sunstone instance for the specified VDC.
- VDCs extended information contains a selected text field with the value to set ONEXML_RPC, in order to manage the VDC from the CLI.
(cherry picked from commit 55fa96153f7f9c87fb1a2dacb49c00e40f7ccbf9)
History
#1
Updated by Hector Sanjuan over 9 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
- Resolution set to fixed
#2
Updated by Ruben S. Montero over 9 years ago
- Target version changed from Release 3.4 to Release 3.2 - S1