Tuesday, 2018-07-10

openstackgerritTelles Mota Vidal Nóbrega proposed openstack/sahara master: Adding Ambari 2.6 to image pack  https://review.openstack.org/57902400:01
*** masuberu has quit IRC01:09
*** masber has joined #openstack-sahara01:29
*** masuberu has joined #openstack-sahara02:12
*** rodrigod` has joined #openstack-sahara02:18
*** masber has quit IRC02:19
*** rodrigods has quit IRC02:19
*** hoonetorg has quit IRC02:31
*** hoonetorg has joined #openstack-sahara02:47
openstackgerritNguyen Hung Phuong proposed openstack/sahara-image-elements master: fix tox python3 overrides  https://review.openstack.org/58117603:33
*** masuberu has quit IRC03:43
*** Bhujay has joined #openstack-sahara03:49
openstackgerritTuan Do Anh proposed openstack/sahara master: Trivial fix typo of description  https://review.openstack.org/58118104:01
openstackgerritNguyen Hung Phuong proposed openstack/sahara-specs master: fix tox python3 overrides  https://review.openstack.org/58119304:47
*** links has joined #openstack-sahara05:22
*** pgadiya has joined #openstack-sahara05:22
*** pgadiya has quit IRC05:22
*** links has quit IRC06:38
*** links has joined #openstack-sahara06:53
*** tesseract has joined #openstack-sahara07:13
*** tosky has joined #openstack-sahara07:39
*** links has quit IRC07:44
*** rcernin has quit IRC07:47
*** links has joined #openstack-sahara07:57
*** rcernin has joined #openstack-sahara09:44
*** rcernin has quit IRC09:47
*** Bhujay has quit IRC10:15
*** Bhujay has joined #openstack-sahara10:15
*** Bhujay has quit IRC10:17
*** Bhujay has joined #openstack-sahara10:18
*** Bhujay has quit IRC10:19
*** Bhujay has joined #openstack-sahara10:19
openstackgerritJeremy Freudberg proposed openstack/python-saharaclient master: Rework saharaclient authentication  https://review.openstack.org/58069313:49
openstackgerritJeremy Freudberg proposed openstack/sahara-tests master: Allow for the future python-saharaclient  https://review.openstack.org/58137214:03
*** jeremyfreudberg has joined #openstack-sahara14:04
jeremyfreudbergtosky: eyes on https://review.openstack.org/#/c/581372/ ?14:04
toskyjeremyfreudberg: I was checking it right now14:10
toskyjeremyfreudberg: more then "remove me after requrement bump" is "leave only the code after the except after the code bump", but yeah14:13
openstackgerritJeremy Freudberg proposed openstack/python-saharaclient master: Fixup args in data source create  https://review.openstack.org/57968014:16
toskyso, is this ^^ major bump required to support S3 data sources?14:17
openstackgerritJeremy Freudberg proposed openstack/python-saharaclient master: Support of S3 data sources in OSC  https://review.openstack.org/58072714:18
openstackgerritJeremy Freudberg proposed openstack/python-saharaclient master: Remove ResourceManager aliases  https://review.openstack.org/58109514:19
jeremyfreudbergokay, i think i got the patch chain correct there14:19
jeremyfreudbergtosky: yes, "Fixup args in data source create" is necessary for S3 data sources14:20
jeremyfreudbergsome of the other patches are just other things which I felt were good to cram into the new saharaclient release14:20
toskyso, if I get it correctly, this new release is going to be backward incompatible with older code which uses saharaclient14:21
jeremyfreudbergtosky: yes, it will backwards incompatible, but also signified as so by semver14:22
toskyI guess I will ask the TC (or the appropriate body) if the the deprecation and compatibility rules apply also to the Python clients14:23
jeremyfreudbergtosky: "Note: this tag can currently only be applied to services (type:service deliverables). The tag definition may evolve in the future to include library feature deprecation policy and be applicable to libraries as a result"14:25
tellesnobregajeremyfreudberg, we need to rush with apiv2 on saharaclient right14:25
tellesnobrega?14:25
toskysure, but better ask now14:25
toskymaybe we are setting a precedent14:25
*** Bhujay has quit IRC14:26
jeremyfreudbergtellesnobrega: yes, we need to rush. library freeze is very soon (coinciding with rocky-3)14:26
toskyI did not check the old review, but the changes for S3 for job binaries did not require a bump - was it much different?14:28
jeremyfreudbergtosky: in the case of job binaries the arguments were already generalized. in the case of data sources they are annoyingly swift specific14:29
toskyoh14:30
jeremyfreudbergit is possible to write more code with lots of optional arguments, but that means more bad UX and bad code that we will have to carry around14:30
tellesnobregajeremyfreudberg, I will do my best to get a jump on it14:30
tellesnobrega-1 to carry bad code around14:31
toskyI disagree14:35
tellesnobregajeremyfreudberg, to be sure, we are done with the api side, we need to work on the osc part14:36
toskyasking on -tc, it looks like we should try to keep the compatibility with the old interface14:37
toskyif you want to join #openstack-tc, and discuss about it, it would be better14:37
toskyas it is right now I don't think I can accept a breaking change14:37
jeremyfreudbergtellesnobrega: https://review.openstack.org/#/c/581072/ is one more server-side patch. and i want to do one more patch which will lay the groundwork for microversion, if i have time14:38
jeremyfreudbergtosky: ok, i'll jump over14:39
tellesnobregajeremyfreudberg, quick question, why don't we have s3 on apiv2 only?14:52
jeremyfreudbergtellesnobrega: good question14:53
tellesnobregathat solves that breakage issue, and "forces" us to work harder on v214:53
tellesnobregabut I'm not sure that is what I want14:55
tellesnobregatosky ^14:55
toskyyou can't ask me what you want O.o14:55
jeremyfreudbergtellesnobrega: that would expose strange bugs with submitting a job through apiv1 and referening an s3 datasource by uuid14:55
jeremyfreudbergi included s3 in apiv1 because the plugins, job binaries, and data sources APIs are sort-of understood to be dynamic14:56
toskymy quick estimate says that changing the client to keep the compatibility is closer than closing the v2 work14:56
tellesnobregatosky, sorry, it was to the previous info14:56
tellesnobregaif we can work the compatibility issue I'm all for s3 in apiv114:57
tellesnobregaand I agree with tosky that fixing it is easier that working apiv2 completely although we really need to do the work15:00
jeremyfreudbergtosky, so, the new arguments would have to be optional, and come *after* is_protected? https://github.com/openstack/python-saharaclient/blob/master/saharaclient/api/data_sources.py#L2915:05
tellesnobregajeremyfreudberg, that sounds correct15:06
tellesnobregafollowing doug's suggestion15:06
toskyyes, that's the way to have it working in a compatible way (unless the last arguments are changed to **kwargs)15:07
toskyand luckily it's python and we don't have ABI15:07
jeremyfreudbergtosky: we can't do kwargs, because there could be someone out there relying on argument order15:08
tellesnobregayou could kwargs for the new stuff15:09
tellesnobregabut I would go with named arguments15:10
jeremyfreudbergyeah, it should be named arguments15:11
tellesnobregacool15:15
tellesnobregatosky, I will spawn ambari images today15:15
tellesnobregacan you remind me again which versions I need to test?15:15
toskyAmbari 2.6 images should be able to spawn HDP 2.6, HDP 2.5 and HDP 2.415:17
toskyAmbari 2.4 can create HDP 2.4 and HDP 2.3 clusters15:17
tellesnobregaok15:17
tellesnobregaso ambari 2.4 and try to spawn 2.4 and 2.3 to see if the error comes up?15:17
toskyoh, but that's with sahara-image-elements?15:18
toskyright, that's different15:18
tellesnobregayes15:18
tellesnobregaI'm going to test the ssl error iirc15:18
toskyok, sorry, then: Ambari 2.2.1.0 is the one used for HDP 2.4, while Ambari 2.2.0.0 is the one used for HDP 2.315:19
tellesnobregaok15:19
toskysie can also build Ambari 2.4.2.0 images, but those have been reported to have other issues; we may want to try to fix them (maybe)15:19
toskybut we have sahara-image-pack for them too (apart from pike)15:19
tellesnobregaok15:20
tellesnobregaI will generate all sorts of ambari images and start testing15:20
tellesnobregawhile working on apiv2 on client osc15:20
tellesnobregaand test new spark image15:20
tellesnobregaI might go crazy at some point15:20
tellesnobrega:)15:21
tellesnobregaheading out for lunch15:21
tellesnobregabbl15:21
jeremyfreudbergtosky: feel free to use your review powers on the "good to merge" section here: https://etherpad.openstack.org/p/jeremy-20180710-patches15:25
jeremyfreudbergand also free to poke into the "to discuss" patches15:26
*** links has quit IRC15:26
toskyoh, oki15:26
*** Bhujay has joined #openstack-sahara15:30
openstackgerritJeremy Freudberg proposed openstack/python-saharaclient master: Allow S3 credentials in data source create  https://review.openstack.org/57968015:51
openstackgerritJeremy Freudberg proposed openstack/python-saharaclient master: Support of S3 data sources in OSC  https://review.openstack.org/58072715:51
openstackgerritJeremy Freudberg proposed openstack/python-saharaclient master: Support of S3 data sources in OSC  https://review.openstack.org/58072715:58
openstackgerritJeremy Freudberg proposed openstack/sahara-dashboard master: Support of S3 data sources in dashboard  https://review.openstack.org/58074816:25
*** jeremyfreudberg has left #openstack-sahara16:35
*** Bhujay has quit IRC16:38
*** tesseract has quit IRC17:07
openstackgerritJeremy Freudberg proposed openstack/python-saharaclient master: Support of S3 data sources in OSC  https://review.openstack.org/58072717:48
tellesnobregatosky, have you generated ubuntu images recently?20:03
toskytellesnobrega: uhm, no20:06
tellesnobregathe image is just huge20:06
tellesnobrega9GB20:06
toskymore than centos?20:07
tellesnobregano reference20:12
tellesnobregatesting spark now20:12
tellesnobregawe never did spark on centos20:12
*** jeremyfreudberg has joined #openstack-sahara20:29
jeremyfreudbergtellesnobrega: your spark image was 9gb?20:29
tellesnobregayes20:29
jeremyfreudbergi've never seen that happen20:30
jeremyfreudbergfor s3 work all the spark images came out normal sized20:30
tellesnobregaI tried creating it with normal xenial file size it fails with no disk left20:30
tellesnobregaso I increased20:30
jeremyfreudbergwhen you get a chance (could be tomorrow), can you paste the entire output from a failed run?20:31
jeremyfreudberga failed run, meaning, one which failed with no disk left20:32
tellesnobregajeremyfreudberg, sure20:32
jeremyfreudbergjust whenever you get a chance, any time this week20:33
jeremyfreudbergno huge rush20:33
*** jeremyfreudberg has quit IRC20:33
tellesnobregatosky, on an unrelated matter, the i18n workaround worked20:37
toskytellesnobrega: so full deployment with python3?20:39
tellesnobregavenv with python320:40
toskynice20:42
tellesnobregajeremyfreudberg, http://paste.openstack.org/show/725467/20:45
tellesnobregatosky, not a good news, cluster fails to access the instances on python321:16
tellesnobregainstance: none, cluster: 0ed8da4e-7e33-42ca-9e15-af43b8b0ebce] Can't login to node, IP: 10.0.0.14, reason Ran out of input21:17
toskythat's probably more complicated than the i18n workaround21:18
toskyand who knows which component is failing21:18
tellesnobregaI'm not sure the whole devstack is under python321:22
tellesnobregacould also be conflict between py2 and py321:23
*** rcernin has joined #openstack-sahara22:22
*** tosky has quit IRC23:08

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!