[Serdev] SER's core design features(process model/parser/lumps/script) - was: So who/what is SER for, anyway?

[Dragos Vingarzan]

Martin Hoffmann wrote:
>> Greger V. Teigre wrote:
>>     
>>>     But, on the stuff that Martin writes about, operations, change
>>> management, scalability, failover, etc, we have lots to learn. I'm
>>> ashamed that there are no standardized way to monitor SER proxies,
>>>       
>
> That is just plain wrong. You wouldn't really believe I run a large
> scale operation without monitoring my proxies, would you? True, there is
> no drag-and-drop solution. But hey, every decent sysadmin is able to
> write the necessary scripts in a couple of hours.
>   
But Martin, telco's toys come with that thing built in. And that is a
different approach from the Internet-like one. Their toys are built to
survive and work even if the sysadmin decides to take a long vacation
and several things crash. They have things like 3 redundant nodes, with
total load of max 66%, so that in case that one fails, the others can
take over. And all this is BUILT IN and TRANSPARENT, like nothing
happened. No BOFH needed ;-).

If the IMS convergence thing will ever work, then the telcos will learn
some lessons on "freedom" and "openness". It would just be a shame if
the IP guys won't learn the reliability thing back from them. I worked
for some time in parallel with guys doing that and believe me that they
were more serious than we are now.

-Dragos