Monday, 2015-11-23

*** banix has joined #openstack-meeting-300:13
*** salv-orlando has quit IRC00:13
*** pavel_bondar has quit IRC00:25
*** hoangcx has joined #openstack-meeting-300:41
*** hoangcx has left #openstack-meeting-300:41
*** yamamoto has quit IRC00:55
*** ihrachys has joined #openstack-meeting-300:55
*** egallen has quit IRC00:57
*** Sukhdev has quit IRC00:58
*** ihrachys has quit IRC01:00
*** msambol has quit IRC01:00
*** banix has quit IRC01:04
*** yamamoto has joined #openstack-meeting-301:07
*** salv-orlando has joined #openstack-meeting-301:14
*** gcb has joined #openstack-meeting-301:22
*** julim has quit IRC01:27
*** shaohe_feng has joined #openstack-meeting-301:31
*** masterbound has quit IRC01:31
*** salv-orlando has quit IRC01:32
*** stanzgy has joined #openstack-meeting-301:40
*** btully has quit IRC01:43
*** shaohe_feng1 has joined #openstack-meeting-301:45
*** zhenguo has joined #openstack-meeting-301:48
*** shaohe_feng has quit IRC01:48
*** banix has joined #openstack-meeting-301:50
*** shaohe_feng has joined #openstack-meeting-301:53
*** shaohe_feng1 has quit IRC01:54
*** msambol has joined #openstack-meeting-302:01
*** galstrom_zzz is now known as galstrom02:04
*** banix has quit IRC02:05
*** galstrom is now known as galstrom_zzz02:05
*** msambol has quit IRC02:05
*** shaohe_feng1 has joined #openstack-meeting-302:09
*** shaohe_feng has quit IRC02:11
*** banix has joined #openstack-meeting-302:15
*** ihrachys has joined #openstack-meeting-302:27
*** ihrachys has quit IRC02:31
*** salv-orlando has joined #openstack-meeting-302:32
*** masterbound has joined #openstack-meeting-302:32
*** masterbound has quit IRC02:37
*** sdake has joined #openstack-meeting-302:41
*** ihrachys has joined #openstack-meeting-302:43
*** sdake_ has joined #openstack-meeting-302:47
*** ihrachys has quit IRC02:47
*** sdake has quit IRC02:48
*** salv-orlando has quit IRC02:48
*** yantarou has quit IRC02:49
*** yantarou has joined #openstack-meeting-302:51
*** klkumar has joined #openstack-meeting-302:51
*** sankarshan_away is now known as sankarshan02:51
*** beekhof has quit IRC02:51
*** shaohe_feng1 has quit IRC02:56
*** sdake_ has quit IRC03:05
*** coolsvap has quit IRC03:16
*** msambol has joined #openstack-meeting-303:17
*** coolsvap has joined #openstack-meeting-303:19
*** ihrachys has joined #openstack-meeting-303:23
*** ihrachys has quit IRC03:27
*** banix has quit IRC03:29
*** neelashah has joined #openstack-meeting-303:35
*** Sukhdev has joined #openstack-meeting-303:36
*** neelashah has quit IRC03:37
*** msambol has quit IRC03:38
*** salv-orlando has joined #openstack-meeting-303:47
*** salv-orlando has quit IRC03:55
*** shwetaap has joined #openstack-meeting-303:55
*** wuhg has joined #openstack-meeting-303:55
*** galstrom_zzz is now known as galstrom04:33
*** msambol has joined #openstack-meeting-304:38
*** kebray has joined #openstack-meeting-304:39
*** kebray has quit IRC04:40
*** kebray has joined #openstack-meeting-304:42
*** msambol has quit IRC04:43
*** kebray has quit IRC04:43
*** kebray has joined #openstack-meeting-304:44
*** yamamoto has quit IRC04:50
*** shaohe_feng has joined #openstack-meeting-304:59
*** Sukhdev has quit IRC05:09
*** galstrom is now known as galstrom_zzz05:13
*** btully has joined #openstack-meeting-305:26
*** yamamoto has joined #openstack-meeting-305:28
*** mchestr has joined #openstack-meeting-305:28
*** galstrom_zzz is now known as galstrom05:33
*** mdbooth has quit IRC05:33
*** mdbooth has joined #openstack-meeting-305:39
*** shaohe_feng has quit IRC05:40
*** wojdev has joined #openstack-meeting-305:44
*** galstrom is now known as galstrom_zzz05:46
*** mrmartin has joined #openstack-meeting-305:48
*** klkumar has quit IRC05:51
*** wojdev has quit IRC05:52
*** mrmartin has quit IRC05:52
*** klkumar has joined #openstack-meeting-305:55
*** irenab has joined #openstack-meeting-306:08
*** numans has joined #openstack-meeting-306:18
*** yamamoto has quit IRC06:20
*** jhesketh has quit IRC06:31
*** jhesketh has joined #openstack-meeting-306:34
*** msambol has joined #openstack-meeting-306:40
*** Sukhdev has joined #openstack-meeting-306:40
*** msambol has quit IRC06:46
*** f13o has joined #openstack-meeting-307:09
*** shaohe_feng has joined #openstack-meeting-307:09
*** shwetaap has quit IRC07:11
*** yamamoto has joined #openstack-meeting-307:17
*** openstack has joined #openstack-meeting-307:18
*** ChanServ sets mode: +o openstack07:18
*** shaohe_feng has quit IRC07:20
*** shaohe_feng has joined #openstack-meeting-307:23
*** shaohe_feng has quit IRC07:23
*** Sukhdev has quit IRC07:24
*** shaohe_feng1 has quit IRC07:25
*** yamamoto has quit IRC07:34
*** yamamoto has joined #openstack-meeting-307:36
*** shwetaap has joined #openstack-meeting-307:38
*** sdake has joined #openstack-meeting-307:38
*** nkrinner has joined #openstack-meeting-307:45
*** mrmartin has joined #openstack-meeting-307:48
*** mchestr has quit IRC07:50
*** kebray has quit IRC08:13
*** jed56 has joined #openstack-meeting-308:15
*** irenab_ has joined #openstack-meeting-308:21
*** sankarshan is now known as sankarshan_away08:22
*** irenab has quit IRC08:24
*** irenab_ is now known as irenab08:24
*** sankarshan_away is now known as sankarshan08:24
*** btully has quit IRC08:25
*** matrohon has joined #openstack-meeting-308:32
*** dedery has joined #openstack-meeting-308:40
*** jlanoux has joined #openstack-meeting-308:43
*** msambol has joined #openstack-meeting-308:43
*** dedery has quit IRC08:46
*** msambol has quit IRC08:48
*** btully has joined #openstack-meeting-308:52
*** Poornima has joined #openstack-meeting-308:54
*** safchain has joined #openstack-meeting-308:55
*** btully has quit IRC08:56
*** beekhof has joined #openstack-meeting-308:57
*** beekhof has quit IRC09:00
*** yamamoto has quit IRC09:00
*** f13o has quit IRC09:08
*** f13o has joined #openstack-meeting-309:09
*** f13o has quit IRC09:10
*** f13o has joined #openstack-meeting-309:10
*** tmazur has joined #openstack-meeting-309:15
*** f13o has quit IRC09:16
*** salv-orlando has joined #openstack-meeting-309:17
*** dedery has joined #openstack-meeting-309:19
*** klkumar has quit IRC09:22
*** f13o has joined #openstack-meeting-309:28
*** e0ne has joined #openstack-meeting-309:28
*** vgridnev has joined #openstack-meeting-309:29
*** irenab_ has joined #openstack-meeting-309:34
*** neiljerram has joined #openstack-meeting-309:35
*** irenab has quit IRC09:36
*** irenab_ is now known as irenab09:36
*** vinay_yadhav has joined #openstack-meeting-309:41
*** klkumar has joined #openstack-meeting-309:41
*** masterbound has joined #openstack-meeting-309:42
*** egallen has joined #openstack-meeting-309:52
*** zhenguo has quit IRC09:56
*** ekarlso- has joined #openstack-meeting-309:59
*** ekarlso has quit IRC10:00
*** gcb has quit IRC10:00
*** ekarlso- is now known as ekarlso10:00
*** JeanBriceCombebi has joined #openstack-meeting-310:00
*** yamamoto has joined #openstack-meeting-310:01
*** yamamoto has quit IRC10:06
*** JeanBriceCombebi has quit IRC10:12
*** JeanBriceCombebi has joined #openstack-meeting-310:12
*** yamamoto has joined #openstack-meeting-310:13
*** JeanBriceCombebi has quit IRC10:18
*** JeanBriceCombebi has joined #openstack-meeting-310:18
*** salv-orlando has quit IRC10:21
*** salv-orlando has joined #openstack-meeting-310:22
*** neiljerram has quit IRC10:24
*** tmazur has quit IRC10:26
*** tmazur has joined #openstack-meeting-310:29
*** klkumar has quit IRC10:33
*** tellesnobrega_af is now known as tellesnobrega10:33
*** klkumar has joined #openstack-meeting-310:40
*** shwetaap has quit IRC10:43
*** ozamiatin has joined #openstack-meeting-310:45
*** sambetts-afk is now known as sambetts10:45
*** egallen has quit IRC10:45
*** flaper87 has quit IRC10:46
*** flaper87 has joined #openstack-meeting-310:46
*** stanzgy has quit IRC10:50
*** neiljerram has joined #openstack-meeting-310:55
*** yamamoto has quit IRC11:07
*** yamamoto has joined #openstack-meeting-311:15
*** ozamiatin has left #openstack-meeting-311:24
*** klkumar has quit IRC11:43
*** ^Gal^ has joined #openstack-meeting-311:43
*** klkumar has joined #openstack-meeting-311:44
*** msambol has joined #openstack-meeting-311:46
*** kzaitsev_mb has joined #openstack-meeting-311:50
*** msambol has quit IRC11:51
*** masterbound is now known as mbound_11:53
*** gcb has joined #openstack-meeting-311:57
*** baoli has quit IRC11:58
*** salv-orlando has quit IRC12:00
*** vinay_yadhav has quit IRC12:00
*** vinay_yadhav has joined #openstack-meeting-312:05
*** jaypipes has joined #openstack-meeting-312:08
*** akamyshnikova has joined #openstack-meeting-312:12
*** salv-orlando has joined #openstack-meeting-312:14
*** acabot has quit IRC12:25
*** mbound_ has quit IRC12:28
*** mbound_ has joined #openstack-meeting-312:31
*** eliqiao_ has joined #openstack-meeting-312:31
*** egallen has joined #openstack-meeting-312:32
*** eliqiao has quit IRC12:34
*** sankarshan is now known as sankarshan_away12:35
*** mbound_ has quit IRC12:35
*** mrmartin has quit IRC12:36
*** sankarshan_away is now known as sankarshan12:36
*** egallen has quit IRC12:40
*** egallen has joined #openstack-meeting-312:40
*** acabot has joined #openstack-meeting-312:57
*** armax has joined #openstack-meeting-313:06
*** baoli has joined #openstack-meeting-313:09
*** armax has quit IRC13:10
*** klkumar has quit IRC13:24
*** doug-fish has joined #openstack-meeting-313:25
*** klkumar has joined #openstack-meeting-313:25
*** jaypipes has quit IRC13:29
*** tmazur has quit IRC13:29
*** f13o has quit IRC13:31
*** jaypipes has joined #openstack-meeting-313:32
*** klkumar has quit IRC13:33
*** klkumar has joined #openstack-meeting-313:36
*** JeanBriceCombebi has quit IRC13:37
*** mbound_ has joined #openstack-meeting-313:43
*** JeanBriceCombebi has joined #openstack-meeting-313:43
*** klkumar has quit IRC13:43
*** shwetaap has joined #openstack-meeting-313:43
*** shwetaap has quit IRC13:48
*** vinay_yadhav has quit IRC13:51
*** Poornima has quit IRC13:52
*** shwetaap has joined #openstack-meeting-313:54
*** jckasper has quit IRC13:55
*** klkumar has joined #openstack-meeting-313:56
*** baoli has quit IRC13:56
*** JeanBriceCombebi has quit IRC13:56
*** mrmartin has joined #openstack-meeting-313:57
*** julim has joined #openstack-meeting-313:59
sheeprinegpocentek: huats: time for CK meeting14:02
sheeprinehere?14:02
*** mrmartin has quit IRC14:02
sheeprineOther people here for CloudKitty meeting?14:02
huatsHi sheeprine !14:03
sheeprineHi14:03
gpocentekhello14:04
*** JeanBriceCombebi has joined #openstack-meeting-314:04
sheeprineOk let's go14:04
sheeprine#startmeeting cloudkitty14:05
openstackMeeting started Mon Nov 23 14:05:20 2015 UTC and is due to finish in 60 minutes.  The chair is sheeprine. Information about MeetBot at http://wiki.debian.org/MeetBot.14:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:05
*** openstack changes topic to " (Meeting topic: cloudkitty)"14:05
openstackThe meeting name has been set to 'cloudkitty'14:05
sheeprineI wanted to talk first about the new contributors.14:06
sheeprineThat's awesome, we've got multiple people contributing to CloudKitty and submiting bug reports. I hope the numbers will keep growing.14:06
sheeprineI think 0.5 will help us gather new people around the project.14:07
sheeprine#topic gnocchi support14:07
*** openstack changes topic to "gnocchi support (Meeting topic: cloudkitty)"14:07
sheeprineOk first topic, gnocchi.14:07
sheeprineWe've talked about this during sessions at the summit in Tokyo.14:08
sheeprineAnd people are waiting for us to integrate support for gnocchi.14:08
sheeprineWe've started working on this with gpocentek. And we plan on providing a first iteration ASAP.14:08
*** amotoki_ has joined #openstack-meeting-314:09
*** yamamoto has quit IRC14:09
sheeprineAnd then make the integration evolve with new version (new collector format, full gnocchi storage support)14:10
*** yamamoto has joined #openstack-meeting-314:10
sheeprineSome parts need work in CloudKitty others from Gnocchi. That's why we started implementing support new and we'll incrementally add features as they are available14:11
sheeprineOur plan is to bundle gnocchi support with 0.514:11
sheeprinewhich should hit git in a few weeks max.14:11
sheeprineWe implemented an hybrid storage for gnocchi to leverage capabilities of gnocchi and remove information from the current storage driver.14:11
sheeprineIt should greatly improve performances and reduce the amount of duplicated data.14:11
sheeprineAnyone got suggestions so far?14:12
*** amotoki has quit IRC14:12
gpocenteksounds good to me so far14:12
*** amotoki_ is now known as amotoki14:12
sheeprinegreat14:12
sheeprineShould we move to next topic or anyone got something to add?14:13
sheeprineI guess we can move to next topic.14:14
*** baohua has joined #openstack-meeting-314:14
sheeprine#topic pending reviews14:14
*** openstack changes topic to "pending reviews (Meeting topic: cloudkitty)"14:14
sheeprineOk, to make it simple... We've need to validate some code pending review14:14
sheeprineThere are some patches that in my opinion should hit git and be integrated in the master.14:15
gpocentekit's on my todo to review/validate a few patches14:16
*** yamamoto has quit IRC14:16
gpocentektoday or more likely tomorrow14:16
*** tellesnobrega is now known as tellesnobrega_af14:17
sheeprineMost are bug fixes about v3 breaking cloudkitty or data duplication in the storage driver14:17
sheeprineWithout them I doubt people will keep using CK.14:17
sheeprinewhich brings us to next point14:17
sheeprine#topic road to version 0.514:17
*** openstack changes topic to "road to version 0.5 (Meeting topic: cloudkitty)"14:17
*** tellesnobrega_af is now known as tellesnobrega14:17
sheeprineWe need to define what should be integrated in next release.14:18
sheeprineDuring Tokyo summit we decided to move to multiple release during a cycle, and that's a good thing because we can easily deprecate code and move forward.14:18
sheeprineI think the last points waiting for 0.5 to go live is the integration of the bugfixes and some features.14:19
*** baohua has quit IRC14:20
sheeprineGnocchi support is a plus, and since 0.5 is supposed to be compatible with Liberty we can have users in real prod environments.14:20
sheeprineAnd then we should transition to Mitaka, to implement new features and integrate changes from libs.14:20
*** baohua has joined #openstack-meeting-314:21
sheeprineOne last thing, we need to validate the Horizon integration. I'm not 100% sure that it's working flawlessly due to js compression.14:21
*** pavel_bondar has joined #openstack-meeting-314:21
sheeprineWe've changed the way we setup cloudkitty in Horizon enabled files. And it looks like only applications can use compressed js.14:22
sheeprineWe need to be sure that 0.5 bundles a working version of Horizon integration.14:22
sheeprinegpocentek: huats: Other thoughts?14:22
gpocenteknot here14:23
*** salv-orlando has quit IRC14:23
*** baoli has joined #openstack-meeting-314:23
sheeprine#topic next version goals14:24
*** openstack changes topic to "next version goals (Meeting topic: cloudkitty)"14:24
sheeprineOk last topic, we need to define what new version will feature.14:25
sheeprineWe've got a list of pending features, some needs CloudKitty code rewrite or refactor. And potentially to deprecate old code.14:25
*** bklei has joined #openstack-meeting-314:25
sheeprineI'm working on a blueprint to implement rating rule validity times and all middleware code needed so it is rating module agnostic.14:26
sheeprineWe can implement this feature without the need of major refactor, or backward compatibility breaking changes.14:27
sheeprineSo we can integrate it in whatever release as soon as it's ready14:28
sheeprineNext we've got the collector model.14:28
sheeprineHere we are breaking old CloudKitty format, we'll need to implement a compatibility layer to expose data as it was in previous versions.14:29
sheeprineThe new format will decompose metric from metadata "a la gnocchi", it will reduce duplicated data from the pipeline and speeds calculations up.14:29
sheeprineWe can imagine implementing new collector format and have a flag in configuration to "flatten" the metadata in a dict like before.14:30
sheeprineNew storage will benefits from the new format and store the metadata only once.14:30
sheeprineHere we don't really have choice, it will be a new version. So you can still use the old one or transition to the new one when you are ready.14:31
*** jckasper has joined #openstack-meeting-314:31
sheeprineWith these changes we'll have a really robust and scalable solution. It will even improve modularity.14:31
sheeprineI've got a patch that I'll send in review as WIP in a few days to handle dynamic resource typing from the API or collector.14:32
*** dedery_ has joined #openstack-meeting-314:32
*** jasondotstar_afk is now known as jasondotstar14:33
sheeprineGnocchi needs the same kind of stuff so we might chop some code from it and move it in a lib. I'm looking towards oslo.db, it will make sense.14:33
*** banix has joined #openstack-meeting-314:33
sheeprineSo I guess we should have 2 more release, one related to collectors and one to storage.14:34
sheeprineWith this implemented we should be close to a version 1.0 :)14:34
*** dedery has quit IRC14:34
*** superdan is now known as dansmith14:35
sheeprineSome features I am missing?14:36
sheeprinegpocentek: huats: ^14:36
gpocentekstill nothing here, sounds good, and enough work ,à14:37
gpocentek;)14:37
sheeprineHuge patches incoming indeed.14:37
sheeprine#topic possible next topics14:38
*** openstack changes topic to "possible next topics (Meeting topic: cloudkitty)"14:38
sheeprineDo we have other topic ideas?14:39
sheeprinegpocentek: huats: ^14:39
sheeprineI'll do a mail summary on the mailing. Some people might be interested.14:39
gpocentekI don't think so14:39
sheeprineI'll wait a few minutes just in case and if nobody speaks then I'll stop this meeting.14:40
sheeprineOk, thanks guys.14:43
sheeprine#endmeeting14:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:43
openstackMeeting ended Mon Nov 23 14:43:58 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cloudkitty/2015/cloudkitty.2015-11-23-14.05.html14:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cloudkitty/2015/cloudkitty.2015-11-23-14.05.txt14:44
openstackLog:            http://eavesdrop.openstack.org/meetings/cloudkitty/2015/cloudkitty.2015-11-23-14.05.log.html14:44
*** dshakhray has joined #openstack-meeting-314:44
*** baohua has quit IRC14:47
*** dtardivel has joined #openstack-meeting-314:48
*** msambol has joined #openstack-meeting-314:49
*** vinay_yadhav has joined #openstack-meeting-314:51
*** ihrachys has joined #openstack-meeting-314:53
*** msambol has quit IRC14:53
*** nelsnelson has joined #openstack-meeting-314:54
*** mrmartin has joined #openstack-meeting-314:54
*** rossella_s has joined #openstack-meeting-314:56
*** korzen has joined #openstack-meeting-314:57
*** subscope has joined #openstack-meeting-314:58
*** julim_ has joined #openstack-meeting-315:00
*** mhickey has joined #openstack-meeting-315:01
ihrachysakamyshnikova: mhickey: rossella_s: korzen: mestery: sc68cal: ajo: amotoki: friendly ping before upgrades meeting starts here15:02
*** dedery_ has quit IRC15:02
mesteryo/15:02
*** julim has quit IRC15:02
rossella_sihrachys, hello15:02
*** Eva-i has joined #openstack-meeting-315:02
korzenhello15:02
mhickeyHello15:02
amotokihi. am just looking of the channel15:02
akamyshnikovahi!15:03
ihrachysI *hope* that I pinged everyone but I could miss someone. if so, mea culpa in advance. :-|15:03
ihrachysok, let's try it out15:03
ihrachys#startmeeting neutron_upgrades15:03
openstackMeeting started Mon Nov 23 15:03:54 2015 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:03
openstackThe meeting name has been set to 'neutron_upgrades'15:03
ajoo/15:04
ihrachyswelcome all to the 1st meeting of the subteam :)15:04
ihrachys#link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam15:04
ihrachysthat's the agenda we'll follow during our meetings. feel free to update. :)15:04
ihrachyssome history for those not informed: the subteam is formed for Mitaka the least and will look into upgrade story for Neutron.15:05
ihrachysit covers cold upgrades as well as rolling ones, looking at stability, speed and whatnot all related to upgrades15:06
ihrachysI want to clarify on the channel mess first15:06
ihrachysinitially we planned to handle the meeting in #openstack-meeting-2 but it was pointed out on Fri that the channel is not an official one, so no logging, no bots etc.15:07
*** Sam-I-Am has joined #openstack-meeting-315:07
sc68calo/15:07
Sam-I-Amhowdy15:07
ihrachyshence we switched to #openstack-meeting-3 this time since it's free today, and we'll work on getting official channel booking this week15:07
ihrachysthere is a patch to book -3 bi-weekly for now15:07
ihrachys#link https://review.openstack.org/24746415:07
rossella_sthanks ihrachys15:08
ihrachysbut we'll probably look into getting a slot weekly, unless you think it's not worth it15:08
mesteryyes, thanks for taking care of this ihrachys15:08
ihrachyscomments on frequency?15:08
mhickeyihrachys: I am easy15:08
ihrachysok, let's assume everyone agrees with the goal to have it weekly and move on. if not, speak up later.15:09
*** pavel_bondar has quit IRC15:09
rossella_sok15:09
ihrachys#topic Announcements15:09
*** openstack changes topic to "Announcements (Meeting topic: neutron_upgrades)"15:09
*** btully has joined #openstack-meeting-315:09
ajolet's try weekly, and step back if it's too much15:09
*** JeanBriceCombebi has quit IRC15:10
*** pavel_bondar has joined #openstack-meeting-315:10
ihrachysas you probably know, openstack is now a big tent, and we use tags to claim common features for projects15:10
*** klkumar has quit IRC15:10
ihrachyslately two project tags were merged in governance repo: assert:supports-upgrade https://review.openstack.org/239771 and assert:supports-rolling-upgrade: https://review.openstack.org/23977815:10
*** klkumar has joined #openstack-meeting-315:10
ihrachysI believe first thing we'll track as a team is those tags for neutron. it seems we are there or almost there to claim those15:11
ihrachysthere is actually a patch up for review to add supports-upgrade for neutron15:11
ihrachys#link https://review.openstack.org/24624215:11
*** JeanBriceCombebi has joined #openstack-meeting-315:11
ihrachyswe already had it covered with grenade jobs before, so there are no action items beyond that patch15:12
* ihrachys .oO (I wish all victories are that easy)15:12
sc68calwoo15:12
ihrachysfor supports-rolling-upgrade, we have some stuff to do, but not much either, thanks to grenade folks15:12
ihrachyssc68cal put a patch for infra to add partial job for neutron experimental queue15:13
ihrachys#link https://review.openstack.org/24586215:13
ihrachysand it's merged. sc68cal, wanna update on what's the status for the job?15:13
sc68calI made a bit of a mistake, the job needs a different node type to run15:14
sc68calhttps://review.openstack.org/#/c/248737/15:14
sc68calso, it should be able to be run in the next hour15:14
ihrachyssc68cal: aha. cool, and it's already in gate :)15:14
ajoniice15:15
ihrachyssc68cal: what's the plan for the job after we make sure it works in experimental?15:15
njohnstono/15:15
sc68calihrachys: run it, see what explodes, fix15:15
ihrachyssc68cal: ok. once we are there, do we go thru non-voting state or go straight to enable it in gate?15:16
sc68calnon-voting probably15:16
sc68calif it consistently passes, then make it voting15:16
amotokisc68cal: is there a good pointer to understand how multinode jobs is run?15:16
ihrachysyeah, it may be worth to collect some stats.15:17
*** galstrom_zzz is now known as galstrom15:17
*** zz_dimtruck is now known as dimtruck15:17
sc68calamotoki: not..... really :(15:17
ajosc68cal , how healthy is the normal multinode now?15:17
ihrachysamotoki: I believe there was an email on the matter from sdague, I will try to find it now.15:17
amotokisc68cal: no problem. it seems better to collect our knowledge somewhere.15:17
ajoI saw it had issues last week, but seems to be running fine now?15:17
korzenI assume that multinode job should ne able to run VMs on not upgraded node, is it correct? tempest smoke tests covers that?15:17
sc68calamotoki: I badgered clarkb to write some docs - this was what we got https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/multinode_setup_info.txt15:17
ihrachysamotoki: http://lists.openstack.org/pipermail/openstack-dev/2015-November/079397.html15:18
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2015-November/079397.html details on grenade partial multinode jobs15:18
sc68calajo: non-dvr multinode I think is pretty healthy15:18
sc68calajo: DVR multinode has been good, then not so good, for a while15:18
sc68calI think the new DVR subteam has been working on fixing15:18
ajoack, I see a few patches passing DVR too15:18
ajomultinode-dvr I mean15:19
ihrachyskorzen: I presume for partial we run whole suite with old compute node15:19
ihrachysok, so we have plan for partial, and we have sc68cal on it, so there is no place for failure :)15:20
rossella_s:)15:20
ihrachyssc68cal: thanks for hopping onto the job quickly15:20
*** rbak has joined #openstack-meeting-315:20
*** dedery has joined #openstack-meeting-315:20
ihrachys#topic Patches15:21
*** openstack changes topic to "Patches (Meeting topic: neutron_upgrades)"15:21
korzenI have spotted that grenade upgrade code is not using the expand/contract schema migration15:21
ihrachysI guess I should have switched the topic before, but meh15:21
*** mdbooth has quit IRC15:21
korzenshould we work on adding the online schema migration to grenade upgrade scripts?15:21
ihrachyskorzen: yeah, that's something we should look into. but that would be a separate job that would run all tests/code from stable EXCEPT applying expand migrations from master before that15:22
ihrachyskorzen: since the whole idea is that you can execute those on previous releases and continue running with no issues.15:22
ihrachysmaybe it would also require actual upgrade and another tempest run to validate that we didn't break anything while running the old code15:23
*** ajmiller has joined #openstack-meeting-315:23
ihrachysok, moving to next patches up for review15:24
*** JeanBriceCombebi has quit IRC15:24
ihrachyswe have two upgrade related patches for devref15:24
*** salv-orlando has joined #openstack-meeting-315:24
ihrachys#link https://review.openstack.org/241687 devref page for upgrades15:24
ihrachys^ is a page with general info on scenarios, struggles, plans, whatnot. I believe it's mostly for cultural changes outside those explicitly interested in upgrades, though if you find smth interesting for you too, cool.15:25
ihrachyswe also have another devref change that puts plan for RPC callbacks mechanism upgrade from ajo15:25
ihrachys#link https://review.openstack.org/241154 devref update for rpc callbacks upgrades15:26
ajo:-)15:26
*** JeanBriceCombebi has joined #openstack-meeting-315:26
ihrachysif someone is not aware, rpc callbacks is a mechanism used for QoS feature to propagate updates to QoS resources into agents15:26
ihrachysand it changes usage pattern somewhat: instead of asking agents to pull data from neutron-server, it makes neutron-server broadcast updates for agents15:27
ihrachysthat's similar to how we do notifications, but with actual data payload attached15:27
ajoAlso plans to use them to sync agents more reliably by kevinbenton15:27
ajo#link : https://review.openstack.org/#/c/225995/ agent push notification refactor15:27
ihrachysthere are plans to reuse the mechanism for other features, like port_details updates ^15:27
ihrachysso the mechanism and rolling upgrades for it become more important than before :)15:28
*** dedery has quit IRC15:28
ihrachysnote that since we need versioned objects to make usage of the mechanism, we would need to provide those to kevinbenton asap. rossella_s was kind to take the PoC for port objects.15:29
ihrachysrossella_s: I guess you had no time for that till now, correct?15:30
rossella_sihrachys, yes15:30
ajoThe new testing jobs will also help validate all this work15:30
ihrachysajo: yes, I believe partial is explicitly mentioned in the spec as a blocker15:30
rossella_sihrachys, I hope to give an update regarding this in the following days...my plan is to start this week15:30
ajorossella_s , ihrachys , keep me looped in into that work15:31
rossella_sajo sure15:31
korzenrossella_s please include me also15:31
ihrachysrossella_s: thanks a lot! reach me whenever you have questions on objects. I put that all in the tree initially, so hopefully I may be of some help15:31
rossella_skorzen, will do15:32
rossella_sihrachys, thanks a lot, I will15:32
*** msambol has joined #openstack-meeting-315:32
*** mdbooth has joined #openstack-meeting-315:32
ihrachysrossella_s: btw to make it clear, the idea for start is merely providing objects to allow kevinbenton to switch notification code to use them. Other code that currently touches tables may still use the old way. This is to unblock further work.15:32
rossella_sihrachys, got it15:33
ihrachysok cool on that one :)15:33
ajoYes, the complication is on extension of ports and networks by mixins :)15:33
korzenis there rfe or bp for OVO implementation?15:33
ihrachys#action rossella_s will start on PoC for port objects15:33
ajokorzen , not sure if an RFE is needed, is not an external feature, but more of internal design, may be as part of any dependent work?15:34
ihrachysdo we think it needs a separate rfe?15:34
ajoihrachys, i don't know, may be it's worth checking with armax, mestery, any idea ^ ?15:34
sc68calajo: +115:34
ihrachysajo: it may worth checking with drivers team on that one. maybe they will indeed want it.15:34
ajoihrachys : +115:35
ihrachysyeah, let's better check instead of hoping for the best and being blocked later15:35
mesteryajo ihrachys: I don't think an RFE is needed, we have to do this work, so my opinion is lets file a bug (or write a quick spec) and move forward.15:35
mesteryAlthough15:35
mesteryI guess the bug could be an RFE bug :)15:35
ihrachysmestery: we don't have specs without bps, and bps without rfes, so...15:35
mesterylol15:35
ihrachys(unless I miss smth)15:35
ihrachysthat process thing is hard!15:35
mestery:)15:36
ajolol15:36
korzenhttps://review.openstack.org/#/c/168955/6/specs/liberty/versioned-objects.rst15:36
ajoa devref? :)15:36
korzenold spec from Liberty15:36
ihrachyskorzen: cool, thanks for the pointer!15:36
*** neelashah has joined #openstack-meeting-315:37
ajokorzen++15:37
ihrachysok, let's check with drivers tomorrow (I believe we have drivers meeting on Tue)15:37
mesteryihrachys: Yup, 1500 UTC I believe15:37
amotokidevref sounds a good idea for this kind of things. we can discuss design and code in parallel.15:37
ihrachys#action ihrachys will follow up with drivers team on the need for RFE/BP/spec/bribe to proceed with OVO adoption15:37
amotokibut it seems good to ask armando.15:38
ihrachysamotoki: yeah, he is usually concerned about over commit15:38
ihrachysok, we don't have anything more on agenda, so switching the topic15:38
ihrachys#topic Open Agenda15:39
*** openstack changes topic to "Open Agenda (Meeting topic: neutron_upgrades)"15:39
ihrachysone thing I wanted to clarify is whether we need a LP tag for the team15:39
ajoopen is good, we love open15:39
ajo:)15:39
amotokione question on the upgrade strategy is whether we can assume neutron server is upgraded first.15:39
*** galstrom is now known as galstrom_zzz15:39
sc68calamotoki: I think that's a given15:39
amotokiit is reasonable to me but I think no other projects are doing so now. is it better to hear opinions from oeprators or others?15:39
sc68calamotoki: I believe that's the way Nova does upgrades15:39
ajoI guess that's good as long as is well documented15:39
ihrachysamotoki: if we don't specify it, we complicate our lifes for no reason15:39
ihrachysamotoki: I *think* nova does? isn't conductor the first one to upgrade?15:40
*** mdbooth has quit IRC15:40
amotokiihrachys: I totally agree.15:40
Sam-I-Amthe server (read: db schema) has to be upgraded first15:40
*** rbak_ has joined #openstack-meeting-315:40
ihrachysSam-I-Am: in nova, it's conductor that touches db, right?15:40
*** mdbooth has joined #openstack-meeting-315:40
sc68calihrachys: yep15:40
Sam-I-Amihrachys: yeah15:41
amotokiihrachys: I might be wrong. I will check again.15:41
Sam-I-Amthe general upgrade process is upgrade source, update db, restart services15:41
Sam-I-Amif any config options require changing, do that prior to the service restart15:41
Sam-I-Amor if they pertain to db stuff, before db update15:41
ihrachyshttp://superuser.openstack.org/articles/upgrading-nova-to-kilo-with-minimal-downtime , step 315:41
*** galstrom_zzz is now known as galstrom15:42
ihrachysnote that the order is to be documented for neutron with https://review.openstack.org/24168715:42
Sam-I-Amanother thing that should be tested during upgrade is connectivity to vms15:43
Sam-I-Amit should not break15:43
*** salv-orlando has quit IRC15:43
ihrachysSam-I-Am: yeah. I believe it's not supposed to break, but it's indeed not tested.15:43
ajoSam-I-Am , Isn't that checked by tempest in grenade job?15:43
*** JeanBriceCombebi has quit IRC15:43
ihrachysit was fixed in L by akamyshnikova15:44
*** rbak has quit IRC15:44
ihrachysajo: I don't think so. during upgrade no actual tests are executed that could catch connectivity drop15:44
Sam-I-Amalso vm connectivity outbound if possible15:44
ajoha15:44
Sam-I-Ambut inbound usually implies outbound works15:44
ajowe should at least run the smoke tests15:44
ihrachysajo: we do run them, but not while we restart services.15:45
ajoor the network related15:45
ihrachysajo: it's like 'run smoke, upgrade, run tests'15:45
ihrachysin sequence15:45
ajoah, you mean while upgrade?15:45
korzenthe idea of vm connectivity is to have constant ping to VM during upgrade, it is not covered by smoke test, right?15:45
ajook, not sure how that would be possible.15:45
ajoThat's assumed by the idea that agents going down don't remove the dataplane settings15:45
ajoor bring down any real service15:46
Sam-I-Amsome sort of basic check to make sure an upgrade doesnt break connectivity, and if it does, accurately determine the downtime15:46
ajoso the only issues to arise, are when new agents boot up15:46
ihrachysajo: they don't, since L (at least OVS)15:46
ajoah, for OVS we had some before, but it was momentary ( a few seconds) and not related to upgrade itself15:47
ajojust because of ovs agent restart15:47
ajo(any restart)15:47
ihrachysajo: it may be some background service in devstack that runs while uppgrade is ongoing that provides data on connectivity into some file that we can parse later.15:47
Sam-I-Amquestion is, would any sort of upgrades cause agents to 'rework' the dataplane structure? for example, an architectural change to dvr.15:47
*** dedery has joined #openstack-meeting-315:47
*** dedery has quit IRC15:47
ihrachysajo: yeah, but it's kinda related to upgrades because you can't hot swap python code ;)15:47
ajoSam-I-Am : eventually..15:47
*** dedery has joined #openstack-meeting-315:48
ajoSo, may be a background pinger15:48
ajothat provides a report by the end of the upgrade15:48
ajook, you convinced me15:48
Sam-I-Amyeah. it just needs to glean the instance info15:48
ihrachysSam-I-Am: I agree it's worth validating. I believe we had a patch merged in master lately that changed names for LB devices for no big reason, and we haven't caught it15:48
ajoSam-I-Am , ihrachys , when debugging stuff like that, I found specially useful to run a pinger in the openstack log format15:49
Sam-I-Amit would need to test all common cases... floating ip, private ip, public ip, router ip, etc.15:49
ihrachysI believe the more visible the subteam work is in gerrit, the more aware community will be about where to look at15:49
ajothat way you could sync with the agent reboot logs, etc, to see when disruptions happen15:49
Sam-I-Amprobably dhcp too15:49
*** Sukhdev_ has joined #openstack-meeting-315:49
*** lazy_prince has joined #openstack-meeting-315:49
ihrachysajo: ack. as long as we have data points with time stamps, it's not an issue to sync logs with those15:50
ajocorrect15:50
Sam-I-Amwill these upgrades test both ovs and lb?15:50
ihrachysSam-I-Am: dhcp disruption may be fine for a tiny bit of time since we can have multiple agents to serve a network15:50
ihrachysSam-I-Am: I don't think we will look into LB before OVS.15:50
Sam-I-Amihrachys: yeah, dhcp isnt as big of an issue since access is intermittent15:50
ihrachysSam-I-Am: I even suspect LB may still have connectivity disruption since akamyshnikova's patch was OVS specific15:51
Sam-I-Amihrachys: but we should at least check for breaking it because instances do crazy things when they cant get a lease15:51
ihrachysack15:51
ajoihrachys : I think disruption was ovs specific too15:51
ihrachysajo: ok then I get why operators lean towards LB ;)15:51
Sam-I-Amiirc, ovs was the only thing that had disruption during a restart of ovs-agent (not specific to upgrades)15:52
Sam-I-Ambecause it re-created all of the magic15:52
ihrachysbtw one more patch that I want to point out related to upgrades is https://review.openstack.org/24819015:52
akamyshnikovaihrachys, yes I agree with ajo, I'm not sure that LB has problems15:52
Sam-I-Amlinuxbridge has been resilient for a while now15:52
*** numans has quit IRC15:52
*** calbers has joined #openstack-meeting-315:52
*** Piet has joined #openstack-meeting-315:52
ihrachysthe patch ^ adds a command to neutron-db-manage to detect whether there are pending contract migrations that would require offline neutron-server instances before execution15:52
Sam-I-Amyou can kill off all the agents and the bridges stick around (sometimes too many of them stick around)15:52
ihrachysI know puppet folks already have some code to determine whether full shutdown is needed, but they rely on ugly hacks like filenames15:53
*** peristeri has joined #openstack-meeting-315:53
ihrachysthe idea of the patch is to make it a supported command they can rely on15:53
ihrachysnote it's WIP and I need to play with alembic a bit before it's ready. so just a heads-up.15:53
ihrachysSam-I-Am: good to hear :)15:54
ihrachysok anything else to point out upgrades related?15:54
Sam-I-Ami'm good for now15:55
korzencan we slit the OVO implementation?15:55
ihrachysSam-I-Am: thanks for joining btw, I somehow missed you :)15:55
Sam-I-Amihrachys: np. somanymeetings :)15:55
ihrachyskorzen: you mean per object type?15:55
korzenyes15:55
ihrachyskorzen: I don't see any reasons not to if we have interested parties!15:55
Sam-I-Amihrachys: i have a spec to improve the general openstack upgrade procedures15:55
ihrachyskorzen: I presume networks/subnets could be a separate piece to bite15:56
ihrachysrossella_s: comments ^ ?15:56
korzenyes, my idea is to touch the network/subnets15:56
ihrachysSam-I-Am: nice. link?15:56
Sam-I-Ameach release will include a list of potential issues including downtime, so having an automated upgrade test process is important15:56
rossella_sihrachys, I agree with you15:56
Sam-I-Amihrachys: http://specs.openstack.org/openstack/docs-specs/specs/mitaka/upgrades.html15:57
ihrachyskorzen: so just go ahead ^ :)15:57
korzenok, thx15:57
ihrachys#link http://specs.openstack.org/openstack/docs-specs/specs/mitaka/upgrades.html15:57
ihrachysSam-I-Am: thanks, added to reading list :)15:57
ajokorzen , what do you mean by slit?15:57
*** kebray has joined #openstack-meeting-315:58
korzensplit*15:58
korzen;)15:58
ajoupps, sorry I was reading an old log somehow15:58
ajo:)15:58
Sam-I-Amthx. i added your devref patch to my reading list15:58
ihrachysok, I believe we are near the end of the meeting. if anything, we may proceed in #openstack-neutron channel. thanks for joining and looking forward to your patches and reviews. :)15:58
ajoihrachys: thanks for driving this15:59
*** kebray has quit IRC15:59
rossella_sihrachys, thanks a lot!15:59
mhickeyihrachys, thanks15:59
ihrachysand keep attention to meeting time updates in openstack-dev@, we may need to switch if we don't get -2 channel as the official one.15:59
ihrachysadieu! o/15:59
amotokithanks!15:59
Sam-I-Amseeya, great meeting15:59
ihrachys#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
ajoadios amigos! o/15:59
*** kebray has joined #openstack-meeting-315:59
openstackMeeting ended Mon Nov 23 15:59:54 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-11-23-15.03.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-11-23-15.03.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-11-23-15.03.log.html15:59
*** Sam-I-Am has left #openstack-meeting-316:00
jklare#startmeeting openstack_chef16:00
openstackMeeting started Mon Nov 23 16:00:10 2015 UTC and is due to finish in 60 minutes.  The chair is jklare. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: openstack_chef)"16:00
*** mhickey has left #openstack-meeting-316:00
openstackThe meeting name has been set to 'openstack_chef'16:00
jklarehello everybody o/16:00
sc`o/16:00
calbershi there16:00
jklareany topics from you guys for today?16:02
sc`i don't have anything for this week16:02
jklareok then lets start with this one16:03
jklare#topic refactoring the cookbooks16:03
*** openstack changes topic to "refactoring the cookbooks (Meeting topic: openstack_chef)"16:03
*** galstrom is now known as galstrom_zzz16:04
*** igordcard has joined #openstack-meeting-316:04
*** kebray_ has joined #openstack-meeting-316:04
jklarecalbers and me have pushed up some refactored versions of compute and network and the network cookbook seems to be already working again in our integration tests16:04
jklareit would be great so have some more eyes on this16:04
jklareto check if these patches go into the right direction16:05
jklareanother thing i realised while going through the network cookbook is our (in my eyes) completely broken way of handling the identity (and maybe most of the other) endpoints right now16:06
jklarei think somewhere along our path we decided to split the endpoints into internal, admin and public like the projects do16:06
jklarewhich is great16:06
*** kebray has quit IRC16:06
jklarethe issue is, that judging from the current state of the code, the refactoring never finished completely16:06
jklarewhich led to something like this https://github.com/openstack/cookbook-openstack-network/blob/56c95b6ce3ad2f9fd2ff2882a05e03781f73b8ca/recipes/default.rb#L148-L15316:07
sc`the endpoint stuff is rather fragile, at least that's what my experience was backporting some code to icehouse16:08
jklarein line 148 the internal_endpoint is defined by calling internal_endpoint on 'identity-internal', which will first search for an attribute like node.openstack.endpoints.internal.identity-internal.... and after not finding it, fall back to node.openstack.endpoints.identity-internal... which exists16:08
*** armax has joined #openstack-meeting-316:09
jklareso the fact that it is working is currently based on a fallback16:09
jklareand some workaround definitions16:09
jklaresince these methods and the definition of endpoints is very important for all cookbooks, we should try to fix this during this refactoring cycle imo16:10
sc`+116:10
jklare:)16:10
jklareso you want to go for it sc` ?16:10
sc`may not have as much time as i'd like16:11
jklareyeah, i know that feeling :D16:11
sc`being as $job is icehouse, there's a good deal of context switching that has to happen16:12
*** korzen has quit IRC16:12
jklarein my opinion this endpoint methods are too complicated and to workaroundy right now16:13
*** salv-orlando has joined #openstack-meeting-316:14
sc`it is rather complicated to work with. suggestions on how to improve it?16:14
jklarei think we can define a more generic endpoint method, that depends on some more sane user input16:15
jklareright now our endpoints and uri methods try to correct things from attributes that might be set wrong16:16
jklarelike removing '/' or replacing 'v3.0' with 'v3'16:16
sc`bad node attribute data is just a consequence of chef. i can see where consolidating methods would be useful16:17
jklareif we agree that the cookbook user knows what he is doing and has read the documentation (which needs to be updated ofc), we could remove a lot of complicated code here and go with a lot more 'convention over configuration'16:17
sc`assuming people read documentation is a lofty assumption :D16:18
jklarei know16:18
jklaresad but true16:18
jklareso, since nobody has touched the common cookbook and its methods yet, i could give it a shot and refactore these methods16:20
sc`but i agree. we shouldn't be managing the configuration of openstack as much as we are16:20
jklare-e16:20
*** JeanBriceCombebi has joined #openstack-meeting-316:20
*** galstrom_zzz is now known as galstrom16:20
sc`if the cookbooks move away from ubuntu/centos packages and use something a la giftwrap, a good deal of things could go down to the packages themselves and be out of the cookbooks16:21
*** dimtruck is now known as zz_dimtruck16:22
*** zz_dimtruck is now known as dimtruck16:22
jklarethats true, but does not change anything regarding the dynamic configurations16:22
*** rossella_s has quit IRC16:22
jklareexcept if we include the whole package and service configuraiton in the postinst scripts ;)16:22
sc`i think it depends on how we want the future to look16:23
jklare?16:23
sc`continuing the use of upstream packages the way we are locks us to certain assumptions at the packaging level16:24
*** rossella_s has joined #openstack-meeting-316:24
sc`less control, etc.16:24
*** Swami has joined #openstack-meeting-316:24
jklarebut that is mainly the installation path and the init scripts right?16:25
*** bpokorny has joined #openstack-meeting-316:26
*** procmisc has joined #openstack-meeting-316:27
sc`one thing that pops out is keystone.wsgi vs wsgi.py. i don't have a comprehensive list of what's different between distros, but it's plausible that there are other variances versus upstream openstack16:28
j^2hey all :D16:29
jklaretrue, but i am not sure if we should try to move away from upstream packaging to correct these minor things and face all the heavy lifting of packaging ourselfs instead16:29
jklarehey j^216:29
sc`ohai j^216:30
calbershi j^216:30
j^2it seems my NAS at home got hacked :(16:30
jklareCIA?16:31
jklareNSA?16:31
j^2the "LOL" hack16:31
*** vinay_yadhav has quit IRC16:35
jklarewould you volunteer to try some automated building of packages that we could use sc` ? because my main objection with this right now is, that we only have so much resources and i have not seen anybody working on this packaging thing for our project so far16:35
jklarei also have tried the giftwrap thing and spend 2 hours patching code to get it to build some packages from master16:36
jklarei have no idea if they work or not16:36
*** BrianB__ has joined #openstack-meeting-316:36
jklareand no automation to test them right now16:36
jklareso from my point of view the " we should package ourselfs" idea is great, but not doable right now16:37
jklareand i would love to be proven wrong here16:37
sc`indeed. perhaps a 'not right now' thing given the number of active contributors. i can see if i can spend some time over the coming US holiday16:38
jklaresounds good16:39
jklare@j^2 i heard you have some desginate things to tell?16:39
jklare#topic designate-cookbook16:39
*** openstack changes topic to "designate-cookbook (Meeting topic: openstack_chef)"16:39
j^2yeah16:40
j^2so i've started a POC for designate16:40
j^2i havent gotten common put in yet, but it's a start16:40
j^2there is no "production" instructions so this is the best i got16:40
j^2#link https://github.com/jjasghar/cookbook-openstack-dnsaas16:41
j^2I'd love some eyes/PRs if yall have some time16:41
sc`j^2: apparently this is the "production" instructions - http://docs.openstack.org/developer/designate/install/ubuntu-kilo.html16:41
j^2when it's "ready" i'll squash/not squash everything down to one and cerate the openstack/ repop16:41
j^2oh levely16:42
j^2lovely16:42
*** sinval has joined #openstack-meeting-316:42
j^2this is the one i used: http://docs.openstack.org/developer/designate/getting-started.html16:42
j^2i'll go through that link jklare and make the changes16:42
j^2luckly designate looks pretty straight forwarbd16:43
j^2i'm planning on tk'ing it also too so16:43
*** sankarshan is now known as sankarshan_away16:43
j^2and then we can add it to the openstack-chef-repo and have it part of the aio16:43
*** stendulker has joined #openstack-meeting-316:44
jklareseems like great progress16:44
*** dedery_ has joined #openstack-meeting-316:44
j^2thanks16:45
j^2i'm trying16:45
j^2:D16:45
*** vishwanathj has joined #openstack-meeting-316:45
j^2it looks like it's only Ubuntu for the time being16:45
jklareadding support for other distributions should not be too hard16:46
jklarechef should be build for that ;)16:46
j^2I posted to openstack-dev too; trying to figure out if anyone had any suggestions, but no responses16:46
*** MattMan has joined #openstack-meeting-316:46
j^2yeah the install guide only says Ubuntu :(16:46
sc`one person responded this morning, which is where i got that link16:46
j^2oh, i must have missed it in the FLOOD of email :'(16:47
j^2i hate -dev for that reason16:47
sc`i have a filter specifically for [chef]16:47
j^2yeah but they sometimes fuck up the subjects :(16:47
j^2anywho, i'll filter through again16:47
*** dedery has quit IRC16:48
j^2jklare: that's more or less all i got, i just want to make sure yall have seen it16:48
*** mchestr has joined #openstack-meeting-316:48
j^2and ideally i should be able to take that same frame/skeleton and make magnum out of it too16:48
*** rpioso has joined #openstack-meeting-316:49
*** dedery_ has quit IRC16:49
j^2can i answer anything else about it?16:49
jklareno i think i am good here16:50
*** subscope has quit IRC16:50
j^2cool, i'll be at their meeting too16:50
j^2sc`: thanks for the heads up on the email16:51
*** balajin has joined #openstack-meeting-316:51
sc`np16:51
j^2jklare: fearless leader, back to you ;)16:51
jklare#topic anything else16:51
*** openstack changes topic to "anything else (Meeting topic: openstack_chef)"16:51
jklarei was at the ha-openstack meetup this morning16:52
*** JeanBriceCombebi has quit IRC16:52
j^2i bet that was an exciting conversation! :P16:52
jklarewas a quite interesting discussion on how to improve the documentation and how to get started in documenting all the solutions people have build for archieving the ultimate and true HA16:53
jklarethey will start with creating some etherpads and diagramms to sync up16:53
jklarei think we should try to get involved after that initial step has happened and see if we can use these diagramms and documentation to build some ha-wrappers16:54
*** thiagop has joined #openstack-meeting-316:54
j^2jklare: that's a great idea16:55
*** mgould has joined #openstack-meeting-316:55
*** Piet has quit IRC16:55
jklareall from my side :D16:56
jklareanything anybody wants to add?16:56
sc`getting ha configurations in will be good16:56
jklare4mins left16:56
*** cdearborn has joined #openstack-meeting-316:57
sc`i'm good16:57
j^2same here i'm good16:57
jklareok, thanks for attending and see you around16:58
jklare#endmeeting16:58
*** JeanBriceCombebi has joined #openstack-meeting-316:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Mon Nov 23 16:58:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-11-23-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-11-23-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-11-23-16.00.log.html16:58
j^2:D16:58
*** mariojv has joined #openstack-meeting-316:58
sc`see you on the channel :D16:58
*** dtantsur has joined #openstack-meeting-316:58
*** calbers has quit IRC16:59
*** rloo has joined #openstack-meeting-316:59
*** JeanBriceCombebi has quit IRC17:00
jrollohai.17:00
dtantsuro/17:00
mgouldo/17:00
vdroko/17:00
jroll#startmeeting ironic17:00
openstackMeeting started Mon Nov 23 17:00:50 2015 UTC and is due to finish in 60 minutes.  The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
stendulkero/17:00
jrollwelcome, welcome17:00
thiagopo/17:01
sinval\o17:01
krtayloro/17:01
jrolllight agenda today, which is here:17:01
*** pas-ha has joined #openstack-meeting-317:01
jroll#link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting17:01
mariojv\o17:01
pas-hao/17:01
jrolljumping right in.17:01
rloohi17:01
cdearborno/17:01
jroll#topic Announcements/Reminders17:01
*** openstack changes topic to "Announcements/Reminders (Meeting topic: ironic)"17:01
sambettso/17:01
jrollI just have one thing here; the midcycle plans17:01
*** Nisha has joined #openstack-meeting-317:01
jlvillalo/  Sorry I'm late17:01
rpiosoo/17:01
jrollnobody has opposed my proposal on the mailing list yet, for virtual midcycles17:02
jrollso I think we're going to go ahead with that if nobody has massive objections17:02
pas-hajroll, +117:02
jrollI will reply to that thread to that affect17:02
*** procmisc has left #openstack-meeting-317:02
jrollit'll take some work but I think it will be doable :)17:02
* krtaylor can help17:03
jrollalso, I'll be off next monday so I will find someone else to run this meeting17:03
jrolldevananda: ^17:03
jrollanyone else have announcements / reminders?17:03
*** jlanoux has quit IRC17:03
Nishao/17:03
*** mjturek1 has joined #openstack-meeting-317:03
davidlenwello/17:03
*** matrohon has quit IRC17:03
mjturek1\o17:03
dtantsurI'd like to remind that OSC spec was posted based on the discussion last meeting: https://review.openstack.org/24753917:04
dtantsurthis is public-facing bits, so make sure to have a look :)17:04
jrollthanks dtantsur :D17:04
jrollanything else? going once...17:05
thiagopdtantsur: reading...17:05
jroll#link https://review.openstack.org/#/c/247539/17:06
jroll#topic Subteam status updates17:06
*** openstack changes topic to "Subteam status updates (Meeting topic: ironic)"17:06
jrollas always, these are on the whiteboard:17:06
jroll#link https://etherpad.openstack.org/p/IronicWhiteBoard17:06
jrollI'll give folks a few minutes to review, feel free to ask questions etc17:06
*** vgridnev has quit IRC17:06
rloohmm, the number of 'high' bugs is creeping up17:07
jrollI wonder if they're actually all 'high'17:09
jroll:)17:09
rlookrtaylor: what's the hold up with the CI spec? anything we can do to speed it up?17:09
*** mjturek1 has left #openstack-meeting-317:09
rloowe should get email out, contact driver owners soon...17:09
*** mjturek1 has joined #openstack-meeting-317:09
jrollrloo: I was going to point that out, I think we should land it and bikeshed in the docs17:09
krtaylorrloo, there are a few questions, but we think that they can just be documented instead of doing everything in the spec17:10
rloojroll, krtaylor: OK. if you delete the stuff I question, I'll +2 it :)17:10
*** Swami has quit IRC17:10
thiagopGuys, I'm sorry to inform that liliars has suffered a car crash this weekend and will be out of combat for the next week. She is fine and at home, but with a shoulder dislocation to take care of17:10
krtaylorrloo, no, they are good questions, we'll address them, I'll add a comment to that effect17:10
thiagopkrtaylor jroll ^17:11
jrollthiagop: so I heard :(17:11
krtaylorwow! give her our best wishes!17:11
thiagopkrtaylor: I will17:11
jrollkrtaylor: rloo: let's get that done andmerged today17:11
rloothiagop: oh no. Glad she is fine...17:11
jlvillalthiagop, So sorry! Please send her best wishes for a fast recovery!17:11
rlooany way to send a virtual get well card signed by all of us?17:12
thiagoprloo: She would love it :D17:12
krtaylor++17:12
rlooanyone know how to do it?17:12
krtaylormaybe we just did :)17:13
*** ir2ivps7 has joined #openstack-meeting-317:13
rlookrtaylor: :D17:13
jrollrloo: I know of a thing, remind me after the meeting :)17:13
rloojroll: will do17:13
*** galstrom is now known as galstrom_zzz17:13
* devananda walks in late, still sipping his first coffee of the day17:14
jrollalright, anything else on subteam updates?17:14
jrollmorning deva :P17:15
rlooif anyone has ideas about ironic-lib17:15
rloomy comment about root_helper config, etc17:15
devanandaI ran out of coffee last night :(17:16
thiagopdevananda: creepiest story ever! o.o17:16
* jroll will think about rloo's ironic-lib thing17:17
* thiagop shivers17:17
rlooI'm guessing lintan isn't here?17:17
rlooI wanted to know what ASAP meant and why. Nothing happens ASAP around here :)17:17
*** gcb has quit IRC17:18
jrollrloo: I assume because that oslo.config change will drop soon17:18
jrollhttps://review.openstack.org/#/c/243001/17:18
jrollthey release weekly on mondays17:18
jrollwhen it does it will break our gate unless we fix all the things17:18
*** mdbooth has quit IRC17:18
rloojroll: I'm surprised they'd release something so soon that might break. I thought they normally gave some x period of time.17:19
rloojroll: or did we miss that announcement?17:19
jrollrloo: not sure17:19
* jroll asks a question on the oslo patch17:20
jrollrloo: now that I look, I'm not sure this actually breaks us17:21
*** yamahata has joined #openstack-meeting-317:22
jrollrloo: oh heh, it's something they *want* to do but can't because it will break projects, so we're blocking oslo on this17:22
jrollso ASAP to me means "soon" here17:22
rloojroll: oh, i see. that makes more sense :)17:23
*** lucasagomes has joined #openstack-meeting-317:23
jrollalright, going to move on then17:23
* lucasagomes is late17:23
jroll#topic Open Discussion17:23
*** openstack changes topic to "Open Discussion (Meeting topic: ironic)"17:23
jrollI have nothing here, others can feel free :)17:23
JayFGenerally speaking, I'm back to full time on Ironic technolgy stuff, so feel free to ping me to take a look at anything you think I could help on.17:24
rlooYay, welcome back JayF17:24
devanandaJayF: \o/17:24
JayFAs part of that I'm going to try and get the rescue spec cleaned up and comments responded to17:24
thiagopJayF: that's awesome17:24
* jroll has been so excited about this17:24
rlooJayF: and we could use your eyes on the other specs!17:24
lucasagomesJayF, w00t! wb17:24
*** ihrachys has quit IRC17:24
jlvillalJayF, Going to go back to software developer :)17:25
JayFrloo: I've already put votes on quite a few17:25
JayFjlvillal: technically "Linux Engineer", but you've got the right idea17:25
rloothx JayF!17:25
jlvillal:)17:25
dtantsurJayF, \o/17:25
rloooh, devananda, jroll wants to know if you can chair next Monday's meeting17:26
jrolloh yeah17:26
devanandasure17:26
jrollthanks17:26
* jroll sends supply of coffee to make sure you aren't late17:27
devanandathanks :)17:27
*** bklei_ has joined #openstack-meeting-317:27
*** lazy_prince has quit IRC17:28
jrollnothing else here?17:28
lucasagomesrloo, just saw ur answer on the ML for the logs for sensitive data17:29
rloolucasagomes: you good with that?17:29
lucasagomesrloo, +1 that's what I was thinking about the filter, someway you can enable/disable17:29
lucasagomespython logging framework supports it already17:29
lucasagomeswe need to check if the oslo.log abstraction allows we adding a filter to the logger or not17:30
lucasagomesbut can be worked out AFAIUI17:30
rloolucasagomes: ok, good to know if it can be worked out :)17:30
*** bklei has quit IRC17:31
rlooi think we can end the meeting early?17:31
vdrokoh, welcome back JayF :)17:31
*** nicodemos has joined #openstack-meeting-317:31
rloowe had a client release last week, right?17:32
jrollyep, 1.0!17:32
rloothe big thing is no py2617:32
jrolland ironic-lib 0.4.017:33
lucasagomeso/17:33
rloowell, there were probably other big things...17:33
jrolla few features17:33
jrollthere was an announcement on the -announce list17:33
JayFThis is a kinda-Ironic related note17:33
JayFThe work to make mimic py3 compatible is done, pending library releases17:33
*** galstrom_zzz is now known as galstrom17:33
krotschecko/17:33
JayFso hopefully the efforts to use it to test can get restarted and it can get into g-r17:34
* krotscheck has a messed up calendar since daylight savings17:34
rlooJayF: cool17:34
JayFApparently there's a twistd release in RC + a couple of other libs, and once they land it's good to go17:34
krotscheckRandom status update, we've got UX resources at Intel that we're working with now to start nailing down personas on both the horizon ironic panel and the webclient17:34
lucasagomesJayF, ah nice! Will be great to test the ironic client17:34
jrollso, I made a card for lilia, if you all want to sign it that will be awesome. it goes out in 5.5 hours: http://www.groupcard.com/c/zDMB_CexmHF17:34
devanandaJayF: nice17:35
rloothx jroll!17:35
*** kebray has joined #openstack-meeting-317:35
sinvaljroll: awesome, she will love it17:35
*** kebray_ has quit IRC17:36
jroll:)17:36
*** afaranha has joined #openstack-meeting-317:37
*** nkrinner has quit IRC17:37
* lucasagomes signs it17:37
* krotscheck signs it17:38
*** numans has joined #openstack-meeting-317:38
* sambetts signed it17:38
jrollok anything else here or can we go away now :)17:39
*** e0ne has quit IRC17:39
* krotscheck needs a running ironic + webclient to do UX testing on. Any suggestions are welcome, but brainstorming is probably more useful in the main channel.17:40
jrollyeah, let's do that in main channel17:40
jrollthanks for coming everyone :)17:40
jroll#endmeeting17:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:40
openstackMeeting ended Mon Nov 23 17:40:52 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-11-23-17.00.html17:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-11-23-17.00.txt17:40
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-11-23-17.00.log.html17:40
*** mariojv has left #openstack-meeting-317:40
*** lucasagomes has left #openstack-meeting-317:40
*** thiagop has left #openstack-meeting-317:41
*** cdearborn has left #openstack-meeting-317:41
*** rloo has left #openstack-meeting-317:41
*** dtantsur has left #openstack-meeting-317:41
*** rpioso has left #openstack-meeting-317:42
*** mjturek1 has left #openstack-meeting-317:43
*** sc68cal has quit IRC17:46
*** nicodemos has quit IRC17:46
*** sc68cal has joined #openstack-meeting-317:47
*** stendulker has quit IRC17:49
*** nicodemos has joined #openstack-meeting-317:50
*** nicodemos has left #openstack-meeting-317:51
*** vgridnev has joined #openstack-meeting-317:51
*** mgould has left #openstack-meeting-317:54
*** kzaitsev_mb has quit IRC17:55
*** kzaitsev_mb has joined #openstack-meeting-317:55
*** galstrom is now known as galstrom_zzz17:56
*** afaranha has left #openstack-meeting-317:57
*** safchain has quit IRC17:58
*** betherly has joined #openstack-meeting-317:59
*** bklei_ has quit IRC18:01
*** Swami has joined #openstack-meeting-318:01
*** bklei has joined #openstack-meeting-318:01
*** msambol has quit IRC18:03
*** iyamahat has joined #openstack-meeting-318:03
*** kzaitsev_mb has quit IRC18:04
*** rossella_s has quit IRC18:07
*** Sukhdev_ has quit IRC18:09
*** armax has quit IRC18:10
*** yamahata has quit IRC18:11
*** egallen has quit IRC18:13
*** e0ne has joined #openstack-meeting-318:22
*** madhu_ak has joined #openstack-meeting-318:22
*** sinval has left #openstack-meeting-318:23
*** aleksandr_null has quit IRC18:23
*** balajin has left #openstack-meeting-318:24
*** ivar-lazzaro has joined #openstack-meeting-318:28
*** ivar-lazzaro has quit IRC18:28
*** klkumar has quit IRC18:28
*** bpokorny_ has joined #openstack-meeting-318:28
*** e0ne has quit IRC18:29
*** e0ne has joined #openstack-meeting-318:29
*** BrianB__ has quit IRC18:29
*** ivar-lazzaro has joined #openstack-meeting-318:30
*** neiljerram has quit IRC18:32
*** bpokorny has quit IRC18:32
*** bpokorny_ has quit IRC18:33
*** s3wong has joined #openstack-meeting-318:41
*** wuhg has quit IRC18:41
*** shwetaap has quit IRC18:43
*** igordcard has quit IRC18:44
*** ihrachys has joined #openstack-meeting-318:45
*** lazy_prince has joined #openstack-meeting-318:46
*** dshakhray has quit IRC18:50
*** numans has quit IRC18:50
*** egallen has joined #openstack-meeting-318:52
*** msambol has joined #openstack-meeting-318:53
*** bpokorny has joined #openstack-meeting-318:56
*** ihrachys has quit IRC18:59
*** ihrachys has joined #openstack-meeting-318:59
*** pas-ha has left #openstack-meeting-319:02
*** lazy_prince has quit IRC19:02
*** egallen has quit IRC19:06
*** Nisha has quit IRC19:09
*** Nisha has joined #openstack-meeting-319:09
*** flwang has quit IRC19:13
*** iyamahat has quit IRC19:15
*** rossella_s has joined #openstack-meeting-319:22
*** ihrachys has quit IRC19:23
*** flwang has joined #openstack-meeting-319:27
*** ihrachys has joined #openstack-meeting-319:29
*** salv-orlando has quit IRC19:34
*** ihrachys_ has joined #openstack-meeting-319:35
*** ihrachys has quit IRC19:35
*** iyamahat has joined #openstack-meeting-319:39
*** bpokorny has quit IRC19:41
*** bpokorny has joined #openstack-meeting-319:42
*** vkmc is now known as vkmc-afk19:47
*** ihrachys_ has quit IRC19:49
*** ihrachys has joined #openstack-meeting-319:49
*** john-davidge has joined #openstack-meeting-319:51
*** e0ne has quit IRC19:55
*** dims has joined #openstack-meeting-319:56
*** bklei_ has joined #openstack-meeting-319:57
*** ihrachys has quit IRC19:58
*** bklei has quit IRC20:00
*** ihrachys has joined #openstack-meeting-320:01
*** john-davidge has quit IRC20:03
*** neelashah has quit IRC20:08
*** neelashah has joined #openstack-meeting-320:09
*** neelashah1 has joined #openstack-meeting-320:12
*** neelashah has quit IRC20:13
*** dshakhray has joined #openstack-meeting-320:14
*** neelashah has joined #openstack-meeting-320:16
*** ihrachys has quit IRC20:16
*** neelashah1 has quit IRC20:16
*** bklei_ has quit IRC20:19
*** yamahata has joined #openstack-meeting-320:20
*** bklei has joined #openstack-meeting-320:20
*** ihrachys has joined #openstack-meeting-320:21
*** armax has joined #openstack-meeting-320:22
*** rossella_s has quit IRC20:23
*** rossella_s has joined #openstack-meeting-320:23
*** alaski_ is now known as alaski20:24
*** baoli has quit IRC20:27
*** madhu_ak_ has joined #openstack-meeting-320:34
*** madhu_ak has quit IRC20:36
*** dtardivel has quit IRC20:37
*** e0ne has joined #openstack-meeting-320:42
*** vinay_yadhav has joined #openstack-meeting-320:45
*** madhu_ak_ is now known as madhu_ak20:45
*** baoli has joined #openstack-meeting-320:46
*** baoli has quit IRC20:47
*** baoli has joined #openstack-meeting-320:47
*** sarob_ has joined #openstack-meeting-320:47
*** mchestr has quit IRC20:48
*** mchestr has joined #openstack-meeting-320:48
*** sarob_ has quit IRC20:51
*** baoli has quit IRC20:52
*** hichihara has joined #openstack-meeting-320:54
*** baoli has joined #openstack-meeting-320:55
*** salv-orlando has joined #openstack-meeting-320:56
*** baoli has quit IRC20:56
*** baoli has joined #openstack-meeting-320:57
*** bklei_ has joined #openstack-meeting-320:57
*** yamamoto has joined #openstack-meeting-320:58
*** sarob_ has joined #openstack-meeting-320:58
*** neiljerram_bb has joined #openstack-meeting-320:59
flwang#startmeeting zaqar21:00
openstackMeeting started Mon Nov 23 21:00:09 2015 UTC and is due to finish in 60 minutes.  The chair is flwang. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: zaqar)"21:00
openstackThe meeting name has been set to 'zaqar'21:00
*** hoangcx has joined #openstack-meeting-321:00
jasondotstaro/21:00
flwangjasondotstar: hey21:00
flwang#topic roll call21:00
*** openstack changes topic to "roll call (Meeting topic: zaqar)"21:00
flwangjasondotstar: if there is only you and me, then let's make it as a party instead of meeting :)21:01
* jasondotstar grabs chips and dip21:01
*** hoangcx has left #openstack-meeting-321:01
*** bklei has quit IRC21:02
flwangjasondotstar: don't want to waste your time, before the others joining, would you mind updating the puppet status?21:02
flwangi'm really keen to know it :)21:02
jasondotstarsure.21:02
jasondotstarso I've got the debian stuff working now21:02
flwangjasondotstar: awesome awesome21:02
jasondotstarmeaning w/ the puppet module you can install it with RPM or DEB based21:03
jasondotstari didn't get a chance to talk to anyone about which conf options to expose21:03
jasondotstarso perhaps someone can advise me there21:03
flwangjasondotstar: i mentioned that with kgriffs21:03
jasondotstarand then,  we need to write the tests21:04
flwangwho is the funder of zaqar/marconi from Rackspace21:04
flwangyou know rackspace is running zaqar21:04
jasondotstari didn't know that21:04
flwangi asked him to share the conf what rackspace is using21:04
jasondotstarright21:04
flwangbut i haven't got the response, i will ping him again21:04
jasondotstarthat'd be helpful21:04
jasondotstarwe can maybe default to those21:05
flwangbut before that, i can help you21:05
jasondotstar*nod*21:05
jasondotstarok21:05
flwangjasondotstar: so what do you need for now? a basic reference conf?21:05
jasondotstaryes plz21:05
jasondotstarthat would work21:05
flwangjasondotstar: what's the database you're using?21:06
flwangmongo?21:06
jasondotstaryes mongo.21:06
flwangcool, it would be nice if you can give me your email21:06
*** bklei_ has quit IRC21:06
jasondotstarsure21:07
flwangso that i can send it to you after it's ready21:07
*** bklei has joined #openstack-meeting-321:07
jasondotstarsent21:07
flwangjasondotstar: got, cool21:07
*** Nisha has quit IRC21:07
*** sdake_ has joined #openstack-meeting-321:07
flwangjasondotstar: did you upload your patch for review?21:08
flwangjasondotstar: if so, i can ask my colleague(ops guy) to give it a review/try21:08
*** e0ne has quit IRC21:08
*** sdake has quit IRC21:09
*** krotscheck has quit IRC21:10
*** baoli has quit IRC21:11
*** anteaya has quit IRC21:11
*** epheo has quit IRC21:11
*** baoli has joined #openstack-meeting-321:11
*** jasondotstar has quit IRC21:12
*** baoli has quit IRC21:12
*** baoli has joined #openstack-meeting-321:12
*** krotscheck has joined #openstack-meeting-321:17
*** e0ne has joined #openstack-meeting-321:17
*** epheo has joined #openstack-meeting-321:18
*** jasondotstar has joined #openstack-meeting-321:18
*** kzaitsev_mb has joined #openstack-meeting-321:19
flwangjasondotstar: still around?21:20
*** baoli has quit IRC21:22
*** anteaya has joined #openstack-meeting-321:26
*** vgridnev has quit IRC21:27
*** bradjones has quit IRC21:27
*** vkmc-afk is now known as vkmc21:27
vkmcflwang, o/21:28
*** vgridnev has joined #openstack-meeting-321:28
flwangvkmc: i miss you21:28
*** egallen has joined #openstack-meeting-321:28
flwangwe lost jasondotstar now21:28
flwangvkmc: i just confirmed with jasondotstar the puppet status21:29
flwangvkmc: basically, we're in good shape21:29
vkmcflwang, that's great to hear!21:29
flwangvkmc:  we need to provide a ref config for him21:29
*** bradjones has joined #openstack-meeting-321:29
*** bradjones has quit IRC21:29
*** bradjones has joined #openstack-meeting-321:29
flwangas the default config file21:29
vkmcflwang, we need an operator POV for this probably21:30
flwangvkmc: and we definately made some great progress for zaqar client and the docs work, see https://etherpad.openstack.org/p/mitaka-zaqar-assignment21:30
vkmcflwang, yeah :) saw the patchsets going up21:31
flwangvkmc: i have mentioned that with kgriffs to ask a conf which rackspace is using21:31
flwangbut i haven't got response, i will ping him again21:31
flwangvkmc: so pls review them :)21:31
*** david-lyle has quit IRC21:31
vkmcflwang, sure thing21:31
vkmcflwang, I'll try to catch kgriffs myself, he is closer to my tz21:32
flwangvkmc: awesome, thanks21:32
*** vgridnev has quit IRC21:32
vkmcflwang, I also had several discussions about docs with Eva-i21:32
flwangvkmc: cool, would you like to share them now?21:32
vkmcflwang, I'm aware she already told you that she will be an intern in Zaqar for the upcoming Outreachy round21:33
vkmcflwang, the internship starts in December, but she is willing to start already... that's very awesome from her :D21:33
*** krtaylor has quit IRC21:33
vkmcflwang, sure, we are laying out things here https://etherpad.openstack.org/p/zaqar-mitaka-docs21:34
*** david-lyle has joined #openstack-meeting-321:34
flwangvkmc: yep, Eva-i is really helpful, she does a great job21:35
flwangi'm really happy to see she could be a formal intern for the outreachy project21:35
vkmcme too :D21:35
flwangas for the docs, anything you want to highlight?21:35
vkmcyeah... we will have an important revamp on docs21:36
vkmcwe are going to remove most of the content we have in the wiki, since it's redundant to some of the content under developer/zaqar21:36
vkmcwe are going to move the API reference to developer/zaqar21:36
vkmcplus we are going to fix the bugs Eva-i pointed out in the etherpad (and if we find more in the way, we are going to add them there)21:37
vkmconce we have all the developers docs in place, we are going to start working on some user docs, with configuration samples and use cases21:37
vkmcthat with the OpenStack Docs team21:37
flwangvkmc: sounds a plan21:37
vkmcperhaps something we need to define if that change from wiki to developers guide is ok for you21:38
flwangvkmc: as you know, i'm working on the spec for config ref and user guides21:38
vkmcsuper21:38
*** baoli has joined #openstack-meeting-321:38
vkmcEva-i checked how other projects are handling docs and perhaps this is the best way21:38
flwangvkmc: agree21:39
vkmcsomething that was a bit confusing is that the docs under developer/zaqar are shipped with the code21:39
vkmcand those docs contains information on "how to contribute"21:39
vkmcbut that is an standard for every other OpenStack project21:39
flwangvkmc: agree21:39
*** Sukhdev has joined #openstack-meeting-321:40
vkmcso yeah, that's pretty much it21:40
vkmcI think we are going to start with that soon :)21:40
vkmcand then we can help you with the spec for config red and user guides21:40
flwangrecently, i realized that we focused the zaqar server side too much in previous cycles21:40
flwangand we're losing some potential users because of the bad docs, weak client support, etc21:41
flwangvkmc: sounds good, really appreciate for your support21:41
vkmcflwang, totally agree21:42
vkmcthis cycle should be to polish that21:42
vkmcthanks for leading the effort :)21:42
*** sdake_ has quit IRC21:42
*** sdake has joined #openstack-meeting-321:42
*** dims_ has joined #openstack-meeting-321:43
flwangvkmc: so pls pls review the client patches heavily so that we can ask sahara team to start integrate zaqar21:43
*** e0ne has quit IRC21:43
vkmcflwang, I'm doing that now21:43
flwangvkmc: i know you're busy but i have to push you guys, sorry :)21:44
vkmcflwang, that's totally fine21:44
vkmcwe work under pressure21:44
*** dims has quit IRC21:44
*** Piet has joined #openstack-meeting-321:45
flwangvkmc: i will update the assignment etherpad to add the docs work which Eva-i and you're working21:45
*** njohnston is now known as nate_gone21:46
*** vinay_yadhav has quit IRC21:46
*** banix has quit IRC21:46
vkmcflwang, do you want me to do that?21:46
*** krtaylor has joined #openstack-meeting-321:47
flwangvkmc: it would be awesome21:47
flwangvkmc: yes, pls21:47
vkmcflwang, cool :) will add that after I'm done with the reviews21:47
flwangvkmc: btw, for the client work, we obviously need some unti test for cli21:47
flwangbut we don't have any test for that21:47
vkmcoh.. hmm21:48
flwangso i will user a separate patch to add a test framework for cli21:48
vkmcgood point21:48
vkmcyes21:48
flwangif you're not really comfortable with that, i can do that firstly and then as the other patches to depend on it21:49
flwangbut21:49
flwangit will slow the progress21:49
flwangi have to balance :(21:49
vkmcnah, we don't have enough resources21:49
vkmcwe need to move fast21:49
*** dshakhray has quit IRC21:50
flwangvkmc: yep21:50
flwangbesides, i'm still a fan of queue :D21:50
flwangi know flaper87 may beat me, hah21:51
vkmchaha no worries, he is not around21:51
flwangso i'm working on the comparison between SQS, and other china public cloud's queuing service to figure out the gap21:51
vkmcthat sounds good21:52
flwangbasically, the first thing i may propose is allow user to edit the queue's properties21:52
vkmclike... metadata?21:52
flwangyep, i know, we can do that, but my point is21:53
flwanghaving some reserved properties21:53
flwanglike the TTL, which we're putting them in conf file21:53
flwangnot flexible for each queue21:53
*** dconde has joined #openstack-meeting-321:53
vkmcnot flexible for each message you mean21:54
flwangmaybe that's not a good example, so pls see this http://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SetQueueAttributes.html21:54
vkmclet see21:55
flwangfor now, IIRC, we can set the queue's metadata21:55
flwangbut21:55
*** jhesketh has quit IRC21:55
*** david-lyle has quit IRC21:55
flwangwe're not really using them21:55
*** jhesketh has joined #openstack-meeting-321:55
flwanguser can put anything in the queue's matadata, so what?21:55
flwangzaqar don't know what they are21:56
vkmcthat's true21:56
*** john-davidge has joined #openstack-meeting-321:56
vkmcour metadata is just info that users think are important, but we don't do anything with it21:56
flwangvkmc: we could/should have some reserved metadata starts with _21:57
*** john-davidge has quit IRC21:57
vkmcflwang, sounds good21:57
vkmcsomething I'm interested about21:57
flwangand zaqar can use them to get a more flexiable queue21:57
vkmcis in the visibility attribute SQS has21:57
*** john-davidge has joined #openstack-meeting-321:57
flwangvkmc: we can take 2-3 attributes as the first step21:58
vkmcsounds good21:58
vkmcfeature for mitaka? :) v221:58
vkmcmitaka-321:58
flwangv221:59
flwangm-221:59
flwangso that we can have some time to revoke21:59
flwangi'm joking :D21:59
flwanglet's talk in zaqar channel :)22:00
flwangthank you, everyone22:00
*** mrmartin has quit IRC22:00
flwang#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Mon Nov 23 22:00:19 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-11-23-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-11-23-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zaqar/2015/zaqar.2015-11-23-21.00.log.html22:00
*** fitoduarte has joined #openstack-meeting-322:00
vkmcthanks!22:01
*** mrmartin has joined #openstack-meeting-322:03
*** krtaylor has quit IRC22:03
*** david-lyle has joined #openstack-meeting-322:03
*** neelashah1 has joined #openstack-meeting-322:03
*** neiljerram_bb has quit IRC22:04
*** david-lyle has quit IRC22:04
*** neelashah has quit IRC22:06
*** neelashah has joined #openstack-meeting-322:06
*** neelashah1 has quit IRC22:08
*** hichihara has quit IRC22:09
*** neelashah1 has joined #openstack-meeting-322:09
*** julim_ has quit IRC22:09
*** neelashah has quit IRC22:11
*** sarob_ has quit IRC22:13
*** salv-orl_ has joined #openstack-meeting-322:15
*** krtaylor has joined #openstack-meeting-322:15
*** yamamoto has quit IRC22:18
*** salv-orlando has quit IRC22:19
*** isq has quit IRC22:19
*** david-lyle has joined #openstack-meeting-322:21
*** isq has joined #openstack-meeting-322:21
*** david-lyle has quit IRC22:25
*** egallen has quit IRC22:27
*** armax has quit IRC22:30
*** ihrachys has quit IRC22:30
*** ihrachys has joined #openstack-meeting-322:31
*** dimtruck is now known as zz_dimtruck22:32
*** sdake has quit IRC22:37
*** salv-orlando has joined #openstack-meeting-322:39
*** sdake has joined #openstack-meeting-322:39
*** salv-orl_ has quit IRC22:42
*** woodster_ has joined #openstack-meeting-322:43
*** mrmartin has quit IRC22:43
*** sambetts is now known as sambetts-afk22:45
*** mrmartin has joined #openstack-meeting-322:45
*** mrmartin has quit IRC22:45
*** iyamahat has quit IRC22:55
*** dims_ has quit IRC22:55
*** amotoki has quit IRC22:58
*** msambol has quit IRC22:58
*** david-lyle has joined #openstack-meeting-323:03
*** david-lyle has quit IRC23:05
*** tellesnobrega is now known as tellesnobrega_af23:08
*** peristeri has quit IRC23:14
*** doug-fish has quit IRC23:17
*** john-davidge has quit IRC23:19
*** mchestr has quit IRC23:21
*** mchestr has joined #openstack-meeting-323:21
*** jhesketh has left #openstack-meeting-323:22
*** david-lyle has joined #openstack-meeting-323:23
*** mchestr has quit IRC23:24
*** mchestr has joined #openstack-meeting-323:24
*** dims_ has joined #openstack-meeting-323:25
*** david-lyle has quit IRC23:25
*** dims_ has quit IRC23:26
*** galstrom_zzz is now known as galstrom23:27
*** ihrachys has quit IRC23:29
*** david-lyle has joined #openstack-meeting-323:35
*** david-lyle has quit IRC23:41
*** david-ly_ has joined #openstack-meeting-323:41
*** rbak_ has quit IRC23:46
*** armax has joined #openstack-meeting-323:47
*** kebray has quit IRC23:50
*** bklei has quit IRC23:59
*** msambol has joined #openstack-meeting-323:59
*** bklei has joined #openstack-meeting-323:59

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