SD4H wiki - User contributions [en]

OpenStack Client

2026-05-05T15:27:49Z

Jrdundas: /* Install the openstack client */

==Install the openstack client==
You will need to install and configure the [https://pypi.org/project/python-openstackclient/ openstack client] on your machine.

<tabs>
<tab name="Fedora/RedHat Linux">
You can install the client from you package manager, but the pip install is probably more up to date!
{{Code
|lang="bash"
|contents=
sudo dnf install python-openstackclient.noarch
# test the installation
openstack --version
}}
</tab>
<tab name="Debian/Ubuntu Linux">
You can install the client form you package manager
{{Code
|lang="bash"
|contents=
sudo apt-get install python python-dev python-pip
sudo pip install python-openstackclient
# test the installation
openstack --version
}}
</tab>

<tab name="pip">
This will get you the latest version of the client. You might wish to use a python version/environment manager like pyenv.
{{Code
|lang="bash"
|contents=
pip install python-openstackclient
# test the installation
openstack --version

}}
</tab>

<tab name="OSX">

You need to have [https://brew.sh/ homebew] installed, then the client can be install using pipx
{{Code
|lang="bash"
|contents=
brew install pipx
pipx install python-openstackclient
# test the installation
openstack --version
}}
</tab>

<tab name="windows">
Install your favorite linux distribution
with [https://learn.microsoft.com/en-us/windows/wsl/install-manual Windows Subsystem Linux]
and follow the precedure from another tab :)
</tab>

</tabs>

===Installing Missing Plugins===

Depending on the procedure that was used to install the OpenStask client, some plugin could be missing. They can be added with pip, for example the <code>share</code> subcommand is part of the Manilla plugin:
<syntaxhighlight lang="bash" line>
pip install python-manilaclient
</syntaxhighlight>

A list of the main plugins is available in [https://docs.openstack.org/python-openstackclient/latest/cli/plugin-commands/index.html openstack documentation client page].

==Configure the client==

Once the client is installed you need to configure it so it can connect to Juno. The credentials are first found on[https://juno.calculquebec.ca/ Juno's Horizon web page].

===Use Application Credential===
While you can use your username and password to configure your OpenStack client (see the Get the client rc file below), it is recommended to use application credential to connect to the platform.

On the Juno's web page left side menu, '''click Identity >> Application Credentials'''''Italic text'', then click '''Create Application Credentials'''''Italic text''. This pops up a Creation window. You need to set a Name for the credential, all other entries are optional but we also recommend setting an expiration date for the credential. Note that the credentials are always linked to a ''user'' and cannot be a ''project'' credential without any owner.

Once you are happy with the Name, click '''Create Application Credential'''''Italic text''. This pups up a window with the credential ID and its secret. You can copy that information, but downloading the <code>clouds.yaml</code> file is more convenient.

That file will need some minimal modification to be usable.

<div class="filename">'''File :''' clouds.yaml </div>
<syntaxhighlight lang="yaml" file="clouds.yaml">
clouds:
OpenStack:
auth:
auth_url: https://juno.calculquebec.ca:5000

application_credential_id: <application id>
application_credential_secret: <application secret>
region_name: "RegionOne"
interface: "public"
identity_api_version: 3
auth_type: "v3applicationcredential"
</syntaxhighlight>

You need to replace the <code>OpenStack</code> key with a unique name <code><cred reference></code>; it could be the project name or the credential name, you pick.

The first time you create the credentials, you will need to copy the full file here:

<syntaxhighlight lang="bash">
mkdir ~/.config/openstack/
cp clouds.yaml ~/.config/openstack/
</syntaxhighlight>

But if you already have credentials in place, only change the <code>OpenStack</code> key with <code><cred reference></code> and copy that whole block in your <code>~/.config/openstack/cloud.yaml</code> file.

Then the credentials can be used by setting the <code>OS_CLOUD</code> env var in your session or by using the <code>--os-cloud</code> client flag. For example to list all the networks in your project:

<syntaxhighlight lang="bash">
export OS_CLOUD=<cred reference>
openstack network list
# or
openstack --os-cloud <cred reference> network list
</syntaxhighlight>

===Use your Username and Password===

[[File:Get openstack rc file.gif|caption|frame|none| the RC file from the Juno website]]

Let’s say that we have saved the files here <code> $HOME/id/myproject-openrc.sh.</code>

You can test the connection by listing all the images made available on the platform that can be used out of the box to start VMs.

<syntaxhighlight lang="bash" line>
$ source $HOME/id/myproject-openrc.sh
Please enter your OpenStack Password for project <my-project> as user <my user name>:
# Use the same password that you used to connect to the [https://juno.calculquebec.ca/ Juno web page].
# you can now create the credentials
$ openstack image list
+--------------------------------------+----------------------------------+--------+
| ID | Name | Status |
+--------------------------------------+----------------------------------+--------+
| 8b1f4da1-fc76-4658-b1c0-6cf804b41471 | AlmaLinux-8.10-x64-2024-05 | active |
| dfaf1644-a43b-4e90-8183-57a790d86721 | AlmaLinux-8.9-x64-2023-11 | active |
| dc381bb1-ad39-41d5-90d0-b95b71e845e6 | AlmaLinux-9.3-x64-2023-11 | active |
| 7a6e0a71-3748-49a9-aff7-33723ee087af | AlmaLinux-9.4-x64-2024-05 | active |
| 8afc3889-3430-4609-96a1-c318d4be2c61 | Debian-11.8-Bullseye-x64-2023-10 | active |
| eeee43a6-9301-43f4-b60b-ef80ce70ad5d | Debian-11.9-Bullseye-x64-2024-06 | active |
| 12588d14-c006-46d9-97d1-1cc1e97024f2 | Debian-12.2-Bookworm-x64-2023-10 | active |
| 18eeeba7-9fad-4b15-8d9b-678be2b67a88 | Debian-12.5-Bookworm-x64-2024-06 | active |
| f0580bb8-ff31-4bd4-818a-e5f45897bd1e | Fedora-39-1.5-x64-2023-11 | active |
| e9b7ef77-4d50-4d14-8094-44aa6d40ba83 | Fedora-40-1.14-x64-2024-06 | active |
| 4d533cb2-8179-4bc2-8c54-2e0f065b5137 | Rocky-8.10-x64-2024-06 | active |
| 90894672-707b-4103-8683-f06b9d5a6bd0 | Rocky-8.8-x64-2023-05 | active |
| cef2dcef-5c0d-40f3-9fde-b4d3a26ce8e1 | Rocky-8.9-x64-2023-11 | active |
| f95b59a2-99fd-4b7f-912c-d7f17640a791 | Rocky-9.3-x64-2023-11 | active |
| dcf29959-7404-4677-b24d-c25dfcef8da0 | Ubuntu-20.04.6-Focal-x64-2023-11 | active |
| 09222ea9-a2e2-405e-af14-1d5a59b6eab0 | Ubuntu-22.04.3-Jammy-x64-2023-11 | active |
| 9884ac0b-a05c-4327-b16a-104fabdf74cf | Ubuntu-22.04.4-Jammy-x64-2024-06 | active |
| 512331f0-b039-4e90-be2e-d79765a5b21a | Ubuntu-22.04.Jammy-x46-2023-07 | active |
| d812cc8a-caf9-4237-824c-0660d7654dc1 | Ubuntu-24.04-Noble-x64-2024-06 | active |
+--------------------------------------+----------------------------------+--------+
</syntaxhighlight>

A return value looking like

<syntaxhighlight lang="bash" line >
$ openstack image list
The request you have made requires authentication. (HTTP 401) (Request-ID: req-5305b993-4c73-4a14-8596-a90bf64f293f)
</syntaxhighlight>

Would normaly mean that there is a typo in you pasword, you can source the RC file again to correct your password.

OpenStack Client

2026-05-05T15:26:53Z

Jrdundas: /* Install the openstack client */

==Install the openstack client==
You will need to install and configure the [https://pypi.org/project/python-openstackclient/ openstack client] on your machine.

<tabs>
<tab name="Fedora/RedHat Linux">
You can install the client from you package manager, but the pip install is probably more up to date!
{{Code
|lang="bash"
|contents=
sudo dnf install python-openstackclient.noarch
# test the installation
openstack --version
}}
</tab>
<tab name="Debian/Ubuntu Linux">
You can install the client form you package manager
{{Code
|lang="bash"
|contents=
sudo apt-get install python python-dev python-pip
sudo pip install python-openstackclient
# test the installation
openstack --version
}}
</tab>

<tab name="pip">
This will get you the latest version of the client
{{Code
|lang="bash"
|contents=
pip install python-openstackclient
# test the installation
openstack --version

}}
</tab>

<tab name="OSX">

You need to have [https://brew.sh/ homebew] installed, then the client can be install using pipx
{{Code
|lang="bash"
|contents=
brew install pipx
pipx install python-openstackclient
# test the installation
openstack --version
}}
</tab>

<tab name="windows">
Install your favorite linux distribution
with [https://learn.microsoft.com/en-us/windows/wsl/install-manual Windows Subsystem Linux]
and follow the precedure from another tab :)
</tab>

</tabs>

===Installing Missing Plugins===

Depending on the procedure that was used to install the OpenStask client, some plugin could be missing. They can be added with pip, for example the <code>share</code> subcommand is part of the Manilla plugin:
<syntaxhighlight lang="bash" line>
pip install python-manilaclient
</syntaxhighlight>

A list of the main plugins is available in [https://docs.openstack.org/python-openstackclient/latest/cli/plugin-commands/index.html openstack documentation client page].

==Configure the client==

Once the client is installed you need to configure it so it can connect to Juno. The credentials are first found on[https://juno.calculquebec.ca/ Juno's Horizon web page].

===Use Application Credential===
While you can use your username and password to configure your OpenStack client (see the Get the client rc file below), it is recommended to use application credential to connect to the platform.

On the Juno's web page left side menu, '''click Identity >> Application Credentials'''''Italic text'', then click '''Create Application Credentials'''''Italic text''. This pops up a Creation window. You need to set a Name for the credential, all other entries are optional but we also recommend setting an expiration date for the credential. Note that the credentials are always linked to a ''user'' and cannot be a ''project'' credential without any owner.

Once you are happy with the Name, click '''Create Application Credential'''''Italic text''. This pups up a window with the credential ID and its secret. You can copy that information, but downloading the <code>clouds.yaml</code> file is more convenient.

That file will need some minimal modification to be usable.

<div class="filename">'''File :''' clouds.yaml </div>
<syntaxhighlight lang="yaml" file="clouds.yaml">
clouds:
OpenStack:
auth:
auth_url: https://juno.calculquebec.ca:5000

application_credential_id: <application id>
application_credential_secret: <application secret>
region_name: "RegionOne"
interface: "public"
identity_api_version: 3
auth_type: "v3applicationcredential"
</syntaxhighlight>

You need to replace the <code>OpenStack</code> key with a unique name <code><cred reference></code>; it could be the project name or the credential name, you pick.

The first time you create the credentials, you will need to copy the full file here:

<syntaxhighlight lang="bash">
mkdir ~/.config/openstack/
cp clouds.yaml ~/.config/openstack/
</syntaxhighlight>

But if you already have credentials in place, only change the <code>OpenStack</code> key with <code><cred reference></code> and copy that whole block in your <code>~/.config/openstack/cloud.yaml</code> file.

Then the credentials can be used by setting the <code>OS_CLOUD</code> env var in your session or by using the <code>--os-cloud</code> client flag. For example to list all the networks in your project:

<syntaxhighlight lang="bash">
export OS_CLOUD=<cred reference>
openstack network list
# or
openstack --os-cloud <cred reference> network list
</syntaxhighlight>

===Use your Username and Password===

[[File:Get openstack rc file.gif|caption|frame|none| the RC file from the Juno website]]

Let’s say that we have saved the files here <code> $HOME/id/myproject-openrc.sh.</code>

You can test the connection by listing all the images made available on the platform that can be used out of the box to start VMs.

<syntaxhighlight lang="bash" line>
$ source $HOME/id/myproject-openrc.sh
Please enter your OpenStack Password for project <my-project> as user <my user name>:
# Use the same password that you used to connect to the [https://juno.calculquebec.ca/ Juno web page].
# you can now create the credentials
$ openstack image list
+--------------------------------------+----------------------------------+--------+
| ID | Name | Status |
+--------------------------------------+----------------------------------+--------+
| 8b1f4da1-fc76-4658-b1c0-6cf804b41471 | AlmaLinux-8.10-x64-2024-05 | active |
| dfaf1644-a43b-4e90-8183-57a790d86721 | AlmaLinux-8.9-x64-2023-11 | active |
| dc381bb1-ad39-41d5-90d0-b95b71e845e6 | AlmaLinux-9.3-x64-2023-11 | active |
| 7a6e0a71-3748-49a9-aff7-33723ee087af | AlmaLinux-9.4-x64-2024-05 | active |
| 8afc3889-3430-4609-96a1-c318d4be2c61 | Debian-11.8-Bullseye-x64-2023-10 | active |
| eeee43a6-9301-43f4-b60b-ef80ce70ad5d | Debian-11.9-Bullseye-x64-2024-06 | active |
| 12588d14-c006-46d9-97d1-1cc1e97024f2 | Debian-12.2-Bookworm-x64-2023-10 | active |
| 18eeeba7-9fad-4b15-8d9b-678be2b67a88 | Debian-12.5-Bookworm-x64-2024-06 | active |
| f0580bb8-ff31-4bd4-818a-e5f45897bd1e | Fedora-39-1.5-x64-2023-11 | active |
| e9b7ef77-4d50-4d14-8094-44aa6d40ba83 | Fedora-40-1.14-x64-2024-06 | active |
| 4d533cb2-8179-4bc2-8c54-2e0f065b5137 | Rocky-8.10-x64-2024-06 | active |
| 90894672-707b-4103-8683-f06b9d5a6bd0 | Rocky-8.8-x64-2023-05 | active |
| cef2dcef-5c0d-40f3-9fde-b4d3a26ce8e1 | Rocky-8.9-x64-2023-11 | active |
| f95b59a2-99fd-4b7f-912c-d7f17640a791 | Rocky-9.3-x64-2023-11 | active |
| dcf29959-7404-4677-b24d-c25dfcef8da0 | Ubuntu-20.04.6-Focal-x64-2023-11 | active |
| 09222ea9-a2e2-405e-af14-1d5a59b6eab0 | Ubuntu-22.04.3-Jammy-x64-2023-11 | active |
| 9884ac0b-a05c-4327-b16a-104fabdf74cf | Ubuntu-22.04.4-Jammy-x64-2024-06 | active |
| 512331f0-b039-4e90-be2e-d79765a5b21a | Ubuntu-22.04.Jammy-x46-2023-07 | active |
| d812cc8a-caf9-4237-824c-0660d7654dc1 | Ubuntu-24.04-Noble-x64-2024-06 | active |
+--------------------------------------+----------------------------------+--------+
</syntaxhighlight>

A return value looking like

<syntaxhighlight lang="bash" line >
$ openstack image list
The request you have made requires authentication. (HTTP 401) (Request-ID: req-5305b993-4c73-4a14-8596-a90bf64f293f)
</syntaxhighlight>

Would normaly mean that there is a typo in you pasword, you can source the RC file again to correct your password.

Networking

2026-03-17T14:23:19Z

Jrdundas: add dhcp req for security groups note

== Basics ==

You can see the current network of your project from the [https://juno.calculquebec.ca/project/network_topology/ Juno webpage]. There you see the three basic networks available to all projects: <code> <myproject>_network </code>, where you VM lands by default, it is the ''local area network'' (LAN) of your project; the <code>Public-Network</code> that is the internet, you see that a router named <code><myproject>_router</code> is connecting your LAN to the internet; <code> CephFS-Network </code> is the CephFS file system network; you need to connect your VM to that network to [https://docs.alliancecan.ca/wiki/CephFS access CephFS volumes].

=== Networking & Security Groups ===
To get & retain IP connectivity via DHCP, an instance must be able to receive DHCP leases and renewals. If you are setting custom security groups, be sure to add some rules for DHCP: egress to 0.0.0.0/0 UDP port 67, and ingress from 0.0.0.0/0 UDP port 68. Leases last 12 hours, and if the instance is unable to renew it upon expiry it will lose IP connectivity.

== Share a Network with another OpenStack project ==

There could be situations where it is needed to share a network with the project of a collaborator on SD4H so communication between two servers belonging to different projects, also called tenants, can be done without having to resort to the internet.

=== Create a new network ===
You can create a network from the Create network button from both the <code> Network Topology</code> tab. Pick the name of the network with <code>Enable Admin State </code> and <code>Create Subnet box checked</code>, click next, pick a name for the subnet, in <code>Network Address Source</code> select <code>Allocate Network Address from a pool </code>, select the 172.16.0.0/12 pool and use the needed <code> Network Mask </code>, 24 will give you 256 addresses, click Next, make sure Enable DHCP is checked and click Create. You now have a new network. You can attach an existing VMs to that new network in the <code>Instance</code> tab by selecting <code> Attach Interface</code> in the <code>Actions</code> drop down menu of the instance.

Not that VMs that will be solely attached to that network will have no internet access. You need to attach the router that has access to the Public-Network to the network to give it access to the internet.

=== Share the network with another tenant ===

This step can only be made with the [[OpenStack Client]], start by following the client's [[OpenStack_Client#Install_the_openstack_client|installation and configuration procedure]]. You also need the project ID of the tenant that will get access right to your network. The project ID can be found in the [https://juno.calculquebec.ca/identity/ identity tab] of the Juno platform web site by clicking on the Projects menu. In this example, all code is run for the <code>po-test</code> projet, we will share the <code> share-net</code> network with the ''target project'' <code> c3g-dev</code>, <code> id = b84ceb857d8f40feb7eed5e972ec0e56</code>.

Let’s start by looking at the networks of the <code>po-test</code> project:

<syntaxhighlight lang="bash" line>
$openstack network list
+--------------------------------------+-----------------+--------------------------------------+
| ID | Name | Subnets |
+--------------------------------------+-----------------+--------------------------------------+
| 00b327b4-4fb2-4ed8-a7f2-6ff49e3b7e7c | CephFS-Network | ebe6ed39-2304-457c-a758-c251bae591af |
| 052ea294-5ad8-46a9-a988-8a41688bd155 | po-test_network | 5eb14686-b56a-4628-8218-a3da340fdfae |
| 391bf6f5-ba1d-4262-8b45-dd87d130f3cd | share-net | 9ea97afa-9dc9-4ed1-81d0-ab76d128fcef |
| 68512dd8-ecd5-44fc-8aa4-9d129ad2026d | Public-Network | 5f6c7900-601a-4c92-8bd6-731688164e62 |
+--------------------------------------+-----------------+--------------------------------------+
</syntaxhighlight>

We see the three default networks and <code>share-net</code>, the network that we created in the previous step. We will share it by creating a [https://docs.openstack.org/neutron/latest/admin/config-rbac.html Role-Based Access Control (RBAC)] that targets the project <code>b84ceb857d8f40feb7eed5e972ec0e56</code>

<syntaxhighlight lang="bash" line>

$openstack network rbac create --target-project \
b84ceb857d8f40feb7eed5e972ec0e56 --action access_as_shared \
--type network 391bf6f5-ba1d-4262-8b45-dd87d130f3cd
+-------------------+--------------------------------------+
| Field | Value |
+-------------------+--------------------------------------+
| action | access_as_shared |
| id | e7ffbe71-9b49-4036-8e0a-24d73c199fab |
| object_id | 391bf6f5-ba1d-4262-8b45-dd87d130f3cd |
| object_type | network |
| project_id | ad99d6c3087041bcb6c0fe5f2da54df9 |
| target_project_id | b84ceb857d8f40feb7eed5e972ec0e56 |
+-------------------+--------------------------------------+
</syntaxhighlight>

The target project now sees <share-net> and can attach VMs to it.

<syntaxhighlight lang="bash" line>

$openstack network rbac create --target-project \
b84ceb857d8f40feb7eed5e972ec0e56 --action access_as_shared \
--type network 391bf6f5-ba1d-4262-8b45-dd87d130f3cd
+-------------------+--------------------------------------+
| Field | Value |
+-------------------+--------------------------------------+
| action | access_as_shared |
| id | e7ffbe71-9b49-4036-8e0a-24d73c199fab |
| object_id | 391bf6f5-ba1d-4262-8b45-dd87d130f3cd |
| object_type | network |
| project_id | ad99d6c3087041bcb6c0fe5f2da54df9 |
| target_project_id | b84ceb857d8f40feb7eed5e972ec0e56 |
+-------------------+--------------------------------------+
</syntaxhighlight>

Here is how to list your Network RBACs and how to delete them.

<syntaxhighlight lang="bash" line>
$openstack network rbac list
+--------------------------------------+-------------+--------------------------------------+
| ID | Object Type | Object ID |
+--------------------------------------+-------------+--------------------------------------+
| e7ffbe71-9b49-4036-8e0a-24d73c199fab | network | 391bf6f5-ba1d-4262-8b45-dd87d130f3cd |
+--------------------------------------+-------------+--------------------------------------+
$openstack network rbac delete e7ffbe71-9b49-4036-8e0a-24d73c199fab
</syntaxhighlight>

Store and Share data

2026-01-30T21:02:48Z

Jrdundas: add S3 API endpoint URL

=Intro=
SD4H has a large Object Store. Objects are accessible through a web API via the Rados Gateway (radosgw) service. Both the S3 and swift API standards are supported by the radosgw.

In an Object Store, an object is the equivalent of a file on a posix file system. The object store gives users a lot of flexibility, but the steps to do simple tasks like sharing and transferring data involve somewhat of a learning cure. We propose a procedure here so this curve is as gentle as possible. Once done, the procedure will be both more secure and more flexible than sharing data on a share HPC platform or on some VM owned by your group. You can find more information in our [[Object Store Quick Start]] page.

= Configuring S3 access =

# You first need to have your [[OpenStack Client]] installed and configured.
# Then, with the client you generate an e2c/S3 id and secret

With the client is installed and the RC files downloaded in step 1 you can create the S3 ID and secret.

<syntaxhighlight lang="bash" line>
$ source $HOME/id/myproject-openrc.sh
Please enter your OpenStack Password for project po-test as user poq:
# Use the same password that you used to connect to the [https://juno.calculquebec.ca/ Juno web page].
# you can now create the credentials
$ openstack ec2 credentials create
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| access | XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX |
| links | {'self': 'https://juno.calculquebec.ca:5000/v3/users/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/credentials/OS-EC2/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'} |
| project_id | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| secret | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| trust_id | None |
| user_id | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
</syntaxhighlight>

The important values here are <code>access</code> and <code>secret</code>which are the S3 [aws_]access_key_id and [aws_]secret_access_key respectively. AWS stands for Amazon Web Services, they are the creator of the S3 API.

You probably need an S3 API endpoint as well, use <code><nowiki>https://objets.juno.calculquebec.ca</nowiki></code>
= Manage you S3 buckets with Globus =

See the [[Globus]] documentation

= Use a S3 client to manage your bucket =
There are a few clients that can be used to access Ceph S3 api. We recomend [[rclone]], it is fast and and flexible.

Store and Share data

2026-01-30T20:48:51Z

Jrdundas:

=Intro=
SD4H has a large Object Store. Objects are accessible through a web API via the Rados Gateway (radosgw) service. Both the S3 and swift API standards are supported by the radosgw.

In an Object Store, an object is the equivalent of a file on a posix file system. The object store gives users a lot of flexibility, but the steps to do simple tasks like sharing and transferring data involve somewhat of a learning cure. We propose a procedure here so this curve is as gentle as possible. Once done, the procedure will be both more secure and more flexible than sharing data on a share HPC platform or on some VM owned by your group. You can find more information in our [[Object Store Quick Start]] page.

= Configuring S3 access =

# You first need to have your [[OpenStack Client]] installed and configured.
# Then, with the client you generate an e2c/S3 id and secret

With the client is installed and the RC files downloaded in step 1 you can create the S3 ID and secret.

<syntaxhighlight lang="bash" line>
$ source $HOME/id/myproject-openrc.sh
Please enter your OpenStack Password for project po-test as user poq:
# Use the same password that you used to connect to the [https://juno.calculquebec.ca/ Juno web page].
# you can now create the credentials
$ openstack ec2 credentials create
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| access | XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX |
| links | {'self': 'https://juno.calculquebec.ca:5000/v3/users/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/credentials/OS-EC2/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'} |
| project_id | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| secret | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| trust_id | None |
| user_id | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
+------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
</syntaxhighlight>

The important values here are <code>access</code> and <code>secret</code>which are the S3 [aws_]access_key_id and [aws_]secret_access_key respectively. AWS stands for Amazon Web Services, they are the creator of the S3 API.

= Manage you S3 buckets with Globus =

See the [[Globus]] documentation

= Use a S3 client to manage your bucket =
There are a few clients that can be used to access Ceph S3 api. We recomend [[rclone]], it is fast and and flexible.