| openstackgerrit | Zhenyu Zheng proposed openstack/refstack-client master: Refstack-client should use stestr for tempest testing https://review.openstack.org/562956 | 02:08 |
|---|---|---|
| *** markvoelker has quit IRC | 04:29 | |
| openstackgerrit | Chandan Kumar proposed openstack/refstack-client master: [DNM]Generate tempest.conf using python-tempestconf https://review.openstack.org/563827 | 05:43 |
| openstackgerrit | Chandan Kumar proposed openstack/refstack-client master: [DNM]Generate tempest.conf using python-tempestconf https://review.openstack.org/563827 | 05:55 |
| *** markvoelker has joined #refstack | 06:30 | |
| *** kopecmartin has joined #refstack | 06:33 | |
| *** markvoelker has quit IRC | 07:04 | |
| *** rmart04 has joined #refstack | 07:31 | |
| openstackgerrit | Chandan Kumar proposed openstack/refstack-client master: [DNM]Generate tempest.conf using python-tempestconf https://review.openstack.org/563827 | 07:32 |
| *** markvoelker has joined #refstack | 08:01 | |
| *** tosky has joined #refstack | 08:13 | |
| *** markvoelker has quit IRC | 08:34 | |
| *** markvoelker has joined #refstack | 09:31 | |
| openstackgerrit | Martin Kopec proposed openstack/python-tempestconf master: Refstack integration https://review.openstack.org/562672 | 09:39 |
| openstackgerrit | Martin Kopec proposed openstack/python-tempestconf master: Refstack integration https://review.openstack.org/562672 | 09:40 |
| openstackgerrit | Chandan Kumar proposed openstack/refstack-client master: [DNM]Generate tempest.conf using python-tempestconf https://review.openstack.org/563827 | 09:46 |
| *** rmart04_ has joined #refstack | 10:04 | |
| *** markvoelker has quit IRC | 10:06 | |
| *** rmart04 has quit IRC | 10:06 | |
| *** rmart04_ is now known as rmart04 | 10:06 | |
| *** rmart04 has quit IRC | 10:17 | |
| *** rmart04 has joined #refstack | 10:33 | |
| *** rmart04 has quit IRC | 10:46 | |
| *** markvoelker has joined #refstack | 11:02 | |
| *** rmart04 has joined #refstack | 11:09 | |
| *** markvoelker has quit IRC | 11:36 | |
| *** markvoelker has joined #refstack | 12:16 | |
| *** designbybeck has quit IRC | 13:07 | |
| *** chandankumar has joined #refstack | 13:16 | |
| chandankumar | tosky: kopecmartin hello | 13:16 |
| chandankumar | tosky: kopecmartin with this patch https://review.openstack.org/#/c/562672/, one thing is still missing for refstack integration | 13:17 |
| kopecmartin | which one? | 13:17 |
| chandankumar | tosky: kopecmartin as per ptg discussion, before running refstack-client config user should source clourc credentials | 13:18 |
| chandankumar | then refstack client config should generate accounts.yaml file and use them during tempest.conf generation | 13:18 |
| chandankumar | account.yaml is generated by tempest account-generator with needs username and password, tenant name which has permissions to create resources like admin credentails | 13:19 |
| kopecmartin | chandankumar, why does accounts.yaml file need to be generated? | 13:19 |
| tosky | well | 13:19 |
| kopecmartin | well, i understand why, but is it refstack case too? | 13:20 |
| tosky | the credentials used may not be powerful enough to create resources, and being able to create resources is not a requirement for refstack-client, if I remember correctly | 13:20 |
| chandankumar | the question is when refstack tests will be invoked the user will be sourcing non-admin crendentials (which might not have the power to generate resources) | 13:20 |
| chandankumar | that time refstack-client config will dump the credentails in account.yaml file | 13:21 |
| chandankumar | tosky: am i correct? | 13:21 |
| chandankumar | if user credentials have power then it will use tempest accoutn generator to create accounts.yaml | 13:21 |
| tosky | then I don't understand the part about "needs username and password, tenant name which has permissions to create resources like admin credentails" | 13:22 |
| tosky | oh, I see | 13:22 |
| tosky | but I don't get one thing | 13:22 |
| chandankumar | *which needs | 13:22 |
| chandankumar | tosky: yup | 13:22 |
| tosky | do we need two different code paths? If refstack-client or tempestconf can create accounts.yaml, why do we need toi use tempest account generator? | 13:23 |
| tosky | because they will be new non-admin credentials in a separate tenant? | 13:24 |
| chandankumar | tosky: the end goal was to have create accounts.yaml, I was speaking about the implimentation details so asked | 13:24 |
| tosky | chandankumar: do you have the link to the etherpad with the notes that you took during the PTG? | 13:25 |
| tosky | the one that you used to create the stories | 13:25 |
| chandankumar | tosky: one way to create tempest account-generator otherway is to dump the data in accouts.yaml | 13:25 |
| chandankumar | tosky: kopecmartin https://storyboard.openstack.org/#!/story/2001693 | 13:25 |
| chandankumar | tosky: kopecmartin https://storyboard.openstack.org/#!/story/2001696 | 13:25 |
| chandankumar | tosky: https://review.openstack.org/#/c/541273/25/refstack_client/refstack_client.py@793 at os-cloud usage part hogepodge was not sure | 13:27 |
| tosky | chandankumar: that's another implementation question | 13:30 |
| chandankumar | tosky: https://review.rdoproject.org/etherpad/p/rocky-tempest-ptg | 13:30 |
| chandankumar | which i taken notes during ptg | 13:30 |
| kopecmartin | so the big epic goal is to be able to run refstack with python-tempestconf with only non admin credentials, right? | 13:31 |
| chandankumar | kopecmartin: yup | 13:31 |
| kopecmartin | that mean, a user already has all resources python-tempsetconf needs for generating tempest.conf | 13:32 |
| chandankumar | kopecmartin: yup | 13:32 |
| kopecmartin | so where is the problem, tempest.conf is generated and refstack be run | 13:32 |
| kopecmartin | *can be run | 13:32 |
| tosky | oh, on review.rdoproject, I was looking in the wrong place | 13:34 |
| chandankumar | kopecmartin: the problem is about the implementation question. once clourc file is sourced, then tempestconf should generate accounts.yaml (by dumping the data in yaml file as per https://github.com/openstack/refstack-client/blob/master/etc/accounts.yaml.sample) | 13:35 |
| chandankumar | tempestconf should use it to discover resources through refstack client config and write the date to tempest.conf | 13:35 |
| chandankumar | kopecmartin: but we need to maintain a general usecase here for generating accounts.yaml which will be used for admin/non-admin users | 13:36 |
| chandankumar | s/usecase/implementation | 13:37 |
| kopecmartin | i still missing the point .. if a non admin user wants to run refstack, we expect all resources are already created for him by admin .. why accounts.yaml file is not created by that admin as well? | 13:40 |
| chandankumar | reason for using accounts.yaml was not expose password/user credentails in tempest.conf | 13:41 |
| chandankumar | kopecmartin: yup resources will be created by user having permissions before that | 13:42 |
| kopecmartin | and also that user who has permissions can create an accounts.yaml file | 13:43 |
| kopecmartin | and no admin credentials are exposed to tempest.conf | 13:43 |
| tosky | kopecmartin: the idea is: tempest.conf can be published, and having the credentials on accounts.yaml you don't expose user's credentials | 13:44 |
| tosky | so basically the idea is more: never expose the credentials in tempest.conf so that you can publish tempest.conf | 13:44 |
| chandankumar | kopecmartin: but that user having permission to creat accounts.yaml will create test accounts for the same na | 13:45 |
| tosky | if I remember correctly | 13:45 |
| tosky | kopecmartin: and if you start using accounts.yaml, you can always use it | 13:45 |
| chandankumar | kopecmartin: but for running refstack tests, non-admin accounts should be created by admin it might be not be create using tempest account generator | 13:46 |
| chandankumar | tosky: yup | 13:46 |
| kopecmartin | an admin creates resources for demo user, admin also creates accounts.yaml file so that demo user is able to run tempest tests which require creating new resources ... then demo user wants to generate tempest.conf .. no problem, he passes his credentials and path to accounts.yaml file to tempestconf and done, configuration is generated , RESULT: tempest.conf doesn't have admin credentials and can be published | 13:50 |
| kopecmartin | so i don't understand, why python-tempestconf should be able to create accounts.yaml when it does't even have admin credentials | 13:50 |
| tosky | kopecmartin: because (if I remember correctly) you don't want to publish the credentials of public clouds on non-admin users, but you may want to publish tempest.conf | 13:52 |
| chandankumar | kopecmartin: tosky sorry let me rewrite again | 13:53 |
| chandankumar | tempest account-generator is generally used to create accounts.yaml, It required admin or user having previlage to create resources. | 13:54 |
| chandankumar | on running tempest account generator it will create test-accounts in accounts.yaml. | 13:55 |
| chandankumar | But for a normal cloud operator, might create test-accounts manually then dump the data in accounts.yaml for refstack purpose | 13:56 |
| tosky | chandankumar: that's clear, I think that the question from kopecmartin was more: why do you need to create and use accounts.yaml if you are not an admin? | 13:56 |
| chandankumar | then tempestconf can use this accounts.yaml to generate tempest.conf | 13:56 |
| tosky | not *how*, but *why* | 13:57 |
| tosky | how is pretty straightforward | 13:57 |
| tosky | the why, I think it's about detaching the credentials from tempest.conf in any case, admin or not | 13:57 |
| chandankumar | on using accounts.yaml, we are detaching credentails from tempest.conf | 13:58 |
| chandankumar | the workflow discussion was this: if we source clourdrc file and then no accounts.yaml then tempestconf tool should generate accounts.ayml and use it for config generation | 14:00 |
| chandankumar | kopecmartin: due to above point, I was asking about the implementation details | 14:02 |
| kopecmartin | to conclude, in case of running python-tempestconf from refstack , we don't to have any credentials in tempest.conf? | 14:08 |
| chandankumar | kopecmartin: yup | 14:09 |
| kopecmartin | it means, you want to create an test-accounts.yaml file and make an reference to it from tempest.conf (still don't understand the difference between accounts.yaml and test-accounts.yaml file) | 14:10 |
| chandankumar | both are same, it will be used the locking the accounts and using the same for running refstack tempest | 14:11 |
| kopecmartin | ok, then we will not be creating accounts.yaml in python-tempestconf, tempest can do it, why should we copy the functionality | 14:13 |
| tosky | kopecmartin: I didn't know what test-accounts.yaml is, but if I read it correctly, accounts.yaml is the name used by default in tempest documentation for the file with credentials | 14:13 |
| kopecmartin | tosky, ok, makes sense so far | 14:13 |
| tosky | kopecmartin: not copy; the point is not who does what (ok, it is important, but) but adapt the code so that the credentials do not end in tempest.conf | 14:14 |
| tosky | so something should happen inside tempestconf to make sure that this happens; if it is "call some magic (with a stable interface)", sure | 14:14 |
| kopecmartin | tosky, oh, i get it now! | 14:15 |
| tosky | that's the part about implementation detail that chandankumar was raising too | 14:15 |
| chandankumar | tosky: kopecmartin For next tripleo tempest ci sprint, we are targetting refstack integration epic to get it done | 14:15 |
| kopecmartin | chandankumar, ok | 14:16 |
| chandankumar | tosky: apart from this https://review.openstack.org/#/c/562672/ this one looks ok from myside (the thing which i needed ) | 14:19 |
| chandankumar | kopecmartin: please update the commit message something meaningful | 14:19 |
| tosky | more than "refstack integration", it's more "make tempestconf easier to use as library" | 14:20 |
| tosky | or something like that | 14:20 |
| chandankumar | arxcruz: https://review.openstack.org/#/c/562672/ feel free to take a look | 14:20 |
| kopecmartin | chandankumar, what's not meaningful about that? | 14:21 |
| tosky | kopecmartin: see my comment ^^ for a possible explantion | 14:21 |
| chandankumar | kopecmartin: 'refstack integration' should be changed to something useable as tosky suggested | 14:21 |
| chandankumar | sorry for mine sleepy head | 14:21 |
| kopecmartin | oh, i see, ok | 14:22 |
| kopecmartin | I have enough too, this one hour conversation was too hard :D | 14:22 |
| chandankumar | kopecmartin: we can get it merged today, I am going out in sometime, may be join meeting for next week continously I am skipping lots of things | 14:23 |
| openstackgerrit | Martin Kopec proposed openstack/python-tempestconf master: Make tempestconf easier to use as an external library https://review.openstack.org/562672 | 14:25 |
| chandankumar | logging out | 14:56 |
| *** rmart04 has quit IRC | 15:01 | |
| *** kopecmartin has quit IRC | 15:48 | |
| *** designbybeck has joined #refstack | 16:37 | |
| openstackgerrit | megan guiney proposed openstack/refstack master: allow for the addition of new capability sources https://review.openstack.org/547246 | 17:27 |
| *** rmart04 has joined #refstack | 17:31 | |
| *** rmart04 has quit IRC | 17:45 | |
| *** rmart04 has joined #refstack | 17:46 | |
| *** rmart04 has quit IRC | 18:53 | |
| *** xinliang has quit IRC | 18:56 | |
| *** xinliang has joined #refstack | 19:11 | |
| openstackgerrit | Martin Kopec proposed openstack/python-tempestconf master: Make tempestconf easier to use as an library https://review.openstack.org/562672 | 20:59 |
| *** tosky has quit IRC | 23:58 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!