1. 03 Nov, 2017 1 commit
  2. 12 Oct, 2017 2 commits
  3. 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
  4. 27 Sep, 2017 2 commits
  5. 13 Sep, 2017 1 commit
    • Julien Muchembled's avatar
      erp5: by default, create site automatically · b82d57df
      Julien Muchembled authored
      Since erp5@6c6b77a0, this is now a safe
      operation, in that a mistake while moving databases won't result in a loss of
      the catalog if the zodb is empty.
      
      This new implementation relies on
      erp5@6bb4c56e, which means that zopes
      decide on their own to create the site at startup if there's none, and the
      'erp5-bootstrap' service is removed from the root partition.
      
      /reviewed-on !217
      b82d57df
  6. 01 Sep, 2017 1 commit
  7. 03 Jul, 2017 1 commit
  8. 21 Jun, 2017 2 commits
  9. 20 Jun, 2017 3 commits
  10. 06 Apr, 2017 1 commit
  11. 22 Mar, 2017 1 commit
  12. 27 Feb, 2017 1 commit
  13. 22 Feb, 2017 1 commit
  14. 16 Feb, 2017 1 commit
  15. 08 Feb, 2017 1 commit
  16. 18 Jan, 2017 1 commit
  17. 26 Oct, 2016 1 commit
    • Kirill Smelkov's avatar
      erp5: Jupyter internal service is subinstance, not slave instance · 92c18f87
      Kirill Smelkov authored
      @vpelletier says:
      
          I do not think this is a "slave" instance, but just a sub-instance.
      
          "slave instance" is a way to pass parameter to a foreign instance. For example,
          frontend is an instance, and a slave instance is the rule given by an unrelated
          partition to make that existing frontend instance direct http://foo.com to 1.2.3.4:80 .
      
          OTOH, "balancer" is a sub-instance of ERP5's SR base instance (which is typically the root instance also).
      
      /noticed-by @vpelletier (on !43)
      92c18f87
  18. 28 Sep, 2016 1 commit
    • Vincent Pelletier's avatar
      erp5: Improve replication setup support. · 5ff0a4e0
      Vincent Pelletier authored
      Document how to setup replication.
      Add support for no-zope ERP5 instance, so it is possible to setup a
      replicating, full-featured ERP5 Cluster instance tree without providing
      service until it needs to take over its upstream, or to become
      otherwise independent.
      5ff0a4e0
  19. 27 Sep, 2016 1 commit
  20. 26 Aug, 2016 3 commits
  21. 25 Aug, 2016 2 commits
  22. 04 Jul, 2016 1 commit
  23. 27 May, 2016 2 commits
  24. 12 May, 2016 1 commit
  25. 04 Apr, 2016 1 commit
  26. 15 Feb, 2016 1 commit
  27. 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 (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 (erp5!29) which just got merged to erp5.git recently (see 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 !43
      0a446263
  28. 25 Jan, 2016 1 commit
  29. 02 Oct, 2015 1 commit
  30. 24 Aug, 2015 1 commit
    • Vincent Pelletier's avatar
      erp5: Rework postfix integration. · 86295f82
      Vincent Pelletier authored
      Add support for "hosts" aliasing in Zope instances.
      Add support for SASL relayhost with mandatory TLS encryption.
      Add mandatory TSL + SASL authentication, to not be an open relay.
      Wrap postfix commands with proper environment instead of symlink +
      source-able script.
      Add ipv6 listening support (untested).
      Drop non-required main.cf configuration options.
      Make postifx instance optional (requires postmaster address to be
      provided).
      Document and rework smtp-related parameters.
      Expose an userhosts hostname for smtp server.
      Add diversion support (solution to "prod clone sent mails to real customer").
      Use etc/run rather than etc/service, for consistency (if it needs to be
      changed, it must be changed for all software types).
      Hook into syslog and setup local syslog daemon, with logrotate integration.
      Update TODO entries.
      86295f82
  31. 08 Jul, 2015 1 commit