Monday, 2015-09-14

openstackgerritCatherine Diep proposed openstack/refstack: Update to reflect project movement from stackforge to openstack.  https://review.openstack.org/22294500:22
*** openstackgerrit has quit IRC01:16
*** openstackgerrit has joined #refstack01:16
*** geoffarnold is now known as geoffarnoldX02:01
*** geoffarnoldX is now known as geoffarnold03:04
*** davidlenwell_ has quit IRC03:24
*** eglute has quit IRC03:25
*** davidlenwell has joined #refstack03:26
*** ChanServ sets mode: +o davidlenwell03:26
*** eglute has joined #refstack03:29
*** geoffarnold is now known as geoffarnoldX04:06
*** geoffarnoldX is now known as geoffarnold04:40
openstackgerritMerged openstack/refstack-client: Update .gitreview for project rename  https://review.openstack.org/22281705:27
openstackgerritMerged openstack/refstack: Update .gitreview for project rename  https://review.openstack.org/22281205:31
*** geoffarnold is now known as geoffarnoldX05:43
*** openstackgerrit has quit IRC10:16
*** openstackgerrit has joined #refstack10:16
openstackgerritMerged openstack/refstack: Update to reflect project movement from stackforge to openstack.  https://review.openstack.org/22294510:37
*** openstackgerrit has quit IRC12:16
*** openstackgerrit has joined #refstack12:16
*** openstackgerrit has quit IRC13:16
*** openstackgerrit has joined #refstack13:16
*** geoffarnoldX is now known as geoffarnold14:36
*** cody-somerville has joined #refstack15:43
*** cody-somerville has quit IRC15:43
*** cody-somerville has joined #refstack15:43
*** openstackgerrit has quit IRC16:01
*** openstackgerrit has joined #refstack16:01
*** geoffarnold is now known as geoffarnoldX16:06
*** geoffarnoldX is now known as geoffarnold16:10
openstackgerritCatherine Diep proposed openstack/refstack-client: Update refstack-client to reflect movement to openstack namespace.  https://review.openstack.org/22322016:46
*** openstackgerrit has quit IRC18:16
*** openstackgerrit has joined #refstack18:16
*** pvaneck has joined #refstack18:21
*** edmondsw has joined #refstack18:24
edmondswso I just discovered that refstack-client only works with keystone v2.0... is anyone working on support for keystone v3?18:25
catherineDHi 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
catherineDtrying to get the Keystone ID ..18:33
edmondswfails here: https://github.com/openstack/refstack-client/blob/master/refstack_client/refstack_client.py#L14118:35
edmondswnot sure what a "cloudid" is18:35
catherineDedmondsw: yup that is the area we are fixing ....18:36
edmondswbut 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 keystoneclient18:36
edmondswbut you are working on that, to support v3?18:37
edmondswis there a commit I should watch?18:37
catherineDyes18:37
edmondswcatherineD is there a commit I should help review? or a bug I should subscribe to?18:40
catherineDwe are updating https://review.openstack.org/#/c/221555/ first ..18:50
catherineDPlease 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 IRC18:53
*** nijaba has quit IRC19:01
*** nijaba has joined #refstack19:04
*** nijaba has quit IRC19:04
*** nijaba has joined #refstack19:04
openstackgerritMerged openstack/refstack-client: Update refstack-client to reflect movement to openstack namespace.  https://review.openstack.org/22322019:09
sslypushenkoping all)20:00
catherineDhi20:00
sslypushenkoDisabling anonimous uploading doesn't mean creating an account20:00
sslypushenkoIf you want to look on test results on refstack.net - you should have one20:01
sslypushenkoBut user can upload data just with his own pubkey and create account later20:02
catherineDsslypushenko: 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
catherineDthat means that the data will never being accessed ..20:02
pvaneckyou mean user for that key?20:02
sslypushenkoAnd it is by design)20:02
sslypushenkoI was planning to add users with admin access level20:03
catherineDyes if there is malicisous data upload to fill up refstack ....20:03
sslypushenkoThey should see all test results20:03
sslypushenkoAdmins can remove any trash things20:03
catherineDno one will see t he results with that key is not imported20:04
sslypushenkoRight now - yes20:04
catherineDhow would admin define what is trash?20:04
sslypushenkoBut it can be easly changed)20:04
sslypushenkofor example if there is now pubkey in server for one month20:05
sslypushenkoor somthing like that20:05
catherineDor would it be better to check for key existence  before acepting the data?20:05
sslypushenkoMaybe20:06
catherineDjust give it some thoughts ....20:06
sslypushenkoBut it brings user to neccessity of account creation20:06
catherineDjust something that we should consuder ..20:06
catherineDyup all is back to the vendor registration, vendore to user, and vendor user to data relatonship ..20:07
*** edmondsw has left #refstack20:07
catherineDJust want us to give some thoughts to the subject  ..20:07
sslypushenkoSure, it should be next big move for RefStack20:07
catherineDfor now our priority should be to support keystone v3 API20:07
catherineDsslypushenko: yes it is ... no doubt20:08
sslypushenkoIf I will have free time this week I'll try to add v3 support20:08
catherineDthank you all!  got to run to an other meeting ...20:08
*** esker has joined #refstack20:10
*** cody-somerville has joined #refstack20:27
*** openstackgerrit has quit IRC20:31
*** openstackgerrit has joined #refstack20:31
sslypushenkoI investigated keystone code and got a litte shock))) In API V2 service id is not service id20:46
sslypushenkoIt is id of the first keystone endpoint (public, admin, internal) in mysql database20:47
sslypushenkoI can extract all these ids using API V3, but I cann't guess what endpoint ID is using in V2 API as service ID20:49
sslypushenkoSo, my suggestion is to use API V2 if it is possible and API V3 - only if not.20:51
sslypushenkoIt can cause some issues if cloud drops V2 support and only API V3 stays20:52
catherineDsslypushenko: 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 IRC21:39
*** openstackgerrit has quit IRC21:46
*** openstackgerrit has joined #refstack21:46
catherineDmy 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 use21:58
*** coolsvap has quit IRC22:48
*** cody-somerville has quit IRC23:00
*** geoffarnold is now known as geoffarnoldX23:22

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