Re: Questions about SmartFrog

Murray, Paul (HP Labs, Bristol) wrote:
> Just a couple of corrections:
> 
>>  We also have an anubisdeployer component that exists to deploy anubis itself.
> 
> The AnubisDeployer is a SmartFrog deployer that uses Anubis to determine where to deploy things - it doesn't deploy Anubis.

ah, now I understand. Sorry for causing the confusion

>>  3. It is currently dependent on the clocks being synchronised.
>>     If NTP is not working properly across all nodes, you have problems. this is something that
>>     could be fixed, as it is less fundamental to the design than multicasting.
> 
> This statement is not true (but once was). Anubis has two timing protocols:
>  - one times clock skew, comms delay and scheduling dely so machines with clocks that drift become untimely relative to one another
>  - one times comms delay and scheduling delay only, so clocks are allowed to drift.

the latter works best on virtualized systems, yes?


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4