An error occurred fetching the project authors.
- 18 Aug, 2017 2 commits
-
-
Hardik Juneja authored
-
Hardik Juneja authored
-
- 11 Aug, 2017 1 commit
-
-
Vincent Pelletier authored
-
- 21 Jul, 2017 1 commit
-
-
Alain Takoudjou authored
-
- 18 Jul, 2017 1 commit
-
-
Hardik Juneja authored
whenever the zope instances have the same title (example all zope have 'Zope monitor' as title) the request to frontends consider it as the same request and gives same frontend to each of them. /reviewed-on nexedi/slapos!202
-
- 03 Jul, 2017 1 commit
-
-
Alain Takoudjou authored
Allows requesting a caucase partition and reusing an existing caucase instance. For client-certificate-based authentication, client must be able to access backend directly (frontend is not possible).
-
- 20 Jun, 2017 3 commits
-
-
Hardik Juneja authored
-
Hardik Juneja authored
-
Hardik Juneja authored
-
- 16 May, 2017 1 commit
-
-
Vincent Pelletier authored
-
- 06 Apr, 2017 1 commit
-
-
Yusei Tahara authored
-
- 22 Mar, 2017 1 commit
-
-
Yusei Tahara authored
software/erp5 & stack/erp5: Add a new parameter wendelin-core-zblk-fmt. Use it to specify wendelin.core format(ZBlk0 or ZBlk1).
-
- 26 Oct, 2016 1 commit
-
-
Kirill Smelkov authored
When originally in 0a446263 (ERP5 and Jupyter integrated together) I added Jupyter support into ERP5 the parameter for whether to enable/disable it was declared as boolean in JSON schema but processed as string in instance code, this way preventing usage of real JSON's boolean. Fix it. (also fixing up software/slapos-master/ which copied the files for play in 87d13789) /noticed-by @vpelletier (on nexedi/slapos!43)
-
- 28 Sep, 2016 1 commit
-
-
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.
-
- 01 Feb, 2016 1 commit
-
-
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 (nexedi/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 (nexedi/erp5!29) which just got merged to erp5.git recently (see nexedi/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 nexedi/slapos!43
-
- 01 Dec, 2015 1 commit
-
-
Vincent Pelletier authored
-
- 05 Oct, 2015 1 commit
-
-
Julien Muchembled authored
-
- 02 Oct, 2015 1 commit
-
-
Julien Muchembled authored
-
- 24 Aug, 2015 2 commits
-
-
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.
-
Marco Mariani 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.
-
- 08 Jul, 2015 1 commit
-
-
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 1 commit
-
-
Saurabh authored
-
- 01 Jun, 2015 1 commit
-
-
Vincent Pelletier authored
-
- 22 Apr, 2015 1 commit
-
-
Vincent Pelletier authored
One thread is just too limited to produce a usable instance (for example, a single-zope setup with default thread count fails to run live tests). It is also not an advised setting for activity nodes, because of timerserver still queuing process_timer calls while CMFActivity is busy processing; the result being a (limited) waste of memory, and hammering mysql after long processing periods. Zope's default value must be duplicated because thread-amount is also used to generate haproxy configuration file (so just not providing the value in Zope's configuration file is wrong).
-
- 19 Feb, 2015 1 commit
-
-
Vincent Pelletier authored
-
- 18 Feb, 2015 1 commit
-
-
Vincent Pelletier authored
hosts-dict alone is not powerful enough: in some cases, we want to alias a foreign hostname in order to control access to it (ex: to make interface calls fail on a clone).
-
- 09 Dec, 2014 1 commit
-
-
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'.
-
- 18 Nov, 2014 2 commits
-
-
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.
-
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 %}
-
- 28 Aug, 2014 3 commits
-
-
Vincent Pelletier authored
Implemented using libuserhosts. Only provided to zope processes so far, may be extended in the future with each process seeing different sets of aliases, with potentially different resolutions.
-
Vincent Pelletier authored
-
Vincent Pelletier authored
Also, do not tolerate missing instance-count internal zope partition parameter.
-
- 22 Apr, 2014 1 commit
-
-
Vincent Pelletier authored
-
- 05 Apr, 2014 1 commit
-
-
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.
-
- 02 Apr, 2014 2 commits
-
-
Vincent Pelletier authored
Balancer parameters were and are not supported, so this compatibility breakage is not important. The goal of this change is to make balancer parameter layout consistent with other software-types. Also, balancer's base TCP port is not taken from empty-string parameter anymore.
-
Vincent Pelletier authored
They contain section references, not immediate values, so they are intended to be evaluated by buildout and hence must not be escaped.
-
- 01 Apr, 2014 1 commit
-
-
Vincent Pelletier authored
-
- 20 Mar, 2014 1 commit
-
-
Vincent Pelletier authored
Not perfect yet, as some strings end in configuration files for example and need escape mechanisms aware of individual configuration file syntaxes.
-