OD 6.0.2 - local directories != filelist?

Adam Stoller · 2005-09-01T18:15:20+00:00

EnvironmentOpenDeploy 6.0.2TeamSite 6.5 SP1W2K3 EE (base server)Linux (receiver) ProblemI don't believe I've ever seen this error before - so I'm hoping someone can explain it:LIB: ... ERROR: Deployment (...): Size of local directories[2] is not equal to that of of filelist[1] I'm running the deployment in simulated mode -…

Adam Stoller

Environment

Problem

LIB: ... ERROR: Deployment (...): Size of local directories[2] is not equal to that of of filelist[1]

Ideas anyone?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Migrateduser

would you mind posting the actual OD Conf file? I have a hunch, but it'd be easier to look at the xml file instead of trying to explain it :-)
-Rori

Adam Stoller

While I think I've figured it out - I'm not crazy about what it means.
Basically I'm trying to take a list of files that are based off the root of the workarea and deploy different segments of that list in different definitions - in so doing, I've gotten into cases where I want to filter out more than one path specification from the filelist and I want to target the resulting set to be deployed to a single root directory (in this case, the source path would still have directory paths attached so the actual outcome would be root_dir/subdir1/files, root_dir/subdir2/files - but I think OD is ignoring the subdirs on the source side and complaining about trying to deploy two source files into a single target directory.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

In reply to:

I've gotten into cases where I want to filter out more than one path specification from the filelist

that's what I thought you were doing...according to the DTD, filelist elements can only have ONE pathspecification element, not multiples like all other deployment types...

what I've done before is create multiple definitions each using a different filelist...you are allowed only one filelist, but that's per definition, not per OD conf file ;-) and yes, it does seem inefficient to have 2 separate definitions and therefore two deployment processes, but what can you do?

so for example, it looks like you want to deploy <workarearoot>/static to /apps/site/prev, if the source path matches /account or /contact, so what you have seems to be fine, except that the filelist (d:/temp/test_flist) should include only <workarearoot>/static path files, and strip out the /static level, therefore contain:


account/test.txt
account/test1.doc
contact/Diagnostics.xml
about/copy.doc
about/copy2.txt
about/copy3.xml
about/copy4.doc
images/big_fish_swimming_md_clr_10954_001.gif

then you'd need a second definition to deploy <workarearoot>/templatedata/cat/home/data to /apps/site/prev/home, and your filelist would have to be a different one, stripping out /templatedata/cat/home/data so that that directory structure wouldn't get created on the target side...the filelist for that definition could be d:/temp/test_flist2 and would contain only /templatedata/cat/home/data path files:


test.dcr

also, exclude the apps/site/prev/home target directory in the first definition or you'll have problems ;-)

hope that helps,
-Rori

Adam Stoller

Part of the problem stemmed from the workarea root not mapping directly to the various docroots.
Once I got that issue resolved, the deployments became much simpler.
It's kind of unfortunate that the DCRs that will be deployed (as XML files) will end up in docroot/templatedata/..../data/ directories, but they seem to be willing to live with that for now.

This is the first time I've run into this kind of odd source/target pairing and so I never really thought about the issue of having multiple path specifications for a filelist before. Live and learn ;-)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

In reply to:

It's kind of unfortunate that the DCRs that will be deployed (as XML files) will end up in docroot/templatedata/..../data/ directories, but they seem to be willing to live with that for now.

a second definition with a second filelist would take care of stripping out the extraneous levels, and it's not that hard to add the little extra scripting to whatever script is kicking off your deployment...I've actually got a deployment with 6 definitions using 4 different filelists for the same reason you're now experiencing LOL...

In reply to:

This is the first time I've run into this kind of odd source/target pairing and so I never really thought about the issue of having multiple path specifications for a filelist before. Live and learn ;-)

seems like there are infinite use cases and ways to use the various interwoven products, so quite understandable that even you wouldn't have run into every scenario ;-)

cheers,
-Rori

Adam Stoller

<font color='blue'>a second definition with a second filelist would take care of stripping out the extraneous levels, and it's not that hard to add the little extra scripting to whatever script is kicking off your deployment...I've actually got a deployment with 6 definitions using 4 different filelists for the same reason you're now experiencing LOL...</font>

Yeah - I could do that - but that means putting a lot more logic into the workflow externaltask scripts to generate multiple filelists and provide them to the invokation of OpenDeploy (the latter part is trivial, the former part requires effort and wasn't clear that there was a decently generic way to do this such that the logic would apply in all situations - and the time-crunch is on ;-))

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

what's a time crunch? ;-)

check your netcom inbox...payback for help you've provided other times :-)

cheers,
-Rori

Ish

I am running inot same problem of multiple pathspecifications not being liked by OD. I have question the target host is running OD5.6 , could that be causing problem, coz when I included additional sourcefilesystem element
I go this error For downrev to OD5.6.0 or before, when using file_list mode only one local_directory section is allowed.