Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ChatQnA - Add Terraform and Ansible Modules information #970

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

lucasmelogithub
Copy link

Description

  • Intel has developed Terraform and Ansible Modules.

  • These have now been enhanced to provision Xeon based Cloud Instances and to automate deployment of OPEA ChatQnA

Issues

Addresses: #560 #962 #963

Type of change

List the type of change like below. Please delete options that are not relevant.

  • [ x ] Documentation

Dependencies

List the newly introduced 3rd party dependency if exists.

Tests

Validated deployments following Terraform/Ansible Modules README.md

chensuyue and others added 2 commits October 16, 2024 12:47
Signed-off-by: chensuyue <suyue.chen@intel.com>
Signed-off-by: lucasmelogithub <lucas.melo@intel.com>
Signed-off-by: lucasmelogithub <lucas.melo@intel.com>
@mkbhanda
Copy link
Collaborator

Please publish your scripts in the OPEA repo. That way OPEA is self contained and the launch scripts are readily available through just a purview of the repository, beyond embedded in a readme file. Do consider naming the script OPEA single node VM or something to that effect and add some text perhaps that suggests number of vCPUs, disk size based on model or example pipeline, so its generic and can be used for more than ChatQnA, re-use being my intent. Also anticipating these scripts changing a bit as other handware vendors join the effort.

@lucasmelogithub
Copy link
Author

Please publish your scripts in the OPEA repo. That way OPEA is self contained and the launch scripts are readily available through just a purview of the repository, beyond embedded in a readme file. Do consider naming the script OPEA single node VM or something to that effect and add some text perhaps that suggests number of vCPUs, disk size based on model or example pipeline, so its generic and can be used for more than ChatQnA, re-use being my intent. Also anticipating these scripts changing a bit as other handware vendors join the effort.

Feedback received, I'm thinking through it and will propose a change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants