14:01:34 <[1]JonasB> #startmeeting Fuel OPNFV status No6 14:01:34 Meeting started Thu Apr 16 14:01:34 2015 UTC. The chair is [1]JonasB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:34 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:34 The meeting name has been set to 'fuel_opnfv_status_no6' 14:01:48 <[1]JonasB> #topic RC2 status 14:02:13 <[1]JonasB> Status on KVM deploy - Stefan, please use info 14:02:55 #info The full deploy chain is completed for libvirt, "deploy.sh " will spin up the environment. 14:03:25 #info Fatih has integrated with Jenkins and we're using blade 15 to test this. 14:03:56 #info The commit for this is finalized and ready for approval/merge. 14:04:00 #link https://gerrit.opnfv.org/gerrit/#/c/306/ 14:04:23 That's it. 14:04:32 Oh. 14:04:41 <[1]JonasB> Cool, we can soon declare victory for RC2 14:04:52 #info The deploy is one Fuel master, three controllers, two computes, full HA with Ceilometer. 14:05:20 <[1]JonasB> #info first cut of documentation done and merged into the repo. 14:05:40 #info - comment on that 14:05:55 <[1]JonasB> #docs will be built in RC2 and put on the google artifact repository 14:06:27 <[1]JonasB> yes Daniel 14:07:21 #info for nested environments with such a payload (3x3 and that turned on) - have you done this anywhere before? I have had failures (to to massive i/o wait at the disk, when trying to fire three controllers on a single blade) 14:08:48 We can scale back on that, but yes, I've done it before - that was the smoke test for 15A :) - and usually works OK. 14:09:29 #info - on your own setup Sberg or elsewhere? - i guess my question is more of - is that something we really want to push - that layout - for nested environments. Judging from the support questions we have receivd thus far, i can see it being a bit of a hassle - can we simply have two profiles (a simple MultiNode - no Ha and bells/whistles) and then the full HA one 14:09:49 It's pretty easy to tune this (look in functions/deploy_env.sh) for a smaller config. 14:09:52 #info - it will make sense in the long run cause we can have simple test (smoke test) on smaller profile) and larger / longer ones 14:09:55 ok 14:10:05 <[1]JonasB> #info I have now rebsed fuel due to upstream repo changes 14:10:09 just thinking about testing times / deployment cycles from jenkins 14:10:30 <[1]JonasB> Stefan and szilard, you need to rebase your patch sets. 14:10:34 ok 14:11:05 #info The plan moving forward is to have the "create_dea.sh" script detect also node roles, and then I'd suggest to turn our example into a non HA one, that makes sense yes. 14:11:29 #info - as part of my nested i will end up doing it anyway 14:11:57 #info - since i will use your structure to pass a common "profile" so that we dont have two different formats for two different types (or other hypervisors we add later) 14:12:27 <[1]JonasB> Okay, is that all for RC2? 14:13:18 <[1]JonasB> #info GREAT WORK DONE EVERYONE, REALLY APPRECIATED! 14:13:46 <[1]JonasB> So lets go to the items for RC3 next week? 14:14:02 <[1]JonasB> #topic debootstrap patch 14:14:06 * stefan_berg nods 14:14:19 I prepared change which will fix debootstrap problems 14:14:21 <[1]JonasB> mskalski: updates? 14:14:25 #link https://gerrit.opnfv.org/gerrit/#/c/351/ 14:14:32 I need to test it more, but today it will be ready 14:14:49 make sure you rebase before you push :) 14:15:18 I think I included last Jonas commit 14:16:30 when it will be done I will add you guys as reviewers 14:16:43 then switch to work on centos integration 14:17:48 <[1]JonasB> #info mskalski and all: Seems that you need to add revievers, otherwise it is not vissible to others. I think that behavior has changed in gerrit lately. 14:17:51 I think questions coming for you 14:17:55 in opnfv-meeting 14:18:16 nope, skipped 14:18:29 <[1]JonasB> Multitasking :-) 14:18:59 <[1]JonasB> # info mskalski: so add all of us as reviewers. 14:19:08 <[1]JonasB> Great Michal 14:19:40 <[1]JonasB> So lets move on to next topic - Centos 14:19:51 <[1]JonasB> #topic Cento support 14:20:03 <[1]JonasB> mskalski: any update? 14:20:43 [1]JonasB: I was focused on debootstrap, today it will be ready and I will come back to centos integration 14:21:23 <[1]JonasB> #info Centos work will start from tomorrow. 14:21:34 <[1]JonasB> mskalski: Thanks 14:23:44 <[1]JonasB> Lets move on to autodeploy 14:24:01 <[1]JonasB> #topic Auto deploy 14:24:12 <[1]JonasB> Szilard - updates 14:24:49 [1]JonasB: okay, so I'm adding the last bits for Autodeploy, tommorrow I start testing on Nested Environment 14:25:30 but the Libvirt Adapters are missing, I will take from Stefan's code and integrate it into mine ... 14:26:14 depending on which type of environment you want to run it, you need either ESXi Adapters of Libvirt Adapters 14:26:15 <[1]JonasB> Szilard, can you "info" your updates 14:26:20 sorry 14:26:48 you wan't me to do shoot it again ? :) 14:27:04 with info 14:27:16 <[1]JonasB> Yes please 14:27:19 ok 14:27:33 #info I'm adding the last bits for Autodeploy, tommorrow I start testing on Nested Environment 14:27:43 #info but the Libvirt Adapters are missing, I will take from Stefan's code and integrate it into mine 14:27:48 # depending on which type of environment you want to run it, you need either ESXi Adapters of Libvirt Adapters 14:27:53 #info depending on which type of environment you want to run it, you need either ESXi Adapters of Libvirt Adapters 14:28:06 that's all 14:28:30 <[1]JonasB> Great szilard 14:28:40 <[1]JonasB> Stefan Updates 14:29:16 #info Tuning of how the libvirt DEA is created and used at deploy. 14:29:46 #info Then looking into how to move forward together with Daniel and Szilard for real iron deploy. 14:30:44 stefan_berg: this will be Cisco, we have to do the Hardware Adapters for that as well 14:30:47 #info Hopefully the deployement logic of my libvirt prototype can be reused for the main functionality. 14:31:17 #info - i have ciso and hp prototype (on/off attach media) working - delivered for friday or monday along with esxi adapter 14:31:24 <[1]JonasB> stefan_berg: Great, maybe a place for an audio call on how to bring all pieces together for the final? 14:31:46 bgs status reporting coming 14:31:46 [1]JonasB: That's a good idea, let's do an audio/Etherpad call on Monday! 14:31:53 opnfv-meeting 14:32:43 <[1]JonasB> So lets move on to our fantastic lab 14:32:52 <[1]JonasB> #topic Lab status 14:32:57 ok.. my update above for autodeploy was enough then? 14:33:12 <[1]JonasB> #undo 14:33:12 Removing item from minutes: 14:33:26 <[1]JonasB> Daniel, sorry go on 14:33:51 <[1]JonasB> I dont really have what it takes to be in two parallel meetings 14:34:36 #info - esxi adapter works, will rebase with autodeployable ISO from SBerg and hook in a jenkins slave to esxi for Friday 14:34:51 * stefan_berg wonders if we should go for a 10 meeting coffe break in this meeting? 14:34:57 #info - HP adapter prototype work (API method) for attach, on/off or 14:35:09 #info - Cisco done as well - only against Simulator 14:35:18 #info - will merge Friday night and set reviewers 14:35:24 thats all 14:35:43 <[1]JonasB> lmcdasm: That is cool, using their python SDK? 14:35:46 lmcdasm: Just to be clear, this autodeploy stuff is not on the ISO, only in the repo. 14:35:48 #info yes 14:36:10 <[1]JonasB> Daniel: thanks! 14:36:14 <[1]JonasB> Now to lab 14:36:17 OK, now Jonas will do a report in the meeting. 14:36:23 #stefan_berg - understood - i meant im gonna clone your setup to blade 15 from my own build server 14:36:25 Frank s asking for Fuel update Jonas. 14:36:26 <[1]JonasB> #topic Lab status 14:36:39 [1]JonasB: now the question asked for Fuel status 14:36:56 Let's take five, people. :) 14:39:01 :D 14:41:47 argh - too many windows - i meant to ask in here to Jonas - can i get HW access for the LF stuff and ill just do the setup/install there. 14:42:22 <[1]JonasB> lmcdasm: I will fix that for you! 14:42:46 ok - i mean, might as well just do it since we are (or i am) in a build-out / install mode 14:43:49 <[1]JonasB> lmcdasm: Makes sense 14:45:21 <[1]JonasB> lmcdasm: Labstatus since yesturday use "info" 14:48:19 <[1]JonasB> #info Daniel have the nested environment up, documented on the Wiki 14:49:22 [1]JonasB: super great 14:49:38 <[1]JonasB> #link https://wiki.opnfv.org/_media/get_started/opnfv_montreal_lab-revc.pdf 14:50:49 <[1]JonasB> So can we move on to next topic - repo mirror 14:51:00 uh hno 14:51:09 i have outstanding questions on the Lab for you and Stefan 14:51:15 for finsihing the repo/web cloner 14:51:19 and getting that done today 14:51:29 sorry - lemme try again 14:51:35 <[1]JonasB> That is the next topic 14:51:37 #info - outstanding questions on the repo/web server 14:51:47 <[1]JonasB> #topic Local repo mirror 14:51:56 <[1]JonasB> lmcdasm: shoot 14:51:57 #info - outstanding questions on the repo/web server 14:52:22 #info - system is ready and staged - need to know how much / where desired clone point is 14:53:08 #info - as soon as input is received ITTE will set firewall and we can point the build sytems at the CLONE_REPO in config.mk (probably some nicer code if you want options as outlined is good). 14:53:31 #info - will take about 1 hour once i create the domain name for DNS around the world to update and we are in business 14:53:34 thats it 14:53:34 <[1]JonasB> mskalski: Can you/Mirantis help here? 14:55:52 <[1]JonasB> lmcdasm: Do you know how to set up the mirrors or do you need help from Mirantis? 14:55:53 [1]JonasB: what kind of help is needed? Poiting to external repo I described yesterday in mail, regarding clone point it can be also done in config.mk 14:56:00 #link http://docs.mirantis.com/fuel-dev/develop/env.html 14:57:36 #info - the question is not just about the FUEL_REPO Pointing - there are the other repos in config.mk and other upstream items that we use. The question about what we are "snapshoting" from upstream is more to the focus of my point 14:58:26 #info - for example other libs in our build, and do we want to freeze other parts as well - working towards having the structure that i outilned in the mail on the server for dealing with control of the repo, etc. 14:59:24 <[1]JonasB> lmcdasm: Lets figure that out off-line you and I tonight 14:59:27 #info - simply setting up a "mirror" of their Repo is not what we want, otherwise we are just a hop in the chain - anyway - if you can take a look at the mail and send me an answer to the questions that would be wonderful. 15:00:04 lmcdasm: so you mean ubutnu/centos repos which can be configured here? https://github.com/stackforge/fuel-main/blob/master/config.mk#L191? 15:00:07 #info - since a mirror (nightly) will change in sync with others - we want to "freeze" frame the upstream and control it - to match with released / builds (and now the auto-deploy and testing parts). 15:00:21 <[1]JonasB> #action Jonas and Daniel to come with a mirror strategy proposal 15:00:43 #mskalski = yes - that is a part of it correct 15:03:13 <[1]JonasB> Can we end here? 15:04:11 <[1]JonasB> 1 15:04:38 <[1]JonasB> 2 15:04:46 :) 15:04:51 <[1]JonasB> 3 15:05:05 <[1]JonasB> THanks everyone for a fantastic work 15:05:13 <[1]JonasB> #endmeeting