| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Update the checksum of Licence.rdoc, since file formate and date in it has been changed,
but the LICENSE has not been changed.
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Li xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Spice is in meta-cloud-services, so we'll move that package config item
there.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
basename -s is not unviversally supported, so we switch to something
more standard.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The meta-python pexpect version was being preffered and masking errors
in the download location. So we switch to the pypi location and we
can once again download.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
syncing the core components to the latest juno hashes. We also introduce
new packages and update others to meet the juno requirements.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The following nova commit:
commit 5cacad3508570ce70b1f9ef620e0508169687fda
Author: Gary Kotton <gkotton@vmware.com>
Date: Tue Jun 3 03:44:40 2014 -0700
Deprecate neutron_* configuration settings
Create a new section in the configuration file called 'neutron'.
Move all of the neutron_* configuration settings to this section.
DocImpact
The table below has the changes:
+---------------------------------+-------------------------+
| 'DEFAULT' Section | 'neutron' Section |
|---------------------------------|-------------------------|
| neutron_url | url |
| neutron_url_timeout | url_timeout |
| neutron_admin_username | admin_username |
| neutron_admin_password | admin_password |
| neutron_admin_tenant_id | admin_tenant_id |
| neutron_admin_tenant_name | admin_tenant_name |
| neutron_region_name | region_name |
| neutron_admin_auth_url | admin_auth_url |
| neutron_api_insecure | api_insecure |
| neutron_auth_strategy | auth_strategy |
| neutron_region_name | region_name |
| neutron_ovs_bridge | ovs_bridge |
| neutron_extension_sync_interval | extension_sync_interval |
| neutron_ca_certificates_file | ca_certificates_file |
+---------------------------------+-----------------------=-+
Means that we need to create a [neturon] section, move and rename
our configs appropriately.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Updating components and support utilities for the juno 2014.2 update.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The upstream project is concerned with a bug in empty schemes with
2.7.3. But since Yocto is 2.7.3 and we get an empty scheme via websockify,
no VNC consoles are possible.
Rather than upreving python (big change), we aren't being hit by the
referenced bug, so we simply make sure that the condition can never
be true.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Juno nova requires 0.6.x for websockify, so we do the update.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Juno removes support for the unified OVS and linuxbridge plugins. So
we switch to the ml2 OVS plugin.
This involves configuration and packaging changes.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
We have three changes in a single commit:
- A runtime substition fix controller IP values
- When the substitions were moved for chef integration, the chef
disabled path wasn't tested. This meant that %CONTROLLER_IP% remained
in the final config files, and broke keystone startup.
- The addition of oathlib to keystone depedencies
- oauthlib is a juno dependency
- A temporary patch to the apache httpd front end modules
- At times keystone would fail to load via apache due to the inability to
load localcontext from oslo. To work around these sporadic failures, an
explicit import was added to the http front end module. This will be
removed in the future.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To support iscsi backends, cinder uses rtslib-fb.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In the juno release, keystone depends on oauthlib, so we introduce the
recipe.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Integrate oslo.rootwrap to meet juno dependencies for core projects
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
oslo rootwrap was missing from the DEPENDS of these core projects.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Horizon had a rather large set of duplicated DEPENDS, to work around
bitbake evaluation order issues. We can now unify the DEPENDS into
a single list, and leave RDEPENDS to deal with arch specific
differences.
We also add missing horizon juno dependencies.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Updating the horizon dependent packages to the juno-rc2 required versions
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>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Instead of having a central file or group of files to
describe what data resources should be monitored. The
content of these files will depend on what core system
monitoring is used ((e.g. Nagios or Monasca).
It's desirable to have each recipe describes what
it wants be monitored in generic way such that various system
monitors can understand and convert these into their format.
If a recipe wishes to register itself to system monitor, it
inherits monitor bbclass and use MONITOR_SERVICE_PACKAGES and
MONITOR_SERVICE_<package name> to indicate what processes
should should be monitored. Also MONITOR_CHECKS_<package name>
variale can be used to pass list of scripts which will be run
on target and if any of these scripts fail then will report.
Eventually monitor.bbclass will be expanded to allow recipe
to describe more complicated information passed down to
system monitor (e.g. Nagios or Monasca)
Signed-off-by: Vu Tran <vu.tran@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Although the use of PRINC is deprecated in later versions of Yocto it
may still be used and if you are using this layer with older Yocto it
is recommended for use in bbappends. It is therefore expected to
work. PRINC expects a non-numeric prefix followed by a numeric value,
as can be seen in base.bbclass
pr_prefix = re.search("\D+",pr)
prval = re.search("\d+",pr)
if pr_prefix is None or prval is None:
bb.error("Unable to analyse format of PR variable: %s" % pr)
Failing to stick to this convention yields a parsing error when you
attempt to use PRINC:
ERROR: Unable to analyse format of PR variable
Adding the non-numeric prefix allows PRINC use in bbappends to
function correctly.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
|
|
Ceilometer requires oslo.serialization and kazoo (plus its depdencies), so
we add them here, and ceilometer-api works again.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
keystone: move initscript install to before fixups
There are sed operations being performed on the sysvinit script .. but the
script wasn't being installed until after that block of code. We relocate
the install of the script to above any fixups, and everything works again.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Openstackchef class provides the framework to reconfigure openstack
at run-time. These services are inheriting openstackchef so that
script file(s), specified in the respective recipe file,
using the variables below are restarted by the decentralized
openstackchef class framework when reconfiguring openstack:
INITSCRIPT_PACKAGES: The list of init-scripts to start/stop when
reconfiguring openstack.
INITSCIPT_NAME_x: The name of the init-script mentioned above.
INITSCRIPT_PARAMS_X: This parameter defines the run-level and
priority for the init-script. However, the only parameter in this
variable that is of interest to openstackchef class is the priority of
the init-script.
Changes to none of the above variables is shown by this patch set,
however, it's to point out that openstackchef makes the assumption
that these variables are set in the service's recipe file.
Failure to set these variables, could lead to the service not
working properly after the stack is re-configured.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
Openstackchef enables us to recreate configuration files
for services in an openstack installation. It does this by
creating template file(s) out of openstack services' configuration
file(s) exposed to it.
The following services are inheriting the openstack class
and then exposing a set of configuration files to the class.
The configuration files are assumed to have been installed in the image
in the service's WORKDIR and are exposed to openstackchef by assigning
them to the variable CHEF_SERVICES_CONF_FILES.
For legacy reasons, the string OPENSTACKCHEF_ENABLED is defined in
openstackchef class, but it can be overwritten to an empty string in
a .bb, .class, .bbapend or local.conf file when openstackchef support
is not desired. This enables all of these services to be built without
openstackchef support. In addition, it prevents the recipes for these
sevices from substituting the placeholders in their configuration
files when inheriting openstackchef.
However, since services like python-glance and python-cinder install some
of their configuration files to the image directory during the
substitution, it means that these files at not installed when the
substitutions are not required.
Therefore, we have taken the liberty to install those missing configuration
files before the check for whether or not substitutions should be made,
without having any side effect on when the substitutions are required.
At build-time, openstackchef makes chef-solo templates out of
the registered files. And at run-time, the deploychef package
makes a call to chef-solo, which in-turn use the template files
to recreate the registered configuration files.
In making template files out of configuration files, openstackchef
makes a simple placeholder/value substitution in the configuration files.
However, it provides a mechanism for services inheriting the class
to define a special shell callback function which can do more than
a simple placeholder/value substitution. This special callback
function is exposed to openstackchef by assigning it to the variable
CHEF_SERVICES_SPECIAL_FUNC. And the name of the file passed back to the shell
callback function as an argument is set to the variable
CHEF_SERVICES_FILE_NAME by openstackchef. In this patch set, only
python-neutron and python-glance recipe files makes special
substitutions.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
Openstackchef enables us to recreate configuration files
for services in an openstack installation. It does this by
creating template file(s) out of configuration file(s) exposed
to the class by services.
The following services are inheriting the openstack class
and then exposing a set of configuration files to the class.
These services expose their configuration files to openstackchef
by assigning them to the variable CHEF_SERVICES_CONF_FILES. The files
are assumend to have been installed in the image directory under the
service's WORKDIR.
At build-time, openstackchef makes chef-solo templates out of
the registered files. And at run-time, the deploychef package
makes a call to chef-solo, which in-turn use the template files
to recreate the registered configuration files.
For legacy reasons, the string OPENSTACKCHEF_ENABLED is defined in
openstackchef class, but it can be overwritten in a .bb, .class,
.bbappend or local.conf file to an empty string when openstackchef
support is not desired. This enables all of these services to be built
without openstackchef support. In addition, it prevents the recipes
from substituting the placeholders in their configuration files
when inheriting openstackchef.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
Maintainer's of the upstream git trees for these packages have branched
the repos from which these packages were fetched.
This creates a mismatch between the SRCREV and branch name in the recipe
files.
Specify the branch name to resolve the error or update
the SRCREV to match a commit id found on master.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
This commit changes all required configurations to use keystone running
on apache. The following packages configurations were modified for
keystone running on apache: python-neutron, python-nova, tempest,
python-swift, python-rally, python-heat, python-glance,
python-cinder, python-ceilmoeter, python-horizon.
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
|
|
This patch set configures an apache vhost server on port 8081 which will
serve as the main authentication method and documents the change in
README.keystone.
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
|
|
Update troveclient to newer git commit to support postgresql and split
the package into a meta-package, the python package, bin package, and
test package. Add the meta-package to the compute image & trove RDEPENDS.
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
|
|
Create the OpenStack Database as a service recipe and add it to the
controller image. The recipe includes the init script and initial setup
to use postgres.
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
|
|
Conform as much as possible to the bitbake coding standard. (80 or less
chars/line, 4x space indent).
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Along with this update, we also fix a bug with nova and neutron port types.
this patch will be removed once it is fixed in the upstream project.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Introducing Juno B3 horizon dependencies to the build.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The storage backends have been factored out of the core glance
repository. So we introduce glancestore to meet the backend requirements
of glance.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The horizon recipe had lines running well over 80 characters and
indentation that was not a multiple of 4. This patch fixes those
issues.
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
|
|
The horizon recipe had references to paths defined as variables for
recipe use. This patch converts those paths into the variable version
for easier portability.
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
|
|
Removed duplicate dhcpbridge_flagfile from the nova.conf file.
Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Update the horizon recipe to have all the juno dependencies. We
also introduce the recipes to build those dependencies.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
Li xin
Bruce Ashfield
Vu Tran
Mark Asselstine
Mustapha Lansana
Liam R. Howlett