1.0 Configure the controller

1.1 Create a VM to be used as the Controller

It is easier to use resource group to organize and manage all your resources for this demo.
Create a resource group and change into that resource group.
Use + Create button to create a resource.
Azure will take you to the Marketplace screen. In the search bar, type in Ubuntu Server.
Choose "Ubuntu Server 22.04 LTS".

Diagram

On the Create a virtual machine screen.

The Subscription and Resource group should already be filled.
In the Instance details section, enter the VM name.
Select the Region to host your VM.
Leave default Availability options and Security type(Standard).
Leave the selected image Ubuntu Server 22.04 LTS x64 Gen2.
For the Size, choose the appropriate size for your application. For this demo, Standard_B2s(2CPU,4 GB) size was used.

Diagram

Next, choose Authentication type to login to the VM. (We highly discourage login to the VM using Password).
Enter an username (remember the username, you will need it to login to the VM), or leave the default user azureuser
Choose your ssh key
For inbound ports, select the ssh. You can add extra port based on your OpenZiti setup.
You can leave everything default. Press Review + create
After the Validation passed. Press Create to create VM.
Important: If you are creating the network controller, you need to associate an DNS name to the public IP of your VM.
You can do this from "Virtual machine" page.

1.2 Firewall

Azure's firewall is blocking all incoming access to the VM. You will need to open ports you specified for controller and ZAC (if you plan to use ZAC). Here is a example of the firewall ports if you used the default ports (TCP 8440-8443).

Oracle cloud by default blocks all incoming traffic to the VM. You will need to open ports you specified for controller and ZAC (if you plan to use ZAC).

First, we need to Create security group
From the Networking category, select the Virtual cloud networks.
Select the VCN your VM is in.
On the left side menu, select the Network Security Group.
Select Create Network Security Group.
Name the security group and select the next.
Now create rules for ingress traffic.
Port 22/TCP for SSH
OpenZiti ports: 8440-8443/TCP (default ports from quickstart)
Also create a rule to allow all traffic outbound (Egress).

Following is the example of the Security Group for the controller

Diagram

After the security group is created, attach it to the instance.
From the "Instance details" screen, select Edit under the Network security groups section.
Select the security group from the drop down and press Save changes.

Diagram

NOTE 1

Oracle Cloud also uses Security Lists (on the subnet) to marshal the traffic, 
please make sure the setting under Security Lists is not conflicting
with your security group rules.

NOTE 2

It is possible that after the security group configuration, the ufw does not
work correctly on the VM.

You should Turn on ufw and restart the VM after the security group configuration.

ufw must be turned on for traffic to get to the VM.
after ufw is enabled, setup allow traffic for OpenZiti ports:

sudo ufw enable
sudo ufw allow 8440:8443/tcp
sudo shutdown -r 0

Once the VM is created, we can get the IP address (and the DNS name) of the VM from the Virtual machine screen.
Login to the VM by using defined user "username" (default username is azureuser) and the private sshkey:

ssh -i <private_key> <username>@<ip>
or
ssh -i <private_key> <username>@<dns-name>

Use the DNS name to setup the controller with Host OpenZiti Anywhere.

Once the VM is created, we can get the IP address (and the DNS name) of the VM from the Instance detail screen.
NOTE: DNS name is only available if you enabled DNS Hostnames under VPC.
Login to the VM by using user name "ubuntu":

ssh -i <private_key> ubuntu@<ip>
or
ssh -i <private_key> ubuntu@<dns-name>

export the DNS record

export EXTERNAL_DNS=$(dig +short -x $(curl -s icanhazip.com) | sed "s/.$//")

Then follow the Host OpenZiti Anywhere guide to setup the controller.

Once the VM is created, we can login through SSH button on the VM instances screen.
export the DNS record

export EXTERNAL_DNS=$(dig +short -x $(curl -s icanhazip.com) | sed "s/.$//")

Then follow the Host OpenZiti Anywhere guide to setup the controller.

