IBM Cloud Foundry – Deprecation of Runtime Management Utility (RMU)
5 min read
What is RMU?
The RMU provides dump and dynamic tracing capability to diagnose problems with Cloud Foundry applications when it is in a running state. It only supports applications pushed with IBM Liberty for Java and IBM SDK for Node.js buildpacks.
Why Deprecate RMU
The current design of RMU is based on the Cloud Foundry DEA architecture. Also, the RMU client and server provide a management channel over HTTP so that dump and trace can be done without the SSH capability. IBM Cloud Foundry has fully migrated to the Diego architecture which has SSH enabled. Most of the functions RMU now provides, can be done by simply using SSH to connect into the application instance container and examine the runtime directly.
The replacement solution leverages the SSH capability in the Cloud Foundry Diego architecture to log into the application container. This is done by using the cf command line ‘cf ssh’, for generating dump and change trace/log settings. The solution is documented here.
Please note the replacement solution does not provide the following that RMU has today:
Web GUI. This should be fine given that most of the developers are using CF CLI / Bluemix CLI to manage their applications.
Set Node.js log level on the fly. The developer needs to implement this in his/her application – i.e. loading log configuration periodically from file to pick up a new log level configuration when the application is running. There are quite a few Node.js logging modules that Node.js developers are using, so this capability is redundant to those options.
February 26th – stop updating RMU in Public / Dedicated / Local environments
March 26th – remove RMU function from console in public regions
April 9th – start to remove RMU function in dedicated/local environments – scheduled with each customer