02:00:36 <zhenguo> #startmeeting mogan 02:00:37 <openstack> Meeting started Thu Aug 10 02:00:36 2017 UTC and is due to finish in 60 minutes. The chair is zhenguo. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:00:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:00:41 <openstack> The meeting name has been set to 'mogan' 02:01:19 <zhenguo> liusheng, shaohe_feng, wanghao, litao__, Xinran, zhangyang: o/ 02:01:32 <liusheng> o/ 02:01:57 <litao__> 0/ 02:02:53 <zhenguo> as always, the agenda: 02:02:53 <zhenguo> #link https://wiki.openstack.org/wiki/Meetings/Mogan#Agenda_for_next_meeting 02:03:03 <zhenguo> #topic announcements and reminders 02:03:29 <zhenguo> PTL Voting is now open, but seems we only have one candidacy, so I will continue to run the PTL for next cycle, thanks all! 02:03:56 <litao__> zhenguo: congratulation 02:03:59 <liusheng> congrats! 02:04:01 <liusheng> hah 02:04:05 <zhenguo> thanks, hah 02:04:43 <zhenguo> Fo the keyword of our CLI, I would like to get everyone's consensus instead of voting. 02:05:13 <zhenguo> Personally, I would like to keep the 'baremetal' but add another workd to indicate it's mogan 02:05:36 <zhenguo> like 'baremetal-compute', 'baremetal compute', or something like that 02:06:23 <zhenguo> as there's autocomplete support in openstack CLI, so make the keyword a bit long seems doesn't matter, wdyt? 02:06:47 <litao__> or baremetalcompute? 02:06:54 <zhenguo> litao__: yes 02:07:09 <zhenguo> litao__: a good alternative :D 02:07:21 <litao__> zhenguo: hah 02:08:11 <zhenguo> seems only we 3 here, let's wait for others suggestions later 02:08:39 <litao__> ok 02:08:39 <zhenguo> I plan to get rid of the default availability zone to avoid confusions when scheduling, operators should define it well 02:09:01 <zhenguo> any concerns about this? 02:09:39 <litao__> zhenguo: you mean the user must specify az when creating a server? 02:09:47 <zhenguo> litao__: no 02:09:58 <zhenguo> litao__: when you dont' sepcify, the server's availablity_zone will be None 02:10:06 <Xinran> o/ 02:10:07 <zhenguo> litao__: instead of a default one 02:10:17 <zhenguo> Xinran: o/ 02:11:39 <litao__> zhenguo: If a sever is not in a az, how to search it by az filter? 02:12:22 <zhenguo> litao__: we have a az filter? 02:13:38 <zhenguo> litao__: seems we don't support that as a filter now 02:13:49 <litao__> zhenguo: If not, what is az for specifying az 02:14:07 <shaohe_feng> zhenguo: hi 02:14:11 <zhenguo> litao__; az is an aggregate for us 02:14:18 <zhenguo> shaohe_feng: o/ 02:14:28 <shaohe_feng> zhenguo: In another meeting. will call you for sync. 02:14:32 <shaohe_feng> zhenguo: sorry. 02:14:39 <zhenguo> sahohe_feng: ok, np 02:15:47 <liusheng> maybe we can treat the "default" az as None now 02:16:26 <zhenguo> when scheduling? 02:16:35 <liusheng> yes 02:16:50 <zhenguo> but we don't have an aggregate for None 02:17:09 <litao__> liusheng: Now the az is not used for scheduling , right? 02:17:31 <liusheng> zhenguo: no, I mean we removed the defaut az now, but the action when scheduling is similar 02:18:09 <zhenguo> so if users don't specify az, we don't add az filter when getting rps 02:18:18 <zhenguo> the node may in any az 02:18:23 <liusheng> zhenguo: both are defaultly to freely select a node 02:18:27 <zhenguo> should we seet the az back to server or just leave it None 02:19:59 <liusheng> I think it should depend on the actual usages 02:20:48 <zhenguo> or we keep the default az 02:21:36 <liusheng> it is ok to leave it None I think 02:22:04 <zhenguo> so if users don't specify it, the server availability zone is None 02:22:11 <zhenguo> and we don't consider it when scheduling? 02:22:24 <zhenguo> but the node will actually be in another az 02:22:33 <liusheng> yes, we just ignore the az query filter 02:23:12 <zhenguo> so, it's really confused if the node in another az 02:23:51 <zhenguo> if we don't specify aggregate filters, it will get all nodes in different azs 02:24:58 <liusheng> hmm.. so isn't it the users want when no az specified ? 02:25:32 <zhenguo> not sure what default az is defined for 02:26:13 <zhenguo> anyonw knows how nova handle this? 02:26:25 <liusheng> mybe just to give a default choice where to place the usr's server 02:26:55 <zhenguo> seems nova has a default schedule az 02:28:04 <litao__> Yes, nova has its default az 02:28:39 <zhenguo> litao__: default az and default scheule az, right? 02:29:36 <litao__> zhenguo: what is default schedule az？ 02:29:41 <liusheng> zhenguo: seems yes 02:29:52 <zhenguo> litao__: another option 02:30:09 <litao__> zhenguo: yes 02:30:47 <litao__> liusheng: How to use az for selecting nodes in mogan cu rrently? 02:31:01 <litao__> liusheng: I see mogan ignore the az 02:31:12 <liusheng> litao__: currently, we ignore it 02:31:12 <zhenguo> not az filter suport yet 02:31:21 <liusheng> litao__: yes, and zhenguo is working on that 02:31:36 <litao__> got it 02:31:42 <zhenguo> yes, that's why I want to get rid of default az 02:33:04 <litao__> zhenguo: If we drop default az, would scheduler select a az randomly? 02:33:22 <zhenguo> litao__: yes 02:34:29 <zhenguo> litao__: then, if users don't specify az, the node can be in any az 02:34:39 <zhenguo> litao__: or it would be None 02:34:45 <liusheng> zhenguo: the default_availability_zone is used for nova-compute to determine which az the nova-compute belong to 02:35:10 <zhenguo> liusheng: but we don't have that 02:35:22 <litao__> zhenguo: It is not under control, so is it good for user? 02:35:30 <liusheng> zhenguo: the default_schedule_zone is for server scheduling, to determine which az the server will be place to if no az specified 02:36:05 <liusheng> zhenguo: and az is a limitation for migration 02:36:57 <zhenguo> but we don't have a way to make a node in the default az :( 02:37:55 <zhenguo> litao__: not sure, or maybe if user dont's specify the az, we just use default az to filter nodes, then got error if operators didn't set the aggregate 02:38:02 <liusheng> zhenguo: by aggregate metadata ? 02:38:12 <zhenguo> liusheng: who will set that 02:38:32 <liusheng> openstack: operators or deployers 02:38:49 <zhenguo> liusheng: so if they are not set it, we will fail it 02:40:50 <liusheng> zhenguo: in nova the default_schedule_zone is None defaultly, and all hosts can pass 02:40:57 <zhenguo> so our default az is not nova's default az, it's more like default scheduling az 02:41:41 <zhenguo> we can follow the default_schedule_zone defination 02:42:15 <zhenguo> liusheng: so, in nova, if you don't specify the az when claiming a server ,the instance.availability_zone will be None, right? 02:42:22 <litao__> [stack@devstack ~]$ nova aggregate-list 02:42:22 <litao__> +----+------+-------------------+------+ 02:42:22 <litao__> | Id | Name | Availability Zone | UUID | 02:42:22 <litao__> +----+------+-------------------+------+ 02:42:22 <litao__> +----+------+-------------------+------+ 02:42:23 <litao__> [stack@devstack ~]$ nova availability-zone-list 02:42:23 <litao__> +-------------------------+----------------------------------------+ 02:42:23 <litao__> | Name | Status | 02:42:24 <litao__> +-------------------------+----------------------------------------+ 02:42:24 <zhenguo> instead of setting by really az 02:42:25 <litao__> | internal | available | 02:42:25 <litao__> | |- devstack.localdomain | | 02:42:26 <litao__> | | |- nova-conductor | enabled :-) 2017-08-10T02:41:54.000000 | 02:43:30 <liusheng> zhenguo: yes if the default_schedule_zone didn't configured 02:43:58 <zhenguo> liusheng: so, it's not set with default az, right? 02:44:15 <zhenguo> liusheng: and it can be node in any az, but not set back to the instance 02:44:41 <liusheng> zhenguo: no, default az is only for nova-compute, default scheduler az is for schelding 02:45:14 <liusheng> zhenguo: i don't think so, if set the nova-compute's az back to server, the server will be limitted to this az in migration 02:45:17 <zhenguo> liusheng: yes, I know, I mean the scheduled host must be in one az as there's default az 02:46:11 <zhenguo> so we can follow nova 02:46:28 <zhenguo> we changed to use default schedule zone option 02:46:29 <liusheng> default_schedule_zone 02:46:39 <liusheng> Possible values: 02:46:39 <liusheng> * Any string representing an existing availability zone name. 02:46:39 <liusheng> * None, which means that the instance can move from one availability zone to 02:46:39 <liusheng> another during its lifetime if it is moved from one compute node to another. 02:46:39 <zhenguo> which default to None 02:46:52 <liusheng> default_schedule_zone 02:46:57 <zhenguo> ok 02:47:12 <zhenguo> so we will replace our default_availabilty_zone with default_schedule_zone 02:47:30 <zhenguo> oh, sorry, seems not much time left :( 02:47:34 <liusheng> hah 02:47:51 <zhenguo> hah, let's move on and continue to discuss this later 02:48:03 <zhenguo> #topic task tracking 02:48:13 <zhenguo> #links https://etherpad.openstack.org/p/MoganWhiteBoard 02:49:14 <zhenguo> looks like things are moving along nicely 02:50:36 <zhenguo> wanghao: please add boot from volume task there when you are online, thanks 02:51:02 <zhenguo> liusheng, litao__: anything else want to talk here? 02:51:51 <liusheng> liusheng: server group feature is almost done :) 02:52:14 <zhenguo> liusheng: awesome, hah 02:52:22 <litao__> zhenguo: I am refactor the codes according to your reviews 02:52:36 <zhenguo> litao__: cool 02:52:55 <wanghao> zhenguo: sure, sorroy I can't attend the meeting, I must test some internal task. 02:53:03 <zhenguo> liusheng: need to add server group support when claiming servers when aggregates one finished 02:53:03 <liusheng> zhenguo: :), will push some client patches, place take a look if you get time 02:53:16 <zhenguo> wanghao: ok, np 02:53:17 <liusheng> zhenguo: sure 02:53:33 <zhenguo> liusheng: ok, I will 02:54:32 <liusheng> thanks 02:54:58 <zhenguo> seems aggregates stuff is almost done, only two patches up for review 02:55:36 <liusheng> ok, will review 02:55:41 <zhenguo> liusheng: thanks 02:56:02 <zhenguo> 5 mins left, let's move to next topic 02:56:09 <zhenguo> #topic open discussion 02:56:26 <zhenguo> liusheng, litao__: let's continue the default scheulde zone here, hah 02:56:44 <zhenguo> I think it's ok to just keep one default schedule zone option in mogan 02:56:58 <zhenguo> default to None, and we will skip it when filtering 02:57:30 <litao__> I aggree 02:57:32 <zhenguo> and the server availability zone filed will be the option 02:57:37 <zhenguo> default to None 02:57:48 <zhenguo> regardless of which az the node in 02:57:52 <liusheng> sounds reasonable 02:58:06 <zhenguo> ok, I will update the patch 02:58:34 <zhenguo> anything else? 02:59:06 <zhenguo> thanks all for joinning the meeting! 02:59:12 <liusheng> bye 02:59:20 <zhenguo> #endmeeting