1. 21 Feb, 2016 1 commit
  2. 18 Feb, 2016 2 commits
  3. 17 Feb, 2016 2 commits
  4. 16 Feb, 2016 3 commits
  5. 15 Feb, 2016 5 commits
  6. 13 Feb, 2016 1 commit
    • gitlab: Wait a bit for PostgreSQL to be ready in Unicorn startup · 949e55e2
      As it was outlined in 5a744de7 (gitlab: Compile assets on instantiation
      and make sure DB is properly setup/migrated before unicorn runs) we are
      performing DB initialization and migration in pre-action as part of
      unicorn startup script. But that currently has one drawback:
      
          if all services start at the same time - e.g. both PostgreSQL and
          Unicorn - and that is a common scenario when SR is compiled and
          instantiated / started, PostgreSQL is usually not yet ready to
          process queries from Unicorn startup script, and first-time Unicorn
          startup fails.
      
      Until now this problem was workarounded by manually starting unicorn
      second time - after some time postgresql is started and ready. But why
      do it manually, if we can do the same logic automatically. So fix it:
      
          in Unicorn startup script wait a bit (up to 5 seconds) for
          PostgreSQL to become ready.
      
      /cc @kazuhiko, @jerome
      Kirill Smelkov committed
  7. 11 Feb, 2016 11 commits
  8. 01 Feb, 2016 3 commits
    • Jupyter: ERP5 kernel sends code using POST · cf117ccd
      Query strings used on GET requests have size limitations
      on servers and this causes big code cells to not be executed
      at all, returning only an Internal Server Error with no
      further explanation.
      
      /reviewed-by @kirr, @Tyagov (on !43)
      Douglas committed
    • erp5: Provide pandas, scikit-learn & matplotlib out of the box · 5cd3fc51
      Pandas and scikit-learn are handy to have for data processing which we
      are going to do more and more in ERP5 context. Matplotlib is very handy
      to have when one works with Jupyter, but also can be used by just
      backend code to generate graphs.
      
      From this point of view it makes sense to have this eggs always
      available out of the box. To do so move them from Wendelin to ERP5.
      
      /suggested-by @tiwariayush
      /reviewed-by @Tyagov (on !43)
      Kirill Smelkov committed
    • ERP5 and Jupyter integrated together · 0a446263
      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
      Kirill Smelkov committed
  9. 31 Jan, 2016 2 commits
  10. 27 Jan, 2016 1 commit
  11. 26 Jan, 2016 1 commit
  12. 25 Jan, 2016 1 commit
  13. 24 Jan, 2016 1 commit
  14. 20 Jan, 2016 1 commit
  15. 17 Jan, 2016 5 commits