Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
a400bdda
Unverified
Commit
a400bdda
authored
4 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
establish a network naming policy
parent
cba00472
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
tsa/doc/naming-scheme.mdwn
+18
-0
18 additions, 0 deletions
tsa/doc/naming-scheme.mdwn
tsa/howto/ganeti.mdwn
+13
-0
13 additions, 0 deletions
tsa/howto/ganeti.mdwn
with
31 additions
and
0 deletions
tsa/doc/naming-scheme.mdwn
+
18
−
0
View file @
a400bdda
...
@@ -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
This diff is collapsed.
Click to expand it.
tsa/howto/ganeti.mdwn
+
13
−
0
View file @
a400bdda
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment