15:00:11 #startmeeting Copper Weekly Meeting 15:00:11 Meeting started Wed Aug 12 15:00:11 2015 UTC. The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:11 The meeting name has been set to 'copper_weekly_meeting' 15:00:51 #info Bryan Sullivan 15:00:52 Hi all, I will wait to see who joins, then continue. Please #info 15:01:04 #info Prakash Kanthi 15:01:15 #info Ryota Mibu 15:01:55 hi, this is my first time to join copper meeting 15:01:59 no GTM? 15:03:01 no, IRC only 15:03:32 Been doing it that way for some time. Seemed that the OPNFV community preferred IRC-only. 15:03:33 ok, thanks 15:03:54 #topic Status Update 15:04:11 #info I have updated the wiki with the dependencies 15:04:28 #link https://wiki.opnfv.org/copper/planning 15:05:04 #info the only hard dependency is Kilo and Congress added to it 15:05:33 #info the other config policy/intent stuff is now being driven in various other projects e.g. SFC 15:05:59 #info so there are some "working plan" dependencies that if not fulfilled will not prevent us from delivering Congress at least 15:06:21 #info as a tool to detect config violations 15:06:53 #info that doesn't mean the other goals are less important, just more dependent on other projects and thus softer dependencies, to be safe 15:07:23 #info I am also trying to get the doc toolchain working still - worked with Aric in the hackfest but it's still not quite there 15:07:24 #info Have Congress up and running on my DevStack. My goal this week would be to try merging it with OPNFV environment. 15:07:57 #info Once the docs are generated and presented as HTML via sphinx, I will start updating the docs with new use cases, etc 15:08:40 #info If there are no other reviewers I am likely to just +2 the patches 15:08:40 #info So if you want to review, just watch the gerrit 15:08:52 #info Last update point is the major focus on getting a testbed up and running 15:09:19 #info This is the #1 dependency, and I'm working with Spirent currently to try to use their lab environment 15:09:59 #info but everywhere I turn, this is more complex than expected and is running into roadblocks that I can't resolve alone. 15:10:17 #info So everything else is secondary to getting past those roadblocks 15:10:48 #info If anyone wants to help with setting up a testbed that is the biggest help that could be provided right now 15:11:19 #info I would hope the LF would have provided community testbeds by now, but it hasnt happened 15:11:22 howdy 15:11:26 #info So we are on our own 15:11:39 That's my update. Any other input for today? 15:12:11 #info Bryan, are you asking the help in terms of helping "provide" lab or work on lab setup tasks. 15:12:30 Prakash_DataTap_, work on lab setup at the least 15:12:40 #info Prakash_DataTap_, work on lab setup at the least 15:12:53 #info If there is a lab environment that can be used, even better 15:13:05 #info Sure, count me in. I can work with anyone else that is interested. 15:13:07 #info Devstack is tool fragile for me. Always breaking 15:13:16 we need people to workon tasks to setup the components - Bryan - did you share teh trello link yet? 15:13:56 #info What we need is to get ODL (Lithium) and Kilo installed into the Spirent lab 15:14:26 #info At least three non-HA nodes - two controllers and one compute 15:14:29 #link https://trello.com/b/vRhIA8sP/opnfv <— look at the “copper” list here on trello 15:14:40 #info All running as VMs 15:14:46 hi Iben 15:15:23 kilo is installed and running 15:15:40 i can give you the admin pw and we can make accounts for ourselves as needed 15:16:10 that’s for the horizon/keystone auth 15:16:11 iben: thanks, that will help 15:16:38 you (we) also have ssh access today as well - we just need bodies to setup the other parts (copper, opendaylight, etc) 15:16:41 #info iben: admin access to kilo only or to the full OPNFV install? 15:16:57 we will add the other things as needed 15:17:10 we are working towards the “B” release 15:17:20 since it is not out yet we have to build it ourselves 15:17:33 just adding the components together - using jenkins scripts 15:17:44 this makes it repeatable 15:17:52 #info B release is fine, I don't need all it but it will help with testing the SFC+GBP part using Lithium 15:18:19 #info So we need someone who can install ODL in another VM, right? 15:18:29 this lab also has ipv6 running which is needed for us 15:18:33 yes 15:18:36 #info I guess Kilo is running in its own VM? 15:18:40 we need help to setup ODL 15:18:45 #info Did you use Foreman or Fuel to setup OPNFV? That should get ODL as well right? 15:18:54 KILO is running on bare metal box 15:19:31 #link https://wiki.opnfv.org/pharos/spirentvctlab - info on spirent virtual cloud test lab with KILO and OpenDaylight 15:19:47 BTW - we have others using the lab already with ODL - we can ask them for help too 15:20:05 we need to get on the ODL integration call tomorrow - I will forward you the calendar invite 15:20:23 OK, thanks 15:20:38 What box/VM should we install ODL on? 15:20:43 #info Any reason we are not using Foreman/Fuel that automates OpenStack and ODL installation? 15:20:55 #link https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Meetings#Schedule_and_Logistics meeting invite for odl integration team 15:21:03 #info I think because it isn't ready for B release yet 15:21:18 #info o ok 15:21:21 they have a few ODL installations already in the spirent vct lab - we can ask if they will let us us one 15:21:39 #info We have to look to the installer projects to get it working basically, with the default features, then add Congress etc 15:21:53 #info In the short term we need to install Kilo + ODL manually 15:21:57 this was discussed via email today 15:22:22 we need to create our glue code then share with the install teams so they can suck it in 15:22:36 this lab is the dev environment to create that glue code. 15:22:51 OK, Iben I will reach out to you later on IRC if you're around, to get more details on which box/VM to install Lithium on 15:23:31 For the next couple of hours I'm going to solve the Copper doc toolchain issues 15:23:41 k 15:24:04 #info We should coordinate on IRC or via email - which and where? 15:24:26 #info i.e. #opnfv-copper or another channel? 15:25:59 #info I guess by default I will ping you all on #opnfv-copper to see if you're available 15:26:14 Nothing more from me right now - any other topics? 15:26:50 If not you have 30 min back... 15:27:19 #endmeeting