Cloud User Shell 1.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Cloud User Shell 1.0 (Default branch)
# 1  
Old 08-28-2008
Cloud User Shell 1.0 (Default branch)

Image Cloud User Shell (cush) is a multi-call executable bringing RESTful cloud control to the command line, combining many useful cloud computing utilities into a single executable. It follows the Unix philosophy of writing components that work together, do one thing and do it well, and communicate over text (HTTP) streams. It is also RESTful, clearly delineating the 3 sides of the REST Triangle: verbs (e.g. GET), nouns (e.g. http://samj.net/), and content types (e.g. text/html). Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Change default shell of a specific user with awk

I would like to replicate the functionality of chsh (or passwd -e) by awk. This is what I got so far, but I think there should be an easier way to search and replace field $7 only for lines beginning with user_name: awk -v user_name="$user_name" -v new_shell="$new_shell" -F: '$1 == user_name {... (2 Replies)
Discussion started by: nomad84
2 Replies

2. UNIX for Dummies Questions & Answers

default shell for the user

for example, if we specify,#!/usr/bin/ksh then the script will be executed in korn shell. If we don't specify that line, the script will be executed using the default shell. So, how we can identify the default shell for the current user? Will it be in .profile file ? Thanks (13 Replies)
Discussion started by: pandeesh
13 Replies

3. UNIX for Dummies Questions & Answers

FTP user default shell defunct

Hello, I have a problem with my FTP users. I have create the ftp user on my AIX server, I set the default shell /bin/false or /usr/bin/false. Its enough that the user can logon via FTP. But when I try the user for example via ssh, the shell session is not killed, the session is defunct... (4 Replies)
Discussion started by: kalaso
4 Replies

4. UNIX for Dummies Questions & Answers

How to change Default Shell for any user?

Hi, I am new for solaris... how can we change default shell for any user and how to check that which shall currently we are in...... (1 Reply)
Discussion started by: lalit21984
1 Replies

5. Shell Programming and Scripting

root user command in shell script execute as normal user

Hi All I have written one shell script for GPRS route add is given below named GPRSRouteSet.sh URL="www.google.com" VBURL="10.5.2.211" echo "Setting route for $URL for GPRS" URL_Address=`nslookup $URL|grep Address:|grep -v "#"|awk -F " " '{print $2}'|head -1` echo "Executing ... (3 Replies)
Discussion started by: mnmonu
3 Replies

6. Shell Programming and Scripting

How do i change to super user then revert back to ordinary user ,using shell script?

Hi all, I am trying to eject the cdrom from a livecd after certain stage... Now assuming that it is possible to eject,please consider my issue!!! The OS boots into a regular user by default...so i am unable to use the eject command to push out the drive... However if i try pfexec eject it... (3 Replies)
Discussion started by: wrapster
3 Replies

7. Virtualization and Cloud Computing

Event Cloud Computing - IBM Turning Data Centers Into ?Computing Cloud?

Tim Bass Thu, 15 Nov 2007 23:55:07 +0000 *I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
Discussion started by: Linux Bot
0 Replies
Login or Register to Ask a Question
CPANPLUS::Shell::Default::Plugins::HOWTO(3)		User Contributed Perl Documentation	       CPANPLUS::Shell::Default::Plugins::HOWTO(3)

NAME
CPANPLUS::Shell::Default::Plugins::HOWTO -- documentation on how to write your own plugins SYNOPSIS
package CPANPLUS::Shell::Default::Plugins::MyPlugin; ### return command => method mapping sub plugins { ( myplugin1 => 'mp1', myplugin2 => 'mp2' ) } ### method called when the command '/myplugin1' is issued sub mp1 { .... } ### method called when the command '/? myplugin1' is issued sub mp1_help { return "Help Text" } DESCRIPTION
This pod text explains how to write your own plugins for "CPANPLUS::Shell::Default". HOWTO
Registering Plugin Modules Plugins are detected by using "Module::Pluggable". Every module in the "CPANPLUS::Shell::Default::Plugins::*" namespace is considered a plugin, and is attempted to be loaded. Therefor, any plugin must be declared in that namespace, in a corresponding ".pm" file. Registering Plugin Commands To register any plugin commands, a list of key value pairs must be returned by a "plugins" method in your package. The keys are the commands you wish to register, the values are the methods in the plugin package you wish to have called when the command is issued. For example, a simple 'Hello, World!' plugin: package CPANPLUS::Shell::Default::Plugins::HW; sub plugins { return ( helloworld => 'hw' ) }; sub hw { print "Hello, world! " } When the user in the default shell now issues the "/helloworld" command, this command will be dispatched to the plugin, and its "hw" method will be called Registering Plugin Help To provide usage information for your plugin, the user of the default shell can type "/? PLUGIN_COMMAND". In that case, the function "PLUGIN_COMMAND_help" will be called in your plugin package. For example, extending the above example, when a user calls "/? helloworld", the function "hw_help" will be called, which might look like this: sub hw_help { " /helloworld # prints "Hello, world! " } If you don't provide a corresponding _help function to your commands, the default shell will handle it gracefully, but the user will be stuck without usage information on your commands, so it's considered undesirable to omit the help functions. Arguments to Plugin Commands Any plugin function will receive the following arguments when called, which are all positional: Classname -- The name of your plugin class Shell -- The CPANPLUS::Shell::Default object Backend -- The CPANPLUS::Backend object Command -- The command issued by the user Input -- The input string from the user Options -- A hashref of options provided by the user For example, the following command: /helloworld bob --nofoo --bar=2 joe Would yield the following arguments: sub hw { my $class = shift; # CPANPLUS::Shell::Default::Plugins::HW my $shell = shift; # CPANPLUS::Shell::Default object my $cb = shift; # CPANPLUS::Backend object my $cmd = shift; # 'helloworld' my $input = shift; # 'bob joe' my $opts = shift; # { foo => 0, bar => 2 } .... } BUG REPORTS
Please report bugs or other issues to <bug-cpanplus@rt.cpan.org<gt>. AUTHOR
This module by Jos Boumans <kane@cpan.org>. COPYRIGHT
The CPAN++ interface (of which this module is a part of) is copyright (c) 2001 - 2007, Jos Boumans <kane@cpan.org>. All rights reserved. This library is free software; you may redistribute and/or modify it under the same terms as Perl itself. SEE ALSO
CPANPLUS::Shell::Default, CPANPLUS::Shell, cpanp perl v5.16.3 2013-05-20 CPANPLUS::Shell::Default::Plugins::HOWTO(3)