Stats

Locked Locked
Replies 6
Subscribers 65
Views 17482
Members are here 0

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VManager + DRM user specific config (HTCondor)

Hello Everyone,

I am in the process of setting up a VManager + HTC server farm (using HTCondor) for regressions.

As HTCondor is not natively supported by Cadence like NC or SGE is, I need to specify it is a USER SPECIFIC DRM and then select a path of the DRM TCL implementation file.

I am unsure what this DRM TCL file contents and structure should be and I cannot find anything related to this particular file in the documentation.

Has anyone implemented anything like this and can provide me with some examples/guidelines on how to make this file?

Best Regards,

Baudilio Garcia

Parents

StephenH over 5 years ago

Please refer to the section "Creating User-defined DRM API for Parallel Merge / Parallel Rank/ DRM Options" in the docs: support.cadence.com/.../techpubDocViewerPage

You basically have to provide a Tcl file that implements some call-backs to submit / kill / monitor the jobs by calling out to the right commands in your DRM (HTCondor) and returning the information in the format that vManager expects.
Cancel
Vote Up +1 Vote Down

Cancel

Reply

StephenH over 5 years ago

Please refer to the section "Creating User-defined DRM API for Parallel Merge / Parallel Rank/ DRM Options" in the docs: support.cadence.com/.../techpubDocViewerPage

You basically have to provide a Tcl file that implements some call-backs to submit / kill / monitor the jobs by calling out to the right commands in your DRM (HTCondor) and returning the information in the format that vManager expects.
Cancel
Vote Up +1 Vote Down

Cancel

Children

BGarcia over 5 years ago in reply to StephenH

Hello Stephen,

That is exactly what I was looking for! Thank you very much for your help and support!!

Best Regards,

Baudilio Garcia
Cancel
Vote Up +1 Vote Down

Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.