*** annabelleB has quit IRC | 00:32 | |
*** annabelleB has joined #openstack-tc | 00:37 | |
*** annabelleB has quit IRC | 00:51 | |
*** ricolin has joined #openstack-tc | 01:34 | |
*** rosmaita has quit IRC | 03:34 | |
*** e0ne has joined #openstack-tc | 05:31 | |
*** openstackgerrit has quit IRC | 06:07 | |
*** e0ne has quit IRC | 06:19 | |
*** e0ne has joined #openstack-tc | 06:20 | |
*** e0ne has quit IRC | 06:20 | |
*** dklyle has quit IRC | 06:43 | |
*** dklyle has joined #openstack-tc | 06:44 | |
*** lxkong has quit IRC | 07:19 | |
*** tosky has joined #openstack-tc | 07:38 | |
evrardjp | I think at some point we're gonna have to build an "instagram" of office pictures. I heard that's what kids do nowadays. | 07:38 |
---|---|---|
evrardjp | or maybe a new technology already | 07:39 |
*** jpich has joined #openstack-tc | 07:56 | |
*** cdent has joined #openstack-tc | 07:59 | |
*** Bhujay has joined #openstack-tc | 08:37 | |
ttx | Regarding vendor talks masquerading as technical talks... If "we" can so easily see those and the track chairs can't, that probably means "we" should be volunteering a bit more to do track chairing | 08:45 |
ttx | I'll admit that in the rare cases I've been doing it, I focused on tracks that do not have that many vendor content anyway | 08:46 |
*** e0ne has joined #openstack-tc | 08:48 | |
*** dtantsur|afk is now known as dtantsur | 08:49 | |
*** flaper87 has quit IRC | 09:34 | |
*** flaper87 has joined #openstack-tc | 09:36 | |
*** cdent has quit IRC | 10:02 | |
dims | o/ | 10:24 |
*** jaosorior has quit IRC | 10:25 | |
*** jaosorior has joined #openstack-tc | 10:27 | |
evrardjp | ttx: that's true | 10:27 |
evrardjp | you're proposing something something behind that message? | 10:27 |
*** ricolin has quit IRC | 10:29 | |
*** cdent has joined #openstack-tc | 11:15 | |
ttx | evrardjp: yeah, probably paying more attention when the calls for track chairs go out | 11:16 |
*** cdent has quit IRC | 11:23 | |
*** cdent has joined #openstack-tc | 11:49 | |
*** gouthamr has quit IRC | 11:49 | |
*** mriedem has joined #openstack-tc | 12:54 | |
*** rosmaita has joined #openstack-tc | 12:55 | |
fungi | when we had a security track, it attracted a lot of advertising-type proposals (at least the few times i chaired that) | 13:44 |
fungi | i think we did a fairly good job of spotting and rejecting those, or redirecting them to more vendory lightning talk options | 13:44 |
*** Bhujay has quit IRC | 13:47 | |
ttx | Rocky final release process started | 13:53 |
dhellmann | release status and 80's playlists now in #openstack-release | 13:54 |
mnaser | woo | 13:55 |
* dims reading "[OpenStack Foundation] OSF Open Infrastructure Projects" | 14:02 | |
*** dangtrinhnt_x has joined #openstack-tc | 14:04 | |
smcginnis | Good there were no big surprises there. | 14:08 |
* cdent gives smcginnis a cookie and a hug | 14:14 | |
lbragstad | fungi same here - i remember seeing several vendor specific talks in the private cloud track, but they were "usually" flagged | 14:17 |
smcginnis | https://twitter.com/tcarrez/status/1035169339433869314 | 14:22 |
jbryce | nicely done mnaser | 14:23 |
fungi | an ouroboros of sorts | 14:25 |
mnaser | jbryce: thanks :) | 14:25 |
mnaser | wouldn't have been possible with the awesome support of all the teams | 14:26 |
mnaser | just reaching out and asking at the state of their rc's and everyone's so easy and transparent to work with in saying "yeah we're good" or "make sure you have this commit in" | 14:26 |
mnaser | (just another indicator that if you do you work within the community, things get much easier) | 14:26 |
mnaser | and it's all deployed using OSA so the whole stack is pretty much 100% upstream | 14:27 |
jroll | that's awesome \o/ | 14:27 |
lbragstad | damn... | 14:31 |
lbragstad | nice work mnaser | 14:31 |
dims | very cool mnaser | 14:36 |
mnaser | thanks :) | 14:51 |
*** ricolin has joined #openstack-tc | 14:54 | |
*** annabelleB has joined #openstack-tc | 14:58 | |
cdent | tc-members it looks like that time | 15:00 |
* mnaser will be in and out as i have to be in the marketing webinar for rocky | 15:00 | |
* smcginnis still busy wrapping up the rocky release | 15:00 | |
TheJulia | Also about time for the community call that annabelleB is running | 15:00 |
mnaser | i suggest people hop on, even if its called marketing, some great updates from the community/project sides btw | 15:00 |
mnaser | yeah, it's called "marketing" but it very much is community call/update | 15:01 |
lbragstad | mnaser do you happen to have a link handy? | 15:01 |
cdent | https://zoom.us/j/551803657 | 15:01 |
ttx | yes, ICYMI you are not subscribed to the -foundation ML, you should probably still read http://lists.openstack.org/pipermail/foundation/2018-August/002617.html | 15:01 |
mriedem | always fun to see what things we'll get committed to during the marketing all | 15:02 |
mriedem | *call | 15:02 |
annabelleB | mriedem: don’t worry, i only commit you to the work you’ve already completed. everyone wins! | 15:03 |
TheJulia | this is more geared to operate from the project hilights | 15:03 |
mriedem | oh there were things in the queens call that committed us to stuff in rocky that i don't think we got done | 15:03 |
mriedem | but it's ok | 15:03 |
cdent | annabelleB: is it going, my zoom is telling "will begin soon"? | 15:04 |
cdent | magic! | 15:04 |
jbryce | mriedem: which things? | 15:04 |
cdent | it started just as I said that | 15:04 |
mriedem | jbryce: i'll look it up and get back to you | 15:05 |
lbragstad | everyone is muted by default, yeah? | 15:06 |
clarkb | lbragstad: yes, it uses a webinar zoom feature where only "panelists" can speak | 15:06 |
lbragstad | whew | 15:06 |
* dims back in a bit | 15:06 | |
jbryce | mriedem: thanks. we try to base all our materials and statements off the publicly available info + direct info from ptls so want to know if we're getting things wrong | 15:06 |
mriedem | was queens the first for this? i don't see a pike one | 15:07 |
* lbragstad was frantically searching for a mute button | 15:07 | |
jbryce | mriedem: you mean for a community webinar around the release? i think we've done one for almost every release but i don't know where the recordings might go to once the releases move on | 15:09 |
lbragstad | did we just start recording them though? | 15:09 |
smcginnis | Shamail used to do some I remember. It was recorded. | 15:10 |
smcginnis | I remember cringing at myself for at least one of them. | 15:10 |
* TheJulia really does not enjoy public speaking | 15:11 | |
mnaser | lbragstad: you're muted by default :p | 15:11 |
lbragstad | the _best_ default | 15:12 |
mriedem | https://www.openstack.org/marketing/#tab=software | 15:12 |
mriedem | "https://www.openstack.org/marketing/#tab=software" | 15:12 |
mriedem | oops | 15:12 |
mriedem | "With Cyborg, operators can list, identify and discover accelerators, attach and detach accelerators to an instance, and install and uninstall drives. It can be used standalone or in conjunction with Nova or Ironic." | 15:13 |
mriedem | there was no nova/cyborg integration in queens | 15:13 |
mriedem | nor rocky | 15:13 |
* TheJulia was unaware of any ironic integration there... | 15:14 | |
lbragstad | lol - the rocky release was built using a cloud running rocky release candidates, that's awesome | 15:17 |
zaneb | I'm relieved that joining without installing anything didn't work for me, so I can maintain my record of never having attended a webinar | 15:17 |
mriedem | huh, cyborg rest api isn't listed https://developer.openstack.org/api-ref/ | 15:18 |
mriedem | https://docs.openstack.org/cyborg/latest/admin/api.html | 15:19 |
mriedem | not even in their own repo | 15:19 |
smcginnis | mriedem: Do they have an api-ref publishing job? | 15:19 |
TheJulia | re cyborg "Nova or Ironic" should be "Nova and Ironic" as it seems to just understand data it gets from ironic's api. | 15:20 |
mriedem | smcginnis: no idea; i'm currently harassing the PTL internally now | 15:20 |
jroll | I'd assume that cyborg thing really means "this can talk to nova or ironic for a tighter integration" | 15:20 |
TheJulia | I'm uncomfortable with that since they have no ironic client invocation, but *shrug* | 15:21 |
fungi | lbragstad: yep, that's mnaser's newest region in vexxhost | 15:22 |
jroll | I mean, I hope that statement came from the PTL, so I assume it to be relatively correct | 15:22 |
jbryce | i'll dig deeper on what is meant by that cyborg statement and see if there's something to clarify | 15:26 |
TheJulia | I suspect it is just something lost in translation | 15:27 |
*** e0ne has quit IRC | 15:27 | |
TheJulia | did the call end? | 15:27 |
mnaser | i got kicked out | 15:27 |
mnaser | too | 15:27 |
jbryce | nope. eric ernst is talking now | 15:27 |
mnaser | maybe because we were speakers? | 15:27 |
TheJulia | mnaser: that makes sense | 15:27 |
mnaser | i think just like how we got kicked off in the practice run TheJulia i guess | 15:27 |
mnaser | ill hop back on | 15:27 |
clarkb | when I got depromoted my client auto reconnected me early today during testing | 15:27 |
clarkb | but ya it looked like a disconnect | 15:28 |
mnaser | https://zoom.us/j/551803657 | 15:28 |
mnaser | for the easy click | 15:28 |
TheJulia | jbryce: btw, your awesome! | 15:28 |
jbryce | well the projects are awesome...we're just trying to keep up with it all = ) | 15:34 |
mnaser | nice to see the starlingx update | 15:35 |
mnaser | they are very much doing this the right way | 15:36 |
ttx | on the topic of pilot projects and their confirmation process, ICYMI on the -foundation ML, see you should probably still read http://lists.openstack.org/pipermail/foundation/2018-August/002617.html | 15:38 |
ttx | err... I mean you should read | 15:38 |
mnaser | as a word of an advice i'd probably suggest they try to replace the word 'product' by 'project' because that might catch people off guard :) | 15:40 |
cdent | nicely done annabelleB | 15:49 |
mnaser | annabelleB: awesome job :) | 15:49 |
annabelleB | cdent mnaser thank you! new format, but hopefully valuable for folks to get caught up | 15:51 |
smcginnis | annabelleB: Yep, nice work! | 15:51 |
cdent | annabelleB: will there be a text version for "I like to read" types? | 15:52 |
annabelleB | cdent: yes! We’ll get those slides uploaded and shared this afternoon | 15:53 |
*** jpich has quit IRC | 16:10 | |
* ttx knows firsthand how difficult it is to try to make sense of everything that was done during a cycle, so yes, kudos to annabelleB for being on top of it | 16:13 | |
annabelleB | there’s always room for improvement in that process, and I am all ears in Denver if people have ideas on how to capture and verify information. | 16:14 |
mriedem | simply asking the ptls to review the slides for their project before it's presented seems like a good verification | 16:15 |
mriedem | if i would have seen the queens marketing slides beforehand, i would have called out the nova/cyborg integration thing | 16:15 |
*** dangtrinhnt_x has quit IRC | 16:15 | |
mriedem | we control our own project highlights, but don't really know what other projects are saying which might be misleading | 16:15 |
fungi | that would make sense | 16:18 |
annabelleB | mriedem: I hate adding more things to PTL plates during release time, but it sounds like that’s important enough that people would take time to review slides, ya? | 16:18 |
lbragstad | i would review them | 16:18 |
mnaser | annabelleB, mriedem: maybe just say "here's the slides for review, they should be ok but if they're not, that's on you for not checking them" ;) | 16:19 |
annabelleB | this is good feedback | 16:19 |
fungi | ptls as a whole reviewing what ends up at https://releases.openstack.org/rocky/highlights.html might have caught some too? | 16:20 |
lbragstad | i know we get asked to do cycle highlight and propose them for review to the openstack/releases repository, i personally would just review the slides around the same time and make sure they are in sync with each other | 16:20 |
fungi | i guess depending on the degree to which the marketing slides are based on the highlights content | 16:20 |
lbragstad | right - you could parse the highlights to generate a presentation that you slim down later | 16:21 |
annabelleB | fungi: probably 50/50? usually I have things pulled beforehand, and use what people submit in cycle-highlights to verify that I’m not off base | 16:21 |
fungi | reasonable | 16:21 |
mriedem | the marketing slides are pretty sparse, it wouldn't be hard to skim those | 16:21 |
annabelleB | sometimes there’s things hiding that projects don’t necessarily see as a highlight, but a user and or press folks are excited about | 16:21 |
mriedem | heh now that you mention it, https://releases.openstack.org/rocky/highlights.html#neutron-networking-service is wrong | 16:22 |
annabelleB | mriedem: yup, actual time is pretty slim | 16:22 |
mriedem | mlavalle! | 16:22 |
annabelleB | heh, maybe we do need an all-PTL review of the highlights page | 16:23 |
lbragstad | if something is cross-project related i could see that being useful | 16:23 |
smcginnis | Could be useful too just as a way for other projects to be aware of some of the things being done in projects they aren't paying attention to. | 16:24 |
lbragstad | another thing is community goals... for example, keystone missed the mutable config goal for Rocky because we opted to stage it behind a much needed refactor in order to implement it sanely | 16:25 |
lbragstad | we fully expect to implement it in Stein, but i'm wondering if people will be confused if they try to do mutable config stuff with a rocky version of keystone | 16:26 |
smcginnis | We do kind of need a retrospective on cycle goals I think. So far we just kind of put them out there and just expect that things work out. | 16:26 |
lbragstad | i hate not getting goals done, especially when people in other parts of the community are working hard to finish it (but we just ran out of bandwidth) | 16:28 |
lbragstad | but i can see where trying to relay the state for a community goal for each project on a slide is probably less than ideal | 16:28 |
clarkb | lbragstad: I've found writing down what you/we/I did accomplish always makes me feel better about what we didn't do | 16:28 |
clarkb | it is easy to think in the short tmer about what we are failing to do right now but when you look back like once a cycle or once a year it really can be amazing at how much we do accomplish | 16:29 |
lbragstad | true | 16:30 |
clarkb | I know my backlog today is painful, but every time I prep for project updates at the summit or similar I am happy with what we do get done :) | 16:30 |
*** jamesmcarthur has joined #openstack-tc | 16:31 | |
lbragstad | i know there is usually a time slot at the ptg to discuss goals - does anyone know if there is going to be time dedicated to retrospective/review of the process, is that the right venue? | 16:31 |
lbragstad | kinda what smcginnis was saying | 16:31 |
smcginnis | We should at least get it on our TC agenda. | 16:34 |
smcginnis | If not a larger venue/audience. | 16:34 |
lbragstad | i'd like to be a fly on the wall for that | 16:35 |
cdent | lbragstad: don't be a fly on the wall, be a fish in the bowl | 16:36 |
fungi | we've sort of split the goals discussions across ptg and forum | 16:42 |
* dims catches up | 16:43 | |
*** gouthamr has joined #openstack-tc | 16:49 | |
persia | Re: PTG/Forum: my interpretation was that goals at Forum were often multi-cycle-spanning, and goals at PTG tended to be more concrete "what can we do now". | 17:04 |
*** dtantsur is now known as dtantsur|afk | 17:04 | |
ttx | In theory the Forum ran a couple of months ahead of PTG and therefore was the step 0 in the next cycle | 17:04 |
ttx | In practice we just discussed what needed to be discussed | 17:04 |
ttx | but yes, Forum is more gathering input and PTG more around acting on that input | 17:05 |
persia | To some degree, although the differences in attendance at Forum and PTG gave me the impression that operators and vendors were more involved in Forum discussions. | 17:05 |
* fungi wanders off to find lunch while people pick http://lists.openstack.org/pipermail/openstack-dev/2018-August/134046.html apart and start preparing their rotten vegetable projectiles | 17:05 | |
ttx | persia: by design yes | 17:05 |
persia | My assertion is that the design was successful :) | 17:06 |
ttx | fungi: I love it! But then you knew that | 17:06 |
*** diablo_rojo has joined #openstack-tc | 17:06 | |
*** jamesmcarthur has quit IRC | 17:09 | |
*** jamesmcarthur has joined #openstack-tc | 17:10 | |
*** mriedem is now known as mriedem_afk | 17:11 | |
*** annabelleB has quit IRC | 17:13 | |
cdent | this will increase my email debt guilt but lessen my excluding-people guilt so I guess it balances out | 17:14 |
*** jamesmcarthur has quit IRC | 17:24 | |
*** jamesmcarthur has joined #openstack-tc | 17:31 | |
notmyname | I love getting 12 emails from 3 people (to 4 different lists) saying, "I support merging!" ;-) | 17:33 |
*** annabelleB has joined #openstack-tc | 17:34 | |
*** ricolin has quit IRC | 17:41 | |
cdent | notmyname: :0 Wh: msgid.lock\n| formail -D 8192 msgid.cache | 17:45 |
notmyname | cdent: indeed (wat? I'm guessing that's a procmail filter?) | 17:45 |
cdent | yeah. it keeps a cache of every msgid it's seen recently and drops stuff that it has seen before | 17:46 |
notmyname | cool | 17:46 |
notmyname | I use sieve on my mail server. I should look into something similar | 17:46 |
*** jamesmcarthur has quit IRC | 17:51 | |
*** annabelleB has quit IRC | 17:58 | |
*** annabelleB has joined #openstack-tc | 18:06 | |
*** rosmaita has quit IRC | 18:24 | |
*** jamesmcarthur has joined #openstack-tc | 18:30 | |
*** jamesmcarthur has quit IRC | 18:40 | |
*** annabelleB has quit IRC | 18:42 | |
*** jamesmcarthur has joined #openstack-tc | 18:43 | |
*** jamesmcarthur has quit IRC | 18:48 | |
*** annabelleB has joined #openstack-tc | 18:56 | |
*** jamesmcarthur has joined #openstack-tc | 18:59 | |
*** jamesmcarthur has quit IRC | 19:02 | |
*** jamesmcarthur has joined #openstack-tc | 19:02 | |
*** annabelleB has quit IRC | 19:03 | |
*** jamesmcarthur has quit IRC | 19:04 | |
*** mriedem has joined #openstack-tc | 19:11 | |
*** mriedem_afk has quit IRC | 19:12 | |
fungi | i subscribe to and dump posts from all those lists into the same maildir. mutt immediately identifies and marks them as duplicates in the thread so i know to skip the rest | 19:28 |
fungi | but i guess the lesson there is i'm able to ignore the cross-posted duplicates because i already treat them all as the same mailing list | 19:29 |
*** jamesmcarthur has joined #openstack-tc | 19:29 | |
*** e0ne has joined #openstack-tc | 19:34 | |
*** mugsie has quit IRC | 20:25 | |
*** e0ne has quit IRC | 20:29 | |
*** mugsie has joined #openstack-tc | 20:38 | |
*** annabelleB has joined #openstack-tc | 20:42 | |
*** harlowja has joined #openstack-tc | 20:43 | |
*** openstackgerrit has joined #openstack-tc | 21:01 | |
openstackgerrit | Doug Hellmann proposed openstack/governance master: make the board repo list file format consistent with others https://review.openstack.org/598350 | 21:01 |
fungi | https://techcrunch.com/2018/08/30/openstacks-latest-release-focuses-on-bare-metal-clouds-and-easier-upgrades/ | 21:02 |
fungi | https://www.sdxcentral.com/articles/news/despite-what-vmware-says-not-everyone-wants-to-deploy-containers-in-vms/2018/08/ | 21:02 |
smcginnis | That TechCrunch article is refreshingly positive. | 21:04 |
* fungi waits for the other shoe to drop | 21:04 | |
fungi | i agree that's a more pleasant spin than i usually expect | 21:05 |
fungi | ironic's really taking the spotlight in these | 21:06 |
jroll | nice :) | 21:07 |
fungi | people do love the idea of bios control, apparently. or at least the press thinks so | 21:07 |
jroll | I notice openstack has a fast-forward upgrades feature now :P | 21:07 |
fungi | yes, i will try to upgrade my diablo cloud to stein | 21:07 |
* fungi looks around for the pushbutton | 21:08 | |
fungi | still, yahoo!/oath upgrading from juno to ocata is pretty monumental | 21:10 |
*** annabelleB has quit IRC | 21:15 | |
*** diablo_rojo has quit IRC | 21:53 | |
*** annabelleB has joined #openstack-tc | 21:57 | |
mnaser | tc-members: https://slides.com/dfarrell07/appointed-to-elected-gov | 22:01 |
mnaser | Really interesting governance related talk today at OSS | 22:02 |
mnaser | Also, interesting idea of representative groups | 22:02 |
fungi | will a recording of that be posted, do you know? the slide deck is very sparse | 22:10 |
fungi | i have to assume he spoke many words over those slides | 22:11 |
*** jamesmcarthur has quit IRC | 22:13 | |
*** jamesmcarthur has joined #openstack-tc | 22:14 | |
*** purplerbot has quit IRC | 22:16 | |
*** purplerbot has joined #openstack-tc | 22:17 | |
*** mriedem is now known as mriedem_lawnboy | 22:17 | |
*** tosky has quit IRC | 22:23 | |
*** lxkong has joined #openstack-tc | 22:24 | |
mnaser | fungi: unfortunately the sessions weren’t recorded :( I really hope we can find a way to hear the story said by Dan | 22:24 |
openstackgerrit | Chris Dent proposed openstack/governance master: Add placement deliverable to nova https://review.openstack.org/598380 | 22:26 |
mtreinish | mnaser: heh, the linux foundation has never recorded the regular talks at any of their confs I've been to | 22:30 |
mtreinish | it's really quite annoying | 22:30 |
fungi | jbryce: ^ also useful event feedback. seems people do appreciate our choice to record most presentations | 22:34 |
*** annabelleB has quit IRC | 22:35 | |
smcginnis | Definitely | 22:39 |
*** annabelleB has joined #openstack-tc | 22:39 | |
jbryce | fungi: the interface for the slides was kind of weird. if you click the right arrow, sometimes a down arrow appears and then there are more slides on that topic with more details | 22:41 |
jbryce | fungi: maybe you already discovered that, but it tripped me up at first and i was like "these slides are really high level" | 22:42 |
smcginnis | Looks like GitPitch. | 22:43 |
fungi | yeah | 22:44 |
fungi | it was certainly a weird slide viewer | 22:44 |
fungi | dhellmann: ttx: to answer the question earlier about un-black-holing the openstack-announce-owner@lists.o.o address, yesterday it received 1530 messages (basically all of which claimed to be sent from random @qq.com addresses | 22:48 |
smcginnis | Lovely | 22:49 |
fungi | so maybe declining? but still a lot | 22:49 |
dhellmann | fungi : ok, yeah, let's just leave things as they are | 22:49 |
fungi | especially given we've been rejecting those since something like february | 22:49 |
dhellmann | do we bounce them or just throw them away? | 22:49 |
fungi | we reject them at receipt time, so in theory anyone sending to that address receives an ndr from the mta on their side | 22:50 |
dhellmann | not that I expect a spam bot to pay attention to bounces | 22:50 |
dhellmann | yeah | 22:50 |
fungi | bouncing would be a disaster since these are almost certainly spoofed addresses anyway | 22:50 |
dhellmann | yeah | 22:50 |
fungi | so we'd be spamming people too | 22:50 |
*** jamesmcarthur has quit IRC | 22:56 | |
*** jamesmcarthur has joined #openstack-tc | 23:00 | |
*** jamesmcarthur has quit IRC | 23:03 | |
*** jamesmcarthur has joined #openstack-tc | 23:03 | |
*** jamesmcarthur has quit IRC | 23:06 | |
*** annabelleB has quit IRC | 23:07 | |
mrhillsman | dhellmann these patches do not require quorum right? | 23:13 |
mrhillsman | or should not rather | 23:13 |
dhellmann | mrhillsman : that's entirely up to the owners of the repo | 23:13 |
dhellmann | the import ones ought to be no-ops at this point, moving settings from one place to another without changing them | 23:13 |
dhellmann | there are others that add or change jobs | 23:14 |
mrhillsman | ok cool | 23:14 |
dhellmann | the import ones would be an easy set to say you could fast-approve with 1 reviewer, IMHO, but that's up to you -- some teams are, some are not (since they are CI settings) | 23:14 |
*** cdent has quit IRC | 23:22 | |
zaneb | re that slide deck... I'm very glad we don't have a culture when we expect our elected leaders to represent the Interests of their employers | 23:24 |
*** annabelleB has joined #openstack-tc | 23:29 | |
*** annabelleB has quit IRC | 23:51 | |
*** annabelleB has joined #openstack-tc | 23:56 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!