Currently init-runonce script changes directory to the
script's base directory (/usr/...) before doing anything else.
This unnecessarily _forces_ a non-root user to use sudo for
running this script thereby raising privileges for code which
doesn't want it. Also downloading temporary stuff in places like
/usr... seems not a good choice.

Hence deleting the said code part and letting the deployer work
comfortably from any directory.

Made documentation changes accordingly.

Change-Id: Ib3c7ed97aa5f53c115b6337aaf572b5fdc7a71f3
Closes-Bug: #1732963

In kolla-ansible "quick start" document, the python-openstackclient
is recommended. It is better to validate Swift with "openstack"
commands instead of "swift" commands.

Change-Id: I6287b40f702de2f3c270109803fad8d93a903c01
Closes-Bug: #1732857
Signed-off-by: Tone Zhang <tone.zhang@arm.com>

Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.

Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.

This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.

Change-Id: I72537ef7a9c56221fb13d11b4fc5aef9c7446601

Change-Id: Ica929fd8d3ef1972fec0daeb4ae2c00b9a9be3a0

The current syntax of Ubuntu fluentd rewrite rules are not supported
anymore, reference to this commit[1].
According to the build of this patch[2], The Centos has no such isuue.
Only Ubuntu needs to be upgrade to use the <rule> section.

* Centos use 01-rewrite-0.12.conf.j2
* Ubuntu use 01-rewrite-0.14.conf.j2

backport: pike

[1] https://github.com/fluent/fluent-plugin-rewrite-tag-filter/commit/248ed8e97def0a60121199c0d0e2fa8785f0d076
[2] https://review.openstack.org/#/c/517907

Depends-on: I47985113fe732569d640a262ca832c6edc8c2bb6
Change-Id: I0b131c2f65652cf3c61b33d8162097b047603923
Closes-Bug: #1730664

Change-Id: Id71c1ecda9f8647a0eb290fe02a12afb3df09988

  1- Expand and migrate database in first keystone node
  2- Upgrade all nodes sequentially along with updation of each node's
     configuration file with latest release version
  3- Last keystone node, contract database

With this patch, there is small downtime when all containers are
restarted. It will be fixed in other patch.

[1] http://docs.openstack.org/developer/keystone/upgrading.html#upgrading-without-downtime



Co-Authored-By: Surya Prakash Singh <surya.singh@nectechnologies.in>
Co-Authored-By: Eduardo Gonzalez <dabarren@gmail.com>
Co-Authored-By: Duong Ha-Quang <duonghq@vn.fujitsu.com>

Partially-Implements: blueprint ks-rolling-upgrade-role

Change-Id: I2159af567c40848840ff5e483e7d1f6de760b435

Change-Id: I05d9982f64918abc9da32ca40a25328a15f328d6

Endpoints are updated in pike upgrade,  queens and later
dont need such action.

Change-Id: I13723bafc4bf09c24d9bcd2ec7b4e002ae83aec0

Now that the "openstack_auth" in defined in all.yml,
the freezer should better use it.

Change-Id: Ibe799ce6bb1656994b1e9b6642d1011d9dcf30a7

Change-Id: I094a9f60aa154f92b87c4b4af88296bcc0cb920c

dns-integration extension should be enable when
vmware is used.

Change-Id: I31943146e139108a913b9b5e9a0b0283b8ae4830

We should not assume the VIP is accessible from the deploy node.

Change-Id: I39640f98b4adddb9cb8dfdd09d9fb7ecba15a820
Closes-Bug: #1730651