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

Drop aws terraform files #840

Merged
merged 3 commits into from
Aug 1, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 3 additions & 9 deletions INSTALL.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Project is arranged as monorepository. Each of sub-modules has it's own installation instructions.

## Client (QuantumServerless) library
## Client (Quantum-Serverless) library

```shell
pip install quantum_serverless
Expand Down Expand Up @@ -43,14 +43,8 @@ For the first one, **Locally**. You will need to have a k8s approach installed i

If this is your case you just need to execute the helm configuration on you k8s instance following the installation step described in the helm's [README](./infrastructure/helm/quantum-serverless/README.md).

If you are interested into manage the infrastructure in a **cloud provider** the project supports two of them, currently: [IBM Cloud](./infrastructure/terraform/ibm/), [AWS](./infrastructure/terraform/aws).
If you are interested into manage the infrastructure in a **cloud provider** the project currently supports [IBM Cloud](./infrastructure/terraform/ibm/).

Once time you select one you will need to run the terraform configuration as is described in the terraform's [README](./infrastructure/terraform/README.md). Depending of the provider that you decide to use you will neeed to refer to the documentation of each provider to see if you need to configure something:
- [IBM Cloud](./infrastructure/terraform/ibm/README.md)
- [AWS](./infrastructure/terraform/aws/readme.md)
You will need to run the terraform configuration as is described in the terraform's [README](./infrastructure/terraform/README.md). You will neeed to refer to the documentation of [IBM Cloud](./infrastructure/terraform/ibm/README.md) to see if you need to configure something.

:warning: Each provider has a `values.yaml` with the configuration for the helm execution. In case you use `terraform` you will need to fill those files with the information from the [second step](#configure-helm-values).

## Manager

All you will need to build the docker image inside the [manager folder](./manager/). You can follow the `docker build` examples described in the docker's README for that or simply run `make build-manager`.
9 changes: 0 additions & 9 deletions docs/deployment/cloud.rst
Original file line number Diff line number Diff line change
Expand Up @@ -97,8 +97,6 @@ In this step your only requirement is to have a *k8s cluster* available. You hav
* Docker desktop offers you a simple one. You just need to go to the "Docker desktop settings" > "Kubernetes section" and click in the option that says: "Enable Kubernetes".
* Create a cluster in a third party cloud service. Some examples from where you can take inspiration are:
* `IBM Cloud cluster <https://cloud.ibm.com/docs/containers?topic=containers-clusters&interface=ui>`_
* `Amazon EKS cluster <https://docs.aws.amazon.com/eks/latest/userguide/create-cluster.html>`_
* `Azure AKS cluster <https://learn.microsoft.com/en-us/azure/aks/tutorial-kubernetes-deploy-cluster?tabs=azure-cli>`_

Once your cluster is ready, the installation is relatively straightforward with Helm. To install a released version, You just need to access to your cluster
and run the next commands:
Expand Down Expand Up @@ -155,16 +153,12 @@ This approach is useful if you have a cloud provider account and also need to se

First, create an account with some cloud provider:
* `IBM Cloud registration process <https://cloud.ibm.com/registration>`_
* `AWS registration process <https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/>`_
* Azure will be supported in a future release.

Once you have created an account, you will need to configure an API key/access key:
* `IBM Cloud API key creation <https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=ui#create_user_key>`_
* `AWS Access key creation <https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-about>`_

Finally, install the provider's CLI:
* `IBM Cloud CLI <https://cloud.ibm.com/docs/cli?topic=cli-getting-started>`_
* `AWS CLI <https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html>`_

Now that your cloud provider is configured, you may configure ``terraform`` to
deploy the infrastructure where you want. Depending on the provider, you need to
Expand All @@ -181,8 +175,6 @@ with the following contents:

* Note the `region <https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cloudfunctions_regions>`_ and the `resource group <https://cloud.ibm.com/docs/account?topic=account-rgs&interface=cli>`_ associated with your account.

To use **AWS**, configure environment variables, depending on your system, in accordance with the instructions `here <https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html#envvars-set>`_.

To confirm the configuration just run ``terraform plan``:

.. code-block::
Expand All @@ -199,7 +191,6 @@ Finally, deploy the plan to your account:

When the process finishes, you should be able to see the cluster with the resources in your provider information:
* `IBM Cloud cluster access guide <https://cloud.ibm.com/docs/containers?topic=containers-access_cluster>`_
* `AWS cluster connection guide <https://aws.amazon.com/premiumsupport/knowledge-center/eks-cluster-connection/>`_

Now that you have a cluster you can follow the steps in the :ref:`helm-deployment` section for using helm to deploy the different applications.

Expand Down
1 change: 0 additions & 1 deletion infrastructure/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,5 @@ In [this folder](./helm) you will find the main configuration to set up your k8s
## Terraform
The [folder](./terraform) contains the configuration that helps you to create your k8s and Ray clusters. Currently, the project supports deployments in:
- [IBM Cloud](https://cloud.ibm.com/login)
- [AWS](https://aws.amazon.com/)

:memo: For more advanced ways to deploy the project you have the guide: [Multi cloud deployment](https://qiskit-extensions.github.io/quantum-serverless/guides/08_multi_cloud_deployment.html).
6 changes: 2 additions & 4 deletions infrastructure/terraform/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,9 @@

This folder will provide you a set of configurations to deploy your k8s cluster and minimum requirements to be able to run the project.

Right now the project supports two platforms where you can deploy the infrastructure:
- [IBM Cloud](./ibm)
- [AWS](./aws)
Right now the project supports deploying the infrastructure to [IBM Cloud](./ibm):

In each folder you will find all the documentation to be able to run the configuration in each platform. For that we are using `terraform`.
In the folder you will find all the documentation to be able to run the configuration. For that we are using `terraform`.

### Plan

Expand Down
195 changes: 0 additions & 195 deletions infrastructure/terraform/aws/.terraform.lock.hcl

This file was deleted.

Loading