An error occurred fetching the project authors.
- 04 Apr, 2016 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 01 Apr, 2016 1 commit
-
-
Ivan Tyagov authored
-
- 01 Mar, 2016 2 commits
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
- 24 Feb, 2016 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 31 Jan, 2016 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 25 Jan, 2016 1 commit
-
-
Julien Muchembled authored
-
- 20 Jan, 2016 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 21 Dec, 2015 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 07 Dec, 2015 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 21 Oct, 2015 1 commit
-
-
Julien Muchembled authored
NEO is still in heavy development and it must be easy to update code on existing deployment.
-
- 15 Oct, 2015 4 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Julien Muchembled authored
This fixes the following random failures: While: Installing slapos-deps-eggs. Getting distribution for 'ZODB3==3.10.5+SlapOSPatched001'. An internal error occurred due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): ... File "zc/buildout/easy_install.py", line 968, in _get_dist shutil.copytree(dist.location, newloc) File "shutil.py", line 177, in copytree os.makedirs(dst) File "os.py", line 157, in makedirs mkdir(name, mode) OSError: [Errno 17] File exists: '.../eggs/ZODB3-3.10.5-py2.7-linux-x86_64.egg'
-
Julien Muchembled authored
-
- 05 Oct, 2015 2 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
- 02 Oct, 2015 2 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
- 01 Oct, 2015 1 commit
-
-
Julien Muchembled authored
-
- 28 Sep, 2015 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 17 Jul, 2015 1 commit
-
-
Saurabh authored
For performance reasons, the root partition requests subpartitions during initialization of sections, whereas such processing should normally be done during the update/install phase. The consequence is that partitions may be requested whereas they depend on sections that fail (usually just temporarily, because of missing returned parameters in the first runs). For example, the request of zope partitions depends on the generation of passwords: 1. password generated (__init__) 2. zope partitions requested (__init__) 3. password saved (install) As long as a failure happens between 2 and 3, zope parameters are always updated with a different password. In the case of NEO, the instanciation of zope partitions currently succeeds even if the list of master nodes is missing (note that there is a minor bug to fix here: whenever a NEO storage is not the main one, zope processes may start too early, and the user may have to restart zopes manually). The 'inituser_done' file is created but zope processes fail to start if NEO is used as main storage, and all this happens before the password was saved in the root partition ([neo-0-final] failing to install because 'admins' parameter returned yet). This was never an issue with ZEO because zopes start successfully at the same time the 'inituser_done' file is created. One way to solve this could have been to introduce a dummy dependency between [neo-0-final] and any other section generating a password. Quite ugly and we also found non-optimal to use a non-backuped file in the root partition to save such information, whereas we need anyway to publish them for the user. Therefore, we introduce a new 'publish-early' recipe for accessing and publishing desired parameters before any request of partitions. Of course, these must not be dropped by the usual [publish] section, and to avoid having to repeating them all manually, we have also added a '-extends' option to the 'publish' recipe. We use the same technique to autogenerate and configure cluster name for NEO, which helps us in minimizing the number of params one has to pass for requesting NEO. In the 'generate.password' recipe, the 'storage-path' can now be empty, when there's no need to save the generated password in a file.
-
- 13 Jul, 2015 1 commit
-
-
Saurabh authored
-
- 08 Jul, 2015 2 commits
-
-
Julien Muchembled authored
-
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.
-
- 25 Jun, 2015 1 commit
-
-
Julien Muchembled authored
-
- 11 Jun, 2015 2 commits
- 10 Jun, 2015 1 commit
-
-
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'.
-
- 04 Feb, 2015 2 commits
-
-
Julien Muchembled authored
This problem was not found during development because I used a local checkout of slapos cookbook and these files were not downloaded but directly copied from the disk. In zc.buildout, the Download class should be changed to use something that respects umask, instead of 'tempfile.mkstemp'.
-
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.
-
- 09 Dec, 2014 2 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
- 08 Dec, 2014 1 commit
-
-
Julien Muchembled authored
-
- 19 Nov, 2014 1 commit
-
-
Julien Muchembled authored
-
- 18 Nov, 2014 3 commits
-
-
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
-
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.
-
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 %}
-
- 05 Mar, 2014 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 09 Jul, 2013 1 commit
-
-
Mame Coumba Sall authored
-