16:01:08 <frankbrockners> #startmeeting BGS release readiness - daily check in
16:01:08 <collabot> Meeting started Wed Apr 22 16:01:08 2015 UTC.  The chair is frankbrockners. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:08 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:01:08 <collabot> The meeting name has been set to 'bgs_release_readiness___daily_check_in'
16:01:25 <pbandzi> #info pbandzi
16:01:48 <frankbrockners> #info Frank Brockners
16:01:49 <radez> #info radez
16:01:58 <trevor_intel> #info Trevor Cooper
16:03:00 <frankbrockners> anyone from the fuel folks around? Jonas, Chris?
16:03:15 <frankbrockners> [1]JonasB: r u there?
16:03:28 <frankbrockners> ChrisPriceAB: r u there?
16:04:23 <frankbrockners> #info main topic for discussion today is to report current status - and create rough estimates for the remaining tasks
16:05:04 <frankbrockners> #info from now on we'll update the following list (BGS entries only):
16:05:18 <frankbrockners> #link https://wiki.opnfv.org/releases/arno/releasereadiness
16:05:32 <ChrisPriceAB> Hi frankckbrockners, yes but waay overbooked
16:05:36 <ChrisPriceAB> #info ChrisPrice
16:05:41 <frankbrockners> #info this list will be used by TSC for planning
16:05:45 <trozet> #info Tim Rozet
16:06:07 <frankbrockners> ChrisPriceAB: Thanks for joining. Is Jonas around as well?
16:06:46 <ChrisPriceAB> I will try and swing him in, also overbooked at the moment
16:07:27 <frankbrockners> #info Quick update on any progress since yesterday
16:07:53 <frankbrockners> Who'd like to go first: Chris, Tim, Dan, Jonas, Peter?
16:08:11 <pbandzi> i can write in short
16:08:23 <ChrisPriceAB> Jonas is joining, better he provides input from our side.
16:08:41 <ChrisPriceAB> Go peter
16:09:12 <pbandzi> #info removed redundant interfaces from POD1, added MAC of CIMC interfaces to wiki
16:09:33 <pbandzi> #info right now don't know about pending task for lab setup
16:09:56 <[1]JonasB> #info Jonas Bjurel
16:10:17 <frankbrockners> #info can everyone review https://wiki.opnfv.org/get_started/lflab_hosting and note any missing info?
16:10:37 <frankbrockners> #info and if there is incorrect info - please correct and let everyone know - thanks!
16:10:37 <radez> #info pbandzi will ipmi be made available?
16:10:53 <ChrisPriceAB> Important to identify if it is worth capturing important items that might not be visible.  (increase granularity where it makes sense to show things)
16:10:57 <frankbrockners> #info IPMI info is already present on the page
16:10:57 <radez> I think we talked about this yesterday but I don't remember the outcome
16:11:14 <pbandzi> #info IPMI were configured also. MACs provided on wiki (IPs same as CIMC)
16:11:31 <[1]JonasB> #info The fuel team is currently focusing on autodeply in the Eri Lab, once we have that working I will work with Peter based on those net specs
16:11:42 <frankbrockners> #info go to https://wiki.opnfv.org/get_started/lflab_hosting and search for IPMI
16:11:57 <pbandzi> #info IPMI user/pass present on  mentioned wiki
16:11:57 <radez> thx for the update frankbrockners & pbandzi I missed that
16:12:36 <frankbrockners> Jonas - is autodeploy to bare metal working?
16:12:51 <radez> #info foreman team is fighting virtualbox the bridging is not working as it did in the intel lab and we are blocked until we figure it out
16:13:21 <radez> #info we can see arps going out from our virtual box vm but they never get back to the vm
16:13:27 <lmcdasm> #info - dan smith - sorry im late
16:13:43 <lmcdasm> hey Dan Radez
16:13:52 <radez> hello!
16:13:53 <lmcdasm> have you set promiscous mode on that BRdighes and nics?
16:14:03 <radez> tried on the host
16:14:09 <radez> didn't seem to help
16:14:25 <lmcdasm> cause otherwise the tags are not going to passs out those ENPs.. as well..do you have a snoop (tcpdump -e) of the enp that thins are bound too?
16:14:46 <lmcdasm> that would tell quite a bit.. sound slike we are tshooting the stack (dump the VNIC, dump the matching vi/tap on the host, dump the bridge and the NIC)
16:14:59 <lmcdasm> if you can send me tcpdumps i can look 0- but you are going to need to sit on the switch
16:15:13 <lmcdasm> and see where the packets are going if you can see them leaving the ENP
16:15:29 <radez> we see them coming back into the hypervisor
16:15:38 <lmcdasm> hmm.m
16:15:44 <radez> they're not getting passed back to the vm from the hypervisor
16:15:53 <lmcdasm> ahh
16:15:54 <lmcdasm> ok..
16:16:05 <lmcdasm> some its the return path -
16:16:15 <frankbrockners> radez: did you try with libvirt instead? Tim was planning to afaik
16:16:17 <lmcdasm> hmm.  are there any routes on that VM that might conflight?
16:16:26 <lmcdasm> (oh.. you're not using libvirt?).
16:16:45 <radez> virtual box right now, betting vagrant integration
16:16:49 <radez> *better
16:16:50 <lmcdasm> hmm.
16:17:12 <lmcdasm> ok..  i dont  know the Vbox vswtiches well so i cant help (libux bridges, ovs, esxi , nsx i know - vbox not so much)
16:17:35 <frankbrockners> could we table this issue for the next 15min (we can come back later)? - I'd like to get through status first - so that we have the data for the TSC meeting tomorrow
16:17:52 <radez> yup
16:18:10 <frankbrockners> #info Could folks review https://wiki.opnfv.org/releases/arno/releasereadiness
16:18:38 <lmcdasm> ok.. my comments
16:18:48 <frankbrockners> #info two asks: (1) could you update to today's status (obviously only BGS items)
16:19:20 <radez> #info no new updates for foreman team as of now. will make updates to https://wiki.opnfv.org/releases/arno/releasereadiness with todays progress eod
16:19:46 <frankbrockners> #info (2) could you add rough estimates for the BGS tasks. In case you are 100% unsure - keep it open, otherwise lets add a number that includes some slack
16:20:01 <lmcdasm> # info - no update from me on LF FUEL Setup
16:20:06 <frankbrockners> radez: any chance to add some estimates?
16:20:18 <radez> frankbrockners: sure we'll work on that
16:21:01 <frankbrockners> radez: thanks - this will be the basis for arguing with TSC and board - so with proper data, we can buy time and offload pressure
16:21:19 <radez> gotta head to another meeting, we'll work on updates and I'll check back in tomorrow
16:21:54 <frankbrockners> [1]JonasB: Could you also help with some estimates from a Fuel perspective?
16:22:14 <radez_afk> also, trozet is still here if there are foreman quiestions that come up
16:22:37 <frankbrockners> additional question: Are there any tasks we should add - which are currently not shown?
16:22:42 * ChrisPriceAB omg his bot talks too!
16:22:49 * ChrisPriceAB :D
16:22:53 <trozet> :)
16:23:33 * frankbrockners everyone has his private Eliza these days...
16:23:51 <lmcdasm> #info - common confiuration set - are we all aligned so that our openstacks are the same (Tim and i had email excahnge)
16:24:03 <frankbrockners> or should we break any of the line items further down?
16:24:05 <lmcdasm> shoudl this not be published somewhere?  And is CEPH really a requiremnts?
16:24:44 <frankbrockners> lmcdasm: good point - I'll add a line on the "system state finalized and closed"
16:24:48 <lmcdasm> the table with "comon component" and "Might be dropped' isnt really descriptive of the openstack configuratino set we are deploying
16:25:10 <lmcdasm> so while we know we cant at a HW / Infra level match between the two - i think its still a good idea to try to keep from teh OS up the same
16:25:13 <lmcdasm> as much as possible :)
16:25:18 <lmcdasm> good thx Frank
16:26:09 * frankbrockners changing the wiki now...
16:26:12 <[1]JonasB> frankbrockners and lmcdasm: Lets work on getting this up on the end system state wiki
16:26:22 <lmcdasm> hey Tim - quick one to confirm
16:26:27 <lmcdasm> you guys are deploying JUNO right?
16:26:34 <trozet> yes
16:26:37 <lmcdasm> k
16:27:55 <lmcdasm> #JonasB - sure - in boht our II adn in the Lab Workbook we have screen shots of all the things we turn on.. so if we have something similar (text or whatver) we can just cross off the common stuff and highlight the delta
16:28:08 <lmcdasm> Frank - do you have enough info from me and Tim/Dan to do that comparison ?
16:28:21 <lmcdasm> OR - we can do it the other way - we come up with the list and make sur ethat each Deployment uses it
16:28:29 <lmcdasm> either way -im easy
16:28:44 <frankbrockners> Daniel - I like the latter approach.
16:29:25 <frankbrockners> Can you update https://wiki.opnfv.org/get_started/get_started_system_state with the missing pieces? And if you're unsure whether things are really the same, just flag them.
16:29:56 <frankbrockners> Similar ask would go to Tim and Dan (or Dan's robot :-))
16:30:26 <trozet> ok
16:30:27 <frankbrockners> ok - sounds like we're done with status reporting
16:30:32 <trozet> I'll program Dan's bot to do it
16:30:48 <lmcdasm> hmm. looking at the page
16:30:56 <frankbrockners> anything else - otherwise we can switch back to the VM connectivity discussion - or any other topic that needs attention
16:30:56 <lmcdasm> what do you want to do with ethe "Possibiulity to drop" stuff
16:31:08 <lmcdasm> and Tempest - "What about documenting ont he CI" page
16:31:22 <lmcdasm> just blank em out -? are we agreed we do everything on the page then?
16:31:53 <frankbrockners> Daniel - let's create a category for "candidates which might not get included in Arno"
16:31:56 <lmcdasm> for example - i dont see CEPH there, but we are both doing it
16:32:01 <[1]JonasB> lmcdasm: we can always undo, so lets try to give it a shot
16:32:24 <lmcdasm> ok - but i mean - that doesnt reflect reality
16:32:27 <lmcdasm> in our builds - we have them in there
16:32:35 <lmcdasm> so i asking - are we saying they are IN or OUT
16:32:41 <lmcdasm> if we put "maybe" and then delivery
16:32:46 <lmcdasm> and people ask qeustion and we arent ready
16:32:48 <lmcdasm> then its a wsah
16:32:57 <[1]JonasB> lmcdasm: I ment lets start to modify it and if some one doesnt like it we can fix it
16:32:58 <lmcdasm> so.. lets be clear and concise on what we are going to support
16:33:05 <lmcdasm> #JonasB - ack
16:33:11 <frankbrockners> just create a category for things where you are in doubt
16:33:18 <lmcdasm> haha.. ok -
16:33:40 <[1]JonasB> Will we talk tempest here?
16:33:55 <frankbrockners> e.g. Tempest and Robot will be there - but done by the Functest team - so no topic for us in BGS
16:34:16 <[1]JonasB> No I mean will we discuss tempest testing in this meeting?
16:34:16 <frankbrockners> one thing less to worry about here
16:34:33 <frankbrockners> I did not plan to - we don't have functest people here
16:34:54 <frankbrockners> I assume that this will come up in the larger readiness meeting tomorrow
16:34:58 <[1]JonasB> No, that exactly why we need to start discussing it!
16:35:37 <[1]JonasB> I mean we're dependent on functest in that it defines our goal end state
16:35:41 <frankbrockners> [1]JonasB: Yes it is an important topic - because functest ultimately defines what we call "success"
16:36:11 <frankbrockners> i.e. we pass their tests. For now we don't even have a list of tests from them... see the open items for functest on the releasereadiness wiki
16:36:17 <[1]JonasB> And I dont se that happen, so I start to ask the team to do that definition our selves
16:36:25 <lmcdasm> soo. then arent we going backawrds then
16:36:39 <lmcdasm> should the functest spec outline the functions and features that need ot be in palce (pre-reqs)
16:36:45 <lmcdasm> shoulndt*
16:36:48 <frankbrockners> please make sure that you rope in the functest folks
16:36:54 <lmcdasm> go ahead
16:37:11 <frankbrockners> yes - functest owns this
16:37:23 <frankbrockners> i understand the catch22 situation
16:37:25 <[1]JonasB> frankbrockners: Who? Im planning to involve peter B
16:37:36 <frankbrockners> Morgan leads functest
16:37:55 <[1]JonasB> frankbrockners: Isnt he on vac?
16:37:57 <frankbrockners> it seems that he's the only one who has the full picture of who does what in functest
16:37:58 <pbandzi> i am focusing on robot and for robot i will provide tests list
16:38:09 <frankbrockners> afaik morgan is bacl
16:38:11 <frankbrockners> back
16:38:40 <frankbrockners> Chris is busy getting hold of a rep in functest and getting answers
16:38:40 <[1]JonasB> frankbrockners: OK
16:39:55 <frankbrockners> anything else? Otherwise I'd close the "BGS synch" meeting for now - and we can continue discussing VM connectivity issues etc.
16:40:23 <frankbrockners> going once
16:40:28 <frankbrockners> going twice
16:40:35 <frankbrockners> thanks for now!
16:40:39 <frankbrockners> #endmeeting