1. 30 Jan, 2018 1 commit
  2. 29 Jan, 2018 1 commit
  3. 26 Jan, 2018 1 commit
  4. 12 Jan, 2018 1 commit
    • Alain Takoudjou's avatar
      Move slapgrid checkpromise method to utils so it can be reused · c49161fb
      Alain Takoudjou authored
      rename checkPromises to checkPromiseList, and move the method to grid/utils so it can be imported by monitor to check promises.
      
      
      `raise_on_failure` will be used to check all promises without raise. All promises result will be returned.
      
      `profile` True/False will log promise execution time.
      
      /reviewed-on !35
      c49161fb
  5. 19 Sep, 2017 1 commit
  6. 14 Sep, 2017 1 commit
  7. 03 Jul, 2017 1 commit
  8. 13 Jun, 2017 2 commits
  9. 27 Feb, 2017 1 commit
    • Vincent Pelletier's avatar
      slapos.grid.SlapObject: Get rid noisy and pointless comment. · 1d4e3aed
      Vincent Pelletier authored
      Comment duplicates the url. It is available 3 lines below, thank you very
      much.
      Comment assumes resulting file is actually intended for viewer to edit it,
      which is wrong.
      
      So just leave the comment out altogether, as it does not bring any value.
      Also, allows simplifying code.
      1d4e3aed
  10. 25 Oct, 2016 1 commit
  11. 24 Oct, 2016 1 commit
  12. 19 Oct, 2016 1 commit
  13. 12 Oct, 2016 3 commits
    • Alain Takoudjou's avatar
    • Sebastien Robin's avatar
      svcbackend: raise exception if supervisord is failing · 7b59f9a4
      Sebastien Robin authored
      errors will be much more visible
      7b59f9a4
    • Sebastien Robin's avatar
      svcbackend: explicitely call the executable instead of using Popen 'executable' keyword · 14979297
      Sebastien Robin authored
      Some testnodes were failing more or less randomly while calling "slapos node instance".
      On failing nodes, unlike other ones, there was this unexpected log:
      
      2016-10-06 15:35:18 slapos[11671] INFO Processing computer partitions...
      2016-10-06 15:35:18 slapos[11671] INFO Launching supervisord with clean environment.
      2016-10-06 15:35:18 slapos[11671] INFO Could not find platform independent libraries <prefix>
      2016-10-06 15:35:18 slapos[11671] INFO Could not find platform dependent libraries <exec_prefix>
      2016-10-06 15:35:18 slapos[11671] INFO Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
      2016-10-06 15:35:18 slapos[11671] INFO ImportError: No module named site
      2016-10-06 15:35:18 slapos[11671] WARNING Supervisord unknown problem:
      2016-10-06 15:35:18 slapos[11671] INFO Processing Computer Partition test0-0.
      
      Then slapgrid was later failing with :
      
      slapgrid_cp :   File "/opt/slapgrid/75e907b4c1523ecfa2aa210ec2754db4/eggs/supervisor-3.3.1-py2.7.egg/supervisor/xmlrpc.py", line 521, in connect
      slapgrid_cp :     self.sock.connect(self.socketfile)
      slapgrid_cp :   File "/opt/slapos/rebootstrap/parts/python2.7/lib/python2.7/socket.py", line 228, in meth
      slapgrid_cp :     return getattr(self._sock,name)(*args)
      slapgrid_cp : error: [Errno 2] No such file or directory
      
      But the initial suspect logs sounds be the original issue that is the source
      of next ones.
      
      So it looks like supervisord was not able to start at all.
      
      After playing with subprocess.Popen, is sounds not a good idea to play
      with the keyword 'executable'. It looks like not always be strictly equivalent
      to a replacement of the first argument of the first Popen args. It's much better
      to directly set the process we want to call in the invocation list :
      - it avoid to rely on a feature that is "very seldom needed" as we see
        in subprocess documentation
      - it makes the code much readable, it avoid the guy reading the
        code wasting time understanding that the invocation_list is not
        really what is going to be executed.
      14979297
  14. 07 Oct, 2016 1 commit
  15. 05 Oct, 2016 2 commits
    • Alain Takoudjou's avatar
      71801958
    • Alain Takoudjou's avatar
      Introduce new garbage collector for instances ignored by buildout · a403cff3
      Alain Takoudjou authored
      Buildout cannot request destroy sub instances when it is removed from
      instance parameters by the user. Ex: request a cluster of KVM, with
      kvm1 and kvm2 instances, edit parameters and remove kvm2 in the list.
      Buildout will just ignore that instance and it will be removed only when
      the hosting subscription will be destroyed.
      
                       -- kvm1
      root instance --|
                       -X- kvm2
      
      So when processing a partition, we send to master the list of requested sub
      instance(s). If the previous list was ['kvm1', 'kvm2'], then after remove kvm2
      the list will be ['kvm1'] (for the root instance). Commit this list to the
      master will unlink between root instance and kvm2 (predecessor categorie).
      
      A new alarm will search for unlinked instances: Instance which has no parent,
      and destroy them (also destroy the sub tree).
      a403cff3
  16. 27 Oct, 2015 1 commit
  17. 26 Oct, 2015 1 commit
  18. 15 Oct, 2015 2 commits
  19. 02 Oct, 2015 1 commit
  20. 29 Sep, 2015 1 commit
  21. 25 Sep, 2015 1 commit
  22. 21 Aug, 2015 1 commit
  23. 24 Apr, 2015 2 commits
  24. 25 Mar, 2015 1 commit
  25. 17 Mar, 2015 1 commit
  26. 30 Jan, 2015 1 commit
  27. 29 Jan, 2015 1 commit
  28. 23 Jan, 2015 2 commits
  29. 22 Jan, 2015 1 commit
  30. 20 Jan, 2015 1 commit
  31. 16 Jan, 2015 1 commit
  32. 12 Jan, 2015 1 commit
  33. 09 Jan, 2015 1 commit