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
3fcf1847
Verified
Commit
3fcf1847
authored
2 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
gnt-dal: disk, network setup (
team#40971
)
parent
35054ead
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
howto/ganeti.md
+21
-7
21 additions, 7 deletions
howto/ganeti.md
with
21 additions
and
7 deletions
howto/ganeti.md
+
21
−
7
View file @
3fcf1847
...
...
@@ -2664,6 +2664,23 @@ the SSH `known_hosts` file, see [SSH key verification failures](#ssh-key-verific
This procedure replaces the
`gnt-node add`
step in the initial setup
of the first Ganeti node when the
`gnt-chi`
cluster was setup:
First, we need to partition the disks. Normally, this would have been
done in the
`setup-storage`
configuration, but we were in a rush:
mdadm --create --verbose --level=10 --metadata=1.2 --raid-devices=6 /dev/md2 /dev/sd[abcdef] &&
cryptsetup luksFormat --key-file=/etc/luks/crypt_dev_md2 /dev/md2 &&
cryptsetup luksOpen --key-file=/etc/luks/crypt_dev_md2 /dev/md2 crypt_dev_md2 &&
pvcreate /dev/mapper/crypt_dev_md2 &&
vgcreate vg_ganeti /dev/mapper/crypt_dev_md2 &&
echo crypt_dev_md2 UUID=$(lsblk -n -o UUID /dev/md2 | head -1) /etc/luks/crypt_dev_md2 luks,discard >> /etc/crypttab &&
update-initramfs -u
Reboot to test the LUKS configuration:
reboot
Initialize the ganeti cluster:
gnt-cluster init \
--master-netdev eth1 \
--nic-parameters link=br0 \
...
...
@@ -2717,7 +2734,7 @@ The [network configuration](#network-configuration) (below) must also be perform
address blocks reserved in the cluster. This is the actual initial
configuration performed:
gnt-network add --network 204.8.99.128/25 --gateway 204.8.99.254 --network6 2620:7:6002::/64 --gateway6 2620:7:6002:1 gnt-dal-01
gnt-network add --network 204.8.99.128/25 --gateway 204.8.99.254 --network6 2620:7:6002::/64 --gateway6 2620:7:6002:
:
1 gnt-dal-01
gnt-network connect --nic-parameters=link=br0 gnt-dal-01 default
Note that we reserve the first
`/25`
(209.44.8.99.0/25) for future
...
...
@@ -2725,12 +2742,9 @@ use. The above only uses the second half of the network in case we
need the rest of the network for other operations. A new network will
need to be added if we run out of IPs in the second half. This also
The following IPs were reserved:
gnt-network modify --add-reserved-ips=204.8.99.254 gnt-dal-01
This is just for the gateway. The node's public addresses are in the
other /25 and do not need to be reserved in this allocation.
No IP was reserved as the gateway is already automatically reserved by
Ganeti. The node's public addresses are in the other /25 and also do
not need to be reserved in this allocation.
### Network configuration
...
...
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