Skip to content
Snippets Groups Projects
  1. Apr 05, 2016
  2. Mar 31, 2016
  3. Mar 24, 2016
  4. Mar 22, 2016
    • Carlos Cesario's avatar
      Added note about nested environment · 8e2423a3
      Carlos Cesario authored
      Added information when using nested environment for Kolla deployment.
      
      Added check command to verify hardware acceleration
      
      Change-Id: I6cb43ebbf11b5cf34f866fdccb550e9641a47f6c
      8e2423a3
  5. Mar 21, 2016
    • SamYaple's avatar
      Add generate_passwords.py to generate passwords · f03e06e0
      SamYaple authored
      
      As with all tools, this is a first pass at the generation. Perhaps we
      even want to move this into kolla/kolla/cmd and be generated with tox
      itself in the future.
      
      This tool, when run, will only populate empty fields that have no
      values meaning that it is safe to run repeatedly on the same file.
      
      Of note, there is no way to preserve comments in the file after it has
      been processed by the yaml parser in python. Comments and sections
      will remain in the passwords.yml template for additional documentation
      if the user wishes to populate the file themselves.
      
      Use SystemRandom and clean up the docs a bit to not use pronouns.
      
      Co-Authored-By: default avatarSteven Dake <stdake@cisco.com>
      
      Closes-Bug: #1559266
      Change-Id: I2932d592df8871f1b7811059206d0b4d0553a687
      f03e06e0
  6. Mar 19, 2016
    • Maru Newby's avatar
      Update quickstart doc to use drop-in unit files · b9205399
      Maru Newby authored
      While it's possible to edit distro/package unit files installed to
      /lib/systemd/system, a cleaner solution exists.  systemd will pick up
      'drop-in' unit files located in '/etc/systemd/system/[unit name].d/'.
      A drop-in unit file only has to include fields that override those in
      the main unit file, and the drop-in unit and main unit file can change
      independently.
      
      This change updates the quickstart doc to use drop-in unit files to
      configure docker.service instead of editing the main unit file.
      
      See: https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html
      
      Change-Id: Iddbebf658741937e3c4157fc0a021751f10fabd2
      b9205399
  7. Mar 18, 2016
    • Steven Dake's avatar
      Explain how to use kolla-ansible pull · 50c52081
      Steven Dake authored
      During multi-node, it is possible for master target node images to
      be older then the Ansible master playboks if the repository is
      updated.  Add documentation to explain this situation.
      
      Change-Id: I2ccf57004147873e89f23fbb996d01f550e90c3f
      50c52081
  8. Mar 12, 2016
  9. Mar 11, 2016
    • Swapnil Kulkarni (coolsvap)'s avatar
      Restructuring the Quickstart guide · 333ee4e7
      Swapnil Kulkarni (coolsvap) authored
      We need the gcc and other dependencies
      installed before we can do any tox related
      commands.
      
      Installation of git was never checked in QSG.
      I happened to create a baremetal CentOS server
      with minimal install and there was no git.
      Added steps to install git.
      
      Moved the steps related to git clone and other
      kolla configuration after basic installation.
      since tox fails for gcc.
      
      In the quickstart guide we are generating
      the configuration using tox but tox is not
      installed before doing so. Adding steps to
      install tox before generating conf.
      
      Change-Id: Ic8a756e66d33963e47607ed60c4c768e0859152d
      333ee4e7
  10. Mar 10, 2016
    • Martin André's avatar
      Provide instruction to generate kolla-build.conf · 3105580d
      Martin André authored
      Although not strictly mandatory, it's less confusing to have
      a kolla-build.conf file in /etc/kolla that users can modify it they
      want to customize their builds, rather than to rely on defaults
      settings and command line options.
      
      The `tox -e genconfig` was already documented in "Image building" doc.
      
      Change-Id: Ia44e6f28ce18601cdaba5109ea12cd50fa8372b2
      Closes-Bug: #1532066
      3105580d
  11. Mar 03, 2016
  12. Feb 27, 2016
    • Rajath Agasthya's avatar
      Recommend vagrant and heat for development only · 58ef5fee
      Rajath Agasthya authored
      Vagrant and Heat, while really cool tech, are not very well maintained
      in Kolla. They are not always up to date, and as a result, are not
      recommended for evaluation purposes by this change.
      
      TrivialFix
      
      Change-Id: Ic8b8519431ed5c50a9a46b2e8b8f822d0982b1cf
      58ef5fee
  13. Feb 26, 2016
    • SamYaple's avatar
      Change kolla_internal_address variable · d3cfb205
      SamYaple authored
      Due to poor planning on our variable names we have a situation where
      we have "internal_address" which must be a VIP, but "external_address"
      which should be a DNS name. Now with two vips "external_vip_address"
      is a new variable.
      
      This corrects that issue by deprecating kolla_internal_address and
      replacing it with 4 nicely named variables.
      
      kolla_internal_vip_address
      kolla_internal_fqdn
      kolla_external_vip_address
      kolla_external_fqdn
      
      The default behaviour will remain the same, and the way the variable
      inheritance is setup the kolla_internal_address variable can still be
      set in globals.yml and propogate out to these 4 new variables like it
      normally would, but all reference to kolla_internal_address has been
      completely removed.
      
      Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5
      Partially-Implements: blueprint ssl-kolla
      d3cfb205
    • Michael A. Trimm's avatar
      Fixed slight gramatical issues that could be considered confusing · f9b60387
      Michael A. Trimm authored
      
      Signed-off-by: default avatarMichael Trimm <mitrimm@cisco.com>
      Change-Id: Iccd3c53526caf8b109ba4ede117eebf66958782d
      f9b60387
  14. Feb 25, 2016
  15. Feb 24, 2016
  16. Feb 23, 2016
  17. Feb 22, 2016
  18. Feb 18, 2016
    • Suhail Syed's avatar
      Refined documentation regarding registry · 2ccb83ce
      Suhail Syed authored
      The documentation had old information about running
      docker registry version 1.  Documentation improvement
      uses exclusively Docker register version 2.
      
      TrivialFix
      
      Change-Id: I320341c1a646eeeec35fb928a970f4d7e8a13bb9
      2ccb83ce
    • Éric Lemoine's avatar
      Fix typo in quickstart · bc3d4715
      Éric Lemoine authored
      TrivialFix
      Change-Id: I885995498ac70251e317c49c9374c9850165af89
      bc3d4715
  19. Feb 17, 2016
  20. Feb 16, 2016
  21. Feb 12, 2016
    • Naren Narendra's avatar
      Clarify Ansible installation for distros in docs. · e4a659e0
      Naren Narendra authored
      For CentOS, install from distro packaging by default.  Explain
      how to install on DEB based systems from packaging when they
      update to a newer version of Ansible.  Finally, clean up the
      ordering of the dependencies for a pip based install.
      
      TrivialFix
      
      Change-Id: I9564a03c2e75fd30b5ec9c7d64f5defb709d7fde
      e4a659e0
  22. Feb 09, 2016
  23. Jan 24, 2016
  24. Jan 16, 2016
  25. Jan 14, 2016
  26. Jan 03, 2016
    • SamYaple's avatar
      Documentation improvements. · 64a75735
      SamYaple authored
      The version changes in docker are needed to support named volumes
      which are replacing data containers in our implementation. Docker
      is no unblocked upstream for us thanks to our new kolla_docker
      module so I removed the cap on that as well.
      
      Change-Id: I847979b9f7c9e42a55273b5ee926a4aff19a7bec
      64a75735
  27. Dec 24, 2015
  28. Nov 23, 2015
    • Hui Kang's avatar
      Create openrc file on the deploy node · 46673b81
      Hui Kang authored
      This task is run as a post-deploy playbook
      
      Implements: blueprint ansible-task-generate-openrc
      Change-Id: I69f4ee895094da5c73494a41dccb2e86eb481656
      46673b81
  29. Nov 20, 2015
  30. Nov 13, 2015
  31. Nov 09, 2015
    • Steven Dake's avatar
      Add registry information to quickstart.rst · dcd4f3fa
      Steven Dake authored
      We get an awful lot of questions about how to operate with a registry
      on the IRC channel and the obvious way to fix that is to document it.
      
      I don't know what to document about Ubuntu but if someone leaves the
      appropriate commands in the review I'll be happy to update it to include
      the correct operations to make the registry run on Ubuntu.  Another option
      is perhaps we can get Sam to write those docs once this hits the repo since
      the structure will be mostly in place.
      
      TrivialFix
      
      Change-Id: Ib88abbaf9bd6bcabddae994157d9288aab8be2bf
      dcd4f3fa
Loading