Rapyuta

We are happy to announce the availability of the pre-built Public AMI for Rapyuta. All you need to do is log in with your EC2 credentials and fire up a pre-built, maintained and tested instance. That way you can have your very own engine running in less than a couple of minutes, sans the effort involved in setting up, configuring and testing a new installation. You can get straight to what you wan to do, get cracking, testing, using and contributing to the project.

It is quite simple to get up and running and just a matter of a few clicks.

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
2. Select the Zone as EU-West/ Ireland in the top right corner. We currently offer this, we may extend to other zones in the future.
3. Start a Classic Launch Instance Wizard
4. In the choose an AMI options select “Community AMIs”
5. In the search box type in 'rapyuta' (Latest AMI ID 'ami-ef48569b', Alpha2 AMI ID : 'ami-e79f8e93')

The result will show up listing all available instances of Rapyuta Alpha 2 (Currently Only available in the EU-West/Ireland Zone)

1. Select the Number of Instances (You could choose micro to qualify for the free tire if eligible, however if you intend to perform compute intensive/ multiple parallel tasks it would perhaps be better to choose a larger instance type according to your needs), Instance Type, Zone Preference (If you happen to have any), hit continue.
2. Optional : Add User Data, Kernel, RAM Disk ID and other options, we recommend keeping the defaults.
3. Optional : Storage Configuration, again recommend defaults.
4. Optional : Add some value to the Name tag, this will just help you identify the instance through out the console. ec2 tools.
5. Important : Choose one of your valid key pairs, if you skip this text, you will not be able to login!
6. If this is the first time you are using Rapytua, you will not have an appropriate firewall and will need to configure a new security group. Select : Create a New Security Group at this stage. Firewall Configuration
7. Review and your setup and hit Launch

* Group Name* : Some unique name eg: 'Rapyuta' * Group Description : Some description eg: 'My rapyuta config' * Create the following TCP Rules for the cloud engine to work. (based on defaults, may need tweaking if you decide to modify the ports in the setting file)

1. 'Port Range' : 22 'Source' : 0.0.0.0/0 [SSH]
2. 'Port Range' : 8081 'Source' : 0.0.0.0/0 [Console Client]
3. 'Port Range' : 9000 'Source' : 0.0.0.0/0 [Robot HTTP Connect]
4. 'Port Range' : 9010 'Source' : 0.0.0.0/0 [Robot Web-socket Connect]
5. 'Port Range' : 9020 'Source' : 0.0.0.0/0 [Console ROS Proxy Port]
6. 'Port Range' : 8080 'Source' : 10.0.0.0/8 [Internal HTTP Connect Port]
7. 'Port Range' : 10030 'Source' : 10.0.0.0/8 [Internal Web-socket Communication]
8. 'Port Range' : 8800-8900 'Source' : 10.0.0.0/8 [Variable Internal Container]

For general usage refer to usage.

DEVELOPER MODE IS ENABLED BY DEFAULT ON THE PUBLIC AMI

• Host Ubuntu Release : Ubuntu 12.04 LTS
• Host ROS Release : Groovy
• Container Ubuntu Release : Ubuntu 12.04 LTS
• Container ROS Release : Groovy

Sample file available at Sample Settings

• The config file is located at ~/.rce/config.ini. Can also be recreated using ./provision config.
• The credentials are auto created and used in developer mode and located at ~/.rce/creds. Can also be recreated using ./provision cred. Note: Depends on settinsg in the config file)

The following are the defaults.

 username    : password
 admin       : admin
 adminInfra  : adminInfra
 testUser    : testUser

The default config file mounts all the contents of ~/packages into the container filesystem ROS_PACKAGE_PATH (/opt/rce/packages)

1. Place your packages in ~/packages
2. Start the container environment system

   sudo rce-make

3. Rosmake any packages you require

   rosmake <example_package>

4. Install any depends inside this environment using standard apt-get procedures as it's usually done on Ubuntu
5. Exit the environment

   exit

Use as usual