| Issue 39: | GUI framework for OHSM 1.0.0 | |
| 2 people starred this issue and may be notified of changes. | Back to list |
Enter description here
Jan 25, 2009
Firstly Sneha, You dont need to cc anyone, all the members of the fscops group get the notifications by default. Here are the comments, 1. Rotate the FScops logo by 90 degrees, clockwise. The font for "OHSM" looks quite ok to me. 2. Replace "any thing can be written here " by "End User License Agreement" followed by the open source EULA. Google for it. 3. Your 5th image should be your third image and It will have the following options. 1. Deifne teirs ---- > click will take to your image 3 and Image 4. 2. Allocation Policy --> should take you to image 6. 3. Relocation Plicy ---> Take you to image 7. 4. Create LVM --> New Page 3. 5. Define Mount Point ----> New page 1. 6. Other Options ---> New page 2 . New Page 1 Will have the following: You will accept the mount point. And ok clicking OK, It will display all the information about the device and the mountpoint. ( for OHSM 1.0 you can have a dummy page displayed) The new page 2 will have the following options. 1. Generate XML file 2. Conflicts 3. Display XML file 4. Edit XML file. New page 3 It will display all the devices in the LVM ( which will be the list of devices accpeted in the previous pages ), if No devices have been enetered ( tiers not defined) you can display an error and ask the user to Define tiers first. 4. Image 4 and 6 look good to me and shold go ahead with that. 5. Image 7 needs a change. Remove all the columns from that image. And display the information in the text box itself. Something like: Source Tier : Destination Tier : File Access Age : <rel_op> <value> // Example : <= 7 FIle Size : <value> ... .. ... ... In the last part replace FileAccessage - > File Access Age FileModificationage -> File Modification Age. Let me know if you have some queries. You can go ahead with the following changes for NOW. Keep updating the status through issues.
Status:
In-progress
Cc: -fscops -sandeepksinha -sneha.hendre -postrishi -rohitvashist2kk3 -imreckless -checkout.vineet Labels: Component-UI Milestone-Release1.0
Jan 25, 2009
>>Ok for first 2 points 3. Your 5th image should be your third image and It will have the following options. 1. Deifne teirs ---- > click will take to your image 3 and Image 4. 2. Allocation Policy --> should take you to image 6. 3. Relocation Plicy ---> Take you to image 7. 4. Create LVM --> New Page 3. 5. Define Mount Point ----> New page 1. 6. Other Options ---> New page 2 . New Page 1 Will have the following: You will accept the mount point. And ok clicking OK, It will display all the information about the device and the mountpoint. ( for OHSM 1.0 you can have a dummy page displayed) The new page 2 will have the following options. 1. Generate XML file 2. Conflicts 3. Display XML file 4. Edit XML file. >>This will be done sir New page 3 It will display all the devices in the LVM ( which will be the list of devices accpeted in the previous pages ), if No devices have been enetered ( tiers not defined) you can display an error and ask the user to Define tiers first. >>The list of devices that the user will enter >>will be present in the list >>so if the list is empty then it will not proceed further >>i.e. when apply button is cliked it will not display the success message >>it will be validated here itself. >>after defining tiers and creating LVM only >>user can set allocation and relocation policies >>So for that purpose I have made two separate windows >>I forgot to add the next button in image3 >>that will be enabled only after defining tier. >>I will add the button in image3 for accepting mount point >>and further it will open a new page as said for this. >>what say for this 4. Image 4 and 6 look good to me and shold go ahead with that. 5. Image 7 needs a change. Remove all the columns from that image. And display the information in the text box itself. Something like: Source Tier : Destination Tier : File Access Age : <rel_op> <value> // Example : <= 7 FIle Size : <value> >>do you mean to say a single rich text box >>or separate for every one ... ..
Jan 25, 2009
Also user cannot enter wrong devices as it will be selected from non editable drop down list Also when the user will add the device or user or group it will be removed from the drop down list And if he again removes it from list it will be again added to the drop down list. so validation for devices,UID,GID will be finished here.
Jan 25, 2009
i want a single simple text ou can box. I agree with all others ur points. go ahead with coding.
Jan 25, 2009
>>The list of devices that the user will enter >>will be present in the list >>so if the list is empty then it will not proceed further >>i.e. when apply button is cliked it will not display the success message >>it will be validated here itself. Do you mean to say that the validation for devices should be done here itslef. Then thats fine. >>after defining tiers and creating LVM only >>user can set allocation and relocation policies That fine. But the options in the main menu. See, whenever you defining tier is successful, you can simply set one flag. And similarly when lvm is created. Now, whenever user clicks on alloc and reloc policy, check if these two flags are set, if not then you can throw an error. >>So for that purpose I have made two separate windows >>I forgot to add the next button in image3 >>that will be enabled only after defining tier. >>I will add the button in image3 for accepting mount point >>and further it will open a new page as said for this. Yes thats right. >>what say for this I am ok with this. >>do you mean to say a single rich text box >>or separate for every one ... .. I simply want it displayed in a non-changeble text box. Use should not be able to modify it manually.
Summary:
GUI framework for OHSM 1.0.0
Jan 25, 2009
There will be one problem in having non editable text box user will not be able to delete any rule if has mistakenly added wrong policy since the text is non editable. He will have to clear whole text and again start from first. :(
Jan 25, 2009
This is EULA for FScops's OHSM any suggestions anything should be added or removed???? A SOURCE CODE VERSION OF OHSM (Online Hierarchical Storage Management) FUNCTIONALITY THAT YOU MAY USE, MODIFY AND DISTRIBUTE IS AVAILABLE TO YOU FREE-OF-CHARGE FROM https://code.google.com/p/fscops/source/list UNDER THE FScops PUBLIC LICENSE and other open source software licenses. The accompanying executable code version of OHSM and related documentation (the "Product") is made available to you under the terms of this FScops OHSM END-USER SOFTWARE LICENSE AGREEMENT (THE "AGREEMENT").BY CLICKING THE "ACCEPT" BUTTON, OR BY INSTALLING OR USING THE FScops OHSM YOU ARE CONSENTING TO BE BOUND BY THE AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT CLICK THE "ACCEPT" BUTTON, AND DO NOT INSTALL OR USE ANY PART OF THE FScops OHSM. 1. LICENSE GRANT: The FScops grants you a non-exclusive license to use the executable code version of the Product. This Agreement will also govern any software upgrades provided by FScops that replace and/or supplement the original Product, unless such upgrades are accompanied by a separate license, in which case the terms of that license will govern. 2. TERMINATION: If you breach this Agreement your right to use the Product will terminate immediately and without notice, but all provisions of this Agreement except the License Grant (Paragraph 1) will survive termination and continue in effect. Upon termination, you must destroy all copies of the Product. 3. PROPRIETARY RIGHTS: Portions of the Product are available in source code form under the terms of the FScops Public License and other open source licenses (collectively, "Open Source Licenses") at https://code.google.com/p/fscops Nothing in this Agreement will be construed to limit any rights granted under the Open Source Licenses. Subject to the foregoing, FScops, for itself and on behalf of its licensors, hereby reserves all intellectual property rights in the Product, except for the rights expressly granted in this Agreement. You may not remove or alter any trademark, logo, copyright or other proprietary notice in or on the Product. This license does not grant you any right to use the trademarks, service marks or logos of FScops or its licensors. 4. DISCLAIMER OF WARRANTY: THE PRODUCT IS PROVIDED "AS IS" WITH ALL FAULTS. TO THE EXTENT PERMITTED BY LAW, FScops AND FScops's DISTRIBUTORS, LICENSORS HEREBY DISCLAIM ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES THAT THE PRODUCT IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE AND NON-INFRINGING. YOU BEAR ENTIRE RISK AS TO SELECTING THE PRODUCT FOR YOUR PURPOSES AND AS TO THE QUALITY AND PERFORMANCE OF THE PRODUCT. THIS LIMITATION WILL APPLY NOT WITH STANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY REMEDY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES, SO THIS DISCLAIMER MAY NOT APPLY TO YOU. 5. LIMITATION OF LIABILITY: EXCEPT AS REQUIRED BY LAW, FScops AND ITS DISTRIBUTORS, DIRECTORS, LICENSORS, CONTRIBUTORS AND AGENTS (COLLECTIVELY, THE "FScops GROUP") WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES ARISING OUT OF OR IN ANY WAY RELATING TO THIS AGREEMENT OR THE USE OF OR INABILITY TO USE THE PRODUCT, INCLUDING WITHOUT LIMITATION DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, LOST PROFITS, LOSS OF DATA, AND COMPUTER FAILURE OR MALFUNCTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND REGARDLESS OF THE THEORY (CONTRACT, TORT OR OTHERWISE) UPON WHICH SUCH CLAIM IS BASED. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL, CONSEQUENTIAL OR SPECIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. 6. EXPORT CONTROLS: This license is subject to all applicable export restrictions. You must comply with all export and import laws and restrictions and regulations of any United States or foreign agency or authority relating to the Product and its use. 8. MISCELLANEOUS: (a) This Agreement constitutes the entire agreement between FScops and you concerning the subject matter hereof, and it may only be modified by a written amendment signed by an authorized executive of FScops. (b) Except to the extent applicable law, if any, provides otherwise, this Agreement will be governed by the laws of the state of California, U.S.A., excluding its conflict of law provisions. (c) This Agreement will not be governed by the United Nations Convention on Contracts for the International Sale of Goods. (d) If any part of this Agreement is held invalid or unenforceable, that part will be construed to reflect the parties' original intent, and the remaining portions will remain in full force and effect. (e) A waiver by either party of any term or condition of this Agreement or any breach thereof, in any one instance, will not waive such term or condition or any subsequent breach thereof. (f) Except as required by law, the controlling language of this Agreement is English. (g) You may assign your rights under this Agreement to any party that consents to, and agrees to be bound by, its terms; the FScops may assign its rights under this Agreement without condition. (h) This Agreement will be binding upon and will inure to the benefit of the parties, their successors and permitted assigns.
Jan 25, 2009
New Screen shots as per the modifications
Jan 25, 2009
Looks absolutely fantastic. It would be nice you finish off with the "other options" as well. Also, test you code for displaying devices and uid, gid, etc....
Jan 26, 2009
I have finished the other options part.... I started with the coding ... finished half of the coding ..... For a trial I made an executable .... And now all the images from executable are disappeared :( Lost in finding the images.... I have not at all touched to the images while coding .... Will soon find out them :(
Jan 26, 2009
The Problem is solved now the images are appearing in the executable.... Displayed it with another function as the function used by glade was deprecated...
Jan 29, 2009
Here is the GUI for 1.0 1) Open glade software. 2) Make a new project. 3) New GTK project. 3) Save the project. 4) Click on build. 5) In terminal go to the directory where project is stored. 6) ./autogen.sh 7) Extract the attached folder. 8) copy all the file to the src folder that is created in directory of the saved project. 9) again in terminal goto src directory i.e cd src 10)make 11)./ (whatever the the executable created).
Jan 29, 2009
To be done in the file It is just a working model of GUI 1) All the functions in interface.c will be moved to callbacks.c As it is a standard file for those functions. 2) In relocation policy window the text is to be displayed. I need just few minutes for that. (The policy file at the back is built) just have to display those values. 3) The window for viewing the LV's is to be done. as I will have to go to wadi for that where the system is not available for that purpose. :) 4) And finally the Remove and Clear buttons functionality. 5) RV providing you with the list of devices part is also remaining I will do it as I get the script. This is just a working model and enhancement part is remaining.
Jan 29, 2009
Here are a couple of comments. 1. The OHSM Acknowledgement should be in justify text, and should fix in the width of the windows. We don't want to scroll to right side. 2. Why are we taking the mount point ??? It should only be taken when the user wants to apply the Policies. Remove it from that page. 3. If the Mountpoint is not provided, you should be able to go back. Add a back button along with the cancel button. 4. While adding tiers, after filling dev as "/dev/sda5" and tier as "teir1", when I click add. these fields should be displayed in the window. it is getting displayed. But at the same time, the selection list should be blank. as it was initially. the name still remains on the selection box. Remove that. 5. Why the first 2 lines of this window empty ? When we add , i can see some lines empty there ? Remove it. 6. Why new windows are opening everytime I say next ? Either hide the old ones or remove them when somebody says next. 7. Why the option of view LV is there when you are defining tiers ? Its all messed up sneha.... Its pathetic... I am really pissed off with all these... can you show me your design doc ? As to what was planned and what you are making?
Jan 30, 2009
Currently the GUI is on hold as sneha is working on the validation of xml policy files entered by the user while enabling OHSM
Status:
On-Hold
Feb 1, 2009
The validation coding is over . The logs will be added soon. The gui is now started and rishi is working with sneha on this
Status:
In-progress
Labels: -Priority-High Priority-Critical
Feb 1, 2009
This is still at medium priority. I am not worried about this. Remember Rishi, most servers doesn't have GUI. So, better concentrate on other stuffs like testing the code well and for various cases. Focus more on testing your code and optimizing the relocation time as it delays and hits performance.
Feb 2, 2009
Sneha is not working fully into this I want it to be done ASAP I am working in parser
Labels:
-Priority-Critical Priority-High
Feb 2, 2009
Well, good attitude but we need to be stable. I would only allow this code to go if its 200% stable. Also, put everyone to work on code cleanup and optimization of their individual modules.
Feb 2, 2009
Rishi.... Status, if you working on this ???
Feb 3, 2009
The individual modules are almost clean only a lot of debug messages are there in my code. I am using #ifdef and #endif for it as i need the debug messages. Is it bad and not according to standards ??
Feb 3, 2009
GUI is still not ready due to some problems.......sneha will update soon
Feb 3, 2009
Thats absolutely acceptable but the better way would have been something like this: #ifdef DEBUG ohsm_printk(x,y) printk(x,y) else ohsm_printk(x) /* */ #endif This will make it look more cleaner. You can do this later as well. Its not an issue.
Feb 7, 2009
GUI have become pathetic I am going to go mad now ..... The code working in one function is not working in another function ..... same compiled code run for 1st time gives no bugs and 2nd time it give bugs with out changing the code ??? :( * ~ >; " ? # ^ confused a lot....
Feb 8, 2009
I am not able to find the bug. I am stuck not getting any thing ....... I need some one :(
Feb 9, 2009
Hey I got the error ...... There was some problem with GTK function :P
Feb 20, 2009
Hi, These are the snapshots of the GUI....
Feb 20, 2009
Sorry forgot to attach the file here it is...
Feb 20, 2009
Some more validation part is also there but I think this is enough .... Validation like: for devices, rules, policies etc.
Feb 20, 2009
Elaborate the types of validation which are left according to you We will try to do all the things that are possible
Feb 20, 2009
No its done Not there in the snapshots ....
Feb 20, 2009
Triggering relocation form has an error will be rectified in the final design.
Feb 20, 2009
The error is its taking only one rule for now and the option for having multiple rules is to be added.
Feb 26, 2009
Sneha is currently making the final design on paper. The job will be done by 28th Feb Evening
Labels:
-Priority-High Priority-Critical
Mar 6, 2009
Can I have a update from sneha on this issue.
Mar 7, 2009
Why I am not seein any update on this? Rishi ???????????
Mar 8, 2009
GUI is ready only integration with CLI is left, copying the GUI files to ohsm directory will do the job. GUI cannot display specific type of errors, that would require support from CLI. For eg: if the specified mount point or LV name is incorrect then CLI pukes an error in console, but GUI is not aware of these errors as CLI does not return specific error values. So there has to be some sort of interface that GUI can use to get the specific type of error that has occurred.
Mar 12, 2009
Sneha and Vineet did some work in GUI. But there is a problem. The problem is : to enable OHSM we need to run the command "ohsm -e -a -i.................." using system command wether the command has worked properly can be checked only by the return value of the system command. But system command is not returning the value we want to return. The man page also does not clear this thing. So possible solutions are : Solution 1: writing the whole code of getopt.c in the GUI functions. That will solve this issue completely BUT while parsing there are chances of errors in XML files. There are two types of errors. Type 1 is the errors which the parser libxml catches like DTD mismatch etc. Type 2 is the errors which we catch like tier number is greater than 10 etc. So type 2 errors can be shown using a text box and a show details button while we dont have any method to show the type 1 error ( as per now) So sneha is trying to show the type 1 errors also. If we could not do that then we will leave the type 1 errors and will show only type 1 errors as we are falling short of time. Solution 2: Find a solution to the system command. BUT Now the errors will have to be redirected to a temp file which will be shown when the user presses the show details button.
Mar 12, 2009
Yes Rishi is right but again the problem is there in coping the code of getopt.c to GUI code because there will be a conflict between the makefile of GUI generated code and OHSM makefile (am I right vineet this will also be the case then please correct me I am wrong here).
Mar 14, 2009
Can Sneha please update the issue ?? What work has been done in last two days. Sneha should note that the deadline for this work is 16th March as We want to show this in Roorkee also. If any problem then kindly let us know ? And do this before the deadline expires
Mar 14, 2009
GUI is ready , only work left is to get return values from CLI VA can you please provide a solution for getting return values from CLI RV can u provide me the script that will have logical volume name also ... when it will be done ..
Mar 14, 2009
Hi every one, I think system commands do return values of exit status. I have verified and tested it. for exit(1) i got a return value 256 and for exit(2), i got 512. VA , Rishi and RV do you have any clue why we are not getting return values from CLI, have u tried using 'exit(status)'. Merging the code of getopt.c might create problem in GUI i suppose, may be some compilation issue as sneha has mentioned.
Mar 14, 2009
I dont think there will be any problem if you merge the code. It will be better if this is checked by Sneha.
Mar 15, 2009
GUI is complete finally I was able to display the messages ... As we have ppt tomorrow I am now preparing for that. The testing of GUI will be done tomorrow. RV please bring your laptop to college tomorrow. I have my practical off from 10 to 12 I will be doing GUI in college tomorrow ...
Mar 19, 2009
Hi Sneha, kindly update the issue with your status?
Mar 20, 2009
Here is a GUI working fine.
Requirements for it is ohsm should be patched in the kernel.
I have my kernel patched with 1.0.
And GUI is working fine there.
Its a compiled code.
Better if you do ./ohsm1 in konsole.
Execution details:
1) Extract the files.
2) ohsm1 -> src
there will be a file ohsm1
3) Click it(./ohsm1 for command line).
4) Create the logical volume & Tier device file
NOTE : Activate Logical volume before enabling OHSM.
5) Create the allocation policy file.
6) Create the relocation policy file.
7) enable OHSM / Disable OHSM / Trigger Relocation.
Basic functionality is being provided by GUI.
It will be improved more further after 27th.
Apr 24, 2009
Thus we have finally made a working GUI, closing the issue
Status:
Fixed
|
636 KB Download
535 KB Download
653 KB Download
623 KB Download
695 KB Download
683 KB Download
1.5 MB Download
Labels: Priority-High