Tuesday, 2015-01-06

*** GheRivero has quit IRC00:03
*** fischerw has quit IRC00:07
*** fischerw has joined #openstack-meeting-300:07
*** carl_baldwin has quit IRC00:09
*** banix has quit IRC00:12
*** fischerw has quit IRC00:14
*** GheRivero has joined #openstack-meeting-300:15
*** ivar-lazzaro has quit IRC00:22
*** Guest60568 is now known as beagles00:25
*** wuhg has joined #openstack-meeting-300:25
*** ivar-lazzaro has joined #openstack-meeting-300:26
*** sarob has quit IRC00:27
*** markmcclain has quit IRC00:27
*** ChuckC has quit IRC00:32
*** david-lyle has joined #openstack-meeting-300:33
*** david-ly_ has joined #openstack-meeting-300:36
*** david-ly_ has quit IRC00:41
*** markmcclain has joined #openstack-meeting-300:59
*** ChuckC has joined #openstack-meeting-301:03
*** JAHoagie has quit IRC01:07
*** sunny__ has quit IRC01:09
*** GheRivero has quit IRC01:10
*** GheRivero has joined #openstack-meeting-301:11
*** markmcclain has quit IRC01:15
*** baoli has joined #openstack-meeting-301:15
*** markmcclain has joined #openstack-meeting-301:18
*** GheRivero has quit IRC01:20
*** salv-orlando has quit IRC01:21
*** markmcclain has quit IRC01:21
*** gduan has quit IRC01:22
*** garyduan has joined #openstack-meeting-301:23
*** banix has joined #openstack-meeting-301:24
*** GheRivero has joined #openstack-meeting-301:27
*** banix has quit IRC01:29
*** ivar-lazzaro has quit IRC01:34
*** baoli has quit IRC01:36
*** baoli has joined #openstack-meeting-301:37
*** baoli has quit IRC01:43
*** markmcclain has joined #openstack-meeting-301:45
*** stanzgy has joined #openstack-meeting-301:47
*** yamahata has quit IRC01:51
*** baoli has joined #openstack-meeting-301:52
*** markmcclain has quit IRC01:57
*** ChuckC has quit IRC02:07
*** alexsyip has quit IRC02:08
*** GheRivero has quit IRC02:09
*** SumitNaiksatam has quit IRC02:10
*** GheRivero has joined #openstack-meeting-302:15
*** ChuckC has joined #openstack-meeting-302:18
*** bpokorny has quit IRC02:24
*** eghobo has quit IRC02:27
*** baoli_ has joined #openstack-meeting-302:37
*** baoli__ has joined #openstack-meeting-302:39
*** baoli has quit IRC02:41
*** sigmavirus24 is now known as sigmavirus24_awa02:42
*** baoli_ has quit IRC02:42
*** vkmc has quit IRC03:04
*** sigmavirus24_awa is now known as sigmavirus2403:04
*** salv-orlando has joined #openstack-meeting-303:07
*** salv-orlando has quit IRC03:10
*** salv-orlando has joined #openstack-meeting-303:10
*** marun has quit IRC03:15
*** salv-orlando has quit IRC03:16
*** salv-orlando has joined #openstack-meeting-303:16
*** carl_baldwin has joined #openstack-meeting-303:20
*** nelsnelson has quit IRC03:24
*** david-lyle has quit IRC03:39
*** SumitNaiksatam has joined #openstack-meeting-303:40
*** baoli__ has quit IRC03:40
*** takadayuiko has joined #openstack-meeting-303:43
*** david-lyle has joined #openstack-meeting-303:45
*** david-lyle has quit IRC03:46
*** david-lyle has joined #openstack-meeting-303:48
*** VW_ has joined #openstack-meeting-303:53
*** carl_baldwin has quit IRC03:53
*** salv-orlando has quit IRC03:54
*** Longgeek has joined #openstack-meeting-303:56
*** Longgeek has quit IRC03:57
*** ramineni has joined #openstack-meeting-304:01
*** Longgeek has joined #openstack-meeting-304:03
*** naohirot has joined #openstack-meeting-304:04
*** VW_ has quit IRC04:07
*** yamahata has joined #openstack-meeting-304:11
*** JayF has joined #openstack-meeting-304:15
*** marun has joined #openstack-meeting-304:20
*** amotoki has joined #openstack-meeting-304:21
*** hironori has joined #openstack-meeting-304:24
*** sigmavirus24 is now known as sigmavirus24_awa04:24
*** david-lyle is now known as david-lyle_afk04:25
*** hironori has quit IRC04:26
*** shiina has joined #openstack-meeting-304:27
*** shiina has quit IRC04:29
*** hshiina has joined #openstack-meeting-304:30
*** watanabe_isao has joined #openstack-meeting-304:34
*** watanabe_isao has left #openstack-meeting-304:36
*** Nisha has joined #openstack-meeting-304:37
*** watanabe_isao has joined #openstack-meeting-304:37
*** lsmola has quit IRC04:45
*** rameshg87 has joined #openstack-meeting-304:52
*** JAHoagie has joined #openstack-meeting-304:58
*** Haomeng has joined #openstack-meeting-304:59
devanandahi! anyone here for the Ironic meeting?04:59
naohirotdevananda: Hi HNY to all05:00
Haomenghappy new year to all:)05:00
devananda#startmeeting ironic05:00
*** lsmola has joined #openstack-meeting-305:00
openstackMeeting started Tue Jan  6 05: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.05:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:00
*** openstack changes topic to " (Meeting topic: ironic)"05:00
openstackThe meeting name has been set to 'ironic'05:00
NobodyCamhyn all05:00
devanandahappy new year, and good evening/morning/afternoon/other time of day :)05:01
*** wanyen has joined #openstack-meeting-305:01
devanandaas usual, our agenda is up on the wiki here: https://wiki.openstack.org/wiki/Meetings/Ironic05:01
*** lintan has joined #openstack-meeting-305:01
devanandaapologies in advance if I'm typing slower than usual, it's late for me -- but I'm glad to see a couple folks that I don't usually see :)05:02
devananda#chair NobodyCam05:02
openstackCurrent chairs: NobodyCam devananda05:02
devananda#topic announcements05:02
*** openstack changes topic to "announcements (Meeting topic: ironic)"05:02
* NobodyCam will also be slow05:02
devanandaonly announcement for me is just a reminder to folks05:03
devanandathat I've posted details for an early February meetup / sprint to the mailing list05:03
devanandaduring the break, so I wanted to draw attention to it in case anyone missed it05:03
devananda#link http://lists.openstack.org/pipermail/openstack-dev/2014-December/053617.html05:03
devanandaand some further thoughts, since it seems like a lot of US folks may not make it, are posted here05:04
devananda#link http://lists.openstack.org/pipermail/openstack-dev/2014-December/053618.html05:04
NobodyCamare their any details on the SF meetup? like where should I look for a hotel?05:04
wanyenremtoe dial-in is available?05:05
devanandaNobodyCam: no. TBD. I just floated the idea and it seems people liked it, so need to arrange that this week05:05
NobodyCamlol ack :)05:05
devanandawanyen: it will be a developer sprint, not a planning meeting05:05
jrolldevananda: NobodyCam: fwiw, we have plenty of room at our office in soma05:06
jrollI think russell even booked a room, plus we have this big open area we could hack at05:06
jrollfree to use it if you'd like05:06
*** eghobo has joined #openstack-meeting-305:07
devanandajroll: let's iron out the details of that so we can announce at next week's (more US-time-friendly) meeting05:07
jrolldevananda: yep, just a heads up :)05:07
devanandajroll: ack. ty05:07
naohirotdevananda: If I had an issue to be discussed with core members, it it possible to attend SF meeting via WebEX or something?05:07
NobodyCamjroll: with a white board or two too?05:07
jrollNobodyCam: yessir05:07
jrolland TVs for code pairing05:07
naohirotdevananda: I can provide WebEX.05:08
devanandanaohirot: I'm trying specifically to avoid having the sprint be(come) a planning meeting05:08
devanandanaohirot: so if there are design issues, we should try to discuss those via IRC, email, etherpad, etc -- all the usual means05:09
wanyendeva, what will be covered in the sprint?05:09
naohirotdevananda: Yeah, Okay. What does "sprint" mean?05:10
devanandawanyen: it's a sprint - who ever is there will work on writing code for the open specs. or something like that, I hope :)05:10
jrollwrite all the code.05:10
jrollhack the planet05:10
naohirotjroll: I see.05:10
JayFIt's much less interesting than I suspect you all expect it will be :)05:10
devanandaah, i see. I assume everyone knows what a "code sprint" means05:10
devanandalet's move on for now, and come back to this if there's time at the end05:11
devananda#topic subteam status reports05:11
*** openstack changes topic to "subteam status reports (Meeting topic: ironic)"05:11
devananda#link https://etherpad.openstack.org/p/IronicWhiteBoard05:11
devanandahm, bug stats look quite old05:11
devanandaI count 19 NEW bugs right now :(05:12
jroll"dtantsur on PTO/holidays, back on Jan 5th"05:12
jrollhe was in meetings all day today, probably didn't catch a break to count05:12
* devananda makes a note to go do bug triage05:12
Haomengdevananda: yes, I raise some bugs during my testing05:12
lintandevananda: I see some old but high bugs, are these still import for Ironic?05:13
devanandalintan: I suspect they are miscategorized05:13
NobodyCamieek about 20 + NEW bugs05:13
devanandalaunchpad doesn't separate "impact" from "urgency"05:14
jrollat least people are filing them :)05:14
devanandaso we end up with bugs that are high impact but low urgency05:14
jrollwe should poke dtantsur in the morning and see if he wants help, maybe a bug day in the next couple weeks05:14
devanandare-visiting all the bugs and re-assessing them would be good05:15
devanandaprobably some stale, definitely a lot of new ones05:15
devanandawanyen: any updates on third-party CI ?05:15
devananda#info it looks like we still need to get reviews on the iRMC and AMT drivers05:16
wanyendeva: tried to setup 3rd-party CI but found out that we need more hardware.05:16
naohirotdevananda: Yes, please05:16
devananda#info many new bugs, and lots of stale bugs. we should clean this up before kilo-3 (at the latest)05:17
NobodyCamdevananda: code, spec's or both05:17
devanandaNobodyCam: code, it looks like05:17
JayFiirc iRMC has a pending spec05:17
NobodyCamat least one05:17
lintanAMT driver has both....05:18
JayFhttps://review.openstack.org/#/c/134865/ yeah; I've been looking at this. Others should too.05:18
devanandawanyen: hm, I see05:18
devanandaNobodyCam: ok, both it is.05:18
devanandaany other status updates?05:19
JayFI have a patch for IPA we should talk about; but I called it out specifically on the agenda. Other than that nothing notable for IPA05:19
devanandaJayF: ack, I'll make sure we get to it05:20
naohirotJayF: I appreciated your view :)05:20
devanandaok, thanks everyone for keeping the status page up to date!05:20
devanandamoving on ...05:20
devananda#topic new state machine code reviews05:20
*** openstack changes topic to "new state machine code reviews (Meeting topic: ironic)"05:20
devanandaNobodyCam: that's you. well, and me ...05:20
devanandaNobodyCam: but you put it on the agenda :p05:21
NobodyCamI was looking to get eyes on the state machine reviews05:21
* jroll makes a note to review those this week05:22
jrollNobodyCam: what's the topic for those?05:22
NobodyCamI must admit I forgot to look them over today with all the catch up05:22
devananda#link https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:master+topic:bp/new-ironic-state-machine,n,z05:22
JayFjroll: it's linked from agenda05:22
devanandaNobodyCam: I haven't posted a new rev since the break05:22
jrolloh, maybe I should look at the agenda then :P05:22
* jroll thought he was just here for moral support :P05:22
*** chenglch has joined #openstack-meeting-305:23
devanandashort version - these are laying the foundation for the Finite State Machine work that we need to move forward05:23
NobodyCamI will look them over first thing tomorrow over coffee05:23
devanandabut so far, there have been very few reviews on the code I wrote05:23
devanandamostly rloo and NobodyCam, with a few from Shrews05:23
devanandait would be good to have more eyes on it, since it is refactoring some central parts of the ConductorManager05:24
naohirotdevananda: In case of iRMC deploy, is it enough to follow the implementation of https://review.openstack.org/#/c/140883/?05:24
*** k4n0 has joined #openstack-meeting-305:24
devanandanaohirot: excellent question -- this is one reason I'd really like to get more eyes on it, and hopefully land that05:25
naohirotdevananda: I'm wondering  how new state machine affects iRMC deploy implementation.05:25
*** salv-orlando has joined #openstack-meeting-305:25
*** k4n0 has quit IRC05:25
*** eghobo has quit IRC05:26
devanandanaohirot: in my opinion, yes, but other cores must approve of it as well05:26
naohirotdevananda: Yes, of course05:26
devanandaok. moving on because of time05:27
jrollapprove of using process_event() in iRMC? or approve of iRMC following that patch in the chain?05:27
devanandajroll: the implementation pattern. my patches are affecting drivers05:27
jrollok, yeah05:27
devanandajroll: so naturally anyone who is writing a driver now is affected ...05:27
devananda#topic stable branch maintenance05:28
*** openstack changes topic to "stable branch maintenance (Meeting topic: ironic)"05:28
devananda#link http://lists.openstack.org/pipermail/openstack-dev/2014-December/053366.html05:28
*** salv-orlando has quit IRC05:28
jrollnaohirot: assuming that patch goes through as-is, yes, it will follow05:28
devanandaI posted this question to the list last month05:28
devanandashould we officially say we're no longer supporting icehouse?05:28
naohirotjroll: Okay, I got it, thank!05:28
devanandaand how long should we commit to supporting juno?05:29
devanandabut didn't get any replies on the ML05:29
devanandaopinions now, or discuss on the ML ?05:29
*** salv-orlando has joined #openstack-meeting-305:30
NobodyCamI have seen question in channel about Icehouse support at least a few days before the break05:30
jrollwith my trunk-chaser hat on, I don't care much for stable maintenance... I think we should support juno for two cycles like other projects do05:30
*** eghobo has joined #openstack-meeting-305:30
jrollicehouse seems fairly useless to support05:30
devanandajroll: so juno until "L" is released?05:31
jrolldevananda: I guess so, yeah, that's what other integrated projects do, yes?05:31
devanandaalso, fwiw, I think we need adam_g to weigh in on this, as he's been doing the lion's share of stable maint for us so far05:31
devanandaand it'd be great to have >1 person doing that05:31
devanandajroll: yea, generally I think it's 2 cycles after a release05:32
devanandaso that distros and users have a reasonable migration window05:32
devanandawhere reasonable is somehow defined as "one year"05:32
jrollI don't really understand it, but willing to do the right thing :)05:33
devanandajroll: apt-get install05:33
devanandajroll: that's why05:33
NobodyCami would agree with where reasonable is somehow defined as "one year"05:33
jrolldevananda: I know that, I still don't understand :P05:33
devanandajroll: heh :)05:34
JayFI think if distros want Juno maintained for a year, they should help do it :)05:34
NobodyCamlb -s /bin/apt-get /usr/bin/pip05:34
NobodyCamln not lb05:34
jrollJayF: they do, to be fair05:34
JayFI know; it's just I wish we were able to spend all our time on the future instead of the past :)05:35
devanandajroll: hm, but to be precise, they aren't doing stable maint for ironic, afaik05:35
devanandaI can draft something more formal-like and sjhare at the next meeting05:36
devanandaat least no one seems to have initially objected :)05:37
devanandamoving on ..05:37
devananda#topic AMT spec05:37
*** openstack changes topic to "AMT spec (Meeting topic: ironic)"05:37
devanandalintan: hi!05:37
lintanHi all guys05:37
lintanI need your opinions about the design05:37
lintanOne thing is to discuss about where to put amt_boot_device05:38
lintanin driver_info or extra05:38
JayFIf it's driver specific, wouldn't it belong in driver_info?05:39
devanandait shouldn't be exposed to users via either JSON field, though05:39
devanandalintan: i'm not sure why it needs to be stored at all05:40
lintanAMT/vPro only accept the first boot device and ignore the rest if we send multiple _set_boot_device_order requests to AMT nodes.05:40
jrolldevananda: AMT doesn't support persistent=true, and doesn't have a "get boot device" command, AIUI05:40
devanandalintan: the hardware ignores repeated requests?05:40
devanandajroll: right. I think that can be worked around05:41
devanandabut if the hardware only accepts the FIRST one05:41
devanandathen we can't change it before the next reboot05:41
devanandathat's a problem05:41
devanandalintan: is ^ what you mean?05:41
lintandevananda:I mean it doesn't support05:42
jrollI don't see that as a problem, when do you need to change it twice between boots?05:42
jrollmy question is, if you do "set boot device pxe", and then "set boot device pxe", does it pxe boot?05:42
lintanjroll: it does pxe boot in your case05:43
devanandajroll: if I do "set boot device hdd" then "set boot device pxe" then "reboot" -- which one does it boot?05:43
devanandaoops, lintan ^05:43
jrolldevananda: why would you do that05:43
jrollas long as this works: "set boot device hdd" then "reboot" then "set boot device pxe" then "reboot"05:44
jrollshould be fine05:44
* devananda waits for lintan's answer before stating why that would bork things05:44
lintanjroll: but other drives support "set boot device hdd" then "set boot device pxe" then "reboot"05:44
jrollwhen/why do we do that?05:45
devanandaour API exposes set-boot-device, so if a user (for what ever reason) issues such a command manually, it would, i05:45
jrollwhy would you set bootdev to hdd if you're not going to boot from hdd05:45
lintanjroll: another critical concern is for persistent boot05:45
jrollwhich this whole "remember the boot device" doesn't help with05:45
lintanin pxe boot processing, we have two pxe boot05:46
jrolllintan: that's a different issue that can be solved generically, I think05:46
devanandalintan: I'm sad that AMT hardware doesn't support changing this option multiple times05:46
jrollanother point to make here: Haomeng managed to find ipmi hardware that doesn't support persistent=true05:47
devanandalintan: can it be worked around in the hardware somehow, eg. by issuing another command just before hand to "erase" a previous request?05:47
Haomengjroll: YES05:47
jrollwhich means the latter problem isn't just an AMT problem05:47
devanandaoh :(05:47
devanandaok then05:47
Haomengjroll: for some hardware, it ignore persistent=true05:47
devanandathat's awesome05:47
jrollHaomeng: right05:48
jrollso awesome05:48
lintanfor most case it should work right ?05:48
jrollon the plus side, it forces us to solve this generically05:48
jrollmost isn't good enough, unfortunately05:48
devanandaok - lintan, can you propose that as a separate change?05:48
lintanfor persistent issue?05:48
Haomengjroll: I just tested with two machine, not working with pxe set set bootdev persistent=true05:48
devanandaI think we'll need a new table to store "requested but not applied changes"05:48
devanandaor "persistent things we need to set every time"05:49
devanandaor something05:49
jrollHaomeng: yeah, I believe you. hardware is bad.05:49
Haomengjroll: :)05:49
Haomengjroll: maybe:)05:49
NobodyCamdevananda: uggh :(05:50
devanandalintan: I think the general approach you have is fine, but this shouldn't be saved in a JSON field like driver_info or extra05:50
devanandalintan: and it needs to be available for other drivers to leverage as well05:50
wanyenHaomeng, is this the problem for bios or uefi mode?05:50
jrollok, so someone (maybe lintan) should propose a spec to add a table or something to deal with this05:50
Haomengjroll: I understand some hardware does not implement all ipmi stand to support more options such as persistent=true05:50
lintanOK, I am willing to do that05:50
Haomengwanyen: bios mode05:50
wanyenHaomeng, I see.05:51
*** Longgeek has quit IRC05:51
devananda#agreed we need a generic way to store a user-requested persistent boot device settign which has not been applied yet, and then only apply it during the reboot phase05:51
devananda#note this issue affects some IPMI-based hardware as well as AMT hardware05:51
lintanI have another issue for AMT05:51
jrolldo we have time for JayF?05:51
*** JAHoagie has quit IRC05:51
rameshg87devananda, do we expect the user to reboot through Ironic only every time ?05:52
jrolllintan: what's the issue05:52
devanandalintan: we're almost out of time - can you be quick?05:52
lintanDuring PXE deploy processing, the target machine will boot by itself.05:52
JayFNot having time for me is not an option after staying up :)05:52
wanyendeva,for hardware that does support persistent boot then no need to use the table.  So the use of table is optional.  right?05:52
jrollrameshg87: that's an interesting question, I don't think we can expect that, unfortunately :(05:52
lintanAMT Driver has to call ensure_next_boot_device again in_continue_deploy().05:52
jrollwanyen: I think that's irrelevant05:53
devanandawanyen: dunno. we'll discuss that on the relevant spec, when it's proposed05:53
rameshg87jroll, and ironic cli doesn't have an option for reboot or soft-reboot05:53
jrollrameshg87: node-set-power-state reboot (also nova reboot)05:53
rameshg87jroll, oh :D05:53
devanandaok - I am going to need to cap this so we can get to JayF05:53
Haomengdevananda: another one -should ironic support force-delete to follow nova commad?05:53
rameshg87jroll, soft reboot is missing afaik05:53
jrollrameshg87: though both are hard power off, power on05:53
jrollI'd love to add this05:54
* jroll wants to #topic05:54
rameshg87jroll, +1 me too05:54
devananda#note need to discuss this more05:54
devananda#topic breakign change for IPA05:54
*** openstack changes topic to "breakign change for IPA (Meeting topic: ironic)"05:54
devananda#link http://lists.openstack.org/pipermail/openstack-dev/2014-December/053662.html05:54
NobodyCamjroll: you want soft poweroff?05:54
jrollJayF: gogogo05:54
jrollNobodyCam: yes05:54
JayFSo tl;dr: when looking at splitting up our hardware manager into smaller, more sharable pieces, I realized our hardware manager loading didn't work the wqy I expected it to -- or the way josh and I modeled it at the summit05:55
JayFso I proposed https://review.openstack.org/#/c/143193 to allow for multiple simultaneous hardware managers05:55
JayFthe only downside is this would be a breaking-api change for any out of tree hardware managers05:55
JayFOf which; the only one I know exists today is the one I maintain, heh05:55
*** mrmartin has joined #openstack-meeting-305:56
JayFSo I wanted to generally get visibility on this and a general "OK" from the group for doing this05:56
rameshg87JayF, very soon i would like to use this - for raid configuration05:56
devananda#note If you are using Ironic-Python-Agent with an out-of-tree hardware manager, please respond to JayF's email (linked above)05:56
JayFAlso reviews very much appreciated; particularly by those who may want to consume this interface later05:57
jrollI've voiced my opinion to JayF elsewhere, but again here: posted to mailing list, no response, should be ok05:57
devanandarameshg87: is there any reason you will not submit your hardware manager upstream?05:57
rameshg87devananda, there isn't. i will want to submit it to upstream :)05:57
JayFdevananda: you think highly hardware specific managers should go upstream?05:57
devanandaJayF: yes05:58
JayFdevananda: what about in cases (almost all, in cases I've seen) that they require a proprietary tool to work?05:58
jrollI tend to agree05:58
devanandaJayF: if Ironic supports a given vendor's hardware, IPA ought to as well ...05:58
JayFthat's always been what has slowed me down when looking at upstreaming things05:58
rameshg87JayF, adding ironic-agent element in dib solves this05:58
jrollbut when it comes to firmware things, that will almost certainly be downstram in most cases05:58
jrollthough you could just say "requires crappy-vendor-tool.sh"05:59
rameshg87JayF, i can build a ironic-python-agent ramdisk by including my custom element05:59
JayFrameshg87: sure; that's what I do now; but should we ship code that doesn't work without a custom element that we probably couldn't even open source05:59
devanandaif the separation is clean -- custom element is just "include proprietary utility.sh"05:59
devanandaand the interface to taht is in IPA -- I think it's good05:59
jrollrameshg87: it's also straightforward to build IPA with a custom manager without DIB05:59
devanandaJayF: yes. we do that in Ironic today.06:00
devanandaJayF: look at all the third-party drivers06:00
wanyenJayF, iLO teamis interested in adding Proliant hardware manager to IPA06:00
jrolldevananda: so you're ok with IPA shelling out to "utility.sh", where utility.sh is unspecified?06:00
JayFwanyen: rameshg87: The big thing this change (Which you should apparently review) that matters is that you can do small HardwareManager pieces06:00
devanandajroll: or is specified by the hardware manager06:00
JayFi.e. I'd rather see 5 hardware managers for 5 components than a single, large hardware manager targetted at specific hardware mixes06:01
JayFbut that's just my vision :)06:01
rameshg87JayF, sure i will take a look asap06:01
devanandaJayF: ++06:01
JayFThanks all06:01
jrolldevananda: sure, but is quanta-modelxyz-hwmanager ok? this could grow extremely large06:01
jrolland keep in mind everything in tree bloats the ramdisk06:01
jrollI'm not saying we shouldn't, it's just a somewhat hard proiblem to solve06:01
devanandait shouldn't install all the driver's req's all teh time -- that does need to be configurable in some way06:02
devanandaor -- on large platforms, maybe that's fine06:02
NobodyCamwe're over time06:02
devanandaanyway, we're over time06:02
wanyenJayF, the bottomline is to allow vendor to add hardware management functionalitites.  We will take a look at your proposal.06:02
JayFGood meeting, thanks all, see you tomorrow06:02
jrollok, thanks everyone :)06:02
devanandaplease go check out the change / respond on the ML if you're interested in IPA and hardware managers06:02
NobodyCamty all06:02
devanandathanks all! see you next time06:02
Haomengsee you06:02
lintansee you06:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:03
openstackMeeting ended Tue Jan  6 06:02:59 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-01-06-05.00.html06:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-01-06-05.00.txt06:03
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-01-06-05.00.log.html06:03
*** JayF has left #openstack-meeting-306:03
*** takadayuiko has quit IRC06:03
*** chenglch has quit IRC06:06
*** wanyen has quit IRC06:07
*** Longgeek has joined #openstack-meeting-306:09
*** salv-orlando has quit IRC06:11
*** salv-orlando has joined #openstack-meeting-306:13
*** salv-orlando has quit IRC06:20
*** salv-orlando has joined #openstack-meeting-306:22
*** killer_prince is now known as lazy_prince06:24
*** rameshg87 has quit IRC06:26
*** Haomeng has left #openstack-meeting-306:28
*** hshiina has left #openstack-meeting-306:33
*** stanzgy has quit IRC06:36
*** stanzgy has joined #openstack-meeting-306:37
*** ramineni has left #openstack-meeting-306:51
*** reed has quit IRC06:54
*** miguelgrinberg has quit IRC07:23
*** armax has quit IRC07:36
*** iovadia has joined #openstack-meeting-307:41
*** sergef has joined #openstack-meeting-307:45
*** miguelgrinberg has joined #openstack-meeting-307:52
*** sarob has joined #openstack-meeting-307:52
*** belmoreira has joined #openstack-meeting-307:56
*** sahid has joined #openstack-meeting-308:03
*** mrunge has joined #openstack-meeting-308:06
*** salv-orlando has quit IRC08:15
*** salv-orlando has joined #openstack-meeting-308:15
*** matrohon has joined #openstack-meeting-308:25
*** sarob has quit IRC08:27
*** belmoreira has quit IRC08:27
*** Nisha has quit IRC08:31
*** sahid has quit IRC08:35
*** sahid has joined #openstack-meeting-308:36
*** miguelgrinberg has quit IRC08:38
*** Nisha has joined #openstack-meeting-308:38
*** watanabe_isao has quit IRC08:39
*** MaxV has joined #openstack-meeting-308:40
*** eghobo has quit IRC08:43
*** Nisha has left #openstack-meeting-308:47
*** zz_ttrifonov is now known as ttrifonov08:49
*** safchain has joined #openstack-meeting-308:58
*** miguelgrinberg has joined #openstack-meeting-309:00
*** jcoufal has joined #openstack-meeting-309:03
*** jcoufal has quit IRC09:03
*** yamahata has quit IRC09:12
*** yamahata has joined #openstack-meeting-309:13
*** salv-orlando has quit IRC09:22
*** JeanBriceCombebi has joined #openstack-meeting-309:27
*** salv-orlando has joined #openstack-meeting-309:27
*** amotoki has quit IRC09:31
*** jtomasek has joined #openstack-meeting-309:38
*** gduan has joined #openstack-meeting-309:41
*** garyduan has quit IRC09:42
*** GheRivero has quit IRC09:48
*** GheRivero has joined #openstack-meeting-309:48
*** GheRivero has quit IRC09:53
*** GheRivero has joined #openstack-meeting-309:53
*** JeanBriceCombebi has quit IRC09:54
*** JeanBriceCombebi has joined #openstack-meeting-309:57
*** alexpilotti has joined #openstack-meeting-310:02
*** jcoufal has joined #openstack-meeting-310:04
*** JeanBriceCombebi has quit IRC10:08
*** isviridov_away is now known as isviridov10:10
*** JeanBriceCombebi has joined #openstack-meeting-310:11
*** GheRivero has quit IRC10:20
*** naohirot has quit IRC10:26
*** igordcard has joined #openstack-meeting-310:29
*** igordcard has quit IRC10:29
*** GheRivero has joined #openstack-meeting-310:31
*** JeanBriceCombebi has quit IRC10:34
*** iovadia has left #openstack-meeting-310:38
*** iovadia has joined #openstack-meeting-310:38
*** JeanBriceCombebi has joined #openstack-meeting-310:39
*** GheRivero has quit IRC10:46
*** GheRivero has joined #openstack-meeting-310:47
*** JeanBriceCombebi has quit IRC10:49
*** Longgeek has quit IRC10:51
*** Longgeek has joined #openstack-meeting-310:51
*** stanzgy has quit IRC10:54
*** JeanBriceCombebi has joined #openstack-meeting-310:54
*** JeanBriceCombebi has quit IRC11:10
*** yamahata has quit IRC11:23
*** GheRivero has quit IRC11:24
*** GheRivero has joined #openstack-meeting-311:24
*** naohirot has joined #openstack-meeting-311:27
*** bradjones has quit IRC11:28
*** bradjones has joined #openstack-meeting-311:30
*** vkmc has joined #openstack-meeting-311:46
*** vkmc has quit IRC11:46
*** vkmc has joined #openstack-meeting-311:46
*** jaypipes has joined #openstack-meeting-311:51
*** jtomasek has quit IRC12:01
*** baoli has joined #openstack-meeting-312:19
*** jtomasek has joined #openstack-meeting-312:22
*** baoli has quit IRC12:24
*** baoli has joined #openstack-meeting-312:24
*** enykeev has quit IRC12:46
*** mwagner_lap has quit IRC12:48
*** sergef_ has joined #openstack-meeting-312:49
*** sergef has quit IRC12:49
*** sergef_ is now known as sergef12:49
*** JeanBriceCombebi has joined #openstack-meeting-313:11
*** JeanBriceCombebi has quit IRC13:22
*** xuhanp has joined #openstack-meeting-313:37
*** mwagner_lap has joined #openstack-meeting-313:40
*** sigmavirus24_awa is now known as sigmavirus2413:57
*** mrunge is now known as mrunge_bbl13:57
*** thomasem has joined #openstack-meeting-314:00
*** vishwanathj has joined #openstack-meeting-314:00
*** Longgeek has quit IRC14:04
*** Longgeek has joined #openstack-meeting-314:05
*** evgenyf has joined #openstack-meeting-314:06
*** Longgeek has quit IRC14:06
*** Longgeek has joined #openstack-meeting-314:07
*** Longgeek has quit IRC14:09
*** Longgeek_ has joined #openstack-meeting-314:09
*** naohirot has quit IRC14:11
*** Longgeek_ has quit IRC14:11
*** Longgeek has joined #openstack-meeting-314:12
*** Longgeek has quit IRC14:13
*** Longgeek has joined #openstack-meeting-314:14
*** JeanBriceCombebi has joined #openstack-meeting-314:15
*** markmcclain has joined #openstack-meeting-314:15
*** marun has quit IRC14:17
*** lblanchard has joined #openstack-meeting-314:18
*** kragniz has quit IRC14:22
*** kragniz has joined #openstack-meeting-314:22
*** Piet has quit IRC14:28
*** lazy_prince is now known as killer_prince14:28
*** markmcclain has quit IRC14:31
*** markmcclain has joined #openstack-meeting-314:32
*** JAHoagie has joined #openstack-meeting-314:33
*** VW_ has joined #openstack-meeting-314:34
*** markmcclain has quit IRC14:36
*** Longgeek has quit IRC14:36
*** peristeri has joined #openstack-meeting-314:37
*** JeanBriceCombebi has quit IRC14:37
*** markmcclain has joined #openstack-meeting-314:38
*** markmcclain has quit IRC14:39
*** JeanBriceCombebi has joined #openstack-meeting-314:39
*** GheRivero has quit IRC14:42
*** marun has joined #openstack-meeting-314:43
*** gholler has joined #openstack-meeting-314:45
*** GheRivero has joined #openstack-meeting-314:49
*** thangp has joined #openstack-meeting-314:52
*** Longgeek has joined #openstack-meeting-314:56
*** dboik has joined #openstack-meeting-314:58
*** mhanif has joined #openstack-meeting-314:59
*** sigmavirus24 is now known as sigmavirus24_awa14:59
*** apmelton has joined #openstack-meeting-315:00
*** sew has joined #openstack-meeting-315:00
*** mhanif has left #openstack-meeting-315:00
*** nelsnelson has joined #openstack-meeting-315:03
*** nelsnelson has quit IRC15:03
*** JeanBriceCombebi has quit IRC15:03
*** nelsnelson has joined #openstack-meeting-315:04
*** JeanBriceCombebi has joined #openstack-meeting-315:05
*** zz_jgrimm is now known as jgrimm15:05
*** mattfarina has joined #openstack-meeting-315:10
*** JAHoagie has quit IRC15:15
*** fischerw has joined #openstack-meeting-315:18
*** sigmavirus24_awa is now known as sigmavirus2415:23
*** mrunge_bbl is now known as mrunge15:27
*** markmcclain has joined #openstack-meeting-315:36
*** david-lyle has joined #openstack-meeting-315:38
*** jcoufal_ has joined #openstack-meeting-315:44
*** jcoufal has quit IRC15:47
*** apmelton has left #openstack-meeting-315:50
*** xuhanp has quit IRC15:50
*** vkmc_ has joined #openstack-meeting-315:51
*** barra204_ has joined #openstack-meeting-315:52
*** john-davidge has joined #openstack-meeting-315:52
*** barra204_ is now known as shakamunyi15:53
*** banix has joined #openstack-meeting-315:55
*** carl_baldwin has joined #openstack-meeting-315:58
*** reed has joined #openstack-meeting-315:59
*** armax has joined #openstack-meeting-316:02
*** vkmc has quit IRC16:03
*** vkmc_ is now known as vkmc16:03
*** vkmc has quit IRC16:03
*** vkmc has joined #openstack-meeting-316:03
*** vkmc_ has joined #openstack-meeting-316:03
*** JAHoagie has joined #openstack-meeting-316:04
*** vkmc_ has quit IRC16:05
*** david-lyle has quit IRC16:13
*** mikedillion has joined #openstack-meeting-316:13
*** mikedillion has quit IRC16:14
*** vishwanathj has quit IRC16:16
*** wuhg has quit IRC16:24
*** marun has quit IRC16:27
*** JeanBriceCombebi has quit IRC16:34
*** [1]evgenyf has joined #openstack-meeting-316:36
*** evgenyf has quit IRC16:37
*** [1]evgenyf is now known as evgenyf16:37
*** banix has quit IRC16:37
*** banix has joined #openstack-meeting-316:45
*** pballand has joined #openstack-meeting-316:45
*** Networkn3rd has joined #openstack-meeting-316:54
*** regana has joined #openstack-meeting-316:55
*** ttrifonov is now known as zz_ttrifonov16:57
*** thinrichs has joined #openstack-meeting-316:58
*** yamahata has joined #openstack-meeting-316:59
*** Networkn3rd has quit IRC16:59
*** MaxV has quit IRC16:59
*** stevenld has joined #openstack-meeting-316:59
*** Networkn_ has joined #openstack-meeting-317:01
thinrichsHi all.  Is anyone here for the Congress meeting?17:01
*** Networkn_ has quit IRC17:01
pballandgood morning17:02
*** VW_ has quit IRC17:02
*** armax has quit IRC17:02
*** Networkn_ has joined #openstack-meeting-317:02
*** jwy has joined #openstack-meeting-317:02
thinrichspballand: hi!17:02
thinrichsI thought it might just be me.17:03
*** sarob has joined #openstack-meeting-317:03
thinrichsPerhaps this is too close to the holidays.17:03
pballandguess everyone else is still on vacations17:03
*** kudva has joined #openstack-meeting-317:03
thinrichskudva: Hi17:03
*** marun has joined #openstack-meeting-317:03
*** bpokorny has joined #openstack-meeting-317:04
*** alexsyip has joined #openstack-meeting-317:05
thinrichsFirst off, Happy New Year everyone.17:05
thinrichsNo better way to start off than a Congress IRC.  :)17:05
*** VW_ has joined #openstack-meeting-317:06
kudvahappy new year!17:06
kudvathinrichs: agreed on the congress IRC as a start :)17:06
*** iovadia has quit IRC17:06
*** sew has left #openstack-meeting-317:06
*** eghobo has joined #openstack-meeting-317:06
*** VW_ has quit IRC17:07
*** VW__ has joined #openstack-meeting-317:07
thinrichsSeems we don't have a full crew today.17:07
thinrichsThis morning I went through the blueprints to see where we're at.17:07
thinrichsI know we're making progress on a couple of them.17:07
thinrichsWe have active development on …17:08
thinrichsdatalog-aggregates (adding sum/count/etc. to our policy language)17:08
thinrichsmurano-congress-integration (helping the Murano project utilize Congress as a gating function before they spin up apps)17:08
*** VW_ has joined #openstack-meeting-317:09
thinrichsIs there someone here that knows about progress on the DSE blueprints?17:09
thinrichsdse-control-bus (adding a control bus to the DSE)17:10
thinrichshierarchical-dse (making it possible to have a hierarchical naming scheme for DSE nodes)17:10
thinrichsNetworkn_: do you know?17:10
thinrichs(Hoping I have the right handle.)17:11
*** VW__ has quit IRC17:11
thinrichsregana: Do you know?17:11
thinrichsjwy: any progress on horizon-create-policies (enabling people to create policy rules within Horizon)?17:13
*** mikedillion has joined #openstack-meeting-317:13
*** VW_ has quit IRC17:13
*** sarob has quit IRC17:13
jwythinrichs: started brainstorming, nothing written yet17:13
thinrichsjwy: sounds good.  Let us know if you want help brainstorming.17:14
jwythinrichs: yeah if anyone has suggestions, definitely let me know17:15
*** sarob has joined #openstack-meeting-317:15
kudvathinrichs: I am interested in the nfv use case as an example of congress/domain-specific engine connection (in this case solver), how best to join in/co-ordinate my efforts with this work?17:15
*** madhumohan has joined #openstack-meeting-317:16
thinrichskudva: I think you're doing the right thing already—participating in the email thread.17:16
thinrichsFor those who haven't noticed, there's a thread on openstack-dev ..17:16
thinrichswhere we're discussing integrating Congress with linear solvers to do placement of VMs.17:17
thinrichsWe're using this as an example of how to integrate solver-like tools with Congress...17:17
kudvathinrichs: Seems like the next step in the discussion is to break up the work items in terms of implementation. I'll follow up on the openstack-dev thread then.17:17
thinrichsand how to integrate domain-specific solvers with Congress.17:17
thinrichskudva: I don't know that we're ready for implementation yet.17:18
*** jcoufal_ has quit IRC17:18
thinrichsI'd say we want to work out an example in full first...17:18
*** Longgeek has quit IRC17:19
thinrichsStart with the Datalog, figure out the actual linear program we want to produce, figure out the solution to that program, see how to use that solution to invoke the vm-migration API call.17:19
thinrichsThen we'd need the algorithms for (i) converting Datalog to linear program and (ii) using the output to invoke vm-migration API calls.17:20
thinrichsOnce we have that worked out over email, I'd say we're ready to implement.17:20
*** rcarrillocruz has left #openstack-meeting-317:21
thinrichsThe other thing to keep in mind is that there's already a policy-aware scheduler available.17:21
thinrichsI think it's called nova-scheduler.17:21
thinrichsSo in perhaps a parallel effort we should figure out how to integrate with that.17:21
thinrichsI think both efforts are worthwhile, and we'll learn different things from each.17:21
thinrichskudva: do you know if gokul is interested in this?  He was really interested in optimization originally.17:22
thinrichsBut I haven't heard from him lately.17:22
kudvathinrichs: let me check with him. I think he was quite interested in this.17:23
kudvathinirchs: still is as far as I know.17:23
thinrichskudva: that's be great.  I'm trying to track down all the folks who were interested in this.17:24
thinrichskudva: how does what I said above about moving forward on the LP/nova-scheduler sound?17:25
*** Longgeek has joined #openstack-meeting-317:25
kudvathinrichs: agreed17:26
thinrichsmadhumohan: great you could make it!17:26
*** markmcclain has quit IRC17:27
thinrichsmadhumohan: how's the modal-operators work going?modal-operators-for-policy17:27
*** evgenyf has quit IRC17:27
*** mikedillion has quit IRC17:29
thinrichsWe'll come back to the folks who stepped away.17:29
thinrichsSince we all just got back from the holidays, I'm thinking we'll wait on status reports until next week.17:30
thinrichsBut if there's anyone who wants to discuss what they're working on, let's do that now.17:30
alexsyipI've been fixing some intermittent  test failures17:32
sarobI'll mention17:32
alexsyipand performance work17:32
alexsyipthose changes are on gerrit now.17:32
thinrichsPerformance is quickly becoming important.17:33
thinrichsSo it's great to see work being done.17:33
madhumohanthinrichs: Modal operators is WIP. started working on the runtime part.17:33
*** VW_ has joined #openstack-meeting-317:34
madhumohanan initial code is in gerrit.17:34
thinrichsmadhumohan: great!  I was just trying to get some sense as to how things were progressing for our high priority blueprints.17:34
thinrichsmadhumohan: let me know if you need anything from me.17:34
thinrichsalexsyip: Do you know what kind of performance improvements your changes are producing?17:35
thinrichsmadhumohan: is it worth me taking a look at what you have, or do you think it better that I wait until you get further along?17:35
alexsyipin our test policy, it reduced the complexity from n^2 to n.17:36
madhumohanI am still trying to use NonRecursiveRule theory for modals... is that to be theory is to be linked with Action theory ?17:36
alexsyipIt will reduce complexity for many joins by a factor of n.17:36
alexsyipIn our example, the policy would run for probably 3 hours, and this change reduce it to 1 minute.17:37
thinrichsalexsyip: Wow!17:37
thinrichsAsymptotic improvements are rare—and clearly powerful.17:37
alexsyipyeah, it's way faster, but costs a bit of memory.17:37
*** sahid has quit IRC17:38
alexsyipThe change is to add indexing for joins, so that each join does not iterate through all items in the congress table being joined.17:38
thinrichsmadhumohan: you can ignore the ActionTheory.  Focus on the NonrecursiveRuleTheory.17:38
*** matrohon has quit IRC17:38
thinrichsmadhumohan: I could be wrong about this, but I think you might only need to change the unifier in unify.py.17:39
thinrichsmadhumohan: give me a sec while I look at the code.17:39
thinrichsmadhumohan: You might get away with just modifying unify.py:bi_unify_atoms.17:40
thinrichsJust treat atom1 and atom2 as if they are either atoms or modals.17:41
thinrichsIf atom1 and atom2 are not both modals or both atoms, fail.17:41
thinrichsIf they're both modals, make sure they are the same modal and then continue as the code does now.17:41
thinrichsIf they're both non-modals, continue as the code does now.17:41
thinrichs(Of course I don't know exactly how your Modal datastructure works.)17:41
madhumohanthinrichs: I have the changes for unify...I guess I will get a better version before this friday for your review.17:42
thinrichsmadhumohan: sounds good.  I'm guessing the unify changes will get you most of the way there.17:42
thinrichsalexsyip: indexing is great, and I don't imagine the memory cost will be a problem.17:42
*** sarob has quit IRC17:42
thinrichsEven if memory cost is a problem, we can't spend 3 hours on a query that should be answered in < 1 minute.17:43
alexsyipI'll agree to that.17:43
*** sarob has joined #openstack-meeting-317:43
thinrichssarob: did you want to mention something?17:43
sarobHousekeeping info17:44
sarobCommits are up which is good17:45
sarobReviews are not17:45
*** SumitNaiksatam has quit IRC17:45
sarobTwo people are doing most of the reviews17:45
sarob#link http://stackalytics.com/?project_type=all&module=congress17:45
sarobSo I'd put out there17:45
sarobA review a day is all I ask17:46
*** thangp has quit IRC17:46
sarobFrom everyone that's part of the team here17:46
*** thangp has joined #openstack-meeting-317:46
sarobIt's important to have more than just the core reviewers17:47
sarobGoing over patches17:47
sarobAnd commenting17:47
*** jwy has quit IRC17:48
*** jwy has joined #openstack-meeting-317:49
thinrichsIt's also a good way to learn about code you haven't worked on.17:49
alexsyipThanks for bringing it up sarob.  I'll spend more time reviewing in the new year.17:49
*** safchain has quit IRC17:50
thinrichsBefore we wrap up, we have a newcomer.17:51
thinrichsstevenld: want to say a few words about who you are and why you're interested in Congress?17:51
*** markmcclain has joined #openstack-meeting-317:51
*** MaxV has joined #openstack-meeting-317:52
stevenldHi, I'm Steven Tran from HP.  I'm with Kishan's team working on Murano/Congress.17:52
*** sarob_ has joined #openstack-meeting-317:53
thinrichsWelcome Steven!17:53
stevenldWe're interested in policy-based deployment of application in Murano17:53
stevenldThank you!17:54
thinrichsIntegrating with Murano is great for us!17:54
*** sunny_ has joined #openstack-meeting-317:54
*** sarob has quit IRC17:55
thinrichsIt's great to see what kinds of policies people want to use to gate application deployment.17:55
*** sarob_ is now known as sarob17:55
thinrichsThis will be the first deep integration we've done with another system.  Exciting stuff!17:55
*** markmcclain has quit IRC17:56
thinrichsJust a few minutes left.  Any last thoughts?17:56
*** markmcclain1 has joined #openstack-meeting-317:56
*** Longgeek has quit IRC17:56
thinrichsSo let's end the meeting a few minutes early.17:57
*** Longgeek has joined #openstack-meeting-317:57
thinrichsHappy New Year all!  See you next week.17:57
thinrichs#endmeeting CongressTeamMeeting17:57
*** stevenld has left #openstack-meeting-317:57
thinrichsHmmm…may have forgotten to start the meeting.17:57
banixthinrichs: you may want to start meeting and then end and mention that logs are in meeting-3 logs17:58
thinrichs#startmeeting CongressTeamMeeting17:58
openstackMeeting started Tue Jan  6 17:58:18 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.17:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:58
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:58
openstackThe meeting name has been set to 'congressteammeeting'17:58
thinrichsForgot to start the meeting this week.  Logs are in meeting-3 logs.17:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:58
openstackMeeting ended Tue Jan  6 17:58:56 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-01-06-17.58.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-01-06-17.58.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-01-06-17.58.log.html17:59
*** regana has quit IRC17:59
*** kudva has quit IRC17:59
*** sarob has quit IRC17:59
*** jwy has left #openstack-meeting-317:59
*** dboik has quit IRC17:59
*** thinrichs has left #openstack-meeting-318:00
*** eghobo has quit IRC18:01
*** madhumohan has quit IRC18:03
*** Networkn_ has left #openstack-meeting-318:03
*** Networkn3rd has joined #openstack-meeting-318:04
*** vishwanathj has joined #openstack-meeting-318:04
*** jtomasek has quit IRC18:07
*** alexsyip has quit IRC18:09
*** armax has joined #openstack-meeting-318:09
*** lhcheng has joined #openstack-meeting-318:10
*** lhcheng has left #openstack-meeting-318:10
*** SumitNaiksatam has joined #openstack-meeting-318:13
*** john-davidge has quit IRC18:17
*** yamahata has quit IRC18:18
*** Longgeek_ has joined #openstack-meeting-318:27
*** dboik has joined #openstack-meeting-318:30
*** Longgeek has quit IRC18:30
*** bpokorny_ has joined #openstack-meeting-318:30
*** bpokorny has quit IRC18:33
*** jtomasek has joined #openstack-meeting-318:35
*** yamahata has joined #openstack-meeting-318:37
*** bpokorny has joined #openstack-meeting-318:44
*** killer_prince has quit IRC18:47
*** killer_prince has joined #openstack-meeting-318:47
*** bpokorny_ has quit IRC18:48
*** killer_prince is now known as lazy_prince18:48
*** terrylhowe has joined #openstack-meeting-318:48
*** reed has quit IRC18:49
*** banix has quit IRC18:56
*** yapeng has joined #openstack-meeting-318:58
*** stevelle has joined #openstack-meeting-318:59
*** jamielennox has joined #openstack-meeting-319:00
*** briancurtin has joined #openstack-meeting-319:00
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Jan  6 19:00:17 2015 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
terrylhoweTerry Howe, HP19:00
briancurtinif you're here for the python-openstacksdk meeting, say hi. no formal agenda today, just seeing what's going on19:01
briancurtinBrian Curtin, Rackspace19:01
stevelleSteve Lewis, Rackspace19:01
jamielennoxJamie Lennox, Red Hat19:01
*** Longgeek_ has quit IRC19:01
briancurtinquick mention: Alex Gaynor left Rackspace so i don't expect him to be involved anymore19:02
sigmavirus24Ian Cordasco, Rackspace19:02
*** banix has joined #openstack-meeting-319:02
briancurtinso there hasnt been much movement in the last few weeks save for me getting tests into the swift proxy at https://review.openstack.org/#/c/132100/19:03
*** Longgeek has joined #openstack-meeting-319:04
stevelleI was trying to work through some of the reviews but it was slow progress as other things demanded attention19:04
briancurtinstevelle: +1'ed that, but it could use another look from someone to see if it's at least sane to start building on. i've been thinking about generalizing the "to_container" type stuff inside of Resource, but haven't done that yet19:04
sigmavirus24Yeah, I've been trying to help out the glance folks since they're short reviewers it seems. I'll start integrating more SDK stuff back into my schedule19:04
* sigmavirus24 will look at that19:04
briancurtini'm currently looking at bringing https://review.openstack.org/#/c/136606/ up to speed since it has a merge conflict, but it's also failing in completely random ways, which is scary, especially that it fails randomly with the same hashseed so it's not an ordering problem19:05
*** julim has joined #openstack-meeting-319:05
briancurtinhowever, as much as test coverage is important, i'm probably going to move on from that in the interest of broadening high-level service implementation so i can build something with this instead of fiddle with small examples19:05
stevelleI started on image uploads to Glance but had to shelve it.19:06
*** shakamunyi has quit IRC19:07
*** eghobo has joined #openstack-meeting-319:08
briancurtinterrylhowe: any movement on the OSC side of things that you were working on before thanksgiving?19:08
sigmavirus24briancurtin: I'll look at those tests too to see if I can offer any help19:08
terrylhoweI’ve made no progress.  I thought I’d have more time over the break to mess with things, but I’ve been skiing too much :)19:09
terrylhoweI will have time for some reviews this week and probably some dev work next week19:09
briancurtinsounds better19:09
sigmavirus24terrylhowe: don't you know something like 50% of Americans didn't take a single vacation day this year? How could you buck the majority like that? ;)19:12
*** miguelgrinberg has quit IRC19:12
terrylhoweI’m a total slacker, it is true.19:13
terrylhowebriancurtin: https://review.openstack.org/#/c/136926/ last patch was just a rebase?19:14
terrylhowethat’s what it looks like19:14
*** yamahata has quit IRC19:14
* briancurtin looking19:14
*** sunny_ has quit IRC19:14
briancurtinterrylhowe: the only change i made there was s/account/container in container.py -- a couple of the other comments i think i'd rather address separately, but i should go in and create launchpad issues to track them rather than leaving it open ended like that19:16
briancurtinsince the change was about docs i didn't want to mix in behavior changes, but some should be made19:17
terrylhoweYeh, I’d just like to get that one through19:17
briancurtini'll go through after this and create issues and do one last check to see if it can move on19:17
*** reed has joined #openstack-meeting-319:17
*** markmcclain1 has quit IRC19:18
briancurtinterrylhowe: i'll take another look at the jenkins one as well. i had some comments on the wait_for_status function in https://review.openstack.org/#/c/137394/19:19
briancurtinIIRC the jenkins one is good, just depends on that what happens in that issue19:20
terrylhoweLooks like I have some work on https://review.openstack.org/#/c/13739419:20
terrylhowethe jenkins one should be g2g though https://review.openstack.org/#/c/121660/19:21
terrylhoweoh, yeh, just what you said19:21
*** yamahata has joined #openstack-meeting-319:21
terrylhoweI’ll make a note on the wait for server method, I’d forgotten that was blocking things19:22
terrylhoweanyway, nothing more from me19:23
sigmavirus24If y'all have anything we prioritized that we need to knock out soon, let me know. I'll try and help out19:23
*** eghobo has quit IRC19:23
briancurtinsigmavirus24: will do19:24
*** markmcclain has joined #openstack-meeting-319:24
briancurtinother than that, seems like just plugging through the open reviews and seeing where to go from there. should be able to put together more of an agenda for next week and steer work better once we have things moving19:24
*** evgenyf has joined #openstack-meeting-319:26
*** yamahata has quit IRC19:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:28
openstackMeeting ended Tue Jan  6 19:28:38 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-01-06-19.00.html19:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-01-06-19.00.txt19:28
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-01-06-19.00.log.html19:28
*** jamielennox has left #openstack-meeting-319:29
*** eghobo has joined #openstack-meeting-319:30
*** stevelle has left #openstack-meeting-319:32
*** sunny_ has joined #openstack-meeting-319:36
*** david-lyle_afk is now known as david-lyle19:39
*** miguelgrinberg has joined #openstack-meeting-319:42
*** baoli has quit IRC19:43
*** sarob has joined #openstack-meeting-319:49
*** briancurtin has quit IRC19:51
*** Rockyg has joined #openstack-meeting-319:51
*** shakamunyi has joined #openstack-meeting-319:51
*** barra204_ has joined #openstack-meeting-319:54
*** shakamunyi has quit IRC19:58
*** MaxV has quit IRC20:01
*** dboik has quit IRC20:02
*** fischerw has quit IRC20:05
*** fischerw has joined #openstack-meeting-320:05
*** matrohon has joined #openstack-meeting-320:05
*** fischerw has quit IRC20:08
*** markmcclain has quit IRC20:12
*** markmcclain has joined #openstack-meeting-320:15
*** vishwanathj has quit IRC20:16
*** evgenyf has quit IRC20:16
*** MaxV has joined #openstack-meeting-320:20
*** mrunge has quit IRC20:30
*** terrylhowe has left #openstack-meeting-320:33
*** pettori has joined #openstack-meeting-320:41
*** pettori has left #openstack-meeting-320:42
*** sunny_ has quit IRC20:56
*** bpokorny_ has joined #openstack-meeting-321:00
*** JAHoagie has quit IRC21:03
*** baoli has joined #openstack-meeting-321:03
*** bpokorny has quit IRC21:04
*** SumitNaiksatam has quit IRC21:07
*** mrmartin has quit IRC21:08
*** lblanchard has quit IRC21:13
*** banix has quit IRC21:16
*** Longgeek has quit IRC21:18
*** banix has joined #openstack-meeting-321:23
*** JAHoagie has joined #openstack-meeting-321:26
*** russellb has joined #openstack-meeting-321:27
*** SumitNaiksatam has joined #openstack-meeting-321:37
*** barra204_ has quit IRC21:39
*** barra204_ has joined #openstack-meeting-321:39
*** mestery has quit IRC21:40
*** eghobo has quit IRC21:41
*** sunny_ has joined #openstack-meeting-321:48
*** jtomasek has quit IRC21:53
*** eghobo has joined #openstack-meeting-321:57
*** mestery has joined #openstack-meeting-321:57
*** sunny_ has quit IRC22:06
*** MarkAtwood has joined #openstack-meeting-322:06
*** MaxV has quit IRC22:08
*** sunny_ has joined #openstack-meeting-322:10
*** gholler has quit IRC22:11
*** markmcclain has quit IRC22:11
*** markmcclain has joined #openstack-meeting-322:12
*** barra204_ has quit IRC22:12
*** barra204 has joined #openstack-meeting-322:13
*** MaxV has joined #openstack-meeting-322:13
*** mwagner_lap has quit IRC22:15
*** bpokorny has joined #openstack-meeting-322:22
*** matrohon has quit IRC22:25
*** MaxV_ has joined #openstack-meeting-322:25
*** bpokorny_ has quit IRC22:26
*** MaxV has quit IRC22:28
*** sarob has quit IRC22:34
*** sergef has quit IRC22:34
*** emagana has joined #openstack-meeting-322:38
*** thangp has quit IRC22:38
*** Networkn3rd has quit IRC22:42
*** sigmavirus24 is now known as sigmavirus24_awa23:01
*** Rockyg has quit IRC23:02
*** Rockyg has joined #openstack-meeting-323:03
*** Rockyg has quit IRC23:03
*** Piet has joined #openstack-meeting-323:11
*** alexpilotti has quit IRC23:12
*** eghobo has quit IRC23:13
*** jgrimm is now known as zz_jgrimm23:18
*** MaxV has joined #openstack-meeting-323:19
*** baoli has quit IRC23:19
*** baoli has joined #openstack-meeting-323:20
*** MaxV has quit IRC23:20
*** emagana has quit IRC23:20
*** mestery has quit IRC23:20
*** julim has quit IRC23:20
*** ChuckC has quit IRC23:20
*** aweeks has quit IRC23:20
*** jemangs has quit IRC23:20
*** rharwood has quit IRC23:21
*** notmyname has quit IRC23:21
*** vitorc has quit IRC23:21
*** isq has quit IRC23:21
*** SotK has quit IRC23:21
*** cgoncalves has quit IRC23:21
*** NobodyCam has quit IRC23:21
*** dstanek has quit IRC23:21
*** dosaboy has quit IRC23:21
*** TheJulia has quit IRC23:21
*** markmcclain has quit IRC23:21
*** reed has quit IRC23:21
*** yapeng has quit IRC23:21
*** armax has quit IRC23:21
*** peristeri has quit IRC23:21
*** krotscheck has quit IRC23:21
*** burgobianco has quit IRC23:21
*** redrobot has quit IRC23:21
*** aignatov has quit IRC23:21
*** SergeyLukjanov has quit IRC23:21
*** ekarlso- has quit IRC23:21
*** DinaBelova has quit IRC23:21
*** marios has quit IRC23:21
*** blogan has quit IRC23:21
*** TheJulia has joined #openstack-meeting-323:21
*** NobodyCam has joined #openstack-meeting-323:21
*** aweeks has joined #openstack-meeting-323:21
*** cgoncalves has joined #openstack-meeting-323:21
*** julim has joined #openstack-meeting-323:21
*** emagana has joined #openstack-meeting-323:21
*** mestery has joined #openstack-meeting-323:21
*** vitorc has joined #openstack-meeting-323:21
*** MaxV has joined #openstack-meeting-323:21
*** ChuckC has joined #openstack-meeting-323:22
*** notmyname has joined #openstack-meeting-323:22
*** MaxV_ has quit IRC23:22
*** markmcclain has joined #openstack-meeting-323:22
*** reed has joined #openstack-meeting-323:22
*** yapeng has joined #openstack-meeting-323:22
*** armax has joined #openstack-meeting-323:22
*** peristeri has joined #openstack-meeting-323:22
*** krotscheck has joined #openstack-meeting-323:22
*** burgobianco has joined #openstack-meeting-323:22
*** redrobot has joined #openstack-meeting-323:22
*** aignatov has joined #openstack-meeting-323:22
*** SergeyLukjanov has joined #openstack-meeting-323:22
*** ekarlso- has joined #openstack-meeting-323:22
*** DinaBelova has joined #openstack-meeting-323:22
*** marios has joined #openstack-meeting-323:22
*** blogan has joined #openstack-meeting-323:22
*** rharwood has joined #openstack-meeting-323:23
*** SotK has joined #openstack-meeting-323:23
*** watanabe_isao has joined #openstack-meeting-323:24
*** burgobianco has quit IRC23:24
*** jemangs has joined #openstack-meeting-323:24
*** MaxV has quit IRC23:26
*** dosaboy has joined #openstack-meeting-323:26
*** zz_jgrimm has quit IRC23:26
*** burgobianco has joined #openstack-meeting-323:27
*** zz_jgrimm has joined #openstack-meeting-323:29
*** pballand has quit IRC23:29
*** pballand has joined #openstack-meeting-323:29
*** baoli has quit IRC23:31
*** baoli has joined #openstack-meeting-323:32
*** pballand has quit IRC23:34
*** pballand has joined #openstack-meeting-323:35
*** pballand has quit IRC23:38
*** sunny_ has quit IRC23:39
*** pballand has joined #openstack-meeting-323:39
*** baoli has quit IRC23:40
*** barra204 has quit IRC23:43
*** pballand has quit IRC23:44
*** pballand has joined #openstack-meeting-323:44
*** banix has quit IRC23:45
*** nelsnelson has quit IRC23:51
*** nelsnelson has joined #openstack-meeting-323:51
*** VW_ has quit IRC23:52
*** markmcclain has quit IRC23:54
*** dstanek has joined #openstack-meeting-323:55
*** mattfarina has quit IRC23:57

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