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
8571ed73
Unverified
Commit
8571ed73
authored
4 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
number and flatten the new-node procedure
parent
d25116ac
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tsa/howto/ganeti.mdwn
+57
-56
57 additions, 56 deletions
tsa/howto/ganeti.mdwn
with
57 additions
and
56 deletions
tsa/howto/ganeti.mdwn
+
57
−
56
View file @
8571ed73
...
...
@@ -797,78 +797,79 @@ catastrophic data loss bug in Ganeti or [[drbd]].
### New node
-
To create a new box, follow [[new-machine-hetzner-robot]] but change
the following settings:
1.
To create a new box, follow [[new-machine-hetzner-robot]] but change
the following settings:
* Server: [PX62-NVMe][]
* Location: `FSN1`
* Operating system: Rescue
* Additional drives: 2x10TB HDD (update: starting from fsn-node-05,
we are *not* ordering additional drives to save on costs, see
[ticket 33083](https://trac.torproject.org/projects/tor/ticket/33083) for rationale)
* Add in the comment form that the server needs to be in the same
datacenter as the other machines (FSN1-DC13, but double-check)
* Server: [PX62-NVMe][]
* Location: `FSN1`
* Operating system: Rescue
* Additional drives: 2x10TB HDD (update: starting from fsn-node-05,
we are *not* ordering additional drives to save on costs, see
[ticket 33083](https://trac.torproject.org/projects/tor/ticket/33083) for rationale)
* Add in the comment form that the server needs to be in the same
datacenter as the other machines (FSN1-DC13, but double-check)
[PX62-NVMe]: https://www.hetzner.com/dedicated-rootserver/px62-nvme?country=OTHER
[PX62-NVMe]: https://www.hetzner.com/dedicated-rootserver/px62-nvme?country=OTHER
-
follow the [[new-machine]] post-install configuration
2.
follow the [[new-machine]] post-install configuration
- Network setup:
3. Add the server to the two `vSwitch` systems in [Hetzner Robot web
UI](https://robot.your-server.de/vswitch)
1. Add the server to the two `vSwitch` systems in [Hetzner Robot web UI](https://robot.your-server.de/vswitch)
4. install openvswitch and allow modules to be loaded:
2. install openvswitch and allow modules to be loaded
touch /etc/no_modules_disabled
reboot
apt install openvswitch-switch
touch /etc/no_modules_disabled
reboot
apt install openvswitch-switch
3. Allocate a private IP address in the `30.172.in-addr.arpa` zone for
the node.
5. Allocate a private IP address in the `30.172.in-addr.arpa` zone for
the node.
4
. copy over the `/etc/network/interfaces` from another ganeti node,
changing the `address` and `gateway` fields to match the local
entry.
6
. copy over the `/etc/network/interfaces` from another ganeti node,
changing the `address` and `gateway` fields to match the local
entry.
5
. knock on wood, cross your fingers, pet a cat, help your local
book store, and reboot:
7
. knock on wood, cross your fingers, pet a cat, help your local
book store, and reboot:
reboot
-
Prepare all the nodes by configuring them in puppet. They should
be
in the class `roles::ganeti::fsn` if they are part of the fsn
cluster.
8.
Prepare all the nodes by configuring them in puppet. They should
be
in the class `roles::ganeti::fsn` if they are part of the fsn
cluster.
-
Re-enable modules disabling:
9.
Re-enable modules disabling:
rm /etc/no_modules_disabled
- reboot again
Then the node is ready to be added to the cluster, by running this on
the master node:
puppet agent -t
gnt-node add \
--secondary-ip 172.30.135.2 \
--no-ssh-key-check \
--no-node-setup \
fsn-node-02.torproject.org
If this is an entirely new cluster, you need a different procedure:
gnt-cluster init \
--master-netdev vlan-gntbe \
--vg-name vg_ganeti \
--secondary-ip 172.30.135.1 \
--enabled-hypervisors kvm \
--nic-parameters link=br0,vlan=4000 \
--mac-prefix 00:66:37 \
--no-ssh-init \
--no-etc-hosts \
fsngnt.torproject.org
The above assumes that `fsngnt` is already in DNS.
10. reboot again:
reboot
11. Then the node is ready to be added to the cluster, by running
this on the master node:
puppet agent -t
gnt-node add \
--secondary-ip 172.30.135.2 \
--no-ssh-key-check \
--no-node-setup \
fsn-node-02.torproject.org
If this is an entirely new cluster, you need a different procedure:
gnt-cluster init \
--master-netdev vlan-gntbe \
--vg-name vg_ganeti \
--secondary-ip 172.30.135.1 \
--enabled-hypervisors kvm \
--nic-parameters link=br0,vlan=4000 \
--mac-prefix 00:66:37 \
--no-ssh-init \
--no-etc-hosts \
fsngnt.torproject.org
The above assumes that `fsngnt` is already in DNS.
### cluster config
...
...
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