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

Opendeploy File naming convention

lokesh

Hi,

Does any one is having the OpenDeploy file naming convention spects.

I had OpenDeploy script which is having several definitions within that,can i have each individual definition can be deployed with each account.

Thank you,
lokesh.

Find more posts tagged with

Comments

Adam Stoller

I'm not sure I understand your question. Perhaps you can use an example to illustrate your question?

Also - what version of OpenDeploy (5.5.1 SP2?) are you using, on what platform (Windows / Unix)?

--fish
(Interwoven Senior Technical Consultant)

lokesh

OD5.5.1,SP2,SOLARIS 8.0.

I had a deployment script which contanins several definitions for the deployment can i have each def to be deployed with individual account.

Thank you,
lokesh.

Adam Stoller

If I'm understanding your question correctly - the answer is 'no'.

I am assuming you are trying to set up permissions for specific users to be able to run specific deployments through the OpenDeploy GUI - yes?

The granularity for this control is on the deployment configuration file level - not the contents within the deployment configuration file.

So if you have foo.xml and it includes 3 definitions ("def1", "def2", "def3") and you want user "jqpublic" to only be able to run deplyments for "def1" from the GUI, you would need to put "def1" into it's own separate deployment configuration file (foo-def1.xml)

Is that what you were asking?

--fish
(Interwoven Senior Technical Consultant)

upgrade.docx

lokesh

Hi,

foo.xml contains definitions as you said def1,def2,def3 for this i need def1 should be deployed with 'a' user,def2 should be deployed with 'b' user,def3 should be deployed with 'c' users.

if i have foo1.xml with def1 definition and should be deployed with 'a' user,foo2.xml with def2 definition and should be deployed with with 'b' user,foo3.xml with def3 definition and should be deployed with 'c' users and i want to scheduled at the same time for three to happen.

The real time situation is like this:
If i schedule the deployments at the same time it will be crashed or killing the receiver,even if it work the deployment of these two scripts will be going on one account because the service is running on this account and if that account is locked deployments will fail that's why i am asking doing deployments on different account at the same time or doing the deployment with n number of definitions with differnt accounts.

Thank you,
lokesh.

Adam Stoller

Are you talking about these users *running* the deployments, or these users being set in the permissionRules part of the definition to eventually be the owners of the files once they are deployed?

Is the OpenDeploy Receiver running as root or non-root?

Why would running three deployments at the same time crask or kill the receiver? I've seen multiple deployments with mutiple definitions run cocurrently without any problems.

Perhaps you should post (as an *attachment*) the deployment configuration file in question.

--fish
(Interwoven Senior Technical Consultant)

lokesh

this is what i got from support site od Interwoven:

Hi,

Ok, here is what I have found out for you. Since the port is set in
the odnodes.xml, all deployments will use that port. To that end, you can
not send to the same destination on different ports. This also means that
concurrent deploys to the same host are not possible. This is being
addresses in a future release, but for now, unfortunately, it is not
supported. You can try defining the same host on a different port in the
odnodes.xml, however this will slow the deployments down and is not a qa'd
method. Let me know if you want to try that or stagger your schedule until
the fix comes out.

Thanks,

Fred

Adam Stoller

I'm still not understanding whether you are trying to have 3 *people* initiate different parts of a deployment configuration file at the same time, or whether the deployment configuration is using different users in the permissionRules settings for the different definitions.

I think there is some inaccurate information in the quoted message you posted - i'll contact you about that off-line.

In the meantime, could you please post to the forum your deployment configuration file (as an attachment)

--fish
(Interwoven Senior Technical Consultant)

Adam Stoller

Okay, based on conversations with Lokesh and Support, it appears that there were some communication problems somewhere along the way and the response provided by support was based on OpenDeploy 4.x and not OpenDeploy 5.x.

OpenDeploy 5.5.1 *does* support concurrent deployments to the same Receiver.

--fish
(Interwoven Senior Technical Consultant)

lokesh

Hi Ghoti,

I need very urgent clarification i have to do this for yesturday's change freeze.!!!!!!!!!!!!!!!here is my concerns.

I had solaris8.0(Admin,Opserver(teamsite open API),Base server) and windows2000(Receiver server) OD5.5.1
on the receiver side i made to choose the operational server as unix and the bootstarp user name as root. which work fine.
I had one more senario here i had one more windows which acts as baseserver and need to point to the same windows receivers as above but here the receiver is choosing the operational server as unix which is a conflict here....how do i go with this.

Adam Stoller

If I'm understanding you correctly - you have:

A TeamSite server
- Solaris
- OpenDeploy Admin Server
- OpenDeploy Base Server

A second OpenDeploy Base Server
- Windows

This should not be a problem - the Windows Base Server should refer to the Unix Operations / Admin Server - there should be no conflict.

Note: You should NOT install the AdminServer (and/or Operations Server) again once it has already been installed on the Solaris machine - just install the OpenDeploy Base Server and let it talk to the pre-existing Operations / AdminServer.

--fish
(Interwoven Senior Technical Consultant)