On Tue, 7 Jun 2005 13:43:13 +0100 (BST)
[log in to unmask] wrote:
> Hi Owen,
>
> > pragmatic I have to complete my work on a new configuration
> > management system before you guys see the benefit.
>
> I don't want to be discouraging but I don't want any parallel
> management tool. Can your management tool be integrated in YAIM? If
> not why?
I agree and do intend to use YAIM as one of the front ends to this work.
This is more to separate out the configuration provided by YAIM and the
configuration provided by the d-cache developers.
The driving motivations are in two area's first and foremost reducing
our effort in supporting deployment over the foreseeable life time of
D-cache and secondarily contributing real benefit back to D-cache in a
way that I and now Jiri are better qualified than the D-Cache
development team.
What I see of the configuration of D-Cache is similar to the edg-se,
where some people described our initial configuration files as the
internal configuration database, and demanded a clear separation between
values that don't need changing and values that do need changing. YAIM
provides this for you guys but the code absorbed from D-cache is not up
to the standard of the rest of YAIM.
This process will clean up some of the sed modifications to d-cache
configuration values that seem to have acquired the level of complexity
that makes maintaining and extensibility difficult. This is the current
situation.
Using a similar approach to the last version of the EDG-SE of a
configuration directory that is parsed and applied can provide you with
an RPM that can be used parallel to YAIM or as a configuration option
that will switch d-cache behaviour to say set a set of properties for a
tier 2 site, and another that sets a set of properties for the tier 1,
while you as an end user just select a configuration profile.
So to summarise what I am proposing is a clear separation and easy to
maintain layer beneath YAIM from your perspective, with the ability to
drop in configuration profiles as an add on benefit. Its just standard
computer engineering of making yet another layer of abstraction and
customisation to simplify and reduce complexity.
Regards
Owen
|