Download free

Install on OpenStack

Upload the image to Glance, give gate42 a WAN and a LAN network, and start it.

This is the setup we test every release on: gate42 with its WAN on a cloud network behind a floating IP, and its own LAN network with a client behind it. The commands use the openstack client; the dashboard (Horizon) has the same settings.

1. Upload the image

openstack image create gate42-1.8.2 \
  --disk-format qcow2 --container-format bare --file gate42-1.8.2-b17-amd64.qcow2 \
  --min-disk 10 --min-ram 2048 \
  --property hw_disk_bus=virtio --property hw_vif_model=virtio \
  --property hw_qemu_guest_agent=yes --property os_distro=freebsd

On clouds with Ceph storage, a raw image starts faster: convert it first with qemu-img convert -O raw gate42-1.8.2-b17-amd64.qcow2 gate42.raw, then upload gate42.raw with --disk-format raw.

2. The LAN network

gate42 is the LAN's router and DHCP server, so the LAN network has no OpenStack DHCP and no OpenStack gateway, and its ports have no port security (gate42 forwards traffic for other addresses):

openstack network create gate42-lan --disable-port-security
openstack subnet create gate42-lan --network gate42-lan \
  --subnet-range 192.168.1.0/24 --gateway none --no-dhcp
openstack port create gate42-lan --network gate42-lan \
  --fixed-ip subnet=gate42-lan,ip-address=192.168.1.1

3. The WAN port

On your cloud network, with a security group that lets only your own addresses reach the web GUI:

openstack security group create gate42-wan
openstack security group rule create gate42-wan --ingress --protocol tcp \
  --dst-port 8443 --remote-ip 203.0.113.0/24      # your office or VPN addresses
openstack port create gate42-wan --network <your network> --security-group gate42-wan

4. Start gate42

The first port is NIC 1, the WAN:

openstack server create gate42 --image gate42-1.8.2 --flavor <2 vCPU, 4 GB> \
  --nic port-id=$(openstack port show gate42-wan -f value -c id) \
  --nic port-id=$(openstack port show gate42-lan -f value -c id)
openstack floating ip create <external network> --port gate42-wan

After one to two minutes, the console log shows the root password:

openstack console log show gate42 | grep 'first boot'

If your cloud returns no console log, open the VNC console in the dashboard. Then log in at https://<floating IP>:8443 (first login).

5. Machines behind gate42

Give your VMs a port on gate42-lan. They take their address, gateway and DNS from gate42 by DHCP. The LAN has no OpenStack metadata service, so start them with a config drive (--config-drive true) if they use cloud-init.

Notes

  • MTU: cloud networks often have an MTU below 1500 (1442 or 1450). gate42's WAN takes it from OpenStack's DHCP. The LAN does not yet: set the LAN network's MTU (openstack network show gate42-lan -c mtu) under Interfaces › LAN › MTU, and give it to the machines behind gate42 as the DHCP option mtu [26] (Services › Dnsmasq DNS & DHCP › DHCP options).
  • Secure Boot: gate42 boots with BIOS or UEFI, but not with Secure Boot.