Rubiscape uses the Celery (execution engine) worker to execute tasks on the server. For example, in AWS, the worker runs on the configured Amazon Elastic Compute Cloud (EC2) instance. Hence, it is also called the “Worker node configuration.”

The Node Configuration

Allows you to select the required instance and instance types with different memory, storage, CPU, and network capacity combinations.
Helps you scale your resources suitably.
Provides control to the user to execute tasks on the server.

Notes:

EC2 is a web service that provides secure and resizable compute capacity in the cloud. It is designed to make cloud computing easier for developers.
It provides you with complete control of your computing resources and lets you run on Amazon’s proven computing environment.

Auto Scaling using Node Configuration

Worker Node Configuration appears with every node, whether it is an algorithm, a functionality, or any other selection from the tool pane of the Rubiscape platform. You can use the drag-and-drop method to use them on the canvas.

To select the required computing environment, you should select the Node Configuration checkbox. The available Fields in Node Configuration are shown in the figure below. The figure shows the default options for Instance Type and Instance for AWS.

The table below describes the different fields present on the Fields of Node Configuration.

Field	Description	Remark
Instance Type	It allows you to select the type of Instance based on the server on which the Rubiscape platform is deployed.	Currently, the Rubiscape platform is deployed on the following servers. AWS Microsoft Azure At the time of deployment, the server is known. Depending on the server type, the list of Instance Types available is given below. AWS: General Purpose Compute Optimized Memory Optimized Microsoft Azure: D Series E Series F Series G Series H Series Ls Series M Series
Instance	It allows you to select a specific instance corresponding to the instance type chosen.	It gives you a choice to change the Instance according to compute required for executing a particular task. For example, for heavy compute requirements, you can select higher version instances in Compute Optimized or Memory Optimized Instance Types. The list of Instances depends upon the selected Instance Type. It changes according to the Instance Type.
Queue Name	It allows you to enter a queue name to a task.	The given queue name can be used while deploying many tasks on the server. For example, you want to execute several tasks from a database on a specific Celery (or worker) with a particular queue name. If you enter the queue name in the dedicated box, the tasks get executed on that Celery (or worker). Note: Currently, the entered value of queue name is not employed at the time of execution. The functionality shall be available soon in the future releases.

Note:

Auto scaling can be enabled/disabled at the time of deployment itself. The user can use Node Configurations only when the auto scaling option is enabled.
If auto scaling is enabled and the user does not select the node configuration, then the default instance type and instance selected by the Administrator are used for the execution of the task.

Table of Contents