summaryrefslogtreecommitdiffstats
path: root/meta-openstack/recipes-devtools/python/python-keystoneclient_git.bb
Commit message (Collapse)AuthorAgeFilesLines
* clients: update to juno release candidate versionsBruce Ashfield2014-10-171-2/+2
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* add generic monitor frameworkVu Tran2014-09-301-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* clients: update clients to juno b3 sync pointBruce Ashfield2014-09-161-2/+2
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* clients: update barbican, ceilo, cinder, glance, heat, keystone and swiftBruce Ashfield2014-07-211-1/+1
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* keystoneclient: update to 0.9.0Bruce Ashfield2014-07-181-2/+2
| | | | | | Updating keystone client to 0.9.0 in preparation for juno compability. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* keystoneclient: fix keystoneclient-test packageKeith Holman2014-06-241-1/+1
| | | | | | | | | | | The keystoneclient-test package (created in the keystoneclient recipe) is currently being generated with no files. This is causing a build error. The path to the files to include in this package specify the "${D}" variable at the beginning of the path, which isn't needed. Removing this variable from the line fixes the problem. Signed-off-by: Keith Holman <Keith.Holman@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* httpretty: create recipe for packageKeith Holman2014-06-231-1/+5
| | | | | | | | | Keystoneclient tests require the package httpretty be available on the system in order to run. This fix includes a recipe file for obtaining and building httpretty. The fix also adds httpretty as a dependency of keystoneclient. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* keystoneclient: add example test certificatesKeith Holman2014-06-231-1/+9
| | | | | | | | | The tests included with keystoneclient require the use of example certificates. This fix copies the example certificates that are found in the source to the target system. It also patches the test files to find the certificates in the correct location. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* clients: update to the latest client codeBruce Ashfield2014-04-031-1/+1
| | | | | | Updating to the latest clients as of April 3, 2014. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* clients: add bash-completion supportBruce Ashfield2014-04-031-0/+11
| | | | | | | Package and enable the bash completion suppor that comes with the various client packages. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Memory leak from timingsAmy Fong2014-03-311-1/+4
| | | | | | | | | | | | | | | | | Memory leak happens when the dynamic list times grows without anything to reset it. In ceilometer and cinder configuration files, the new option is created: [nova_client] max_timing_buffer=<value> In all clients found that uses extends the HTTPClient and uses the times list, we limit the size of the list by popping off the oldest item in the list to maintain a maximum size. A default size of 200 is chosen, configurable by the above configuration option. Signed-off-by: Amy Fong <amy.fong@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-*: prevent setuptools from fetching required eggsMark Asselstine2014-03-171-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* *client: updating the openstack client packages to their latest versionsBruce Ashfield2014-03-031-2/+2
| | | | | | Tested with a controller boot, compute boot and guest launch. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-*client: update PV to include client versionBruce Ashfield2013-12-091-1/+1
| | | | | | | | Rather than only using the git has for the client apis, we'll also use the latest tagged version. This makes the mapping to pypi and capabilities much simpler. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* keystone: update to havana versionBruce Ashfield2013-11-251-0/+24
Updating the keystone OpenStack component to the havana release version. As part of this switch, we also start building out of git versus the release tarballs. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>