Menu

#21 GUI for OHSM

OHSMv1.2
open
3
2010-01-10
2009-09-26
No

Graphical interface for OHSM. Below is the layout proposed by manish. I have extended a bit of it.

How about having a layout as simple as below. The "Action" tab is a clickable
hyperlink which is like toggle.

Main screen :-

---------------------------------------------------------------------------------------------------------------------------
| Radio btn | Mount point | FS | Logical volume | Status | Action |
---------------------------------------------------------------------------------------------------------------------------
| O | /mnt | ext4 | /dev/vg0/lv1 | Enabled | Disable |
| O | /vol1 | ext4 | /dev/vg4/lvol | Disabled | Enable |
| O | /vol2 | ext4 | /dev/vg0/lv3 | Enabled | Disable |
| O | /vol3 | ext4 | /dev/vg1/lv0 | Disabled | Enable |
----------------------------------------------------------------------------------------------------------------------------
| Add Instance ... | Edit Instance ... | Details .. | Relocate | Reserved |
----------------------------------------------------------------------------------------------------------------------------
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
----------------------------------------------------------------------------------------------------------------------------

Data types for each of them and a bit of functional flow.

1. Only one of the radio buttons can be selected at a time.
2. The selection through radio button will be used for option like edit instance, relocate, status etc..
3. Mountpoint, Logical Volume, status, FS should be plain text.
4. Action will be a toggle button. Any click on it should flip the status field as well.
5. If none raidio button selected and someone clicks on edit instance, relocate etc, throw an error.
6. If someone clinks on disable(inorder to re-enable), pop a window and accept the path to policy file.
7. Similarly, when someone clinks on add instance, in the empty box display "text boxes" to accept the mountpoint and path_to_policy_file.
8. If someone clicks on edit instance, use the empty box below to display a choice, "allocation policy" or "relocation policy". Which ever is selected, accept the relevant file_path_to policy.
9. If someone clicks on relocate, give him the choice,
all or selective,
if selective accept the rule no.
10. If someone clicks on details, display all the information in struct ohsm_instance.

This is enough to start your coding with. We have "policy file generator" in plan along with ability to display tier specific information (like free block, num of relocate blocks, used blocks etc).

Discussion

  • Sandeepksinha

    Sandeepksinha - 2010-01-01
    • milestone: --> 1024815
    • priority: 5 --> 3
    • assigned_to: imreckless --> patilrahul
    • summary: GUI for OHSMv1.1 --> GUI for OHSM
     
  • Sandeepksinha

    Sandeepksinha - 2010-01-01

    Rahul is working on this... Hence changing the owner.

     
  • Sandeepksinha

    Sandeepksinha - 2010-01-10

    Changing owner to sanket as he is working on the GUI....
    All further communication pertaining GUI development must happen here....

    This is a must have for v1.2 mow....

     
  • Sandeepksinha

    Sandeepksinha - 2010-01-10
    • milestone: 1024815 --> OHSMv1.2
    • assigned_to: patilrahul --> teknas
     

Log in to post a comment.