
| Key: |
RHQ-2
|
| Type: |
New Feature
|
| Status: |
Accepted
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
John Mazzitelli
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Relation
|
|
This issue Relates To:
|
|
RHQ-61
server rejects entire inventory report if agent has unknown plugin
|
|
|
|
|
|
RHQ-1 be able to ignore resource types
|
|
|
|
|
|
This issue Is Related To:
|
|
RHQ-847
error when executing plugins update
|
|
|
|
|
|
|
| Date of First Response: |
02/Dec/08 01:43 PM
|
|
In order to reduce the footprint of the agent at runtime, we want to be able to configure the plugin container to ignore certain plugins. When the agent's plugin container is told to ignore certain plugins, the PC should just not load it, thus reducing the memory footprint of the agent. Reducing the number of types to discover and manage also reduces CPU utilization of the agent.
If the PC is told to ignore a plugin that is a dependency of a unignored plugin, an error should result. You can't disable or ignore plugins that other, unignored, plugins need. The agent startup should fail in this case.
|
|
Description
|
In order to reduce the footprint of the agent at runtime, we want to be able to configure the plugin container to ignore certain plugins. When the agent's plugin container is told to ignore certain plugins, the PC should just not load it, thus reducing the memory footprint of the agent. Reducing the number of types to discover and manage also reduces CPU utilization of the agent.
If the PC is told to ignore a plugin that is a dependency of a unignored plugin, an error should result. You can't disable or ignore plugins that other, unignored, plugins need. The agent startup should fail in this case. |
Show » |
|
I think this will become more important in the future.