Hi,
Adds support for host definition by a environment variables of the
following form:
KEYWORDHOST__envX, where X is the number of the environment
for which host referenced by a keyword should be defined.
You can also optionally use KEYWORDHOST__IP_envX to define
the IP address directly,
On 10/22/2013 09:20 AM, Tomas Babej wrote:
Hi,
Adds support for host definition by a environment variables of the
following form:
KEYWORDHOST__envX, where X is the number of the environment
for which host referenced by a keyword should be defined.
You can also optionally use
On 10/22/2013 09:54 AM, Petr Viktorin wrote:
On 10/22/2013 09:20 AM, Tomas Babej wrote:
Hi,
Adds support for host definition by a environment variables of the
following form:
KEYWORDHOST__envX, where X is the number of the environment
for which host referenced by a keyword should be defined.
Replying to one part only:
On 10/21/2013 04:50 PM, Tomas Babej wrote:
On 10/16/2013 03:44 PM, Petr Viktorin wrote:
I still think it would be simpler if IPA and AD domains shared the
numbering namespace (users would need to define $AD_env2; if they had
$MASTER_env1 and $AD_env1 they would be
On 10/22/2013 02:41 AM, Dean Hunter wrote:
This patch is only for the FreeIPA 3.1.5 User Guide. The 3.1.5 User
Guide currently has a procedure carried over from the 2.2 User Guide.
And the procedure will be different, again, for the 3.4 User Guide. The
procedure is based on
On 10/22/2013 10:09 AM, Tomas Babej wrote:
On 10/22/2013 09:54 AM, Petr Viktorin wrote:
On 10/22/2013 09:20 AM, Tomas Babej wrote:
Hi,
Adds support for host definition by a environment variables of the
following form:
KEYWORDHOST__envX, where X is the number of the environment
for which host
On Tue, 2013-10-22 at 10:39 +0200, Martin Kosek wrote:
On 10/22/2013 02:41 AM, Dean Hunter wrote:
This patch is only for the FreeIPA 3.1.5 User Guide. The 3.1.5 User
Guide currently has a procedure carried over from the 2.2 User Guide.
And the procedure will be different, again, for the 3.4
On 10/22/2013 10:37 AM, Petr Viktorin wrote:
Replying to one part only:
On 10/21/2013 04:50 PM, Tomas Babej wrote:
On 10/16/2013 03:44 PM, Petr Viktorin wrote:
I still think it would be simpler if IPA and AD domains shared the
numbering namespace (users would need to define $AD_env2; if they
On Tue, 2013-10-22 at 10:39 +0200, Martin Kosek wrote:
On 10/22/2013 02:41 AM, Dean Hunter wrote:
This patch is only for the FreeIPA 3.1.5 User Guide. The 3.1.5 User
Guide currently has a procedure carried over from the 2.2 User Guide.
And the procedure will be different, again, for the
On 10/22/2013 12:27 PM, Tomas Babej wrote:
On 10/22/2013 10:37 AM, Petr Viktorin wrote:
Replying to one part only:
On 10/21/2013 04:50 PM, Tomas Babej wrote:
On 10/16/2013 03:44 PM, Petr Viktorin wrote:
I still think it would be simpler if IPA and AD domains shared the
numbering namespace
On 10/22/2013 02:15 PM, Tomas Babej wrote:
On 10/22/2013 12:27 PM, Tomas Babej wrote:
On 10/22/2013 10:37 AM, Petr Viktorin wrote:
Replying to one part only:
On 10/21/2013 04:50 PM, Tomas Babej wrote:
On 10/16/2013 03:44 PM, Petr Viktorin wrote:
I still think it would be simpler if IPA and
Hello list,
here is never-ending discussion about freeipa.org wiki and documentation. Any
opinions are more than welcome! (Each participating user will receive
e-thank-you e-mail, I promise! :-D)
We started the discussion privately and then realized that we should move it
to mailing list,
Hello,
This patch addresses ticket https://fedorahosted.org/freeipa/ticket/3819
--
Regards,
Ana Krivokapic
Associate Software Engineer
FreeIPA team
Red Hat Inc.
From 0bc373fe9a8d6f7ed1cc2cd82bf9a69f0a8613d5 Mon Sep 17 00:00:00 2001
From: Ana Krivokapic akriv...@redhat.com
Date: Tue, 22 Oct
13 matches
Mail list logo
