Tuesday, 2015-03-03

*** david-lyle has quit IRC00:00
*** markvoelker has quit IRC00:03
*** SridharRamaswamy has quit IRC00:04
*** yamamoto has joined #openstack-meeting-300:06
*** SridharRamaswamy has joined #openstack-meeting-300:11
*** annegentle has quit IRC00:14
*** marun has joined #openstack-meeting-300:15
*** iymht has joined #openstack-meeting-300:17
*** eghobo has joined #openstack-meeting-300:29
*** e0ne is now known as e0ne_00:33
*** e0ne_ is now known as e0ne00:33
*** e0ne has quit IRC00:34
*** marun has quit IRC00:35
*** bknudson has joined #openstack-meeting-300:37
*** markmcclain has quit IRC00:48
*** markmcclain has joined #openstack-meeting-300:48
*** MaxV has quit IRC00:51
*** xuhanp has joined #openstack-meeting-300:53
*** hareeshp has quit IRC00:56
*** thomasem has quit IRC00:59
*** jaypipes has quit IRC01:03
*** s3wong has quit IRC01:03
*** markvoelker has joined #openstack-meeting-301:04
*** peristeri has quit IRC01:05
*** s3wong has joined #openstack-meeting-301:08
*** david-lyle has joined #openstack-meeting-301:09
*** markvoelker has quit IRC01:13
*** VW_ has quit IRC01:14
*** baoli has joined #openstack-meeting-301:16
*** Sukhdev has quit IRC01:17
*** annegentle has joined #openstack-meeting-301:17
*** xuhanp has quit IRC01:22
*** bpokorny_ has joined #openstack-meeting-301:23
*** bpokorny has quit IRC01:26
*** xuhanp has joined #openstack-meeting-301:27
*** ivar-laz_ has joined #openstack-meeting-301:28
*** annegentle has quit IRC01:29
*** sbalukoff has quit IRC01:29
*** stanzgy has joined #openstack-meeting-301:30
*** stanzgy_ has joined #openstack-meeting-301:30
*** ivar-lazzaro has quit IRC01:31
*** watanabe_isao has joined #openstack-meeting-301:31
*** ivar-laz_ has quit IRC01:32
*** megm_ has joined #openstack-meeting-301:40
*** megm has quit IRC01:41
*** annegentle has joined #openstack-meeting-301:45
*** sarob has joined #openstack-meeting-301:50
*** zz_johnthetubagu has quit IRC01:52
*** david-lyle has quit IRC01:52
*** david-lyle has joined #openstack-meeting-301:53
*** Longgeek has joined #openstack-meeting-301:57
*** carl_baldwin has quit IRC02:00
*** annegentle has quit IRC02:03
*** SridharRamaswamy has quit IRC02:08
*** sigmavirus24 is now known as sigmavirus24_awa02:08
*** bpokorny_ has quit IRC02:14
*** VW_ has joined #openstack-meeting-302:22
*** VW_ has quit IRC02:23
*** VW_ has joined #openstack-meeting-302:23
*** david-lyle has quit IRC02:23
*** markvoelker has joined #openstack-meeting-302:26
*** annegentle has joined #openstack-meeting-302:30
*** amotoki has joined #openstack-meeting-302:32
*** clu_ has quit IRC02:36
*** annegentle has quit IRC02:36
*** mattgriffin has joined #openstack-meeting-302:39
*** mattgriffin has quit IRC02:39
*** lazy_prince has quit IRC02:46
*** thangp has joined #openstack-meeting-302:48
*** ivar-lazzaro has joined #openstack-meeting-302:49
*** s3wong has quit IRC02:53
*** eghobo has quit IRC02:59
*** Longgeek has quit IRC03:02
*** ivar-lazzaro has quit IRC03:10
*** ivar-lazzaro has joined #openstack-meeting-303:10
*** baoli has quit IRC03:11
*** jckasper has quit IRC03:15
*** Longgeek has joined #openstack-meeting-303:15
*** thangp has quit IRC03:16
*** iymht has quit IRC03:16
*** yamahata has quit IRC03:20
*** baoli has joined #openstack-meeting-303:26
*** jckasper has joined #openstack-meeting-303:28
*** xuhanp has quit IRC03:29
*** nelsnelson has joined #openstack-meeting-303:33
*** bpokorny has joined #openstack-meeting-303:37
*** ivar-lazzaro has quit IRC03:49
*** amotoki has quit IRC04:02
*** Longgeek has quit IRC04:06
*** yamamoto has quit IRC04:07
*** yamamoto has joined #openstack-meeting-304:08
*** killer_prince has joined #openstack-meeting-304:18
*** killer_prince is now known as lazy_prince04:18
*** Longgeek has joined #openstack-meeting-304:18
*** armax has joined #openstack-meeting-304:21
*** stendulker has joined #openstack-meeting-304:30
*** coolsvap_ is now known as coolsvap04:37
*** Networkn3rd has quit IRC04:41
*** Networkn3rd has joined #openstack-meeting-304:42
*** armax has quit IRC04:45
*** Networkn3rd has quit IRC04:46
*** nelsnelson has quit IRC04:47
*** armax has joined #openstack-meeting-304:47
*** bpokorny has quit IRC04:48
*** bpokorny has joined #openstack-meeting-304:49
*** faizan_ has joined #openstack-meeting-304:53
*** rameshg87 has joined #openstack-meeting-304:55
*** wanyen has joined #openstack-meeting-304:56
*** bpokorny has quit IRC04:58
*** markvoelker has quit IRC04:59
*** jlvllal_rem has joined #openstack-meeting-304:59
*** BadCub has joined #openstack-meeting-305:00
devanandahi folks!05:00
*** markvoelker has joined #openstack-meeting-305:00
devanandawho's here for the ironic meeting?05:00
* NobodyCam maybe lurking05:00
*** armax has quit IRC05:00
* BadCub is lurking somewhere05:00
*** Nisha has joined #openstack-meeting-305:00
stendulker\o05:00
jlvllal_remI am05:00
*** Haomeng has joined #openstack-meeting-305:00
wanyeno/05:01
devanandaI'll give folks a minute more to trickle in05:01
Haomengo/05:01
jroll\o05:01
rameshg87o/05:01
jrollif I disconnect during the meeting, blame xen.05:01
*** lintan has joined #openstack-meeting-305:01
* rameshg87 wonders who's xen05:01
Nishao/05:01
JoshNango/05:01
lintano/05:01
devanandajroll: hasn't someone there fixed xen yet?05:02
jrollrameshg87: the hypervisor, which has a new exploit that has rackspace/amazon/linode/more rebooting the cloud05:02
*** naohirot has joined #openstack-meeting-305:02
jrolldevananda: yeah, applying patches to my bouncer's region tonight05:02
devanandaok, let's get started. enough folks here now05:02
devananda#startmeeting ironic05:02
openstackMeeting started Tue Mar  3 05:02:43 2015 UTC and is due to finish in 60 minutes.  The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot.05:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:02
*** openstack changes topic to " (Meeting topic: ironic)"05:02
openstackThe meeting name has been set to 'ironic'05:02
jrolldevananda: or do you mean the fact that we use xen :P05:02
* jroll stays on topic05:02
devananda#chair NobodyCam05:02
openstackCurrent chairs: NobodyCam devananda05:02
*** sbalukoff has joined #openstack-meeting-305:03
devanandaas always, the agenda can be found on the wiki here05:03
* rameshg87 wonders whether NobodyCam is around05:03
devananda#link https://wiki.openstack.org/wiki/Meetings/Ironic05:03
devananda#topic announcements05:03
*** openstack changes topic to "announcements (Meeting topic: ironic)"05:03
NobodyCamsi I am05:03
devanandaonly announcement on my end -- feature proposal freeze is this week05:03
devanandaI expect much of today (and tomororw) will be going over that05:04
*** markvoelker has quit IRC05:04
devanandaanyone else have announcements?05:04
jrolldevananda: any specs we want to try to land for that?05:04
devanandamaybe - let's cover that after announcements05:05
devanandaalso - FPF shouldn't actually be an announcement05:05
devanandathat's been planned for the whole cycle :)05:05
Haomengdevananda: :)05:05
devanandaok - moving on to status reports05:05
devananda#topic subteam status reports05:05
*** openstack changes topic to "subteam status reports (Meeting topic: ironic)"05:05
jrolllight reports this week, people must be slacking :)05:06
devanandafor those that updated the etherpad already, thanks much05:06
*** david-lyle_afk has joined #openstack-meeting-305:06
devananda#link https://etherpad.openstack.org/p/IronicWhiteBoard05:06
devanandasince I dont see dmitry here, i'll post his update05:06
*** baoli has quit IRC05:06
* jroll just realized IPA has updates05:06
devananda(As of Mon, 02 Mar 17:00 UTC) Open: 129 (-7). 3 new (-4), 32 in progress (-4), 0 critical, 18 high and 7 incomplete05:06
mrdaI think you guys might be running over... ?05:06
jrollmrda: ?05:07
NobodyCam??05:07
mrdaSorry, mea culpa05:07
NobodyCam:)05:07
Haomengmrda: :)05:07
mrda(damn scrollback!)05:07
jrollalways page down when your question feels out of place :P05:07
*** jckasper has quit IRC05:08
devanandaalso of note, a security issue was found and fixed last week05:08
* devananda annotates it on the 'pad05:08
jroll#link https://launchpad.net/bugs/142520605:08
openstackLaunchpad bug 1425206 in OpenStack Security Notes "Setting debug mode also causes Pecan to run in debug mode" [Undecided,New]05:08
devanandathanks, jroll05:08
* naohirot I just updated iRMC in the white board.05:09
devanandanaohirot: cheers, ty05:09
NobodyCamthank you naohirot05:09
devanandanaohirot: iRMC has a pxe-based deploy driver already landed, right?05:09
naohirotdevananda: NobodyCam: you are welcome05:09
* rameshg87 notes jroll forgot to update ironic.conf.sample :)05:09
jrollfolks can feel free to ping devananda or myself if you have questions about that bug, but it isn't particularly horrible in most cases05:09
jrollrameshg87: shh :P05:10
naohirotdevananda: Yes, it has been landed. thanks!05:10
rameshg87jroll, :)05:10
*** stendulker has quit IRC05:12
devanandagreat, thanks for all the updates there05:12
*** stendulker has joined #openstack-meeting-305:12
devananda#topic kilo-305:12
*** openstack changes topic to "kilo-3 (Meeting topic: ironic)"05:12
devanandawe could probably talk about this for a long time05:13
devanandai'll time-box us to 30 minutes though :)05:13
devanandatldr; we have a tonne of specs already approved05:13
rameshg87devananda, i guess there are many driver-related stuffs waiting this time in kilo-305:13
devananda#link https://launchpad.net/ironic/+milestone/kilo-305:13
devanandayes05:13
devanandasome, but not all of them, require changes in the core code05:14
devanandaeg, all the cleaning & zapping work05:14
devanandarameshg87: by the way, thank you for the excellent email on the benefits of working out-of-tree05:14
rameshg87devananda, :)05:14
JoshNangenough of cleaning should have landed today for everyone to base their code on (hopefully!)05:15
devanandaJoshNang: fantastic!05:15
devanandaJoshNang: how much // what is left?05:15
rameshg87JoshNang, and zapping, are you working on that ?05:15
devananda#info JoshNang> enough of cleaning should have landed today for everyone to base their code on (hopefully!)05:15
rameshg87JoshNang, i have my specs dependent on zapping :)05:15
JoshNangdevananda: the actual execution of the cleaning code, the api, and zapping api05:15
JoshNangplus the agent bits (mostly ready in IPA, needs driver support)05:16
devanandaJoshNang: can you update the status of those BP then? they say "started" right now05:16
devanandasounds like they are further along than that?05:16
JoshNang:/ oh, yeah05:16
*** Nisha has quit IRC05:16
devanandaty05:16
JoshNangrameshg87: as far as zapping, you should be able to go, as the @clean_step decorator should be all you need05:16
devanandaBadCub and I will be watching the milestone page closely05:16
*** Nisha has joined #openstack-meeting-305:16
devanandaso if a BP is assigned to you, please keep it up to date regularly over the next month05:17
rameshg87JoshNang, yeah i understand, but i need some more info on how inband zapping steps are planned (like getting the ramdisk booted and such stuffs)05:17
*** stendulker has quit IRC05:17
*** stendulker has joined #openstack-meeting-305:18
rameshg87JoshNang, any examples of agent zapping task on your private github might help as well05:18
JoshNangrameshg87: ahh gotcha. my plan is to have it all the clean/zap reviews up by end of the day thursday05:18
devanandanaohirot: irmc virtual media deploy driver is marked "blocked" right now -- I see code, some of which has landed05:18
devanandanaohirot: is either the spec or code waiting on anything at this point (besides reviews) ?05:18
rameshg87JoshNang, okay. let me know if i can help with something on the zapping if that will speed it up :)05:19
rameshg87JoshNang, i will be happy to try to help :)05:19
JoshNangrameshg87: we haven't really used zapping yet :/ and downstream we just always have an agent booted. i might take you up on that :)05:19
devanandanaohirot: ooh. I see. there is still disagreement on the architecture around the driver mounting NFS shares05:19
rameshg87JoshNang, ah okay .. here we might need to get the agent booted when the node is in manageable state. will discuss on that when you have time05:20
naohirotdevananda: No, both are not waiting for anything, both are independent, i thinks.05:20
devanandanaohirot: given the other project proirities, i'm going to untarget that at this point because there is still contention on the design05:20
naohirotdevananda: I understand the situation, I'm going to contribute reviewing high priority feature05:21
*** stendulker has quit IRC05:21
*** stendulker has joined #openstack-meeting-305:22
naohirotdevananda: And later if we had some space, please consider iRMC virtual media :)05:22
*** stendulker has quit IRC05:22
devanandanaohirot: thank you. I think it also poses a good question for us -- should drivers, in their constructor, take administrative actions on the host, like mounting NFS or asserting that tftpd is running?05:22
*** stendulker has joined #openstack-meeting-305:22
devanandain the past the answer's been "no"05:22
devanandanaohirot: definitely. I like the feature but I can understand the objections people have raised05:23
*** JAHoagie has joined #openstack-meeting-305:23
devanandawe've got one other blocked BP up here05:23
*** takadayuiko has joined #openstack-meeting-305:23
jrollyeah, localboot05:23
devanandayea05:23
jrollwhich doesn't appear to be blocked05:23
devanandahttps://blueprints.launchpad.net/ironic/+spec/local-boot-support-with-partition-images05:23
devanandaright ...05:23
jrollif it's blocked, it's blocked on DIB or IPA :P05:23
rameshg87devananda, and https://blueprints.launchpad.net/ironic/+spec/inband-raid-configuration05:24
rameshg87devananda, inband raid configuration05:24
naohirotdevananda: really, some core member has some objection regarding NIF/CIFS?05:24
rameshg87devananda, that has dependency on the zapping implementation05:24
jrollnaohirot: yes, it's on the review05:24
jrollthough this isn't the place/time to discuss that...05:24
rameshg87devananda, i would say it's a dependency, not that it's blocked :)05:24
devanandarameshg87: ahh, right05:25
devanandarameshg87: what's your sense -- will there be time to land inband raid config this cycle, with zapping still in the works?05:25
devananda(my sense is "no")05:25
rameshg87devananda, ironic-python-agent is going through some refactoring on zapping space - so JoshNang asked to wait05:25
devanandaok05:25
naohirotjroll: If so, I wanted to discuss earlier, I thought I've already answered some of questions.05:25
rameshg87devananda, inband doesn't have much code - all is done in proliantutils - with ipa hardware manager05:26
JoshNangyeah, we landed the multiple hardware managers bit, which through a wrench in my previous patches05:26
rameshg87devananda, ironic is just triggering it - just like any other agent cleanup/zap task05:26
devanandarameshg87: that's out of band05:26
JoshNang*threw05:26
devanandarameshg87: out-of-band means via the BMC. in-band means via the ramdisk (IPA + local utilities)05:26
rameshg87devananda, yeah, it's in-band05:26
devanandaJoshNang: heh. so punt on in-band until L* ?05:26
* naohirot s/some of questions/all of questions/05:27
jrollnaohirot: I'm looking at patchset 22, it doesn't appear resolved. I think y'all should debate it more in gerrit/mailing list/irc.05:27
rameshg87devananda, ilo can't do raid configuration out of band05:27
devanandarameshg87: oh!05:27
rameshg87devananda, so we choose to do it from agent ramdisk - and implementation is in hardware manager05:27
jrollnaohirot: "I think this way is better" is not an answer.05:27
JoshNangdevananda: hmm hopefully not. i just need to refactor a bit. i might enroll some help from other IPA people for that05:27
devanandarameshg87: I thought that it could do out-of-band. sorry05:27
jrolldevananda: JoshNang: to be clear, "refactor" here means re-write existing patches to IPA05:28
rameshg87devananda, yeah, it's only in-band for ilo. so the code in ironic is just to trigger the in-band thing through ipa05:28
*** lazy_prince has quit IRC05:28
devanandagotcha05:28
JoshNangjroll: probably half of it, the calling and listing steps bit05:28
* devananda refrains from retargeting that05:29
naohirotjroll: I'm wondering that there is no comments on patch #2205:29
jrollnaohirot: we are talking about https://review.openstack.org/#/c/134865/ correct?05:29
*** killer_prince has joined #openstack-meeting-305:29
*** killer_prince is now known as lazy_prince05:29
naohirotjroll: Yes, it is. it's iRMC virtual media deploy spec.05:30
jrollnaohirot: I see comments on patch 22; not inline, just comments.05:30
*** markvoelker has joined #openstack-meeting-305:30
devanandaany other specs or BPs folks wnat to talk about now?05:31
jrollnaohirot: anyway, I don't think we should spend the whole meeting talking about that spec, let's discuss later.05:31
naohirotjroll: Okay05:31
NobodyCamactualy i do05:31
wanyendevananda, get/set boot mode spec still needs approval05:32
NobodyCamhttps://review.openstack.org/#/c/151596/05:32
devanandawanyen: link?05:32
stendulkerlink : https://review.openstack.org/#/c/129529/05:33
wanyenhttps://review.openstack.org/#/c/129529/05:33
NobodyCamthats for the ilo-properties-capabilities-discovery05:33
stendulkerNobodyCam: Its for Add get/set boot mode to Management Interface05:33
NobodyCamyour link or mine?05:34
wanyenalso, need reviewers for uefi secure boot (no core reviewers review it yet)05:34
stendulkerstendulker: mine05:34
jrollone thing at a time...05:34
devanandawanyen: ah05:35
jrollso- I'm of the opinion we shouldn't land any more specs, personally05:35
jrollbut if something is SUPER important I guess we could05:35
*** markvoelker has quit IRC05:35
devanandajroll: fwiw, I think we already have far too many to actually finish them all05:35
devanandajroll: but that's what I'm trying to find out :)05:35
jrolldevananda: agree, which means more is worse05:35
mrda+105:35
devanandawithout digging into it deeply yet, this is relatively small and  might be something we want to land now05:36
devanandahttps://review.openstack.org/#/c/129529/6/specs/kilo/add-boot-mode-mgmt-interface.rst,cm05:36
devanandasince we just added a lot of similar things this cycle05:36
jrollyeah, seems fine05:36
* jroll quickly reviews05:36
devanandamy only concern there is impact to existing drivers // drivers that can't support it05:37
jroll(I thought this was already landed)05:37
wanyendevananda, to clarify, no core reviewers review uefi secure boot code yet https://blueprints.launchpad.net/ironic/+spec/uefi-secure-boot05:37
devanandajroll: that should make your vote easy to cast :)05:37
wanyendevananda, the secuer boot spec has been approved.05:37
jrollwanyen: we're very busy, we will get to it.05:37
wanyenjrol, ty05:38
devanandawanyen: ok. we're focusing on specs and blueprints right now, not code reviews.05:38
wanyens/jrol/jroll05:38
devananda(now == this meeting)05:38
rameshg87devananda, only concern we had regarding that get-set boot mode was whether boot mode should have it's own get/set methods or not05:39
rameshg87devananda, that was rloo's concern05:39
devanandarameshg87: I see this now says that there's no REST API change05:39
*** mrmartin has joined #openstack-meeting-305:39
rameshg87devananda, yeah it doesn't have05:39
*** eghobo has joined #openstack-meeting-305:39
devanandarameshg87: what calls these methods then?05:40
jrollrameshg87: what's the alternative to that?05:40
rameshg87devananda, wherever we are getting/setting boot mode in place, just a request to make it part of an interface05:40
rameshg87devananda, we are doing get/set boot mode in ilo driver deploy right now05:40
devanandarameshg87: it needs to be called somehow OUTSIDE of the driver though05:40
rameshg87jroll, alternative to that was to have a generic method which can get/set any capability - and boot_mode is one of them05:40
devanandaa) some external event triggers it one way or another05:40
wanyendevananda, iLo health sensor spec  https://review.openstack.org/#/c/127378/ still need to be approved05:40
*** eghobo has quit IRC05:40
devanandab) if that is done for drivers which don't support it, how will UnsupportedDriverExtension be handled?05:41
stendulkerstendulker: its required to prepare the pxe config as well based on boot mode05:41
*** eghobo has joined #openstack-meeting-305:41
jrolldevananda: essentially this will s/ilo_utils.set_boot_mode/driver.management.set_boot_mode/05:41
rameshg87devananda, we don't call get/set boot mode from outside right now (no api for that)05:41
jrollAIUI05:41
rameshg87jroll, exactly05:41
devanandajroll: oh05:41
devanandarameshg87: ok. that makes no sense to me05:41
stendulkerrameshg87: we need get boot mode in pxe05:42
devanandarameshg87: if there's no need for a REST API and nothing outside of the driver needs, it, why make it part of the driver API ?05:42
rameshg87devananda, it's not something needed right now05:42
jrollso, I posted this in gerrit: if only iLO is using this, why standardize on an interface for it?05:42
jrollthis might be the same question devananda had05:42
devanandajroll: ++05:42
NobodyCamFyi Timebox 30 Minutes is up..05:43
devanandaok - I'm going to copy this conversation to gerrit and let's revisit this in Liberty05:43
*** megm has joined #openstack-meeting-305:43
devanandaNobodyCam: thanks05:43
rameshg87jroll, yeah drivers can use this later - that was intention of that spec05:43
rameshg87devananda, okay05:43
*** megm_ has quit IRC05:43
jrollcool05:43
devanandarameshg87: driver API should only be changed when there is a clear need for multiple drivers, and they can agree upon a standard05:43
devanandanever pre-emptively05:43
rameshg87devananda, okay05:43
*** david-lyle_afk has quit IRC05:44
devanandarameshg87: i'm happy to explain more on that, and should probably write a blog post on it or something .... anyway ...05:44
jrollthis was also stendulker's agenda item yes?05:44
devananda#topic open discussion05:44
*** openstack changes topic to "open discussion (Meeting topic: ironic)"05:44
devanandajroll: was it?05:44
jrollI believe so05:44
devanandathat seems separate05:44
rameshg87jroll, no05:44
rameshg87jroll, it's separate05:44
jrollwow, not at all05:44
devanandastendulker: your item is about elilo vs. grub2,05:44
devanandaright?05:44
jrollok, I mis-remembered, had to look again05:45
stendulkerthanks devananda05:45
stendulkerthis is more of a heads-up on change of uefi boot loader05:45
stendulkerWe need grub2 to support secure boot feature. Linux vendors supply signed grub2 binaries with their distribution05:45
stendulkerelilo is not signed by any linux vendors.05:45
*** Nisha has quit IRC05:45
stendulkerhence its proposed to change the uefi bootloader to grub2 as part of  https://review.openstack.org/#/c/154808/05:45
NobodyCamNisha: ran in to a issue with the ilo discovery deleting a port from a reserved node would love to get eyes on the fix: https://review.openstack.org/#/c/151596/24/ironic/db/sqlalchemy/api.py05:46
devanandastendulker: what parts of ironic does this affect?05:46
*** Nisha has joined #openstack-meeting-305:46
naohirotdevananda: jroll: regarding iRMC spec, it's not a contention which Demitry commented, because he gave +2. I thought it was just a suggestion.05:46
stendulkerdevananda: uefi deploy05:46
devanandanaohirot: Dmitry Tantsur05:46
devanandaFeb 3 11:46 PM05:46
devananda-105:47
stendulkerstendulker: so far only pxe‎_ilo driver was supporting uefi, but in K-release it seems many other drivers would be supporting uefi05:47
devanandaoops - bad paste05:47
devanandanaohirot: Patch Set 21: Code-Review-105:47
stendulkerdevananda: hence thought of bringing this up in the meeting05:47
naohirotdevananda: sorry, s/Demitry/Dmitry/05:47
jrollnaohirot: he gave a +2 in patchset 7, that's completely unrelated 15 patchsets later05:47
rameshg87stendulker, pxe_ipmitool also support uefi deploy (just that setting boot device fails)05:48
devanandastendulker: partition-based deploys only? or does this affect all deploys because it affects the deploy ramdisk itself?05:48
jrollnaohirot: it *is* a contention, you have at least two cores and two regular contributors that have pointed out this issue.05:48
stendulkerdevananda: partition based05:49
stendulkerdevananda: I could nt gets secure boot enabled disk image to test it out though05:49
devanandastendulker: k, thought so05:49
devanandastendulker: oh... that's surprising05:49
naohirotjroll: Patch Set 21: Code-Review-1 that was his misunderstanding, I answered to him05:49
devanandastendulker: don't some cloud providers already produce uefi-capable cloud images?05:49
jrollnaohirot: it does not seem that way to me, it's a -1 with clear concerns05:50
stendulkerdevananda: coreos provides dis images but they are just uefi ones05:50
stendulkerdevananda: not sure if they are signing them with their own digital sign and not using Microsoft digital signature05:51
*** Nisha has quit IRC05:51
stendulkerdevananda: Other vendors like ubuntu, fedora and redhat supply microsoft signed  shim bootloader and grub2 with teir own signatures05:52
*** Nisha_away has joined #openstack-meeting-305:52
naohirotjroll: yeah, if there is still concern we can discuss. but I'd like to know what kind of concern is it?05:52
devanandanaohirot: I have posted on the spec. let's discuss later05:52
jrollnaohirot: I've also posted on the spec, if it's not clear please ask me after the meeting05:52
naohirotdevananda: okay, let's discuss in the channnel.05:53
devanandastendulker: interesting. well - as you proceed, please share documentation on testing  and using it05:53
stendulkerdevananda: sure. Have already raised review for DIB changes to accomaodate this05:54
stendulkerdevananda: link https://review.openstack.org/#/c/15398705:54
devananda#info locally-bootale partition-based deploys need grub2 to support UEFI-boot05:54
devananda#link https://review.openstack.org/#/c/15398705:55
jrolldevananda: and pxe-bootable, if I'm reading that change correctly?05:55
devanandastendulker: oh! does this also affect net boot?05:55
jrolllooking at https://review.openstack.org/#/c/154808/17/ironic/drivers/modules/pxe_grub_config.template05:55
jrollhard to tell05:55
*** takadayuiko has quit IRC05:56
*** Sukhdev has joined #openstack-meeting-305:56
stendulkerdevananda: Since netboot is just a kernel parameter, it can be accomodated05:56
stendulkerdevananda: kernel parameter passed into bootloader config file05:57
devanandathat seems odd. grub shouldnt be involved in pxe boot...05:57
jrollyeah, I thought I was just learning something new today05:57
jrollbut I'm skeptical05:57
devanandastendulker: you're configuring grub to boot from network?05:57
devanandathat's fascinatingly backwards :)05:57
stendulkerdevananda: we need to have a bootloader into tftpdir to support pxe-boot, right?05:58
NobodyCamlog.warn(_LW("2 minutes to go."))05:58
devanandaNobodyCam: lol, nice :)05:58
HaomengNobodyCam: :)05:58
NobodyCam:)05:58
jrolllol05:58
stendulkerdevananda: yes05:58
jrollNobodyCam: I think that should be at info level, -105:58
stendulkerdevananda: just as we do it for elilo today05:58
devanandastendulker: neat. I need to think more about that05:58
NobodyCamlol05:59
jrolllog.error in t-30 seconds05:59
devanandamy initial reaction is that that's crazy .... but I dunno05:59
stendulkerdevananda: ok. Please have a look at https://review.openstack.org/#/c/154808/05:59
devanandawill do05:59
devanandathanks, all!05:59
devanandasee you tomorrow :)05:59
NobodyCamThank you all06:00
Haomengbye, good night:)06:00
stendulkerdevananda: thank you06:00
jrollthanks deva :)06:00
jlvllal_remCiao!06:00
Haomengthanks06:00
devananda#endmeeting06:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:00
openstackMeeting ended Tue Mar  3 06:00:10 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-03-03-05.02.html06:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-03-03-05.02.txt06:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-03-03-05.02.log.html06:00
*** BadCub has quit IRC06:00
*** rameshg87 has left #openstack-meeting-306:02
*** stendulker_ has joined #openstack-meeting-306:02
*** wanyen has quit IRC06:03
*** stendulker has quit IRC06:04
*** iymht has joined #openstack-meeting-306:05
*** killer_prince has joined #openstack-meeting-306:10
*** lazy_prince has quit IRC06:10
*** killer_prince is now known as lazy_prince06:10
*** eghobo has quit IRC06:20
*** redrobot has quit IRC06:21
*** redrobot has joined #openstack-meeting-306:25
*** redrobot is now known as Guest3254406:25
*** markvoelker has joined #openstack-meeting-306:31
*** eghobo has joined #openstack-meeting-306:32
*** fungi has quit IRC06:34
*** russellb has quit IRC06:34
*** markvoelker has quit IRC06:36
*** JAHoagie has quit IRC06:42
*** stendulker has joined #openstack-meeting-306:43
*** david-lyle_afk has joined #openstack-meeting-306:44
*** stendulker_ has quit IRC06:46
*** ivar-lazzaro has joined #openstack-meeting-306:47
*** Nisha_away has quit IRC06:48
*** jroll has quit IRC06:49
*** xuhanp has joined #openstack-meeting-306:58
*** reed has quit IRC06:58
*** jroll has joined #openstack-meeting-306:59
*** ivar-lazzaro has quit IRC07:00
*** ivar-lazzaro has joined #openstack-meeting-307:01
*** mrda is now known as mrda-away07:04
*** jtomasek has joined #openstack-meeting-307:06
*** yamahata has joined #openstack-meeting-307:21
*** sergef has joined #openstack-meeting-307:24
*** yamamoto has quit IRC07:24
*** scheuran has joined #openstack-meeting-307:26
*** mrunge has joined #openstack-meeting-307:27
*** markvoelker has joined #openstack-meeting-307:32
*** VW_ has quit IRC07:33
*** VW_ has joined #openstack-meeting-307:33
*** VW_ has quit IRC07:35
*** VW_ has joined #openstack-meeting-307:35
*** markvoelker has quit IRC07:37
*** jkoelker has quit IRC07:38
*** Sukhdev has quit IRC07:45
*** jkoelker has joined #openstack-meeting-307:48
*** VW_ has quit IRC07:48
*** VW_ has joined #openstack-meeting-307:49
*** VW_ has quit IRC07:53
*** VW_ has joined #openstack-meeting-307:54
*** armax has joined #openstack-meeting-307:59
*** VW_ has quit IRC08:00
*** VW_ has joined #openstack-meeting-308:01
*** Haomeng has quit IRC08:01
*** Haomeng has joined #openstack-meeting-308:03
*** VW_ has quit IRC08:03
*** VW_ has joined #openstack-meeting-308:04
*** sahid has joined #openstack-meeting-308:05
*** jcoufal has joined #openstack-meeting-308:07
*** VW_ has quit IRC08:09
*** VW_ has joined #openstack-meeting-308:09
*** VW_ has quit IRC08:11
*** VW_ has joined #openstack-meeting-308:11
*** armax has quit IRC08:12
*** lsmola has joined #openstack-meeting-308:16
*** hareeshp has joined #openstack-meeting-308:18
*** VW_ has quit IRC08:19
*** matrohon has joined #openstack-meeting-308:19
*** VW_ has joined #openstack-meeting-308:19
*** hareeshp has quit IRC08:23
*** sigmavirus24_awa has quit IRC08:26
*** e0ne has joined #openstack-meeting-308:26
*** jkoelker has quit IRC08:27
*** VW_ has quit IRC08:30
*** VW_ has joined #openstack-meeting-308:30
*** iovadia has joined #openstack-meeting-308:30
*** markvoelker has joined #openstack-meeting-308:33
*** e0ne has quit IRC08:34
*** VW_ has quit IRC08:35
*** iovadia has quit IRC08:35
*** VW_ has joined #openstack-meeting-308:35
*** MaxV has joined #openstack-meeting-308:36
*** evgenyf has joined #openstack-meeting-308:37
*** eghobo has quit IRC08:38
*** markvoelker has quit IRC08:39
*** e0ne has joined #openstack-meeting-308:39
*** watanabe_isao has quit IRC08:39
*** MaxV has quit IRC08:41
*** hareeshp has joined #openstack-meeting-308:48
*** iovadia has joined #openstack-meeting-308:49
*** MaxV has joined #openstack-meeting-308:50
*** e0ne is now known as e0ne_08:59
*** ivar-lazzaro has quit IRC09:00
*** VW_ has quit IRC09:01
*** ivar-lazzaro has joined #openstack-meeting-309:01
*** VW_ has joined #openstack-meeting-309:01
*** e0ne_ is now known as e0ne09:01
*** iymht has quit IRC09:05
*** lifeless has quit IRC09:05
*** lifeless has joined #openstack-meeting-309:06
*** e0ne is now known as e0ne_09:06
*** JoshNang has quit IRC09:07
*** VW_ has quit IRC09:07
*** VW_ has joined #openstack-meeting-309:08
*** e0ne_ is now known as e0ne09:09
*** yamahata has quit IRC09:13
*** ivar-lazzaro has quit IRC09:14
*** e0ne has quit IRC09:15
*** hareeshp has quit IRC09:27
*** safchain has joined #openstack-meeting-309:28
*** Haomeng|2 has joined #openstack-meeting-309:29
*** Haomeng has quit IRC09:30
*** VW__ has joined #openstack-meeting-309:33
*** markvoelker has joined #openstack-meeting-309:35
*** VW_ has quit IRC09:37
*** VW__ has quit IRC09:38
*** markvoelker has quit IRC09:39
*** megm_ has joined #openstack-meeting-309:44
*** megm has quit IRC09:45
*** naohirot has quit IRC09:49
*** coolsvap is now known as coolsvap_09:52
*** JeanBriceCombebi has joined #openstack-meeting-309:56
*** Longgeek has quit IRC10:01
*** hareeshp has joined #openstack-meeting-310:05
*** Haomeng|2 has left #openstack-meeting-310:05
*** JeanBriceCombebi has quit IRC10:07
*** JeanBriceCombebi has joined #openstack-meeting-310:22
*** amotoki has joined #openstack-meeting-310:34
*** hareeshp has quit IRC10:34
*** markvoelker has joined #openstack-meeting-310:35
*** hareeshp has joined #openstack-meeting-310:36
*** igordcard has joined #openstack-meeting-310:36
*** markvoelker has quit IRC10:40
*** Longgeek has joined #openstack-meeting-310:41
*** e0ne has joined #openstack-meeting-310:43
*** Longgeek has quit IRC10:43
*** Longgeek has joined #openstack-meeting-310:44
*** matrohon has quit IRC10:44
*** scheuran_ has joined #openstack-meeting-310:49
*** scheuran has quit IRC10:52
*** stanzgy has quit IRC10:54
*** stanzgy_ has quit IRC10:54
*** e0ne is now known as e0ne_11:09
*** stendulker has quit IRC11:13
*** xuhanp has quit IRC11:14
*** coolsvap_ is now known as coolsvap11:17
*** pavel_bondar has quit IRC11:18
*** e0ne_ has quit IRC11:20
*** e0ne has joined #openstack-meeting-311:21
*** hareeshp has quit IRC11:21
*** markvoelker has joined #openstack-meeting-311:36
*** markvoelker has quit IRC11:41
*** JeanBriceCombebi has quit IRC11:42
*** e0ne is now known as e0ne_11:53
*** hareeshp has joined #openstack-meeting-311:57
*** Longgeek has quit IRC11:58
*** e0ne_ is now known as e0ne12:01
*** evgenyf has quit IRC12:06
*** killer_prince has joined #openstack-meeting-312:06
*** wojdev has joined #openstack-meeting-312:07
*** lazy_prince has quit IRC12:07
*** killer_prince is now known as lazy_prince12:07
*** russellb has joined #openstack-meeting-312:08
*** baoli has joined #openstack-meeting-312:10
*** evgenyf has joined #openstack-meeting-312:11
*** yamamoto has joined #openstack-meeting-312:12
*** wojdev has quit IRC12:18
*** wojdev has joined #openstack-meeting-312:19
*** yamamoto has quit IRC12:26
*** faizan_ has quit IRC12:37
*** markvoelker has joined #openstack-meeting-312:38
*** baoli has quit IRC12:42
*** markvoelker has quit IRC12:42
*** baoli has joined #openstack-meeting-312:43
*** Longgeek has joined #openstack-meeting-312:43
*** yamamoto has joined #openstack-meeting-313:02
*** markvoelker has joined #openstack-meeting-313:04
*** hareeshp has quit IRC13:05
*** yamamoto_ has joined #openstack-meeting-313:06
*** jroll has quit IRC13:07
*** jroll has joined #openstack-meeting-313:07
*** yamamoto has quit IRC13:09
*** JeanBriceCombebi has joined #openstack-meeting-313:15
*** mwagner_lap has quit IRC13:19
*** sarob has quit IRC13:20
*** sarob has joined #openstack-meeting-313:21
*** sarob has quit IRC13:26
*** banix has joined #openstack-meeting-313:32
*** JeanBriceCombebi has quit IRC13:32
*** banix has quit IRC13:34
*** JeanBriceCombebi has joined #openstack-meeting-313:35
*** banix has joined #openstack-meeting-313:39
*** megm has joined #openstack-meeting-313:47
*** megm_ has quit IRC13:47
*** wojdev has quit IRC13:53
*** sankarshan_away is now known as sankarshan13:54
*** absubram has joined #openstack-meeting-313:55
*** hareeshp has joined #openstack-meeting-313:58
*** sreshetnyak has joined #openstack-meeting-314:00
*** yamamoto_ has quit IRC14:01
*** yamamoto has joined #openstack-meeting-314:02
*** yamamoto has quit IRC14:02
*** julim has joined #openstack-meeting-314:03
*** wojdev has joined #openstack-meeting-314:03
*** mwagner_lap has joined #openstack-meeting-314:08
*** sarob has joined #openstack-meeting-314:09
*** bryan_att has joined #openstack-meeting-314:12
*** mattfarina has joined #openstack-meeting-314:18
*** lazy_prince has quit IRC14:19
*** sergef has quit IRC14:20
*** wojdev has quit IRC14:20
*** wojdev has joined #openstack-meeting-314:21
*** killer_prince has joined #openstack-meeting-314:24
*** killer_prince is now known as lazy_prince14:24
*** thangp has joined #openstack-meeting-314:25
*** yamamoto has joined #openstack-meeting-314:26
*** absubram has quit IRC14:28
*** peristeri has joined #openstack-meeting-314:30
*** lblanchard has joined #openstack-meeting-314:30
*** david-lyle has joined #openstack-meeting-314:31
*** VW_ has joined #openstack-meeting-314:35
*** yamamoto has quit IRC14:36
*** gholler has joined #openstack-meeting-314:36
*** banix has quit IRC14:36
*** banix has joined #openstack-meeting-314:37
*** sarob_ has joined #openstack-meeting-314:37
*** sarob has quit IRC14:39
*** zz_jgrimm is now known as jgrimm14:43
*** salv-orlando has joined #openstack-meeting-314:43
*** coolsvap is now known as coolsvap_14:43
*** banix has quit IRC14:55
*** mhanif has joined #openstack-meeting-315:00
*** mhanif has quit IRC15:01
*** xuhanp has joined #openstack-meeting-315:05
*** JeanBriceCombebi has quit IRC15:06
*** JeanBriceCombebi has joined #openstack-meeting-315:08
*** egallen has quit IRC15:10
*** absubram has joined #openstack-meeting-315:11
*** nelsnelson has joined #openstack-meeting-315:12
*** nelsnelson has quit IRC15:12
*** sarob_ is now known as sarob15:13
*** xuhanp has quit IRC15:17
*** pavel_bondar has joined #openstack-meeting-315:18
*** nelsnelson has joined #openstack-meeting-315:18
*** eghobo has joined #openstack-meeting-315:20
*** eghobo has quit IRC15:21
*** eghobo has joined #openstack-meeting-315:21
*** alexpilotti has joined #openstack-meeting-315:25
*** nelsnelson has quit IRC15:28
*** wuhg has quit IRC15:29
*** vikram has joined #openstack-meeting-315:32
*** vikram has quit IRC15:32
*** eghobo has quit IRC15:33
*** sigmavirus24 has joined #openstack-meeting-315:35
*** wojdev has quit IRC15:35
*** JeanBriceCombebi has quit IRC15:36
*** Piet has quit IRC15:37
*** annegentle has joined #openstack-meeting-315:42
*** carl_baldwin has joined #openstack-meeting-315:42
*** sahid has quit IRC15:43
*** egallen has joined #openstack-meeting-315:45
*** jaypipes has joined #openstack-meeting-315:46
*** lazy_prince has quit IRC15:47
*** iovadia has quit IRC15:48
*** JeanBriceCombebi has joined #openstack-meeting-315:51
*** sahid has joined #openstack-meeting-315:52
*** sahid has quit IRC15:52
*** sahid has joined #openstack-meeting-315:52
*** sahid has quit IRC15:56
*** wojdev has joined #openstack-meeting-315:57
*** thangp has quit IRC15:58
*** thangp has joined #openstack-meeting-315:59
*** erikmwilson has joined #openstack-meeting-316:00
*** ekarlso has quit IRC16:03
*** egallen has quit IRC16:03
*** banix has joined #openstack-meeting-316:05
*** annegentle has quit IRC16:06
*** annegentle has joined #openstack-meeting-316:06
*** mrunge has quit IRC16:08
*** ekarlso has joined #openstack-meeting-316:08
*** ChuckC has joined #openstack-meeting-316:08
*** egallen has joined #openstack-meeting-316:13
*** JoshNang has joined #openstack-meeting-316:14
*** sahid has joined #openstack-meeting-316:14
*** amotoki has quit IRC16:16
*** carl_baldwin has quit IRC16:16
*** jkoelker has joined #openstack-meeting-316:17
*** shwetaap has joined #openstack-meeting-316:18
*** egallen has quit IRC16:18
*** egallen has joined #openstack-meeting-316:19
*** ChuckC has quit IRC16:20
*** bpokorny_ has joined #openstack-meeting-316:20
*** carl_baldwin has joined #openstack-meeting-316:24
*** nelsnelson has joined #openstack-meeting-316:26
*** nelsnelson has quit IRC16:27
*** nelsnelson has joined #openstack-meeting-316:28
*** alexpilotti has quit IRC16:31
*** yamahata has joined #openstack-meeting-316:33
*** SridharRamaswamy has joined #openstack-meeting-316:36
*** david-lyle_afk has quit IRC16:37
*** david-lyle has quit IRC16:37
*** reed has joined #openstack-meeting-316:38
*** MaxV has quit IRC16:39
*** MarkAtwood has joined #openstack-meeting-316:45
*** MarkAtwood has quit IRC16:45
*** MarkAtwood has joined #openstack-meeting-316:45
*** Guest32544 is now known as redrobot16:51
*** killer_prince has joined #openstack-meeting-316:51
*** killer_prince is now known as lazy_prince16:51
*** annegent_ has joined #openstack-meeting-316:54
*** jcoufal has quit IRC16:54
*** regana has joined #openstack-meeting-316:57
*** scheuran_ has quit IRC16:57
*** annegentle has quit IRC16:58
*** evgenyf has quit IRC16:58
*** thinrichs1 has joined #openstack-meeting-316:59
*** jwy has joined #openstack-meeting-317:00
thinrichs1Hi all!17:01
thinrichs1This is the Congress meeting.17:01
thinrichs1#startmeeting CongressTeamMeeting17:01
openstackMeeting started Tue Mar  3 17:01:20 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs1. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:01
openstackThe meeting name has been set to 'congressteammeeting'17:01
thinrichs1Who do we have this week?17:01
*** bpokorny has joined #openstack-meeting-317:01
*** CTtpollard has left #openstack-meeting-317:02
*** MaxV has joined #openstack-meeting-317:02
thinrichs1jwy: I see you're here.  How's the Horizon UI going?17:02
jwyhi, good, i pushed what's there so far: https://review.openstack.org/#/c/160722/17:03
jwyfor policy creation and deletion17:03
jwyfew more things to do for that17:04
*** arosen1 has joined #openstack-meeting-317:04
arosen1Hi17:04
jwyhi17:04
jwyalso talked with Yali more about policy abstraction17:05
*** bpokorny_ has quit IRC17:05
jwyshe is working on a func spec for that17:05
*** david-lyle has joined #openstack-meeting-317:05
*** bpokorny has quit IRC17:05
jwyi also made some updates to horizon and the docs since the datasources are now retrieved by id instead of name17:06
jwywaiting for review on those. i think the ci might still be broken?17:06
thinrichs1Not sure about the CI.  We've been having trouble with our cloud of late.17:07
arosen1Yea hopefully that will be under control soon17:07
thinrichs1It's great that you're making progress!17:07
arosen1some how the python unit tests in our repo broke17:07
arosen1I haven't tracked down how this is possible yet (I wanna ping the guys in the infra channel about it)17:07
*** alexsyip has joined #openstack-meeting-317:07
arosen1but i have a fix that should merge in a sec that makes the tests pass again.17:08
thinrichs1Did the Makefile change get merged yet?17:08
arosen1https://review.openstack.org/#/c/160680/17:08
arosen1thinrichs1: not yet that doesn't unblock the tests.17:08
arosen1hrm weird i see the tests did pass on your patch17:09
thinrichs1The tests *should* be failing without that patch.17:09
thinrichs1We shouldn't be able to parse anything.17:09
arosen1thinrichs1: the tests passed on my patch that isn't rebased on yours though.17:09
thinrichs1Locally is different b/c you still have the output of the Makefile sittig around.17:10
arosen1thinrichs1:  I don't mean locally.17:10
arosen1If you click on that link jenkins +1'ed it.17:10
thinrichs1Maybe there's a Python-path thing happening somehow.17:11
thinrichs1Not sure.17:11
arosen1also i'm not sure how we could break the unit tests without jenkins stopping it from merging17:11
thinrichs1But Jenkins also let in the deletion of the config file.17:11
arosen1since they would have had to pass at one point.17:11
*** alexpilotti has joined #openstack-meeting-317:11
*** qwebirc50941 has joined #openstack-meeting-317:11
arosen1in that case i'm sure the unit tests were passing then (not sure which config file you're talking about).17:12
*** bpokorny has joined #openstack-meeting-317:12
thinrichs1The missing test_datasource_driver_config.py.17:12
arosen1ah yea!17:12
arosen1That one i want to dig deep and figure out how this could occur17:12
jwysorry, which patch are we talking about that passed17:12
*** syrus has left #openstack-meeting-317:12
*** Longgeek has quit IRC17:12
arosen1jwy: https://review.openstack.org/#/c/160680/17:12
jwyi see failure for http://logs2.aaronorosen.com/80/160680/1/check/dsvm-tempest-full-congress-pg-nodepool/917a56817:13
arosen1jwy:  yea the cloud is flaky right now17:13
arosen1the gateways are over loaded and connections timeout :(17:13
jwywhich part are you saying passed?17:13
arosen1the python unittests17:14
arosen1they failed to pass in the gate pipe line but they passed on check17:14
jwyok17:14
thinrichs1This one passed too but probably shouldn't have.17:14
thinrichs1https://review.openstack.org/#/c/158489/17:14
arosen1thinrichs1:  anyways lets do a little investigating later on and try and nail down what happened.17:15
thinrichs1arosen1: Sounds good.17:15
thinrichs1Back to status updates.17:16
thinrichs1jwy: thanks for the update.17:16
thinrichs1arosen1: want to give a status update?17:16
arosen1thinrichs1: sure17:17
arosen1so I haven't done much on congress the last week or so. Most of my time was sucked up trying to help debug our cloud17:17
arosen1that's it from me for now...17:18
*** Longgeek has joined #openstack-meeting-317:18
thinrichs1arosen1: thanks.17:19
thinrichs1sarob couldn't attend but sent his status via email.17:19
*** sahid has quit IRC17:20
thinrichs1He cleaned up  https://launchpad.net/congress/kilo17:20
thinrichs1He tagged https://github.com/stackforge/congress/tree/2015.1.0b217:20
thinrichs1He is still working out getting the tarred file out to http://tarballs.openstack.org/ as part of the process17:20
*** stevenldt_ has joined #openstack-meeting-317:20
*** Longgeek has quit IRC17:21
thinrichs1This seems like a good step toward getting us into the OS release cadence.17:21
thinrichs1I believe kilo3 is mid-March, so a couple weeks away.17:22
*** JeanBriceCombebi has quit IRC17:22
thinrichs1I think we'll delay code freeze to say 3-4 weeks before the summit, since we don't have a ton of stabilization to do.17:22
*** ChuckC has joined #openstack-meeting-317:23
thinrichs1That should give us enough time to do some testing, round out the features/bugs that we want available, and still have time to work on some specs for the summit.17:23
thinrichs1How does that sound?17:24
*** thomasem has joined #openstack-meeting-317:24
arosen1sounds good to me!17:24
alexsyipsame here17:24
jwysure17:25
thinrichs1So that'll be the plan moving forward then.17:25
thinrichs1alexsyip: want to give a status update?17:25
alexsyipI’ve been working on high availability for the congress server + datasource drivers.17:25
alexsyipFor a first cut, we’ll runn two completely replicated congress servers, where each replica will fetch data from the data sources17:26
alexsyipand clients can make api calls to either replica17:26
*** wojdev has quit IRC17:27
alexsyipWrites (for things like rules and datasource config) will go to the database, and congress server will pull new changes on a period basis.17:27
arosen1nice, sound good to me alexsyip17:28
thinrichs1Sounds like the right first cut to me.17:28
thinrichs1Excited about HA!17:28
alexsyipCurrently, I’m setting up a tempest test to run in this configuration.17:28
*** melwitt has joined #openstack-meeting-317:29
alexsyipthat’s all17:30
thinrichs1That reminds me—we should fix up our logging so we don't fill up the disk (and crash).17:30
arosen1thinrichs1: where did you see this problem?17:30
arosen1in devstack?17:30
thinrichs1alexsyip: do you have a blueprint for HA?17:30
arosen1I think that logging that jwy pointed out was in horizon17:30
alexsyipI’m working on an HA17:30
alexsyipblueprint.17:30
thinrichs1arosen1: if we're going for HA, and we never empty out the logs, we'll eventually fill up the disk.17:31
thinrichs1And crash, thereby making HA harder.17:31
alexsyipActually, I think I already made the blueprint, but not the spec17:31
arosen1thinrichs1:  I don't think that's really related to HA per say17:31
arosen1are you talking about syslog?17:31
arosen1like output from congress-server logs?17:31
thinrichs1Just the other day I saw ceilometer fill up the disk with its log.17:31
thinrichs1arosen1: yes17:32
arosen1thinrichs1:  the ceilometer in cloud or devstack ?17:32
alexsyipHere’s the blueprint: https://blueprints.launchpad.net/congress/+spec/query-high-availability17:32
*** e0ne has quit IRC17:32
arosen1I think logrotate is probably not configured in that case thinrichs117:32
thinrichs1arosen1: so you're saying it's easy to fix the logging so it doesn't fill up the disk?17:32
arosen1yes17:33
*** wojdev has joined #openstack-meeting-317:33
arosen1logrotate does it for you17:33
*** sarob has quit IRC17:33
arosen1it tar.gz's your logs and deletes them eventually if it's running out of diskspace17:33
thinrichs1If we don't have that turned on, let's turn it on by default now.17:33
arosen1it shouldn't ever run out of diskspace in devstack though if it's dupping the output to screen.17:33
arosen1on a proper install logrotate would handle this.17:34
arosen1sorry battery is about to die on the train :(17:34
*** arosen1 has quit IRC17:34
thinrichs1Whatever we need to do to make sure we don't fill up the disk, (whether we're running as part of devstack or standalone), let's add a bug/blueprint to make sure that happens.17:34
thinrichs1If it's an deployment option, let's make sure it's documented and on-by-default.17:35
thinrichs1I added a blueprint for this and made it a dependency on query-high-availability.17:37
thinrichs1I guess I'll give a quick status update.17:37
thinrichs1Now that datasources are spun up/down at runtime, we need to be more careful with how we deal with column-references in policy rules.17:38
thinrichs1Remember that a column-reference is where we identify the value for a column using its name, not its position.17:38
thinrichs1Example: p(id=x, name=y) asks for the column named 'id' to be variable x and the column named 'name' to be variable y.17:39
thinrichs1Previously we were compiling these into the usual datalog version *at read-time*.17:39
thinrichs1To do that we needed to know the schema for all the tables *at read-time*.17:40
thinrichs1If our schema for table p has columns ('name', 'id', 'status'), then we would compile the example above into...17:40
thinrichs1p(y, x, z)17:40
thinrichs1But since datasources are spun up/down at runtime, we no longer know the schema at read-time, so we can't do this compilation any longer.17:41
thinrichs1So I'm adding support for column references into the heart of the evaluation algorithms.17:41
thinrichs1We'll still be able to do schema-consistency checking (making sure people don't reference non-existent columns), but we'll want to do it whenever a schema change occurs, e.g. spin up a new datasource.17:41
thinrichs1Hope that made some sense.17:42
thinrichs1It should be transparent to the user.17:42
thinrichs1That's it for me.17:43
jwyis this related to the issue with a policy table like nova:servers being empty now?17:43
thinrichs1jwy: Yes that's where I noticed the problem.17:43
thinrichs1Say we have a rule like  p(x) :- q(id=x) in the database.17:43
thinrichs1Sorry.. different rule.17:44
thinrichs1p(x) :- nova:q(id=x)17:44
thinrichs1If we startup/restart Congress and try to load that rule, we won't know the schema for q because Nova hasn't necessarily been spun up yet.17:44
thinrichs1So we won't load it; we'll throw an error.17:45
jwyah17:45
thinrichs1jwy: the original problem was that we weren't even trying to load the rules into the policy engine.17:45
thinrichs1So we didn't get an error.  We just didn't load anything.17:45
thinrichs1Then once I fixed it to actually load the rules, I saw the errors.17:45
jwyglad you found those!17:46
thinrichs1jwy: thanks for pointing those out.17:46
thinrichs1I think it's probably a weird case when this would actually be problematic.17:46
thinrichs1But it's just not functional as it stands.17:46
thinrichs1And if someone deletes a datasource named 'nova' and creates a new one also called 'nova', we weren't doing the right thing.17:47
thinrichs1This should fix all that.17:47
thinrichs1Okay.  Time to open it up for discussion.17:47
thinrichs1Oops.. first: is anyone else here that wants to give a status update?17:48
thinrichs1Okay—open discussion it is.17:49
thinrichs1#topic open discussion17:49
*** openstack changes topic to "open discussion (Meeting topic: CongressTeamMeeting)"17:49
*** yamahata has quit IRC17:49
*** megm_ has joined #openstack-meeting-317:49
*** megm has quit IRC17:49
*** sarob has joined #openstack-meeting-317:49
jwyit's daylight savings this weekend, so the local time for this meeting for some folks will change17:51
jwystarting next week17:51
thinrichs1jwy: thanks for the reminder!17:52
*** eghobo has joined #openstack-meeting-317:52
thinrichs1Thanks for the meeting all!  See you next week (an hour later b/c of daylight savings for some of us, I believe).17:53
*** jwy has quit IRC17:53
thinrichs1#endmeeting17:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:53
openstackMeeting ended Tue Mar  3 17:53:09 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-03-03-17.01.html17:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-03-03-17.01.txt17:53
*** wojdev has quit IRC17:53
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-03-03-17.01.log.html17:53
*** stevenldt_ has quit IRC17:53
*** jwy has joined #openstack-meeting-317:53
*** jwy has quit IRC17:54
*** bpokorny_ has joined #openstack-meeting-317:54
*** igordcard has quit IRC17:56
*** bpokorny has quit IRC17:57
*** goalotc has quit IRC17:59
*** regana has quit IRC17:59
*** sandr8 has quit IRC18:00
*** SridharRamaswamy has quit IRC18:00
*** goalotc has joined #openstack-meeting-318:01
*** SridharRamaswamy has joined #openstack-meeting-318:02
*** sandr8 has joined #openstack-meeting-318:02
*** sandr8 has quit IRC18:02
*** goalotc has quit IRC18:03
*** goalotc has joined #openstack-meeting-318:03
*** marun has joined #openstack-meeting-318:06
*** jaypipes has quit IRC18:07
*** jaypipes has joined #openstack-meeting-318:10
*** qwebirc50941 has quit IRC18:12
*** sankarshan is now known as sankarshan_away18:15
*** alexpilotti_ has joined #openstack-meeting-318:16
*** ivar-lazzaro has joined #openstack-meeting-318:16
*** alexpilotti has quit IRC18:16
*** alexpilotti_ is now known as alexpilotti18:16
*** s3wong has joined #openstack-meeting-318:19
*** yamahata has joined #openstack-meeting-318:20
*** yamahata has quit IRC18:21
*** yamahata has joined #openstack-meeting-318:22
*** bpokorny has joined #openstack-meeting-318:31
*** bpokorny_ has quit IRC18:34
*** SridharRamaswamy has quit IRC18:35
*** terrylhowe has joined #openstack-meeting-318:36
*** MaxV has quit IRC18:37
*** thinrichs1 has left #openstack-meeting-318:43
*** peristeri has quit IRC18:47
*** peristeri has joined #openstack-meeting-318:47
*** bpokorny_ has joined #openstack-meeting-318:49
*** SumitNaiksatam has joined #openstack-meeting-318:50
*** bpokorny has quit IRC18:52
*** Sukhdev has joined #openstack-meeting-318:57
*** yamahata has quit IRC18:59
*** SridharRamaswamy has joined #openstack-meeting-318:59
*** yamahata has joined #openstack-meeting-318:59
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Mar  3 19:00:15 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
briancurtinif you're here for the SDK meeting, say hi19:00
*** lazy_prince has quit IRC19:00
*** stevelle has joined #openstack-meeting-319:01
terrylhoweTerry Howe, HP19:01
stevelleSteve Lewis, Rackspace19:01
briancurtinBrian Curtin19:01
briancurtinand Ian will be late, so that's our usual crew19:02
briancurtinhere's a little agenda https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2015-03-01_1900_UTC19:02
*** LouisF has joined #openstack-meeting-319:02
briancurtin#topic conn.update vs conn.compute.update_server - https://review.openstack.org/#/c/160635/19:02
*** openstack changes topic to "conn.update vs conn.compute.update_server - https://review.openstack.org/#/c/160635/ (Meeting topic: python-openstacksdk)"19:02
etoewso/19:02
briancurtinthat topic, or ones like it, had come up in the past, but after working with the update_server call, i really like it, but also see the use case for conn.update (which i previously disliked)19:03
*** peristeri has quit IRC19:03
*** SridharRamaswam1 has joined #openstack-meeting-319:03
*** SridharRamaswamy has quit IRC19:04
briancurtinthey support two different needs, with conn.update there if you want to update attributes on a resource and pass it in, or conn.compute.update_server (or really any update call on any resource in any service) being a way to accomplish the same thing via a function call19:05
*** peristeri has joined #openstack-meeting-319:05
briancurtinthe update_server way fits more closely with the way something like create_server works, so it looks pretty clean. i dont usually like providing multiple ways to do the same thing, but the conn.update method isn't something i think should have to go away, but it isn't something that we'd push as hard as the more resource-specific way to fit that mold19:06
terrylhoweseems like most people would be updating a server through the properties rather than through a dictionary19:06
stevelle+1, for update scenarios19:07
*** alexsyip has quit IRC19:07
stevellethinking on it however19:07
briancurtinterrylhowe: i think doing it via dictionary is probably the least likely case, but making use of the keyword arguments to pass in is super nice19:07
*** jtomasek has quit IRC19:08
briancurtinupdate_server(server, name="new name") is pretty hard to top, or in the case terry brought up that i broke, update_server(id="theid", name="new name")19:09
briancurtingiven how create_server(name, flavor, image) works, i'd like to allow update_server to look the same19:10
terrylhoweserver.name=“new name” #just seems like the more normal way to me19:10
briancurtinanother part of the reason i'd like to have update_server is that it allows you to stay within one context. doing your server operations on conn.compute.<something>_server feels nicer than having to jump from methods on conn.compute to methods straight on conn19:11
briancurtinthe server_builder example looks a bit nicer with create and update operations both being on conn.compute. the diff between patchset 1 and 2 shows how it changed19:12
stevellehow about update_by(name=None, id=None, **data) for the alternate form?19:13
terrylhowewe could move the generic updates, create etc to the base proxy class19:13
briancurtinwhat does  update_by mean?19:13
*** egallen has quit IRC19:13
terrylhoweby_id maybe like the resource class19:13
*** Rockyg has joined #openstack-meeting-319:14
briancurtinthat's too low level - you could just use the resource class directly then19:14
stevelleI guess my thinking is that Terry's syntax could be supported by  that means19:15
stevelleby_id("theid", name="new name") or the like19:15
briancurtinjust so my thought process is out there, i think the *main* usage is in the methods on a service, so compute.create_server, compute.delete_server, compute.update_server, etc. conn.create, conn.delete, conn.update, and the like are what i consider the alternate form19:15
*** Yi has joined #openstack-meeting-319:16
stevelleif you have a server and want to update it, use update_server.  If you don't, use the other form and specify an identifier19:16
stevellethe name I suggested was just to allow update_by(id="theid", [...])19:17
briancurtini just dont understand the name update_by. the update is done on an ID, and the _by name seems confusing. it kind of evokes a SQL feeling and doesn't seem to fit in the higher level19:17
sigmavirus24hm19:18
stevellethe name is not important for me.19:18
* sigmavirus24 scrolls backwards19:18
briancurtineven if you dont have the server object, update_server(id=1, name="new") will cover that19:18
briancurtin(right now i build off a passed in server obj, but i'm going to change that to default to none so that previous message works)19:19
terrylhowemaybe if update_server just didn’t take **data instead19:19
briancurtintaking **data is the best thing about it though19:19
terrylhoweit would be kind of repetitive to what is out there, but more ituitive for the user19:19
terrylhowe:)19:20
*** VW_ has quit IRC19:20
stevellesorry I'm thinking through the alternatives at the expense of the group's time19:20
briancurtinif it takes **data is just takes the attributes on the resource. i'm liking this way a ton more than what i did for object_store, as in i'm thinking about making a temporary object_store2 that fits more with how compute is done so we can see side-by-side how it works19:20
*** Piet has joined #openstack-meeting-319:21
briancurtini totally didn't really see how a lot of the current proxies, basically anything outside of object_store, were going to work, but after we got a bunch of stuff out of the way, they're more powerful than object_store's manual stuff19:21
* sigmavirus24 isn't familiar enough with all of the proxies to be helpful here19:23
terrylhoweto me the **data makes it look like the correct way to update an object is by passing in name values19:23
terrylhowethere is also the problem of we have no method to create a new server without calling GET right now19:24
briancurtinwhat's wrong with create_server?19:24
terrylhowethat doesn’t help for a server that exists19:24
*** VW_ has joined #openstack-meeting-319:25
terrylhoweI would just think some people would want to update an object without a call to GET19:25
sigmavirus24terrylhowe: I would think likewise19:25
briancurtini think i'm missing what we're talking about here19:25
sigmavirus24but in reality, the connection pooling in requests makes the extra request/response time tie directly to bandwidth and how long it takes the server to respond19:26
sigmavirus24briancurtin: I'm agreeing the general let's not have one method make two requests19:26
briancurtinwhat method makes two requests?19:26
etoewsterrylhowe: can you throw out some example user code of what user's can (or can't) do?19:26
sigmavirus24but I'm not familiar with the code terrylhowe is mentioning19:26
etoewsi think that would clear things up quickly19:26
terrylhowewith this update_server you need a server19:26
terrylhoweserver = conn.compute.existing_server(‘id’:’foo’)19:27
terrylhoweserver.name = ‘bar’19:27
terrylhoweconn.compute.update_server(server)19:27
terrylhowewe’d need some method like existing to create one with no GET19:28
briancurtinif you have the id, you could just do update_server(id="foo", name="bar") **after i make the change that's in the comment on the review19:28
terrylhoweah, the None default19:28
briancurtinif you happen to actually have a server already that you've received through a GET, you can pass it directly in, but you shouldn't need to19:28
briancurtinterrylhowe: yep - if it's none, you'll have to pass in the ID (no way around it), but you won't need to GET just to have an object to pass in19:29
briancurtini'm currently working on some API guidelines as i'm writing some stuff, and i'll put together a doc that includes all of the possible ways you can do these operations and then see if/where we need to coalesce or expand19:31
sigmavirus24ah19:31
sigmavirus24makes sense19:31
*** jckasper has joined #openstack-meeting-319:32
briancurtinsince we spent a half hour on that, i'll write up more of the doc and share it and we can discuss further with more concrete examples19:32
stevellebriancurtin: in cases where patch is not supported will that work uniformly across different service APIs?19:32
briancurtin#topic put vs patch19:33
*** openstack changes topic to "put vs patch (Meeting topic: python-openstacksdk)"19:33
briancurtinstevelle: we currently have to have resources specify if they use PUT for updates, defaulting to PATCH. from what i can tell, we should maybe switch that, so PATCH users have to specify instead of the more common PUT having to specify19:34
*** killer_prince has joined #openstack-meeting-319:35
*** killer_prince is now known as lazy_prince19:35
briancurtinso your conn.update or conn.service.resource_update will work however you've configured the resource you're operating on19:35
*** ivar-laz_ has joined #openstack-meeting-319:36
terrylhowethat might be for the best, not sure how many support PATCH.  maybe just open a ticket to investigate19:36
*** lsmola has quit IRC19:36
terrylhoweif there isn’t one already19:36
briancurtini opened one last night19:36
etoewsthere's a handful that use PATCH and more using it all the time19:36
briancurtinPATCH shows up a few times in identity v3 and then once in another service i can't think of19:36
etoewsglance19:37
etoewspoppy19:37
etoewszaqar19:37
briancurtinetoews: what is more popular: put or patch19:37
etoewsput19:37
terrylhoweencyclopedia etoews !19:37
*** yapeng has quit IRC19:38
briancurtinetoews: is there an overall trend towards patch, or is this just newer projects wanting to use it? currently we get patch by default but have to specify for put, which currently feels backwards19:38
terrylhoweanyway, research done.  PUT should be default19:38
*** ivar-lazzaro has quit IRC19:39
sigmavirus24briancurtin: I expect the API WG to suggest PATCH for updates (if we don't already have a guideline along those lines)19:39
etoewsi feel like there's a trend towards PATCH but can't quantify or even qualify this.19:39
etoewssigmavirus24: +119:39
sigmavirus24etoews: we're everywhere lately ;)19:40
stevelleI feel like expressing the resource's expectation in terms of PATCH is more meaningful and clear.19:40
stevelleeven if default is False19:41
briancurtini'm sitll with terrylhowe on PUT being the default just given reality of what we have to live with now and over the next while19:41
sigmavirus24So inspite of what new APIs should be doing19:42
sigmavirus24For now, it makes sense to default to PUT19:42
sigmavirus24I garee with Brian and Terry since we're trying to provide the best interface to those APIs19:42
stevelledefault clearly should point at PUT, either way.19:42
sigmavirus24I want to suggest an attribute like 'update_method' that defaults to PUT19:42
sigmavirus24Because I think booleans are tricky here19:42
sigmavirus24But I can see if we don't want to accept put/PUT patch/PATCH or whatever else for a resource19:43
briancurtinsigmavirus24: i dont know how that will work with how we do the actual Resource.update19:43
sigmavirus24Yeah I have to look but if we used session.request we'd be able to pass it directly as the first argument, no conditionals necessary19:44
sigmavirus24briancurtin: just an idea, it doesn't change what the default behaviour should be though19:44
briancurtini think short term we should just flip that default, but explore how to make it better after that19:44
sigmavirus24briancurtin: +119:44
briancurtin#action fix https://bugs.launchpad.net/python-openstacksdk/+bug/1427479 to flip the default from patch to put19:44
openstackLaunchpad bug 1427479 in OpenStack SDK "switch put_update to be patch_update" [Medium,New]19:44
briancurtin#topic need to implement CaseInsensitiveDict for header dict19:45
*** openstack changes topic to "need to implement CaseInsensitiveDict for header dict (Meeting topic: python-openstacksdk)"19:45
briancurtinthat's sort of a note for me - we implemented the CID, then added the separate header storage, but never used the CID for it19:45
terrylhoweshould be easy to do19:46
briancurtin#action finish https://bugs.launchpad.net/python-openstacksdk/+bug/1422234 to combine the resource.header storage with the CaseInsensitiveDict19:46
openstackLaunchpad bug 1422234 in OpenStack SDK "Case sensitivity in resource.prop doesn't work with headers" [Critical,New] - Assigned to Brian Curtin (brian.curtin)19:46
briancurtin(i'm trying to get better at actually using meetbot)19:46
briancurtin#topic identity: use set() for valid_options https://review.openstack.org/#/c/160840/19:47
*** openstack changes topic to "identity: use set() for valid_options https://review.openstack.org/#/c/160840/ (Meeting topic: python-openstacksdk)"19:47
briancurtinsome details aside, it seems like using a set here is actually fine? (i jumped in with something on KSC that i forgot is not true)19:47
stevelleagreed19:48
terrylhoweit makes sense to me, I think the change is good19:48
* sigmavirus24 agrees as well19:48
briancurtincool, will take another look after this19:48
terrylhoweI didn’t understand the perf implications19:48
sigmavirus24terrylhowe: which ones?19:48
sigmavirus24the ones in the most recent patch?19:48
terrylhowethere was some mention in a comment19:49
*** lsmola has joined #openstack-meeting-319:49
sigmavirus24it's a matter of convertiing a set to a list and adding multiple lists together and then converting back to a set19:49
terrylhoweah19:49
sigmavirus24so creating 4 linked lists + a 5th from the previous 4th is a performance drag19:49
sigmavirus24I provided an alternative to the rather ugly first attempt19:49
*** MaxV has joined #openstack-meeting-319:49
sigmavirus24But instead of using the alternative that i proposed, Julien chose to use this new approach19:49
sigmavirus24sets do make more sense and if we do any kind of opt in valid_options will make that much faster19:50
sigmavirus24__contains__ for lists are O(n)19:50
briancurtingiven the tiny size, i dont think it's something to even worry about, really - readability matters more than there speed (and correctness matters, too)19:50
etoewsbriancurtin: +119:50
sigmavirus24briancurtin: _union(A.valid_options, B.valid_options, C.valid_options) is both readable and fast ;)19:51
briancurtinotherwise i'd like to see benchmarks if we're going to make changes to actually optimize code for performance19:51
terrylhowethe code is only used during auth19:51
briancurtinyep, it's really not a big deal, so as long as it's readable and correct, it's good19:52
sigmavirus24And only executed when the class definition is loaded by Python19:52
sigmavirus24it's a one time hit so it isn't a problem19:52
terrylhowesigmavirus24: suggest was good, but what is out there is probably good enough19:52
sigmavirus24if it happened every time auth was instantiated it might be a problem then19:52
briancurtintelling people you want to see benchmarks usually results in them realizing it's not actually important for performance19:52
sigmavirus24terrylhowe: I'm just joking. I don't care if Julien listens to me19:52
terrylhowewell, green light that19:53
briancurtinwill take a look in a few minutes19:53
briancurtinanything else to cover in the last few minutes?19:53
terrylhowethe tenant_id one I’d just like to try it out and make sure it works as expected19:54
terrylhowehttps://review.openstack.org/#/c/160821/219:55
briancurtinyeah i'll try that out as well19:55
*** MaxV has quit IRC19:58
briancurtinthanks everyone!19:59
briancurtin#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Mar  3 19:59:28 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-03-03-19.00.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-03-03-19.00.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-03-03-19.00.log.html19:59
*** MaxV has joined #openstack-meeting-320:00
*** MarkAtwood has quit IRC20:00
*** VW_ has quit IRC20:04
*** SridharRamaswam1 has quit IRC20:04
*** yapeng has joined #openstack-meeting-320:04
*** VW_ has joined #openstack-meeting-320:05
*** ChuckC has quit IRC20:05
*** ivar-laz_ has quit IRC20:05
*** matrohon has joined #openstack-meeting-320:06
*** ivar-lazzaro has joined #openstack-meeting-320:06
*** MaxV has quit IRC20:10
*** MarkAtwood has joined #openstack-meeting-320:10
*** egallen has joined #openstack-meeting-320:10
*** e0ne has joined #openstack-meeting-320:11
*** SridharRamaswamy has joined #openstack-meeting-320:12
*** MaxV has joined #openstack-meeting-320:13
*** hareeshp has quit IRC20:15
*** hareeshp has joined #openstack-meeting-320:16
*** hareeshp has quit IRC20:22
*** jckasper has quit IRC20:26
*** sbalukoff has quit IRC20:29
*** e0ne is now known as e0ne_20:29
*** e0ne_ has quit IRC20:30
*** e0ne has joined #openstack-meeting-320:31
*** sbalukoff has joined #openstack-meeting-320:31
*** peristeri has quit IRC20:31
*** e0ne has quit IRC20:33
*** LouisF has quit IRC20:35
*** e0ne has joined #openstack-meeting-320:39
*** MaxV has quit IRC20:41
*** egallen_ has joined #openstack-meeting-320:43
*** mrda-away is now known as mrda20:44
*** MaxV has joined #openstack-meeting-320:44
*** MaxV has quit IRC20:45
*** peristeri has joined #openstack-meeting-320:45
*** egallen has quit IRC20:47
*** egallen_ is now known as egallen20:47
*** terrylhowe has left #openstack-meeting-320:47
*** VW_ has quit IRC20:49
*** peristeri has quit IRC20:50
*** mrmartin has quit IRC20:51
*** peristeri has joined #openstack-meeting-320:52
*** MaxV has joined #openstack-meeting-320:52
*** e0ne has quit IRC20:55
*** Sukhdev has quit IRC20:57
*** VW_ has joined #openstack-meeting-320:58
*** clu_ has joined #openstack-meeting-321:00
*** SridharRamaswamy has quit IRC21:02
*** SridharRamaswamy has joined #openstack-meeting-321:02
*** sergef has joined #openstack-meeting-321:14
*** hareeshp has joined #openstack-meeting-321:17
*** gugl2 has joined #openstack-meeting-321:22
*** eghobo has quit IRC21:25
*** gugl has quit IRC21:25
*** ChuckC has joined #openstack-meeting-321:26
*** wojdev has joined #openstack-meeting-321:31
*** gugl3 has joined #openstack-meeting-321:31
*** eghobo has joined #openstack-meeting-321:34
*** gugl2 has quit IRC21:35
*** sergef has quit IRC21:36
*** egallen has quit IRC21:36
*** egallen has joined #openstack-meeting-321:37
*** wojdev has quit IRC21:41
*** egallen has quit IRC21:42
*** wojdev has joined #openstack-meeting-321:42
*** thangp has quit IRC21:43
*** SridharRamaswamy has quit IRC21:47
*** egallen has joined #openstack-meeting-321:47
*** hareeshp has quit IRC21:49
*** megm has joined #openstack-meeting-321:51
*** megm_ has quit IRC21:51
*** wojdev has quit IRC21:52
*** SridharRamaswamy has joined #openstack-meeting-321:53
*** julim has quit IRC21:54
*** SridharRamaswamy has quit IRC21:56
*** jgrimm is now known as zz_jgrimm21:57
*** egallen has quit IRC21:57
*** mattfarina has quit IRC21:59
*** SridharRamaswamy has joined #openstack-meeting-322:01
*** wojdev has joined #openstack-meeting-322:01
*** ivar-laz_ has joined #openstack-meeting-322:01
*** ivar-laz_ has quit IRC22:02
*** ivar-laz_ has joined #openstack-meeting-322:03
*** zz_jgrimm is now known as jgrimm22:03
*** ivar-lazzaro has quit IRC22:04
*** mwagner_lap has quit IRC22:06
*** safchain has quit IRC22:09
*** devlaps has joined #openstack-meeting-322:13
*** devlaps has quit IRC22:13
*** wojdev has quit IRC22:16
*** jckasper has joined #openstack-meeting-322:17
*** MaxV has quit IRC22:18
*** lblanchard has quit IRC22:21
*** wojdev has joined #openstack-meeting-322:23
*** e0ne has joined #openstack-meeting-322:26
*** Piet has quit IRC22:29
*** sarob has quit IRC22:31
*** alexsyip has joined #openstack-meeting-322:32
*** jckasper has quit IRC22:39
*** Rockyg has quit IRC22:39
*** jckasper has joined #openstack-meeting-322:39
*** banix has quit IRC22:39
*** thomasem has quit IRC22:41
*** Yi has quit IRC22:43
*** annegent_ has quit IRC22:49
*** mwagner_lap has joined #openstack-meeting-322:53
*** wojdev has quit IRC22:53
*** peristeri has quit IRC22:53
*** wojdev has joined #openstack-meeting-322:57
*** erikmwilson is now known as Guest2816423:01
*** erikmwilson has joined #openstack-meeting-323:01
*** erikmwilson has quit IRC23:01
*** Guest28164 has quit IRC23:01
*** erikmwilson has joined #openstack-meeting-323:02
*** gholler has quit IRC23:02
*** ivar-laz_ has quit IRC23:02
*** ivar-lazzaro has joined #openstack-meeting-323:03
*** ivar-lazzaro has quit IRC23:04
*** ivar-lazzaro has joined #openstack-meeting-323:05
*** egallen has joined #openstack-meeting-323:06
*** absubram has quit IRC23:08
*** yamamoto has joined #openstack-meeting-323:11
*** sarob has joined #openstack-meeting-323:12
*** Yi has joined #openstack-meeting-323:15
*** matrohon has quit IRC23:19
*** alexpilotti has quit IRC23:19
*** Yi has quit IRC23:25
*** Yi has joined #openstack-meeting-323:26
*** jckasper has quit IRC23:26
*** e0ne has quit IRC23:30
*** e0ne has joined #openstack-meeting-323:34
*** yamamoto has quit IRC23:36
*** sigmavirus24 is now known as sigmavirus24_awa23:36
*** erikmwilson has quit IRC23:41
*** eghobo_ has joined #openstack-meeting-323:44
*** eghobo has quit IRC23:45
*** e0ne has quit IRC23:47
*** Sukhdev has joined #openstack-meeting-323:49
*** annegentle has joined #openstack-meeting-323:49
*** jgrimm is now known as zz_jgrimm23:50
*** nelsnelson has quit IRC23:52
*** watanabe_isao has joined #openstack-meeting-323:57
*** MarkAtwood has quit IRC23:59
*** yamamoto has joined #openstack-meeting-323:59

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