summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* hashie: upgrade 2.1.1 -> 3.4.2Li xin2015-07-271-2/+2
| | | | | Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* chef-zero: upgrade 2.0.2 -> 4.2.3Li xin2015-07-271-4/+2
| | | | | Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* libconfig-general-perl: upgrade 2.51 -> 2.58Li xin2015-07-221-3/+2
| | | | | Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* meta-openstack: gptfdisk: Remove recipeIoan-Adrian Ratiu2015-07-222-49/+0
| | | | | | | | A gptfdisk recipe has been added to openembedded-core by commit 8c219e making this one unecessary. Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* tgt: update to v1.0.37Bruce Ashfield2015-07-141-2/+2
| | | | | Signed-off-by: Daniel Badea <daniel.badea@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* salt: upgrade to 2015.5Alejandro del Castillo2015-06-011-5/+4
| | | | | | | 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>
* salt: add recipe for saltAlejandro del Castillo2015-06-0112-0/+2158
| | | | | Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* openldap: drop bbappendBruce Ashfield2015-05-211-72/+0
| | | | | | | | The bbappend in meta-openstack breaks the meta-oe recipe's do_install_append, so we drop it for now. This assumes that the default recipe and install is sufficient for users. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* qemu: add (and enable) spice in qemuBruce Ashfield2015-05-211-0/+3
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* qemu: drop spice from default packageconfigBruce Ashfield2015-05-211-3/+1
| | | | | | | Spice is in meta-cloud-services, so we'll move that package config item there. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* iproute2: remove patch already appliedTudor Florea2015-05-212-29/+0
| | | | | | | | | | | 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>
* chef: make deploychef dependencies a distro featureBruce Ashfield2015-05-211-2/+2
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* hiera: add recipe for hiera 1.3.4YangHaibo2014-12-182-0/+43
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* facter: add recipe for facter 2.3.0YangHaibo2014-12-182-0/+42
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* puppet: add recipe for puppet 3.7.3YangHaibo2014-12-183-0/+129
| | | | | | A simple demo is added Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* trove: switch to basename <file> <suffix>Bruce Ashfield2014-12-031-1/+1
| | | | | | | basename -s is not unviversally supported, so we switch to something more standard. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* core: update to stable/juno release branchesBruce Ashfield2014-11-2510-27/+28
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* meta-openstack: prefer pexpect 3.3Bruce Ashfield2014-11-181-0/+1
| | | | | | | The meta-python version is taking precedence, so we pin the version to the one in meta-openstack. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-pexpect: fix download locationBruce Ashfield2014-11-181-5/+4
| | | | | | | | 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>
* core: update to juno 2014.2 + dependenciesBruce Ashfield2014-11-1718-32/+34
| | | | | | | 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>
* nova: update configuration settingsBruce Ashfield2014-11-171-10/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* core: add juno (2014.2) dependenciesBruce Ashfield2014-11-117-0/+54
| | | | | | Updating components and support utilities for the juno 2014.2 update. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* trove: update core package and dependencies to juno -rc2Bruce Ashfield2014-11-104-11/+28
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* nova: allow empty schemes at python 2.7.3Bruce Ashfield2014-11-052-0/+35
| | | | | | | | | | | | 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>
* websockify: update to 0.6.0Bruce Ashfield2014-11-051-2/+2
| | | | | | Juno nova requires 0.6.x for websockify, so we do the update. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* neutron: move from OVS unified to OVS ml2 pluginBruce Ashfield2014-10-272-48/+42
| | | | | | | | | 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>
* keystone: update for Juno rc1Bruce Ashfield2014-10-212-9/+43
| | | | | | | | | | | | | | | | | | 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>
* horizon/libs: introduce jquery-ui for juno requirementsBruce Ashfield2014-10-211-0/+27
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* cinder/libs: add rtslib-fbBruce Ashfield2014-10-211-0/+27
| | | | | | To support iscsi backends, cinder uses rtslib-fb. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* keystone/libs: introduce oauthlibBruce Ashfield2014-10-211-0/+35
| | | | | | | In the juno release, keystone depends on oauthlib, so we introduce the recipe. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* oslo: add rootwrapBruce Ashfield2014-10-211-0/+27
| | | | | | Integrate oslo.rootwrap to meet juno dependencies for core projects Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* nova/cinder/ceilometer: adding missing oslo dependenciesBruce Ashfield2014-10-213-0/+4
| | | | | | oslo rootwrap was missing from the DEPENDS of these core projects. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: reorder and update dependenciesBruce Ashfield2014-10-211-33/+17
| | | | | | | | | | | 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>
* horizon: update dependencies for juno rc2Bruce Ashfield2014-10-217-15/+15
| | | | | | Updating the horizon dependent packages to the juno-rc2 required versions Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* clients: update to juno release candidate versionsBruce Ashfield2014-10-1710-22/+22
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: update to juno -rc1 candidateBruce Ashfield2014-10-171-2/+3
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* bootstrap-scss: introduce to meet horizon juno dependenciesBruce Ashfield2014-10-171-0/+27
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* core: update to juno-rc1 candidate releaseBruce Ashfield2014-10-1710-21/+24
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* lxc: update bbappend to match meta-virtualization package versionBruce Ashfield2014-10-141-0/+0
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* libvirt: update bbappend to meta-virtualization latestBruce Ashfield2014-10-141-0/+0
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* add monitoring packagegroup into openstack buildVu Tran2014-09-303-1/+23
| | | | | | | | | | | | | | | | | | | Include monitoring packagegroups into various openstack packagegroups. Monitoring feature can be turned on by including the following in local.conf OPENSTACK_EXTRA_FEATURES += "monitoring" There are various different system monitoring recipes (e.g. Nagios or Monasca) provide packagegroup-monitoring-xxxxx. To choose what system monitoring to use set the following in local.conf PREFERRED_PROVIDER_virtual/monitoring = "packagegroup-nagios-monitoring" Signed-off-by: Vu Tran <vu.tran@windriver.com>
* add generic monitor frameworkVu Tran2014-09-3023-14/+243
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* housekeeping: Add a non-numeric PR prefix to allow PRINC in bbappendsMark Asselstine2014-09-297-7/+7
| | | | | | | | | | | | | | | | | | | | | | 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: update to juno dependenciesBruce Ashfield2014-09-297-0/+168
| | | | | | | 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:Bruce Ashfield2014-09-291-6/+6
| | | | | | | | | | 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>
* deploychef: use /etc/init.d/run-postinsts to execute scriptsMustapha Lansana2014-09-262-4/+18
| | | | | | | | | | | | | | | | | | 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>
* openstack: restart daemons exposed by the following services in openstackMustapha Lansana2014-09-263-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | 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>
* cinder/glance/neutron: support for openstackchef classMustapha Lansana2014-09-263-51/+96
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* openstack: add support for openstackchef class to servicesMustapha Lansana2014-09-268-117/+162
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* openstack-base: support for openstackchef to hook into rootfs creationMustapha Lansana2014-09-261-3/+3
| | | | | | | | | | | | | Openstack-base class is inheriting openstackchef class Since we want openstackchef post-rootfs function to be called after rootfs creation for all openstack images, openstack-base class need to inherit openstackchef class. In addition, we want the node names; compute/controller to be reconfigurable to other variables beside compute/controller in /etc/hosts file at run-time, and be consistent with node names used for compute/controller in all openstack installation. Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-05 17:36:14 +0000