We upgrade the rst convention by following Documentation Contributor
Guide[1].
[1] https://docs.openstack.org/doc-contrib-guide
Change-Id: Ieceb3942073512fb10670a48d258c4055909496e
Partially-Implements: blueprint optimize-the-documentation-format
We upgrade the rst convention by following Documentation Contributor
Guide[1].
[1] https://docs.openstack.org/doc-contrib-guide
Change-Id: I0e4184e24210f920ea5e7b33e4878385a0758a01
Implements: blueprint optimize-the-documentation-format
We upgrade the rst convention by following Documentation Contributor
Guide[1].
[1] https://docs.openstack.org/doc-contrib-guide
Change-Id: Id480cd24f5eed810e81af0f12e84a4a6db49247d
Partially-Implements: blueprint optimize-the-documentation-format
We upgrade the rst convention by following Documentation Contributor
Guide[1].
[1] https://docs.openstack.org/doc-contrib-guide
Change-Id: I825deadefcf996732a03e61c8fd19cfd6a498e77
Partially-Implements: blueprint optimize-the-documentation-format
This change makes it so that if preconfigured database users are used,
the attempt to change the log_bin_trust_function_creators mysql
variable isn't made anymore.
Also updated the upgrade docs
Change-Id: I356313952d435de6d3b5444c0dd8a71f45aee452
Closes-Bug: 1748269
We upgrade the rst convention by following Documentation Contributor
Guide[1].
[1] https://docs.openstack.org/doc-contrib-guide
Change-Id: I10660e2df0e57be0800e26aa4d320074084c3acf
Partially-Implements: blueprint optimize-the-documentation-format
This change allows the following use cases:
1. Using an already-configured MariaDB / MySQL server / Cluster
2. Using already-created DB users, without requiring root DB access.
Update: added external mariadb precheck
Change-Id: I78b0d178306d7c5293b0bf53e445f19f18b4b824
Implements: blueprint external-mariadb-support.
Closes-Bug: #1603121
doc/source/user/quickstart.rst:194: D001 Line too long
doc/source/user/quickstart.rst:337: D001 Line too long
doc/source/user/quickstart.rst:339: D001 Line too long
Change-Id: Ibbb3588bddf3bfe9d49c2b2b6909f80c36ec2aff
Using external Ceph with Kolla means there is no storage node for
kolla, but cinder-volume must be run on nodes(it can be controller
nodes or compute nodes), and the external-ceph-guide miss storage node,
this patch to fix it.
Closes-Bug: #1740028
Change-Id: I6cfb86c5c0d7b30291bd9f263fb030e4703d9602
Nearly full rewrite of our QSG to make it more 2017.
Co-Authored-By: chenxing <chason.chan@foxmail.com>
Partially-Implements: blueprint ka-queens-doc-restructure
Change-Id: Ie558e1121438a502611c7c0e6c0e5ac0f6574827
when cinder use external ceph, and edit the cinder-backup.conf follow
the external-ceph-guide.rst, cinder will backup failed because the
backup_ceph_user is not cinder-backup, the patch to fix it.
Change-Id: Ie7213c1280b2b8fc0a4648d09d9ba132427952aa
Closes-Bug: #1740222
when use external ceph, kolla need set ceph to "no",this way by default, the
gnocchi_backend_storage will be file, refer to [0]. we should set
it to ceph, this patch to explain in docs.
[0] https://github.com/openstack/kolla-ansible/blob/master/etc/kolla/globals.yml#L302
Change-Id: If35082531e9de4524299fe4fc7e97bec5a6c2c79
add domain_name for multi-regions. When deploying regiontwo，
nova_compute simple_cell_setup will use domain_name.
Change-Id: I2f4171e1469966140ccccb38540fa5c54258bdfb
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 some scenarios it may be useful to apply custom filters to logs
before forwarding them. This may be useful to add additional tags to
the messages or to modify the tags to conform to a log format that
differs from the one defined by kolla-ansible.
Configuration of custom fluentd filters is possible by placing filter
configuration files in ``/etc/kolla/config/fluentd/filter/*.conf`` on
the ansible control host.
Change-Id: I29a20efb0df4bf3564ef009616c786e928aa26d9
Implements: blueprint fluentd-custom-filters
