17:02:30 <timsim> #startmeeting designate
17:02:31 <openstack> Meeting started Wed Jun 28 17:02:30 2017 UTC and is due to finish in 60 minutes.  The chair is timsim. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:02:35 <openstack> The meeting name has been set to 'designate'
17:02:37 <timsim> #topic Roll Call
17:02:52 <timsim> mugsie daidv trungnv hieulq_
17:02:56 <mugsie> o/
17:02:57 <trungnv_> o/
17:03:33 <sonuk> o/
17:03:44 <timsim> #topic Announcements
17:03:52 <timsim> anyone want to announce anything? :P
17:04:53 <timsim> Probably not
17:04:55 <timsim> #topic Bug Triage
17:05:07 <timsim> huh. I actually don't see anything new, cool
17:05:13 <mugsie> :D
17:05:28 <timsim> No stable backport needed, last merge was 18 days ago...
17:05:31 <timsim> #topic Open Discussion
17:05:46 <trungnv_> Hi
17:06:14 <timsim> o/
17:06:18 * timsim needs to do code reviews
17:06:30 <trungnv_> I am preparing to test upgrade and OVO code which we coded.
17:06:45 <trungnv_> do you have any suggestion for this test?
17:07:00 <mugsie> add a new record type
17:07:03 <trungnv_> like scenario for OVO testing/
17:07:28 <trungnv_> yep.
17:08:44 <trungnv_> I can test with create, delete, .. with zone and record. this is my scenario at the moment.
17:09:16 <mugsie> trungnv_: adding a new type of record would test it properly
17:09:25 <trungnv_> I will build 2 Node designate along with 1 BIND9 and NGnix for LB.
17:10:14 <mugsie> like a new designate/objects/rrdata_<type>.py
17:10:39 <trungnv_> yep.
17:11:16 <trungnv_> I will look at whole case with record type.
17:11:51 <mugsie> I am currently starting a test system to check OVO
17:12:15 <trungnv_> cool. that is good news for me.
17:13:02 <trungnv_> I hope I get your outcome soon.
17:13:12 <mugsie> yeah - it will be a day or two
17:13:23 <trungnv_> yeah. thanks.
17:14:28 <timsim> Cool, anything else folks want to discuss?
17:14:53 <trungnv_> could I ask you about BIND9 in HA topology?
17:15:03 <mugsie> yeah
17:15:40 <trungnv_> I am not sure what happen with my environment when I remote connect from designate node to BIND9 server.
17:16:22 <trungnv_> I can check created zone on BIND9.
17:16:51 <trungnv_> but when I show it via openstack zone list or check in SQL then ERROR.
17:17:12 <mugsie> we would need to see logs
17:17:33 <mugsie> if it is in error, there will definitly be logs in pool-manager / worker
17:17:34 <trungnv_> any special config for BIND9 and or pool.yaml?
17:17:56 <trungnv_> yep. I also saw it via worker/pool-manager.
17:18:00 <mugsie> no, just add the bind server as normal
17:18:10 <mugsie> what is the error?
17:18:29 <trungnv_> yep. I will check whole things again.
17:18:31 <trungnv_> thanks.
17:19:00 <trungnv_> last question
17:19:08 <trungnv_> about genconfig PS
17:19:26 <mugsie> yup - i left a review earier
17:19:31 <trungnv_> I just got your comments in my PS.
17:20:42 <trungnv_> yep. with centralize backend, I think this donot affected to code-base.
17:21:25 <trungnv_> developer will look at config easier.
17:23:18 <mugsie> as I said a few weeks ago, centralising config is not a good idea, in my opinion
17:23:37 <mugsie> and I dont think we should do both config generation, and centralise config at the same time
17:23:49 <mugsie> config generation can happen before, and shoudl
17:23:53 <mugsie> should*
17:24:10 <trungnv_> sure. I agree with your opinion.
17:24:25 <trungnv_> I will update my PS soon. thank
17:24:37 <mugsie> OK - so if we can clean up that PS, we should merge it soon
17:24:38 <mugsie> :)
17:24:58 <trungnv_> yep. :)
17:26:37 <trungnv_> that's enough for me today.
17:26:41 <trungnv_> thanks
17:27:00 <timsim> Great. Anything else?
17:27:03 <timsim> Going once....
17:28:01 <timsim> twice
17:28:07 <timsim> #endmeeting