nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Co-existing OpenDeploy 5.6 and 6.0.2

mstradling

Can anyone confirm is OpenDeploy 6.0.2 can be installed in parallel with OpenDeploy 5.6 - my client wants to phase the migration of deployment from 5.6 to 6.0.2?

The 6.0.2 Installation guide suggests they can (P50 - Upgrading From Previous Release states "...you will be prompted on whether you want to upgrade your existing software with the current release, or wether you want to install the new component alongside your existing software.".

It doesn't give any further details so hoping someone can confirm it works.

Find more posts tagged with

Comments

Adam Stoller

Can anyone confirm is OpenDeploy 6.0.2 can be installed in parallel with OpenDeploy 5.6 - my client wants to phase the migration of deployment from 5.6 to 6.0.2?

The 6.0.2 Installation guide suggests they can (P50 - Upgrading From Previous Release states "...you will be prompted on whether you want to upgrade your existing software with the current release, or wether you want to install the new component alongside your existing software.".

It doesn't give any further details so hoping someone can confirm it works.

Yes - OD 6.x and OD 5.x can co-exist on the same server - but you will need to specify both:

a different path for the installation directory, and
a different port for the deployment transition

In general - you're best off by replacing / upgrading your Base Server and then, over time as needed, replacing / upgrading your Receivers. In this way you do not have to have both versions active on the same server - you just have both versions active in the same network and gradually replace the older version with the newer version.

Check for patches and such too though, as I believe there's a 5.6 patch to enable the 5.6 receiver to work with filelist deployments from a 6.x base server (or something like that - don't remember the details right now) - so even if you don't want to fully upgrade the version of the receiver - you'll probably have to apply a patch to them...

mstradling

Thanks ghoti.

Migrateduser

Ghoti's right on an incompatibility betweeen 6.02 base server and v. 5.6 receiver that's not fully patched. Just ran into this last week.

A filelist deployment will fail unless the 5.6 version has both SP1 and the latest patch applied to it. It'll give an error about not finding the .mf (manifest) file.

I don't believe this is a problem when using 6.02 Base with 5.5 recievers. Just 5.6 receivers.

marcussteiner

Hi,
I've got a further question with regards to this. Can I run two OpenDeploy 6.02 sender on one Teamsite box and then deploy to different recievers on version 6.02. Reason for this would be two teams Internet/Intranet would like to sperate their deployment scenarios cause they both take quite a while to run and they would like to have and improvement in performance?

hollis

Migrateduser

Uhhh, well, yes you can do this but I'm not sure that this would improve performance at all. In fact, I'm pretty sure that this won't buy you anything. Could you give a bit more background about what these groups want to do and why they're interested in having two separate instances of OD?

marcussteiner

uhhh, well I'm trying to find that out myself. I didn't see much benefit yet and was wondering if someone has done this before. I think one group is crashing/blocking the OD sender for hours because of their deplomyments and the other are getting fed up with waiting for them to finish. I think the bottleneck would here be more network traffic than OD performance. One group is deploying full deployments with some 15Gig each night and this is blocking the whole traffic. (and yes we want to change this to differential deployments in the near future)

Migrateduser

I see. Does OD report any errors that the deployment is too large that it can't handle it? If not, I suggest exactly what you stated -- that the bottleneck is more network / infrastructure-related and that adding another instance of OD doesn't add anything.

OD can also be resource-heavy so adding another one on the same box might double that effect.

Also, are these two groups utilizing the same OD definition in od-home/conf? I wouldn't think so but that would be another thing to keep away from.

Adam Stoller

Hi,
I've got a further question with regards to this. Can I run two OpenDeploy 6.02 sender on one Teamsite box and then deploy to different recievers on version 6.02. Reason for this would be two teams Internet/Intranet would like to sperate their deployment scenarios cause they both take quite a while to run and they would like to have and improvement in performance?

hollis

OpenDeploy 6.0.2 allows you to have multiple 'instances' of the server running (read the manuals for more information) - I don't believe it will work if you try to install the software twice on the same machine (on Windows there's only 1 OD60HOME environment variable, on Unix there's only 1 /etc/defaultiwod60home file)

I believe you can multiple receiver instances too (don't have my manuals handy right now).

However - if the teams are running different deployment configuraiton files then I don't believe the above will make any significant difference in terms of the amount of time being used for the deployment.

Instead - you may need to consider other options:

disabling the OD event reporting on both sides (sender/receiver) will tend to improve speed of deployments
doing filelist deployments instead of source/target directory comparison deployments will be faster
non-transactional deployments are faster than transactional deployments

marcussteiner

Hi guys,
thanks for the help. I will consider this in my furhter investigations.

m