Monday, 2017-07-17

*** rods has joined #openstack-shade00:58
*** gkadam has joined #openstack-shade03:39
*** gouthamr has quit IRC03:42
*** yfried has joined #openstack-shade06:17
*** dhellmann has quit IRC07:16
*** dhellmann has joined #openstack-shade07:17
openstackgerritRosario Di Somma proposed openstack-infra/shade master: WIP: Don't remove top-container element in the adapter  https://review.openstack.org/48417809:48
openstackgerritRosario Di Somma proposed openstack-infra/shade master: WIP: Don't remove top-container element in the adapter  https://review.openstack.org/48417810:06
*** yfried has quit IRC10:50
*** yfried has joined #openstack-shade10:51
*** gouthamr has joined #openstack-shade13:00
*** gkadam has quit IRC13:26
*** yfried has quit IRC15:20
openstackgerritMonty Taylor proposed openstack/os-service-types master: WIP Use CacheControl for caching  https://review.openstack.org/48439715:33
noshankusHi Guys - anyone know if there is a way to list volumes for a specific project OR instance?15:59
mordrednoshankus: I'm not sure 100% what you mean - I _think_ the answer is "not at the moment" - but I might be wrong, so can you say a few more words?16:39
noshankus@mordred - yeah, apologies for the blurb. I'm looking for a way to query for the count of, and size of, volumes per project. I'm playing with search_volumes() and list_volumes(), but these only ever seem to show me based on inital project I connect to. I'm looking for a way to execute: search_volumes(project=xyz) as I iterate through projects16:45
noshankusOr at least get a list of volumes, their size and whihc project they are used by. Maybe it's more by instance and then link up to project...16:49
mordrednoshankus: yah - SO ... there's two things here - (or three)16:55
noshankusCool, hit me! :)16:55
mordredfirst is that yes, we're missing support for "all_projects" or equiv on list_volumes -which is going to make this harder for you16:55
mordrednoshankus: looking at the rest api docs, there doesn't seem to be an all_projects param that can be passed - which means we'd need to do a list_projects then a specific list call for each project (we should double-check with cinder folks on that ... thingee ??)16:58
mordrednow - that said - there is a TODO-list item we've got that I think we can get to real soon now (the rest-migration makes it easier) - which is to provide a _general_ way of making calls on projects otherthan the one you authenticated to16:58
mordred(since that's a common admin-type task)16:59
mordredin any case - the workaround for now is to doa list_projects, then in a loop create a new OpenstackCloud object with project_id overridden in the constructor, do a list_volumes on that, then stich it all together17:00
mordredI should write up a few thoughts on this class of problems so people can work on it17:00
noshankusOk, no problem. So, I can iterate over the projects without any issue... what is the best way to specify a particular project when trying to list the volumes?17:00
noshankusAh!17:00
mordredI think we can add a project_id param to list_volumes pretty easily - lemme look at that real quick17:01
noshankusHadn't thought of going back up to that level17:01
noshankusCool, that would mean just using a single connection which should make sense anyway.17:01
noshankusI already doing something like: self.cloud_operator.get_volume_quotas(tenant.name), so having something like self.cloud_operator.list_volumes(tenant.name) would be ideal also17:03
openstackgerritMonty Taylor proposed openstack-infra/shade master: Add project_id parameter to list_volumes  https://review.openstack.org/48443017:06
mordrednoshankus: based on API docs, something like that ^^ (untested)17:06
noshankus@mordred - excellent, thanks for the help!17:07
noshankusFor now, I'll just go back to the shade.openstack_cloud for each project - really does seem like overkill, thanks again17:09
*** spredzy has joined #openstack-shade17:12
spredzyShrews: hey, bringing the subject on this side of IRC, regarding applying filter based on 'OS-EXT-STS:task_state', is there any weekly meeting I can bring this point to ?17:13
spredzycontext: Having this logic https://github.com/ansible/ansible/pull/26318 directly into shade17:14
Shrewsspredzy: hi! welcome. no, we don't have weekly meetings.17:15
Shrewsspredzy: but i do think we might need to investigate the relationship between the 'status' field and the 'OS-EXT-STS:task_state' field. TBH, I'm very surprised status would be ACTIVE while task_state says deleting17:16
Shrewsmordred: have you ever experienced that? ^^^^17:19
spredzyShrews: Reading https://wiki.openstack.org/wiki/VMState17:20
spredzy"vm_state should only be updated at the end of a task, when the task successfully finishes, and setting the task_state to None."17:20
spredzyNot sure how vm_state relates to status, but I've observed this behavior (status chaning when the tasks successfully finishes) hence the initial need for this PR17:21
mordredso - this is likely more on the deleting-side, right? I node shouldn't hit ACTIVE until it's finished its booting tasks I'd hope?17:21
Shrewsspredzy: so if we want to do this shade side (and i think that's a good idea), then we'd want to look at changing lists_hosts() in shade/inventory.py17:22
mordredspredzy: or have you seen it apply to things booting hitting ACTIVE but still having task_state things17:22
spredzymordred: So far I've hit it only with deleting17:22
mordredShrews, spredzy: yes - definitely should do this in shade. (actually, there's a TON of logic in os_server that needs to migrate back in to shade, fwiw)17:22
spredzyBut it can apply I suppose to migrating, resizing, etc...17:22
mordredah17:23
Shrewsshade doesn't support those ops right now17:23
mordredShrews: I think we finallydo - we just haven't updated the modules17:23
Shrewsmordred: oh? neat!17:23
spredzyShrews: shade might not, but as the inventory/openstack.py user, I'd like not to have VM in active/migrating being returned for example17:24
* Shrews forgets all of shade things17:24
spredzyonly active/None17:24
mordredspredzy: well - so I think we might need to think about the combos ... like, ACTIVE + migrating I suppose is not actually active since you can't actually do anything with it, right?17:24
mordredspredzy: yah. I think you're correct17:24
Shrewsspredzy: yah17:24
spredzymordred: Yep, I'd go only for the active/None combo, but not a nova expert here :/ So to take it with a grain of salt17:24
spredzyI'll look into the shade codebase tomorrow and start with what Shrews pointed me too (ie lists_hosts() in shade/inventory.py)17:25
spredzys/too/to17:25
Shrews\o/17:27
mordredspredzy, Shrews: so - we don't currently define task_state, vm_state or power_state in doc/source/model.py or in _normalize_server as part of the'strict' interface - we do expose them on the server objects as task_state, power_state and vm_state if the longer version exists17:29
mordredwe probably want to go ahead and add the three of them to the things we always return (and set them to None if OS-EXT-STS:{state} doesn't exist)17:29
mordredespecially if they're actually important for things like this :)17:29
* spredzy takes note17:30
Shrewsyeah. that's pretty simple17:30
openstackgerritMonty Taylor proposed openstack/os-service-types master: Add support for getting OpenStack project information  https://review.openstack.org/48443517:34
Shrewswell that's a new thing i've not noticed before ^^^^17:40
openstackgerritMonty Taylor proposed openstack/os-service-types master: Add support for getting OpenStack project information  https://review.openstack.org/48443518:20
openstackgerritMonty Taylor proposed openstack/os-service-types master: Refactor bulk of data checking into mixin class  https://review.openstack.org/48444518:20
*** SamYaple has quit IRC18:47
*** SamYaple has joined #openstack-shade18:47
*** cmurphy has quit IRC19:09
*** cmurphy has joined #openstack-shade19:11
openstackgerritMerged openstack-infra/shade master: De-client-ify Service Create  https://review.openstack.org/48219420:01
openstackgerritMonty Taylor proposed openstack/os-service-types master: Add support for getting a complete list of type names  https://review.openstack.org/48447320:02
openstackgerritOpenStack Proposal Bot proposed openstack-infra/shade master: Updated from global requirements  https://review.openstack.org/48332721:59
*** gouthamr has quit IRC22:12
*** gouthamr has joined #openstack-shade22:14
openstackgerritPaul Belanger proposed openstack-infra/shade master: DNM - testing  https://review.openstack.org/48452022:56
*** gouthamr has quit IRC23:32
*** gouthamr has joined #openstack-shade23:52
*** gouthamr has quit IRC23:53
*** gouthamr has joined #openstack-shade23:53

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