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