Thursday, 2020-09-24

*** yasufum has joined #openstack-meeting00:22
*** gyee has quit IRC00:27
*** rbudden has joined #openstack-meeting00:45
*** ociuhandu has joined #openstack-meeting00:46
*** mlavalle has quit IRC00:50
*** ociuhandu has quit IRC00:50
*** mlavalle has joined #openstack-meeting00:51
*** jmasud has quit IRC01:11
*** Liang__ has joined #openstack-meeting01:24
*** Liang__ has quit IRC02:26
*** Liang__ has joined #openstack-meeting02:27
*** jmasud has joined #openstack-meeting02:30
*** rcernin has quit IRC02:38
*** rcernin has joined #openstack-meeting02:42
*** jmasud has quit IRC02:46
*** andrebeltrami has quit IRC03:12
*** psachin has joined #openstack-meeting03:26
*** jmasud has joined #openstack-meeting03:30
*** jmasud has quit IRC03:43
*** jmasud has joined #openstack-meeting03:56
*** jmasud has quit IRC03:59
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-meeting04:33
*** rbudden has quit IRC04:39
*** rbudden has joined #openstack-meeting04:39
*** rbudden has joined #openstack-meeting04:40
*** rbudden has joined #openstack-meeting04:41
*** rbudden has joined #openstack-meeting04:42
*** rbudden has joined #openstack-meeting04:43
*** rbudden has joined #openstack-meeting04:44
*** psachin has quit IRC04:45
*** apetrich has joined #openstack-meeting04:57
*** jmasud has joined #openstack-meeting05:27
*** lpetrut has joined #openstack-meeting06:10
*** slaweq has joined #openstack-meeting06:11
*** slaweq has quit IRC06:29
*** vishalmanchanda has joined #openstack-meeting06:30
*** slaweq has joined #openstack-meeting06:32
*** ralonsoh has joined #openstack-meeting06:36
*** dklyle has quit IRC06:48
*** belmoreira has joined #openstack-meeting06:54
*** baojg has quit IRC07:29
*** baojg has joined #openstack-meeting07:30
*** apetrich has quit IRC07:48
*** tosky has joined #openstack-meeting08:04
*** e0ne has joined #openstack-meeting08:17
*** moguimar has joined #openstack-meeting08:19
*** ralonsoh has quit IRC08:23
*** yamamoto has quit IRC08:23
*** ralonsoh has joined #openstack-meeting08:24
*** yamamoto has joined #openstack-meeting08:25
*** yamamoto has quit IRC08:25
*** rcernin has quit IRC08:35
*** yamamoto has joined #openstack-meeting08:39
*** rcernin has joined #openstack-meeting08:41
*** rcernin has quit IRC08:57
*** yamamoto has quit IRC08:58
*** baojg has quit IRC09:04
*** Lucas_Gray has joined #openstack-meeting09:20
*** mbuil has quit IRC09:25
*** ociuhandu has joined #openstack-meeting09:29
*** yamamoto has joined #openstack-meeting09:31
*** yamamoto has quit IRC09:36
*** baojg has joined #openstack-meeting09:41
*** Lucas_Gray has quit IRC09:56
*** mbuil has joined #openstack-meeting10:02
*** Liang__ has quit IRC10:04
*** baojg has quit IRC10:22
*** baojg has joined #openstack-meeting10:23
*** yamamoto has joined #openstack-meeting10:24
*** yamamoto has quit IRC10:26
*** rcernin has joined #openstack-meeting10:35
*** yamamoto has joined #openstack-meeting10:42
*** yamamoto has quit IRC10:51
*** rcernin has quit IRC10:56
*** yamamoto has joined #openstack-meeting11:29
*** yamamoto has quit IRC11:40
*** apetrich has joined #openstack-meeting11:50
*** priteau has joined #openstack-meeting12:00
*** adrianc has quit IRC12:06
*** yamamoto has joined #openstack-meeting12:06
*** adrianc has joined #openstack-meeting12:11
*** masahito has joined #openstack-meeting12:26
*** yamamoto has quit IRC12:48
*** rfolco has joined #openstack-meeting12:49
*** yamamoto has joined #openstack-meeting12:54
*** rfolco is now known as rfolco|ruck12:54
*** masahito has quit IRC12:58
*** priteau has quit IRC13:02
*** yamamoto has quit IRC13:03
*** eharney has joined #openstack-meeting13:06
*** tdasilva has quit IRC13:15
*** tdasilva has joined #openstack-meeting13:17
*** yasufum has quit IRC13:20
*** baojg has quit IRC13:21
*** priteau has joined #openstack-meeting13:21
*** priteau has quit IRC13:33
*** yamamoto has joined #openstack-meeting13:36
*** rcernin has joined #openstack-meeting13:36
*** yamamoto has quit IRC13:45
*** TrevorV has joined #openstack-meeting13:46
*** rcernin has quit IRC13:51
*** andrebeltrami has joined #openstack-meeting13:56
*** rosmaita has joined #openstack-meeting13:57
abhishekk#startmeeting glance14:01
openstackMeeting started Thu Sep 24 14:01:10 2020 UTC and is due to finish in 60 minutes.  The chair is abhishekk. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: glance)"14:01
openstackThe meeting name has been set to 'glance'14:01
abhishekk#topic roll call14:01
*** openstack changes topic to "roll call (Meeting topic: glance)"14:01
abhishekkwaiting couple of minutes for others to join14:02
abhishekkdansmith, looks like again only two of us :D14:03
abhishekkrosmaita, might be busy with cinder release14:03
dansmiththat's too bad,14:03
rosmaitasorry, am not paying attention14:03
dansmithbecause I wanted to discuss openstack client, like we should have before we merged that patch >:(14:03
rosmaitaif jokke were here, he would say openstack client is dead to us14:04
abhishekkwe can14:04
*** Steap has joined #openstack-meeting14:04
dansmithrosmaita: I'm aware :/14:04
abhishekklets proceed14:04
rosmaitawell, somebody had to say it14:04
Steapdang, I was in #openstack-unregistered :-(14:05
abhishekk#topic Updates14:05
*** openstack changes topic to "Updates (Meeting topic: glance)"14:05
abhishekkPTL nominations are open now14:05
abhishekkI have filed nomination for W cycle14:05
abhishekkAnyone interested can also file the nomination14:05
rosmaitaabhishekk: you have my vote!14:06
abhishekkrosmaita, thank you14:06
rosmaitathanks for stepping up14:06
abhishekkthanks for your support14:06
abhishekkmoving ahead14:07
abhishekk#topic release/periodic jobs update14:07
*** openstack changes topic to "release/periodic jobs update (Meeting topic: glance)"14:07
abhishekkglance rc1 released today14:07
abhishekk\o/ we managed to get targeted patches in time14:07
abhishekkthank you to all new contributors and reviewers14:07
abhishekkRC1 will be final release candidate for Victoria, unless we found any critical issue14:08
abhishekk#topic Periodic jobs - Couple of timeouts for functional-py36 jobs, I will analyze the logs14:08
*** openstack changes topic to "Periodic jobs - Couple of timeouts for functional-py36 jobs, I will analyze the logs (Meeting topic: glance)"14:08
abhishekkPeriodic jobs - Couple of timeouts for functional-py36 jobs14:09
abhishekkothers are green14:09
abhishekk#topic Next week meeting14:09
*** openstack changes topic to "Next week meeting (Meeting topic: glance)"14:09
abhishekkI am taking a week off, so can we cancel next week's meeting or either of you are interested to chair the meeting14:10
abhishekkack, I think its better to cancel the next weeks meeting, I will sent mail on ML to notify the same14:11
abhishekkMoving into open discussion14:11
abhishekk#topic Open discussion14:11
*** openstack changes topic to "Open discussion (Meeting topic: glance)"14:12
abhishekkthis reminds me to ping fungi for symlinks in specs (for moving specs from approved to implemented directory)14:13
*** hemna has quit IRC14:13
abhishekkdansmith, regarding your concern about OSC14:14
abhishekkIt was decided by all the cores to not use osc in glance as it was not fully supported14:14
dansmithshall I start talking or are you about to say something?14:15
abhishekkyou can put your concern14:15
dansmithI understand that was done at some point, but I'd like to know when that was, and what the gaps were at the time, as well as what gaps need to be filled before glance is willing to be less than overtly hostile towards it14:16
dansmithglance doesn't have to "support" OSC at all necessarily,14:16
abhishekkI guess it was decided two cycles back14:17
dansmithalthough I think that a purely-infra piece of code (those playbooks are basically an extension of devstack and d-g) is a perfect place to use it and even to get a little test coverage for some basic parts of it14:17
rosmaitaa key thing we need to do is to remove the deprecated tenant_is_owner option14:17
rosmaitabecause OSC assumes that that is True14:17
dansmithrosmaita: I don't know what that means, or what the impact is14:18
rosmaitadansmith: give me a min to find you some info14:18
dansmithrosmaita: but I can tell you that it doesn't prevent successful use of osc for listing and showing images, as that code was doing :)14:18
rosmaitaactually, it can affect a lot of stuff14:19
rosmaitajust look at any of the image sharing docs and see how complicated they are14:19
jokkedansmith: so bit background for the OSC decision. We moved to endorse it back in the time when that was community goal (first time) even with all the gaps and issues the image part of it had. We raised those issues and told the community that we'll keep python-glanceclient around as long as needed for closing those gaps and getting the osc image parts to the state they should be14:20
*** baojg has joined #openstack-meeting14:21
jokkeWe changed all our docs etc. and kept doing our new development on python-glanceclient. Couple of years, in every PTG and Summit we discussed about those very same issues and gaps in OSC and every time we were told they're been fixed. And 6 months later we had exactly the same discussion14:21
jokkeso couple of cycles ago, we pulled the plug and let the comunity know that we will recosider after OSC gets their client to good state and keeps feature parity to the API at least couple of cycles so we know it's actually maintained and not just one off effort to get us swap again14:22
dansmithrosmaita: am I still waiting for a link or pointer?14:22
*** hemna has joined #openstack-meeting14:23
dansmithjokke: so we move from "it kinda works but there are some gaps" to "we are going to ignore this until someone tells us it is 100% working"?14:23
dansmithjokke: I don't understand why using it in infra-only code, which doesn't even get packaged in the distribution is anything other than free test coverage14:24
dansmithI understand the desire not to encourage people to use it, to use glanceclient in glance docs, etc14:25
jokkedansmith: we moved from "we're promoting broken client which has some things working to give it endorsement" to "We support the client we have control over and works"14:25
dansmithI don't see how that relates to using it in infra-only code14:25
abhishekkunfortunately that's true, since couple of years we don't have bandwidth to work other things than glance due to shortage of contributors14:25
dansmithjokke: and that pertains to infra-only code, how? neither promotion, nor support are implied in that use14:25
*** rbudden has joined #openstack-meeting14:25
dansmithabhishekk: but you've got a new contributor here, which wrote infra code for missing test functionality, using the community-standard client, and it was working fine,14:26
dansmithabhishekk: and then you took time out for writing and reviewing a rewrite of that14:27
dansmithrosmaita: thanks, will review14:27
fungiabhishekk: sorry, stepped away but yes, please do get up with me to revisit your .htaccess redirects14:27
abhishekkfungi, ack, thank you14:28
dansmithabhishekk: that kind of approach doesn't really encourage new contributors to help, and probably relates to an approach that doesn't encourage other people in the community to help fix osc stuff in glance :/14:28
jokkedansmith: so why should we use osc in there and expect people who might need to review those infra used bits to dig in how something works in osc? If infra wants to use osc only, they can host those files in their repos and maintain them. I just don't see reason nor benefit having OSC used in Images API facing stuff if we're not supporting it14:28
rosmaitadansmith: the implications of that setting are explained here:
dansmithjokke: no, these files are not hostable anywhere else14:29
dansmithjokke: you're kinda implying that you will _never_ support it, because clearly support is never going to come in the form of 100% completion.. we already do image manipulation in devstack with osc, and if it were to break, ya'll would have to fix it all the same14:30
fungiplease also don't think that "infra" (tact sig and/or opendev collaboratory sysadmins) cares whether you use glanceclient or openstacksdk/openstackclient in your tests14:30
dansmithcovering a couple more cases here (really it's just image-show, so come on) gets you a little more baseline coverage at least14:30
dansmithfungi: i'm lumping infra and qa together a bit here, which was fine until YOU showed up :P14:31
fungiheh ;)14:31
fungifine, i can be the whipping post14:31
fungii personally care, but that's only my opinion14:31
jokkedansmith: I think my biggest thing here is our little experiment with uwsgi ... that's actually very great example. We told strongly to everyone that it's not working, we don't have time nor expertese to figure it out, don't use it. And people went with "Oh it's used in infra for testing so it must be the right thing to do" I really don't want to send that message again14:32
fungias a user of glance in many public clouds, i use openstackclient and openstacksdk to upload, list and delete images in them14:32
dansmithanyway, I know I'm not a *real* core here, but I'd just like to say that I don't think the "don't use OSC in docs" resolution should apply to something like this, and it would have been a lot cooler if we could have had a discussion about it before just steamrolling over it14:32
fungibecause i don't want to have to run a separate tool or library to interact with each api in openstack14:32
dansmithespecially since you guys are trying to attract and retain reviewers and contributors14:33
dansmithjokke: right, but you might recall, it actually works fine for all those people who were using it :)14:33
dansmithas does osc for glance, as fungi just mentioned14:33
fungii will readily admit i am not an advanced user of glance's features, but what i do with it probably represents what 90% of glance users need14:34
dansmithand for those 90%, there is a substantial benefit in having a unified client, with repeatable behaviors and patterns14:35
fungii don't use it for cloud administration, i don't run any production openstack clouds14:35
abhishekkthat was the story until import and multiple stores support is added14:35
dansmithwhich is the thing most people hate the most about openstack, both in the community, and OUR customers14:35
*** ralonsoh has quit IRC14:35
dansmithabhishekk: no, remember, lots of people are totally fine without using import and some outright disable is14:35
abhishekkI guess import support is added recently and not sure it is supporting all import methods14:35
dansmithabhishekk: so I still assert that the 90% (or greater) case applies14:35
dansmithabhishekk: we could quickly test it in that same post playbook for things like web-download you know14:36'd mean adding osc back into it :)14:36
*** ralonsoh has joined #openstack-meeting14:37
*** dklyle has joined #openstack-meeting14:37
fungiwith my clueless user hat on, i'm not sure what benefit "image import" represents to me. i just have this image i want to upload. it would of course be nice if all openstack providers supported most popular image types and converted them. some are doing that opaquely with tasks, and some have also asked not to rely on that because it brings their cloud to its knees when you do it a lot14:37
jokkedansmith: fungi: the 90% also applies to the help requests we got over here from people. "Could someone help me I tried to do openstack image <X Y Z> and it's failing" and our first response was "Could you try with glance image-<X> <Y Z>" and reply we got back was "Hey thanks it works!"14:37
jokkethat was big contributor to that frustration14:38
dansmithjokke: it's super easy to say "reproduce it with glanceclient and then I'll help you"14:38
fungiis that 90% of your users, or 10% of your users? ;)14:38
jokkefungi: I mean 90% of people that came to ask help on this channel14:38
dansmithfungi: as a user, the only benefit (IMHO) is being able to provide a web url so glance fetches the image from there instead of you uploading14:39
dansmithfungi: that could (of course) be implemented without import too, but that's how people can do it14:39
dansmithfungi: otherwise import is just extra pain for users14:39
fungidansmith: got it. yeah i guess if i was super bandwidth constrained and wanted to use images someone else was publishing, that would be helpful14:40
jokkedansmith: fungi: also automatic conversion, comression handling + anything the cloud op wants/needs to do upon image creation, like metadata injection.14:40
dansmithjokke: he said *users*14:40
jokkefor glance user, it's still just one client call, but instead of figuring out what properties you need to set on that specific cloud and what format the image needs to be to work. you can just end the image on it's way and if it becomes active you should expect it to work14:41
fungiwell, as a user i want to be able to use the image i've uploaded, so glance's import process doing the things the provider wants for me to be able to do that in their environment is part of it (the client is merely triggering the call to perform the import if i understand)14:41
fungibut i guess this is veering into the uwsgi problem discussion, not the osc/sdk discussion14:42
jokkefungi: actually no, the osc got import support very recently14:42
dansmithfungi: right, because osc supports this :)14:42
dansmithand the reason osc supports this,14:43
jokkethis was one of those big feature gaps why we finally pulled the plug14:43
dansmithis because in order to test this in devstack, we needed to do an import, and contributors jumped up to write the osc support so that we could do all those things, without having to add glanceclient usage back into devstack, which uses osc for basically everything14:43
*** Lucas_Gray has joined #openstack-meeting14:44
dansmithif we had just told those people to eff off, or even worse, gave up and just never tested it, then we wouldn't have that support14:44
abhishekkfungi, dansmith to be frank, we faced lots of issues with osc, didn't have enough contributors or neither got any support from osc guys even after following up for couple of PTG14:45
dansmithabhishekk: all of your tests are set up with osc now, which means you can either (a) deal with things as they arise or (b) just remove tests when those things break14:46
dansmith(a) helps your users, (b) does not14:46
dansmith(a) means less likely that people will show up with osc problems you have to solve (but can punt on) (b) hurts glanceclient users as well as osc users14:46
*** baojg has quit IRC14:46
fungiwith my user hat on, the only real concern is that the docs don't indicate that the things i want to do are possible with osc/sdk and that i don't actually need to install a separate client. as someone who happens to know that it already does all the things i personally need, i'm mostly happy to just go on ignoring the glance user docs14:47
*** baojg has joined #openstack-meeting14:47
jokkedansmith: don't get me wrong, I was very concerned when you jumped into looking that uwsgi stuff as I was expecting us to need spend loads of time on that based on the previous experience. I'm super happy that you did as it moved lots of thing in very good direction in general14:48
fungiif glance made changes which caused it to stop working to that degree with osc, or osc made changes which caused it to stop working with glance, due to lack of testing, then that would also concern me as a user14:48
dansmithfungi: that's kinda my point about not barring use of osc in upstream-only test playbooks.. we get a little early-mover advantage test coverage for basic things, without waiting for something dumb like "image show doesn't work anymore" to end up in a user's lap, which costs way more time to diagnose and fix14:50
dansmithjokke: the same goes here.. we have good evidence that lots of people use osc with glance all the time, as they did glance and uwsgi. taking the absolutist approach that we will not allow any use of it doesn't change the reality of what people are doing, and is also far more extreme of a stance than we really need14:51
dansmithrefuse to help people with osc bugs all you want, but we needn't be client extremists, IMHO14:51
jokkefungi: yeah, the osc path did not start well to begin with as we were told to not bother "OSC will do things it's way and the glance community input is not required nor desired" then lots of companies downscaled their contributions and all that was left just hanging but the two communities never collaborated about any of those aspects as we were struggling to keep afloat at that point and I think14:52
jokkeOSC folks just never got to it as basic create/delete/list worked "just fine"14:52
dansmithjokke: do you know that osc now uses the python clients to do its actual work?14:53
dansmithmeaning, osc does (or will/should) use glanceclient to actually talk to glance, as it does with nova, et al14:53
fungibut also the nodepool in opendev is using openstacksdk to upload something like 10 different images to a dozen different providers on various openstack releases with at least several different format requirements every day14:53
jokkedansmith: honestly no, I have no idea about the details of osc current state14:54
abhishekkI didn't know that14:54
fungithe current high-level interface in openstacksdk is actually inherited from code which used to be a part of nodepool14:54
fungibecause we needed something which could present a consistent experience across a bunch of inconsistent clouds with their own quirks and requirements14:55
abhishekklast 5 minutes,14:55
fungiwithout the user needing to know each cloud's quirks14:55
fungibut yes, the osc migration to openstacksdk isn't complete yet, so lots of service clients get called into where the sdk lacks coverage14:57
jokkefungi: yeah, I think the drive behind the interop/trademark groups or what ever they were called that started this whole image-import journey were very noble and unfortunately that traction was something that got lost on all these downscales. Wouldn't it be great i you could have just send couple of API requests style: "Here is the metadata _we_ need and the payload, do what you must" and get14:57
jokkeworking image in that specific cloud out of it :P14:57
jokkeUnstead of needing to do that in all the arious clients that might want to interface with said clouds14:58
abhishekklast minute14:59
fungiit wasn't so much interop/trademark pushing that as it was our ci system's needs to be able to create nodes in lots of different clouds ;)14:59
fungithe interop effort merely benefited from it14:59
abhishekkAs I stated, we will be happy to support OSC back once we ensure that it has support to all new features15:00
*** lpetrut has quit IRC15:00
jokkefungi: no I mean the interop push finished would have solved ot for you without needing special client for that ;)15:00
fungioh, yep15:00
abhishekkI will find out the gap and will bring it during PTG or after next weeks discussion15:00
jokkeThanks all! Good conversation. We ran out of time15:00
* fungi goes back to using osc to upload some new debian images to his accounts15:01
abhishekkwe can continue in openstack-glance15:01
abhishekkthank you all15:01
*** openstack changes topic to "OpenStack Meetings ||"15:01
openstackMeeting ended Thu Sep 24 15:01:30 2020 UTC.  Information about MeetBot at . (v 0.1.4)15:01
openstackMinutes (text):
gagehugo#startmeeting security15:01
openstackMeeting started Thu Sep 24 15:01:44 2020 UTC and is due to finish in 60 minutes.  The chair is gagehugo. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: security)"15:01
openstackThe meeting name has been set to 'security'15:01
gagehugo#link agenda15:02
*** rosmaita has left #openstack-meeting15:02
gagehugoNo agenda today, so open discussion15:05
gagehugo#topic open discussion15:05
*** openstack changes topic to "open discussion (Meeting topic: security)"15:05
*** lpetrut has joined #openstack-meeting15:07
*** openstack changes topic to "OpenStack Meetings ||"15:08
openstackMeeting ended Thu Sep 24 15:08:03 2020 UTC.  Information about MeetBot at . (v 0.1.4)15:08
openstackMinutes (text):
*** Lucas_Gray has quit IRC15:11
*** tdasilva_ has joined #openstack-meeting15:12
*** Lucas_Gray has joined #openstack-meeting15:12
*** tdasilva has quit IRC15:14
*** moguimar has quit IRC15:16
*** belmoreira has quit IRC15:24
*** yasufum has joined #openstack-meeting15:35
*** yamamoto has joined #openstack-meeting15:43
*** baojg has quit IRC15:45
*** e0ne has quit IRC15:50
*** yamamoto has quit IRC15:50
*** _mlavalle_1 has joined #openstack-meeting15:54
*** _mlavalle_1 has quit IRC15:54
*** mlavalle has quit IRC15:57
*** gyee has joined #openstack-meeting15:59
*** priteau has joined #openstack-meeting15:59
*** belmoreira has joined #openstack-meeting16:07
*** Lucas_Gray has quit IRC16:14
*** belmoreira has quit IRC16:15
*** mlavalle has joined #openstack-meeting16:15
*** ralonsoh has quit IRC16:22
*** armstrong has joined #openstack-meeting16:22
*** hemna has quit IRC16:25
*** hemna has joined #openstack-meeting16:25
*** yasufum has quit IRC16:26
*** Lucas_Gray has joined #openstack-meeting16:46
*** Lucas_Gray has quit IRC16:56
*** lpetrut has quit IRC17:06
*** ociuhandu has quit IRC17:07
*** lpetrut has joined #openstack-meeting17:09
*** hemna has quit IRC17:10
*** hemna has joined #openstack-meeting17:19
*** baojg has joined #openstack-meeting17:32
*** jamesmcarthur has joined #openstack-meeting17:48
*** yasufum has joined #openstack-meeting18:10
*** yasufum has quit IRC18:13
*** jamesmcarthur has quit IRC18:21
*** tosky has quit IRC18:22
*** jamesmcarthur has joined #openstack-meeting18:23
*** jamesmcarthur has quit IRC18:31
*** jamesmcarthur has joined #openstack-meeting18:38
*** priteau has quit IRC18:58
*** bbowen has quit IRC19:05
*** jamesmcarthur has quit IRC19:21
*** jamesmcarthur has joined #openstack-meeting19:23
*** armstrong has quit IRC19:31
*** TrevorV has quit IRC19:35
*** yamamoto has joined #openstack-meeting19:48
*** yamamoto has quit IRC19:52
*** rfolco|ruck is now known as rfolco|ruck|brb19:53
*** jamesmcarthur has quit IRC20:13
*** jamesmcarthur has joined #openstack-meeting20:14
*** bbowen has joined #openstack-meeting20:21
*** Lucas_Gray has joined #openstack-meeting20:24
*** rfolco|ruck|brb has quit IRC20:36
*** rfolco|ruck|brb has joined #openstack-meeting20:37
*** rfolco|ruck|brb is now known as rfolco|ruck20:37
*** slaweq has quit IRC21:06
*** rfolco|ruck has quit IRC21:11
*** whoami-rajat__ has quit IRC21:19
*** jamesmcarthur has quit IRC21:24
*** apetrich has quit IRC21:28
*** lpetrut has quit IRC21:30
*** jamesmcarthur has joined #openstack-meeting21:41
*** raildo has quit IRC21:42
*** jamesmcarthur has quit IRC21:42
*** jamesmcarthur_ has joined #openstack-meeting21:42
*** yamamoto has joined #openstack-meeting21:49
*** baojg has quit IRC21:53
*** yamamoto has quit IRC21:53
*** baojg has joined #openstack-meeting21:54
*** baojg has quit IRC21:58
*** baojg has joined #openstack-meeting21:59
*** yamamoto has joined #openstack-meeting22:13
*** vishalmanchanda has quit IRC22:39
*** jamesmcarthur has joined #openstack-meeting22:41
*** rbudden has quit IRC22:43
*** jamesmcarthur_ has quit IRC22:45
*** rcernin has joined #openstack-meeting22:58
*** mlavalle has quit IRC23:02
*** rcernin has quit IRC23:14
*** rcernin has joined #openstack-meeting23:14
*** thgcorrea has quit IRC23:32
*** andrebeltrami has quit IRC23:45
*** yasufum has joined #openstack-meeting23:58
*** jamesmcarthur has quit IRC23:59

Generated by 2.17.2 by Marius Gedminas - find it at!