16:00:26 #startmeeting Fuel 16:00:27 Meeting started Thu Mar 19 16:00:26 2015 UTC and is due to finish in 60 minutes. The chair is kozhukalov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:32 The meeting name has been set to 'fuel' 16:00:37 #chair kozhukalov 16:00:38 Current chairs: kozhukalov 16:00:43 Hey guys 16:00:47 hi 16:00:47 hi 16:00:48 hey 16:00:48 hi 16:00:48 is anybody here? 16:00:55 hey 16:01:19 thanks to mihgen we have a lot of stuff to discuss today 16:01:28 agenda as usual 16:01:38 #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda 16:01:51 hey 16:01:55 hi 16:01:57 hi 16:02:00 o/ 16:02:03 well let's discuss most critical things 16:02:11 let's start 16:02:14 hello 16:02:23 #topic Separating MOS from upstream ubuntu (vparakhin) 16:02:49 hi 16:02:58 hi 16:03:00 brain461: ^^ 16:03:16 guys, please review this huge patch 16:03:20 There's no major updates in the code for this feature itself. But now we have all required jenkins jobs in place. 16:03:22 #link https://review.openstack.org/#/c/161222/ 16:03:29 yesterday we were blocked by issue with system tests (LP #1431469), but now we're back on track. 16:04:01 what's still left to be done? 16:04:07 this patch is huge but not complex, so I'd encourage you to participate in the review 16:04:46 patch for qa part is not merged, afair 16:04:46 do I get it right that once it's landed into master, we can treat feature being completed? 16:05:07 debian part 16:05:09 Sergey Golovatiuk still has not managed to take a loot at it 16:05:35 he read the patch, will comment later (tomorrow) 16:05:38 brain461: is qa part a blocker? 16:06:13 as long as we want to have working bvt's - yes 16:06:34 anyone from qa here who works on that? 16:06:51 ddmitriev ^^ 16:06:52 brain461: when do we expect to see it from them? 16:08:11 #link https://review.openstack.org/#/c/163824/ 16:08:14 we want to be agile here. We can't hold this thing forever in the review queue. So if holser agrees with overall approach in patch, let's go ahead with merging, but file bug to address particular things 16:08:37 we can't uncover what other issues are waiting for us before we merge this stuff 16:09:07 brain461: it's not QA patch ) 16:09:16 #link https://review.openstack.org/#/c/161058/ 16:09:27 both of them are related 16:10:06 this patch needs to be merged together with brain's one https://review.openstack.org/#/c/161208/ 16:10:59 so basically we are done with code, just waiting for review/merge? 16:11:12 or there is anything else to be done (jenkins config, etc.) ? 16:12:06 mihgen: there are couple patches about dhcp gateway 16:12:21 they are also waiting to be merged 16:12:23 we already had bvts passed with our patches, just need to put all of them together and test again 16:12:36 we need them to make gateway working on slave nodes 16:12:59 to make sure they are able to consume external repos 16:13:06 outside of a lab 16:13:30 do we have repos ready? fuel devops team created those? 16:13:46 upstream repos are ready 16:13:54 in all three locations 16:14:00 ikalnitsky: can you give ETA for merging dhcp related stuff? 16:14:03 sorry, all five :) 16:14:11 hi guys 16:14:15 kozhukalov, yep. 16:14:26 we have merge dhcp patch in library 16:14:31 *merged 16:14:38 and in fuelmenu 16:14:44 wow, great 16:14:44 there's one patch on review for nailgun 16:14:53 #link https://review.openstack.org/#/c/163824/ 16:14:55 brain461: ok. thanks for status. let's push this stuff forward please. Guys, we need to help to land this stuff. 16:15:20 ikalnitsky: yep, let's change 127.0.0.1 -> 10.0.0.1 there pls ;) 16:15:38 ok, if there are no other q here, let's move on 16:15:39 mihgen, no problem. 16:15:48 guys, the scale of changes is enormous. let me encourage all of you to participate in reviews once again 16:15:49 mihgen: you mean 10.20.0.1? right? 16:15:56 kozhukalov: yep 16:16:08 moving on 16:16:26 #topic Consume external ubuntu mirrors (ikalnitsky, devops team) 16:17:01 ok, as i already said - we have merged dhcp patch in library today. 16:17:25 and we have dhcp related patch in nailgun in review 16:17:30 except these patches 16:17:47 we have two patches tp nailgun: one is about downloading initrd 16:17:56 #link https://review.openstack.org/#/c/161208/ 16:18:00 it has two +2 16:18:17 we'll merge it within separate repo patch 16:18:37 and another patch is about upstream defaults in openstack.yaml 16:18:41 #link https://review.openstack.org/#/c/163840/ 16:19:37 what about updates repo for fuel pkgs? 16:20:00 please be aware that everyone from moscow team will be unavailable tomorrow 16:20:01 mihgen, sorry, what do you mean? 16:20:02 is it in yaml? so when we produce updates for nailgun, etc. 16:20:17 oh, got it 16:20:22 yes, it should be in yaml. 16:20:22 packages repo should be available, right 16:20:30 so is it there?0 16:20:38 i didn't add this because i don't know exact location 16:20:49 brain461, could you help me with it? 16:21:00 do we have updates channel online? 16:21:05 that's not good. teran_ should help here, together with aglarendil 16:21:14 ikalnitsky: sure 16:21:18 we need to know location upfront 16:22:04 anyone who know - please add a comment in review 16:22:05 ok, I think the status here is quite clear 16:22:14 moving on? 16:22:20 patching feature FF criteria should be ability to just run apt-get update , if package is placed manually to the required location 16:22:38 ikalnitsky: so please find out location and inject into yaml 16:22:56 thanks, let's move on 16:22:59 mihgen, ok. 16:23:06 #topic IBP (agordeev) 16:23:30 merge status: I'm pleased to announce that all IBP fixes have successfully passed FF. Thanks everyone for participating. 16:23:51 backports to 6.0: 16:23:53 I'm still insisting on backporting of ibp-reconnect to 6.0. Additionaly it will close one of customer-found bugs https://bugs.launchpad.net/fuel/6.0.x/+bug/1389120 16:23:54 Launchpad bug 6 in Launchpad itself ""next 10 entries" at bottom of page" [Medium,Invalid] - Assigned to Carlos Perelló Marín (carlos) 16:23:55 https://review.openstack.org/#/c/161721/ https://review.openstack.org/#/c/161722/ 16:23:57 Let me know should i need to ask for merge exception on mail list or not. 16:24:15 agordeev: but we still need to re-work image build script and fix provision progress bar, right? 16:24:21 right 16:24:26 To deliver IBP only the following 2 thing required (besides bug fixing): 16:24:28 1) to re-implement tool for building image in python 16:24:29 i gonna take next week 16:24:30 2) implement proper progress tracking 16:24:32 Bugs: not so much bugs are still here. Most of them are medium 16:25:02 both those items are critical bugs on launchpad 16:25:05 agordeev: how long would it take to rewrite bash to python for image building? 16:25:32 also few days ago, i was notified by QA folks that swarm jobs are failing. 16:25:34 about reconnects - I think you'd need to raise it in email in openstack-dev.. 16:25:49 mihgen: 2-3w 16:26:26 agordeev: sounds like a little bit too long 16:26:37 that's gonna be too late in release cycle, we would bring additional risks of new python code 16:26:50 can we survive with bash then in this release? 16:27:11 agordeev, let's prioritize it correctly 16:27:13 i'll try to fit into 2w 16:27:15 and prepare & polish python code for the 7.0 16:27:41 agordeev: i believe we can implement the majority of this in just 1 w 16:28:17 kozhukalov: you'd be fixing bugs then for couple more weeks, and release not very stable code at the end 16:28:26 mihgen: bash version is just MVP, and nothing more 16:28:35 it didn't meet FF then 16:28:40 mihgen: actually we can survive, but I'd be strictly oriented on python version of this script 16:29:16 we need to look into details then. Can you please share in the email link to script, amount of work to be done in python, etc. 16:29:27 so we can have a look what risks are there 16:29:28 mihgen: sure, i'll do 16:29:34 thx 16:29:46 about swarm, we need to figure out what's in there 16:30:07 mihgen: if someone with ruby skills can help with progress bar, then i think we can make it happen much faster (i mean image build script in python) 16:30:07 actually since we enabled it by default, I'm curious if everything is ok on our scale lab 16:30:35 mihgen: as i can see, swarm jobs has been failing for 1 month at least 16:30:35 kozhukalov: I know warpc is on vacation, but when is he back? 16:30:44 O_o 16:31:16 let's fix it! why it's so 16:31:33 http://jenkins-product.srt.mirantis.net:8080/view/6.1_swarm/job/6.1.system_test.centos.thread_5/ eg 16:31:37 dpyzhov ^^^ next week. right? 16:32:41 aglarendil: can we give some help from warpc next week? 16:32:58 or he's going to be busy with something else? 16:33:05 ok let's move on. kozhukalov, pls let me know later if you've got warpc 16:33:14 mihgen: ok 16:33:20 then, dilyin might be able to help too 16:33:28 #topic Patching-related things in Fuel (packaging, enabled "updates" repo) 16:34:19 aglarendil: around? 16:34:56 mattymo: who can reply for packaging here? 16:35:54 mihgen: afaik we have merged packages related stuff for docker containers, bootstrap image and centos target images (at least) 16:36:26 thx. it's pity folks are not here for patching. 16:36:29 ok, let's move on 16:36:36 mihgen: but i have no idea about the whole status around this 16:36:37 ok 16:36:54 #topic Fuel Library modularization status (adidenko) 16:37:03 Only ceilometer task is not yet merged from Step #4 of our implementation plan https://github.com/stackforge/fuel-specs/blob/master/specs/6.1/fuel-library-modularization.rst#implementation-plan 16:37:08 Here it is - https://review.openstack.org/163457 16:37:13 We've uploaded new patchsets today and it passes local deployment and OSTF tests, so it's ready for reviews. I'm still running some local tests for it though. 16:37:19 So currently we have over 30 different puppet tasks instead of single site.pp for controller node deployment. 16:37:41 excellent 16:38:02 once it's landed, are we done for 6.1? 16:38:06 yep 16:38:34 cool. Will you document it somewhere, what was splitted, and how to use it? 16:38:41 good to hear this 16:38:47 I'd love to see a single list of separated things 16:39:00 and how to disable some of them, for instace. 16:39:10 it should be pretty handy for field engineers 16:39:21 ok, I'll double-check what we have in docs/specs already and let you know 16:39:51 if there are no other q, moving on 16:39:55 thx. We might want to add some piece into user/dev docs, at least a reference to this spec 16:40:08 we have tasks graph visialisation tools, so it should help to get actual info at any time 16:40:26 you know that we have it, but I'm not yet as a user ) 16:40:38 alex_didenko: is it available in runtime for a user? 16:40:48 so it has to be documented. No need to write poem, but short description would be very beneficial 16:40:56 as far as I know it's available via CLI on fuel node 16:41:09 but did not have time yet to check it myself :) 16:41:26 alex_didenko: that is awesome 16:41:36 ok, next topic 16:41:42 we have a card on our trello board about doc, so we'll take care of it 16:41:54 #topic Ability to add roles via REST API (dshulyak) 16:42:19 looks like dshulyak is not here 16:42:35 is there a link for it? 16:43:04 xarses: i have no idea if there is one 16:43:09 let's move on for now, and try to catch dshulyak later 16:43:16 I'm trying to get him in skype 16:43:36 #topic Fuel plugin notification in the UI (evgenyl) 16:45:03 evgenyl is also not here 16:45:12 aglarendil: around? 16:45:51 evgeniyl___: #topic Fuel plugin notification in the UI (evgenyl) 16:45:57 Hi guys. 16:46:03 evgeniyl___: great, to see you here 16:46:18 evgeniyl___: could you please give us status about 16:46:27 Fuel plugin notification in the UI 16:46:35 Actually we've implemented the feature. 16:46:38 #link https://review.openstack.org/#/c/164256/ 16:46:48 Now we show a list of installed plugins. 16:46:54 With their descriptions. 16:47:14 Also the same information is in notification. 16:47:55 Any questions? 16:47:58 That is all. 16:48:07 Can a plugin throw some notifications just after it was installed? 16:48:11 so, it's been merged and works, no q from my side 16:48:17 It was not a big deal to implement, but in the next release we should come up with more proper solution. 16:48:44 adanin: plugin cannot create any custom notifications or banners or anything else. 16:48:44 can we refresh the plugins list in a created, but not deployed cluster now? 16:48:46 thx. Q: do you use description field in meta of a plugin? 16:48:47 adanin: so far. 16:48:59 mihgen: yes. 16:49:34 xarses: no, you cannot do that. 16:49:47 =( 16:50:10 what do you mean under refresh ? 16:50:10 xarses: we have plans to rewrite this part, to provide better deletion mechanism and as result it can help with enabling plugins after env creation. 16:50:48 mihgen: currently there is no way to see checkbox on settings tab, after environment is created, even if new plugin was installed 16:51:03 mihgen: user has to recreate the env, to see new plugins. 16:51:35 xarses: did I get your question correctly? 16:51:42 well it's fair limitation I would say 16:51:55 evgeniyl___: seems yes 16:52:04 for now) Let's see if we can get rid of it in next release though 16:52:12 how much efforts it would take 16:52:40 ok thx evgeniyl___ 16:53:09 ok, we have 7 minutes 16:53:31 and looks like dshulyak and aglarendil are unavailable 16:53:44 open discussion then 16:53:52 #topic open discussion 16:54:09 does anybody have anything to discuss? 16:54:42 looks like noone has. 16:54:46 can we get review / merge on 16:54:53 #link https://review.openstack.org/#/c/158996/ 16:55:07 #link https://review.openstack.org/#/c/164038 16:55:41 5 people set +1 for the first of this patches 16:55:46 let's merge it 16:55:52 looks like there's enough consensus to merge them both 16:56:16 angdraug: yep 16:56:20 xarses: is that the last of openrc fixes? 16:56:53 angdraug: were there other fixes? 16:57:08 angdraug: no, https://review.openstack.org/#/c/158995/ is still open 16:57:21 It's broken and I need to fix it 16:58:07 ok 16:58:36 ending? 16:58:51 thanx everyone for attending 16:58:56 great meeting 16:59:04 #endmeeting