aboutsummaryrefslogtreecommitdiffstats
path: root/meta-openstack/recipes-devtools/python/python-swift_git.bb
AgeCommit message (Collapse)Author
2020-06-05python-swift: satisfy setup.py setup_requiresBabak Sarashki
Commit 8fdbb0381d disallows fetch of code during do_compile task. This commits extends DEPENDS to python-pbr-native. Signed-off-by: Babak Sarashki <Babak.SarAshki@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2020-01-22python: prepare for python3 only configurationBruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2017-11-15python-*: fixup postinst scriptsMark Asselstine
Checking for "$D" and doing an "exit 1" now results in errors such as: [log_check] warning: %post(keystone-cronjobs-...) scriptlet failed, exit status 2 during image creation. Instead of escaping the script for "level-1" (image creation postinst) we wrap the "level-2" (first boot) postinst in an if statement. This also ensure the scriptlet in indentity.bbclass is less prone to behaving differently based on the postinsts defined in the classes which inherit 'identity'. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2017-01-09chef: remove the use of chefMark Asselstine
The use of chef was never complete, had isses with updating binary database files and had a cumbersome implementation. Since we are using Ansible in meta-overc we are dropping the use of chef here and will look to being at par with meta-overc by using Ansible if/when we get time to look at runtime configuration in meta-cloud-services. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2015-03-03support-libs: refresh round1Bruce Ashfield
Refreshing the support libraries to prepare for kilo uprevs of the core components. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2015-02-21QA: fix build and runtime warningsBruce Ashfield
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>
2014-11-25core: update to stable/juno release branchesBruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-11-17core: update to juno 2014.2 + dependenciesBruce Ashfield
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>
2014-10-17core: update to juno-rc1 candidate releaseBruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-09-26openstack: add support for openstackchef class to servicesMustapha Lansana
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>
2014-09-16core: update core projects to juno b3 releaseBruce Ashfield
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>
2014-08-29core: update core projects to juno 2014.2-b2 versionsBruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-07-30Keystone: package service/user additionsAndy Ning
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>
2014-07-25openstack initscript: add resetAmy Fong
Some of the openstack data is associated with external resources (ie glance may have external files), we explicitly invoke the delete commands on those in additional to dropping and recreating the databases. Signed-off-by: Amy Fong <amy.fong@windriver.com>
2014-07-21swift: update to juno release candidateBruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-05-07swift: update to icehouse releaseBruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-04-11swift: add setup packageVu Tran
Introduce swift setup package. At boot time, this package setups a simple swift cluster including: * 3 zones * each zone has 1 storage device which are based on loopback devices which the backing files size is controlled by variable SWIFT_BACKING_FILE_SIZE The script /etc/swift/swift_setup.sh is also provided to ease the task of setting up a complicated Swift cluster. It reads a cluster config file, which describes what storage devices are included in what rings, and constructs the cluster. For details of how to use swift_setup.sh and the format of Swift cluster config file please refer to the script's help: $ swift_setup.sh Signed-off-by: Vu Tran <vu.tran@windriver.com>
2014-04-11swift: add testsVu Tran
Introduce swift test package which contains all Swift unit tests. Swift unit tests can be run as: $ cd /usr/lib64/python2.7/site-packages/swift $ nosetests -v test Signed-off-by: Vu Tran <vu.tran@windriver.com>
2014-04-11swift: separate dispersion configVu Tran
There are many changes required for proxy-dispersion config file. So instead of having sed to replace all little details, it's cleaner to add new config file that contains the changes Signed-off-by: Vu Tran <vu.tran@windriver.com>
2014-04-11swift: separate proxy server configVu Tran
There are many changes required for proxy-server config file. So instead of having sed to replace all little details, it's cleaner to add new config file that contains the changes Signed-off-by: Vu Tran <vu.tran@windriver.com>
2014-04-11swift: change services config filesVu Tran
Modify config files of the following Swift services: contains-server, account-server, and object-server in order for these services are able to start correctly. Signed-off-by: Vu Tran <vu.tran@windriver.com>
2014-04-11swift: include dnspythonVu Tran
Swift depends on dnspython Signed-off-by: Vu Tran <vu.tran@windriver.com>
2014-03-17python-*: prevent setuptools from fetching required eggsMark Asselstine
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>
2013-12-19swift: update to 2013.2.2Bruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2013-11-25swift: uprev to havana releaseBruce Ashfield
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>