Wednesday, 2017-06-07

*** markvoelker has quit IRC00:07
*** eanylin_ has quit IRC00:29
*** markvoelker has joined #openstack-meeting-501:03
*** mattmceuen has joined #openstack-meeting-501:51
*** eanylin_ has joined #openstack-meeting-502:11
*** marst has joined #openstack-meeting-502:27
*** gomarivera has joined #openstack-meeting-502:58
*** gomarivera has quit IRC03:03
*** ricolin has joined #openstack-meeting-503:08
*** marst has quit IRC03:49
*** zenirc369 has joined #openstack-meeting-507:01
*** rarcea has joined #openstack-meeting-507:14
*** derekh has joined #openstack-meeting-508:37
*** zenirc369 has quit IRC08:38
*** zenirc369 has joined #openstack-meeting-508:50
*** zenirc369 has quit IRC08:57
*** gomarivera has joined #openstack-meeting-508:59
*** gomarivera has quit IRC09:03
*** ralonsoh has joined #openstack-meeting-509:55
*** zenirc369 has joined #openstack-meeting-510:50
*** zenirc369 has quit IRC11:23
*** LanceHaig has joined #openstack-meeting-511:26
*** LanceHaig has joined #openstack-meeting-511:26
*** rarcea has quit IRC11:33
*** rarcea has joined #openstack-meeting-511:34
*** gmarton has joined #openstack-meeting-511:42
*** gmarton has quit IRC11:43
*** gaborm_ has joined #openstack-meeting-511:44
gaborm_help11:45
*** gaborm_ has quit IRC11:46
*** skazi is now known as skazi__11:58
*** skazi_ is now known as skazi11:58
*** skazi__ is now known as skazi_11:58
*** mattmceuen has quit IRC12:34
*** eanylin_ has quit IRC12:48
*** felipemonteiro has joined #openstack-meeting-513:15
*** felipemonteiro_ has joined #openstack-meeting-513:16
*** felipemonteiro has quit IRC13:20
*** eanylin has joined #openstack-meeting-513:23
*** srwilkers has joined #openstack-meeting-513:25
*** zhipeng_ has joined #openstack-meeting-513:47
*** srwilkers has quit IRC13:57
*** gomarivera has joined #openstack-meeting-513:59
*** zhipeng_ has quit IRC14:18
*** zhipeng_ has joined #openstack-meeting-514:18
*** srwilkers has joined #openstack-meeting-514:28
*** srwilkers has quit IRC14:35
*** marst has joined #openstack-meeting-514:57
*** ramishra has joined #openstack-meeting-514:59
*** mrwolf has joined #openstack-meeting-515:00
ricolin#startmeeting heat15:00
ricolin#topic roll call15:00
openstackMeeting started Wed Jun  7 15:00:23 2017 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: heat)"15:00
openstackThe meeting name has been set to 'heat'15:00
*** openstack changes topic to "roll call (Meeting topic: heat)"15:00
*** gaborm has joined #openstack-meeting-515:00
zanebhowdy15:00
gabormhello15:00
ramishrahi15:00
*** therve has joined #openstack-meeting-515:01
mrwolfhi all15:01
kazshHi team15:01
ricolino/15:01
therveHey15:01
*** strigazi has joined #openstack-meeting-515:01
gabormI am Gábor Márton from Nokia15:01
LanceHaigHi15:01
ricolingaborm, so glad you're here!15:01
strigazio/15:01
ricolin#topic adding items to agenda15:01
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:01
ricolin#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-06-07_1500_UTC.2915:01
gabormthanks rico, looking forward to discussing15:01
ricolingaborm, I already put it in agenda15:02
ricolinfeel free to add more in15:02
gabormthanks for putting it onto the agenda15:02
mrwolfconnecting to the adopt/abandon topic, I would like to discuss the state/future of externalId/external reference15:03
mrwolf(Peter Wolf, also from Nokia)15:03
ricolinmrwolf, sure15:03
zaneb+115:04
ricolin#topic weekly report15:04
*** openstack changes topic to "weekly report (Meeting topic: heat)"15:04
ricolinno big bug this week, uwsgi just got reverted:/15:04
*** ralonsoh_ has joined #openstack-meeting-515:04
ricolin#link https://review.openstack.org/#/c/471730/15:05
*** tiantian has joined #openstack-meeting-515:05
ricolin#topic pike-2 release15:06
ramishraI now have patch to fix that issue though https://review.openstack.org/#/c/471804/15:06
*** openstack changes topic to "pike-2 release (Meeting topic: heat)"15:06
zanebthere was a big bug this week, but ramishra squashed it pretty quick: https://review.openstack.org/#/c/470942/15:06
tiantianhi ;)15:06
ricolin#link https://review.openstack.org/#/c/470942/15:06
*** ralonsoh has quit IRC15:07
*** ralonsoh_ is now known as ralonsoh15:07
ricolinshould we wait for that fix before pike-2?15:07
ramishraricolin: nope15:08
ricolinI already send release patch for stable branch15:08
ricolin#link https://review.openstack.org/#/c/471760/15:08
*** gomarivera has quit IRC15:08
ricolinAlso plan to release heat, python-heatclient, heat-agents15:08
ricolinIf nothing to raise here, I will send release patch today15:09
zanebricolin: newton gate is in bad shape, with lots of patches queued up15:10
zanebhttps://review.openstack.org/#/q/status:open+project:openstack/heat+branch:stable/newton15:10
ricolinzaneb, we never actually fix that issue15:12
zanebyeah15:12
ramishralast 2 patches are green15:12
zanebhttps://review.openstack.org/#/c/466008/1 needs to merge before it will get better, but that is also blocked15:12
zanebI just rechecked it15:12
ricolinwill try to dive in that and hope we can pass that patch or find something to work with it15:15
*** felipemonteiro_ has quit IRC15:15
ricolin#link https://review.openstack.org/#/q/topic:heat-pike-2-release15:16
ricolinrelease patch is up15:16
ricolinmove on:)15:17
ricolin#action dive in newton gate and make it green15:17
ricolin#topic deprecate ceilometer client15:17
*** openstack changes topic to "deprecate ceilometer client (Meeting topic: heat)"15:17
ricolinonce https://review.openstack.org/#/c/439433/12 land15:18
ricolinwe will have no resource depend on ceilometer client plugin(at least not in heat repo)15:18
ricolinas ramishra suggest, we should consider mark it as deprecate15:19
ricolinbefore we do that, is there any concern not to do so?:)15:20
ricolinnice:)15:21
ricolinmove on:)15:21
ricolin#stack abandon/adopt15:21
ricolingaborm, it's yours:)15:22
gabormok15:22
gabormabandon/adopt is important for us15:22
gabormwould like to make sure that it is not dropped until external_id turns out to be a good replacement15:23
zanebI don't have a problem with that15:24
ramishragaborm: does it work well with convergenceengine ? Do you use it with newton+ heat?15:24
zanebit's disabled by default, so currently mostly not hurting anyone15:24
mrwolf:)15:24
mrwolfwe actually have to support from  liberty+15:24
mrwolfI'm not even sure if we have to support newton yet.15:25
gabormwe rely on it as a tool for doing whatever topology change needed for upgrading a vnf _in-service_15:25
zanebramishra: I believe it should work with convergence. it's basically a variation on create/delete. it definitely didn't work at first but iirc that was fixed15:25
ricolingaborm, maybe you guys can give a heads up for convergence, since you might want to test it with abandon/adopt before you actually move your env to use it15:25
therveThere is no reason to drop it really. Did we deprecate it?15:25
mrwolfFrom what we see, enterprise environment tend to lag behind.15:26
zanebtherve: the config option is not deprecated afaik15:26
mrwolfTo be honest, I'm not have to catch up on what convergence engine is15:26
zanebmrwolf: it will change your life ;)15:27
mrwolfon the latest summit, it was brought up that the adopt/abandon interface might be deprectaed and dropped15:27
mrwolfso what I see, from major release to another major release VNFs tend to have major topology changes15:27
LanceHaigI agree Enterprise lags behind others15:27
mrwolfand sometimes they approach it with the following way15:28
LanceHaigso we should make sure we don't break stuff to much15:28
ricolinmrwolf, maybe this can help you a little15:28
ricolin#link https://www.youtube.com/watch?v=FVo_zHXcMC015:28
mrwolfthey would like to build a new stack, representing new topology15:28
ricolina bad video for onboarding15:28
mrwolfbut there are key resources that should somehow be moved from the old stack to the new one15:29
kazshumm we also rely on abandon well....15:29
mrwolf(for example they hold random allocated IP for port, or floatingIp, that are propagated to other systems so they should be kept)15:30
zanebtopology of what exactly here?15:30
zanebnetworks?15:30
gabormricolin: hopefully only the audio quality is bad :)15:30
mrwolfsorry, topology of VNFs15:30
mrwolf~application15:31
ricolingaborm, lol15:31
gabormzaneb: ports and volumes seem the most critical ones15:31
zanebmrwolf: just trying to get an idea of why this requires a whole new stack and can't be done with an update15:31
gaborme.g. keep an IP address15:31
mrwolfbasicaly a bunch of vms, volumes, networking deployed to satisfy a given purpose/service15:31
gabormor keep a volume that was originally attached as "delete on terminate"15:32
zaneb(still clueless so far)15:32
mrwolfyeah, so this is 5-9 environment, it is often reqired or advised15:32
mrwolfto do sanity check on the new deployment ,before traffic is routed there15:32
gabormsay someone was not careful enough to define the HOT such that it can be upgraded by consecutive stack updates15:33
gabormpractically noone is careful enough like that15:33
mrwolfbasically the old stack does everything up until the very last minute, where they do a quick switch over15:33
ricolinmrwolf, you mean "adopt" stack?15:34
mrwolfand sometimes, it just laziness where it's easier to build anew, the figuring out a logical path via stack updates to get from one topology to a majorly different new one15:34
zanebmrwolf: we're working toward a future where Heat can automate all of that, but I understand15:34
mrwolfwith abandon and adopt, one can create let go of the resources and if they are very lucky they can manually create an "export json", they can use for adopt15:35
LanceHaigI have to jump off something has come up sorry15:35
mrwolf-create15:36
ricolinLanceHaig, np, see you soon:)15:36
mrwolfhence importing resources15:36
zanebmrwolf: use export *before* abandon, then you don't need as much luck15:36
*** LanceHaig has quit IRC15:36
gabormzaneb: thanks, that's a great feature115:37
gaborm*!15:37
mrwolfI also saw, that the original blueprint for external resoucres contained use cases like this: #link https://specs.openstack.org/openstack/heat-specs/specs/liberty/external_resource.html15:37
zanebexternal resources is designed to be the long-term solution to this15:38
mrwolfbut my trials show me, that actually updating the externalId of a resource, if it was created by HEAT is not allowed15:38
mrwolfso this is no way to let go, or import a resource15:38
mrwolf(currently)15:38
zanebmrwolf: you can always set deletion_policy: retain and then delete the stack15:38
mrwolfok, that's half way there :)15:39
ricolinmrwolf, what we might do in long term, is to make sure external resource can fully take over abandon/adopt before we retire abandon/adopt15:40
zanebricolin: yes, absolutely15:40
mrwolfexport is useful indeed, the lucky part was about editing that output with addnig new resources, in the perfect way so heat can consume it15:40
gabormricolin, zaneb: that's already great news for us15:41
zanebmrwolf: haha, yeah, you will always need luck for that bit. one reason that external resources are a considerably better design15:41
mrwolfin Boston @zaneb said that the adopt/abandon is disabled because it is buggy, and not maintained15:41
mrwolfis there a list for bugs that are still valid?15:42
zanebthere is a standing query for those bugs :)15:42
zaneb#link https://bugs.launchpad.net/heat/+bugs?field.tag=abandon-adopt15:42
mrwolfhow far back it is realistic to backport a fix, if we provide one? (I mean as an OS version, like liberty). Or is there major changes (like convergence sounds like) that would mean the same fix most probably won't work for older verions?15:43
ricolinnewton15:44
ricolinif for security15:44
zanebhttps://docs.openstack.org/project-team-guide/stable-branches.html#appropriate-fixes15:44
zanebwe're obliged to follow that policy ^15:45
ricolinzaneb, thx15:45
mrwolf:(, ok so what can be an earliest realistic target for new features to external resources?15:45
zanebthat said, it should be *technically* possible to backport fixes without too much difficulty in most cases15:45
gabormI encountered strange behavior of adopting nested stacks: the "files" map needed to be filled in inconsistently, depending on the level15:45
mrwolf(yes, thx for all the answers, we're kind of newbie, we were at the user side of heat for the most part)15:46
zanebthe convergence_engine is a separate code path15:46
mrwolfi see15:47
ricolinmrwolf, gaborm do hope if you guys can help us to test with convergence mode + export/abandon/adopt for your use case when you try to move to mitaka or further15:47
gabormbtw, adopting nested stacks does not work with the cli---only with python-heatclient (with the create method; no adopt)15:47
*** felipemonteiro has joined #openstack-meeting-515:47
gabormricolin: sure, we hope so too15:48
*** felipemonteiro_ has joined #openstack-meeting-515:48
gabormconvergence can be turned on from mitaka?15:49
mrwolfinternally we "play" with newton15:49
ricolingaborm, yes, and it's default= true since newton15:50
ricolinmrwolf, ^^^15:50
mrwolfbut as long as we have to support down to liberty, we have to come up with solutions that can cover all supported platforms15:50
mrwolf...again enterprise15:50
mrwolf:)15:50
zanebtbh I wouldn't recommend using it in mitaka, just because it's so much better tested since it became the default in newton15:50
gabormok, we'll start testing with newton15:51
ricolinzaneb, +115:51
mrwolfthx, I look into convergence.15:52
*** felipemonteiro has quit IRC15:52
gabormthanks a lot so far! we'll talk to our managers on that we need to contribute to heat15:52
ramishramrwolf: liberty is EOL for us https://releases.openstack.org/ , though as zaneb mentioned you can technically backport fixes15:52
ricolingaborm, mrwolf  looking forward for any bug report from you guys15:52
mrwolfthanks for the time and aswers15:52
*** Rockyg has joined #openstack-meeting-515:53
gabormok, we'll report at least those two issues above15:53
zanebmrwolf, gaborm: thanks, I think this was productive :)15:53
ricolinmrwolf, yes, like ramishra just said, it's possible that you can backport our work in new version, if that can do any help to you15:54
gabormsame here! :)15:54
ricolinnice:)15:54
ricolinmove on15:54
ricolin#topic Open discussion15:54
*** openstack changes topic to "Open discussion (Meeting topic: heat)"15:54
ricolinanything would like to discuss?:)15:55
ramishrazaneb: what should we do for nova floatingip resources? They are broken atm, Is there a different approach than https://review.openstack.org/#/c/466187/ you've in mind?15:56
zanebso I read somewhere that nova-network actually still exists, and it's just the passthrough to neutron in the client that was deleted15:57
*** gomarivera has joined #openstack-meeting-515:57
zanebnow I don't know what to believe or what we should be doing15:57
ramishrazaneb: the support is removed from novaclient15:57
zaneball support for nova-network?15:58
ramishrayes15:58
zanebbut nova-network still exists in nova?15:59
ramishrayes, they have kept it in the server due to some dependency with placement services, that's the most I know15:59
ramishraI think that's what also mentioned in the mail you mentioned16:00
ricolinokay guys time16:00
zaneb"nova-network still exists in Pike and will continue to exist until we can get rid of cells v1, which isn't until we can claim support for multiple cells v2 cells."16:00
ricolintime's up16:00
ricolinshall we move this back to heat:)16:00
zanebby all means16:01
ricolinthanks all:)16:01
ricolin#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Wed Jun  7 16:01:54 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-06-07-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-06-07-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-06-07-15.00.log.html16:01
*** mrwolf has quit IRC16:02
*** gaborm has quit IRC16:03
*** ramishra has quit IRC16:41
*** ricolin has quit IRC16:46
*** derekh has quit IRC16:56
*** zhipeng_ has quit IRC16:59
*** zhipeng_ has joined #openstack-meeting-517:00
*** zhipeng_ has quit IRC17:01
*** ralonsoh has quit IRC17:06
*** Rockyg has quit IRC17:20
*** rarcea has quit IRC18:13
*** marst_ has joined #openstack-meeting-520:20
*** marst has quit IRC20:23
*** dougbtv_ has joined #openstack-meeting-520:34
*** dougbtv has quit IRC20:38
*** cargonza_ has joined #openstack-meeting-521:24
*** skazi__ has joined #openstack-meeting-521:26
*** SamYaple_ has joined #openstack-meeting-521:27
*** cargonza has quit IRC21:29
*** mcnanci_ has quit IRC21:29
*** skazi_ has quit IRC21:29
*** SamYaple has quit IRC21:29
*** cargonza_ is now known as cargonza21:29
*** mcnanci has joined #openstack-meeting-521:32
*** therve has left #openstack-meeting-521:45
*** SamYaple_ has quit IRC21:57
*** marst_ has quit IRC22:52
*** felipemonteiro_ has quit IRC22:52
*** gomarivera has quit IRC22:53
*** gomarivera has joined #openstack-meeting-522:54
*** gomarivera has quit IRC22:58
*** openstack has joined #openstack-meeting-523:15
*** ChanServ sets mode: +o openstack23:15
*** gomarivera has joined #openstack-meeting-523:30
*** gomarivera has quit IRC23:34

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