Monday, 2017-01-30

*** thorst_ has joined #openstack-meeting-400:00
*** thorst_ has quit IRC00:04
*** baoli has joined #openstack-meeting-400:05
*** spotz_zzz is now known as spotz00:08
*** sdake has joined #openstack-meeting-400:09
*** thorst_ has joined #openstack-meeting-400:13
*** thorst_ has quit IRC00:13
*** acabot has quit IRC00:13
*** sdake has quit IRC00:14
*** spotz is now known as spotz_zzz00:18
*** sshnaidm has joined #openstack-meeting-400:34
*** sdake has joined #openstack-meeting-400:39
*** armax has quit IRC00:51
*** bobh has joined #openstack-meeting-400:58
*** bobh has quit IRC01:18
*** sdake has quit IRC01:28
*** thorst_ has joined #openstack-meeting-401:44
*** bobmel has joined #openstack-meeting-401:44
*** admcleod_ has joined #openstack-meeting-401:44
*** admcleod has quit IRC01:46
*** bobmel has quit IRC01:49
*** thorst_ has quit IRC01:49
*** amotoki has joined #openstack-meeting-401:53
*** Julien-zte has joined #openstack-meeting-401:58
*** v1k0d3n has quit IRC02:00
*** v1k0d3n has joined #openstack-meeting-402:02
*** iyamahat has joined #openstack-meeting-402:02
*** sferna1_ has quit IRC02:03
*** thorst_ has joined #openstack-meeting-402:09
*** spotz_zzz is now known as spotz02:09
*** unicell has quit IRC02:10
*** thorst_ has quit IRC02:12
*** hemanthm is now known as hemanthm|afk02:16
*** amotoki has quit IRC02:18
*** spotz is now known as spotz_zzz02:20
*** sdake has joined #openstack-meeting-402:20
*** sdake has quit IRC02:20
*** yamahata has joined #openstack-meeting-402:23
*** amotoki has joined #openstack-meeting-402:26
*** sdake has joined #openstack-meeting-402:32
*** reedip_ has joined #openstack-meeting-402:36
*** hongbin has joined #openstack-meeting-402:44
*** amotoki has quit IRC02:45
*** thorst_ has joined #openstack-meeting-402:57
*** thorst_ has quit IRC02:57
*** baoli has quit IRC02:58
*** Sukhdev has joined #openstack-meeting-403:01
*** thorst_ has joined #openstack-meeting-403:07
*** thorst_ has quit IRC03:07
*** sdake has quit IRC03:12
*** sdake has joined #openstack-meeting-403:13
*** reedip_ has quit IRC03:14
*** Julien-zte has quit IRC03:17
*** sdake has quit IRC03:22
*** hoangcx has joined #openstack-meeting-403:41
*** amotoki has joined #openstack-meeting-403:45
*** hoangcx has quit IRC03:47
*** sdake has joined #openstack-meeting-403:51
*** links has joined #openstack-meeting-403:56
*** links has quit IRC03:57
*** baoli has joined #openstack-meeting-403:57
*** hoangcx has joined #openstack-meeting-404:00
*** hoangcx has quit IRC04:00
*** baoli has quit IRC04:04
*** baoli has joined #openstack-meeting-404:10
*** spotz_zzz is now known as spotz04:12
*** baoli has quit IRC04:12
*** sdake has quit IRC04:17
*** baoli has joined #openstack-meeting-404:18
*** sanfern has joined #openstack-meeting-404:18
*** spotz is now known as spotz_zzz04:21
*** sdake has joined #openstack-meeting-404:25
*** baoli has quit IRC04:32
*** rainya has joined #openstack-meeting-404:33
*** sdake_ has joined #openstack-meeting-404:35
*** yfauser has joined #openstack-meeting-404:36
*** rainya has quit IRC04:38
*** sdake has quit IRC04:38
*** sanfern has quit IRC04:49
*** sanfern has joined #openstack-meeting-404:50
*** atuly_ has quit IRC04:55
*** amotoki has quit IRC04:56
*** hemanthm|afk is now known as hemanthm05:05
*** atuly_ has joined #openstack-meeting-405:07
*** hongbin has quit IRC05:10
*** spotz_zzz is now known as spotz05:12
*** sdake_ has quit IRC05:15
*** spotz is now known as spotz_zzz05:22
*** amotoki has joined #openstack-meeting-405:25
*** sanfern has quit IRC05:26
*** sanfern has joined #openstack-meeting-405:27
*** psachin has joined #openstack-meeting-405:28
*** sferna1_ has joined #openstack-meeting-405:32
*** sanfern has quit IRC05:34
*** unicell has joined #openstack-meeting-405:44
*** thorst_ has joined #openstack-meeting-405:49
*** thorst_ has quit IRC05:55
*** adisky_ has joined #openstack-meeting-405:59
*** unicell1 has joined #openstack-meeting-406:01
*** unicell has quit IRC06:02
*** anilvenkata has joined #openstack-meeting-406:08
*** spotz_zzz is now known as spotz06:13
*** nkrinner_afk is now known as nkrinner06:17
*** spotz is now known as spotz_zzz06:23
*** yfauser has quit IRC06:52
*** yfauser has joined #openstack-meeting-406:56
*** yfauser has quit IRC07:01
*** unicell has joined #openstack-meeting-407:07
*** unicell1 has quit IRC07:08
*** spotz_zzz is now known as spotz07:14
*** trinaths has joined #openstack-meeting-407:14
*** spotz is now known as spotz_zzz07:24
*** yamamoto has quit IRC07:27
*** karthiks has joined #openstack-meeting-407:29
*** thorst_ has joined #openstack-meeting-407:51
*** matrohon has joined #openstack-meeting-407:52
*** thorst_ has quit IRC07:56
*** yfauser has joined #openstack-meeting-407:57
*** yfauser has quit IRC08:02
*** Sukhdev has quit IRC08:02
*** sferna1__ has joined #openstack-meeting-408:06
*** sferna1_ has quit IRC08:08
*** spotz_zzz is now known as spotz08:15
*** pcaruana has joined #openstack-meeting-408:15
*** dtardivel has joined #openstack-meeting-408:18
*** spotz is now known as spotz_zzz08:25
*** alexchadin has joined #openstack-meeting-408:30
*** rainya has joined #openstack-meeting-408:38
*** alexchadin has quit IRC08:38
*** alexchadin has joined #openstack-meeting-408:39
*** rainya has quit IRC08:43
*** mohankumar_ has joined #openstack-meeting-408:55
*** ishafran has joined #openstack-meeting-408:56
*** yfauser has joined #openstack-meeting-408:58
*** amotoki has quit IRC08:59
*** ralonsoh has joined #openstack-meeting-409:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Jan 30 09:00:15 2017 UTC and is due to finish in 60 minutes.  The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: Dragonflow)"09:00
openstackThe meeting name has been set to 'dragonflow'09:00
oansonHi. Who's here for the Dragonflow weekly?09:00
lihiHi09:00
*** amotoki has joined #openstack-meeting-409:00
oansonIf it's just the two of us, we have an issue.09:00
oansonI understood it's the new year in china, so they are in holiday09:01
dimakHey09:01
oansonLet's wait another minute, and take it from there09:01
*** yfauser has quit IRC09:02
irenabhi09:02
yuli_shello09:02
oansonSince we are a skeleton crew today, I'll just run through the stuff real quick09:03
ishafranHi09:03
oansonIPv6 - Waiting on lihi for security group support.09:03
oansonSFC - no change.09:03
oansonService health reporting - no change (AFAIK)09:03
oansonTap as a service - No change (AFAIK)09:04
oansonsNAT - There is a new patch set. Please review09:04
*** itamaro has joined #openstack-meeting-409:04
lihiI'll upload a patch today for the sg09:04
oansonNB Refactor - There are new patches. Please review.09:04
itamaroHi All09:04
oansondimak, note that the tests are failing on the more advanced stuff. Please fix.09:04
oansonNative API - There is a spec, but it's WF-1. I think it is ready for review/voting09:05
dimakYeah, openstack picked a new version of jsonmodels and I need to fix something there, I hope it gets merges and released by tomorrow09:05
dimak*openstack-requirements09:05
oansondimak, sound good, oh jsonmodels lead commiter!09:05
irenaboanson, I added working items to the API spec, will upload the patch in few mins09:06
oansonGreat! Once that's done, it can be reviewed09:06
yuli_si am trying to push my commits to be finally released.09:06
oansonyuli_s, great!09:06
oansonAnything else for roadmap?09:06
oanson#topic bugs09:07
*** openstack changes topic to "bugs (Meeting topic: Dragonflow)"09:07
dimakI hope we can merge nb refactor spec too :)09:07
oansonHopefully09:07
dimakI'll remove the line Irena pointed out if there's another PS09:07
oansonnick-ma added a spec for the duplicate publisher issues: https://review.openstack.org/#/c/425619/09:07
oansonI'd be happy if it can be reviewed. It looks very interesting09:08
*** barmaley has joined #openstack-meeting-409:08
oansonThat's all I have for bugs.09:08
oansonAnything else, or can we move on?09:08
yuli_syes09:08
*** rajivk has joined #openstack-meeting-409:08
oansonyuli_s, shoot!09:08
yuli_san old problem with private network tenant is getting back09:09
yuli_sI need to do "NEUTRON_CREATE_INITIAL_NETWORKS=False"09:09
yuli_sto run stack.sh09:09
oansonyuli_s, I ran stack yesterday, and it worked09:09
oansonAre you sure it's not an environment issue?09:10
yuli_shm, you have this line in configuration ?09:10
yuli_sby default it should be true09:10
oansonNope09:10
oansonNo such line in my local.conf09:10
lihiI think I ran into this issue also09:10
lihiOn new VM and env09:11
oansonlihi, can you verify? Does adding this line help?09:11
*** iyamahat has quit IRC09:11
lihiI'll try. I did not knew adding it might help09:11
*** yamahata has quit IRC09:11
oansonAnyone else seeing this issue?09:11
oansonAll right. lihi, yuli_s, let's take this offline.09:12
oansonAnything else for bugs?09:12
*** rajivk has left #openstack-meeting-409:13
oanson#topic Open Discussion09:13
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:13
oansonThe floor is for the taking09:13
itamaroThere is a small bug I encountered while doing my tests, I published a fix,Pls review it09:13
oansonitamaro, what's the link?09:14
itamarohttps://review.openstack.org/#/c/426601/09:14
dimakWill take a look09:14
oansonSame here09:15
itamaro:)09:15
oansonThe floor is free once more09:15
*** sferna1__ has left #openstack-meeting-409:15
dimakI have a patch for datapath prop09:15
dimakI want it in quite fast as it is a pain to rebase09:15
dimakhttps://review.openstack.org/#/c/426584/09:16
oansonHmm....09:16
itamaroIt has a lot of lines. but the change is stright forward :)09:17
oansondimak, any chance we give nick-ma/xiaohhui another day to look at it?09:17
dimakSure09:17
oansonYes09:17
oansonyuli_s, please review it too.09:17
dimakIf nick-ma is not around then we don't have 2x +2 for other patches as well :P09:18
oansonYes. But he will be back next week.09:18
oansonAll right. Let's wait until tomorrow.09:18
dimakI meant that it can wait without rebasing09:18
dimakBecause other patches will wait too09:18
oansonyuli_s, please review it as well. I will feel better pushing it if your review is there as well09:19
oansonOther patches can already rebase on top of this patch. I doubt it will have any major changes, even if there are negative reviews.09:19
oansonAnd I agree it's important09:20
oansonMakes our code simpler09:20
oansonishafran, if you want to review it as well, that can also help09:20
oansonBasically, I want another review! :)09:20
ishafranOK I'll review it too09:21
oansonThanks!09:21
oansonThe floor is for the taking again09:21
ishafranI reviewed changes required for different modes of SNAT: global IP/tenant based IP. Current intention to separate SNAT application into two different applications with common code base09:21
ishafranAre we OK with it?09:21
oansonI am, but I am not sure everyone knows what this is about. Maybe give some context?09:22
itamaroWhy no do it in one apllication and have  cofiguration dictate behevior09:22
ishafranit described well in spec09:22
itamaronot09:22
ishafranI tried to make it this way - too much ifs09:23
itamaroit can be a compiste class or impl-pimpl kind of implemantation09:24
oansonFine. I'll give the context :)09:24
oansonThe snat application is designed to have two modes of operation09:25
oanson1. single external IP assigned to the host/compute node09:25
oanson2. A pool of IPs, each assigned to <host, tenant> pair09:25
oansonno. 1 is up for review09:25
oansonno. 2 is now being written. Will it be written as part of the original application (option 1), or as a second application?09:26
oansonAnd extract a base class to parent both apps.09:26
oansonishafran, is this summary correct?09:26
itamarounderstood.09:26
ishafransummary is perfect :)09:26
itamarostill think an envolope class that 'loads' the right impl is a ggod way to do it.09:27
ishafranyou mean dynamically loaded implementation09:27
oansonitamaro, that's an infrastructure we don't have, that will be used only for one app09:27
*** jschwarz is now known as jschwarz|lunch09:27
oansonWe already have such a configuration - it states which apps to load :)09:28
itamaroOK09:28
oansonAll right, so we're agreed - 2 apps, with a parent class?09:28
dimakOr a common module they use :)09:29
ishafranI guess I will implement it separately and then I'll think how to pack it together09:29
oansondimak, even better, if it can be done09:29
oansonishafran, sounds like a plan09:29
oansonAre we all agreed then?09:30
itamaroV09:30
oansonThe floor is free once more09:30
oansonThe floor is lava - take it while it's hot!09:31
*** janki has joined #openstack-meeting-409:31
oansonAll right. Thanks everyone for coming.09:31
oanson#endmeeting09:31
itamarobye09:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:31
openstackMeeting ended Mon Jan 30 09:31:40 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-01-30-09.00.html09:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-01-30-09.00.txt09:31
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-01-30-09.00.log.html09:31
dimakBye09:31
*** jchhatbar_ has joined #openstack-meeting-409:36
*** ishafran has quit IRC09:36
*** janki has quit IRC09:38
*** jchhatbar_ has quit IRC09:41
*** janki has joined #openstack-meeting-409:41
*** makowals has quit IRC09:48
*** makowals has joined #openstack-meeting-409:49
*** thorst_ has joined #openstack-meeting-409:52
*** makowals has quit IRC09:54
*** makowals has joined #openstack-meeting-409:55
*** thorst_ has quit IRC09:57
*** janki has quit IRC09:58
jamespageo/10:01
gnuoyo/10:01
tinwood\o10:02
jamespage#startmeeting charms10:03
openstackMeeting started Mon Jan 30 10:03:33 2017 UTC and is due to finish in 60 minutes.  The chair is jamespage. Information about MeetBot at http://wiki.debian.org/MeetBot.10:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.10:03
*** openstack changes topic to " (Meeting topic: charms)"10:03
openstackThe meeting name has been set to 'charms'10:03
jamespagehi folks10:03
jamespageso this is the first run for the earlier meeting slot - lets see how this goes10:03
* jamespage reads previous10:04
jamespage#topic Review ACTION points from previous meeting10:04
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"10:04
jamespagejamespage    talk py27 retirement with tc as ptl10:04
jamespagecarry that forward still - hoping to chat with folks about that at the PTG10:04
jamespage#action jamespage  to  talk py27 retirement with tc as ptl10:04
jamespagecholcombe    close out bugs against ceph-fs10:05
jamespageas cholcombe won't be at this slot, lets carry that forwards but I'm pretty sure he's close10:05
gnuoyI think he just had one left10:05
jamespage#action cholcombe    close out bugs against ceph-fs10:05
jamespage#topic State of Development for next Charm Release10:05
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"10:05
*** amotoki has quit IRC10:05
jamespagereminder on dates10:05
jamespageFeb 9 - feature freeze - new features must be landed by this date10:06
jamespageFeb 23 will be the charm release date10:06
jamespagein terms of new features I think we have some work to complete on the new charms in terms of functional tests10:06
jamespageand I know that huats is working on the functional tests for the cloudkitty charm, so hopefully we can include that as wll10:06
jamespageI'm also working on a feature to support domain specific backends in the keystone charm; I anticipate that the changes for keystone will land this week10:07
jamespagewith a new keystone-ldap backend charm in the pipe for freeze day as well10:07
jamespageBUT I would say a few of us have travel and conference commitments over the next 10 days or so10:08
jamespageso that might be tight!10:08
jamespagegnuoy, tinwood: anything else to add?10:08
gnuoyI'm going to finally move the charm templating stuff upstream10:08
jamespage\o/10:08
tinwoodI'm still circling the manila templating stuff, but I'm a bit pushed for time.  Hope so.10:09
jamespagelets get a baseline in first, and then we can iterate on new templates10:09
jamespageI was going todo one for keystonebackends but then realized that ldap is pretty much the only one :-)10:10
jamespage#topic High Priority Bugs10:10
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"10:10
tinwood:)10:10
tinwood(not :) to high priority bugs btw)10:10
jamespageOK so current breakdown is that we have 4 critical and 71 high priority bugs open still (that excludes anything fix committed btw)10:11
jamespagethursday is a bug day so maybe we can get some traction on that subset of the bug base10:11
gnuoyyay for bug day10:12
jamespagewe're still getting a general tickover of new bugs entering the queue so please remember to try to spend some time each week looking at new bugs please10:12
tinwoodsure thing10:12
gnuoyack10:13
jamespagelink to LP is in the topic in #openstack-charms10:13
jamespage#topic Openstack Events10:13
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"10:13
jamespageOKIES10:13
jamespageso we have FOSDEM and ConfigMangement camp coming up over the weekend and next week10:13
gnuoyI'll be at ConfigMangement camp10:14
tinwoodMee too10:14
jamespageI'l speaking at FOSDEM on LXD + Nova-LXD with stgraber on saurday10:14
jamespageand we have sessions scheduled in the Juju track at configmangement camp so see you all there!10:14
jamespageand then the PTG is three weeks away10:14
jamespage#action jamespage to send out etherpad link to list for charms planning for mon/tues10:14
jamespage#action all - brainstorm ideas so we can come up with a scheduler and objectives for the PTG10:15
jamespage#topic Open Discussion10:15
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"10:15
jamespagefloor is open10:15
tinwoodgnuoy and me are doing a workshop on writing better charms at cfgmgmtcamp10:15
tinwoodOn the Tuesday.10:15
*** amotoki has joined #openstack-meeting-410:15
tinwoodIt's an interactive workshop.  Should be fun.10:15
gnuoyI shall be tinwood debbie mcgee10:15
tinwood:)10:16
gnuoys/tinwood/tinwoods/10:16
*** spotz_zzz is now known as spotz10:16
gnuoyjamespage, are we done with the open chat?10:20
jamespage#endmeeting10:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:20
openstackMeeting ended Mon Jan 30 10:20:34 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-01-30-10.03.html10:20
jamespageyes10:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-01-30-10.03.txt10:20
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-01-30-10.03.log.html10:20
gnuoythanks jamespage10:20
tinwoodthanks jamespage10:20
*** spotz is now known as spotz_zzz10:26
*** sambetts|afk is now known as sambetts10:28
*** neiljerram has joined #openstack-meeting-410:30
*** pbourke has quit IRC10:32
*** pbourke has joined #openstack-meeting-410:32
*** amotoki has quit IRC10:34
*** rainya has joined #openstack-meeting-410:40
*** rainya has quit IRC10:44
*** yfauser has joined #openstack-meeting-410:59
*** rfolco has joined #openstack-meeting-410:59
*** trinaths1 has joined #openstack-meeting-411:02
*** trinaths has quit IRC11:02
*** yfauser has quit IRC11:03
*** janki has joined #openstack-meeting-411:12
*** spotz_zzz is now known as spotz11:17
*** dims has joined #openstack-meeting-411:26
*** spotz is now known as spotz_zzz11:27
*** psachin has quit IRC11:32
*** alexchadin has quit IRC11:32
*** rainya has joined #openstack-meeting-411:41
*** trinaths1 has quit IRC11:41
*** rainya has quit IRC11:45
*** thorst_ has joined #openstack-meeting-411:53
*** alexchadin has joined #openstack-meeting-411:57
*** thorst_ has quit IRC11:57
*** alexchadin has quit IRC12:01
*** alexchadin has joined #openstack-meeting-412:01
*** alexchadin has quit IRC12:06
*** spotz_zzz is now known as spotz12:18
*** spotz is now known as spotz_zzz12:28
*** janki has quit IRC12:30
*** sdague has joined #openstack-meeting-412:40
*** thorst_ has joined #openstack-meeting-412:41
*** bobh has joined #openstack-meeting-412:49
*** janki has joined #openstack-meeting-412:51
*** dave-mccowan has joined #openstack-meeting-413:00
*** yfauser has joined #openstack-meeting-413:01
*** yfauser has quit IRC13:06
*** matrohon has quit IRC13:09
*** matrohon has joined #openstack-meeting-413:11
*** spotz_zzz is now known as spotz13:19
*** bobmel has joined #openstack-meeting-413:27
*** spotz is now known as spotz_zzz13:29
*** bobh has quit IRC13:30
*** Christophe_ has joined #openstack-meeting-413:38
*** woodard_ has quit IRC13:42
*** sdake has joined #openstack-meeting-413:42
*** woodard has joined #openstack-meeting-413:43
*** acabot has joined #openstack-meeting-413:49
*** Christophe_ has left #openstack-meeting-413:50
*** alraddarla has joined #openstack-meeting-413:50
*** baoli has joined #openstack-meeting-413:50
*** cleong has joined #openstack-meeting-413:53
*** sdake has quit IRC13:58
*** alexchadin has joined #openstack-meeting-413:59
*** karthiks has quit IRC13:59
*** ivc_ has joined #openstack-meeting-413:59
*** alexchadin has quit IRC14:00
*** apuimedo has joined #openstack-meeting-414:00
*** alexchadin has joined #openstack-meeting-414:00
*** garyloug has joined #openstack-meeting-414:00
*** jschwarz|lunch is now known as jschwarz14:01
apuimedo#startmeeting kuryr14:01
openstackMeeting started Mon Jan 30 14:01:15 2017 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: kuryr)"14:01
openstackThe meeting name has been set to 'kuryr'14:01
apuimedoHello everybody and welcome to another kuryr meeting!14:01
apuimedoWho's here for the show?14:01
ivc_o/14:01
janonymouso/14:01
garylougo/14:01
irenabhi14:01
apuimedoivc_: ltomasbo: ?14:02
jankio/14:02
apuimedoivc_: is already here, I'm on the moon14:02
apuimedosorry14:02
ivc_apuimedo :)14:02
apuimedoalright then!14:02
apuimedolet's move forward14:02
apuimedo#topic kuryr-libnetwork14:03
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:03
*** Gideon has joined #openstack-meeting-414:03
ltomasboo/14:03
alraddarlao/14:04
apuimedo#info yedongcan's tag optimization patch seems to have progressed well https://review.openstack.org/#/c/420610/14:04
apuimedoirenab: please review it when you get the chance14:04
irenabapuimedo: ok14:04
GideonCan I ask about Magnum<>Kuryr integration?14:05
apuimedoGideon: sure thing14:05
*** alexchadin has quit IRC14:05
GideonIs it planned for a specific OS release?14:05
apuimedo#info yedongcan's https://review.openstack.org/419735 is also ready for merge14:06
apuimedotag support is improving :-)14:06
apuimedoGideon: If there is people working on it, we could probably do pike for kuryr-libnetwork14:07
apuimedofor kuryr-kubernetes it may be a bit tighter, but we'd like to get there too14:07
apuimedojust there's nobody at the moment sponsoring this work directly, although hongbin has been pushing on it14:08
apuimedoand we've been doing the groundwork necessary to tackle it14:08
apuimedoI think the remaining work is outside our repos, so we have to do a bit of asking14:08
*** sdake has joined #openstack-meeting-414:09
GideonThanks. I'm from Nokia and we see added value in integrating both. I'll check with Redhat.14:09
apuimedo#info janonymous's tls patch that adds TLS support for our ipam/rd driver seems ready https://review.openstack.org/#/c/410609/14:09
apuimedoGideon: I remember you from the meeting we ahd14:10
apuimedo*had14:10
apuimedo;-)14:10
Gideonoh. The nicknames are not so clear...14:10
janonymousI could not find the reason for non-voting gate failure though...14:11
apuimedoI'm the bearded PTL of Kuryr (who works at RH)14:11
janonymousHaha14:11
apuimedojanonymous: that's exactly what I was gonna ask you14:11
GideonAntony14:11
apuimedoGideon: yes, Antoni14:11
janonymousapuimedo: i tried digging down, i saw only busy box failure14:11
janonymousnothing that might fail the gate though14:11
*** cathrichardson has joined #openstack-meeting-414:11
apuimedojanonymous: could you run the fullstack tests locally on a new 16.04 machine and paste me the output?14:12
apuimedowhich brings up14:12
apuimedoI would like to propose to make the fullstack tests voting14:12
irenabjanonymous: in k8s or libnetwork?14:13
apuimedoI think they have been non-voting for enough time14:13
janonymousapuimedo: sure, will do it tomorrow on top priority!14:13
apuimedoirenab: kuryr-libnetwork14:13
apuimedothanks Jaivish14:13
irenabok14:13
*** cathrich_ has quit IRC14:13
janonymousirenabL libenetwork14:13
apuimedoalraddarla: what's the status on https://review.openstack.org/#/c/422394/14:14
apuimedoI saw there was some discussion, but I think I probably missed some context14:14
*** sdake has quit IRC14:14
alraddarlaEssentially that patch and mine could easily be merged. I was waiting to see what everyone wanted to do.14:15
alraddarlaI am more than happy to merge that patch with mine and put the co-author tag on.14:15
*** pc_m has joined #openstack-meeting-414:15
alraddarlaNo one ever responded to my question though so I didn't want to overstep14:15
apuimedoalraddarla: doesn't it make more sense to simple rebase rajiv's patch on top of yours?14:15
apuimedos/simple/simply/14:15
alraddarlaThat would work as well! If you guys would like to merge mine14:16
alraddarlahttps://review.openstack.org/#/c/424198/14:17
alraddarlaAt least review it, I mean :)14:17
apuimedoalraddarla: please, remember to add people as reviewers, otherwise sometimes we miss patches ;-)14:17
apuimedo(just did for this patch now14:18
apuimedo)14:18
apuimedo#action apuimedo irenab vikasc limao to review the reno support patch https://review.openstack.org/#/c/424198/14:18
*** cathrichardson has left #openstack-meeting-414:18
apuimedo#action rajiv rebase https://review.openstack.org/#/c/422394/2 on top of https://review.openstack.org/#/c/424198/14:19
apuimedoAnything else on kuryr-libnetwork?14:19
apuimedoalright then... Moving on!14:20
alraddarlaapuimedo, yes. My apologies. I forgot14:20
apuimedo#topic fuxi14:20
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:20
apuimedohongbin is not here today since it's the Chinese new year's Holidays :-)14:20
*** mchiappe1o is now known as mchiappero14:20
apuimedo#info The proposal to containerize Fuxi has been accepted for Pike https://blueprints.launchpad.net/kolla/+spec/containerized-fuxi14:21
apuimedo#info Kuryr-kubernetes has been accepted as a subproject https://review.openstack.org/#/c/423791/14:21
apuimedofsck!!!14:21
apuimedo#info fuxi-kubernetes has been accepted as a subproject https://review.openstack.org/#/c/423791/14:22
janonymous but why fuxi-kubernetes?14:22
apuimedoFor those keeping the score at home, k8s already has cinder integration, but only for when k8s runs on OSt VMs14:22
apuimedothis is for bare-metal14:22
janonymoussorry but wanted to know about fuxi-kubernetes as kubernetes has already cinder support14:22
apuimedojanonymous: as I stated above, for bare-metal cases14:23
janonymousyeah14:23
apuimedoand maybe for some functionality like snapshotting14:23
apuimedobut we'll see about that one14:23
janonymousapuiemdo:thanks14:23
apuimedoI want to keep the scope small14:23
apuimedoWe already have bare-metal kubernetes in scope, so it was logical to accept the proposal14:23
janonymousyeah great!14:24
apuimedobut going to replicate the in-tree functionality is going to be a harder sell :-)14:24
apuimedo#topic kuryr-kubernetes14:24
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:24
irenabapuimedo: regarding previous topic14:25
apuimedoThanks janonymous for https://review.openstack.org/#/c/424972/114:25
apuimedo:-)14:25
apuimedoirenab: go ahead, sorry I closed it so fast14:25
irenabfuxi is for libnetwork and fuxi-kubernetes is for k8s?14:25
janonymoustrivial bump :D14:25
apuimedoirenab: yes. We should probably consider a rename of 'fuxi'14:26
apuimedoto keep consistency with the networking naming14:26
irenabapuimedo: yes, will be less confusing14:26
apuimedoirenab: also. I'm not sure if fuxi folks shouldn't just add handlers and drivers to kuryr-kubernetes14:27
apuimedootherwise they are going to duplicate a good bit of effort14:27
apuimedomaybe they can import kuryr-k8s in their repo14:27
apuimedobut that's gonna be painful with the fast evolution14:27
irenabapuimedo: I also would like to undrstand more on what is ging to land there14:27
*** mattmceuen has joined #openstack-meeting-414:28
irenabapuimedo: wasthere any email on this?14:28
apuimedoirenab: it will be tackled on the vtg session14:28
apuimedothere were some emails but for some reason they did not send them to the list14:28
irenabok, just looks its getting crowded in the kury arena :-)14:29
apuimedoI'll start a thread in the ml14:29
apuimedoirenab: I still want to possibly help fuxi to move out of home, since it's starting to grow a beard14:29
apuimedo#action apuimedo to send ML thread about fuxi-kubernetes14:30
apuimedo#info Merging ivc_'s patch to move from id to selflink to ease troubleshooting https://review.openstack.org/#/c/423903/214:30
apuimedo#action irenab to look at this dragonflow gate failure https://review.openstack.org/#/c/425597/114:31
*** sdake has joined #openstack-meeting-414:31
*** sdake has quit IRC14:31
irenabapuimedo: https://bugs.launchpad.net/dragonflow/+bug/166034614:32
openstackLaunchpad bug 1660346 in DragonFlow "setting initial networking with df devstack fails" [Undecided,New]14:32
apuimedoirenab: that was fast!14:32
irenab:-)14:32
apuimedo#info df nv gate affected by https://bugs.launchpad.net/dragonflow/+bug/166034614:32
apuimedo#action ivc_ to address comments to https://review.openstack.org/#/c/422946/14:33
apuimedo:-)14:33
apuimedoTHis patch helps us me more understanding of resourceVersions conflicts and not just fail when there's a missmatch14:33
apuimedothanks for that!14:33
apuimedo#info ivc_ pushed a temp improvement for skipping events that would force us into repeating handler work https://review.openstack.org/#/c/422910/ It will make the handler 'actor' for an entity sleep to increase the likelihood of having the annotation by the time the next "irrelevant" event comes around14:35
apuimedoThe idea is to make some code in the k8s client that handles this case more gracefully, but for now it is a good improvement14:36
apuimedo#action irenab ltomasbo vikasc to review https://review.openstack.org/#/c/422910/14:36
irenabapuimedo: there is also k8s provided client in the incubation state, we may want to move using it14:37
ltomasbook, I'll take a look asap14:37
apuimedoirenab: we do want to move to use it14:37
apuimedoirenab: we have to propose it for openstack/requirements if we see it as likely to be maintained14:37
irenabapuimedo: +114:37
irenabI think Magnum team is interested as well14:38
apuimedoirenab: got a contact?14:38
apuimedo(on who's been looking into it in the magnum side)14:38
irenabapuimedo: saw some email on this, can check later14:38
apuimedo#info ltomasbo has been working on port reuse so that we reduce the cost of new pod addition to networks by using ports that were previously freed14:39
apuimedo#link https://review.openstack.org/#/c/426687/14:39
apuimedoirenab: thanks irena!14:39
ltomasboyes, but that is just initial work14:39
ltomasboI will update the blueprint with a more detailed information14:39
irenabapuimedo: http://lists.openstack.org/pipermail/openstack-dev/2017-January/111021.html14:40
apuimedo#link http://lists.openstack.org/pipermail/openstack-dev/2017-January/111021.html14:40
ltomasboand also push some changes to cover some of the TO DOs14:40
irenabltomasbo: maybe better to update existing or add devref for this optimization14:40
apuimedobasically ltomasbo's patch saves the neutron creation (it still updates the port with the name of the port to ease troubleshooting), but the ovs binding needs to happen due to the veths getting destroyed when K8s bombs the infra container14:40
apuimedoltomasbo: did you try what happens in OVS native mode if you use an internal port for the pod instead of a veth?14:41
apuimedoirenab: ltomasbo: what do you think about a different devref about resource management?14:41
apuimedoor is it better to use the same?14:41
irenab+114:41
irenabbetter separate14:42
ltomasboapuimedo, I didn't try that14:42
apuimedo(I'd probably use a different one and I'd link it from the original one)14:42
apuimedoltomasbo: don't let me distract you then :P14:42
ltomasboapuimedo, resource management for the ports pool?14:42
apuimedo#action ltomasbo to push a basic resource management devref. Maybe even an etherpad or public gdocs14:43
ltomasbothink it makes sense, yes14:43
irenabltomasbo: I would suggest to maintain pors per project id to be ready to extend for multi-tenance14:43
apuimedoltomasbo: resource management in general, you take the first part "Port resources"14:43
apuimedo:-)14:43
apuimedoirenab: we'll have to account for policy too :P14:44
apuimedobut we'll see about that when we get there14:44
apuimedowith the name update we can probably update the sg14:44
apuimedothe tenancy may need a separate grouping14:44
apuimedoivc_: any news on services?14:44
ltomasbomaybe we can just have different pools for different tenants14:45
ltomasboand security groups14:45
apuimedoCould you use some help with the UTs?14:45
irenabltomasbo: sounds good14:45
*** hongbin has joined #openstack-meeting-414:45
hongbino/14:45
apuimedoltomasbo: for tenants I'd say yes, for SGs let's see if it's not more trouble than it is worth14:45
apuimedohongbin: you should be at a party!14:45
irenabsorry, need to leave14:45
hongbinapuimedo: :)14:45
apuimedowe already updated on fuxi :P14:45
apuimedoirenab: thanks for joining!14:46
hongbinapuimedo: sure. thx14:46
*** karthiks has joined #openstack-meeting-414:46
*** sdake has joined #openstack-meeting-414:46
apuimedohongbin: we agreed to send an email to the ML about fuxi-kubernetes14:46
hongbinapuimedo: sure thing14:46
apuimedowe wondered if the work couldn't be done in kuryr-kubernetes14:46
apuimedosince it's about adding handlers and drivers14:46
apuimedoand it could then share the controller code14:47
hongbini am open for the community input14:47
apuimedobut it needs further discussion14:47
hongbinsure14:47
apuimedohongbin: also, Gideon was asking about the kuryr magnum integration. I wonder if you could put some email on the ML about the missing pieces so people can sign up for them14:48
apuimedo(asking you since you are the most magnum knowledgeable guy we have :P )14:48
hongbinapuimedo: about libnetwork or kubernetes?14:48
hongbinapuimedo: sure, i will try that14:49
apuimedohongbin: both :-)14:49
hongbinapuimedo: ack14:49
apuimedothanks a lot hongbin!14:49
hongbinapuimedo: np14:49
apuimedoand thanks for joining even on holidays14:49
apuimedo#topic general discussion14:49
*** openstack changes topic to "general discussion (Meeting topic: kuryr)"14:49
apuimedoDoes anybody else have a topic to bring up?14:50
janonymousyes14:50
alraddarlaQuestion: We use Contrail at AT&T....have you all started any integration with Contrail? If yes, ca we help? If no, are you itnerested?14:50
alraddarlatypos...it's definitely Monday morning for me14:50
apuimedoalraddarla: we have not started and of course we are interested!14:51
apuimedoalraddarla: for kuryr-libnetwork, kuryr-kubernetes or both?14:51
alraddarlakuryr-kubernetes....potentially both eventually14:52
apuimedovery well14:52
apuimedoin that case, let's go over it now on #openstack-kuryr14:52
apuimedo:-)14:52
apuimedo(after the meeting)14:52
apuimedoAnything else?14:53
ltomasboI sent this a week ago or so14:53
*** rbak_ has joined #openstack-meeting-414:54
janonymousapuimedo: It would be great if 28th Feb meeting could be scheduled in the end if possible.14:54
*** sdake_ has joined #openstack-meeting-414:54
ltomasboI sent this a week ago or so https://review.openstack.org/#/c/42264114:54
*** reedip_ has joined #openstack-meeting-414:54
apuimedojanonymous: you mean the virtual team gathering?14:54
janonymousyeah, But that is upto community completely ,i would suggest 1,2,3 march14:55
apuimedoltomasbo: it seems you are blocked on unit tests14:55
apuimedo:P14:55
ltomasbothere is no unit test for any seg_driver14:55
apuimedojanonymous: please, send the date change proposal as a reply to the mailing list thread I send on teh virtual team gatehring so otehr people can weigh in14:55
*** bobh has joined #openstack-meeting-414:56
apuimedoltomasbo: hence the 'add' of irena14:56
apuimedo:P14:56
janonymousapuimedo: sure,thanks14:56
apuimedoShe doesn't mean modify, but add a new one :P14:56
apuimedoyou can do it as follow-up14:56
apuimedovery well, closing time https://www.youtube.com/watch?v=7-0lV5qs1Qw14:57
*** sdake has quit IRC14:57
apuimedoThank you all for joining!14:57
apuimedo#endmeeting14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:57
openstackMeeting ended Mon Jan 30 14:57:55 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-01-30-14.01.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-01-30-14.01.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-01-30-14.01.log.html14:57
*** alraddarla has left #openstack-meeting-414:58
*** pc_m has left #openstack-meeting-414:58
*** ivc_ has left #openstack-meeting-414:59
jimbaker#startmeeting craton15:00
openstackMeeting started Mon Jan 30 15:00:25 2017 UTC and is due to finish in 60 minutes.  The chair is jimbaker. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: craton)"15:00
openstackThe meeting name has been set to 'craton'15:00
sigmaviruso/15:00
jimbaker#chair sigmavirus sulo jimbaker15:00
openstackCurrent chairs: jimbaker sigmavirus sulo15:00
thomasemo/15:00
jimbaker#link https://etherpad.openstack.org/p/craton-meetings15:00
jimbaker#topic Roll Call15:01
*** openstack changes topic to "Roll Call (Meeting topic: craton)"15:01
jimbakero/15:01
thomasemo/15:01
*** git-harry has joined #openstack-meeting-415:01
jimbakersigmavirus, as usual please be today's chair15:02
sigmavirussure15:02
*** rainya has joined #openstack-meeting-415:03
sigmavirus#topic Action Items from the Last Meeting15:03
*** openstack changes topic to "Action Items from the Last Meeting (Meeting topic: craton)"15:03
sigmavirus#link http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-19-17.03.html15:03
sigmavirus#info there were no action items15:03
sigmavirusoh wait15:03
sigmavirusthat's two weeks ago15:03
sigmavirushold please15:03
*** yfauser has joined #openstack-meeting-415:03
*** TxGirlGeek has joined #openstack-meeting-415:03
jimbakerhttp://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-23-15.00.html15:04
sigmavirus#link http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-23-15.00.html15:04
sigmavirus#info We don't have an agenda for this week15:04
jimbakerso standing agenda please15:04
sigmavirus#info It looks as though jimbaker completed his action item15:04
sigmavirus#topic Stand-up15:05
*** openstack changes topic to "Stand-up (Meeting topic: craton)"15:05
*** garyloug has left #openstack-meeting-415:05
sigmavirus#info I'll go round-robin and collect each person's stand-up finishing with myself. Please let us know when you're done with your stand-up items15:05
sigmavirus#topic Stand-Up :: sulo15:05
*** openstack changes topic to "Stand-Up :: sulo (Meeting topic: craton)"15:05
suloso my functional tests are up for review15:06
suloi am currently working on networks, network-devices and network-interfaces cli commands15:06
sulowill prolly look/work at misc stuff for demo this week15:06
sulodone15:06
sigmavirus#topic Stand-Up :: jimbaker15:07
*** openstack changes topic to "Stand-Up :: jimbaker (Meeting topic: craton)"15:07
*** yfauser has quit IRC15:08
jimbakeri got some initial code working for python client and CLI support of setting/getting variables. we just discussed over in #craton and  <resource>-get/set-vars is probably the ergonomics for this for the CLI15:08
jimbakerexample: cat baz.json | craton host-set-vars 8 x=47 y=9915:08
*** nkrinner is now known as nkrinner_afk15:08
*** julim has joined #openstack-meeting-415:08
jimbaker(sets from baz.json, then adds additional settings x=47, y=99; works well)15:09
jimbakerwill push into WIP this morning15:09
jimbakerand finalize15:09
* sigmavirus holds tongu15:09
jimbakerwill be interested in hearing more from sigmavirus, but later15:09
jimbaker;)15:09
jimbakerso this is in prep for this week's round of demos. that's going to be my main focus, along with onboarding thomasem15:10
jimbakerdone15:10
*** spotz_zzz is now known as spotz15:10
sigmavirus#topic Stand-Up :: thomasem15:10
*** openstack changes topic to "Stand-Up :: thomasem (Meeting topic: craton)"15:10
thomasemfirst day, so getting up-to-speed15:11
thomasemprobably going to be pinging folks, most likely jimbaker regarding dev env setup. I've got craton pulled down and tests are passing and such (first time, too, nice to see it work with a basic python env :)15:11
sigmavirusthomasem: so you're saying "Thank god we don't use Jython"? :P15:12
thomasemGoing to also be looking at reviews, already glanced over the one sulo sent me last week, so some questions may be coming out of that.15:12
thomasemWell, I used to work on other projects, like Nova, Neutron, etc. and those tests never passed locally the first time. Always had to do some magic to get them all working correctly.15:12
jimbakersigmavirus, not today...15:12
sigmavirusthomasem: I'm just teasing jimbaker15:13
thomasemAnyway, small amount of distraction from a previous project tomorrow morning, but other than that just getting my feet wet.15:13
jimbakersigmavirus, :)15:13
thomasemdone15:13
sigmavirus#topic Stand-Up :: rainya15:13
*** openstack changes topic to "Stand-Up :: rainya (Meeting topic: craton)"15:13
* sigmavirus noticed rainya join the meeting :P15:14
rainyasigmavirus, my textual client just signed in :( sorry! not really here15:14
sigmavirusOkay :)15:15
sigmavirusNo need to apologize15:15
sigmavirus#topic Stand-Up :: git-harry15:15
*** openstack changes topic to "Stand-Up :: git-harry (Meeting topic: craton)"15:15
git-harryApart from the usual work keeping up with reviews, I need to finish of a spec I've started with some suggestions on how the variables API could be improved.15:17
jimbakergit-harry, that would be most welcome work15:17
*** armax has joined #openstack-meeting-415:17
git-harryIt's about 90% there so should be done today or tomorrow. Also noticed a bug in the unit testing that I want to look into.15:18
git-harrydone15:18
sigmavirusI don't see Syed_ or jovon, so I'll skip them15:18
*** baoli has quit IRC15:18
sigmavirusDid I miss anyone else?15:18
sigmavirus(I'll take silence as a no)15:19
sigmavirus#topic Stand-Up :: sigmavirus15:19
*** openstack changes topic to "Stand-Up :: sigmavirus (Meeting topic: craton)"15:19
*** baoli has joined #openstack-meeting-415:19
sigmavirusWrapping up the pagination work - the response bodies have all been modified to include the hypermedia API links15:19
sigmavirusThe links that we include are first, prev, self, and next15:19
sigmavirusWorking on fixing up that testing, adding more testing, etc.15:20
sigmavirusDepending on the order with which they merge, I'll either be updating sulo's patches, or rebasing and updating mine =P15:20
sigmavirusHoping to get to some client reviews today too15:20
sigmavirus#topic Priority Reviews15:21
*** openstack changes topic to "Priority Reviews (Meeting topic: craton)"15:21
jimbakercool15:21
sulohttps://review.openstack.org/#/c/408784/15:21
sulohttps://review.openstack.org/#/c/422564/15:21
sigmavirus#link https://review.openstack.org/#/c/408784/15:21
sigmavirus#link https://review.openstack.org/#/c/422564/15:21
jimbakersulo, thanks, looks like those reviews got fixed15:22
sulohttps://review.openstack.org/#/c/426250/ << jim needs to fix the host delete api first for that to work15:22
sigmavirus#link https://review.openstack.org/#/c/426250/15:22
jimbakersulo, i pushed up some changes on that, works fine except for some problems with a region test (which i hope is addressed in the other reviews)15:22
suloyeah they should all work, i am not sure how the coverage looks15:23
jimbakermaybe missing dependency? but the region test was borken15:23
suloprolly not great, but its a start15:23
jimbakerbroken15:23
jimbakeralthough borken is also good15:23
suloyeah i had bad code pushed for the regions tests15:23
jimbakersulo, anyway, we will revisit and get through15:23
sulofixed that today15:23
jimbakercool15:23
sigmavirusAny other priorities?15:24
sulowell15:24
sulonot priority but i'd apprecitate folks start looking at15:25
sulo#link https://review.openstack.org/#/c/421337/15:25
suloit will open paths for next week15:25
jimbakersulo, yep, owe you that detail15:25
jimbakerand it's likely something we will have thomasem working on as well15:25
jimbakergiven interest in containers15:26
thomasem+115:26
thomasemDefinitely on my agenda. :) I did glance over it yesterday, but would like to get more up-to-speed before taking up a bunch of y'alls time asking questions I could have answered myself.15:27
thomasems/yesterday/last week15:27
sigmavirusShall we move on?15:27
sigmavirus(Silence in this case is acceptance)15:27
sigmavirus#topic Open Discussion15:28
*** openstack changes topic to "Open Discussion (Meeting topic: craton)"15:28
jimbakersigmavirus, indeed it is. i will add that to the standing agenda :)15:28
jimbakerso we have demos tomorrow and thursday15:28
jimbakerdemo #1 will be in our usual vidyo room, at our usual vidyo time15:29
jimbakerso 10a MT to be precise (note we do not use UTC here, because we want to move dev meetings to accommodate changes in DST)15:29
thomasemSo, is there any guides on getting a basic dev env set up? Also, I think I might have a schedule conflict with some of the meetings this week. I will be rearranging my recurring appointments to fit the Craton schedule better.15:30
*** trinaths has joined #openstack-meeting-415:30
thomasemI will be comparing calendars this morning and will let y'all know in #craton about what things I can and cannot attend. By next week, for sure, I will have my schedule re-arranged properly.15:31
sulothomasem: http://craton.readthedocs.io/en/latest/dev/install.html15:31
jimbakerthomasem, ok, hopefully we can work these out. demo #2 is 9a MT on thurs, followed by our usual text #craton meeting at 10a MT15:31
thomasemXD Thanks, sulo!15:31
jimbakeralways good when we doc stuff! :)15:32
thomasemIt really is.15:32
thomasemPerfect. This should get me going!15:32
jimbakersigmavirus, you were holding your tongue earlier about i believe the CLI ergonomics15:32
sulothomasem: actually, not sure the doc covers https://github.com/openstack/craton/blob/master/Dockerfile#L14 in dev setup15:32
*** erikmwilson has quit IRC15:33
sulobut thats prolly much easier than doing all the installs etc15:33
*** erikmwilson has joined #openstack-meeting-415:33
jimbakerso one example $ cat baz.json | craton host-set-vars 9 x=47 y=99; craton host-get-vars --format=json 9 ;15:33
thomasemAhhh, well I believe in myself. I'll see how far I get and ask questions if I get stuck.,15:33
sigmavirusjimbaker: yeah, so the reality is that cat'ing a json file and providing params on the cli at the same time looks absolutely awful15:33
jimbakersulo, yeah that's an essential piece to know15:33
jimbakerplus all the docker commands to attach a bash shell; or get logs; etc15:34
thomasemDanke shön, sulo15:34
sigmavirusthat means you're looking at stdin and the cli for things and which ones win if x and y are in both?15:34
sigmavirusif baz.json has x=48, y=20 and you set them on the CLI, which gets priority? It's best not to try to guess at this point and to disallow using both15:34
*** janki has quit IRC15:34
jimbakerthomasem: docker logs -f craton-api; docker exec -it craton-api mysql -ucraton -pcraton craton; docker exec -it craton-api bash # for a bash shell, etc15:34
*** trinaths1 has joined #openstack-meeting-415:34
thomasemRight15:34
thomasemThanks15:35
sigmavirusalso, stdin is actually a disaster to try to handle consistently between py2 and py3 as well15:35
thomasemOh?15:35
jimbakersigmavirus, my assumption is that the args passed to the CLI do, vs stdin15:35
jimbakerand i implemented that assumption :)15:35
jimbakerand documented that assumption15:35
*** erikmwilson has quit IRC15:35
sigmavirusjimbaker: you're going to confuse 50% of our users one way or the other15:35
*** erikmwilson has joined #openstack-meeting-415:35
jimbakerCLIs are notorious for this. but if we offer two ways of doing stuff, there are two choices15:36
jimbaker1. allow both, and have an override15:36
jimbaker2. raise an error and say 'choose one, oh user'15:36
sigmavirusjimbaker: there's three ways of doing it now, stdin, cli args, and both15:36
sigmavirus1. still works, but it's two commands instead of one15:36
sigmavirusand that makes explicit what won't be explicit to users unless they carefully read the docs15:36
jimbakersigmavirus, that feels very unlike CLI to me15:37
thomasemIs there a use-case for each of these different ways? Is there a way that covers each of the use-cases? Giving multiple ways of doing things tends to cause maintenance and UX problems.15:37
sigmavirushosts-set-vars < baz.json ; host-set-vars x=48 y=9915:37
jimbakerCLIs generally take a variety of options15:37
sigmavirusthomasem: right, hence why I want to restrict it from 3 to 2 ways15:37
thomasemGotcha15:37
jimbakerok, sigmavirus sounds like you want one command after all15:37
sigmaviruswhere the 3rd way has implicit order and precedence that is made explicit15:37
sigmavirusjimbaker: right, I want a command that will *either* take stdin, or cli args, but not both15:38
jimbakerso you want my #2 option - 2. raise an error and say 'choose one, oh user'15:38
sigmavirusyes15:38
jimbakerperfectly fine15:38
*** trinaths has quit IRC15:38
thomasemI'd be interested in seeing the use-cases for each method.15:39
* thomasem doesn't know enough about what it actually does yet to have an opinion15:40
jimbakerthomasem, so stdin works better with tooling like jq15:40
jimbakerwhere you keep in a json pipeline15:40
thomasemright15:40
thomasemI'm more referring to a user has a goal to accomplish, and they have this tool that does it. Which are they more likely to go for?15:40
jimbakerthomasem, yeah, so the thinking i would have is that there is a very casual use from the CLI - i'm making changes, trying stuff out15:41
jimbakerthen one elaborates with a little pipelining. and then this is further developed as packaged tooling, using the python client15:42
thomasemGoootcha15:42
thomasemOkay, so, yeah. I'm personally fine with both ways. Admittedly, a lot of tools (look at... idk, httpie, for example) stdin and args are both acceptable and both are handy at different times.15:43
thomasemSo, it's worth the maintenance cost.15:43
jimbakerso if someone says - but that takes multiple steps, doesn't cache, etc, if from CLI... well we are not going to work on making the CLI performant like that15:43
thomasemGotcha15:44
sigmavirusthomasem: stdin is specifically used for data you don't want httpie to structure though15:44
sigmavirus(I kind of help Jakob support that tool)15:44
thomasemHaha, nice15:44
sigmavirusstructure/modify15:44
thomasemThat's a good point and how I've used it several times.15:44
jimbakerso i think the point here is that sigmavirus has been down this path before...15:44
jimbakerand really wants to avoid some pains15:44
thomasemGotcha15:45
sigmavirusI've taken far too many paths15:45
sigmavirusMy feet are weary15:45
jimbakerwhen all we wanted is just an easy to use CLI, and a sign pointing to the python client for heavy usage :)15:45
jimbakerso +1 on this, much as we did in not combining with <resource>-show15:46
jimbakereven though it's the same underlying code15:46
thomasemCool. Thanks for the explanation.15:48
jimbakerinstead let's do the colorization, command completion support, and all the other bells and whistles ;) ok, maybe not. at least not for this week15:48
thomasemHaha15:49
jimbakeranything else?15:49
sigmavirusjimbaker: uh, cli shell completion is a gnarly topic in openstack with downstream redistributors15:50
sigmavirusalso they aren't easily shippable in Python anyway because some tools restrict who can write what files to where15:50
sigmavirusso that's stuff I think might be better left until someone actually desperately asks for it =P15:50
jimbakerwhich they won't. good15:50
sigmavirusThey may well ask for it15:51
sigmavirusBut we'll have no good way of shipping it to them besides them grabbing it out of an sdist or the repo15:51
sigmavirusI know of many ways to really annoy downstream redistributors ;)15:51
*** spzala has joined #openstack-meeting-415:51
jimbakersigmavirus, i can only imagine15:51
sigmavirusI've nothing else for the meeting15:52
jimbakercool, i think we are done15:52
thomasemCheers!15:52
sigmavirus#endmeeting15:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:53
openstackMeeting ended Mon Jan 30 15:53:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-30-15.00.html15:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-30-15.00.txt15:53
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-30-15.00.log.html15:53
*** git-harry has left #openstack-meeting-415:53
*** iyamahat has joined #openstack-meeting-416:04
*** bobmel has quit IRC16:04
*** chandanc_ has joined #openstack-meeting-416:05
*** sdake_ has quit IRC16:06
*** sdake has joined #openstack-meeting-416:08
*** yfauser has joined #openstack-meeting-416:09
*** dandruta has joined #openstack-meeting-416:10
*** armax_ has joined #openstack-meeting-416:16
*** armax has quit IRC16:17
*** armax_ is now known as armax16:17
*** unicell has quit IRC16:18
*** baoli has quit IRC16:19
*** yamahata has joined #openstack-meeting-416:23
*** Julien-zte has joined #openstack-meeting-416:29
*** Julien-zte has quit IRC16:34
*** spzala has quit IRC16:34
*** spzala has joined #openstack-meeting-416:35
*** tonytan4ever has joined #openstack-meeting-416:36
*** baoli has joined #openstack-meeting-416:36
*** armax has quit IRC16:36
*** baoli has quit IRC16:37
*** woodard has quit IRC16:38
*** spzala has quit IRC16:40
*** Syed__ has joined #openstack-meeting-416:46
*** baoli has joined #openstack-meeting-416:47
*** sdake_ has joined #openstack-meeting-416:49
*** sdake has quit IRC16:53
*** trinaths1 has quit IRC16:54
*** bnemec has quit IRC16:56
*** matrohon has quit IRC16:59
*** baoli has quit IRC16:59
*** bobmel has joined #openstack-meeting-417:00
*** anilvenkata has quit IRC17:01
*** bnemec has joined #openstack-meeting-417:01
*** sdake has joined #openstack-meeting-417:06
*** Swami has joined #openstack-meeting-417:06
*** sdake_ has quit IRC17:09
*** julim has quit IRC17:10
*** mjturek has joined #openstack-meeting-417:12
*** baoli has joined #openstack-meeting-417:15
*** oanson has quit IRC17:15
*** oanson has joined #openstack-meeting-417:17
*** barmaley has quit IRC17:17
*** woodard has joined #openstack-meeting-417:18
*** jose-phillips has joined #openstack-meeting-417:19
*** yamahata has quit IRC17:20
*** tonytan4ever has quit IRC17:25
*** tonytan4ever has joined #openstack-meeting-417:26
*** woodard_ has joined #openstack-meeting-417:29
*** woodard has quit IRC17:29
*** chandanc_ has quit IRC17:31
*** Gideon has quit IRC17:32
*** yfauser has quit IRC17:34
*** bobmel has quit IRC17:35
*** bobmel has joined #openstack-meeting-417:36
*** yfauser has joined #openstack-meeting-417:40
*** yfauser has quit IRC17:45
*** reedip_ has left #openstack-meeting-417:46
*** baoli has quit IRC17:58
*** rbak_ has quit IRC17:58
*** baoli has joined #openstack-meeting-417:59
*** tonytan4ever has quit IRC18:02
*** armax has joined #openstack-meeting-418:02
*** harlowja has joined #openstack-meeting-418:02
*** ralonsoh has quit IRC18:02
*** tonytan4ever has joined #openstack-meeting-418:03
*** alexchadin has joined #openstack-meeting-418:03
*** _ody has joined #openstack-meeting-418:03
*** yamahata has joined #openstack-meeting-418:10
*** jwagner_lunch is now known as jwagner18:11
*** unicell has joined #openstack-meeting-418:15
*** dandruta has quit IRC18:16
*** spzala has joined #openstack-meeting-418:24
*** adisky_ has quit IRC18:29
*** Sukhdev has joined #openstack-meeting-418:37
*** mohankumar_ has quit IRC18:40
*** alexchadin has quit IRC18:43
*** tonytan4ever has quit IRC18:43
*** tonytan4ever has joined #openstack-meeting-418:45
*** julim has joined #openstack-meeting-418:46
*** jovon has joined #openstack-meeting-418:48
*** MeganR has joined #openstack-meeting-418:48
*** neiljerram has quit IRC18:49
*** galstrom_zzz is now known as galstrom19:02
*** vishnoianil has quit IRC19:14
*** bobmel has quit IRC19:19
*** anilvenkata has joined #openstack-meeting-419:20
*** matrohon has joined #openstack-meeting-419:20
*** yfauser has joined #openstack-meeting-419:23
*** vishnoianil has joined #openstack-meeting-419:26
*** sdake has quit IRC19:32
*** spzala has quit IRC19:37
*** mjturek has quit IRC19:44
*** matrohon has quit IRC19:47
*** sdake has joined #openstack-meeting-419:48
*** rainya has quit IRC19:50
*** s3wong has joined #openstack-meeting-420:01
*** TxGirlGeek has quit IRC20:02
*** mjturek has joined #openstack-meeting-420:05
*** Julien-zte has joined #openstack-meeting-420:06
*** Julien-zte has quit IRC20:10
*** tonytan4ever has quit IRC20:20
*** tonytan4ever has joined #openstack-meeting-420:21
*** TxGirlGeek has joined #openstack-meeting-420:22
*** jose-phillips has quit IRC20:23
*** baoli has quit IRC20:25
*** sambetts is now known as sambetts|afk20:25
*** sdague_ has joined #openstack-meeting-420:25
*** baoli has joined #openstack-meeting-420:26
*** baoli has quit IRC20:27
*** jose-phillips has joined #openstack-meeting-420:29
*** anilvenkata has quit IRC20:32
*** rbak_ has joined #openstack-meeting-420:34
*** baoli has joined #openstack-meeting-420:36
*** marst has joined #openstack-meeting-420:44
*** Rockyg has joined #openstack-meeting-420:51
*** mjturek has quit IRC20:52
*** yfauser has quit IRC21:01
*** yfauser has joined #openstack-meeting-421:01
*** AndyU has joined #openstack-meeting-421:03
*** AndyU has left #openstack-meeting-421:04
*** tonytan_brb has joined #openstack-meeting-421:05
*** tonytan4ever has quit IRC21:05
*** yfauser has quit IRC21:06
*** sdake has quit IRC21:06
*** sdake has joined #openstack-meeting-421:07
*** mjturek has joined #openstack-meeting-421:10
*** jwagner is now known as jwagner_lunch21:12
*** dtardivel has quit IRC21:14
*** sdague_ has quit IRC21:22
*** cleong has quit IRC21:27
*** Jeffrey4l__ has joined #openstack-meeting-421:34
*** Jeffrey4l_ has quit IRC21:35
*** woodard_ has quit IRC21:37
*** woodard has joined #openstack-meeting-421:38
*** sdague has quit IRC21:38
*** jose-phillips has quit IRC21:41
*** atuly_ has quit IRC21:41
*** rtheis has joined #openstack-meeting-421:43
*** rtheis has quit IRC21:43
*** baoli has quit IRC21:46
*** jose-phillips has joined #openstack-meeting-421:47
*** atuly_ has joined #openstack-meeting-421:57
*** armax has quit IRC21:57
*** baoli has joined #openstack-meeting-421:58
*** armax has joined #openstack-meeting-421:59
*** MeganR has quit IRC22:00
*** woodard_ has joined #openstack-meeting-422:01
*** yamamoto has joined #openstack-meeting-422:03
*** woodard has quit IRC22:05
*** woodard_ has quit IRC22:05
*** tonytan_brb has quit IRC22:10
*** jose-phillips has quit IRC22:17
*** vishnoianil has quit IRC22:19
*** jose-phillips has joined #openstack-meeting-422:19
*** jovon has quit IRC22:20
*** unicell has quit IRC22:27
*** vishnoianil has joined #openstack-meeting-422:30
*** thorst_ has quit IRC22:36
*** unicell has joined #openstack-meeting-422:39
*** baoli has quit IRC22:40
*** armax has quit IRC22:49
*** armax has joined #openstack-meeting-422:51
*** woodard has joined #openstack-meeting-422:53
*** marst has quit IRC22:53
*** woodard has quit IRC22:53
*** woodard has joined #openstack-meeting-422:54
*** Swami_ has joined #openstack-meeting-422:56
*** Swami has quit IRC22:56
*** Swami_ has quit IRC23:00
*** unicell has quit IRC23:05
*** thorst_ has joined #openstack-meeting-423:06
*** TxGirlGeek has quit IRC23:07
*** sdake has quit IRC23:09
*** bobh has quit IRC23:10
*** thorst_ has quit IRC23:10
*** jrist has quit IRC23:13
*** unicell has joined #openstack-meeting-423:14
*** jrist has joined #openstack-meeting-423:28
*** armax has quit IRC23:29
*** armax has joined #openstack-meeting-423:30
*** armax has quit IRC23:31
*** Swami_ has joined #openstack-meeting-423:33
*** Swami has joined #openstack-meeting-423:33
*** Swami__ has joined #openstack-meeting-423:33
*** TxGirlGeek has joined #openstack-meeting-423:35
*** TxGirlGeek has quit IRC23:38
*** armax has joined #openstack-meeting-423:39
*** woodard has quit IRC23:48
*** sdake has joined #openstack-meeting-423:50
*** Swami_ has quit IRC23:52
*** Swami has quit IRC23:52
*** Swami has joined #openstack-meeting-423:54
*** baoli has joined #openstack-meeting-423:55
*** sshnaidm is now known as sshnaidm|off23:57

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!