As a restructure, nothing is changed from the original behaviour and
naming despite the file structure changing. The symlinks to build had
to be updated generating lots of "deleted" and "new_file".
The new structure is:
docker/${base_distro}/${type}/${container}
base_distro == centos, ubuntu, fedora, etc
type == source, binary, rdo
type rdo is a symlink to binary for backwards compatibility
Two new flags are added to the build-all script to support the ability
to support different base distros and a flag to support binary or source
containers.
There are several added folders that are empty to hold the directory
structure for future containers of these types.
To use a prefix other than centos-rdo- you can set PREFIX in the toplevel
directory .buildconf file
Change-Id: Ifc7bac0d827470f506c8b5c004a833da9ce13b90
Previously, vnc was not completely working properly because
nova.conf config flags were not properly implemented in t he correct
containers.
This patch moves the nova.conf config flags for vnc to the proper
containers. Additionally, the patch modifies the proxy client ip
param to be consistent with the param within nova.conf and adds
all the novnc params to docs.
Change-Id: I1944baca64ccd113bbca582784b08f90dc0eff69
Having the dasboard in /dashboard doesn't feel right, especially
since there is no automatic redirect when people browse to the ip or
hostname. Which would be a natural first try. Moving to / now to make
the process behave in a simpler fashion.
Because of a packaging error the js/css wouldn't load properly, next
to that there is an issue with a supposed missing 'manage.py
compress' run. This is handled through Kolla now as well (for the
time being).
There is another supposed bug in packaging that makes webfont.ttf
return a 404. This is because of a missing alias for /static stuff,
and with moving the whole thing to / this gets adressed as well.
Change-Id: I64cd7c9effad6cf9ec7c6a41f34e1184640c8adc
Previously these services would not start because the start
script requires the associated log file to exist. The default
settings for these 2 log files are blank causing the failure.
Since the log files are not required for the services to start,
this patch removes the parameter requirement from both start
scripts.
Change-Id: I84d3d128728075e52282b49d9df229917a34a7b5
In Kilo Nova deprecated proxying options in the DEFAULT group. Instead
they were moved to the "neutron" group. This resulted in the metadata
service not serving up metadata.
See this bug for more information:
https://bugzilla.redhat.com/show_bug.cgi?id=1217999
Change-Id: I4f7eac0100d31c5329f8d1857f6d7da1bb6784da
Neutron was loading a bunch of modules that are not currently
supported in Kolla. Remove them as they were causing problems
loading Neutron.
Partially-Implements: blueprint port-kilo
Change-Id: If53071bbb0a22aa05219b9e99ca6d693f96db4ce
Both of these paths were missing from the configuration
but they appear necessary for Kilo. I'm not clear on why
it worked ok in Juno, perhaps different defaults.
Change-Id: I8b7c375627ada860356f9b9fcc205751083b804c
Partially-Implements: blueprint port-klo
The default dnsmasq configuration file doesn't operate with the Kilo
agents in /etc/neutron when used with the --config-dir option. Instead move
it to a subdirectory.
Change-Id: Iab8a54e879f8e630ba38205750ca9670e82834df
Partially-Implements: blueprint port-kilo
policy.json comes from the openstack-neutron package and is required
for the agents to run. So install it. fwaas_driver.ini has been deleted
in master and in the kilo branch, but the agents won't run without the
file present. So copy one from the Juno release.
fwaas_driver.ini is probably not actually required, but there is a
configuration problem somewhere in our Neutron code base. We are out
of time for the Kilo branch, so this short term workaround should be fine.
Change-Id: I154599925308765349634b1a53e598599fc20ec1
Partially-Implements: blueprint port-kilo
Glance has two undefined dependencies. Without installing these
dependencies out of band, glance will not operate.
Change-Id: I096881467d8e0022d58e6c6f745e610d9332dd82
Partially-Implements: blueprint port-kilo
In Kilo, nova no longer reads the config files automatically. They must
be specified in the command line to run the nova-* tools.
Change-Id: Ifbdf4fd3f952f7bb65e9937b46cf9b96e262c3b0
Paritally-Impleents: blueprint port-kilo
All VNC-specific configuration bits are moved from nova-api-base to
nova-compute and the new nova-novncproxy and nova-consoleauth
containers. The compose specification has been updated to reflect this.
A future patch will make the desired backend configurable (spice/vnc).
Change-Id: I8b64abf125fd1ecd7d3463515e3717dd9bd60420
Blueprint: novnc-container
Change nova networking config to work properly with Neutron Juno and later.
Partially-implements: blueprint port-kilo
Change-Id: I18c324c34b4c3af8526d32b3e42f426ec519750b
This represents making build-docker-images --release build
with the icehouse tag and causes docker-compsoe to pull from
the icehouse tag.
Partially-implements: blueprint port-kilo
Change-Id: I66b2c39abc55c0f47152dd90e696fc46b9c58f50
Zaqar was introduced in Juno, so remove it prior to branching
icehouse, then add it back in after branching icehouse.
Partially-implements: port-kilo
Change-Id: Icce95b4d404e6d8238206716e74f6826bc860860
This sets up nova networking properly to work with Neutron in the Icehouse
release.
Partially-implements: blueprint port-kilo
Change-Id: I0d37411c61d0d705d1ddf39c25c6610ea04f56f1
Add Heat-api-cfn for wait conditions
Magnum needs wait conditions in order to operate properly. heat-api-cfn
is where wait conditions connect.
Change-Id: I56742dd96e4607dc0042d0cef4e18c922f9ed736
Implements: blueprint container-heat-api-cfn
Rather then upgrading to a specific version of OpenStack, just
upgrade to Head. This works for both juno and kilo.
Change-Id: I6305218eabd7de0878e24c8fdae968ac6d612175
Partially-implements: blueprint port-kilo
Previously, network namespaces would not work correctly when
restarting or stop/rm/start the neutron-agents container. This
is because network namespaces created within the container are
associated to the container's pid: /pid/$CONTAINER_PID/ns/net.
With this patch, when a container starts or restarts, the l3/dhcp
agent start scripts will remove any existing qrouter/qdhcp network
namespaces before starting the agents. The agents will recreate the
necessary network namespaces since they are stored in the db.
Closes-Bug: 1444219
Change-Id: Ia86729766fe8c2fc145b3a02d519746b149a73bb
The cirros image uses an old dhcp client which does not work
properly with hardware that has checksum offload enabled. Add
a bootp rule to rewrite the checksum via iptables.
Latest cirros 0.3.33 is afflicted by this bug.
Change-Id: Ibfd1f87af5d0bef9fcb1354121e76e4e0db8ab5e
The nova-config.sh script was exiting because of incorrect shell syntax.
The correct syntax for a regex search is
[[ haystack =~ needle ]]. The .*needle.* is unnecessary. I think this shell
script exited because a period was missing.
Change-Id: I3aca5e0729eb5fedbe9ecb4d75ed85d5a1c7815a
For some reason glance sometimes fails to permanently find keystone
while other services do find keystone. The host also has full access
to keystone. Change wait_for to fail_unless.
This could be a docker bug, a wait_for bug, or some other problem.
Change-Id: I02d611d65b7ffddb9c27101fd60e2a8b7cc25658
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, 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, 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
