The kolla-cli is deprecation [1], it should be clean up from
kolla-ansible's cleanup-host script
[1]: https://review.opendev.org/#/c/749045/
Change-Id: I7072de235d9d629b0f538dc98c5258ee5f023376
Not everyone wants Kafka data stored on a Docker volume. This
change allows a user to flexibly control where the data is stored.
Change-Id: I2ba8c7a85c7bf2564f954a43c6e6dbb3257fe902
This allows you to tune the performance of InfluxDB by locating the
volume on a drive that is separate to the default docker storage.
Change-Id: Iea555a2702b225b30f5d7035b8a703d4f3376ee7
Kolla-Ansible Ceph deployment mechanism has been deprecated in Train [1].
This change removes the Ansible code and associated CI jobs.
[1]: https://review.opendev.org/669214
Change-Id: Ie2167f02ad2f525d3b0f553e2c047516acf55bc2
User can use custom directory for nova instance.
For example using a shared file system as backend.
Change-Id: I11fe4891719a2e2a34888d8b798df5602e294e4f
When running the kolla-ansible destroy playbook most of the files
under /etc/kolla are cleaned up. This change will cause the
clean-up to skip the kolla-cli related directories. When running
the deployment code in a container or a separate VM this is not
an issue, but when doing an all-in-one or running the deployment
process from one of the systems being deployed onto it would have
previously destroyed the kolla-cli inventory and any generated
certificates used for TLS.
Change-Id: Icd62e177964b8fb31052131785c6d7b138975a28
- This change creates a new role to
support deploying ovs with dpdk.
- This change introduces an enable_ovs_dpdk
variable to enable ovs with dpdk as part of
the deploy action.
- This change extends the ovs-dpdkctl.sh tool
to correctly deploy ovs-dpdk on Ubuntu and CentOS
hosts.
- This change extends the cleanup-host tool
to correctly uninstall ovs-dpdkctl.sh tool and its
systemd files if present on the host.
- This change automatically configures userspace
kernel drivers.
partial-implementes: bp/ovs-dpdk
Change-Id: I55858d81df437e8258705b75426f61ab9b907c7d
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
This seems to have got lost during repo split. Adding it back in now.
Change-Id: Ic0b0f5efb12eab58e7872b30611a39640dc44cc2
Closes-Bug: #1629224
(cherry picked from commit e1a2f99014a1aeb3697e8ec3c999cdc12380376b)
Move ovs-cleanup step to cleanup-containers,
otherwise bridges will not be removed because neutron_openvswitch_agent
container does not exists after running cleanup-containers.
Add logic to cleanup ovs bridges only when openvswitch_db
is removed and openvswitch-agent is running,
so when removing other container from a parameter at script
invocation ovs-cleanup will not be executed.
Change-Id: Ie5fea40426df0e9e465fc173aba185f61098f676
Closes-Bug: #1640178
- One of the usecase supported by tools/cleanup-containers
was the ablity to remove container with a regex so that
you could redepoloy just that single componet.
- By cleaning up ovs in cleanup-containers that is nolonger
possible.
- This change move the cleanup of ovs from,
tools/cleanup-contianers to tools/cleanup-hosts
TrivialFix
Change-Id: If2001130f4a2400555ce4d9ac5ee506482e4c25e
new cleanup-host script removes kolla-build.conf
in /etc/kolla directory which contains the build
configuration for building images.
This should be preserved.
Change-Id: I20fbf3f8a2400a5e048ba55beb0c8e1ec849d8a3
Related-Bug:#1561055
Kolla deployment creates /etc/kolla folder on a target host
with multiple configuration files. In some scenarios,
the presence of these files prevent successful deployment
of certain services especially when their configuration parameters
have been changed on the deployment host.
Change-Id: Iefd544b50fc90b7f00d6e137bc14ab4807ef7c0f
Closes-Bug: #1561055
After run cleanup-containers script, was necessary to
clear references to the ceph in fstab file manually
Change-Id: I264e6644d5d569a9b56115ea31b15589b093c3f9
Closes-Bug: #1562991
Split the content of cleanup-containers into containers cleanup and host
cleanup. This allows to run the cleanup-containers from OSX clients,
while keeping needed code to delete host artifacts left behind by the
neutron agents container.
In addition, cleanup-containers may disappear in the future, replaced by
a docker-compose wrapper.
Co-Authored-By: Martin André <martin.andre@kvhasia.com>
Co-Authored-By: Swapnil Kulkarni <me@coolsvap.net>
Change-Id: I3aa731e7e0f9eb3dad9c363bb5d4a575d84a2fae
Closes-Bug: #1477383