Age | Commit message (Collapse) | Author |
|
The return code check after the DB user creation was inverted, which results
in false reports of errors, and post-insts that are not cleaned up.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Havana requires the pip module, so we add it into glance's runtime
dependencies. This package comes from meta-oe, so an up to date checkout
is required.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
We need a newer python-babel for the uprev'd havana components.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The havana nova-compute requires python-six for python2 -> 3 compatibility
so we add it into the RDEPENDS of the common python-nova package.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Havana component require a newer python-six, so we uprev to the 1.4.1
version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Upreving the swift component to the havana release. At the same time,
we switch to building from git.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Updating the cinder block storage component to the havana release.
At the same time, we switch to a git based build.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
While updating to the havana release version, we also switch to git based
builds.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The havana horizon component requires jinja2 for template services.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To support the havana horizon dashboard we need at least the heat
client APIs available on the controller. We introduce this package
first, and the full heat implementation later.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To support the horizon dashboard, we require at least the ceilometer client
application and libraries. The full server/application will be introduced
later.`
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To provide compression and template capabilities the havana release of
horizon requires lesscpy.
But lesscpy is typically a python3 acript, so not only do we introduce
the recipe, we make it compatible with python2.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The python LESS compiler requires python-ply, and horizon requires
python LESS. So we introduce python ply to meet the rutime
dependencies.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
OpenStack Havana requires a newer version of websockify, so we uprev to
0.5.1.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In the havana release, keystone depends on dogpile to provide locking
and cachine functionality.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To work with havana, nova needs to reference neutron and not quantum.
We also add dependencies that the uprev has added.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
As part of the glance uprev to havana, we switch to a git based build.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Updating the keystone OpenStack component to the havana release version.
As part of this switch, we also start building out of git versus the
release tarballs.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Updating the OpenStack networking component to the havana release version.
As part of this switch, we rename the components from quantum to neutron
and switch to a git based build for the client and servers.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
This commit uprevs the nova component to the havana release version, and
switches the build from tarballs to using the git repository. No other
runtime changes are made at this point.`
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
OpenStack havana nova requires oslo 1.2.1+ for configuration management, so
we uprev our support.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
pbr is a runtime dependency for OpenStack havana component configuration.
This initial packaging only provides runtime library support for configuration
parsing and management, and is not intended to replace build system support
for setuptools or provide on target self tests.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
oe-core has a newer python-setuptools available, so we update our bbappends
to include that new version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Without adding the initscript package, postgres won't start automatically
on boot.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When using the target installer with postgresql can end up installing
in the wrong order due to bad dependencies and cause the install
transaction to fail as follows:
====
initdb: invalid locale name ""
initdb: invalid locale name ""
initdb: invalid locale name ""
initdb: invalid locale name ""
initdb: invalid locale name ""
could not open directory "/usr/share/postgresql/timezone": No such file or directory
sh: locale: command not found
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
/etc/init.d/postgresql: line 25: start-stop-daemon: command not found
====
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
|
|
After the merging of python-nova-controller and python-nova-compute, we were
missing the inherit of useradd bbclass. As a result, there wasn't a valid
nova user and group on the system.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Since we can't count on package postinst order, many components check for
a configured postgresql daemon, and if not found, initialize it.
Rather than sprinkling the knowledge of how to initialize the database
through all these packages, we create a more robust, central postgresql-init
script, and call it when any component needs the database configured.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The split of compute and controller is no longer necesary, since configuration
inheritance is done with overriding layers, not split recipes.
This simplifies the build, and packaging of the recipe. Good riddance.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
pre-0.4.0 versions of python greenlet are known to segfault and cause
general instability.
We temporarily carry 0.4.1 here, until meta-openembedded is upgraded
to have a new enough version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
pre-0.4.0 versions of python greenlet are known to segfault and cause
general instability. So we set our preferred version to 0.4.1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The network and compute images have a MIT license, but are missing the
required checksums. Adding it removes a checksum error during the build.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
novnc is required for horizon serial console access, so we add it to the
controller task by default.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
With this commit the appropriate daemons are started on a control node boot to
support horizon console access via the novnc proxy.
Additionally, the proper nova configuration is set for boh the control and
compute nodes for out of the box console connectivity between the compute,
control and horizone interface.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
syncing the documentation to match the current layers, configuration and
launch.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To make keystone work properly in a node with "real" IP addresses,
both the configuration and identity setup script should use the
external address and not localhost.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Since external IPs can now be used, we can unify the IP configuration to
the single global file.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To allow both a controller and compute node to use the same nova.conf,
we can switch in more use of %CONTROLLER_IP% and less use of localhost.
We also disable the firewall configuration by default, it can be re-enabled
by subsequent layers.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
${NOVA_CONF_DIR} points to the staging/build directories, so it shouldn't be
placed into on-target config files. Using ${sysconfdir} is the right, on-target,
directory to use.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Replace the controller and compute specific deployment classes with the central
"hosts" class, and change the configuration file update routines to use the
new values and externally visible IPs.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
For proper operation of quantum in both a control and compute node, the
following items are required:
- The controller IP set to the rabbit_host
-
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Various components (such as rabbitmq) have checks for minimum amounts
of free space on a image. If those checks fail, the service exits in
a hard to debug manner. To ensure that these services run, and meet
typical usage scenarios, we increase the free space in the image to 3G.
Finally, we inherit openstack-image-base, to trigger simple rootfs
configuration and deployment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Various components (such as rabbitmq) have checks for minimum amounts
of free space on a image. If those checks fail, the service exits in
a hard to debug manner. To ensure that these services run, and meet
typical usage scenarios, we increase the free space in the image to 3G.
We also automatically include the network node packages into this image
type, to ensure that full quantum functionality is available.
Finally, we inherit openstack-image-base, to trigger simple rootfs
configuration and deployment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
For systems with non-volatile /var mounts, adding /var/log/rabbmitmq
to the main package allows logging to be enabled by default. For
volatile /var based systems, it does no harm, but does not always
create the directory on boot.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To allow better out of the box configuration of postgresql, two things
are required: listen on all addresses, and add explicit permissions for
the known nodes in the network.
In this change, the former is done by adding listen_addresses = '*' to the
generated postgresql configuration on first boot, as well as adding the
known compute and controller IPs to pg_hba.conf. (note: the values for these
IPs come from hosts.bbclass)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To facilitate the creation of a simple OpenStack configuration with
a single control and compute node, several things should be known
at build time (since in this simple configuration, we are not using
dhcp, or other name resolution techniques):
- The IP of control node
- The IP of the compute node
- The IP of the node being built
From these values, the OpenStack components and support applications
(databases, access control, etc) are configured, as well as simple name
resolution generated at build time.
A single "hosts" bbclass should be provided with the following values:
COMPUTE_IP ?= "192.168.7.4"
COMPUTE_HOST ?= "compute"
CONTROLLER_IP ?= "192.168.7.2"
CONTROLLER_HOST ?= "controller"
MY_IP ?= "${CONTROLLER_IP}"
MY_HOST ?= "${CONTROLLER_HOST}"
The above example is for a control node, using the runqemu default addresses.
The openstack-base.bbclass is responsible for generating /etc/hosts and
/etc/hostname. Any image type that requires these values at boot tiem, should
inherit this class to allow its rootfs post population hooks to run and
generate the required configuration.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
On some targets postgresql's server processes start slowly. If they haven't
started and the admin account or other operations are attempted, they fail
with a message about not being able to communicate to the local server.
If postgres is not properly setup, then subsequent components will also fail,
since they either cannot talk to the server, or can't use the 'admin' account.
To fix this issue, we add additional sleep states, and attempt to create the
admin role 10 times, with a delay between each attempt. If we fail to contact
the server after 10 attempts, a clear message is displayed and the postinst
returns a failing return code.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|