Wednesday, 2017-12-13

openstackgerritHengqing Hu proposed openstack/octavia master: Extend api to accept qos_policy_id  https://review.openstack.org/45830800:23
*** tongl has quit IRC00:27
*** openstackgerrit has quit IRC00:33
*** openstackgerrit has joined #openstack-lbaas00:38
openstackgerritHengqing Hu proposed openstack/octavia master: Improve Neutron driver _get_resource()  https://review.openstack.org/52719900:38
openstackgerritHengqing Hu proposed openstack/octavia master: Extend api to accept qos_policy_id  https://review.openstack.org/45830800:42
openstackgerritHengqing Hu proposed openstack/octavia master: Extend api to accept qos_policy_id  https://review.openstack.org/45830800:47
johnsomUmmm, what is going on there?00:47
dayouAdam's patch just merged, caused a few merge conflicts00:58
dayouhttps://review.openstack.org/#/c/525790/00:58
johnsomTypically that can be resolved in one rebase/merge patch....00:59
*** Swami has quit IRC01:01
johnsomAre we sure that TaskUtils can be run as a property that way?01:01
dayouI am not sure, but it wouldn't cause any harm01:01
dayouWe can do the other way also01:02
johnsomIt moves the instantiation from startup to runtime right?01:03
dayouWhat's the difference between startup and runtime for this specific use case?01:04
johnsomWe did that on the network driver since it connects to an outside service, which if it fails we want the flow to fail and revert.  task_utils are special database methods that do not raise exceptions so that it does not cause a revert.01:05
johnsomrm_work Do you have an opinion? https://review.openstack.org/#/c/458308/60..63/octavia/controller/worker/tasks/network_tasks.py01:06
dayouIt is connected to the db service, right?01:07
dayouMariadb and Neutron should be considered the same as outside service01:08
johnsomMy point is more about task_utils should never fail in the eyes of Octavia.  We moved the network driver to a property so it will cause failures if neutron goes down.01:09
dayouWhat if there is a temporary database failure, some spikes caused by mariadb cluster01:11
johnsomtask utils methods must silently fail. If they were to raise it could abort the revert flow and leave a LB in a poor state like PENDING01:12
johnsomBasically we are trading off and saying, if that DB update fails, it's ok, continue your cleanup01:12
johnsomSo, going up the init stack, I don't see anything that will break with this.  It's just odd01:15
dayouGot you01:15
dayouI am trying to learn the art of argument01:16
dayou:-D01:16
johnsomHa01:16
openstackgerritHengqing Hu proposed openstack/octavia master: Extend api to accept qos_policy_id  https://review.openstack.org/45830801:17
johnsomIt's the end of a long day for me, so not the best adversary tonight.01:17
dayouGet some good rest, you should get refreshed tomorrow01:18
dayouI go out and do some morning exercise01:21
johnsomEnjoyh01:21
bzhaoOh, I think I miss something. Sorry for late. Just back. T_T01:40
johnsombzhao FYI, I am working on an edit of the UDP spec.  Will post here in a bit01:44
bzhaojohnsom, Thanks, just do it. :). I will follow it and change the exist patch.01:48
johnsomMostly formatting, but I think the session persistence needs to change01:48
*** tongl has joined #openstack-lbaas01:50
bzhaojohnsom, sorry for that, my bad english. And thanks for your kind help. OK, nevermind , I coding from backend to front. The change must be small, I think. :)01:51
*** tongl has quit IRC01:56
*** annp has joined #openstack-lbaas02:07
openstackgerritMichael Johnson proposed openstack/octavia master: Support UDP load balancing  https://review.openstack.org/50360602:45
johnsombzhao ^^^ Please have a look.  I need to sign off for the night.  Feel free to comment on the patch, I will look in the morning02:46
bzhaojohnsom, OK. I will check. Please hava a good rest. Thank you very much. :) Good Night02:48
openstackgerritHengqing Hu proposed openstack/octavia master: Don't run fucntional jobs for docs changes  https://review.openstack.org/52654802:51
dayou@johnsom, fixed a typo for you, since you are busy editing bo's udp spec.02:52
openstackgerrithujin proposed openstack/neutron-lbaas master: Remove key "l7_policies" in pool dict  https://review.openstack.org/52728702:54
*** sanfern has quit IRC03:13
*** tongl has joined #openstack-lbaas03:16
*** bar_ has joined #openstack-lbaas03:18
bar_rm_work, ping03:23
*** tongl has quit IRC03:41
*** armax has quit IRC03:57
rm_workbar_: pong04:07
bar_hey04:07
bar_do you have conflicts?04:07
bar_rm_work, my patch was altered https://review.openstack.org/#/c/527199/ ...04:08
bar_can you +2 it?04:08
*** fnaval has quit IRC04:09
*** fnaval has joined #openstack-lbaas04:09
bar_(or should i revert those changes perhaps... not sure why they're required)04:09
rm_workyep04:10
rm_worki mean it seems fine04:10
rm_workwas trying to see what changed between the patchsets, don't see anything bad04:10
bar_ok, thanks. perhaps you should rebase onto it? unless another core wants to +2 it.04:12
rm_worki'll get to rebasing my stuff when i need to04:12
rm_workfor now it's fine04:12
rm_workwe'll see what merges when04:12
bar_cool04:13
*** fnaval has quit IRC04:14
*** threestrands has joined #openstack-lbaas04:14
*** threestrands has quit IRC04:14
*** threestrands has joined #openstack-lbaas04:14
*** jappleii__ has quit IRC04:15
*** fnaval has joined #openstack-lbaas04:15
*** threestrands has quit IRC04:15
*** threestrands has joined #openstack-lbaas04:16
*** threestrands has quit IRC04:16
*** threestrands has joined #openstack-lbaas04:16
*** openstackgerrit has quit IRC04:18
*** links has joined #openstack-lbaas04:30
*** links has quit IRC04:32
bar_johnsom, ping04:34
bar_bzhao, ping04:35
*** threestrands has quit IRC04:36
*** threestrands has joined #openstack-lbaas04:43
*** threestrands has quit IRC04:43
*** threestrands has joined #openstack-lbaas04:43
*** threestrands has quit IRC04:44
*** threestrands has joined #openstack-lbaas04:44
*** threestrands has quit IRC04:44
*** threestrands has joined #openstack-lbaas04:44
*** threestrands has quit IRC04:45
*** threestrands has joined #openstack-lbaas04:46
*** threestrands has quit IRC04:46
*** threestrands has joined #openstack-lbaas04:46
*** threestrands has quit IRC04:47
*** threestrands has joined #openstack-lbaas04:47
*** threestrands has quit IRC04:47
*** threestrands has joined #openstack-lbaas04:47
*** openstackgerrit has joined #openstack-lbaas05:01
openstackgerritBar RH proposed openstack/python-octaviaclient master: Add VIP QoS Policy client support  https://review.openstack.org/52621705:01
*** bar_ has quit IRC05:02
*** tongl has joined #openstack-lbaas05:06
openstackgerritSanthosh Fernandes proposed openstack/octavia master: [WIP] ACTIVE-ACTIVE ExaBGP rest api driver  https://review.openstack.org/52700905:25
*** AlexeyAbashkin has joined #openstack-lbaas05:43
*** tongl has quit IRC05:56
*** bbzhao has quit IRC05:58
*** bbzhao has joined #openstack-lbaas05:58
*** threestrands has quit IRC06:03
openstackgerritOpenStack Proposal Bot proposed openstack/neutron-lbaas-dashboard master: Imported Translations from Zanata  https://review.openstack.org/52759106:19
bzhaobar_, pong06:20
*** gcheresh has joined #openstack-lbaas06:23
openstackgerritOpenStack Proposal Bot proposed openstack/neutron-lbaas master: Imported Translations from Zanata  https://review.openstack.org/52760006:41
*** dokua has joined #openstack-lbaas06:49
*** AlexeyAbashkin has quit IRC06:57
*** rcernin has quit IRC07:12
nmagnezirm_work, o/07:17
nmagnezirm_work, we still need to discuss bar's amphora agent IP patch :)07:18
*** Alex_Staf has joined #openstack-lbaas07:41
*** b_bezak has joined #openstack-lbaas07:58
*** rcernin has joined #openstack-lbaas08:13
openstackgerritZhaoBo proposed openstack/octavia master: Support UDP load balancing  https://review.openstack.org/50360608:21
*** tesseract has joined #openstack-lbaas08:25
*** AlexeyAbashkin has joined #openstack-lbaas08:27
*** AlexeyAbashkin has quit IRC08:32
*** AlexeyAbashkin has joined #openstack-lbaas08:37
*** AlexeyAbashkin has quit IRC08:43
*** annp has quit IRC08:46
*** annp has joined #openstack-lbaas08:46
*** yuanying has quit IRC08:52
*** AlexeyAbashkin has joined #openstack-lbaas08:57
*** links has joined #openstack-lbaas09:00
openstackgerritZhaoBo proposed openstack/octavia master: Support UDP load balancing  https://review.openstack.org/50360609:19
*** annp has quit IRC10:05
*** yamamoto has quit IRC10:13
*** dosaboy has quit IRC10:24
*** dosaboy has joined #openstack-lbaas10:25
*** sapd_ has quit IRC10:28
*** sapd has joined #openstack-lbaas10:30
*** dosaboy has quit IRC10:31
*** salmankhan has joined #openstack-lbaas10:35
*** dosaboy has joined #openstack-lbaas10:37
*** eN_Guruprasad_Rn has joined #openstack-lbaas10:39
*** yamamoto has joined #openstack-lbaas10:43
*** eN_Guruprasad_Rn has quit IRC10:46
openstackgerritSanthosh Fernandes proposed openstack/octavia master: Adding exabgp-speaker element to amphora image  https://review.openstack.org/49016410:46
*** eN_Guruprasad_Rn has joined #openstack-lbaas10:47
*** eN_Guruprasad_Rn has quit IRC10:50
*** eN_Guruprasad_Rn has joined #openstack-lbaas10:51
*** salmankhan has quit IRC11:37
*** salmankhan has joined #openstack-lbaas11:51
*** bar_ has joined #openstack-lbaas12:11
*** sanfern has joined #openstack-lbaas12:14
*** sanfern has quit IRC12:33
openstackgerritHengqing Hu proposed openstack/octavia master: Adding exabgp-speaker element to amphora image  https://review.openstack.org/49016412:37
*** dmellado has quit IRC12:47
*** atoth has joined #openstack-lbaas12:58
*** dmellado has joined #openstack-lbaas12:58
*** rcernin has quit IRC13:04
*** dmellado has quit IRC13:08
*** dmellado has joined #openstack-lbaas13:09
*** tesseract has quit IRC13:51
openstackgerritBar RH proposed openstack/octavia master: Specify management IP addresses per amphora  https://review.openstack.org/50515813:52
*** links has quit IRC13:58
*** links has joined #openstack-lbaas14:00
*** bar_ has quit IRC14:00
*** links has quit IRC14:05
*** fnaval has quit IRC14:13
*** openstackstatus has quit IRC14:36
*** openstackstatus_ has joined #openstack-lbaas14:37
*** openstackstatus_ has quit IRC14:37
*** openstackstatus has joined #openstack-lbaas14:38
*** openstack has quit IRC14:39
*** openstack has joined #openstack-lbaas14:43
*** ChanServ sets mode: +o openstack14:43
*** openstack has quit IRC14:43
*** openstack has joined #openstack-lbaas14:48
*** ChanServ sets mode: +o openstack14:48
*** armax has joined #openstack-lbaas14:57
*** fnaval has joined #openstack-lbaas14:59
*** ianychoi has quit IRC15:04
*** salmankhan has quit IRC15:14
*** tongl has joined #openstack-lbaas15:17
*** links has joined #openstack-lbaas15:19
*** eN_Guruprasad_Rn has quit IRC15:23
*** eN_Guruprasad_Rn has joined #openstack-lbaas15:24
*** dokua has quit IRC15:25
*** dosaboy has quit IRC15:28
*** dosaboy has joined #openstack-lbaas15:28
openstackgerritGerman Eichberger proposed openstack/octavia master: ACTIVE-ACTIVE with LVS - DIB  https://review.openstack.org/49980715:34
*** salmankhan has joined #openstack-lbaas15:47
*** armax has quit IRC15:47
*** gcheresh has quit IRC15:47
*** b_bezak has quit IRC15:53
*** Alex_Staf has quit IRC16:01
*** ianychoi has joined #openstack-lbaas16:06
*** longstaff has joined #openstack-lbaas16:07
*** ssmith has joined #openstack-lbaas16:09
*** armax has joined #openstack-lbaas16:18
*** armax has quit IRC16:21
*** eN_Guruprasad_Rn has quit IRC16:42
johnsomI love coming into the office in the morning finding uwsgi out to lunch with 100% cpu usage for the devstack services....  Ugh16:44
*** AlexeyAbashkin has quit IRC16:47
xgerman_fun times16:47
*** tongl has quit IRC16:49
johnsomIf the thing is going to go into cryptocurrency mode to fund the dev it might as well be efficient about it and use the GPU....16:50
xgerman_we should add some cryprocurrency code to Octavia to fund an Octavia party in Dublin16:56
johnsomWe wouldn't get far with uwsgi stealing all of the cycles.16:59
johnsomInteresting tidbit of the morning: TCP bandwidth through an amp is the same with HAproxy or just a simple socat tunnel.  Both of which are about 10gbps slower than a direct connection. (this is on devstack inside vmware on a desktop).17:06
johnsomIf I go from amp to member it is ~6gbps slower than host to member.17:08
johnsomIt doesn't appear to be CPU in the amp, but qemu certainly spikes on the host.17:10
xgerman_I saw some cilium stuff in my twitter feed and they manages to do that kernel network proxying without decoding TCP…17:11
johnsomYeah, I'm not decoding or inspecting either, it's bits in bits out. Pretty happy that haproxy is pretty close to the same performance as that17:12
*** sanfern has joined #openstack-lbaas17:13
johnsomJust wishing the infrastructure around us was a bit faster.17:13
xgerman_yeah, they probably do decoding/encoding or at least copying things around17:13
xgerman_in OVS, linux Bridge17:13
johnsomYeah, don't see CPU spikes there though, it's really qemu that seems questionable.17:14
xgerman_mmh17:14
sanferno/17:15
johnsomI kind of expected to see OVS up but it wasn't the clear CPU hog17:15
xgerman_yeah, I would have fingered them, too17:17
sanfernJohnsom., I tested exabgp element patch and figured out the issue. Basically I had to add my review id in amphora-agent element17:19
*** tongl has joined #openstack-lbaas17:19
sanfernby default exabgp will not start - http://paste.openstack.org/show/CVH8BVALOyLXdfjnhs2A/17:20
johnsomHmm, it's not picking up the patch version...  We should fix that.  Probably a zuul change issue.17:20
sanfernok17:20
sanfernone more query - https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt this shows exabgp version 4.0.217:21
sanfernbut when we update requirements.txt to exabgp>=4.0.2 it fails17:22
johnsomYou must copy the line exactly from https://git.openstack.org/cgit/openstack/requirements/tree/global-requirements.txt#n5717:22
*** eN_Guruprasad_Rn has joined #openstack-lbaas17:23
*** bar_ has quit IRC17:26
*** armax has joined #openstack-lbaas17:30
sanfernThere is a mismatch in upper-constraints.txt and global-requirements.txt file :(17:30
johnsomYes, they are two different config files17:31
sanfernok thanks17:33
sanfernhttps://review.openstack.org/#/c/524722/13 - this patch is not running through gates17:33
sanfernI want your help to solve those repo tests are failing :(17:34
johnsomOk, I will have a look once that zuul run finishes17:34
*** links has quit IRC17:40
sanfernThank you johnsom17:50
*** eN_Guruprasad_Rn has quit IRC17:51
*** bar_ has joined #openstack-lbaas17:54
*** bar_ has quit IRC17:57
openstackgerritMerged openstack/octavia-dashboard master: Imported Translations from Zanata  https://review.openstack.org/52590818:08
*** Swami has joined #openstack-lbaas18:11
*** AlexeyAbashkin has joined #openstack-lbaas18:17
*** AlexeyAbashkin has quit IRC18:21
*** gcheresh has joined #openstack-lbaas18:27
*** gcheresh has quit IRC18:38
*** yamamoto has quit IRC18:45
*** gcheresh has joined #openstack-lbaas18:50
*** yamamoto has joined #openstack-lbaas19:01
*** atoth has quit IRC19:03
*** sshank has joined #openstack-lbaas19:04
*** yamamoto has quit IRC19:06
*** salmankhan has quit IRC19:14
*** openstackstatus has quit IRC19:27
*** jniesz has joined #openstack-lbaas19:37
sanfernjohnsom, http://paste.openstack.org/show/8If6iLYePrSRS3ohEjxL/ - help19:45
sanfernhttp://paste.openstack.org/show/3LiJtFfIuVzbpwYbX9YY/19:47
johnsomOk, updated the very full agenda: https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Agenda19:52
johnsomI re-ordered some stuff to try to give a fair timeslot19:53
johnsom#startmeeting Octavia20:00
openstackMeeting started Wed Dec 13 20:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is johnsom. 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: Octavia)"20:00
openstackThe meeting name has been set to 'octavia'20:00
johnsomHi folks!20:00
xgerman_o/20:00
johnsomAnother fine week in OpenStack land20:00
nmagnezio/20:00
longstaffhi20:00
*** rm_mobile has joined #openstack-lbaas20:00
cgoncalveshey20:00
johnsom(well, ok, zuul had it's issues...)20:00
johnsom#topic Announcements20:00
*** openstack changes topic to "Announcements (Meeting topic: Octavia)"20:01
rm_mobileo/20:01
johnsomI have two items20:01
johnsomOne, queens MS2 did finally release20:01
johnsomI also released a new python-octaviaclient20:01
johnsomSo, good stuff there.20:01
johnsomAlso I wanted to make you aware of a lively discussion on the mailing list about changing the release cycle of OpenStack to once per year.20:02
johnsom#link http://lists.openstack.org/pipermail/openstack-dev/2017-December/125473.html20:02
xgerman_guess we are maturing…20:02
johnsomIf you have any feeling about the PTG meetings or release timing, feel free to jump into the conversation20:02
nmagnezijohnsom, what do you think about this?20:02
johnsomI have mixed feelings.20:03
johnsomI think overall it will slow innovation on the project. I worry about trying to do stable branch bug backports from master that has up to a year of feature work. I do think we are a bit of a treadmill with the PTGs and PTL elections, etc. Finally, the goals do hurt the projects with the six month cycles since some require a lot of work.20:04
johnsomI think it may mean that the PTL needs to take on more management work to keep the project on track.  Maybe more defined sprints or team milestones.20:05
johnsomJust some top of head thoughts.20:05
rm_mobileYeah... Some of the stuff is too fast, but... Longer cycles means bigger releases which does not help with upgrades20:05
johnsomAny other comments?20:05
nmagneziyeah. i wonder how we exactly shift to 1 year planning - feature-wise20:05
johnsomYep20:06
xgerman_one PTG per year clearly makes attanding the summits more imrportant20:06
johnsomYeah, my last read of the list the proposal was one PTG, still two summits20:06
johnsomOk, any other announcements?20:06
nmagnezixgerman_, so virtual PTGs? :)20:06
xgerman_midcycles?20:07
johnsomnmagnezi I thought about that20:07
nmagnezicould be tricky, timezone-wise20:07
nmagnezibut I'll be in favor of that.20:07
johnsom#topic Brief progress reports / bugs needing review20:07
*** openstack changes topic to "Brief progress reports / bugs needing review (Meeting topic: Octavia)"20:07
johnsomOk, moving along to try to give time for other topics20:08
rm_mobileDo we need to pick up anything from last week?20:08
johnsomI have been focused on getting reviews done and updates to the specs in flight.20:08
johnsomrm_mobile Yes, I have a long list20:08
rm_mobileLol k20:08
johnsom5 topics including the carry over20:08
*** Kowsalya has joined #openstack-lbaas20:08
johnsomI hope we can merge QoS this week.20:09
*** yamamoto has joined #openstack-lbaas20:09
johnsomProvider driver spec is looking good, but we really would like feedback on some topics.  Specifically on my mind is should the Octavia API create the VIP port and pass to the driver or should the driver be responsible for creating the VIP port.20:10
johnsomPlease comment on that topic if you have a driver in your future.20:10
*** sshank has quit IRC20:10
johnsomThe UDP spec is also coming along nicely.  Feedback welcome.20:10
johnsom#link https://review.openstack.org/50995720:10
nmagneziI commented about that (VIP port create). would be happy to elaborate more if needed20:11
johnsom#link https://review.openstack.org/50360620:11
johnsomAny other progress updates?20:11
johnsom#topic (rm_work / dayou) Element Flag for Disabling DHCP20:11
*** openstack changes topic to "(rm_work / dayou) Element Flag for Disabling DHCP (Meeting topic: Octavia)"20:12
johnsom#link https://review.openstack.org/#/c/520590/20:12
johnsomWe didn't get to this last week, so I put it at the top this week20:12
rm_mobileGetting to a real keyboard for this lol20:12
johnsomMy understanding on it was the issue dayou was having was/can be resolved without this.20:12
rm_worko/20:12
rm_workhmmm can it?20:12
rm_workI mean, the DHCP issue is one that I have as well (just use an internal patch to fix it)20:13
johnsomMy biggest concern with the patch is issues with cloud-init overriding those changes.20:13
jnieszi think the problem with cloud init it doesn't support slaac20:13
jnieszexpects dhcp or static20:13
johnsomjniesz No, it uses slaac.  That is all I have in my lab20:14
rm_workmy issue is that our cloud HAS NO DHCP (i believe we're not alone in this either), and images stall on the dhcp step for ipv4 even20:14
rm_workmaybe there is a better way to fix this that I'm missing?20:14
jnieszjohnsom it wasn't in the source code, i didn't see anything for it to write out inet6 auto lie20:14
xgerman_but then the coud-init shoudl set it as static?20:14
rm_workbut, it seems that it stalls on dhcp even before cloud-init runs to change it20:14
rm_workbecause cloud-init DOES have a static config to send it20:14
jnieszstatic != slaac20:15
johnsomrm_work That is a different issue20:15
rm_workright20:15
rm_workbut this patch was designed to fix both20:15
jnieszyea20:15
rm_worki guess if it's just my issue, I can just stick to my current internal patch that ... well, does exactly this (which works)20:16
johnsomIt's been a while since I booted a v6 enabled amp, so I'm not sure how cloud init handles it.  I know we have code in for the v6 auto case20:16
jnieszjohnsom: is that dhcpv6 though?20:16
johnsomNo, I don't have dhcpv620:16
nmagnezijohnsom, IIRC the jinja templates handle a static ipv6 as well. but I didn't test it20:16
rm_workthis is what I apply internally: http://paste.openstack.org/show/628898/20:17
xgerman_so rm_work says it comes up eventually after dhcp gives up20:17
rm_workyes, like 5 minutes >_>20:17
rm_workwhich is way outside the timeout for my cloud20:17
johnsomSo, I think we should break this into two stories. 1. for the dhcp delay 2. for booting v6 only amps.20:17
xgerman_+120:17
rm_workk, just figured it was a workable solution for both, but yeah if his issue needs to be solved in a different way, then this would just be for me20:18
rm_worki just pushed this because at the time he was duplicating my work for dhcp disabling20:18
*** yamamoto has quit IRC20:18
jnieszyea this would work for booth20:18
johnsomThe concern is hacking on the network scripts that cloud-init manages/overwrites is worrisome, especially if we don't explicitly tell cloud-init that we are managing those.20:19
johnsomLike, that paste, doesn't a reboot overwrite that?20:19
xgerman_+120:19
rm_workjohnsom: it doesn't seem to <_< though a reboot causes a failover and recycle for me20:19
rm_workso it's hard to tell20:19
rm_workbut i mean, it doesn't seem to be overwritten by cloudinit20:19
jnieszcloud-init assumes wrong things : )20:19
rm_worklooking at existing amps20:19
johnsomI'm also not as familar with cloud-init under CentOS as I am ubuntu20:20
xgerman_nmagnezi?20:20
nmagneziwould have to check20:20
johnsomcloud-init does what neutron and nova tells it.  That was the solution we came up with for your case jniesz20:20
jnieszyea, but it doesn't work20:21
jnieszfor slaac20:21
jnieszcloud init needs to be enhanced to add that20:21
jnieszand then would have to wait for distros to add new cloud init20:21
johnsomjniesz Something doesn't jive with that.  All I have is slaac here and I had working IPv6, so ...20:21
jnieszit looks for dhcp20:22
jnieszotherwise assumes static20:22
johnsomThe other part I didn't like with the script is it is specific to the distros, where cloud init handles the translations for us.20:22
jnieszin the network metadat20:22
rm_workoh actually yes, looked again, it IS overwritten by cloud-init :( but cloud-init does this AFTER the boot step that tries to DHCP an address20:23
rm_workso yeah probably on reboot it would have issues :(20:23
johnsomSo, my ask, let's open stories that characterize the use cases, then we bind patches to those and work from there.20:23
*** dokua has joined #openstack-lbaas20:23
rm_workis there some way for me to send these options during cloud-init boot?20:23
johnsomrm_work See, I'm not totally crazy... grin20:23
rm_workbut ...20:23
rm_worksee this is a problem still20:24
rm_worki still need my patch20:24
johnsomYes, there are much better ways.20:24
rm_workjust ALSO need to update cloud-init20:24
rm_workbecause again, cloud-init hasn't replaced it by the time it causes a problem20:24
rm_workit replaces it AFTER20:24
rm_workso i need both fixes20:24
johnsomSo, let's open stories and work on solutions for those use cases20:24
rm_workk20:24
johnsom#topic (rm_work / BAR_RH) Specify management IP addresses per amphora20:25
*** openstack changes topic to "(rm_work / BAR_RH) Specify management IP addresses per amphora (Meeting topic: Octavia)"20:25
johnsom#link https://review.openstack.org/#/c/505158/20:25
johnsomSo we discussed this last week.  I think there was concern about the approach.  We talked about the update config API extension that we have wanted for a while.20:26
johnsomWhere did we leave this?20:26
rm_workWas this the one where nmagnezi and I needed to talk after?20:26
nmagneziyes. and we didn't catch each other here in the past week20:27
*** Kowsalya has quit IRC20:27
rm_workT_T20:27
johnsomlol20:27
*** dokua has quit IRC20:27
johnsomSo should we table this another week?20:27
rm_workSummary I think was: Instead of futzing with the flows, we just need to leave the binding as-is on boot, and then on first connect we update the config to point to the single management address20:27
*** openstackstatus has joined #openstack-lbaas20:27
nmagneziI must admit that the agent restart per-api call sounds a bit like a hack to me. so I wanted to discuss this a bit more20:27
*** ChanServ sets mode: +v openstackstatus20:27
rm_worknmagnezi: not every API call... just the update-agent-config call20:28
rm_workwhich we wanted for a while anyway20:28
rm_workfor things like updating the HM list20:28
nmagneziwhy did we want it to begin with?20:28
johnsomWe can use the oslo reload stuff too, no need for a full restart20:28
xgerman_+120:28
johnsomThe HM IP:Port list is my #120:29
rm_worksame20:29
nmagneziwell, I'm open for discussion about this. if there's a nice way to achieve this I'm all ears20:29
johnsomnmagnezi Why did we want the IP fixed?  It's a very old bug before we added the namespace20:29
xgerman_if you ever hack the system you can then sink the whole fleet by sending bogus configs20:30
*** Kousalya has joined #openstack-lbaas20:30
rm_work?20:30
rm_workhow20:30
nmagnezijohnsom, because it might be risky to bind to *20:30
rm_worknmagnezi: thats how it CURRENTLY works20:30
nmagnezijohnsom, the agent runs on the root namespace20:30
johnsomnmagnezi Correct20:30
rm_worknmagnezi: and what i'm saying is, on the *initial* call, we move it to the correct IP20:31
johnsomxgerman_ ??? what?  no20:31
johnsomIt uses the same two way SSL all of our config work happens over20:31
rm_worknmagnezi: and if the initial call fails (someone somehow beat us to it???) we fail to finish amp creation and we trash it anyway20:31
xgerman_if we allow configs being changed that is a theoretical possibility20:31
johnsomSo, if you get that far you are game over anyway20:31
johnsomxgerman_ We are talking about the amphora-agent config file inside the amp, not controllers20:32
nmagnezirm_work, let's discuss this further. I'm open for discussion about this, as I said.20:32
nmagnezi:)20:32
rm_worklolk20:33
johnsomOk20:33
rm_workso, next year? :P20:33
johnsom#topic (sanfern / rm_work) Changes to DB schema for VRRP ports20:33
*** openstack changes topic to "(sanfern / rm_work) Changes to DB schema for VRRP ports (Meeting topic: Octavia)"20:33
nmagnezirm_mobile, ¯\_(ツ)_/¯20:33
johnsom#link https://review.openstack.org/#/c/521138/20:33
*** rm_mobile has quit IRC20:33
johnsomSo next up was the rename patch.20:33
rm_workI guess all I wanted to know was, is everyone else OK with us changing field names in a DB schema20:33
johnsomI think some work as occurred over the last week to resolve some of the backwards compatibility issues.20:34
rm_workas an upgrade it is scary to me, since it absolutely kills zero-downtime20:34
rm_workhmm20:34
jnieszit doesn't bring the amps down, just the control plane20:34
rm_workyes20:34
jnieszI know sanfran added fix for amp agents20:34
rm_workjust a control-plane outage20:34
jnieszso they wouldn't all have to be upgraded20:34
rm_workyeah that's good :P20:34
rm_worki hadn't even noticed that part yet, that would have been bad20:35
johnsomRight, my stance has been we have not asserted any of the upgrade support tags yet. (nor do we have a gate)20:35
rm_worki just saw the migration and immediately stopped20:35
rm_workso as i keep saying, if everyone else is OK with this, then I am fine20:35
xgerman_yeah, I think we can do a rename/update — I also think we are still in the window to change the /octavia/amphora endpoint20:36
rm_workyes20:36
johnsomYeah, I agree on that20:36
nmagneziI have to abstain once more. since we yet to ship Octavia that does affect us in any way20:36
nmagneziso.. If it's in I'm fine with it.20:37
rm_workso I just wanted a vote on "Can we change field names in our existing DB schema"20:37
rm_workI'm concerned about my deployment, but also others20:37
* johnsom gives nmagnezi a glare of shame.... grin20:37
nmagnezijohnsom, lol, why? :-)20:37
johnsomYou haven't shipped20:37
cgoncalves:)20:37
rm_workas one of the things we get yelled at during project update sessions every summit is that our upgrades are not clean (though usually it's around the APIs)20:37
nmagnezijohnsom, tripleO.. soon enough!20:37
johnsomrm_work I hear you. We should be working towards clean upgrades. My question to you is if all of the glue code required to do a smooth transition to reasonably sane names is worth it.20:38
johnsomI mean really it's a migration that adds the new column, copies the data, and maintains both for some deprecation cycle.20:39
rm_worki absolutely would love to have these column names fixed to be less dumb20:40
johnsomLong term I would hate to have one set of terms in the models and a different in the DB20:40
rm_worki am just concerned about whether we're supposed to be doing this kind of change20:40
rm_workyeah20:40
johnsomWell, from an OpenStack perspective, if we have not asserted the upgrade tags (we have not), a downtime upgrade is fair game20:41
johnsomAs long as we don't require the amps to go down, I think I'm ok with it. (pending reviewing the full patch again)20:41
rm_workkk20:42
nmagnezi#link https://review.openstack.org/#/c/521138/20:42
rm_workyeah that's why i asked we vote not on the patch but on the core concept20:42
rm_work"Can we change field names in our existing DB schema"20:42
rm_workseems like everyone is thinking "yes"20:42
johnsomBut you, jniesz and mnaser have this running in some form of production, so your voices matter here20:42
rm_workfor me it matters a lot, since this upgrade will happen for me just about the moment it merges20:43
jnieszwhen we upgrade openstack regions we have to schedule control plane downtime anyways20:43
rm_worksince I run master, deployed weekly <_<20:43
nmagnezirm_work, master? really?20:43
rm_workyes20:43
nmagneziman..20:43
*** amotoki has quit IRC20:43
*** logan- has quit IRC20:43
johnsomYes, see nmagnezi you should ship...  grin20:43
nmagnezilol.20:43
johnsomgrin20:43
*** logan- has joined #openstack-lbaas20:43
* rm_work laughs maniacally 20:43
*** amotoki has joined #openstack-lbaas20:44
jnieszyea, I would like to get us to the point where we are deploying master20:44
rm_workjniesz: it isn't that hard actually IME20:44
rm_workjust switch what tag you pull :P20:44
rm_workhopefully existing CI+tests takes care of issues20:44
jnieszyea, I think something we will look at after the pike upgrades20:44
johnsomOk, so I hear an operator wanting an upgrade path.  We should try to support them.20:45
rm_workyeah since Octavia is cloud-version-agnostic20:45
johnsomrm_work are you willing to help with the coding for the patch?20:45
rm_workthe coding for this patch?20:45
johnsomYep20:45
rm_workI mean... how do we even do this20:45
mnaserthanks for highlighting me20:45
rm_worki thought it was basically "rename or don't"20:45
mnasermy comment is: control plane downtime is acceptable, because that sort of thing can be scheduled20:46
johnsommnaser Are you caught up? Do you have an opinion here?20:46
rm_workyeah I am leaning towards that as well honestly20:46
mnaseralso, api downtime in this case doesn't really cause that much issues, its not as critically hit as a service like nova for example20:46
rm_workbut I was literally not sure if this was a smart idea politically20:46
*** kpalan1 has joined #openstack-lbaas20:46
rm_workbut johnsom asserts we have not tagged ourselves with anything that would cause a problem20:46
rm_workso20:46
mnaserto be honest, it is very rare that you can get downtime-less upgrades, even with big projects20:46
johnsomI think we would have to do the migration to have both columns in parallel so the models can continue using the old until upgraded.20:46
rm_workah yes.20:47
rm_workwell20:47
mnaserjohnsom: brings a good point, unless you make it very clear that the old services must be shut down when starting a new one20:47
rm_workhonestly -- i think if we don't have any big political issues with this -- we just do it, and make a big flashy release node20:47
rm_work*release note20:47
johnsomRight, this would have rich release notes for upgrade....20:47
jniesz+120:47
mnaserwe run 3 replicas of octavia but our upgrade procedure usually is, turn off all replicas except one, upgrade this single replica, when everything is back up and working properly ,start up the rest20:47
mnaserperhaps add some sort of failsafe to prevent it from starting up with a newer database and failing unpredictabely?20:48
johnsommnaser This would be a "shutdown control plane", "run DB migration", "upgrade control plane", "start control plane" type of release20:48
xgerman_you forgot backup DB20:49
mnaserperhaps if db_migration_version > release_migration_version: refuse_to_start()20:49
johnsomAs it is written now.20:49
johnsommnaser Hmm, we don't have that today20:49
xgerman_yeah, we need that to not corrupt the DB willingly20:50
johnsomCurrently our upgrade is "db migration", then update control plane20:50
johnsomThis is the first patch that would not work that way20:50
*** Kousalya has quit IRC20:50
johnsomSo, let me ask again, Are there folks willing to help on this patch to make it a smooth upgarde?20:51
mnaserim unable to commit any effort into that so for our side, it will likely be: turn off all replicas, upgrade packages of 1 replica, sync db, start 1 replica, check if all ok, start up other replicas after upgrading20:52
mnaseras an operator im perfectly content with that procedure (its what we used for many others)20:52
rm_worki'm pretty much booked for this week and then i'm out essentially until January20:52
rm_workso20:52
rm_work....20:52
rm_workand i'm ok with this upgrade procedure20:52
rm_workpersonally20:53
rm_workmy concern was that it's the ... like, 4 of us that deploy AND are active enough in the project to be talking in the weekly meetings20:53
johnsomOk, so I think I hear all three stack holders that are present saying they are ok with this upgrade procedure. Correct?20:53
rm_workthat are saying it's ok20:53
rm_workpeople who aren't this active but are deploying octavia ... those are who I worry about20:53
johnsomUnderstand.20:54
rm_workand i wonder about what kind of support load this will cause20:54
johnsomI guess  the last option is to sit on this until someone can work on it20:54
rm_workbut ... i also don't have a lot of time to devote to this patch, so20:54
rm_workwe COULD patch just the amphora API20:54
rm_workso we get it before it releases20:54
johnsomI don't think that is a good option given it's scope20:54
rm_workand then fix the actual DB later20:55
rm_workthe only place it's exposed is that API20:55
nmagnezirm_work, that's a valid point. they way I see it is the best option to ensure we don't break existing deployments is with alembic migrations\20:55
rm_workso if we're looking like it won't make it to Queens, it's simple to update just those fields20:55
johnsomIt's the internals that are important for L3 Act/Act work20:55
rm_workyeah ...20:55
rm_workalright, maybe the best approach IS to "add columns"20:55
rm_workand duplicate the writes?20:56
*** alex_staf_1 has joined #openstack-lbaas20:56
rm_workthese columns aren't large20:56
rm_workso it's extra data but not tooo much20:56
rm_workright?20:56
johnsomYeah, that is the work I described.20:56
jnieszI think that would be acceptable20:56
johnsomThen at some later point drop the duplicates20:56
rm_workyeah20:56
rm_workwhen is the last day we could do this20:57
johnsomWe have four minutes. I would like to close on this20:57
rm_workQ-3?20:57
johnsomYes20:57
rm_workis it a "feature"?20:57
rm_workk and that's ... mid-Jan?20:57
johnsomYes.20:57
rm_workk... I just won't have time until January20:57
rm_workbut THEN maybe I could look at it ... MAYBE.20:57
rm_workif it's not done yet20:57
johnsomOk, so decided to make it upgrade compat.  We can figure out how/when it gets done later.20:57
rm_workk20:58
rm_workwhat DIDN'T we get to20:58
johnsom Interface driver support and Members API Improvements Proposal20:58
nmagnezibar is not around20:58
nmagneziand.. we have like a min for it..20:59
cgoncalvesyeah...20:59
rm_workyeah i was mostly just curious20:59
johnsomRight.20:59
johnsomOk, thanks for a lively meeting today.  We got through some of it.20:59
johnsomcgoncalves If you can hang around for a minute we can talk about your topic20:59
rm_workyeah i'm good for a few min too21:00
johnsom#endmeeting21:00
*** ssmith has quit IRC21:00
*** openstack changes topic to "Welcome to LBaaS / Octavia - Queens development is now open."21:00
openstackMeeting ended Wed Dec 13 21:00:06 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-12-13-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-12-13-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2017/octavia.2017-12-13-20.00.log.html21:00
cgoncalvesI'm okay with that, not sure about other folks21:00
johnsomThis is just an informal chat about the topic, it's a good topic for the weekly meeting oto21:00
johnsomtoo21:00
*** kpalan1 has left #openstack-lbaas21:00
xgerman_k21:00
johnsomSo, the middle story, https://storyboard.openstack.org/#!/story/168522321:01
johnsomI am tempted to close as a duplicate to "we need an install guide"21:01
cgoncalvesok. not sure it has got your (cores) attention yet to those storyboards/launchpad bugs21:01
cgoncalvesthere are 2 main problems with the current approach21:01
johnsomYeah, we have had some isssues with storyboard not notifying21:01
cgoncalves1) subnet collision because o-hm0 is on root namespace21:02
johnsomWell, it is super clear you can't use the devstack solution in production, that was never intended21:02
cgoncalves2) dependency on the deployment tool to create o-hm021:02
openstackgerritSanthosh Fernandes proposed openstack/octavia master: [WIP] ACTIVE-ACTIVE create distributoe flow  https://review.openstack.org/52778421:02
johnsom#1 how so?21:02
cgoncalvesjohnsom: o-hm0 is on root namespace, agree? it has an IP address so...21:03
johnsomo-hm0 is just a port for devstack. It should not be used necessarily in production21:03
cgoncalvesthus an  ip route entry also gets added to the route table21:03
nmagnezijohnsom, yeah but it translates to a NIC, which adds entry in the routing table21:04
johnsomRight, so don't do that21:04
nmagneziso.. how do you do it?21:04
cgoncalvesyes, but if the ip address assigned is e.g. 192.168.0.100 which might collide with existing subnets21:04
cgoncalvesor am I getting it wrong?21:04
johnsomDo what works for your deployment.  Those calls all route, if routing works better for your deployment, do that.21:04
cgoncalvesyes, right21:05
johnsomIf you want to setup a NIC, create a namespace, the network config files, and run it in a namespace21:05
rm_workwhat existing subnets?21:05
cgoncalvesthe idea now would be to find a way to not be dependent on the deployment tool21:05
johnsomI think OpenStack Ansible puts it all in a container.21:05
rm_workah wait, this is for HM21:06
xgerman_yep21:06
rm_worki forget what this one even is >_<21:06
rm_workwe don't use this21:06
johnsomrm_work yeah, how control plane talks to amps21:06
xgerman_anibsle puts all services in the same container21:06
xgerman_9for now)21:06
cgoncalvesyes yes :)21:06
rm_workoh21:06
rm_workyou mean mgmt-net?21:06
rm_worknot hm21:06
cgoncalveso-hm0 = octavia health manager :)21:06
johnsomRight, it's really about the lb-mgmt-net21:06
xgerman_most deployments have different network setup so it’s hard for us to prescrive a solution21:07
rm_workisn't that the ONLY thing plugged in the root namespace?21:07
johnsomxgerman_ +121:07
johnsomrm_work That is up to the deployer21:07
xgerman_all we need is connectivity between the amps and the hm-port21:08
cgoncalvesrm_work: it is, I believe21:08
nmagnezixgerman_, and the worker as well, right?21:08
xgerman_it doesn’t necessarily need to be a subnet — could also be some routable thing21:08
xgerman_nmagnezi the worker needs outbound connectivity and hm inbound21:09
cgoncalvesthe suggested approach in LF/storyboard is to put o-hm0 in a seperate namespace and find another way (not relying on the deplpoyment tool) to create it21:09
johnsomRight, this is fully routable, so it does not need to be L2 at all21:09
xgerman_should have been ore precise21:09
xgerman_more21:09
cgoncalvesso, perhaps os-vif could be something we could explore21:09
johnsomcgoncalves Tell me more?21:10
xgerman_yes - but you also need to run it inot a neuwron network21:10
xgerman_so unless you have flat there a vif won’t solve all your problems21:10
johnsomI can think of at least five options for how to implement this network.21:11
xgerman_yep21:11
cgoncalvesjohnsom: long story short: os-vif could handle port creation on the host plus being vendor-agnostic21:11
johnsomAll of which need to go into an install guide whenever we get time to write it.21:12
xgerman_and the network the hm connects to and the one the vm connect to are separate problems (and you cna bridge them together if needed)21:12
cgoncalvesthe deployer selects the network driver (same as the one setup in ml2, for instance) and os-vif would handle it21:12
johnsomcgoncalves Can you go into detail on how that would work?21:12
cgoncalvesI'm still quite in early phase exploring it, so be easy on me :)21:12
cgoncalvesjohnsom: os-vif user API consists only on 2 funcs: plug and unplug21:13
nmagnezijohnsom, from what I know, Nova uses os-vif for plugging stuff as well21:13
cgoncalvesnmagnezi: yes21:13
xgerman_nut you can also do a neutron net-create —provider flat:oct or so21:13
johnsomRight for nova instance, but this is not necessarily a nova instance, or even a host with neutron on it21:14
xgerman_yep, we need a real network - not. aneutron one21:14
cgoncalvesright, even though os-vif docs mention instance as being a nova instance I couldn't find any strict relationship with nova21:14
cgoncalvesso could be literally any resource you want21:14
cgoncalveshttps://docs.openstack.org/os-vif/latest/user/usage.html21:15
cgoncalveshttps://docs.openstack.org/os-vif/latest/user/vif-types.html21:15
johnsomBasically our devstack plugin is simulating the controller having a physical nic plugged into a switch that has a VLAN for the lb-mgmt-net.  It's just a simple setup for devstack.21:16
xgerman_mmh, so you would do hm->vif->ovs->amp21:16
cgoncalvesone thing missing in os-vif is namespace aware21:16
xgerman_and then you hope ovs will tunnel that to the other hosts?21:17
xgerman_cgoncalves: you can always add another bridge21:17
*** threestrands has joined #openstack-lbaas21:18
*** threestrands has quit IRC21:18
*** threestrands has joined #openstack-lbaas21:18
cgoncalvesif you create a neutron port and then feed the details to os-vif it should configure the vif to be on the same net21:18
*** sshank has joined #openstack-lbaas21:18
cgoncalvesI just wanted to bring this topic to your attention at this point and get your thoughts about the current approach vs next-gen if agreed it's the way to move forward21:19
xgerman_it’s now what I am using but it sounds feasible… so yeah, let us kn ow if it works ;-)21:19
cgoncalveswill do!21:20
nmagnezicgoncalves, tripleO will eventually deploy each Octavia service in it's own container. so maybe the fact that os-vif is not network namespace aware is not that of an issue21:20
xgerman_I am quite happy with vlan or whatever topology the DC has21:20
cgoncalvesnmagnezi: true, though is still deployment tool constraint21:20
xgerman_yeah, os_vif might let you bypass the need for an extra VLan21:20
johnsomI just don't understand what os-vif brings.  It's essentially just a library doing the same thing our plugin script is doing.  The downside is it expects OVS and the neutron network to exist on all of the control plane hosts/containers.21:20
cgoncalvesif one deploys with devstack he would get the same problem, no?21:21
xgerman_johnsom: my understanding is you could save the extra vlan by plugging straight i ti ovs and let it do the tunneling21:21
xgerman_cgoncalves: in my AIO deploys I simulate a provide rnet with an extra (linux) bridge21:22
johnsomNo21:22
johnsomos_vif doesn't do any magic tunneling21:23
johnsomOVN can do things like that, but this is purely creating a bridge into an OVS or linux bridge.21:23
nmagneziit doesn't. but it allows you to interact with an interface driver that does21:23
nmagnezisuch as ovs21:23
cgoncalvesit can handle bridging and tunneling. at least there are parameters for those21:23
cgoncalvesnmagnezi: right21:23
johnsomFrom what I have seen of it, it is exactly the same as our plugin.sh script, just abstracted and pythony21:24
nmagnezijohnsom, and not hard coded to ovs. which is important..21:24
cgoncalvesright, which is good because of a) abstraction and b) deployment tool agnostic21:25
johnsomOh, as requires a nove instance, but that isn't clear I guess21:25
cgoncalvesjohnsom: it does not require nova instance21:25
johnsomWell, our plugin.sh isn't hard coded to OVS either, it supports linux bridge21:25
cgoncalvesjohnsom: the instance object contains: uuid, name, project_id. even though doc mentions nova instances, there's no real constraint on nova21:26
johnsomcgoncalves So what do you put in for vif_objects.InstanceInfo.uuid then?21:26
nmagneziyup. that's actually true (forgot about that). but we'll also gain the option to support 3rd party interface drivers21:26
nmagneziwhich neutron do allow21:26
cgoncalvesjohnsom: whatever you want? :) o-hm id? :)21:26
*** gcheresh has quit IRC21:26
johnsomI think you need to spend some more time with that code. All of my interactions say that will fail, but I have also not spent time with it.21:29
cgoncalvessure. I need to put more time on it21:29
johnsomI mean if you want no vlans setup a vxlan neutron network and tunnel it into your controllers.21:30
cgoncalvesagain, wanted initially to get an ack from devs about the mentioned issues21:30
johnsomIs what you are trying to solve that you install the control plane package and it automatically connects out to the lb-mgmt-net?21:30
cgoncalvesyes21:31
johnsomWe have to configs in place for devstack, neither of which are right for a deployment or production.  Everyone does it differently, some setup provider nets, some install on neutron nodes and bridge, some setup vxlan tunnels, some just do routing, etc.21:32
cgoncalvesthe health manager service would init os-vif and request the plugging21:32
johnsomSome run IPv4, some IPv621:33
johnsomSo, the first step towards your goal would be figuring out the discovery part.  Where is the lb-mgmt-net and how is it accessible. VPN, vxlan, vlan, routing, local bridge to neutron/ovs/ovn, etc.21:34
cgoncalvesallow me to explore a bit more and present my findings a little bit clear21:34
johnsomOk21:34
nmagneziit's almost midnight here. calling it a day :)21:34
johnsomo/21:34
nmagnezicgoncalves, we'll sync tomorrow21:34
cgoncalvesnmagnezi: alright21:34
cgoncalvesthanks everyone!21:34
nmagnezijohnsom, thank you for taking the time. I'll catch up on this.21:34
johnsomSorry, I'm not trying to be argumentative, I just think there are details missing here. so trying to find answers21:35
nmagnezino! don't stop because of me :D21:35
cgoncalvesI also need to actually xD21:35
nmagnezihah21:35
openstackgerritHengqing Hu proposed openstack/octavia master: Add element and flag to disable DHCP on amp images  https://review.openstack.org/52059021:35
nmagnezijohnsom, would a spec make sense here?21:35
nmagnezior are we even before that stage in this point21:36
cgoncalvesnmagnezi: I would think so, but first would like to present something less "formal"21:36
johnsomMight be early for that, but a detailed spec could help21:36
xgerman_+121:37
*** longstaff has quit IRC21:50
*** longstaff has joined #openstack-lbaas21:53
*** AlexeyAbashkin has joined #openstack-lbaas21:54
*** AlexeyAbashkin has quit IRC21:58
*** rcernin has joined #openstack-lbaas22:00
*** alex_staf_1 has quit IRC22:14
*** bar_ has joined #openstack-lbaas22:15
*** sshank has quit IRC22:23
*** sshank has joined #openstack-lbaas22:23
*** ssmith has joined #openstack-lbaas22:24
rm_workaugh another rebase time22:44
rm_worki think...22:45
rm_workhmmm22:45
openstackgerritAdam Harwell proposed openstack/octavia master: WIP: Floating IP Network Driver (spans L3s)  https://review.openstack.org/43561222:46
rm_workmaybe not but this makes very little sense to me22:46
*** harlowja has quit IRC22:54
*** longstaff has quit IRC22:59
*** alex_staf_1 has joined #openstack-lbaas23:16
*** sshank has quit IRC23:17
*** yuanying has joined #openstack-lbaas23:18
*** alex_staf_1 has quit IRC23:20
rm_workahhhhhhhhhhh lame23:27
rm_worksomeone did not do a copy right23:27
rm_workdamnit blogan23:28
bar_rm_work, what's wrong?23:28
rm_workwas wondering how i got a random failure23:28
*** sshank has joined #openstack-lbaas23:28
rm_workone test is altering the test constants23:28
rm_workso other tests that use them break23:28
bar_rm_work, can you please share a link?23:29
rm_worklet me see...23:29
bar_I wonder whether that patch has got into one of my patches23:30
bar_*that test got into23:30
rm_workhttps://github.com/openstack/octavia/blob/master/octavia/tests/unit/network/drivers/neutron/test_allowed_address_pairs.py#L408-L41123:30
rm_workit's been in there for a long time23:30
rm_workbut we weren't using those fields until recently23:30
rm_worknow that we check for them... this is a problem23:31
rm_workit should be copy.deepcopy23:31
rm_workbecause it's just a wrapper dict... so just a "copy"23:31
rm_workdoesn't do much23:31
rm_workbasically nothing in fact :P23:31
bar_yeah, I got exactly the same error (here: https://review.openstack.org/#/c/505158/), but only with py27, not py35. any thoughts of why?23:32
bar_rm_work, Do you want me to patch it?23:35
rm_workit has to do with run order23:35
rm_workit's random23:35
rm_workso not consistent23:35
rm_worki patched it in my patch23:35
rm_workyou're welcome to patch it in yours too23:35
rm_workone of them will land23:35
rm_workand it's a pretty straightforward rebase :P23:35
openstackgerritAdam Harwell proposed openstack/octavia master: Add unit tests for neutron utils, add model/util for floating_ip  https://review.openstack.org/52535323:36
openstackgerritAdam Harwell proposed openstack/octavia master: WIP: Floating IP Network Driver (spans L3s)  https://review.openstack.org/43561223:36
*** tongl has quit IRC23:39
*** tongl has joined #openstack-lbaas23:40
*** harlowja has joined #openstack-lbaas23:42
*** armax has quit IRC23:44
openstackgerritBar RH proposed openstack/octavia master: Improve Neutron driver _get_resource()  https://review.openstack.org/52719923:46
rm_worki'm still +223:50
bar_rm_work, thx!23:50
rm_workstill would appreciate reviews on https://review.openstack.org/#/c/525778/23:50
rm_workwould ideally like to get that merged23:50
rm_workalthough actually might tweak it a tiny bit <_<23:51
*** tongl has quit IRC23:53
*** longstaff has joined #openstack-lbaas23:56
*** fnaval has quit IRC23:57
bar_rm_work, I've been eyeing it for a while. The relate patch, Floating IP Network Driver, seems quite big. Did you think of dividing it to even more patches?23:58
rm_worki don't intend that to merge even close to now23:58
rm_workthat's Work In Progress23:58
rm_workand it's what we use downstream23:58
rm_workyou can safely ignore that patch23:58
bar_ah23:58
rm_workI just put it up in case anyone wants to look23:59
*** tongl has joined #openstack-lbaas23:59
rm_workand it makes my process easier23:59
rm_workthat's the driver we run internally right now23:59
rm_workit *works*, but only in our specific cloud23:59
bar_right23:59

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