Here's some of the commands the client would have. I had a look at osc
and the Studio API in coming up with this. Let me know what you think.
Templates:
template list
Appliances:
appliance list
appliance status <id>
appliance create [--clone_from=appliance_name --arch=x86_64/i686]
[name] # Creates a local directory with a manifest that stores
apppliance id and other changes that have been made locally and not
committed
appliance delete <id>
Repositories:
repository list
On Tuesday 22 March 2011 14:19:27 Ratan Sebastian wrote:
I'd like to work on the improvement of the Suse Studio command line client(ssc) idea for GSOC this year. I've gone through the current ssc code but found no documentation on it. Is there someone here I can talk to who has worked on it and would know what is lacking. It would help me formulate a detailed project proposal.
You can find more information here: http://en.opensuse.org/openSUSE:SUSE_Studio_command_line_client
You can also join us on IRC in the #susestudio channel, or use the mailing list studio-users@suse.de to reach the team and the community.
As I see it I'd first write a wrapper for the suse studio api(http://susestudio.com/help/api/v1) and a command like client to use the wrapper. It would be a good idea to separate the two so that the wrapper can be used programatically as well.
There already is a library to access the Studio API at https://github.com/jreidinger/studio_api.
-- Cornelius Schumacher
-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-- Ratan Sebastian -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org