1. 15 Jun, 2017 1 commit
  2. 06 Apr, 2017 1 commit
  3. 22 Mar, 2017 1 commit
  4. 27 Feb, 2017 1 commit
  5. 16 Feb, 2017 1 commit
  6. 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
  7. 26 Aug, 2016 1 commit
  8. 25 Aug, 2016 1 commit
  9. 12 May, 2016 1 commit
  10. 04 Apr, 2016 1 commit
  11. 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
  12. 25 Jan, 2016 1 commit
  13. 02 Oct, 2015 1 commit
  14. 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
  15. 02 Jul, 2015 1 commit
  16. 01 Jun, 2015 1 commit
  17. 25 May, 2015 1 commit
  18. 22 May, 2015 1 commit
  19. 22 Apr, 2015 1 commit
  20. 18 Mar, 2015 2 commits
  21. 12 Mar, 2015 1 commit
  22. 18 Feb, 2015 2 commits
  23. 13 Feb, 2015 1 commit
  24. 09 Dec, 2014 1 commit
    • Julien Muchembled's avatar
      erp5: review request parameters for SLA & ZODB · a2ba55e0
      Julien Muchembled authored
      All parameters about SLA, i.e. computer-guid & instance-guid, are removed in
      favor of a new "sla-dict" parameter, which is easier to implement and much more
      versatile.
      
      All changes in the request parameters are incompatible. The old ones are
      ignored without warning/error.
      
      For compatibility, the reference of ZEO partition is still "zodb".
      
      Default settings were also fine. Default name of mount-point and FileStorage
      file is reverted to 'root' instead of 'main'.
      a2ba55e0
  25. 08 Dec, 2014 2 commits
  26. 18 Nov, 2014 1 commit
    • Julien Muchembled's avatar
      Make ERP5 instantiable with an external NEO storage · a546487f
      Julien Muchembled authored
      In order not to conflict with a future integration of NEO in ERP5:
      - the input schema has a new parameter for external storages.
      - zodb-software-type & zodb is used only for internal storages
        and only ZEO is supported.
      
      NEO logging is also enabled for clients.
      a546487f
  27. 28 Aug, 2014 1 commit
  28. 05 Apr, 2014 1 commit
    • Vincent Pelletier's avatar
      erp5: Add webdav support. · f2183d38
      Vincent Pelletier authored
      Move haproxy httpchk configuration per-listen as zope's webdav returns 401
      on (at least) GET / . TCP-level checks are still active, which should be
      sufficient.
      Also, change zope_family_address_list check to getitem as it's more natural
      than concatenating.
      Also, stop using apache.zope.backend recipe to add support for per-port
      scheme so automatic ERP5Site creation knows which URL is really HTTP.
      Also, stop using certificate_authority recipe and call openssl directly
      when generating self-signed cert for https/webdavs support.
      Also, rework balancer parameters a bit (still undocumented).
      Also, make instance-balancer always publish ipv6 value (empty when no ipv6
      available), so instance-erp5 always succeeds.
      f2183d38
  29. 04 Feb, 2014 1 commit
  30. 03 Feb, 2014 1 commit
  31. 21 Jan, 2014 1 commit
  32. 04 Sep, 2013 1 commit
  33. 22 Aug, 2013 1 commit
  34. 16 Aug, 2013 1 commit
  35. 16 Jul, 2013 2 commits