An error occurred fetching the project authors.
  1. 12 Dec, 2023 1 commit
  2. 28 Aug, 2023 1 commit
  3. 23 Aug, 2023 1 commit
  4. 17 Aug, 2023 1 commit
  5. 26 Jul, 2023 1 commit
  6. 12 Jan, 2023 1 commit
    • Jérome Perrin's avatar
      stack/erp5: also use backup cloudooo by default · a729a677
      Jérome Perrin authored
      We have two public cloudooo instances, https:///cloudooo.erp5.net/ and
      https://cloudooo1.erp5.net/ but the software release uses only the first
      one. This changes to use both instances by default, in a random order.
      This happens for the ERP5 instance and also for the test runner.
      
      This also includes a breaking change: the parameter is renamed from
      `cloudooo-url` into `cloudooo-url-list` and instead of being a coma
      delimited list of URLs, this is now a proper list of URLs.
      
      Some obsolete code and comments about the old `erp5-cloudooo` partition
      that used to part of ERP5 software release have also been removed.
      
      On testing side, ZopeSkinsMixin._setUpClass is changed be made more
      robust, by waiting that all activities are processed and using a new
      xmlrpc client in every iteration ( to prevent issues like the one from
      https://erp5js.nexedi.net/#/test_result_module/20230107-548523A7/10 )
      a729a677
  7. 10 Nov, 2022 1 commit
  8. 15 Jun, 2022 2 commits
    • Jérome Perrin's avatar
      software/erp5: set server timeout in haproxy to match publisher-timeout · d25ab7bd
      Jérome Perrin authored
      Instead of having an hardcoded timeout that users will hit anyway even
      if they increase publisher timeout, set this timeout value to be
      slightly higher than publisher timeout. This way publisher-timeout can
      be used to allow longer requests and it's generally more consistent.
      d25ab7bd
    • Jérome Perrin's avatar
      software/erp5: default publisher-timeout to 5 minutes · 369fa364
      Jérome Perrin authored
      We already had haproxy configured to stop serving requests longer than
      this duration, but the requests was still being processed by zope.
      
      By adding such default in publisher-timeout, zope will stop processing
      the request after the timeout.
      
      This is slightly different behavior, because before this change the
      request was still being processed, even if the client did not get the
      response it may make change to databases.
      Users who want to keep the previous behavior can request with
      publisher-timeout parameter null.
      369fa364
  9. 07 Feb, 2022 1 commit
  10. 22 Dec, 2021 1 commit
    • Vincent Pelletier's avatar
      erp5: Change default timerserver-interval from 5s to 1s. · 6f2c9945
      Vincent Pelletier authored
      5s is the historical default tic periodicity, but 1s is typically used in
      production instances. 1s periodicity should improve validation node
      reactivity in all cases, and general activity reactivity in instances with
      few processing nodes (like development instances).
      6f2c9945
  11. 01 Dec, 2021 1 commit
    • Jérome Perrin's avatar
      stack/erp5: expose random_activity_priority argument of testrunner · 0b7511b4
      Jérome Perrin authored
      By setting this in the test suite configuration, we can force ERP5 tests
      to use random priorities for activity processing.
      
      The intended usage is to set this to an empty string, in which case
      ERP5's runUnitTest chooses a random value for the seed and prints the
      chosen value. It may also be possible to use a value, to reproduce a
      previous run.
      0b7511b4
  12. 15 Jul, 2021 1 commit
  13. 22 Jun, 2021 1 commit
  14. 31 May, 2021 2 commits
  15. 15 Apr, 2021 1 commit
    • Kirill Smelkov's avatar
      stack/erp5 += WCFS service (technology preview) · 48b24182
      Kirill Smelkov authored
      This complements 7f877621 (Move wendelin.core from Wendelin to ERP5) and
      introduces new WCFS service into ERP5 software-release to support
      upcoming wendelin.core 2. Wendelin.core 2 will introduce new WCFS
      filesystem server component that serves in-ZODB arrays data as OS files
      for Zopes to memory-map. Please see the following links for overview of
      what WCFS is and how it interoperates with and serves Python clients:
      
      https://lab.nexedi.com/kirr/wendelin.core/blob/b5fc98bb/wcfs/wcfs.go#L20-247
      https://lab.nexedi.com/kirr/wendelin.core/blob/b5fc98bb/wcfs/client/wcfs.h#L20-96
      
      Implementation notes:
      
      - WCFS is by default disabled in ERP5 - we do not want to load every
        ERP5 user with it in the early days of wendelin.core 2. WCFS service
        will also not work when ERP5 is built with wendelin.core 1, so keeping
        it disabled by default is reasonable for now.
      
      - There is a duplication for instance-erp5.cfg.in in between stack/erp5/
        and software/slapos-master/ . It was negotiated with VIFIB developers
        to go this way instead of first deduplicating instance-erp5.cfg.in
        copying that was started in 87d13789 (slapos-master: Copy files from
        erp5 stack for local changes).
      
      To enable wcfs one can either pass `wcfs` configuration parameter, or
      add the following to a software-release that uses stack/erp5:
      
        [erp5-defaults]
        wcfs-enable-default = true
      
      /cc @rafael, @tomo
      48b24182
  16. 09 Mar, 2021 1 commit
  17. 08 Mar, 2021 5 commits
  18. 03 Mar, 2021 1 commit
  19. 25 Jan, 2021 1 commit
  20. 21 Jan, 2021 1 commit
    • Jérome Perrin's avatar
      software/erp5: Adjust apachedex promise for haproxy · e6087b7d
      Jérome Perrin authored
      Since bd3c2b18 (Remove httpd from ERP5 and use haproxy instead, 2020-12-14)
      timing in balancer access log files are in milliseconds, no longer in
      microseconds as they use to be with apache.
      
      We update apachedex to version 1.8, where it supports generating reports
      from access log files with milliseconds, as long as the expected format is
      passed with --logformat argument.
      
      We changed the default value of apachedex configuration to use the expected
      --logformat argument, but users with a custom apachedex config passed as
      instance parameters (monitor.apachedex-configuration) will have to update
      their request parameters, to also pass --logformat.
      Since this is breaking change, we take this opportunity to introduce another
      breaking change, this parameter is not longer a string with all arguments
      on the same line, which was problematic because these arguments contained
      quotes and backslashes. The arguments are now passed as a list of strings
      which will become the list of arguments passed to apachedex.
      
      This is implemented by generating an apachedex config file, which simplifies
      the generation of the wrapper. For this we also needed to upate
      slapos.toolbox.
      
      The same change is reflected to the overriden profiles in slapos-master,
      but for slapos-master we don't pass the --logformat argument, because
      slapos-master is using httpd, so the logs timings are still in microseconds.
      e6087b7d
  21. 21 Dec, 2020 1 commit
    • Jérome Perrin's avatar
      stack/erp5: new promise to check software release URL of zope instances · a8271791
      Jérome Perrin authored
      When root instance is updated to a new software release URL, it will re-request
      all the instances with the new software release URL.
      To make sure the new root instance does not appear has ready when it is
      re-requested with new software release URL, introduce a promise that will check
      that the instances requested by the root instance have the same software
      release URL. For now we do this only for Zope instances, because they are
      stateless and restart automatically on configuration changes, unlike stateful
      instances like mariadb or ZEO that we don't restart automatically (yet ?).
      a8271791
  22. 07 Dec, 2020 2 commits
    • Jérome Perrin's avatar
      stack/erp5: leave apachedex reports with wrong microsecond timing for now · 06ce6b17
      Jérome Perrin authored
      The apachedex reports when produced on backend will be wrong, because haproxy
      logs timings in milliseconds and apachedex parses as microsecond, but as far as
      I know we produce reports from frontend logs, so it should not really affect
      our operations.
      06ce6b17
    • Jérome Perrin's avatar
      stack/erp5: remove httpd and use haproxy instead · 6a8f58c5
      Jérome Perrin authored
      Two main differences of haproxy are file format for certificates and logs.
      
      HAProxy also uses certificates in PEM format, but it expect its own server
      certificate and the key to be in the same file (although recent version seems
      to accept separate files, we don't use this now) and the CRL and CA certificates
      also all together in the same file.
      We change to use the same file for certificate and key and for CA and CRL, in
      the updater script we we build PEM files by containing all CA certificates and
      all CRL together.
      Also, since haproxy needs to be reloaded when certificate change, we run it in
      master-worker mode, with a pid file so that we can signal it to reload.
      
      For the logs, since haproxy does not log to file, we introduce a rsyslogd to
      log to a file. The log format is same as with httpd, except that timing are not
      in microseconds but in milliseconds - this did not seem to be configurable.
      This is a problem for apachedex reports on log, for that we plan to use an
      updated version of apachedex with support for `%{ms}T` for durations.
      
      HAProxy is configured with same timeouts, except:
       - "connect" timeout has been increased a bit (from 5 to 10s), because the
         comment "The connection should be immediate on LAN" was no longer true, now
         that haproxy is accessed from frontend.
       - the server entries for testrunner are a very long timeout (8h) because some
         ERP5 functional tests exceeed the 305s timeout.
      
      The SSL configuration is with current "modern" config from https://ssl-config.mozilla.org/
      
      Tests have been modified a bit, because haproxy uses HTTP/2.0 and not 1.1
      like httpd was doing several haproxy features (keep alive and gzip
      compression) are only available when backend uses HTTP/1.1, so we adjusted
      tests to use a 1.1 backend.
      
      There was also differences with logs, because of the time being in milliseconds.
      
      TestPublishedURLIsReachableMixin._checkERP5IsReachable was also updated, it
      was working by chance because when accessed behind httpd->haproxy->zope, zope
      was producing a redirect URL that was the URL of haproxy, which could be
      resolved by chance. This test was updated to access zope with a path that
      contains VirtualHostMonster magic, as the shared frontend ( with "zope" software
      type) is supposed to set.
      
      This should hopefuly solve the "502 Proxy Error" that we are observing with httpd.
      6a8f58c5
  23. 04 Nov, 2020 1 commit
  24. 11 May, 2020 1 commit
  25. 19 Nov, 2019 2 commits
  26. 06 Nov, 2019 1 commit
  27. 13 Sep, 2019 1 commit
  28. 09 Sep, 2019 1 commit
  29. 30 Aug, 2019 1 commit
  30. 20 Aug, 2019 1 commit
  31. 13 Aug, 2019 1 commit
  32. 26 Jul, 2019 1 commit