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

dynamic deployment configuration

herald10

Hi,
I have a set of files that need to be transferred from host A to a set of nodes, and another set of files that need to be transferred from host A to another set of nodes. With od5.6 we can use multiple replication farms and definitions and easily achieve it. But My Problem is it is supposed to be one click deployment. I mean there are two files that contains the list of webservers to deploy the content. So how can I achieve this? May be use a dummy deployment and run a dnr script that reads the target hosts from those properties files and prepares a configuration file on the fly and then invoke that deployment from the dnr script itself.... how feasible is it?

TIA.

Find more posts tagged with

Comments

Adam Stoller

How are these lists of files being generated?
How is the deployment being kicked off?
Is it always one-or-the-other ? Is it always both sets of files?
I don't think you could do this easily within the OpenDeploy Admin GUI - but you should be able to do it relatively easily with a custom menu item or through a workflow externaltask script - however I'd need a more thorough description of the process / design / requirements / usage in order to propse something more concrete.

--fish
(Interwoven Senior Technical Consultant)

herald10

hi Fish,
We have a folder called "content" which has a directory structure having files with extensions jpg, gif, html, xml, css, js. Before invoking the deployment the user provides arguments specifying the extensions of the files to be deployed and a list of webservers to which they are deployed to. The deployment is supposed to be a one click deployment be it from a custom menu or workflow or admin gui. Two different set of files are deployed seperately to two different set of web servers. Always the deployment is done to both set of web servers. But the set of webservers vary for each deployment.

We are thinking of using directory comparison for deployments. Only the files that are changed with the given extensions are deployed.

Thank you.

Adam Stoller

I don't have time to give this a lot of throught right now - but:
(a) if you want to do directory differences between Base and Receiver - there's no point in selecting which files you want deployed.
(b) if the specific extensions go to different receivers - you'll want different definitions for each of the [groups of] extensions that go to a particular set of receivers
(c) since it seems possible, from your description, that someone could select N different files which might go to M different Receivers - you'll have to build the logic of which files go where [unless ['a' is true] and divide the selected files into appropriate filelists and then deploy them - using distinct definitions with the deployment configuration file - each definition utilizing a distinct filelist.

I *do* believe it is possible to acheive what you're looking for - but it will take a bit of work to get it down to single-click operation - because you need to figure out all the logic to apply based on what the user had selected at the time they made that click.

Work it out on paper first - develop the design - then implement.

--fish
(Interwoven Senior Technical Consultant)

herald10

Hi Fish,
(a) if you want to do directory differences between Base and Receiver - there's no point in selecting which files you want deployed.

What do you mean by the option (a)..... so do you think its better to use either teamsite comparison or filelist deployment?

Thanks

RichValue.ssd.zip

15292.pdf

Adam Stoller

Option (a) refers to doing a sourceFilesystem deployment *without* filelist.

--fish
(Interwoven Senior Technical Consultant)