Each project's network is kept apart from every other, even when they're both yours. Peering opens a route between two of them, so a web server in one project can reach a database in another without going over the internet.
Set it up
- Open Peering at panel.alienxservers.co.uk/cloud/peering. It shows a grid of your projects, with From down the side and To along the top.
- Find the row for the project that starts the connections, and the column for the project it should reach.
- Press Allow in that cell.
It shows Applying while every VM in both projects is updated, then Allowed. If it says Failed, try again. Then connect using the other VM's private address.
How it behaves
- It's one way. "A to B" lets VMs in A open connections to VMs in B. Replies come back, but B can't start anything. If you want both, allow both cells.
- It opens every port. Every VM in the source can reach every port on every VM in the destination. Use the destination VMs' firewall rules to narrow it down.
- It doesn't chain. A to B and B to C doesn't let A reach C.
- It affects other people's VMs. It applies to every VM in both projects, including ones other members made.
Narrowing it down
Peered traffic that reaches a VM falls through to that VM's own inbound rules, and then to the peering block. Allow all inbound, which comes first on a new VM, lets all of it through anyway. To limit a peering on one VM, add your own rules above the peering block and move Allow all inbound out of the way.
If you can't allow it
- Not possible means the two projects are on different clusters, or one of them doesn't have a network yet.
- You need to own or have rights over both projects. Peering with someone else's isn't possible.
- With fewer than two projects you can manage, there's nothing to set up.
Taking it away
Press Revoke in the cell. Access stops straight away, and connections already open will break. The opposite direction isn't changed.