1

Topic: Update of systems 24\7

Let's imagine an update of a software of atomic station or other software 24/7 which it is impossible to stop. As there  an update if it is necessary to update for example a software + basis. From a software I still can understand that by turns we update , computers. And here with basis not clearly. If the structure changes so, what the old version of application cannot work with new as do? A variant at me, but all the same  difficult 1. We do a cluster of bases and replication between bases. 2. We chop off a little  from a cluster, we roll on all of them changes 3. We include the new version of basis, we chop off old versions and further we roll 4. We roll on new versions of basis a script on data migration which happened on the old version of basis while did point 2 Who with such faced?

2

Re: Update of systems 24\7

Hello, Rikomer, you wrote: R> Who faced the such? It is possible to have simply some systems which at first are updated completely, and then there is an operation switching on them (hotswap). Thus, at you the full version of old system on which it will be possible to be rolled away and completely upgraded version.

3

Re: Update of systems 24\7

Hello, Rikomer, you wrote: R> we Imagine an update of a software of atomic station or other software 24/7 which it is impossible to stop. If atomic station there critical a software such that it or is possible  on the move, or it is not necessary to update between operation cycles at all. And the planned stop of times in couple of years is quite admissible. And noncritical let to itself though every night . R> As there  an update if it is necessary to update for example a software + basis. R> from a software I still can understand that by turns we update , computers. Or the software allows to be updated on the move. It allow, for example: Erlang (there is a complete set of regular mechanisms of such update), Python (functions and declarations of classes are updated at once, for objects on these classes there are some decisions of a different level ), Java (an overload of classes with recovery from ), many other things... R> And here with basis not clearly. If the structure changes so, what the old version of application cannot work with new as do? That is simple so do not do there should be a compatibility on road even if the plan of passage demands the several artful intermediate stages and operation rise in price at passage (how to update some versions of columns simultaneously). R> a variant at me, but all the same  difficult R> 1. We do a cluster of bases and replication between bases. R> 2. We chop off a little  from a cluster, we roll on all of them changes R> 3. We include the new version of basis, we chop off old versions and further it is rolled R> 4. We roll on new versions of basis a script on data migration which happened on the old version of basis while did point 2 All the same there will be not consistent intermediate states. It is necessary to do without such .

4

Re: Update of systems 24\7

Hello, Rikomer, you wrote: R> we Imagine an update of a software of atomic station or other software 24/7 which it is impossible to stop. R> as there  an update if it is necessary to update for example a software + basis. R> from a software I still can understand that by turns we update , computers. R> and here with basis not clearly. If the structure changes so, what the old version of application cannot work with new as do? R> a variant at me, but all the same  difficult R> 1. We do a cluster of bases and replication between bases. R> 2. We chop off a little  from a cluster, we roll on all of them changes R> 3. We include the new version of basis, we chop off old versions and further we roll R> 4. We roll on new versions of basis a script on data migration which happened on the old version of basis while did point 2 R> Who with such faced? If the reactor after automatics failure instantly blows up - that is explicitly bad reactor, and any automatics, even the most reliable can refuse. The output - the reactor needs to be projected so that it any time could work "on the autopilot" while for example the controlling computer reboots. If it so is designed, it is possible to update directly in an operating time, observing only temporal periods. P.S. If the system of triple reservation (i.e. the voting protocol is used) then generally problems are not present is used for example: in turn we update on on computers and all.

5

Re: Update of systems 24\7

Hello, Rikomer, you wrote: R> we Imagine an update of a software of atomic station or other software 24/7 which it is impossible to stop. R> as there  an update if it is necessary to update for example a software + basis. And what for at atomic station basis? On the answer to this question depends, as there it update...

6

Re: Update of systems 24\7

Hello, Qulac, you wrote: Q> If the reactor after automatics failure instantly blows up - that is explicitly bad reactor, and any automatics, even the most reliable can refuse. The output - the reactor needs to be projected so that it any time could work "on the autopilot" while for example the controlling computer reboots. If it so is designed, it is possible to update directly in an operating time, observing only temporal periods. On the autopilot it can quite according to plan and safely leave in such state from which in its operating conditions it is necessary to translate week.

7

Re: Update of systems 24\7

Hello, Rikomer, you wrote: R> we Imagine an update of a software of atomic station or other software 24/7 which it is impossible to stop. R> as there  an update if it is necessary to update for example a software + basis. R> from a software I still can understand that by turns we update , computers. R> and here with basis not clearly. If the structure changes so, what the old version of application cannot work with new as do? R> a variant at me, but all the same  difficult R> 1. We do a cluster of bases and replication between bases. R> 2. We chop off a little  from a cluster, we roll on all of them changes R> 3. We include the new version of basis, we chop off old versions and further we roll R> 4. We roll on new versions of basis a script on data migration which happened on the old version of basis while did point 2 R> Who with such faced? Normally in operation the main set also is a reserve set. If it is necessary to update - that the main set deduce from operation, put a reserve set into operation. The main set update and switch reversely. So do in power, I suspect atomic station also.

8

Re: Update of systems 24\7

About atomic stations I do not know, but generally becomes approximately so: 1. The software that worked both with old and with the new version of basis is updated. 2. The basis is updated, new fields and  are added, old are not deleted. 3. The data is migrated. 4. The software that worked only with the new version of basis is updated. 5. The basis is updated, old fields are deleted. Depending on character of changes any steps can be passed.

9

Re: Update of systems 24\7

Hello, Rikomer, you wrote: R> And here with basis not clearly. If the structure changes so, what the old version of application cannot work with new as do? And what for so to do? We expand structure DB so that the extension did not hinder the old version. We update. If needed online is deleted old fields which the new version does not touch. Also it is not forgotten to transfer/skonvertirovat the data from deleted fields... avalon/2.0.3

10

Re: Update of systems 24\7

Hello, Rikomer, you wrote: As you understand, it is necessary to understand not simply as , but also to "prepare" + under this process. R> who faced the such? Gave a similar question at social security . R> As there  an update if it is necessary to update for example a software + basis. R> and here with basis not clearly. If the structure changes so, what the old version of application cannot work with new as do? The collective unconscious was declined in the core to the content of two copies of BD/APPENDICES through  against what I especially did not protest