Skip to content
Snippets Groups Projects
Unverified Commit a400bdda authored by anarcat's avatar anarcat
Browse files

establish a network naming policy

parent cba00472
No related branches found
No related tags found
No related merge requests found
...@@ -78,3 +78,21 @@ Another naming scheme used for virtual machines is `hoster-locN-ID` ...@@ -78,3 +78,21 @@ Another naming scheme used for virtual machines is `hoster-locN-ID`
This is used for virtual machines at Hetzner that are bound to a This is used for virtual machines at Hetzner that are bound to a
specific location. specific location.
Network naming
==============
Networks also have names. The network names are used in reverse DNS to
designate network, gateway and broadcast addresses, but also in
[[Ganeti]], where networks are managed automatically for virtual
machines.
The first network was named `gnt-fsn`, for `Ganeti in the Falkenstein
datacenter`. Future networks should be named `FUN-LOCNN-ID` (example
`gnt-fsn13-02`) where:
* `FUN` is the function (e.g. `gnt` for [[Ganeti]])
* `LOCNN` is the location (e.g. `fsn13` for Falkenstein)
* `ID` is a two-character number, padded with zero, starting from
one, to distinguish multiple instances at the same
function/location pair
...@@ -870,8 +870,15 @@ system. Say we have `192.0.2.0/24` reserved for the cluster, with ...@@ -870,8 +870,15 @@ system. Say we have `192.0.2.0/24` reserved for the cluster, with
the host IP `192.0.2.100`` and the gateway on `192.0.2.1`. You will the host IP `192.0.2.100`` and the gateway on `192.0.2.1`. You will
create this network with: create this network with:
gnt-network add --network 192.0.2.0/24 --gateway 192.0.2.1 example-network
If there's also IPv6, it would look something like this:
gnt-network add --network 192.0.2.0/24 --gateway 192.0.2.1 --network6 2001:db8::/32 --gateway6 fe80::1 example-network gnt-network add --network 192.0.2.0/24 --gateway 192.0.2.1 --network6 2001:db8::/32 --gateway6 fe80::1 example-network
Note: the actual name of the network (`example-network`) above, should
follow the convention established in [[doc/naming-scheme]].
Then we associate the new network to the default node group: Then we associate the new network to the default node group:
gnt-network connect --nic-parameters=link=br0,vlan=4000,mode=openvswitch example-network default gnt-network connect --nic-parameters=link=br0,vlan=4000,mode=openvswitch example-network default
...@@ -880,6 +887,12 @@ The arguments to `--nic-parameters` come from the values configured in ...@@ -880,6 +887,12 @@ The arguments to `--nic-parameters` come from the values configured in
the cluster, above. The current values can be found with `gnt-cluster the cluster, above. The current values can be found with `gnt-cluster
info`. info`.
For example, the second ganeti network block was assigned with the
following commands:
gnt-network add --network 49.12.57.128/27 --gateway 49.12.57.129 gnt-fsn13-02
gnt-network connect --nic-parameters=link=br0,vlan=4000,mode=openvswitch gnt-fsn13-02 default
## SLA ## SLA
As long as the cluster is not over capacity, it should be able to As long as the cluster is not over capacity, it should be able to
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment