1. 27 Nov, 2020 5 commits
    • Jérome Perrin's avatar
    • Jérome Perrin's avatar
      software/theia: run standalone slapos in a service · 17b4240f
      Jérome Perrin authored
      Until now, standalone subsystem was started as a daemon first time a terminal
      was openned and since it was running as daemon, stopping the theia instance
      did not stop any of the services running in the embedded slapos.
      
      Before nexedi/slapos.core!265 there was
      two supervisor running as daemon:
       - ~/srv/slapos/etc/supervisord.conf which runs slapos proxy etc
       - ~/srv/slapos/inst/etc/supervisord.conf with runs instances in the embedded
         slapos
      After, the second one runs as a service in the first one, but the first one
      was still running as daemon.
      
      This changes so that the first supervisor runs as a service managed by the
      Theia instance, so stopping Theia instance will effectively stop the services.
      
      When upgrading, running instances should continue to run as detached. To
      attach them to the new service, procedure could be something like this
      
      Stop supervisors inside Theia instance:
      
        supervisorctl -c ~/srv/slapos/etc/supervisord.conf shutdown
        supervisorctl -c ~/srv/slapos/inst/etc/supervisord.conf shutdown
      
      Restart slappartX:slapos-standalone-instance-XXX-on-watch from host slapos
      17b4240f
    • Jérome Perrin's avatar
    • Jérome Perrin's avatar
      component/bash-completion: new component · e7ba1f75
      Jérome Perrin authored
      e7ba1f75
    • Jérome Perrin's avatar
      software/theia: set TERMINFO · fd1475c6
      Jérome Perrin authored
      We are observing some segmentation fault with python curses applications
      that might be because the TERMINFO are different from the system one.
      I did not debugged, but since I set this environment variable I did not
      observe any segmentation fault.
      
      By comparing strace, the invocations seems same with or without $TERMINFO.
      In both cases the termcaps from the correct ncurses are selected, this
      just seem to workaround for some reason.
      fd1475c6
  2. 26 Nov, 2020 4 commits
  3. 24 Nov, 2020 3 commits
  4. 20 Nov, 2020 5 commits
  5. 19 Nov, 2020 2 commits
  6. 18 Nov, 2020 6 commits
  7. 16 Nov, 2020 2 commits
  8. 12 Nov, 2020 1 commit
  9. 11 Nov, 2020 4 commits
  10. 10 Nov, 2020 6 commits
    • Jérome Perrin's avatar
      stack/erp5: stop using caucase managed certificate for balancer · 620c9332
      Jérome Perrin authored
      Revert "software/erp5: use a caucase managed certificate for balancer"
      
      This reverts commit 74d18b9d and also follow
      up fixup ( 555b26a2 ).
      
      We are not ready to use caucase here, there are still too many problems with
      caucase (keys are lost at each SR update etc) and design might still evolve,
      so let's go back to self signed certificate for now.
      
      Also remove the promise and the updater, since they are also not working and
      causing problems on instances that have been updated (and where the key no
      longer match the certificate)
      620c9332
    • Jérome Perrin's avatar
      fixup! software/erp5: use a caucase managed certificate for balancer · 555b26a2
      Jérome Perrin authored
      fix balancer CSR generation:
      
      Caucase rerequest uses a CSR *template* and use it to generate
      a new CSR with a new key, so we should not use the actual key to
      generate this CSR, because it is caucase rerequest job to generate
      the key.
      Also, we should be careful not to generate a new CSR every time this
      command run, otherwise a new key will be generated and a new CSR will
      be sent to caucase, but caucase will not sign it automatically (since
      we configure it to sign only one certificate).
      
      This means that the case of IP address changes is currently not
      supported automatically. To support it we would need to:
        - force generation of a new CSR template
        - force caucase rerequester to request a new certificate (by removing
        existing certificate)
        - force caucased to sign the new certificate
      
      This commit also fix indentation and remove simplefile macro that is no longer used
      555b26a2
    • Łukasz Nowak's avatar
      Feature Caddy Frontend Haproxy Active Check · fb49ccdb
      Łukasz Nowak authored
      See merge request nexedi/slapos!837
      fb49ccdb
    • Łukasz Nowak's avatar
      7f2e592d
    • Łukasz Nowak's avatar
      caddy-frontend: Allow to have simple backend · f1351dcb
      Łukasz Nowak authored
      Just running test.py with ip and port allows to expose the internal testing
      backend. IPv4 and IPv6 are supported.
      f1351dcb
    • Łukasz Nowak's avatar
      caddy-frontend: Fix software type usage · cc4d556b
      Łukasz Nowak authored
      By default there is no sense to play with software type, since it's fixed in
      slapos.testing.testcase.
      cc4d556b
  11. 09 Nov, 2020 1 commit
    • Łukasz Nowak's avatar
      caddy-frontend: Dodge lowercasing in profile generation · 3d747c95
      Łukasz Nowak authored
      slapos.cookbook:softwaretype tends to lowercase keys in each section, which
      has been undetected due to using lowercase references of slaves in the tests.
      
      By restructuring information in the sections, and putting slave references
      inside of dumped part of information, now the slave reference case is kept.
      
      Also real care was taken to stabilise published lists by sorting them, as it
      also slipped, that they could be unstable.
      
      Tests has been updated to catch this issue, also other tests were fixed, as
      they had wrong assertions.
      3d747c95
  12. 06 Nov, 2020 1 commit