14:00:14 #startmeeting sahara 14:00:15 Meeting started Thu Aug 24 14:00:14 2017 UTC and is due to finish in 60 minutes. The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:18 The meeting name has been set to 'sahara' 14:00:49 o/ 14:00:53 o/ 14:01:17 hi 14:01:48 lets wait a couple minutes to see if anyone else shows up 14:03:57 #topic News/Updates 14:04:17 I just finished preparing the schedule for the Queens PTG 14:04:26 #link https://etherpad.openstack.org/p/sahara-queens-ptg 14:04:49 I encourage all of you to take a look and suggest improvements 14:05:08 and it's pretty packed! 14:05:12 a lot of stuff to discuss 14:05:17 investigating the scale up and down failed if user update cluster name before scaling 14:05:29 will look it later 14:05:33 for sure, it is going to be a busy couple of days 14:05:37 shuyingya, that is interesting 14:05:42 sory, i am late 14:05:43 let me know how that goes 14:05:47 trying to improve my patch for sahara-ci, nothing special 14:05:47 no worries esikachev 14:06:24 from my side: the documentation should be settled, all repositories with documentation (doc, release notes, api, etc) have the new theme 14:06:38 I'm also working on CDH 5.9.0 image with new image generation 14:06:53 including sahara-specs (the last forgotten), and a tiny bit of cleanup, with major cleanup coming with/after the PTG, I guess 14:06:54 and we all salute you tosky for making that happen 14:06:55 no updates from me. I planning to finish my patches for sahara-ci-config 14:07:22 the "no trust creation" was fixed with a team effort, Jeremy and Telles went to nag oslo people 14:08:21 yeah, I believe the final answer came with a talk with adam young from keystone team 14:09:17 we still have an action item in Queens to create a separate configuration section, and update puppet (and at least notify other installers like ansible) about that 14:09:51 true 14:10:15 tosky and telles, really good partner, haha 14:10:20 :) 14:10:23 :) 14:10:38 also, today I will be sending a patch with pike_rc2 14:10:52 please take a look once I send that 14:11:52 I still need to create a patch with the pike templates for sahara-tests, so that we can tag a release (just for reference) 14:12:55 sure, but that is a separated patch right? 14:13:42 I mean, sahara-tests is not cut in the same way as the rest of the project 14:14:00 yes, totally independent 14:14:02 cool 14:14:05 so ignore it for your release :) 14:14:09 :) 14:14:23 :) 14:14:30 #topic Queens PTG 14:15:06 just a heads up, we are very close to PTG, so please get some time to study the discussion topics so we can make the most of our time together 14:15:41 as tosky mentioned to me yesterday, studying all of this will be a great read material for the flight 14:15:56 specially for esikachev and zemuvier (longer flights I believe) 14:16:06 yes, it's true 14:16:14 btw, zemuvier got approved by TSP and will be joining us at the PTG 14:16:30 yep, i will :) 14:16:32 I am interested in how many people will attend sahara PTG this time 14:16:33 \o/ 14:16:47 I believe we have confirmed 5 people 14:17:02 med_, tosky, esikachev, jeremy and zemuvier 14:17:11 sorry med_ 14:17:14 I mean me 14:17:28 nice one more people to Atlanta 14:17:28 double ping) 14:18:16 shuyingya, I will try to see if I can get video conference for you to participate, but as I mentioned I'm not sure it will work, we need good microphones and speakers 14:18:32 so lets see how it goes 14:18:57 at the very least we can try to keep updating the etherpad and you can follow up there and shoot questions 14:19:09 thanks tellesnobrega. The etherpad is always useful 14:19:14 yes 14:19:16 yep 14:19:33 I think this is all I have on the PTG 14:19:55 did any of you had talks accepted for the Sydney Summit? 14:20:27 - 14:21:04 mine not be accepted 14:21:22 I got one and might do a project update on Sahara if i'm confirmed to go there 14:21:29 not sure yet 14:22:11 if anyone is going I would like to know because if I don't make it and someone else does and is willing to do the update it would be awesome as well 14:22:17 lets move on 14:22:59 #topic Open Discussion 14:23:47 how about talking about the name updated cluster scale up failed? 14:23:56 that could work 14:24:04 go ahead 14:24:22 http://paste.openstack.org/show/619327/ 14:25:38 when I updated the cluster name (from old to new), no matter storm or vanilla cluster, all failed at this step 14:26:26 hm, the instaces names are updated as well? 14:26:55 yep 14:27:10 and the fixed ips are changed as well 14:28:11 looks like we are missing some updates here, maybe the instance reference is not updated on /etc/hosts 14:28:21 but the no such file or directory is very weird 14:28:35 I have log out the /etc/hosts 14:28:43 wait a moment 14:29:09 yeah, that's what I am confused 14:30:21 I have to take a deeper look and will test it here, for sure something that needs reporting 14:30:28 please file a bug on it 14:30:59 sure, but I want to get more info to describe it 14:31:05 sounds good 14:31:12 you can always update the bug description 14:31:28 it is good to write a first draft there just so we all know what is going on 14:31:44 I forgot it :( 14:31:45 ok 14:32:10 no worries, just file the bug and once you get more info you update and we can compare notes on what is going on 14:32:36 sounds good 14:32:57 another thing is: 14:33:35 when we support hbase on vanilla, do we need scale up zookeeper or HBase Regionserver? I am not sure. 14:33:51 or maybe I should post a bp to describe it 14:34:07 probably 14:34:30 hmm, I'm not sure either, maybe a bp describing why we need either will be better so we can look up more details and make an informed decision 14:34:47 at least I'm not able to say now what the better option is 14:35:28 In my product, I do scale them, but the code can be kind of intricate 14:35:53 I see 14:36:12 so I will post the bug tomorrow. and write a bp on weekend 14:36:28 please write the bp and/or spec and we can take a look 14:36:53 tellesnobrega, would you try the name updated issue later? 14:37:18 yes, as soon as I'm finished with a downstream task I will try that 14:37:28 you experience would be great helpful I think 14:37:31 hopefully today and at most tomorrow 14:37:39 no worry 14:37:51 It's not blocker for me 14:38:16 cool 14:38:24 just for curiosity 14:38:46 I have no more question :) 14:38:51 cool 14:39:01 does anybody else has other topics to discuss? 14:39:17 not from my side 14:39:34 thanks all 14:39:37 not from me 14:39:49 so I will give you all 20 minutes back 14:39:59 thanks for being here and lets keep up the good work 14:40:01 thanks all 14:40:13 #endmeeting