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.

Sign up for GitHub

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

Jump to bottom

Adding important note in the testbed configuration #24

Merged
merged 3 commits into from
Dec 7, 2023
Merged

Adding important note in the testbed configuration #24

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
87d60d1
adjusting testbed instructions
fracappa Nov 28, 2023
6bb39ac
Apply suggestions from code review
frisso Dec 7, 2023
38f06ee
Merge branch 'main' into main
frisso Dec 7, 2023
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
17 changes: 10 additions & 7 deletions testbed/kind/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,17 +7,17 @@

## Getting Started

This guide will help you to install a FLUIDOS Node **Testbed** using KIND (Kubernetes in Docker). This is the easiest way to install FLUIDOS Node on a local machine.
This guide will help you to install a FLUIDOS Node **Testbed** using KIND (Kubernetes in Docker). This is the easiest way to install the FLUIDOS Node on a local machine.

This guide has been made only for testing purposes. If you want to install FLUIDOS Node on a production environment, please follow the [official installation guide](/docs/installation/installation.md)

## What will be installed

This guide will create two different Kubernetes clusters:

- **fluidos-consumer**: This cluster will act as a consumer of the FLUIDOS Node. It will be used to deploy a `solver` example CR which will simulate an Intent resolution request. Through the REAR Protocol it will be able to communicate with the Provider cluster and to receive matching Flavours, reserving the one that best fits the request and purchasing it.
- **fluidos-consumer**: This cluster (a.k.a., FLUIDOS node) will act as a consumer of FLUIDOS resources. It will be used to deploy a `solver` example CR that will simulate an _Intent resolution_ request. This cluster will use the REAR protocol to communicate with the Provider cluster and to receive available Flavours, reserving the one that best fits the request and purchasing it.

- **fluidos-provider**: This cluster will act as a provider of the FLUIDOS Node. It will offer its own Flavours on the specific request made by the consumer, reserving and selling it.
- **fluidos-provider**: This cluster (a.k.a. FLUIDOS node) will act as a provider of FLUIDOS resources. It will offer its own Flavours on the specific request made by the consumer, reserving and selling it.

### Prerequisites

Expand Down Expand Up @@ -47,15 +47,15 @@ cd testbed/kind
chmod +x setup.sh
```

3. Launch the `setup.sh` script
4. Launch the `setup.sh` script

```sh
./setup.sh
```

4. Wait for the script to finish. It will take some minutes.
5. Wait for the script to finish. It will take some minutes.

5. After running the script, you can check the status of the pods in the consumer cluster using the following commands:
6. After running the script, you can check the status of the pods in the consumer cluster using the following commands:

```sh
export KUBECONFIG=consumer/config
Expand Down Expand Up @@ -101,7 +101,7 @@ NAME PROVIDER ID TYPE CPU

Now lets try to deploy a `solver` example CR on the `fluidos-consumer` cluster.

1. Open a new terminal on the repo and move into the `deployments/samples` folder
1. Open a new terminal on the repo and move into the `deployments/node/samples` folder

```sh
cd deployments/node/samples
Expand All @@ -119,6 +119,9 @@ export KUBECONFIG=../../../testbed/kind/consumer/config
kubectl apply -f solver.yaml
```

> **Note**
> Please review the **architecture** field and change it to **amd64** or **arm64** according to your local machine architecture.

4. Check the result of the deployment

```sh
Expand Down