17:00:13 <timsim> #startmeeting designate
17:00:17 <mugsie> o/
17:00:18 <openstack> Meeting started Wed Jul 12 17:00:13 2017 UTC and is due to finish in 60 minutes.  The chair is timsim. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:21 <openstack> The meeting name has been set to 'designate'
17:00:33 <timsim> #topic Roll Call
17:00:39 <mugsie> hey
17:00:50 <trungnv_> o/
17:01:04 <daidv> o/
17:01:41 <timsim> sonuk hieulq
17:02:49 <timsim> skipping over some stuff
17:02:53 <timsim> #topic Stable Backport Triage
17:03:10 <timsim> http://paste.openstack.org/show/615189/
17:03:20 <timsim> Anything in there worth bp'ing?
17:03:37 <mugsie> a989d0d Merge "Ensure TTL is not 0 for zone imports"
17:03:51 <mugsie> abvout it
17:03:54 <mugsie> I can take that
17:04:09 <timsim> Alright, sweet. Sounds good
17:04:23 <timsim> #topic Open Discussion
17:04:41 <mugsie> I am about 1/2 way through OVO testing
17:04:49 <trungnv_> yep
17:04:52 <mugsie> but - I will have a list of thing that need to change
17:04:57 <daidv> nice :D
17:05:12 <timsim> woo
17:05:13 <daidv> Can you let me and trungnv_ know that?
17:05:17 * mugsie broke his devenv last week
17:05:22 <mugsie> so still fixing that
17:05:32 <mugsie> I will, as soon as I have a list, I will review it
17:05:35 <mugsie> and add the comments
17:05:51 <trungnv_> yep. thanks.
17:05:55 <daidv> thanks
17:06:09 <mugsie> no problem
17:07:31 * timsim is looking at code reviews quickly
17:08:22 <timsim> Anyone have anything else they'd like to discuss?
17:08:32 <daidv> does we have any other topics?
17:08:32 <mugsie> we also need to think about how to fix up mdns - it does not use objects
17:09:13 <trungnv_> with OVO code-base?
17:10:01 <mugsie> no, but for zero downtime it needs to deal with different DBS
17:10:06 <mugsie> DB schema
17:10:15 <mugsie> OVO would cause performance issues
17:10:54 <trungnv_> yep. we also have a schedule to working on OSM after OVO well done.
17:13:18 <timsim> I need to turn my irc notifications off at night, 1am pings are not fun :P
17:14:08 <mugsie> timsim: :D
17:14:20 <mugsie> at least your watch doesnt vibrate :P
17:14:21 <trungnv_> timsim, sorry about that. We will look at time-zone before ping you.
17:14:26 <timsim> No worries.
17:14:38 <timsim> I'll have to think about how mdns would work.
17:14:47 <timsim> It'd probably be fine because of how limited those queries are.
17:14:52 <mugsie> yeah
17:15:08 <timsim> But if the db were unavailable for a time....eh it'd probably retry.
17:15:53 <mugsie> maybe ....
17:15:58 * mugsie isnt actually sure
17:16:07 <trungnv_> yep. I saw this issue when I upgrade and replace services to new version.
17:16:12 <daidv> mugsie: you are talking about DBS
17:16:31 <daidv> By the way, I want to ask about rolling upgrade in Designate?
17:16:54 <daidv> Because we just had a upgrade testing with Designate but.
17:17:15 <mugsie> well, mini dns would need to be fixed first
17:17:29 <daidv> we can have the diffrent version running in the same time.
17:17:37 <daidv> because of RPC :(
17:17:49 <mugsie> sure - rpc isnt an issue
17:18:04 <mugsie> that works now, and worked on older versions
17:18:22 <mugsie> rpc will just put the message back on the queue if it cannot deal with the verison
17:18:51 <daidv> mugsie: I don't see any thing like pin RPC version in Designate upgrade, right?
17:19:12 <mugsie> ?
17:19:13 <daidv> so it is the reason
17:19:27 <daidv> that we must turn off all of Designate service during upgrade?
17:19:34 <mugsie> we shouldnt need to pin anything?
17:19:41 <mugsie> what are you trying to pin?
17:19:45 <mugsie> olso.messaging?
17:19:58 <daidv> RPC version.
17:20:01 <daidv> yep,
17:20:11 <mugsie> thats not needed
17:20:23 <daidv> Humm.
17:20:40 <trungnv_> I saw worker call mdns to retry create/del when upgrade and replace pool-manager and zone-manager to worker and producer.
17:21:16 <mugsie> well, with pool-manager -> producer, that was different APIs
17:21:17 <trungnv_> if keep services in new version then this issue don't occurred.
17:22:15 <mugsie> but normal upgrades are fine
17:22:23 <trungnv_> Should we fix mdns issue in this case. right?
17:23:25 <mugsie> no, not this case
17:23:34 <mugsie> we need to fix the mini dns and DB
17:23:56 <daidv> mugsie: normal upgrade with something like canary can't work.
17:24:26 <daidv> we have used NGINX for HA two Designate node.
17:24:44 <daidv> and when we upgraded the first one
17:25:11 <daidv> we will get the error about RPC in logging
17:25:33 <mugsie> I would need to see logs
17:26:35 <trungnv_> mugsie, we will make video and log and send you in next meeting.
17:26:46 <mugsie> OK
17:27:05 <timsim> Alright, anything else to discuss?
17:27:23 <trungnv_> that all for me. thanks
17:27:41 <daidv> No thanks.
17:28:10 <timsim> Alright, see you in #openstack-dns
17:28:21 <daidv_> see u
17:28:24 <timsim> #endmeeting