OSCAR CLI

To deploy a service on an OSCAR cluster using the OSCAR CLI, the first step is to add a cluster so you can then manage it. To do this, use the add command. In this case, we will call it oscar-cluster, so from now on, when working with our cluster using OSCAR-CLI, we will refer to it as oscar-cluster. Use the username and password you obtained when deploying the OSCAR cluster. To use the OSCAR-CLI in a local deployment, you must set the --disable-ssl flag at the end to disable the verification of self-signed certificates.

oscar-cli cluster add oscar-cluster https://localhost $OSCARuser $OSCARpass

If you want to use a remote OSCAR cluster that includes access via EGI credentials.

Via OIDC agent:

oscar-cli cluster add oscar-cluster https://oscar-cluster-remote -o oidc-account-name

Via Access Token:

oscar-cli cluster add oscar-cluster https://oscar-cluster-remote -t access-token

The next step is to create the FDL file, which contains all the service configuration. Next, using this .yaml file, you can deploy the service(s) with the following apply command:

oscar-cli apply $yaml_file

Note that there are many other available options, documented in OSCAR CLI's GitHub repository. Using the list command, you can verify if the service was deployed correctly to the cluster.

oscar-cli service list -c oscar-cluster

This returns a list of all services deployed in the cluster.

NAME            IMAGE                   CPU  MEMORY
cowsay          ghcr.io/grycap/cowsay   1    1Gi
...             ....                    ...  ...

With this, the service is deployed and ready to run (see Service Execution section). Alternatively, you can remove the cluster from the OSCAR-CLI tool with the following command:

oscar-cli cluster remove oscar-cluster