*** mwarad has joined #openstack-outreachy | 04:04 | |
*** mwarad has quit IRC | 04:26 | |
*** katyafervent_awa has quit IRC | 05:44 | |
*** katyafervent_awa has joined #openstack-outreachy | 05:44 | |
*** mwarad has joined #openstack-outreachy | 07:37 | |
*** jpich has joined #openstack-outreachy | 07:47 | |
*** rossella_s has joined #openstack-outreachy | 08:01 | |
*** rossella_s has quit IRC | 08:18 | |
*** rossella_s has joined #openstack-outreachy | 08:19 | |
*** mwarad has quit IRC | 09:09 | |
*** neiljerram has joined #openstack-outreachy | 09:20 | |
*** neiljerram has quit IRC | 09:29 | |
*** mwarad has joined #openstack-outreachy | 12:14 | |
*** raildo has joined #openstack-outreachy | 12:16 | |
*** rossella_s has quit IRC | 12:46 | |
*** rossella_s has joined #openstack-outreachy | 13:02 | |
*** rossella_s has quit IRC | 13:11 | |
*** rossella_s has joined #openstack-outreachy | 13:23 | |
*** rossella_s has quit IRC | 13:46 | |
*** rossella_s has joined #openstack-outreachy | 14:01 | |
*** lwanderley has joined #openstack-outreachy | 14:12 | |
*** lwanderley has quit IRC | 14:27 | |
*** lwanderley has joined #openstack-outreachy | 16:20 | |
*** jpich has quit IRC | 16:25 | |
*** lwanderley has quit IRC | 17:07 | |
*** lwanderley has joined #openstack-outreachy | 17:07 | |
*** lwanderley has quit IRC | 17:14 | |
*** lwanderley has joined #openstack-outreachy | 17:22 | |
rodrigods | hello | 17:31 |
---|---|---|
rodrigods | who is already here? ping lwanderley raildo | 17:31 |
lwanderley | I am | 17:31 |
rodrigods | o/ | 17:31 |
rodrigods | raildo said that he could arrive a couple of minutes late, so let's get started | 17:31 |
lwanderley | hi :) | 17:31 |
lwanderley | ok, cool | 17:31 |
rodrigods | from the last meeting, i remember that you were almost finishing the devstack plugin | 17:32 |
lwanderley | i have a couple of questions about the next task | 17:32 |
rodrigods | and was going to submit a patch that is "review ready" | 17:32 |
rodrigods | this is done, right? | 17:32 |
lwanderley | yes, it is | 17:32 |
rodrigods | cool, did you ask around for reviews? | 17:33 |
lwanderley | i didn't, but raildo did | 17:34 |
lwanderley | we got some new comments there, about improving the commit message, which i already did, and running the new code somewhere | 17:34 |
raildo | hey :) | 17:34 |
lwanderley | hi o/ | 17:34 |
rodrigods | cool | 17:35 |
rodrigods | so you basically have a couple of options: provide a VM with external access where this is running | 17:35 |
rodrigods | or setup already a devstack job that runs this | 17:35 |
lwanderley | this second option is the CI job task isn't it? | 17:36 |
rodrigods | yeah | 17:36 |
raildo | lwanderley, yes | 17:36 |
rodrigods | basically :) | 17:36 |
lwanderley | ok | 17:36 |
lwanderley | any advice? | 17:37 |
rodrigods | if it is easier to get a VM deployed, i would go with this | 17:38 |
rodrigods | so we can have the patch merged sooner | 17:38 |
lwanderley | cool, i will look into it | 17:39 |
raildo | if you don't have available resource for now, you can at least record a demo showing that is working and ask him if it enough | 17:39 |
raildo | but having a vm with this will be great | 17:39 |
raildo | lwanderley, so, did you check if tempest is running properly on your environment? | 17:41 |
*** lwanderley has quit IRC | 17:41 | |
*** leticiawanderley has joined #openstack-outreachy | 17:41 | |
*** leticiawanderley is now known as lwanderley | 17:41 | |
lwanderley | sorry about that | 17:41 |
raildo | lwanderley, np, during this last week, did you check if tempest is running properly on this environment? | 17:42 |
lwanderley | yes, that's what i wanted to ask you about, how do i know that? | 17:43 |
lwanderley | and should i check tempest first and then work on the ci job? | 17:44 |
rodrigods | yes, check tempest first | 17:45 |
raildo | yes, would be great you check tempest first, since the ci job, will running those tests on your environment | 17:45 |
raildo | I believe just running tox will be enough (rodrigods is more expert on tempest than me) | 17:46 |
rodrigods | tempest has a ton of docs about how to run it | 17:47 |
raildo | https://docs.openstack.org/tempest/latest/run.html | 17:47 |
rodrigods | devstack itself already sets up tempest by default | 17:47 |
lwanderley | ok, i've ran tox but probably not tempest | 17:48 |
lwanderley | just found that i was using the wrong directory | 17:50 |
lwanderley | it's running now | 17:50 |
rodrigods | cool | 17:50 |
raildo | there is another docs about it: https://docs.openstack.org/zun/latest/dev/tempest_tests.html | 17:50 |
lwanderley | great, thanks! | 17:52 |
raildo | ops, this second link didn't run all the tempest tests, but you can take it as a model for what you have to do | 17:52 |
lwanderley | ok, got it, that helps | 17:53 |
raildo | lwanderley, so work on this tempest tests as soon as possible, so if you have any problem with this, ping us or send a email and we can help you | 17:55 |
lwanderley | ok, i will | 17:55 |
lwanderley | the tempest run looks ok, so far | 17:56 |
lwanderley | but i will ping you with the results | 17:56 |
rodrigods | cool | 17:56 |
raildo | lwanderley, once we have your ack that everything is fine with tempest we can move on to the ci job creation, if not, we have to fix any issue that we find on tempest | 17:56 |
lwanderley | cool | 17:57 |
raildo | ok, anything else? | 17:58 |
lwanderley | not for now | 17:58 |
raildo | rodrigods, do you have something else that you like to share? | 18:00 |
rodrigods | nope | 18:01 |
raildo | great, so have a good week everyone :) | 18:01 |
lwanderley | thanks, you too! :) | 18:02 |
lwanderley | raildo rodrigods everything is fine with tempest :) | 18:54 |
raildo | lwanderley, that's great news :) how did you tests it? | 18:58 |
lwanderley | i ran all tests inside the keystone directory | 19:00 |
raildo | the keystone tests inside tempest, or keystone tests inside devstack? | 19:03 |
lwanderley | keystone tests inside tempest | 19:04 |
raildo | great :) | 19:05 |
raildo | lwanderley, so, since your tempest is running fine with your devstack environment with LDAP enabled, the next step will be implement an automatic solution to tests it for keystone patches | 19:07 |
raildo | lwanderley, so, that why we will create a ci job, to do all the needed changes and execute this tempest tests | 19:07 |
raildo | lwanderley, so, first of all, notice that we need to use this cross-repo dependence: https://docs.openstack.org/infra/manual/developers.html | 19:09 |
lwanderley | ok, so create tests for that environment and add them to tempest on keystone? | 19:09 |
raildo | since you patch on devstack isn't merged yet | 19:09 |
raildo | lwanderley, you're gonna create something similar to this: https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/keystone.yaml#L1-L35 | 19:09 |
raildo | lwanderley, so you should enable the LDAP and multiple domains | 19:10 |
lwanderley | On the local.conf topic? | 19:16 |
raildo | lwanderley, yes, so any change on local.conf and keystone.conf that you need to made to enabled the ldap support, you should do on this job | 19:18 |
lwanderley | ok, cool | 19:18 |
raildo | so, if you need to export some variable to perform this, or change something on devstack you'll add on this script | 19:18 |
raildo | I'm trying to find some tutorial on how to create a new job in the ci | 19:19 |
raildo | if I find something I'll send to you | 19:19 |
lwanderley | thanks! | 19:20 |
raildo | lwanderley, another thing, you should send some answer with your decision for Matthew's comment :) | 19:23 |
raildo | avoid leaving reviewers waiting for answers :) | 19:25 |
lwanderley | i will answer him right now | 19:27 |
raildo | lwanderley, great :) | 19:27 |
*** lwanderley has quit IRC | 19:48 | |
*** lwanderley has joined #openstack-outreachy | 20:00 | |
*** lwanderley has quit IRC | 20:08 | |
*** raildo has quit IRC | 21:16 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!