• 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 15674
  • 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

    You weren't supposed to understand it - all I was saying was that internally we have produced some utilities which use an XML file to describe which releases we want to update, and then have some perl scripts to manage the installations which use this XML file to control what gets done. Since I can't share these utilities, I was just broadly describing what we've done around the batch iscape.sh command to manage software releases within the EMEA support team. The key part was using iscape.sh in batch mode.

    Regards,

    Andrew.

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

    You weren't supposed to understand it - all I was saying was that internally we have produced some utilities which use an XML file to describe which releases we want to update, and then have some perl scripts to manage the installations which use this XML file to control what gets done. Since I can't share these utilities, I was just broadly describing what we've done around the batch iscape.sh command to manage software releases within the EMEA support team. The key part was using iscape.sh in batch mode.

    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