Monday, 2015-02-23

*** etoews has quit IRC00:02
*** yamamoto has joined #openstack-meeting-300:05
*** MarkAtwood has joined #openstack-meeting-300:08
*** yamamoto has quit IRC00:08
*** lazy_prince has quit IRC00:13
*** armax has joined #openstack-meeting-300:14
*** killer_prince has joined #openstack-meeting-300:14
*** killer_prince is now known as lazy_prince00:14
*** markvoelker has joined #openstack-meeting-300:16
*** markvoelker has quit IRC00:20
*** lazy_prince has quit IRC00:21
*** pavel_bondar has quit IRC00:21
*** killer_prince has joined #openstack-meeting-300:22
*** killer_prince is now known as lazy_prince00:22
*** pavel_bondar has joined #openstack-meeting-300:22
*** armax has quit IRC00:32
*** seizadi has joined #openstack-meeting-300:40
*** yamamoto has joined #openstack-meeting-300:48
*** sbalukoff has joined #openstack-meeting-300:49
*** markvoelker has joined #openstack-meeting-300:50
*** amotoki has joined #openstack-meeting-300:53
*** markvoelker has quit IRC00:55
*** stanzgy has quit IRC01:00
*** watanabe_isao has joined #openstack-meeting-301:04
*** Yi has joined #openstack-meeting-301:07
*** Yi_ has joined #openstack-meeting-301:08
*** Yi has quit IRC01:08
*** Yi_ has quit IRC01:12
*** Yi has joined #openstack-meeting-301:16
*** Yi has quit IRC01:19
*** salv-orlando has quit IRC01:22
*** kbyrne has quit IRC01:23
*** kbyrne has joined #openstack-meeting-301:25
*** VW_ has quit IRC01:27
*** baoli has joined #openstack-meeting-301:28
*** lazy_prince has quit IRC01:33
*** Yi has joined #openstack-meeting-301:33
*** etoews has joined #openstack-meeting-301:41
*** baoli has quit IRC01:41
*** armax has joined #openstack-meeting-301:41
*** sbalukoff has quit IRC01:42
*** amotoki has quit IRC01:44
*** killer_prince has joined #openstack-meeting-301:50
*** killer_prince is now known as lazy_prince01:50
*** markvoelker has joined #openstack-meeting-301:51
*** markvoelker has quit IRC01:57
*** markvoelker has joined #openstack-meeting-302:00
*** baoli has joined #openstack-meeting-302:02
*** MarkAtwood has quit IRC02:03
*** lazy_prince has quit IRC02:05
*** seizadi has quit IRC02:05
*** killer_prince has joined #openstack-meeting-302:07
*** killer_prince is now known as lazy_prince02:07
*** MarkAtwood has joined #openstack-meeting-302:08
*** MarkAtwood has quit IRC02:15
*** baoli has quit IRC02:16
*** lazy_prince has quit IRC02:20
*** MarkAtwood has joined #openstack-meeting-302:21
*** markvoelker has quit IRC02:26
*** markvoelker has joined #openstack-meeting-302:27
*** markvoelker has quit IRC02:31
*** yamahata has quit IRC02:32
*** yamahata has joined #openstack-meeting-302:32
*** killer_prince has joined #openstack-meeting-302:33
*** killer_prince is now known as lazy_prince02:33
*** MarkAtwood has quit IRC02:37
*** lazy_prince has quit IRC02:38
*** killer_prince has joined #openstack-meeting-302:40
*** killer_prince is now known as lazy_prince02:40
*** yamahata has quit IRC02:46
*** Yi has quit IRC02:46
*** lazy_prince has quit IRC02:48
*** killer_prince has joined #openstack-meeting-302:53
*** killer_prince is now known as lazy_prince02:53
*** lazy_prince has quit IRC02:57
*** killer_prince has joined #openstack-meeting-302:58
*** killer_prince is now known as lazy_prince02:58
*** lazy_prince has quit IRC03:05
*** killer_prince has joined #openstack-meeting-303:07
*** killer_prince is now known as lazy_prince03:07
*** etoews has quit IRC03:14
*** MarkAtwood has joined #openstack-meeting-303:19
*** amotoki has joined #openstack-meeting-303:19
*** baoli has joined #openstack-meeting-303:27
*** tellesnobrega_ has joined #openstack-meeting-303:31
*** tellesnobrega_ has quit IRC03:31
*** baoli has quit IRC03:42
*** bpokorny has quit IRC04:01
*** megm_ has joined #openstack-meeting-304:01
*** megm has quit IRC04:01
*** yushiro has joined #openstack-meeting-304:08
*** armax_ has joined #openstack-meeting-304:19
*** armax has quit IRC04:20
*** armax_ is now known as armax04:20
yushiroSumitNaiksatam, Hi.04:21
*** armax has quit IRC04:22
*** ivar-lazzaro has quit IRC04:22
*** Yi has joined #openstack-meeting-304:29
*** MarkAtwood has quit IRC04:31
yushirodougwig, amotoki Hi.  Do you have a minute?04:35
amotokiすみません。メインディスプレイが映らなくなったので、右側しか見えないのでちょっとやばいです04:39
amotokisorry. I wrote to the wrong channel.04:42
amotokiyushiro: what meeting here?04:42
*** Yi has quit IRC04:48
yushiroamotoki, Thank you.  I'd like you to review my patch about fwaas and neutron-unit test04:50
amotokiyushiro: it is not a channel for such request.04:50
yushiroamotoki, I'm so sorry.04:51
*** etoews has joined #openstack-meeting-304:53
*** etoews has quit IRC04:57
*** Yi has joined #openstack-meeting-304:59
*** Yi has quit IRC05:00
*** Yi has joined #openstack-meeting-305:01
*** lazy_prince has quit IRC05:14
*** baoli has joined #openstack-meeting-305:16
*** lazy_prince has joined #openstack-meeting-305:16
*** lazy_prince is now known as killer_prince05:19
*** killer_prince is now known as lazy_prince05:20
*** baoli has quit IRC05:28
*** Yi has quit IRC05:30
*** baoli has joined #openstack-meeting-305:32
*** lazy_prince has quit IRC05:34
*** lazy_prince has joined #openstack-meeting-305:39
*** lazy_prince is now known as killer_prince05:40
*** Yi has joined #openstack-meeting-305:41
*** killer_prince is now known as lazy_prince05:42
*** Yi has quit IRC05:42
*** seizadi has joined #openstack-meeting-305:44
*** lazy_prince has quit IRC05:45
*** baoli has quit IRC05:46
*** killer_prince has joined #openstack-meeting-305:51
*** killer_prince has quit IRC05:55
*** baoli has joined #openstack-meeting-306:04
*** killer_prince has joined #openstack-meeting-306:15
*** killer_prince is now known as lazy_prince06:15
*** baoli has quit IRC06:18
*** lazy_prince has quit IRC06:19
*** lazy_prince has joined #openstack-meeting-306:22
*** lazy_prince is now known as killer_prince06:24
*** killer_prince is now known as lazy_prince06:27
*** sankarshan has joined #openstack-meeting-306:27
*** coolsvap_ is now known as coolsvap06:27
*** etoews has joined #openstack-meeting-306:36
*** MarkAtwood has joined #openstack-meeting-306:39
*** etoews has quit IRC06:41
*** Yi has joined #openstack-meeting-306:42
*** FallenPegasus has joined #openstack-meeting-306:44
*** MarkAtwood has quit IRC06:45
*** FallenPegasus is now known as MarkAtwood06:45
*** Yi has quit IRC06:47
*** etoews has joined #openstack-meeting-306:54
*** jcoufal has joined #openstack-meeting-306:57
*** etoews has quit IRC06:59
*** mrunge has joined #openstack-meeting-307:04
*** scheuran has joined #openstack-meeting-307:08
*** belmoreira has joined #openstack-meeting-307:10
*** yushiro has quit IRC07:16
*** mrmartin has joined #openstack-meeting-307:20
*** seizadi has quit IRC07:26
*** sbalukoff has joined #openstack-meeting-307:39
*** sahid has joined #openstack-meeting-307:40
*** yushiro has joined #openstack-meeting-307:51
*** baoli has joined #openstack-meeting-307:52
*** MarkAtwood has quit IRC07:58
*** Yi has joined #openstack-meeting-308:00
*** MarkAtwood has joined #openstack-meeting-308:00
*** evgenyf has joined #openstack-meeting-308:02
*** megm has joined #openstack-meeting-308:03
*** megm_ has quit IRC08:04
*** Yi has quit IRC08:05
*** sahid has quit IRC08:06
*** baoli has quit IRC08:06
*** matrohon has joined #openstack-meeting-308:09
*** yushiro has quit IRC08:09
*** iovadia has joined #openstack-meeting-308:10
*** iovadia has quit IRC08:14
*** ttx2 has joined #openstack-meeting-308:15
*** ttx2 is now known as ttx08:15
*** ttx has quit IRC08:17
*** ttx has joined #openstack-meeting-308:17
*** ttx has quit IRC08:17
*** ttx has joined #openstack-meeting-308:18
*** ttx has quit IRC08:19
*** ttx has joined #openstack-meeting-308:19
*** jcoufal has quit IRC08:22
*** jcoufal has joined #openstack-meeting-308:23
*** jtomasek has joined #openstack-meeting-308:24
*** sahid has joined #openstack-meeting-308:28
*** iovadia has joined #openstack-meeting-308:28
*** egallen has joined #openstack-meeting-308:35
*** MaxV has joined #openstack-meeting-308:46
*** watanabe_isao has quit IRC08:49
*** zz_ttrifonow is now known as ttrifonov08:53
*** VW_ has joined #openstack-meeting-309:02
*** zz_johnthetubagu is now known as johnthetubaguy09:09
*** devvesa has joined #openstack-meeting-309:12
*** devvesa has quit IRC09:14
*** devvesa has joined #openstack-meeting-309:14
*** bauwser is now known as bauzas09:15
*** sankarshan is now known as sankarshan_away09:17
*** yamamoto has quit IRC09:23
*** wojdev has joined #openstack-meeting-309:25
*** salv-orlando has joined #openstack-meeting-309:33
*** yamamoto has joined #openstack-meeting-309:51
*** salv-orlando has quit IRC10:04
*** kashyap has left #openstack-meeting-310:12
*** ozamiatin has joined #openstack-meeting-310:13
*** salv-orlando has joined #openstack-meeting-310:14
*** evgenyf has quit IRC10:26
*** kbyrne has quit IRC10:49
*** kbyrne has joined #openstack-meeting-310:49
*** wojdev has quit IRC10:49
*** egallen has quit IRC10:52
*** armax has joined #openstack-meeting-310:53
*** yamamoto has quit IRC10:58
*** evgenyf has joined #openstack-meeting-311:04
*** jaypipes has joined #openstack-meeting-311:05
*** wojdev has joined #openstack-meeting-311:06
*** armax has quit IRC11:12
*** salv-orlando has quit IRC11:19
*** MarkAtwood has quit IRC11:24
*** salv-orlando has joined #openstack-meeting-311:25
*** SumitNaiksatam has quit IRC11:26
*** SumitNaiksatam has joined #openstack-meeting-311:26
*** salv-orlando has quit IRC11:29
*** salv-orl_ has joined #openstack-meeting-311:29
*** baoli has joined #openstack-meeting-311:41
*** wojdev has quit IRC11:46
*** wojdev has joined #openstack-meeting-311:58
*** egallen has joined #openstack-meeting-312:02
*** megm_ has joined #openstack-meeting-312:05
*** megm has quit IRC12:06
*** jcoufal has quit IRC12:10
*** jcoufal_ has joined #openstack-meeting-312:10
*** VW_ has quit IRC12:10
*** yamamoto_ has joined #openstack-meeting-312:14
*** VW_ has joined #openstack-meeting-312:31
*** salv-orl_ has quit IRC12:38
*** salv-orlando has joined #openstack-meeting-312:39
*** salv-orlando has quit IRC12:42
*** salv-orlando has joined #openstack-meeting-312:43
*** zigo has quit IRC12:52
*** wojdev has quit IRC12:53
*** zigo has joined #openstack-meeting-312:56
*** salv-orlando has quit IRC13:04
*** etoews has joined #openstack-meeting-313:05
*** jckasper has quit IRC13:08
*** etoews has quit IRC13:10
*** mwagner_lap has joined #openstack-meeting-313:13
*** pkoniszewski has joined #openstack-meeting-313:19
*** lsmola has quit IRC13:23
*** salv-orlando has joined #openstack-meeting-313:23
*** lsmola has joined #openstack-meeting-313:27
*** salv-orlando has quit IRC13:28
*** lblanchard has joined #openstack-meeting-313:31
*** salv-orlando has joined #openstack-meeting-313:33
*** lazy_prince is now known as killer_prince13:39
*** salv-orlando has quit IRC13:41
*** bknudson has quit IRC13:41
*** Yi has joined #openstack-meeting-313:43
*** jckasper has joined #openstack-meeting-313:44
*** salv-orlando has joined #openstack-meeting-313:46
*** Yi has quit IRC13:48
*** thomasem has joined #openstack-meeting-313:49
*** cbader has joined #openstack-meeting-313:53
*** salv-orlando has quit IRC13:53
*** bknudson has joined #openstack-meeting-314:05
*** wojdev has joined #openstack-meeting-314:17
*** Yi has joined #openstack-meeting-314:21
*** Yi_ has joined #openstack-meeting-314:21
*** Yi has quit IRC14:21
*** seizadi has joined #openstack-meeting-314:23
*** peristeri has joined #openstack-meeting-314:30
*** Yi_ has quit IRC14:35
*** wojdev has quit IRC14:36
*** mrmartin has quit IRC14:36
*** Yi has joined #openstack-meeting-314:37
*** amotoki has quit IRC14:37
*** jcoufal_ has quit IRC14:38
*** jcoufal has joined #openstack-meeting-314:38
*** etoews has joined #openstack-meeting-314:42
*** watanabe_isao has joined #openstack-meeting-314:46
*** thangp has joined #openstack-meeting-314:47
*** mrmartin has joined #openstack-meeting-314:47
*** watanabe_isao has quit IRC14:52
*** superdan is now known as dansmith14:53
*** erikmwilson has joined #openstack-meeting-315:06
*** lascii is now known as alaski15:09
*** wojdev has joined #openstack-meeting-315:13
*** pkoniszewski has quit IRC15:13
*** nelsnelson has joined #openstack-meeting-315:13
*** sigmavirus24_awa is now known as sigmavirus2415:16
*** Piet has quit IRC15:27
*** wojdev has quit IRC15:27
*** mestery has quit IRC15:36
*** zigo_ has joined #openstack-meeting-315:36
*** alexpilotti has joined #openstack-meeting-315:37
*** wojdev has joined #openstack-meeting-315:37
*** mrmartin has quit IRC15:39
*** mattfarina has joined #openstack-meeting-315:41
*** Yi_ has joined #openstack-meeting-315:43
*** Yi has quit IRC15:47
*** seizadi has quit IRC15:47
*** wojdev has quit IRC15:47
*** ChuckC has joined #openstack-meeting-315:49
*** cbader has quit IRC15:49
*** mrmartin has joined #openstack-meeting-315:52
*** cbader has joined #openstack-meeting-315:52
*** ChuckC_ has quit IRC15:52
*** jfjoly has joined #openstack-meeting-315:53
*** yolanda has joined #openstack-meeting-315:53
*** evgenyf has quit IRC15:53
*** bpokorny has joined #openstack-meeting-315:54
*** MarkAtwood has joined #openstack-meeting-315:55
krotscheck#startmeeting Storyboard16:00
openstackMeeting started Mon Feb 23 16:00:32 2015 UTC and is due to finish in 60 minutes.  The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** Piet has joined #openstack-meeting-316:00
*** openstack changes topic to " (Meeting topic: Storyboard)"16:00
openstackThe meeting name has been set to 'storyboard'16:00
yolandao/16:00
krotscheckAgenda: https://wiki.openstack.org/wiki/StoryBoard#Agenda16:01
krotscheckWho's here?16:01
*** rcarrillocruz has joined #openstack-meeting-316:01
yolandahi hi16:01
rcarrillocruzhi16:01
krotscheckwooooo16:01
krotscheckpeople!16:01
jeblairand other persons16:01
krotscheckPeople, and other persons? Wow, do we get some personalities too?16:01
krotscheck#topic Actions from Last Week: DB Refactor Spec16:02
*** openstack changes topic to "Actions from Last Week: DB Refactor Spec (Meeting topic: Storyboard)"16:02
krotscheckNikitaKonovalov: You around? Any work on the spec?16:02
ttxo/16:03
krotscheckI'll take that as a no. Leaving it on the agenda.16:03
krotscheck#topic Urgent Items16:03
*** openstack changes topic to "Urgent Items (Meeting topic: Storyboard)"16:03
krotscheckDid anything major come up?16:03
krotscheckAlso silence!16:04
* krotscheck is happy when that topic has silence.16:04
krotscheckI did bring one up though16:04
krotscheck#topic Urgent Items: HP Things16:04
*** openstack changes topic to "Urgent Items: HP Things (Meeting topic: Storyboard)"16:04
yolanda:(16:04
krotscheckSo, as some of you may have seen on the TripleO threads on channel, there've been some changes inside of HP.16:04
krotscheckI cannot comment on details from inside of HP16:05
krotscheckHowever at this point it's becoming clear that our team will be impacted as well.16:05
* ttx doesn't want to see the insides16:05
*** amotoki has joined #openstack-meeting-316:05
jeblairkrotscheck: in what way?16:05
*** carl_baldwin has joined #openstack-meeting-316:06
krotscheckjeblair: There is significant concern that yolanda, rcarrillocruz, and jedimike won't be able to contribute much anymore.16:06
yolandai will do on free time16:06
* krotscheck notes that some of them have been doing so on free time already.16:06
yolandai'm really commited with storyboard16:06
rcarrillocruzi will as well, but obv. this will impact SB...16:07
jeblairkrotscheck: this is news to me16:07
krotscheckjeblair: I'd be happy to discuss internal HP things with you in internal HP channels, or you could reach out to them direclty.16:07
jeblairyolanda, rcarrillocruz: has someone told you such?16:07
*** CTtpollard has joined #openstack-meeting-316:07
rcarrillocruzlikewise, i'm happy to share our thoughts and concerns16:07
*** megm has joined #openstack-meeting-316:07
yolandajeblair, we cannot share so much but it will be like that16:08
rcarrillocruzin private or an internal HP channel16:08
yolandayes16:08
yolandaprivate16:08
*** megm_ has quit IRC16:08
jeblairkrotscheck: ok, i'm just confused, because yolanda and rcarrillocruz were not on the tripleo team.16:08
krotscheckWith that in mind though, we do not yet know any details.16:08
yolandajeblair, krotscheck, we can create later some channel and talk  about it16:09
jeblairkrotscheck: i do not believe what you say should be the case16:09
jeblairi'm happy to talk about it privately16:09
rcarrillocruzagree16:09
jeblairbut i did not bring it up publicly16:09
krotscheckjeblair: I agree, I am saying there's concern, and that we don't know much yet.16:10
jeblairso, i will say publicly that i don't think it should be the case, there may be a misunderstanding16:10
krotscheckAgain, I agree, and I am saying publicly that the situation remains unresolved.16:10
jeblairkrotscheck: yes, but saying "i have concern that hp is cutting support for 3 people who are working on this project" is a dangerous thing to say16:10
krotscheckjeblair: Dangerous how? I am being honest.16:11
jeblairkrotscheck: i wish you would have said nothing until you knew something factual.  i believe you have just muddied the waters.16:11
jeblairkrotscheck: because now people will think that hp is less committed to storyboard, and this is all based on a reorganization of an unrelated team.16:11
ttxI for one appreciate the heads-up. Let me know how that evolves (one way or another)16:12
krotscheckWell, I'm not a fan of hiding things until facts develop. Concerns need to be raised so they can be addressed, and I welcome public statements to address those concerns.16:13
mordredI have no reason to believe that anyone at HP will be prevented from working on storyboard16:14
jeblairkrotscheck: sure, but "at this point it's becoming clear that our team will be impacted as well" seems counterfactual to me16:14
krotscheckmordred: Good to hear.16:14
*** sandhya has joined #openstack-meeting-316:15
*** jcoufal has quit IRC16:15
mordredor, let me rephrase, there are no priorities that have been changed that I am aware of for any of the people at HP other than krotscheck who have been hacking on storyboard.16:15
krotscheckListen: There's an elephant in the room. I am not a fan of ignoring the elephant until we know whether it's pink or not. I am worried, lots of people are worried.16:15
yolandamordred, so i think we all need to have better clarification, and expose the situation clearly16:15
yolandathat's not the moment btw16:15
krotscheckI say we recognize that there's an elephant, and express our color preferences.16:16
mordredthey have always had a primary job description that could trump for moments of time their ability to have a ton of time to devote16:16
mordredgiven that they are responsible for a production service and outages take priority16:16
mordrednothing about that has changed16:16
*** erikmwilson has quit IRC16:16
krotscheckGuys, I'm not trying to put anyone on the defensive here.16:17
mordredsimilarly, their production service is based on openstack-infra, so being involved with usptream infra efforts has been and remains to be a priority16:17
*** wojdev has joined #openstack-meeting-316:17
*** belmoreira has quit IRC16:17
mordredsure - I just want to be clear about what the situation has been and is now16:17
mordredI apoligize for any lack of clarity that is causing stress16:17
mordredapologize16:17
mordredapoligize is not a word :)16:17
krotscheckIt is in some parts of the states.16:18
mordredtouche16:18
krotscheckOk, so my intent with bringing this up was to just say: Hey, things inside of HP are really uncertain right now, there's a bunch of people who contribute to this project who are worried.16:18
krotscheckIf something similar happened to Mirantis, I would hope they bring it up as well.16:18
mordredindeed. I'll make a note to try to clarify with everyone16:19
mordredthere is actually not uncertainty - but that may be unclear and uncertain16:19
krotscheckmordred: Oh good.16:19
krotscheckAnyone have anything else to say on this before we move on?16:19
mordredI had meant to follow up with everyone towards the end of last week, but I am only just now really back online16:20
mordredso sorry for stress my company causes sometimes16:20
krotscheckAlright, let's move on.16:21
krotscheck#topic Discussion Topics: Google Summer of Code16:21
*** jtomasek has quit IRC16:21
*** openstack changes topic to "Discussion Topics: Google Summer of Code (Meeting topic: Storyboard)"16:21
*** devlaps has joined #openstack-meeting-316:21
yolandanot related, but haven't seen Jovanka for some days16:21
krotscheckyolanda: Where's she based out of?16:22
yolandaMacedonia16:22
krotscheckkk.16:22
krotscheckSo we've got the UX team support as a potential project. Does anyone else have ideas?16:22
krotscheckOh, comeon. Does anyone else have off-roadmap pet projects they want to see in storyboard?16:23
yolandaonly UX ? why not a full feature?16:23
jeblairyolanda: the full feature is adding support for interactive annotation of attached images in support of the ux team16:24
yolandaattached images will be covered by Jovanka16:24
yolandabut i need to contact her again, not sure what happens16:24
krotscheckmordred: What about a storyboard IRC bot?16:25
jeblairkrotscheck: we're discussing alternative bot frameworks, but i don't think we've quite settled how that will work.  we may not be ready for that.16:26
krotscheckjeblair: Will that discussion have settled by may?16:26
jeblairkrotscheck: probably.  it will also be a very small project; probably 50 lines of code.16:27
ttxkrotscheck: I suggested the file attachment stuff :)16:27
krotscheckttx: Right!16:27
krotscheckSOrry, forgot about that.16:27
krotscheckIf jovanka's able to work on that, great.16:28
* ttx tries to remember the other idea he had16:28
ttxoh, markup comments16:28
krotscheckttx: Could you explain that one a bit more?16:29
ttxwell, the ability to use rich(er) text in comments16:29
krotscheckOh, nice.16:29
* krotscheck puts that on the list.16:29
ttx(and descriptions for that matter)16:29
ttxI see two items that correspond in the Roadmap:16:29
ttxEtherpad Summit Design Session Markup Import16:29
*** nelsnelson has quit IRC16:30
ttx Rich Text Comments (markdown?)16:30
ttxOh oh oh16:30
ttxI remember now: "task ordering".16:30
krotscheckThe ability to push our code back to the various node/bower repositories would be nice too.16:30
ttxThat was the other idea16:30
krotscheckBrilliant.16:30
ttxI think that's sufficiently standalone16:30
krotscheckThat gives us 6 projects to propose.16:30
ttxAll the others are pretty deep in the code16:30
*** mwagner_ has joined #openstack-meeting-316:31
krotscheckYeah, and who knows how much code someone can get. It'll take at least a month to get into the codebase.16:31
krotschecks/get/get done/16:31
ttxFile attachments and task ordering neatly touch transversally without depending on too much other's work16:31
jeblairbtw, i worked on a story the other day that is almost certainly going to want task ordering16:31
*** cbader02 has joined #openstack-meeting-316:31
krotscheckjeblair: Is that the one that was entered on friday?16:32
jeblairya16:32
jeblairwe were brainstorming into the story, and i'm certain we didn't get all the things we need to do in the right order the first time :)16:32
krotscheckSo just to be clear, we're talking about a simple ordering mechanism, not something like task dependencies?16:33
ttxkrotscheck: exact16:33
krotscheckCool.16:33
ttxideally with awesome UI to match16:33
krotscheck:)16:33
* krotscheck really wants to work on the UI again :(16:33
*** mestery has joined #openstack-meeting-316:33
* krotscheck gets annoyed at that yack not being shaved.16:33
*** sbalukoff has quit IRC16:34
*** cbader__ has joined #openstack-meeting-316:34
*** wojdev has quit IRC16:34
ttxThe idea being to be lightweight enough so that people can ignore ordering when it doesn't matter but can order when it does16:34
krotscheckAlright, it's on the list.16:34
*** cbader has quit IRC16:34
krotscheckDoes anyone object to settling this topic? YOu can marinate on it in our free time and add thigns later.16:35
krotscheckCurrently I have UX Feature, File attachments, Rich Text markup, and Task Ordering16:35
*** cbader02 has quit IRC16:36
*** cbader__ has quit IRC16:36
krotscheck#action Krotscheck Get GSoC onto the wiki with some descriptions.16:37
krotscheck#topic InProgress (krotscheck)16:37
*** openstack changes topic to "InProgress (krotscheck) (Meeting topic: Storyboard)"16:37
krotscheckSo, last week I was working on puppet. There's enough features lined up on the storyboard codebase that it warrants an update to the module.16:37
krotscheckThe hope being that storyboard-dev will soon become a thing.16:37
krotscheckI do have a few patches that won't pass because they're interdependent with ones on system-config, so I'll be poking the infra channel about figuring out the depends-on tag for that one.16:38
krotscheckThe pile starts here: https://review.openstack.org/#/c/156755/216:39
ttxkrotscheck: I still couldn't get auth through -draft to work, still "Oh No"16:39
krotscheckttx: Yep. That's what that first patch is there for.16:39
krotscheckWait, i lied.16:39
krotscheckIt's the second one in the chain16:39
krotscheckThis one: https://review.openstack.org/#/c/157464/16:40
krotscheckI think16:40
krotscheckOr did I lie again?16:40
ttxack -- don't have +2 there and seems to have enough +1s16:40
krotscheckYep.16:40
*** killer_prince is now known as lazy_prince16:40
krotscheckThat one'll make the configuration flag available, we'll need to add a similar patch in system-config to move things.16:40
* krotscheck doesn't have +2 there either16:41
jeblairkrotscheck: then in your system-config patch, add "Depends-On: I29495a0b640c3ca097cca8c17349df5cc42388de" to the commit message16:41
krotscheckjeblair: I did for some of them. There's a bit of a chicken-egg problem on one of the patches though, will flag you later if I can't figure it out.16:42
jeblairkk16:42
krotscheckThat stack happens to start here: https://review.openstack.org/#/c/157981/2/modules/openstack_project/manifests/storyboard.pp16:42
*** devlaps has quit IRC16:42
krotscheckI'm going to continue working on that, because I have too many things on my plate and I want to get some of them off.16:42
krotscheckNext.16:42
krotscheck#topic InProgress (yolanda)16:42
*** openstack changes topic to "InProgress (yolanda) (Meeting topic: Storyboard)"16:42
krotscheckWhat's up?16:42
yolandaso...16:43
yolandahttps://review.openstack.org/15654316:43
yolandaneeds review16:43
yolandathe index for access_token16:43
* krotscheck rechecks that patch now that python34 is voting.16:44
krotscheck(Oh yeah, I forgot to mention that python34 is voting now!)16:44
yolandaspecs for integration tests had a +2 https://review.openstack.org/15074316:44
*** cbader has joined #openstack-meeting-316:45
krotscheck+1 from me.16:45
yolandaand i started working on it even the spec wasn't approved 100%16:45
yolandaso this one is for adding the tooling in the backend to run the tests16:45
yolandahttps://review.openstack.org/15597516:45
yolandaand this one to create the configuration in project-config16:46
yolandahttps://review.openstack.org/15604416:46
yolandaand that's all from my side16:46
krotscheckNeat!16:47
krotscheck#topic InProgress (greghaynes)16:47
*** openstack changes topic to "InProgress (greghaynes) (Meeting topic: Storyboard)"16:47
krotscheckHe's... not here.16:47
krotscheckI'll give his update.16:47
krotscheckHe made python 34 work!16:47
yolandawoot!16:47
*** nelsnelson has joined #openstack-meeting-316:47
* krotscheck is looking forward to the land of no more six.16:48
*** devlaps has joined #openstack-meeting-316:48
rcarrillocruzgood, i was fed up of getting tox failures :-)16:48
krotscheckrcarrillocruz: Me too :)16:48
CTtpollardcool16:48
*** amotoki has quit IRC16:48
krotscheckDoes anyone have major objections to eventually getting rid of python27? Right now the only issue seems to be older debian versions (ubuntu-precise-ish) that don't have a py34 distor.16:48
krotscheck*distro16:48
krotscheckWell, if so, we can argue that on gerrit.16:49
krotscheck#topic InProgress (rcarrillocruz)16:50
*** openstack changes topic to "InProgress (rcarrillocruz) (Meeting topic: Storyboard)"16:50
krotscheckHi hi!16:50
rcarrillocruznothing i'm afraid16:50
rcarrillocruzdrowned by dayjob the whole week16:50
rcarrillocruzsorry :(16:50
krotscheckNo worries!16:50
krotscheck#topic InProgress (NikitaKonovalov)16:51
*** openstack changes topic to "InProgress (NikitaKonovalov) (Meeting topic: Storyboard)"16:51
krotscheckYou here?16:51
krotscheck....wait a sec.16:51
*** iovadia has quit IRC16:51
krotscheckOh, it's "Defend the Fatherland" day in russia.16:51
krotscheck(Defender of)16:51
krotscheckThey're probably on holiday.16:51
krotscheck#topic InProgress (jedimike)16:52
krotscheckYou here?16:52
*** openstack changes topic to "InProgress (jedimike) (Meeting topic: Storyboard)"16:52
jeblairkrotscheck: i'd like to keep python27 for a while; it's the default python in the current ubuntu lts16:52
krotscheckjeblair: You got it.16:52
yolandajedimike had day off16:52
krotscheckCool!16:52
krotscheck#topic Open Discussion.16:52
*** sirushti has joined #openstack-meeting-316:52
*** openstack changes topic to "Open Discussion. (Meeting topic: Storyboard)"16:52
*** naohirot has joined #openstack-meeting-316:52
krotscheckWe have 8 minutes!16:52
ttxwoohoo16:52
*** stendulker has joined #openstack-meeting-316:53
ttx(says the guy attending two meetings in parallel)16:53
*** romcheg has joined #openstack-meeting-316:53
krotscheckI wnt to apologize fro dragging my feet on email, dev.storyboard, and other things.16:53
yolandaso for the integration tests, i hope the project and the tools are merged this week, and i want to do some more tests than just testing an empty api result16:53
krotscheckI don't know why it's been tough to focus on that, but something else keeps getting in the way.16:53
krotscheckyolanda: The only question on that I have is about the DB_ADMIN user - isnt' there a ci_openstacktest user that we can use?16:55
yolandawell, i wanted to do the tool more generic16:55
yolandaso you can run the tests in your own environment16:55
*** rloo has joined #openstack-meeting-316:55
*** dtantsur has joined #openstack-meeting-316:56
yolandaso i added the flag that indicates if you want to create the initial user16:56
krotscheckyolanda: Right, I see that. I was thinking more here -> https://review.openstack.org/#/c/156044/12/jenkins/jobs/javascript.yaml16:56
*** wanyen has joined #openstack-meeting-316:56
yolandaah, ok16:56
krotscheckThe DB_ADMIN_USER field16:56
*** reed has joined #openstack-meeting-316:57
*** sandhya has quit IRC16:57
*** ChuckC_ has joined #openstack-meeting-316:57
yolandabut in that case you install mysql from scratch, no user will be present at this moment16:57
yolandayou need to connect as root and create the initial users16:57
*** ChuckC_ has quit IRC16:58
krotscheckyolanda: Right. So we've got two use cases, the need to install things from scratch, and the need to use something sane on the jenkins instance.16:59
krotscheckWe're out of time though, I'll comment on the review.16:59
krotscheckThanks everyone!16:59
krotscheck#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Mon Feb 23 16:59:24 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-02-23-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-02-23-16.00.txt16:59
NobodyCamThank you krotscheck :)16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-02-23-16.00.log.html16:59
yolandabye!16:59
krotscheckNobodyCam: You're welcome, have fun in your meeting :)16:59
NobodyCam:) yeppers :)17:00
*** jlvillal has joined #openstack-meeting-317:00
*** ChuckC has quit IRC17:00
jroll\o17:00
*** Nisha has joined #openstack-meeting-317:00
*** ChuckC_ has joined #openstack-meeting-317:00
devananda#startmeeting ironic17:00
openstackMeeting started Mon Feb 23 17:00:33 2015 UTC and is due to finish in 60 minutes.  The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
devanandahi all!17:00
dtantsur\o/17:00
jrollhellooo!17:00
NobodyCamo/17:00
Nishao/17:00
stendulkero/17:00
naohiroto/17:00
lazy_princehi all..17:00
*** seizadi has joined #openstack-meeting-317:01
devanandaas usual, our agenda's on the wiki - https://wiki.openstack.org/wiki/Meetings/Ironic17:01
rloohi17:01
maurosrhi17:01
wanyeno/17:01
*** CTtpollard has left #openstack-meeting-317:01
NobodyCamlight agenda today17:01
*** BadCub_ has joined #openstack-meeting-317:01
JoshNango/17:01
devananda#topic announcements17:01
*** openstack changes topic to "announcements (Meeting topic: ironic)"17:01
*** 43UABVQBF has joined #openstack-meeting-317:01
*** matrohon has quit IRC17:02
devanandafeature freeze is coming up, and while we got a lot done at the sprints the last few weeks, we've got A TONNE to review ...17:02
*** sandhya has joined #openstack-meeting-317:02
NobodyCam:)17:02
dtantsuroh yeah17:02
*** faizan_ has joined #openstack-meeting-317:02
rloofeature proposal (ie specs) freeze is March 5. Feature freeze (code) is March 19?17:03
rloohttps://wiki.openstack.org/wiki/Kilo_Release_Schedule17:03
devanandarloo: sounds right17:03
*** scheuran has quit IRC17:03
devanandawe're sticking to that, but practically, it means we need to stay on top of our priorities17:04
devanandawhich brings me to17:04
*** mjturek1 has joined #openstack-meeting-317:04
devanandalast week I was pretty sick and was only sort of here for the meeting17:04
devanandaat the SF meetup, we talked about how we're tracking our priorities17:04
NobodyCam:) /me hopes deva is feeling better17:04
* dtantsur too17:04
*** TheJulia has joined #openstack-meeting-317:04
* BadCub_ too17:04
devanandaand BadCub_ volunteered to help me - mostly to help around communicating and keeping launchpad up to date17:05
devanandasince I don't check on it often enough17:05
devanandaso I wanted to (re)announce that :)17:05
devanandathat's all from me - any other announces?17:05
NobodyCam:) Thank you BadCub_ :)17:05
* BadCub_ will be digging deeper into that this week :-)17:05
devanandaok - moving on17:06
devananda#topic status report17:06
*** openstack changes topic to "status report (Meeting topic: ironic)"17:06
wanyendeva, some of the approved specs are not on kilo3 launchpad yet17:06
devanandawanyen: yes, BadCub_ is aware. please ping him (after the meeting) to update those17:06
NobodyCamwanyen: can we #link thouse to BadCub_17:06
wanyenwill do17:07
NobodyCam#link https://etherpad.openstack.org/p/IronicWhiteBoard <- for status reports17:07
*** mrmartin has quit IRC17:07
devanandajroll, JayF: quick update on IPA - I was at the tripleo sprint for a couple days last week, and hope that I made it clear we're switching to IPA17:08
*** eghobo has joined #openstack-meeting-317:08
*** jfjoly has left #openstack-meeting-317:08
devanandathe only blocker for them was iSCSI-based deploy support17:08
devanandaI think ya'll were working with lucas on that -- so if/when that lands, let's make sure to let #tripleo folks know17:08
jrolldevananda: that's almost done afaik, lucas has been working on it17:08
NobodyCamwhich lucas has been working on17:08
jrollthat's part of the switch to IPA17:08
jrollok17:08
devanandayea17:09
jrollwe aren't switching without that, so it's not really a blocker17:09
devanandai mean that is what blocked tripleo from switching17:09
*** lucasagomes has joined #openstack-meeting-317:09
lucasagomeso/17:09
jlvillalo/17:09
jroll#link https://review.openstack.org/#/c/155727/17:09
dtantsurlucasagomes, we've assigned everything to you, thanks17:10
jrolliscsi/ipa review ^17:10
devanandalucasagomes: ohhai! I was just talking about adding iSCSI support to IPA17:10
NobodyCamlucasagomes: how is the iscsi support for IPa going?17:10
lucasagomessorry I'm late, was looking into a problem here17:10
lucasagomesNobodyCam, devananda jroll so it works :) but we need to bump the memory on gate17:10
jrollya17:10
* jroll reviews17:10
devanandalucasagomes: ah right. in the tempest serial job17:11
NobodyCamlucasagomes: what do we need to bump to17:11
lucasagomesthere's only on problem, as we are using the same PXE config file for both IPA and normal ramdisk17:11
lucasagomesI had to remove the rootfstype=ramfs from the PXE17:11
devanandalucasagomes: that puts us in a pickle -- we'll have to have support for DIB for the tempest parallel job, then17:11
lucasagomesbut that makes it use tempfs and the default ramdisk will need more ram too :(17:11
lucasagomesdevananda, yeah, I was thinking about passing that option to the parallel job17:11
lucasagomesas append_pxe_config_option17:11
lucasagomesand document that the it can be done for the bash ramdisk17:12
lucasagomesdevananda, and run the parallel job with the bash ramdisk17:12
jrollseems reasonable to me17:12
naohirotI'd like to know core team's status of iRMC review, https://review.openstack.org/#/c/146803/ and https://review.openstack.org/#/c/134865/17:12
devanandastill bothers me that we don't have a means to drop support for the bash ramdisk if we keep the parallel job17:13
devanandabut let's do it, because we already test both, and this is still better17:13
lucasagomesdevananda, yeah :/ I don't have a solution for that, it have to go to infra17:13
devanandaBadCub_: can you add naohirot's links there to the hey-lets-get-some-reviews list?17:13
wanyenis there any plan to add ubuntu support for ipa dib element17:13
jrollwanyen: I believe (but may be wrong) that the goal is to drop DIB17:14
lucasagomeswanyen, not from me, but IPA is just a service like any other. It could be added17:14
lucasagomesjroll, I'm not assuming that, not yet at least17:14
naohirotdevananda: both updated more than 20 times each and there is no issue to be discussed remained.17:14
jrolllucasagomes: maybe that's just my goal :)17:14
lucasagomesjroll, heh yeah, I mean, the tool that builds the ramdisk is at the end not very relevant for us17:14
devanandajroll: we're not necessarily dropping DIB itself - just its init-style ramdisk17:14
jrollright, right17:15
devanandajroll: there are still folks who care about DIB as a tool17:15
*** sambetts has joined #openstack-meeting-317:15
devanandaand folks care about using iSCSi as a deploy mechanism.17:15
jrollright, ok17:15
lucasagomesdtantsur, lol just read ur message now. Oh noes everything is too much :)17:15
* jroll digresses17:15
lucasagomesdevananda, just a point here17:15
lucasagomeswe still using ISCSI with IPA17:16
*** carl_baldwin has quit IRC17:16
lucasagomesI think that's important because that's the only way to deploy without using swift17:16
*** eghobo has quit IRC17:16
lucasagomesso it should continue17:16
devanandalucasagomes: yes17:16
lucasagomesIMHO17:16
NobodyCamyes17:16
*** MarkAtwood_ has joined #openstack-meeting-317:16
jrolltotally agree17:17
devanandalucasagomes: oh, we are definitley NOT removing the iscsi-based deploy mechanism17:17
lucasagomescool :) just making sure17:17
devanandaif i wasn't clear, I'll restate17:17
devanandawe need the iSCSI-based deploy as one option, and the fetch-from-swift as another17:17
lucasagomes+117:17
NobodyCam:)17:17
devanandathere are users/operators who want to use coreos to build the ramdisk, and others who want to use DIB17:18
NishaNobodyCam, devananda so if any changes required in DIB for any ironic features they will be considered/supported?17:18
lucasagomesso yeah, I have to rebase the patchs in Ironic for IPA. It's now failing gate due the memory problem I pointed17:18
devanandawe should allow both to continue17:18
lucasagomesbut should be good. We need this merged: /me getting the link17:18
devanandahowever - the particular "init" style ramdisk which is built by diskimage-builder/ramdisk-image-create -- no one has any particular feelings for that _tool_17:18
lucasagomes#link https://review.openstack.org/#/c/158251/17:18
*** seizadi has quit IRC17:19
*** seizadi has joined #openstack-meeting-317:19
devanandaNisha: that's very vague. can you be more specific?17:19
NobodyCamBadCub_: please add lucasagomes' link to the list too :)17:19
BadCub_NobodyCam will do!17:20
Nishadevananda, like for secure boot it requires changes in DIB to build signed iso and images17:20
stendulkerdevananda: There are DIB changes required to iso element in DIB to support secure boot. Would that be upported?17:20
devanandalucasagomes: ack, ty. I'll look later. would also like to get adam_g to weigh in on that17:20
lucasagomesdevananda, cool yeah I've added u and adam_g to the reviewer list17:20
jrollthis is going fairly off-topic, but as a note, if we can figure out a good way to pass an authenticated glance URL to the agent, we could consider dropping iscsi deploys (not sure what other implications there may be)17:20
devanandaNisha: signed instance image? or signed deploy image?17:20
devanandajroll: nope. we need to keep iscsi-based deploys.17:21
lucasagomesjroll, keystone v3 trusts17:21
Nishasigned deploy iso17:21
stendulkerdevananda: Signed instance images17:21
devanandajroll: that's waaay off topic, btw17:21
devanandaNisha: stendulker: which is it? :)17:21
lucasagomesjroll, but also we are making glance optional by only requiring a http url17:21
lucasagomesso that would do that too17:21
jrolldevananda: I know it's off topic, let's talk later; just thinking out loud17:21
stendulkerdevananda: https://review.openstack.org/#/c/153987/17:21
devanandaNisha: stendulker: also I did not say anything about dropping DIB support, so I dont understand why you're both asking this17:22
dtantsurlet's not go too off-topic, we're still in subteam reports17:22
devanandayea ...17:22
*** baoli has quit IRC17:22
devanandaand we're over our 10 minute cap for that17:22
devanandaalso, it didn't seem like we actually had any subteam reports. *shrug*17:22
stendulkerdevananda: We felt its support getting dropped... my mistake.17:22
*** baoli has joined #openstack-meeting-317:22
devananda#topic K3 priorities17:23
*** openstack changes topic to "K3 priorities (Meeting topic: ironic)"17:23
devanandawho put this on the agenda? there's no name or link ...17:23
NobodyCamoh sorry that was me17:23
NobodyCamjust before the meeting17:23
*** marun has joined #openstack-meeting-317:23
devanandaI mean, we should talk about it, but I wasn't prepared17:23
wanyendeva, I addded iLO driver status17:23
jrollit was last minute17:23
NobodyCamnor I17:23
*** baoli has quit IRC17:23
devanandaNobodyCam: oh you ninja'd it :p17:23
jrollwe can punt on it17:23
devananda#undo17:24
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x2db4310>17:24
NobodyCamI would like to take about open spec reviews17:24
devananda#topic chassis discovery tool17:24
*** openstack changes topic to "chassis discovery tool (Meeting topic: ironic)"17:24
*** rcarrillocruz has left #openstack-meeting-317:24
rlooI wanted to know if there were any specs that were K3 priorities, to get approved before the deadline17:24
jrollI just think from now til end of cycle we should cover priorities and see where we're at17:24
*** baoli has joined #openstack-meeting-317:24
devanandalet's honor the meeting format17:24
devanandaand get to K3 priorities at the end17:24
NobodyCamlol we can come back to that in OD17:24
devanandasandhya: hi!17:24
sandhyahi devananda...17:24
*** MaxV has quit IRC17:25
devanandasandhya: do you have a summary prepared?17:25
devanandasandhya: if not, I can try to type fast17:25
sandhyaI added the chassis discovery tool blueprint discussion to17:25
NobodyCam#link https://review.openstack.org/#/c/134866/17:25
*** stendulker_ has joined #openstack-meeting-317:26
*** baoli has quit IRC17:26
sandhyaThe blueprint started with a plan initially. And then certain complexities came forth and we decided to do it as a tool17:26
devanandaI like the tool approach17:26
*** baoli has joined #openstack-meeting-317:26
dtantsur... in it's own repo17:26
devanandabut I think we need a separate directory for vendor contributed tools17:26
devanandadtantsur: actually, no17:27
lazy_princeso separate dir or repo..?17:27
lucasagomesI think I'm fine with any, but we need to extend the test support to tools/17:27
lucasagomeswe can't run unittests on that dir in the moment17:27
devanandafrom a packager's perspective, it's going to be awkward if all the tools are in one (or more) separate projects17:27
lucasagomeswe need some plumbing17:27
devanandalucasagomes: right. and tools/* is currently for our project mgmt tooling17:27
devanandalike building config files and such17:27
dtantsurfrom a packager perspective we need a proper CLI installed by setup.py17:27
lucasagomesyes17:27
devanandai'd rather put it in contrib/17:27
devanandawhich we dn't have17:27
devanandadtantsur: yup17:28
NobodyCamlucasagomes: I'm not sure we can test all of these types of tools17:28
NobodyCamwe could do unittest17:28
sandhyaSo we create a ironic/contrib dir17:28
lucasagomesyeah, maybe adding a new dir which we could run unittests agains the scripts in the new dir17:28
lucasagomesthat would be fine17:28
devanandadtantsur: except not everyone will want them17:28
lazy_princeso shall we create it and try pushing our patch there..?17:28
jrollI'm skeptical that we want user-contributed scripts packaged in distros, idk17:28
dtantsurdevananda, we won't for example17:28
devanandadtantsur: and upstream doesn't claim the're supported or tested -- because, frankly, we can't17:28
lucasagomesNobodyCam, I see, maybe not all. But, the chassis one is a python script right?17:28
lucasagomesNobodyCam, we should have some test for it17:28
jrolllet's be concrete and think about what other tools might end up in there... deployment tools? management tools? etc17:29
dtantsurdevananda, why are we adding it then? what prevents us from having it separately?17:29
NobodyCamlucasagomes: yes but requires hardware to support it17:29
devanandadtantsur: for non-default, not-everyone-wants-them pyhton scripts, what's wrong with contrib/* and NOT having them installed on the system?17:29
lucasagomesNobodyCam, not for unittests17:29
dtantsurand not putting even more reviews of unknown stuff on folks?17:29
*** stendulker has quit IRC17:29
devanandajroll: tools for chassis discovery of different kinds of hardware17:29
NobodyCamlucasagomes: ++ very true!17:29
dtantsurdevananda, we have to review thing we don't understand and don't care about17:29
devanandajroll: tools for automating some operations that aren't part of our standard17:29
dtantsur(we = some subset of core team)17:30
jrollright, ok.17:30
devanandadtantsur: well. nothing prevents anyone from putting up a separate repo with their tooling in it today17:30
dtantsurdevananda, that's what I did for ironic-discoverd, and that's why I feel strange now17:30
devanandadtantsur: for some reason, sandhya &co want it to be in the main repo. propbably because they think it'll be easier for users to find it that way17:30
dtantsuroh yeah, people read stackforge like "experimental, unsupported and not Official OpenStack (tm)"17:31
NobodyCamI am in favor of a contrib type folder, if for nothing more that they make great examples of how people are using ironic17:31
devanandadtantsur: I know ... and I want to move discoverd off of stackforge as soon as reasonably possible17:31
dtantsurdevananda, but I believe if we bring it under openstack/ namespace and mention it in docs, people will easily discover them17:31
rloodevananda: do you think that anything that goes in the proposed /contrib need to be reviewed like the rest of the ironic code?17:32
NobodyCamthou I do agree that unit tests should be enabled17:32
dtantsurdevananda, I'm ready at any moment (and I wanted to talk to you about it)17:32
dtantsur:)17:32
devanandadtantsur: the difference being discoverd should be official, supported, tested in the gate, and is widely applicable17:32
devanandadtantsur: this, on the other hand, is a vendor-contributed tool for a very narrow set of users17:32
devanandaand not testable i nthe gate17:32
jrollit makes me sad that people won't use things just because it's in stackforge :(17:32
devananda(aside from unit tests)17:32
devanandajroll: ++ me too17:32
dtantsurjroll, I have problems even here at RH :(17:33
jrollugh17:33
devanandadtantsur: that's really sad :(17:33
devanandadtantsur: fwiw, I'm constantly telling people about discoverd17:33
lucasagomesyeah, it's def a big misconception about it17:33
dtantsuroh thanks17:33
lazy_princeif unittests are the only concerns, we can put that as part of the patch being proposed too..We can add unittests as well for the tool...17:33
sandhyaYes. Unit tests will be enabled. A fake discovery driver that can be plugged in for the tool to run.17:33
jlvillalSo contrib/XXXXX/some_file.py    Should there be an XXXXXX and if so, would need a naming convention.17:33
jrollrandom thought: would this fit into discoverd?17:34
* jroll ducks17:34
dtantsurcontrib/ sounds a tiny bit better, though I still won't feel easy approving changes17:34
NobodyCamjlvillal: are you thinking XXXXX is per vendor?17:34
lazy_princejlvillal: so you mean a spec for the naming convention..17:34
*** mestery has quit IRC17:34
dtantsurjroll, I don't have vendor drivers there for now :)17:34
jlvillalNobodyCam: That was my first thought.  But not sure.17:34
jrollNobodyCam: let's *not* put vendor names in our repo :/17:35
*** mestery has joined #openstack-meeting-317:35
*** SumitNaiksatam has quit IRC17:35
jrollI never want "rackspace" to show up in the ironic tree17:35
NobodyCamthat what I was thinking17:35
* 43UABVQBF wonders why do we have chassis concept in Ironic 17:35
*** devvesa has quit IRC17:35
dtantsurgood question arrived ^^^17:35
devanandaheh yea17:35
lucasagomes43UABVQBF, to group nodes, but yeah we are not actually using it very well yet17:35
devanandaI've been suggesting we remove it for >6mo17:35
jrollI've heard it's useful for blades as well17:35
43UABVQBFlucasagomes: it was me17:35
jrollI'd be fine with removing it17:35
devananda43UABVQBF: who's you?17:36
43UABVQBFoh it's me rameshg87. for some reason name is not coming17:36
lucasagomeslol17:36
jrollheh17:36
devanandaheh17:36
dtantsurwow17:36
NobodyCamahh17:36
devanandahi ramesh :)17:36
43UABVQBFhello devananda :)17:36
devanandaso, I'd _love_ to remove chassis entirely from ironic17:36
*** SumitNaiksatam has joined #openstack-meeting-317:36
*** ChuckC_ has quit IRC17:36
devanandahowever we need to provide some mechanism to group nodes17:36
devanandaand no one's done that work yet17:36
jroll... do we? why?17:36
lucasagomesyeah why? I mean I would rather extend it's use17:37
dtantsurwhat about having tags?17:37
devanandadtantsur: ++17:37
devanandawe're also now pretty far off topic17:37
jrollnode.extra works well for us to do things like "which rack is this in"17:37
dtantsuroh yeah17:37
devanandaso back to topic17:37
devanandaI'll summarize17:37
devananda- we have the concept of chassis in tree today, but aren't actually using it anywhere17:37
NobodyCamthis tool can / will make use of this concept17:38
dtantsurpeople will beat me up now, but can we bump it to L? with the decision of whether we're dropping chassis or not...17:38
devanandawhat NobodyCam said :)17:38
NobodyCamI like the idea of a contrib folder17:38
*** rameshg871 has joined #openstack-meeting-317:38
devananda- we don't have a designated place for vendors, or anyone else ,to contribute "useful" tools17:39
NobodyCamThe concern I do have is ATC statuc for it17:39
*** jckasper has quit IRC17:39
devananda(for some definition of useful that is not clear)17:39
*** rameshg871 is now known as got17:39
NobodyCamI would like to exclude atc status for that folder.. .if such could be done17:39
*** got is now known as rameshg87_17:39
devanandaNobodyCam: interesting. so if we put it in a repo on stackforge, AND said that repo is part of ironic, the net effect is the same17:39
devanandaNobodyCam: nope. can't be done17:39
NobodyCamahh17:39
jrolldo we actually care about atc status things? :|17:40
devanandaNobodyCam: th eonly way to do that is to push it to stackforge and NOT say it is part of hte ironic project17:40
dtantsurmy concern is review throughput17:40
devanandajroll: I do. but I also think this _should_ grant ATC status.17:40
NobodyCamwhich would MORE harmfull imho17:40
rloo++ with dtantsur17:40
jrollhuh, ok17:40
devanandathis is clearly coming from a team of people who use and contribute regularly to ironic17:40
* naohirot what is ATC?17:40
dtantsurI'm afraid of getting more and more reviews of stuff I don't remotely understand...17:40
devanandawhy on earth would we want to exclude that from ATC?17:40
devanandanaohirot: active technical contributor. it means you have voting rights in elections and a free pass t othe design summit17:41
lucasagomesnaohirot, active technical contributor17:41
NobodyCam:-p17:41
naohirotthanks :)17:41
devanandadtantsur: ahhh. so we need to trust driver authors to know their own code17:41
devanandadtantsur: and driver authors need to start ponying up third-party CI17:41
devanandadtantsur: if the core team doesn't trust driver authors, we have huge problems as a community17:42
rloodevananda: so if we trust driver authors to know their own code, there isn't any need to review their patches?17:42
NobodyCamdevananda: ++17:42
dtantsurdevananda, if we don't really review it, what's the use of having in-tree?17:42
devanandadtantsur: also we're absolutely going to get more drivers being contributed for hardware that none of us remotely understand17:42
lucasagomesyeah, we still have to review it for code styles etc17:42
devanandalike Cray supercomputers17:42
dtantsurdevananda, drivers are necessary evil IMO17:42
jrolllucasagomes: that's a job for computers :/17:42
*** mwang2 has joined #openstack-meeting-317:43
devanandadtantsur: they're not evil. they are the reason I'm working on this17:43
lucasagomesjroll, we can add a lot of hacking rules :D17:43
NobodyCammy understanding is that reviews for this folder would have a less strick review criteria17:43
rameshg87_vendors can abstract most of their hardware related stuff in their own module and leave little to ironic17:43
lucasagomesI mean, we still have to look at the code, idk, I don't wanna blind merge it. I want to see if there's something malicious17:43
dtantsurrameshg87_, ++17:43
lucasagomesor a dependncy on a non f/oss tool17:43
sandhyaThe tool will be generic. I can probably push the code for it. It will have a base discovery class that can be implemented by drivers.17:43
devanandalucasagomes: right17:44
jrollwhoa17:44
dtantsursandhya, which drivers? I don't see real opportunity for now (maybe FUJITSU?)17:44
devanandasandhya: eh?17:44
jrollnow we're talking about a contrib plugin framework?17:44
jrollwhoaaa.17:44
dtantsurno frameworks please17:44
* devananda is in the whooooaa boat with jroll17:44
*** alexsyip has joined #openstack-meeting-317:44
dtantsurif we're going to have plugins for contrib tools, we'd go insane soon17:44
jrollthis screams separate repo to me at this point17:45
*** ChuckC has joined #openstack-meeting-317:45
lucasagomesyeah for a generic thing17:45
lucasagomeseither driver vendor passthru17:45
lucasagomessince it already abstract it per driver17:45
dtantsurif we're talking about a generic mechanism, let's introduce an API in L cycle (or vendor passthru now)17:45
lucasagomesor a separated repo17:45
*** mwang2 has quit IRC17:45
devanandasandhya: if you're going to make it general enough to have a plugin framework for additional drivers, it's really much more than I had thought17:45
*** mwang2 has joined #openstack-meeting-317:45
NobodyCamwait is this a simple tool or a framwork.17:45
devanandaI need to time box this discussion17:46
lucasagomesdevananda, driver vendor passthru? It's already kinda like a abstraction for driver specific code17:46
*** Sukhdev has joined #openstack-meeting-317:46
lazy_princeits a framework..17:46
devanandasince we have 15 minutes left and two more large topics17:46
* dtantsur votes for vendor passthru17:46
lucasagomesok move on then17:46
* jroll votes for voting on gerrit17:46
lucasagomesjroll, +117:46
NobodyCamlucasagomes: devananda: ++ move on and come back17:46
devananda#action devananda to re-review the chassis discovery tool code in depth17:46
sandhyaYes, it is a generic framework. I will push the code...17:46
*** salv-orlando has joined #openstack-meeting-317:46
devanandasandhya: thanks. I'll take a look today17:46
lazy_princewill vendor passthrough let mw enroll a new server in ironic.. if so, we will look into it and come-back...17:47
devananda#topic passing capabilities from nova to ironic17:47
*** openstack changes topic to "passing capabilities from nova to ironic (Meeting topic: ironic)"17:47
rameshg87_i am here17:47
rameshg87_this is regarding how capabilities can be passed to Ironic with the current changes in nova that got recently merged17:47
rameshg87_i know this has been discussed many times in last week, and hardware/driver capabilities will be attempted in a better way in L release17:47
rameshg87_this is just a proposal on how it can be done for kilo with the nova patch that got merged with minimal/no changes17:47
rameshg87_i have put up a small spec for it - https://review.openstack.org/#/c/158243/17:47
rameshg87_we may ask deployers to configure and use the capabilities in the way mentioned in the spec for K release17:47
rameshg87_all please have a look at spec17:47
NobodyCam#link https://review.openstack.org/#/c/15824317:47
rameshg87_mainly wanted to bring out this much. ready to take more questions :)17:47
* lucasagomes adds to his todo list17:48
devanandarameshg87_: iiuc, we had originally approved a spec whereby nova would pass only a small set of rules to ironic, but then the code which landed in nova passes EVERYTHING down17:48
devanandarameshg87_: so now ironic has to take on the responsibility of parsing that17:48
devanandarameshg87_: is that correct?17:48
rameshg87_devananda: yeah.17:48
rloowondering why this spec isn't a developer doc17:48
*** egallen has quit IRC17:48
Nishadevananda, yes17:48
NobodyCamrameshg87_: do you have the link to the nova spec that landed17:48
rameshg87_devananda: but in my opinion ironic doesn't need to actually care about parsing everything17:48
devanandarameshg87_: ok, i see17:48
rameshg87_NobodyCam: it's within the ironic spec17:48
rameshg87_devananda: i have put out my reasons in the spec.17:49
NobodyCamack17:49
devananda#link https://review.openstack.org/#/c/141012/17:49
devanandathat's the nova code which landed17:49
rameshg87_devananda: it is more of an agreement from ironic on how they can make use of capabilities for scheduling with the changing in K release17:49
NobodyCamthank you devananda :)17:49
devanandarameshg87_: great, thanks for bringing it up!17:49
jrollrloo: I think turning this into a dev doc might be the goal17:49
NobodyCam*10 minutes*17:50
devanandaok, moving on17:50
rameshg87_yeah, i would contents of this spec will land into docs17:50
devananda#topic K3 priorities17:50
*** openstack changes topic to "K3 priorities (Meeting topic: ironic)"17:50
devanandafirst off, I know that LP doesn't match the list of approved specs17:50
devanandaBadCub_ and I will sort that out soon (today I hope)17:51
NobodyCamNot to bring it up as a topic now. but I would folks to think about maybe moving the FF deadline up next cycle17:51
devanandaNobodyCam: yea... I agree17:51
devanandaI'll bring that up with ttx at the summit (and he'll probably see the ping here too)17:51
NobodyCam:)17:51
devanandaas a suggestion for the general timeline17:51
dtantsurproposal freeze or feature freeze?17:51
dtantsur(I would like the former to be moved)17:52
BadCub_devananda that sounds good17:52
rlooif the latter is moved, the former should probably be too17:52
NobodyCamdtantsur: maybe both. but I see PF for sure17:52
devanandaproposal freeze definitely should be sooner, like K217:52
*** coolsvap is now known as coolsvap_17:52
devanandaso a question for everyone17:52
NobodyCamdevananda: ++17:52
devanandalast cycle, I used a google spreadsheet towards the end of the cycle17:53
*** sandhya has quit IRC17:53
devanandato coordinate what we were reviewing17:53
devanandahow'd that work? should I do that again?17:53
jrollmy two cents: code freezes make me sad17:53
NobodyCam#link https://docs.google.com/spreadsheets/d/1Hxyfy60hN_Fit0b-plsPzK6yW3ePQC5IfwuzJwltlbo/edit#gid=160497010917:53
NobodyCamdevananda: ++ it worked for me...17:53
devanandajroll: coordinated release makes me sad17:53
dtantsurworked for me too17:53
jrolldevananda: ++17:53
*** yolanda has left #openstack-meeting-317:53
*** Piet has quit IRC17:53
lucasagomesdevananda, ++17:54
jrollalso, yeah, I seem to remember that doc being helpful17:54
devanandajroll: what if services were released like clients -- when ever we want?17:54
jrolldevananda: then things would be more sane, and also infra would ragequit17:54
jroll:P17:54
devanandaok - so BadCub_ and I will work on updating the spreadsheet17:54
lucasagomesheh17:54
devananda#link https://docs.google.com/spreadsheets/d/1Hxyfy60hN_Fit0b-plsPzK6yW3ePQC5IfwuzJwltlbo17:54
devanandajroll: actually infra doesn't care17:55
devanandajroll: sorry - they do care. I think they would love it17:55
NobodyCam% minutes17:55
NobodyCam5 even17:55
devanandait's downstream distros that want coordinated releases17:55
jrolldevananda: twas a joke, I think the move would be difficult but after that things would be better17:55
devanandabut in a big tent, it's probably going to go away, or at least become a lot fuzzier ...17:55
*** marun has quit IRC17:55
*** yamahata has joined #openstack-meeting-317:56
* jroll jumps for joy17:56
devanandajroll: so fwiw, the TC has already laid out a framework for more projects to release the way swift does (when ever they want)17:56
lucasagomesnice17:56
jrollo.o link?17:56
NobodyCamoh17:56
dtantsurwow17:56
jrolland going back on topic... let's get that spreadsheet updated and go from there17:56
NobodyCam++17:57
lucasagomes++17:57
dtantsur++17:57
naohirot++17:57
jrollnice ++ train :D17:57
rloo++++17:57
NobodyCamcan we # agree on it17:58
wanyendeva, can you consider raising secure boot fromlow priority to medium?  It's an ilo driver top priority item.17:58
devananda#agree we will again be using a google doc for coordinating review priorities for the rest of this cycle17:58
NobodyCam:)17:58
devananda#topic open discussion17:58
*** openstack changes topic to "open discussion (Meeting topic: ironic)"17:58
dtantsur1 minute of OD :)17:59
NobodyCamlol17:59
* jroll thinks everybody here is doing awesome work. please discuss.17:59
dtantsurjroll ++17:59
NobodyCamjroll: /me seconds that thought17:59
* devananda throws a puppy at jroll17:59
jrollnothing else we're going to agree on in 60 seconds :P17:59
jroll\o/17:59
rloodiscuss on openstack-dev email17:59
* jroll cuddles said puppy17:59
* BadCub_ is happy to be officially part of the gang :-)18:00
rloooh there was that *ED states thingy.18:00
NobodyCamahh a puppy18:00
dtantsurtoo late18:00
devanandarloo: nice timing18:00
lucasagomes:D18:00
NobodyCamlol Thank you everyone18:00
rloo:D18:00
jlvillalrloo: You convinced me on the *ED state thingy :)18:00
dtantsurthanks18:00
devanandathanks all! keep up the good work - I know it's challenging for everyone18:00
*** nelsnelson has quit IRC18:00
devananda#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
NobodyCam:)18:00
openstackMeeting ended Mon Feb 23 18:00:38 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-02-23-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-02-23-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-02-23-17.00.log.html18:00
*** rameshg87_ has left #openstack-meeting-318:00
*** nelsnelson has joined #openstack-meeting-318:01
*** faizan_ has quit IRC18:01
*** lucasagomes has left #openstack-meeting-318:01
*** Yi_ has quit IRC18:01
*** wanyen has quit IRC18:02
*** BadCub has quit IRC18:07
*** BadCub_ has quit IRC18:08
*** 43UABVQBF has quit IRC18:08
*** david-lyle_afk is now known as david-lyle18:09
*** lazy_prince is now known as killer_prince18:09
*** ChuckC has quit IRC18:11
*** stendulker_ has quit IRC18:15
*** dtantsur is now known as dtantsur|afk18:16
*** naohirot has quit IRC18:17
*** mrmartin has joined #openstack-meeting-318:17
*** ivar-lazzaro has joined #openstack-meeting-318:20
*** ivar-lazzaro has quit IRC18:22
*** ivar-lazzaro has joined #openstack-meeting-318:22
*** dtantsur|afk has left #openstack-meeting-318:23
*** mestery has quit IRC18:24
*** mestery has joined #openstack-meeting-318:25
*** VW_ has quit IRC18:31
*** carl_baldwin has joined #openstack-meeting-318:32
*** eghobo has joined #openstack-meeting-318:33
*** mestery has quit IRC18:34
*** mestery has joined #openstack-meeting-318:38
*** ivar-laz_ has joined #openstack-meeting-318:38
*** melwitt has joined #openstack-meeting-318:39
*** ivar-laz_ has quit IRC18:39
*** etoews has quit IRC18:39
*** ivar-laz_ has joined #openstack-meeting-318:40
*** ivar-laz_ has quit IRC18:40
*** ivar-laz_ has joined #openstack-meeting-318:41
*** egallen has joined #openstack-meeting-318:41
*** egallen has quit IRC18:41
*** ivar-lazzaro has quit IRC18:41
*** ivar-laz_ has quit IRC18:42
*** marun has joined #openstack-meeting-318:42
*** ivar-lazzaro has joined #openstack-meeting-318:42
*** etoews has joined #openstack-meeting-318:46
*** jckasper has joined #openstack-meeting-318:55
*** SumitNaiksatam has quit IRC18:56
*** marun has quit IRC18:57
*** marun has joined #openstack-meeting-319:01
*** Yi has joined #openstack-meeting-319:02
*** marun has quit IRC19:06
*** Yi has quit IRC19:06
*** sbalukoff has joined #openstack-meeting-319:10
*** mrunge has quit IRC19:10
*** Rockyg has joined #openstack-meeting-319:17
*** SumitNaiksatam has joined #openstack-meeting-319:19
*** Yi has joined #openstack-meeting-319:21
*** alexpilotti has quit IRC19:24
*** VW_ has joined #openstack-meeting-319:25
*** Piet has joined #openstack-meeting-319:29
*** marun has joined #openstack-meeting-319:33
*** johnthetubaguy is now known as zz_johnthetubagu19:35
*** mestery_ has joined #openstack-meeting-319:38
*** mestery has quit IRC19:38
*** SridharRamaswamy has joined #openstack-meeting-319:39
*** salv-orlando has quit IRC19:40
*** bauzas has quit IRC19:43
*** marun has quit IRC19:43
*** marun has joined #openstack-meeting-319:44
*** Sukhdev has quit IRC19:45
*** Nisha has quit IRC19:46
*** sahid has quit IRC19:46
*** ivar-lazzaro has quit IRC19:54
*** ivar-lazzaro has joined #openstack-meeting-319:54
*** VW_ has quit IRC19:56
*** VW_ has joined #openstack-meeting-319:57
*** bpokorny_ has joined #openstack-meeting-320:00
*** bpokorny has quit IRC20:02
*** markvoelker has joined #openstack-meeting-320:07
*** mestery_ has quit IRC20:09
*** Rockyg has quit IRC20:09
*** megm_ has joined #openstack-meeting-320:09
*** megm has quit IRC20:10
*** mestery has joined #openstack-meeting-320:11
*** clu_ has joined #openstack-meeting-320:13
*** zz_johnthetubagu is now known as johnthetubaguy20:17
*** ivar-lazzaro has quit IRC20:20
*** matrohon has joined #openstack-meeting-320:21
*** ivar-lazzaro has joined #openstack-meeting-320:21
*** baoli has quit IRC20:22
*** ivar-lazzaro has quit IRC20:22
*** ivar-lazzaro has joined #openstack-meeting-320:23
*** eghobo has quit IRC20:23
*** matrohon has quit IRC20:29
*** Piet has quit IRC20:31
*** sergef has joined #openstack-meeting-320:34
*** salv-orlando has joined #openstack-meeting-320:41
*** matrohon has joined #openstack-meeting-320:43
*** baoli has joined #openstack-meeting-320:44
*** thomasem has quit IRC20:47
*** marun has quit IRC20:49
*** markvoelker has quit IRC20:51
*** marun has joined #openstack-meeting-320:52
*** VW__ has joined #openstack-meeting-320:56
*** VW_ has quit IRC20:59
*** hichihara has joined #openstack-meeting-320:59
*** lblanchard has quit IRC21:00
*** bknudson has quit IRC21:05
*** jckasper has quit IRC21:08
*** lnr has joined #openstack-meeting-321:09
*** mestery has quit IRC21:10
*** mestery has joined #openstack-meeting-321:11
*** salv-orlando has quit IRC21:12
*** marun has quit IRC21:13
*** markvoelker has joined #openstack-meeting-321:15
*** markvoelker has quit IRC21:15
*** markvoelker has joined #openstack-meeting-321:16
*** salv-orlando has joined #openstack-meeting-321:17
*** thomasem has joined #openstack-meeting-321:20
*** egallen has joined #openstack-meeting-321:23
*** watanabe_isao has joined #openstack-meeting-321:23
*** ChuckC has joined #openstack-meeting-321:25
*** baoli has quit IRC21:27
*** matrohon has quit IRC21:27
*** lnr has quit IRC21:31
*** lnr has joined #openstack-meeting-321:32
*** lnr has left #openstack-meeting-321:33
*** pkoniszewski has joined #openstack-meeting-321:33
*** matrohon has joined #openstack-meeting-321:35
*** VW__ has quit IRC21:41
*** VW_ has joined #openstack-meeting-321:41
*** mrmartin has quit IRC21:43
*** egallen has quit IRC21:45
*** seizadi has quit IRC21:47
*** egallen has joined #openstack-meeting-321:49
*** MaxV has joined #openstack-meeting-321:50
*** mestery has quit IRC21:51
*** sergef has quit IRC21:51
*** VW_ has quit IRC21:58
*** VW_ has joined #openstack-meeting-321:58
*** bpokorny has joined #openstack-meeting-322:02
*** bpokorny_ has quit IRC22:05
*** egallen has quit IRC22:05
*** baoli has joined #openstack-meeting-322:05
*** thangp has quit IRC22:11
*** romcheg has quit IRC22:12
*** romcheg has joined #openstack-meeting-322:17
*** sarob has quit IRC22:23
*** bpokorny_ has joined #openstack-meeting-322:23
*** VW_ has quit IRC22:24
*** VW_ has joined #openstack-meeting-322:25
*** bpokorny has quit IRC22:26
*** watanabe_isao has quit IRC22:27
*** mattfarina has quit IRC22:28
*** rloo has left #openstack-meeting-322:30
*** matrohon has quit IRC22:36
*** seizadi has joined #openstack-meeting-322:37
*** johnthetubaguy is now known as zz_johnthetubagu22:44
*** etoews has quit IRC22:44
*** alexsyip has quit IRC22:48
*** VW_ has quit IRC22:51
*** alexsyip has joined #openstack-meeting-322:53
*** thomasem has quit IRC22:54
*** sarob has joined #openstack-meeting-322:55
*** VW_ has joined #openstack-meeting-323:03
*** thomasem has joined #openstack-meeting-323:03
*** thomasem has quit IRC23:03
*** thomasem has joined #openstack-meeting-323:04
*** romcheg has quit IRC23:08
*** romcheg has joined #openstack-meeting-323:09
*** romcheg has quit IRC23:09
*** baoli has quit IRC23:11
*** devlaps has quit IRC23:14
*** devlaps has joined #openstack-meeting-323:14
*** sarob has quit IRC23:14
*** sarob has joined #openstack-meeting-323:16
*** baoli has joined #openstack-meeting-323:17
*** MaxV has quit IRC23:17
*** sarob has quit IRC23:19
*** sarob has joined #openstack-meeting-323:20
*** sarob has quit IRC23:24
*** pkoniszewski has quit IRC23:28
*** baoli has quit IRC23:30
*** watanabe_isao has joined #openstack-meeting-323:31
*** peristeri has quit IRC23:34
*** sbalukoff has quit IRC23:36
*** alexpilotti has joined #openstack-meeting-323:36
*** carl_baldwin has quit IRC23:37
*** Yi has quit IRC23:41
*** armax has joined #openstack-meeting-323:41
*** ivar-laz_ has joined #openstack-meeting-323:42
*** ivar-lazzaro has quit IRC23:45
*** salv-orlando has quit IRC23:45
*** carl_baldwin has joined #openstack-meeting-323:47
*** VW_ has quit IRC23:47
*** sbalukoff has joined #openstack-meeting-323:48
*** VW_ has joined #openstack-meeting-323:48
*** sbalukoff has quit IRC23:54
*** MarkAtwood_ has quit IRC23:56
*** MarkAtwood has quit IRC23:57
*** melwitt has quit IRC23:57
*** ivar-laz_ has quit IRC23:58
*** ivar-lazzaro has joined #openstack-meeting-323:59

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