On 05/27/2011 02:41 PM, Carl Trieloff wrote:
First we agreed that the dirty bit and marking that an instance has been
updated by some our other management API via conductor (Aeolus) would
remain unchanged.
We also agreed that the main goal is to notify the user of the status of
an instance, and that actions results from this status for the near term
would be user actions.
The states that we need to indicate on any given image are:
- unmanaged
- managed by (list ) and whether that management agent has mutated the
content. (example of list can be JON, Kattello, Opsware etc)
- build from artefacts, for example a JOES, i.e. if you start another
instance you will get what is current in the content source repositories.
Carl.
_______________________________________________
aeolus-devel mailing list
aeolus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel From a Katello perspective,
we will require the following in order to
provide information on instance drift:
1. The image package-profile (I think this was referred to as ICICLE).
2. The instance be registered to Katello; leveraging the katello-client
for package-profile updates.
-Todd