1. 27 Dec, 2019 1 commit
  2. 18 Dec, 2019 1 commit
  3. 30 Oct, 2019 1 commit
  4. 25 Oct, 2019 1 commit
    • Jérome Perrin's avatar
      standalone: also cleanup supervisor configuration · a620b0b5
      Jérome Perrin authored
      destroying instance is supposed to remove these, but when there are
      issues removing instances we sometimes have supervisor config left from
      previous instances.
      Reformating now delete theses after logging the problem.
  5. 23 Oct, 2019 2 commits
  6. 10 Oct, 2019 1 commit
    • Jérome Perrin's avatar
      standalone: fix support of recursive slapos · 2baa2125
      Jérome Perrin authored
      When having more than one read_only_shared_part_list, the template was
      first rendered with indentation and then dedented, but since dedent only
      remove the common indentation, we ended up with slapos.cfg like this:
      $ cat /data/slappart11_testnode/cqg/inst/test0-9/tmp/etc/slapos.cfg
                  software_root = /data/slappart11_testnode/cqg/inst/test0-9/tmp/soft
                  instance_root = /data/slappart11_testnode/cqg/inst/test0-9/tmp/inst
                  shared_part_list =
                  master_url =
                  computer_id = local
                  root_check = False
      First dedent, then render the template to prevent this issue. Apply this to
      other uses of textwrap.dedent for consistency.
      /reviewed-on !140
  7. 01 Oct, 2019 4 commits
  8. 10 Sep, 2019 2 commits
  9. 02 Sep, 2019 1 commit
  10. 09 Aug, 2019 1 commit
  11. 08 Aug, 2019 3 commits
  12. 01 Aug, 2019 2 commits
  13. 19 Jul, 2019 8 commits
  14. 16 Jul, 2019 2 commits
  15. 15 Jul, 2019 1 commit
  16. 04 Jun, 2019 1 commit
  17. 20 Dec, 2018 1 commit
    • Jérome Perrin's avatar
      proxy: implement software destruction · ac32cc74
      Jérome Perrin authored
      proxy was just removing the software from database when destruction was
      requested. Instead, keep it as requested_state = "destroyed" and return
      this information to the node, so that nodes properly destroy the
  18. 14 Dec, 2018 1 commit
  19. 26 Nov, 2018 1 commit
    • Jérome Perrin's avatar
      slap/interface/slap: pep8, typos · 5e7fbda4
      Jérome Perrin authored
      checked with:
        pylint --disable all --enable spelling --spelling-ignore-words=URI,SSL,API,XXX,uninstall,initialize,slapgrid,slapformat,kvm,instantiation,IComputer,IException,Vifib,IRequester,ISupply,SocketError,virtio,boolean,traceback,http,mysoftwareproduct,foo,buildout --spelling-dict en_US slapos/slap/interface/slap.py
      /reviewed-on !66
  20. 20 Jul, 2018 1 commit
    • Rafael Monnerat's avatar
      API Change: Remove available/building API from Computer Partition · 9fdaa54d
      Rafael Monnerat authored
        The API that notify availability and building from Computer Partition is unecessary and it's
        implementation overuse resources and cause flaky effect on the state of the Computer Partition.
        At the Software Release, the states can be available/building/error, and this state tens to be
        immutable once the software release is finished (it will be available, where building and error are
        transitory states).
        At Computer Partition, we intent to have started/stopped/destroyed instances, where available and
        building were transitory, but they have no practical function as a second report would come quickly
        after. So we may consider that started is actually same as available, in this case, it is a duplicated
        meaning, as you cannot be available w/o been started/stopped.
        computer_partition.building were never used, as the master knew that a partition is been processed,
        so this API were never used.
        Report transitory states are prevent us to determinate the actuall state, considering that the latest
        actuall state is more relevant (started/stopped/destroyed).
  21. 28 Mar, 2018 1 commit
  22. 24 Jan, 2018 2 commits
  23. 05 Oct, 2016 1 commit
    • 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).