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
e1314716
Verified
Commit
e1314716
authored
2 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
move disk partitioning to node installation
That needs to be done everywhere.
parent
3fcf1847
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
+20
-16
20 additions, 16 deletions
howto/ganeti.md
with
20 additions
and
16 deletions
howto/ganeti.md
+
20
−
16
View file @
e1314716
...
...
@@ -2640,6 +2640,25 @@ be reclaimed eventually.
cumin -p 0 'C:roles::ganeti::chi' 'puppet agent -t'
10.
partition the extra disks:
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
Normally, this would have been done in the `setup-storage`
configuration, but we were in a rush.
TODO: `vg_ganeti_nvme` configuration.
11.
Reboot to test the LUKS configuration:
reboot
10.
Then the node is ready to be added to the cluster, by running
this on the master node:
...
...
@@ -2662,22 +2681,7 @@ the SSH `known_hosts` file, see [SSH key verification failures](#ssh-key-verific
### gnt-dal cluster initialization
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
of the first Ganeti node when the
`gnt-chi`
cluster was setup.
Initialize the ganeti cluster:
...
...
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