Thursday, 2016-02-18

*** fzdarsky has quit IRC00:04
*** fzdarsky has joined #openstack-sdks00:06
*** sdague has quit IRC00:06
*** Qiming has quit IRC00:16
*** lhcheng_ has joined #openstack-sdks00:20
*** RuiChen has quit IRC00:21
*** RuiChen has joined #openstack-sdks00:22
*** lhcheng has quit IRC00:23
openstackgerritPushkar proposed openstack/python-openstackclient: Format the metadata/properties dict for aggregate  https://review.openstack.org/28159200:23
openstackgerritTang Chen proposed openstack/python-openstackclient: Subnet Pool: Add "subnet pool show" command  https://review.openstack.org/27993500:56
openstackgerritTang Chen proposed openstack/python-openstackclient: Subnet Pool: Add "subnet pool list" command  https://review.openstack.org/27991800:56
openstackgerritTang Chen proposed openstack/python-openstackclient: Subnet Pool: Add "subnet pool delete" command  https://review.openstack.org/27955000:56
*** tangchen has joined #openstack-sdks01:01
*** Qiming has joined #openstack-sdks01:14
*** fzdarsky has quit IRC01:18
*** Yanyanhu has joined #openstack-sdks01:37
openstackgerritReedip proposed openstack/python-openstackclient: Subnet: Add "subnet set" command using SDK  https://review.openstack.org/28112901:37
openstackgerritReedip proposed openstack/python-openstackclient: Subnet: Add "subnet set" command using SDK  https://review.openstack.org/28112901:38
openstackgerritReedip proposed openstack/python-openstackclient: Subnet: Add "subnet delete" command using SDK  https://review.openstack.org/27820901:41
openstackgerritReedip proposed openstack/python-openstackclient: Subnet: Add "subnet set" command using SDK  https://review.openstack.org/28112901:53
*** gouthamr has joined #openstack-sdks02:15
*** gouthamr_ has joined #openstack-sdks02:16
*** gouthamr has quit IRC02:20
openstackgerritReedip proposed openstack/python-openstackclient: Subnet: Add "subnet delete" command using SDK  https://review.openstack.org/27820902:43
*** salv-orl_ has quit IRC03:04
*** gildub has quit IRC03:11
*** dims_ has quit IRC03:30
*** dims has joined #openstack-sdks03:32
*** gildub has joined #openstack-sdks03:35
*** woodster_ has quit IRC03:36
*** lhcheng_ has quit IRC03:42
*** lhcheng has joined #openstack-sdks04:27
openstackgerritSergey Nikitin proposed openstack/api-wg: Added tags restrictions to the tagging guidelines  https://review.openstack.org/27670904:27
*** dims_ has joined #openstack-sdks04:53
*** dims has quit IRC04:55
*** dims_ has quit IRC05:00
openstackgerritTang Chen proposed openstack/python-openstackclient: Router: Add --route and --clear-routes options to "router set" command  https://review.openstack.org/27604205:01
openstackgerritTang Chen proposed openstack/python-openstackclient: Add KeyValueListAction to custom parser action  https://review.openstack.org/27604105:01
*** dims has joined #openstack-sdks05:02
*** dims has quit IRC05:02
*** gildub has quit IRC06:13
openstackgerritSergey Nikitin proposed openstack/api-wg: Added tags restrictions to the tagging guidelines  https://review.openstack.org/27670906:25
*** fzdarsky has joined #openstack-sdks06:34
*** fzdarsky has quit IRC06:52
*** fzdarsky has joined #openstack-sdks06:54
*** e0ne has joined #openstack-sdks07:41
*** salv-orlando has joined #openstack-sdks07:44
*** e0ne has quit IRC07:58
*** fzdarsky has quit IRC08:08
*** lhcheng has quit IRC08:10
openstackgerritReedip proposed openstack/python-openstackclient: [WIP] Add "router port add" to osc  https://review.openstack.org/28169108:24
openstackgerritReedip proposed openstack/python-openstackclient: [WIP] Add "router port delete" to osc  https://review.openstack.org/28169408:31
openstackgerritReedip proposed openstack/python-openstackclient: [WIP] Add "router port delete" to osc  https://review.openstack.org/28169408:34
openstackgerritMerged openstack/python-openstackclient: Refactor security group rule delete to use SDK  https://review.openstack.org/27677509:03
openstackgerritMerged openstack/python-openstackclient: Support "network list" command in nova network  https://review.openstack.org/27825309:03
openstackgerritMerged openstack/python-openstackclient: Support "network show" command in nova network  https://review.openstack.org/27908509:03
*** Qiming has quit IRC09:06
*** lucas-dinner is now known as lucasagomes09:24
*** e0ne has joined #openstack-sdks09:35
*** gouthamr_ has quit IRC09:51
*** Yanyanhu has quit IRC09:52
*** lhcheng has joined #openstack-sdks09:53
openstackgerritMerged openstack/python-openstackclient: Subnet Pool: Add "subnet pool delete" command  https://review.openstack.org/27955009:58
*** lhcheng has quit IRC09:58
*** openstackgerrit has quit IRC10:02
*** salv-orl_ has joined #openstack-sdks10:03
*** openstackgerrit has joined #openstack-sdks10:03
*** salv-orlando has quit IRC10:06
*** lhcheng has joined #openstack-sdks10:14
*** sdague has joined #openstack-sdks10:48
*** cdent has joined #openstack-sdks10:52
*** dims has joined #openstack-sdks10:59
*** tobe has joined #openstack-sdks11:11
*** lhcheng has quit IRC11:20
*** fzdarsky has joined #openstack-sdks11:20
*** dims_ has joined #openstack-sdks11:30
*** dims has quit IRC11:31
*** cdent_ has joined #openstack-sdks11:42
*** cdent has quit IRC11:46
*** cdent_ is now known as cdent11:46
*** Qiming has joined #openstack-sdks11:56
*** fzdarsky has quit IRC11:57
*** salv-orl_ has quit IRC12:03
*** erlon has joined #openstack-sdks12:11
*** rtheis has joined #openstack-sdks12:18
*** salv-orlando has joined #openstack-sdks12:26
openstackgerritabregman proposed openstack/os-client-config: Fix formulation  https://review.openstack.org/28180612:30
*** e0ne has quit IRC13:13
*** e0ne has joined #openstack-sdks13:14
*** lucasagomes is now known as lucas-hungry13:22
*** Qiming has quit IRC13:30
*** Qiming has joined #openstack-sdks13:32
openstackgerritTom Cocozzello proposed openstack/python-openstackclient: TypeError when user show user_id and specifiying the domain  https://review.openstack.org/28152413:32
*** Qiming has quit IRC13:32
*** Qiming has joined #openstack-sdks13:34
*** petertr7_away is now known as petertr714:04
*** britthou_ has joined #openstack-sdks14:17
*** britthouser has quit IRC14:19
*** lucas-hungry is now known as lucasagomes14:28
*** gouthamr has joined #openstack-sdks14:30
openstackgerritRichard Theis proposed openstack/python-openstackclient: Refactor security group list to use SDK  https://review.openstack.org/27848114:31
*** fzdarsky has joined #openstack-sdks14:37
openstackgerritChaozhe Chen(ccz) proposed openstack/python-openstackclient: Remove unused test-requirments  https://review.openstack.org/28189514:53
*** tobe has quit IRC14:57
*** fzdarsky_ has joined #openstack-sdks15:02
*** amotoki has joined #openstack-sdks15:05
*** sigmavirus24_awa is now known as sigmavirus2415:05
*** britthouser has joined #openstack-sdks15:12
*** britthou_ has quit IRC15:12
openstackgerritRichard Theis proposed openstack/python-openstacksdk: WIP: Basic resource.prop for ID attributes (message)  https://review.openstack.org/28190315:17
*** RuiChen has quit IRC15:36
*** RuiChen has joined #openstack-sdks15:37
*** woodster_ has joined #openstack-sdks15:39
*** tobe has joined #openstack-sdks15:40
*** fzdarsky_ has quit IRC15:43
*** fzdarsky has quit IRC15:43
*** Qiming has quit IRC15:49
*** fzdarsky has joined #openstack-sdks15:50
*** fzdarsky_ has joined #openstack-sdks15:50
*** fzdarsky has quit IRC15:56
*** fzdarsky_ has quit IRC15:56
*** krotscheck_dcm is now known as krotscheck16:00
*** salv-orl_ has joined #openstack-sdks16:03
*** zigo has quit IRC16:03
*** zigo has joined #openstack-sdks16:05
*** salv-orlando has quit IRC16:06
*** fzdarsky_ has joined #openstack-sdks16:07
*** fzdarsky has joined #openstack-sdks16:07
*** fzdarsky has quit IRC16:24
*** fzdarsky_ has quit IRC16:24
*** fzdarsky has joined #openstack-sdks16:40
*** fzdarsky_ has joined #openstack-sdks16:41
*** fzdarsky_ has quit IRC16:41
*** fzdarsky__ has joined #openstack-sdks16:41
*** fzdarsky__ has quit IRC16:41
*** fzdarsky_ has joined #openstack-sdks16:42
*** dims has joined #openstack-sdks16:50
*** dims_ has quit IRC16:51
*** jaypipes has quit IRC16:54
*** e0ne has quit IRC16:59
*** jose4183 has joined #openstack-sdks17:02
*** jose4183 has quit IRC17:02
*** jose4183 has joined #openstack-sdks17:03
*** jaypipes has joined #openstack-sdks17:08
*** dencaval has quit IRC17:12
*** tobe has quit IRC17:13
openstackgerritRichard Theis proposed openstack/python-openstacksdk: Basic resource.prop for ID attributes (message)  https://review.openstack.org/28190317:26
*** krotscheck is now known as krotscheck_dr17:27
openstackgerritBrandon Palm proposed openstack/python-openstackclient: Fixed command list  https://review.openstack.org/28150117:52
*** lhcheng has joined #openstack-sdks18:02
*** e0ne has joined #openstack-sdks18:07
openstackgerritJas Singh proposed openstack/python-openstackclient: Add port list command  https://review.openstack.org/27637118:14
openstackgerritJas Singh proposed openstack/python-openstackclient: Add 'port create' command  https://review.openstack.org/27367018:14
*** e0ne has quit IRC18:16
*** e0ne has joined #openstack-sdks18:30
*** petertr7 is now known as petertr7_away18:34
*** fzdarsky has quit IRC18:50
*** fzdarsky_ has quit IRC18:51
*** fzdarsky has joined #openstack-sdks19:01
*** fzdarsky_ has joined #openstack-sdks19:02
*** annegentle has joined #openstack-sdks19:12
*** fzdarsky_ has quit IRC19:15
*** fzdarsky has quit IRC19:16
*** d0ugal has quit IRC19:29
*** d0ugal has joined #openstack-sdks19:30
*** d0ugal has quit IRC19:30
*** d0ugal has joined #openstack-sdks19:30
openstackgerritJas Singh proposed openstack/python-openstackclient: Add 'port create' command  https://review.openstack.org/27367019:42
*** lucasagomes is now known as lucas-dinner19:54
*** annegentle has quit IRC19:59
openstackgerritJas Singh proposed openstack/python-openstackclient: Add 'port create' command  https://review.openstack.org/27367020:07
*** annegentle has joined #openstack-sdks20:07
*** _RuiChen has joined #openstack-sdks20:07
*** markvoelker_ has joined #openstack-sdks20:07
*** petertr7z has joined #openstack-sdks20:09
*** petertr7z is now known as petertr720:09
*** petertr7_away has quit IRC20:12
*** markvoelker has quit IRC20:12
*** bnemec has quit IRC20:12
*** RuiChen has quit IRC20:12
*** stevemar has quit IRC20:12
*** stevemar has joined #openstack-sdks20:13
*** bnemec has joined #openstack-sdks20:13
*** boris-42 has quit IRC20:16
*** boris-42 has joined #openstack-sdks20:18
*** boris-42 has quit IRC20:24
*** cdent has quit IRC20:28
*** annegentle has quit IRC20:29
openstackgerritJas Singh proposed openstack/python-openstackclient: Add 'port create' command  https://review.openstack.org/27367020:29
*** annegentle has joined #openstack-sdks20:29
openstackgerritAnne Gentle proposed openstack/fairy-slipper: Handle other status codes  https://review.openstack.org/27857120:29
*** annegentle has quit IRC20:30
*** cdent has joined #openstack-sdks20:36
*** samueldmq has joined #openstack-sdks20:40
stevemarany api-wg folks around? sdague etoews?20:44
sdaguecdent is a good one as well20:44
*** htruta has joined #openstack-sdks20:44
stevemarsdague: true!20:44
cdentwhats up?20:44
samueldmqstevemar: may I explain ?20:44
stevemarsamueldmq: sure, less typing for me20:45
*** e0ne has quit IRC20:45
samueldmqcdent: sdague: so, updating projects in keystone are expressed as PATCH calls20:45
samueldmqfor example, PATCH /project/{id}, which seems fine20:45
*** e0ne has joined #openstack-sdks20:45
samueldmqhowever, we want to support an update that goes further, and actually updates the project itself and its subtree (in hierarcical projects context)20:46
samueldmqso that's an update (disabling them, for example) in more than one entity20:46
samueldmqso PATCH doesn't seem appropriate, as I was discussing with sdague20:46
*** e0ne has quit IRC20:46
samueldmqa POST should be used instead, as it is used for modify the server state somehow20:47
samueldmqI wanted to get more views on this ...20:47
cdentsamueldmq: It really depends on what the resource at /project/{id} means or represents20:47
cdentcan you say "this is a project which has a subtree"?20:48
stevemarcdent: yep20:48
sdaguecdent: is some background https://github.com/openstack/keystone-specs/blob/master/api/v3/identity-api-v3.rst#update-project20:48
cdentthanks20:48
* cdent reads20:48
sdaguebut are subtree resources defined as a resource hierarchy?20:48
samueldmqsdague: thanks , forgot to mention that20:48
stevemarcdent: sdague maybe it'll help with the decision, there will also be a call to delete an entire subtree20:48
samueldmqstevemar: ++20:49
sdaguewhat does the GET of /project/{id} look like if it has a "subtree"20:49
samueldmqsdague: the same as returned by UPDATE20:49
htrutasamueldmq, sdague: correct me if I'm wrong, but the POST to bulk update would be used if we wanted to specify all the entities that would be updated. Right?20:49
samueldmqsdague: but accepts query aprams such as ?subtree_as_list20:50
samueldmqsdague: which would include then the subtree in the response20:50
sdaguesamueldmq: all I see is parent_id20:50
sdagueI don't see any child relations20:50
stevemarsdague: i think they are only returned if you specify a query param20:50
samueldmqsdague: yes, but if you do /projects/{id}?subtree_as_list it will include a list of subprojects20:51
samueldmqstevemar: ++20:51
htrutastevemar: ++20:51
sdagueand what does that look like?20:51
cdentsamueldmq: what are the operations that would be performed on the subtree? Is there anything else besides removing something from the subtree?20:51
samueldmqsdague: ctrl+f 'GET /projects/{project_id}?subtree_as_list' in that doc20:52
htrutacdent: only disabling or enabling the subtree20:52
samueldmqcdent: disabling all the subtree and deleting it20:52
htrutacdent: and other call to delete20:52
cdentso disabling sort of detaches the subtree from the parent but it continues to exist, whereas delete is a proper removal (if I seem a bit roundabout about this, I'm just trying to get a feel for the context)20:53
samueldmqcdent: it doesnt' dettach, all projects go to disabled state20:54
samueldmqso a scoped token can't be generated to them20:54
samueldmqcdent: they become unusable20:54
stevemarso, in my mind, we keep POST open in case we want to do a bulk/cascade crete, use the PATCH to do a cascade update20:57
cdentI would think that it would be fine to use PATCH if you can come up with a representation of the PATCH body that adequately reflects the change in state that you are doing20:58
cdent(that's what PATCH is after all)20:58
cdentso something like `"subtree": []`20:59
cdentWhat you don't want to do is the cascade thing that's been done elsewhere20:59
cdentcascade looks like it is being used as a verb not a noun20:59
stevemaryes, it is20:59
stevemarcdent: so you don't like /projects/{id}/cascade21:00
cdentresource design before representation design before method choice21:00
cdentmethod choice falls out natural if you've got the first two okay21:00
cdentI'm not certain I understand cascade but I'm pretty sure I don't like it21:00
cdentBecause if you have a url that "/projects/{project_id}/cascade" then that means that is a thing21:01
cdentbut that's not a thing the thing is "/projects/{project_id}"21:01
cdentyou could DELETE "/projects/{project_id}?cascade=true"21:01
cdentbut I can see how that would be awkward21:01
*** samueldmq1 has joined #openstack-sdks21:02
samueldmqcdent: yes so PATCH URLs can be GET'ed right ?21:02
samueldmqcdent: that's another argument sdague proposed POST21:02
cdentif you can PATCH it you ought to be able to GET it21:02
sdague /cascade would be kind of like an action, which I know you don't like as well21:03
cdentsdague: there's an argument to be made that both /projects/id/cascade and /projects/id?cascade=True are specific resources, but in practice query parameters then to mean "modifiers of the resource in the path"21:04
sdagueI also try to shy everyone away from PATCH because it's not actually in HTTP 1.1, so not all client libs support it21:04
stevemarcdent: remember we need a delete function to go along with the update :\21:05
cdentstevemar: if you're thinking in terms of functions then you're on the wrong foot ;)21:05
cdentwe want to delete resource X21:05
stevemarcdent: probably, i don't like creating APIs :(21:05
cdentI know how that can be21:06
cdentHave we gotten anywhere, or just made the problem worse by creating more questions?21:07
*** samueldmq1 has quit IRC21:07
htrutacdent: not sure. I haven't even thought on having the POST for update. My only concern was ?cascade or /cascade. So, we have another question21:08
cdentIf there's some change in progress and you want to add me to the review I'm happy to look if that will be of any use21:08
samueldmqhtruta: yes, first things first :)21:08
samueldmqwe need to decide whether POST or PATCH, then / or ?21:08
samueldmqcdent: https://review.openstack.org/#/c/243585/21:08
*** dstanek has quit IRC21:09
stevemarPOST seems like it should be reserved for creating new resources, we're not doing that, i don't see how it's an option at all?21:09
cdentPOST is also the fallback for "I can't get anything else to fit"21:10
*** dstanek has joined #openstack-sdks21:10
samueldmqPOST is also used to modify the server state somehow, so yes basically what cdent jsut said21:10
cdentPATCH or PUT to /project/{id} seems right, PUT only if you are doing a replace of some kind21:10
stevemarwhich i don't think we're doing21:11
htrutacdent: we need a body, I think we need a PATCH21:11
stevemari'm OK with PATCH /projects/{id}?cascade=True ...21:11
cdentsamueldmq: everything but GET and HEAD modify the server state...21:11
sdaguecdent: so you don't have concerns about library support for PATCH?21:11
cdentsdague: I'm not sure how to answer that. I guess the short answer is no.21:12
sdagueok21:12
cdentIn any case, PATCH is already present in the existing api isn't it? As in that bridge has been crossed?21:13
samueldmqcdent: yes it is21:13
htrutacdent: it is21:13
stevemaryeah, we have a bunch of PATCH calls all over the place21:13
samueldmqcdent: if we go with PATCH, would it make more sense to21:13
stevemarand i think we're not alone there21:13
samueldmqi) PATCH /projs/id/cascade21:13
samueldmqor21:13
samueldmqii) PATCH /projs/id?cascade21:13
stevemar2!21:14
cdentIf possible I'd choose iii) PATCH /projs/id with something in the body that signals the cascade, not by verb but a change in the representation21:14
cdentbut if that's not possible ii is better than i21:15
stevemarhehe http://williamdurand.fr/2014/02/14/please-do-not-patch-like-an-idiot/21:16
stevemarNo! PATCH is not about sending an updated value, rather than the entire resource21:17
stevemarthis guy would hate keystone's APIs21:17
cdentsigh, I disagree with that attitude to PATCH. I think somebody misunderstands "description of changes"21:18
cdentthat op, path, value stuff is heinous and painful21:18
stevemaryeah, it's not obvious :(21:19
stevemarit also implies you know a lot of other IDs21:19
stevemarsamueldmq: PATCH /projects/123?cascade=True works for me21:20
cdentI have to admit I'm still fairly confused about what cascade actually means21:21
cdentand why it needs to be in the url instead of the representation21:21
htrutacdent: cascade means: propagate it to my subtree.21:21
htrutacdent: update/delete me and my whole subtree21:21
cdentif you want to "cascade" to the subtree, why not include (some of) the subtree in the representation of the patch?21:22
samueldmqcdent: so you create a project21:22
samueldmqcdent: and subproject under it, setting the first as tehir parent21:22
samueldmqcdent: it's about hierarchical organization of projects21:22
samueldmqcdent: cascade mean that operation will apply on the parent AND on the projects that are structurally organized under it in the hierarhcy21:23
samueldmqcdent: we only have been putting the attributes to be updated in the body request21:26
samueldmqchanging that might be confusing ?21:26
* cdent is looking at the test code21:27
samueldmqcdent: sure21:27
sdaguecdent: because while there is a resource tree in the data model, it is exposed as a flat resource set with cross refs in their API21:29
cdentso: declaring cascade is effectively an optimization to avoid doing something like:21:29
sdaguethe real REST model would be GET /projects/{id}/projects21:29
cdent{project: {enabled: False, subtree: [{id: x, enabled: False},{id: y, enabled: False}]}} or some such, yeah?21:30
cdentsdague: I'd guess /projects/{id}/subtree21:31
htrutacdent: exactly21:31
htrutaeither that, or do a lot of simple PATCH calls21:31
sdaguecdent: well /projects/{id}/projects/{id}/projects/{id}21:31
cdentsdague: heh, yeah21:32
sdagueat which point DELETE /projects/{id}/projects/{id}21:32
sdaguewould be really clear21:32
cdenthtruta: if the caller already knows all the sub-projects, my inclination would be to avoid the optimization and be explicit21:32
sdaguebecause if it's really  /projects/{id1}/projects/{id2}/projects/{id3}21:32
sdaguewhat happens in keystone today if you try to DELETE /projects/{id2}21:33
sdaguebut {id3} is still a thing21:33
htrutasdague: you can't21:33
htrutacdent: but we would fall on the same UX problem that we have today. Deleting a subtree is very painful21:34
htrutasdague: you need to disable and delete id3, and then disable and delete id221:34
cdenthtruta: is deleting really the only use case that matters?21:35
htrutacdent: both of them, matter, actually. Because we need to disable before deleting21:35
cdentI mean in terms of cascading21:35
cdentokay21:35
* cdent thinks21:36
* cdent shrugs21:37
cdentI think ?cascade in some for is  a reasonble compromise. We can beat on forever about purity21:37
cdents/for/form/21:38
*** e0ne has joined #openstack-sdks21:38
cdentdefinitely prefer ?cascade to /cascade21:38
htrutacdent: I'd also prefer it, because /cascade gives the idea that cascade is an attribute of project, or even another entity21:39
samueldmqcdent: htruta: subtree is an attribute of a project21:41
samueldmqwhat about /projects/{id}/subtree then passing the body as {'enabled':False}21:42
samueldmqany better ?21:42
samueldmqI am okay with PATCH /projects/{id}?cascade too21:42
cdentsamueldmq: the implication there is that only the subtree is disabled, not the top too21:42
samueldmqcdent: yes, that would require two calls21:42
samueldmqcdent: sdague: stevemar: htruta: let's stick with PATCH ?cascade then, seems reasonable ?21:43
htrutasamueldmq: subtree is not an attribute either.21:43
samueldmqhtruta: it is21:43
samueldmqbecause it's returned from a GET call in the entity21:43
htrutasamueldmq: ?cascade is the best approach for me ++21:44
samueldmqhtruta: GET /projects/{id}?subtree_as_list returns 'subtree' as an attribute of project21:44
*** gildub has joined #openstack-sdks21:48
*** chlong has quit IRC21:57
*** chlong_ has joined #openstack-sdks21:58
*** cdent has quit IRC21:58
*** salv-orlando has joined #openstack-sdks22:03
*** salv-orl_ has quit IRC22:05
*** rtheis has quit IRC22:05
*** petertr7 is now known as petertr7_away22:07
*** thrash is now known as thrash|g0ne22:35
openstackgerritBrad Behle proposed openstack/python-openstackclient: Add "os subnet show" command using SDK  https://review.openstack.org/27649522:40
*** lucas-dinner has quit IRC22:47
openstackgerritBrad Behle proposed openstack/python-openstackclient: Add "os subnet show" command using SDK  https://review.openstack.org/27649522:47
*** lucasagomes has joined #openstack-sdks22:53
*** gildub has quit IRC22:59
*** e0ne has quit IRC23:06
*** gouthamr has quit IRC23:14
*** jamielennox is now known as jamielennox|away23:20
*** tobe has joined #openstack-sdks23:28
*** Qiming has joined #openstack-sdks23:33
*** tobe has quit IRC23:35
*** dims_ has joined #openstack-sdks23:36
*** dims has quit IRC23:38
*** openstackgerrit has quit IRC23:47
*** openstackgerrit_ is now known as openstackgerrit23:47
*** openstackgerrit_ has joined #openstack-sdks23:48
*** openstackgerrit_ is now known as openstackgerrit23:48
*** openstackgerrit_ has joined #openstack-sdks23:49
*** tobe has joined #openstack-sdks23:49
*** gildub has joined #openstack-sdks23:50
*** chlong_ has quit IRC23:52
*** sigmavirus24 is now known as sigmavirus24_awa23:53
*** openstackgerrit_ has quit IRC23:55
*** openstackgerrit_ has joined #openstack-sdks23:57

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