HTTPS clone URL
Subversion checkout URL
2.5-patches GH-6 RepoManCase availability_zones backfill bug6908 bug7031 bug7088 bug7101 buzz4-30-10 cachefix copyproxyandhttps cpu-error-message ctx-info-client ctxfiltercontrol details_element docs-2.2 docs-2.3 docs-2.4 docs-2.5 docs-2.6 docs-2.7 docs-2.8 docs-2.9 docs-2.10 docs-2.10.1 fgbuzz1 gateway gsocadmin-merge gsocadmintools hide-scripts idea9.0.2 magellan master maven multiplecpuarchs nodemgmt origin/virga1 pilotlocking tinydocumentationfix virga1 vmreaper
Nothing to show
Nothing to show
Fetching latest commit...
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
Nimbus Context Agent ==================== http://www.nimbusproject.org The context agent is a small program which is meant to be bundled onto VM images. It is invoked on boot by a distribution-specific mechanism (rc.local for example). It retrieves context information in an IaaS-specific way and securely contacts a Nimbus Context Broker. Out of the box, the agent does little more than SSH key exchange but you can customize the ctx-scripts to perform different contextualization tasks. Supported IaaS Providers ------------------------ * Amazon EC2 * Nimbus versions 2.2+ Software Dependencies --------------------- * Python 2.3+ (but not Python 3) * curl command with SSL support Installation ------------ 1. Untar the package and copy the ctx/ and ctx-scripts/ directories to /opt/nimbus/ on your VM image. 2. Add calls to the clean.sh and launch.sh scripts to your system boot process. They should be run at the end of the boot, after network and daemons are running. On many systems, you can edit the /etc/rc.local file and add these calls. An example script is provided at ctx/sample-rc-local-entry.txt 3. Customize the ctx-scripts/ as needed to contextualize your VM. 4. Save/bundle your VM image and then try to boot it via the Nimbus cloud-client with a cluster document (or some other client that supports Nimbus contextualization).