Thursday, 2017-04-27

*** hongbin has quit IRC00:33
*** markstur has quit IRC00:41
*** markstur has joined #openstack-manila00:42
*** markstur has quit IRC00:46
*** gouthamr has joined #openstack-manila00:46
*** kaisers has quit IRC01:37
*** gcb has joined #openstack-manila01:38
*** gouthamr has quit IRC01:42
*** chenying__ has joined #openstack-manila01:55
*** chenying_ has quit IRC01:55
openstackgerritzhongjun proposed openstack/manila-specs master: Allow to filter resources by inexact value matching in 'list' APIs  https://review.openstack.org/44777501:56
*** zhugaoxiao has quit IRC02:10
*** chlong has joined #openstack-manila02:48
*** gouthamr has joined #openstack-manila02:51
*** tuanluong has joined #openstack-manila03:36
*** gouthamr has quit IRC04:01
*** kaisers has joined #openstack-manila04:01
*** dsariel has joined #openstack-manila04:04
*** MikeG451 has quit IRC04:07
*** arnewiebalck_ has joined #openstack-manila04:13
*** MikeG451 has joined #openstack-manila04:20
*** markstur has joined #openstack-manila04:35
*** kaisers has quit IRC04:39
*** kaisers has joined #openstack-manila05:09
*** kaisers_ has joined #openstack-manila05:14
*** arnewiebalck_ has quit IRC05:15
*** kaisers has quit IRC05:15
*** rraja has joined #openstack-manila05:28
openstackgerritShubhendu Poothia proposed openstack/manila master: Set access_policy for messaging's dispatcher  https://review.openstack.org/45994405:29
*** digvijay2016 has joined #openstack-manila05:53
*** mkoderer_ has joined #openstack-manila06:25
*** tpatzig_ has joined #openstack-manila06:25
*** mkoderer_ has quit IRC06:27
*** tpatzig_ has quit IRC06:27
*** markstur has quit IRC06:28
*** jprovazn has joined #openstack-manila06:40
*** pcaruana has joined #openstack-manila06:44
*** tuanluong has quit IRC07:51
*** tuanluong has joined #openstack-manila08:12
*** makowals_ has quit IRC08:39
*** tuanluong has quit IRC08:42
*** lpetrut has joined #openstack-manila08:50
*** a-pugachev has joined #openstack-manila08:51
*** makowals has joined #openstack-manila08:52
*** makowals has quit IRC09:04
*** MikeG451 has quit IRC09:19
*** MikeG451 has joined #openstack-manila09:33
*** rraja has quit IRC09:55
*** lpetrut_ has joined #openstack-manila09:58
*** ociuhandu has quit IRC09:59
*** lpetrut has quit IRC10:00
*** ganso has joined #openstack-manila10:40
tommylikehuping jprovazn10:42
jprovazntommylikehu, hi10:42
tommylikehuyeah, do you have any idea on this patch?10:43
tommylikehuabout the user message10:44
tommylikehuI think I should not paste the link here :)10:44
jprovazntommylikehu, I think it's fine as it is, my previous comment was invalid. I was updating manila's patch today and if I don't find an obstacle then +1 from me (well, Eric added a comment)10:46
tommylikehuthanks10:46
tommylikehujprovazn you mean Eric added a comment on which one?10:49
jprovaznhttps://review.openstack.org/#/c/448384/14/cinder/volume/manager.py10:50
jprovazntommylikehu, ^10:50
tommylikehuwow, he is right :)10:52
*** makowals has joined #openstack-manila11:15
*** zhonghua has quit IRC11:23
*** zhonghua has joined #openstack-manila11:23
*** kaisers_ has quit IRC11:29
*** rraja has joined #openstack-manila11:29
*** kaisers has joined #openstack-manila11:30
*** kaisers has quit IRC11:34
*** kaisers has joined #openstack-manila11:41
*** digvijay2016 has quit IRC11:42
*** dsariel has quit IRC12:01
openstackgerritTom Barron proposed openstack/manila master: coordination: use tooz builtin heartbeat feature  https://review.openstack.org/46052212:01
*** dgonzalez has quit IRC12:02
*** dgonzalez has joined #openstack-manila12:07
*** zhonghua has quit IRC12:09
*** zhonghua has joined #openstack-manila12:10
*** ociuhandu has joined #openstack-manila12:25
openstackgerritzhongjun proposed openstack/manila-specs master: Add spec for gathering share usage size  https://review.openstack.org/45915012:28
*** dustins has joined #openstack-manila12:31
*** dsariel has joined #openstack-manila12:39
*** zhonghua has quit IRC12:53
*** zhonghua has joined #openstack-manila12:53
*** catintheroof has joined #openstack-manila13:17
*** zengyingzhe has quit IRC13:25
*** zengyingzhe has joined #openstack-manila13:26
*** dsariel has quit IRC13:33
*** eharney has joined #openstack-manila13:38
bswartzzhongjun: what other projects rely on memcached?13:44
tommylikehubswartz: keystone and nova?13:47
bswartztommylikehu: do those projects have memcached as a hard requirement or a soft requirement?13:47
*** ubijtsa is now known as assassin13:49
tommylikehubswartz: not sure, let't check their documentation or just wait her online13:50
tommylikehubswartz: doesn't like a hard requirement for keystone13:53
tommylikehuhttps://docs.openstack.org/developer/keystone/configuration.html#caching-layer13:53
*** xyang_ has joined #openstack-manila13:58
*** xyang_ has quit IRC14:00
*** hongbin has joined #openstack-manila14:13
*** dsariel has joined #openstack-manila14:17
*** gouthamr has joined #openstack-manila14:31
*** xyang_ has joined #openstack-manila14:31
*** lpetrut_ has quit IRC14:40
*** darrenc has quit IRC14:43
zhongjunbswartz:  It does not  a hard requirement  for nova and keystone14:45
zhongjunbswartz: But openstack recommend to use memcached in nova and keystone14:46
zhongjunbswartz: memcached is set to default in devstack14:46
zhongjunbswartz: and it also used in heat and horizon14:50
bswartzzhongjun:  soft or hard requirement for those projects?14:51
zhongjunbswartz: soft14:52
*** jmlowe has quit IRC14:52
bswartzzhongjun: can we ensure that manila has a soft requirement too? perhaps make usage monitoring completely optional?14:53
bswartzI would like it if by default it's not turned on, and the administrator needs to specifically enable it -- this will avoid any breakage during upgrades14:54
tbarronzhongjun: not related to the hard/soft dependency - though I agree it's an important issue -14:54
tbarronwikipedia says: The servers keep the values in RAM; if a server runs out of RAM, it discards the oldest values. Therefore, clients must treat Memcached as a transitory cache; they cannot assume that data stored in Memcached is still there when they need it. Other databases, such as MemcacheDB, Couchbase Server, provide persistent storage while maintaining Memcached protocol compatibility.14:54
zhongjunbswartz: yes, now, we make usage monitoring completely optional in the spec14:55
tbarronzhongjun: are you planning a fallback to a driver call if there's a cache miss?14:55
tbarronzhongjun: not an objection, just a design aspect to be thought through.14:56
bswartzzhongjun: might want to add some comments in "other deployer impact" about what an admin needs to do to turn on the feature after an upgrade from ocata to pike, or after a fresh install of pike14:56
zhongjuntbarron: yeah, we could do it like the other project14:57
bswartztbarron: that's a good point -- if memcached is acting as a cache only and not an authoritative data source then we need an authoritative data source somewhere14:57
*** cknight has joined #openstack-manila14:57
tbarronAnd if we're going to have a slower-path lookup if the cache entry is missing maybe we can still get usage if the whole cache itself is not present as well.14:58
*** xyang_ has quit IRC14:59
zhongjunbswartz:  sure14:59
bswartzyeah that argues for only implemented the slow path if the first implementation and leaving caching as an optimization for future releases14:59
bswartzit's not clear to me that an optimization would be required at all for our use case15:00
tbarronI could see a cloud operator who just wants to know usage once a day doing a lot of little queries over the course of the day, driven by some automatioon outside manila instead of running the periodic task that grabs usages for all shares on the backend at once.15:00
bswartzalright let's start the meeting15:00
tbarronzhongjun does allow for not running the periodic task at cloud ops discretion15:00
bswartz--> #openstack-meeting-alt <--15:00
*** xyang_ has joined #openstack-manila15:01
*** pcaruana has quit IRC15:05
*** zhonghua has quit IRC15:07
*** zhonghua has joined #openstack-manila15:08
*** zigo has quit IRC15:17
*** rraja has quit IRC15:29
*** makowals has quit IRC15:50
openstackgerritMerged openstack/manila-specs master: Allow to filter resources by inexact value matching in 'list' APIs  https://review.openstack.org/44777515:55
bswartztbarron: did it spawn more than 1?16:00
gansolol I cannot avoid laughing when someone talks about a project named gnochi16:00
bswartzganso: ikr? worst project name ever16:01
tbarronbswartz: there's time series data project (gnocchi), alarms/notifications project (aodh)16:03
tbarronI could see admin's wanting an alarm if a share passes a size threshold.16:03
tbarronAnd doing reports on distribution of share utilizations over time series, plotting utilization and nominal size against time and classes of users.16:04
bswartztbarron: if we emit the data properly though, aren't all those things possible without further changes to manila?16:05
*** eharney has quit IRC16:05
*** makowals has joined #openstack-manila16:05
*** xyang_ has quit IRC16:06
zhongjunbswartz:  If we  store info in db or other place,   gathering usage size from memcached will reduce the interaction and16:07
zhongjun  improve the performance when we have multiple manila share service nodes16:07
*** chlong_ has joined #openstack-manila16:08
bswartzzhongjun: the proposal is that we transmit the data to other services and let them store the data -- performance then depends on how those other projects implement storage16:08
bswartzif ceilometer or gnocchi uses memcached already, then perhaps it's very efficient to retrieve data from them16:09
tbarronzhongjun: so if we have active-active share service, or multiple share server processes on one active node for multiple backends, does emitting to another consumer have a problem?16:10
tbarronin the active active case one could optimize and elect a leader for this kind of thing.16:10
tbarronor just let all active services announce.16:11
tbarronwe have a similar issue with active-active for updates to the scheduler.16:11
zhongjunbswartz:  so I just store it in memcatch.   If we send huge shares info to ceilmetor by API or RPC...  It will not have performance problem?16:11
bswartzzhongjun: memcache isn't a stable storage system -- it's lossy by design16:12
bswartzzhongjun: memcached must have some kind of stable storage behind it16:12
bswartzsending the data to another service using the notifications framework is likely to be as efficient as any other solution16:13
zhongjunbswartz: the notifications framework?16:13
*** chlong_ has quit IRC16:14
*** makowals has quit IRC16:14
tommylikehumake manila depended on well known software is better than a openstack project.16:14
*** makowals has joined #openstack-manila16:15
*** jmlowe has joined #openstack-manila16:17
*** makowals has quit IRC16:17
bswartztommylikehu: the problem I see is that we can't implement this inside manila without duplicating functionality already in other projects like ceilometer16:18
*** eharney has joined #openstack-manila16:18
bswartzefficiently storing time-series data is not the hardest problem in the world, but they've solved it already and we haven't16:19
bswartzwhy would we (a small dev team) take on that problem when others in openstack ecosystem have a solution we can use?16:19
bswartzzhongjun: read vkmc's spec about ceilometer integration16:19
bswartzI'm fuzzy on the details but the mechanism to emit data from any project to ceilometer is relatively lightweight and easy to use as I understand it16:20
tommylikehubswartz:  Idon't like the idea to use ceilmeter or any time series databse, if memcache is not good enough for our case, then try to replace it with a simple one16:21
bswartztommylikehu: I have good news then -- the mechanism we would use to emit data to ceilometer is pluggable, and if ceilometer is undesirable then it should be possible to plug in any other storage solution16:23
bswartzthe key is that it makes sense for manila to collect this data, but not to store or retrieve it -- we should leave that to an external thing (could be ceilometer, could be anything else)16:23
bswartzthe core of the objection here is that we don't want to increase manila's scope beyond what we already do and just collecting and emiting this data16:24
bswartzif we store the data and provide an API to retrieve it then that's a significant new responsibility that comes with various problems to solve16:25
tbarrontommylikehu: I know you won't have usage data to collect for cinder, but isn't there some data for cinder that a cloud admin might want to look at16:25
tbarronwhile looking at manila data for the same users?16:25
bswartzthe problems were mentioned during the meeting: how to deal with data staleness/inaccuracy, how to store and retrieve the data compactly/efficiently16:25
tbarrontommylikehu: that argues for both cinder and manila sending their data to a third party.16:26
bswartzalso the lower level question of how to handle cases when the feature is turned off or the backend doesn't support collection16:27
zhongjunbswartz: ok, I will.16:28
bswartzthe best argument that I heard during the meeting was that this data is inherently volatile, and manila currently doesn't store anything volatile16:28
tommylikehubswartz:  store that info into a seperate database table as a default and provide a better experience when configured with redis or memcache16:29
zhongjunbswartz:  We could store even if we doesn't store now. :)16:29
bswartztommylikehu: I think you're still missing the point of the argument -- manila should not expose this kind of data directly through our REST interface -- it's not a storage issue or a performance issue16:30
bswartzI mean those things do matter, but even if they didn't, the core of the problem is the kind of data we're collecting16:30
tommylikehubswartz:  ok16:31
*** gouthamr has quit IRC16:31
bswartzthey're volatile values, and they should be consumed differently that other aspects of the shares16:31
bswartzlike CPU usage of a nova VM16:31
bswartzit's a number that changes over time16:32
bswartzif the number is too old, it might be wildly inaccurate16:32
bswartzthis kind of data greatly benefits from historical storage too16:32
bswartznothing else in manila would16:33
bswartzwe're not going to build a historical usage table into manila just for this feature -- it's been done well elsewhere16:33
bswartzif your argument is against ceilometer/gnocchi, then the mechanism we would use to integrate with them can also be used to integrate with something far simpler16:34
bswartzthe point is to push the storage/retrieval parts of the problem outside of manila16:34
bswartzso keep manila's scope small and focused16:34
bswartzs/so/to/16:34
tommylikehubswartz:  I am happy with ceilometer not required:)16:35
zhongjunbswartz: If we add a new third part software to collect usage size,  if can be work after we need to add some code in manila to send usage size info to software?16:37
zhongjuns /if /it16:37
*** gouthamr has joined #openstack-manila16:40
*** ociuhandu has quit IRC16:48
*** a-pugachev has quit IRC16:53
*** jprovazn has quit IRC17:01
*** xyang_ has joined #openstack-manila17:04
*** harlowja has quit IRC17:08
*** arnewiebalck_ has joined #openstack-manila17:10
*** jmlowe has quit IRC17:16
*** jmlowe has joined #openstack-manila17:17
*** jmlowe has quit IRC17:22
*** jmlowe has joined #openstack-manila17:22
*** jmlowe has quit IRC17:39
*** jmlowe has joined #openstack-manila17:39
*** tongli has joined #openstack-manila17:41
bswartzzhongjun: yes that's why I encourage you to talk to vkmc and look at her spec about ceilometer integration17:42
bswartzit's about more than just ceilometer -- it's integration with all things like ceilometer17:42
openstackgerritValeriy Ponomaryov proposed openstack/manila-ui master: Fix manila quota operations  https://review.openstack.org/46069817:49
*** harlowja has joined #openstack-manila17:51
*** arnewiebalck_ has quit IRC17:51
openstackgerritValeriy Ponomaryov proposed openstack/manila-ui master: Fix manila quota operations  https://review.openstack.org/46069817:55
*** cknight has quit IRC17:56
*** erlon has joined #openstack-manila17:57
*** jmlowe has quit IRC17:58
*** jmlowe has joined #openstack-manila17:59
*** cknight has joined #openstack-manila17:59
openstackgerritValeriy Ponomaryov proposed openstack/manila-ui master: Fix share creation from snapshot  https://review.openstack.org/46024818:03
vponomaryovgouthamr: enjoy ^18:04
gouthamrbrilliant. thanks18:04
openstackgerritValeriy Ponomaryov proposed openstack/manila-ui master: Fix manila quota operations  https://review.openstack.org/46069818:05
vponomaryovgouthamr: and above just for case you review it too ))18:06
*** tongli has quit IRC18:06
gouthamrhaha... lemme test it :)18:06
vponomaryovgouthamr: it is available in three places18:07
*** arnewiebalck_ has joined #openstack-manila18:07
vponomaryovgouthamr: 1) create project in admin tab, 'quotas' page18:07
vponomaryovgouthamr: 2) update existing project's quota18:08
vponomaryovgouthamr: 3) update default quotas in general18:08
vponomaryovgouthamr: all three in admin tab18:08
*** jmlowe has quit IRC18:10
* vponomaryov dreams about very light-weight "tox" job for building reno releasenotes, because now it installs lots of heavy redundant deps such as "horizon"18:10
*** jmlowe has joined #openstack-manila18:11
bswartzis horizon even used when building release notes?18:11
bswartzit not, why can't we remove it?18:11
vponomaryovbswartz: used, we can18:11
*** jmlowe has quit IRC18:12
*** jmlowe has joined #openstack-manila18:12
gouthamrohh, because of test-requirements?18:14
gouthamrinteresting side-effect18:14
gouthamrvponomaryov: thanks for the test steps.. will try it right now18:15
*** dustins has quit IRC18:18
gouthamrbswartz: can i be added to this: https://launchpad.net/~manila-drivers18:26
bswartzgouthamr: I'd rather add you to a specific team with the power that lets you do what you need to18:27
bswartzwhat can't you do?18:27
gouthamri traced back to that from manila-ui bugs page18:27
gouthamr"Bug supervisor" is set to that team18:28
bswartzactually it's set to this team: https://launchpad.net/~manila-ui-drivers18:28
gouthamryes18:28
gouthamrthat has two teams18:28
bswartzdifferent team18:28
bswartzand manila has a separate bug supervisors team18:29
gouthamrhttps://launchpad.net/~manila-ui-drivers/+members#active18:29
gouthamrperhaps we should add https://launchpad.net/~manila-bug-supervisors directly under https://launchpad.net/~manila-ui-drivers/+members#active18:30
bswartzI can fix this18:31
bswartzone moment18:31
bswartzgouthamr: fixed (I hope)18:33
bswartzI created a new group for manila ui bug supervision that inherits from the other groups18:33
bswartzgouthamr: eventually they will make us use storyboard anyways =-P18:34
gouthamr:) so many levels of nesting18:34
gouthamrgot an email18:34
bswartzindeed18:34
gouthamrand launchpad shows a graph now 'Goutham Pacha Ravi → Manila Bug Supervisors → Manila UI Bug Supervisors'18:35
gouthamr:P18:35
*** carthaca_ has quit IRC18:36
*** david_4 has quit IRC18:36
*** sapcc-bot has quit IRC18:36
*** david_5 has joined #openstack-manila18:36
*** sapcc-bot2 has joined #openstack-manila18:36
*** carthaca_2 has joined #openstack-manila18:36
bswartzsounds like working as intended18:36
bswartzthe groups merely exist because you can't assign the power to multiple people18:36
bswartzand we're trying to avoid everyone having the power to do everything18:37
*** jmlowe_ has joined #openstack-manila18:38
*** jmlowe has quit IRC18:38
*** arnewiebalck_ has quit IRC18:40
*** arnewiebalck_ has joined #openstack-manila18:42
openstackgerritMerged openstack/manila-ui master: Fix share creation from snapshot  https://review.openstack.org/46024818:46
*** openstackgerrit has quit IRC18:48
gouthamr^ cherry-picked18:51
gansogouthamr: thanks!18:54
gouthamrganso: :) button-clicking18:55
*** jmlowe_ has quit IRC19:05
*** jmlowe has joined #openstack-manila19:05
*** a-pugachev has joined #openstack-manila19:12
*** jmlowe has quit IRC19:25
*** jmlowe has joined #openstack-manila19:25
*** jmlowe has quit IRC19:31
*** jmlowe has joined #openstack-manila19:31
*** xyang_ has quit IRC19:33
*** jmlowe has quit IRC19:33
*** jmlowe has joined #openstack-manila19:33
*** jmlowe has quit IRC19:36
*** jmlowe has joined #openstack-manila19:37
*** xyang_ has joined #openstack-manila19:39
*** xyang_ has quit IRC19:40
*** kaisers has quit IRC19:41
*** kaisers has joined #openstack-manila19:42
*** dustins has joined #openstack-manila19:46
*** kaisers has quit IRC19:46
*** kaisers has joined #openstack-manila19:48
*** porrua has quit IRC19:49
*** arnewiebalck_ has quit IRC20:03
*** makowals has joined #openstack-manila20:11
*** jmlowe has quit IRC20:14
*** jmlowe has joined #openstack-manila20:14
*** eharney has quit IRC20:17
*** jmlowe has quit IRC20:24
*** makowals has quit IRC20:33
*** kaisers has quit IRC20:38
*** xyang_ has joined #openstack-manila20:38
*** xyang_ has quit IRC20:48
*** xyang_ has joined #openstack-manila20:48
*** cknight has quit IRC20:50
*** tongli has joined #openstack-manila20:59
*** dustins has quit IRC21:05
*** tongli has quit IRC21:22
*** zigo has joined #openstack-manila21:32
*** xyang_ has quit IRC21:47
*** catintheroof has quit IRC22:00
*** dsariel has quit IRC22:04
*** erlon has quit IRC22:13
*** jungleboyj has quit IRC22:14
*** harlowja has quit IRC22:14
*** ganso has quit IRC22:27
*** a-pugachev has quit IRC22:29
*** kaisers has joined #openstack-manila22:38
*** kaisers has quit IRC22:42
*** harlowja has joined #openstack-manila23:23
*** hongbin has quit IRC23:29
*** jungleboyj has joined #openstack-manila23:55

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