<br>On Sat, Jun 13, 2009 at 4:54 AM, Michael Giagnocavo <span dir="ltr"><<a href="mailto:mgg@giagnocavo.net">mgg@giagnocavo.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="blue" style="" lang="EN-US">
<div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Well, Nextone for instance has a database the keeps most of the
state of calls, and it’s replicated between the two nodes. (I seem to recall
the database was GNU dbm, but I might be mistaken.) However, as of 4.3 anyways,
the CDRs still get truncated when there’s any kind of switchover. </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p></div></div></blockquote><div> </div><div>BTW in Nextone v4.0.x the GNU db is used for storing configuration data
like storing routes & other bits which is then loaded
into memory. Nextone 4.3 and above uses postgres for this configuration
data. The actual call state information is stored in memory and
replicated to the standby box via some custom network protocol.<br><br>Stateful call migration would be a very useful feature in FS but I imagine its way down the roadmap.<br>
<br>But as to the original question of live upgrades, having some form of
load balancing proxy and then bleeding off traffic from the box you
want to upgrade is the most feasible approach, as others have mentioned.<br><br>Steve<br></div></div><br>