| 2010-08-13 20:06:05 |
Gustavo Niemeyer |
bug |
|
|
added bug |
| 2010-08-13 20:08:30 |
Gustavo Niemeyer |
ensemble: status |
New |
Confirmed |
|
| 2010-08-13 20:08:38 |
Gustavo Niemeyer |
ensemble: importance |
Undecided |
Medium |
|
| 2010-08-13 20:20:39 |
Gustavo Niemeyer |
description |
The Service Unit Agent (SUA) is the part of the Ensemble puzzle responsible for actually dealing with the needs of integrating an individual formula in the Ensemble space. The SUA starts its life when being fired by the Machine Agent, as defined in bug #617042.
The Machine Agent must provide the agent with the needed details for it to run: the $ENSEMBLE_ZOOKEEPER_HOSTS and $ENSEMBLE_MACHINE_ID environment variable must be in place so that the base agent class (bug #614508) will work correctly. In addition to these basic settings, it will also need to be told its service id, through the $ENSEMBLE_SERVICE_UNIT_ID environment variable, so that it knows its own identity. The fact that this latter setting is an environment variable (rather than a command line argument) makes it easier for tools fired by the SUA to work properly in the same context as well.
Once the SUA is alive, it should notify Ensemble of this fact by calling the ServiceUnitState.connect_agent() method (bug #617541).
This is the scope for this bug. Once that foundational mechanism is in place, the SUA should start to handle the formula it was asked to manage. This follow up task is covered in bug #XXXXXX. |
The Service Unit Agent (SUA) is the part of the Ensemble puzzle responsible for actually dealing with the needs of integrating an individual formula in the Ensemble space. The SUA starts its life when being fired by the Machine Agent, as defined in bug #617042.
The Machine Agent must provide the agent with the needed details for it to run: the $ENSEMBLE_ZOOKEEPER_HOSTS and $ENSEMBLE_MACHINE_ID environment variable must be in place so that the base agent class (bug #614508) will work correctly. In addition to these basic settings, it will also need to be told its service id, through the $ENSEMBLE_SERVICE_UNIT_ID environment variable, so that it knows its own identity. The fact that this latter setting is an environment variable (rather than a command line argument) makes it easier for tools fired by the SUA to work properly in the same context as well.
Once the SUA is alive, it should notify Ensemble of this fact by calling the ServiceUnitState.connect_agent() method (bug #617541).
This is the scope for this bug. Once that foundational mechanism is in place, the SUA should start to handle the formula it was asked to manage. This follow up task is covered in bug #617581. |
|
| 2010-08-13 20:33:55 |
Gustavo Niemeyer |
description |
The Service Unit Agent (SUA) is the part of the Ensemble puzzle responsible for actually dealing with the needs of integrating an individual formula in the Ensemble space. The SUA starts its life when being fired by the Machine Agent, as defined in bug #617042.
The Machine Agent must provide the agent with the needed details for it to run: the $ENSEMBLE_ZOOKEEPER_HOSTS and $ENSEMBLE_MACHINE_ID environment variable must be in place so that the base agent class (bug #614508) will work correctly. In addition to these basic settings, it will also need to be told its service id, through the $ENSEMBLE_SERVICE_UNIT_ID environment variable, so that it knows its own identity. The fact that this latter setting is an environment variable (rather than a command line argument) makes it easier for tools fired by the SUA to work properly in the same context as well.
Once the SUA is alive, it should notify Ensemble of this fact by calling the ServiceUnitState.connect_agent() method (bug #617541).
This is the scope for this bug. Once that foundational mechanism is in place, the SUA should start to handle the formula it was asked to manage. This follow up task is covered in bug #617581. |
The Service Unit Agent (SUA) is the part of the Ensemble puzzle responsible for actually dealing with the needs of integrating an individual formula in the Ensemble space. The SUA starts its life when being fired by the Machine Agent, as defined in bug #617042.
The Machine Agent must provide the agent with the needed details for it to run: the $ENSEMBLE_ZOOKEEPER_HOSTS and $ENSEMBLE_MACHINE_ID environment variable must be in place so that the base agent class (bug #614508) will work correctly. In addition to these basic settings, it will also need to be told its service id, through the $ENSEMBLE_SERVICE_UNIT_ID environment variable, so that it knows its own identity. The fact that this latter setting is an environment variable (rather than a command line argument) makes it easier for tools fired by the SUA to work properly in the same context as well.
Once the SUA is alive, it should notify Ensemble of this fact by calling the ServiceUnitState.connect_agent() method (bug #617541).
This is the scope for this bug. Once that foundational mechanism is in place, the SUA should start to handle the formula it was asked to manage. This follow up task is covered in bug #617581.
|
|
| 2010-08-25 19:28:20 |
Kapil Thangavelu |
ensemble: milestone |
|
0.1 |
|
| 2010-10-27 19:25:09 |
Kapil Thangavelu |
ensemble: assignee |
|
Kapil Thangavelu (hazmat) |
|
| 2010-10-27 19:34:58 |
Kapil Thangavelu |
ensemble: milestone |
0.1 |
0.3 |
|
| 2010-12-03 18:53:00 |
Kapil Thangavelu |
ensemble: status |
Confirmed |
In Progress |
|
| 2010-12-17 17:55:43 |
Kapil Thangavelu |
branch linked |
|
lp:~hazmat/ensemble/unit-agent |
|
| 2010-12-23 23:45:56 |
Kapil Thangavelu |
ensemble: status |
In Progress |
Fix Committed |
|
| 2010-12-24 00:06:26 |
Kapil Thangavelu |
ensemble: status |
Fix Committed |
Fix Released |
|
