15:00:39 #startmeeting openstack search 15:00:40 Meeting started Thu Jun 29 15:00:39 2017 UTC and is due to finish in 60 minutes. The chair is sjmc7. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:45 The meeting name has been set to 'openstack_search' 15:00:57 hi 15:01:06 hello! 15:01:12 o/ 15:01:23 facing few issues on node scheduling 15:01:31 ? 15:01:52 in ironic spinning 20 vm...scheduling happens for only 10 at a time ? 15:02:02 i don’t know much about ironic.. 15:02:16 once ten completes, then remaming ten get scheduled 15:02:23 any reason ? 15:02:43 i’ve no idea :) this isn’t the ironic meeting 15:03:00 ok 15:03:07 try #openstack-ironic 15:04:12 keerthivasan: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 15:04:27 #endmeeting 15:04:33 keerthivasan: join the #openstack-ironic channel 15:04:34 keerthivasan: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 15:04:44 this is a scheduled meeting for the searchlight project 15:04:50 ok 15:05:05 #openstack-ironic 15:05:38 ‘/join #openstack-ironic’ without the quotes 15:06:30 seems don't have too many people today 15:06:49 nope :( i’ve been caught up on keystone and horizon stuff all week so i didn’t have anything on the agenda 15:07:24 one thing about versioned notification patch 15:07:41 the state_update comment 15:07:43 thanks 15:08:05 yeah 15:08:15 I end up with a case 15:08:23 when I launch a vm successfully 15:08:55 I find there are two 'state' field in notification payload 15:09:05 oo, that’s exciting 15:09:09 are they the same? 15:09:33 there's one top level field in the payload 15:09:55 which has value 'active' 15:10:08 that would be what preivously would have been ‘status’ i think 15:10:42 ah, interesting. so has status gone completely? i missed that 15:10:50 and state_update field is empty, because it's a not a update action I think 15:11:00 you’re right - looking at https://docs.openstack.org/developer/nova/notifications.html for instance.update 15:11:06 then your code will set payload['state'] = None 15:11:17 "state": "building", 15:11:17 "task_state": "scheduling", 15:11:20 which overwrite original value in the payload 15:11:51 yeah.. i misunderstood what you were saying. i think ‘state’ needs to map to ‘status' 15:12:03 let me see 15:12:08 and ‘task_state’ is the one should be cleared 15:12:42 maybe i can ignore the state_update entirely, if ‘state’ and ‘task_state’ are always there. old_state and old_task_state are used to decide whether an update can be ignored 15:14:14 yeah, I think 'state' means vm state 15:14:26 and there is a 'task_state' 15:14:27 with the old notifications, ‘state’ was ‘status’ 15:14:38 oh, kind of mess : ) 15:14:40 ok, i totally missed that, good catch. sorry i misunderstood your comment 15:15:15 and they have a 'status', it's kind of combination of both vm state and task state 15:16:13 'status is more like user understandable description I think 15:17:25 yep, and it’s more stable than task state 15:17:30 so after a server has been started, I end up with a server document whose 'state' is null, which is supposed to be 'active' 15:17:41 yeah, so ‘state’ shouldn’t be there at all 15:17:45 and ti should be ‘status' 15:17:48 which should never be null 15:18:51 ‘state’ was previously mapped to ‘OS-EXT-STS:vm_state' 15:18:55 yeah, there is only 'status' in nova instance api 15:19:09 and task_state OS-EXT-STS:task_state 15:19:20 exactly 15:19:48 yeah, the API reports the OS-EXT-STS fields 15:20:14 it looks though like ‘state’ and ‘status’ aren’t the same values 15:20:31 ‘status’ is/was ‘BUILD’ versus ‘state’ = ‘building’ 15:20:38 yes, they are different 15:20:55 I think there is a mapping to do convert jobs 15:21:15 give me vm state and task state and I'll return you a status, such like that 15:21:37 yeah. i’ll check with the nova team. that’s annoying 15:21:59 lots of concepts lol 15:22:12 mm. stupid of me to miss that 15:23:47 I just figure it out too : ) 15:24:15 ok, I don't have other issues 15:24:35 ok, i will correct that. me neither. there’s been a thread about the ‘big tent’ for the last week or so 15:25:27 it looks like the TC want to narrow down the definition of ‘what is openstack’ but not clear to what extent yet 15:25:34 oh, I missed that, are there any changes 15:25:43 i’ll keep an eye on it. no, not yet, it’s just discussion 15:26:05 I've heard a new name 'openstack hosted' 15:26:17 people are (rightfully) saying that it’s hard, especially for newcomers, to understand exactly what openstack is when there are 1600 projects, some of which aren’t very active 15:26:18 right 15:26:22 that’s part of it 15:27:04 1600, gosh 15:27:53 i don’t know much it matters practically, but i’ll keep watching the thread 15:27:58 ok, well, i guess might as well end here 15:28:12 have a good weekend! the US is on holiday monday and tuesday 15:28:23 cool 15:28:32 enjoy your time 15:28:42 will do! lots of bbq 15:28:51 i'm guessing that the big tent change also has to do with funding for infra jobs 15:29:35 yes, that’s a big part of it and that’s the part that might affect projects like ours 15:30:09 which means some projects have to move? 15:30:40 *shrug* don’t know. hopefully not! 15:31:36 ok, have a nice day! 15:31:42 yup, you too 15:31:44 bye folks 15:31:48 #endmeeting