16:01:52 #startmeeting Fuel 16:01:53 Meeting started Thu Oct 2 16:01:52 2014 UTC and is due to finish in 60 minutes. The chair is kozhukalov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:57 The meeting name has been set to 'fuel' 16:02:20 #chair kozhukalov 16:02:21 Current chairs: kozhukalov 16:02:28 agenda as usual 16:02:34 #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda 16:02:58 #topic announcements 16:03:06 mihgen: your turn 16:03:43 hi guys 16:04:00 our key drivers for the current release are the following: 16:04:45 1) Juno support in 6.0; 2) Pluggable architecture MVP: https://blueprints.launchpad.net/fuel/+spec/cinder-neutron-plugins-in-fuel, 3) 100-nodes support certification: https://blueprints.launchpad.net/fuel/+spec/100-nodes-support 16:05:08 Release schedule is available here with all important dates: 16:05:10 #link https://wiki.openstack.org/wiki/Fuel/6.0_Release_Schedule 16:05:42 that's all from short announcement, let's move on the agenda 16:06:06 mihgen: thanx 16:06:19 #topic CI BVT status (nurla) 16:06:58 nurla: around? 16:07:50 ok, maybe it is better to postpone this topic? 16:07:58 let's pospone 16:08:09 #topic Juno support status (mattymo) 16:08:36 We're moving along in Juno with some really good pace now finally 16:08:56 A lot of things fell into place this week. Neutron glance and some client dependency issues were fixed 16:09:15 All we have broken right now is haproxy (already rebuilt but not tested) and murano package renaming, which should be also resolved today 16:09:39 We can already deploy Juno with all modes, except Murano and with HA on CentOS. HA Ubuntu works 16:09:58 We're expecting a community friendly ISO hopefully next week 16:10:06 (that's it from me) 16:10:22 mattymo: thanx a lot 16:10:28 moving on 16:10:30 btw fuel core, please review CRs required for Juno support 16:10:30 so is it correct that partner can test their feature against Juno already? 16:10:39 dmitryme+++++++++ 16:11:16 it is just really annoing to build custom ISO with 20+ patches 16:11:35 *annoying 16:12:11 that is all :-) 16:12:13 eshumkher, in HA, wait till tomorrow. As long as you don't need murano for testing 16:12:14 from em 16:12:17 * me 16:12:40 mattymo, thanks, got it 16:13:30 ok, moving on 16:13:43 #topic external CI  (eshumakher) 16:14:09 ok, my turn 16:14:24 i believe everyone saw the email in the ML 16:14:38 are devops folks here? 16:14:52 igor, sasha? 16:15:07 teran__: ^^ 16:15:14 devops: ^ 16:15:29 whatever, my proposal is to describe the strategy for Fuel external CI 16:15:45 make a couple of rounds of discussions 16:15:52 eshumkher: yeap 16:16:09 make an announcement and webcast for those who are interested 16:16:17 and move on with implementation 16:16:47 teran__, bookwar, would you drive it? 16:17:14 I think you guys should discuss it verbally first 16:17:20 understand use cases better 16:17:26 eshumkher: yeah, we're planing to start doc implementation in few time 16:17:31 eshumkher: but not right now 16:17:36 might be we can have do something simple for the beginning 16:17:46 documentation doesn't solve the issue, right? 16:17:53 eshumkher: I see it's high for you, but we need to determine how it wil look first 16:18:09 let's meet and understand use cases - then see what can be made fast 16:18:13 yes, the doc is an output 16:18:28 I want to participate in the discussion 16:18:32 but someone should work on the process, who will take ownership? 16:18:38 ok, let's give an action for eshumkher to talk to devops guys verbally 16:18:57 eshumkher: I'll take it from CI side 16:19:11 ok 16:19:43 but i would let’s make an action item to get external CI’s for 6.0 16:19:52 relese 16:19:56 *release 16:20:01 #action eshumkher talks to devops guys about external ci for plugins 16:20:12 moving on? 16:20:15 yep 16:20:30 #topic Cinder/Neutron plugins (evgeniyl, nmarkov) 16:20:35 hi 16:20:41 We have draft for the feature, https://review.openstack.org/#/c/125608/3 you can review and leave your comments there. 16:20:57 Stanislaw B. started to create scripts for lbaas configuration and installation, it will be one of the POC plugins. 16:21:03 there are a few already on first patchset, feel free to join 16:21:14 Also we are going to use ClusterFS and/or NFS as an example of Cinder plugin. 16:21:41 The first thing which we want to do is to make POC of LBaaS plugin. 16:22:36 evgeniyl__: thanks, good 16:22:54 great 16:23:14 there is also another spec for fuel plugins as a whole 16:23:22 feel free to contribute, as well 16:23:50 #link https://review.openstack.org/#/c/118610/ 16:23:58 ok, thanx guys 16:24:02 moving on 16:24:21 #topic reduce upgrade tarball size aka diff-based repo (ikalnitsky) 16:24:27 hi guys 16:24:32 the feature is in progress. here the spec: 16:24:33 hi 16:24:36 #link https://review.openstack.org/#/c/121591/ 16:24:45 as for now, we have draft versions of scripts for generating diff-based repos, so we can compare a full-repo with diff-based one. 16:24:58 unfortunately, the results are not as we expected earlier - a diff-based repo weights 40-50% less in compare with a full one. 16:25:12 there is an idea to use deltarpm/deltadeb tools which should allow us to distribute diff-based packages. 16:25:34 as for other parts - nailgun and astute don't require any changes and works fine. i belive we can start configuring a jenkins job and change our make system on Monday. 16:26:16 ikalnitsky: ok. are you aligned with devops team on CI jobs? 16:26:17 any comments on the spec are welcome. :) 16:26:34 are we still including the whole set of packages into an update? are we really repackaging everything for new releases? 16:26:42 mihgen: yep 16:27:21 angdraug: in 6.0, for example, we have a lot of system packages that have changed another hash sum 16:27:29 angdraug: so we need to distribute them too 16:27:50 did we have to change them? 16:28:18 did you think about kind of binary deduplication? 16:28:28 angdraug: not directly. we change, for example, just one library, so all packages that are linked to that library statically should be rebuilt 16:28:28 is it possible at all? 16:29:04 I seriously hope we don't have statically linked binaries :/ 16:29:50 angdraug: as far as i know, we do. :( 16:30:23 how many? 16:30:25 examples? 16:31:14 angdraug: i don't have a number. i need to request osci team, i think. but as far as i remember, some packages link statically to libssl. 16:32:09 $ diff -u 5.1.html 5.1.1.html |grep ^+|wc -l 16:32:09 502 16:32:14 $ grep deb 5.1.html|wc -l 16:32:14 1181 16:32:30 so at least half of our packages are exactly the same between 5.1 and 5.1.1 so far 16:33:15 folks can you guys discuss it in more details in #fuel-dev please? 16:33:21 and that is why diff repo takes 50% only of the 5.1 16:33:25 moving on 16:33:40 angdraug: ikalnitsky don't forget about it though ;) 16:33:45 #topic granular deployment: needs config files upload mechanism, testing, will be ready for a merge as experimental by the end of next week (dshulyak) 16:33:51 hi 16:33:57 hi 16:34:02 we need to prepare configs for all roles 16:34:10 next week i will show demo with tasklib approach, and difference with using ansible as task executor 16:34:14 if everyone will be ok with tasklib api, we can start merging patches 16:34:37 as experimental 16:35:29 that is all from me 16:36:08 sounds great, but what about mixing different disk allocations for different roles when they are on the same node? 16:36:25 dshulyak: looking forward to see a demo.. next week? 16:37:26 kozhukalov: this is more about plugable architecture, meow-nofer have POC in ceph plugin for doing such things 16:38:05 mihgen: yes, it works already, so next week for sure 16:38:23 ok, moving on 16:38:43 #topic Status of implentation of 1-1 mapping between nova-compute and vSphere cluster (izinovik) 16:39:10 hello 16:39:16 Blueprint: 16:39:16 #link https://blueprints.launchpad.net/fuel/+spec/1-1-nova-compute-vsphere-cluster-mapping 16:39:16 hello 16:39:28 Specification of 1-1 mapping: 16:39:28 #link https://review.openstack.org/#/c/118998 16:39:28 Here is more friendly HTML generated variant: http://docs-draft.openstack.org/98/118998/13/check/gate-fuel-specs-docs/f7a48a8/doc/build/html/specs/6.0/1-1-nova-compute-vsphere-cluster-mapping.html 16:39:38 fuel-library/ part: 16:39:38 #link https://review.openstack.org/122242 16:39:38 People who are familiar with Puppet are welcome 16:39:47 I manually tested CentOS and Ubuntu with vCenter (both in simple and HA deployment modes). 16:39:47 Deployment works smooth, but CentOS cannot provision VMs due to bug #1376683 (srogov@ is 16:39:48 working on it with good progress). OpenStack on Ubuntu works fine. 16:39:49 Launchpad bug 1376683 in fuel "Service glance-api not starting when deploy HA and Glance backend is vCenter" [High,New] https://launchpad.net/bugs/1376683 16:40:00 Currently from end user perspective everything look same, but we need significant UI 16:40:00 changes to implement specification of different credentials for different vSphere 16:40:00 clusters and provide an opportunity to add vSphere clusters to deployed OpenStack environment. 16:40:11 More blueprints will follow for UI part and Nailgun. 16:40:42 don’t you think it can be done in 1 BP? 16:40:59 I do not know 16:41:06 just to extend the one you have? 16:41:12 in my opinion current spec is a bit overloaded 16:42:06 and scope of blueprint is too wide (IMO) 16:42:30 izinovik: thanx 16:42:42 if no q then moving on 16:42:45 ok, thats all from my side 16:43:13 #topic Anonymous statistics collecor (akislitsky) 16:43:18 hi 16:43:22 we have prototype of stats collector, repo on stackforge, working on saving action logs in the Nailgun. next week we are planning to integrate services together and process data from Nailgun. as analytic engine we are trying to use Elasticsearch. it provides all our reports requirements. next week demo we can show data exchange between Nailgun and collector. and may be some UI for analityc based on Kibana. also we are initiated implem 16:43:22 entation of Nailgun UI. 16:44:30 what about VM with it running? 16:44:42 I think we need some fixtures generated for collector 16:44:53 in order to be able to see how it reports data 16:45:18 VM will be ordered next week by DevOps 16:45:20 and make it available as soon as possible to review - so we can react and change approach for reports before release 16:45:35 why only next week?) 16:45:45 per your request or devops can't do it earlier? 16:46:27 mihgen: akislitsky_ we can do it anytime 16:46:40 mihgen: akislitsky_ anyway we need packages built by OSCI 16:47:15 what packages? I'm fine if we start with simplest bash scripts, and then replace it week later with packages 16:47:16 ok, that will be great. all is ready for packaging now - repo with setup.py, requirements and tox. 16:47:38 akislitsky_: so please request OSCI to package that stuff 16:47:42 tox run on VM for the beginning is all what we need to start seeing how it works 16:47:56 this is not production VM (I assume) 16:48:02 it's for development 16:48:08 like fuelweb.vm.mirantis.net:8000 16:48:09 mihgen: not development - testing 16:48:12 teran__, I will request OSCI 16:48:55 for developing we don't need VMs 16:49:03 10 minutes - 2 topics 16:49:16 moving on? 16:49:23 akislitsky: it's for me to see it, and give feedback 16:49:26 and for QA 16:49:44 so let's make it easy for me and some business ppl who don't know how to run tox :) 16:49:51 let's move on.. 16:49:57 akislitsky_: mihgen I thing we could start performance testing when it will be done 16:50:08 mihgen, got it 16:50:21 #topic authx improvements (prmtl) 16:50:28 we are having very good progress, first changes are on review 16:50:28 #link https://review.openstack.org/#/q/status:open++topic:bp/access-control-master-node-improvments,n,z) 16:50:28 we got rid of usage of admin token and both nailgun and ostf have now it’s own service users in keystone on fuel master 16:50:30 next step now is to make upgrade ask for admin password so user doesn’t have to change it in astute.yaml 16:50:32 specs still wait for +1’s (or comments): 16:50:34 #link https://review.openstack.org/#/c/118284/ 16:50:38 that's all 16:50:55 teran__, I gave requirements to Alex for VMs. use them for request, please 16:51:07 akislitsky_: Ok 16:52:49 ok, if no questions, moving on 16:53:07 prmtl: thanks 16:53:08 #topic 100 nodes (loles) 16:53:19 hi 16:53:22 This week we were focusing on nailgun. Kamil finished writing load tests for API with nice graphs which shows slow functions. It's under review now. 16:53:22 #link https://review.openstack.org/#/c/123967/ 16:53:22 #link https://review.openstack.org/#/c/118123/ 16:53:25 Roman is writing tests for fuelclient. We have first Rally scenario for Fuel. Next week we are starting to work on astute. There are still some comments in blueprint, but it's bassicly ready. 16:53:25 #link https://review.openstack.org/#/c/119400/9/specs/6.0/100-nodes-support.rst 16:53:30 From Matt about pressed download impovement and dhcp timeouts: 16:53:31 1 - merged into fuel already is a patch to retry downloading ubuntu preseed file 16:53:31 2 - testing a config change to raise DHCP timeout in Ubuntu for scaling 16:54:01 preseed not pressed :) 16:54:06 prmtl: please make sure nurla knows about it, it has to be covered by system tests. Also I thought we gonna do services token, so no requirement to interactive mode asking for a password 16:54:20 mattymo: sorry:) 16:55:02 salmon_: great! 16:55:43 no questions at the moment from me.. kozhukalov, should we move on? not much time left 16:56:06 we don't have any other topics 16:56:18 ooops 16:56:21 we do 16:56:41 #topic Moving development docs from fuel-dev to fuel-docs is in progress, will be done soon as I sort out an issue with building PDFs 16:56:58 just wanted to let everyone know it's in progress right now 16:57:05 who was that who added this topic at the last moment? ) 16:57:24 kuzhukalov: me, just wanted to make a little mention of it 16:57:41 christopheraedo: thanx 16:57:51 let's leave links right here 16:58:02 #link https://blueprints.launchpad.net/fuel/+spec/fuel-dev-docs-merge-fuel-docs 16:58:15 #link https://review.openstack.org/#/c/125234/ 16:58:29 ok, i think that is it 16:58:30 christopheraedo: next time, please add you items to the agenda _before_ the meeting starts :) 16:58:39 great meeting 16:58:47 thanx everyone 16:58:50 If anyone has deep experience with the autogenerated API docs, ping me please - and I'll add BEFORE next time ;) 16:59:13 meow-nofer___: has, I think 16:59:28 ok, guys, ending 16:59:33 Thanks. 16:59:36 #endmeeting