1. 08 Jan, 2020 1 commit
  2. 04 Dec, 2019 1 commit
  3. 07 Oct, 2019 1 commit
    • Jérome Perrin's avatar
      grid: new shared_part_list config file option · 5cbd70bc
      Jérome Perrin authored
      This new option for slapos.cfg allow to define a list of paths to use
      for shared parts feature of `slapos.recipe.cmmi`.
      This will be injected in the buildout profile used to install software,
      as `${buildout:shared-part-list}` which is the option `slapos.recipe.cmmi`
      use since 0.11.
      
      Note that the option changed in `slapos.recipe.cmmi` because this was
      incompatible. In 0.10, the option was named `${buildout:shared-parts}` and
      it was supposed to be a single path. `slapos.recipe.cmmi` 0.10 was trying
      to create this path. If we continued using this `${buildout:shared-parts}`
      option and changed to passe a newline-separated list of paths, then
      `slapos.recipe.cmmi` would just create one directory with \n in the name
      and will probably fail, which would make all software from 1.0.73 to 1.0.121
      not installable on next `slapos.core`, so we used another buildout option
      to prevent this problem.
      
      Because generally, profiles using slapos.recipe.cmmi 0.10 were not
      "safely" shared, we don't even provide compatibility with old option.
      
      /reviewed-on !46
      5cbd70bc
  4. 27 Aug, 2019 1 commit
  5. 02 Jan, 2019 1 commit
    • Thomas Gambier's avatar
      Make IPv6 on tap optionnal and put only 1 IPv6 address on the tap itself. · 40ee3280
      Thomas Gambier authored
      tap_ipv6 option let you chose if you want IPv6 on the taps or not. Some
      customers may decide to have only IPv4 inside their VMs.
      
      We put only 1 address on the tap itself (e.g.
      2001:67c:1254:e:89:69b0:ffff:ffff/128 instead of
      2001:67c:1254:e:89:69b0:ffff:ffff/96) otherwise, when we assign the
      address 2001:67c:1254:e:89:69b0::/96 inside the VM, the address has
      "dadfailed" status (dad = "Duplicate Address Detection"). The problem
      appears only with address "0" (ending in ::) but not with others
      addresses. We had 2 solutions:
       * put only one address on the tap (the solution we choose)
       * forbid address "0" inside the VM
      
      The chosen solution has the advantage that the host machine won't
      answer the ping on behalf of the VM since the tap has only 1 address
      (its own).
      
      /cc @alain.takoudjou
      
      /reviewed-on !86
      40ee3280
  6. 19 Nov, 2018 2 commits
  7. 31 Jul, 2018 1 commit
  8. 13 Nov, 2017 1 commit
  9. 07 Nov, 2017 1 commit
  10. 29 Feb, 2016 1 commit
  11. 25 Sep, 2015 1 commit
  12. 02 Jul, 2015 1 commit
  13. 13 Jan, 2014 1 commit
  14. 15 Aug, 2013 1 commit
  15. 26 Jun, 2013 1 commit
  16. 10 Jun, 2013 1 commit
  17. 24 May, 2013 1 commit
  18. 09 Apr, 2013 1 commit
  19. 29 Jan, 2013 1 commit
  20. 09 Jan, 2013 2 commits
  21. 11 Oct, 2012 1 commit
  22. 27 Sep, 2012 2 commits
  23. 31 Aug, 2012 1 commit
  24. 17 Aug, 2012 1 commit
  25. 07 Aug, 2012 1 commit
  26. 02 Aug, 2012 1 commit
  27. 24 Jul, 2012 2 commits
  28. 11 Jul, 2012 1 commit
  29. 03 Jul, 2012 1 commit
  30. 29 May, 2012 1 commit
  31. 26 May, 2012 1 commit
  32. 04 Apr, 2012 1 commit
  33. 01 Feb, 2012 2 commits
  34. 26 Jan, 2012 1 commit
  35. 25 Jan, 2012 1 commit