Skip to content

Commit

Permalink
Update image (#1653)
Browse files Browse the repository at this point in the history
  • Loading branch information
FyzHsn authored May 17, 2023
1 parent 2b77a47 commit 9d9041e
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 11 deletions.
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Clarify installation instructions for SLURM plugin in Read the Docs (x2).
- Fix waiting order of electrons in docs inside snippet for adding a dependency when inputs and outputs are independent.
- Expose GCP Batch executor RTD.
- Add GCP Batch executor image in RTD.

### Fixed

Expand Down
Binary file added doc/source/api/executors/GCP_Batch.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
14 changes: 3 additions & 11 deletions doc/source/api/executors/gcpbatch.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
Google Batch Executor
""""""""""""""""""""""""

.. image:: Azure_Batch.png
.. image:: GCP_Batch.png

Covalent Google Batch executor is an interface between Covalent and `Google Cloud Platform's Batch compute service <https://cloud.google.com/batch/docs/get-started>`_. This executor allows execution of Covalent tasks on Google Batch compute service.

Expand Down Expand Up @@ -228,7 +228,7 @@ To run the scripts manually, users must first authenticate with Google cloud via
gcloud auth print-access-token
Once the user has authenticated, the infrastructure can be deployed by running the Terraform commands in the `infra` folder of the plugin's repository.
Once the user has authenticated, the infrastructure can be deployed by running the Terraform commands in the ``infra`` folder of the plugin's repository.

.. code:: shell
Expand All @@ -239,17 +239,9 @@ Once the user has authenticated, the infrastructure can be deployed by running t

For first time deployment, the terraform provides must be initialized properly via ``terraform init``.

The HCL scripts also build the base executor docker image and upload it to the artifact registry after it gets created. This way the user need not build and push an image separately as the process is fully automated via Covalent.
The Terraform script also builds the base executor docker image and uploads it to the artifact registry after getting created. This means that users do not have to manually build and push the image.






===========================================
5. Source
===========================================

.. autoclass:: covalent.executor.GCPBatchExecutor
:members:
:inherited-members:

0 comments on commit 9d9041e

Please sign in to comment.