17:05:22 <arturt> #startmeeting JOID weekly
17:05:22 <collabot`> Meeting started Wed Nov 23 17:05:22 2016 UTC.  The chair is arturt. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:05:22 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:05:22 <collabot`> The meeting name has been set to 'joid_weekly'
17:05:29 <arturt> #info Artur Tyloch
17:05:53 <arturt> #topic Agenda bashing
17:05:58 <arturt> #link https://etherpad.opnfv.org/p/joid
17:05:59 <narindergupta> #info Narinder Gupta
17:08:00 <bryan_att> #info Bryan Sullivan
17:10:50 <arturt> #topic Colorado release
17:11:21 <arturt> #info OCL status - close to solution
17:12:12 <arturt> #info stability issues Narinder is working on
17:14:36 <arturt> #topic D release implementation
17:16:47 <bryan_att> #info I recommend that we consider how a stable release can be fully packaged with all working dependencies, e.g. for offline deployment, as a way to ensure that stable releases don't break due to external dependencies that keep changing after OPNFV release. This should be an option, if the OPNFV user needs that level of stability.
17:18:33 <bryan_att> #info I think addressing this need will benefit Canonical and OPNFV, as it gets closer to the "real-world" deployment goals that I mentioned on the OPNFV list. So the effort to make it work (including any upstream effects, e.g. on the JuJu and MAAS frameworks) will benefit those communities and commercial products based upon them.
17:19:17 <arturt> #topic OPNFV plugtest and plugfest
17:20:56 <arturt> sierakowrutra
17:25:05 <arturt> #link https://jujucharms.com/u/debayan-ch/abot-ims-basic/trusty/35
17:25:32 <bryan_att> #info final note: of course, essential things (e.g. security patches) need to get thru this "stable" code firewall, and how that would work needs to be considered. In our case it would be that we build the system internally and let in any patches through a process of staged platform CI/CD.
17:26:32 <arturt> #topic Other project
17:30:54 <arturt> Domino and Movie testing with JOID - update planned on Dec 20
17:44:25 <bryan_att> #info re config files, my input to the Infra call:  there are 3 things - the pod descriptor (actual hardware information); scenario use intent for the hardware and software settings (e.g. which NICs have which role, or the intended VIM settings); as-deployed state (including additonal VIM settings that were decided by the installer or unspecified in the
17:44:25 <bryan_att> scenario file)
17:44:33 <arturt> #topic JIRA issues review
17:44:41 <bryan_att> #info ... scenario file)
17:45:39 <bryan_att> #info log of the Infra meeting: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-11-23-04.31.log.html
18:41:04 <bryan_att> narindergupta: let me know when the deploy issue is resolved. otherwise I will just keep trying.
18:41:33 <narindergupta> bryan_att, sure i will let you know. Also my next target will be 16.04
18:41:49 <narindergupta> where we are not using juju-deployer using just juju
18:42:14 <bryan_att> narindergupta: anything I can do to help you there let me know. e,g. the issues I posted in IRC earlier with the virtual install. if you need them again let me know.
18:43:03 <narindergupta> not now. Lets resolv this current issue first
18:43:23 <bryan_att> ok, they're in the log for later
15:58:04 <arturt> #endmeeting