1. 30 Sep, 2021 1 commit
  2. 28 Sep, 2021 1 commit
  3. 09 Sep, 2021 1 commit
  4. 12 Aug, 2021 1 commit
  5. 05 Jul, 2021 2 commits
    • Łukasz Nowak's avatar
      playbook: Introduce nexedi-laptop playbook · 1b9e724c
      Łukasz Nowak authored
      The general idea is to provide a machine connected to re6st, registered as
      computer in SlapOS Master and with thorwable user to work on it.
      
      Starting from default installation some uneeded packages are removed, and
      few expected ones are added in order to have common set of packages and use
      scenarios across all installations.
      1b9e724c
    • Łukasz Nowak's avatar
      playbook: Ignore ntp check · c52084b5
      Łukasz Nowak authored
      It's not possible on Ubuntu/Focal
      c52084b5
  6. 01 Jul, 2021 2 commits
  7. 30 Jun, 2021 1 commit
  8. 14 Jun, 2021 1 commit
  9. 03 Jun, 2021 1 commit
  10. 01 Jun, 2021 1 commit
  11. 27 May, 2021 1 commit
    • Łukasz Nowak's avatar
      playbook: Sekeltonize rapid.space-vps-brute-capri playbook · f893455c
      Łukasz Nowak authored
      Additional role rapid-space-vps-base is added for furhter extensions.
      
      Unfortunately a lot of various approaches is needed:
      
       * ini_file for oneline manipulation
       * blockinfile for adding a section
       * lineinfile for uncommenting
      
      Note: it was discovered, that some specific parts are just missing in
      vifib-server, so add them there.
      f893455c
  12. 21 May, 2021 1 commit
  13. 07 May, 2021 1 commit
  14. 05 May, 2021 1 commit
  15. 17 Mar, 2021 1 commit
  16. 15 Mar, 2021 1 commit
  17. 12 Mar, 2021 2 commits
  18. 04 Feb, 2021 2 commits
  19. 29 Jan, 2021 1 commit
  20. 25 Jan, 2021 1 commit
  21. 28 Dec, 2020 2 commits
  22. 04 Dec, 2020 1 commit
  23. 25 Nov, 2020 1 commit
  24. 19 Nov, 2020 1 commit
  25. 16 Nov, 2020 1 commit
  26. 13 Nov, 2020 2 commits
    • Kirill Smelkov's avatar
      playbook: debian{9,10}: Track distro kernel updates · 177c353e
      Kirill Smelkov authored
      Debian 9 and Debian10 ship linux-4.9.x and linux-4.19.x correspondingly.
      However kernel packages on those distributions include ABINAME as
      package version, for example linux-image-4.9.0-13-amd64
      means linux 4.9.x with ABINAME=13.
      
      The ABINAME is there because Linux sometimes breaks ABI compatibility in
      small places and Debian is very strict on not throwing ABI changes onto
      users unless requested.  However even with that protection Debian
      "strongly recommends" to explicitly install just linux-image-amd64 -
      without ABINAME - which is just a dependency package that depends on the
      latest kernel in particular distribution series:
      
      https://wiki.debian.org/DebianKernelABIChanges
      
      The reason for this recommendation is that upstream Linux rarely breaks
      any ABI and even if there is a breakage it is so small and in obscure
      places that in practice it does not affect people.
      
      Today, for Debian9, we are explicitly requesting to install Linux 4.9
      with ABINAME=13. That stops on 4.9.228 while current Linux 4.9 is
      4.9.240 bumped to ABI 14. Before ABI=13, we were requesting to install
      ABI=11 which stopped on 4.9.189 and was v↑'ed in 1f249bf7 (playbook:
      debian9: kernel v↑  (4.9.189-3 -> 4.9.228-1). In other words by
      explicitly specifying linux ABINAME we prevent to keep on updating Linux
      kernel to latest _stable_ updates provided by upstream Linux and the
      distribution.
      
      Another inconvenience of installing Linux with explicit ABINAME is
      interaction with nxd-fuse.ko: this module comes with nxd-fuse-dkms
      package, which uses dkms to build itself, and dkms recommends
      linux-headers-amd64 for modules that it manages to be able to build.
      
      However we recently saw an issue when linux-headers-amd64 was installed
      as latest and depending on linux-headers-14-amd64 (NOTE ABINAME=14),
      while the kernel on that server was only linux-image-4.9.0-13-amd64
      (NOTE ABINAME=13) as requested by our playbook. As the result nxd-fuse
      was skipped to compile, failed to be loaded and FUSE became non-working
      on that machine:
      
          nexedi/slapos.package!132 (comment 120438)
      
          root@rapidspace-testnode-005:~# apt install nxd-fuse-dkms
          Reading package lists... Done
          Building dependency tree
          Reading state information... Done
          The following NEW packages will be installed:
            nxd-fuse-dkms
          0 upgraded, 1 newly installed, 0 to remove and 105 not upgraded.
          Need to get 0 B/58.8 kB of archives.
          After this operation, 295 kB of additional disk space will be used.
          Selecting previously unselected package nxd-fuse-dkms.
          (Reading database ... 80295 files and directories currently installed.)
          Preparing to unpack .../nxd-fuse-dkms_4.9.nxd3+debian2_all.deb ...
          Unpacking nxd-fuse-dkms (4.9.nxd3+debian2) ...
          Setting up nxd-fuse-dkms (4.9.nxd3+debian2) ...
          Loading new nxd-fuse-4.9.nxd3+debian2 DKMS files...
          Building for 4.9.0-13-amd64
          Module build for kernel 4.9.0-13-amd64 was skipped since the
          kernel headers for this kernel does not seem to be installed.
      
      -> Fix it by requiring only linux-image-amd64 without specifying ABINAME and
      relying on upstream Linux and distro to provide stable updates for the kernel.
      177c353e
    • system_user's avatar
      Add johan public key · 92076a35
      system_user authored
      92076a35
  27. 20 Oct, 2020 2 commits
  28. 13 Oct, 2020 1 commit
  29. 12 Oct, 2020 2 commits
  30. 09 Oct, 2020 1 commit
  31. 07 Oct, 2020 1 commit
  32. 05 Oct, 2020 1 commit