Re: [Condor-users] Flocking

[<john.kewley@xxxxxxxxxx>]

> Hi John!

Hi - longtime no see/hear!
 
> Flocking is a relationship between a schedd and a "remote" 
> condor pool.  

So for a 1-way flock from all schedds in pool A to pool B:

* each schedd in pool A needs a FLOCK_TO statement to pool B's central
node
* Do you need some FLOCK_FROM statements anywhere in pool B (FLOCK_FROM
info also
  appears to be lacking in 5.2)?
* AND every execute node in pool B needs to be able to communicate to
all these flocking
  schedd machines in pool A via the current prevailing condor ports (I
assume this still
  includes fixed and ephemeral ports, udp and tcp)

> We sometimes may lazily refer to flocking as though it were a 
> relationship between one pool and another, but this should be 
> interpreted as meaning that all schedds in pool A are 
> configured to flock to pool B.
> 
> I'll see if I can clarify the language in the manual.
> 
> Cheers,
> --Dan
> 
> john.kewley@xxxxxxxxxx wrote:
> > Hi
> >  
> > In section 5.2 of the Condor Manual it states:
> >  
> > "The simplest flocking configuration sets a few configuration 
> > variables. If jobs from machine A are to flock to pool B, then in 
> > machine A's configuration, set the following configuration 
> variables: "
> >  
> > By "If jobs from machine A" refer to
> > a) Every submit machine
> > b) Every machine with a schedd
> > c) The central node with a Collector (or is it Negotiator)
> >  
> > I thought flocking was c), but the wording used above seems 
> to suggest
> > a) or b) which implies
> > a lot of machines (assuming many schedds in pool) would 
> need updating 
> > if an extra pool was needed to be flocked to.
> >  
> > i.e. is it not just the central nodes (Collectors) that 
> need updating 
> > when you add a new flock.
> >  
> > cheers
> >  
> > JK
> >
> > --
> > Scanned by iCritical.
> >
> >
> > 
> ----------------------------------------------------------------------
> > --
> >
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx 
> > with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
> > The archives can be found at:
> > https://lists.cs.wisc.edu/archive/condor-users/
> >   
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to 
> condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
> 
--
Scanned by iCritical.