Once the VM is created, we can get the IP address of the droplet from the Resources screen.
Login to the VM by using user "root" and IP address:

ssh root@<ip>

Then follow the Host OpenZiti Anywhere to setup the controller. You must replace the EXTERNAL_DNS with the following command before running the quickstart.

export EXTERNAL_DNS="$(curl -s eth0.me)"

This ensures the Controller setup by the quickstart is advertising the external IP address of the VM.

Once the VM is created, we can get the IP address of the VM from the instance details screen.
Login to the VM by using user name "ubuntu" and the IP address:

ssh -i <private_key> ubuntu@<ip>

Then follow the Host OpenZiti Anywhere to setup the controller. You must replace the EXTERNAL_DNS with the following command before running the quickstart.

export EXTERNAL_DNS="$(curl -s eth0.me)"

This ensures the Controller setup by the quickstart is advertising the external IP address of the VM.

Once the VM is created, we can get the IP address of the VM from the Devices screen.
Login to the VM by using user name "ubuntu" and the IP address:

ssh -i <private_key> ubuntu@<ip>

export the DNS record

export EXTERNAL_DNS=$(dig +short -x $(curl -s icanhazip.com) | sed "s/.$//")

Then follow the Host OpenZiti Anywhere guide to setup the controller.

1.4 Setup Ziti Administration Console (ZAC)

Optional

ZAC provides GUI for managing the OpenZiti network. If you prefer UI over CLI to manage network, please following the ZAC Setup Guide to setup ZAC before going to the next section.

Quickfix:

To setup npm executables, you can follow install Node.js guide.

For example, this is how to install the version of node needed for ZAC.

Setup the repo:

cd ~
curl -sL https://deb.nodesource.com/setup_18.x -o nodesource_setup.sh
sudo bash nodesource_setup.sh

Install nodejs:

sudo apt install nodejs

After the nodejs is installed, following the rest of ZAC Setup Guide to setup ZAC.

1.5 Helpers

Following helpers are needed to complete the guides for router and services.

1.5.1 Add Environment Variables Back to the Shell

Source the environment variables when you log back in the shell

source ~/.ziti/quickstart/$(hostname -s)/$(hostname -s).env

If the environment variables are sourced correctly, you can do the following to check:

echo $ZITI_HOME

Output:

/root/.ziti/quickstart/OMSINER

1.5.2 Change Ziti edge admin password

Find the Current admin edge login password of controller (if you forget the password):

grep "export ZITI_PWD" ~/.ziti/quickstart/$(hostname -s)/$(hostname -s).env

Or if you have environment variable setup correctly:

echo $ZITI_PWD

To update the passwd

ziti edge update authenticator updb -s

Important: if you change the password, you must update the passwd (ZITI_PWD) in the "~/.ziti/quickstart/$(hostname -s)/$(hostname -s).env" file.

1.5.3 Some useful command for the Router

login the CLI

zitiLogin

Verify ER status

ziti edge list edge-routers

Delete the ER

ziti edge delete edge-routers $ROUTER_NAME
ziti edge delete edge-routers $ROUTER_ID

Update the ER

ziti edge update edge-router $ROUTER_NAME [flags]
ziti edge update edge-router $ROUTER_ID [flags]

example to update attributes:

ziti edge update edge-router $ROUTER_NAME -a private

1.0 Configure the controller

1.1 Create a VM to be used as the Controller​

1.2 Firewall​

1.3 Login and Setup Controller​

1.4 Setup Ziti Administration Console (ZAC)​

1.5 Helpers​

1.5.1 Add Environment Variables Back to the Shell​

1.5.2 Change Ziti edge admin password​

1.5.3 Some useful command for the Router​

1.1 Create a VM to be used as the Controller

1.2 Firewall

1.3 Login and Setup Controller

1.4 Setup Ziti Administration Console (ZAC)

1.5 Helpers

1.5.1 Add Environment Variables Back to the Shell

1.5.2 Change Ziti edge admin password

1.5.3 Some useful command for the Router