|
|
| |
Oct
4
Written by:
Shawn Bass
Thursday, October 04, 2007 6:55:54 AM
The SoftGrid Team blog published an entry today that describes the three methods for upgrading Softgrid applications. The three types are:
1) Active Upgrade - You open the existing package up in the sequencer, install your updates and add the package version to the Management Console. New launch requests for the package will begin using the new version.
2) Completely new sequence - You build a completely new sequence. The new sequence will need to be streamed down to new clients, but a client can run both versions simultaneously. The downside is the user preferences from the old version of the app are not carried into the new package.
3) Branched package - You approach a branched package like an ActiveUpgrade, only you perform a Save As function which will create a separate package GUID and asset folder. This operates like a completely new sequence in that both can operate at the same time, the difference is that you avoid having to recreate the sequence from scratch.
Each of these methods has advantages and disadvantages. Which method you choose largely depends on the following criteria:
1) Do you need to offer both versions of an application concurrently? If yes, then options 2 and 3 are your choices.
2) Do you care about retaining user preferences/customizations when you perform your upgrade? If yes, then option 1 is the only built in solution, unless you want to attempt some method of migrating the user preferences between your sequences. This would need to be an export/import process external to SoftGrid.
3) How concerned are you about being able to quickly revert to a prior version if the upgrade fails? This can technically be done with all three approaches, but using ActiveUpgrade may put you in a situation that the user customizations may not allow a revert to the previous version, so you may need to drop the user customizations and start over with a blank slate.
4) Are you concerned about re-streaming large amounts of the package? If you use options 2 or 3, you're looking at streaming the entire contents of the package. If you use option 1, you'll only be streaming the delta components of the package that occurred during the upgrade.
The ideal scenario in my opinion is option 3 (Branched package). The only exception would be if you needed to carry user preferences over or if the package was of a substantial size that you don't want to re-stream it again. Read the full article here.
EDIT: Thanks to BoruRR for clarification on Branched Package streaming.
Tags:
8 comment(s) so far...
Re: The three methods of deploying software upgrades via SoftGrid
Hi,
Regarding Option 3, the line "so you don't need to stream the entire package down again (just the delta changes)." is incorrect. It is a completely different package and would require restreaming
By Brian on
Wednesday, September 26, 2007 12:55:42 PM
|
Re: The three methods of deploying software upgrades via SoftGrid
Yes, I agree with Brian. Since you are doing a SAVE AS in #3, its a new package altogether with a new GUID. So it will need to be streamed again. Right?
By Shanx on
Thursday, October 18, 2007 3:25:50 PM
|
Re: The three methods of deploying software upgrades via SoftGrid
Yes Brian is correct. I was mistaken as the packages that I attempted it on were small and had streamed rather quickly. It does in fact restream the entire thing as it is a new package and GUID. I have updated the misinformation in this blog entry as well as on Softgridguru.
By Shawn Bass on
Saturday, October 20, 2007 8:52:11 AM
|
Re: The three methods of deploying software upgrades via SoftGrid
So with an active upgrade, when you copy the updated package back up to the server, do you overwrite the old version or create a new folder?
By Dave on
Thursday, April 10, 2008 9:42:35 AM
|
Re: The three methods of deploying software upgrades via SoftGrid
So with an active upgrade, when you copy the updated package back up to the server, do you overwrite the old version or create a new folder?
By Dave on
Thursday, April 10, 2008 10:18:20 AM
|
Re: The three methods of deploying software upgrades via SoftGrid
@Dave,
When you perform an active upgrade, you launch the sequencer and choose Open package for upgrade. When it's done it will create it an _2.sft file. You need to copy that .sft file up to your content share. You should just copy the entire contents over because the OSDs get updated as well. Then in the SoftGrid management console you go to the Packages node, right click on the app and do Add Version. This is all from memory so the verbiage may not be 100% correct.
Shawn
By Shawn Bass on
Thursday, April 10, 2008 10:39:07 AM
|
Re: The three methods of deploying software upgrades via SoftGrid
Oppps, I should have said you copy it to the exact same folder. The SFT won't be overwritten because it doesn't exist yet.
Shawn
By Shawn Bass on
Thursday, April 10, 2008 10:40:01 AM
|
Re: The three methods of deploying software upgrades via SoftGrid
we are the chinese wholesalers,u will see product as MAC ,china phone,china mobile phone.china cellphone in our site .we are strong Introduction the
wholesale NFL,mbt shoes ,wholesale Christian louboutin,
wholesale abercrombie,moncler jacketsnokia mobile phone ,good luck best apple iphone or apple ipod nano and HTC touch Diamond in our site ,Just look for wholesale boots,peak shoes
zumba dvd wholesale
Wholesale nfl,Motorola AURA ,Wedding Dresses , wholesale mbt shoes ,wholesale abercrombie , NFL Jerseys ,ed hardy come here .It`s a good choice to buy wholesale from trademic.
By sdfs on
Tuesday, February 23, 2010 9:13:15 PM
|
|
|
|
|
|