Wednesday, 2018-08-15

« Tuesday, 2018-08-14 Index Thursday, 2018-08-16 »
openstackgerritchenhb proposed openstack/rally-openstack master: [WIP]Lanuch functional test  https://review.openstack.org/59187300:44
openstackgerritchenhb proposed openstack/rally-openstack master: [WIP]Lanuch functional test  https://review.openstack.org/59187300:49
openstackgerritchenhb proposed openstack/rally master: Launch unittest coverage test  https://review.openstack.org/58842900:54
openstackgerritchenhb proposed openstack/rally master: Launch unittest coverage test  https://review.openstack.org/58842900:56
openstackgerritchenhb proposed openstack/rally master: Launch unittest coverage test  https://review.openstack.org/58842901:12
*** linuxaddicts has quit IRC02:05
*** dave-mccowan has quit IRC02:19
*** openstack has joined #openstack-rally02:34
*** ChanServ sets mode: +o openstack02:34
openstackgerritHomero Pawlowski proposed openstack/rally-openstack master: Fixed README typo  https://review.openstack.org/59189404:58
*** pcaruana has joined #openstack-rally05:12
*** e0ne has joined #openstack-rally06:16
*** alexchadin has joined #openstack-rally06:59
*** noama has joined #openstack-rally07:23
openstackgerritchenhb proposed openstack/rally-openstack master: [WIP]Add api check into health check  https://review.openstack.org/59194507:51
*** alexchadin has quit IRC09:00
*** alexchadin has joined #openstack-rally09:17
*** dave-mccowan has joined #openstack-rally10:12
*** zul has quit IRC10:25
*** devfaz has joined #openstack-rally10:53
devfazHi, im having problems with openstack-tempest-tests since rally_openstack 1.2 - as soon as I update to 1.2 no single test is executed any longer. If I switch back to 1.1. everything is working as expected. Any hints where to look at? I dont get any errors :(10:54
*** alexchadin has quit IRC10:59
*** alexchadin has joined #openstack-rally11:00
*** alexchadin has quit IRC11:00
*** alexchadin has joined #openstack-rally11:01
*** alexchadin has quit IRC11:01
*** alexchadin has joined #openstack-rally11:01
*** alexchadin has quit IRC11:02
*** rh-jelabarre has joined #openstack-rally11:14
*** alexchadin has joined #openstack-rally11:33
devfazFYI: looks like rally-openstack 1.2 requires tempest 18.0+ - 17.2 is not working with rally-openstack 1.211:38
*** alexchadin has quit IRC11:38
*** alexchadin has joined #openstack-rally11:56
*** alexchadin has quit IRC12:23
*** alexchadin has joined #openstack-rally12:30
*** zul has joined #openstack-rally12:43
*** mvkr has quit IRC13:10
*** mvkr has joined #openstack-rally13:40
*** alexchadin has quit IRC14:32
*** zul has quit IRC14:39
*** mvkr has quit IRC15:46
*** itlinux has joined #openstack-rally16:14
*** e0ne has quit IRC16:47
*** noama has quit IRC16:50
*** openstackstatus has joined #openstack-rally16:58
*** ChanServ sets mode: +v openstackstatus16:58
*** rallydev-bot has quit IRC16:58
*** rallydev-bot has joined #openstack-rally16:58
rallydev-bot[From Gitter] andreykurilin : hi @homeski !16:59
rallydev-bot[From Gitter] andreykurilin : In old OpenStack releases, it was possible to boot server without network. The latest releases, doesn't allow this16:59
rallydev-bot[From Gitter] andreykurilin : @homeski https://github.com/openstack/rally-openstack/blob/master/rally_openstack/scenarios/nova/utils.py#L44 doesn't do any magic. It takes the "random" network from "networks" context. If "networks" context was not used for the workload, there is nothing to take17:02
rallydev-bot[From Gitter] andreykurilin : there are 2 options to you.17:06
rallydev-bot[From Gitter] andreykurilin : More complex scenarios, like `NovaServers.boot_server_attach_created_volume_and_resize` accepts additional parameters for  booting VM via `boot_server_kwargs` agument17:06
rallydev-bot[From Gitter] andreykurilin : 2) Another option - use temporary networks, i.e. use "networks" context. see https://github.com/openstack/rally-openstack/blob/master/rally_openstack/scenarios/nova/servers.py#L62 (complex example with a lot of options, but actually, the default configuration of networks context should be enought for you - `networks: {}`)17:08
rallydev-bot[From Gitter] andreykurilin : https://github.com/openstack/rally-openstack/blob/master/samples/tasks/contexts/network.yaml#L1417:08
*** zul has joined #openstack-rally17:09
rallydev-bot[From Gitter] andreykurilin : devfaz: hi! It sounds really strange.17:10
rallydev-bot[From Gitter] andreykurilin : devfaz: there is no change in rally-openstack package related to tempest for the last 4 month . The only thing which can affect: check the version of rally framework in rally_openstack 1.1 installation and rally_openstack 1.2 (by running `rally --version` command)17:12
rallydev-bot[From Gitter] homeski : Thanks Andrey, I'll try these suggestions soon17:15
rallydev-bot[From Gitter] andreykurilin : rh-jelabarre: hi! sorry for the late reply. I suppose it is latest pip (>=10) which is compaining about enum34, it deslikes system-packages17:18
rallydev-bot[From Gitter] andreykurilin : the possible solution for you - installing rally in virtual environemnt or using docker image (https://hub.docker.com/r/xrally/xrally-openstack/)17:19
rallydev-bot[From Gitter] andreykurilin : As for Rally requirements, it doesn't have a lot of dependencies (https://github.com/openstack/rally/blob/master/requirements.txt and https://github.com/openstack/rally-openstack/blob/master/requirements.txt for OpenStack) and we are working on reducing them. Most of packages which is installed are non-direct dependencies of rally - from openstack clients, it is the p17:21
rallydev-botlace which we cannot change17:21
*** e0ne has joined #openstack-rally17:56
*** mvkr has joined #openstack-rally17:56
*** zul has quit IRC18:18
rh-jelabarreandreykurilin: I've gotten the rally/tempest packages included with Queens to work now, so I'm sticking with those.  If I have to start messing with replacing every package, we're no longer testing the product as we're releasing it.18:34
rh-jelabarreI am wondering what it will mean when Rally says "OpenStack plugins moved to the separate package" etc.  Does that mean we won't be abe to run Rally testing against a plain/vanilla Openstack install of a particular release?18:47
rh-jelabarreIt seems, from trying to install Rally with pip, it wants to replace half of the installation18:48
rallydev-bot[From Gitter] andreykurilin : rh-jelabarre: for a long period Rally was a framework for various kind of testing (performance, concurrency, functional, etc) of OpenStack platform. At some point, we realized that limitation of supporting only OpenStack is not the thing which satisfies our consumers, so we started a long process of refactoring. It took more than 2 years. Now Rally become a generic fr18:54
rallydev-botamework which can be used for not only OpenStack. For example, we have some plugins for docker and kubernetes18:54
rallydev-bot[From Gitter] andreykurilin : If someone wants to test other then OpenStack, it doesn't need all these dependencies which are required for openstack clients18:55
rallydev-bot[From Gitter] andreykurilin : And we decided to move in-tree OpenStack plugins from the main repo (github.com/openstack/rally) to the separate one (github.com/openstack/rally-openstack)18:56
rh-jelabarremy main concern is whether newer releases (18.x as opposed to the 8.x in Queens/OSP) will try to install too much, and thereby make the env different than what customers would have18:57
rallydev-bot[From Gitter] andreykurilin : but you need to understand it is not what "rally" or our installation script do, it is the global change of python-community18:58
rallydev-bot[From Gitter] andreykurilin : it is the new behaviour of "pip"18:58
rallydev-bot[From Gitter] andreykurilin : as you can see, we haven't change installation script for more that 7 month https://github.com/openstack/rally/commits/master/install_rally.sh18:59
*** rallydev-bot has quit IRC19:06
*** rallydev-bot has joined #openstack-rally19:06
*** openstackgerrit has quit IRC19:19
*** e0ne has quit IRC20:03
rallydev-bot[From Gitter] homeski : @andreykurilin20:58
rallydev-bot[From Gitter] homeski : When I try to use context in a subtask in task.yaml , I get 'Task config is invalid" errors20:59
rallydev-bot[From Gitter] homeski : what am I doing wrong :D20:59
rallydev-bot[From Gitter] homeski : ```---20:59
*** rallydev-bot has quit IRC20:59
*** rallydev-bot has joined #openstack-rally20:59
rallydev-bot[From Gitter] homeski : ```Task config is invalid: `Task config is invalid:```20:59
rallydev-bot[From Gitter] homeski : ```Failed validating 'oneOf' in schema['properties']['subtasks']['items']:21:00
rallydev-bot[From Gitter] homeski : ```    -21:07
rallydev-bot         -21:07
rallydev-bot[From Gitter] homeski : your suggestion to put the nic into the kwargs *did* work though21:08
rallydev-bot[From Gitter] homeski : my understanding that using context, I can get a dynamically created network that the VM attaches to, instead of statically setting the UUID ?21:08
*** rh-jelabarre has quit IRC21:09
rallydev-bot[From Gitter] andreykurilin : @homeski in task format v2 we renamed context to contexts key21:12
rallydev-bot[From Gitter] andreykurilin : It is the reason why your task is invalid21:12
rallydev-bot[From Gitter] andreykurilin : I'll work in the current release to make error message user-friendly21:12
rallydev-bot[From Gitter] andreykurilin : Sorry21:13
rallydev-bot[From Gitter] homeski : yes, I just discovered that  :) I looked at another sample in the repo21:13
rallydev-bot[From Gitter] homeski : but using, that I get a different error21:13
rallydev-bot[From Gitter] homeski : :D21:14
rallydev-bot[From Gitter] homeski : ```    -21:14
rallydev-bot         -21:14
rallydev-bot[From Gitter] homeski : ```Task config is invalid: `Input task is invalid!21:14
rallydev-botd actions against it.", "scenario": {"NovaServers.boot_and_bounce_server": {"flavor": {"name": "m1.pico"}, "image": {"name": "cirros"}, "availability_zone": "nova", "force_delete": false, "actions": [{"hard_reboot": 1}, {"soft_reboot": 1}, {"stop_start": 1}, {"rescue_unrescue": 1}]}}, "contexts": {"network": {}}, "runner": {"constant": {"times": 1, "concurrency": 1}}, "hooks": [], "sla": {"failure21:14
rallydev-bot_rate": {"max": 0}}}]}21:14
rallydev-bot[From Gitter] andreykurilin : Ok, as far as I understand you are using the permanent user for rally without specifying admin credentials. Right?21:15
rallydev-bot[From Gitter] homeski : I just followed the readme steps21:18
rallydev-bot[From Gitter] homeski : ```21:18
rallydev-bot[From Gitter] homeski : but it is my admin user21:18
rallydev-bot[From Gitter] homeski : should I be using ```        "admin": {21:20
rallydev-bot[From Gitter] homeski : https://github.com/openstack/rally-openstack/blob/master/samples/deployments/existing.json21:21
rallydev-bot[From Gitter] andreykurilin : It depends on your use-case. There are 2 main cases. 1) using admin as admin. In this case rally can create temporary users for the load. 2) using the real users to test the real tenant21:22
rallydev-bot[From Gitter] homeski : ultimately I want to be able to have Rally create resources (networks/flavors/images/vms) inside a designated project21:26
rallydev-bot[From Gitter] homeski : but **not** using the actual admin user21:26
*** rcernin has joined #openstack-rally21:29
*** itlinux has quit IRC22:22
rallydev-bot[From Gitter] homeski : so it looks like defining admin + user does just that23:08
*** rcernin has quit IRC23:18
*** rcernin has joined #openstack-rally23:19
« Tuesday, 2018-08-14 Index Thursday, 2018-08-16 »

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!