Cisco Cisco Application Extension Platform for SRE

Page of 134
Cisco Application eXtension Platform 1.1 Developer Guide
  Flexible Resource Allocation
106
  Flexible Resource Allocation
'b4b0ee92-cf8e-472b-8434-e8e7412ec71a,all' --source-dir '/xyz-src/build' --disk-limit 
"100M" --memory-limit "128M" --cpu-limit "2000" --memory-wildcard --cpu-wildcard 
--disk-wildcard --postinstall 'bin/post-install.sh' --swap 'ON'
Additional References
Cisco AXP Command Reference
: See the show swap usage command.
: See the “Installation and Upgrade” section for information on the software 
install clean command, software install upgrade command, and the boothelper.
Flexible Resource Allocation
During packaging, flexible resource allocation can be turned on for an application.
Flexible Resource Allocation:
makes it easier to control the hardware's capability to support the application 
grants extra memory, CPU, and disk resources to an application if those resources are available, as 
part of a resource management system
shares unallocated resources between virtual instances (provided the applications in those virtual 
instances have flexible resource allocation turned on)
Note
If you override the resource limits of an application using the Cisco AXP CLI on the application service 
module, then flexible resource allocation no longer allocates additional available resources for this 
application.
The following packaging tool parameters control the main memory, CPU, and disk resources:
--memory-wildcard
--cpu-wildcard 
--disk-wildcard
If you configure the resource limit using the Cisco IOS CLI and use the write memory command and 
reload or reload apps command, resources are reallocated or rebalanced.
Resource allocation occurs after installing an add-on package, upgrading or uninstalling a package, or 
configuring resource limits with the Cisco AXP CLI on the application service module.
Resource Limits Exceeded after Downgrade
The following scenario may occur after downgrading an application on Cisco AXP. When using an 
application version 2 with Cisco AXP host OS 1.1.1, then downgrading to a lower version of Cisco AXP 
host OS (for example, 1.0.6) using version 1 of the same application, the files for version 2 of the 
application may still be present on the application service module. The presence of two versions of the 
application may cause resource limits may be exceeded. For example, the following error messages may 
be displayed when trying to run version 1 of application APP1 on Cisco AXP host OS (1.0.6):
localhost err_handler: invalid parameters: 'space_used' is larger than 'space_total'. 
localhost err_handler: Failed to start vserver 'APP1'.