1. 27 May, 2021 5 commits
  2. 25 May, 2021 2 commits
  3. 24 May, 2021 1 commit
  4. 21 May, 2021 3 commits
  5. 20 May, 2021 2 commits
  6. 19 May, 2021 3 commits
  7. 17 May, 2021 1 commit
  8. 16 May, 2021 1 commit
    • Julien Muchembled's avatar
      ERP5: notebook 4.4.1 does not need argon2-cffi · 12eab3c1
      Julien Muchembled authored
      This fixes:
      
        Installing jupyter.
        While:
          Installing jupyter.
          Base installation request: ...
          Getting distribution for 'argon2-cffi'.
        Error: Picked: argon2-cffi = 20.1.0
      
      Addition of argon2-cffi in commit 7d1ea024
      was a last-minute change to fix jupyter SR.
      12eab3c1
  9. 15 May, 2021 12 commits
  10. 14 May, 2021 3 commits
  11. 12 May, 2021 3 commits
  12. 11 May, 2021 4 commits
    • Julien Muchembled's avatar
    • Łukasz Nowak's avatar
      Merge branch 'feature/edgetest-pop' · 7ae4d31a
      Łukasz Nowak authored
      Edggetest monitoring got capability of region definition in each cluster.
      
      In order to stabilise parameter serialisation the json-in-xml has been used.
      7ae4d31a
    • Łukasz Nowak's avatar
      monitor: Ensure internal safety of section names · e62fe778
      Łukasz Nowak authored
      Slave reference can be dangerous for buildout validity or file names.
      e62fe778
    • Łukasz Nowak's avatar
      monitor: Implement edgetest regions · dadfec3c
      Łukasz Nowak authored
      Request and publication is switched to fully serialised approach, so that
      complex data structures like lists and objects can be safely transmitted.
      
      The requests are backward compatible, so for current and simple usage
      automatic region is setup.
      
      Much more information are published to main and shared instances, like
      lists of available and assigned regions. Regions can be added and removed,
      which will be reflected automatically for the slaves.
      
      Information send to the bot node are minimised to only needed ones.
      
      check-frontend-ip-list can be configured according to the list, and each
      element overrides previous one:
      
       * globally on cluster
       * default per region
       * globally per slave
       * specific per region on slave
      
      Note: It's known that:
      
       {%-     set base_slave_dict = json_module.loads(slave.pop('_')) %} {#- XXX: Unsafe! #}
      
            is really unsafe, but for most of usage of monitoring slaves it's
            considered good enough.
      dadfec3c