14:00:37 #startmeeting sahara 14:00:38 Meeting started Thu Jul 19 14:00:37 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:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:41 The meeting name has been set to 'sahara' 14:00:50 #topic News/Updates 14:01:25 I'm currently working on boot from volume, since osc-lib was released. Also I'm working on adding spark to sahara image pack 14:01:53 I was busy with some fixes on openstack-ansible-os_sahara. I'm also trying to push patches around to deploy with unversioned endpoints for puppet, tripleo, etc, but no much success 14:01:58 after I need to take a look at mutable config (community goal) and work on decommissioning of a specific node on the dashboard 14:02:21 and finally, I'm quite sure we have apiv2 set on the client 14:02:24 probably mutable config is more relevant, as it is a community goal 14:02:41 yes, that is what I'm tackling first 14:02:55 oh, I will have also work on testing S3, but that leads to the relevant topic... saharaclient and its release 14:02:58 we need reviews on the boot from volume patches 14:03:14 we can move to this topic 14:03:20 if there are no more updates 14:03:43 #topic saharaclient and its release 14:04:04 you have the floor tosky 14:04:25 next week it's an important milestone; we some time for cleanup in sahara, but we need to release the final client 14:04:56 we know that this version will be a major one (2.0.0) due to this: https://review.openstack.org/#/c/580693/ 14:05:26 yes 14:05:29 we removed a long-deprecated way to setup the authentication (deprecated 3 years ago), so all users should still work as before 14:05:55 but still the signature of the constructor of Client changed, so major version 14:06:22 on the other side we agreed to not have other breaking changes, so the new API for s3 did not break the feature 14:06:40 that said, can we go through the remaining patches for saharaclient and see what's missing? 14:07:21 sure 14:07:31 starting from the bottom of the list, there is a fix that I messed up (submitted with the wrong authorship, then reverted) 14:07:41 this is ready to be merged (again); sorry for the mess: https://review.openstack.org/#/c/582511/ 14:07:53 "Fix the cover tox target (switch to stestr)" 14:08:19 this should be simple enough 14:08:44 approved 14:08:50 thanks! 14:08:51 second in the list there is the backward-compatible support for S3 for data sources "Allow S3 credentials in data source create" https://review.openstack.org/#/c/579680/ 14:09:17 from my point of view is fine, apart from two small changes that were moved to another review 14:10:50 the fixes for it are in "Clean S3 data source create/update" https://review.openstack.org/#/c/582643/, fine by me but it can't be merged directly because it depends on another review (more of that soon) 14:11:26 ok 14:11:31 so +A the firts 14:12:47 moving forward with the triplet, there is "Support of S3 data sources in OSC" https://review.openstack.org/#/c/580727/ 14:13:32 where there is a disagreement between Jeremy and me on the usage of boolean flags, which are usually --enable-something with no parmeters (and the dual --disable-something) 14:13:50 but here it is --something=True/False, which is not a pattern seen on other projects 14:14:03 I tried to ask on #openstack-sdks, I've got only one answer so far 14:14:31 http://eavesdrop.openstack.org/irclogs/%23openstack-sdks/%23openstack-sdks.2018-07-18.log.html#t2018-07-18T17:32:09 14:15:04 it should --enable --disable 14:15:05 for sure 14:16:12 makes more sense 14:16:14 and looks better 14:16:19 easier to understand 14:16:38 slaweq: you asked for this a few weeks ago: https://review.openstack.org/#/c/581487/. haleyb cracked the whip on me while you were away on vacation. hopefully the downstream guys got they wanted 14:17:13 * mlavalle apologizes. wrong channel 14:17:40 no worries 14:17:53 i will comment on the patch 14:18:01 and consistent, at least; I know it may be not the best in absolute terms, but still 14:18:38 and finally, we have the two boot-from-volume patches 14:18:47 python part: https://review.openstack.org/#/c/572536/ 14:18:54 OSC part: https://review.openstack.org/#/c/582319/ 14:19:27 I'm not supposed to merge those Ç) 14:19:28 uhm, I wonder why the latter failed; it is already based on 572536, so it should use it 14:19:29 :) 14:19:33 right :) 14:19:45 just one final question, as we have one pending implementation detail on S3 14:20:02 I think of the updates I removed the dependency 14:20:46 uhm 14:20:55 I will add the dependency back and see if it works 14:21:30 about https://review.openstack.org/#/c/580727/ (S3) apart from the issue with the parameters, it should work even if we manage to implement trasparent uniform support for s3:/ 14:21:41 so I think we should be fine next week 14:21:58 awesome 14:22:15 so to summarize: recheck the boolean argument, test the boot from volume patches, and we can close the client for now 14:22:30 there is the apiv2 part 14:22:36 we could merge as well 14:22:43 I will send a patch soon 14:22:54 so we can see if it will fit 14:23:02 oh, not proposed as patch yet? 14:23:11 notmyname, but it is ready 14:23:24 I will send it today 14:23:27 I guess it was a "not yet" 14:23:28 ok 14:24:40 I don't have anything else about this point, but I felt it was better to have a complete picture 14:26:34 sounds good 14:26:41 I guess we can close it earlier today 14:26:57 yeah 14:27:07 and Jeremy, please think about s3 vs s3a :) 14:27:13 we have some time to fix it 14:28:53 awesome 14:28:54 thanks tosky 14:29:00 #endmeeting