Monday, 2017-05-01

*** esikachev has joined #openstack-meeting-alt00:00
*** esikachev has quit IRC00:04
*** cloudrancher has quit IRC00:11
*** bzhao has quit IRC00:11
*** cloudrancher has joined #openstack-meeting-alt00:12
*** JudeC has quit IRC00:18
*** armstrong has joined #openstack-meeting-alt00:21
*** armstrong has quit IRC00:21
*** neiljerram has quit IRC00:23
*** EricGonczer_ has quit IRC00:31
*** ijw has joined #openstack-meeting-alt00:32
*** baoli has joined #openstack-meeting-alt00:33
*** ijw has quit IRC00:38
*** amotoki has joined #openstack-meeting-alt00:38
*** baoli has quit IRC00:38
*** amotoki has quit IRC00:42
*** esikachev has joined #openstack-meeting-alt00:59
*** bsilverman_12 has quit IRC01:02
*** bsilverman_ has joined #openstack-meeting-alt01:02
*** esikachev has quit IRC01:03
*** EricGonczer_ has joined #openstack-meeting-alt01:03
*** baoli has joined #openstack-meeting-alt01:06
*** EricGonczer_ has quit IRC01:08
*** salv-orlando has joined #openstack-meeting-alt01:16
*** salv-orlando has quit IRC01:22
*** shobhar has quit IRC01:22
*** shobhar_ has quit IRC01:22
*** baoli has quit IRC01:24
*** baoli has joined #openstack-meeting-alt01:24
*** ijw has joined #openstack-meeting-alt01:30
*** baoli has quit IRC01:31
*** slagle has joined #openstack-meeting-alt01:34
*** yamahata_ has joined #openstack-meeting-alt01:35
*** JudeC has joined #openstack-meeting-alt01:47
*** brault has joined #openstack-meeting-alt01:57
*** esikachev has joined #openstack-meeting-alt01:57
*** brault has quit IRC02:01
*** esikachev has quit IRC02:01
*** esikachev has joined #openstack-meeting-alt02:03
*** esikachev has quit IRC02:07
*** salv-orlando has joined #openstack-meeting-alt02:18
*** iyamahat has joined #openstack-meeting-alt02:20
*** salv-orlando has quit IRC02:22
*** yamamoto has joined #openstack-meeting-alt02:24
*** yangyapepeng has joined #openstack-meeting-alt02:37
*** amotoki has joined #openstack-meeting-alt02:39
*** yangyapepeng has quit IRC02:41
*** amotoki has quit IRC02:43
*** JudeC has quit IRC02:44
*** ijw has quit IRC03:01
*** ijw has joined #openstack-meeting-alt03:02
*** esikachev has joined #openstack-meeting-alt03:03
*** ijw has quit IRC03:06
*** esikachev has quit IRC03:08
*** fnaval has quit IRC03:10
*** slaweq has joined #openstack-meeting-alt03:13
*** fnaval has joined #openstack-meeting-alt03:13
*** slaweq has quit IRC03:17
*** dave-mccowan has quit IRC03:22
*** iyamahat has quit IRC03:23
*** yamamoto has quit IRC03:27
*** yamahata_ has quit IRC03:40
*** dimtruck is now known as zz_dimtruck03:50
*** ijw has joined #openstack-meeting-alt04:02
*** esikachev has joined #openstack-meeting-alt04:04
*** ijw has quit IRC04:07
*** yangyapepeng has joined #openstack-meeting-alt04:08
*** esikachev has quit IRC04:08
*** yamamoto has joined #openstack-meeting-alt04:09
*** yangyapepeng has quit IRC04:12
*** links has joined #openstack-meeting-alt04:12
*** adisky_ has joined #openstack-meeting-alt04:14
*** sshnaidm is now known as sshnaidm|pto04:19
*** tonytan4ever has joined #openstack-meeting-alt04:25
*** ijw has joined #openstack-meeting-alt04:38
*** ijw has quit IRC04:42
*** brault has joined #openstack-meeting-alt04:57
*** brault has quit IRC05:01
*** esikachev has joined #openstack-meeting-alt05:05
*** esikachev has quit IRC05:09
*** trinaths has joined #openstack-meeting-alt05:18
*** salv-orlando has joined #openstack-meeting-alt05:20
*** trinaths has quit IRC05:22
*** salv-orlando has quit IRC05:25
*** ijw has joined #openstack-meeting-alt05:39
*** JudeC has joined #openstack-meeting-alt05:43
*** ijw has quit IRC05:46
*** trinaths has joined #openstack-meeting-alt05:51
*** esikachev has joined #openstack-meeting-alt05:58
*** trinaths has left #openstack-meeting-alt06:00
*** esikachev has quit IRC06:08
*** yangyapepeng has joined #openstack-meeting-alt06:09
*** yangyapepeng has quit IRC06:13
*** esikachev has joined #openstack-meeting-alt06:20
*** salv-orlando has joined #openstack-meeting-alt06:22
*** salv-orlando has quit IRC06:26
*** salv-orlando has joined #openstack-meeting-alt06:37
*** lei-zh has joined #openstack-meeting-alt06:37
*** amotoki has joined #openstack-meeting-alt06:40
*** vds has joined #openstack-meeting-alt06:41
*** ijw has joined #openstack-meeting-alt06:43
*** amotoki has quit IRC06:45
*** ijw has quit IRC06:48
*** knangia has joined #openstack-meeting-alt06:52
*** tesseract has joined #openstack-meeting-alt07:06
*** salv-orlando has quit IRC07:08
*** rcernin has joined #openstack-meeting-alt07:12
*** slaweq has joined #openstack-meeting-alt07:13
*** myoung has quit IRC07:16
*** slaweq has quit IRC07:18
*** slaweq has joined #openstack-meeting-alt07:23
*** rcernin has quit IRC07:32
*** tonytan_brb has joined #openstack-meeting-alt07:39
*** tonytan4ever has quit IRC07:41
*** slaweq has quit IRC07:42
*** ijw has joined #openstack-meeting-alt07:44
*** JudeC has quit IRC07:48
*** slaweq has joined #openstack-meeting-alt07:50
*** ttx has quit IRC08:00
*** ttx has joined #openstack-meeting-alt08:01
*** ijw has quit IRC08:05
*** d0ugal has quit IRC08:07
*** d0ugal has joined #openstack-meeting-alt08:08
*** salv-orlando has joined #openstack-meeting-alt08:08
*** yangyapepeng has joined #openstack-meeting-alt08:09
*** salv-orlando has quit IRC08:13
*** yangyapepeng has quit IRC08:14
*** JudeC has joined #openstack-meeting-alt08:17
*** leanderthal|afk is now known as leanderthal08:19
*** brault has joined #openstack-meeting-alt08:20
*** MarkBaker has joined #openstack-meeting-alt08:32
*** leanderthal is now known as leanderthal|afk08:38
*** MarkBaker has quit IRC08:51
*** tonytan_brb has quit IRC08:54
*** esikachev has quit IRC08:54
*** ijw has joined #openstack-meeting-alt09:01
*** MarkBaker has joined #openstack-meeting-alt09:03
*** ijw has quit IRC09:07
*** salv-orlando has joined #openstack-meeting-alt09:09
*** JudeC has quit IRC09:11
*** salv-orlando has quit IRC09:14
*** dalgaaf has quit IRC09:29
*** dalgaaf has joined #openstack-meeting-alt09:31
*** lei-zh has quit IRC09:32
*** ijw has joined #openstack-meeting-alt10:03
*** sdague has joined #openstack-meeting-alt10:09
*** esikachev has joined #openstack-meeting-alt10:10
*** yangyapepeng has joined #openstack-meeting-alt10:10
*** salv-orlando has joined #openstack-meeting-alt10:10
*** ijw has quit IRC10:12
*** yangyapepeng has quit IRC10:15
*** salv-orlando has quit IRC10:15
*** dizquierdo has joined #openstack-meeting-alt10:38
*** jkilpatr has joined #openstack-meeting-alt10:41
*** tonytan4ever has joined #openstack-meeting-alt10:54
*** rossella_s has joined #openstack-meeting-alt10:58
*** ansmith has quit IRC11:05
*** ijw has joined #openstack-meeting-alt11:09
*** ijw has quit IRC11:14
*** ganso has joined #openstack-meeting-alt11:22
*** dave-mccowan has joined #openstack-meeting-alt11:23
*** yangyapepeng has joined #openstack-meeting-alt11:26
*** yangyapepeng has quit IRC11:30
*** slaweq has quit IRC11:31
*** slaweq has joined #openstack-meeting-alt11:31
*** slaweq__ has joined #openstack-meeting-alt11:33
*** slaweq has quit IRC11:37
*** MarkBaker has quit IRC11:42
*** dizquierdo has quit IRC11:54
*** sdague has quit IRC11:55
*** tonytan4ever has quit IRC11:55
*** rossella_s has quit IRC11:59
*** unrahul has quit IRC12:06
*** dprince has joined #openstack-meeting-alt12:07
*** ijw has joined #openstack-meeting-alt12:11
*** sdague has joined #openstack-meeting-alt12:12
*** ijw has quit IRC12:17
*** MarkBaker has joined #openstack-meeting-alt12:17
*** amotoki has joined #openstack-meeting-alt12:27
*** MarkBaker has quit IRC12:28
*** knangia has quit IRC12:41
*** dustins has joined #openstack-meeting-alt12:48
*** jaypipes has joined #openstack-meeting-alt12:54
*** dklyle has joined #openstack-meeting-alt12:57
*** david-lyle has quit IRC12:57
*** ansmith has joined #openstack-meeting-alt12:59
*** gcb has joined #openstack-meeting-alt13:00
*** jcoufal has joined #openstack-meeting-alt13:03
*** gcb has quit IRC13:03
*** gcb has joined #openstack-meeting-alt13:04
*** funzo has joined #openstack-meeting-alt13:07
*** funzo_ has joined #openstack-meeting-alt13:10
*** funzo has quit IRC13:10
*** salv-orlando has joined #openstack-meeting-alt13:12
*** ijw has joined #openstack-meeting-alt13:13
*** baoli has joined #openstack-meeting-alt13:13
*** baoli has quit IRC13:13
*** baoli has joined #openstack-meeting-alt13:14
*** jkilpatr has quit IRC13:16
*** salv-orlando has quit IRC13:17
*** ijw has quit IRC13:18
*** baoli has quit IRC13:25
*** yangyapepeng has joined #openstack-meeting-alt13:27
*** tonytan4ever has joined #openstack-meeting-alt13:27
*** haleyb has quit IRC13:27
*** jkilpatr has joined #openstack-meeting-alt13:28
*** links has quit IRC13:29
*** yangyapepeng has quit IRC13:31
*** ijw has joined #openstack-meeting-alt13:33
*** lbragstad_ is now known as lbragstad13:37
*** EricGonczer_ has joined #openstack-meeting-alt13:38
*** neiljerram has joined #openstack-meeting-alt13:41
*** esikachev has quit IRC13:43
*** neiljerram has quit IRC13:46
*** cknight has joined #openstack-meeting-alt13:46
*** baoli has joined #openstack-meeting-alt13:46
*** neiljerram has joined #openstack-meeting-alt13:48
*** lei-zh has joined #openstack-meeting-alt13:49
*** esikachev has joined #openstack-meeting-alt13:52
*** gcb has quit IRC13:52
*** gcb has joined #openstack-meeting-alt13:53
*** gcb_ has joined #openstack-meeting-alt13:54
*** gcb_ has quit IRC13:56
*** lei-zh has quit IRC13:56
*** cdent has joined #openstack-meeting-alt13:57
*** gcb has quit IRC13:58
*** esikachev has quit IRC13:58
*** ijw has quit IRC13:59
*** mriedem has joined #openstack-meeting-alt14:00
*** beekneemech is now known as bnemec14:00
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon May  1 14:00:27 2017 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:00
*** gcb has joined #openstack-meeting-alt14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
cdento/14:00
mriedemo/14:00
edleafeWho's here?14:00
*** neiljerram has quit IRC14:00
jaypipes0/14:00
jaypipesor o/14:01
cdentjaypipes: I think the first was right, you do have an impressively large head14:01
*** xyang1 has joined #openstack-meeting-alt14:01
jaypipescdent: lol14:01
* edleafe thought cdent was going to make a zero brains crack14:01
cdentlook at the big brains on jay!14:02
edleafe#topic Specs & Reviews14:02
*** openstack changes topic to "Specs & Reviews (Meeting topic: nova_scheduler)"14:02
edleafeos-traits14:02
edleafe#link Sync os-traits in placement DB https://review.openstack.org/45012514:02
edleafeIs this something we need? Or should we only do this if we see a performance hit?14:03
jaypipesI don't think it's a performance thing14:03
*** ijw has joined #openstack-meeting-alt14:03
mriedemsfinucan would probably warn them against using anything from "from nova.cmd import common as cmd_common"14:03
jaypipesya14:04
edleafeso is this something necessary?14:05
mriedemhe's been alerted14:05
mriedemso what is this for? if we don't find a trait in the db we lookup in the library?14:05
mriedemi still haven't read the traits spec14:06
mriedemand if your library is backlevel then you're kind of screwed for new traits14:06
cdentmriedem: its to put all the traits in the db14:06
cdentinstead of using the library14:06
edleafeIt's for when the os-traits lib changes14:06
edleafeThis will update the copy in the DB14:06
*** esikachev has joined #openstack-meeting-alt14:06
jaypipesmriedem: yeah, basically it adds records for the standard traits (os-traits traits) into the API DB and ensures there's records in the traits table with the name of the trait and an autoincremt id.14:06
edleafeSo we can do all those yummy SQL joings14:06
mriedembut if we don't find a trait in the db we fallback to the library?14:06
edleafejoins14:06
mriedemhow often are operators expected to run this?14:07
jaypipesmriedem: whereas we have all the standard resource classes use their "ID" from the fields.ResourceClass.STANDARD enum, we don't have the same luxury for standard traits.14:07
mriedemon a cron?14:07
*** cloudrancher has quit IRC14:07
jaypipesmriedem: whenever os-traits does a release and they want to use one of the new traits in that release.14:07
jaypipesmriedem: it's not too onerous, really...14:08
mriedemit's not just operators using traits though right? but i guess they can control if they expose the support14:08
*** cloudrancher has joined #openstack-meeting-alt14:08
mriedemare the traits available in a cloud discoverable by the end user?14:08
cdentso, just for sake of devil's advocate, what's wrong with validating input against the os.traits module, and then storing the strings in the db?14:08
jaypipesmriedem: yes14:09
mriedemoh right,14:09
mriedem /traits14:09
mriedemderp14:09
jaypipesright14:09
jaypipescdent: either way, it will depend on the release of os-traits the controller has installed.14:10
mriedemok i was concerned about interop, but since it's discoverable i care less14:10
mriedemso if i'm an operator, i probably run this like i run nova-manage db sync14:10
cdentjaypipes: sure but if you don't sync, then you don't have to sync14:10
cdentwhich is one less thing to forget14:10
cdentand the package will automatically depend on the os_traits lib14:11
cdentso the question still stands: what's wrong with strings?14:11
jaypipescdent: yeah, we could also do a "hey, check if the $TRAIT_NAME is in os-traits. If it isn't, return 404. If it is, check if it's in the DB and if not, add it. but that would be a little less efficient, yes?14:11
jaypipesso maybe this is a perf thing after all :)14:11
cdentif we are worried about efficiency on a list of strings that is <10,000 entries, aren't we...confused?14:12
*** zz_dimtruck is now known as dimtruck14:13
cdent(I'm not exactly opposed to the change, I just want to be clear on the reasons)14:13
*** salv-orlando has joined #openstack-meeting-alt14:14
*** haleyb has joined #openstack-meeting-alt14:15
edleafeWell, why don't we all review that change, and comment on the review?14:15
* cdent nods14:15
edleafeNext up:14:15
edleafeClaims in the Scheduler14:15
edleafe#link Claims in the scheduler series: https://review.openstack.org/#/c/460177/14:15
* jaypipes nods too14:15
edleafeSylvain is off today like a good French worker14:16
* cdent is a bad worker14:16
edleafeI'm concerned with the last one in that series14:16
edleafeMoving claims to the scheduler because of a previous premature optimization choice seems... bad14:17
*** cloudrancher has quit IRC14:17
edleafes/the scheduler/the conductor14:17
*** salv-orlando has quit IRC14:17
*** cloudrancher has joined #openstack-meeting-alt14:18
cdentI think perhaps at this point we're just going to have to go with the WIP aspect of all this14:18
edleafeYes, and keep providing direction14:18
cdenthowever, I'd prefer if we were WIPping in the general direction of the original plan, and then moving away from that if it proves incomplete14:19
jaypipesedleafe: k, will review that today.14:19
edleafeSo yeah, it is all still WIP, so let's make sure we actually *make progress*14:19
cdentprogress++14:19
mriedemkeep in mind,14:20
mriedemthere is also a push for a general long-term direction to make the scheduler a library,14:20
mriedemso we can drop another service you have to run14:20
mriedemthat's motivating some of this14:20
mriedemat this point,14:21
mriedemi've already forgotten all of the pros/cons of each approach really,14:21
mriedemand they weren't all documented in the spec14:21
edleafeHaving the scheduler as a library doesn't seem to impact this at all14:21
edleafeIn general, we always assumed that the thing making the choice from placement would then make the allocation14:22
mriedemi honestly don't even remember why we said conductor needs to do it last week14:23
edleafeMoving on... Nested Resource Providers14:23
edleafeNested Resource provider series still doesn't show any signs of life14:23
edleafe#link Nested RPs: https://review.openstack.org/#/c/415920/14:23
edleafejaypipes: status?14:23
jaypipesedleafe: I'd like to get the shared resources pike series done first, along with the get_inventory() patches.14:24
mriedemoh right the scheduler interface... ignore me14:24
jaypipesedleafe: then rebase and move forward with n-r-p14:24
mriedemjaypipes: that makes sense, since nrp needs to give it's inventory via get_inventory14:24
jaypipesright14:24
edleafejaypipes: link?14:24
jaypipessec14:24
jaypipes#link get_inventory: https://review.openstack.org/45778214:25
jaypipes#link shared-resources-pike: https://review.openstack.org/46079814:25
edleafecool, thx14:25
jaypipescurrently fixing up comments on https://review.openstack.org/460798 from you and cdent.14:25
edleafeWill look those over later14:25
edleafenext up: Ironic testing for custom Resource Classes14:26
edleafe# link Ironic custom RC tests https://review.openstack.org/#/c/443628/14:26
edleafeAnyone have anything to comment on that?14:26
jaypipesno, just need to review.14:26
edleafeok, then... Docs14:27
edleafe#link Placement API ref https://review.openstack.org/#/q/topic:cd/placement-api-ref14:27
jaypipesalso rpodolyaka just got married on Saturday, so he's out for a few :)14:27
edleafelooks like that series is making some progress14:27
edleafehow dare he!14:27
jaypipesand avolkov is also still on PTO14:27
edleafecdent: anything to add about docs?14:28
cdentI was looking this morning at what's required to do the actual publishing (not draft). shouldn't be too onerous14:28
cdentbut will require a special job because of the placement-within-nova-ness14:29
*** gcb has quit IRC14:29
*** gcb has joined #openstack-meeting-alt14:29
edleafefun14:29
mriedembecause the existing job assumes a file structure right?14:29
cdentmriedem: yes14:30
cdentit's a small difference14:30
*** ijw has quit IRC14:30
*** gcb has quit IRC14:31
edleafeOK, any other specs/reviews to discuss?14:31
*** gcb has joined #openstack-meeting-alt14:31
jaypipesedleafe: no specs, but I have an open item to discuss. :)14:32
edleafejaypipes: opens is coming up soon14:33
jaypipeskk14:33
edleafe#topic Bugs14:33
edleafe#link Placement bugs https://bugs.launchpad.net/nova/+bugs?field.tag=placement14:33
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:33
edleafeOne new bug, that I see cdent has already responded to14:33
cdentthere was a new one, I responded to it asking for n-cpu logs14:33
cdentjinx!14:33
edleafejinx14:33
cdentyay!14:33
edleafeanything else about that bug?14:33
edleafe...or any other bug?14:34
cdentit's probably  the <Directory> thing14:34
edleafelet's move on14:34
edleafe#topic Open discussion14:34
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:34
edleafejaypipes?14:34
jaypipesso, I have two talks on the placement API in Boston. I'm done with slides for one of them and 85% done with the other one. I was hoping I could get feedback from folks on them?14:35
jaypipesalready shared with mriedem and dansmith but I'd like to share with edleafe, cdent and others if that's ok?14:35
cdentyes please14:36
edleafeof course14:36
jaypipesok, thanks guys.14:36
jaypipesyou'll see a google docs share notice shortly.14:36
edleafejaypipes: use my gmail addy: edleafe@gmail.com14:36
jaypipeswill do, thx14:36
edleafemakes sharing gdocs easier14:36
jaypipesalso, word of warning: the slide template is the Mirantis Boston summit template. I don't control it or the fonts. :)14:37
edleafeexcuses, excuses...14:37
jaypipescdent: you have a gmail14:37
jaypipes?14:37
cdentchris.dent14:37
jaypipesk, thx14:38
jaypipesk, shared. thx in advance for the feedback.14:38
edleafeOK, looking forward to tearing up jay's slide decks14:38
jaypipesI'll share the second talk shortly.14:38
jaypipes:)14:38
jaypipesgo for it, edleafe!14:38
edleafeAnything else for open discussion?14:39
edleafewow, even the crickets are quiet this morning!14:39
jaypipesheh14:39
edleafe#endmeeting14:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:39
openstackMeeting ended Mon May  1 14:39:56 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-05-01-14.00.html14:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-05-01-14.00.txt14:40
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-05-01-14.00.log.html14:40
cdentthanks edleafe14:40
*** mriedem has left #openstack-meeting-alt14:41
*** cdent has left #openstack-meeting-alt14:41
*** mickeys has joined #openstack-meeting-alt14:45
*** mickeys has quit IRC14:46
*** fnaval has quit IRC14:46
*** markvoelker has joined #openstack-meeting-alt14:54
*** esikachev has quit IRC14:56
*** chyka has joined #openstack-meeting-alt14:56
*** salv-orlando has joined #openstack-meeting-alt14:57
*** tonytan4ever has quit IRC14:59
*** tonytan4ever has joined #openstack-meeting-alt14:59
*** fnaval has joined #openstack-meeting-alt15:00
*** EricGonczer_ has quit IRC15:10
*** cloudrancher has quit IRC15:11
*** cloudrancher has joined #openstack-meeting-alt15:12
*** links has joined #openstack-meeting-alt15:13
*** links has quit IRC15:17
*** MarkBaker has joined #openstack-meeting-alt15:20
*** EricGonczer_ has joined #openstack-meeting-alt15:21
*** tonytan_brb has joined #openstack-meeting-alt15:21
*** tonytan4ever has quit IRC15:23
*** yangyapepeng has joined #openstack-meeting-alt15:28
*** mickeys has joined #openstack-meeting-alt15:31
*** yangyapepeng has quit IRC15:32
*** mickeys has quit IRC15:32
*** jaugustine has joined #openstack-meeting-alt15:35
*** jaugustine has quit IRC15:36
*** cloudrancher has quit IRC15:40
*** cloudrancher has joined #openstack-meeting-alt15:41
*** cloudrancher has quit IRC15:41
*** beslemon has joined #openstack-meeting-alt15:47
*** cloudrancher has joined #openstack-meeting-alt15:48
*** salv-orl_ has joined #openstack-meeting-alt15:52
*** esikachev has joined #openstack-meeting-alt15:52
*** salv-orlando has quit IRC15:55
*** amotoki has quit IRC15:55
*** persia has joined #openstack-meeting-alt15:55
*** dklyle has quit IRC16:00
*** dklyle has joined #openstack-meeting-alt16:00
*** gyee has joined #openstack-meeting-alt16:00
*** Sukhdev has joined #openstack-meeting-alt16:00
*** neiljerram has joined #openstack-meeting-alt16:01
*** esikachev has quit IRC16:02
*** salv-orl_ has quit IRC16:05
*** Swami has joined #openstack-meeting-alt16:08
*** neiljerram has quit IRC16:13
*** neiljerram has joined #openstack-meeting-alt16:13
*** esikachev has joined #openstack-meeting-alt16:14
*** Sukhdev has quit IRC16:14
*** rossella_s has joined #openstack-meeting-alt16:17
*** esikachev has quit IRC16:20
*** dklyle is now known as david-lyle16:24
*** ijw has joined #openstack-meeting-alt16:26
*** tesseract has quit IRC16:29
*** openstack has joined #openstack-meeting-alt17:00
*** openstack has joined #openstack-meeting-alt17:10
*** openstack has joined #openstack-meeting-alt17:22
*** ChanServ sets mode: +o openstack17:22
*** baoli has quit IRC17:24
*** MarkBaker has joined #openstack-meeting-alt17:24
*** tonanhngo has joined #openstack-meeting-alt17:24
*** beslemon has quit IRC17:27
*** tonanhngo_ has joined #openstack-meeting-alt17:27
*** tonanhngo has quit IRC17:29
*** tonanhngo_ has quit IRC17:29
*** trinaths has joined #openstack-meeting-alt17:29
*** ijw has quit IRC17:30
*** tonanhngo has joined #openstack-meeting-alt17:32
*** dprince has quit IRC17:33
*** salv-orlando has joined #openstack-meeting-alt17:36
*** salv-orlando has quit IRC17:40
*** bzhao has joined #openstack-meeting-alt17:41
*** baoli has joined #openstack-meeting-alt17:43
*** hongbin has joined #openstack-meeting-alt17:45
*** s3wong has joined #openstack-meeting-alt17:48
*** dprince has joined #openstack-meeting-alt17:52
*** marst has joined #openstack-meeting-alt17:59
*** MeganR has joined #openstack-meeting-alt18:00
*** ansmith has quit IRC18:03
*** mariannelm has joined #openstack-meeting-alt18:04
*** apetrich has joined #openstack-meeting-alt18:07
*** pradk has quit IRC18:09
*** pradk has joined #openstack-meeting-alt18:10
*** pradk has quit IRC18:10
*** pradk has joined #openstack-meeting-alt18:17
*** ansmith has joined #openstack-meeting-alt18:19
*** felipemonteiro has joined #openstack-meeting-alt18:26
*** MarkBaker has quit IRC18:26
*** ccamacho has quit IRC18:29
*** ansmith has quit IRC18:35
*** salv-orlando has joined #openstack-meeting-alt18:37
*** ijw has joined #openstack-meeting-alt18:37
*** diablo_rojo has quit IRC18:39
*** salv-orlando has quit IRC18:41
*** tonytan4ever has joined #openstack-meeting-alt18:42
*** trinaths has left #openstack-meeting-alt18:44
*** JudeC has joined #openstack-meeting-alt18:45
*** ccamacho has joined #openstack-meeting-alt18:48
*** ansmith has joined #openstack-meeting-alt18:49
*** matrohon has joined #openstack-meeting-alt18:52
*** diablo_rojo has joined #openstack-meeting-alt18:53
*** matrohon has quit IRC18:55
*** slaweq has quit IRC18:57
*** ansmith has quit IRC18:59
*** ijw has quit IRC19:01
*** kfarr has joined #openstack-meeting-alt19:02
*** dustins_ has joined #openstack-meeting-alt19:11
*** dustins has quit IRC19:12
*** diazjf has joined #openstack-meeting-alt19:12
*** gouthamr has joined #openstack-meeting-alt19:13
*** ansmith has joined #openstack-meeting-alt19:14
*** mickeys has joined #openstack-meeting-alt19:15
*** david-lyle is now known as dklyle19:17
*** dklyle is now known as david-lyle19:17
*** tonytan_brb has joined #openstack-meeting-alt19:18
*** gouthamr has quit IRC19:18
*** adisky_ has quit IRC19:19
*** tonytan4ever has quit IRC19:20
*** mickeys has quit IRC19:20
*** markstur has joined #openstack-meeting-alt19:22
*** yangyapepeng has joined #openstack-meeting-alt19:29
*** slaweq has joined #openstack-meeting-alt19:32
*** yangyapepeng has quit IRC19:35
*** ansmith has quit IRC19:36
*** gouthamr has joined #openstack-meeting-alt19:37
*** vds has quit IRC19:38
*** vds has joined #openstack-meeting-alt19:38
*** gouthamr has quit IRC19:42
*** esikachev has quit IRC19:46
*** ijw has joined #openstack-meeting-alt19:49
*** ijw has quit IRC19:49
*** ijw has joined #openstack-meeting-alt19:49
*** ansmith has joined #openstack-meeting-alt19:49
*** ijw has quit IRC19:50
*** esikachev has joined #openstack-meeting-alt19:51
*** gcb has quit IRC19:53
*** caboucha has joined #openstack-meeting-alt19:54
*** gcb has joined #openstack-meeting-alt19:55
*** kfarr has quit IRC19:56
*** kfarr has joined #openstack-meeting-alt19:57
*** esikachev has quit IRC19:58
*** annegentle has joined #openstack-meeting-alt19:59
dave-mccowan#startmeeting barbican20:00
openstackMeeting started Mon May  1 20:00:01 2017 UTC and is due to finish in 60 minutes.  The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: barbican)"20:00
openstackThe meeting name has been set to 'barbican'20:00
dave-mccowan#topic roll call20:00
*** openstack changes topic to "roll call (Meeting topic: barbican)"20:00
*** JudeC has quit IRC20:00
diazjfo/20:00
dave-mccowanhi diazjf20:01
diazjfhey dave-mccowan20:01
kfarr\o/20:02
*** alee has joined #openstack-meeting-alt20:02
aleeo/20:02
dave-mccowanhi alee kfarr!20:02
aleeyo20:02
dave-mccowanthe agenda is in the usual spot https://wiki.openstack.org/wiki/Meetings/Barbican20:03
dave-mccowan#topic pike status20:03
*** openstack changes topic to "pike status (Meeting topic: barbican)"20:03
dave-mccowan17 weeks to go :-)20:03
dave-mccowanhttps://etherpad.openstack.org/p/barbican-tracker-pike20:03
dave-mccowanfor the py35 community goal, barbican is looking good now.  we could expand it to include barbican client, tempest, and castellan.20:04
dave-mccowanthe goal is to get any functional tests working in both p27 and py3520:04
dave-mccowandiazjf what's the latest with deprecation?20:05
diazjfStill need some reviews20:05
diazjfhttps://review.openstack.org/#/c/459135/20:05
diazjfwill rebase it tonight20:05
dave-mccowanalee kfarr any pike feature updates?20:06
kfarrNope, not for now!20:06
aleedave-mccowan, nope - though I may have a little time this week20:07
dave-mccowan#topic summit prep20:07
*** openstack changes topic to "summit prep (Meeting topic: barbican)"20:07
dave-mccowanhttps://etherpad.openstack.org/p/barbican-pike-summit20:07
dave-mccowanwe already have a pretty full schedule, would anyone be interested in reserving a "hacking room" for a work session?20:08
aleedave-mccowan, I think its going to be a pretty full schedule20:09
kfarrI think my schedule will be pretty full the whole time20:09
diazjfdave-mccowan, I was able to add myself as a speaker for the managing contributions presentation, will have slides complete by Thursday.20:09
diazjfkfarr, will review your changes to the workshop application and add some20:09
diazjfchanges as well as review the presentation. If I am unable to meet tomorrow20:09
diazjfI will email y'all with what I have completed.20:09
redroboto/20:09
dave-mccowani agree... unless we had a specific topic that would benefit from a face-to-face, we shouldn't add another session.20:09
dave-mccowanredrobot!  \o/20:10
aleeredrobot, diazjf , dave-mccowan , kfarr - we still planning on meeting tomorrow?20:10
kfarrI was planning on it!20:10
dave-mccowanalee +1  11am EDT20:10
aleewe really should have at least one last meeting to iron out all the things needed20:10
aleegood20:10
redrobotYes, I'm officially FUNemployed, so I have nothing but time to work on prezos and workshop and stuff :D20:10
*** MarkBaker has joined #openstack-meeting-alt20:11
aleeredrobot, no margarita during the meeting please ..20:11
aleebefore and after maybe ..20:11
diazjfalee, I'll be up tonight getting a few things ready. Will email you whats done if I cannot attend the meeting20:11
*** funzo_ has quit IRC20:11
kfarrredrobot :(20:12
redrobotalee lol20:12
diazjfredrobot, make a startup!20:12
aleeok - I think we're in pretty good shape - it would be nice to wrap it all all up over the couple of days and do a final test20:12
*** gcb has quit IRC20:13
*** gcb has joined #openstack-meeting-alt20:14
dave-mccowani'm wrapping up the "Project Update" slides. The foundation sent a template in PPT format, instead of google.   I'll upload them for review/comments later tonight.20:14
dave-mccowan#topic review requests20:15
*** openstack changes topic to "review requests (Meeting topic: barbican)"20:15
dave-mccowanJeremy has had "Refactor barbicanclient" outstanding for a while now.  https://review.openstack.org/40360420:16
dave-mccowanany thoughts on this?20:16
diazjfhttps://review.openstack.org/#/c/459135/20:16
diazjfThe deprecation of Certificate Orders20:17
diazjfUntil when do I have to remove these items. At worst case, I will remove certificates from the API and remove everything  else after. dave-mccowan how does that idea sound?20:18
dave-mccowanalso, please take a look at Nicholas's and Rohan's patches on migrating us to cryptography library.  hopefully we can get at least 3 core reviews on these, since crypto has to be right.20:19
dave-mccowandiazjf that makes sense to split up the removal like that.  i'm not sure we have a deadline... just as long as we don't have every feature at once right at the end. :-)20:19
diazjfdave-mccowan, cool! That will make reviewing way easier :)20:20
dave-mccowan#topic any other business20:21
*** openstack changes topic to "any other business (Meeting topic: barbican)"20:21
kfarrI have a question for the dogtag plugin folks: alee20:21
kfarrI think the dogtag unit tests are getting skipped in the gate20:21
kfarrSo I put up a test patch to add dogtag-pki to test-requirements: https://review.openstack.org/#/c/461237/20:22
kfarrAnd after I added that, it seemed like the tests are *now* running,  but barf on config errors20:22
kfarrI was wondering that was something that should be addressed20:23
aleekfarr, hmm .. I'll take a look at that this week20:23
aleekfarr, I know that there was a config issue , but I though oz had resolved it20:23
kfarrRight, that was for the functional tests though20:24
*** dsariel has quit IRC20:24
aleekfarr, oh - the unit tests ..20:24
kfarrright right20:24
aleekfarr, well its possible those might be skipped because to run those you have to have the dogtag python package installed20:25
*** dimtruck is now known as zz_dimtruck20:25
aleethere is a try: import pki  at the top of the file20:25
kfarralee, right, exactly, they were being skipped because the package wasn't there20:26
kfarrbut then, I don't think they were getting run in any gate anywhere20:26
kfarrbecause I thought the dogtag gate only ran the functional tests20:26
aleeat the time it was because the dogtag client was not pip installable -- but thats no longer true20:26
aleeso yes, this is something that should be changed20:27
aleeso it can be run20:27
aleekfarr, I'll look into that this week20:27
aleekfarr, I suspect there may be things I need to fix :/20:27
kfarralee ok!20:27
dave-mccowanalee's week is filling up. :-)20:27
dave-mccowanshould we extend the timeout for dogtag functional tests.  they look like they almost finish now, but not quite.20:28
kfarryeah in the patch I linked above, it seemed like things were not very happy after I added the dogtag dependency20:28
aleedave-mccowan, and I'm not done with meetings today yet20:28
aleedave-mccowan, yeah - I'll look into that -- they finish once but not twice iirc20:29
dave-mccowanalee i changed it, so we only run once now.  (at least for the regular functional tests now)20:29
aleedave-mccowan, ok -- so we should be almost three -- I need to see what takes so long to run20:29
alee( I suspect its the package installs)20:30
*** esikachev has joined #openstack-meeting-alt20:30
aleeand I had a relatively light week this week before now ..20:30
dave-mccowanwe're very close to all passing gate jobs now. :-)20:31
dave-mccowanlast two things....20:31
dave-mccowanCongratulations to Jeremy Liu, new Barbican core reviewer20:31
kfarr\o/ hooray!20:31
diazjfCongrats!!!!20:31
kfarrI already saw him giving out +2s20:31
dave-mccowanyou can still add your +1 to the mail list if you haven't already20:31
dave-mccowanand no meeting next Monday due to summit20:32
kfarrdave-mccowan also I wanted to ask re: the gate timeouts20:32
*** rossella_s has quit IRC20:32
aleejust out of curiosity -- who will be at summit?20:32
*** caboucha has quit IRC20:32
kfarrI think the gates are launching a full devstack, and we might be able to cut down on time if we just do keystone and barbican20:33
kfarralee me !20:33
*** caboucha has joined #openstack-meeting-alt20:33
aleebesides me, dave-mccowan , diazjf , kfarr , redrobot20:33
aleekfarr, yeah - that would hep everywhere!20:33
kfarrdane-fichter from apl20:33
dave-mccowanthat's all i have for today then.  talk to you all tomoroww!20:35
dave-mccowan#endmeeting20:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:35
openstackMeeting ended Mon May  1 20:35:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-05-01-20.00.html20:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-05-01-20.00.txt20:35
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-05-01-20.00.log.html20:35
*** Shrews has joined #openstack-meeting-alt20:36
*** diazjf has quit IRC20:38
*** kfarr has quit IRC20:38
*** dprince has quit IRC20:44
*** zz_dimtruck is now known as dimtruck20:45
*** ijw has joined #openstack-meeting-alt20:50
*** diazjf has joined #openstack-meeting-alt20:50
*** annegentle has quit IRC20:52
*** iyamahat has joined #openstack-meeting-alt20:54
*** leong has joined #openstack-meeting-alt20:54
*** ijw has quit IRC20:55
*** caboucha has quit IRC20:55
*** hichihara has joined #openstack-meeting-alt20:55
*** JudeC has joined #openstack-meeting-alt20:58
*** ccamacho has quit IRC20:58
*** Sukhdev has joined #openstack-meeting-alt20:59
*** ansmith has quit IRC21:00
*** JudeC has quit IRC21:00
*** shamail has joined #openstack-meeting-alt21:00
leong#startmeeting product_working_group21:00
openstackMeeting started Mon May  1 21:00:40 2017 UTC and is due to finish in 60 minutes.  The chair is leong. 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: product_working_group)"21:00
openstackThe meeting name has been set to 'product_working_group'21:00
leong#chair shamail21:00
openstackCurrent chairs: leong shamail21:00
leong#topic rollcall21:01
*** openstack changes topic to "rollcall (Meeting topic: product_working_group)"21:01
*** heidijoy has joined #openstack-meeting-alt21:01
shamailHi! I'm going to be mostly quiet since in transit but Siri can speak for me from time to time21:01
*** rockyg has joined #openstack-meeting-alt21:01
leonghello ..anyone here for PWG meeting?21:01
leonghi Siri :-)21:01
heidijoyo/21:01
MeganRo/21:01
leonghello heidijoy21:01
rockygo/ brb21:01
shamaillol21:01
leonghello meganr, rockgy21:01
leonglet's wait for 2 minutes for other folks to join in...21:02
shamailOk21:02
*** GeraldK has joined #openstack-meeting-alt21:02
leong#link Agenda https://wiki.openstack.org/wiki/Meetings/product-team21:02
* leong waiting 2 mins for other folks to join in... 21:03
leongtoday agenda can be found in the above link...21:03
AndyUHi All o/21:03
leonghi andyu21:04
leonglooks like we have the quorum to kick start...21:04
AndyUHi Leong21:04
GeraldKo/21:04
leong#link Agenda https://wiki.openstack.org/wiki/Meetings/product-team21:04
*** ijw has joined #openstack-meeting-alt21:04
leonglet's get going..21:05
leong#topic Boston Summit/Forum planning review21:05
*** openstack changes topic to "Boston Summit/Forum planning review (Meeting topic: product_working_group)"21:05
leongi want to make sure that the team is ready for summit/forum21:05
*** slaweq has quit IRC21:05
leonganyone still need help?21:06
leongI have email the UC/operators/dev maillist about the pre-forum preparation, which includes the etherpad template and ##hashtag21:06
*** markvoelker has quit IRC21:06
*** sdague has quit IRC21:06
AndyUI have something... who's responsible for building this page? us?21:06
shamailI'm good, thanks for asking.21:07
AndyU#link  https://wiki.openstack.org/wiki/Forum/Boston201721:07
leongandyu: which page?21:07
leongi assume each session's moderator is asked to add the link21:07
*** ijw has quit IRC21:07
rockygAndyU, yup.  Remove the directions on the etherpad and put in your session's information/questions/whetever, then let the community also add stuff21:07
AndyUThere's A LOT missing21:07
rockygWe're all procrastinators21:08
shamailYes, each moderator is supposed to add the link21:08
*** Sukhdev_ has joined #openstack-meeting-alt21:08
leongwe probably can remind Forum Planning committee to send the email again as a reminder?21:08
AndyUThere are a lot of people who don't know what to do21:08
leongjust for information here in case you need the link..21:08
leong#link Moderator Template: https://etherpad.openstack.org/p/BOS-forum-moderator-template21:08
rockyggood idea.  Also, might want to include quick instructions for logging into the wiki and editing it21:08
leong#link Hashtag Definition: https://etherpad.openstack.org/p/BOS-forum-hashtag-definition21:09
leong#link Bostom Forum Session Etherpad: https://wiki.openstack.org/wiki/Forum/Boston201721:09
leongshamail: since you are in the forum planning committee, do you want to do that?21:09
leongshamail: --> remind Forum Planning committee to send the email again as a reminde21:09
AndyU+1 RockyG21:09
*** annegentle has joined #openstack-meeting-alt21:10
shamailSure, I can do that. I was going to remind people when I send a note to the moderators21:10
leong#action shamail, as a Forum Planning committee will send reminder email to moderators to include etherpad links at the wiki page.21:11
AndyUAs a moderator I don't recall getting anything telling me to add my session and etherpad link to that wiki page. But doesn't mean I didn't get one...21:11
leongandyu: there was an email sent out21:11
shamailTom sent an email to the mailing list, not individual moderators.21:11
AndyUDirect or via mail lists?21:12
rockygmail lists21:12
shamailMLs21:12
*** funzo has joined #openstack-meeting-alt21:12
*** rossella_s has joined #openstack-meeting-alt21:13
AndyUAh... yep. There are many "Users" jumping in now who are not plugged into those mail lists and other "community insider" type things21:13
*** mickeys has joined #openstack-meeting-alt21:13
leongi believe, majority of the moderators are aware....21:14
shamailleong: +121:14
*** pchadwick has joined #openstack-meeting-alt21:15
leongwith regards to the Forum and ##hashtag, i would like to ask all PWG members (especially those attending any session), to actively using (and advising people) the ##hashtag21:15
shamailWe wouldn't even after have their email addresses he didn't post to mailList since we didn't collect email addresses in the form21:16
leongthis is the first time PWG driving this effort at Boston Forum, so the ##hashtag method is pretty new21:16
shamailBlah :)21:16
AndyUI'm sure the majority are, but still some are not. maybe more that we realize. I think a direct email would be good. Covering at least: basic logistics, creating etherpads and posting to the wiki page, the hashtags, maybe some moderator tips21:16
shamailDidn't collect email addresses21:17
*** tonytan_brb has quit IRC21:17
AndyUShamail - Ahhh... lesson for next time  ;-)21:17
*** funzo has quit IRC21:17
leongin the normal practice in the past, usually the "moderator" will take the initiative..:-)21:17
*** MarkBaker has quit IRC21:18
shamail🙂21:18
*** rocky_g has joined #openstack-meeting-alt21:18
leongi think the action item to remind moderator should be fine.. let's move on next topic :-)21:18
leongjust want to emphasis this again :) --> with regards to the Forum and ##hashtag, i would like to ask all PWG members (especially those attending any session), to actively using (and advising people) the ##hashtag21:19
*** rockyg has quit IRC21:19
AndyUI added some sessions to the wiki/Forum/Boston2017 page fixed some formatting, and filled in some missing bits21:19
GeraldKleong: got it21:20
AndyULeong - understood21:20
leongalso want to make sure all aware the BoF and Working Session date/time21:20
heidijoyJust adding a note about the ##hashtag use on each etherpad will help people remember. We can all do that (add reminders in the etherpad during sessions)21:20
leong#link PWG BoF: https://www.openstack.org/summit/boston-2017/summit-schedule/events/17633/product-work-group-what-is-that21:20
leong#info PWG BoF: Wednesday, May 10, 5:20pm-6:00pm, Hynes Convention Center - Level 2 - MR 20221:21
leong#link PWG Working Session: https://www.openstack.org/summit/boston-2017/summit-schedule/events/17637/product-working-group-working-session21:21
leong#info PWG Working Session: Wednesday, May 10, 2:40pm-3:20pm, Hynes Convention Center - Level 2 - MR 20121:21
*** krtaylor has quit IRC21:21
leongheidijoy: yes.. i did included a note on the etherpad template21:21
AndyU#link PWG Development Proposal Process  https://www.openstack.org/summit/boston-2017/summit-schedule/events/18773/usersoperators-contributing-multi-project-requirements21:21
heidijoyI saw that, just thinking adding it "in the moment" will help21:22
leongheidijoy: +121:22
*** diazjf has left #openstack-meeting-alt21:22
AndyU#link PWG Development Proposal Process etherpad  https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements21:22
*** MarkBaker has joined #openstack-meeting-alt21:23
leong#info PWG Development Proposal Process: Thursday, May 11, 9:00am-9:40am, Hynes Convention Center - Plaza Level - MR 10421:23
leongandyu: thanks for the link :-)21:23
AndyUI just want to remind everyone of the dev proposal forum session21:23
leongand also the "Roadmap" session21:23
AndyUand encourage all to join and/or get into the etherpad.  I confess I haven't yet.  Thanks to Leong for getting it started.21:24
leong#link Community Generated Roadmap: https://www.openstack.org/summit/boston-2017/summit-schedule/events/17775/whats-going-on-in-openstack-learn-about-the-community-generated-roadmap21:24
leong#info Community Generated Roadmap: Tuesday, May 9, 2:50pm-3:30pm, Hynes Convention Center - Level 3 - MR 31121:24
*** ijw has joined #openstack-meeting-alt21:25
leong#link Evolving Roadmap (Forum): https://www.openstack.org/summit/boston-2017/summit-schedule/events/18744/evolving-the-community-generated-roadmap21:25
*** ijw has quit IRC21:25
leong#info Evolving Roadmap (Forum): Monday, May 8, 2:00pm-2:40pm, Hynes Convention Center - Plaza Level - MR 10421:25
AndyUheidijoy - looking forward to the roadmap and survey sessions21:25
heidijoy:-)21:25
*** ijw has joined #openstack-meeting-alt21:25
leongany PWG-driving session that i missed out?21:25
AndyUI'd like to help with those efforts next chance21:26
leongheidijoy: since you are here. do you want to update anything on the roadmap?21:27
heidijoyThe purpose of the "Evolving the Roadmap" session at the Forum is to talk about what's going well and what could we do differently wrt the roadmap collection, content and expression of it. The Roadmap presentation to the community goes through the data we collected this cycle and various visualizations of it.21:27
leong#topic Roadmap Update21:27
*** openstack changes topic to "Roadmap Update (Meeting topic: product_working_group)"21:27
heidijoyWe have 24 projects reporting (~6 more than ever before) including all projects with 50% or greater adoption (9 projects) and 8 projects with >25% adoption, and 7 whose adoption isn’t tracked on the User Survey yet.   This is by far the best (and most digestible) roadmap we’ve produced. It gives us deep info for the Pike marketing release well in advance. It also looks at:21:27
*** EricGonczer_ has quit IRC21:27
heidijoyIndividual projects - top 3 features/enhancements coming in Pike Top 10 features/enhancements for Pike (from all projects’ input) Individual projects- 80% of them shared 1 or more likely Queens features Development themes - we move from yes/no answers to “is resiliency a focus?” to answers with “major focus,” “minor focus,” “not a focus,” and “n/a or no info” to give a sharper sense of where deve21:27
heidijoyprevalent in each cycle, and a collapsed view of the next 3 cycles Which projects are focused on each development theme21:27
*** cloudrancher has quit IRC21:28
heidijoyThis is a key chart to pay attention to, and you can use it to cite when media/analysts are asking about NPS user dissatisfaction, in pointing out that the top 3 issues users identified are also getting the most attention from our developers over the coming three cycles: https://www.dropbox.com/s/ovjjy5v4zxn6wvq/Major%20Dev%20Forecast.png?dl=021:28
AndyUWe moved the LCOO wg meeting to be right before or after(?) the PWG meeting. It would be great if lots of pwg folks could join the lcoo meeting. It would be great to make introductions and have discussion about opportunities to collaborate21:28
*** cloudrancher has joined #openstack-meeting-alt21:29
AndyUoops... missed the topic change21:29
heidijoyCan I answer any questions on the roadmap?21:29
leong#andyu: LCOO working session is after PWG21:29
leongall: any question on roadmap?21:29
heidijoyI'm very happy with the strong response rate we got back. And the new visualizations should be interesting for the community.21:30
*** yangyapepeng has joined #openstack-meeting-alt21:30
leongheidijoy: that's awesome... :)21:30
shamail+121:30
leongshamail: do you have anything to add for the Roadmap Updat?21:31
GeraldKheidijoy: on the chart shared: shouldn't it show % instead of absolute numbers as the sum of major areas is not the same per release?21:31
heidijoyA question I've received is whether the chart I posted the link to above suggests that our projects are NOT interested in security.21:31
AndyUCan we get a sneak peak?21:31
*** ijw has quit IRC21:31
heidijoyI showed the absolute numbers to indicate how many projects responded to each.21:31
shamailNope,   Good from me21:31
heidijoyandyu I think we'll have a sneak peek in a couple of days. Working on assembling the individual project features content now.21:32
AndyUok, thx21:32
leongi think the chart shows that: how many projects is taking X as a major focus in release Y21:33
GeraldKheidijoy: we could show the total number of responses in the bottom, e.g. Pike (56 votes), Queens (... votes), ...21:33
heidijoySomething the roadmap doesn't do this round, which we discussed in our Milan meeting, was incorporating user requests to guide dev. We're just not asking for that/ showing that yet.21:33
leong+1 to 'incorporating user requests to guide dev' to improve future roadmap21:34
heidijoyThe total number of responses is 24 (total projects reporting). These aren't so much "votes" as they are the number of projects reporting that X theme is a "major focus" area for them in X cycle.21:34
*** krtaylor has joined #openstack-meeting-alt21:34
shamailI think we have to have the forum session 1st to get there21:34
*** ijw has joined #openstack-meeting-alt21:34
leongshamail: +121:34
heidijoyWe do have context building in the beginning of our presentation to help further explain the visualization GeraldK21:34
*** ijw has quit IRC21:35
heidijoyshamail +121:35
*** yangyapepeng has quit IRC21:35
*** ijw has joined #openstack-meeting-alt21:35
leongare we all good on the Roadmap topic?21:35
pchadwick@heidijoy - In the last roadmap session, we talked about what was in the current release as well as futures is that the plan this time?21:35
heidijoyI'm done with my update21:35
* pchadwick comes late to the party.21:36
heidijoyYes, we're going to show Pike, Queens and Rocky in this presentation21:36
leongi would encourage all to attend the "evolving roadmap" forum session if you are interested to help with Roadmap :)21:36
pchadwickI meant Ocata ;)21:36
AndyUOur "Rocky"?  :)21:36
*** baoli has quit IRC21:37
*** hichihara has quit IRC21:37
rocky_gHi, guys!.  Nope.  The R release got named Rocky21:37
* leong Rockyg will be famous in two more releases... 21:37
pchadwickIn Barcelona, we listed what the key features were in Newton as well as futures in Ocata and Pike21:37
rocky_gThere might have been a few votes because people knew me, but....21:37
AndyU@RockyG - congrats... quite an honor  ;)21:37
*** flaper87 has quit IRC21:38
rocky_gThanks!  Let's make this a Quality in operations focused release!21:38
heidijoyIn this roadmap cycle we asked projects about PQR not OPQ since Ocata has already been released.21:38
AndyUCan't wait for the Shamail release21:38
heidijoyAndyU +1,000,00021:38
pchadwickDarn, I missed my chance.21:38
leongi will try to challenge S release to "sun".. my last name.. lol21:39
*** salv-orlando has joined #openstack-meeting-alt21:39
AndyUhaha21:39
leongok.. let's get back to business...21:39
*** neiljerram has quit IRC21:39
pchadwick@heidijoy - OK21:39
shamailI think with the New release cadence it doesn't make sense to include a release that came out two months prior. The new road map shows what is in flight and what's coming21:40
leongcool21:40
shamailLol AndyU21:40
*** jcoufal has quit IRC21:40
leongshamail: +1 roadmap shows in progress and future21:40
pchadwick@shamail - yes, I just figured that out.21:40
leongnext topic ...21:41
leong#topic Post-forum Report21:41
*** openstack changes topic to "Post-forum Report (Meeting topic: product_working_group)"21:41
*** esikachev has quit IRC21:41
*** neiljerram has joined #openstack-meeting-alt21:41
leongshall we discuss what sort of data we would like to collect from Forum etherpad (by using the ##hashtag)21:41
*** krtaylor has quit IRC21:42
leongbtw, thanks AndyU for a quick tip that allow me to "export" etherpad into text format in a very "super easy" way...21:42
AndyUHow about we discuss what our role/objectives are for all that forum data21:43
*** MarkBaker has quit IRC21:43
leongandyu: +121:43
leonganyone any suggestion?21:43
*** mariannelm has quit IRC21:44
*** salv-orlando has quit IRC21:44
GeraldKfind out about new user stories or user story priorities21:44
AndyUFor ex, look for important items that do not appear to have an "owner" and seek to get them one?  Look for themes that would have broad impact and produce Development Proposals / solicit for owners of a Dev Proposal?21:45
shamailProvide a consolidated summary of the events using the data for those who weren't able to attend or join all session21:45
rocky_gget dev commitments for specs for high priority gaps -- if we can.  Even one would be a start on learning how to make it happen21:45
AndyUWe could make sure info tagged for a wg or a project is shared with them21:46
leongsummarize tangible action items and priority that help dev to build features/solve problems for operators21:46
shamailrocky_g: +121:46
AndyUConsolidated Summary +121:46
rocky_gshamail, if you can attend/join all sessions, I will worship you as a modern day god21:46
shamailLol21:46
leongandyu: +1  info tagged for a wg or a project is shared with them21:47
AndyU+1 identifying priority gaps for follow-up21:47
AndyUHmmm... could we align the forum results to Roadmap and/or user Survey contents, themes, etc?21:49
AndyUIt feels like Forum, Survey, Roadmap should all flow together21:50
leongthe forum results would probably help project teams to align with user needs, which eventually will drive the roadmap items..21:50
heidijoyleong + 121:51
*** cloudrancher has quit IRC21:51
AndyUright. they all play a role in the same overall objective of injecting user needs/priorities21:51
leongok.. let me summarize a few key points based on the above inputs21:51
*** cloudrancher has joined #openstack-meeting-alt21:52
leong#info Post-Forum Report: Consolidated Summary21:52
leong#info Post-Forum Report: info tagged for a wg or a project is shared with respective team21:52
shamailLet's make sure we don't bite off more than we can chew because this is the first time we will be doing this. Showing value going to be important21:52
*** jamielennox has joined #openstack-meeting-alt21:52
leong#info Post-Forum Report: Prioritize features that align with user needs21:53
leongi think these 3 points is more than enough for us ...21:53
leongsecond item should be easy to generate using the small python program that i have21:54
shamail+121:54
AndyUpriority gaps in need of ownership (at risk of not getting any follow-up)21:54
leongthird item might need some analysis21:54
leonglet's keep that as our Report objectives first, if anyone has suggestion, we can discuss over email21:55
leonglast 5 minutess.. open21:55
leong#topic Open21:55
*** openstack changes topic to "Open (Meeting topic: product_working_group)"21:55
leongI have one quick open item which brought up by Anni lai21:55
leongdo we want to present a report to Board Meeting at Boston?21:55
AndyUI think doing a retrospective on the Forum would be beneficial as well21:55
*** esikachev has joined #openstack-meeting-alt21:56
rocky_gYeah, AndyU cand do that before the summit/forum, though.21:56
leongto update the Board and get engagement from TC/UC/Board for Development Proposal21:57
AndyUright. I meant the retrospective comment for part of the post-forum analysis21:57
*** markvoelker has joined #openstack-meeting-alt21:57
rocky_gI'd like to figure out a proposal based on what we've been discussing of how we work with TC to get developers involved once the priority gaps have been identified.  Like asking them to drive some cross project meetings or something21:57
rocky_gWe could use their help as facilitators to get the gap(s) turned into specs.21:58
leongrock_g: i assume that would be in the "gap analysis" phase?21:58
leonggetting TC to faciliate "gap analysis"?21:58
rocky_gAgain, one would take us a long way in the learning process.  If we can get a commitment for them to stick with trying to get one turned into a spec, we all win21:58
*** Swami has quit IRC21:59
*** JudeC has joined #openstack-meeting-alt21:59
AndyUDo we have any alignment with this? https://www.openstack.org/summit/boston-2017/summit-schedule/events/17585/the-openstack-technical-committee-vision-for-2019-updates-stories-and-q-and-a21:59
rocky_gleong, no, not the gap analysis, but once we know the gap, getting them to create a spec for the work needing to be done to fill the gap21:59
leonglet's push that the email discussion, then we will decide if we need an agenda item in the Board meeting21:59
shamailFYI: I asked for a session (and it's been accepted) for the Kubernetes SIG-PM group to meet and I proposed that the OpenStack PWG come to the session as well so we can discuss open-source Product Management (find out what works for them, us, etc.). The session isn't on the schedule yet but will be on Monday at 5:30P, I'll send an email to the ML once it's posted.21:59
*** ganso has left #openstack-meeting-alt21:59
leongshamail: +121:59
pchadwickshamail: +122:00
*** dustins_ has quit IRC22:00
leongcool.. let's wrap up the meeting here22:00
*** esikachev has quit IRC22:00
leongsee u all at Boston (for those attending)22:00
leongand safe travel...22:00
pchadwickbye22:00
shamailCya22:00
leong#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Mon May  1 22:00:58 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
*** pchadwick has left #openstack-meeting-alt22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-05-01-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-05-01-21.00.txt22:01
*** shamail has quit IRC22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-05-01-21.00.log.html22:01
*** heidijoy has quit IRC22:01
GeraldKbye22:01
jeblairany zuul folks around?22:01
*** slaweq has joined #openstack-meeting-alt22:01
*** GeraldK has quit IRC22:01
* fungi checks22:02
fungier, yep!22:02
clarkbsort of22:02
*** rossella_s has quit IRC22:03
fungiit's like pre-summit week is an openstack holiday or something22:03
fungioh, though today _is_ a holiday in most parts of the world where i don't live, so maybe it's just that22:04
rocky_gLike?  Uh, week before and week after.  Crickets.22:04
pabelangero/22:04
jeblairi think mordred is traveling today, and Shrews is more productively engaged :)22:04
jeblairSpamapS: around?22:04
* fungi saw him push a zuulv3 change... radio silence broken22:04
*** jlk has joined #openstack-meeting-alt22:05
jlko/22:05
jeblairseems vaguely quorumish22:05
jeblair#startmeeting zuul22:05
openstackMeeting started Mon May  1 22:05:40 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:05
*** openstack changes topic to " (Meeting topic: zuul)"22:05
openstackThe meeting name has been set to 'zuul'22:05
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:05
jeblair#topic  Status updates: Zuul test enablement22:06
*** openstack changes topic to "Status updates: Zuul test enablement (Meeting topic: zuul)"22:06
jeblairSpamapS is on a roll here22:06
*** MeganR has quit IRC22:06
jeblairthere are still some more remaining if folks are looking for fun and educational tasks22:06
jeblairnot sure there's much else to add on this22:07
jeblair#topic Status updates: Zuul sample jobs22:07
*** openstack changes topic to "Status updates: Zuul sample jobs (Meeting topic: zuul)"22:07
jeblairpabelanger: you restarted zuulv3-dev, right?22:07
pabelangeryes, last week22:08
jeblairpabelanger: what's the status with the sample jobs; should we be writing or reviewing anything?22:08
pabelangerAlso started on our first stdlib: https://review.openstack.org/#/c/459066/ was going to ping some people this week to bikeshed on it, specifically how we handle variables22:09
*** slaweq has quit IRC22:09
jeblairoh cool, so we're ready to start reviewing that22:10
pabelangerwould like to engage bonnyCI folks see if they could use that if we merged it or not22:10
jeblairi think shortly afterwords, we need to start thinking about how to make that reusable22:10
pabelangerin what sense?22:10
jlkyeah I SpamapS and I would like to get other BonnyCI folks engaged on the standard lib front22:11
pabelanger459066 should be a simple one to tackle first22:11
pabelangerit has default users, and ports for zuul_stream22:11
jeblairwhether it should go in a new repo, or be installed with zuul as a special case.  the "playbooks/" directory within zuul is not necessarily the right place for it (it will contain playbooks for running and testing zuul, not necessarily things that should be in the stdlib)22:11
pabelangeragree22:12
jeblair(i don't think we need to block on that -- just indicating that it's destined for the stdlib vs something else is good enough for us to iterate on it for now)22:12
jeblairjlk: ++22:13
jeblairanything else folks should be aware of on this?22:13
*** funzo has joined #openstack-meeting-alt22:14
jeblair#info starting to organize "standard library" roles/playbooks in https://review.openstack.org/45906622:14
*** xyang1 has quit IRC22:15
jeblair#topic Status updates: Github22:15
*** openstack changes topic to "Status updates: Github (Meeting topic: zuul)"22:15
jlkoh hey, that's me.22:15
jeblairjlk, mordred, and I had a significant conversation about what the config syntax should look like last week22:16
jlkwe had an excellent chat on Friday about the patch set, and I got some direction to move in22:16
jeblair(that should be archived by eavesdrop.openstack.org for posterity)22:16
*** esikachev has joined #openstack-meeting-alt22:16
jlkI've made a lot of progress on that front, another pass of rebasing on top of the earlier changes22:16
jlkI should have the whole patch set ready to put up for review again later today if I'm lucky.22:17
jeblairneat!22:17
*** ijw has quit IRC22:17
jeblairi'll continue to try to review down the tip of teh stack (i've only gotten about 7 patches in so far), as well as loop back to the top as things are addressed22:17
*** ijw has joined #openstack-meeting-alt22:17
jlkand jamielennox is going to have an implementation of zv3 with our github patches running hooked up to github, so we can do some extra validation.22:17
*** haleyb has quit IRC22:18
*** jkilpatr has quit IRC22:18
jeblairjlk, jamielennox: great!  (caveat: there's still some known incorrect behavior and missing security bits, but i think you know that)22:18
jlkyup!22:19
*** funzo has quit IRC22:19
jeblairmordred has been chiming in on reviews too; if anyone else wants to review, please feel free to do so, and let me know if you want me to make sure we wait for your reviews before merging22:19
jeblair#info github series is being rebased and revised to address review comments22:20
jeblairanything else on this?22:21
*** leong has left #openstack-meeting-alt22:21
*** esikachev has quit IRC22:21
jeblair#topic Status updates: Bubblewrap22:21
*** openstack changes topic to "Status updates: Bubblewrap (Meeting topic: zuul)"22:21
*** ijw has quit IRC22:22
jeblairSpamapS, pabelanger: can one of you fill us in on the latest here?22:22
fungii heard we're no longer concerned about whether the ubuntu ppa system is (still) working22:23
*** ijw has joined #openstack-meeting-alt22:23
pabelangermordred suggested we might use the PPA now that vhd-utils built over the weekend22:23
jeblairfungi: yeah, apparently it's working now?  so ppas are an option?22:23
SpamapSI have nothing new to report22:23
pabelangerI am not sure if anybody is working on backporting that or not22:24
SpamapSif PPA's are in fact building, then I'd suggest we just use a PPA22:24
fungiso maybe uploading the source package from stretch or yakkety to rebuild would be an option22:24
SpamapSuntil xenial-backports gets bubblewrap22:24
SpamapSwhich I do expect to happen at some point22:24
pabelangerI can see about doing an upload, to my own PPA first22:24
jeblairokay, ppa until xenial-backports sounds like it's an option22:24
fungii have a feeling pushing that source package into a ppa would "just work[tm]" since the claimed deps are already met on xenial22:25
SpamapSThere's a script in ubuntu-dev-scripts that will do it for you even22:25
pabelangerSo, has anybody seen this: https://launchpad.net/~ansible/+archive/ubuntu/bubblewrap22:25
SpamapSbackportpackage -d xenial -u ppa:foo bubblewrap <-- that's all you need22:25
jeblaircan we use the same ppa we use for vhd-util?22:25
pabelangerwhich is xenial package22:25
pabelangermaybe we can just work with ansible on it22:25
jeblairi have not seen that.22:26
SpamapSpabelanger: that's also under Ansible's control. So it may not match what infra wants.22:26
pabelangerppa:ansible/bubblewrap22:26
SpamapSbut it's likely exactly the same thing22:26
pabelangerright, but we could audit and copy into our PPA22:26
jeblairbtw, are we positive that's really ansible?22:26
fungii think we should create a new ppa under the same team22:27
fungilink at https://launchpad.net/~openstack-ci-core22:27
jeblairfungi: that seems safest and most stable22:27
fungithe existing ppa is "VHD Util" which is probably surprising if it contains a package set for bubblewrap22:27
pabelangerya, we can check GPG keys first22:27
SpamapSliterally make a PPA and run that backportpackage command.. that's all you need to do22:28
fungi#link https://launchpad.net/~openstack-ci-core create a new ppa here, adjacent to "VHD Util"22:28
fungisolution so simple, it's probably time to stop debating it until we find out there's a problem ;)22:28
SpamapSCan verify that the source package in the ansible PPA is a no-change backport22:28
jeblairshould we call the ppa 'zuul-deps' or 'bublewrap'?22:28
SpamapSwould be safe to just copy that into a PPA and we don't have to wait for build22:29
*** marst has quit IRC22:29
fungicopying their ppa to one under our control seems fine to me. relying on their ppa indefinitely does not22:29
jeblairSpamapS: by "Can verify" do you mean that you have verified or that one is able to verify?22:30
fungibut we have the source package they used and assume the canonical build infrastructure is reliable, so can trust what's currently there at least22:30
SpamapShttp://paste.openstack.org/show/608551/22:30
SpamapSjeblair: have verified22:30
jeblaircool22:31
fungialso neat that they seem to already be using or otherwise want it22:31
fungi(assuming tat's really ansible)22:31
jeblair#action pabelanger create new ppa under openstack-ci-core and add bubblewrap to it; copy existing source package from ansible bubblewrap ppa.22:31
jeblairdoes that look correct ^?22:31
fungisure22:32
SpamapSwe don't, however, have any proof that launchpad.net/~ansible _is_ ansible. That GPG key is single-purpose for debs22:32
SpamapSbut again, safe to copy the debs for speed22:32
jeblairyep.  out of curiosity, i'll ask 'em next time i see 'em.  :)22:32
SpamapSjeblair: indeed, tell them to sign their keys ;)22:32
fungi(and maybe also add contact info to that lp profile)22:33
*** iyamahat has quit IRC22:33
pabelangerI am guess it is driven by jenkins, based on SSH keys added to https://launchpad.net/~ansible22:33
fungiyup22:33
fungithat was my guess as well22:33
jeblairhopefully we can move this along quickly now -- we have patches we should be able to test as soon as the ppa is available22:33
SpamapSfungi: the GPG keys list security@ansible.com as their email, that counts.22:33
SpamapSjeblair: indeed!22:33
SpamapSI started poking at seccomp22:34
jeblaircool, this has been productive, thanks :)22:34
pabelangerI'm happy to give backportpackage a go too, if I can find it for fedora :)22:34
jeblairSpamapS: what does that entail?22:34
fungiSpamapS: yeah, i suppose openpgp uids are a relevant contact ;)22:34
SpamapSjeblair: stracing ansible-playbook and then locking down to just those syscalls22:34
SpamapSthere's a tool to generate a binary file to feed into bwrap22:34
fungithough one of them lists security@, the other jenkins@22:35
fungipabelanger: you could debootstrap an ubuntu chroot... ;)22:35
SpamapSauditd will also log seccomp for you if you ask it to22:35
jeblairSpamapS: neat... think it'll be workable/useful?22:35
*** jkilpatr has joined #openstack-meeting-alt22:36
*** cknight has quit IRC22:36
jeblair(there's probably some number of file and network operations we'll have to allow in order to have useful untrusted playbooks)22:36
pabelangerfungi: it looks to be python. Going to clone source22:36
SpamapSjeblair: yes I do, it's pretty straight forward whitelisting of behavior.22:37
jeblairyay!22:37
jeblairanything else on this topic then?22:37
SpamapS(you can blacklist too, but that's for small minds, and we are HUGE minds.. YUGE)22:37
jeblairoy22:38
jeblairthat's my cue22:38
jeblair#topic nodepool image testing spec (pabelanger)22:38
*** openstack changes topic to "nodepool image testing spec (pabelanger) (Meeting topic: zuul)"22:38
pabelangerso, I wanted to talk a little about if possible22:39
*** marst has joined #openstack-meeting-alt22:39
pabelangerbasically, over the last 3 weeks we worked in openstack-infra to remove puppet from our images22:39
pabelangerit became obviously pretty fast, it was a little painful to ensure our image didn't break as we started deleting puppet things22:40
*** salv-orlando has joined #openstack-meeting-alt22:40
pabelangerI know this was a topic in the past, but was curious if we could maybe spend some time talking about this22:40
pabelangeras a operator, it is hard to stage images in nodepool before they go live22:41
*** tonanhngo has quit IRC22:41
pabelangerand not sure how to make this easier moving forward22:41
jeblair#link nodepool image testing spec https://review.openstack.org/#/c/139598/22:41
jeblairpabelanger: well, the *best* outcome would be gate testing of images, right?22:41
jeblairthen we can stop problems before they start22:42
*** tonanhngo has joined #openstack-meeting-alt22:42
pabelangerRight, that is something I am trying to do now. Hence my recent changes to project-config22:42
*** JudeC has quit IRC22:42
pabelangerbut, it would mean running nodepool dsvm against project-config, maybe?22:42
clarkband tripleo and puppet openstack and osa and ....22:43
jeblairpabelanger: yep; probably with file restrictions since it's so heavyweight.  or in experimental pipeline.22:43
pabelangerhowever, thinking of general zuul users, I am not sure if users will do that or expect some sort of audit in nodepool / zuul22:43
jeblairclarkb: i don't think we use tripleo to build images?22:43
jeblairpabelanger: i think many zuul users don't have nearly so complex images.  to be fair, we're trying to have simpler images too.22:44
clarkbjeblair: the problem isn't the build failing though its tripleo failing when it runs on the image22:44
SpamapSIf it's really really heavy weight, can also be done as a more stable-release paradigm.. let post-commit jobs test all the combos and tag good images when things stabilize.22:44
clarkbso just checking if dib works or not isn't going to get us much22:44
SpamapSs/post-commit/periodic/22:44
*** MarkBaker has joined #openstack-meeting-alt22:44
jeblairclarkb: that situation is pretty untenable from a post-image build testing situation as well.  i think an image-validity check has to be relatively low cost.22:45
clarkbjeblair: yup I agree22:45
*** salv-orlando has quit IRC22:45
*** tonanhngo_ has joined #openstack-meeting-alt22:45
clarkbproblem is I don't know that such a thing exists. We could start with something arbitrary like jenkins and zuul users exist and then tack on things as we go22:45
SpamapSv3's secrets thing comes in handy here..22:45
*** esikachev has joined #openstack-meeting-alt22:46
SpamapS"it uploads and boots"22:46
pabelangerI think most of this could be covered by a pre-task in zuulv3, ensure directories exist, proper user permissions, etc from DIB creation. But, is that something we'd want all jobs to run? or just 1 time after we upload / launch a image22:46
fungithough that eats into your quota unless you set aside a separate tenant22:46
jeblairpabelanger: how does a pre-task help?22:46
*** tonanhngo has quit IRC22:46
pabelangerjeblair: I might be thinking wrong, but a job will not fail is a pre-task does?22:47
clarkbpabelanger: or even make it part of the dib build itself? and inspect the chroot?22:47
jeblairpabelanger: right, it will run again.  but it will fail the second and third times as well.22:47
jeblairpabelanger: and then the job will fail.22:47
SpamapSfungi: can be a very small flavor at least.22:47
pabelangerclarkb: I'd love to use the ansible chroot connection to audit, is we want to do that22:47
fungisomething a little less error-prone than when we ran devstack smoke on new images before putting them into use ;)22:47
adam_gwe've been embedding some basic validation checks into an elements post-install.d phase, so we can fail the build and prevent nodepool from uploading and using a broken image22:48
pabelangerjeblair: k, I wasn't sure if we limited on pre-task failures22:48
jeblairpabelanger: well, what i'm saying is that by the time zuul runs the job, if it's failing because the image is broken, there's no way to fix that.22:48
jeblairadam_g: what kind of things do you check?22:48
clarkbpabelanger: I don't know that you'd need to specify the tool. Just have a run stage in dib for checking things then each element can publish its own arbitrary checkers22:48
fungiadam_g: yeah, self-checking elements seem like a great idea22:48
clarkbor just use post-install.d22:49
* clarkb catches up to adam_g22:49
adam_gjeblair: atm just some things that have broken in recent DIB releases (a functioning python, specifically).. that zuul-cloner at least loads and spits its usage, etc.22:49
jeblairadam_g: good ideas22:49
*** ansmith has joined #openstack-meeting-alt22:49
adam_ga proper validate-image.d or similar phase in DIB would be preferable22:50
*** tonanhngo_ has quit IRC22:50
adam_goh also, we then monitor nodepool image age and alert if we dont have an image newer than $foo, so we know when builds start failing22:50
*** esikachev has quit IRC22:50
SpamapSadam_g: very easy to add phases22:50
SpamapSand I think it's a good ide22:51
SpamapSa22:51
fungiwe also do test our dib elements in the nodepool integration job, so can easily reject changes which would cause images to fail such self-validation22:51
SpamapSmaybe have those checks inside the chroot but after everything else including cleanup22:51
clarkbfungi: I don't think we do a full build with our elements, its minimal22:52
pabelangerSo, if we want to do this pre commit, that is not a problem. I already have some thoughts / plans to help make project-config better. I mostly wanted to see if we want to add this functionality native into nodepool / zuul as an audit / testing stage22:53
jeblairclarkb: because of git clones?22:53
fungiclarkb: oh, well, i suppose we could require that at least those minimal elements pass their validation22:53
pabelangerthen have operator either manually promote images or auto promote if the audit passed22:53
jeblairpabelanger: i feel like with our limited developer bandwidth at the moment, the best bang for the buck is gate jobs and dib validation.  i think that nodepool image validation is workable and i'm not opposed to implemeting it (i think that spec was heading in a good direction), but from the openstack-infra operator perspective, i don't think it's critical to our workflow if we are able to do the other checks.22:53
fungiit does seem like something an industrious downstream consumer could contribute if they need it22:54
pabelangerfungi: yes, we can add nodepool-dsvm job to project-config, but full builds today are 1hr+22:54
pabelangerjeblair: okay, that works for now. I'll work on this from openstack-infra POV today22:54
clarkbjeblair: our builds take like an hour right now with hot cache22:54
clarkbnot sure how feasible a full build in integration job is as a rsult22:54
pabelangerif we drop cache-devstack / openstack-repos (what I am testing) it is about 20mins22:55
fungiagain, though, if this is because of iterating over all 1.7k (or however many we're up to now) git repos to see whether they need to be updated, that's likely to get much better if we can drop git caches from our im ages with zuul v322:55
jeblairclarkb: i'd say 1 hour is in the realm of feasible, certainly for an experimental pipeline job.22:55
clarkbjeblair: it will be longer on test nodes with a cold cache22:55
jeblairclarkb: test nodes have a warm cache :)22:56
pabelangersure, but today there is only 2 things that depend on openstack cached repos at build time, zuul-env and tempest-env22:56
*** chyka has quit IRC22:56
pabelangerwhich we could update to git clone from another source22:56
fungiwe should probably look into moving the tempest-env addition to job runtime22:56
*** chyka has joined #openstack-meeting-alt22:56
jeblairpabelanger: agreed, then the only issue becomes how important it is that we validate the cache on image builds (maybe it's not that important)22:57
fungicreating zuul-env at job runtime is more likely to be a catch-22 but maybe we make it stop requiring a local cache22:57
pabelangerjeblair: yes, so far, that hasn't been our issues22:57
pabelangerunless repo didn't mirror from gerrit to git.o.o properly22:58
jeblairpabelanger: yeah, i can get behind severing those deps and dropping the repo cache from the gate testing22:58
jeblairfungi: pabelanger's proposed change just clones master directly, which i think is reasonable.  it's functionally the same as what we're doing now.22:58
fungithat totally brings the runtime into a reasonable realm for check jobs, in my opinion22:58
jeblairfungi: yeah, we're into the territory where we can run it on a wider variety of changes22:59
clarkbbut if all we check is can it build we haven't done much to fix real problems?22:59
clarkbif something fails to build we continue to use old image happily22:59
fungiif the elements incorporate validation22:59
pabelangernext step would be post build auditing22:59
fungii think was the assumption22:59
clarkbfungi: if elements incorporate validation we can likely even defer that to build time too22:59
clarkbfor the same reason22:59
clarkb(though in check it will make review easier)23:00
jeblairor upload the image somewhere (as SpamapS suggested, or to a devstack, if we're really patient)23:00
jeblairwe're out of time23:00
fungiwell, if we defer validation to production build time (is that what you mean?) then we get to merge changes which break image builds23:00
jeblairthanks everyone!23:00
clarkbfungi: yes but don't impact production23:00
fungithanks jeblair!23:00
jeblair#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
openstackMeeting ended Mon May  1 23:00:44 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-05-01-22.05.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-05-01-22.05.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-05-01-22.05.log.html23:00
jeblaircontinue in #openstack-infra if needed23:00
*** dimtruck is now known as zz_dimtruck23:01
*** chyka has quit IRC23:03
*** dtrainor has quit IRC23:03
*** JudeC has joined #openstack-meeting-alt23:07
*** dtrainor has joined #openstack-meeting-alt23:08
*** fnaval has quit IRC23:09
*** felipemonteiro has quit IRC23:11
*** Sukhdev has quit IRC23:16
*** ijw has quit IRC23:19
*** ijw has joined #openstack-meeting-alt23:22
*** ijw has quit IRC23:23
*** ijw has joined #openstack-meeting-alt23:23
*** manjeets has quit IRC23:24
*** rocky_g has quit IRC23:28
*** yangyapepeng has joined #openstack-meeting-alt23:31
*** neiljerram has quit IRC23:31
*** yangyapepeng has quit IRC23:36
*** salv-orlando has joined #openstack-meeting-alt23:41
*** salv-orlando has quit IRC23:45
*** esikachev has joined #openstack-meeting-alt23:46
*** esikachev has quit IRC23:51
*** rfolco has joined #openstack-meeting-alt23:54
*** jamielennox is now known as jamielennox|away23:56
*** jamielennox|away is now known as jamielennox23:58
*** esikachev has joined #openstack-meeting-alt23:58
*** gcb has quit IRC23:59

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