*** mjturek has quit IRC | 00:03 | |
*** slaweq has joined #openstack-meeting-4 | 00:11 | |
*** slaweq has quit IRC | 00:15 | |
*** seajay has joined #openstack-meeting-4 | 00:18 | |
*** seajay has quit IRC | 00:35 | |
*** iyamahat has quit IRC | 01:19 | |
*** yamahata has quit IRC | 01:19 | |
*** hongbin has joined #openstack-meeting-4 | 01:19 | |
*** liuyulong has joined #openstack-meeting-4 | 01:32 | |
*** iyamahat has joined #openstack-meeting-4 | 01:44 | |
*** diablo_rojo has quit IRC | 02:33 | |
*** liuyulong has quit IRC | 02:48 | |
*** psachin has joined #openstack-meeting-4 | 02:48 | |
*** markvoelker has joined #openstack-meeting-4 | 02:50 | |
*** slaweq has joined #openstack-meeting-4 | 03:11 | |
*** slaweq has quit IRC | 03:15 | |
*** dave-mccowan has quit IRC | 03:46 | |
*** hongbin has quit IRC | 03:47 | |
*** haleyb has quit IRC | 04:07 | |
*** dave-mccowan has joined #openstack-meeting-4 | 04:49 | |
*** macza has joined #openstack-meeting-4 | 05:03 | |
*** macza has quit IRC | 05:08 | |
*** slaweq has joined #openstack-meeting-4 | 05:11 | |
*** slaweq has quit IRC | 05:15 | |
*** mtreinish has quit IRC | 05:37 | |
*** mtreinish has joined #openstack-meeting-4 | 05:38 | |
*** bnemec has quit IRC | 05:39 | |
*** mtreinish has quit IRC | 05:56 | |
*** mtreinish has joined #openstack-meeting-4 | 05:59 | |
*** slaweq has joined #openstack-meeting-4 | 06:11 | |
*** njohnston has quit IRC | 06:14 | |
*** slaweq has quit IRC | 06:15 | |
*** njohnston has joined #openstack-meeting-4 | 06:15 | |
*** slaweq has joined #openstack-meeting-4 | 06:23 | |
*** pcaruana has joined #openstack-meeting-4 | 06:33 | |
*** diablo_rojo has joined #openstack-meeting-4 | 06:55 | |
*** Luzi has joined #openstack-meeting-4 | 07:06 | |
*** diablo_rojo has quit IRC | 07:27 | |
*** celebdor has joined #openstack-meeting-4 | 07:32 | |
*** gkadam has joined #openstack-meeting-4 | 07:36 | |
*** e0ne has joined #openstack-meeting-4 | 08:12 | |
*** lkoranda has quit IRC | 08:12 | |
*** iyamahat has quit IRC | 08:19 | |
*** alexchadin has joined #openstack-meeting-4 | 08:21 | |
*** janki has joined #openstack-meeting-4 | 08:27 | |
*** gkadam is now known as gkadam-afk | 08:52 | |
*** gkadam-afk is now known as gkadam | 08:59 | |
*** janki has quit IRC | 09:13 | |
*** salmankhan has joined #openstack-meeting-4 | 09:16 | |
*** pbourke has quit IRC | 09:24 | |
*** pbourke has joined #openstack-meeting-4 | 09:24 | |
*** alexchadin has quit IRC | 09:42 | |
*** yamamoto has quit IRC | 10:17 | |
*** yamamoto has joined #openstack-meeting-4 | 10:25 | |
*** yamamoto has quit IRC | 10:46 | |
*** yamamoto has joined #openstack-meeting-4 | 10:48 | |
*** yamamoto has quit IRC | 10:49 | |
*** macza has joined #openstack-meeting-4 | 11:11 | |
*** macza has quit IRC | 11:15 | |
*** alexchadin has joined #openstack-meeting-4 | 11:22 | |
*** yamamoto has joined #openstack-meeting-4 | 11:23 | |
*** pcaruana has quit IRC | 11:50 | |
*** salmankhan has quit IRC | 12:08 | |
*** seajay has joined #openstack-meeting-4 | 12:08 | |
*** e0ne has quit IRC | 12:09 | |
*** e0ne has joined #openstack-meeting-4 | 12:09 | |
*** yamamoto has quit IRC | 12:14 | |
*** yamamoto has joined #openstack-meeting-4 | 12:16 | |
*** pcaruana has joined #openstack-meeting-4 | 12:39 | |
*** alexchadin has quit IRC | 12:43 | |
*** bobh has joined #openstack-meeting-4 | 12:59 | |
*** haleyb has joined #openstack-meeting-4 | 13:04 | |
*** liuyulong has joined #openstack-meeting-4 | 13:15 | |
*** njohnston has quit IRC | 13:15 | |
*** njohnston has joined #openstack-meeting-4 | 13:16 | |
*** bnemec has joined #openstack-meeting-4 | 13:18 | |
*** mjturek has joined #openstack-meeting-4 | 13:20 | |
*** e0ne has quit IRC | 13:22 | |
*** rosmaita has joined #openstack-meeting-4 | 13:23 | |
*** rosmaita has left #openstack-meeting-4 | 13:25 | |
*** rosmaita has joined #openstack-meeting-4 | 13:26 | |
*** e0ne has joined #openstack-meeting-4 | 13:26 | |
*** yamamoto has quit IRC | 13:31 | |
*** yamamoto has joined #openstack-meeting-4 | 13:31 | |
*** abhishekk has joined #openstack-meeting-4 | 13:32 | |
*** psachin has quit IRC | 13:36 | |
*** iyamahat has joined #openstack-meeting-4 | 13:36 | |
*** salmankhan has joined #openstack-meeting-4 | 13:45 | |
*** mhen has joined #openstack-meeting-4 | 13:51 | |
jokke_ | #startmeeting glance | 14:00 |
---|---|---|
openstack | Meeting started Thu Sep 27 14:00:01 2018 UTC and is due to finish in 60 minutes. The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
*** openstack changes topic to " (Meeting topic: glance)" | 14:00 | |
openstack | The meeting name has been set to 'glance' | 14:00 |
jokke_ | #topic roll-call | 14:00 |
*** openstack changes topic to "roll-call (Meeting topic: glance)" | 14:00 | |
jokke_ | o/ | 14:00 |
Luzi | o/ | 14:00 |
mhen | o/ | 14:01 |
rosmaita | o/ | 14:01 |
abhishekk | o/ | 14:03 |
jokke_ | #topic updates | 14:03 |
*** openstack changes topic to "updates (Meeting topic: glance)" | 14:03 | |
*** JamesBenson has joined #openstack-meeting-4 | 14:03 | |
jokke_ | First of all the periodic jobs: there was keystone tips failure, will need to keep eye on that and if it keeps failing see what is breaking it. Others are green | 14:05 |
jokke_ | Based on the PTG we have quite a bit calmer cycle feature wise coming but reminder that the spec proposals will stay open until after Berlin Summit | 14:06 |
*** LiangFang has joined #openstack-meeting-4 | 14:07 | |
jokke_ | I have yet to update the store driver maintainer page so will try to get that done by tomorrow eob | 14:07 |
abhishekk | ack | 14:08 |
jokke_ | I think that's pretty much it from quick updates from me | 14:08 |
jokke_ | I did merge bunch of the zuul stuff that was sent in scripted | 14:09 |
jokke_ | so if you think there was something that got messed up in the job definitions have a look and blame me :) | 14:10 |
LiangFang | ack | 14:11 |
jokke_ | #topic patch call to to replace locations | 14:11 |
*** openstack changes topic to "patch call to to replace locations (Meeting topic: glance)" | 14:11 | |
jokke_ | so we're back to imcdonns favorite child | 14:12 |
jokke_ | which is also on my still to do list for this week. So I will have mail going to the ops list before next week checking if anyone else is using that API | 14:12 |
abhishekk | ok | 14:13 |
rosmaita | i don't see any reason why it makes sense for add /0 to have different behavior from replace {} | 14:13 |
jokke_ | But in short, so there is couple of mistakes in Iain's statements to the dev mailing list | 14:14 |
jokke_ | first, that after replacing the empty list there is nothing one can do to get the image out of queued, that's not trye, all the mechanisms that works before the replace call is made will still work after | 14:15 |
jokke_ | so one doesn't just need to delete the image record | 14:15 |
rosmaita | jokke_: what's the workaround? | 14:15 |
jokke_ | rosmaita: so like it has always been patch call to add location does the status change, as does image upload and image import | 14:17 |
rosmaita | but i mean in the situation where you just did the replace and are now in queued, what would you do? | 14:18 |
jokke_ | and this is where me and Iain disagree ... I did agree on his initial statement that it's a bug that if you use the locations API there is _no_ way to activate the image as he stated when he came to us | 14:18 |
rosmaita | ok, so the workaround is to add /0 in the first place | 14:18 |
jokke_ | rosmaita: you do add and then you either delete or replace to get to single source of truth | 14:19 |
jokke_ | rosmaita: no, that's the orginal idea how that API should work | 14:19 |
jokke_ | you don't replace unless you're actually in need to replace something :) | 14:19 |
jokke_ | I just thing no-one thought that one would want to start by replace and just built the whole final locations list by hand | 14:20 |
rosmaita | sort of ... but it is legitimate to replace an empty list with a populated list | 14:20 |
rosmaita | anyway, i didn't realize there was the workaround | 14:21 |
rosmaita | (though i still think the replace situation is a bug!) | 14:21 |
rosmaita | but the existence of a workaround does change the backport situation, i think | 14:22 |
jokke_ | so my biggest problem with this is that we changed iirc deprecated API that has been stable for years based on bug that was filed on assumption "There is no way to do this at all" | 14:22 |
rosmaita | well, i think a key thing is that we want consistent behavior in the api, and add /0 and replace {} should behave the same, i think | 14:24 |
jokke_ | and yes if I was designing that API from scratch I definitely would take this use case in consideration and make sure the API behaves well, now the problem is really the API stability contract | 14:24 |
rosmaita | i guess the key thing at this point is that we need a clear direction for how we will handle this. i understand both your and ian's frustration, but i personally don't know how to resolve this | 14:26 |
*** smcginnis has joined #openstack-meeting-4 | 14:26 | |
jokke_ | but I'm kind of willing to let this slip in if there is no outcry us breaking someone else's process by us changing this. Is it valid bug for backporting within our stable rules, I don't think so but we can ask the rest of the stable folks after we make sure it's ok to keep in master | 14:27 |
smcginnis | Sorry, I'm on the road and missed it. What's the stable change? | 14:28 |
jokke_ | that is kind of where I'm at now | 14:28 |
jokke_ | smcginnis: we're talking about the patch call replace locations to make image active | 14:28 |
smcginnis | Ah, OK. Thanks! | 14:29 |
*** iyamahat has quit IRC | 14:30 | |
*** yamamoto has quit IRC | 14:32 | |
jokke_ | And just that ye all are on the same page, I have no intention to make a rush call on this. We kind of need to make the call if we're reverting the patch on master by milestone 1 as at that point it will be in tagged release but what comes to backporting it into Rocky and perhaps before, I need to know that we're not on war path with everyone else to make one user able to use their preferred ap | 14:33 |
jokke_ | i call instead of the one that just works | 14:33 |
*** yamamoto has joined #openstack-meeting-4 | 14:33 | |
*** yamamoto has quit IRC | 14:33 | |
*** yamamoto has joined #openstack-meeting-4 | 14:34 | |
*** abhishekk has quit IRC | 14:34 | |
jokke_ | IMO we have been in enough wars for changing our stable APIs before ;) | 14:34 |
*** abhishekk has joined #openstack-meeting-4 | 14:34 | |
rosmaita | speaking of which ... i take it you didn't like my proposal to make 'private' the default visibility? | 14:35 |
jokke_ | rosmaita: actually we did ... IIRC that was what was originally agreed and the feedback has been it would make lots of users happier | 14:36 |
rosmaita | oh wow, that's good to hear -- i may pick that up | 14:37 |
rosmaita | i have like a 3 day window to do some glance work | 14:37 |
jokke_ | :) | 14:37 |
jokke_ | ok, if nothing else on this lets move on | 14:37 |
abhishekk | great, then please review my patches | 14:38 |
*** yamamoto has quit IRC | 14:38 | |
rosmaita | one thing | 14:38 |
jokke_ | shoot | 14:38 |
rosmaita | https://etherpad.openstack.org/p/glance-imacdonn-relnote | 14:38 |
rosmaita | this was the description of the relnote for the replace change i wrote up | 14:38 |
jokke_ | #link https://etherpad.openstack.org/p/glance-imacdonn-relnote | 14:38 |
rosmaita | i think it may be slightly inaccurate | 14:38 |
rosmaita | anyway, just pointing it out in case it will be helpful to advance the discussion | 14:39 |
smcginnis | That looks good to me. | 14:39 |
jokke_ | yeah, that's based on the original assumption that there is no way, in which case this change would have made sense | 14:40 |
rosmaita | also, i speak of "adding" instead of "replace" | 14:40 |
jokke_ | yup | 14:40 |
abhishekk | +1 | 14:40 |
rosmaita | which is sort of the same thing, but inaccurate in this context | 14:40 |
jokke_ | and the add already does behave like the reno proposal claims to change it to | 14:41 |
jokke_ | ;) | 14:41 |
rosmaita | i must admit, i misunderstood the situation | 14:41 |
jokke_ | so did I initially | 14:41 |
jokke_ | that's why I was like "Yes that does sound like nasty bug" | 14:42 |
rosmaita | ok, in one sense we don't want to rush, but on the other, we do need to get it out of master pronto if we don't want to make this change | 14:42 |
rosmaita | all i did was verify the bug, didn't think of trying a workaround | 14:42 |
jokke_ | and then I started to look the code and wen't "WWaait!" and the discussion was left there when I went to PTO and meanwhile the change was merged ;) | 14:42 |
*** yamamoto has joined #openstack-meeting-4 | 14:43 | |
jokke_ | rosmaita: like said I'm willing to let this slip if there is no outcry of us changing it from the API folks and operators. Because it does make sense in logical way | 14:44 |
rosmaita | ++ | 14:44 |
jokke_ | if it breaks anyone, I rather revert it and tell Iain "Sorry but you need to use the api call that already does it for you" | 14:44 |
jokke_ | ok lets move on before we run out of time | 14:45 |
jokke_ | #topic image encryption proposal | 14:45 |
*** openstack changes topic to "image encryption proposal (Meeting topic: glance)" | 14:45 | |
mhen | hello all :) | 14:45 |
Luzi | hi :) | 14:45 |
jokke_ | hey! | 14:45 |
mhen | we'd like to propose the introduction of an encrypted image format in OpenStack | 14:45 |
mhen | we have written a spec for it and have a basic implementation ready which we'd like to contribute | 14:45 |
mhen | based on the code alone Glance would be the least affected project (mostly Nova, Cinder and OSC are involved) | 14:46 |
jokke_ | could you link the spec for us, please? | 14:46 |
mhen | but we figured you are responsible for the image concept in OpenStack anyhow | 14:46 |
mhen | so since the old cross-project contribution workflow is outdated, we're currently wondering where the best place to put the spec would be, actually | 14:46 |
jokke_ | oh, Ok | 14:46 |
mhen | any suggestions? | 14:47 |
jokke_ | so that's a good question. I'd say you likely need to write 4 specs to all involved projects describing what you are trying solve and how it affects that project | 14:47 |
jokke_ | and I don't mean 4 specs to each repo | 14:48 |
jokke_ | but a spec to those 4 projects you need to change to make this happen | 14:48 |
rosmaita | mhen: quick question, you mean a new value for the disk_format or container_format properties? | 14:48 |
mhen | rosmaita, exactly, 'container_format' specifically | 14:48 |
rosmaita | mhen: i wonder whether a new property would be better | 14:49 |
smcginnis | Thinking from the Cinder side - I would expect the changes to not be too disruptive. So I think if you came to Cinder with changes saying they are for "the new encryption format from Glance" that we can probably just have a blueprint, not a full spec. | 14:49 |
rosmaita | othewise, you might have encrypted_gzip, encrypted_raw, etc | 14:49 |
smcginnis | I guess it really depends on the extent of the changes needed. | 14:49 |
Luzi | jokke_ but wouldn't it be better, if people from all involved project could discuss this in one repo? | 14:50 |
smcginnis | I woud start with describing your goal with a ML post. | 14:50 |
smcginnis | That woud be the best forum for cross-project discussion. | 14:50 |
jokke_ | Luzi: yes I do agree, but like mhen said the cross project specs were sacked :( | 14:50 |
jokke_ | what smcginnis just said, yes! | 14:51 |
mhen | so we could use appropriate excerpts of the spec and post in on the ML? | 14:51 |
mhen | *it | 14:51 |
rosmaita | mhen: yes, that would be the best way to get started | 14:51 |
mhen | that sounds reasonable, thanks for the suggestion! | 14:51 |
jokke_ | mhen: just quick question as if you just were thinking of new container_format where are you planning to store the secrets? | 14:52 |
smcginnis | I think so. Expain your use case(s), describe the changes you plan to make, and get input from affected projects. And have the opportunity for other interested parties to get involved too. | 14:52 |
mhen | jokke_, key manager (e.g. Barbican) for now | 14:52 |
*** yamamoto has quit IRC | 14:52 | |
mhen | we have other mechanisms in the work but they are currently not ready for contribution | 14:52 |
jokke_ | mhen: ok, in that case you would likely want to have reserved property where to store that in glance as well | 14:53 |
mhen | jokke_, that's what our implementation currently does basically | 14:53 |
rosmaita | mhen: have you looked at how we handle the digital signatures? | 14:53 |
mhen | we did, yes | 14:53 |
rosmaita | ok, cool | 14:53 |
jokke_ | one thing we have learned is that as glance has freeform properties for images, users really hates everyone using them as they wish ;) | 14:54 |
mhen | we contributed image signature generation for OSC recently | 14:54 |
rosmaita | nice | 14:54 |
jokke_ | cool. Then I think the easiest for you guys get on this is like smcginnis proposed ML thread, get everyone on board and after that to file the specs or blueprints to affected projects | 14:55 |
mhen | regarding the ML thing: iirc, there's a new combined ML coming up. It's still fine to post on the current openstack-dev? | 14:56 |
jokke_ | for something like this we will want spec to glance-specs repo. It's even more for ducumenting the future change and book keeping than us just wanting to fight the design | 14:56 |
smcginnis | Yes, no changes have been made yet, so posting to openstack-dev would be best. | 14:56 |
* rosmaita has completely missed the discussion about a new ML | 14:56 | |
* jokke_ too | 14:57 | |
smcginnis | rosmaita: You've been busy. ;) | 14:57 |
mhen | jokke_, we figured as much, that's why we came here first :) | 14:57 |
jokke_ | mhen: gr8 | 14:57 |
mhen | ok, then we will do as you advised and post on the ML soon | 14:58 |
jokke_ | mhen: just that you know. The image encryption has been discussed quite a bit and everyone has been kind of going away at the point when we have told them it's not Glance's job to encrypt those images but we're more than happy to keep track of it. By the looks of it you guys are taking the right approach ;) | 14:58 |
mhen | I see. I can confirm that most code changes have to happen elsewhere, like I initally stated ;) | 14:59 |
jokke_ | ;) | 14:59 |
jokke_ | I look forward for the ML post | 14:59 |
jokke_ | anything else you need from us now? | 15:00 |
mhen | nope that would be sufficient for now, thanks for the talk! | 15:00 |
*** hamzy_ has quit IRC | 15:00 | |
jokke_ | well if so, we're out of time so lets continue if needed and Open discussion in #openstack-glance | 15:00 |
jokke_ | thanks all! | 15:00 |
jokke_ | #endmeeting | 15:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:01 | |
openstack | Meeting ended Thu Sep 27 15:00:58 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-09-27-14.00.html | 15:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-09-27-14.00.txt | 15:01 |
*** abhishekk has quit IRC | 15:01 | |
openstack | Log: http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-09-27-14.00.log.html | 15:01 |
*** smcginnis has left #openstack-meeting-4 | 15:03 | |
*** Luzi has quit IRC | 15:13 | |
*** LiangFang has quit IRC | 15:14 | |
*** spiette_ is now known as spiette | 15:21 | |
*** dave-mccowan has quit IRC | 15:23 | |
*** mjturek has quit IRC | 15:24 | |
*** hamzy_ has joined #openstack-meeting-4 | 15:26 | |
*** yamamoto has joined #openstack-meeting-4 | 15:28 | |
*** hamzy has joined #openstack-meeting-4 | 15:29 | |
*** hamzy_ has quit IRC | 15:30 | |
*** mjturek has joined #openstack-meeting-4 | 15:33 | |
*** dave-mccowan has joined #openstack-meeting-4 | 15:42 | |
*** macza has joined #openstack-meeting-4 | 15:47 | |
*** e0ne has quit IRC | 15:51 | |
*** rosmaita has left #openstack-meeting-4 | 15:59 | |
*** mjturek has quit IRC | 15:59 | |
*** liuyulong has quit IRC | 16:00 | |
*** yamamoto has quit IRC | 16:02 | |
*** dave-mccowan has quit IRC | 16:08 | |
*** diablo_rojo has joined #openstack-meeting-4 | 16:17 | |
*** bobh has quit IRC | 16:37 | |
*** bobh has joined #openstack-meeting-4 | 16:42 | |
*** e0ne has joined #openstack-meeting-4 | 16:52 | |
*** e0ne has quit IRC | 16:54 | |
*** diablo_rojo has quit IRC | 17:05 | |
*** salmankhan has quit IRC | 17:06 | |
*** e0ne has joined #openstack-meeting-4 | 17:16 | |
*** mjturek has joined #openstack-meeting-4 | 17:16 | |
*** gkadam has quit IRC | 17:20 | |
*** iyamahat has joined #openstack-meeting-4 | 17:21 | |
*** hamzy_ has joined #openstack-meeting-4 | 17:31 | |
*** hamzy has quit IRC | 17:32 | |
*** hamzy_ has quit IRC | 17:35 | |
*** hamzy has joined #openstack-meeting-4 | 17:35 | |
*** hamzy has quit IRC | 17:37 | |
*** iyamahat_ has joined #openstack-meeting-4 | 17:38 | |
*** iyamahat has quit IRC | 17:39 | |
*** diablo_rojo has joined #openstack-meeting-4 | 17:56 | |
*** yamamoto has joined #openstack-meeting-4 | 18:00 | |
*** iyamahat_ has quit IRC | 18:02 | |
*** iyamahat has joined #openstack-meeting-4 | 18:05 | |
*** dims_ is now known as dims | 18:05 | |
*** bobh has quit IRC | 18:12 | |
*** mjturek has quit IRC | 18:31 | |
*** salmankhan has joined #openstack-meeting-4 | 18:37 | |
*** salmankhan has quit IRC | 18:41 | |
*** bobh has joined #openstack-meeting-4 | 18:45 | |
*** hongbin has joined #openstack-meeting-4 | 18:47 | |
*** mjturek has joined #openstack-meeting-4 | 18:52 | |
*** iyamahat has quit IRC | 18:56 | |
*** yamamoto has quit IRC | 19:01 | |
*** iyamahat has joined #openstack-meeting-4 | 19:05 | |
*** mjturek has quit IRC | 19:11 | |
*** mjturek has joined #openstack-meeting-4 | 19:13 | |
*** iyamahat has quit IRC | 19:27 | |
*** bobh has quit IRC | 19:30 | |
*** bobh has joined #openstack-meeting-4 | 19:30 | |
*** hamzy has joined #openstack-meeting-4 | 19:38 | |
*** e0ne has quit IRC | 19:42 | |
*** hamzy has quit IRC | 19:44 | |
*** e0ne has joined #openstack-meeting-4 | 19:47 | |
*** e0ne has quit IRC | 19:50 | |
*** pcaruana has quit IRC | 19:54 | |
*** bobh has quit IRC | 20:01 | |
*** iyamahat has joined #openstack-meeting-4 | 20:02 | |
*** e0ne has joined #openstack-meeting-4 | 20:08 | |
*** diablo_rojo has quit IRC | 20:08 | |
*** hamzy has joined #openstack-meeting-4 | 20:09 | |
*** diablo_rojo has joined #openstack-meeting-4 | 20:11 | |
*** mjturek has quit IRC | 20:11 | |
*** hamzy has quit IRC | 20:20 | |
*** hamzy has joined #openstack-meeting-4 | 20:20 | |
*** hamzy has quit IRC | 20:25 | |
*** mjturek has joined #openstack-meeting-4 | 20:26 | |
*** diablo_rojo has quit IRC | 20:26 | |
*** hamzy has joined #openstack-meeting-4 | 20:28 | |
*** mjturek has quit IRC | 20:29 | |
*** macza has quit IRC | 20:31 | |
*** macza has joined #openstack-meeting-4 | 20:32 | |
*** hamzy has quit IRC | 20:34 | |
*** hamzy has joined #openstack-meeting-4 | 20:34 | |
*** mjturek has joined #openstack-meeting-4 | 20:43 | |
*** hamzy has quit IRC | 20:43 | |
*** mjturek has quit IRC | 20:58 | |
*** yamamoto has joined #openstack-meeting-4 | 20:59 | |
*** mjturek has joined #openstack-meeting-4 | 21:00 | |
*** mjturek has quit IRC | 21:02 | |
*** e0ne has quit IRC | 21:14 | |
*** bobh has joined #openstack-meeting-4 | 21:18 | |
*** bobh has quit IRC | 21:18 | |
*** yamamoto has quit IRC | 21:48 | |
*** diablo_rojo has joined #openstack-meeting-4 | 21:57 | |
*** seajay has quit IRC | 22:00 | |
*** macza has quit IRC | 22:38 | |
*** macza has joined #openstack-meeting-4 | 22:38 | |
*** macza has quit IRC | 22:51 | |
*** macza_ has joined #openstack-meeting-4 | 22:51 | |
*** iyamahat has quit IRC | 22:59 | |
*** celebdor has quit IRC | 23:10 | |
*** macza_ has quit IRC | 23:18 | |
*** iyamahat has joined #openstack-meeting-4 | 23:19 | |
*** hongbin has quit IRC | 23:26 | |
*** bobh has joined #openstack-meeting-4 | 23:28 | |
*** iyamahat has quit IRC | 23:38 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!