EDA blueprints

[okrause]

This PR adds two blueprints and a README.MD file to a new examples/eda folder.

Both blueprints use Google Cloud NetApp Volumes as the shared NFS storage for the compute cluster. The eda-all-on-cloud blueprint builds on top of #4583. Since that one is not merged, this PR looks pretty big, but it is only a folder, a readme and two blueprint files.

I open it as a draft PR for now. To make it ready for prime time, the following things need to happen:

1. PR Add Google Cloud NetApp Volumes support #4583 needs to be merged to develop
2. I need to complete work on README.md. Will complete next week.
3. I need to work with Google EDA experts to have them verify (and potentially update) the cluster deployment group for EDA workloads.

[okrause]

Hello, this PR is about the files in the examples/eda folder. It adds two new blueprints and a readme.md. All the other changes are from #4583 and not subject of this PR. I am going to rebase to develop as soon an #4583 is merged. I just want to get the review process started on the two blueprints and the readme file.

Kudos to @thomasnyc for providing the H4D compute part of these blueprints.

[okrause]

@sarthakag Can you please have a look? Should these blueprints be added as core or community? I am open to both. Do we need tests?

[okrause]

@sarthakag BTW: We cannot add an test for ./examples/eda/eda-hybrid-cloud.yaml, as this required the user to provide existing volumes. Apart from that, it is basically the same as the eda-all-cloud blueprint anyways.

[sarthakag]

Hi @okrause, can you please rebase ?

Had a quick look over the PR, left a few comments. Will look more into the integration tests and get back to you in a week's time. Thanks!

[sarthakag]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces two new blueprints for Electronic Design Automation (EDA) workloads, along with comprehensive documentation. The changes are well-structured and provide valuable examples for users. My review focuses on improving the clarity and correctness of the documentation and enhancing the configuration of the new blueprint files. I've identified several typos and inconsistencies in the README files that should be addressed. In the YAML blueprints, I've pointed out a hardcoded value that should use a variable for better flexibility and a security concern regarding overly permissive file permissions.

[okrause]

@sarthakag Thank you for the review. The gemini review is also very helpful to find small gotchas which easily go unnoticed.
I incorporated the requested changes, rebased and pushed latest version.
Looking forward to the answer if eda-all-cloud needs a test.

[bytetwin]

@okrause

1. Both the blueprints and its Readme should be in community/examples. Examples folder is for core blueprints that cluster toolkit team supports and will continue to maintain. Netapp volume is gcp supported product and is in core module as it can be used as filestore, these blueprints are for specific workload type which cluster toolkit team won't support.
2. Please avoid adding images to the repo. Cluster toolkit is cloned from github by users as well as automated systems and repository size will impact the cloning speed.

[okrause]

@okrause

1. Both the blueprints and its Readme should be in community/examples. Examples folder is for core blueprints that cluster toolkit team supports and will continue to maintain. Netapp volume is gcp supported product and is in core module as it can be used as filestore, these blueprints are for specific workload type which cluster toolkit team won't support.
2. Please avoid adding images to the repo. Cluster toolkit is cloned from github by users as well as automated systems and repository size will impact the cloning speed.

@bytetwin Understood. Moved to community/examples/eda. Removed the pictures. Especially the hybrid use case benefit a lot from a picture, so I added a link to a blog where the interested user can find a picture of the concept. Pushed the changes.

Thank you for your input!

[okrause]

git history of this one is messy. For the merge I created clean PR #4931. Closing this one.