14:00:50 <ChrisPriceAB> #startmeeting OPNFV Arno RC2 status meeting 14:00:50 <collabot> Meeting started Thu Apr 16 14:00:50 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:50 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:50 <collabot> The meeting name has been set to 'opnfv_arno_rc2_status_meeting' 14:00:56 <ChrisPriceAB> #topic roll call 14:01:04 <ulik> #info Uli 14:01:05 <ChrisPriceAB> #info Chris Price 14:01:26 <HKirksey> #info Heather 14:01:29 <fdegir> #info Fatih Degirmenci 14:01:32 <radez> # Dan Radez 14:01:37 <radez> #info Dan Radez 14:01:41 <rprakash_> #info Prakash R 14:01:49 <radez> I always do that for some reason :( 14:01:52 <trevor_intel> #info Trevor Cooper 14:01:55 <trozet> #info Tim Rozet 14:01:57 * ChrisPriceAB info, don't forget the info 14:02:23 <ChrisPriceAB> ok will give it a minute and wait for our project leads to arrive before pushing on 14:02:26 <[1]JonasB> #info Jonas Bjurel 14:03:00 <frankbrockners> #info Frank Brockners 14:03:07 <icbts> #info Jamie Goodyear 14:03:28 <Guest98285> #info Larry Lamers 14:03:44 * ChrisPriceAB still looking for trevor (or delegate) and morgan (in this case need a delegate) 14:03:57 <ChrisPriceAB> Oh I see trevor :s 14:04:01 <trevor_intel> I am here ... Trevor 14:04:14 * ChrisPriceAB yes sorry trevor. old age, bad eyes 14:04:29 <ChrisPriceAB> Anyone who can speak on functest? 14:04:38 * ChrisPriceAB maybe trevor again??? 14:04:55 <trevor_intel> Do we have Sama, Martin, Peter? 14:05:00 <ChrisPriceAB> in any case will push on at 5 minutes past 14:05:07 <ChrisPriceAB> which is now 14:05:25 <ChrisPriceAB> #topic RC execution reporting and issue logging 14:05:58 <ChrisPriceAB> #info aricg, fdegir where are we with toolchain and lab status and task completion for RC2 14:06:02 <dneary> #info Dave Neary 14:06:15 <bryan_att> #info Bryan Sullivan 14:06:37 <fdegir> #info Build jobs are still in same state - up and running and producing/storing ISOs daily 14:07:00 <fdegir> #info Build jobs are still running on ericsson-build 14:07:08 <fdegir> #info We're starting with deploy jobs 14:07:12 <ChrisPriceAB> #info do we have toolchain execution up on LF hardware yet? 14:07:29 <fdegir> #info LF hardware is not ready to use from Jenkins as of yet 14:07:46 <ChrisPriceAB> #info ok, thanks. 14:08:08 <frankbrockners> #info Do we know what is required by CI to get going to LF hardware? 14:08:41 <fdegir> #info We need OS and needed tool installations done on LF HW in order for us to connect them as slaves to OPNFV Jenkins 14:09:11 <frankbrockners> #info Who is working the OS installation? 14:09:14 <ChrisPriceAB> #info is there a Jira on that, and who has the ball? 14:09:21 * ChrisPriceAB same question :D 14:09:51 <ChrisPriceAB> #info or a helpdesk ticket for that matter 14:10:16 <ulik> #info Why do we need a Jira there? Did we need Jira for hardware? 14:10:20 <fdegir> #info pbandzi is working on with setup 14:10:40 <fdegir> #info but I'm not sure how far he will go with the setup/installation/configuraiton 14:10:43 <ulik> #info It is pretty obvious, we need software setup. 14:10:43 <frankbrockners> pbandzi: In case you are here could you give us a quick update 14:10:52 <ChrisPriceAB> #info We should use Jira for activity and task tracking, seems like a task to be tracked (unless it's a helpdesk ticket) 14:11:11 <frankbrockners> #info pbandzi has configured UCSs - and is in the process of installing the jumphost with base OS (Centos 7) 14:11:20 <ulik> #info Is it a Jira in Pharos? 14:11:27 <frankbrockners> but i don't think that he'll bring up other nodes 14:11:45 <[1]JonasB> #info to be able to deploy, wee need some decent documentation of the LF environment. 14:11:56 <ChrisPriceAB> #info One topic at a time please 14:12:29 <ChrisPriceAB> #info Ok, so is it enough to have OS up on the jumphost. Does our toolchain automate other nodes bring up sufficiently? 14:13:22 * ChrisPriceAB that's a question for our CI team :D 14:13:55 <trozet> #info ChrisPriceAB, thats the whole point of deploy right, it brings up nodes other than the jumphost 14:14:05 <fdegir> #info If we will connect jumphost to jenkins and initiate deployment and testing from there than that should be enough 14:14:29 <fdegir> #info Builds probably need other hosts to be attached to OPNFV Jenkins 14:14:33 <ulik> #info (hoping the IMPI etc. is up) 14:14:34 <ChrisPriceAB> #info Good, I like confirmation on the simple questions. 14:14:35 <trozet> #info other nodes just need to be set to pxe boot first, off their first interface 14:14:49 <frankbrockners> fdegir: can you check with Peter to get the jumphost connected to Jenkins? 14:15:02 <fdegir> frankbrockners: will do 14:15:05 <ChrisPriceAB> #info Ok, tables discussions. Jira actions on LF HW activity. Pharos documentation. 14:15:10 <ChrisPriceAB> #undo 14:15:10 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1cfb690> 14:15:15 <ChrisPriceAB> #info Ok, tabled discussions. Jira actions on LF HW activity. Pharos documentation. 14:16:01 <ChrisPriceAB> #info So my take right now is we are in progress on the LF hardware. Currently using a hosted lab for the purposes of build and deploy. 14:16:14 <fdegir> #info That is correct ChrisPriceAB 14:16:22 <ChrisPriceAB> #info thanks. 14:16:29 <fdegir> #info Foreman deploy work could start with intel lab until LF HW is ready 14:16:36 <fdegir> #info Fuel work will continue with ericsson lab 14:16:46 <fdegir> #info until LF HW is ready 14:16:50 <ChrisPriceAB> #topic Project reports on RC completion and next RC readiness 14:17:01 <ChrisPriceAB> #info let's move onto the project reporting. 14:17:01 <frankbrockners> #info Do we successfully deploy by now? 14:17:19 <ChrisPriceAB> one thing at a time. ;) 14:17:37 <frankbrockners> ChrisPriceAB: agreed - this was to the earlier topic.... 14:17:47 <ChrisPriceAB> #info Pharos project status, needed actions, incl. LF activities. 14:18:04 <ChrisPriceAB> trevor_intel can you give us an update? 14:18:20 <trevor_intel> ok 14:18:54 <trevor_intel> #info 1) Spec file is in gerrit 14:19:24 <frankbrockners> trevor_intel: could we add the link? 14:19:36 <trevor_intel> #info 2) Infrastructure usernames is still outstanding but haev made progress with input from community 14:19:59 <trevor_intel> #info https://gerrit.opnfv.org/gerrit/289 14:20:01 <vlaza> #info https://gerrit.opnfv.org/gerrit/#/c/289/ 14:20:21 <ChrisPriceAB> #link https://gerrit.opnfv.org/gerrit/289 pharos spec file patch 14:21:07 <ChrisPriceAB> Ok, any more, I will come back to Pharos in the docs piece later 14:21:08 <trevor_intel> #info What I am not sure is how doc project inputs for this realease 14:21:27 <ChrisPriceAB> #info let's discuss in the opnfvdocs update section 14:22:26 <ChrisPriceAB> #info Can we action Pharos to capture activity in Jira so we can track issues leading to next week? 14:22:37 <trevor_intel> #info yes 14:22:58 <ChrisPriceAB> #action Pharos to update Jira leading up to Arno release (and onwards :) 14:23:15 <vlaza> #info I already added a Jira ticket to request for documentation where we can help ; https://jira.opnfv.org/browse/PHAROS-1 14:23:29 <ChrisPriceAB> #info Octopus status update for RC2 14:23:53 <ulik> #info fdegir has reported the main things already 14:24:27 <fdegir> #info We are also working with reference documentation for Octopus 14:24:32 <ulik> #info additionally octopus doc is in createion 14:24:34 <frankbrockners> #info Does automatic deploy to some lab work already? 14:24:39 * ChrisPriceAB yes we were hoping to be task complete by now so this may be a fast section to report on 14:24:42 <fdegir> #info and working with BGS teams to get deployment working 14:25:02 <fdegir> #info Fuel deployment is currently ongoing on Ericsson lab 14:25:16 <fdegir> #link https://build.opnfv.org/ci/view/genesis/job/genesis-fuel-daily-master/48/console 14:25:30 <ChrisPriceAB> #info do we have Jira tasks for each deploy/lab activity and someone who owns them from the CI side? 14:25:43 * ChrisPriceAB is assigned to - rather than owns 14:25:55 <fdegir> #info Here they are 14:26:22 <fdegir> #link Fuel daily pipeline: https://jira.opnfv.org/browse/OCTO-3 14:26:33 <fdegir> #link Foreman daily pipeline: https://jira.opnfv.org/browse/OCTO-4 14:26:50 <fdegir> #info Daily Pipelines include deployment activities 14:27:01 <fdegir> #info for CI 14:27:32 <fdegir> #info Lab details are excluded since we work with deploying to whatever we have 14:27:45 * ChrisPriceAB thanks#info can I ask for an assignee to BGS Foreman Daily Pipeline: https://jira.opnfv.org/browse/OCTO-4 14:27:55 <ChrisPriceAB> #info can I ask for an assignee to BGS Foreman Daily Pipeline: https://jira.opnfv.org/browse/OCTO-4 14:28:32 * ChrisPriceAB Uli time to throw someone to the wolves.... 14:29:22 <ulik> action me .. 14:29:33 <HKirksey> or gently encourage…. ;-) 14:29:57 <ChrisPriceAB> #actio Assign a responsible person to the foreman daily pipeline activity 14:30:03 <ChrisPriceAB> #action Assign a responsible person to the foreman daily pipeline activity 14:30:28 <ChrisPriceAB> Let me say - SUPER DUPER IMPORTANT!!!! 14:30:40 <fdegir> I told trozet to contact octopus so it needs to be fast to get a name for OCTO-4 so trozet dradez know who to talk to 14:30:56 <ulik> frank, give me the foreman contacts for my guy.... 14:31:12 <ChrisPriceAB> #info BGS status reporting for RC2 14:31:15 <ulik> OK so it's trozet & dradez to talk to. 14:31:25 <fdegir> ulik: yes 14:31:26 <frankbrockners> ulik: you have them here radez and trozet 14:31:40 <ChrisPriceAB> frankbrockners, take us away. (or Jonas / Tim & Dan) 14:32:21 <frankbrockners> #info default username/passwd chosen: opnfv/opnfvstack 14:32:52 <frankbrockners> trozet, [1]JonasB, radez - could you summarize deployment tool status? 14:32:58 <ChrisPriceAB> Implemented in each deployment toolchain? 14:33:55 <trozet> #info trying to deploy on Intel Pod 1. Intel Pod 1 uses different subnet masks, have submitted a patch for deploy to allow subnets other than /24. Hitting a DNS problem with Foreman install right now. 14:34:05 <rprakash_> synch between Foreaman and Fuel track you mean on installs? 14:34:07 <trozet> #info have a fix for it and will retry, hoping to be done today 14:34:45 <frankbrockners> #info Plans to deploy to LF hardware? 14:35:07 <trozet> #info Will do when it is ready. 14:35:51 <frankbrockners> [1]JonasB: Do you have an update on Fuel? 14:36:43 <[1]JonasB> #info build working 14:37:08 <[1]JonasB> #info 60-70% of docs in place and will be built in RC2 14:37:48 <[1]JonasB> #Autodeployment integrated with jenkins work done 14:38:10 <ChrisPriceAB> #info Autodeployment integrated with jenkins work done 14:38:39 <[1]JonasB> #info Deploying as we speek, and hopefully we can claim victory on that in an hour or so 14:38:49 <frankbrockners> # same question as earlier: Plans to deploy to LF hardware? 14:39:17 <[1]JonasB> #link Ongoing deployment console https://build.opnfv.org/ci/view/genesis/job/genesis-fuel-daily-master/48/console 14:40:08 <[1]JonasB> #inf On topic LF lab, yes we have plans, we have started integration with the CISCO Python API and the emulator. 14:40:16 <[1]JonasB> #info On topic LF lab, yes we have plans, we have started integration with the CISCO Python API and the emulator. 14:40:21 <ChrisPriceAB> #info I have a question, once we get the LF hardware up there will be some resource contention I guess between deploy toolchain fixing, functest validation activities etc. 14:40:32 <lmcdasm> question - on that - can i get console access to the HW to start to sort out the port mapping? 14:40:37 <ChrisPriceAB> #info do we have a plan in place to maintain order and keep things smooth? 14:41:05 <fdegir> #info About resource contention: we can adjust the Jenkins job scheduling 14:41:13 * ChrisPriceAB answer lmcdasm first I think 14:41:20 <[1]JonasB> #info As I mentioned, in order to prepare for LF, we need some environment documentation. 14:41:50 <ChrisPriceAB> #info can we action Pharos to provide a concise document? 14:42:49 <trevor_intel> #info ... LF will produce this? 14:42:57 <frankbrockners> #info on maintaining order: We could consider using a LF HW POD per installer for the time being. It would reduce potential conflicts. 14:43:37 <ChrisPriceAB> #info trevor_intel, no it should be a target hardware config document. Will need to be part of the release documentation as well. We need to set up an activity to produce this. 14:44:02 <rprakash_> concise in terms of node and topolgy of of hardware and connectivity? 14:44:06 <ChrisPriceAB> opnfvdocs and bgs can help with it, but Pharos needs to own it 14:44:21 <pbandzi> quick update about LF: UCS manager configured, now installing centos 7 on jump server 14:44:34 * ChrisPriceAB nice pbandzi 14:44:43 <trevor_intel> #info ok 14:45:18 <ChrisPriceAB> #action Pharos to produce lab environment documentation, opnfvdocs and bgs to help 14:45:27 * ChrisPriceAB this week! 14:45:28 <trevor_intel> #info pharos owns logical ... LF owns physical documentation? 14:46:22 <HKirksey> I believe that Konstantin and Aric sent out a physical diagram to the infra list? 14:46:44 <ChrisPriceAB> #info ok, we need to get this together. I'll call for a gathering tomorrow. 14:47:04 <ChrisPriceAB> #action ChrisPriceAB to rally the troups for environment documentation 14:47:14 <[1]JonasB> Can we have the LF documentation at the same Wiki place as the rest of the labs? 14:47:27 <ChrisPriceAB> #info functest status reporting for RC2 14:48:25 <trevor_intel> #info Rally scenarios = Morgan who is out this week, vPing = Sama, vIMS = Martin, Robot = Peter ... 14:48:42 <ChrisPriceAB> pbandzi can you give us an update on Robot? 14:48:46 <trevor_intel> I haven't seen updates 14:50:01 <ChrisPriceAB> ok, anyone from functest. Running out of time. 14:50:23 <ChrisPriceAB> #action functest to provide concise reporting on the mailing lists before the end of the week 14:50:34 <ChrisPriceAB> #info opnfvdocs status update for RC2 14:50:35 <frankbrockners> #info (from what I know from Peter): Robot up and running on Intel lab - performing subset of ODL tests 14:50:40 <pbandzi> #info couple of robot tests are uploaded in git, there is however some duplicated code with odl integratiion tests... - need to decide how we going to proceed 14:51:15 <pbandzi> #info if we want to create just scripts whil will configure env and start required test from odl integration 14:51:17 <ChrisPriceAB> #info ok, can we please solve these things and whoever is standing in for Morgan this week needs to provide an upadte on mail 14:51:23 <ChrisPriceAB> #info opnfvdocs status update for RC2 14:51:40 <ChrisPriceAB> #info toolchain for Arno is in place, described on the documentation WiKi 14:52:14 <ChrisPriceAB> #link https://wiki.opnfv.org/documentation docs & toolchain description 14:52:25 <pbandzi> suppose we don't want to duplicate code from other repos so thios might be the way how to do it 14:52:32 <ChrisPriceAB> #info templates in place, not all documents yet under authorship. 14:53:05 <ChrisPriceAB> #info release notes and instalation guide drafts ready for parts of BGS. 14:53:29 <ChrisPriceAB> #link http://artifacts.opnfv.org/genesis/fuel/docs/release-notes.html current release note artifacts built 14:53:50 <ChrisPriceAB> #link http://artifacts.opnfv.org/genesis/fuel/docs/installation-instructions.html current installation instructure notes built 14:54:10 <ChrisPriceAB> #info user guide template not yet started. 14:54:20 <ChrisPriceAB> #info environment documentation not yet started 14:54:34 <ChrisPriceAB> #info remaining BGS docs to be integrated into templates 14:55:03 <ChrisPriceAB> #info that's it. 5 minutes left lets capture actions. 14:55:08 <ChrisPriceAB> #topic Actions and activities planned 14:55:10 <[1]JonasB> #info We should also document build-guidelines 14:55:27 <ChrisPriceAB> #info extrapolate that thought Jonas 14:56:34 <ChrisPriceAB> Is that something for the release docs? Or something like the CI documentation activity? 14:56:57 <fdegir> I think it is BGS documentation 14:57:02 <fdegir> CI is not into build details 14:57:19 <fdegir> we will document what happens before we issue the build command 14:57:26 <fdegir> and what happens once the ISO is built 14:57:29 <fdegir> but nothing in between 14:57:33 <ChrisPriceAB> #info ok, but not as part of the release documentation, BGS general build documentation. 14:57:35 <[1]JonasB> #info I would assume that we should allow consumers of Arno to build them selves, even if the result is not supported? 14:57:57 <fdegir> like ref guide 14:58:31 <bryan_att> #info I agree with Jonas - we will need to extend ARNO due to lack of certain features we need for project testing 14:58:37 <ChrisPriceAB> #info Ah, OK yes. But I don't gate on Arno for that, I think we need to improve documentation across the board a little. So agree, but will not focus on that for the next 7 days. :) 14:58:59 <bryan_att> #info SO we need build instructions - it's OK that this follows release though 14:59:18 <ChrisPriceAB> #info Ok, want to hear form the project leads. Next 7 days, priority areas places we need support from others 15:00:08 <rprakash_> is there a ticket for build dcumentaion? 15:00:25 <ChrisPriceAB> #action ChrisPriceAB to coordinate across projects for Arno key items leading up to next week. 15:00:43 <ChrisPriceAB> #info unless there is something urgent, or to be added we can close off the RC2 meeting. 15:01:04 <ChrisPriceAB> #info basic status is that we are not yet Jenkns integrated with the LF hardware and have not egun deployment there. 15:01:10 <vlaza> #info rprakash_: for what project? 15:01:18 <ChrisPriceAB> Deployment testing ongoing to hosted labs, functest status unknown. 15:01:28 <ChrisPriceAB> #info sound accurate? 15:01:36 <rprakash_> bgs 15:01:46 <HKirksey> Ok, I have to ask this question. :) Are we on track for an April 23 launch? Or is that a day by day decision at this point? 15:02:17 <ChrisPriceAB> Day by day. Many pieces are in place. Just not the whole picture 15:02:42 <vlaza> rprakash_: I don't find any 15:02:46 <ChrisPriceAB> High (very high) risk if we do not get the toolchain in place in the LF labs today and begin working there 15:02:52 <HKirksey> Ok. 15:02:54 <HKirksey> thanks 15:03:14 <ChrisPriceAB> High, (very high) risk in any case. (notice the lack of caps) 15:03:25 <rprakash_> vlaze can you add one for us to trcak 15:03:50 <vlaza> rprakash_: yes 15:03:55 <ChrisPriceAB> #info Ok thanks all. I might start a series of daily syncs for project leads starting tomorrow so we get day by day updates 15:03:59 <ChrisPriceAB> #endmeeting