Thanks Justin, >>Capsule syncs are no longer handled via qdrouterd (since katello 3.0). Ok, so i think that works over https and that is handled by apache.
>>I'm not 100% sure what you are asking here. Could you explain a bit more? I have my capsule behind firewall, and master in other region and they are connected over WAN, so i was looking for information if there is any impact if connection disruption, any timeout values, also how to measure latency of content sync, is there any document on how much capsules one single master can handle ? how to calculate latency between capsule <-> master sync ? how to handle DR or HA for capsules and Satellite master ? how to run Capsule and master on CNAME ? >> if you use REX it will still work fine though. what is that REX mean ? On Friday, 28 April 2017 18:52:02 UTC+5:30, jsherril wrote: > > > > On 04/28/2017 09:10 AM, Unix SA wrote: > > Hello, > > > > I would like to understand qdrouterd communication between katello > master and katello capsule > > > > 1) what will happen if connection is broken while some sync going on ? > Capsule syncs are no longer handled via qdrouterd (since katello 3.0). > So essentially no issue would occur if you were doing a capsule sync and > the qdrouterd communication died. > > > 2) if my capsule and master are connected using WAN does it have any RTT > impact on communication. > I'm not 100% sure what you are asking here. Could you explain a bit more? > > > 3) I assume if qdrouterd is broken between master and capsule, I will > not be able to use hammer to install/remove/update erratas on client > machines connected to capsule ?? > Correct, if you use REX it will still work fine though. > > > > > Does anyone has any user stories, diagrams on how wood, gofer, > qdrouterd, celery are communication and any impact if those connections are > disturbed or broken. > > This is kinda old, but should still be accurate may help: > > https://raw.githubusercontent.com/ehelms/connection_diagram/master/katello.png > > Doesn't really cover broken connections. > > > > Thanks in advance. > > DJ > > > Hope that helps. > -Justin > -- 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 foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
