| Age | Commit message (Collapse) | Author |
|---|
|
Follow Debian dependencies from official salt repo at repo.saltstack.com
Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Nam Ninh <nam.ninh@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fix wrong hard-coded OPENLDAP_LIBEXECDIR that causes the following
build failure:
mv: cannot stat `<build_dir>/bitbake_build/tmp/work/core2-64-wrs-linux/openldap/2.4.39-r0/image/usr/lib64/openldap/slapd': No such file or directory
The base openldat bb installs slapd under ${sbindir}, so LIBEXEC should be
replaced with sbindir instead of OPENLDAP_LIBEXECDIR. The "run" directory
is already removed in the base bb, so removing the second time causes this
build failure:
rmdir: failed to remove `<build_dir>/bitbake_build/tmp/work/core2-64-wrs-linux/openldap/2.4.39-r0/image/var/run': No such file or directory
Finally, ops-base.ldif is needed in the initscript, so we also include it
in the package.
Signed-off-by: Nam Ninh <nam.ninh@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In order to avoid future danglers move more bbappends to use
wildcards. This also helps when folks are using meta-cloud-services
with other branches then master. These are trivial in that they are
not being modified and have been audited and shown to be still
applicable.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To facilitate future support and to simplify using meta-cloud-services
with other branches we prefer to use a wildcard. In making this move
the content of the bbappend has been audited and most of the content
is now no longer needed (it is found in dnsmasq.inc for some time now)
and so we are removing these parts.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Puppet can be used by many 'cloud services', it is not openstack
specific, so moving puppet and puppet related recipes to the
meta-cloud-services base layer. This allows either internal sub-layers
found in meta-cloud-services or external layers to include
meta-cloud-services without being burdened by bbappends and configs
found in meta-openstack.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The puppet could not add or change the user's password automatically,
because the puppet tool requires the "libshadow" to implement this feature.
Failure information without the "libshadow" feature:
==================================================================
Debug: /User[username]: Provider useradd does not support features
manages_passwords; not managing attribute password
Signed-off-by: Guojian Zhou <guojian.zhou@windriver.com>
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The puppet agent requires the /etc/puppet/puppet.conf.
Signed-off-by: Guojian Zhou <guojian.zhou@windriver.com>
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The puppet's execution depends on the facter, so add the required
RDEPENDS in the bb file.
The puppet tool run failure information:
==============================================
root@# puppet help
/usr/lib64/ruby/rubygems/custom_require.rb:36:in `require': cannot load such file -- facter (LoadError)
from /usr/lib64/ruby/rubygems/custom_require.rb:36:in `require'
from /usr/lib64/ruby/gems/1.9.1/gems/puppet-3.7.3/lib/puppet.rb:6:in `<top (required)>'
from /usr/lib64/ruby/rubygems/custom_require.rb:36:in `require'
from /usr/lib64/ruby/rubygems/custom_require.rb:36:in `require'
from /usr/lib64/ruby/gems/1.9.1/gems/puppet-3.7.3/lib/puppet/util/command_line.rb:12:in `<top (required)>'
from /usr/lib64/ruby/rubygems/custom_require.rb:36:in `require'
from /usr/lib64/ruby/rubygems/custom_require.rb:36:in `require'
from /usr/lib64/ruby/gems/1.9.1/gems/puppet-3.7.3/bin/puppet:7:in `<top (required)>'
from /usr/bin/puppet:23:in `load'
from /usr/bin/puppet:23:in `<main>'
Signed-off-by: Guojian Zhou <guojian.zhou@windriver.com>
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Lei Maohui <leimaohui@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Several bbappends were raising 'dangling' warnings since the base
recipe version has changed without a similar change being made in this
repo. The following are renames that include a wildcard to broaden the
versions to which these bbappends will be applied to. This will
address the 'dangling' warnings while ensuring the changes made in
this repo are properly applied to the associated recipes.
For the most part the files remain unchanged, in the case of
postgresql the 'brokensep' has been removed as there exists no more S
!= B issues in the base recipe.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Several bbappends are now dangling as the base recipes have moved to
different versions. These specific danglers have been reviewed and
don't have any demonstrable purpose any longer and can therefor be
removed.
For example the busybox default config now enables CONFIG_WHICH so
there is no reason to continue to 'patch' this config setting.
For recipes which used brokensep in order to work around S != B build
issues the fact that the bbappend was dangling and the recipe was
building successfully is enough to demonstrate that the bbappend was
no longer needed.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.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>
|
|
Add 0001-usr-Makefile-WARNING-fix.patch to avoid build WARNING.
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
|
|
Signed-off-by: Daniel Badea <daniel.badea@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
python-request is now only a dependency of salt-cloud.
Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Some package formats explicitly track which files are configuration files
so that they are not overwritten on updates. Explicitly list the
configuration file.
Signed-off by: Rob Woolley <rob.woolley@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Some package formats explicitly track which files are configuration files
so that they are not overwritten on updates. Explicitly list the
configuration file.
Signed-off by: Rob Woolley <rob.woolley@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Refreshing the support libraries to prepare for kilo uprevs
of the core components.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
oe-core now warns on detected missing runtime and build time warnings.
So we update our recipes to have these missingn deps (largely bash).
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Remove the patch 0003-Don-t-enforce-that-dev-already-exists.patch
as the similar patch exist in poky git repo added by
commit 673bb3cffc1fdedb7c25178233c8699650194545
Author: Roy.Li <rongqing.li@windriver.com>
Date: Wed Oct 29 14:01:07 2014 +0800
Signed-off-by: Tudor Florea <tudor.florea@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Updating the bbappends to match the oe-core versions ~commit 530565c6cb77319f4cc49edeea6fec6be997415d
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>
|
|
A simple demo is added
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
With changes made to the identity class, the postinstall
scripts no longer register users and services with keystone.
Instead, the registration is put inside the file
/etc/keystone/service-user-setup by the postinstall scripts.
Executing /etc/keystone/service-user-setup then registers
the users and services with keystone through /etc/keystone/identity.sh.
Therefore, executing just the postinstall scripts is not enough
enough to properly bring up the stack. However, executing
/etc/init.d/run-postinsts does both.
In addition, we are executing scripts within run-deploy in the
current shell environment so that the user can see all the updates
to the databases on the terminal.
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>
|
|
The functionality the following files provide are now implemented in
openstackchef class, they are no longer needed in the deploychef package.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
Spelling mistake correction and sentence restructuring to the
header section in recipe file.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
The deploychef package has been adapted to implement the
run-time functionality required by decentralized openstackchef
class.
It does this by executing a script (deploychef) which instruct chef-solo
to recreate configuration files from all template files placed
at
/opt/deploychef/cookbooks/openstack/templates/default
by openstackchef class at build-time.
The deploychef init script run-level is lower than run-postinsts
script, which runs all openstack post-install scripts at first boot.
The deploychef script makes a call to run-chefsolo script,
which then creates openstack configuration files from all template
files mentioned above as directed by a recipe file.
This enables us to reconfigure an openstack image on first-boot,
thereby, updating the image with environment variables like IP address.
Like the template files above, there is a list of all default
variables used by the services in an openstack installation.
These variables, like the templates files above are created by
the openstackchef class and saved to a file under deploychef
directory at:
/opt/deploychef/cookbooks/openstack/attributes/default.rb
Whenever it's desired to reconfigure an openstack deployment
with an updated value of any of the variables in the attributes file
above, the script file run-deploychef should be executed to
reconfigure the stack as shown below.
cd /opt/deploychef
./run-deploychef
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
The deploychef package enables us to reconfigure an openstack
installation at run-time. It does this with the help of chef-solo,
by first creating a set of template files from openstack services'
configuration files. The template files are then passed on to chef-solo
at run-time. Finally, chef-solo recreates the services' configuration
files from the template files at run-time; this enables us to reconfigure
openstack services with dynamic run-time environment variables.
This patch set consist of files with helper functions which enables
deploychef to recreate the template files for the respective openstack
services.
Later on in this commit series, the files in this patch set
will be deleted, because the functionality they provide will be
provided by openstackchef class.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
Deploychef package reconfigures an openstack installation.
These are helper files used by the deploychef package to bring the
system down and back up again before, and after chef-solo has generated
our desired configuration files from template files.
Later on in this commit series, the *-list files will be replaced with
dynamically generated *-list files by openstackchef. In addition,
the script files will be adapted to support openstackchef.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
The deploychef package uses chef-solo to reconfigure an openstack
installation by converting services' configuration files to template
files. The attributes file defines the constants chef-solo uses to generate
configuration files/scripts. The recipe file describes how those
files/scripts should be created. The config and .json files
are input to chef-solo and describe location of files.
Later in this series, the attributes file will be replaced by a
dynamically generated attributes file. In addition, the recipe file
will change to accommodate changes to deploychef in order to support
openstackchef.
Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
|
|
The current openstack build bakes a number of variables into openstack
services' configuration files at build-time. This makes it impossible
to deploy an openstack image built for one run-time environment into a
different run-time environment.
The deploychef package uses chef-solo to enable the re-use of an
openstack image in different run-time environments.
The attached patch set is deploychef package recipe and init script
files. The script deploychef.init gives us the ability to make a copy of
the postinstall script before they are tainted. This enables us to create
chef-solo templates out of the untainted postinstall scripts.
The template files are then used to recreate the postinstall script
whenever the stack needs to be reconfigured at run-time.
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>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Not only do we update to meta-oe latest, we inherit the following issue
that prevents instance creation:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1364828
To fix the issue, we import 0003-Don-t-enforce-that-dev-already-exists.patch,
until it is integrated into the upstream package.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Removing PRINC from recipes to silence the bitbake warning about
it being a depreciated variable.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To avoid configuration errors, we need to get the latest meta-networking
changes.
This recipe will be dropped eventually, but will stay a bit longer for
migration purposes.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Explicitly set the libexec dir to /usr/libexec for openstack
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Package nss-pam-ldapd, this is a daemon enabling pam/ldap
authentication.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Add openstack specific parts of openldap.
openldap's init script initializes the data with the basic tree structures
needed for keystone - the Group, User and Role tree.
Additionally, we add two variables which can be set in local.conf,
LDAP_DN - default DN for ldap
default: "dc=my-domain,dc=com"
LDAP_DATADIR - default directory for ldap's data directory
default: "/etc/openldap-data/"
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Not only must postgres depend on libxml for xml support, we need to
point at the sysroot/staging area for the header files to be found.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Using the /etc/init.d/tgtd script, allows the service be started
multiple times, but only the last instance can be stopped using
the script. This fix ensures that the service isn't running
before attempting to start the service multiple times.
Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Make ruby binaries more accessible by creating symlinks from
${libdir}/ruby/gems/${ruby version}/bin/ to /usr/bin
RDEPENDS needs to be package specific
coderay needs to depends on yard
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Use chef-solo to help reconfigure and deployment of controller
and compute nodes. Install script downloaded from this link
(https://www.opscode.com/chef/install.sh) and the attached archives created from it.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Since oe-core introduced the autotools separated build and source
directory changes, some package builds broke.
With this change, we can build against the latest oe-core master.
It should be noted that this masks the build issues, and the bbappends
should be removed as dependency layers update or "real" fixes are
generated.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
Alejandro del Castillo
Nam Ninh
Mark Asselstine
Guojian Zhou
Lei Maohui
Li xin
Bruce Ashfield
Rob Woolley
Tudor Florea
YangHaibo
Mustapha Lansana
Amy Fong
Keith Holman