18:00:02 <bh526r_> #startmeeting gluon
18:00:03 <openstack> Meeting started Wed Mar 29 18:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r_. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:07 <openstack> The meeting name has been set to 'gluon'
18:00:17 <pcarver> hi
18:00:19 <bh526r_> #topic Roll Call
18:00:23 <bh526r_> Hi Paul
18:00:27 <bh526r_> #info Bin Hu
18:00:35 <pcarver> #info Paul Carver
18:00:41 <krenczewski> #info Kamil Renczewski
18:01:12 <bh526r_> Hi Kamil
18:01:27 <krenczewski> Hi Bin
18:01:49 <georgk> #info Georg Kunz
18:02:34 <bh526r_> Hi Georg
18:02:42 <bh526r_> #topic Admin Update
18:03:13 <bh526r_> #info We are planning PoC/demo for OpenStack Summit in Boston
18:03:15 <georgk> hi
18:03:33 <bh526r_> #info There are several opportunities
18:04:05 <bh526r_> #info First is SDN NFV (Nirvana Stack) Mini-Summit on Thursday May 11
18:04:31 <bh526r_> #info Second is OPNFV Open Source Days Mini Summit on Monday May 8
18:05:03 <bh526r_> ##info Third is in AT&T Booth in Marketplace
18:05:37 <bh526r_> #info Fourth is that we can also demo Gluon in OPNFV Booth in Marketplace at various times
18:06:07 <bh526r_> #info I have also submitted a proposal of a session in Forum:
18:06:34 <bh526r_> #link http://forumtopics.openstack.org/cfp/details/47
18:07:03 <bh526r_> #info We will have lots of activities in Boston. Hope you all can make it
18:07:38 <bh526r_> #topic PoC Update for Boston Summit
18:07:48 <bh526r_> #link https://wiki.openstack.org/wiki/Gluon/PoC-Boston
18:08:12 <bh526r_> #info The scope description and general tasks and steps are in wiki [age
18:09:19 <bh526r_> #info 1. Lab Status
18:09:43 <bh526r_> #info Georg has re-deployed Fuel OpenStack, and will re-deploy and re-verify Gluon there
18:10:51 <bh526r_> #info Robert also set up the hardware in Santa Clara, and configured 2 networks. He will complete setting up admin network and install NetReady there.
18:11:07 <bh526r_> #info 2. Contrail Status
18:11:20 <krenczewski> +I was able to install Contrail today
18:11:45 <bh526r_> #info Kamil found issues with deploying Contrail. And he is able to install Contrail now.
18:11:51 <krenczewski> I need to check couple of things and do some configuration
18:11:52 <bh526r_> great news
18:11:55 <jinli> #info JinLi
18:12:03 <krenczewski> but this should be easy now
18:12:25 <bh526r_> Sounds good. Then you can try to make mechanism driver work, right?
18:12:36 <krenczewski> So next steps are: configure and later deploy mechanis driver on control node
18:12:48 <krenczewski> Yes
18:13:04 <bh526r_> #info Kamil's next step is to configure and later deploy Mechanism Driver on controller node
18:13:39 <bh526r_> #info So we are one more step forward
18:13:57 <bh526r_> #info 3. L3VPN YAML and API
18:14:13 <bh526r_> #info Georg has submitted a patch
18:15:13 <bh526r_> #link https://review.openstack.org/#/c/450917/
18:16:05 <bh526r_> #info There is a build failure. Log is here:
18:16:24 <bh526r_> #link http://logs.openstack.org/17/450917/1/check/gate-gluon-python27-ubuntu-xenial/6b5c5a3/console.html
18:17:45 <bh526r_> anyone has insight about this error "oslo_config.cfg.NoSuchOptError: no such option sqlite_db in group [database]"?
18:18:58 <georgk> well, I think the sqlite_db option is nowhere defined as a configruation option
18:19:13 <georgk> so i am wondering why the tests succeeded at all before
18:19:22 <georgk> that´s my current understanding
18:19:58 <bh526r_> it might be related to patch https://review.openstack.org/#/c/446776/, which removed those imports that are not explicitly used in code
18:21:30 <bh526r_> I remember several months ago, there was a similar effort to remove unused import, but Tom said that that unused import is actually used implicitly
18:26:17 <bh526r_> ok, let's dig further offline
18:26:48 <bh526r_> #info 4. SFC YAML, P2P YAML and ELAN YAML
18:27:18 <bh526r_> #info Georg, Robert/Ian and Eric/Ian will work on it respectively
18:28:44 <bh526r_> #topic Pike Release Tasks
18:29:21 <bh526r_> #link https://wiki.openstack.org/wiki/Gluon/Tasks-Pike
18:29:54 <bh526r_> #info Thanks to Jin, Georg and everyone that signed up for some tasks
18:30:47 <bh526r_> That's all from my side
18:31:00 <bh526r_> #topic AOB
18:31:24 <bh526r_> anything else to discuss except debugging the sqllite_db issue?
18:32:42 <georgk> no, i am good
18:32:47 <bh526r_> @georgk, this might be helpful:
18:32:51 <bh526r_> #link https://github.com/openstack/oslo.db/commit/master
18:33:06 <bh526r_> Merge "Remove deprecated config option sqlite_db"
18:33:28 <georgk> oh, yes
18:33:43 <bh526r_> It was done 5 days ago
18:33:57 <georgk> ah, i checked the wrong repo
18:34:11 <georgk> oslo.config instead of oslo.db
18:34:17 <georgk> thanks for the hint
18:34:49 <bh526r_> sure. any idea to fix it?
18:36:33 <bh526r_> one way might indicate the oslo version !>= x.x.x so to rely on the oslo.db before the deprecation
18:37:51 <georgk> maybe that´s one way to fix it, but i guess this is no permanent fix
18:37:54 <jinli> In the bottom of the page Bin posted , they have some suggestions
18:38:06 <jinli> +upgrade:
18:38:07 <jinli> 3 +  - The configuration option ``sqlite_db`` is removed. Pease use
18:38:07 <jinli> 4 +    configuration option ``connection`` or ``slave_connection``
18:38:07 <jinli> 5 +    to connect to the database.
18:38:35 <georgk> yeap, let´s do that
18:40:18 <bh526r_> Yup, that's the right way.
18:40:56 <bh526r_> Will you submit an updated patch set with this fix?
18:41:38 <georgk> i can take a look
18:41:50 <bh526r_> Great
18:41:51 <georgk> but i suggest to create a new patchse
18:41:52 <georgk> t
18:42:03 <georgk> to not mix the bugfix and the API extension
18:42:07 <bh526r_> sure.
18:42:23 <bh526r_> perhaps the new patch first.
18:43:03 <bh526r_> Hope the new patch works well to fix the deprecated sqlite_db
18:45:19 <bh526r_> I greped the code, and sqlite_db is only used in gluon/tests/db/base.py
18:46:21 <bh526r_> ok, good.
18:46:29 <bh526r_> anything else?
18:47:23 <bh526r_> Are you good, georgk?
18:48:25 <bh526r_> if nothing else, we can adjourn and give back 12 minutes to everyone
18:48:36 <bh526r_> #info Meeting adjourned
18:48:44 <bh526r_> #endmeeting