openstackgerrit | Catherine Diep proposed openstack/refstack: Update to reflect project movement from stackforge to openstack. https://review.openstack.org/222945 | 00:22 |
---|---|---|
*** openstackgerrit has quit IRC | 01:16 | |
*** openstackgerrit has joined #refstack | 01:16 | |
*** geoffarnold is now known as geoffarnoldX | 02:01 | |
*** geoffarnoldX is now known as geoffarnold | 03:04 | |
*** davidlenwell_ has quit IRC | 03:24 | |
*** eglute has quit IRC | 03:25 | |
*** davidlenwell has joined #refstack | 03:26 | |
*** ChanServ sets mode: +o davidlenwell | 03:26 | |
*** eglute has joined #refstack | 03:29 | |
*** geoffarnold is now known as geoffarnoldX | 04:06 | |
*** geoffarnoldX is now known as geoffarnold | 04:40 | |
openstackgerrit | Merged openstack/refstack-client: Update .gitreview for project rename https://review.openstack.org/222817 | 05:27 |
openstackgerrit | Merged openstack/refstack: Update .gitreview for project rename https://review.openstack.org/222812 | 05:31 |
*** geoffarnold is now known as geoffarnoldX | 05:43 | |
*** openstackgerrit has quit IRC | 10:16 | |
*** openstackgerrit has joined #refstack | 10:16 | |
openstackgerrit | Merged openstack/refstack: Update to reflect project movement from stackforge to openstack. https://review.openstack.org/222945 | 10:37 |
*** openstackgerrit has quit IRC | 12:16 | |
*** openstackgerrit has joined #refstack | 12:16 | |
*** openstackgerrit has quit IRC | 13:16 | |
*** openstackgerrit has joined #refstack | 13:16 | |
*** geoffarnoldX is now known as geoffarnold | 14:36 | |
*** cody-somerville has joined #refstack | 15:43 | |
*** cody-somerville has quit IRC | 15:43 | |
*** cody-somerville has joined #refstack | 15:43 | |
*** openstackgerrit has quit IRC | 16:01 | |
*** openstackgerrit has joined #refstack | 16:01 | |
*** geoffarnold is now known as geoffarnoldX | 16:06 | |
*** geoffarnoldX is now known as geoffarnold | 16:10 | |
openstackgerrit | Catherine Diep proposed openstack/refstack-client: Update refstack-client to reflect movement to openstack namespace. https://review.openstack.org/223220 | 16:46 |
*** openstackgerrit has quit IRC | 18:16 | |
*** openstackgerrit has joined #refstack | 18:16 | |
*** pvaneck has joined #refstack | 18:21 | |
*** edmondsw has joined #refstack | 18:24 | |
edmondsw | so I just discovered that refstack-client only works with keystone v2.0... is anyone working on support for keystone v3? | 18:25 |
catherineD | Hi edmondsw: just a question is your test faiing at the place where refstack-client trying to the cloudid (Keystone ID) ... we are working on a patch for that ... | 18:33 |
catherineD | trying to get the Keystone ID .. | 18:33 |
edmondsw | fails here: https://github.com/openstack/refstack-client/blob/master/refstack_client/refstack_client.py#L141 | 18:35 |
edmondsw | not sure what a "cloudid" is | 18:35 |
catherineD | edmondsw: yup that is the area we are fixing .... | 18:36 |
edmondsw | but looking at the code, this isn't just a bug, it's missing function... there is nothing in here that would support v3... no way to specify domain, and the code imports the v2.0 client from keystoneclient | 18:36 |
edmondsw | but you are working on that, to support v3? | 18:37 |
edmondsw | is there a commit I should watch? | 18:37 |
catherineD | yes | 18:37 |
edmondsw | catherineD is there a commit I should help review? or a bug I should subscribe to? | 18:40 |
catherineD | we are updating https://review.openstack.org/#/c/221555/ first .. | 18:50 |
catherineD | Please see https://github.com/openstack/refstack/blob/master/specs/proposed/refstack-org-api-cloud-uuid.rst for information about CPID (cloud provider id) | 18:52 |
*** cody-somerville has quit IRC | 18:53 | |
*** nijaba has quit IRC | 19:01 | |
*** nijaba has joined #refstack | 19:04 | |
*** nijaba has quit IRC | 19:04 | |
*** nijaba has joined #refstack | 19:04 | |
openstackgerrit | Merged openstack/refstack-client: Update refstack-client to reflect movement to openstack namespace. https://review.openstack.org/223220 | 19:09 |
sslypushenko | ping all) | 20:00 |
catherineD | hi | 20:00 |
sslypushenko | Disabling anonimous uploading doesn't mean creating an account | 20:00 |
sslypushenko | If you want to look on test results on refstack.net - you should have one | 20:01 |
sslypushenko | But user can upload data just with his own pubkey and create account later | 20:02 |
catherineD | sslypushenko: that also bring us to another issues is that ... right now we can upload the data with a key ... but the key may not exist in the refstack server ... | 20:02 |
catherineD | that means that the data will never being accessed .. | 20:02 |
pvaneck | you mean user for that key? | 20:02 |
sslypushenko | And it is by design) | 20:02 |
sslypushenko | I was planning to add users with admin access level | 20:03 |
catherineD | yes if there is malicisous data upload to fill up refstack .... | 20:03 |
sslypushenko | They should see all test results | 20:03 |
sslypushenko | Admins can remove any trash things | 20:03 |
catherineD | no one will see t he results with that key is not imported | 20:04 |
sslypushenko | Right now - yes | 20:04 |
catherineD | how would admin define what is trash? | 20:04 |
sslypushenko | But it can be easly changed) | 20:04 |
sslypushenko | for example if there is now pubkey in server for one month | 20:05 |
sslypushenko | or somthing like that | 20:05 |
catherineD | or would it be better to check for key existence before acepting the data? | 20:05 |
sslypushenko | Maybe | 20:06 |
catherineD | just give it some thoughts .... | 20:06 |
sslypushenko | But it brings user to neccessity of account creation | 20:06 |
catherineD | just something that we should consuder .. | 20:06 |
catherineD | yup all is back to the vendor registration, vendore to user, and vendor user to data relatonship .. | 20:07 |
*** edmondsw has left #refstack | 20:07 | |
catherineD | Just want us to give some thoughts to the subject .. | 20:07 |
sslypushenko | Sure, it should be next big move for RefStack | 20:07 |
catherineD | for now our priority should be to support keystone v3 API | 20:07 |
catherineD | sslypushenko: yes it is ... no doubt | 20:08 |
sslypushenko | If I will have free time this week I'll try to add v3 support | 20:08 |
catherineD | thank you all! got to run to an other meeting ... | 20:08 |
*** esker has joined #refstack | 20:10 | |
*** cody-somerville has joined #refstack | 20:27 | |
*** openstackgerrit has quit IRC | 20:31 | |
*** openstackgerrit has joined #refstack | 20:31 | |
sslypushenko | I investigated keystone code and got a litte shock))) In API V2 service id is not service id | 20:46 |
sslypushenko | It is id of the first keystone endpoint (public, admin, internal) in mysql database | 20:47 |
sslypushenko | I can extract all these ids using API V3, but I cann't guess what endpoint ID is using in V2 API as service ID | 20:49 |
sslypushenko | So, my suggestion is to use API V2 if it is possible and API V3 - only if not. | 20:51 |
sslypushenko | It can cause some issues if cloud drops V2 support and only API V3 stays | 20:52 |
catherineD | sslypushenko: that is exactly what we are saying is that in V2 what is returned is the first keystone endpoint id and we do not know which one (public, private or admin) | 21:36 |
*** esker has quit IRC | 21:39 | |
*** openstackgerrit has quit IRC | 21:46 | |
*** openstackgerrit has joined #refstack | 21:46 | |
catherineD | my approach is we should use V3 when possible (that applies for env that supports both v2 and v3 and the env that only support v3) if the env only support v2 then that is what we should use | 21:58 |
*** coolsvap has quit IRC | 22:48 | |
*** cody-somerville has quit IRC | 23:00 | |
*** geoffarnold is now known as geoffarnoldX | 23:22 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!