You can look how Erlang handles software hot-update. /Kaiduan
--- On Tue, 3/13/12, Hanmer, Robert S (Robert) <[email protected]> wrote: > From: Hanmer, Robert S (Robert) <[email protected]> > Subject: Re: [telecom-patterns] [patterns-discussion] Patterns for > self-updateable systems? > To: "Dragos Manolescu" <[email protected]>, > "[email protected]" <[email protected]> > Cc: "[email protected]" <[email protected]> > Received: Tuesday, March 13, 2012, 2:56 PM > Hi Dragos, > > Not a whole lot has been published in the form of patterns > for self-update. There are of course ideas and > techniques but some are not published for competitive > reasons. > > I'll point you first to chapter 12 of "Robust Communications > Software" by Greg Utas. He talks about the core > techniques for Hitless Patching, Hitless Upgrade and Rolling > Upgrade. These aren't quite patterns as we know them > and I'm pretty sure you won't find earlier versions from > Greg in any of the PLoP proceedings. > http://www.amazon.com/Robust-Communications-Software-Availability-Carrier-Grade/dp/0470854340/ref=sr_1_1?s=books&ie=UTF8&qid=1331664530&sr=1-1 > > There is a forthcoming book from two colleagues, Randee > Adams and Eric Bauer, "Reliability and Availability of Cloud > Computing", that might have something of relevance to your > search, I'm not sure. It is coming from IEEE Press > this summer. > http://www.amazon.com/Reliability-Availability-Cloud-Computing-Bauer/dp/1118177010/ref=sr_1_2?ie=UTF8&qid=1331664253&sr=8-2 > > One of the biggest problems is always the data conversion > from one release to the next release. The schema > update in database terms. I wonder (but don't know) if > concepts like meta-programming and reflection can help. > > Bob > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] > On Behalf Of Dragos Manolescu > Sent: Monday, March 12, 2012 1:47 PM > To: [email protected] > Subject: [patterns-discussion] Patterns for self-updateable > systems? > > Hi -- > > I'm building a system that needs the ability to self-update > (software) from the network, at run time. This is an area I > don't have first hand experience with but I know that it's > been done for years--for example, telecom switches. If you > know of patterns that focus on self-updateable software I > would appreciate your pointing me their way. > > Thanks, > > -Dragos > > > -- > Data Services, HP Cloud Services | [email protected] | +1 > 512 5DRAGOS > > _______________________________________________ > patterns-discussion mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/patterns-discussion > > _______________________________________________ > telecom-patterns mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/telecom-patterns > _______________________________________________ telecom-patterns mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/telecom-patterns
