BOTH:
* Document how to clean partition and pvremove stuffs
* Fail error codes that correspond to error messages in help
* Create wiki site for README and other docs
* Create survey/feedback page we can use as a placeholder, this url will go in the app.  We can put us_clusters@dell.com or whatever email there for now, change it as more options (survey) become available

FE:

Next Release:
* (sev2) NFS client options validation
* (sev1) figure out ip/hostname status, and/or allow a hostname instead of just ip
* (sev3) change detail to default if debug
* (sev3) confirm password column for nodes
* (sev3) create install.log with output of everything
* (sev2) drac ips need to be checked against node ips... right now dupes are allowed between the 2 lists.
* (sev3) change frontend to trace return code of add_nodes
* (sev3) username prompt for ipmi/drac, or remove password field from ipmi/drac entry and use the cluster password
* (sev3) Color progress bar red or something
* (sev3) Buttons on the summary page to allow edit back to that item's page, set the forward button to return to the summary page instead of the next sequential page
* (sev3) Add power switch fencing properly
* (sev3) help references/tooltip
* (sev3) increment ips based on first entry
* (sev3) it would be nice if there was a config file option that would cause the front end to prepopulate with data from a config file to simply data entry for testing.
* (sev3) change getopt code to not execute when defining the class but pull it out in a function like in BE


BE:
* (sev2) for phase 1, if back/forward, need to call something on BE to blow away cluster.conf (like reset_nodes), which we can later use for --reconfigure that I always wanted
* (sev2) do not reboot on phase2 for equallogic
* (sev2) find VENDOR with scsi_id -x and report back to FE
* (sev3) use scsi_id -x 
* (sev2) unique error for "no storage found" instead of currently it says "storage could not be matched across nodes"

Next Release:
* (sev1) have debug log call status_cb to write to it
* (sev1) add firmware repo to node functions:
http://linux.dell.com/repo/firmware/
wget -q -O - http://linux.dell.com/repo/firmware/bootstrap.cgi | bash

* (sev1) figure out ip/hostname status, and/or allow a hostname instead of just ip
* (sev1) need to insatll SMcli and other MD3000/MD3000i rpms for nodes.  These are on the MD3000/i cd, but probably need to be in the software repo. (if you run the install.sh, it creates /tmp/install.dir.XXXX.  Look in there for InstallerData/Disk1/InsData and get Resource1.zip.  If you unzip that, you see $BASE_DIR$/Resources/Platforms/LINUX/ in this dir are SMruntime.rpm, SMclient.rpm, SMutil.rpm, SMagent.rpm.  These need to be installed on all the clients, and probably put in the Dell software repo.  Check /var/ftp/pub/md_extracted_rpms/ on the mgmt server for the rpms.
* (sev1) virt application creation, nothing working, probably what we want anyway?
* (sev1) set hostname if does not match
* (sev3) set hostnames according to input
* (sev2) timeout on length of reboots
* (sev3) ping app ip to see if it does not exist
* (sev3)Add as many callback status calls as possible to pulse the bar
* (sev3) add "reconfigure"
* (sev3) change long processes like yum update to do a pulse instead of progress fraction, and tail -f something like /var/log/yum.log into status details
* (sev3) validate nfs client options
