1. 06 Jan, 2016 2 commits
    • Kirill Smelkov's avatar
      gitlab: Add empty instance · ab6d2f28
      Kirill Smelkov authored
      Add stub instance configuration which just establishes a way to have
      several software types(*), pass all needed info from software to
      instance, organizes base directory and establishes log rotation base for
      upcoming services.
      Log rotation is done with the help of cron periodicallly calling
      logrotate. The rotation is done in "copytruncate" mode - i.e. log file
      is not moved away and signal sent for service to reopen it, but instead
      log content is just copied to outside and there is no need for a service
      to reopen it's log file.
      The reason it is done this way, is that there is a chance of not
      handling such "reopen-log-file" callbacks correctly on a service side,
      and so the net is full of crashing reports, e.g. like this:
      That's why we take a safer approach instead, even if "copytruncate" mode
      is risking to loose several log entries(**) on rotation.
      NOTE services will organize log rotation with just
          <= logrotate-entry
          log     = path/to/log/files/*.log
      For this to work some "!py!" magic (our way to serialize object into
      executable python and process it in buildout recipes) is used to process
      section names.
      The approach trick is also used for cron, e.g. logrotate registers to
      cron this way:
          <= cron-entry
          time    = daily
          command = ${logrotate:wrapper}
      NOTE2 instance md5 are not fixed yet - we'll fix them after applying all
          patches in gitlab series.
      (*) for now there is only 1 - "gitlab", but we'll need to have "-export"
          and "-import" for resiliency in the future.
      (**) ideally such things should be done with logfs - a filesystem
          specializeing in logging - for client services it will look like as
          they just continue to write to log file, and on log service side, the
          rotation can happen, all transparent to client service.
      /cc @kazuhiko, @jerome
    • Kirill Smelkov's avatar
      Start of GitLab Software Release · 5e971c58
      Kirill Smelkov authored
      First step - build all needed software. We build:
      - Git
      - PostgreSQL 9.2
      - Redis 2.8
      - Nginx
      - gitlab-shell
      - gitlab-workhorse
      - gitlab-ce 8.2 itself
      and everything which is needed to build the above programs.
      Git is needed because GitLab is a git-hosting service and uses git
      underneath. PostgreSQL is used as DB by gitlab and Redis as a cache.
      GitLab-shell is a small project to manage ssh access to the service
      (we'll disable ssh though) and to perform all "change a repository"
      GitLab-workhorse is a service which offloads long-running or slow
      request from main GitLab service.
      GitLab-ce is the main Ruby-on-Rails-based web application.
      Ruby- and Go- based programs are built in a way similar to:
          - 31a45a94    (helloworld & helloweb: Ruby version), and
          - 24e82414    (helloworld & helloweb: Go version)
      Version of all components, except Git, were picked the same, as used by
      gitlab omnibus v8.2 .
      /cc @kazuhiko, @jerome
  2. 04 Jan, 2016 1 commit
  3. 28 Dec, 2015 4 commits
  4. 26 Dec, 2015 1 commit
  5. 23 Dec, 2015 1 commit
    • Julien Muchembled's avatar
      re6stnet: update and cleanup · 284612ac
      Julien Muchembled authored
      ../../stack/slapos.cfg is removed from component/*/buildout.cfg
      because we normally don't specify it in component/
      The OBS package will need to extend it.
  6. 21 Dec, 2015 4 commits
  7. 18 Dec, 2015 10 commits
    • Ayush Tiwari's avatar
      erp5 kernel jupyter · 8206dcdd
      Ayush Tiwari authored
      ipython_notebook SR hooked with ERP5 kernel.
      This kernel helps in interaction between erp5 and Jupyter frontend.
      The patches have been cleaned up
      - All the code execution is being done at erp5 side, Jupyter just acts as dumb client.
      - Receives result as string and its mime_type and thanks to kernel, displays it accordingly.
      - Interactions b/w erp5 and Jupyter frontend are based on HTTP requests.
      Major changes:
      - Addition of erp5 kernel
      - Improvement in code according to guidelines(name, section name)
      - Use jinja template as instance file and make it more dynamic
      - Debugging added for ipython_notebook service.
      Note: The certificate authentication changed has been reverted to the previous
      one(done by creating wrapper around openssl command) for now.
      /cc @Tyagov
      /reviewed-by @kirr, @jerome  (on !33)
    • Kirill Smelkov's avatar
      Jupyter: --matplotlib=inline is nether supported nor needed · 837c05c6
      Kirill Smelkov authored
      @jerome added --matplotlib=inline in 48eefab5 (ipython notebook) but it is
      really neither needed:
         I remember adding this --matplotlib=inline line, but I am not sure it was
         ever needed. Using magic %matplotlib in notebook should be enough.
         Yeah, for inline matplotlib in default python kernel, magics do there
         work(therefore neither pylab nor matplotlib alias are needed while starting the
         server), so I'd say leave this commit as it is and regarding version updation:
         a new patch making change wherever required.
      nor supported:
         $ cat .slappart0_ipython_notebook.log
         [W 15:51:35.454 NotebookApp] Unrecognized alias: '--matplotlib=inline', it will probably have no effect.
      Remove it.
      '--logfile' isn't available for ipython version 3.2.0 but we are not removing
      it since we are planning to upgrade IPython to versions 4.x where it is supported.
      Based on patch by @tiwariayush  (see !33)
    • Ayush Tiwari's avatar
      Jupyter: Change section name to instance-jupyter so as not to raise conflict... · bd3d8e48
      Ayush Tiwari authored
      Jupyter: Change section name to instance-jupyter so as not to raise conflict in case of multiple extends
      /reviewed-by @kirr  (on !33)
    • Ayush Tiwari's avatar
      Jupyter: Publish the serialized result · 0fb4f687
      Ayush Tiwari authored
      Maintain consistency with the slapOS SR format.
      This SR can be hooked with other SR(ex:wendelin) and its better
      to follow one way of publishing result parameters
      [ kirr: This essentially changes publication format to JSON:
          $ xslapos proxy show --params
          # before
          slappart0: ipython_notebook (type default)
              url = https://[2001:67c:1254:e:49::952d]:8888
              monitor_url = https://[2001:67c:1254:e:49::952d]:9685
          # after
          slappart0: ipython_notebook (type default)
              _ = {"url": "https://[2001:67c:1254:e:49::952d]:8888", "monitor_url": "https://[2001:67c:1254:e:49::952d]:9685"}
        I'm not convinced we really need this, nor that the .serialized version is
        the most oftenly used one:
          slapos$ git grep 'slapos.cookbook:publish$' |wc -l
          slapos$ git grep 'slapos.cookbook:publish.serialised$' |wc -l
        but we can have it and see how it goes, reverting if needed ]
      /cc @jerome
      /proposed-for-review-on !33
    • Ayush Tiwari's avatar
      Jupyter: Set log-level alias to 'DEBUG' for ipython notebook service · 3bf1cce9
      Ayush Tiwari authored
      This helps in logging up the requests made by ipython_notebook service
      [ kirr: To be clear - until log-level is set to DEBUG, IPython notebook does
        not log HTTP requests, and since logging of HTTP requests is considered normal
        for most of our services (Zope, Apache, etc), it makes sense to enable such
        functionality for notebook too.
        There is not much additional noise produced by --log-level=DEBUG - in
        practice ipython only prints what config files it uses on startup, so this
        should be ok to go. ]
      /reviewed-by @kirr, @jerome  (on !33)
    • Ayush Tiwari's avatar
      Jupyter: Hook ERP5 Kernel · 33954c66
      Ayush Tiwari authored
      ERP5 kernel basic info/workflow:
      1. User enters code on notebook cell and executes
      2. Code is sent to kernel via websockets
      3. Kernel sends request to ERP5
      4. Code is executed by ERP5 and the result is returned back via request.
      5. Result is received and rendered on the notebook frontend.
      6. Other message formats such as error and status are also conveyed by the Kernel.
      [ kirr: in IPython notebook speak kernel is something that allows IPython
        notebook server side to talk to execution backend. ERP5 kernel is a thing that
        allows ipython notbook to talk to ERP5 (with help on-ERP5-server special bt5
        installed which accepts and executes commands).
        The bt5 to handle notebook calls on ERP5 side - erp5-data-notebook - is
        proposed to be merged into erp5.git on erp5!29 ]
      /initially-reviewed-by @kirr, @Tyagov  (in a lot of places, last time on !33)
    • Ayush Tiwari's avatar
      IPython Notebook: Explicitly add environment variable around wrapper and use... · 77ffa61e
      Ayush Tiwari authored
      IPython Notebook: Explicitly add environment variable around wrapper and use ipython directory inside instance in env
      [ kirr: By default IPython keeps configuration and other files location in
        ~/.ipython . What this patch does is organize explicit directory in instance
        tree to keep such files  ]
      /reviewed-by @kirr  (on !33)
    • Ayush Tiwari's avatar
      IPython Notebook: Add dynamic-template-base section for common jinja related... · 2ff9b784
      Ayush Tiwari authored
      IPython Notebook: Add dynamic-template-base section for common jinja related file section and extend them with this section
    • Ayush Tiwari's avatar
      IPython Notebook: Convert instance to jinja2 template · fbfaaef8
      Ayush Tiwari authored
      [ kirr: to-Jinja2 conversion is required because jinja is more suitable to
        describing instances compared to buildout, because jinja2 has e.g. control
        structures ]
      /reviewed-by @kirr  (on !33)
    • Kirill Smelkov's avatar
      wendelin: Adjust to recent ipython-notebook section renaming · ae1aa162
      Kirill Smelkov authored
      Commit cee110b2 (IPython Notebook: Fixing coding crimes for section
      names) changed IPython notebook section name to use '-' as word
      delimiter but forgot to update users, and this way wendelin build
      started to fail:
          INFO While:
          INFO   Installing.
          INFO   Getting section ipython_notebook.
          INFO Error: The referenced section, 'ipython_notebook', was not defined.
      Fix it. (And I've made sure with whole-tree git grep that there is no
      more ipython notebook users except wendelin in whole slapos.git so far)
      /reported-by @Tyagov
      /cc @tiwariayush
      /reviewed-by TrustMe
  8. 17 Dec, 2015 4 commits
  9. 16 Dec, 2015 2 commits
  10. 15 Dec, 2015 3 commits
  11. 14 Dec, 2015 1 commit
    • Alain Takoudjou's avatar
      kvm: Add restrict mode for nat interface · b1dcbf77
      Alain Takoudjou authored
      If restrict mode is set to true, nat interface (eth0) will be isolated, no network access, only host and guest forward rules will work throught that interface.
      This option is true by default for kvm-cluster, and false for single and resilient kvm.
  12. 09 Dec, 2015 5 commits
    • Rafael Monnerat's avatar
    • Kirill Smelkov's avatar
      slapos/recipe/postgresql: Do not leave half-installed postgresql instance · b7f00def
      Kirill Smelkov authored
      In case there are errors when creating cluster / setting up its
      configuration files, currently we leave pgsql database left
      half-installed and next time instantiation runs do not do anything,
      because os.path.exists(pgdata) is already true.
      I've personally hit this situation via providing ipv4 and ipv6
      parameters as strings and the recipe wanted to do `ipv4.join(ipv6)` but this
      works only for sets and raises for strings.
      What is worse is that the above error becomes hidden in our default
      setup, because webrunner tries to do instantiation _several_ times, and
      on the second run instantiation succeeds, because pgdata directory
      already exists and recipe thinks there is nothing to do _and_ webrunner
      already removed instance.log from previous run.
      So do not hide errors, and if we see there are problems, remove the
      wholly created pgsql database directory.
      /cc @kazuhiko, @jerome
      /proposed-for-review on !29
    • Cédric Le Ninivin's avatar
    • Cédric Le Ninivin's avatar
    • Julien Muchembled's avatar
      ERP5: sort balancer families by name before assigning ports · ba9ef609
      Julien Muchembled authored
      If the list of families does not change, their ports must not change, and it's
      wrong to get this by relying on CPython implementation details. Even if we
      automated the update of frontends with new urls, this couldn't be done
      atomically and we'd get random failures.
      Currently, frontends are only updated manually so we also want to minimize
      changes when families are added/renamed/removed. By sorting alphabetically,
      we have something predictable. Of course, this does not cover cases like the
      following one:
      - before: A, B, C
      - after: A, C
      Even if we added a 'port-base' parameter for the balancer, the port would
      change for one of the 2 families.
      We have no need for the moment, but we could go further with an optional list
      parameter to choose the order, and a special value to skip ports. Another
      option is to use publish-early but it's more complicated to implement and
      we lose everything when we reinstanciate.
      The sort in haproxy.cfg.in is for the stats page.
  13. 08 Dec, 2015 1 commit
  14. 07 Dec, 2015 1 commit