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

add some steps to HA dev setup #1518

Merged
merged 1 commit into from
Nov 26, 2023
Merged
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
50 changes: 36 additions & 14 deletions doc/ha/dev-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,32 +70,54 @@ ziti pki create server --pki-root ./pki --ca-name ctrl3 --dns localhost --ip 127
## Running the Controllers

1. The controller configuration files have relative paths, so make sure you're running things from this directory.
2. Start all three controllers
1. `ziti controller run ctrl1.yml`
2. `ziti controller run ctrl2.yml`
3. `ziti controller run ctrl3.yml`
4. All three are configured with `minClusterSize` of 3, so they will wait to be joined to a raft cluster
5. The ctrl1.yml config file has the other two controllers as bootstrap members, so when it starts the first controller will start trying form the raft cluster.
3. Initialize the edge using the agent
1. `ziti agent controller init <pid of any controller> admin admin 'Default Admin'`
2. You can of course use different values if you desire

You should now have a three node cluster running. You can log into each controller individually.
2. Start all three controllers.

```bash
ziti controller run ctrl1.yml
ziti controller run ctrl2.yml
ziti controller run ctrl3.yml
```

All three are configured with `minClusterSize` of 3, so they will wait to be joined to a raft cluster.
The ctrl1.yml config file has the other two controllers as bootstrap members, so when it starts the first
controller will start trying form the raft cluster.

qrkourier marked this conversation as resolved.
Show resolved Hide resolved
3. Call `ctrl1` to add `ctrl2`, `ctrl3` to the cluster by `ctrl.listener`.

```bash
ziti agent cluster --app-id ctrl1 add tls:127.0.0.1:6363
ziti agent cluster --app-id ctrl1 add tls:127.0.0.1:6464
```

4. Inspect the cluster.

```bash
ziti agent cluster list --app-id ctrl1
```

5. Initialize the edge administrator.

```bash
ziti agent controller init admin admin 'Default Admin' --app-id ctrl1
```

You should now have a three node cluster running. You can log into each controller individually with separate named CLI profiles.

1. `ziti edge login localhost:1280`
2. `ziti edge -i ctrl2 login localhost:1380`
3. `ziti edge -i ctrl3 login localhost:1480`

You could then create some model data on any controller:
You could then create some model data on any controller. These demos will run to completion and print built-in
documentation about the actions performed.

```
```bash
ziti demo setup echo client
ziti demo setup echo single-sdk-hosted
```

Any view the results on any controller

```
```bash
ziti edge ls services
ziti edge -i ctrl2 ls services
ziti edge -i ctrl3 ls services
Expand Down
Loading