• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Installing Virtuoso with Chef

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 15670
  • 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

Installing Virtuoso with Chef

awesome1
awesome1 over 10 years ago

Are you aware of a Chef.io cookbook for deploying and configuring Virtuoso 6.xx?

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    I wasn't that aware of Chef (I just read up on it). I'm not sure there's anything special needed. Generally speaking you install Cadence releases (such as IC616) on a filer and then NFS mount the software using a mount point (often automount). This means that there's no major deployment task since you don't need to replicate the installation to each machine in the network. All I do is install on the server and add an automount entry in the automount map, and then it is available to all users. I have a version selection system that uses rule-based lookup to find releases, but if you were using something like "modules", it would just be a matter of adding a module entry for that release too so that users can pick it.

    So I'm not sure what you're asking - to me it doesn't look as if Chef would add much value here. Maybe others in the community have used Chef and can give you the advice you're looking for.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    I wasn't that aware of Chef (I just read up on it). I'm not sure there's anything special needed. Generally speaking you install Cadence releases (such as IC616) on a filer and then NFS mount the software using a mount point (often automount). This means that there's no major deployment task since you don't need to replicate the installation to each machine in the network. All I do is install on the server and add an automount entry in the automount map, and then it is available to all users. I have a version selection system that uses rule-based lookup to find releases, but if you were using something like "modules", it would just be a matter of adding a module entry for that release too so that users can pick it.

    So I'm not sure what you're asking - to me it doesn't look as if Chef would add much value here. Maybe others in the community have used Chef and can give you the advice you're looking for.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information