Wednesday, 2017-06-28

*** sshank has quit IRC00:01
*** bobh has joined #openstack-meeting00:03
*** dimtruck is now known as zz_dimtruck00:06
*** gmann has quit IRC00:08
*** gmann has joined #openstack-meeting00:08
*** VW has joined #openstack-meeting00:11
*** unicell has quit IRC00:16
*** jamesmcarthur has joined #openstack-meeting00:19
*** markstur has quit IRC00:24
*** bobh has quit IRC00:28
*** jamesmcarthur has quit IRC00:29
*** abalutoiu has quit IRC00:30
*** abalutoiu has joined #openstack-meeting00:31
*** bobh has joined #openstack-meeting00:31
*** slaweq_ has joined #openstack-meeting00:36
*** salv-orl_ has joined #openstack-meeting00:37
*** wanghao has joined #openstack-meeting00:39
*** artom has quit IRC00:40
*** salv-orlando has quit IRC00:40
*** slaweq_ has quit IRC00:41
*** yangyapeng has joined #openstack-meeting00:46
*** Apoorva_ has joined #openstack-meeting00:48
*** hongbin has joined #openstack-meeting00:49
*** bobh has quit IRC00:50
*** yangyapeng has quit IRC00:50
*** Yipei has joined #openstack-meeting00:52
*** Apoorva has quit IRC00:52
*** Apoorva_ has quit IRC00:53
*** yangyapeng has joined #openstack-meeting00:54
*** annabelleB has quit IRC00:56
*** zhiyuan has joined #openstack-meeting00:57
*** joehuang has joined #openstack-meeting00:57
*** yinxiulin has joined #openstack-meeting00:58
*** Julien-zte has joined #openstack-meeting00:59
*** dongfeng has joined #openstack-meeting00:59
*** hongbin has quit IRC01:00
*** xuzhuang has joined #openstack-meeting01:00
joehuang#startmeeting tricircle01:00
openstackMeeting started Wed Jun 28 01:00:39 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: tricircle)"01:00
openstackThe meeting name has been set to 'tricircle'01:00
joehuang#topic rollcall01:00
*** openstack changes topic to "rollcall (Meeting topic: tricircle)"01:00
joehuang#info joehuang01:01
dongfeng#info dongfeng01:01
Yipei#info Yipei01:01
yinxiulin#info xiulin01:01
zhiyuan#info zhiyuan01:01
xuzhuang#info xuzhuang01:01
*** RonghUI has joined #openstack-meeting01:01
*** markstur has joined #openstack-meeting01:02
joehuang#topic feature implementation review01:02
*** unicell has joined #openstack-meeting01:02
*** openstack changes topic to "feature implementation review (Meeting topic: tricircle)"01:02
joehuanghello, as the pike-3 is approaching01:02
*** fredli__ has joined #openstack-meeting01:02
fredli__good morning01:02
joehuanglet's review the feature wants to land in pike01:02
Yipeifor lbaas, already finish lbaas in one region successfully01:03
*** kevinz has joined #openstack-meeting01:03
*** SerenaFeng has joined #openstack-meeting01:03
joehuanggreat message, yipei01:03
Yipeiplan to configure it again to make sure it is reproducible01:03
joehuangyou mean the LBaaS can work with tricircle now01:03
Yipeiyes, in one region, it works well01:03
joehuangand one central neutron, one local neutron01:04
Yipeii will update spec and prepare for a guide01:04
*** unicell1 has joined #openstack-meeting01:04
joehuanggreat progress, look forward for landing the spec and code update01:04
*** armstrong has quit IRC01:05
joehuang#info LBaaS work in one region scenario where Tricircle is installed01:05
xuzhuangfor async job paginate_query, in first time I use union in query, but can show status of jobs, so now I plan to use dongfeng's paginate_query in core.py01:05
YipeiOK, got it. i will continue with lbaas across multi region in the meantime01:05
*** litao__ has joined #openstack-meeting01:05
*** markstur_ has joined #openstack-meeting01:05
yinxiulinsfc'create and delete can land in pike-301:05
joehuangto xuzhuang, great01:06
joehuangto xiulin, welcome the feature01:06
xuzhuangsorry, using union in query can't show status of jobs, so I plan to use paginate_query now01:06
*** unicell has quit IRC01:06
*** caowei has joined #openstack-meeting01:07
joehuangto yipei, have you registered BP for LBaaS01:07
*** markstur has quit IRC01:07
zhiyuanthe job-log table doesn't have "status" field, since all jobs in that table are considered successful01:07
xuzhuangto zhiyuan,yes so in order to show status of job table, I giving up using union in query01:08
zhiyuani see01:09
dongfengfor routing pagination, I think it can be landed in pike3, the replacement of "cross OpenStack L2 network" can be completed in pike3 too01:09
joehuanggood, will review patches ASAP, but I have to leave tomorrow/Friday, will review next Monday01:10
joehuangto ronghui, how about qos series patches?01:11
dongfengok, thx~01:11
joehuangis xiongqiu online?01:12
RonghUIwill update ASAP01:12
RonghUISeemingly absent01:12
zhiyuanI have posted the newest comment. Two main concerns: (1) try to use driver instead of plugin (2) try not to bring ML2 extension manager to central plugin01:13
zhiyuanfor the qos patches01:13
joehuangyes, qos is high priority feature, hope that it can be merged in pike-301:14
joehuangit has been postponed two milestones01:15
RonghUI we will try best to finish01:16
*** benj_ has joined #openstack-meeting01:17
fredli__RonghUI: please, it is quite important and urgent01:17
RonghUIgot it01:17
joehuangafter pike-3, it'll be difficult to land big feature, we need to test the code, and make sure the quality is good01:17
joehuangso if you miss the pike-3, the feature has to be postponed to next release01:18
zhiyuanudpate not enought frequent, part3 is submitted on Jun 25, failed in all the tests, however, not updated yet01:18
joehuangfine, I am sure ronghui can deal with it01:19
joehuang#topic  Community wide goals, PTG and Sydney summit topics01:20
*** openstack changes topic to "Community wide goals, PTG and Sydney summit topics (Meeting topic: tricircle)"01:20
*** bobh has joined #openstack-meeting01:20
joehuanghello, there are more and more people are trying to use tricircle01:20
joehuangIf you find any topic in the mail-list related to tricircle01:21
joehuangwe can reply and help new committter01:22
*** kaisers__ has joined #openstack-meeting01:22
*** baoli has joined #openstack-meeting01:22
*** csomerville has quit IRC01:22
Yipeiok, got it01:23
joehuanghe/she may seek for help or propose new feature / scenario or implementation discussion01:23
joehuangif more and more people get on board, it'll make tricircle better and better01:23
joehuangif you receive someone send you message in private, you can ask him whether to discuss the topic in mail-list publicly01:24
*** kaisers_ has quit IRC01:25
joehuangif someone send you message in private, you can ask him whether to discuss the topic in mail-list publicly01:25
joehuangthere are lots of enhancement we can do to make it easy for new committer to get on board01:26
dongfengit's fine01:26
xuzhuanggot it01:27
*** cody-somerville has joined #openstack-meeting01:27
joehuangfor community wide goals in pike01:27
joehuangthere are two goals, one is python3 support01:28
joehuangthe other one is Control Plane API endpoints deployment via WSGI01:29
*** yinxiulin has quit IRC01:30
joehuangwe have finished these two goals, need to submit a patch01:30
*** spzala has joined #openstack-meeting01:30
joehuangit should be submitted by PTL, so I'll submit the patch01:31
joehuangone more thing01:31
zhiyuana patch to declare we have done that?01:31
*** yinxiulin has joined #openstack-meeting01:31
joehuangyes, you have to submit a patch to update this page
zhiyuani see01:32
joehuangduring opnfv demo preparation, it's important to import external network to central Neutron if there is already ext-network in local neutron01:33
joehuangit's especially useful if Tricricle will be running in VM or container inside some cloud01:33
*** yamahata has joined #openstack-meeting01:34
joehuangwho can help to provide such an import function?01:34
Yipeii want to have a try01:34
zhiyuandoes this need a spec, to talk about the solution?01:35
joehuangby command like like python db-sync, or admin api, spec is prefered01:35
joehuangit could be short, but good for discussion01:36
*** esberglu has joined #openstack-meeting01:36
*** esberglu has quit IRC01:36
*** esberglu has joined #openstack-meeting01:36
joehuangcode is not complex, how to support such management purpose function is an interesting area01:37
*** slaweq_ has joined #openstack-meeting01:37
joehuangthank you Yipei01:38
Yipeilbaas in one region do not need much code, only one guide, so i would like to try01:38
joehuangyour contribution and guide for LBaaS is very important01:38
joehuangin real production, LBaaS is a must sometimes01:39
joehuangfor PTG and summit, what's your idea and proposal?01:39
*** esberglu has quit IRC01:41
zhiyuansince most of the developers are in China, we can hold PTG in China, if needed, or just discuss online01:42
*** slaweq_ has quit IRC01:42
joehuangwe may have several time slots for the discussion01:43
joehuangone guy from orange is also working on tricircle01:43
*** yamahata has quit IRC01:44
joehuangcurrently he is trying to deploy tricircle01:44
*** bobh has quit IRC01:45
joehuangand some other contributors also express the interest in contribution during OPNFV summit01:45
joehuangso friendly time slot is very important for them to get involved, except mail-list01:46
zhiyuanis our weekly meeting time convenient for them?01:47
joehuangI am not sure yet, if more and more contributors from different time zone, we may rotate the weekly meeting01:48
joehuangso that everyone can work with comfort time slot01:48
joehuangDo you have topics for Sydney summit?01:49
joehuangYou can submit presentation or forum session in Sydney summit01:50
*** rbudden has joined #openstack-meeting01:50
zhiyuanIf nova cellV2 is finished in Pike, we can show a demo about the integration between tricircle and cellv201:51
joehuangit's not urgent, we can continue discuss in next weekly meeting :)01:51
*** bobh has joined #openstack-meeting01:52
joehuangto Zhiyuan, good idea01:53
*** gyee has quit IRC01:53
*** thorst has joined #openstack-meeting01:53
joehuangalso talk with Dan Smith whether to have a session about cells V2 and tricircle01:53
joehuang#topic open discussion01:54
*** openstack changes topic to "open discussion (Meeting topic: tricircle)"01:54
joehuangother topic?01:54
zhiyuanno from me01:54
dongfengno for me01:54
RonghUIno for me01:54
Yipeino from me01:54
xuzhuangno for me01:54
joehuangok, thank you for attending the weekly meeting01:55
*** openstack changes topic to "OpenStack Meetings ||"01:55
openstackMeeting ended Wed Jun 28 01:55:28 2017 UTC.  Information about MeetBot at . (v 0.1.4)01:55
openstackMinutes (text):
joehuangthank you, bye01:55
*** xuzhuang has quit IRC01:56
*** thorst has quit IRC01:57
*** dongfeng has left #openstack-meeting01:58
*** joehuang has left #openstack-meeting02:04
*** youzp has joined #openstack-meeting02:09
*** cody-somerville has quit IRC02:16
*** hongbin has joined #openstack-meeting02:16
*** cody-somerville has joined #openstack-meeting02:22
*** cody-somerville has quit IRC02:22
*** cody-somerville has joined #openstack-meeting02:22
*** bobh has quit IRC02:24
*** shu-mutou-AWAY is now known as shu-mutou02:24
*** bobh has joined #openstack-meeting02:27
*** spzala has quit IRC02:28
*** spzala has joined #openstack-meeting02:28
*** jamesmcarthur has joined #openstack-meeting02:29
*** mrodden has quit IRC02:33
*** jamesmcarthur has quit IRC02:34
*** htruta` has quit IRC02:34
*** raginbajin has quit IRC02:34
*** cmurphy has quit IRC02:34
*** htruta has joined #openstack-meeting02:35
*** knikolla has quit IRC02:35
*** cmurphy has joined #openstack-meeting02:36
*** mrodden has joined #openstack-meeting02:37
*** slaweq_ has joined #openstack-meeting02:38
*** rbudden has quit IRC02:38
*** ubuntu_ has joined #openstack-meeting02:38
*** tonyb_ is now known as tonyb02:40
*** raginbajin has joined #openstack-meeting02:40
*** RonghUI has quit IRC02:41
*** bobh has quit IRC02:43
*** slaweq_ has quit IRC02:43
*** knikolla has joined #openstack-meeting02:43
*** cloudrancher has quit IRC02:46
*** bobh has joined #openstack-meeting02:46
*** cloudrancher has joined #openstack-meeting02:47
*** RonghUI has joined #openstack-meeting02:51
*** csomerville has joined #openstack-meeting02:53
*** ubuntu_ has quit IRC02:54
*** RonghUI has quit IRC02:55
*** cody-somerville has quit IRC02:58
*** Nel1x has quit IRC03:03
*** bswartz has quit IRC03:03
*** caowei_ has joined #openstack-meeting03:04
*** caowei has quit IRC03:07
*** caowei_ is now known as caowei03:07
*** bobh has quit IRC03:08
*** dmacpher has joined #openstack-meeting03:10
*** yinxiulin has quit IRC03:11
*** Yipei has quit IRC03:15
*** baoli has quit IRC03:16
*** wanghao has quit IRC03:17
*** wanghao has joined #openstack-meeting03:18
*** qiang has joined #openstack-meeting03:18
*** trozet has joined #openstack-meeting03:19
*** markstur_ has quit IRC03:19
*** caowei_ has joined #openstack-meeting03:21
*** dbecker has quit IRC03:22
*** unicell has joined #openstack-meeting03:22
*** unicell1 has quit IRC03:23
*** markstur has joined #openstack-meeting03:25
*** caowei has quit IRC03:25
*** caowei_ is now known as caowei03:25
*** dbecker has joined #openstack-meeting03:35
*** xyang1 has quit IRC03:37
*** wanghao has quit IRC03:37
*** VW has quit IRC03:38
*** qiangcao has joined #openstack-meeting03:38
*** wanghao has joined #openstack-meeting03:39
*** slaweq_ has joined #openstack-meeting03:39
*** trozet has quit IRC03:43
*** slaweq_ has quit IRC03:44
qiangcaoHi Everyone, this is Qiang Cao. I’ve been working on policies in the cloud for a while. I’m interested in Congress and related stuff.03:48
*** adisky__ has joined #openstack-meeting03:51
*** julim has quit IRC03:54
*** thorst has joined #openstack-meeting03:54
*** epico has joined #openstack-meeting03:55
*** hongbin has quit IRC03:58
*** SerenaFeng has quit IRC03:59
*** Kevin_Zheng has quit IRC03:59
*** links has joined #openstack-meeting04:00
*** armax has joined #openstack-meeting04:00
*** thorst has quit IRC04:00
*** fredli__ has quit IRC04:01
*** dmacpher has quit IRC04:04
*** vishnoianil has quit IRC04:06
*** Liuqing has joined #openstack-meeting04:12
*** sridhar_ram has joined #openstack-meeting04:12
*** arnewiebalck_ has joined #openstack-meeting04:14
*** qiangcao has quit IRC04:15
*** kaisers__ has quit IRC04:17
*** arnewiebalck_ has quit IRC04:18
*** qiang has quit IRC04:21
*** dmacpher has joined #openstack-meeting04:22
*** artom has joined #openstack-meeting04:27
*** YanXing_an has joined #openstack-meeting04:27
*** tbh_ has joined #openstack-meeting04:29
*** gongysh_ has joined #openstack-meeting04:29
gongysh_#startmeeting tacker04:29
openstackMeeting started Wed Jun 28 04:29:50 2017 UTC and is due to finish in 60 minutes.  The chair is gongysh_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:29
*** openstack changes topic to " (Meeting topic: tacker)"04:29
openstackThe meeting name has been set to 'tacker'04:29
gongysh_#topic roll call04:30
*** openstack changes topic to "roll call (Meeting topic: tacker)"04:30
gongysh_hi, everyone04:30
YanXing_anLiuqing, hello04:30
tbh_Hi all04:30
gongysh_YanXing_an, you have a busy last week, right?04:30
LiuqingYanXing_an ,hi04:30
*** tung_doan has joined #openstack-meeting04:31
YanXing_angongysh, yes, finally fix the CI case, it's a looong work04:31
gongysh_YanXing_an, yes,  it works at last. thanks the CI gate which help us to improve the codes.04:32
gongysh_sridhar_ram, hi, how's the week?04:33
sridhar_ramgongysh_: going on ..04:33
gongysh_sridhar_ram, it never stops the beat!04:33
tung_doansridhar_ram: long time no see :)04:34
sridhar_ramgongysh_: help as much possible w/ the reviews under the circumstances04:34
*** trinaths has joined #openstack-meeting04:34
sridhar_ramunfortunately that the current state of affairs in my end :(04:34
gongysh_#topic bp04:35
*** openstack changes topic to "bp (Meeting topic: tacker)"04:35
gongysh_tung_doan, hi04:35
gongysh_Add auto-healing function for VNFFG04:35
gongysh_I think we should have time for this.04:36
tung_doangongysh_: hi.. I am trying to wrap my bp04:36
gongysh_my concern is the API way for vnfm to nfvo04:36
tung_doangongysh_: I think it just needs some minor changes now04:36
gongysh_sridhar_ram, do you have any comments for the callback method.04:36
*** trinaths has quit IRC04:37
tung_doangongysh_: I prefer using API for this04:37
*** rwsu has quit IRC04:37
sridhar_ramtung_doan: gongysh_: yes, that will break the modularity and the layering04:37
gongysh_tung_doan is using http API, my commented way is to use MESSAGE rpc.04:37
*** noslzzp has quit IRC04:38
sridhar_ramin fact, we should avoid any VNFM -> NFVO call .. both http and rpc04:38
*** diablo_rojo has quit IRC04:39
sridhar_ramcan't NFVO listen for events from VNFM and readjust FFG if needed ?04:39
tung_doangongysh_: sridhar_ram: We also need a generic method for Network Services (NSs). Therefore, I think API is a suitable choice04:39
*** unicell has quit IRC04:39
*** trinaths has joined #openstack-meeting04:40
sridhar_ramwe need to clearly understand the ownership of resources first .. VNF resources are "owned" by VNFM. FFG is "owned" by NFVO04:40
gongysh_sridhar_ram,  even with events: (in fact, RPC or HTTP API is a kind of event) we can not isoloate VNFM and NFVO.04:40
gongysh_sridhar_ram, right04:40
*** unicell has joined #openstack-meeting04:40
sridhar_ramVNFM shouldn't know a VNF is participating in a FFG ..04:41
sridhar_ramall it needs to give are .. low level neutron ports IDs for NFVO to stitch a FFG04:41
tung_doansridhar_ram: alsolutely.04:41
*** spzala has quit IRC04:41
trinathssridhar_ram: +104:42
sridhar_ram.. if that low level ports change .. NFVO needs to be notified so that it can reapply a FFG using newer low level ports04:42
tung_doansridhar_ram: you got the point. That's why we inform vnffgs (NSs), which VNFs belong to04:42
sridhar_ramVNFM shd just emit events out and NFVO shd react04:42
*** spzala has joined #openstack-meeting04:42
sridhar_ramtung_doan: then, can we make this generic .. can VNFM emit "VNF" respawned or altered or scaled event out ..04:43
tung_doansridhar_ram: +204:43
*** qiangcao has joined #openstack-meeting04:43
sridhar_ramtung_doan: NFVO can subscribe to these events and react appropriately04:43
tung_doansridhar_ram: that's totally something I want to do :)04:43
sridhar_ramtung_doan: but there shd be no REST API or RPC calls from VNFM towards NFVO API04:43
*** andreas-f has joined #openstack-meeting04:43
gongysh_what is the event method?04:44
tung_doansridhar_ram: gongysh_: how can we emit events?04:44
sridhar_ramwe don't have the async event publish method implemented yet04:45
gongysh_sridhar_ram,  enssentially, the RPC call, or HTTP API is a kind of event  emit and acceptance. RPC call can be RPC cast, which is asynchronous.04:45
tung_doangongysh_: sridhar_ram: My code locally implemented with API. It looks reasonable04:46
sridhar_ramwe had planned a follow on to which will send the events out ...04:46
sridhar_ramgongysh_: what direction is the HTTP API happens ?04:46
*** spzala has quit IRC04:47
*** kaisers_ has joined #openstack-meeting04:47
sridhar_ramhere is a proposal .. that the most efficient but architecturally the right thing (IMO):04:48
gongysh_one way I think is to differentiate the policy into two level. one level is VNFM,  another is nfvo level.04:48
sridhar_ramhave NFVO poll VNF event list periodically .. if any of the VNFs in the FFG respawned or scaled .. delete and re-apply FFG04:48
tung_doansridhar_ram: my concern is whether it is generic enough to use event/audit functions in place04:48
sridhar_ramtung_doan: why do you think it WON'T be generic?04:49
gongysh_nfvo policy is done on nfvo level, if a vnf is managed by NFVO policy, its own policy is disabled.04:49
*** dmacpher has quit IRC04:49
YanXing_anthe HTTP API is exposed to user, i think it is not a good way, user does not use it04:50
sridhar_ramjust to be clear are we talking about here ?04:50
tung_doansridhar_ram: when we refer to API, we can control request. with event/audit, I cannot imagine how to do04:50
sridhar_ramcall back action from VFNM policy back to NFVO ?04:50
sridhar_ramtung_doan: it is HUGE layer violation for VNFM to call a NFVO API in first place ..04:51
sridhar_ramtung_doan: architecturally that does not make sense ..04:52
*** kaisers_ has quit IRC04:53
YanXing_anIn ETSI NFV MANO, Or-vnfm reference point is used between nfvo and vnfm, supports:04:53
YanXing_anForwarding of events, other state information about the VNF that may impact also the NS instance04:54
sridhar_ramExactly ...04:54
sridhar_ram.. we shd restrict it to events out of VNFM -> NFVO04:54
trinathsYanXing_an: agree04:54
tung_doanYanXing_an: that's right. ETSI said that NSs can get failure events from other functional blocks. It could be from VNFM level04:55
sridhar_ramin fact, the current tacker architecture event envisions a SINGLE NFVO using multiple site-local VNFMs .. we need to preserve that model04:55
gongysh_YanXing_an, sridhar_ram , I think there should allow vnfm to emit event to upper layers.04:55
sridhar_ramgongysh_: we planned a follow for .. to use a pub-sub bus for external entities to receive events from Tacker04:56
sridhar_ramfor now, we can use an internal event queue from VNFM -> NFVO to implement this FFG-HA feature04:57
sridhar_ram.. suggesting this as a way to unblock us for near term04:57
tung_doansridhar_ram: what problem if users they want to do HA functions for VNFFG or even NSs?04:58
gongysh_sridhar_ram,  how about to use rabbit mq for vnfm to emit cast message to a certain queues?04:58
sridhar_ramgongysh_: that would work too ..04:58
sridhar_ramas long as the changes to VNFM are "generic" and not specific04:59
sridhar_ramtung_doan: the user facing functionality is fine .. it is a valid feature and we need to implement it.. "how" is the question here04:59
gongysh_tung_doan, lets use tacker conductor to implement the queue.05:00
tung_doansridhar_ram: that's why I am stil thinking about API support :)05:00
gongysh_vnfm rpc cast, conductor receives it.05:01
sridhar_ramtung_doan: API from VNFM -> NFVO does (reverse) coupling of layers that does not make sense05:01
*** kaisers_ has joined #openstack-meeting05:02
*** dmacpher has joined #openstack-meeting05:02
tung_doansridhar_ram: I mean API support can use for both users and VNFM level. Is it acceptable?05:02
sridhar_ramtung_doan: sorry, what you mean by users here?05:03
gongysh_tung_doan, I don't think is for user05:04
sridhar_ramgongysh_: +105:04
YanXing_angongysh, +105:04
YanXing_anSridhar_ram: Tacker support events on VNF resource, how about nfv subscibe the events? If so, we need define the event carefully05:05
gongysh_so, about for tacker conductor way?05:05
sridhar_ramYanXing_an: that is exactly what I05:05
sridhar_ramYanXing_an: that is exactly what I'm proposing05:05
sridhar_ramgongysh_: for near-term, yes that would work ..05:06
sridhar_rami'm trying to search with success a ppt from a previous tacker midcycle meetup that describes events emitted using a pub-sub bus05:07
gongysh_tung_doan, then do tacker conductor way.05:07
tung_doangongysh_: i will look into conductor. thanks05:07
sridhar_ramthis for any application on top of Tacker to receive events .. that is the ideal way .. an internal rpc might work as a near term alternative05:07
gongysh_sridhar_ram, we have to think pub-sub bus beyond tacker api server process.05:08
gongysh_the rabbitmq is the way to do it.05:08
sridhar_ramyes.. it is generic and can be used internally as well..05:08
sridhar_ramTacker NFVO becomes an "app" for Tacker VNFM05:08
sridhar_ramfor -> "on top of"05:09
gongysh_sridhar_ram, also to remember, we will remove all policy action into tacker conductor.05:09
gongysh_remove -> move.05:09
*** lennyb has quit IRC05:09
sridhar_ramgongysh_: i see tacker-conductor as a worker process shared by both NFVO and VNFM ..05:09
sridhar_ramit is more a utility worker process IMO05:10
*** kaisers_ has quit IRC05:10
sridhar_ramwhat do you think?05:10
sridhar_ramboth NFVO and VNFM can send their long running "work" to tacker-conductor to get it done05:10
sridhar_ram.. and have the results back05:10
gongysh_sridhar_ram, if I understand you, I say yes. we can use tacker conductor as a pub-sub system too.05:11
sridhar_ramack ...05:11
gongysh_lets wrap the healing bp.05:11
sridhar_ramagain, please keep the architecture clean in a way one day Tacker NFVO can be installed in a central site and local Tacker VNFM can be installed in local OpenStack sites05:12
gongysh_tung_doan, to investigate the conductor way, thanks.05:12
gongysh_sridhar_ram, right.05:12
tung_doangongysh_ : sure05:12
trinathssridhar_ram: that must be the design05:12
gongysh_#topic code patches05:13
*** openstack changes topic to "code patches (Meeting topic: tacker)"05:13
sridhar_ramtrinaths: yep05:13
gongysh_vim monitoring mistral way is merged.05:13
gongysh_do you anyone try it?05:13
gongysh_not yet?05:14
YanXing_ani will upgrade my testbed to use it05:14
trinathsgongysh_: not yet. will try that05:14
gongysh_YanXing_an, great.05:14
YanXing_annot yet +1.05:14
gongysh_trinaths, thanks05:14
gongysh_next patch I want you to merge is
gongysh_It passed the CI gate and a long patchset chain.05:16
gongysh_I think it is the time to get it merged.05:16
gongysh_and then we will have time to test it during developers daily work, when they are developing other features.05:17
YanXing_anwow, it's good news. I will fix any bugs if appeared.05:17
trinathsYanXing_an: nice work05:17
sridhar_ramYanXing_an: great job!!05:17
YanXing_antrinaths, sridhar_ram, thanks.05:18
gongysh_this is from05:18
gongysh_vagrant <>05:18
gongysh_will conflict with
gongysh_on db migration script05:18
*** simon-AS559 has joined #openstack-meeting05:18
gongysh_so we will merge and then
*** ekcs has quit IRC05:19
gongysh_other patch is
gongysh_also from dharmendra.kushwaha@nectechnologies.in05:19
*** simon-AS5591 has joined #openstack-meeting05:20
gongysh_recently, our core dharmendra is doing great to improve the tacker inner logical05:20
gongysh_that is great.05:20
*** trinaths has quit IRC05:20
*** lennyb has joined #openstack-meeting05:21
gongysh_before next meeting, we will have these patch to be merged.05:21
gongysh_#topic open discussion05:21
*** openstack changes topic to "open discussion (Meeting topic: tacker)"05:21
gongysh_anything to talk?05:22
*** trinaths has joined #openstack-meeting05:22
gongysh_tung_doan, hi05:22
*** simon-AS559 has quit IRC05:22
tung_doangongysh_: pong05:23
gongysh_could we enable the policy related CI tests?05:23
tung_doangongysh_: could you pls elaborate? Why we need this? thanks05:23
YanXing_angongysh, how to generate a asic chart using blockdiag, i can only generate a picture05:24
sridhar_ramYanXing_an: team: keeps lingering ... seems multiple folks are hitting this issue.05:25
gongysh_tung_doan, tacker.tests.functional.vnfm.test_tosca_vnf_alarm.VnfTestAlarmMonitor05:25
tung_doangongysh_: I am trying to fix this patch: . It will be finished soon for sure05:26
trinathsYanXing_an: you can use ascii to text generators05:26
* gongysh_ is seaching for YanXing_an 05:26
*** SerenaFeng has joined #openstack-meeting05:27
tbh_sridhar_ram:  can I work on that05:27
gongysh_YanXing_an, why do you need asscii?05:27
YanXing_ansridhar_ram, yes, it linger there for long time05:28
tbh_Or someone working on that05:28
gongysh_you can just put the blockdiag in rst.05:28
sridhar_ramtbh_: YanXing_an: i just asked some info .. but tbh_ if yoyu'05:28
gongysh_you don't need to upload the png.05:28
sridhar_ramtbh_: if you've some time please take a look. thanks!05:28
trinathsgongysh_: we dont upload any png.05:28
YanXing_angongysh, if so, we can only see the chart in CI result05:29
trinathsgongysh_: we just do ascii based diagrams05:29
gongysh_trinaths,  no, that is not absolutely.05:29
trinathsgongysh_: can we have png/jpeg stuff included ?05:29
gongysh_YanXing_an, yes sometime.05:29
gongysh_time is up.05:30
gongysh_thanks for everyone.05:30
gongysh_good day or night.05:30
*** openstack changes topic to "OpenStack Meetings ||"05:30
openstackMeeting ended Wed Jun 28 05:30:19 2017 UTC.  Information about MeetBot at . (v 0.1.4)05:30
trinathsone more05:30
openstackMinutes (text):
*** yamamoto has joined #openstack-meeting05:34
*** gongysh_ has quit IRC05:36
*** simon-AS5591 has quit IRC05:38
*** armax has quit IRC05:40
*** slaweq_ has joined #openstack-meeting05:41
*** marios has joined #openstack-meeting05:43
*** tobberydberg has joined #openstack-meeting05:44
*** slaweq_ has quit IRC05:46
*** SerenaFeng has quit IRC05:50
*** trinaths has left #openstack-meeting05:51
*** SerenaFeng has joined #openstack-meeting05:52
*** trinaths1 has joined #openstack-meeting05:53
*** andreas_s has joined #openstack-meeting05:54
*** simon-AS559 has joined #openstack-meeting05:57
*** thorst has joined #openstack-meeting05:57
*** prateek has joined #openstack-meeting05:59
*** lbragstad_ has joined #openstack-meeting06:02
*** rcernin has joined #openstack-meeting06:02
*** thorst has quit IRC06:02
*** lbragstad has quit IRC06:02
*** simon-AS5591 has joined #openstack-meeting06:03
*** spzala has joined #openstack-meeting06:03
*** simon-AS559 has quit IRC06:04
*** ricolin has joined #openstack-meeting06:04
*** abalutoiu has quit IRC06:09
*** spzala has quit IRC06:09
*** salv-orl_ has quit IRC06:10
*** cloudrancher has quit IRC06:10
*** salv-orlando has joined #openstack-meeting06:10
*** kaisers_ has joined #openstack-meeting06:11
*** rbartal has joined #openstack-meeting06:11
*** cloudrancher has joined #openstack-meeting06:13
*** alexyang has quit IRC06:13
*** Julien-zte has quit IRC06:14
*** qiangcao has quit IRC06:14
*** salv-orlando has quit IRC06:15
*** cloudrancher has quit IRC06:16
*** tovin07_ has joined #openstack-meeting06:16
*** simon-AS5591 has quit IRC06:17
*** Liuqing has quit IRC06:18
*** salv-orlando has joined #openstack-meeting06:21
*** ricolin has quit IRC06:23
*** YanXing_an has quit IRC06:23
*** alexyang has joined #openstack-meeting06:26
*** Julien-zte has joined #openstack-meeting06:27
*** ad_rien_ has quit IRC06:37
*** salv-orl_ has joined #openstack-meeting06:37
*** zhonghua has joined #openstack-meeting06:37
*** salv-orlando has quit IRC06:40
*** zhonghua2 has quit IRC06:40
*** slaweq_ has joined #openstack-meeting06:42
*** jeffli has joined #openstack-meeting06:44
*** slaweq_ has quit IRC06:47
*** kaisers_ has quit IRC06:53
*** med_ has quit IRC06:53
*** makowals has joined #openstack-meeting06:54
*** yamamoto has quit IRC06:55
*** simon-AS559 has joined #openstack-meeting06:56
*** acoles has joined #openstack-meeting06:57
*** cloudrancher has joined #openstack-meeting06:57
*** med_ has joined #openstack-meeting06:59
*** slaweq_ has joined #openstack-meeting06:59
*** med_ is now known as Guest3904506:59
*** hieulq_ has joined #openstack-meeting07:00
*** simon-AS559 has quit IRC07:01
*** simon-AS559 has joined #openstack-meeting07:01
*** psachin has joined #openstack-meeting07:02
*** cschwede has joined #openstack-meeting07:02
*** slaweq_ has quit IRC07:02
*** rledisez has joined #openstack-meeting07:02
cschwede#startmeeting swift07:02
openstackMeeting started Wed Jun 28 07:02:47 2017 UTC and is due to finish in 60 minutes.  The chair is cschwede. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:02
*** openstack changes topic to " (Meeting topic: swift)"07:02
openstackThe meeting name has been set to 'swift'07:02
*** slaweq_ has joined #openstack-meeting07:03
cschwedeHello everyone! Who's here for our biweekly Swift-meeting?07:03
acolesI am!07:03
mathiasbme too!07:03
tovin07_me :D07:03
*** wanghao has quit IRC07:03
rledisezi'm here o/07:03
*** yamamoto has joined #openstack-meeting07:04
acolesclayg: !07:04
*** kota_ has joined #openstack-meeting07:04
kota_i'm late07:04
mahatic_clayg: hi!07:04
*** m_kazuhiro has joined #openstack-meeting07:04
claygmahatic_: hello :D07:04
*** wanghao has joined #openstack-meeting07:05
cschwedeawesome - so let's get started! our agenda for today is:07:05
cschwede#topic Follow ups from last two weeks07:05
*** openstack changes topic to "Follow ups from last two weeks (Meeting topic: swift)"07:05
*** spzala has joined #openstack-meeting07:06
cschwedeI had a look at the topics from the last two meetings, and most of the followup are on our agenda for today (bugs, prio reviews etc). Has anyone another important follow up that needs to be discussed?07:06
*** jamesden_ has quit IRC07:06
mahatic_none from me07:07
*** jamesdenton has joined #openstack-meeting07:08
*** tesseract has joined #openstack-meeting07:08
cschwedealright, so let's continue with the next topic then07:08
*** slaweq_ has quit IRC07:08
cschwede#topic Denver PTG - session ideas07:08
*** openstack changes topic to "Denver PTG - session ideas (Meeting topic: swift)"07:08
cschwedePTG is taking place in ~10 weeks, and it's time to collect topic ideas. I duplicated our etherpad from the last time:
*** simon-AS559 has quit IRC07:09
cschwedei thought this worked well the last time - please feel free to add entries!07:10
*** spzala has quit IRC07:10
cschwedealso, note that a limited hotel block is already open for reservation - more details on the mailing list post from Erin:07:10
acolescschwede: thanks, etherpad works well usually07:11
kota_is it useful to add the etherpad link to meeting wiki?07:11
kota_or topic on #openstakck-swift channel07:12
cschwedekota_: already done :)07:12
mahatic_thanks for the info07:12
mahatic_kota_: yeah, adding to the topic is what is usually done I think07:12
cschwedekota_, mahatic_: i'll ping notmyname to change the topic on #openstack-swift - good idea!07:13
cschwedeok, let's continue07:13
cschwede#topic Reminder - Sydney summit: CFP07:13
*** openstack changes topic to "Reminder - Sydney summit: CFP (Meeting topic: swift)"07:13
cschwedethis is just a reminder, call for presentations is open for the Sydney summit07:13
cschwede#topic Bug triage07:14
*** openstack changes topic to "Bug triage (Meeting topic: swift)"07:14
*** markstur has quit IRC07:14
*** markstur has joined #openstack-meeting07:15
cschwedeas you may have noticed, there were quite a few new open bugs in the last few days for Swift. Some are already in discussion, some not07:15
*** markstur has quit IRC07:15
cschwedeSo I had a look at all bugs for Swift in state New, and that list is quite long:07:15
cschwedelink is also on
*** SerenaFeng has quit IRC07:16
*** tmorin has joined #openstack-meeting07:16
cschwedei'm wondering how we could triage this long bug list in a timely manner. some bugs are more questions, some are actually missing infos, and i'm sure some are important bugs that are not worked on yet07:17
cschwedeany ideas?07:17
mahatic_maybe let ppl know when you're triaging a bug, so there's no overlap? (amongst other things)07:18
cschwedefor reference, here's a shorter link:07:19
rledisezis there rules on bugs like on reviews (eg: if i feel it must be closed i set -1, and someone with -2 rights can approve or not)07:19
acolescschwede: we have talked in the past about having a bug triage day - not sure we have ever actually done it07:20
cschwedemahatic_: yes, i think the idea is to change the state then? for example, might be incomplete, or confirmed07:20
*** makowals has quit IRC07:20
mahatic_cschwede: correct07:21
mahatic_as that's one of the things that needs to be done before getting to work on it07:21
cschwedeacoles: i remember - maybe we can do that, but split this a bit? for example, have groups of people in the same timezone working on 10 bugs each, instead of doing this for a whole day?07:21
acolesrledisez: I *think* only cores can change bug importance but I know i would pay a lot of attention to a comment saying 'this is critical'07:21
kota_acoles: correct07:22
*** dmacpher has quit IRC07:22
cschwedeacoles: good point! so there needs to be at least one core taking part in each (sub-)triage07:22
mahatic_rledisez: I think you could set the "status" per your investigation on the bug07:23
rledisezmahatic_: yes, it seems i can edit it (as assigned to)07:24
*** zhonghua has quit IRC07:24
acolesrledisez: ah, so you can change the bug status? or just assign the bug?07:25
mahatic_I think he meant both?07:25
rledisezacoles: both i think. i'll try on a bug later07:25
rledisezi have the "pen" icon07:26
mahatic_rledisez: example bug you can try on:
openstackLaunchpad bug 1700036 in OpenStack Object Storage (swift) "Less number of connection retries between proxy-server and container/object-server." [Undecided,New]07:26
claygI'm interested in the work sdauge is doing - he sent something to the ML - but worried about how an eventual migration to storyboard might effect efforts spent automating against launchpad and defining process for that tool07:26
acolesrledisez: how about 'Importance'?07:26
mahatic_rledisez: yup, you should see a drop down when you click on the "pen" icon07:26
mahatic_for "status"07:26
mahatic_I mean, dropdown == set of options07:27
cschwedeclayg: while there are discussions for some time, i think there is no schedule yet for us to switch over to storyboard?07:27
rledisezacoles: i have the dropdown. but not for importance, i guess this one is for coredev only07:27
acolesrledisez: for the time being, if you find a bug that should be high or ciritical then tell me or another core and we will bump the importance07:28
cschwede^^ that!07:28
cschwede#info ping swift cores if you see bugs that are of critical or high importance07:29
claygI have another idea how we could solve that particular problem...07:29
*** oidgar has joined #openstack-meeting07:29
* cschwede gets curious07:29
claygcschwede: yeah i don't know the status of the storyboard migration either07:30
claygI do think that attacking the bug triage problem with automation is the right approach07:30
*** jamesmcarthur has joined #openstack-meeting07:30
acolessurely a migration to storyboard will preserve bug status etc? or is there a concern our triage would be lost in migration?07:30
claygif it wasn't for the backlog it'd probably be fairly manageable to keep up with bug status if we stayed on top of it07:31
*** SerenaFeng has joined #openstack-meeting07:31
cschwedehere is the ML post from Sean on the bug triage that clayg mentioned:07:32
claygi was thinking more about usefulness of scripts that push lauchpad statuses around... stuff like "in progress with no open patch"07:32
claygor "new/undecided" > 1 yr old (should => needs information or invalid)07:33
cschwedeclayg: so, should that become invalid or new (i mean the "in progress with no open patch")?07:33
claygprobably go back to new07:34
*** ricolin has joined #openstack-meeting07:34
*** alexchadin has joined #openstack-meeting07:34
mahatic_seems the default itself is "new" and "undecided"07:34
cschwedeyeah, that was my thinking as well. however, that would cleanup the state somewhat, but then we'd have even more bugs in state new07:34
cschwedethat need to be triaged07:34
*** jamesmcarthur has quit IRC07:35
acolesgerrit doesn't reliably update bugs with patch references, especially if the Closes-Bug is not in first patch version IIRC07:35
cschwedealso, do we need some more precise notes when opening a new bug? i remember there were some bugs a few days ago which lacked some required infos07:35
claygacoles: we could troll our commit log and make sure to push lp to the correct state07:36
cschwedeand acoles also tried to ping the author on irc without success07:36
cschwedeclayg: neat!07:36
acolesclayg: yes, for merged patches, but for in progress ... cross reference gerrit ?07:37
acolesactually, launchpad  does seem to get updated when patches are released, it is the in progress that go AWAOL07:37
cschwedehere's a proposal: i'll have a look at Seans work, and on automating LP in general and will follow up in next weeks meeting? sounds like this also needs a broader coverage within the community?07:38
cschwede(ie the other meeting)07:38
*** tbh_ has quit IRC07:38
claygacoles: ok, i understand - yeah checking gerrit is probably a good idea07:39
claygwe could probably use some information about the patch status to help add some tagging07:40
acolesdoes swift have a list of 'common' bug tags? I have used ec, low-hanging-fruit - if we start to tag we need to use a common set of tags07:40
clayg"has patch" "patch is +2'd" kind of tagging could help get bugs closed07:40
acolesclayg: ^^ nice07:41
kota_clayg: +107:41
claygacoles: seans email talked about trying to classify bugs under various modules/sub-teams07:41
claygwe could probably spot a ring bug vs. api?07:41
mahatic_patch status tag idea is good!07:42
acolesclayg: yes07:42
claygacoles: but I'm not aware of anyone writing down what we think a good list of appropriate tags for swift bugs would look like07:42
cschwedeclayg: so we have to start with that, right?07:43
claygacoles: maybe we need way-out-reach-fruit07:43
acolesclayg: lol ... 'no-hope'07:43
claygcschwede: maybe... I mean *probably*07:43
claygit would help me if I had some idea how we thought we were going to get these tags onto the bugs07:43
cschwedei'd say we'll continue this discussion in next weeks meeting? and i start an etherpad with some ideas inbetween?07:44
claygto some extend I think the actual tags themselves can be a somewhat emergent observed set - we could bikeshed over names - but if we know *how* to tag a bug that has a single-plus-2 patch we could name the tag "acoles-look-at-this-one" and that'd be fine07:45
mahatic_an etherpad to list out tags we think are appropriate would help07:45
*** tmorin has quit IRC07:45
*** m_kazuhiro_ has joined #openstack-meeting07:45
clayg^ yeah or just do that and get the creative juices flowing07:45
*** pnavarro has joined #openstack-meeting07:45
cschwedeacoles will get a lot of extra work if we automate the "acoles-look-at-this-one" tag07:45
acolesdoes it filter ones that have *my* +2 ;) or do I get to go in circles07:46
* acoles imagines becoming infinitely trapped in launchpad07:46
cschwedethis discussion is great, but let's continue with the next topic and follow up on this one - only 14 mins left07:47
cschwede#action cschwede to start etherpad for bug tag ideas, investigate automation of LP bug state changes and report in next meeting07:47
claygcschwede: awesome07:47
clayggood work07:47
cschwede#topic Priority Reviews07:47
*** openstack changes topic to "Priority Reviews (Meeting topic: swift)"07:47
acolesI would love it if launchpad 'learnt' the tags we were commonly used an offered them on the UI...I have a vague recollection of there being some way to setup project tags in launchpad...that of course only helps humans07:47
*** m_kazuhiro has quit IRC07:48
cschwedethere was some progress on the linked prio reviews (thx Tim & Matt!), but the list didn't get shorter from the last time07:48
acolesyes! ^^07:49
acolesoh, sorry, we moved on07:49
cschwedeacoles: i'll noted that for the follow up, thx for looking into it!07:49
*** kaisers_ has joined #openstack-meeting07:50
*** ralonsoh has joined #openstack-meeting07:50
cschwedeis the list of prio reviews exhaustive, are there any other patches that need some higher priority when reviewing?07:50
mahatic_a couple of bugs on that page are merged, it probably needs some updating07:51
cschwedemahatic_: ah, right. i only had a look at the ones i included in the agenda ( updating the prio page should be a ... prio ;)07:52
cschwede#action cschwede will update
cschwedeok, if there is nothing special to discuss here, let's continue07:53
acolesrledisez: any progress on (needs tests)07:53
acoleswhich fixes
openstackLaunchpad bug 1652323 in OpenStack Object Storage (swift) "ssync syncs an expired object as a tombstone" [Medium,Confirmed]07:53
claygacoles: he's going to be too busy reviewing patch 428408 and patch 478416 to be bothered with tests - you'll have to do it ;)07:54
rledisezacoles: no, sadly i've been very very busy07:54
rledisezi'll really try to find some time by the end of the week07:54
rledisezclayg: noted, on my (too long) todolist ;)07:55
acolesrledisez: well, clayg has bullied me now07:55
cschwede#topic Open Discussion07:55
*** openstack changes topic to "Open Discussion (Meeting topic: swift)"07:55
acolesrledisez: I have a probe test patch that I think can be adapted easily07:56
tovin07_I have one patch that need some comments07:56
acolesrledisez: I'll try to put some time on it07:56
cschwedethat already sounds like an open discussion, anything else for this meeting? a couple of minutes left07:56
claygnotmyname: is out - this is the only meeting today07:56
*** toscalix has joined #openstack-meeting07:57
cschwede#info notmyname is out - no Swift meeting at 2100UTC today07:57
*** csomerville has quit IRC07:57
tovin07_can anyone take a look at patch 468316? :D07:57
*** thorst has joined #openstack-meeting07:58
*** ykatabam has quit IRC07:59
cschwedetovin07_: i'll have a look at it at the end of the week07:59
*** ykatabam has joined #openstack-meeting07:59
tovin07_cschwede, thanks!07:59
cschwedeAlright, thanks everyone for attending this meeting, your ideas and contributions to Swift! Talk to you soon on #openstack-swift again :)08:00
*** openstack changes topic to "OpenStack Meetings ||"08:00
openstackMeeting ended Wed Jun 28 08:00:08 2017 UTC.  Information about MeetBot at . (v 0.1.4)08:00
openstackMinutes (text):
*** rledisez has left #openstack-meeting08:01
*** sridhar_ram has quit IRC08:02
*** thorst has quit IRC08:03
*** acoles has left #openstack-meeting08:03
*** gongysh_ has joined #openstack-meeting08:03
*** slaweq_ has joined #openstack-meeting08:03
*** makowals has joined #openstack-meeting08:05
*** makowals has quit IRC08:05
*** m_kazuhiro_ has quit IRC08:06
*** slaweq_ has quit IRC08:07
*** kota_ has left #openstack-meeting08:11
*** jeffli has quit IRC08:12
*** ykatabam has quit IRC08:17
*** makowals has joined #openstack-meeting08:19
*** kaisers_ has quit IRC08:20
*** ykatabam has joined #openstack-meeting08:26
*** gongysh_ has quit IRC08:28
*** abalutoiu has joined #openstack-meeting08:29
*** makowals has quit IRC08:29
*** tobberyd_ has joined #openstack-meeting08:29
*** gongysh has joined #openstack-meeting08:30
*** ricolin has quit IRC08:30
*** ricolin has joined #openstack-meeting08:31
*** tobberydberg has quit IRC08:33
*** tobberydberg has joined #openstack-meeting08:33
*** tobberyd_ has quit IRC08:33
*** alexchadin has quit IRC08:34
*** ricolin has quit IRC08:35
*** abalutoiu_ has joined #openstack-meeting08:40
*** lpetrut has joined #openstack-meeting08:41
*** abalutoiu_ has quit IRC08:44
*** abalutoiu has quit IRC08:44
*** abalutoiu_ has joined #openstack-meeting08:45
*** hashar has joined #openstack-meeting08:47
*** epico has quit IRC08:50
*** makowals has joined #openstack-meeting08:51
*** makowals has quit IRC08:52
*** abalutoiu__ has joined #openstack-meeting08:58
*** epico has joined #openstack-meeting08:59
*** abalutoiu_ has quit IRC09:01
*** slaweq_ has joined #openstack-meeting09:04
*** spzala has joined #openstack-meeting09:07
*** epico has quit IRC09:08
*** epico has joined #openstack-meeting09:08
*** slaweq_ has quit IRC09:09
*** spzala has quit IRC09:12
*** yamamoto has quit IRC09:13
*** kaisers_ has joined #openstack-meeting09:17
*** yamamoto has joined #openstack-meeting09:17
*** ykatabam has quit IRC09:18
*** makowals has joined #openstack-meeting09:18
*** makowals has quit IRC09:18
*** simon-AS559 has joined #openstack-meeting09:20
*** thorst has joined #openstack-meeting09:24
*** simon-AS559 has quit IRC09:24
*** SerenaFeng has quit IRC09:25
*** sambetts|afk is now known as sambetts09:26
*** makowals has joined #openstack-meeting09:26
*** tobberydberg has quit IRC09:27
*** abhishekk has left #openstack-meeting09:27
*** tobberydberg has joined #openstack-meeting09:27
*** pcaruana has joined #openstack-meeting09:28
*** thorst has quit IRC09:29
*** SerenaFeng has joined #openstack-meeting09:30
*** tobberydberg has quit IRC09:34
*** wanghao has quit IRC09:35
*** tobberydberg has joined #openstack-meeting09:35
*** caowei_ has joined #openstack-meeting09:38
*** makowals has quit IRC09:41
*** caowei has quit IRC09:42
*** caowei_ is now known as caowei09:42
*** kaisers_ has quit IRC09:47
*** makowals has joined #openstack-meeting09:51
*** makowals has quit IRC09:51
*** jtomasek has quit IRC09:52
*** jtomasek has joined #openstack-meeting09:53
*** rossella__ has quit IRC09:55
*** rcernin has quit IRC09:55
*** coolsvap has joined #openstack-meeting09:56
*** jtomasek has quit IRC09:59
*** jtomasek has joined #openstack-meeting09:59
*** jkilpatr has quit IRC10:00
*** amotoki_away is now known as amotoki10:01
*** tovin07_ has quit IRC10:02
*** rcernin has joined #openstack-meeting10:03
*** makowals has joined #openstack-meeting10:04
*** makowals has quit IRC10:05
*** slaweq_ has joined #openstack-meeting10:05
*** SerenaFeng has quit IRC10:06
*** sdague has joined #openstack-meeting10:07
*** rossella__ has joined #openstack-meeting10:08
*** yamamoto has quit IRC10:08
*** rcernin has quit IRC10:09
*** slaweq_ has quit IRC10:10
*** rcernin has joined #openstack-meeting10:11
*** yamamoto has joined #openstack-meeting10:13
*** yamamoto has quit IRC10:15
*** gongysh has quit IRC10:18
*** makowals has joined #openstack-meeting10:20
*** makowals has quit IRC10:22
*** shu-mutou is now known as shu-mutou-AWAY10:24
*** yamamoto has joined #openstack-meeting10:25
*** trinaths1 has left #openstack-meeting10:27
*** caowei_ has joined #openstack-meeting10:29
*** kevinz has quit IRC10:31
*** martinkopec has joined #openstack-meeting10:32
*** caowei has quit IRC10:32
*** caowei_ is now known as caowei10:32
*** gongysh has joined #openstack-meeting10:34
*** gongysh has quit IRC10:41
*** kaisers_ has joined #openstack-meeting10:43
*** martinkopec has quit IRC10:44
*** martinkopec has joined #openstack-meeting10:47
*** ad_rien_ has joined #openstack-meeting10:48
*** yamamoto has quit IRC10:48
*** yamamoto has joined #openstack-meeting10:49
*** epico has quit IRC10:55
*** rossella__ has quit IRC10:57
*** tobberyd_ has joined #openstack-meeting10:58
*** jkilpatr has joined #openstack-meeting10:58
*** tobbery__ has joined #openstack-meeting11:00
*** tobberyd_ has quit IRC11:00
*** tobberydberg has quit IRC11:01
*** tobbery__ has quit IRC11:01
*** tobberydberg has joined #openstack-meeting11:02
*** amit213 has quit IRC11:02
*** slaweq_ has joined #openstack-meeting11:05
*** caowei has quit IRC11:07
*** kaisers_ has quit IRC11:07
*** spzala has joined #openstack-meeting11:09
*** SerenaFeng has joined #openstack-meeting11:10
*** slaweq_ has quit IRC11:11
*** jaypipes has joined #openstack-meeting11:13
*** rossella__ has joined #openstack-meeting11:14
*** spzala has quit IRC11:14
*** alexchadin has joined #openstack-meeting11:18
*** mhenkel has quit IRC11:22
*** thorst has joined #openstack-meeting11:25
*** adisky__ has quit IRC11:25
*** thorst has quit IRC11:29
*** jamesmcarthur has joined #openstack-meeting11:31
*** ralonsoh has quit IRC11:32
*** egallen has quit IRC11:33
*** tobberydberg has quit IRC11:33
*** simon-AS5591 has joined #openstack-meeting11:33
*** tobberydberg has joined #openstack-meeting11:34
*** ad_rien_ has quit IRC11:34
*** ericyoung has joined #openstack-meeting11:34
*** jamesmcarthur has quit IRC11:36
*** julim has joined #openstack-meeting11:38
*** zhhuabj has joined #openstack-meeting11:38
*** julim has quit IRC11:39
*** abalutoiu__ has quit IRC11:41
*** jkilpatr has quit IRC11:41
*** youzp has quit IRC11:47
*** Julien-zte has quit IRC11:51
*** salv-orl_ has quit IRC11:51
*** salv-orlando has joined #openstack-meeting11:51
*** rbudden has joined #openstack-meeting11:53
*** zhhuabj has quit IRC11:53
*** mhenkel has joined #openstack-meeting11:55
*** julim has joined #openstack-meeting11:55
*** salv-orlando has quit IRC11:56
*** makowals has joined #openstack-meeting11:56
*** litao__ has quit IRC11:57
*** ad_rien_ has joined #openstack-meeting11:57
*** simon-AS559 has joined #openstack-meeting12:00
*** simon-AS5591 has quit IRC12:00
*** jkilpatr has joined #openstack-meeting12:01
*** pcaruana has quit IRC12:02
*** simon-AS5591 has joined #openstack-meeting12:02
*** pcaruana has joined #openstack-meeting12:02
*** rbowen has joined #openstack-meeting12:03
*** kaisers_ has joined #openstack-meeting12:04
*** simon-AS559 has quit IRC12:04
*** raildo has joined #openstack-meeting12:05
*** slaweq_ has joined #openstack-meeting12:07
*** janki has joined #openstack-meeting12:07
*** thorst has joined #openstack-meeting12:10
*** jkilpatr has quit IRC12:11
*** slaweq_ has quit IRC12:12
*** aloga has quit IRC12:12
*** aloga has joined #openstack-meeting12:12
*** jkilpatr has joined #openstack-meeting12:13
*** pcaruana has quit IRC12:16
*** bobmel has joined #openstack-meeting12:17
*** jamesdenton has quit IRC12:19
*** jamesdenton has joined #openstack-meeting12:19
*** pcaruana has joined #openstack-meeting12:23
*** pcaruana has quit IRC12:23
*** pcaruana has joined #openstack-meeting12:23
*** ajo has left #openstack-meeting12:25
*** yamamoto has quit IRC12:27
*** esberglu has joined #openstack-meeting12:28
*** jkilpatr has quit IRC12:28
*** kaisers_ has quit IRC12:28
*** pcaruana has quit IRC12:29
*** yamamoto has joined #openstack-meeting12:30
*** yamamoto has quit IRC12:30
*** janki has quit IRC12:33
*** pcaruana has joined #openstack-meeting12:37
*** dprince has joined #openstack-meeting12:39
*** trozet has joined #openstack-meeting12:41
*** baoli has joined #openstack-meeting12:41
*** baoli has quit IRC12:43
*** pcaruana has quit IRC12:43
*** pcaruana has joined #openstack-meeting12:44
*** baoli has joined #openstack-meeting12:44
*** youzp has joined #openstack-meeting12:45
*** marios has quit IRC12:47
*** marios has joined #openstack-meeting12:47
*** SerenaFeng has quit IRC12:48
*** yamamoto has joined #openstack-meeting12:49
*** esberglu has quit IRC12:49
*** marios has quit IRC12:50
*** kylek3h has joined #openstack-meeting12:50
*** marios has joined #openstack-meeting12:50
*** yamamoto has quit IRC12:52
*** youzp has quit IRC12:52
*** Julien-zte has joined #openstack-meeting12:52
*** pcaruana has quit IRC12:53
*** armstrong has joined #openstack-meeting12:53
*** pewp has quit IRC12:54
*** bknudson has joined #openstack-meeting12:55
*** pewp has joined #openstack-meeting12:56
*** youzp has joined #openstack-meeting12:59
*** alexchadin has quit IRC13:01
*** alexchadin has joined #openstack-meeting13:01
*** gouthamr has joined #openstack-meeting13:01
*** baoli has quit IRC13:02
*** baoli has joined #openstack-meeting13:03
*** esberglu has joined #openstack-meeting13:05
*** pcaruana has joined #openstack-meeting13:06
*** alexchadin has quit IRC13:06
*** slaweq_ has joined #openstack-meeting13:07
*** baoli has quit IRC13:09
*** yamamoto has joined #openstack-meeting13:10
*** bastafidli_ has joined #openstack-meeting13:10
*** spzala has joined #openstack-meeting13:11
*** askb has quit IRC13:11
*** slaweq_ has quit IRC13:13
*** pcaruana has quit IRC13:13
*** pcaruana has joined #openstack-meeting13:14
*** spzala has quit IRC13:15
*** links has quit IRC13:16
*** armstrong has quit IRC13:18
*** gongysh has joined #openstack-meeting13:18
*** simon-AS5591 has quit IRC13:18
*** alexchadin has joined #openstack-meeting13:21
*** askb has joined #openstack-meeting13:21
*** gongysh has quit IRC13:23
*** rossella_ has joined #openstack-meeting13:23
*** kaisers_ has joined #openstack-meeting13:26
*** rossella__ has quit IRC13:26
*** adisky__ has joined #openstack-meeting13:31
*** bobh has joined #openstack-meeting13:31
*** links has joined #openstack-meeting13:33
*** tobberyd_ has joined #openstack-meeting13:34
*** askb has quit IRC13:34
*** kaisers_ has quit IRC13:37
*** jamesmcarthur has joined #openstack-meeting13:37
*** tobberydberg has quit IRC13:37
*** eharney has joined #openstack-meeting13:37
*** zhurong_ has joined #openstack-meeting13:38
*** tobberyd_ has quit IRC13:38
*** Fdaisuke has joined #openstack-meeting13:40
*** pcaruana has quit IRC13:40
*** simon-AS559 has joined #openstack-meeting13:41
*** jprovazn has joined #openstack-meeting13:44
*** simon-AS559 has quit IRC13:46
*** pcaruana has joined #openstack-meeting13:46
*** simon-AS559 has joined #openstack-meeting13:46
*** bastafidli_ has quit IRC13:46
*** gouthamr has quit IRC13:52
*** links has quit IRC13:56
*** rhochmuth has joined #openstack-meeting13:57
*** prateek has quit IRC13:58
*** koji has joined #openstack-meeting13:58
*** kornica has joined #openstack-meeting13:58
*** witek has joined #openstack-meeting13:58
*** rossella_ has quit IRC13:59
rhochmuth#startmeeting monasca14:01
openstackMeeting started Wed Jun 28 14:01:18 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: monasca)"14:01
openstackThe meeting name has been set to 'monasca'14:01
rhochmuthhi witek14:01
rhochmuthi just realized that i still have a number of reviews to complete14:02
*** haruki has joined #openstack-meeting14:02
rhochmuthhi koji14:02
rhochmuthhi kornica14:02
rhochmuthlooks like a pretty small group again14:02
kornicapleasure to meet you sire ;)14:02
rhochmuthand the agenda is a little light14:03
kornicagroup is small but strong14:03
*** youzp has quit IRC14:03
rhochmuthso besides all the stuff that I said I would do last week that I didn't get to, are there other items to cover today14:03
*** marios has quit IRC14:04
kornicaI'd mention that we reached a state where we have a gates in place for documentation14:04
witekkornica works on publishing docu14:04
*** haleyb|afk is now known as haleyb14:04
witekfor log-api14:04
kornicaresults can be examined here ->
kornicawitek: yes that's only for log-api, clearing the path14:05
*** marios has joined #openstack-meeting14:05
kornicaapi-ref, api-guide, dev docs and releasenotes14:05
rhochmuthvery impressive14:05
kornicawhat's missing and could be a subject of discussion are install docs, but that's point for agend for another meeting I guess14:05
kornicarhochmuth is there any agenda at all, I don't want to jump in front of it14:06
witeklet's fill this docs with body first14:06
*** gouthamr has joined #openstack-meeting14:06
*** bastafidli_ has joined #openstack-meeting14:06
witekone thing to mention perhaps14:07
kornicawitek: btw, I addressed comments here =>
witekCloudKitty started work on integrating with Monasca14:07
rhochmuthyes, saw that14:07
rhochmuththanks for answering their questions14:07
*** lbragstad_ is now known as lbragstad14:07
witekAshwin and Joseph has given valueable input on using monasca-ceilometer14:08
*** slaweq_ has joined #openstack-meeting14:08
witekfor that purpose14:08
rhochmuththanks ashwin and joseph14:08
*** tobberydberg has joined #openstack-meeting14:10
*** awaugama has joined #openstack-meeting14:10
*** xyang1 has joined #openstack-meeting14:10
witekI don't have anything else14:10
kornicahave they uploaded anything to review ?14:10
witekI don't think so14:11
kornicaI mean what's the scope of their integration ? I think I got little behind in that topic14:11
rhochmuthi don't see anything14:11
rhochmuthi'm going to check with the OP5 folks to see if they are going to start joining the meetings14:12
witekthey want to use Monasca as backend for storing metrics they use in their project14:12
rhochmuthi promise i'll get some reviews done this week14:12
*** slaweq_ has quit IRC14:12
*** rbrndt has joined #openstack-meeting14:13
rhochmuthbtw, next week i'll probably be out for July 4th week14:13
kornicasure things (from my side I can tell you that keystone_auth and new_client topics) are in fairly good shape, however in new_client[monasca-agent] adrian found a flaw around libvirt and ovs that I need to fix tommorow14:13
*** rossella_ has joined #openstack-meeting14:14
kornicabut apart from those two checks everything is ok (rest of agent, ui and client while used in cli)14:14
rhochmuththx kornica14:14
*** tobberydberg has quit IRC14:14
rhochmuthwe added rate calculation to monasca-aggregator recently14:14
*** simon-AS559 has quit IRC14:15
*** VW has joined #openstack-meeting14:15
*** zz_dimtruck is now known as dimtruck14:15
rhochmuthi guess that is it for today14:16
kornicaoh, it is written in go :)14:16
*** eharney has quit IRC14:16
rhochmuthyes i14:16
kornicadid you check that maybe with newer kafka ?14:16
witekdoes it cover all the functionallity of monasca-transform?14:16
witekI mean monasca-aggregator?14:16
rhochmuthyes, it covers everything in monasca-transform and more14:16
kornicawitek: you want to say that it is meant to replace monasca-transform ?14:16
witekI'm wondering what should be the future of these two14:17
rhochmuthand it is a very easy to deploy/configure, very performant, with guarantees on collection14:17
kornicafrom what I saw they still contribute to monasca-transform, so that's a bid odd from my POV14:17
*** bswartz has joined #openstack-meeting14:17
witekwhat Kafka client do you use?14:18
rhochmuthwell, monasca-transform was developed and deployed in Helion OpenStack14:18
rhochmuthDependencies: Dependent on only the following Go libraries:14:18
rhochmuththere is a nice readme that covers what monasca-aggregator does14:18
*** youzp has joined #openstack-meeting14:19
*** haleyb is now known as haleyb|afk14:19
kornicaso the same thing that we considered a while ago for the rest of monasca, but that got swallowed by other more important priorities :/14:19
kornicacofluent is async, right ?14:19
rhochmuthit uses librdkafka14:20
rhochmuththe go client is written ontop of that14:20
kornicahaving that established, couldn't we simply switch to oslo.messaging[kafka] and use newer kafka from their dependencies that is also async14:20
kornicafor the rest monasca14:20
kornicahigh-level idea14:20
rhochmuthi don't recall all the specific issues, but librdkafka requires a C build of the library14:21
*** hongbin has joined #openstack-meeting14:21
kornicakafka in oslo.messaging is I guess the same on as in forked monasca code (what monasca used to use) but newer14:22
*** spzala has joined #openstack-meeting14:22
kornicawell, not kafka but kafkaclient14:22
*** youzp has quit IRC14:23
rhochmuthanything else?14:25
kornicawitek: you have something ?14:25
witekno, thanks14:25
*** simon-AS559 has joined #openstack-meeting14:25
*** awaugama_ has joined #openstack-meeting14:26
rhochmuthok, bye everyone14:26
rhochmuthsmall croud14:26
witekthank you rhochmuth14:26
rhochmuthbut twice as big a last week14:26
kornicaheh, cya14:26
rhochmuthso we are gaining momentum14:26
witekthank you everyone14:26
harukithank you14:26
*** openstack changes topic to "OpenStack Meetings ||"14:26
openstackMeeting ended Wed Jun 28 14:26:54 2017 UTC.  Information about MeetBot at . (v 0.1.4)14:26
openstackMinutes (text):
*** haruki has quit IRC14:27
*** rbrndt has left #openstack-meeting14:27
*** koji has quit IRC14:27
*** rhochmuth has quit IRC14:27
*** awaugama has quit IRC14:27
*** Fdaisuke has quit IRC14:27
*** simon-AS5591 has joined #openstack-meeting14:28
*** eharney has joined #openstack-meeting14:28
*** rossella_ has quit IRC14:29
*** awaugama_ is now known as awaugama14:29
*** kornica has quit IRC14:29
*** simon-AS559 has quit IRC14:30
*** trinaths has joined #openstack-meeting14:30
*** felipemonteiro_ has joined #openstack-meeting14:33
*** kaisers_ has joined #openstack-meeting14:34
*** felipemonteiro__ has joined #openstack-meeting14:34
*** gouthamr has quit IRC14:34
*** salv-orlando has joined #openstack-meeting14:37
*** unicell1 has joined #openstack-meeting14:37
*** felipemonteiro_ has quit IRC14:38
*** unicell has quit IRC14:39
*** rossella_ has joined #openstack-meeting14:40
*** ricolin has joined #openstack-meeting14:42
*** trinaths1 has joined #openstack-meeting14:42
*** gouthamr has joined #openstack-meeting14:43
*** tinwood has quit IRC14:43
*** baoli has joined #openstack-meeting14:43
*** tinwood has joined #openstack-meeting14:43
*** spzala has quit IRC14:45
*** trinaths has quit IRC14:45
*** spzala has joined #openstack-meeting14:45
*** mtanino__ has joined #openstack-meeting14:46
*** ricolin has quit IRC14:49
*** ricolin has joined #openstack-meeting14:50
*** spzala has quit IRC14:50
*** shintaro has joined #openstack-meeting14:51
*** ramineni__ has joined #openstack-meeting14:54
*** ricolin_ has joined #openstack-meeting14:54
*** ricolin has quit IRC14:54
*** ricolin_ has quit IRC14:54
*** ricolin has joined #openstack-meeting14:54
*** markstur has joined #openstack-meeting14:57
*** ramineni__ is now known as ramineni_14:58
*** fnaval has joined #openstack-meeting14:59
*** pewp has quit IRC15:00
*** alexchadin has quit IRC15:02
*** zhurong_ has quit IRC15:03
*** pewp has joined #openstack-meeting15:03
*** rossella_ has quit IRC15:04
*** kaisers_ has quit IRC15:05
*** rcernin has quit IRC15:06
*** links has joined #openstack-meeting15:07
*** gyee has joined #openstack-meeting15:07
*** slaweq_ has joined #openstack-meeting15:09
*** lhx__ has joined #openstack-meeting15:11
*** oidgar has quit IRC15:12
*** jamesmcarthur has quit IRC15:13
*** slaweq_ has quit IRC15:13
*** gnarld_ is now known as cFouts15:14
*** simon-AS5591 has quit IRC15:17
*** spzala has joined #openstack-meeting15:19
*** chyka has joined #openstack-meeting15:20
*** jamesmcarthur has joined #openstack-meeting15:22
*** jamesmcarthur has quit IRC15:24
*** annabelleB has joined #openstack-meeting15:25
*** jamesmcarthur has joined #openstack-meeting15:27
*** martinkopec has quit IRC15:27
*** andreas_s has quit IRC15:28
*** egallen has joined #openstack-meeting15:33
*** makowals has quit IRC15:34
*** shintaro has quit IRC15:34
*** Julien-zte has quit IRC15:34
*** Julien-zte has joined #openstack-meeting15:34
*** Julien-zte has quit IRC15:35
*** trozet has quit IRC15:35
*** Julien-zte has joined #openstack-meeting15:35
*** Julien-zte has quit IRC15:36
*** Julien-zte has joined #openstack-meeting15:36
*** links has quit IRC15:36
*** Julien-zte has quit IRC15:36
*** jkilpatr has joined #openstack-meeting15:37
*** Julien-zte has joined #openstack-meeting15:37
*** Julien-zte has quit IRC15:37
*** Julien-zte has joined #openstack-meeting15:38
*** Julien-zte has quit IRC15:38
*** Julien-zte has joined #openstack-meeting15:38
*** Julien-zte has quit IRC15:39
*** Julien-zte has joined #openstack-meeting15:39
*** Julien-zte has quit IRC15:40
*** Julien-zte has joined #openstack-meeting15:40
*** Julien-zte has quit IRC15:40
*** Julien-zte has joined #openstack-meeting15:41
*** Julien-zte has quit IRC15:41
*** hagridaaron has joined #openstack-meeting15:43
*** rderose has joined #openstack-meeting15:43
*** salv-orlando has quit IRC15:44
*** salv-orlando has joined #openstack-meeting15:45
*** Sukhdev has joined #openstack-meeting15:46
*** salv-orlando has quit IRC15:49
*** hieulq__ has joined #openstack-meeting15:49
*** manjeets_ has joined #openstack-meeting15:50
*** e0ne has joined #openstack-meeting15:51
*** makowals has joined #openstack-meeting15:51
*** jamesmcarthur has quit IRC15:51
*** jamesmcarthur has joined #openstack-meeting15:53
*** csaikia has joined #openstack-meeting15:54
*** ad_rien_ has quit IRC15:57
*** annabelleB has quit IRC15:57
*** marios has quit IRC15:57
*** jamesdenton has quit IRC15:58
*** Sukhdev_ has joined #openstack-meeting15:59
*** jamesdenton has joined #openstack-meeting15:59
*** Rockyg has joined #openstack-meeting15:59
*** makowals has quit IRC15:59
*** chyka has quit IRC15:59
*** salv-orlando has joined #openstack-meeting16:00
jungleboyj#startmeeting cinder16:00
openstackMeeting started Wed Jun 28 16:00:30 2017 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
*** makowals has joined #openstack-meeting16:00
jungleboyjdulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon rhedlind jbernard _alastor_ bluex karthikp_ patrickeast dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino karlamrhein diablo_rojo jay.xu jgregor lhx_ baumann rajinir wilson-l reduxio wanghao thrawn01 chris_morrell watanabe.isao,tommylikehu mdovgal ildikov wxy viks ketonne abishop sivn16:00
*** annabelleB has joined #openstack-meeting16:01
geguileohi! o/16:01
lhx__o/ hi16:01
pewphemna (ஐ╹◡╹)ノ16:01
pewpjungleboyj (♦亝д 亝)ノ16:02
jungleboyjGive people one more minute.16:02
*** xyang1 has quit IRC16:02
*** kaisers_ has joined #openstack-meeting16:02
SwansonYou'll never get that minute back. Gone forever.16:02
*** cloudrancher has quit IRC16:02
SwansonYour last words will be cut short by one minute now.16:02
*** xyang1 has joined #openstack-meeting16:03
jungleboyjOk, we have a lot to cover.  smcginnis , the bum , is sleeping in China right now so I am your fearless leader again today.16:03
*** cloudrancher has joined #openstack-meeting16:03
jungleboyjAnd I am not letting the meeting run over this time!16:03
*** bastafidli_ has quit IRC16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: cinder)"16:03
jungleboyjYour weekly reminder to check our review focus list.16:04
jungleboyjsmcginnis:  Added specs that are approved for pike but not yet complete.  So, need to be reviewing those.16:04
jungleboyjWe need to finish implementation against those specs, move them to queens or revert if no longer needed.16:05
jungleboyjIf you own one of those specs and it needs action, please take care of it.16:05
jungleboyjAlso, we now have the work item of moving documentation from the docs team to the Cinder project.16:05
jungleboyjThe first of the patches asettle  was nice enough to start for us:  #link
*** jamesdenton has quit IRC16:06
*** chyka has joined #openstack-meeting16:06
jungleboyjI took over the docs liaison project so I am going to shoot to put together an etherpad to organize the work.  Haven't had a chance to do that yet though.  Will update everyone here when that happens.16:07
*** xyang1 has quit IRC16:07
*** xyang1 has joined #openstack-meeting16:07
*** diablo_rojo has joined #openstack-meeting16:07
hemnaso all docs for cinder are going to live in cinder now ?16:07
hemnaeverybody knows that engineers don't write docs.......16:07
hemnaguess openstack is just giving up then ?16:08
jungleboyjhemna:  Yes.  This is because of the brain drain on the documentation team.16:08
* diablo_rojo finally gets IRC to connect16:08
jungleboyjhemna:  I know.16:08
jungleboyjSo, it is going to be important for Cores to make sure that Docs are happening.16:08
jgriffithhonestly I think we *should* own our docs16:08
jungleboyjI am going to be working/enforcing in that area.16:08
jgriffithwe should also own interactions with users16:08
jungleboyjjgriffith: I think you are right.16:08
asettleSo nice16:09
asettleVery asettle16:09
* asettle walks in late16:09
jungleboyjhey asettle16:09
*** makowals has quit IRC16:09
jungleboyjSo, I am just going to have to figure out how to get you all to write docs.  ;-)16:09
jungleboyjI can't send a cheesecake to everyone.16:09
tommylikehuyou can16:10
jungleboyjAny other questions on that topic?16:10
*** slaweq_ has joined #openstack-meeting16:10
*** _alastor1 is now known as _alastor_16:10
jungleboyjtommylikehu: Well, I CAN ... but ...16:10
*** psachin has quit IRC16:10
geguileojungleboyj: can't we just make sure that we add the docs together with the code?16:11
geguileojust like unit-tests16:11
jungleboyjLet me get an etherpad put together and we can talk in greater detail in the next week or two.  We need to get this done for Pike though.16:11
ildikovgeguileo: +116:11
diablo_rojogeguileo, +116:11
ildikovgeguileo: that would be the point in the whole initiative16:11
jungleboyjgeguileo: +116:11
lhx__jungleboyj, is this ok?
lhx__or something like this etherpad16:12
ildikovtl;dr the idea is to let the experts write the doc and the docs team help with formatting and phrasing it consistently16:12
jungleboyjlhx__:  Oh cool.  Yes, something like that.  Thanks for getting that to me.16:12
hemnawho don't write docs16:13
hemnaanyway, the projects should own their docs, I'm just saying.....99% of engineers don't write em.16:13
jungleboyjhemna:  :-p  Things change.16:13
asettlehemna: and you have just summed up the problem16:13
*** caboucha has joined #openstack-meeting16:14
hemnayah :(16:14
asettleSo, help us be a part of the change :)16:14
asettlePromise it'll be awesome16:14
asettlejungleboyj:  is promising cheesecake so ya know16:14
* hemna is ready for awesome.16:14
jungleboyjasettle:  ++16:14
ildikovhemna: I didn't say you have to write War and Piece length and quality docs from now on16:14
asettlejungleboyj: yo fo real i'm a very serious gal about cheese cake16:14
geguileoI'm sure we'll bother to write the docs if we can't get our code merged without it16:14
*** slaweq_ has quit IRC16:14
asettleno, no hemna ildikov did say you'd have to write giant docs ;)16:14
jungleboyjgeguileo: ++16:15
ildikovhemna: but you're the expert of what you develop :)16:15
hemnacan we write docs in regex code? :P16:15
ildikovasettle: ;)16:15
asettlePrecisely :)16:15
asettlehemna: errrr16:15
jungleboyjAnd there are those of us that don't mind reviewing and helping with documentation.16:15
jungleboyjSo, it will be ok.16:15
* jungleboyj shakes my head a Swanson 16:16
ildikovhemna: is that the new English? :)16:16
*** trinaths1 has left #openstack-meeting16:16
jungleboyjAnyway, this was more of a 'heads up' that this was coming and we will discuss further once I have a better handle on this.16:16
jungleboyj#topic Critical and security fixes to driverfixes branch16:17
*** openstack changes topic to "Critical and security fixes to driverfixes branch (Meeting topic: cinder)"16:17
jungleboyjSo, this topic came out of last week's Manila meeting.16:17
jungleboyjThey are going to also add a driverfixes branch.16:17
*** sshank has joined #openstack-meeting16:18
hemnaa single branch ?16:18
jungleboyjQuestion came up as to whether we are making sure that critical and security fixes are also going back to that branch, but I think the actual answer here is that we don't want to do that.16:18
eharneythat seems like confusion about what the driversfixes branches are for16:18
jungleboyjhemna:  No, the same thing we are doing.16:18
hemnadidn't we already try this a while back to allow driver devs to get whatever fixes we needed into old releases?16:18
hemna(which we still need badly)16:18
jungleboyjeharney:  Yeah, after I added this I realized that driverfixes is just for fixes to drivers and that we don't need to be putting other changes back there.16:19
eharneyyes, there is no commitment currently to handle security fixes or critical bug fixes there16:19
hemnadid we implement that plan ?16:20
hemnaor wasn't it shot down by the infra folks due to lack of CI ?16:20
jungleboyjOk, good.  Glad we aren't missing anything there.  I will carry that forward to Manila so we are all on the same page.16:20
bswartzthe reason I wanted to duplicate bugfixes in both branches is so that the 2 branches don't end up with conflicts16:20
jungleboyjhemna:  We did, that is the other reason I bring this up is as a reminder that that branch is there.16:20
hemnathe branch?16:20
bswartzdriverfixes should have everything stable has and more16:20
hemnameaning singular ?16:20
*** bobmel_ has joined #openstack-meeting16:20
eharneybswartz: i'm not sure that will happen since the driverfixes branches don't exist until after the regular stable branch has ended (iirc)16:20
hemnawe need the ability to fix bugs on each out of service release16:21
*** slaweq_ has joined #openstack-meeting16:21
eharneyhemna: we have driverfixes/mitaka and driverfixes/newton branches16:21
jungleboyjhemna:  Right.16:21
hemnaeharney, ok thanks16:21
bswartzeharney: there's a period when the both exist -- after the stable branch is closed to non-critical bugfixes but before the stable branch is gone16:21
*** cschwede has quit IRC16:21
hemnathat's what I was wondering16:21
*** bobmel has quit IRC16:21
jungleboyjhemna:  Sorry, I should be plural.16:21
eharneybswartz: ahh, true16:21
hemnaok I was getting confused16:21
hemnaI see the 2 driverfixes branches there in github now16:22
jungleboyjI understand why you are confused now.  Sorry.16:22
bswartzduring that period, everything that goes into stable should (IMO) go into driverfixes too16:22
hemnafor M and N16:22
hemnabswartz, +116:22
bswartzso driverfixes doesn't diverge from stable16:22
hemnais anyone doing that?16:22
jungleboyjbswartz:  Seems reasonable though I don't think people are taking the whole driverfixes branches.16:22
hemnaI presume we are managing those driverfixes/* branches manually now16:22
bswartzprobably not16:22
*** ricolin has quit IRC16:23
jungleboyjSo, do we agree that we should be pulling security and critical fixes back to the driverfixes branches?16:24
eharneyi'm not sure16:24
jungleboyjeharney:  Is RedHat using anything from those branches?16:24
jungleboyjAs are token distro rep.  ;-)16:24
eharneyjungleboyj: we use them as a place to have patches backported upstream that we can then cherry-pick from16:25
*** Sukhdev_ has quit IRC16:25
*** kaisers_ has quit IRC16:25
jungleboyjeharney:  And you are using it?16:25
*** qiangcao has joined #openstack-meeting16:25
bswartzso eharney wouldn't you be happier to have patches in driverfixes already rebased on top of any conflicting critical bug fixes from stable?16:25
eharneywe've used it once or twice, it hasn't been around long enough to see a lot of activity (newton surely will)16:26
jungleboyjbswartz: The changes should only be to drivers in those branches.16:26
eharneybswartz: probably, but my guess is that critical bug fixes are either going to be in-driver and backported there anyway, or not conflict16:26
*** Apoorva has joined #openstack-meeting16:26
eharneycritical bug fixes that conflict with other driver fixes are probably quite rare16:26
tbarroni have some concern about putting critical and security patches on branch that isn't tested16:26
jgriffithtbarron how come?16:27
tbarronmay imply "warrant" as it were to end users that isn't there16:27
hemnatbarron, we already went over this when we decided to do the driverfixes branching scheme16:27
hemnait's up to each dev that puts the patch up to test it16:27
eharneywe don't run all of the test jobs on driverfixes/* iirc16:27
bswartzI agree conflicts are unlikely, but because they're not impossible it seems worth protected against them by just doing the backports16:27
jungleboyjeharney:  Correct.16:27
tbarronhemna: jgriffith well I think that "infra" arg has more credibility w.r.t. critical and security fixes than for driver fixes :)16:27
hemnawe have no way of getting the CI systems to work, as infra refuses to tag/branch their code to keep it working against old stuffs16:27
bswartzwe're talking about a handful of extra cherrypicks16:28
*** Apoorva has quit IRC16:28
jungleboyjbswartz:  ++16:28
jgriffithtbarron I guess my point was I don't know why crit/sec fixes are any different than any change to the driver etc that we've already talked about?16:28
eharneybut we can't show that those cherrypicks for other critical fixes are properly tested16:29
jgriffithtbarron I mean; same rule applies right, change in driver/* only?16:29
tbarronjgriffith: are these *driver* crit/sec or core crit/sec that we rebase on?16:29
* tbarron may be confused16:29
hemnajgriffith, +116:29
jgriffithtbarron I thought we all agreed on no changes to the core code; it wouldn't be feasible/sustainable16:29
bswartztbarron: if you read the apache license you'll see very clearly we offer no warranty on our code16:29
jgriffithbecause in that model if you don't have gate testing this would NEVER EVER work16:30
jungleboyjjgriffith:  ++16:30
jgriffithbut maybe I'm wrong16:30
bswartzjgriffith: somebody has to test these patches -- just not the upstream community16:30
tbarronbswartz: that's why I used quotes, trying to indicate a concern about some weaker level of assurance16:30
bswartzwe rely on vendors and distros to ensure quality of driver bugfixes16:31
jgriffithI guess maybe I'm not being clear16:31
*** makowals has joined #openstack-meeting16:31
bswartzand you can be sure that vendors and distros are testing with a combination of all the security patches and the driver bugfixes in question16:31
jgriffithbswartz so if you provide a change to cinder/api/xxxx. are you going to test it against all 80 backend/drivers?16:31
bswartzso the point here is just to make cherrypicking easier16:31
jgriffithso that's not a great example... let's say cinder/volume/manger.py16:31
hemnabswartz, the person pushing the fix has to test it.16:31
hemnaand it's supposed the be the driver dev/owner anyway16:32
jungleboyjbswartz: I think what we are trying to say is that the cherry picks should only be under /volume/drivers so that shouldn't be an issue.16:32
bswartzjgriffith: such a patch would already have been tested when it went into stable16:32
bswartztaking in into driverfixes too causes no harm16:32
*** lhx__ has quit IRC16:32
jgriffithbswartz my experience in backporting/cherry-picking is very different than yours16:33
eharneybut it also doesn't seem to offer much benefit?16:33
bswartzeharney: the benefit is marginal16:33
jgriffiththe whole point of this was to be a place for driver fixes16:33
bswartzif you say you don't want it we can agree to not do this16:33
jgriffithnot core fixes etc16:33
jungleboyjbswartz:  I think that is what we originally agreed upon.16:34
jgriffithmy experience is that the further back you go with trying to backport/cherry-pick things the more difficult it is in terms of conflicts, missing things etc16:34
*** makowals has quit IRC16:34
bswartzthe specific case I have in mind is a security bug or critical bug in a driver that needs to merge to the stable branch after the driverfixes branch has been forked16:34
jgriffiththese are all just point in time snapshots remember16:34
*** armax has joined #openstack-meeting16:34
*** sshank has quit IRC16:35
*** sshank has joined #openstack-meeting16:35
jgriffithsay for example sec fix to Ocata that relies on something added in the object or rpc modules16:35
bswartzI agree it's kind of pointless to backport a bugfixes that doesn't touch any driver code to the driverfixes branch16:35
jgriffithyou try and backport that to Newton, but it turns out it relies on some special thing in the version that only exists in Ocata16:35
jungleboyjbswartz: So, I think we have the answer there.16:35
jungleboyjI would like to reach consensus and move on here if possible.16:36
jungleboyjSo, it sounds like the Cinder team is in agreement that we agreed to no core changes to the driverfixes branches.16:37
bswartzyeah I can agree to that too16:37
jungleboyjI don't feel a need to change that policy.16:37
*** dstanek has left #openstack-meeting16:37
jungleboyjbswartz:  Are are willing to keep that consistent in Manila?16:37
jungleboyj*Are you16:38
bswartzbut if there's a critical bugfix or security bugfix to a driver that goes into stable, it should *also* go into driverfixes16:38
jungleboyjbswartz:  I can agree with that.16:38
jungleboyjAny disagreements?16:38
eharneysounds good to me16:38
tbarronbswartz: how do you ensure that it happens though?16:38
tbarronvendors will be motivated to do their own patches to drivers16:39
jungleboyjtbarron:  That is going to be the core team's oversight and the driver maintainers should want to do that.16:39
bswartztbarron: I think it's in everyone's best interest16:39
jungleboyjbswartz: Agreed.16:39
tbarronI don't disagree: but it may take some vigilance.16:39
tbarronvendors will be motivated to do a quick dump of a local fix in driverfixes16:40
tbarronbut less motivated to do the due diligence.16:40
hemnadriver devs want the ability to backport fixes to older revs16:40
jgriffithwe could probably right a hook that prevents committing to the upper dirs16:40
jungleboyjhemna: ++16:40
*** dprince has quit IRC16:40
hemnathey are motivated  ( at least I was when I owned the 3par/lefthand drivers)16:40
tbarronand I think we thought there would be expedited review for driver fixes, right?16:40
*** Apoorva has joined #openstack-meeting16:41
eharneyexpedited in that there are fewer CI hoops, maybe16:41
tbarronI guess what I'm saying is that if I'm cherry-picking from driver-fixes and I want to be sure that16:41
tbarronI have all the crit/sec fixes as well I'm probably going to check the other branch anywways16:42
hemnaI think this would help out the various linux distro maintaners....16:42
e0nehemna: +116:42
eharneytbarron: yes16:42
jungleboyjhemna: ++16:42
tbarronbut I'm not objecting to tryinig to keep driver-fixes up to date when there is a correspondiing stable branch either.16:42
jungleboyjAnyway, lets not bikeshed on this further.16:42
jungleboyj#agreed No core changes to driverfixes branches16:43
jungleboyj#agreed security and critical drivers fixes should be backported to driverfixes16:43
jungleboyjAny disagreements there?16:43
tbarrononly when there is a corresponding stable branch, right?16:44
jgriffithjungleboyj but I want it to be fuscia in color!16:44
jungleboyjjgriffith: We are color blind.  Why do you care?16:44
jungleboyjtbarron: I wouldn't say that, any time the backport makes sense.16:44
jgriffithjungleboyj because somebody who's not may tell me they like the color :)16:44
jungleboyjjgriffith: :-p16:45
jungleboyjtbarron:  But obviously when there is a corresponding stable branch it is something we should enforce.16:45
jungleboyjMake sense>?16:45
tbarronsorry but now I think you're back to introducing risk when someone cherry-picks a driver fix16:46
jungleboyjtbarron:  Ok, lets chat about this in the channel afterwards.16:46
tbarronbecause of the issue jgriffith pointed out, you have a sec/crit fix that doesnt' work right in older release16:46
tbarronand it's not tested16:46
*** armstrong has joined #openstack-meeting16:47
jungleboyjI think we are going around in circles.16:47
* jgriffith has left the building16:47
jungleboyjLets move on for now.  I think what we have agreed on is good.  Should make sure it is documented somewhere.  We can further discuss details after the meeting.16:47
jungleboyjSo diablo_rojo  said she is not ready to talk about the config consolidation yet.  I will carry that forward to next week.16:48
*** unicell1 has quit IRC16:48
jungleboyj#topic Dynamic Reconfiguration16:48
*** openstack changes topic to "Dynamic Reconfiguration (Meeting topic: cinder)"16:48
*** slaweq_ has quit IRC16:48
*** hashar has quit IRC16:48
jungleboyjDid anyone try using SIGHUP with cinder not running in screen to see what happened?16:49
* jungleboyj hears crickets16:49
jungleboyjOk, so I tried this with devstack running in systemd and I saw that c-vol reacted to it but didn't re-read the config file.16:50
*** jkilpatr has quit IRC16:50
jungleboyjThere was some version pinning that was released but it didn't appear to do anything else.16:50
jungleboyjSo, I think we have more work to do in this space.16:50
e0neI tried to do it with newton or ocata in the past. not all config options were re-read after SIGHUP16:51
jungleboyjeharney:  You had suggested re-addressing the spec giving the changes that have happened since we originally wrote it.16:51
e0neI didn't have a chance to test with master last week16:51
jungleboyjI tested using the environment from our Upstream Institute.16:51
eharneyi'm interested in this, just haven't had a chance to poke at it yet16:52
jungleboyjeharney: e0ne  diablo_rojo  Thoughts on how to proceed?16:52
eharneyi think we should still proceed down the path that SIGHUP should reload config16:52
geguileoeharney: +116:53
jungleboyjeharney: +116:53
geguileoI agree SIGHUP reload config, not restart the whole service, right?16:53
jungleboyjgeguileo: ++16:53
eharneyis there a bug on this?16:54
jungleboyjSo, lets do this.  Hate to do this, but lets go back, look at the spec and update it based on that knowledge.16:54
jungleboyjeharney:  Good question.  Not that I know of.16:54
jungleboyjeharney: Do we want to handle it as a bug and abandon the spec?16:54
eharneynah, spec is fine for now16:54
tbarronI think the point of a bug would be to have a reproducer with the config that isn't getting reloaded16:55
e0newe have to figure out why cinder doesn't use code approach above ^^16:55
jungleboyjdiablo_rojo:  Can we go back to the spec, make sure it matches the work and keep going forward?16:55
diablo_rojoI will make those updates today.16:55
tbarronnot bug vs spec16:55
diablo_rojojungleboyj, yes16:55
tommylikehutbarron:  +116:56
jungleboyjtbarron: I will make sure we include in the spec the process that should work.16:56
*** efried is now known as efried_afk16:56
jungleboyjdiablo_rojo:  Thanks.  So, I think we have path forward there.  Thank you.16:56
*** spzala has quit IRC16:57
jungleboyj#action diablo_rojo  to update spec to ensure that SIGHUP causes reload of config.16:57
jungleboyjOk, I want to make sure we get to the last topic quickly in 3 minutes.16:57
*** spzala has joined #openstack-meeting16:57
jungleboyj#topic HA A/A Certification Criteria16:57
*** openstack changes topic to "HA A/A Certification Criteria (Meeting topic: cinder)"16:57
jungleboyjgeguileo:  Have we made any progress defining this?16:57
*** eric_young has joined #openstack-meeting16:58
geguileojungleboyj: I'm trying to close the multipath stuff16:58
geguileojungleboyj: just got my hands on a backend that does the discovery16:58
geguileoI should start working on that in 1 or 2 weeks16:58
jungleboyjgeguileo: Ok.  So, looks like this is something that may hang over into Queens?16:58
*** armstrong has quit IRC16:58
jungleboyjgeguileo:  Ok, so may still get traction yet in Pike?16:58
geguileoI should be able to get a good part of it done in P16:59
geguileobut it may drag on to Q16:59
jungleboyjgeguileo:  Ok.  Cool.  Just wanted to make sure it wasn't lost.16:59
jungleboyjpatrickeast:  You still on the hook to verify it?16:59
*** greghaynes has quit IRC16:59
jungleboyjI am hoping I will have a driver to run through the process with in Queens as well.16:59
geguileojungleboyj: I've been dying to get back to it  :-(16:59
jungleboyjgeguileo: Ok.  We have all priorities to juggle.17:00
jungleboyjIt sounds like we still have a plan and just need to keep executing.  Lets check back in a few weeks .17:00
jungleboyjAnd with that, time is up!17:00
jungleboyjLets take additional discussion over to the Cinder channel.17:01
* jungleboyj is looking at tbarron 17:01
jungleboyjThank you everyone for coming.17:01
*** openstack changes topic to "OpenStack Meetings ||"17:01
openstackMeeting ended Wed Jun 28 17:01:19 2017 UTC.  Information about MeetBot at . (v 0.1.4)17:01
openstackMinutes (text):
e0nesee you next week17:01
jungleboyje0ne:  Yes, might be a smaller group due to the 4th of July Holiday but I think we will still have the meeting.17:01
*** spzala has quit IRC17:02
*** e0ne has quit IRC17:03
*** armax has quit IRC17:03
*** bastafidli_ has joined #openstack-meeting17:04
*** jamesmcarthur has quit IRC17:04
*** electrofelix has quit IRC17:06
*** eric_young has quit IRC17:07
*** salv-orlando has quit IRC17:10
*** salv-orlando has joined #openstack-meeting17:10
*** lpetrut has quit IRC17:11
*** lpetrut has joined #openstack-meeting17:11
*** greghaynes has joined #openstack-meeting17:11
*** eusherek has joined #openstack-meeting17:12
*** spzala has joined #openstack-meeting17:12
*** xyang1 has quit IRC17:13
*** jamesmcarthur has joined #openstack-meeting17:13
*** salv-orlando has quit IRC17:15
*** spzala has quit IRC17:17
*** makowals has joined #openstack-meeting17:19
*** jamesmcarthur has quit IRC17:20
*** jamesmcarthur has joined #openstack-meeting17:20
*** diablo_rojo has quit IRC17:21
*** julim has quit IRC17:21
*** kaisers_ has joined #openstack-meeting17:21
*** neiljerram has quit IRC17:22
*** makowals has quit IRC17:22
*** ramineni_ has quit IRC17:23
*** trozet has joined #openstack-meeting17:26
*** lpetrut has quit IRC17:27
*** jamesdenton has joined #openstack-meeting17:28
*** Swami has joined #openstack-meeting17:30
*** Rockyg has quit IRC17:31
*** gouthamr has quit IRC17:34
*** toscalix has quit IRC17:35
*** diablo_rojo has joined #openstack-meeting17:36
*** jamemcc_ has joined #openstack-meeting17:36
*** annegentle has joined #openstack-meeting17:37
*** annegentle has quit IRC17:40
*** bh526r has joined #openstack-meeting17:40
*** sambetts is now known as sambetts|afk17:41
*** cody-somerville has joined #openstack-meeting17:41
*** cody-somerville has quit IRC17:41
*** cody-somerville has joined #openstack-meeting17:41
*** efried_afk is now known as efried17:42
*** csomerville has joined #openstack-meeting17:42
*** cody-somerville has quit IRC17:46
*** links has joined #openstack-meeting17:46
*** krenczewski has joined #openstack-meeting17:47
krenczewskiHi Bin17:48
*** jjmorman has joined #openstack-meeting17:48
*** unicell has joined #openstack-meeting17:49
*** sshank has quit IRC17:49
*** sshank has joined #openstack-meeting17:49
bh526rHi Kamil17:51
bh526rHow are you?17:51
bh526rI was reading some emails.17:51
krenczewskiGreat, no problem, have your time.17:51
*** andreas-f has quit IRC17:52
*** ekcs has joined #openstack-meeting17:53
*** jamesden_ has joined #openstack-meeting17:54
*** simon-AS559 has joined #openstack-meeting17:54
*** jamesdenton has quit IRC17:55
*** ekcs has quit IRC17:55
*** dprince has joined #openstack-meeting17:58
*** Apoorva_ has joined #openstack-meeting17:59
*** artom has quit IRC17:59
*** makowals has joined #openstack-meeting18:00
bh526r#startmeeting gluon18:00
openstackMeeting started Wed Jun 28 18:00:25 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: gluon)"18:00
openstackThe meeting name has been set to 'gluon'18:00
*** csaikia has left #openstack-meeting18:00
bh526r#topic Roll Call18:00
*** openstack changes topic to "Roll Call (Meeting topic: gluon)"18:00
bh526r#info Bin Hu18:00
*** spzala has joined #openstack-meeting18:01
*** jamesmcarthur has quit IRC18:01
bh526r#info Kamil Renczewski18:01
krenczewskiThanks :-)18:01
bh526rLooks like only you and I18:02
bh526rI see Jin's patch was updated18:02
*** hieulq__ has quit IRC18:02
bh526rand you submitted a new patch of doc18:02
*** kaisers_ has quit IRC18:02
bh526r#topic Pike status update18:02
*** kaisers_ has joined #openstack-meeting18:02
*** openstack changes topic to "Pike status update (Meeting topic: gluon)"18:02
*** Apoorva has quit IRC18:02
*** bobh has quit IRC18:03
bh526r#info Patch Update documentation for Contrail installation18:03
krenczewskiThis covers scenario from last summit18:04
bh526r#info There was one review and 2 comments18:04
bh526r#info regarding format18:05
*** spzala has quit IRC18:05
krenczewskiThis also assume that installation is done with docs from ContrailMechanismDriver repo18:05
krenczewskiI think that is all for now.18:05
bh526rI assume it covers 2 areas we discussed (1) detailed steps/instructions to install Contrail dependencies (2) config changes for Fuel18:06
krenczewskiI am working with Sukhdev on new mechanism driver.18:06
*** qwebirc11445 has joined #openstack-meeting18:06
jinli#info JinLi18:07
*** kaisers_ has quit IRC18:07
*** qwebirc11445 has quit IRC18:07
*** jkilpatr has joined #openstack-meeting18:09
*** bh526r_ has joined #openstack-meeting18:11
*** bh526r has quit IRC18:11
bh526r_sorry Kamil,18:11
bh526r_I lost Internet connection for a few minutes18:11
*** yamamoto has quit IRC18:11
krenczewskiNo problem18:11
bh526r_So I must have missed what you have typed after "Correct"18:12
*** eusherek has quit IRC18:12
*** eharney has quit IRC18:12
krenczewskiNothing ...18:12
bh526r_So just go ahead to fix the formatting comments and re-submit a new patch set18:13
*** yamahata has joined #openstack-meeting18:13
krenczewskiOK, will do this tomorrow18:13
bh526r_#info New patch covers (1) details of steps/instructions to install Contrail dependencies (2) config changes for Fuel18:13
bh526r_#info Kamil will work on a new patchset based on comments received18:13
bh526r_#info Next patch is Fix incorrect commands adding Gluon service to Keystone18:14
bh526r_#info Jin has taken care of all comments. Reviewer gave +118:15
*** eharney has joined #openstack-meeting18:15
bh526r_#info I suggest that if there is no further comments for next 24 hours, we approve and merge this patch18:15
bh526r_anything else from you Kamil?18:15
krenczewskiNothing more.18:16
jinliHi Bin, I am here18:16
jinliplease let me know any comments on that patch18:16
bh526r_Hi Jin18:16
*** kaisers_ has joined #openstack-meeting18:16
bh526r_Your patch looks good to me.18:16
bh526r_I leave for another 24 hours just in case Tin or someone may have comments.18:16
*** qiangcao has quit IRC18:17
bh526r_Otherwise, I will approve and merge it tomorrow18:17
jinliI am still working on the policy.json and, try to make the authorization work18:17
jinlisounds good to me.18:17
jinliwill ping Tin to review it18:17
bh526r_Great, and hopefully see your new patch soon :)18:17
bh526r_because Tin gave -1 before, so make sure he is happy now18:18
jinliyeah, agree18:18
*** eusherek has joined #openstack-meeting18:18
bh526r_#info Group agreed to approve and merge Jin's patch 474812 if no more comments in 24 hours18:19
bh526r_#info Jin is also working on the policy.json and, try to make the authorization work18:19
bh526r_any other update, Jin?18:19
jinlithat's all for me18:20
bh526r_If no more update, we can adjourn and go back to work, and Kamil enjoys evening18:20
bh526r_Thank you Kamil and Jin18:20
*** lpetrut has joined #openstack-meeting18:20
bh526r_#info No other update or item to discuss, meeting adjourned18:20
jinlibye Bin and Kamil18:20
*** Sukhdev_ has joined #openstack-meeting18:20
bh526r_Bye all18:21
*** kaisers_ has quit IRC18:22
*** bh526r_ has quit IRC18:22
*** reedip_out_of_ar has joined #openstack-meeting18:22
*** bh526r_ has joined #openstack-meeting18:25
*** bh526r_ has quit IRC18:25
*** andreas-f has joined #openstack-meeting18:25
*** annabelleB has quit IRC18:26
*** bh526r_ has joined #openstack-meeting18:26
*** links has quit IRC18:30
*** bh526r_ has quit IRC18:31
*** jamesmcarthur has joined #openstack-meeting18:32
*** julim has joined #openstack-meeting18:32
*** annabelleB has joined #openstack-meeting18:33
*** krenczewski has quit IRC18:33
*** janki has joined #openstack-meeting18:33
*** adisky__ has quit IRC18:34
*** jamesmcarthur has quit IRC18:37
*** bastafidli_ has quit IRC18:37
*** Sukhdev_ has quit IRC18:38
*** kaisers_ has joined #openstack-meeting18:38
*** jjmorman has quit IRC18:38
*** sshank has quit IRC18:42
*** sshank has joined #openstack-meeting18:42
*** kaisers_ has quit IRC18:42
*** spzala has joined #openstack-meeting18:43
*** kaisers_ has joined #openstack-meeting18:44
*** trozet has quit IRC18:48
*** arnewiebalck_ has joined #openstack-meeting18:49
*** ekcs has joined #openstack-meeting18:53
*** bastafidli_ has joined #openstack-meeting18:56
zara_the_lemur__anyone around for... the storyboard meeting????????????????????18:59
zara_the_lemur__the more question marks, the more excitement18:59
SotK#startmeeting storyboard19:00
openstackSotK: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.19:00
SotKwell then19:00
*** openstack changes topic to "OpenStack Meetings ||"19:00
openstackMeeting ended Wed Jun 28 19:00:58 2017 UTC.  Information about MeetBot at . (v 0.1.4)19:01
openstackMinutes (text):
*** reedip_out_of_ar has quit IRC19:01
SotK#startmeeting storyboard19:01
zara_the_lemur__aw, that was a good reason to not have a meeting xD19:01
openstackMeeting started Wed Jun 28 19:01:13 2017 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: storyboard)"19:01
openstackThe meeting name has been set to 'storyboard'19:01
zara_the_lemur__they're going to have some long logs...19:01
SotKsomewhere there is an agenda, I am unprepared today19:01
SotK#link Agenda19:02
zara_the_lemur__:) dw, I'm mainly attending because I feel chatty19:02
SotKI don't think we have any announcements or urgent items, so...19:02
SotK#topic In Progress Work19:02
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:02
zara_the_lemur__I fail at review :(19:03
zara_the_lemur__I have it on my todo list for tonight19:03
zara_the_lemur__I know diablo_rojo sent an update for the branches patch19:03
zara_the_lemur__which I have not yet looked at19:03
*** makowals has quit IRC19:03
zara_the_lemur__and I have my usual pile of boards patches to look at :)19:04
* SotK intends to write a response to the email from AJaeger tonight, and also look at how much work it will be to provide useful functionality there19:04
SotKsince I think it will solve some other problems too19:04
zara_the_lemur__yeah, 'bug templates', right?19:04
zara_the_lemur__I like the idea of it and am not volunteering to do it because I'm already behind with my commitments19:05
zara_the_lemur__so I'm pleased that you want to work on it19:05
zara_the_lemur__(for my own part, I'm not going to look at coding anything until I get more on top of review)19:06
SotK(the logic with bug templates being, a similar feature will let people provide links to a pre-filled story submission modal, which is basically a template)19:06
fungi#link Report a bug and storyboard19:07
SotKthanks fungi19:07
*** rderose has quit IRC19:07
fungitook me a moment to dig it back out of my history19:07
*** Apoorva_ has quit IRC19:08
fungithanks for following up there19:09
*** krtaylor has quit IRC19:09
*** andreas-f has quit IRC19:09
zara_the_lemur__I don't have any other in-progress things to note myself19:09
SotKyw :)19:09
SotKhey diablo_rojo19:09
*** kaisers_ has quit IRC19:10
fungia more generalized option might be to allow story creation to take an arbitrary title and description and whatnot provided via get parameters, and just expect the client to get prompted to athenticate to sb via openid first or something19:10
fungibut not worry about making it possible to specify arbitrary subfields within the description and just leave that up to the caller19:11
*** simon-AS559 has quit IRC19:11
*** peterlisak has quit IRC19:11
*** onovy has quit IRC19:11
*** yamamoto has joined #openstack-meeting19:12
fungigranted the templates stuff would be more elegant and reusable within the webui for new story submissions which come in without such prior context19:12
SotKyeah, the ability to have reuse there was what I was hoping for19:13
*** jamesmcarthur has joined #openstack-meeting19:13
*** tesseract has quit IRC19:13
SotKthough, I see how both approaches could be useful19:13
* SotK may look at both19:13
persiaContinuing to allow the API to submit arbitrary description content (regardless of subfields), even if the webui allows subfield templating seems safer to me, especially for folk who are already using alternate clients and may be surprised by new validation changes on description input from the API.19:14
SotKI wasn't planning on any change to validation, just the ability to pre-fill the description field for folk who use a particular URL to create a story19:15
SotKthis could have the issue of a bunch of stories with useless content in the description though19:15
fungiif people don't edit them before saving, i guess19:15
persiaThat's a natural side effect of the template clients (and has widely been seen in other trackers).  That a later triager could edit it to be less verbose makes this less painful than some systems that hardcode all the possible subfields.19:16
*** yamamoto has quit IRC19:16
SotKyeah, I expect it would be rare, but I can see it not being impossible someone would see the field with words in and be like "oh automatic description, *submit*"19:17
*** makowals has joined #openstack-meeting19:17
*** Guest28796 is now known as mgagne19:19
*** mgagne has quit IRC19:19
*** mgagne has joined #openstack-meeting19:19
SotKanything else in progress?19:19
*** rbartal has quit IRC19:20
SotK#topic Open Discussion19:21
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:21
diablo_rojoSotK, just that patch I've had around forever. I updated things. It should be good to go I think..19:21
SotKoh yeah, I saw you updated that and was meaning to take a look, thanks!19:21
diablo_rojoSotK, thank you!19:21
*** annabelleB has quit IRC19:22
diablo_rojoStil haven't heard the 'go ahead' from the projects I've reached out to. Kind of waiting to hear back from them currently.19:22
diablo_rojoI replied to one email with questions with some help from the wonderful fungi but that's all I've seen.19:23
* zara_the_lemur__ hasn't looked at the etherpads; wonders if there's anything there19:23
*** xyang1 has joined #openstack-meeting19:23
* diablo_rojo never had the links to them in the first place19:24
*** dbecker has quit IRC19:24
diablo_rojoI have been listening in on Tripleo's meetings and answering questions where I can with them19:24
zara_the_lemur__iirc someone linked one on the list once, will see if I can dig them up.19:24
*** annabelleB has joined #openstack-meeting19:25
*** sshank has quit IRC19:25
*** slaweq_ has joined #openstack-meeting19:26
diablo_rojoDoesn't look like anything new19:26
diablo_rojoThanks for the link zara_the_lemur__ !19:26
zara_the_lemur__yw :)19:27
zara_the_lemur__yeah, I see nothing dramatic there19:28
* SotK neither19:28
*** annabelleB has quit IRC19:28
*** arnewiebalck_ has quit IRC19:29
*** annabelleB has joined #openstack-meeting19:30
*** annabelleB has quit IRC19:30
*** awaugama has quit IRC19:31
*** markstur has quit IRC19:32
SotKanything else or shall we end this meeting here?19:32
diablo_rojoI dont think so but to plead for reviews :)19:33
*** baoli has quit IRC19:34
* SotK will get on it :)19:34
*** openstack changes topic to "OpenStack Meetings ||"19:34
openstackMeeting ended Wed Jun 28 19:34:25 2017 UTC.  Information about MeetBot at . (v 0.1.4)19:34
openstackMinutes (text):
fungithanks everyone!19:35
*** emagana has joined #openstack-meeting19:41
*** salv-orlando has joined #openstack-meeting19:44
*** simon-AS559 has joined #openstack-meeting19:46
*** ayoung has quit IRC19:48
*** julim has quit IRC19:50
*** simon-AS5591 has joined #openstack-meeting19:51
*** simon-AS559 has quit IRC19:51
*** andreas-f has joined #openstack-meeting19:55
*** chyka has quit IRC19:55
*** pnavarro has quit IRC19:56
*** chyka has joined #openstack-meeting19:57
*** pnavarro has joined #openstack-meeting19:57
*** pnavarro has quit IRC19:57
*** pnavarro has joined #openstack-meeting19:57
*** xyang1 has quit IRC19:59
*** ekhugen_alt has joined #openstack-meeting20:00
ekhugen_alt#startmeeting wos_mentoring20:00
openstackMeeting started Wed Jun 28 20:00:17 2017 UTC and is due to finish in 60 minutes.  The chair is ekhugen_alt. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: wos_mentoring)"20:00
openstackThe meeting name has been set to 'wos_mentoring'20:00
ekhugen_altHi who's here for women of openstack mentoring20:00
*** MeganR has joined #openstack-meeting20:00
diablo_rojoHello :)20:01
diablo_rojoThanks for the new invite I just saw now lol :)20:01
ekhugen_altHi Kendall, Hi Megan!20:01
*** emagana has quit IRC20:01
ekhugen_altI think Nicole is off at Intel Kid's day so she won't be on20:01
diablo_rojoOh fun :)20:02
*** kaisers_ has joined #openstack-meeting20:03
*** felipemonteiro__ has quit IRC20:03
ekhugen_altso I think we had a few topics from last week:  1. sydney planning if amrith was on 2. restructuring the long term mentoring program so there are fewer no shows and 3. restructuring mentor/mentee check ins so they're more helpful20:04
diablo_rojoSounds right to me :)20:05
MeganRok, I need to mention that I have a hard stop in 30 min - sorry20:05
ekhugen_altso #topic restructuring the long term mentoring program20:05
ekhugen_alt#topic restructuring the long term mentoring program20:05
*** openstack changes topic to "restructuring the long term mentoring program (Meeting topic: wos_mentoring)"20:05
* ekhugen_alt forgets her irc commands have to come at the beginning of typing20:05
ekhugen_altlast week the discussion was that maybe we should check in more often with mentors/mentees (once every 2 months?) and instead of just an "are you there?" email, make it more helpful to the relationship20:06
*** sshank has joined #openstack-meeting20:07
MeganRmore helpful as in checking to see how things are working, are we looking for specific feedback?20:07
*** peterlisak has joined #openstack-meeting20:08
ekhugen_altMeganR I think the idea is can we do something in the checkin to help the mentor/mentee grow their relationship20:08
ekhugen_altinstead of just "reply if you're still meeting"20:08
MeganRThat makes a lot of sense20:09
*** onovy has joined #openstack-meeting20:09
ekhugen_alton the flip side, keeping track of who's still in the program, giving people a reasonable buffer for vacation/sickness before we kick them out, rematching, etc eats up a lot of time, so we also have to make that easier20:09
*** bastafidli_ has quit IRC20:09
*** bastafidli_ has joined #openstack-meeting20:10
*** julim has joined #openstack-meeting20:10
*** dimtruck is now known as zz_dimtruck20:13
*** yamamoto has joined #openstack-meeting20:14
*** ericyoung has quit IRC20:15
ekhugen_altso, any ideas on either problem?20:15
diablo_rojoIts difficult to minimize work on our end and make it a meaningful and useful for them.20:15
diablo_rojoI think the reply if you are still meeting is a good way to go20:15
ekhugen_altcould we turn it around and say they need to check in with us?20:16
diablo_rojo2 months I think is a good time period unless we want to switch off who is checking in to lighten the load on us20:16
diablo_rojoWe could. It might be harder for them to remember though?20:16
diablo_rojoI like that it gives us a lot lighter load :)20:17
ekhugen_altthat's true20:17
ekhugen_altcan we give them fewer chances?  like not a three strikes policy but like a one strike policy?20:17
ekhugen_alt"if you don't reply in 7 days we unmatch you" or is that too harsh from a perspective of vacation, etc?20:18
MeganRare we ccing the mentor as well - could either respond that they are active20:18
ekhugen_altyes, I think it's been okay for either to respond20:20
ekhugen_althonestly we've had as much trouble with mentors as mentees being MIA20:21
*** bastafidli_ has quit IRC20:21
diablo_rojoIn my experience finite numbers and due dates are incredibly helpful.20:21
MeganRthen I think 7 days is fine, true both could be on vacation at the same time, but the chances are better of having one respond in that time20:22
MeganRtotally agree on the finite dates!20:22
diablo_rojoYeah either one can respond and we'd call it good20:22
*** jamesmcarthur has quit IRC20:23
*** yamamoto has quit IRC20:23
*** pnavarro has quit IRC20:24
*** emagana has joined #openstack-meeting20:24
*** Apoorva has joined #openstack-meeting20:25
ekhugen_althow often do we want to do these heartbeat checks?  I think the past round we asked them to respond when they got matched, then asked them a couple months later if they were still meeting?20:25
ekhugen_alt^ heartbeat check = does the mentoring relationship have a pulse or not20:25
*** jamesmcarthur has joined #openstack-meeting20:25
MeganRI think 2 months is good20:26
diablo_rojoI'd say at start and every 2 months20:26
diablo_rojoGraduation at a year?20:26
ekhugen_altI think we'd talked last week about either 6 months or a year, so yes, that works20:30
ekhugen_altMeganR do you need to leave now, should we table discussion to next meeting?20:30
MeganRSorry, I need to drop - we can table it, or I can also review the meeting notes20:31
*** MeganR has quit IRC20:31
diablo_rojoI'm flexible :)20:31
ekhugen_altwe can keep talking if you have more ideas diablo_rojo I'm guessing we won't come to any conclusions until we have a few more people on20:32
*** krtaylor has joined #openstack-meeting20:33
diablo_rojoDo we want to start clearing up the form to sign up?20:34
diablo_rojoIf not we can wait20:34
ekhugen_altI think last week we talked about taking out preferred working style, how often they want to meet, communication style preference?20:35
*** coolsvap has quit IRC20:36
*** torgomatic has joined #openstack-meeting20:37
*** zz_dimtruck is now known as dimtruck20:37
*** raildo has quit IRC20:39
*** jprovazn has quit IRC20:41
*** slaweq_ has quit IRC20:43
ekhugen_altokay, tabling to 2 weeks from now, since next week is a US holiday on Tuesday20:45
*** openstack changes topic to "OpenStack Meetings ||"20:45
openstackMeeting ended Wed Jun 28 20:45:25 2017 UTC.  Information about MeetBot at . (v 0.1.4)20:45
openstackMinutes (text):
diablo_rojothanks ekhugen_alt !20:47
*** sshank has quit IRC20:47
*** ekhugen_alt has left #openstack-meeting20:48
*** bcafarel has joined #openstack-meeting20:48
*** Swanson has quit IRC20:48
*** markstur has joined #openstack-meeting20:49
*** bkero has quit IRC20:49
*** bkero has joined #openstack-meeting20:50
*** annabelleB has joined #openstack-meeting20:50
*** iyamahat has joined #openstack-meeting20:54
*** markstur has quit IRC20:54
*** julim has quit IRC20:54
*** hagridaaron has quit IRC20:55
*** hagridaaron has joined #openstack-meeting20:57
*** dprince has quit IRC20:57
*** baoli has joined #openstack-meeting20:58
*** felipemonteiro has joined #openstack-meeting21:00
*** pcaruana has quit IRC21:01
*** julim has joined #openstack-meeting21:03
*** eusherek has quit IRC21:03
*** cloudrancher has quit IRC21:03
*** youzp has joined #openstack-meeting21:04
*** cloudrancher has joined #openstack-meeting21:04
*** hagridaaron has quit IRC21:05
*** Sukhdev has quit IRC21:05
*** makowals has quit IRC21:06
*** felipemonteiro_ has joined #openstack-meeting21:07
*** youzp has quit IRC21:08
*** aeng_ has joined #openstack-meeting21:09
*** felipemonteiro has quit IRC21:10
*** markstur has joined #openstack-meeting21:12
*** thorst has quit IRC21:12
*** bastafidli_ has joined #openstack-meeting21:12
*** makowals has joined #openstack-meeting21:15
*** eusherek has joined #openstack-meeting21:16
*** jamesmcarthur has quit IRC21:16
*** kylek3h has quit IRC21:17
*** julim has quit IRC21:18
*** makowals has quit IRC21:19
*** baoli has quit IRC21:21
*** cloudrancher has quit IRC21:23
*** cloudrancher has joined #openstack-meeting21:24
*** eharney has quit IRC21:26
*** esberglu has quit IRC21:27
*** slaweq_ has joined #openstack-meeting21:31
*** caboucha has quit IRC21:32
*** iyamahat_ has joined #openstack-meeting21:33
*** iyamahat has quit IRC21:33
*** askb has joined #openstack-meeting21:36
*** qiangcao has joined #openstack-meeting21:37
*** fnaval has quit IRC21:38
*** fnaval has joined #openstack-meeting21:38
*** emagana has quit IRC21:39
*** emagana has joined #openstack-meeting21:39
*** lpetrut has quit IRC21:40
*** bastafidli_ has quit IRC21:40
*** felipemonteiro_ has quit IRC21:41
*** jamesmcarthur has joined #openstack-meeting21:41
*** felipemonteiro_ has joined #openstack-meeting21:41
*** sshank has joined #openstack-meeting21:42
*** emagana has quit IRC21:43
*** andreas-f has quit IRC21:44
*** thorst has joined #openstack-meeting21:46
*** VW_ has joined #openstack-meeting21:47
*** zaitcev has joined #openstack-meeting21:47
*** zaitcev has left #openstack-meeting21:47
*** fnaval has quit IRC21:48
*** thorst has quit IRC21:50
*** jchhatbar has joined #openstack-meeting21:50
*** VW has quit IRC21:50
*** janki has quit IRC21:51
*** ykatabam has joined #openstack-meeting21:51
*** VW_ has quit IRC21:51
*** esberglu has joined #openstack-meeting21:52
*** markstur has quit IRC21:55
*** esberglu has quit IRC21:57
*** jamesmcarthur has quit IRC21:59
*** jamesmcarthur has joined #openstack-meeting21:59
*** jamesmcarthur has quit IRC22:01
*** jamesmcarthur has joined #openstack-meeting22:01
*** rbudden has quit IRC22:04
*** iyamahat_ has quit IRC22:05
*** mriedem has joined #openstack-meeting22:09
*** eusherek has quit IRC22:09
*** thorst has joined #openstack-meeting22:10
*** jchhatbar has quit IRC22:10
*** salv-orl_ has joined #openstack-meeting22:14
*** emagana has joined #openstack-meeting22:16
*** thorst has quit IRC22:17
*** thorst has joined #openstack-meeting22:17
*** salv-orlando has quit IRC22:18
*** simon-AS5591 has quit IRC22:20
*** annabelleB has quit IRC22:20
*** thorst has quit IRC22:22
*** annabelleB has joined #openstack-meeting22:22
*** bobh has joined #openstack-meeting22:24
*** slaweq_ has quit IRC22:26
*** Julien-zte has joined #openstack-meeting22:30
*** slaweq_ has joined #openstack-meeting22:31
*** bobh has quit IRC22:31
*** slaweq_ has quit IRC22:32
*** krtaylor has quit IRC22:35
*** chyka has quit IRC22:37
*** chyka has joined #openstack-meeting22:39
*** annabelleB_ has joined #openstack-meeting22:42
*** annabelleB has quit IRC22:42
*** annabelleB_ is now known as annabelleB22:42
*** emagana has quit IRC22:47
*** emagana has joined #openstack-meeting22:48
*** mtanino__ has quit IRC22:48
*** gouthamr has joined #openstack-meeting22:51
*** ricolin has joined #openstack-meeting22:51
*** bknudson has quit IRC22:51
*** emagana has quit IRC22:52
*** gouthamr has quit IRC22:54
*** egallen has quit IRC22:55
*** annabelleB has quit IRC22:56
*** spzala has quit IRC22:56
*** salv-orl_ has quit IRC22:59
*** ykatabam has quit IRC23:02
*** mriedem has quit IRC23:02
*** annabelleB has joined #openstack-meeting23:04
*** felipemonteiro_ has quit IRC23:05
*** iyamahat_ has joined #openstack-meeting23:10
*** dimtruck is now known as zz_dimtruck23:10
*** spzala has joined #openstack-meeting23:11
*** spzala has quit IRC23:16
*** annabelleB has quit IRC23:16
*** edmondsw has quit IRC23:19
*** ykatabam has joined #openstack-meeting23:21
*** ricolin has quit IRC23:23
*** amotoki is now known as amotoki_away23:23
*** chyka has quit IRC23:25
*** spzala has joined #openstack-meeting23:28
*** sshank has quit IRC23:32
*** Julien-zte has quit IRC23:36
*** bobh has joined #openstack-meeting23:40
*** bobh has quit IRC23:43
*** hongbin has quit IRC23:44
*** jamesmcarthur has quit IRC23:45
*** emagana has joined #openstack-meeting23:48
*** jamesmcarthur has joined #openstack-meeting23:51
*** emagana has quit IRC23:52
*** annabelleB has joined #openstack-meeting23:56
*** ramineni_ has joined #openstack-meeting23:56

Generated by 2.15.3 by Marius Gedminas - find it at!