1. 01 Apr, 2016 1 commit
  2. 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
  3. 11 Jun, 2015 1 commit
  4. 10 Jun, 2015 1 commit
    • Saurabh's avatar
      NEO: complete review of instanciation without backward compatibility · 61929809
      Saurabh authored
      - There's now a single software type 'neo' (in addition to the default)
        which contains:
        - 1 master
        - 1 admin
        - a configurable number of storage nodes, that share the same MySQL server
      - Review of parameters to configure MySQL server.
        (innodb_buffer_pool_size is important)
      - Check of meaningless values of 'replicas'.
      61929809
  5. 04 Feb, 2015 1 commit
    • Julien Muchembled's avatar
      NEO: fix instanciation issues · af64ee68
      Julien Muchembled authored
      - switch-softwaretype recipe is not merged to master yet so we must
        slapos-cookbook in develop mode, like for ERP5.
      - Recognize "RootSoftwareInstance" as default software type for compatibility.
      af64ee68
  6. 18 Nov, 2014 3 commits
    • Julien Muchembled's avatar
      neoppod: stop using deprecated slapos.cookbook:generic.mysql · 67dbe6d0
      Julien Muchembled authored
      Contrary to ERP5, there's no mysql-update service:
      - this simplifies the SR
      - after reading the MySQL documentation, the automatic use of mysql_upgrade
        is quite frightening:
        « You should always back up your current MySQL installation before performing
        an upgrade. »
        « After running mysql_upgrade, stop the server and restart it so that any
        changes made to the system tables take effect. » (which is currently not done
        by the recipe)
      - the future of NEO is an embedded DB like libmysqld
      67dbe6d0
    • Julien Muchembled's avatar
      logging: refactoring of crond/logrotate for NEO & ERP5 · 61711abc
      Julien Muchembled authored
      New 'slapos-kill' from slapos.toolbox is used instead of 'killpidfromfile'
      This is required for NEO which does not write any pid file.
      61711abc
    • Julien Muchembled's avatar
      New recipe 'switch-softwaretype' deprecating 'softwaretype' · 7ece1a48
      Julien Muchembled authored
      The inline recipe for ERP5 has been improved and converted into recipe,
      which is reused for NEO.
      
      Templates are instanciated only if they're used, so no need anymore to
      wrap them with:
      
        {% if slap_software_type == software_type -%}
        ...
        {% endif %}
      7ece1a48
  7. 10 Oct, 2012 1 commit