Hi,
You're assuming that whoever owns Radiator servers has a team who operate these
complex CM systems, and are interested in taking responsibility for their
configuration. That's not the case.
I'm interested in a very humble feature that shouldn't require such systems nor
much complexity: being able to import variables from external files/DB. These
can be stored in memory when the Radiator process is loaded.
It would definitely go a long way to allowing an organization to create a
generic Radiator installation, having to change a minimal number of variables
that are server and site specific.
________________________________________
From: radiator-boun...@open.com.au [radiator-boun...@open.com.au] on behalf of
shaun gibson [xcor...@gmail.com]
Sent: Wednesday, June 29, 2016 3:38 PM
To: radiator@open.com.au
Subject: Re: [RADIATOR] Questions regarding new release and current roadmap
On 29/06/2016 13:23, Nadav Hod wrote:
> <snip>
>
> 2.5) I probably wasn't clear enough. The include command isn't what I'm
> looking for since that takes blocks of configuration, not variables, and
> embeds it in the current configuration. It can't be used to extract a
> specific variable within that external file. A header file isn't a
> configuration file which is put into another configuration file, it's just
> variables and declarations.
>
> I've used Radiator 4.15, and I couldn't use external variables as part of
> parameters in order to make a generic configuration. What I'm looking for is
> something like the following: assume I have an AuthBy LDAP2 clause. I would
> like to declare:
>
> Host %{GlobalVar:my_ldap_variables.txt::FirstHost}
>
> In this example my_ldap_variables.txt contains variables bindings for LDAP
> configurations, FirstHost being one of them.
>
> Something like this, as far as I can tell, isn't possible today. I would need
> to have FirstHost configured within the local configuration file.
>
> If I could create a directory on each server that contains files, each of
> which contain variables relevant to that file, it would make things very easy
> and manageable. I could put the same Radiator configuration on each server,
> and just update the variables per server.
>
> Is this possible with Radiator using existing features?
> <snip>
hi nadav
there is no need for radiator to do any of the above as there are
numerous tools/suites for exactly this sort of thing : saltstack,
puppet, ansible, chef et al
_______________________________________________
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
