As a part of April 4 NDS workshop demo story board.
- Background
A tool: a Clowder extractor, or a Polyglot software server. - Where data are – MongoDB.
In each checking iteration, the elasticity module writes the following info into MongoDB, along with the timestamp:- for each queue: the queue name, number of messages published/delivered, consumer IP, number of instances on each consumer IP (in 'extr');
- for each cloud VM: VM name, IP, status, status to transition to if any (in 'cloud_vm');
- for each VM running tools: IP, number of CPUs, load average (in 'vm_info'); the tools running on it (in 'vm2ets');
- the elasticity actions taken: add/remove tool instances, suspend/resume VMs, start VMs, ...
- Interaction with the elasticity module
- Currently the above data are written into MongoDB, so the program for the monitoring page can directly connect to MongoDB to get and display the info. So, for READ-ONLY features, this page can reside anywhere.
- However, currently we are implementing deploy/stop tool features in Tool Catalog, using RabbitMQ queues to communicate between Tool Catalog and Elasticity Module.
If we want to add editing features into the monitoring page, or on the same site where the monitoring page is, we need to consider it together with TC/EM integration.
- Options:
- Tool Catalog (likely with Scala, JavaScript).
- Brown Dog machine or other web sites, using any language: PHP, JavaScript, ...
- Others?
- Your suggestions/comments are much appreciated!