summaryrefslogtreecommitdiffstats
path: root/meta-openstack/recipes-devtools/python/python-horizon_git.bb
Commit message (Collapse)AuthorAgeFilesLines
* chef: remove the use of chefMark Asselstine2017-01-091-1/+1
| | | | | | | | | | | 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>
* python-horizon: cleanup QA warningsMark Asselstine2017-01-091-1/+1
| | | | | | | | | | | | | Currently we are seeing warnings like: .../horizon.scss is owned by gid 1001, which is the same as the user running bitbake. These are caused by using 'cp -a' in this case, by excluding the 'ownership' part of -a we can avoid these QA issues. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* housekeeping: replace deprecated base_containsMark Asselstine2016-12-211-1/+1
| | | | | | | | Fixes: base_contains is deprecated, please use bb.utils.contains instead. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: uprev to LibertyMark Asselstine2016-02-051-56/+63
| | | | | Signed-off-by: Mark Asselstine <asselsm@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: add an upstream patch needed for pyscss 1.3.4Mark Asselstine2015-10-301-0/+1
| | | | | | | | | | Without this patch we will get an error: Don't know how to merge conflicting combinators: <SimpleSelector: u'+ .btn:not(:first-child)'> and <SimpleSelector: u'> .btn'> when attempting to connect to the horizon dashboard. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: add missing dependencies to address startup errorsMark Asselstine2015-08-061-1/+3
| | | | | | | | | | | | | | | | | | Horizon requires python-xstatic-angular-lrdragndrop and xstatic-magic-search otherwise errors will prevent the dashboard from being accessed. The depencies are spelled out clearly in the openstack-dashboard-error.log, as per the following error: ImportError: Could not import settings 'openstack_dashboard.settings' (Is it on sys.path? Is there an import error in the settings file?): No module named angular_lrdragndrop Even with these added dependencies there are other issues that prevent the dashboard from being accessed but at least with these dependencies satisfied we can move on to fixing the remaining runtime issues. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-horizon: add rdepends on python-xstatic-angular-irdragndropJackie Huang2015-05-131-0/+1
| | | | | Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-horizon: upgrade to 2015.1.0Jackie Huang2015-05-071-4/+3
| | | | Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
* python-horizon: upgrade to 2015.1.0b3Jackie Huang2015-04-211-2/+2
| | | | | Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: fix kilo login / page renderingBruce Ashfield2015-03-131-0/+1
| | | | | | | | | With this commit, we add a missing dependency (pint) and update the angular support libary to the proper version for kilo support. We can now render and log into the dashboard. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* core: BROKEN: Initial update to kilo branches and REVsBruce Ashfield2015-03-101-3/+6
| | | | | | | | | | | | | This is the initial update to the kilo branches and SRCREVs for some of the core projects. These are known to NOT work, due to SSLv3 issues with oe-core, and missing config/dependencies. Incremental updates will fix issues with the components, but they are best done in-tree, rather than sitting on a huge pile of changes. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* support-libs: fix clean issuesBruce Ashfield2015-02-241-0/+3
| | | | | | | | | | | | | With recent changes to oe-core make clean is run during the configuration phase of python packages. For some packages, this causes breakage as 'make clean' is not supported. To keep the build going, we mark them as brokenclean to avoid the issue. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* QA: fix build and runtime warningsBruce Ashfield2015-02-211-0/+2
| | | | | | | 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>
* core: update to stable/juno release branchesBruce Ashfield2014-11-251-3/+3
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* core: update to juno 2014.2 + dependenciesBruce Ashfield2014-11-171-1/+1
| | | | | | | 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>
* 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 to juno -rc1 candidateBruce Ashfield2014-10-171-2/+3
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* add generic monitor frameworkVu Tran2014-09-301-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* openstack: restart daemons exposed by the following services in openstackMustapha Lansana2014-09-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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>
* core: update core projects to juno b3 releaseBruce Ashfield2014-09-161-2/+4
| | | | | | | 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>
* python-horizon: Fix whitespace in recipe.Liam R. Howlett2014-09-041-8/+14
| | | | | | | | 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>
* python-horizon: Fix path usage to bitbake defined paths.Liam R. Howlett2014-09-041-14/+18
| | | | | | | | 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>
* horizon: add juno dependenciesBruce Ashfield2014-09-041-0/+13
| | | | | | | 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>
* core: update core projects to juno 2014.2-b2 versionsBruce Ashfield2014-08-291-2/+2
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: update to juno releaseBruce Ashfield2014-07-211-3/+9
| | | | | | | Updating horizon to the juno release branch. New required packages have been added to support this integration. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: add full path to test directoriesKeith Holman2014-06-041-1/+2
| | | | | | | | | | | | | | The tests included Horizon expect all files to be in a single location in order to be run directly from the source tree. The recipe for installing Horizon on the system installs Horizon as a python site-package and puts files in different locations depending on the file type. In order to have the tests support this type of install we need to explicitly indicate the full path of the test files to exclude in order to have the tests run successfully. This fix adds the absolute path to the test locations allows the Horizon tests to pass as expected. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* nose-exclude: add plugin for nose to exclude directoriesKeith Holman2014-06-041-0/+2
| | | | | | | | | | | Nose is a package to support unit testing of python source code. Node-exclude is a plugin extending Nose to specify directories to exclude from testing via the command line. Some packages require this plugin to be installed in order to run all the tests successfully. This fix creates recipe to install the node-exclude plugin on the target system. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* django-nose: add recipe and dependencies for testingKeith Holman2014-06-041-0/+2
| | | | | | | | | | Horizon provides unit tests for testing its deployment in target environment. These tests make use of django-nose testing framework. This provides a recipe for building django-nose and adds a dependency from Horizon on this recipe. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* horizon: patch test script to run without coverageKeith Holman2014-06-041-0/+1
| | | | | | | | | | | Currently, the run_tests.sh script provided by the horizon package requires the command "coverage" to be available even if the "-c" option (test with code coverage) is not specified on the command line. This fix patches the test script to remove the calls to the "coverage" tool and calls the test script directly if the "-c" option is not provided. Signed-off-by: Keith Holman <Keith.Holman@windriver.com>
* horizon: update to icehouse releaseBruce Ashfield2014-04-301-4/+5
| | | | | | | | Updating horizon to the icehouse release. Adding troveclient to the rdepends is the biggest recipe level change .. and even that isn't very big. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-horizon: apache mod_wsgi path errorAmy Fong2014-04-111-0/+1
| | | | | | | openstack-dashboard-apache hardcoded libdir, modify this to %LIBDIR% and substitude in the install phase... Signed-off-by: Amy Fong <amy.fong@windriver.com>
* python-horizon init scriptsAmy Fong2014-04-101-3/+6
| | | | | | | Split out a new package horizon-standalone that just contains the init script for the built in webserver. Signed-off-by: Amy Fong <amy.fong@windriver.com>
* Enable python-horizon to run from apache.Amy Fong2014-04-101-2/+34
| | | | | | | | | | | | | | | - modify python-horizon to install files needed for horizon/apache - add apache configuration file (openstack-dashboard-apache.conf) to setup a virtual host running from port 80 to run the mod_wsgi/openstack-dashboard app - add horizon-apache and apache2 to controller task list - Note: local_settings.py differs from the one in examples in two ways: 1. LOCAL_PATH = "/usr/share/openstack-dashboard/openstack_dashboard/static" since the apache app runs as daemon, we neeed to specify a path where daemon has write permissions 2. configure python-horizon/apache to use memcached. (see CACHES) Signed-off-by: Amy Fong <amy.fong@windriver.com>
* horizon: refresh to the latest havana/stable contentBruce Ashfield2014-04-071-1/+1
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Readjust the start level of openstack componentsVu Tran2014-03-171-1/+2
| | | | | | | | | | | | | | Currently all the openstack components have default start level of 20. There are other services such as glusterfs, rabbbitmq, database... are also starting at the same start level. On some platform, this can cause racing condition between services which in turn causes some of openstack components not started. By adjusting the openstack components start level to higher will ensure that system services start in the determistic way. Signed-off-by: Vu Tran <vu.tran@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>
* horizon: update to stable/havana latestBruce Ashfield2014-01-191-1/+1
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Revert "horizon: update to 2013.2.2"Bruce Ashfield2013-12-201-2/+2
| | | | | | | This update breaks the login to metering (ceilometer), so temporarily reverting the update. This reverts commit 3299b0d1375a1a9b0458c43de7b6e3bee2544c9f.
* horizon: update to 2013.2.2Bruce Ashfield2013-12-191-2/+2
| | | | Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: move arch specific RDEPENDS to variablesBruce Ashfield2013-12-171-5/+7
| | | | | | | | | | | Assigning to the python-horizon REDENDS in arch specific variables AFTER the main RDEPENDS exposes and issue with bitbake parsing, and we end up with a singular RDEPEND of "nodejs". Assigning to a variable, and using that variable in the main RDEPENDS, fixes the issue. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* tempest: create per-component test packages and flakes8Bruce Ashfield2013-12-111-1/+9
| | | | | | | | | | | | To add more complete tempest support, we require flakes8, so it is added to the dependency list. To get the individual component test scripts onto the target, create a $PACKAGE-tests package and add the script. When the tests are required on target, these packages should be added to the install list. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-horizon: remove nodejs from RDEPENDS of powerpc archZhenhua Luo2013-11-261-2/+6
| | | | | | | Nodejs only supports arm, x86 and ia32 archs, it doesn't support powerpc. Signed-off-by: Zhenhua Luo <zhenhua.luo@freescale.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* horizon: update to the havana versionBruce Ashfield2013-11-251-0/+94
While updating to the havana release version, we also switch to git based builds. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 23:08:26 +0000