Previously, Heat was deploying Fedora21 instances with firewalld
enabled and running. It is well documented that firewalld causes
problems with OpenStack Neutron. That is becasue Neutron uses
iptables instead of firewalld for security filtering.
Change-Id: I25cb32984841423a7b1c44b55cd19b5b4588c9e8
Previously, Kolla nodes deployed using the Heat template did not
contain OpenStack clients. This patch adds the OpenStack client
packages.
Change-Id: I72a4db1e4edc7350adf5b302955d39182cc58a58
NEUTRON_SHARED_SECRET was being generated incorrectly. It had a colon
at the front, which causes nova not to operate.
Change-Id: Id0d9390fa60b3d946513098fed394aaba3a53c70
Previously, only start/stop scripts existed. The status script
runs docker-compose ps for each container so users can
get a quick snapshot of their Kolla environment.
Change-Id: I3204f3e7404ad906d5330cf67d091fc1f06d3030
Previously, Neutron was not included in the start/stop scripts.
This patch reads the NETWORK_MANAGER value from openstack.env
to start/stop either nova or neutron networking.
Change-Id: I85b31396c2b816b89f33206443c3d60cb4b7914b
Tell users to pull docker-compose from Docker Inc.
Recommend rc3 or greater
Tell users the thread where the bump releases are being discussed
Fix typo in libvirtd
Change-Id: Ib47d3a57452a4266db2b47b41a789908365fda9b
The libvirt package has a dependency on systemd-libs and systemd,
while the centos 7.1 container installs systemd-container-libs
and systemd-container. We don't need either of these systemd tools
but they reuslt in a broken build of the system if they are missing.
As is, the libvirt container will not build.
Change-Id: I8e5aac0e3a7e9d88a81733a3048971fe9d48ba56
Previously, debug logging was enabled by default. Only verbose
logging should be enabled by default.
Change-Id: I5a1fc805284be777dd49c79cc344a5e8600a238d
Previously, Fedora was set as the default image prefix. Since our
reference architecture focuses on CentOS, the default image prefix
has been changed accordingly.
Change-Id: I794ac1aa035d793204fa315752ae8188ce872a3e
Previously, compose would generate an error because the
neutron-agents.yml file was missing a space for the restart policy
line.
Change-Id: Ib17c4c726dcfcda780a242ebe22474e9252cac8a
Previously, check_required_vars was requiring log file variables
to be set in openstack.env. This would cause an error when
starting nova/neutron containers that used default (blank) log
file settings. Since the log files are not required
for the services to start, the default log files are left blank
(without a value in the K/V pair). This patch removes the
log_file variable for check_required_vars in each nova/neutron
script.
Change-Id: I169baab28f63a0e0ae06c8aef21b5e8d3155bdda
Previously, the agents ran in seperate containers. Since some of
the agents create and use network namespaces, runnning them in
seperate containers has become a challenge. This patch adds
neutron agent support in a single container.
Partially Implements: blueprint compute-operation-neutron
Change-Id: If4f893abd50d90b58e8435ec2659870dce36951c
Previously, compose was being pulled from sdake. Since pull 1011
for pid=host support was merged, we can now use the upstream repo.
Additionally, the heat template was using the Kolla ml-3 release.
Since ml3 was cut, trunk should be reverted to using Kolla trunk.
Change-Id: I44ad01ee9fde914c87d981c05b825fa549420f8c
Previously, Heat was using the docker-1.5.0-dev version of the
Docker binary. This PS updates the Heat kollanode template to use
the latest version of the Docker binary used by the project due to
https://github.com/docker/docker/issues/11760#issuecomment-88288278
Change-Id: I1c771b89758baa9faaa04a0e647a23f32bff48a9
Previously, logging was hard coded into the nova and neutron
containers. This patch creates two common params for logging:
DEBUG_LOGGING
VERBOSE_LOGGING
and sets default values of verbose=true and debug=false. This patch
implements logging for Nova and Neutron. Add'l OS service config
scripts and images will need to be updated to use the logging
params.
Change-Id: I03d48005d5b4789aa3c519879a20d963ef1cbaa3
The EXPOSE options will create a local docker-proxy. This is
unnecessary with --net=host mode. The docker-proxy adds about
20 microseconds of latency. Add documentation to the specification
to indicate where to find the ports that are exposed by the
services in case someone were to desire to add EXPOSE back to
the Dockerfiles.
Change-Id: I398e922fe096d6022a2d5985bb92498f89a5ea31
COPR is a repository for third party packages built by the Fedora build
system. Instead of dragging in 250MB of dependencies to build pam, build
externally and load only the RPM into the image.
The pam that is built externally is built with the --with-noaudit flag
and a Provides: pam line.
Change-Id: I28396996943d2fdc12b253faf62af8623c8b0e73
the libvirtd package "Provides" wwas removed from the libvirt packaging.
To workaround this problem just install libvirt-daemon in CentOS 7.1 or Fedora
20+.
WIthout this change, an install of libvirtd does not actually install
libvirtd. The yum tool will not fail if libvirtd is specified so we weren't
catching this in the build.
Change-Id: I81e64f6f659aa0466369dad4b0574ebb24c99555
Clean up version info since all those problems have been fixed in rc3.
Add separate sections for each major section of the document.
Change-Id: Ic011b56872e4cee70f668af58275f31cf083d027
We no longer bindmount qemu directories and instead use the
volume_from feature to get that job done. As such remove the
creation of the directory.
Change-Id: I20aa0b5d8b8e5e0bd9ccc69ab07009635c693b02
Previously the start script would disable SELinux That is a policy
choice by the administrator, not something that should be done in a
development tool. Instead suggest setting SELinux to permissive mode
manually.
Change-Id: I342a1614f9c10ec066cd2a8dc79280481e0b7570
This ansible module for docker-compose allows for idempotency. I have
submitted a pull request upstream to ansible-modules-extra to include
this new module. When/if the module is accepted upstream if can be
removed from the local module library.
The two playbooks have been updated to use this module. The database
data container does not support idempotency due to the fact that it
exists instead of sleeps. Therefore each time `docker-compose up` is
called, it will start the container and register a change. The
message-broker does not have this issue and will remain unchanged even
repeatedly running these playbooks.
Due to the use of a special branch of docker-compose provided by sdake,
this module requires at least docker-compose==1.2.0rc1
Change-Id: If1644eaa3bff0c2a007fa2d479a95bea941945f6
