Reference Information › User Interface Reference Guide › Graphical User Interface › Application Configuration › Resources

Resources

The Resources tab allows you to control the amount of resources the application requires and is allowed to use.

By default, CA AppLogic® calculates the resource range of the application based on the resource ranges of all appliances used in the application.

If you don't want to constrain the application further or simply don't know yet what constraints you want, leave the default settings. This clears all constraints.

There are two ways to constrain the amount of resources to be allocated to the application:

• By number of servers
• By resource range

In addition, you can select a subset of servers in the system where the application can be scheduled. Such constraints allow you to specialize this particular instance of the application for production and sandbox (testing) environments.

CA AppLogic® determines the actual amount of resources to be given to an application when you start the application. Whatever resources are available or specified when starting the application must fit within the range you define.

Note:

• You can set the exact amount of resources to be used when starting the application by specifying the maximum values equal to the minimum. This ensures that:
  • No freedom will be given to the scheduler
  • The application will not start unless at least that amount of resources are available
  • The application will take no more than that amount of resources.
• In the Resource tab, you can only reduce the resource range by specifying a higher minimum or lower maximum for resources.

The Resources contains the following information and configurable fields:

• Limit the resource range - Constrain by Resources--Specify the resource range for each hardware resource separately.
  • CPU - Specify the portion of CPU or number of CPUs to be allocated for the application. Fractional amounts can be specified as a decimal number, such as 0.5 or 3.5). Whole CPUs are specified simply as an integer, such as 12.
  • Memory - Specify the amount of memory to be allocated for the application. The amount can be specified as an integer value in Megabytes (for example, 512M) or in Gigabytes (for example, 9G).
  • Bandwidth - Specify the amount of network bandwidth to be allocated for this application. The amount can be specified as an integer value in Megabits/sec, such as 10M or in Gigabits/sec, such as 1G.

Oversubscription

As an administrator, you can enable the oversubscription of network bandwidth on a grid for the backbone or internal network. If enabled, appliances can use more bandwidth than their configured network bandwidth.

If disabled, the maximum network bandwidth for each appliance is based on its configured network bandwidth . When the appliance closely approaches the configured bandwidth, network packets are randomly dropped for that appliance. As long as the used appliance bandwidth exceeds the configured bandwidth, all network packets are dropped for that appliance.

The enabled state of the resource oversubscription for bandwidth is displays on the dashboard. For additional information on setting oversubscription, refer to the Command Line Shell Reference Guide,

Setting Resource Ranges

A range can be specified for each resource type. The range defines the normal operating parameters desired for the application in production environment.

• Minimum - The minimum amount of a resource that the application needs to work at all. This is useful to allow running the application in functional testing environments, where the application is not expected to run under production load, and therefore can run with much less resources. Contrast this with the Default below, which is amount of resources needed for production use.
• Maximum- The maximum amount of a resource that the application will be allowed to take. Typically this is the maximum that the application can use.For example, giving it more resources will not increase performance. The application will not be allocated more than the specified maximum amount. This ensures that it will not be able to take resources away from other applications -- think of it as a quota.
• Default - The minimum amount of a resource that the application should be provided with for normal operation in production environments. The application will not start unless at least that much resource can be allocated. Specifying a default helps ensure that the application will work within certain guaranteed resource amount -- think of it as a service level agreement (SLA) for that resource.

  Note: You can easily see which values override the defaults -- they are displayed in bold. If you want to restore the default value for a resource, click the restore icon next to the value.

• Limit the set of servers - Constrain by Server Names
  • You can also select the specify servers where you would like the application to run.
  • To locate your list of servers, execute the server list shell command.
  • If the specified server does not having enough resources, the application starts on other servers, provided there are available resources. A log message displays in the dashboard.
  • This is an advanced option that may be useful when you want to run several applications on the same system and the results produced by the scheduler are not satisfactory. In most cases you should leave this constraint disabled.