Age | Commit message (Collapse) | Author |
|
convert FILESEXTRAPATHS to FILESEXTRAPATHS_append to avoid warnings from
the latest oe-core.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Instead of creating tenant/user/role and service/endpoint for all
openstack services in keystone postinstall, now each of the services
creates its own keystone identities by queueing them up in its postinstall
to a file /etc/keystone/service-user-setup. service-user-setup
script, when run as the last postinstall, calls identity.sh with keystone
identity parameters to create necessary identities for the services.
Signed-off-by: Andy Ning <andy.ning@windriver.com>
|
|
The tests included with nova require some files that are within the
"plugin" directory. This fix includes the "plugin" directory on the
target system as part of the recipe. This fix also includes a patch
that updates the tests to find the "plugin" directory where it is
installed on the target system.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
|
|
The tests included with nova require some setup and configuration
files that are within the "doc" directory. This fix includes the doc
directory on the target system as part of the recipe. This fix also
includes a patch that updates the tests to find the "doc" directory
where it is installed on the target system.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
|
|
The api-paste.ini file shipped with nova is installed into the
/etc/nova directory on a target system. The tests included with nova
expect the file to be relative to the location of the tests within the
source tree. This fix sets the absolute path to the api-paste.ini
file as it exists on the system.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
|
|
Nova requires the python-coverage to be available in order for the
unit tests supplied to pass. This fix adds a recipe in order to build
the coverage tool. It also adds the dependency to the new package to
the recipe to build nova.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
|
|
The metadata service is working as the following:
- metadata is being served by nova-api on controller at port 8775.
- VM instance requests metadata by 169.254.169.254 (eg, curl http://169.254.169.254/latest/meta-data)
- metadata request comes to neutron-ns-metadata-proxy on controller in dhcp network name space.
- neutron-ns-metadata-proxy forwards the request to neutron-metadata-agent through a unix domain socket (/var/lib/neutron/metadata_proxy).
- neutron-metadata-agent sends the request to nova-api on port 8775 to be serviced.
To support metadata service, neutron-ns-metadata-proxy is baked into the controller image. Also neutron-metadata-agent startup script
(/etc/init.d/neutron-metadata-agent) and config file (/etc/neutron/metadata_agent.ini) are added to start up metadata agent at system
initialization. dhcp_agent.ini and nova.conf are updated as well.
A README.metadata is added in the Documentation/ directory.
Signed-off-by: Andy Ning <andy.ning@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Updating the recipe's branch and SRCREV to the icehouse/stable release
branch.
The configuration changes required for basic operation are limited, so
we keep nearly everything the same, and will update the config in
subsequent commits.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Editing the files in ${WORKDIR} using sed or similar tools as part of
do_install means they can only be edited once. Supplying a modified
CONTROLLER_IP in local.conf and building the image again will not
result in the CONTROLLER_IP being properly updated since the
substitution placeholders will no longer exist. We therefore simply
swap the other of things, installing the configuration files first,
then editing them to swap the placeholders. This means we can run the
do_install again and again and get the results we expect.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Package and enable the bash completion suppor that comes with the
various client packages.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
argparse is part of python 2.7+, so there's no need to install the .egg
version of argparse.
Nova was pulling in this requirement, which doesn't cause a problem until
another python app includes both argparse and the built in one.
That results in the following:
UserWarning: Module argparse was already imported from /usr/lib/python2.7/argparse.pyc, but /usr/lib/python2.7/site-packages is being added to sys.path
So we drop the argparse dependency, everything still works and we no longer
have the warning.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
We modify the controller so that both vnc and spice html5 proxies are running.
Since in the current recipe, both controller and compute share the same nova.conf
file, in the compute, both vnc and spice html5 are set to enabled and in this
configuration, vnc is chosen (in source: vnc is chosen because it's better
tested).
To change to spice, only change required is on the compute side.
The controller (since the default console_type is auto) will try to talk
to both and run whichever is available.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
nova-novncproxy and nova-spicehtml5proxy both do not check to see if the process
specified in PIDFILE exists before firing off a new one. Both initrd files can
actually use nova.init (used for the many other nova-* daemons)
nova-consoleauth also has this issue, we add a check in start to see if the process
in PIDFILE exists and exits if it does.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Package spice-html5
Modify python-nova to add infrastructure for nova-spicehtml5proxy
support.
Note: spice is the default
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Enable nova-compute to:
* use cinder volume stored in a ceph pool as a block device
* store glance image into a ceph pool.
Also port 2 patches from https://github.com/openstack/nova
branch master into Havana branch.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
Currently all the openstack components have default start level
of 20. There are other services such as glusterfs, rabbbitmq,
database... are also starting at the same start level. On some
platform, this can cause racing condition between services which
in turn causes some of openstack components not started.
By adjusting the openstack components start level to higher will
ensure that system services start in the determistic way.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Several python packages require 'python-pbr' both at build and
runtime, as listed in their respective setup.py files, yet this
dependency is not included in their recipe. Adding python-pbr
to the RDEPENDS to correct this.
In addition this situation is complicated by the fact that the
setuptools will actually fetch python-pip and python-pbr eggs,
regardless of the value of BB_NO_NETWORK, if any of these packages are
built before python-pip and python-pbr are in the sysroot. Most
dramitically if you were to attempt to build any of these packages
with no network connectivity the do_compile() task will fail with the
following:
| DEBUG: Executing shell function do_compile
| Download error: [Errno 110] Connection timed out -- Some packages may not be found!
| Couldn't find index page for 'pip' (maybe misspelled?)
| Download error: [Errno 110] Connection timed out -- Some packages may not be found!
| No local packages or download links found for pip>=1.0
| Traceback (most recent call last):
| File "setup.py", line 21, in <module>
| pbr=True)
Adding the missing DEPENDS will ensure these packages are available
without the need for setuptools to fetch them, and avoid possible
build issues due to network connectivity.
In order to test these modifications all of these packages have been
built with a populated sstate cache and the network crippled using:
iptables -A OUTPUT -p tcp --destination-port 80 -j DROP
to ensure no extra fetches are taking place.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To properly sync the nova database during boot, the migrate.cfg must be
present in the rootfs.
This wasn't currently being packaged, so we add it to the manifest.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Installation from package feeds shows some missing REDPENDS for the
-setup packages.
Signed-off-by: Rob Wolley <Rob.Woolley@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Since python-nova uses the group "libvirt", which is created by the
libvirt recipe, we must specify libvirt explicitly in DEPENDS.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
With this change we now run both the nova controller services and compute
node agents as the dedicated "nova" user.
Changes to configuration were made to relocated locks and logs to nova
writeable directories. Wherever possible configuration files and directories
have been changed to nova instead of root (with the notable exception of
rootwrap configuration).
nova has also been granted sudo privileges to run rootwrap commands.
And finally, a libvirt system group has been created and nova added to
that group. This allows the compute agent to communicate with libvirtd
via the "libvirt" group while keeping permissions tight.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
After moving all database creation initialization packages, we also
remove it from the RDEPENDS of the various control node recipes.
This allows images to select database initialization or skip it.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Rather than use the catch-all "nova-all" initscript, we switch to
one initscript per-service. The old nova-all is still installed, but
not linked as an initscript, so it can be used as a fallback.
In addition to per-service initscripts, we switch to generating those
initscripts from a common template script.
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>
|
|
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>
|
|
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>
|