16:00:23 #startmeeting OPNFV BGS - the last daily release readiness meeting 16:00:23 Meeting started Wed Jun 3 16:00:23 2015 UTC. The chair is frankbrockners. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:23 The meeting name has been set to 'opnfv_bgs___the_last_daily_release_readiness_meeting' 16:00:37 #info Frank Brockners 16:00:46 #info Jonas Bjurel 16:00:47 #info Tim Rozet 16:01:01 #info Morgan Richomme 16:01:03 #info Fatih Degirmenci 16:01:05 #info chris price 16:01:23 #info Uli Kleber 16:01:30 ping jose_lausuch - take a short break 16:02:07 wow - really quickly reaching a quorum today... and things look god 16:02:08 #info Dan Radez 16:02:09 good 16:02:33 let's quickly go through the laundry list and then see what additional open items we still have 16:03:01 #info Daniel Smih 16:03:05 with laundry list I mean bullets 1. - 5. 16:03:06 #info Jose Lausuch 16:03:31 ChrisPriceAB: I'll do :) 16:03:40 sorry Frank - you can lead since we are all not looking ath the agenda list 16:04:07 #topic updates on laundry list (1. POD 1 autodeploy, 2. Foreman ISO, 3. Test documentation, 4. vPing functional, 5. ODL tests completing) 16:04:33 jonasbjurel - quick update on POD1 w/ ODL? 16:04:34 #info POD1 autodeploy has run succesfully for month.. a bug was found in the new ODL code and updates 16:04:46 #info were pushed, re deploy is running now 16:04:56 #info jose will run funtest afterwards 16:05:07 https://build.opnfv.org/ci/view/genesis/job/genesis-fuel-deploy/lastBuild/console in case someone is interested 16:05:16 thats it 16:05:20 its like watching an episode of game of thrones :) 16:05:26 lol! 16:05:30 :D 16:05:43 when do you think you'll be ready to tag the .iso? 16:05:50 winter is coming Jose... 16:05:59 #Info docs almost final 16:06:01 * ChrisPriceAB thinks after the deploy and test? 16:06:01 :D 16:06:02 code is frozen now 16:06:05 that's why you call it FUNtest 16:06:09 i wont be doing any more updates for this release 16:06:11 #info Foreman ISO installs successfully. It's in good shape. We have some planned update for it for R2 16:06:34 frankbrockners: whom did you ask? 16:07:13 we must first get all the genesis docs merged 16:07:16 If we're code frozen then it's a matter of catching state, updating docs and tagging right? 16:07:17 and then build new ISOs 16:07:25 jose_lausuch: anyone who worked on the Fuel autodeploy with ODL 16:07:37 and then we tag the repo (not the ISO) 16:07:37 ah ok 16:08:43 so question is when do we expect to have a "final" iso for fuel 16:08:59 my thinking is that you take what you have now 16:09:05 nope 16:09:06 lmcdasm, we are code frozen right? 16:09:07 the iso is just built 16:09:21 cause there wont be any changes to FUEL or others coming 16:09:22 then the sha1 for the iso won't match to sha1 that's going to be stamped to docs 16:09:41 frankbrokners: We have it, what we didnt make til now will not be made for tonight 16:09:44 so we need to update docs. label the branches. rebuild the ISO with the right SHA1. 16:09:46 sorry fedger - i meant the ISO that JOse and I just built and is being deployed now 16:09:55 ChrisPriceAB: that's the way 16:10:01 and/or what the master is at right now 16:10:14 but master is not settled from doc point of view 16:10:19 https://build.opnfv.org/ci/view/genesis/job/genesis-fuel-build/ 16:10:37 finished like 30 min ago 16:10:38 question - 16:10:44 if we change the docs, cause its in the repo 16:10:51 doesnt that mean you SHA1 changes 16:10:54 you are in a cyclic mode no? 16:10:58 nope 16:11:04 My understanding of next steps: test current deploy, update docs after test results, label the branches, build the final ISO's to store. 16:11:05 cause the doc updates change the Repo? 16:11:08 once people say "we're done with the docs" 16:11:11 it goes into docs 16:11:14 ahh.. ok 16:11:14 thx 16:11:25 and then we build an ISO on that sha1 as well 16:11:39 and then tag that one with arno.2015.1.0 pointing to one version where ISOs and docs are produced 16:12:11 i think i see - Jose to answer back.. its less about the ISO and more about frozen master branach to create 'Final ISO" w/ Docs done 16:12:20 (if i get it ) 16:12:23 ya, I see 16:12:23 right 16:12:28 ok 16:12:40 So we will do the manual artifact moving in the morning "euro time" tomorrow. But have to get the labelling and rebuild done tonight. 16:12:42 and then the same is valid for other repos as well 16:13:04 how much longer do we need on docs then? 16:13:35 I will finish the releasenotes for fuel once we have the test results 16:13:43 ok.. 16:13:46 given that there will be no more changes to the Fuel build - can we go through Chris pipeline mentioned above now? 16:14:03 ok - looks like we're on the same page 16:14:17 the deploy is ongoing frank as per Jose - so as soon as its deployed jose and i will run Funtest 16:14:25 and then provide results to jonas to update rel notes 16:14:28 maybe 2 hours? 16:14:32 wait for tests to finish - update docs with results and then label the branches 16:14:34 give or take vodka and passing out 16:14:39 something like that 16:14:40 2-3 hours 16:14:51 Who will label and bransh 16:14:57 branch 16:15:13 I dont think I got any instructions on that 16:15:27 we have them ready: https://wiki.opnfv.org/octopus/releasepipeline#git_instructions 16:15:37 was just waiting to get sha1s before sending it 16:16:12 #link https://wiki.opnfv.org/octopus/releasepipeline#git_instructions 16:16:39 jonasbjurel - will you do this? 16:17:26 I can try, I'm not a git pro so I cant promise I will make it 16:17:39 And do I have the privs needed? 16:18:04 committer needed 16:18:07 jonasbjurel: you should have 16:18:17 aricg fixed them last night 16:18:19 fdegir: I don't think a push will push the tag 16:18:25 it pushes 16:18:39 we tested in octopus repo - and octopus has already been tagged/branched 16:18:40 git push origin --tags 16:18:49 think you have to specify --tags to push tags 16:18:53 or push the tag individually 16:19:06 Jonas: if you need a commit / have issues, just ping me and ill push it through with you 16:19:20 trozet: this pushes the tag: git push origin arno.2015.1.0 16:19:29 ah 16:19:35 didnt read, my bad 16:19:43 trozet: https://gerrit.opnfv.org/gerrit/gitweb?p=octopus.git;a=tags 16:19:46 Daniel: Thanks 16:20:03 np 16:20:41 ok - looks like we have Fuel/POD1 covered 16:21:10 radez already info'ed that .iso for Foreman is ok as well 16:21:20 which brings us to test 16:21:25 Maybe, just a thought it would be better if trozet could tag it since I will likely work with docs til midnight an 16:21:50 and trozet is on the right timezone for that. 16:21:53 I can do it since im 6 hours behind so it wont be so late 16:21:54 trozet - ok? 16:22:06 trozet: thanks 16:22:19 perfect - thanks. so you just want for green light from Jonas that all doc updates are in. 16:22:20 need to kick off the build as well after the label. aricg can help with that 16:22:38 clarity please Chris 16:22:44 aricg - are you here? 16:22:52 did you mean after the tags and such you want a build and deploy to both PODs done as well? 16:23:07 once we have the docs/labels we need to rebuild the ISO's with the right SHA1 16:23:12 frankbrockners: hi 16:23:35 hmm. ok - i thought that is done after you move the repo.. maybe i dont get it .. but not important 16:24:14 hi aricg: question: can you help with kicking a build once trozet has done the labeling - will likely be around/after 3pm PDT? 16:25:07 yeah, I'll check the chat log after dinner 16:25:30 cool - thanks 16:26:27 let's move to functest... morgan_orange: quick update on where we are (and what we're still missing)? 16:27:05 #info last night run on POD2 was acceptable (vPing OK, ODL OK (except known ODL bugs), Tempest and Rally bench suite run 16:27:34 #info functest guide updated today to reflect last changes in scripts and tests 16:27:41 #info section added on known issues 16:27:49 #info tests in progress on POD1 16:28:55 that is all 16:29:07 thanks morgan_orange 16:29:17 question, shall we also put a lable 16:29:21 morgan_orange: yes 16:29:24 I was going to ask that 16:29:30 no open patches for functest 16:29:34 no 16:29:36 are you ready? 16:29:39 yes 16:29:41 so the plan is to have testdocumentation similar to POD2 for POD1 once tests are done there? 16:29:43 morgan_orange: might want to check where your ToC ended up - http://artifacts.opnfv.org/functest/docs/functest.html 16:31:11 there is one issue with one image 16:31:24 let's do final reviews of the docs before we label. 16:31:25 at the end 16:31:34 frankbrockners: the documentation is the same, just the results wiki will reflect the differences between 2 pods 16:31:55 * ChrisPriceAB wonders if the document heading should come before the ToC? 16:32:06 jose_lausuch - smart approach 16:32:13 Can we refer to the Wiki in the release notes? 16:32:25 well, it will evolve over time... 16:32:46 Without versioning? 16:33:08 * trozet applauds ChrisPriceAB for using /me correctly 16:33:13 jonasbjurel: it is like that :) 16:33:20 hehe :-D 16:33:32 in theory release notes should be release notes 16:33:46 what about the header? 16:33:49 so associated with a release 16:34:06 we could refer to a specifc version of the wiki... 16:34:14 could == should 16:34:45 Nevermind, Jose - once you have finalized, will you give me the URI 16:34:54 you can do always : ?rev=1432820425 16:34:58 for the results I mean 16:34:59 to the URL 16:35:02 yeah - you could put a specific link... - more of a hack 16:35:04 yep 16:35:15 yes jonasbjurel 16:35:32 but this is release 1 - so let's do the pragmatic approach 16:35:37 so back to your ToC what was teh question, shall i remove the ToC from the doc? 16:35:55 no, I would just put it under the doc heading 16:35:56 Chris wants the headline above the ToC 16:35:59 that's it 16:36:06 right now the header is below the ToC 16:36:10 consistent with the other docs 16:36:11 really cosmetic 16:36:20 OK I can do that for you 16:36:28 :p 16:36:37 * ChrisPriceAB likes his cosmetics 16:37:25 It’s so hard not to make a comment….. 16:37:30 :D 16:37:55 yup - too much of a free kick.. don't take it 16:37:59 * lmcdasm has bit through his tongue several times 16:39:09 damn, you line it up... 16:39:26 back on real issues - what else do we need to take care of? 16:39:33 pharos & opnfvdocs 16:39:48 if nothing else for functest and bgs 16:39:55 I think docs are ready to go but will wait 16:40:04 as fr as labelling is concerned 16:40:15 for opnfvdocs to be specific 16:40:21 who labels docs and pharos? 16:40:35 trevor on pharos. 16:40:42 is that confirmed? 16:41:06 have not reached out to him yet, if not morgan can you tackle it in lieu of trevor 16:41:50 We need a pharos committer 16:41:51 when do you plan to do this - both Trevor/Morgan are in Europe I believe 16:42:09 Trevor is in Portland 16:42:10 Trevor’s based in Portland 16:42:16 ah - ok 16:42:27 the accent throws you 16:42:30 do we know what is missing for pharos? 16:42:32 will try get hold of him 16:42:42 thanks ChrisPriceAB 16:42:43 don't see any open patch on gerrit 16:42:43 doc needs final review then we're good to go 16:43:18 if nothing else pharos can be tackled in the morning with morgan_orange as there are no dependancies there. 16:43:49 what do you expect from me here? 16:44:02 same goes for opnfvdocs - right? (with the difference that ChrisPriceAB would cover things) 16:44:07 we would just need to push in any final patches, lthen label 16:44:39 opnfvdocs does not provide content, so it's just if there is a last minute tool issue. otherwise we are good to label that now. 16:45:06 ChrisPriceAB: Cosmetics Ack http://artifacts.opnfv.org/functest/docs/functest.html 16:45:26 beautiful! 16:45:56 added latest sha1 for opnfvdocs to wiki 16:46:02 can we embed this in there somewhere? http://motherhoodlater.com/wp-content/uploads/2013/08/unicorn.jpg 16:46:18 thanks fdegir, will label shortly 16:46:24 lol 16:47:40 * lmcdasm wonders if this process on release is outlined somewhere so we can have "head start" next time around - SR1, etc :) - musing lightly. 16:48:43 lmcdasm: this is total hack - https://wiki.opnfv.org/octopus/releasepipeline 16:48:55 hope to have good process described by our new release manager 16:49:01 and automate stuff 16:49:05 thx Fatih 16:49:08 lmcdasm: We have Debra joining who will be leading our release activities moving forward. 16:49:11 .. and we will bring that out earlier for the next time we use it. 16:49:16 http://openstackreactions.enovance.com/2015/06/unexpected-hiccup-before-the-release/ 16:49:26 - even when using more automation 16:49:42 jose_lausuch: are you waiting that to happen? 16:49:48 lol jose 16:49:51 :p 16:49:52 thx - good to have Debra here to see what is going - since to me things like headers, footers, comesitcs and stuff "could" (and yes we are alla busy) been done a while ago.. 300 commits today alone :) 16:50:04 but c'est la vie :) 16:50:06 well - this is why we hired a lady as release manager 16:50:15 o.o 16:50:18 ?? sorry - i dont get your meaning Frank 16:50:32 no worries... 16:50:37 ouch - you might wanna take that back :) 16:50:57 can you #info stuff please? 16:51:03 ok, where are we? all projects covered? all actions in the chute? 16:51:04 :) 16:51:25 now that the doc is costmetically compatible I will try to tag/branch functest 16:51:35 #action chris to hunt trevor_intel down for pharos labelling 16:51:39 yup - let's summarize 16:52:05 so jose_lausuch pbandzi no more action on functest repo 16:52:21 ok 16:52:24 ok 16:52:33 #action all focus on last minute doc reviews and merges to clean up tonight. 16:52:35 I'll stop commiting things 16:52:45 Its an adiction once you start 16:52:56 #info jonas and tim to synch on POD1 test documentation completion. Tim to label things and check with Aric to kick final builds 16:54:26 #info test results will be documented on a wiki. release notes will just link to the specific wiki version 16:54:48 Jose needs to kick his habit for a couple of days (and get some sleep ((after a few drinks)) ) 16:54:52 well, one more thing 16:55:00 some polish vodka will help 16:55:15 where do we put the comments about the ODL issue for Fuel? 16:55:16 meaning 16:55:23 we ran the tests only with ODL controller activated 16:55:27 without vxlans 16:55:33 where shall be that stated? 16:55:36 Jonas will update 16:55:39 ok 16:55:40 when you have the results 16:55:45 and put it into the releae notes 16:55:48 release notes 16:55:50 good 16:55:53 thanks 16:56:16 lets move on then 16:56:44 * frankbrockners believes we're done with this meeting 16:57:06 * ChrisPriceAB concurs (see tim I can do it too!!!) 16:57:14 #info No more commits to functest repo until release is cleared 16:57:38 cause morgan_orange said he is going to tag/branch stuff now 16:57:51 yes 16:57:59 oki, guess we don't have locks for project leads in place 16:58:22 * lmcdasm wonders who Chris is asking? 16:58:40 just guessing and musing. 16:59:23 ok - looks like we're done with this meeting... 16:59:40 let's continue to keep fingers crossed for the next few hours... 16:59:49 a big thank you to everyone 16:59:55 #endmeeting