VirtualTam's bookmarks
43 bookmarks found
-
Article series:
- Testing Microservices, the sane way
- Testing in Production, the safe way
- Testing in Production: the hard parts
Presentations:
I’m more and more convinced that staging environments are like mocks - at best a pale imitation of the genuine article and the worst form of confirmation bias.
It’s still better than having nothing - but “works in staging” is only one step better than “works on my machine”.
-
-
Container setup:
- https://gist.github.com/netdesk/c1db2985b542f9916995139318e5a7ce
- https://hub.docker.com/r/jwilder/nginx-proxy/
- https://hub.docker.com/r/jrcs/letsencrypt-nginx-proxy-companion/
Gitlab settings:
- https://docs.gitlab.com/omnibus/docker/
- https://docs.gitlab.com/ce/administration/environment_variables.html
- https://docs.gitlab.com/omnibus/settings/ssl.html
- https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template
Performance considerations:
- https://docs.gitlab.com/omnibus/settings/memory_constrained_envs.html (skip the
cgroups
section for Gitaly as we are already running in a container) - https://docs.gitlab.com/ee/update/#gitaly-omnibus-gitlab-configuration-structure-change for Gitlab 16 changes to Gitaly configuration
-
xkcd: Python Environment
2018-05-02 -
Here are the steps I used to migrate a CentOS 7 VM from (presumably?) an ESXi server, to a local VirtualBox environment.
The LVM volumes were not detected at boot, and after the boot timeout, the OS fell back to the Dracut emergency shell.
- get a CentOS minimal installation CD
- check the VM's resources and peripherals:
- ensure there are no floppy drives (!)
- setup CPU and RAM resources
- check virtual drives
- add an SCSI optical drive if needed
- optional: convert the virtual drive images from VMDK to VDI
- mount the CentOS installation disc
- boot on the installation disc:
- select "Troubleshooting", then "Rescue"
- let the rescue utility detect filesystems and mountpoints
$ chroot
to the detected environment- backup files:
/etc/fstab
/boot/grub/grub.cfg
- under /boot, backup the initrd and initramfs for the current configuration (these will be overwritten)
- compare the current
/etc/fstab
with the output of$ lsblk
and$ blkid
- if needed, manually edit /etc/fstab to use the appropriate block device UUIDs, identifiers and mountpoints
- regenerate GRUB configuration:
$ grub2-mkconfig -o /boot/grub2/grub.cfg
- if needed, reinstall GRUB:
$ grub-install /dev/sda
- rebuild initrd:
$ mkinitrd --force /boot/<initrd_image> <kernel_version>
- rebuild initramfs:
$ dracut --force <kernel_version>
- exit the chroot
- unmount the installation disc
- reboot
- optional but highly recommended: cross your fingers
- ...
- profit!