SSH in Stackato

A “run” command for Cloud Foundry

Cloud Foundry lacks support for running arbitrary commands. Being able to run arbitrary commands is essential when processing data outside of the web application request-response cycle. “run” is essential to perform tasks like Django’s admin user creation (and changing its password) or populating a database from a Twitter stream.

Stackato’s old “run” command

Since the first release of Stackato, we included a basic “stackato run” command to do this. As it made HTTP calls to the Cloud Controller and then to the DEA, it was somewhat limited and unreliable. Interaction was not possible and long running scripts would be killed off by the various timeouts in the HTTP stack.

LXC makes “run” secure and easy

Once we added support for LXC, it made no sense to continue using the old “run” implementation, so we added full SSH support for deployed applications. As applications are isolated by LXC – meaning, they run in their virtual Linux instance – running “stackato ssh app-name” is equivalent to SSH’ing to your application container, and you have full sudo rights. Things like sudo apt-get install libfoo-dev1 become possible. Indeed, the recently added requirements feature allows installation of arbitrary system packages through this mechanism.

“stackato run” is now an alias for “stackato ssh”.

When is “run” useful?

Examples

Here are a few sample applications that make use of the new “run” command, based on SSH:

<!–

–>

Trackback URL for this post:

http://www.activestate.com/trackback/3323

Written by admin on February 29th, 2012 with no comments.
Read more articles on browser.

« Older articles

Newer articles »