Wednesday, 2017-02-01

*** amotoki has joined #openstack-meeting-400:04
*** sshnaidm is now known as sshnaidm|off00:04
*** lihi has quit IRC00:06
*** dimak has quit IRC00:06
*** dimak has joined #openstack-meeting-400:07
*** lihi has joined #openstack-meeting-400:07
*** limao_ has quit IRC00:10
*** dims_ has joined #openstack-meeting-400:10
*** bobmel has joined #openstack-meeting-400:11
*** dims has quit IRC00:11
*** limao has joined #openstack-meeting-400:11
*** pmesserli has quit IRC00:13
*** hongbin has quit IRC00:14
*** rainya_ has quit IRC00:14
*** Julien-zte has joined #openstack-meeting-400:16
*** limao_ has joined #openstack-meeting-400:21
*** limao has quit IRC00:22
*** limao_ has quit IRC00:26
*** limao has joined #openstack-meeting-400:26
*** mugsie has quit IRC00:29
*** kylek3h has joined #openstack-meeting-400:36
*** zhurong has joined #openstack-meeting-400:41
*** zhurong has quit IRC00:44
*** jose-phillips has quit IRC00:45
*** yamahata has quit IRC00:48
*** sdake has quit IRC00:50
*** sdake has joined #openstack-meeting-400:52
*** rainya has joined #openstack-meeting-400:54
*** Swami has quit IRC01:01
*** limao has quit IRC01:08
*** limao has joined #openstack-meeting-401:08
*** iyamahat has quit IRC01:13
*** baoli has joined #openstack-meeting-401:24
*** Syed__ has quit IRC01:25
*** yfauser has joined #openstack-meeting-401:28
*** yfauser has quit IRC01:32
*** rainya has quit IRC01:41
*** limao has quit IRC01:44
*** limao_ has joined #openstack-meeting-401:45
*** woodard_ has joined #openstack-meeting-401:51
*** woodard has quit IRC01:51
*** unicell has quit IRC01:52
*** rfolco has joined #openstack-meeting-401:58
*** rfolco has quit IRC01:58
*** revon has quit IRC02:03
*** baoli has quit IRC02:15
*** baoli has joined #openstack-meeting-402:15
*** Sukhdev has quit IRC02:16
*** yfauser has joined #openstack-meeting-402:26
*** Julien-z_ has joined #openstack-meeting-402:32
*** yfauser has quit IRC02:33
*** Julien-zte has quit IRC02:34
*** limao_ has quit IRC02:36
*** Julien-z_ has quit IRC02:40
*** bobh has joined #openstack-meeting-402:49
*** bobh has quit IRC02:49
*** bobh has joined #openstack-meeting-402:50
*** limao has joined #openstack-meeting-402:52
*** woodard_ has quit IRC02:57
*** galstrom_zzz is now known as galstrom02:58
*** woodard has joined #openstack-meeting-402:58
*** bobh has quit IRC03:01
*** woodard has quit IRC03:03
*** limao has quit IRC03:04
*** armax has quit IRC03:05
*** vishnoianil has quit IRC03:14
*** yfauser has joined #openstack-meeting-403:23
*** yfauser has quit IRC03:29
*** ricolin has joined #openstack-meeting-403:49
*** bobh has joined #openstack-meeting-403:51
*** sdake has quit IRC03:53
*** bobh has quit IRC03:57
*** baoli has quit IRC03:58
*** thorst_ has quit IRC04:00
*** psachin has joined #openstack-meeting-404:03
*** cartik has joined #openstack-meeting-404:07
*** yfauser has joined #openstack-meeting-404:25
*** armax has joined #openstack-meeting-404:27
*** yfauser has quit IRC04:30
*** sdake has joined #openstack-meeting-404:45
*** iyamahat has joined #openstack-meeting-404:45
*** thorst_ has joined #openstack-meeting-405:00
*** jamespage has quit IRC05:00
*** janki has joined #openstack-meeting-405:01
*** jamespage has joined #openstack-meeting-405:01
*** galstrom is now known as galstrom_zzz05:01
*** thorst_ has quit IRC05:04
*** yamahata has joined #openstack-meeting-405:05
*** sdake_ has joined #openstack-meeting-405:05
*** sdake has quit IRC05:05
*** Sukhdev has joined #openstack-meeting-405:14
*** dave-mccowan has quit IRC05:18
*** dave-mccowan has joined #openstack-meeting-405:22
*** yfauser has joined #openstack-meeting-405:26
*** thorst_ has joined #openstack-meeting-405:31
*** yfauser has quit IRC05:31
*** thorst_ has quit IRC05:35
*** Rockyg has quit IRC05:52
*** ricolin has quit IRC05:54
*** Sukhdev has quit IRC05:57
*** trinaths has joined #openstack-meeting-405:58
*** dave-mcc_ has joined #openstack-meeting-405:59
*** barmaley has joined #openstack-meeting-406:00
*** dave-mccowan has quit IRC06:01
*** sdake_ is now known as sdake06:16
*** armax has quit IRC06:35
*** nkrinner_afk is now known as nkrinner06:44
*** unicell has joined #openstack-meeting-406:52
*** unicell has quit IRC06:55
*** unicell has joined #openstack-meeting-406:59
*** qwebirc80662 has joined #openstack-meeting-407:08
*** qwebirc80662 has quit IRC07:08
*** usman has joined #openstack-meeting-407:08
*** vishnoianil has joined #openstack-meeting-407:17
*** pcaruana has joined #openstack-meeting-407:19
*** yfauser has joined #openstack-meeting-407:21
*** yamamoto has quit IRC07:25
*** yfauser has quit IRC07:25
*** thorst_ has joined #openstack-meeting-407:31
*** thorst_ has quit IRC07:36
*** unicell1 has joined #openstack-meeting-407:38
*** unicell has quit IRC07:39
*** yifei_ has quit IRC07:47
*** cartik has quit IRC07:53
*** adisky_ has joined #openstack-meeting-407:54
*** ifat_afek has joined #openstack-meeting-407:54
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Feb  1 08:00:19 2017 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: vitrage)"08:00
openstackThe meeting name has been set to 'vitrage'08:00
*** idan_hefetz has joined #openstack-meeting-408:00
idan_hefetzhi08:00
*** eyalb has joined #openstack-meeting-408:00
eyalb\o08:00
ifat_afekhi everyone!08:01
*** danoffek has joined #openstack-meeting-408:01
danoffekHi guys08:01
*** Alon has joined #openstack-meeting-408:04
ifat_afekToday’s agenda:08:04
ifat_afek•Ocata Release08:04
ifat_afek•Status and Updates08:04
ifat_afek•Pike Design sessions08:04
ifat_afek•Boston CFP08:04
ifat_afek#topic Ocata Release08:05
*** openstack changes topic to "Ocata Release (Meeting topic: vitrage)"08:05
ifat_afekLast week I tagged vitrage modules:08:05
ifat_afekvitrage 1.4.008:06
ifat_afekpython-vitrageclient 1.1.008:06
ifat_afekvitrage-dashboard 1.1.008:06
ifat_afekFor each module, I incremented the minor release number. A major release should be incremented only in case we break an API, which we didn’t (We modified the format of the static datasource, but in Ocata we are still supporting the old format).08:06
ifat_afekYesterday I added release notes for all the important features we had in Ocata. Please go over my changes and make sure I didn’t miss anything important:08:06
ifat_afek#link https://review.openstack.org/#/c/427311/08:06
ifat_afek#link https://review.openstack.org/#/c/427130/08:07
ifat_afek#link https://review.openstack.org/#/c/427121/08:07
ifat_afekTomorrow I’m going to tag Vitrage release candidate, and ask to create stable/ocata branches08:07
ifat_afekAfter that, we will be able to push to Ocata only bug fixes. The master will be used for Pike development08:07
*** elisha_r has joined #openstack-meeting-408:08
ifat_afekThe full Ocata schedule can be found here:08:08
ifat_afek#link https://releases.openstack.org/ocata/schedule.html08:08
ifat_afekAny comments regarding the release process?08:08
AlonHi Vitrage people :)08:08
ifat_afek#topic Status and Updates08:09
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:09
ifat_afekI sent you the new Giraffe illustration I got, but only a few responded. I assume it means the Giraffe is ok08:09
ifat_afek;-)08:09
ifat_afekMy updates: I was mostly busy with release issues and with Boston CFPs.08:10
ifat_afekI did not progress with Doctor. I still need to modify Doctor’s test script so that it will test Vitrage in a similar way to the Congress test.08:10
ifat_afekOther tasks I have for Doctor – document how Vitrage can be manually installed in OPNFV environment, and also backport the new “event post API” to Newton… as OPNFV D-release is based on OpenStack Newton.08:11
ifat_afekAnother issue is regarding Aodh. As you might have noticed, we are in continuous discussions with them about the Aodh-Vitrage integration08:11
ifat_afekI don’t have anything to add, but if you are interested then follow the mails in this subject08:11
ifat_afekWho else wants to update?08:11
eyalbi will update08:12
eyalbspec file for vitrage was merged in rdo08:12
ifat_afekcool!!!08:12
eyalbI uploaded also the initial spec file for the vitrage-dashboard08:13
eyalbstill need to work on it08:13
eyalbI still need to update the rdo.yaml for newton and ocata08:13
eyalbit fails now08:13
ifat_afekWhat is the rdo.yaml?08:13
eyalbit a yaml files that describe the version supported08:14
eyalbit was under review for vitrage08:14
ifat_afekOcata is not supported yet. We will branch tomorrow08:14
*** ralonsoh has joined #openstack-meeting-408:14
eyalbI changed it to support ocata and newton08:15
ifat_afekGreat08:15
eyalbthats all08:15
ifat_afekI think we might be able to start and progress with the TripleO installation and Apex08:15
ifat_afekAt least for Doctor tests scripts, they do not need the vitrage-dashboard08:16
eyalbI hope so :-)08:16
ifat_afekAnd the installer is very important for them08:16
ifat_afekThese are great news08:16
eyalbI finished the collectd and pushed the code08:16
eyalbstill waiting to be merged because of a gate problem08:17
ifat_afekUpdating on behalf of alexey_weyl, who can not join now: he is trying to fix the gate problem now. The problem is that we stopped getting notifications from Cinder08:18
idan_hefetzmy update08:18
idan_hefetzI pushed some changes to the processor, allowing for interchangeable graph class for the entity graph08:19
idan_hefetz#link https://review.openstack.org/#/c/425592/08:19
idan_hefetz#link https://review.openstack.org/#/c/423976/08:19
idan_hefetzThis will allow for future additions of graph driver implementations supporting different databases.08:19
idan_hefetzNew configuration in the conf - entity_graph/graph_driver can be used, default (and currently only option) is networkx.08:19
idan_hefetzTo add more options, use the setup.cfg file and specify the desired class.08:19
ifat_afekidan_hefetz: This is great. Hopefully we will add an alternative graph database, which is persistent, in Pike08:20
ifat_afekAnyone else wants to update?08:20
AlonI have an update...08:21
AlonI pushed 2 days ago fix for the entities graph to show an updated alarm08:23
AlonAnd we had a critical issue, that the UI wasn't functional. That was because of Horizon updated their Angular-UI botstrap xstatic package.08:24
AlonI fixed it also08:24
AlonThat's all08:24
*** dave-mcc_ has quit IRC08:24
ifat_afekAlon: thanks08:24
ifat_afekAnyone else?08:24
ifat_afek#topic Pike Design Sessions08:26
*** openstack changes topic to "Pike Design Sessions (Meeting topic: vitrage)"08:26
ifat_afekWe will hold Pike Design Sessions in Israel, on the week of March 6th. You are all invited to participate and to suggest topics for the discussions08:26
ifat_afekPer ZTE request, we will hold some of the design sessions in hours that are suitable for China, so some of our colleagues from ZTE can participate remotely. It means that the design sessions will be not only on March 6th-7th, but also on Marth 8th-9th around 7:00-9:30 UTC08:26
ifat_afekThe design session etherpad:08:27
ifat_afek#link https://etherpad.openstack.org/p/vitrage-pike-design-sessions08:27
ifat_afekAny comments regarding the design sessions?08:27
ifat_afek#topic Boston CFP08:28
*** openstack changes topic to "Boston CFP (Meeting topic: vitrage)"08:28
ifat_afekBoston CFP is still open until February 6th08:28
*** alexchadin has joined #openstack-meeting-408:28
ifat_afek#link https://www.openstack.org/summit/boston-2017/call-for-presentations/08:29
ifat_afek#link https://etherpad.openstack.org/p/vitrage-boston-session-proposals08:29
ifat_afekIf you have other ideas, you can still suggest them08:29
ifat_afekAny other issues you would like to discuss?08:29
ifat_afekSee you next week :-)08:31
danoffekbye08:31
*** danoffek has left #openstack-meeting-408:31
idan_hefetzthanks, bye08:31
ifat_afek#endmeeting08:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:31
openstackMeeting ended Wed Feb  1 08:31:52 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-02-01-08.00.html08:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-02-01-08.00.txt08:31
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-02-01-08.00.log.html08:31
*** eyalb has left #openstack-meeting-408:34
*** ifat_afek has left #openstack-meeting-408:35
*** yamahata has quit IRC08:39
*** iyamahat has quit IRC08:40
*** iberezovskiy|off is now known as iberezovskiy08:43
*** jchhatbar has joined #openstack-meeting-408:46
*** bobmel has quit IRC08:47
*** janki has quit IRC08:48
*** amotoki has quit IRC08:49
*** unicell1 has quit IRC08:50
*** tmetsch has joined #openstack-meeting-409:03
*** tmetsch has left #openstack-meeting-409:04
*** vishnoianil has quit IRC09:14
*** yfauser has joined #openstack-meeting-409:15
*** Alon has quit IRC09:15
*** yfauser has quit IRC09:19
*** cartik has joined #openstack-meeting-409:21
*** cartik_ has joined #openstack-meeting-409:25
*** cartik has quit IRC09:25
*** vishnoianil has joined #openstack-meeting-409:27
*** amotoki has joined #openstack-meeting-409:30
*** thorst_ has joined #openstack-meeting-409:32
*** atuly has joined #openstack-meeting-409:37
*** thorst_ has quit IRC09:38
*** amotoki has quit IRC09:38
*** ricolin has joined #openstack-meeting-409:41
*** hrw has quit IRC09:41
*** hrw has joined #openstack-meeting-409:43
*** amotoki has joined #openstack-meeting-409:45
*** amotoki has quit IRC09:47
*** amotoki has joined #openstack-meeting-409:50
*** bobmel has joined #openstack-meeting-410:03
*** sshnaidm|off is now known as sshnaidm|afk10:05
*** yfauser has joined #openstack-meeting-410:12
*** yfauser has quit IRC10:17
*** sshnaidm|afk is now known as sshnaidm10:25
*** pbourke has quit IRC10:33
*** pbourke has joined #openstack-meeting-410:33
*** thorst_ has joined #openstack-meeting-410:34
*** atuly has quit IRC10:36
*** thorst_ has quit IRC10:39
*** rfolco has joined #openstack-meeting-410:39
*** bobmel_ has joined #openstack-meeting-410:57
*** bobmel has quit IRC10:59
*** bobmel_ has quit IRC11:08
*** yfauser has joined #openstack-meeting-411:09
*** yfauser has quit IRC11:14
*** amotoki has quit IRC11:18
*** alexchadin has quit IRC11:22
*** alexchadin has joined #openstack-meeting-411:22
*** alexchadin has quit IRC11:22
*** alexchadin has joined #openstack-meeting-411:23
*** alexchadin has quit IRC11:23
*** alexchadin has joined #openstack-meeting-411:24
*** alexchadin has quit IRC11:24
*** alexchadin has joined #openstack-meeting-411:24
*** alexchadin has quit IRC11:25
*** alexchadin has joined #openstack-meeting-411:25
*** alexchadin has quit IRC11:26
*** alexchadin has joined #openstack-meeting-411:26
*** alexchadin has quit IRC11:26
*** sdague has joined #openstack-meeting-411:28
*** alexchadin has joined #openstack-meeting-411:49
*** atuly has joined #openstack-meeting-411:51
*** usman has quit IRC12:00
*** v1k0d3n has quit IRC12:02
*** sgordon has joined #openstack-meeting-412:08
*** cdelatte has joined #openstack-meeting-412:11
*** alexchadin has quit IRC12:18
*** mohankumar_ has joined #openstack-meeting-412:18
*** trinaths has quit IRC12:28
*** mohankumar_ has quit IRC12:31
*** jchhatbar_ has joined #openstack-meeting-412:31
*** jchhatbar has quit IRC12:34
*** idan_hefetz has quit IRC12:39
*** atuly has quit IRC12:43
*** thorst_ has joined #openstack-meeting-412:45
*** julim has quit IRC12:54
*** alexchadin has joined #openstack-meeting-412:57
*** bobh has joined #openstack-meeting-413:00
*** bobh has quit IRC13:00
*** bobh has joined #openstack-meeting-413:00
*** elisha_r has quit IRC13:01
*** dtardivel has joined #openstack-meeting-413:03
*** sbezverk_ has quit IRC13:03
*** yfauser has joined #openstack-meeting-413:03
*** shasha_t_ has quit IRC13:04
*** cdelatte has quit IRC13:05
*** lei-zh has joined #openstack-meeting-413:05
*** bnemec has quit IRC13:06
*** ralonsoh_ has joined #openstack-meeting-413:07
*** bapalm has quit IRC13:07
*** cdelatte has joined #openstack-meeting-413:07
*** bnemec has joined #openstack-meeting-413:07
*** yfauser has quit IRC13:08
*** ralonsoh has quit IRC13:09
*** mordred has quit IRC13:10
*** ralonsoh_ is now known as ralonsoh13:11
*** shasha_t_ has joined #openstack-meeting-413:11
*** bapalm has joined #openstack-meeting-413:12
*** woodard has joined #openstack-meeting-413:14
*** sbezverk has joined #openstack-meeting-413:15
*** woodard has quit IRC13:18
*** mordred has joined #openstack-meeting-413:18
*** bobh has quit IRC13:18
*** klamath has joined #openstack-meeting-413:20
*** bapalm has quit IRC13:24
*** sbezverk_ has joined #openstack-meeting-413:28
*** sbezverk has quit IRC13:30
*** hemanthm has quit IRC13:34
*** hemanthm has joined #openstack-meeting-413:34
*** limao has joined #openstack-meeting-413:36
*** limao_ has joined #openstack-meeting-413:41
*** limao has quit IRC13:41
*** lei-zh has quit IRC13:45
*** makowals_ has joined #openstack-meeting-413:46
*** woodard has joined #openstack-meeting-413:48
*** v1k0d3n has joined #openstack-meeting-413:48
*** woodard has quit IRC13:49
*** woodard has joined #openstack-meeting-413:49
*** makowals has quit IRC13:49
*** sbezverk has joined #openstack-meeting-413:55
*** sbezverk_ has quit IRC13:56
*** amotoki has joined #openstack-meeting-413:59
*** yfauser has joined #openstack-meeting-414:01
*** pmesserli has joined #openstack-meeting-414:05
*** sp__ has joined #openstack-meeting-414:05
*** yfauser has quit IRC14:05
*** amotoki has quit IRC14:08
*** limao_ has quit IRC14:08
*** cartik_ has quit IRC14:09
*** iyamahat has joined #openstack-meeting-414:09
*** limao has joined #openstack-meeting-414:09
*** limao has quit IRC14:10
*** atuly has joined #openstack-meeting-414:10
*** limao has joined #openstack-meeting-414:10
*** cathrichardson has joined #openstack-meeting-414:12
*** yamahata has joined #openstack-meeting-414:15
*** cathrich_ has joined #openstack-meeting-414:16
*** julim has joined #openstack-meeting-414:16
*** cathrichardson has quit IRC14:17
*** julim has quit IRC14:17
*** julim has joined #openstack-meeting-414:17
*** ramishra has joined #openstack-meeting-414:21
*** rwallner has joined #openstack-meeting-414:21
*** cdelatte has quit IRC14:25
*** revon has joined #openstack-meeting-414:27
*** Swami has joined #openstack-meeting-414:28
*** cathrich_ is now known as cathrichardson14:29
*** cathrichardson has left #openstack-meeting-414:30
*** cleong has joined #openstack-meeting-414:35
*** dave-mccowan has joined #openstack-meeting-414:46
*** julim_ has joined #openstack-meeting-414:47
*** baoli has joined #openstack-meeting-414:47
*** julim has quit IRC14:49
*** limao has quit IRC14:50
*** limao has joined #openstack-meeting-414:50
*** bklei has joined #openstack-meeting-414:51
*** cdelatte has joined #openstack-meeting-414:53
*** therve has joined #openstack-meeting-414:55
*** rwallner has quit IRC14:55
*** atuly has quit IRC14:55
*** ktychkova has joined #openstack-meeting-414:56
*** rbak__ has joined #openstack-meeting-414:59
*** bobh has joined #openstack-meeting-414:59
ramishra#startmeeting heat15:00
openstackMeeting started Wed Feb  1 15:00:13 2017 UTC and is due to finish in 60 minutes.  The chair is ramishra. 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: heat)"15:00
openstackThe meeting name has been set to 'heat'15:00
ramishra#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: heat)"15:00
*** rwallner has joined #openstack-meeting-415:00
ricolino/15:00
bretono/15:00
cwolferho/15:00
ktychkovao/15:01
skraynevo/15:01
therve/o15:01
zanebo/15:02
ramishramy last meeting as PTL:)15:02
zanebtherve: that looks painful15:02
ramishra#topic adding items to agenda15:02
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:02
ramishra#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-02-01_1500_UTC.2915:02
therve:)15:03
ramishra#topic ocata-rc1 status15:03
*** openstack changes topic to "ocata-rc1 status (Meeting topic: heat)"15:03
ramishra#link https://launchpad.net/heat/+milestone/ocata-rc115:03
*** prazumovsky has joined #openstack-meeting-415:03
prazumovskyHi15:04
ramishraAnything we want from these bugs before we tag rc1?15:04
ramishraNone of them look critical to me15:04
therveThey should be marked as such otherwise :)15:05
therveSo yeah I agree15:05
*** iyamahat has quit IRC15:05
ramishraIt would have been good to land https://review.openstack.org/374321 though15:05
*** nilles has joined #openstack-meeting-415:05
zanebbumped https://bugs.launchpad.net/heat/+bug/1625759 to pike-1, since it's a feature15:06
openstackLaunchpad bug 1625759 in heat "Should be able to select external subnet for FloatingIP" [Medium,In progress] - Assigned to Tanvir Talukder (tanvirt16)15:06
ramishramagnum resource renaming thing.15:06
zanebhttps://review.openstack.org/#/c/358106/ should be an easy one, will review after this15:06
ricolinI will be great to land it:)15:06
*** shardy has joined #openstack-meeting-415:07
ramishraok, I'll wait till tomorrow, else move them to pike-115:07
shardyo/15:07
ramishrashardy: hi15:08
skraynevramishra: sounds good.15:08
*** yamahata has quit IRC15:08
skraynevramishra: regarding https://review.openstack.org/374321 is is just renaming?15:08
*** tonytan4ever has joined #openstack-meeting-415:09
ricolinskraynev: For most of the resource logic, yes!15:09
ramishraskraynev: yeah renaming and some property name changes.15:09
skraynevok. I will try to review it :)15:09
ramishraok, then let's move on15:09
skraynevbut of course you may merge it before me :)15:09
ramishra#topic Heat support of Keystone Federated tokens15:09
*** openstack changes topic to "Heat support of Keystone Federated tokens (Meeting topic: heat)"15:09
skraynevit's mine.15:10
bretonhi15:10
bretonFederated tokens don't work in heat now when heat uses trusts15:10
bretonIt happens because when user authenticates in keystone, their groups (which provide roles) are stored only in tokens.15:10
bretonthere are 2 parts of the problem15:10
ramishraskraynev: yeah we see users coming with issues on irc when they use heat with federated keystone15:10
ramishrashardy: do you know how it should work?15:11
breton1. on trust creation. Keystone tries to lookup federated user's roles in the database and fails, because there is no persistent record. It is kinda solvable, we can extract groups from token and lookup the roles.15:11
skraynevramishra: yeah breton tries to describe the root cause :)15:11
breton2. On trust usage. Keystone tries to verify that trustor still has the roles that he is passing. And here it becomes bad. There is no persistent record about the federated user in the database and keystone cannot verify it. From keystone point of view, federated trustor has no roles.15:12
skraynevramishra: looks like we can not use trusts with fernet tokens15:12
shardybreton: so, basically trusts don't work with Federated tokens in general, this isn't actually a heat specific issue?15:12
bretonskraynev: this is not about fernet at all15:12
*** rwallner has quit IRC15:12
bretonthe problem is there from liberty and we ran into it.15:12
bretonskraynev: yes.15:12
bretonoh15:13
bretonshardy: yes15:13
*** shprotby has joined #openstack-meeting-415:13
*** shprotby is now known as shprotby_15:13
bretonI myself work mostly on keystone, but yesterday at the meeting we decided that fixing it in keystone requires a lot of work and some controversial decisions that might create vulnerabilities.15:13
*** shprotby_ is now known as prazum15:13
breton(and still maybe won't work for heat)15:13
*** mugsie has joined #openstack-meeting-415:13
shardybreton: is there some alternative model for delegation available that does work with federation?15:13
bretonso i was wondering, maybe we can do something on Heat side to work around that issue?15:13
*** prazumovsky has quit IRC15:14
*** prazum has joined #openstack-meeting-415:14
*** mohankumar_ has joined #openstack-meeting-415:14
bretonshardy: i can't think of any15:14
*** sigmavirus has quit IRC15:14
shardybreton: what sort of workaround did you have in mind?15:14
shardyit sounds like the problem is on the keystone side, I'm unclear how we can fix it as a consumer of trusts15:14
bretonshardy: none. I was wondering what you can suggest.15:14
*** jwagner_lunch is now known as jwagner15:15
ramishraprobably a good topic at PTG along with keystone folks?15:15
shardybreton: Hmm, I'm not sure what to suggest, heat uses trusts, and keystone broke trusts, I can't think of a heat side fix for it but we can certainly think about it :)15:15
shardyramishra: yeah that's a good idea, and gives us all some time to look into the issue further15:15
*** jfpeltier has joined #openstack-meeting-415:16
zanebshardy: remind me why we care about the roles?15:16
shardybreton: thanks for raising this, will you be at the PTG?15:16
*** sshnaidm is now known as sshnaidm|afk15:16
bretonshardy: yes, i will, mostly around keystone table probably15:16
shardyzaneb: because trusts require you to specify the roles which are delegated15:16
shardyboth when creating the trust, and when consuming it15:16
*** prazumovsky has joined #openstack-meeting-415:17
zanebcan _we_ store that info when we create the trust?15:17
ricolinbreton: maybe we can add new session15:17
*** jfpeltier has left #openstack-meeting-415:17
ricolin#link https://etherpad.openstack.org/p/heat-pike-ptg-sessions15:17
*** cyberik has joined #openstack-meeting-415:17
shardyzaneb: yes we can, but isn't the problem that keystone doesn't know about it, so it can't validate the list of roles?15:17
zanebah, ok15:18
bretonshardy: right15:18
zanebbreton: I don't see how that's fixable outside of keystone15:18
zanebeven in principle?15:18
skraynevshardy: yes, as I understand keystone can not get any information about roles for users ..15:18
*** makowals_ has quit IRC15:18
shardywhen keystone gives you a trust scoped token, it gives you a token with a list of roles (and user identity) associated with the trust ID15:18
*** hongbin has joined #openstack-meeting-415:19
*** makowals has joined #openstack-meeting-415:19
bretonmaybe heat could do things as `heat` user with admin roles?15:19
bretoninstead of imitating the user15:19
zanebbreton: NO15:19
shardybreton: No, because then when you e.g do autoscaling the new VMs wouldn't be owned by the users15:19
shardyimagine the billing and security implications for a second ;)15:19
bretonok, i was just wondering :)15:20
bretoni have little idea how heat things work :)15:20
shardybreton: the other alternative (which heat already supports) is to use the "password" option for delegated auth, but then we store user passwords, which may change, in the heat DB15:20
shardywhich is bad15:20
zanebbad bad bad15:20
shardybreton: well, honestly the problem seems to be keystone broke trusts for everyone15:20
*** prazum has quit IRC15:21
bretonshardy: you are right15:21
shardyso I'm not clear what heat can do, except maybe plan to find another way to do this in the long term15:21
zanebbreton: if you can offer us OAuth2 or something instead then we can work with that15:21
shardybreaking stuff without deprecation is pretty uncool tho :(15:21
bretonshardy: we never broke it15:21
*** woodard has quit IRC15:21
bretonshardy: federation + trusts never worked :p15:21
ramishrashardy: did they break it?15:21
ramishrayeah it never worked15:21
shardyzaneb: Yeah I was going to say oauth, but last time I looked you can't create delegations without a finite expiry15:22
shardybreton: my point is you implemented a feature which broke trusts15:22
zanebbreton: if you're telling us that only human people physically sitting in front of a keyboard can use OpenStack APIs then you need to have another think about what OpenStack is :)15:22
shardyor at least is incompatible with it15:22
shardyso a heat side workaround doesn't help that much, as I assume there are other users with the same problem15:22
bretonshardy: come tell that at the PTG15:23
bretonshardy: i 100% support you15:23
shardyanyway, lets try to be constructive, I'm just frustrated that this wasn't considered before it broke us15:23
*** sigmavirus has joined #openstack-meeting-415:23
shardybreton: is keystone planning to deprecate trusts, or find a more general solution?15:24
zanebshardy: I don't know that it broke us so much as the intersection of those 2 features doesn't work15:24
bretonshardy: probably no15:24
zanebwhich imho makes federation fairly useless15:24
shardyzaneb: yeah my point was just it's an intesection of two keystone features, heat is just a consumer of keystone15:25
*** alexchadin has quit IRC15:25
skraynevzaneb, shardy, breton. wow. guys. let's avoid accusations. the reality is, that it does not work15:26
shardyOk, well sounds like we won't solve this today, let's all think about it and try to figure out a path forward at the PTG15:26
shardybreton: thanks for raising this, be good to discuss further in atlanta15:26
ramishrashardy: yeah, I'll add a PTG session with keystone team15:26
skraynevand we need to communicate with keystone team and explain our point of view. and try to find solution15:26
skraynevramishra: thx ;)15:27
ramishraNot sure if it would be cross-project session or we can just invite keystone guys15:27
zanebramishra: +115:27
ricolinramishra: cross-project+115:27
zanebfwiw there are many other projects using trusts15:27
zanebaodh, mistral come to mind15:27
*** admcleod_ is now known as admcleod15:27
ramishraI think trusts is an important feature for not to work with federation15:28
shardyYeah mistral, heat, sahara, magnum15:28
shardyI think they all use trusts15:28
ramishrashould we move on now?15:29
zanebsounds cross-project-ish15:29
*** fnafty has joined #openstack-meeting-415:29
*** rwallner has joined #openstack-meeting-415:29
skraynevramishra: yeap15:29
ramishra#topic PTG sessions15:29
*** openstack changes topic to "PTG sessions (Meeting topic: heat)"15:29
ricolin#link https://etherpad.openstack.org/p/heat-pike-ptg-sessions15:30
ramishraMay be it's time to add some more topics:)15:30
*** jovon has joined #openstack-meeting-415:30
ricolinthe keystone cross project will be a good topic to add in15:30
ramishrashardy anything tripleo specific we should add?15:31
ricolinwe will figure out which team going to host the session, but will be great to write down first:)15:31
*** prazumovsky has quit IRC15:33
ramishraWe need 2 full days worth topics15:33
ricolinmaybe no fishbow this time?15:33
thervericolin, There is no such thing in the ptg15:33
therveAFAIK15:34
zanebricolin: yeah, there are no fishbowl-style sessions at the PTG15:34
ricolintherve: great!15:34
zanebthose still happen at the Summit15:34
ramishraricolin: we have a room for 2 days, we can do whatever we want15:34
shardyramishra: Nothing specific, but I've been wondering now we added conditions if we'll ever add a way to create repeating groups of resources natively in heat without having to nest them15:34
*** baoli has quit IRC15:34
ramishranot sure how big the rooms would be though15:34
*** limao_ has joined #openstack-meeting-415:34
shardywe said no several times in the past, but tripleo now shows why folks were asking for it15:34
shardyall the j2 loops everywhere15:34
*** armax has joined #openstack-meeting-415:35
shardythat may be a disscussion for the beer-track vs a formal session though15:35
ramishrashardy: beer-track +115:36
*** limao has quit IRC15:36
*** sp__ has quit IRC15:36
ricolin+115:36
ramishraRequest all to spend some time and help finalize the sessions15:36
ramishramoving on..15:37
ramishra#topic Meeting time discuss15:37
*** openstack changes topic to "Meeting time discuss (Meeting topic: heat)"15:37
zanebwould it help to have a list of people who are planning to attend the PTG?15:37
ricolinI would like to propose to move all meeting time schedule to current one15:38
ricolinzaneb: I think foundation have it15:38
ramishrazaneb: we can ask people to add their names to the etherpad if they are attending15:38
zanebricolin: I meant we should just write in the etherpad15:39
ricolinzaneb: Sounds great15:39
*** spzala has joined #openstack-meeting-415:39
zanebe.g. I suggested a session on property translation but I don't know if prazumovsky is going to be there15:39
ricolin#link https://etherpad.openstack.org/p/heat-pike-ptg-sessions15:40
ricolinI add the attendee list in it15:40
zanebthanks15:40
ramishraricolin: we don't have many APAC guys attending the 0800 meeting, so I would be +1 for having them at 1500 every week15:41
ricolinprazumovsky: are you going to attend PTG?:)15:41
zanebre meeting schedule, this time wfm but I don't know about everyone15:41
*** prazumovsky has joined #openstack-meeting-415:42
therveI've been working on making the py3 gate works15:43
ricolinWe can alway have some other meeting or ML for APAC if we have more people would like to join and discuss15:43
therveI think we mostly have issues in the tests now15:43
ramishraMay be ask a few other folks or start a ML thread?15:43
therveWe'll get stuck on swift soon15:43
*** jchhatbar_ has quit IRC15:43
ramishratherve: I had looked at it last week too15:43
ricolinramishra: Sure, I will send the ML out15:43
ramishraI see some issue with cloud-init no?15:43
therveramishra, Yeah haven't looked at that one yet15:44
*** fnafty has quit IRC15:44
*** baoli has joined #openstack-meeting-415:45
ricolinLet's decide through this week, if no much opposition, we will move next week's meeting to 150015:46
ramishratherve: I've moved the apache job now, now that http+wsgi is the default with devstack for api services15:46
*** alexchadin has joined #openstack-meeting-415:46
therveCool15:46
ramishras/moved/removed in this patch https://review.openstack.org/#/c/427696/15:46
*** Swami_ has joined #openstack-meeting-415:47
ramishra#topic open discussion15:48
*** openstack changes topic to "open discussion (Meeting topic: heat)"15:48
ramishraAnything else we would like to discuss?15:48
*** alexchadin has quit IRC15:48
ramishraNext week it would be ricolin the new PTL chairing the meeting:)15:49
ramishraricolin: congrats!15:49
zanebcongrats ricolin :)15:49
ricolinThanks guys:)15:49
shardycongrats ricolin :)15:49
ricolinI will try my best to be a mediator:)15:50
*** Swami has quit IRC15:50
ricolinAnd we have a bunch of pre-PTL around!15:50
*** mandre has joined #openstack-meeting-415:51
*** Sukhdev has joined #openstack-meeting-415:51
*** mliima_ has joined #openstack-meeting-415:51
ricolineverything will be great:)15:52
ramishraok then, if there is nothing else....15:52
ramishrathank you all for joining15:53
ramishra#endmeeting15:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:53
openstackMeeting ended Wed Feb  1 15:53:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-02-01-15.00.html15:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-02-01-15.00.txt15:53
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-02-01-15.00.log.html15:53
*** therve has left #openstack-meeting-415:54
*** duonghq has joined #openstack-meeting-415:54
*** inc0 has joined #openstack-meeting-415:54
*** egonzalez has joined #openstack-meeting-415:54
*** sp__ has joined #openstack-meeting-415:56
*** SridharP has joined #openstack-meeting-415:57
*** mgiles has joined #openstack-meeting-415:58
*** rwallner has quit IRC15:59
*** zhubingbing has joined #openstack-meeting-415:59
*** gema has joined #openstack-meeting-415:59
inc0#startmeeting kolla16:00
openstackMeeting started Wed Feb  1 16:00:18 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: kolla)"16:00
openstackThe meeting name has been set to 'kolla'16:00
*** vhosakot has joined #openstack-meeting-416:00
inc0#topic rollcall - w00t please16:00
*** openstack changes topic to "rollcall - w00t please (Meeting topic: kolla)"16:00
duonghqwoot o/16:00
gemao/16:00
inc0you know what to do;)16:00
egonzalezwoot o/16:00
sp__woot o/16:00
vhosakoto/   (sorry I missed the past 3 meetings as I had conflicts with other meeting)16:00
vhosakotw00t16:00
*** zhubingbing__ has joined #openstack-meeting-416:00
zhubingbing__o/16:01
pbourkew00t16:01
Jeffrey4l_o/16:01
inc0vhosakot, no problem, glad to have you back16:01
zhubingbing__o/16:01
*** rwallner has joined #openstack-meeting-416:01
vhosakotthanks inc0 :)16:01
*** rwallner has quit IRC16:01
*** sayantani01 has joined #openstack-meeting-416:01
SamYapleo/16:01
sayantani01Woot16:01
*** rwallner has joined #openstack-meeting-416:02
inc0#topic announcements16:02
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:02
*** rwallner has quit IRC16:02
*** nilles has left #openstack-meeting-416:02
*** rwallner has joined #openstack-meeting-416:02
inc01. ocata-3 was tagged, now we're in feature freeze and stabilizing our release16:02
inc0please everyone focus on testing deploy and upgrades16:03
zhubingbing__ok16:03
inc0our release is early march16:03
qwango/16:03
hrwo/16:03
sp__ohhk16:03
inc0any community announcements?16:03
mliima_\o16:03
inc0guess not16:03
inc0#topic ptg schedule16:04
*** openstack changes topic to "ptg schedule (Meeting topic: kolla)"16:04
SamYapleim getting fiber16:04
*** jascott1 has joined #openstack-meeting-416:04
SamYaplethats my announcement16:04
inc0congrats SamYaple16:04
duonghqnice SamYaple16:04
pbourkeseed boxes available from SamYaple16:04
*** zhubingbing has quit IRC16:04
SamYaplestarting at $250 a month16:04
inc0soo we need to plan for PTG16:04
pbourkecontact him by phone directly, his hours are between 1am and 3am16:04
inc0we are left with full authority how we want to split the sessions16:05
inc0we have room and 2 days16:05
inc0so we can have usual 45-15min session/break16:05
inc0or change it in any direction16:05
sdakeo/16:05
inc0#link https://etherpad.openstack.org/p/kolla-ocata-ptg this is our session list16:06
*** ramishra has quit IRC16:06
krtayloro/16:06
inc0#link https://etherpad.openstack.org/p/kolla-pike-ptg-schedule lets put actual schedule here16:06
*** srwilkers has joined #openstack-meeting-416:06
sdakeinc0 i like the 40 minut esessiosn with 10 or20 minutes breaks16:07
sdakekeeps people fresh16:07
sdakedo you know the hours of the ptg so we can make a rough schedule of the times and then sort out what goees where enxt?16:07
inc0I'm not sure how lunch will look like so we probably just push sessions in time of lunch16:08
hrwand enough time to discuss after talk + manage to get to next one16:08
inc0I'll figure that one out16:08
*** ramishra has joined #openstack-meeting-416:08
sdakehey hrw16:08
sdakethanks for getting that answered inc016:08
inc0sdake, we can start/end however we want afaik16:08
inc0hrw, well, all our talks are in same room16:08
sdakeinc0 I know we can manage our own schedule I wasn't sure if the facilities at a start or end time16:08
hrwinc0: ;)16:08
inc0we just get a room16:08
sdakeright- although if we don't set a strict schedule we will overrun topics16:09
inc0and if you want to move to different room, I can't promise that our sessions will be in sync16:09
*** klindgren has joined #openstack-meeting-416:09
* hrw is not going to PTG16:09
sdakeand some topics will get less time while others will get more16:09
inc0sdake, I asked ttx and he's not sure either, but that's a hotel so I don't expect to have too much problems either way16:09
*** bklei has quit IRC16:09
gemanot sure where exactly to add the ARM64 topic16:09
gemaunder deliverable?16:09
inc0not like we want to stay for hours16:09
inc0into night16:09
sdakeinc0 cool - so 9am-5pm then?16:09
sdakegema we are not to that point in our agenda yet :)16:10
gemasdake: lol, ok16:10
inc0sdake, how about we plan for 8 sessions a day and I'll figure out hours when we get lunch info and stuff?16:10
*** marst has joined #openstack-meeting-416:10
gemaI was looking at the PTG list of topics :D16:10
sdakegema im not sure if that is on the agenda -a t present we are talking about ptg agenda16:10
sdakeinc0 cool16:10
sdakeinc0 we can adjust from there16:10
sdakeicn0 before making the final schedule are we going to vote or make up the voting or what on the sessionss we wnt to have16:11
inc0gema, frankly I'd keep arm out of full ptg agenda, unless you feel it's 40min worth of talking16:11
sdake(not beinga pita, just want to understnad how we transfer the  first etherpad to the second)16:11
*** sayantan_ has joined #openstack-meeting-416:11
gemainc0: probably won't need 40 mins, I will grab you all one by one at coffee time and ask questions, you are right :D16:11
inc0I'd like to have plenty of time for random open convos there16:11
hrwinc0: do s/arm64/all-non-x86-archs/ and it makes sense16:12
*** trinaths has joined #openstack-meeting-416:12
*** penfold has joined #openstack-meeting-416:12
inc0hrw, well, yes and no, it will be same thing with more. Once we'll figure out how to add arm16:12
inc0with gema16:12
hrwinc0: there is ppc64le patch for kolla already in review. I have ppc64le+aarch64 one based on review one16:12
inc0we can add stuff like that later too16:12
sdakewe have 16 time slots, lets select which of the 15 we want16:13
sdake16 rather16:13
inc0we'll talk about this, I promise, just can't promise we'll make full fledged session out of it16:13
inc0schedule is pretty tight as it is;)16:13
sdakei am going to ordered number the first etherpad only for counting purposes16:14
inc0I'd like to have split between kolla + kolla-ansible / kolla-k8s in about 50:50 if you agree16:14
sdakegema add to end of the ptg schedule in the firstetherpad so we can see how many sessions we have16:14
*** trinaths1 has joined #openstack-meeting-416:14
inc0that will put our stable deliverables at a bit of disadvantage, but I just feel we need more design time for k8s16:15
*** limao_ has quit IRC16:15
gemathe first etherpad being the ocata one?16:15
inc0gema, yeah, I messed up naming:P16:15
sdakeyou mean 50% for kolla+kolla-ansible and 50% for kolla-k8s?16:15
*** sayantani01 has quit IRC16:15
inc0yes16:16
inc0we can do 1 day for k8s and 1 day for ansible16:16
inc0+ docker16:16
*** ramishra has left #openstack-meeting-416:16
*** trinaths has quit IRC16:16
inc0so people with only one interesest can work their schedule better16:16
inc0although I'd expect most people from kolla-k8s to be interested in at least kolla images;)16:16
inc0thoughts guys? agree? disagree?16:17
gema+116:17
sdakeagreed inc016:17
*** prazumovsky has quit IRC16:17
egonzalez+116:18
*** Serlex has joined #openstack-meeting-416:18
srwilkers+116:18
sdakeok - so we have 29 sessions planned and 18 slots16:18
inc0ok, so let's make Monday kolla-k8s and Tue kolla-ansible16:18
zhubingbing__+116:18
sdakewe either need to select out 11 sessions or select in 18 :)16:18
sp__+116:18
inc0since cross-project will be more interested in latter16:18
sdakesome of these may be duplicates as well16:19
sdakeinc0 i liked thevoting you did in the past on the session interest16:19
sdakeinc0 although we can't wait 2 weeks for results, woudl you be willing to set that up with a short timer?16:19
*** hieulq has joined #openstack-meeting-416:19
sdakeinc0 the oting i used as ptl was pretty terrible :)16:19
sdakeotingvoting16:20
inc0well, I'm not too sure about that, I'd like kolla-k8s community to decide what is important for them16:20
inc0rather than open voting16:20
gemaare they not here?16:20
inc0and kolla+kolla-ansible doesn't have that many sessions proposed16:20
sdakeok so next step then given that thinking is to divide the sessions between kolla-ansible and kolla-kubernetes16:20
sdakeso we have a full count of which deliverable should vote(?) on which sessions and what our capacity looks like16:21
sdakesorry little slow  - just woke up16:21
inc09 sessions in kolla-k8s16:22
inc0I'm not going to make vote just to cast out one:P16:22
*** yamahata has joined #openstack-meeting-416:23
inc0anyway, sdake since I don't think we have quorum for kolla-k8s sessions right now, let's focus on day 216:24
inc0so we have 20 sessions proposed total, not all of them I think are valid16:24
sdakeinc0 cool if there are only 9 sessions on kolla-k8s we cna sort that out eaisly16:25
inc0some can be squashed to one session16:25
sdakethe other 19 sessiosn need to fit into 8 slots then?16:25
inc0yeah, but if we need to refactor it16:26
inc0so let's make 15min timeslot and try to squash/limit number of choices16:26
inc0as some of sessions aren't described in any way and such16:27
inc0let's work on that till 8:45 please16:27
inc0don't delete, crossline16:27
sdakeinc0 sounds good - woud lyou mind moving the k8s sessions to one location and the ansible session to another location16:27
*** Syed__ has joined #openstack-meeting-416:27
sdakeI thnk the kolla deliverable sessions are cross-project for kolla so we can share timeslots there16:28
*** zhubingbing__ has quit IRC16:28
sdakeinc0 or is it already organized that way16:28
srwilkersis this the kolla-ptg-pike etherpad, or did i miss a link earlier at the start?16:29
inc0I found at least one duplicate16:30
inc0no, srwilkers https://etherpad.openstack.org/p/kolla-ocata-ptg <- lets' work on this one16:30
*** wwriverrat has joined #openstack-meeting-416:30
*** vhosakot has quit IRC16:31
*** vhosakot has joined #openstack-meeting-416:32
berendto/16:35
*** tonytan4ever has quit IRC16:36
*** tonytan4ever has joined #openstack-meeting-416:36
inc0sooo....the way I see it16:40
sdakeok made a cross-through  chane to 516:40
sdakeabout the language process16:40
sdakeplease discuss with yoru flame suits on :)16:40
sdakeinc0 just trying to shed non-essential topics if possible16:40
*** bpattewar has joined #openstack-meeting-416:41
*** Rockyg has joined #openstack-meeting-416:41
jascott1is after hours BOF a thing?16:41
inc0yeah, so way I see it, I'd add docs session, separation of deliverables session and all of kolla-ansible and kolla16:41
inc0that makes it 1016:42
inc0so we'd need to drop 2 or maybe canibalize one session from Monday, or have a 9-session days16:42
*** woodard has joined #openstack-meeting-416:42
inc0we can have few 20min ones and few 40min ones16:42
inc0like docs, important topic but we didnt consume full 40min last time16:43
*** spzala has quit IRC16:43
inc0or do just that, put a sessions in waitlist and if we feel we've finished topic, we can just jump to waitlisted one16:43
*** spzala has joined #openstack-meeting-416:44
sdakeinc0 the docs session could go in the community area16:44
sdake9 session days with a little less breaks sounds good16:44
sdakedoes the math work out there?16:44
inc0we don't really have 'community' area:P16:44
* portdirect agile mumble mumble16:45
sdakeinc0 #1, #2 on the ehterpad16:45
sdakeat the top16:45
inc0I mean time-wise16:46
sdakestarts line 2316:46
sdakeinc0 i got it16:46
sdakei mean put it in that bucket16:46
inc0unless we use first day for it16:46
inc0but again, I want to give lot of time to k8s16:46
sdakeso docs can be added to line 2316:46
sdakedoccs are important to koll-kubernetes and kolla-ansible, we could spend some time on that I think as a larger project16:47
sdakerather group of people16:47
* sdake can't form sentences today16:47
sdake3 hours of sleep will do that to ya16:47
inc0ok, executive order, since these are popular lately16:47
gemalol16:47
inc0let's put docs and separation to Monday16:47
inc0as both are closely related to k8s16:47
sdakezomg - exedcutive orders need to go in the us :)16:47
inc0especially separation16:48
vhosakotteam, I'd like to contribute to one of the k8s bp's.  I'm chekcing https://launchpad.net/kolla-kubernetes/+milestone/0.5.0 and will pick a bp.  I'm deploying kolla-k8s now and will ask questions in IRC if I have any questions :)16:48
sdakeinc0 ok that sounds reasonable - rather then an executive order its more like a general agreement :)16:48
sdakevhosakot we are sorting out the ptg16:48
*** spzala has quit IRC16:48
inc0but that wouldn't allow me to make a political joke16:48
sdakepolitics and religion :)16:48
sdakevhosakot can we discuss that after the meeting or in the opens16:49
gemainc0: we may have to do the meetings at the airport for all we know ;)16:49
inc0so if we put these 2 to Monday16:49
inc0we can put all the remaining kolla+kolla-ansible to tuesda16:49
inc0y16:49
sdakeinc0 can you move the two around your talkingabout the tema can see it16:49
*** sshnaidm|afk is now known as sshnaidm16:49
inc0let me write draft of schedule and you can see what I mean16:50
*** spzala has joined #openstack-meeting-416:50
vhosakotsdake: sure, thanks sdake16:50
*** woodard has quit IRC16:50
*** joedborg has joined #openstack-meeting-416:50
*** woodard has joined #openstack-meeting-416:50
inc0there ya go.16:52
inc0#link https://etherpad.openstack.org/p/kolla-pike-ptg-schedule16:52
*** joedborg has quit IRC16:52
inc0ok, we're running out of time16:53
sdakeinc0 looking good there!16:53
*** joedborg has joined #openstack-meeting-416:53
inc0let's pick it up next week16:53
sdakei htink we need ot figure out the 6 slots for kolla-kubernetes16:53
sdakeinc0 sounds good16:53
inc0#topic Open Discussion16:53
*** openstack changes topic to "Open Discussion (Meeting topic: kolla)"16:53
inc0let's have at least few minutes for it16:53
sdakegema up next?16:53
sdakeor vhosakot ?16:54
gemahttps://blueprints.launchpad.net/kolla/+spec/multiarch-and-arm64-containers16:54
gemajust wanted to share that and ask for reviews/comments16:54
*** joedborg has quit IRC16:54
hrwI have to make some arm64 images locally and then get kolla working on it16:54
gemaI am sure I am missing stuff we need to do16:54
*** spzala has quit IRC16:54
vhosakotsure sdake  yeah, I've playing with minikube, so, just wanted to contribute to kolla-k8s and help finish some important bp's for the team16:54
*** joedborg has joined #openstack-meeting-416:54
sdakegema i arbitrarly changed the priority to high16:54
gemasdake: thanks!16:54
sdakechanged to discussion - which alllows peopel to discuss it16:55
inc0vhosakot, so currently best think you can do is to help sdake prepare devenv;)16:55
gemasdake: we'll treat it as such anyway16:55
sp__https://blueprints.launchpad.net/kolla/+spec/coverage-increment-for-kolla     implementation completed need review16:55
hrw 4 files changed, 45 insertions(+), 1 deletion(-)16:55
inc0amirite?16:55
hrwthat's whole ppc64le+arm64 base support ;D16:55
*** FrankZhang has quit IRC16:55
sdakegema right - the priority typicallly matches the priority of the contributors16:55
egonzalezhrw: cool16:55
sdakeand i got impression you had a high priority for it16:55
gemasounds good16:55
vhosakotinc0: sure, is that a kolla-k8s devenv?16:55
gemasdake: yep16:55
inc0hrw, and you wanted 40min to discuss it?:P16:55
sdakegema work items need more detail - i'll leave a note in the discussion16:55
hrwegonzalez: used hacksaw on ppc64le one ;D16:55
gemasdake: great, thanks16:55
*** rwallner has quit IRC16:55
hrwinc0: haha16:56
vhosakotI'll ask questions in the main channel.. thanks for the help!16:56
sdakeinc0 did you aprove that with kolla-drivers?16:56
gemainc0: he won't even be there, it'll be yibo and myself16:56
sdakeinc0 or was that someone else16:56
sp__sdake: please review for the BP     https://blueprints.launchpad.net/kolla/+spec/coverage-increment-for-kolla16:56
inc0no worries, but it seems like pretty straightforward thing16:56
sdakesp__ anyone can review blueprints :)16:56
sdakesp__ that blueprint is in needs code review state16:57
sp__sdake: thanks will ask someone16:57
*** spzala has joined #openstack-meeting-416:57
sdakesp__ so I think you are ready to go from a core reviewer POV16:57
inc0sdake, I can't remember who approved it, but I would16:57
sp__sdake: yes16:57
sdakeinc0 use kolla-drivers from now on?16:57
sdakeinc0 the downside of thatis then we dont know who to blame for who approved  a blueprint :)16:58
inc0it is kolla-drivers now right?16:58
inc0anyway we're out of time16:58
sdakeyes16:58
inc0thank you all from coming16:58
inc0#endmeeting Kolla16:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Wed Feb  1 16:58:44 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-02-01-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-02-01-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-02-01-16.00.log.html16:58
hrwthx16:58
*** jascott1 has left #openstack-meeting-416:59
*** gema has left #openstack-meeting-416:59
*** mgiles has left #openstack-meeting-416:59
*** mliima_ has left #openstack-meeting-416:59
*** bpattewar has quit IRC16:59
*** hrw has left #openstack-meeting-417:00
*** psachin has quit IRC17:01
*** rwallner has joined #openstack-meeting-417:02
*** egonzalez has quit IRC17:04
*** spzala has quit IRC17:06
*** inc0 has quit IRC17:07
*** spzala has joined #openstack-meeting-417:08
*** mandre has left #openstack-meeting-417:08
*** Swami_ has quit IRC17:08
*** spzala has quit IRC17:12
*** vhosakot has quit IRC17:13
*** nkrinner is now known as nkrinner_afk17:14
*** SridharP has quit IRC17:14
*** sbezverk has quit IRC17:15
*** sbezverk has joined #openstack-meeting-417:16
*** hieulq has quit IRC17:22
*** hieulq has joined #openstack-meeting-417:22
*** joedborg has quit IRC17:24
*** hieulq has quit IRC17:26
*** Swami_ has joined #openstack-meeting-417:30
*** kylek3h is now known as kylek3h_away17:34
*** Swami_ has quit IRC17:35
*** inc0 has joined #openstack-meeting-417:38
*** sbezverk has quit IRC17:40
*** sbezverk_ has joined #openstack-meeting-417:40
*** sbezverk has joined #openstack-meeting-417:41
*** Sukhdev has quit IRC17:41
*** rainya has joined #openstack-meeting-417:41
*** spzala has joined #openstack-meeting-417:43
*** trinaths1 has quit IRC17:44
*** sbezverk_ has quit IRC17:45
*** bobh has quit IRC17:46
*** spzala has quit IRC17:47
*** spzala has joined #openstack-meeting-417:49
*** rwallner has quit IRC17:49
*** mohankumar_ has quit IRC17:51
*** cyberik has quit IRC17:52
*** spzala has quit IRC17:54
*** v1k0d3n has quit IRC17:56
*** aarefiev is now known as aarefiev_afk17:57
*** spzala has joined #openstack-meeting-417:57
*** v1k0d3n has joined #openstack-meeting-418:00
*** sdake_ has joined #openstack-meeting-418:01
*** spzala has quit IRC18:02
*** SridharP has joined #openstack-meeting-418:02
*** spzala has joined #openstack-meeting-418:03
*** sdake__ has joined #openstack-meeting-418:03
*** ralonsoh has quit IRC18:04
*** ricolin has quit IRC18:04
*** sdake has quit IRC18:04
*** ricolin has joined #openstack-meeting-418:04
*** harlowja_ has joined #openstack-meeting-418:05
*** sdake_ has quit IRC18:06
*** harlowja has quit IRC18:06
*** spzala has quit IRC18:08
*** jwagner is now known as jwagner_lunch18:10
*** ricolin has quit IRC18:11
*** makowals has quit IRC18:13
*** rwallner has joined #openstack-meeting-418:14
*** makowals has joined #openstack-meeting-418:15
*** spzala has joined #openstack-meeting-418:19
*** jwagner_lunch is now known as jwagner18:22
*** SridharP has quit IRC18:25
*** pcaruana has quit IRC18:28
*** unicell has joined #openstack-meeting-418:32
*** krtaylor has quit IRC18:33
*** sayantan_ has quit IRC18:34
*** yfauser has joined #openstack-meeting-418:34
*** rainya_ has joined #openstack-meeting-418:37
*** barmaley has quit IRC18:40
*** barmaley has joined #openstack-meeting-418:40
*** rainya has quit IRC18:40
*** barmaley has quit IRC18:40
*** wwriverrat_ has joined #openstack-meeting-418:46
*** wwriverrat has quit IRC18:47
*** wwriverrat_ is now known as wwriverrat18:47
*** dharinic is now known as dharinic|lunch18:50
*** spzala has quit IRC18:51
*** spzala has joined #openstack-meeting-418:52
*** rbak__ has quit IRC18:53
*** rbak__ has joined #openstack-meeting-418:54
*** spzala has quit IRC18:56
*** spzala has joined #openstack-meeting-418:58
*** galstrom_zzz is now known as galstrom18:58
*** spzala has quit IRC19:01
*** spzala has joined #openstack-meeting-419:02
*** sdake__ is now known as sdkae19:03
*** sdkae is now known as sdake19:04
*** dtardivel has quit IRC19:04
*** duonghq has quit IRC19:04
*** adisky_ has quit IRC19:09
*** rwallner has quit IRC19:12
*** yamahata has quit IRC19:12
*** Serlex has quit IRC19:12
*** krtaylor has joined #openstack-meeting-419:13
*** rwallner has joined #openstack-meeting-419:14
*** rwallner has quit IRC19:18
*** harlowja_ has quit IRC19:19
*** rwallner has joined #openstack-meeting-419:24
*** krtaylor has quit IRC19:24
*** sambetts is now known as sambetts|afk19:25
*** penfold has quit IRC19:28
*** penfold has joined #openstack-meeting-419:29
*** krtaylor has joined #openstack-meeting-419:31
*** sp__ has quit IRC19:33
*** yfauser has quit IRC19:33
*** yfauser has joined #openstack-meeting-419:34
*** dharinic|lunch is now known as dharinic19:37
*** yfauser has quit IRC19:38
*** Sukhdev has joined #openstack-meeting-419:44
*** tonytan4ever has quit IRC19:44
*** bobh has joined #openstack-meeting-419:47
*** bobh has quit IRC19:52
*** rwallner has quit IRC19:59
*** rainya_ has quit IRC20:00
*** rwallner has joined #openstack-meeting-420:03
*** penfold has quit IRC20:06
*** penfold has joined #openstack-meeting-420:07
*** rwallner has quit IRC20:07
*** Sukhdev has quit IRC20:08
*** jovon has quit IRC20:10
*** iyamahat has joined #openstack-meeting-420:24
*** rainya has joined #openstack-meeting-420:26
*** rainya has quit IRC20:26
*** icey has quit IRC20:37
*** sambetts|afk has quit IRC20:37
*** sambetts_ has joined #openstack-meeting-420:38
*** harlowja has joined #openstack-meeting-420:39
*** icey has joined #openstack-meeting-420:40
*** icey has quit IRC20:40
*** icey has joined #openstack-meeting-420:40
*** icey has quit IRC20:41
*** bobh has joined #openstack-meeting-420:47
*** Sukhdev has joined #openstack-meeting-420:59
*** icey has joined #openstack-meeting-421:04
*** Syed__ has quit IRC21:05
*** jose-phillips has joined #openstack-meeting-421:05
*** armax has quit IRC21:11
*** julim_ has quit IRC21:13
*** srwilkers has quit IRC21:22
*** shardy has quit IRC21:34
*** wwriverrat has left #openstack-meeting-421:34
*** Jeffrey4l_ has quit IRC21:35
*** Jeffrey4l_ has joined #openstack-meeting-421:36
*** Sukhdev_ has joined #openstack-meeting-421:41
*** armax has joined #openstack-meeting-421:54
*** spzala has quit IRC21:55
*** spzala has joined #openstack-meeting-421:58
*** spzala_ has joined #openstack-meeting-422:00
*** spzala has quit IRC22:03
*** spzala_ has quit IRC22:04
*** thorst_ has quit IRC22:09
*** woodard_ has joined #openstack-meeting-422:13
*** cleong has quit IRC22:14
*** thorst_ has joined #openstack-meeting-422:16
*** woodard has quit IRC22:16
*** woodard_ has quit IRC22:17
*** thorst_ has quit IRC22:20
*** bobh has quit IRC22:32
*** thorst_ has joined #openstack-meeting-422:40
*** Syed__ has joined #openstack-meeting-422:41
*** thorst_ has quit IRC22:44
*** rwallner has joined #openstack-meeting-422:47
*** marst has quit IRC22:49
*** rwallner_ has joined #openstack-meeting-422:51
*** rwallner has quit IRC22:52
*** baoli has quit IRC22:54
*** yamahata has joined #openstack-meeting-422:55
*** rwallner_ has quit IRC22:56
*** yamahata has quit IRC23:00
*** yamahata has joined #openstack-meeting-423:01
*** v1k0d3n has quit IRC23:07
*** spzala has joined #openstack-meeting-423:15
*** spzala has quit IRC23:18
*** spzala has joined #openstack-meeting-423:18
*** rwallner has joined #openstack-meeting-423:21
*** rwallner has quit IRC23:21
*** rwallner has joined #openstack-meeting-423:22
*** v1k0d3n has joined #openstack-meeting-423:22
*** yamamoto has joined #openstack-meeting-423:24
*** spzala has quit IRC23:25
*** woodard has joined #openstack-meeting-423:28
*** woodard has quit IRC23:29
*** penfold has quit IRC23:29
*** woodard has joined #openstack-meeting-423:30
*** yfauser has joined #openstack-meeting-423:30
*** klamath has quit IRC23:39
*** v1k0d3n has quit IRC23:41
*** rwallner has quit IRC23:47
*** rwallner has joined #openstack-meeting-423:54
*** sshnaidm is now known as sshnaidm|off23:58
*** galstrom is now known as galstrom_zzz23:59

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