An error occurred fetching the project authors.
  1. 30 Apr, 2020 5 commits
  2. 24 Apr, 2020 2 commits
  3. 15 Apr, 2020 1 commit
  4. 28 Mar, 2020 1 commit
  5. 23 Mar, 2020 1 commit
  6. 22 Mar, 2020 1 commit
  7. 20 Mar, 2020 1 commit
  8. 10 Mar, 2020 2 commits
  9. 09 Mar, 2020 2 commits
  10. 06 Mar, 2020 2 commits
  11. 13 Jan, 2020 1 commit
    • Jérome Perrin's avatar
      software/slaprunner: drop ssh key authority · 4ba5d113
      Jérome Perrin authored
      These keys are not managed by trust of a certificate authority, just by
      "trust of first use" so it does not make sense to use a key authority.
      
      This also cause difficulties to publish the key fingerprint as a
      parameter, because we can't get the key fingerprint until the authority
      service is started.
      
      Also enable ecdsa key.
      
      This fixes random failures with slaprunner tests, because the published
      fingerprint was never correct on first buildout run.
      
      Existing webrunners will have a new ssh host key after this.
      4ba5d113
  12. 29 Nov, 2019 1 commit
  13. 25 Nov, 2019 1 commit
  14. 22 Nov, 2019 2 commits
  15. 19 Nov, 2019 1 commit
  16. 13 Nov, 2019 1 commit
    • Nicolas Wavrant's avatar
      slaprunner: parameterize the shared folder · 70a97144
      Nicolas Wavrant authored
      In test nodes we put the software_root folder out of the webrunner so we
      can keep it for the following tests. Except that the shared folder has
      been introduced by default recently, and it is still inside the webrunner.
      
      Thus, between 2 tests the webrunner is deleted, so the shared parts are too,
      but not the SR folder (which is marked as completed). Then in the successive tests
      the software release fails to build, or the insances fail to isntanciate.
      70a97144
  17. 08 Nov, 2019 1 commit
    • Nicolas Wavrant's avatar
      resilient: add prefix to a published parameter · d6615b72
      Nicolas Wavrant authored
      In 95c05120, a published parameter "ssh-url" was added
      to the webrunner, clashing with the existing "ssh-url" parameter used by the resilient
      stack (which is extended by webrunner).
      As the new "ssh-url" is public and read by customers, it doesn't make sense to rename
      it to something more slaprunner-ished, more especially it already existis "ssh-command",
      so if a second parameter was named "runner-ssh-url" it wouldn't make sense to the user...
      
      This change had to be propagated to all the software releases extending the resilient stack.
      
      Finally, I think that stacks should use namespaces to avoid conflicts with the software
      releases extending them. Currently, we are doing the opposite and are using namespaces
      for software release to avoid conflicting with their stack : for exemple, in stack/resilient
      we have a section [sshd-raw-server] and in the software/slaprunner we have [runner-sshd-raw-server].
      This situation will create clashes when one software release extends 2 stacks, as nothing
      guarantees that 2 stacks have no conflicting section name, config file path, ...
      d6615b72
  18. 30 Oct, 2019 6 commits
    • Jérome Perrin's avatar
      slaprunner: support shared parts · 1a5df533
      Jérome Perrin authored
      If slaprunner itself was installed on a slapos which had shared parts
      enabled, these shared parts will also be used while installing softwares
      inside the slaprunner.
      
      Because ${buildout:shared-part-list} is a multi line property, it was
      not possible to generate .cfg files (which needs special handling of
      multi-line strings) directly from software buildout (where jinja
      templates are not yet available), so we use a trick of generating a
      plain text file in software and parsing it during instance.
      1a5df533
    • Jérome Perrin's avatar
      slaprunner: publish a ssh:// url · 95c05120
      Jérome Perrin authored
      Instead of having to copy and paste the "ssh command", having a
      clickable link is more user friendly. This integrates seamlessly with
      ChromeOS secure shell app (eventhough the app does not do anything with
      fingerprint as per version 0.19)
      95c05120
    • Jérome Perrin's avatar
      slaprunner: ~/bin/slapos: don't override SLAPOS_CONFIGURATION · 2118a01c
      Jérome Perrin authored
      Because this slapos often is executed when just running `slapos` at is
      in the $PATH, we should also consider special cases where users want to
      call this script with another $SLAPOS_CONFIGURATION.
      
      When $SLAPOS_CONFIGURATION is already set, ~/bin/slapos will not change
      it, it will only set it when not set.
      2118a01c
    • Jérome Perrin's avatar
      slaprunner: set $HOME · 06c1f15d
      Jérome Perrin authored
      Because slaprunner might be instanciated in a different directory than
      the shell user $HOME (like in recursive SlapOS), it's necessary to set
      HOME to the base directory. For "bare metal" SlapOS, this would not make
      any difference.
      06c1f15d
    • Jérome Perrin's avatar
      slaprunner: set $TERMINFO in bash profile · d74eb583
      Jérome Perrin authored
      so that terminal uses terminfo from the same curses library.
      d74eb583
    • Jérome Perrin's avatar
  19. 04 Oct, 2019 1 commit
    • Thomas Gambier's avatar
      do not create two wrappers for the same executable if hash change · ed707d3b
      Thomas Gambier authored
      Prevent creating 2 wrapper for the same service if hash changed. Here, one service is exited because port is used by the firt to service to start:
      
          slappart6:runner-sshd-4248650e36a9a26a6481df1baffd9f58-on-watch                RUNNING   pid 27835, uptime 0:03:45
          slappart6:runner-sshd-b3b68f4278ceb84691ec27521ea229eb-on-watch                EXITED    Mar 06 04:52 PM
      
      To achieve that, update slapos.cookbook and use hash-existing-files option of wrapper recipe
      
      hash-existing-files list all the files used for hash that are not
      handled by buildout. For those files, the hash is calculated as soon as
      the __init__ function so that if there is a change in those files,
      buildout will remove the existing wrapper (it will uninstall the
      section) and replace it with the new wrapper.
      
      /reviewed-on nexedi/slapos!525
      ed707d3b
  20. 09 Sep, 2019 1 commit
    • Julien Muchembled's avatar
      slaprunner: do not force instantiation of all partitions · b1d83628
      Julien Muchembled authored
      This is important for performance and it enables testless promises.
      
      For partitions that are instantiated successfully, let slapos decide
      when there's no parameter change (usually once a day).
      
      Instantiation can be forced on manual action in the UI.
      b1d83628
  21. 11 Jul, 2019 1 commit
  22. 24 Jun, 2019 1 commit
  23. 17 Jun, 2019 1 commit
  24. 26 Mar, 2019 1 commit
  25. 11 Mar, 2019 1 commit
  26. 10 Jan, 2019 1 commit