RedHat have published a reference architecture for Satellite 6.2 which 
covers a lot of areas - it is available 
https://access.redhat.com/sites/default/files/attachments/sat6ha-lb-refarch.pdf

On Tuesday, October 25, 2016 at 10:26:52 AM UTC-4, Chris Baldwin wrote:
>
>
>
> On Tuesday, October 25, 2016 at 10:21:30 AM UTC-4, Martin Dobrev wrote:
>>
>>
>>
>> On Tuesday, 25 October 2016 14:43:27 UTC+1, Greg Sutcliffe wrote:
>>>
>>> On 25 October 2016 at 13:53, Christopher Pisano <[email protected]> 
>>> wrote:
>>>
>>>> we should maybe all try and jump on a video call and talk out our 
>>>> different experiences and come together as to what we believe *should* be 
>>>> the best practices. 
>>>>
>>>
>>> That sounds like a good idea - I can host that if needed (but you could 
>>> probably figure out a hangout yourselves :P). Would you want that public 
>>> (recorded, deep-dive style), or "private" (jn the sense that its open to 
>>> the community to join, but not recorded)?
>>>
>>>  
>> Initial talks can be private until we get some sort of draft on work 
>> required. Then we might record as well so community knows what's going on. 
>> Of course everyone's invited to participate and contribute to our talks.
>>  
>>
>>> Greg
>>>
>>
> Honestly, the opsec considerations in either scenario are the same. I 
> would suggest recording it in case there are questions later.
>
> This is my first shot at multiple-foreman documentation: 
> https://theforeman.org/manuals/1.13/index.html#5.8MultipleForemaninstances 
> . It touches on a few things Chris P. mentioned in his blog post (reposted 
> on Foreman's site), and points out a few other issues that I ran in to. It 
> doesn't address HA proxy stuff, PG pool for the DB (if needed), setting up 
> a real (not self-signed) cert, etc.
>

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to