14:00:08 <tellesnobrega> #startmeeting sahara
14:00:13 <openstack> Meeting started Thu Jun 28 14:00:08 2018 UTC and is due to finish in 60 minutes.  The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:16 <openstack> The meeting name has been set to 'sahara'
14:01:07 <jeremyfreudberg> o/
14:01:15 <tosky> o/
14:01:19 <zchkun> o/
14:01:34 <tellesnobrega> #topic News/Updates
14:02:01 <tellesnobrega> I'm still waiting for the patch on the openstackclient to land, also I finished upgrade of storm and spark
14:02:17 <tellesnobrega> I'm now giving a try on adding support to ambari 2.6.2.0
14:03:39 <jeremyfreudberg> totally engrossed in S3 stuff
14:04:09 <tosky> I tested the fix for CDH/extjs, and working on the devstack-plugin-ceph to prepare the S3 testing
14:04:13 <zchkun> I'm in process of MapR6 upgrade
14:04:46 <tellesnobrega> awesome
14:04:48 <jeremyfreudberg> sounds like we are all hard at work
14:04:52 <tellesnobrega> yes
14:05:28 <tellesnobrega> #topic OpenStack PTG
14:05:43 <tosky> this time at the beginning of the week
14:05:59 <tellesnobrega> you all have probably seen the email we are booked for monday and tuesday
14:06:08 <jeremyfreudberg> was that intentional?
14:06:11 <tellesnobrega> does that work for everyone?
14:06:15 <tellesnobrega> not from us
14:06:34 <jeremyfreudberg> it should be fine
14:06:39 <tellesnobrega> I think they changed the order this time
14:06:50 <tellesnobrega> individual projects and later the cross-projects stuff
14:07:01 <tellesnobrega> ok, since it works for everyone I will let it be this way
14:07:03 <jeremyfreudberg> to be more specific, i can only ever go at most 3 out of 5 days, if we are monday tuesday then i can visit API SIG and stuff which will be nice
14:07:21 <tellesnobrega> I have to change my hotel booking, because I had schedule from monday to saturday,
14:07:32 <tellesnobrega> awesome
14:07:50 <tellesnobrega> lets keep monday and tuesday
14:08:01 <jeremyfreudberg> well, unless we want tuesday-wednesday
14:08:14 <tellesnobrega> I will start an etherpad later so we start gathering topics
14:08:20 <tellesnobrega> either way works for me
14:09:11 <jeremyfreudberg> i might be slightly in favor of tuesday-wednesday, because it gives us some freedom on monday.... freedom on thursday and friday doesn't help us
14:09:55 <tellesnobrega> tosky, do you have any preferred days?
14:09:59 <tosky> I still don't know about my travel, so I can't really point out anything
14:10:24 <tosky> Monday-Tuesday would give me one or two days for QA (which starts on Wed iirc)
14:11:35 <tellesnobrega> ok, I will send out an email on the ML later so we can decide which days are best for us
14:11:53 <jeremyfreudberg> sounds good
14:12:17 <tellesnobrega> tosky, what are the topics you want to discuss?
14:12:28 <tellesnobrega> so I can change accordingly
14:13:01 <tosky> tellesnobrega: now or for the PTG?
14:13:08 <tellesnobrega> now
14:13:44 <tosky> oh, ok, more general reminder about something that we did in the past and we should do again
14:13:50 <tosky> doc review and story cleanup
14:14:03 <tellesnobrega> #topic Doc Review and Story Cleanup
14:14:07 <tellesnobrega> you have the floor
14:15:11 <tosky> The topic should be self-explanatory, I think that we should give some focus on those topics again before Rocky
14:15:35 <tosky> we did a doc review before Queens, but with no many action items (I think that tellesnobrega and jeremyfreudberg  pushed few changes at least)
14:15:38 <tellesnobrega> do you want to organize a doc review day?
14:15:53 <tosky> yeah, maybe focus on few topic: I would personally get the image building
14:16:09 <tosky> reorganize it throughout the existing page to remove duplications and inconsistencies
14:16:21 <tosky> and so on
14:16:25 <tellesnobrega> we can send an email on ML to start organizing a day that works best for everyone
14:16:48 <tellesnobrega> I totally agree that we need it
14:17:02 <tosky> probably not next week, with holidays in the US, and after 9th (which seems to be holiday in Brazil)
14:17:13 <tellesnobrega> sure
14:18:03 * jeremyfreudberg reminds tosky that jeremyfreudberg is gone the weeks of july 16 and july 23
14:18:09 <tosky> okidoki
14:18:13 <tosky> we can do also more sessions
14:18:20 <tellesnobrega> of course
14:18:44 <tosky> apart from documentation, I'm not sure if we went through stories recently; I did it through few of them while looking for one, and probably we need to recheck the status
14:18:44 <tellesnobrega> we can set up a first and do more sessions after that one
14:18:59 <tellesnobrega> sounds good too
14:19:01 <tosky> apart from bugs, there were few requests that are small enough that could be squeezed in
14:19:09 <jeremyfreudberg> yes, we definitely have some intereesting stories out there
14:19:16 <tosky> but we probably lack a general picture right now
14:20:01 <tosky> just remember that when you list all the stories for a project, storyboard shows a story as active if there is at least one task still open, even if it's for a different project
14:20:09 <tosky> so the number is slightly smaller than what you see
14:20:15 <tosky> but still, big enough :)
14:20:32 <tellesnobrega> tosky, can you send out the email so we can set it up?
14:20:37 <tosky> oki
14:20:44 <tellesnobrega> thanks
14:21:09 <tellesnobrega> anything else on this topic?
14:22:00 <tosky> not from me
14:22:33 <tellesnobrega> tosky, do you have other topic you want to discuss? jeremyfreudberg or zchkun as well?
14:23:05 <jeremyfreudberg> i'd like to hear about mapr6
14:23:31 <jeremyfreudberg> if there are any problems with the upgrade so far
14:23:52 <tellesnobrega> lets go to open discussion
14:23:55 <zchkun> I am testing to build  mapr5.0.1 image, but it is fault
14:24:01 <tellesnobrega> #topic Open Discussion
14:24:15 <tellesnobrega> mapr 5? or 6?
14:25:05 <zchkun> I prepare to build 6, but first want to test 5
14:25:28 <tellesnobrega> what issue are you seeing with the 5 image?
14:25:51 <tellesnobrega> are you using sahara-image-elements or sahara-image-pack?
14:26:08 <zchkun> sahara-image-elements
14:26:26 <tellesnobrega> try with sahara-image-pack
14:26:30 <tellesnobrega> it should be better
14:26:49 <zchkun> ok
14:27:35 <zchkun> what different  sahara-image-elements and sahara-image-pack?
14:28:18 <tellesnobrega> sahara-image-pack uses libvirt to manipulate the images and SIE uses diskimagebuilder
14:28:55 <tosky> oh, that reminds me another topic (but later)
14:29:18 <tellesnobrega> there some key differences like security, and the fact that sahara-image-pack can work on images and if it fails it will start from the failure, it won't install hte whole thing again
14:29:29 <tellesnobrega> but they should be similar on the content of what is in the image
14:29:48 <tosky> in fact, if you execute sahara-image-pack on an almost-ready image, it should complete the preparation
14:30:03 <tellesnobrega> yes
14:30:36 <tellesnobrega> and we should start using it more often since we plan to drop support to sahara-image-elements and keep only sahara-image-pack
14:32:06 <zchkun> sound good,  got it , I will try it
14:32:12 <tellesnobrega> zchkun, let me know or jeremyfreudberg or tosky if you ran into troubles
14:32:23 <tellesnobrega> don't need to wait for the meeting, just ping us
14:32:45 <zchkun> ok, thanks
14:33:04 <tellesnobrega> tosky, go ahead on the topic you wanted to talk
14:33:43 <tosky> related to sahara-image-pack
14:34:55 <tosky> if I'm not mistaken, the validation stage which happens during cluster provisioning is (if I'm not mistaken) the same recipe executed by sahara-image-pack
14:35:05 <tosky> but with the test_only parameter set?
14:35:27 <tellesnobrega> it is the same recipe
14:35:33 <tellesnobrega> I can't remember if the test_only is set
14:35:41 <tellesnobrega> but you are probably right
14:35:46 <tosky> the related question is: in some plugins, or at least in the current mapr, there is some code to do the configuration, which duplicated the image creation process
14:35:51 <tosky> duplicates*
14:36:04 <jeremyfreudberg> i think i had this question the other day too
14:36:10 <tosky> and that was one of the reason for the unified validation + image building process (reduce the duplication)
14:36:20 <jeremyfreudberg> whether validation just means validation(checking), or actual fixing(doing)
14:36:30 <tosky> but this means that we could cut this old code, solving issues like https://storyboard.openstack.org/#!/story/2001965
14:37:09 <tosky> if the validation is fixing/doing, it's all fine; if the validation is just checking, we could try to find a way to enforce doing in some condition
14:37:17 <tosky> and still cut old code
14:37:45 <tellesnobrega> we can set the validation to fix as well
14:37:59 <tellesnobrega> just remove the test_only if it is in fact set
14:38:04 <tellesnobrega> I will have to double check
14:38:15 <tellesnobrega> and i agree that we can remove old code not doing anything
14:38:30 <tosky> to be precisse, it's doing something, just duplicate
14:38:43 <tellesnobrega> true
14:40:15 <tosky> and that's it from my side
14:40:48 <tellesnobrega> from me as well
14:40:54 <tellesnobrega> jeremyfreudberg, zchkun?
14:41:09 <jeremyfreudberg> that's it from me
14:41:28 <tosky> justremembertheopenreviewswitha+2
14:41:48 <tosky> and also the ones without any
14:42:00 <tellesnobrega> yes, thanks
14:42:02 <tellesnobrega> ok, lets close it. thanks all
14:42:08 <tellesnobrega> #endmeeting