Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cm shell #16

Open
laszewsk opened this issue Mar 9, 2013 · 1 comment
Open

cm shell #16

laszewsk opened this issue Mar 9, 2013 · 1 comment

Comments

@laszewsk
Copy link
Member

laszewsk commented Mar 9, 2013

after you finish the eucalyptus class probably over the weekend, I like you to focus on the development of a new

command line shell bare bones system. All functions will just print "TODO: TO BE IMPLEMENTED"

However you should make sure that the parsing and option handling is done right.

the basic commands are in https://github.com/futuregrid/flask_cm/blob/master/cloudmesh/cm_shell.py

Please do not actually use that class and implement it as command line we want to implement this as a CMD

there are two classes in python that do this that are very easy to use and well documented.

http://docs.python.org/2/library/cmd.html

http://pythonhosted.org/cmd2/index.html

I suggest you start with just plain CMD

http://pymotw.com/2/cmd/index.html

when you pass arguments you may have to use variable number of arguments and you can use argparse for parsing them.

all you have to do is to great functions that start with do_

If you have any questions on this, please contact fugang he is very well knowledgable about this. Please remind him that you will start just using CMD an not CMD2.

When writing the default values, they will be pickled in ~/.futuregird/shell.dat

If someone gets done with their tasks early they can pick up and help shweta on this easy but very fun task.
Fugang will next week add a couple of more "simple" commands for the usage of rain, image generation and other things we have done in the past. However instead of using the same names that Javier used, he will introduce more logical names, such as "list resources" (e.g. with spaces).

Once Shweta finishes eucalyptus pushkar will integrate that into flask. This way shweta can focus on this one and pushcart can do the graphical portion of cloud mesh

@ghost ghost assigned sbpatil Mar 9, 2013
@ghost ghost assigned ppnewaskar May 14, 2013
@laszewsk
Copy link
Member Author

reassigned. I reduced the requirements, so it will be doubtful that this task will be done by Pushkar. However this task could have significantly simplified the management of the flask server while leveraging the CAU model discussed by Gregor at the beginning of the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants