Friday, 2016-02-19

*** cjvolzka has quit IRC00:35
*** _sarob has quit IRC01:31
openstackgerritMerged openstack/refstack: update angular bootstrap lib version  https://review.openstack.org/28018701:53
*** markvoelker_ has quit IRC02:34
*** _sarob has joined #refstack03:03
*** _sarob has quit IRC03:08
*** _sarob has joined #refstack03:12
*** _sarob has quit IRC03:15
*** _sarob has joined #refstack03:17
*** krotscheck_dr is now known as krotscheck_afk03:18
*** esker has joined #refstack03:27
*** _sarob has quit IRC03:34
*** markvoelker has joined #refstack03:34
*** markvoelker has quit IRC03:39
*** _sarob has joined #refstack03:49
*** cjvolzka has joined #refstack03:52
*** cjvolzka has quit IRC03:52
*** _sarob has quit IRC04:14
*** _sarob has joined #refstack05:22
*** _sarob has quit IRC05:32
*** _sarob has joined #refstack05:32
*** markvoelker has joined #refstack05:36
*** markvoelker has quit IRC05:40
*** _sarob has quit IRC05:41
*** _sarob has joined #refstack05:41
*** _sarob has quit IRC05:57
*** _sarob has joined #refstack05:57
*** _sarob has quit IRC06:01
*** _sarob has joined #refstack06:01
*** _sarob has quit IRC06:02
*** resker has joined #refstack06:13
*** esker has quit IRC06:15
*** resker has quit IRC06:30
*** esker has joined #refstack06:53
*** esker has quit IRC07:31
*** markvoelker has joined #refstack07:36
*** markvoelker has quit IRC07:40
*** esker has joined #refstack07:50
*** esker has quit IRC08:31
*** esker has joined #refstack08:41
*** esker has quit IRC09:30
*** esker has joined #refstack09:34
*** markvoelker has joined #refstack09:37
*** markvoelker has quit IRC09:42
*** esker has quit IRC11:31
*** markvoelker has joined #refstack11:38
*** markvoelker has quit IRC11:42
*** esker has joined #refstack11:43
*** esker has quit IRC12:27
*** esker has joined #refstack12:36
*** Deng has quit IRC12:53
*** markvoelker has joined #refstack12:54
*** markvoelker has quit IRC12:58
*** markvoelker has joined #refstack13:04
*** krotscheck_afk is now known as krotscheck13:05
*** edmondsw has joined #refstack13:28
openstackgerritAndrey Pavlov proposed openstack/refstack: WIP: new Refstack model.  https://review.openstack.org/28167913:59
*** cjvolzka has joined #refstack14:23
*** esker has quit IRC14:26
*** openstackgerrit_ has quit IRC14:43
*** openstackgerrit_ has joined #refstack15:00
*** esker has joined #refstack15:20
*** esker has quit IRC15:25
*** coolsvap|away has quit IRC16:03
*** coolsvap|away has joined #refstack16:09
*** esker has joined #refstack17:08
*** esker has quit IRC17:29
*** pilgrimstack has quit IRC17:56
*** _sarob has joined #refstack18:22
*** krotscheck has quit IRC18:25
*** dmellado has quit IRC18:25
*** krotscheck has joined #refstack18:25
*** dmellado has joined #refstack18:26
*** lifeless has quit IRC18:27
*** christiana has quit IRC18:27
*** lifeless has joined #refstack18:27
*** andrey-mp has joined #refstack18:51
*** alexandrelevine has joined #refstack18:58
catherineDhello ...19:01
andrey-mphi19:02
catherineDandrey-mp: sorry you have to stay late on a Friday ...19:02
andrey-mpbut I'm at home )19:02
catherineDLet's wait a few mins19:03
catherineDPaul is on vacation today ...19:05
alexandrelevinehi19:05
catherineDwe can talk about the pypi package for RefStack ... Paul submitted 2 patches for  RefStack to use pypi ... andrey-mp: is one of the reviewers19:06
catherineDalexandrelevine: hi19:06
andrey-mpone is already merged (to project-config)19:06
andrey-mpbut second has a WIP=-1 from Paul19:07
andrey-mpand I don't know why19:07
catherineDyea he is still testing19:07
catherineDhttps://etherpad.openstack.org/p/refstack-meeting-16-02-1519:07
alexandrelevinecatherineD: Have you seen my questions in the mailing list? Do you think they make sense?19:07
catherineDlet's discuss item 919:07
catherineDalexandrelevine: I response ...19:07
catherineDwe can come back to alexandrelevine: email to DefCore later19:08
alexandrelevinecatherineD: Oh, you did. Thanks a lot. Just received it.19:08
catherineDhttps://refstack.openstack.org/api/v1/results?signed   works as designed19:09
catherineDit returns every tests (share, not share)  that the user created19:10
catherineDand that is what used to list in "My Results"19:10
andrey-mpcatherineD: I thought it returns only signed tests19:11
catherineDyes only signed test19:11
andrey-mpbecause we can't decide which test is it if it is not signed19:11
catherineDsigned tests of the user that include share , not share uploaded by the user19:11
alexandrelevinecatherineD: The supposed problem is with simple request, without "signed" filter.19:12
*** _sarob has quit IRC19:12
andrey-mpf19:12
catherineDwithout signed  it will return everything that is public plus what ever crested by the user19:13
andrey-mp(and shared)19:13
catherineDshared and not shared (one sec let me verify)19:15
alexandrelevinecatherineD: "It doesn't return signed but not shared results belonging to the user sending the request"19:15
*** esker has joined #refstack19:15
catherineDchecking ..19:16
andrey-mpi understand code as - without signed it returns all not signed results + all shared results19:17
andrey-mphttps://github.com/openstack/refstack/blob/master/refstack/db/sqlalchemy/api.py#L22919:17
catherineDandrey-mp: you are right .. it does not return "not shared"  that is a bug19:18
*** _sarob has joined #refstack19:18
catherineDandrey-mp: you want to log a bug?19:18
andrey-mplet's discuss it first19:18
catherineDk19:19
andrey-mpfixing of this bug will affect showing private user tests in tab 'community results'19:19
catherineDandrey-mp: only when the user log in19:19
andrey-mpyeah19:19
andrey-mpis it suitable?19:19
catherineDandrey-mp:  not suitable for the UI19:20
catherineDbecause the UI labled "community results" which should only be shared records19:20
andrey-mpbut in UI we can't filter it normally due to paging :)19:20
catherineDbut from REST API ... it should return everything that the user have privilege to19:21
andrey-mpwhat we wil do with UI side?19:21
catherineDandrey-mp: the ui will display less items then the page allow19:22
andrey-mpand sometimes we can see empty page... (because all results on this page is not 'community results')19:23
catherineDandrey-mp: that is a valid concern19:23
andrey-mpalexandrelevine: what do you think?19:24
alexandrelevinecatherineD: We can introduce more filters. Like "public". It'll return all signed and unsigned but publicly available.19:25
catherineDandrey-mp: the other option is to add filer19:25
alexandrelevineand the list without filters would return everything available.19:25
catherineD:-)19:25
catherineDyea19:25
alexandrelevineI guess the same filter we can introduce to other REST APIs if we really want to do server-side paging/sorting/filtering.19:26
andrey-mpalexandrelevine: right now 'signed' word is present in query part of URL.19:26
catherineDalexandrelevine: for test results ... the only sorting right now is on upload date19:26
alexandrelevinecatherineD: I agree. I'm thinking about common approach to all other REST APIs.19:27
alexandrelevinecatherineD: However, obviously, sorting by CloudID would be very useful for test results.19:27
alexandrelevinecatherineD: It'll be much more useful than "by date". Maybe we should introduce filter for this in Mitaka. It'll greatly improve user experience.19:28
catherineDalexandrelevine: I agree ... this is why I want us to carefully thinking about the API19:28
andrey-mpwhat is the last decision about filter param in REST API?19:28
catherineDalexandrelevine: I would suggest that we makethe improvement in the new API s first ...19:29
catherineDdesign the APIs based and improve from the lession learned19:30
alexandrelevinecatherineD: It doesn't much matter - mechanisms should be all very similar, so when you add something or change something in one place - the same in others should be much easier. But the value is huge.19:30
catherineDalexandrelevine: I understand that is why we will select the important feature to implemented first ... at the test results listing time ... we believe sort by data is important and did not implement sort by cpid ...19:31
catherineDbut we did filter by CPID19:31
catherineDso after fitlering the user will have a small list of results with one CPID and sorted by date19:32
alexandrelevinecatherineD: Ok, so you vote for server-side filtering/paging/sorting? Don't want simple REST APIs and paging client-side?19:32
catherineDit is not perfect but are the import feature at the time19:32
andrey-mp(btw, tag is working now and new commits don't go to production)19:33
catherineDno I vote for implementing pagind and filtering at the REST API level ... as I have written the REST aPI spec19:33
catherineDandrey-mp: yea we are good for that ...19:34
alexandrelevinecatherineD: Yes, Andrey is right, now everything should be merged faster, right?19:34
alexandrelevinecatherineD: REST API level means server-side. Ok.19:34
catherineDbut I still want to control what is being merged tp RefStack ... I really do not want us to do a lot of clean up19:34
alexandrelevinecatherineD: We won't. But we need to move faster.19:34
alexandrelevine(sorry to push :) )19:34
catherineDso far the RefStack site does not have a lot of issues becayse we have been careful in code merge and put code on line incrementally19:35
catherineDalexandrelevine: we do not move as fast because we disagree19:35
catherineDI am not saying that disagreement is not good19:35
catherineDI ams saying that we have more aspects to consider ... which I believe is good for the long run19:36
alexandrelevinecatherineD: I take it when we agree we'll move fast :)19:36
catherineDexactly ...19:36
catherineDand we disagree because of different perspective that we have19:36
catherineDand if we take sometime to ion out the different opinions ... our slowness actually will have line issues or even line down situation19:38
catherineDso I would rather we move faster bu do not mind we take time to do the right thing19:38
alexandrelevinecatherineD: Ok, let's put it as one of the outcomes of this meeting: We'll do the right thing :)19:39
catherineDso for the list results .. I think it is a bug in the REST API that it does not return everything ... as for the UI ... we can add a filter at the REST API level ...19:40
catherineDto list all public test results19:40
alexandrelevineagree19:41
catherineDthe thing is this bug a high priority for us now? of course we will log the bug ...  I would rather us to concentrate on vendor registraion for Mitaka19:41
alexandrelevineIt's very easy to fix. We'll squeeze it in at some point. Don't worry.19:42
catherineDalexandrelevine: I know we can implement with adding a public filfer ... but is that what we want .. or we should add a query liek type and let the filter be as type in (public, signd  ...)19:43
alexandrelevinecatherineD: I'll think about it. We'll need to commonize it for all REST APIs so I'll suggest later.19:44
catherineDso I suggest that let's us gain a bit more experience in the vendor, user, product API in terms of filtering and sorting and then fix older API later19:45
andrey-mpcatherineD: good point :)19:45
catherineDlet 's set a uniform way for RefStack API so our API is predictable and therefore user friendly19:46
catherineDbut definitely log a bug for the lis resutls ...19:46
catherineDI have hard stop in 13 mins ... let's talk about user management19:47
andrey-mpcatherineD: could you file a bug?19:47
catherineDandrey-mp: I will19:47
andrey-mpthank you!19:47
alexandrelevinecatherineD: What about user management?19:48
catherineDandrey-mp: THANK YOU!!!  for finding the bug19:48
catherineDwhat do we want to use as the identifier for the user :   v1/vendors/{vendor_id}/users/{user_email}  or   v1/vendors/{vendor_id}/users/{user_openid}19:48
catherineDI think either email or openid would be enough19:49
alexandrelevineuser_openid19:49
catherineDI vote for email because that is what we use to log into openid19:49
alexandrelevinedefinitely not email.19:49
alexandrelevineid should be used in all requests for all entities.19:49
alexandrelevineAll REST APIs should work with IDs.19:49
alexandrelevineSo if for user we choose openid as id - then that's what it is.19:50
catherineDI am confuse ... from your email to DefCore ... I thought you say that OpenID is hard to get19:50
alexandrelevinecatherineD: No. I said it's useless in terms of displaying.19:50
catherineDI don't mind either way ..19:50
alexandrelevinecatherineD: And I said it's hard to get for poor Vendor. Not for our UI. It'll get it from the list of users.19:50
catherineDso we use OpenID as andrey-mp: had commented we have to encode it19:51
alexandrelevineperfect19:51
catherineDif we want to use it on the URI19:51
andrey-mpbase64 encoding19:51
catherineDso that would become a string from the REST API point of view19:52
andrey-mpyes19:52
catherineDok19:52
catherineDI will update the API spec so we can discuss if neede on Monday ...19:53
andrey-mpcould we discuss this review https://review.openstack.org/#/c/281299/ on Monday meeting?19:53
catherineDwe can discuss a bit now ..19:54
andrey-mpperfect19:54
andrey-mpI want to get some reviews19:55
catherineDwhat would be the advantage on create flag vs calling the method api_utils.check_user_is_foundation_admin()  directly? saving cpu process?19:55
andrey-mpmain problem here - is to have additional flag in profile REST and have same flag in JS state19:56
catherineDok I see the point ... between server and JS (client)19:57
andrey-mprendering of some pages needs to know user privileges to render elements19:57
catherineDshould is_admin be is_foundation_admin ?  because down the road we may have vendor admin?  or we have to document somewhere that the term "admin" is used foundation admin?19:58
alexandrelevinecatherineD: no. It shouldn't19:58
alexandrelevinecatherineD: We'll handle vendor admin differently when the time comes.19:58
catherineDalexandrelevine: please explain19:58
andrey-mpuser can be admin of several vendors for example19:59
andrey-mpbut foundation only one19:59
catherineDmy concern is at the JS level ... the code will get the flag of is_admin?  do the reader know that means foundation admin?  T19:59
alexandrelevinecatherineD: foundation admin is a privilege and affects everything. Vendor admin would be in some particular lists or actions and we might want to use various permissions like can_add or can_list or something.19:59
catherineDalexandrelevine I know20:00
andrey-mpi can rename it to is_foundation_admin but we can define term 'admin' as foundation admin20:00
alexandrelevinecatherineD: In any case - admin is the superuser. No need to add foundation_admin. Whatever we do with the vendor admin, is_admin means superuser.20:00
andrey-mpwhere we can define 'admin = foundation admin' ?20:01
alexandrelevineandrey-mp: We shouldn't. Admin - means superuser. No need to bother anymore.20:01
catherineDandrey-mp: I don't mind either way : rename or document ... but we need to do one of it for the new coder to RefStack to read the code eaiser ...20:01
andrey-mpoh, ok20:01
*** davidlenwell has quit IRC20:01
alexandrelevineI think I have to go. Can we continue Monday? Hopefully we'll get some more answers from DefCore as well.20:02
catherineDok thx andrey-mp: alexandrelevine:20:02
andrey-mpcatherineD: I vote for document somewhere20:02
alexandrelevinethank you. bye.20:02
andrey-mpthank you!20:02
*** alexandrelevine has quit IRC20:02
andrey-mpbyu20:02
andrey-mpbye20:03
catherineDandrey-mp: yep document is good thx20:03
*** andrey-mp has quit IRC20:05
*** davidlenwell has joined #refstack20:06
*** ChanServ sets mode: +o davidlenwell20:06
*** christiana has joined #refstack20:34
*** _sarob has quit IRC20:38
*** _sarob has joined #refstack20:42
*** _sarob has quit IRC20:47
*** _sarob has joined #refstack20:50
*** _sarob has quit IRC20:55
*** _sarob has joined #refstack20:55
*** sarob_ has joined #refstack21:02
*** _sarob has quit IRC21:04
*** pilgrimstack has joined #refstack21:12
*** edmondsw has quit IRC21:44
openstackgerritCatherine Diep proposed openstack/refstack: REST API specification for vendor user management.  https://review.openstack.org/27731322:22
*** sarob_ has quit IRC22:24
openstackgerritCatherine Diep proposed openstack/refstack: REST API specification for vendor user management.  https://review.openstack.org/27731322:35
*** _sarob has joined #refstack22:36
*** _sarob has quit IRC22:37
*** _sarob has joined #refstack22:37
*** _sarob has quit IRC22:37
*** _sarob has joined #refstack22:37
*** pilgrimstack has quit IRC23:25

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