14:00:15 #startmeeting sahara 14:00:16 Meeting started Thu Jul 25 14:00:15 2019 UTC and is due to finish in 60 minutes. The chair is jeremyfreudberg. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:20 The meeting name has been set to 'sahara' 14:00:23 o/ 14:00:30 o/ 14:00:35 o/ 14:00:46 #topic news/updates 14:01:29 I have news :) 14:01:42 was looking at sahara image pack for storm, in the process of becoming of familiar with sahara image pack i ran into an issue, more on that later 14:01:46 tellesnobrega, let's hear it 14:01:53 I'm working on Mapr bug that luigi found 14:01:58 simple image check 14:02:05 but that showed a couple more python 3 issues 14:02:08 and soon other bugs :) 14:02:16 I'm working on them now 14:02:20 yeah, we are basically ironing out a few python3 porting bugs 14:02:39 running scenario now 14:02:50 cool 14:02:53 1 job finished successfully other are pending 14:02:55 not sure why 14:03:04 but looks like the issue on MapR is done 14:03:09 patches coming soon 14:03:13 until I properly test it :P 14:03:41 #topic train-2 14:03:53 tosky, yes :) 14:03:57 i assume no releases need for train-2, but correct me if i'm wrong 14:04:44 I'm not sure, tosky can confirm that 14:04:59 I think yes; maybe there should be a sahara-tests release, but to be honest I lost track of the changes they made to the release model to account for the tempest plugins 14:05:09 (not always in a direction that I totally agree with) 14:06:28 okay 14:07:07 happy to ack where needed, but i'm not sure either about the specifics either 14:07:11 ok, no need; right now sahara-tests for train is cycle-automatic 14:07:18 aha 14:07:51 if we need more release of it in train we can always revert it to cycle-with-intermediary 14:08:01 right 14:08:19 moving on 14:08:42 #topic sahara-image-pack issue 14:09:05 as i said, i intend to get storm on sahara-image-pack, at least 14:09:16 but i ran into an issue building a spark image along the way 14:09:23 http://paste.openstack.org/show/754852/ 14:09:39 you can scroll to the end, most likely 14:09:48 oh no, it's cut off 14:09:54 so ignore that pastebin for a second 14:09:57 it is cut off 14:10:49 I remember a few fixes for ubuntu being merged in the previous cycle (thanks to an external contributor), maybe a few others are needed 14:11:19 https://pastebin.com/LHT9iPux 14:11:35 scroll to the end (i doubt anything at the beginning is really relevant, but you never know) 14:11:54 it says moving spark to /opt, but then the next command says that the directory does not exist 14:11:58 jeremyfreudberg: which ubuntu version? 14:12:02 bionic 14:12:24 I think we support it on xenial 14:12:33 maybe it's not related 14:12:39 wait a minute, no it's not bionic 14:12:46 it's actually trusty......... 14:13:31 if you open the image, is /opt/stark populated? 14:14:21 i'll have to check later 14:14:37 oki 14:15:01 maybe i'll run the buildimages job (experimental queue) for now and at least see if it works on centos 14:15:29 yep, even though I may have tested it on ubuntu as well; let's see 14:16:09 jeremyfreudberg, I think I've seen this before 14:16:55 iirc there is a step to create /opt/spark on the image 14:17:01 for some reason its not running 14:17:56 seems like at least the echo statements in this file are being executed https://github.com/openstack/sahara-plugin-spark/blob/7af450e34d30088d5d409915bfc32c955f52410b/sahara_plugin_spark/plugins/spark/resources/images/common/install_spark 14:18:17 i will look some more, unless you already know how to resolve it 14:18:19 but it is running - see "Received response: Downloading SPARK" 14:18:55 echo "Moving SPARK to /opt/" 14:18:55 # Placing spark in /opt/spark 14:18:55 mv $extract_folder /opt/spark/ 14:18:55 mv $tmp_dir/spark_url.txt /opt/spark/ 14:19:18 this should have created the folder 14:20:44 try adding a new echo there to make sure the folder is created 14:20:50 but I can't remember how it was solved 14:21:05 i'll keep working on it and try to better diagnose it 14:21:07 thanks 14:21:27 #topic open discussion 14:22:22 I was going to ping tellesnobrega for the open reviews, but it looks like he is going through them, thanks! 14:22:36 tosky, do you have anything to say about the new tripleo job that you are adding? 14:22:40 also, restarting old discussions, I proposed a tripleo standalone job 14:22:43 tosky, yes 14:22:47 sorry for the delay 14:22:58 it's useful to catch and prevent cross-breakages 14:23:31 on the same line, I think we discussed long time ago about adding an openstack-ansible-os_sahara job; if you agree with both, I may add them in the same change 14:24:10 yeah, i do recall an old discussion about that, i'd be fine adding the osa job too 14:24:24 so we would cover 3 installers: devstack (ok), tripleo (which at the moment still uses puppet, so that's covered; even though they are planning to move away); and os-ansible 14:25:26 fine by me 14:25:38 ok, thanks; let me update the job then 14:26:22 tosky, my only comment would be, is it worth doing more than just the api tests 14:26:35 i mean, should we do scenario tests 14:27:16 I'm not sure whether it could work, but I can try; it may take a bit more work 14:27:30 more than a bit 14:27:43 it can be a followup, for sure 14:28:06 I will try to understand how complicated is to extend it 14:28:20 okay 14:29:14 anything else today? 14:29:35 not from me 14:31:29 nothing else from me right now 14:31:52 okay 14:31:55 let's close 14:31:56 thanks all 14:32:21 thanks! 14:34:12 #endmeeting