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; } } }

Multiple Targets in Deployment using OpenDeploy

gursher

Hi All,

I have a requirement wherein i need to deploy content but to different target areas i.e. more than one location in the "targetFilesystem". The manual states that:-
"The target file location is defined within the definition by the target element. Only a single
target file location is allowed in each definition."

Can somebody please help.

Regards
Gursher

Find more posts tagged with

Comments

Bill Klish

Not sure what version of OpenDeploy you have, but you should be able to do target side overrides which allow multiple targets to be defined.

ISCBorisB

Hi All,

I have a requirement wherein i need to deploy content but to different target areas i.e. more than one location in the "targetFilesystem". The manual states that:-
"The target file location is defined within the definition by the target element. Only a single
target file location is allowed in each definition."

Can somebody please help.

Regards
Gursher

Read about "Fan-Out Deployments" in your OD Manual.

If I understand you correctly what you need is second "Fan-Out" method, using multiple named definitions
and corresponding execDeploymentTask elements.

gursher

I am aware of fan-out deployments but that is not what i am looking for. I am able to deploy content to two different servers siamultaneoulsy but what i need is to deploy them in diferent file systems.

So lets say on server A if the content is getting deployed to C-drive then on Server-B the content should be simultaneously to the D-drive.

Please let me know if it is possible to do so without writing/customising the script.

Thanks & Regards
Gursher

ISCBorisB

I am aware of fan-out deployments but that is not what i am looking for. I am able to deploy content to two different servers siamultaneoulsy but what i need is to deploy them in diferent file systems.

So lets say on server A if the content is getting deployed to C-drive then on Server-B the content should be simultaneously to the D-drive.

Please let me know if it is possible to do so without writing/customising the script.

Thanks & Regards
Gursher

Ok. Let's try one more time...

As pointed earlier, there are two types of fan-out Deployments

Second Fan-out type has individual <target> sub-tags per definition and that's what you are looking for, no?

gursher

Hi,

I know that using multiple definition and multiple execdeplopyment options this can be done, but that is the whole point, i want just one definition which says for e.g. "Deploy Live" and this should deploy content to two different servers on different file systems.

I think it is not possible to do that and i will cutomise the deployment script.

Thanks anyways

Regards
Gursher

ISCBorisB

Thanks anyways

You are welcome anyways

Adam Stoller

Hi,

I know that using multiple definition and multiple execdeplopyment options this can be done, but that is the whole point, i want just one definition which says for e.g. "Deploy Live" and this should deploy content to two different servers on different file systems.

I think it is not possible to do that and i will cutomise the deployment script.

Thanks anyways

Regards
Gursher

If each node in your replicationFarm has a different target directory - you can define that within a targetRules sub-element of the useNode element in the replicationFarm - the target area associated with the node should override any target area path specified within the target element of the definition.

gursher

Gr8, target overrides resolved the issue.
Thanks everybody

Regards
Gursher

Migrateduser

i cant seem to get this to work - its not overriding the targetFilesystem - here is my snippet can someone tell me what is wrong?

replicationFarmSet
replicationFarm name="ai_school_folders" quorum=""
nodeRef useNode="MyLocalHost"
targetRules area="Y:\default\main\EDMC_Marketing\Brands\Art_Institute\AI_austin\WORKAREA\Content\htdocs" /
/nodeRef
/replicationFarm
/replicationFarmSet

ISCBorisB

i cant seem to get this to work - its not overriding the targetFilesystem - here is my snippet can someone tell me what is wrong?

replicationFarmSet
replicationFarm name="ai_school_folders" quorum=""
nodeRef useNode="MyLocalHost"
targetRules area="Y:\default\main\EDMC_Marketing\Brands\Art_Institute\AI_austin\WORKAREA\Content\htdocs" /
/nodeRef
/replicationFarm
/replicationFarmSet

Fragment's Syntax seems correct. quorum="" is a bit ambiguous, I would remove it if I were you.

What is your problem manifestation? Do you get some Deployment error? If so, which one? If not, what happens? Is override
simply ignored and files get successfully Deployed to the definition's target area? You may want to attach complete configuration
if you need some advise.

SethHickel

Additional question/scenario:

This is close to what I need to do except that I would need to have two nodeRef for the same server each with a different targetRules area defined. So for each of my servers currently defined I would need to add a second nodref with a new targetRule area due to an IHS upgrade where the unix admins want to the new version on a new file system on the same server and want, for a limited time, to be able to deploy to both file systems with the same OD Configuration.

Any issues with referencing the same server twice with different targetRule areas defined?

And - since this overides my target file system defined in my definitions target will it cause my filters defined there to be ignored?

FYI - fan-out, file-list deployment using quorum.

Thanks.

Adam Stoller

Additional question/scenario:

This is close to what I need to do except that I would need to have two nodeRef for the same server each with a different targetRules area defined. So for each of my servers currently defined I would need to add a second nodref with a new targetRule area due to an IHS upgrade where the unix admins want to the new version on a new file system on the same server and want, for a limited time, to be able to deploy to both file systems with the same OD Configuration.

Any issues with referencing the same server twice with different targetRule areas defined?

And - since this overides my target file system defined in my definitions target will it cause my filters defined there to be ignored?

FYI - fan-out, file-list deployment using quorum.

Thanks.

I suggest you create an alternate node name for your node (in odnodes.xml) and then specify one of the node names with one of the target paths, and the other node name [for the same receiver] with a different target path. I think that will work - though it's been a long time since I've tried anything like it.