Thursday, 2017-11-30

*** sdague has quit IRC00:01
*** yamamoto has joined #openstack-meeting-300:02
*** david-lyle has quit IRC00:03
*** dklyle has joined #openstack-meeting-300:03
*** slaweq has joined #openstack-meeting-300:04
*** david-lyle has joined #openstack-meeting-300:07
*** dklyle has quit IRC00:08
*** hongbin has quit IRC00:08
*** slaweq has quit IRC00:09
*** Sukhdev has joined #openstack-meeting-300:09
*** Sukhdev has quit IRC00:10
*** VW has joined #openstack-meeting-300:16
*** Sukhdev has joined #openstack-meeting-300:17
*** tssurya_ has quit IRC00:19
*** salv-orlando has joined #openstack-meeting-300:23
*** VW has quit IRC00:26
*** VW has joined #openstack-meeting-300:27
*** salv-orlando has quit IRC00:27
*** dklyle has joined #openstack-meeting-300:29
*** david-lyle has quit IRC00:30
*** VW has quit IRC00:30
*** VW has joined #openstack-meeting-300:30
*** chyka has quit IRC00:32
*** julim has joined #openstack-meeting-300:33
*** VW has quit IRC00:40
*** VW has joined #openstack-meeting-300:41
*** Sukhdev has quit IRC00:41
*** yamamoto has quit IRC00:45
*** VW has quit IRC00:45
*** Sukhdev has joined #openstack-meeting-300:52
*** david-lyle has joined #openstack-meeting-300:55
*** dklyle has quit IRC00:55
*** julim has quit IRC00:58
*** david-lyle has quit IRC01:01
*** shuyingya has joined #openstack-meeting-301:15
*** shuyingya has quit IRC01:19
*** salv-orlando has joined #openstack-meeting-301:24
*** yamamoto has joined #openstack-meeting-301:24
*** salv-orlando has quit IRC01:29
*** shuyingya has joined #openstack-meeting-301:51
*** shuyingy_ has joined #openstack-meeting-301:51
*** sgrasley1 has joined #openstack-meeting-301:51
*** shuyingya has quit IRC01:55
*** spzala has joined #openstack-meeting-302:01
*** spzala has quit IRC02:01
*** yamamoto has quit IRC02:22
*** yamamoto has joined #openstack-meeting-302:24
*** salv-orlando has joined #openstack-meeting-302:24
*** salv-orlando has quit IRC02:29
*** shu-mutou-AWAY is now known as shu-mutou02:30
*** VW has joined #openstack-meeting-302:33
*** yamamoto has quit IRC02:40
*** gcb has joined #openstack-meeting-302:40
*** zhurong has joined #openstack-meeting-302:46
*** yamahata has quit IRC02:54
*** iyamahat has quit IRC02:54
*** yamamoto has joined #openstack-meeting-302:54
*** trungnv has quit IRC03:03
*** trungnv has joined #openstack-meeting-303:04
*** yamamoto has quit IRC03:05
*** Sukhdev has quit IRC03:07
*** diablo_rojo has quit IRC03:13
*** absubram has quit IRC03:17
*** bobh has quit IRC03:23
*** gcb has quit IRC03:25
*** salv-orlando has joined #openstack-meeting-303:25
*** gcb has joined #openstack-meeting-303:26
*** e0ne has joined #openstack-meeting-303:28
*** salv-orlando has quit IRC03:30
*** bobh has joined #openstack-meeting-303:31
*** VW has quit IRC03:31
*** VW has joined #openstack-meeting-303:32
*** e0ne has quit IRC03:32
*** VW has quit IRC03:37
*** zhurong has quit IRC03:46
*** d0ugal_ has joined #openstack-meeting-303:50
*** d0ugal has quit IRC03:52
*** e0ne has joined #openstack-meeting-303:55
*** bobh has quit IRC03:58
*** e0ne has quit IRC04:00
*** gcb has quit IRC04:09
*** iyamahat has joined #openstack-meeting-304:10
*** e0ne has joined #openstack-meeting-304:11
*** e0ne has quit IRC04:16
*** coolsvap has joined #openstack-meeting-304:20
*** psachin has joined #openstack-meeting-304:20
*** e0ne has joined #openstack-meeting-304:23
*** yamahata has joined #openstack-meeting-304:26
*** salv-orlando has joined #openstack-meeting-304:26
*** e0ne has quit IRC04:28
*** VW has joined #openstack-meeting-304:29
*** salv-orlando has quit IRC04:30
*** VW has quit IRC04:34
*** e0ne has joined #openstack-meeting-304:39
*** VW has joined #openstack-meeting-304:42
*** e0ne has quit IRC04:44
*** e0ne has joined #openstack-meeting-304:50
*** Sukhdev has joined #openstack-meeting-304:57
*** e0ne has quit IRC05:03
*** VW has quit IRC05:06
*** VW has joined #openstack-meeting-305:06
*** VW has quit IRC05:06
*** VW has joined #openstack-meeting-305:07
*** e0ne has joined #openstack-meeting-305:07
*** VW has quit IRC05:09
*** VW has joined #openstack-meeting-305:09
*** VW has quit IRC05:10
*** VW has joined #openstack-meeting-305:10
*** VW has quit IRC05:11
*** VW has joined #openstack-meeting-305:11
*** VW has quit IRC05:12
*** e0ne has quit IRC05:12
*** VW has joined #openstack-meeting-305:12
*** pgadiya has joined #openstack-meeting-305:14
*** cshen_ has joined #openstack-meeting-305:15
*** VW has quit IRC05:16
*** e0ne has joined #openstack-meeting-305:17
*** cshen_ has quit IRC05:20
*** e0ne has quit IRC05:22
*** pgadiya has quit IRC05:23
*** Sukhdev has quit IRC05:25
*** salv-orlando has joined #openstack-meeting-305:27
*** chyka has joined #openstack-meeting-305:27
*** e0ne has joined #openstack-meeting-305:30
*** kei-ichi has quit IRC05:31
*** salv-orlando has quit IRC05:32
*** chyka has quit IRC05:32
*** kei-ichi has joined #openstack-meeting-305:34
*** tellesnobrega has quit IRC05:34
*** e0ne has quit IRC05:35
*** e0ne has joined #openstack-meeting-305:38
*** yamamoto has joined #openstack-meeting-305:39
*** yamamoto has quit IRC05:43
*** e0ne has quit IRC05:43
*** e0ne has joined #openstack-meeting-305:45
*** mikal has quit IRC05:47
*** absubram has joined #openstack-meeting-305:47
*** cshen_ has joined #openstack-meeting-305:50
*** absubram_ has joined #openstack-meeting-305:50
*** e0ne has quit IRC05:51
*** absubram has quit IRC05:52
*** absubram_ is now known as absubram05:52
*** cshen_ has quit IRC05:52
*** yamamoto has joined #openstack-meeting-305:53
*** mikal has joined #openstack-meeting-305:55
*** tellesnobrega has joined #openstack-meeting-305:55
*** yamamoto has quit IRC05:57
*** e0ne has joined #openstack-meeting-305:57
*** tellesnobrega has quit IRC05:59
*** tellesnobrega has joined #openstack-meeting-305:59
*** e0ne has quit IRC06:02
*** cshastri has joined #openstack-meeting-306:03
*** e0ne has joined #openstack-meeting-306:04
*** pcaruana has joined #openstack-meeting-306:05
*** mikal_ has joined #openstack-meeting-306:06
*** e0ne has quit IRC06:09
*** mikal has quit IRC06:10
*** salv-orlando has joined #openstack-meeting-306:12
*** e0ne has joined #openstack-meeting-306:15
*** pcaruana has quit IRC06:16
*** e0ne has quit IRC06:20
*** e0ne has joined #openstack-meeting-306:24
*** e0ne has quit IRC06:29
*** yamamoto has joined #openstack-meeting-306:31
*** jgu has quit IRC06:37
*** jgu has joined #openstack-meeting-306:38
*** yamamoto has quit IRC06:43
*** mikal_ has quit IRC06:45
*** mikal has joined #openstack-meeting-306:47
*** marios has joined #openstack-meeting-306:59
*** yamamoto has joined #openstack-meeting-306:59
*** yamamoto has quit IRC07:06
*** david-lyle has joined #openstack-meeting-307:19
*** gouthamr has quit IRC07:20
*** markvoelker has quit IRC07:37
*** yamahata has quit IRC07:38
*** yamamoto has joined #openstack-meeting-307:49
*** yamamoto has quit IRC07:51
*** pcaruana has joined #openstack-meeting-307:55
*** yamamoto has joined #openstack-meeting-307:57
*** georgk has joined #openstack-meeting-308:01
*** TuanLA has joined #openstack-meeting-308:07
*** makowals has quit IRC08:16
*** e0ne has joined #openstack-meeting-308:18
*** yamamoto has quit IRC08:33
*** makowals has joined #openstack-meeting-308:36
*** markvoelker has joined #openstack-meeting-308:38
*** yamamoto has joined #openstack-meeting-308:40
*** gmann is now known as gmann_afk08:41
*** MarkBaker has quit IRC08:44
*** yamamoto has quit IRC08:44
*** iyamahat has quit IRC08:52
*** ccamacho has joined #openstack-meeting-308:52
*** georgk has left #openstack-meeting-308:58
*** ccamacho has quit IRC09:02
*** chyka has joined #openstack-meeting-309:03
*** yamamoto has joined #openstack-meeting-309:04
*** ccamacho has joined #openstack-meeting-309:05
*** ccamacho has quit IRC09:06
*** ccamacho has joined #openstack-meeting-309:06
*** chyka has quit IRC09:08
*** belmoreira has joined #openstack-meeting-309:13
*** rossella_s has joined #openstack-meeting-309:16
*** d0ugal_ has quit IRC09:17
*** d0ugal has joined #openstack-meeting-309:18
*** d0ugal has quit IRC09:18
*** d0ugal has joined #openstack-meeting-309:18
*** yamamoto has quit IRC09:19
*** VW has joined #openstack-meeting-309:22
*** VW has quit IRC09:26
*** mfedosin_ has joined #openstack-meeting-309:38
*** mfedosin has quit IRC09:39
*** _pewp_ has quit IRC09:39
*** pcaruana has quit IRC09:39
*** mfedosin_ is now known as mfedosin09:39
*** _pewp_ has joined #openstack-meeting-309:39
*** pcaruana has joined #openstack-meeting-309:40
*** e0ne has quit IRC09:40
*** kbyrne has quit IRC09:43
*** cshastri has quit IRC09:43
*** kbyrne has joined #openstack-meeting-309:44
*** chason has quit IRC09:45
*** chason has joined #openstack-meeting-309:45
*** david-lyle has quit IRC09:46
*** TuanLA has quit IRC09:58
*** coolsvap has quit IRC09:59
*** e0ne has joined #openstack-meeting-310:01
*** belmoreira has quit IRC10:03
*** belmoreira has joined #openstack-meeting-310:07
*** borisnet[m]1 has joined #openstack-meeting-310:08
*** xgerman_ has quit IRC10:09
*** fyxim has quit IRC10:09
*** kong has quit IRC10:09
*** zhenguo has quit IRC10:09
*** dgonzalez has quit IRC10:09
*** borisnet[m] has quit IRC10:09
*** anubhaskar[m] has quit IRC10:09
*** anubhaskar[m] has joined #openstack-meeting-310:15
*** xgerman_ has joined #openstack-meeting-310:15
*** fyxim has joined #openstack-meeting-310:15
*** kong has joined #openstack-meeting-310:15
*** zhenguo has joined #openstack-meeting-310:15
*** dgonzalez has joined #openstack-meeting-310:15
*** trungnv has quit IRC10:15
*** calbers has quit IRC10:18
*** calbers has joined #openstack-meeting-310:22
*** VW has joined #openstack-meeting-310:33
*** cshastri has joined #openstack-meeting-310:34
*** salv-orlando has quit IRC10:36
*** VW has quit IRC10:37
*** MarkBaker has joined #openstack-meeting-310:47
*** salv-orlando has joined #openstack-meeting-310:48
*** shu-mutou is now known as shu-mutou-AWAY10:55
*** raildo has joined #openstack-meeting-311:00
*** sdague has joined #openstack-meeting-311:02
*** kabhishek[m] has quit IRC11:06
*** natorious has quit IRC11:11
*** warlord77[m] has quit IRC11:13
*** borisnet[m]1 has quit IRC11:13
*** natorious has joined #openstack-meeting-311:14
*** Kodzo[m] has quit IRC11:14
*** anubhaskar[m] has quit IRC11:14
*** zerga[m] has quit IRC11:14
*** johnwhitlow[m] has quit IRC11:14
*** Eko[m] has quit IRC11:14
*** salv-orlando has quit IRC11:18
*** salv-orlando has joined #openstack-meeting-311:32
*** MarkBaker has quit IRC11:53
*** ywat has quit IRC11:53
*** rossella_s has quit IRC11:54
*** rossella_s has joined #openstack-meeting-311:55
*** coolsvap has joined #openstack-meeting-312:10
*** etingof has quit IRC12:12
*** bobh has joined #openstack-meeting-312:26
*** Eko[m] has joined #openstack-meeting-312:27
*** bobh has quit IRC12:30
*** belmoreira has quit IRC12:33
*** chyka has joined #openstack-meeting-312:34
*** yamamoto has joined #openstack-meeting-312:37
*** chyka has quit IRC12:38
*** warlord77[m] has joined #openstack-meeting-312:42
*** zerga[m] has joined #openstack-meeting-312:42
*** johnwhitlow[m] has joined #openstack-meeting-312:42
*** anubhaskar[m] has joined #openstack-meeting-312:42
*** kabhishek[m] has joined #openstack-meeting-312:42
*** Kodzo[m] has joined #openstack-meeting-312:42
*** borisnet[m] has joined #openstack-meeting-312:42
*** dobson has quit IRC12:44
*** etingof has joined #openstack-meeting-312:50
*** dobson has joined #openstack-meeting-312:52
*** belmoreira has joined #openstack-meeting-312:53
*** etingof has quit IRC12:58
*** yamamoto has quit IRC13:04
*** yamamoto has joined #openstack-meeting-313:05
*** etingof has joined #openstack-meeting-313:10
*** lhx_ has joined #openstack-meeting-313:16
*** VW has joined #openstack-meeting-313:17
*** markvoelker has quit IRC13:23
*** markvoelker has joined #openstack-meeting-313:24
*** sambetts|afk is now known as sambetts13:29
*** shuyingy_ has quit IRC13:35
*** lyan has joined #openstack-meeting-313:40
*** stendulker has joined #openstack-meeting-313:41
*** donghao has joined #openstack-meeting-313:51
*** shuyingya has joined #openstack-meeting-313:57
*** tssurya_ has joined #openstack-meeting-313:59
*** gmann_afk is now known as gmann14:00
tellesnobrega#startmeeting sahara14:00
openstackMeeting started Thu Nov 30 14:00:48 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
tellesnobregawaiting for people to show hands14:01
shuyingyao/14:01
shuyingyaWait me 3 minutes please14:01
tellesnobregasure14:01
*** jeremyfreudberg has joined #openstack-meeting-314:01
jeremyfreudbergo/14:02
*** shuyingya has quit IRC14:02
*** d0ugal has quit IRC14:03
*** margaret has joined #openstack-meeting-314:03
*** shuyingya has joined #openstack-meeting-314:03
tellesnobregawaiting until 5 after so we can start14:04
jeremyfreudbergsure14:05
*** shuyingy_ has joined #openstack-meeting-314:05
tellesnobregaand that is time14:05
tellesnobrega#topic News/Updates14:05
*** openstack changes topic to "News/Updates (Meeting topic: sahara)"14:05
shuyingy_Hi  I am comming14:05
*** tosky has joined #openstack-meeting-314:05
toskyhere, sorry14:05
jeremyfreudbergo/14:05
tellesnobregaI'm currently finishing up the work on decommission of specific node. I just need to check shuyingy_'s comment on the order of deletion, and write tests14:06
tellesnobregaother than that, I need to get back to mapr image generation14:06
tellesnobregaand try to squeeze some time to work on plugin outside sahara code14:06
tellesnobreganot sure it will happen, the last one, but I will try14:07
tellesnobregaOh, I also need to do the decommission work on the sahara client and UI14:07
tellesnobregaUI should be a pain, but it is a necessary evil14:07
jeremyfreudbergso, I'm working on revising s3_hadoop element, finishing up s3 job binary mostly14:09
tellesnobregagood, do you believe we will have the feature in queens?14:09
shuyingy_Today is the last day of business travel. this week mostly working on deploying sahara on k8s by helm. If you are interesting, please review https://review.openstack.org/#/c/477718/. and will continue to work on HBase support next week. hopefully it can be finished next week.14:09
jeremyfreudbergtellesnobrega, s3 job binary should defniitely be done14:09
jeremyfreudbergdata source is another story, those are always a bit trickier since they have to work on the cluster itself, it's not just an abstraction14:10
tellesnobregathat is great shuyingy_, did it all work well:14:10
tellesnobrega?14:10
tellesnobregajeremyfreudberg, I understand, we still have some time, let me know if you need help14:10
jeremyfreudbergtellesnobrega, sure14:10
shuyingy_I am try to review s3 patch. but doesn't find any problem because of lack of knowledge about s314:11
jeremyfreudbergyes, it would be good have someone who really knows S3 to say whether or not we are exposing enough boto options14:12
jeremyfreudbergi made some nodes about s3 region and such14:12
jeremyfreudbergthere are lots of fancy kwargs that can go there14:12
jeremyfreudbergbut who knows what users actually need14:12
jeremyfreudberg*notes14:12
tellesnobregathat might be tricky to find14:12
tellesnobregas3 knowledge interested in OpenStack, even more on sahara14:13
shuyingy_yes, it works well. I need try to find more frequently changed configurations for user to configure sahara.14:13
*** shuyingya has quit IRC14:13
tellesnobregatosky, any news/updates?14:14
toskyI'm swamped in internal testing, but I'm still keeping an eye on the zuul changes (and nagging zuul developers)14:14
tellesnobregacool14:14
toskyso yes, we will have proper native jobs way before queens (hopefully before the end of the year)14:15
tellesnobreganice :) that is great to hear14:15
toskyI think I already wrote it: I could have pushed some changes, and then fixed them; but infra is not pushing to remove the old jobs, so I'm lazily waiting to avoid some loops of write/fix14:16
tellesnobregamakes sense14:16
jeremyfreudbergtosky, i see14:16
shuyingy_now is in middle of Queen, right? I am sorry that i didn't finished HBase support and keypair injecting util now14:16
jeremyfreudbergshuyingy_, that's ok14:16
jeremyfreudbergi have the same schedule problems14:16
tellesnobregashuyingy_, yes, we are approaching q-2. It is on December 7th14:17
jeremyfreudbergfeature freeze is between Jan 22 - Jan 26, so you still have time after that14:17
toskyup to the PTL, but as long as the new features are additional and do not impact the existing code, it should not be a problem if they land a bit later14:17
tellesnobregayes14:17
*** d0ugal has joined #openstack-meeting-314:17
tellesnobregaand we can always get FFE if needed14:18
* jeremyfreudberg reminds everyone he has to log off today by 14:27 UTC14:18
shuyingy_that is great14:18
tellesnobregait won't be a problem I believe. But we can't wait too much14:18
*** coolsvap has quit IRC14:19
tellesnobregalets move on, we have a important topic for today14:19
jeremyfreudbergevery topic is important14:19
jeremyfreudberg;)14:19
shuyingy_:)14:19
tellesnobregatrue14:19
shuyingy_aha14:19
tellesnobregacritical one14:19
tellesnobrega#topic plugins update14:20
*** openstack changes topic to "plugins update (Meeting topic: sahara)"14:20
jeremyfreudbergindeed, this is is a critical topic14:20
tellesnobregaAt the PTG we decided that we should try to have all updates by Q214:20
tellesnobregathat means we have about 7 days to finish them all14:20
toskyor defines exceptions :)14:21
tellesnobregathis isn't a must, and if we fail, nobody will die.14:21
tellesnobregaMy plan here is for us to have a list of the plugins that needs to be updated and we can start working on it asap14:21
jeremyfreudbergyes, nobody will die, and i put a provision here https://releases.openstack.org/queens/schedule.html#q-sahara-plugin-deadline that telles can basically suspend this rule if he wants14:21
toskyand an estimated rough complexity, if you can14:21
jeremyfreudbergyes, let's figure out what can get updated14:21
jeremyfreudbergyes14:22
tellesnobregaso we can have it finished close to our schedule14:22
jeremyfreudbergso, there is a finally as of a few weeks ago a stable Hadoop 2.8.x release14:22
jeremyfreudbergit ended up 2.8.214:22
jeremyfreudbergthere is no stable 2.9 or 3.0 yet14:22
tellesnobregayes14:22
jeremyfreudbergso vanilla plugin can be upgraded if we want14:23
jeremyfreudbergalong with pig and hive and oozie(?) on that image14:23
toskyand will 2.9 be close 2.8, before the big breakage with 3.0?14:24
tellesnobregasounds about right14:24
toskyI wonder why they still plan full development on the old series, but well...14:24
jeremyfreudbergtosky, 2.9 is close to 2.8 yes14:24
jeremyfreudbergand there will be parallel development14:24
jeremyfreudbergnot quite like Python 2 / Python 3, but something like that :(14:24
jeremyfreudbergso, vanilla14:25
jeremyfreudbergspark plugin can can be upgraded too14:25
shuyingy_cdh too14:25
shuyingy_it has cdh 5.13 right now14:25
jeremyfreudbergcdh maybe not, i had some problem with a package no longer available14:25
jeremyfreudbergwe had to cancel our 5.12 upgrade because we didn't have time to figure it out14:25
tellesnobrega#action update vanilla to 2.8.2 also pig, hive and oozie(?)14:26
jeremyfreudbergfor spark there is 2.1.2 and 2.2.0 so far14:26
jeremyfreudbergthe cdh thing was navigator trustee if i recall correctly14:26
tellesnobregashuyingy_, jeremyfreudberg is right, we have to take a deeper look into CDH, they changed some packages to enterprise only, so we may have hit a roadblock there14:26
jeremyfreudbergbtw, i have to sign off basically now14:27
jeremyfreudbergbut tellesnobrega can figure out storm14:27
tellesnobregathanks jeremyfreudberg14:27
toskybye jeremyfreudberg o/14:27
jeremyfreudbergmapr and hdp i'm sure have something new14:27
shuyingy_jeremy byebye14:27
jeremyfreudbergnot sure if that's absolutely essential14:27
jeremyfreudbergbye all!14:27
jeremyfreudbergsend me an email if you have urgent questions14:27
tellesnobregasee ya14:27
tellesnobregawill do14:27
jeremyfreudbergi will read the trasncript of ths meeting asap14:27
*** jeremyfreudberg has quit IRC14:27
tellesnobregado we want both new spark versions?14:28
shuyingy_I don't think so.14:28
toskyuhm, do you mean basic spark and cdh/spark?14:28
* tosky confused14:28
tellesnobregaI think spark 2.1.0 should not be deprecated yet, we can add the newest one14:28
tellesnobregaupstream spark14:28
toskyoh, I see14:28
tellesnobregaand later, if needed we replace 2.1.0 with 2.1.214:29
toskyisn't 2.1.2 just a minor update for 2.1? I think we didn't solve the problem of minor compatibile versions14:29
shuyingy_we don't need update minor version I think14:29
toskymaybe we could just allow the code to define multiple tags for each plugin/version14:29
toskyso can we register it as 2.1.0 and it should work?14:29
tellesnobregathat would be nice14:30
tellesnobregato be sure, spark is going to 2.2.014:30
tellesnobregaand we keep 2.1.0 and see if we can work tags to have minor versions14:31
tellesnobregaall agreed?14:31
shuyingy_do you mean we can build an image with spark 2.1.2 and tag it as 2.1.0?14:32
toskyI would say that it should be fine for n ow14:32
toskynow14:32
tellesnobregashuyingy_, yes14:32
shuyingy_from code side, that's is not difficult. sound nice14:32
shuyingy_\o/14:33
tellesnobrega#action update spark to 2.2.014:33
tellesnobregalets move on to storm14:33
tellesnobregastorm newest version is 1.1.114:33
tellesnobregawe have 1.1.0, so we can take the same approach we did for spark14:33
tellesnobregasounds ok?14:34
shuyingy_sure. it is really convenient to user14:35
tellesnobregacool14:35
tellesnobregaMapR14:35
tellesnobregaI check their website, seems like the newest version is 5.214:35
tellesnobregawhich we already have14:36
toskyit would be nice to understand why they disappeared also from sahara14:36
toskybut no new upstream versions too, uhm14:36
tellesnobregawait, seems like there is a mapr 614:37
tellesnobregabut in tr mapr the newest version is 5.214:38
*** e0ne has quit IRC14:39
tellesnobregayeah, seems like 5.2 is the last one on downloads14:40
*** e0ne has joined #openstack-meeting-314:40
tellesnobregaAmbari has a new version 2.614:40
*** gmann is now known as gmann_afk14:40
tellesnobregahttps://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.6.014:41
toskyI can't find the release date for 6, but there is the documentaiton14:41
shuyingy_we may not have too much energy to update them all. MapR used to update by MapR themself, right?14:41
toskyand which HDP versions can be deployed by ambari 2.6?14:41
tellesnobregatosky, checking that now14:41
shuyingy_https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_support-matrices/content/ch_matrices-ambari.html#ambari_stack14:42
tellesnobrega6.0.0November 21, 2017N/A14:42
tellesnobregatosky, ^14:42
*** Swami has joined #openstack-meeting-314:42
toskytellesnobrega: argh, one week14:42
toskyI would say we can push it to Rocky14:42
tellesnobregatosky, for sure14:42
tellesnobregaseems like hdp doesn't support ambari 2.6 yet14:43
toskythat would be weird14:43
toskyI remember that Ambari x.y should support at least HDP x.y14:43
toskybut I may remember incorrectly14:43
tellesnobregathe link is looking was wrong14:44
*** cshastri has quit IRC14:45
tellesnobregaon HDP website there is only the matrix up to ambari 2.514:45
tellesnobregahttps://hortonworks.com/blog/hdp-2-6-3-dataplane-service/14:46
tellesnobregatosky, shuyingy_  ^14:46
toskyuhm uhm14:46
tellesnobregaboth ambari 2.6.0 and HDP 2.6.314:46
toskyat least we are not the only one with documentation that requires some updates :)14:46
tellesnobregalol14:46
tellesnobregatrue14:47
shuyingy_haha14:47
shuyingy_:)14:47
tellesnobregaso we want to update ambari to 2.6.0 with HDP to 2.6.314:47
tellesnobregaall in favor?14:47
shuyingy_up14:48
shuyingy_agree14:48
tellesnobrega#action update ambari to 2.6 with HDP to 2.6.314:49
*** stendulker has quit IRC14:49
shuyingy_Now we should decide how to divide the work14:49
tellesnobregaI think we covered all plugins14:49
tellesnobregayes14:49
shuyingy_yes14:49
tellesnobregaI believe that spark and storm should be fairly quick work, I can take them both14:50
toskyonly HDP 2.6, or should we try to switch to ambari 2.6 to deploy also the older versions?14:50
shuyingy_btw, I will share you the performance comparison of vanilla to aws emr next week14:50
tellesnobregacool14:50
toskyit may be complicated, but it could also simplify part of the matrix14:50
*** mlavalle has joined #openstack-meeting-314:51
tellesnobregatosky, not sure, ambari/hdp has always confused me14:51
shuyingy_I will update vanilla if I can. otherwise I can invite my colleague to help us.14:51
toskyAmbari can deploy few versions14:51
shuyingy_ ambari/hdp has always confused me too14:51
shuyingy_the image name of ambari let me crazy14:52
*** bobh has joined #openstack-meeting-314:52
*** janzian has joined #openstack-meeting-314:52
toskyyeah14:53
tellesnobregatosky, what do you think is the best way to go with ambari?14:53
toskyfrom the previous document it seems that Ambari 2.5 was able to deploy all the old versions14:53
toskyso it may be the same with Ambari 2.614:53
toskyright now, if I'm not mistaken, we deploy two slightly different versions of ambari for the two version of hdp14:54
toskybut if ambari 2.6 can deploy 2.6, 2.4 (and 2.3, if we don't want to deprecated it), maybe it's easier to handle14:54
toskyotherwise we would need different codepaths on our side if the various ambari versions differs14:55
toskybut if ambari hides the differences between HDP versions, well14:55
tellesnobregayeah, I think we have 2.2.0.0 and 2.2.1.014:55
tellesnobregaour ambari version is very old at this point14:55
tellesnobregaso we have ambari and vanilla to update14:57
toskyI think we support ambari 2.4 too14:57
tellesnobregayeah14:57
tellesnobreganot sure14:58
shuyingy_2.4 and 2.5 both support14:58
tellesnobregaon image gen the versions are  2.2.0.0 and 2.2.1.014:58
toskybut again, if HDP 2.6 can be deployed with ambari 2.6 only (ok, also 2.5), we need to update to support that ambari14:58
toskyif, on the other side, that ambari can deploy all hdp versions, why not kill the olders ambari?14:58
tellesnobregasounds good, lets take a closer look on that and get back to it14:59
tellesnobregathat would be good too14:59
tellesnobregaand maybe we should take a class on ambari/hdp14:59
tellesnobregalol14:59
*** hongbin has joined #openstack-meeting-314:59
tellesnobregashuyingy_, do you have time to update any plugin?15:00
shuyingy_so I will update vanilla15:00
shuyingy_you may miss my message15:00
shuyingy_:)15:00
tellesnobregagreat15:00
*** iyamahat has joined #openstack-meeting-315:00
tellesnobregaI will try to check ambari and see if jeremy can work on it15:00
*** yamahata has joined #openstack-meeting-315:00
shuyingy_at 22:51, I said it :)15:00
tellesnobregaotherwise I will work on it was well15:01
tellesnobregayes15:01
shuyingy_haha15:01
tellesnobregawe have to close it15:01
tellesnobregathanks guys15:01
shuyingy_bye15:01
tellesnobregasee you next week15:01
tellesnobregabye15:01
shuyingy_see you next week15:01
toskyo/15:01
tellesnobrega#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Thu Nov 30 15:01:39 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-11-30-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-11-30-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-11-30-14.00.log.html15:01
mlavalle#startmeeting neutron_l315:01
openstackMeeting started Thu Nov 30 15:01:49 2017 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
haleybhi15:02
Swamihi15:02
*** tosky has left #openstack-meeting-315:02
janziano/15:02
mlavallesorry for the delay, the Sahara guys were wrapping up their meeting15:02
mlavalle#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
mlavalleFirst announcement is that the Q-2 milestone will be next week15:03
mlavalleafter that, we are on the home stretch of the Queens cycle15:04
mlavalleSecond annoucement is that the Rocky PTG is open to buy tickets and make hotel reservations15:04
mlavalle#link https://www.openstack.org/ptg/15:05
mlavallethe venue is a soccer stadium that also has meeting rooms to host conferences15:05
Swaminice15:06
haleybs/soccer/football right? :)15:06
mlavalleI made my reservation at the event hotel yesterday, to make sure I get the discounted price of 155 euros and comply with my employer policies15:07
*** davidsha has joined #openstack-meeting-315:07
mlavallehaleyb: lol, you made doubt whether my subconcious had betrayed me....15:07
haleybi just got approved today so will be doing the same.  i will only be there wed-fri though, the ptg always conflicts with my vacation15:08
*** jrist has quit IRC15:08
davidshaSorry I'm late, just got out of a meeting @.@15:08
mlavallethat rate includes breakfasts and taxes15:08
mlavalleso that is the net net rate15:08
*** jrist has joined #openstack-meeting-315:09
mlavallehaleyb: nice, we can have go to the Irish pubs with davidsha to discuss kick ass dvr15:09
davidsha:D15:09
mlavalleany other announcements?15:09
mlavalleok, moving on15:10
mlavalle#topic Bugs15:10
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:10
mlavalleSwami: please fire away15:10
Swamimlavalle: thanks15:10
*** donghao has quit IRC15:11
Swami#link https://bugs.launchpad.net/neutron/+bug/171730215:11
openstackLaunchpad bug 1717302 in neutron "Tempest floatingip scenario tests failing on DVR Multinode setup with HA" [High,Confirmed]15:11
Swamimlavalle, haleyb: I was able to debug this issue further and found some issues in the floatingip translation from the router namespace to the fip namespace.15:12
haleybSwami: great!15:12
SwamiI have captured all my findings in the bug report.15:12
SwamiThe rules are configured in the router namespace and the packet is getting out of the router namespace with a private ip and so it is not getting in sync.15:13
SwamiI see both the nodes reponding to the ping, but they are not syncing up.15:13
*** VW has quit IRC15:13
*** VW has joined #openstack-meeting-315:14
Swamihaleyb: Do you know why this would happen or have you seen similar issues.15:14
haleybi will have to read through all the notes15:14
SwamiThis is very hard to reproduce, because out of the four tests either one fails randomly. The only test that does not fail is the 'without FIP' condition for both SRC and DEST.15:15
Swamisorry I meant hard to debug, but easy to reproduce, you will get a failure at least once in two runs.15:15
haleybSwami: thanks for debugging further15:16
Swamihaleyb: I think the culprit is the floatingip-chain in the router-namespace, but let me look further and update. In the meanwhile if you see any thing let me know or update the bug report.15:16
SwamiSo I will continue my debugging on this.15:17
mlavalleThanks!15:17
*** marst has joined #openstack-meeting-315:17
Swami#link https://bugs.launchpad.net/neutron/+bug/173398715:17
openstackLaunchpad bug 1733987 in neutron "name resolution error with DVR+HA routers" [Medium,In progress] - Assigned to Armando Migliaccio (armando-migliaccio)15:17
SwamiThere is a patch up for review for this bug.15:17
Swami#link https://review.openstack.org/#/c/522362/15:18
haleybi see armando updated it, will take another look15:19
SwamiNothing else to discuss on this patch, since we already have some review comments from anil and haleyb15:19
*** stendulker has joined #openstack-meeting-315:19
Swamihaleyb: ok, thanks.15:19
*** zhipeng has joined #openstack-meeting-315:19
Swami#link https://bugs.launchpad.net/neutron/+bug/173385215:20
openstackLaunchpad bug 1733852 in neutron "Incorrect ARP entries in new DVR routers for Octavia VRRP addresses" [Medium,In progress] - Assigned to Daniel Russell (danielr-2)15:20
SwamiSorry I just noticed this issue. I am backlogged from my vacation in Sydney.15:20
Swamihaleyb: thanks for triaging this.15:20
haleybnp, i just haven't looked at the review yet15:21
*** MarkBaker has joined #openstack-meeting-315:21
SwamiI need to take a further look at this and see what is triggering this ARP entry. May be we might have some code that needs cleanup on the server side.15:21
SwamiBut I will update the bug report after doing my testing.15:21
Swamihaleyb: I did see that the patch was abandoned.15:22
haleybthere's a new one, don't know why the first was abandoned15:22
mlavallethere is another one:15:22
*** zhipeng has quit IRC15:22
Swami#link https://review.openstack.org/#/c/524037/15:22
mlavalleyeah, that seems to be the good one15:23
Swamimlavalle: yes this patch is still active against the bug. I will take a look at it. The other one has been abandoned.15:23
Swami#link .launchpad.net/neutron/+bug/173185715:23
*** stendulker_ has joined #openstack-meeting-315:24
Swami#link https://bugs.launchpad.net/neutron/+bug/173185715:24
openstackLaunchpad bug 1731857 in neutron "DVR scenario tests fail in default deployment" [Low,New]15:24
SwamiThe bug says there is a mismatch in the default settings with DVR and legacy routers.15:24
SwamiI need to check this out. I might not have tested with legacy routers.15:25
haleybfor the migration tests it would seem legacy was not a good choice, so maybe it is just a quick fix?15:26
*** stendulker has quit IRC15:26
*** stendulker_ has quit IRC15:26
Swamihaleyb: yes15:27
*** gouthamr has joined #openstack-meeting-315:27
*** stendulker_ has joined #openstack-meeting-315:27
Swami#link https://bugs.launchpad.net/neutron/+bug/172866515:27
openstackLaunchpad bug 1728665 in neutron "Removing gateway ip for tenant network (DVR) causes traceback in neutron-openvswitch-agent" [Medium,In progress] - Assigned to Brian Haley (brian-haley)15:27
Swami#link https://review.openstack.org/#/c/521199/15:28
SwamiThere is a patch up for review.15:28
haleybSwami: i had forgoteen about that one, will look at your comments15:28
Swamihaleyb: no problem.15:28
Swami#link https://bugs.launchpad.net/neutron/+bug/171640115:29
openstackLaunchpad bug 1716401 in neutron "FWaaS: Ip tables rules do not get updated in case of distributed virtual routers (DVR)" [Undecided,New]15:29
SwamiI haven't got any information on this from the FWaaS team. I tried to sync up with Sridhar in Sydney but he was busy and mentioned that he will through this issue with me later.15:30
SwamiSo this is still pending.15:30
Swamimlavalle: may be you can bring this up in the FWaaS meeting.15:30
SwamiThat's all I had for today's meeting.15:30
mlavalleSwami: ok, I will15:30
Swamimlavalle: back to you15:30
mlavalleon my side we have https://bugs.launchpad.net/neutron/+bug/170675015:31
openstackLaunchpad bug 1706750 in neutron "FlushError for automatic IPAllocations when subnet create is retried" [High,Confirmed] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)15:31
mlavalleihrachys is wroking on it15:31
mlavallehe has two WIP patchsets15:31
mlavalle#link https://review.openstack.org/51898815:32
mlavalle#link https://review.openstack.org/51898915:32
mlavalleso I guess keep an eye on them15:32
mlavalleand that's all I got15:33
mlavalleany other bucgs from the team?15:33
haleybi have one15:33
haleybhttps://bugs.launchpad.net/neutron/+bug/173159515:33
openstackLaunchpad bug 1731595 in neutron "L3 HA: multiple agents are active at the same time" [High,In progress] - Assigned to venkata anil (anil-venkata)15:33
haleybanil has a patch that addresses the problem, just needs an update with a test15:34
mlavalleis that the one where he has patgchset for master and stable branches?15:34
haleybmlavalle: yes, he proposed stable ones just to test, and make it easier to pick downstream for testing15:35
mlavalleok, cool, they are in my radar screen then15:35
haleybthat's it from me15:36
mlavalleok thanks for the updates15:36
mlavalle#topic Kick-ass DVR15:36
*** openstack changes topic to "Kick-ass DVR (Meeting topic: neutron_l3)"15:36
davidshaThanks, I'm working on breaking out the roter_info_base file into a seperate patch atm15:37
davidshaThere are a few calls outside of the routers I'm looking into absorbing into the base router classes15:38
davidshaAn example of some are these calls: https://github.com/openstack/neutron/blob/master/neutron/agent/metadata/driver.py#L283-L32415:38
Swamimlavalle: haleyb: I need to drop off my son at school, so will signogg15:39
Swamis/signogg/signoff15:39
mlavalleSwami: go ahead, thanks for the updates :-)15:39
davidshaJust as a general question, are these functions ok to move into router info base?15:39
haleybSwami: ok, thanks for the updates - jinx15:39
davidshaSwami: cya!15:39
davidshaBy moving them into router_info, I'd hope that we could abstract out the use of iptables from the main l3-agent15:40
mlavalleit seems worth exploring to me15:41
mlavallethey are not even part of the meta driver per se15:42
haleybyeah, they are self-contained15:42
*** nikhil has joined #openstack-meeting-315:42
*** rossella_s has quit IRC15:43
davidshaKk, I'll try to have this patch up for review by next Friday. Are both of you ok with the idea of trying to abstract iptables calls into the routers and out of the Agent?15:44
mlavallewell it seems to me that is an effort to start re-factoring code in prepration for adopting the openflow approach, while we fix our DVR mess15:45
mlavalleunder that assumption, yes15:45
haleybyes, it is fine with me15:45
*** stendulker_ has quit IRC15:46
*** rossella_s has joined #openstack-meeting-315:46
*** stendulker_ has joined #openstack-meeting-315:46
davidshacool, thanks. thats all from me unless there are any questions?15:47
mlavalledavidsha: none from me. Thanks for continuing with this. We are aware your priorities have been changing lately and highly appreciate the effort15:47
mlavallelet's move on15:49
*** yamamoto has quit IRC15:49
mlavalle#topic QoS for floating ips15:49
*** openstack changes topic to "QoS for floating ips (Meeting topic: neutron_l3)"15:49
mlavalleThe patchset for the server side merged yesterday. Thanks haleyb for the reviews :-)15:49
*** dtantsur has joined #openstack-meeting-315:50
*** yamamoto has joined #openstack-meeting-315:50
*** stendulker_ has quit IRC15:51
mlavalleThe agent side is here:15:51
mlavalle#link https://review.openstack.org/#/c/521079/15:51
*** stendulker_ has joined #openstack-meeting-315:51
mlavalleand and seems ripe for reviews15:52
mlavalleI am thinking we also need some docs, either added to this last patchset or in another one15:52
mlavalleand the python openstackclient patch is here:15:53
mlavalle#link https://review.openstack.org/#/c/517845/15:53
*** elmiko has joined #openstack-meeting-315:54
*** thingee has joined #openstack-meeting-315:54
*** thingee has left #openstack-meeting-315:55
*** thingee has joined #openstack-meeting-315:55
mlavalleok, moving on15:55
mlavalle#topic Open agenda15:55
*** openstack changes topic to "Open agenda (Meeting topic: neutron_l3)"15:55
mlavalleDoes anyone have any toher topics to discuss today?15:55
*** cdent has joined #openstack-meeting-315:56
mlavalleI have one15:56
mlavallehaleyb: I took a look at this review: https://review.openstack.org/#/c/516055/15:56
mlavalleit seems good to me. The question is, won't we break someone who is using the extension as it is today?15:57
haleybmlavalle: yes, i thought about that, but it seems they are maybe broken as-is, so perhaps noone is using it much?15:58
mlavallethat was my thinking also but I wanted to check anyway15:58
mlavalleI also think we need some sort of doc15:59
davidshaJust before we run out of time!15:59
mlavallefor the extension, because we have none now15:59
davidshaI have one also, Someone has been assigned to take over the DVR patch, I'll ask him to try and join this meeting next week, but he is in China I believe, so it is late for them.15:59
mlavalledavidsha: ok, thanks for the heads up15:59
cdent(feel free to run over a bit, we api-sig people in no rush)15:59
mlavallecdent: I think we are done16:00
haleybmlavalle: doc the metering extension?  sure16:00
* cdent WAVES AT MLAVALLE16:00
mlavalle#endmeeing16:00
*** rossella_s has quit IRC16:00
* mlavalle waves back at cdent16:00
* edleafe waves at mlavalle too16:00
mlavalle#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
haleyb:16 over16:00
openstackMeeting ended Thu Nov 30 16:00:40 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-11-30-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-11-30-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-11-30-15.01.log.html16:00
cdent#startmeeting api-sig16:01
openstackMeeting started Thu Nov 30 16:01:00 2017 UTC and is due to finish in 60 minutes.  The chair is cdent. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: api-sig)"16:01
openstackThe meeting name has been set to 'api_sig'16:01
cdent#chair edleafe elmiko dtantsur16:01
elmikoheyo/16:01
openstackCurrent chairs: cdent dtantsur edleafe elmiko16:01
cdentdtantsur: are you around today?16:01
edleafe\o16:01
cdent#link https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda16:01
dtantsuro/16:01
dtantsurcdent: it feels so, but I'm not confident :)16:01
*** rossella_s has joined #openstack-meeting-316:01
cdentI know how that can be16:01
edleafelikewise16:02
elmikohehe16:02
cdent#link last log http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-11-16-16.00.html16:02
cdent#topic old biz16:02
*** openstack changes topic to "old biz (Meeting topic: api-sig)"16:02
cdentI think it's been so long that any biz has died on the vine?16:02
elmikoseems likely16:02
dtantsuryeah, I cannot recall anything already16:03
cdentright then16:03
cdent#topic new biz16:03
*** openstack changes topic to "new biz (Meeting topic: api-sig)"16:03
cdent#link summit session etherpad https://etherpad.openstack.org/p/api-sig-sydney-forum16:03
cdentanything we need to lift from that16:03
cdentthe main topic ended up being sdk related16:03
elmikointeresting16:04
*** janzian has quit IRC16:04
edleafehas anyone heard anything from any SDK folk?16:04
cdentsort of a "how to engage with sdk folk"16:04
cdentsince then? no16:04
cdentbut I think they, like us, have been travelling and turkeying &c16:04
elmikomakes sense16:04
elmikowould be nice to figure out how we can pull some of the sdk folks in closer16:05
*** davidsha has left #openstack-meeting-316:05
cdentAt this stage of the game I don't think there's a specific action for us other than to continue to provide a place for people to talk16:05
elmikoagreed16:05
cdentand if they aren't talking yet, that's okay16:05
elmikoyup16:05
cdentdtantsur: did you ever find my email and if you di, did you decide about your availability?16:06
dtantsurcdent: man sorry, I don't think I even looked for it :(16:06
cdentwell we can do it here? Would you like to be a core reviewer on the guidelines? (as in, do you have to continue doing what you were already doing, with slightly more time?)16:07
dtantsurcdent: you did hit spam :) I'll gladly join you guys16:07
cdent#startvote should dtantsur be a core, yes or no16:07
openstackUnable to parse vote topic and options.16:07
cdentomg16:07
cdent#startvote should dtantsure be core?16:07
openstackBegin voting on: should dtantsure be core? Valid vote options are Yes, No.16:07
openstackVote using '#vote OPTION'. Only your last vote counts.16:08
*** MarkBaker has quit IRC16:08
cdentundo16:08
elmiko#vote yes16:08
edleafe#vote YEs16:08
* cdent breaks everything16:08
* edleafe expects nothing less from cdent16:08
cdent#vote yes16:08
cdent#endvote16:08
openstackVoted on "should dtantsure be core?" Results are16:08
* dtantsur votes meow - just for the sake of voting16:08
cdentwell that went about as well as every other official thing we do16:08
cdentwelcome to the club16:08
edleafewow - lots of votes to tally16:08
cdent#info dtantsur is core16:09
dtantsurthanks :)16:09
cdent#action cdent to update the gerrit stuff16:09
edleafeNow for the initiation rites...16:09
cdentTHEY ARE SUPPOSED TO BE A SURPRISE16:09
elmikoXD16:09
*** stendulker_ has quit IRC16:09
* dtantsur gets ready to hide16:09
cdentany other new biz?16:09
* dtantsur looks at mordred16:10
cdentThe only thing I've got is that I continue to maintain all my good intentions about writing additional guidelines and that summary/frontdoor thing I mentioned a while ago16:10
cdentbut so far they are all good intentions16:10
dtantsur++ a few good intentions here too16:11
dtantsurwell, we're in discussion on how to expose API versions in ironicclient in a saner fashion16:11
cdent#topic guidelines16:11
*** openstack changes topic to "guidelines (Meeting topic: api-sig)"16:11
edleafeI have *lots* of good intentions16:11
dtantsurthis may end up in something readable16:11
cdentundo16:11
cdent#undo16:11
openstackRemoving item from minutes: #topic guidelines16:11
* cdent is at a standing desk, all my typing problems are multiplied16:11
cdentdtantsur: you mean so the client can express which version they want, or so that the version is inferred or what?16:12
cdentI ask because that seems to be a big deal for the non-python SDKs (and for osc as well I guess)16:12
dtantsurcdent: so, now the only thing you can do with ironicclient is to pass api_version into its __init__16:12
dtantsurwhich is a very lame way to use microversions, and it can easily lead to broken upgrades16:13
cdentah, indeed16:13
dtantsurwe want to expose some actual negotiation, make a caller be able to be flexible16:13
*** rossella_s has quit IRC16:13
dtantsurwe have a few options of how precisely that could work16:13
dtantsurand we have a real-world case: nova-ironic interaction16:13
mordredyes - also to allow it to be per-call16:13
cdentthe emerging best practice is allow people to set a version on every request, _if_ they want to, based on what discovery/negotiation has revealed16:13
edleafedtantsur: sounds like a reasonable solution would be the __init__ value is the default used, but individual calls should be able to override16:14
dtantsurwell, yes, but there are still details :)16:14
mordredyah. the keystoneauth options added a default_microversion to the __init__ - and then a microversion= argument to each request/get/post whatnot16:14
dtantsurin our case this ^^^ will require rewriting half of ironicclient, I'm afraid..16:14
dtantsurbut that's a side note16:14
mordredhavne't fully decided how to expose that in the openstacksdk object layer16:14
cdentthat ksa stuff is good soup16:15
dtantsurI'm thinking of getting a guideline, explaining this with a real-world example in Python and *preferably* in some compiled language16:15
* dtantsur looks at his rust-openstack and sighs16:15
cdent:)16:15
mordreddtantsur: well - we could discuss whether or not we can implement what you need in sdk more easier and switch nova to using that instead of python-ironicclient - but that's probably *way* out of scope here16:15
mordreddtantsur: I'd love to work with you on both the guideline ... AND rust-openstack :)16:16
dtantsurmordred: welcome - to both :)16:16
* cdent clones self16:16
dtantsurwell, rust-openstack got to the stage of compiling AGAIN after the switch to newer HTTP library16:16
dtantsurnow, unit tests...........16:16
dtantsurbut that's kinda offtopic :)16:16
cdentnaw mate, we the api-sig now, nearly everything is on topioc16:17
dtantsurhah, true16:17
elmikohehe16:17
edleafeon tapioca?16:17
mordreddtantsur: I keep wanting to do more rust - but the lack of an http library as good as requests is annoying16:17
elmikomoar rust-openstack! \o/16:17
dtantsurmordred: they have something actually, it has a funny name like reqwest16:17
elmikoedleafe: tapioca-openstack?16:17
cdentneither tapioca nor bubble-tea are on topic and while I stand on this hill never will be16:18
dtantsurbut I use Hyper, it's more low level. and it got rewritten a few months ago essentialyl from scratch ._<16:18
dtantsurmordred: https://docs.rs/reqwest/0.8.1/reqwest/16:18
elmikocdent: lol16:19
dtantsuranyway, we should team up with TheJulia and come up with something around this version negotiation topic16:19
cdent+116:19
mordreddtantsur: oh awesome! that wasn't there last time I looked16:19
* TheJulia appears and looks slightly confused16:20
TheJuliaoh, that topic :(16:20
dtantsurTheJulia: about having a guideline on dealing with api versions in SDKs like ironicclient16:20
edleafedtantsur: Reading that code with an Elmer Fudd voice16:20
dtantsurheh16:20
TheJuliaedleafe: lol16:20
edleafehttp://www.barbneal.com/the-collection/looney-tunes/elmer-fudd/16:21
mordreddtantsur: fwiw, TheJulia just added some code to shade that consumes ironic microversion - but the shade story for microversion is likely different than the sdk version16:21
dtantsurI suspect so, but worth checking. #link?16:21
*** shuyingy_ has quit IRC16:22
*** MarkBaker has joined #openstack-meeting-316:22
mordredthe shade pov is, I *think* that users should never know anything about a microversion, and as we add support to shade for more microversoins it should use the best available - and normalize the data model we return to include the various fields with None values if the cloud doesn't support the newer thing16:22
TheJuliadtantsur: https://review.openstack.org/#/c/499774/16:22
TheJuliadtantsur: fwiw, I will be revising it later today to align with mordred POV which I agree with16:22
mordredbut shade is a higher-level do-things-for-you interface ... for the object layer in sdk, I imagine we'll need the ability for a user to request microversion specifics and do negotiation16:22
dtantsur#link https://review.openstack.org/#/c/499774/ shade patch to implement microversions for ironic16:23
edleafe#link https://review.openstack.org/#/c/499774/16:23
mordredthat'll be... interesting ... because the object layer has resource objects that make calls behind the scenes for you ...16:23
dtantsurmordred: I still cannot decide if I should make rust-openstack something like shade or something like clients..16:23
mordredcdent: you had a microversion-consumption-version-negotiation lib somewhere didn't you?16:23
edleafedtantsur: in my experience, SDK users generally want things to "just work"16:24
mordreddtantsur: well.... I got some positive feedback from fokls in sydney about eh approach for the shade/sdk merge ...16:24
*** MarkBaker has quit IRC16:24
dtantsurthat's where I'm leaning too16:24
mordredwhich is that we'll have all three in the same thing -16:24
*** MarkBaker has joined #openstack-meeting-316:24
cdentmordred: server side header parsing, but it includes a handy Version class that might be of some use "microversion-parse"16:24
mordredyou get a Connectoin to the cloud-region16:24
dtantsuresp. since I'm not ready to implement All The Things OpenStack in Rust myself16:24
cdentthere's some pending changes under review that ought to make it a bit more useful16:24
cdentand it can happily grow to become whatever is required16:25
mordredthen from that you can do conn.list_servers() (shade version) conn.compute.servers() (sdk object layer) or conn.compute.get('/servers) (rest fallthrough on the compute endpoint)16:25
cdentpatches accepted etc16:25
mordredso sdk should *always* be usable to talk to all the services in all the openstack clouds at at least the rest layer - and as objects are added or shade fancy functions are added, people can shift to them as they desire16:25
*** rossella_s has joined #openstack-meeting-316:26
mordredcdent: ah yes - cool - I remember that now16:26
dtantsurmordred: that's.. an interesting approach, I like it.16:26
mordreddtantsur: the second two parts of that above strategy work today in sdk master ... haven't combined the shade OpenStackCloud object and the Connection object just yet ...16:27
mordredbut that's mostly just code-reorg work rather than actually hard work16:27
cdentthat onion approach++16:27
dtantsuryeah16:27
dtantsurand it can be developed gradually (still thinking about rust-openstack)16:28
dtantsurstart with list_servers(), keeping compute private until it's ready..16:28
dtantsuror the other way around - depends16:28
* dtantsur has food for thought now, thanks all16:28
*** MarkBaker has quit IRC16:29
cdentUnless someone has something to say about them I think we can skip both the guidelines and bugs topics as they haven't seen any recent action (as explained above).16:30
cdent#topic weekly newsletter16:30
cdent#link https://etherpad.openstack.org/p/api-sig-newsletter16:30
*** openstack changes topic to "weekly newsletter (Meeting topic: api-sig)"16:30
cdentAny takers? I got time if nobody else is dying to do it.16:31
* cdent listens to the crickets16:31
elmikoi have more meetings after this, i'd be thankful for someone else doing it16:31
edleafeMaybe dtantsur would like to give it a go?16:31
edleafeBeing all official and such16:32
cdentI figured since in this one we'd be announcing his ascendancy it would be better if it were someone else. He's on the hook for next week.16:32
dtantsurI'm avoiding that because of my English being not on the same level16:32
* cdent does it16:32
edleafedtantsur: well, the rest of us review before sending it out16:32
cdentI'll ping folk when it's ready for a look16:32
edleafebut yeah, I get it16:32
elmikothanks cdent !16:32
dtantsuredleafe: nice, then it's not so painful :)16:32
cdentGonna switch puters though16:33
cdentThanks everyone for coming and the interesting discussion.16:33
cdent#endmeeting16:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:33
openstackMeeting ended Thu Nov 30 16:33:28 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-11-30-16.01.html16:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-11-30-16.01.txt16:33
openstackLog:            http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-11-30-16.01.log.html16:33
*** dtantsur has left #openstack-meeting-316:33
*** cdent has left #openstack-meeting-316:33
*** belmoreira has quit IRC16:37
*** chyka has joined #openstack-meeting-316:39
*** elmiko has left #openstack-meeting-316:41
*** e0ne has quit IRC16:43
*** MarkBaker has joined #openstack-meeting-316:51
*** d0ugal has quit IRC16:55
*** david-lyle has joined #openstack-meeting-316:59
*** marios has quit IRC17:00
*** iyamahat has quit IRC17:07
*** pcaruana has quit IRC17:08
*** yamahata has quit IRC17:08
*** d0ugal has joined #openstack-meeting-317:08
*** Swami has quit IRC17:12
*** lhx_ has quit IRC17:13
*** gauravsitlani has joined #openstack-meeting-317:16
*** psachin has quit IRC17:18
*** VW_ has joined #openstack-meeting-317:23
*** VW has quit IRC17:23
*** d0ugal has quit IRC17:24
*** jlvacation is now known as jlvillal17:25
*** rossella_s has quit IRC17:27
*** tssurya_ has quit IRC17:31
*** iyamahat has joined #openstack-meeting-317:33
*** d0ugal has joined #openstack-meeting-317:35
*** MarkBaker has quit IRC17:36
*** rossella_s has joined #openstack-meeting-317:42
*** yamahata has joined #openstack-meeting-317:51
*** nikhil has quit IRC17:51
*** cshastri has joined #openstack-meeting-317:51
*** SumitNaiksatam has joined #openstack-meeting-317:53
*** rkukura has joined #openstack-meeting-317:54
SumitNaiksatamrkukura: hi17:59
rkukurahi SumitNaiksatam!17:59
SumitNaiksatamrkukura: seems like just us two today18:01
*** absubram has quit IRC18:01
SumitNaiksatamperhaps should have sent a reminder email about the timing18:01
SumitNaiksatambut dont have much of an agenda either18:01
rkukuramaybe an email before next week would help18:02
SumitNaiksatamrkukura: yeah18:02
*** annakk has joined #openstack-meeting-318:02
SumitNaiksatamthought about it, but didnt want to hype it too much :-)18:02
SumitNaiksatamah annakk is here18:02
annakkhi!18:02
SumitNaiksatamannakk: hi18:02
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu Nov 30 18:02:38 2017 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
rkukurahi annakk18:02
SumitNaiksatamas I was mentioning to rkukura, I dont have much of an agenda for today except the “pike sync"18:03
SumitNaiksatambut i thought it might be good to meet since we havent met for a few weeks for different reasons18:04
* mlavalle waves at rkukura and SumitNaiksatam18:04
SumitNaiksatammlavalle: hi there! :-)18:04
rkukuramaybe we should discuss the stable/newton branch a bit too18:04
SumitNaiksatamrkukura: sure18:04
SumitNaiksatam#topic Pike Support18:04
rkukurahi mlavalle!18:04
*** openstack changes topic to "Pike Support (Meeting topic: networking_policy)"18:04
SumitNaiksatamso we need at least one more reviewer on this: #link https://review.openstack.org/#/c/514864/18:05
SumitNaiksatamrkukura: thanks for your review18:05
rkukuralooks good18:05
SumitNaiksatam(had fixed the devstack gate job prior to this, so it reflects in this patch as well)18:05
SumitNaiksatamannakk: sorry, i might have missed your comment here18:05
annakkI had one comment there but its not a must for sure18:06
SumitNaiksatami saw it before thanksgiving and have been on leave since18:06
SumitNaiksatamtotally forgot about it18:06
annakknp :)18:06
annakkI just thought it was preferrable to limit the hack to aim notifier only18:06
SumitNaiksatamannakk: yes sure, i will respond to the comment18:07
rkukuraI’ll be ready to re-review18:07
SumitNaiksatamand i can also do a follow up patch if required (i might not be able to get to this until monday)18:07
SumitNaiksatami was spending most of my time on this patch #link https://review.openstack.org/#/c/514864/18:08
SumitNaiksatambut the patchset is outdated18:08
SumitNaiksatami have lot more changes in my local repo which i should have posted18:08
rkukurasame patch?18:08
SumitNaiksatamoh sorry18:09
SumitNaiksatam#link https://review.openstack.org/#/c/518183/18:09
SumitNaiksatambasically i was stuck at a transactions issue18:09
*** cshastri has quit IRC18:10
SumitNaiksatamthe new reader/wrtier calls in neutron were breaking the apic driver’s long transaction requirement18:10
SumitNaiksatamhad discussed with rkukura and tbachman offline before18:10
SumitNaiksatamrkukura: thanks for the discussion18:11
rkukuraSumitNaiksatam: Is this an issue for the apic_aim MD, or just the aim_mapping PD?18:11
SumitNaiksatamso it seems like nesting the reader/writer calls will preserve the session18:11
annakkis this a new issue? sounds like a deja vu18:11
SumitNaiksatamstarts with apic_aim MD18:11
SumitNaiksatamrkukura: ^^^18:12
SumitNaiksatamand of course for the aim_mapping as well18:12
rkukuraSumitNaiksatam: was wondering if the problem surfaces in the apic_aim MD UTs?18:12
SumitNaiksatamannakk: the issue is now, the usage of reader/writer is not new18:12
SumitNaiksatamrkukura: yes, those are the ones i was trying to fix all along18:13
SumitNaiksatamso anyway, the nesting seems to work, what was throwing me off was another bug in neutron (in the extend dict part)18:13
SumitNaiksatamwe will still have to patch the reader/writer part for attaching the notification queue to the session (like before)18:14
SumitNaiksatamand for that i am trying to figure out how to get it to work with the context manager18:14
annakkthe extend dict was handled in ocata as well (subnet pools and address scopes)18:15
SumitNaiksatamannakk: yes, but there was a commit made in neutron which moved the extend_dict call to a different point (essentially before post_commit is called)18:15
annakkoh18:15
SumitNaiksatamannakk: and because of that we were never seeing resources extended18:16
rkukuraSumitNaiksatam: Is it called within the transaction now?18:16
SumitNaiksatamrkukura: no18:16
rkukuraThat’s too bad18:16
SumitNaiksatamrkukura: i had meant to sent you the commit last week, somehow slipped my mind18:16
SumitNaiksatamby commit, i mean the patch where this change happened18:17
rkukuraI’d like to see it18:17
SumitNaiksatami cant seem to find it now18:17
SumitNaiksatamit was a patch dealing with MTU setting i think18:17
rkukuralater is fine18:17
SumitNaiksatamrkukura: to fix that would require a small monkey patch in GBP18:18
SumitNaiksatambut having done all that, the UT seemed to pass in my local env18:19
rkukuraok, but maybe there is a reason for the change in Neutron18:19
SumitNaiksatamso that was some progress as opposed to what seemed a bit of a hopeless situation with regards to dealing with the transactions (when i last spoke to rkukura)18:19
SumitNaiksatamrkukura: yes, i think for that particular resource they needed it that way18:19
SumitNaiksatamrkukura: they might have not hit the side effects since other resources might not be using the extension18:20
SumitNaiksatamrkukura: but anyway, you can take look at it and let me know what you think18:20
rkukurasure18:20
rkukuraI’ve always felt extend_dict should be done just before the transaction commits to ensure that the results returned to the client reflect the state commited by the operation18:21
SumitNaiksatamrkukura: agree18:22
SumitNaiksatami was down to some 200 UT failures and most seemed to be related to this transaction issue18:22
*** diablo_rojo has joined #openstack-meeting-318:22
SumitNaiksatami hope there is no other issue lurking18:22
SumitNaiksatamthis was just the UT, so we would still need to update the devstack job to see if everything works properly18:23
*** thingee has left #openstack-meeting-318:23
SumitNaiksatam*UTs18:23
rkukuraso did this reduce below 200 failures with the extend_dict monkey patch?18:23
rkukuraor was it 200 failures with the monkey patch?18:23
SumitNaiksatamrkukura: no no, the 200 UT failures is prior to all the discussion above18:24
rkukuraok, great!18:24
SumitNaiksatamall what i discussed above is not in the lastes patchset posted18:24
SumitNaiksatamand apologies, i should have posted that patchset like a week back18:24
SumitNaiksatami had too many debugs all over the place and didnt get a chance to clean them18:25
SumitNaiksatamanywat18:25
SumitNaiksatamannakk: rkukura anything more to discuss on Pike?18:25
annakknot from me..18:25
rkukuranothing from me18:25
SumitNaiksatamonce the UTs pass, perhaps if anyone has time, we can split work and knock off updating the gate jobs in parallel18:26
SumitNaiksatamrkukura:  we would need to create temp branches for the apic repos18:26
SumitNaiksatamrkukura: hopefully we dont have to do much code updates18:26
SumitNaiksatamwill need to discuss with tbachman18:26
rkukuraright18:27
SumitNaiksatamso far i was just running against the master of those branches and the UTs seemed to be okay18:27
SumitNaiksatambut we should at least have place holder branches18:27
annakkI hope to be able to take some, but in a while cause next week I'm on PTO18:27
SumitNaiksatamnsx is great in that regard since they have long had the pike branches :-)18:27
rkukuraI think we use AIM master for all GBP branches, don’t we?18:27
SumitNaiksatamannakk: np18:28
SumitNaiksatamrkukura: will need to go back and check (aim does use some oslo libs)18:28
rkukuraagreed we need to check18:28
SumitNaiksatam#topic Newton branches18:29
*** openstack changes topic to "Newton branches (Meeting topic: networking_policy)"18:29
SumitNaiksatamrkukura: go ahead18:29
rkukuraI back-ported an AIM-related fix to stable/newton recently, and noticed only a small subset of the UTs run. I understand this is done because the number of cores for stable/newton jobs has been reduced.18:30
SumitNaiksatamrkukura: yes, we went through several iterations on this, and eseentially gave up!18:30
rkukuraSo I tried restoring the full set (we had already eliminated a lot of redundant Neutron UTs from ml2plus)18:30
SumitNaiksatamsince the branch is eol’ed upstream18:31
rkukuraRight. That stlll timed out.18:31
SumitNaiksatamrkukura: right18:31
rkukuraSo I tried running the full set locally. I ran into some failures with my branch, then eventually tried running the full set locally on stable/newton without my branch.18:32
rkukuraThis also hit some failures.18:32
rkukuraSo I think stable/newton may already be in a somewhat broken state.18:32
SumitNaiksatamrkukura: i think there is an ordering issue18:32
rkukuraRight, pretty much any small group of tests would run fine in isolation.18:32
SumitNaiksatamwhich gets exposed when we run subsets, or in local environments18:32
rkukuraI think the schema loading and table clearing stuff isn’t exactly right.18:33
SumitNaiksatami think the config gets carried over to tests18:33
SumitNaiksatamrkukura: yes, that too18:33
SumitNaiksatami think i ran into this in the pike prep branch18:33
rkukuraI cleaned that up with regards to the AIM schema by adding a new AimSqlFixture18:33
SumitNaiksatamrkukura: yes, that was great18:33
rkukuraAnd I spent some time trying to cleanup the way we handle the GBP schema, which uses Neutrons base class, and therefore needs to be handled via Neutron’s StaticSqlFixture18:34
rkukuraBut getting this to work properly requires some work…18:35
rkukuraI think we need to elminate all of the non-fixture schema loading and table clearing code18:35
SumitNaiksatamrkukura: yeah, and the problem is that its pretty to challenging to validate this in the upstream gate (for newton)18:35
rkukuraAnd we also need to ensure that the entire GBP schema is visible in every single test module18:35
SumitNaiksatamrkukura: sure18:36
rkukuraSo I think we should add a new models.py into GBP that imports all the DB model files that use Neutron’s ModelBase.18:36
SumitNaiksatamrkukura: the assumption is that it is currently visible in all the tests that need it18:36
SumitNaiksatamrkukura: okay18:37
rkukuraI think some of the tests don’t import model files that are not needed for that test modules, which means subsequent tests run by the same process fail later18:37
SumitNaiksatamrkukura: okay18:37
rkukuraJust wanted to see if you all thought this analysis made sense18:38
SumitNaiksatamwe do the explicit create_tables thing, which is for sure a red flag, and should not be required if we use the fixtures properly, i guess18:38
rkukuraand if its worth trying to clean it up on master, then backport it to all our active branches18:38
SumitNaiksatamrkukura: per my comment above, the only hole in my understanding is the use of the sql fixture, i thought using that correctly would fix this problem18:39
rkukuraSumitNaiksatam: My conclusion is that Neutron’s StaticSqlFixture should work properly as long as all the GBP repo’s models that use Neutron’s ModelBase are imported in every test module18:39
SumitNaiksatamrkukura: ah, was just saying that, perhaps the import is required in addition to get it to work18:40
rkukuraI think its a combo of not going around the fixture, and making sure the fixture always loads the entire schema for all tests18:40
SumitNaiksatamrkukura: yeah, nice explanation, it makes sense to me18:40
rkukuraannakk: make sense to you?18:40
annakkI need to catch up on this, sorry :)18:41
rkukurano problem18:41
rkukuraAnyway, if it does make sense, I’ll start a new branch and try to get it working18:41
SumitNaiksatamrkukura: sounds good to me18:42
SumitNaiksatamannakk: its a little difficult to follow this discussion without enough context18:42
rkukuraSumitNaiksatam: Did you say this may be currently an issue for the pike sync?18:42
annakkyeah I noticed the cleanup was weird, but never got to the bottom of it18:42
*** absubram has joined #openstack-meeting-318:43
SumitNaiksatamrkukura: i made some spot fixes which eliminated issues with configs not getting loaded correctly (previously it worked since the test were running in a different order in the gate, i guess)18:43
SumitNaiksatamrkukura: so, so far not a blocker for pike sync18:44
SumitNaiksatambut i can only say with confidence if can get the whole suite to pass :-)18:44
rkukuraSumitNaiksatam: OK. If there are fixes related to UT ordering, it would be ideal to back-port those to the older branches18:44
SumitNaiksatamrkukura: okay18:44
SumitNaiksatamwe might have to cherry-pick only part of the change18:45
rkukurasure18:45
rkukurathe other thing with stable/newton...18:45
rkukuraIt seems to me that if infra reduces the number of CPU cores allocated, they should correspondingly increase the overall job timeout.18:46
SumitNaiksatamrkukura: right, that is the source of the timeout18:46
SumitNaiksatamsorry, i missed your “if”18:47
rkukuras/if/when/18:47
SumitNaiksatamrkukura: well, based on my observation, that definitely did not happen18:47
rkukurawhat’s the process to request such a change from infra?18:48
SumitNaiksatamrkukura: i think this can be controlled from our gate job18:48
rkukurareally?18:48
SumitNaiksatami mean, not from our repo18:48
SumitNaiksatambut from our definittion of the gate job in the openstack-infra18:48
rkukuraDo we propose a change in gerrit to do that?18:49
SumitNaiksatambut i wasnt comforable even doing that before we put our house in order18:49
SumitNaiksatamrkukura: yes, but i dont know what is that exact config18:49
rkukuraAny particular part of our house?18:49
SumitNaiksatami believe it would go into the zuul def in project-config repo18:49
SumitNaiksatamrkukura: well we did a part of that by eliminating some UTs18:50
SumitNaiksatamsome of our UTs run for 90 seconds or so18:50
*** pcaruana has joined #openstack-meeting-318:50
rkukuraWe control the timeout for individual UTs in our own repo, so I don’t see that as an issue18:50
*** slaweq has joined #openstack-meeting-318:51
SumitNaiksatamin general, if you see much bigger projects like neutron, their py27 jobs still finish in about 20 mins18:51
SumitNaiksatamso we are doing more than unit testing :-)18:51
rkukurawe are better off with fewer long-running UTs that having many UTs duplicate the same work to get setup18:51
rkukuraright18:51
SumitNaiksatamrkukura: i agree that the philosophy makes more sense for GBP18:51
rkukurabut I don’t see us changing that anytime soon18:51
SumitNaiksatamrkukura: yes18:52
SumitNaiksatamand hence my predicament in going to infra :-)18:52
SumitNaiksatam*going to infra -> approaching the infra team earlier18:52
SumitNaiksatamalso trying to make this case for an eol’ed branch seemed like a tough proposition to begin with18:53
rkukuraIf we just proposed a patch to an infra repo to increase the stable/newton py27 job timeout, explaining that its needed due to fewer cores being allocated, do you think they would reject it?18:53
annakkcan we split the UT to several jobs?18:53
SumitNaiksatamannakk: yes, that is possible, and its a nice novel idea18:53
*** slaweq has quit IRC18:53
rkukuraSeems restructuring UTs is not something that should even be back-ported to a stable branch, let alone for an EOL branch18:54
SumitNaiksatamrkukura: agree18:54
*** slaweq has joined #openstack-meeting-318:54
SumitNaiksatamannakk: but i dont think we would be able to do that for newton branch18:54
rkukuraSo we could promise to work to improve things on our master, while asking for the change on the EOL stable jobs18:54
SumitNaiksatamrkukura: one option is taht we enumerate the tests that we want to run18:55
SumitNaiksatamrkukura: possible18:55
rkukurawas wondering if we could specify a regex or list in testr.conf18:55
SumitNaiksatamrkukura: unfortunately not regex18:55
rkukurathat’s what I concluded too18:55
SumitNaiksatamyou can either give a directory starting point for discovery18:55
SumitNaiksatamor provide a list18:56
SumitNaiksatami havent tried the later, but based on documentation it should be doable18:56
*** gauravsitlani has quit IRC18:56
rkukurawhen running tox manually, you can use a regex on the command line I think, which matches a subset of those discovered18:56
*** gauravsitlani has joined #openstack-meeting-318:56
rkukurawonder if we can change the job to do that?18:56
SumitNaiksatamrkukura: ah, i did not try that, but good point18:56
SumitNaiksatamrkukura: we might have to completely define a new py27 job18:57
annakkI think regex worked for me18:57
SumitNaiksatamannakk: nice18:57
SumitNaiksatamrkukura: we currently use the standard py27 job definition18:58
SumitNaiksatamanyway, we are hitting the hour18:58
rkukuraI’ve never looked at how these jobs are defined18:58
SumitNaiksatamrkukura: i can send you a pointer18:58
rkukurathat’s all from me on stable/newton18:58
SumitNaiksatamrkukura: thanks18:58
*** slaweq has quit IRC18:58
SumitNaiksatamannakk: anything more for today?18:59
SumitNaiksatamannakk: great to read that you enjoyed Sydney! :-)18:59
annakkno18:59
annakk:)18:59
SumitNaiksatamwas planning to put your retrospective on the agenda that following week but we missed the meeting18:59
SumitNaiksatamthanks for your email though!18:59
SumitNaiksatamalrighty thanks rkukura and annakk for joining!18:59
SumitNaiksatambye!18:59
rkukurathanks!18:59
SumitNaiksatam#endmeeting19:00
annakkthanks, bye!19:00
rkukurabye19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu Nov 30 19:00:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-11-30-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-11-30-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-11-30-18.02.log.html19:00
*** annakk has quit IRC19:00
*** rkukura has left #openstack-meeting-319:00
*** SumitNaiksatam has quit IRC20:00
*** shuyingya has joined #openstack-meeting-320:05
*** shuyingya has quit IRC20:09
*** gauravsitlani has quit IRC20:10
*** mguiney has quit IRC20:10
*** mguiney has joined #openstack-meeting-320:11
*** VW_ has quit IRC20:11
*** VW has joined #openstack-meeting-320:12
*** slaweq has joined #openstack-meeting-320:32
*** slaweq has quit IRC20:34
*** slaweq has joined #openstack-meeting-320:34
*** e0ne has joined #openstack-meeting-320:39
*** lyan has quit IRC20:42
*** lyan has joined #openstack-meeting-320:47
*** pcaruana has quit IRC20:55
*** e0ne has quit IRC20:58
*** shuyingya has joined #openstack-meeting-321:00
*** shuyingya has quit IRC21:04
*** raildo has quit IRC21:12
*** ccamacho has quit IRC21:21
*** pcaruana has joined #openstack-meeting-321:24
*** lyan has quit IRC21:36
*** pcaruana has quit IRC21:39
*** mlavalle has left #openstack-meeting-321:53
*** julim has joined #openstack-meeting-321:59
*** julim has quit IRC22:02
*** julim has joined #openstack-meeting-322:08
*** marst has quit IRC22:19
*** shuyingya has joined #openstack-meeting-322:35
*** VW has quit IRC22:35
*** shuyingya has quit IRC22:39
*** VW has joined #openstack-meeting-322:49
*** etingof has quit IRC22:53
*** bobh has quit IRC23:01
*** slaweq has quit IRC23:02
*** kei-ichi has quit IRC23:02
*** slaweq has joined #openstack-meeting-323:02
*** kei-ichi has joined #openstack-meeting-323:04
*** slaweq has quit IRC23:07
*** VW has quit IRC23:20
*** iyamahat_ has joined #openstack-meeting-323:22
*** iyamahat has quit IRC23:22
*** bnemec has quit IRC23:22
*** pbourke has quit IRC23:28
*** pbourke has joined #openstack-meeting-323:30
*** MarkBaker has joined #openstack-meeting-323:32
*** salv-orlando has quit IRC23:41
*** ywat has joined #openstack-meeting-323:48
*** MarkBaker has quit IRC23:54
*** etingof has joined #openstack-meeting-323:59
*** chyka_ has joined #openstack-meeting-323:59

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