An error occurred fetching the project authors.
  1. 16 Oct, 2018 1 commit
  2. 04 Oct, 2018 1 commit
  3. 03 Oct, 2018 1 commit
  4. 10 Sep, 2018 1 commit
    • Jérome Perrin's avatar
      erp5: new `test-runner` instance parameter · e4d1ea03
      Jérome Perrin authored
      We have new parameters "how many parallel tests this instance can run"
      ( test-runner.node-count ) and "how many supplementary databases each
      test needs" ( test-runner.extra-database-count ).
      
      Instead of configuring "I need a total of 15 databases", we configure "I
      need to be able to run 3 tests in parallel, each test requiring 4 extra
      databases" which generates 3 * (4 +1) databases.
      
      `mariadb.test-database-amount` becomes deprecated in favour of these new
      arguments, but compatibility is preserved.
      e4d1ea03
  5. 03 Sep, 2018 1 commit
  6. 23 May, 2018 1 commit
  7. 17 May, 2018 1 commit
  8. 23 Feb, 2018 1 commit
  9. 22 Feb, 2018 2 commits
  10. 21 Feb, 2018 1 commit
  11. 13 Feb, 2018 1 commit
    • Julien Muchembled's avatar
      ERP5: new 'private-dev-shm' zope partition option for wendelin.core · e6bd1e78
      Julien Muchembled authored
      Current version of wendelin.core is limited in that there's no cooperation
      in memory allocation between several processes sharing the same /dev/shm.
      Over time, the distribution of memory among processes becomes more and more
      inequal until some of them get killed due to allocation failure.
      
      This is a temporary solution that relies on user namespaces.
      e6bd1e78
  12. 02 Feb, 2018 1 commit
  13. 03 Nov, 2017 1 commit
  14. 12 Oct, 2017 2 commits
  15. 02 Oct, 2017 1 commit
    • Sebastien Robin's avatar
      Revert "stack/erp5: completely remove cloudooo" · fa05bda4
      Sebastien Robin authored
      This reverts commit 40108537.
      
      Using the public cloudooo for all unit tests makes things
      unreliable, we have every day many tests failing due to this. It
      would be required to reapply this change to :
      - make ERP5 more resilient to network failures when there is
        issues connecting to cloudooo
      - find some automated ways to have a cloudooo per testnode machine,
        with idea of having possibility to request "where is the
        nearest service doing that"
      - possibly having a CDN of cloudooo, but this does not prevent having
        a cloudooo per testnode
      fa05bda4
  16. 27 Sep, 2017 2 commits
  17. 13 Sep, 2017 1 commit
  18. 03 Jul, 2017 1 commit
  19. 21 Jun, 2017 1 commit
  20. 20 Jun, 2017 1 commit
  21. 06 Apr, 2017 1 commit
  22. 22 Mar, 2017 1 commit
  23. 27 Feb, 2017 1 commit
  24. 16 Feb, 2017 1 commit
  25. 26 Oct, 2016 1 commit
  26. 26 Aug, 2016 1 commit
  27. 25 Aug, 2016 1 commit
  28. 12 May, 2016 1 commit
  29. 04 Apr, 2016 1 commit
  30. 01 Feb, 2016 1 commit
    • Kirill Smelkov's avatar
      ERP5 and Jupyter integrated together · 0a446263
      Kirill Smelkov authored
      This patch teaches ERP5 software release to automatically instantiate Jupyter
      notebook web UI and tune it to connect to ERP5 by default. When Jupyter is
      enabled, it also installs on-server erp5_data_notebook bt5 (nexedi/erp5!29)
      which handles code execution requested for Jupyter.
      
      For ERP5 - for security and backward compatibility reasons - Jupyter
      instantiation and erp5_data_notebook bt5 install happen only if jupyter is
      explicitly enabled in instance parameters. The default is not to have Jupyter
      out of the box.
      
      On the other hand for Wendelin SR, which inherits from ERP5 SR, the
      default is to have Jupyter out of the box, because Wendelin SR is fresh
      enough without lots of backward compatibility needs, and Jupyter is
      usually very handy for people who use Wendelin.
      
      ~~~~
      
      For integration, we reuse already established in ERP5 infrastructure, to
      request various slave instances, and request Jupyter in a way so it
      automatically tunes and connects to balancer of one of Zope family.
      
      Jupyter code itself is compiled by reusing
      software/ipython_notebook/software.cfg, and Jupyter instance code is
      reused by hooking software/ipython_notebook/instance.cfg.in into ERP5 SR
      properly (the idea to override instance-jupyter not to render into
      default template.cfg is taken from previous work by @tiwariayush).
      
      ~~~~
      
      I tested this patch inside webrunner with create-erp5-site software type and
      various configurations (whether to have or not have jupyter, to which zope
      family to connect it, etc).
      
      I have not tested frontend instantiation fully - because tests were done only
      in webrunner, but I've tried to make sure generated buildout code is valid for
      cases with frontend.
      
      NOTE the code in this patch depends erp5_data_notebook bt5 (nexedi/erp5!29) which just got merged to erp5.git recently (see nexedi/erp5@f662b5a2)
      
      NOTE even when erp5_data_notebook bt5 is installed, on a freshly installed ERP5, it
      is required to "check site consistency" first, so that initial bt5(s) are
      actually installed and erp5 is ready to function.
      
      /cc @vpelletier, @Tyagov, @klaus, @Camata, @tiwariayush, @Kreisel, @jerome, @nexedi
      /proposed-for-review-on nexedi/slapos!43
      0a446263
  31. 25 Jan, 2016 1 commit
  32. 02 Oct, 2015 1 commit
  33. 08 Jul, 2015 1 commit
    • Saurabh's avatar
      Make it possible to instanciate 1 NEO DB inside an ERP5 instance · d35284d8
      Saurabh authored
      Before it was only possible to make an ERP5 cluster connect to a NEO cluster
      that was instanciated separately, by passing "name" and "master_nodes"
      connection parameters in "storage-dict".
      
      For an internal NEO DB, "name" and "master_nodes" is filled automatically
      and you must instead pass a "server" dict, with same parameters as in NEO SR.
      Currently, a NEO cluster name must be given. Later, we hope to generate a good
      name automatically.
      
      All this was implemented by refactoring NEO & ERP5 SR, with common files.
      For the ERP5 SR, the root partition also serves as "root" partition for NEO
      partitions: in other words, there's no second empty partition.
      d35284d8
  34. 02 Jul, 2015 1 commit
  35. 01 Jun, 2015 1 commit
  36. 25 May, 2015 1 commit
  37. 22 May, 2015 1 commit