Skip to content
Snippets Groups Projects
  1. Aug 16, 2017
  2. Aug 11, 2017
  3. Aug 09, 2017
  4. Aug 04, 2017
  5. Jul 31, 2017
  6. Jul 27, 2017
  7. Jul 26, 2017
    • Eduardo Gonzalez's avatar
      Fix zun command in zun-guide · afe16cea
      Eduardo Gonzalez authored
      Zun command is invalid, double colons are not
      valid.
      More info about this in bug report.
      
      Change-Id: I367aec97775dcefb2c45fe55a311c5451d33e703
      Closes-bug: #1706569
      afe16cea
  8. Jul 25, 2017
  9. Jul 24, 2017
    • James Benson's avatar
      Added note · 52bbb65e
      James Benson authored
      Closes-Bug: #1705116
      
      Change-Id: I973b31c9fdba3158810481385ada1be5543144b2
      52bbb65e
  10. Jul 21, 2017
  11. Jul 20, 2017
  12. Jul 19, 2017
  13. Jul 13, 2017
    • Eduardo Gonzalez's avatar
      Remove doc build errors · 66b91d8b
      Eduardo Gonzalez authored
      Gates only build deploy-guide docs, not every doc.
      This change clean doc errors, only Line to long.
      
      Also, removes doc/build folder in tox doc environment.
      doc/build is folder where previus executions are stored
      causing next execution to fail due rendered versions does
      not follow doc style checks.
      
      Change-Id: I623a7ee245729a06509f3a7039d5d5ed3813d977
      66b91d8b
  14. Jul 12, 2017
  15. Jul 11, 2017
    • Paul Bourke's avatar
      Improve Swift ring setup sample script · bf952839
      Paul Bourke authored
      The sample script provided in the docs to configure rings should add
      each storage node the ring, not the control node pointed to by the vip.
      
      Change-Id: I28ad60eb3c07f5da0e04e7780c41a7eed158b6d5
      bf952839
  16. Jul 10, 2017
  17. Jul 04, 2017
  18. Jul 02, 2017
  19. Jun 27, 2017
    • Vladislav Belogrudov's avatar
      Add flag to allow provider networks · f6eefdf3
      Vladislav Belogrudov authored
      In case of provider networks we need to configure external bridge
      on compute nodes, like it is done in DVR. The only way to tell
      if provider networks are to be used is a new flag.
      
      Change-Id: I1aef197ee2b84e28f2131f058e6995551f873fe1
      Closes-Bug: #1694726
      f6eefdf3
  20. Jun 21, 2017
  21. Jun 19, 2017
  22. Jun 15, 2017
  23. Jun 14, 2017
  24. Jun 13, 2017
    • Jeffrey Zhang's avatar
      Bump min Ansible version to 2.2.0 · 00a42b8c
      Jeffrey Zhang authored
      Different Y stream version in Ansible is not compatible. Since ansible
      2.2.0 is released for a while. It is time for kolla-ansible to bump the
      min Ansible version. Then we can remove the annoying WARNING message
      in deploying logs and use the new features.
      
      Change-Id: I99f3c5678f6d2d1f93d61c660fbd166184ff6422
      00a42b8c
    • Eduardo Gonzalez's avatar
      Use kuryr for zun network · da49b49b
      Eduardo Gonzalez authored
      Zun made mandatory to use kuryr for networking.
      This change update zun config to use kuryr.
      Also updates documentation.
      
      Change-Id: I9a55e390709b7e21d3efbd4be17a36db85cd8521
      da49b49b
  25. Jun 12, 2017
    • Juan J. Martinez's avatar
      Update Vagrant dev environment · 056ecc55
      Juan J. Martinez authored
       - Updated Ubuntu image to use 16.04.
       - VirtualBox provider to use centos/7 image + vagrant-vbguest plugin.
       - Improved docs so it is clear that vagrant-vbguest plugin is only
         required with VirtualBox.
       - Clarified comment and made it independent of the release.
       - Refactored the kolla and kolla-ansible paths to be based on the
         username used by Vagrant, that can change depending on the image.
      
      Change-Id: I23d84dcc3297c43eb12eff9c443d282281fc6c82
      056ecc55
  26. Jun 08, 2017
    • Paul Bourke's avatar
      Add a Kolla 'devstack' mode · 5cb37564
      Paul Bourke authored
      Add a new variable 'kolla_devmode', which when enabled, clones and
      bindmounts service source code into the containers.
      
      This commit adds the relevant changes for Heat, more services can be
      added and built upon.
      
      Usage:
      * Set 'kolla_devmode: yes'
      
      * Code is cloned to /opt/stack/{{ project_name }} on target
        node(s)
      
      * Users can develop in these repos, and simply restart the container to
        pick up / test changes.
      
      Debugging can be done from the host via 'remote_pdb'[0].
      
      [0] https://pypi.python.org/pypi/remote-pdb
      
      Implements: blueprint mount-sources
      Change-Id: Ic0431b10d723bf84eeefc72039376fe0058dd902
      5cb37564
  27. Jun 07, 2017
  28. Jun 06, 2017
  29. Jun 02, 2017
  30. May 31, 2017
    • Juan J. Martinez's avatar
      Fix vagrant development environment · 8fe43171
      Juan J. Martinez authored
      After the repo split into kolla and kolla-ansible the Vagrant
      development environment was broken.
      
      With this change Vagrant will run from kolla-ansible and kolla
      repo is expected to be in the same directory level so the
      bootstrap can include it inside the VM.
      
       - Modified the bootstrap code to copy both repos into the VM.
       - Added one configuration token to specify kolla-ansible location
         inside the VM.
       - Updated the docs.
      
      Change-Id: I6b56822d50472f8eda6fc60f69196d3c9b8b6cf8
      Closes-Bug: 1693847
      8fe43171
  31. May 29, 2017
  32. May 25, 2017
Loading