<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="RU" link="blue" vlink="purple"> <div class="WordSection1"> Hello. We were also planned relatively large deployment (8 sites, 19 IPA servers), and for now our experience told us that Red Hat official support is a must-have option for IPA in mission-critical environment.<o:p></o:p> IPA is still a very fresh solution and it have some issues you may face. <o:p></o:p> <o:p> </o:p> WBR,<o:p></o:p> Alexander Frolushkin<o:p></o:p> <o:p> </o:p> From: freeipa-users-bounces@redhat.com [mailto:freeipa-users-bounces@redhat.com] On Behalf Of Арсений Черняков Sent: Tuesday, April 28, 2015 5:05 PM To: Alexander Bokovoy Cc: freeipa-users@redhat.com Subject: Re: [Freeipa-users] freeIPA and AD in multi-homed environment<o:p></o:p> <o:p> </o:p> <div> <div> Thank you for quick response. So, did I got it right, that this limitation is affecting only RedHat support agreement, and not the technical side of configuration? We're considering the CentOS 7 deployment, and we don't have Red Hat support agreement.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Maybe it's a stupid question, but since we don't have support agreement, can I still ask questions in RedHat mailing list? (I haven't found any forums/KBs/mailing lists dedicated solely to freeIPA and CentOS).<o:p></o:p> </div> <div> <div> <div> <o:p> </o:p> <div> 2015-04-28 13:26 GMT+03:00 Alexander Bokovoy <<a href="mailto:abokovoy@redhat.com" target="_blank">abokovoy@redhat.com</a>>:<o:p></o:p> On Tue, 28 Apr 2015, Арсений Черняков wrote:<o:p></o:p> - Hi all. I've got a rather big domain environment with 10 distributed locations, and I'm considering using FreeIPA as an id manager for linux users and servers, alongside with existing AD, using trusts. In every location, there are 2 DCs for windows environment, and I'm thinking about deployment of 2 freeIPA servers for each location, with replicas. This document states that I can't use more than 20 servers per IPA domain: <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/Setting_up_IPA_Replicas.html#replica-topologies" target="_blank"> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/Setting_up_IPA_Replicas.html#replica-topologies</a> - "No more than 20 servers and replicas should be involved in a single Identity Management domain." - How strict is this restriction? Is there any way I can deploy freeIPA in this situation, assuming that number of locations would increace over time? Is there any other limitations to integrate freeIPA in AD?<o:p></o:p> The limitations described above are for supported configurations deployed on Red Hat Enterprise Linux. If you want a larger configuration to be supported, you need to contact your Red Hat representatives and work out with them exact support statement. -- / Alexander Bokovoy<o:p></o:p> </div> <o:p> </o:p> </div> </div> </div> </div> </div> <hr> Информация в этом сообщении предназначена исключительно для конкретных лиц, которым она адресована. В сообщении может содержаться конфиденциальная информация, которая не может быть раскрыта или использована кем-либо, кроме адресатов. Если вы не адресат этого сообщения, то использование, переадресация, копирование или распространение содержания сообщения или его части незаконно и запрещено. Если Вы получили это сообщение ошибочно, пожалуйста, незамедлительно сообщите отправителю об этом и удалите со всем содержимым само сообщение и любые возможные его копии и приложения. The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. The contents may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this communication in error please notify us immediately by responding to this email and then delete the e-mail and all attachments and any copies thereof. (c)20mf50 </body> </html>