02:01:08 <zhenguo> #startmeeting mogan
02:01:09 <openstack> Meeting started Thu Aug 17 02:01:08 2017 UTC and is due to finish in 60 minutes.  The chair is zhenguo. Information about MeetBot at http://wiki.debian.org/MeetBot.
02:01:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
02:01:13 <openstack> The meeting name has been set to 'mogan'
02:01:49 <zhenguo> liusheng, shaohe_feng, wanghao, litao__, Xinran, zhangyang: o/
02:01:58 <zhangyang> o/
02:02:26 <litao__> o/
02:02:26 <Xinran> o/
02:02:31 <liusheng> o/
02:02:45 <wanghao_> hi
02:02:51 <zhenguo> as always, the agenda:
02:02:51 <zhenguo> #link https://wiki.openstack.org/wiki/Meetings/Mogan#Agenda_for_next_meeting
02:02:57 <zhenguo> let's jump in
02:03:04 <zhenguo> #topic announcements and reminders
02:03:22 <zhenguo> The default resource class has changed to baremetal in ironic instead of constructing with the properties
02:03:43 <zhenguo> Which broke our gate, but we have already addressed it, you may find the change in your new devstack env
02:04:05 <liusheng> thanks for fixing that
02:04:13 <zhenguo> hah
02:04:52 <litao__> zhenguo: great
02:05:06 <zhenguo> We have replaced the default_availability_zone with default_scheduled_zone, so and ironic node will not have a default avaiability zone if you don't add it to the aggregate
02:05:36 <zhenguo> the default scheduled zone is None, and we don't filter it when scheudling
02:06:43 <wanghao_> so you can't create the server before you add the nodes to aggregate, doesn't?
02:06:57 <zhenguo> no
02:07:06 <zhenguo> the default scheduled zone is None
02:07:15 <zhenguo> which means we can choose any node
02:07:24 <zhenguo> regardless of the az it in
02:07:26 <wanghao_> ok
02:07:57 <zhenguo> wanghao_: seems we didn't send out our weekly report durning last two weeks :(
02:08:47 <zhenguo> wanghao_: when you are busy, maybe litao__ and liusheng can help :D
02:08:51 <wanghao_> zhenguo: yes, sorry for that,  I send this weekly report this morning!
02:09:01 <wanghao_> zhenguo: sure, shame on me :(
02:09:08 <zhenguo> wanghao_: hah
02:09:10 <liusheng> yes, sure, thaks for wanghao doing that
02:09:30 <liusheng> we others can also help if wanghao are busy :)
02:09:46 <litao__> sure
02:09:47 <zhenguo> wanghao_: oh, just found the report mail, thanks
02:09:57 <wanghao_> zhenguo: :)
02:10:11 <shaohe_feng> zhenguo: morning
02:10:26 <zhenguo> shaohe_feng: o/
02:10:48 <zhenguo> ok, pike release is due soon, we will create the branch by the end of this month
02:11:19 <shaohe_feng> great
02:11:28 <zhenguo> seems requirements has cut the pike release, so our pike branch will not get update from requirements then
02:12:37 <zhenguo> ok, anything else?
02:12:57 <zhenguo> the openstack client keyword :D
02:13:19 <zhenguo> which do you perfer
02:13:24 <zhenguo> *prefer
02:14:41 <zhenguo> liusheng, wanghao_,litao__, shaohe_feng?
02:14:48 <wanghao_> what are the options? I forgot them...
02:14:54 <zhenguo> hah
02:15:12 <litao__> zhenguo: baremetalcomptue
02:15:14 <zhenguo> first I think we should choose one from baremetal and baremachine
02:15:24 <zhenguo> if we want to keep baremetal
02:15:31 <zhenguo> we need to add another word with it
02:15:54 <wanghao_> I want to keep baremetal
02:15:54 <zhenguo> litao__: +1
02:16:07 <zhenguo> wanghao: +1
02:16:26 <wanghao_> baremetalcompute sounds good
02:16:42 <liusheng> baremetalcompute is not a normal word
02:16:52 <zhenguo> liusheng: we don't need normal work
02:16:55 <zhenguo> *word
02:17:16 <wanghao_> baremetalcompute
02:17:17 <litao__> liusheng: baremetal is combination of bare and metal
02:17:27 <wanghao_> or baremetal_compute
02:17:39 <zhenguo> yes, I also find other project use combination to avoid colisions
02:17:41 <liusheng> yes, but baremetal is a common useage, baremetalcompute not
02:17:45 <liusheng> you can google it
02:18:35 <liusheng> and also baremachine
02:18:41 <zhenguo> after we use it, it will become famous maybe, lol
02:18:53 <liusheng> the meaning is same with baremetal
02:18:54 <liusheng> hah
02:19:06 <zhenguo> I still don't quite like baremachine
02:19:36 <liusheng> :)
02:19:39 <wanghao_> since nova use compute in openstackclient,  baremetal_compute means we support baremetal compute.
02:20:11 <shaohe_feng> baremetal looks good for me
02:20:16 <wanghao_> liusheng: baremachine is not common in opentack at least.
02:20:21 <litao__> yes, baremachine is same to baremetal actually
02:20:45 <zhenguo> yes, I like to keep baremetal as well
02:20:56 <liusheng> ok
02:20:59 <zhenguo> but do you like baremetalcompute or baremetal_compute
02:21:12 <wanghao_> baremetal: Ironic,  compute: Nove,  baremetal_compute: Mogan boom!
02:21:18 <zhenguo> I find zun use containerapp to avoid collisions with magnum
02:21:25 <litao__> I
02:21:30 <zhenguo> lol
02:21:37 <shaohe_feng> baremetal_compute
02:22:20 <zhenguo> is it easy to type "_" ?
02:22:22 <zhenguo> hah
02:23:06 <wanghao_> I do some checks in openstackclient, seems no client use '_'
02:23:14 <zhenguo> yes
02:23:15 <litao__> I like baremetalcompute
02:23:32 <wanghao_> baremetalcompute  I'm ok with both.
02:24:03 <zhenguo> hah, ok
02:24:10 <wanghao_> zhenguo: your call, you can have a decision.
02:24:18 <zhenguo> we can make descision during next meeting
02:24:38 <litao__> yes, Its tendency is to remove “-“, If we use it , it is strange.
02:25:03 <zhenguo> litao__: +1
02:25:14 <wanghao_> we can make a vote qucikly for it.
02:25:22 <wanghao_> baremetalcompute +1
02:25:23 <zhenguo> hah
02:25:27 <zhenguo> +1
02:25:42 <litao__> +1
02:26:03 <zhenguo> but I prefer to keep the current keyworkd for a week, replacing it is easy :D
02:26:17 <wanghao_> that's sure
02:27:13 <zhenguo> ok, let's move on
02:27:28 <zhenguo> Contribution into mogan for the last 30 days
02:27:28 <zhenguo> #link http://stackalytics.com/report/contribution/mogan/30
02:28:18 <zhenguo> thanks all for the contributions
02:28:27 <zhenguo> and again, please do more reviews
02:28:45 <wanghao_> en sure
02:28:57 <zhenguo> thanks!
02:29:03 <litao__> come on
02:29:48 <zhenguo> Xinran: besides coding, I would like you to learn to do reviews, it's more interesting :D
02:30:08 <zhenguo> shaohe_feng can mentor you
02:30:20 <shaohe_feng> zhenguo: sure.
02:30:35 <zhenguo> hah, ok anything else?
02:30:50 <Xinran> zhenguo, hah ok
02:30:57 <zhenguo> Xinran: thanks
02:30:57 <shaohe_feng> maybe be I can reserve some time review code with Xinran
02:31:16 <zhenguo> shaohe_feng: sounds good
02:31:37 <zhenguo> ok, let's move on
02:31:41 <Xinran> shaohe_feng,  thanks for carry me hah
02:31:53 <zhenguo> #topic task tracking
02:32:01 <zhenguo> #links https://etherpad.openstack.org/p/MoganWhiteBoard
02:32:11 <zhenguo> looks like things are moving along nicely
02:33:23 <zhenguo> I added a task to support another type of serial console, socat
02:34:52 <zhenguo> and we will support vnc console later for some specific hardeare drivers
02:35:20 <litao__> zhenguo: great
02:35:30 <wanghao_> those will be supported in Pike?
02:36:08 <litao__> I think no much time left
02:36:25 <zhenguo> socat will be supported in Pike
02:36:34 <zhenguo> wil finish by the end of this week
02:36:42 <wanghao_> got it
02:36:47 <liusheng> awesome
02:37:03 <zhenguo> boot from voluem can be move to next cycle
02:37:03 <litao__> awesome，hah
02:37:10 <zhenguo> hah
02:37:38 <zhenguo> I think we only have scheuling for server group and managing running servers before pike
02:38:48 <zhenguo> and on client side, seems also many thinks to do
02:38:54 <zhenguo> *things
02:39:05 <liusheng> sounds good
02:40:48 <liusheng> will finish the server group + schedule_hint work at most in next week
02:41:15 <zhenguo> liusheng: cool
02:41:31 <wanghao> zhenguo: you can add client tasks in our etherpad, I can help if I am free.
02:41:34 <liusheng> zhenguo: :)
02:41:45 <zhenguo> wanghao: ok, thanks
02:41:51 <wanghao> zhenguo: np
02:42:31 <zhenguo> liusheng: seems we discussed to get ird of the flavor access uri
02:43:05 <zhenguo> return it with flavors for admins, and use patch method for flavor to update it
02:43:08 <liusheng> zhenguo: ok, not sure if Nova has saparated API interfaces for flavor zccess
02:43:18 <zhenguo> liusheng: nova does
02:43:58 <liusheng> zhenguo: oh, looks a bit redundant
02:44:08 <zhenguo> liusheng: yes
02:44:15 <zhenguo> anyone wants to take the task
02:45:00 <liusheng> I can take it, but it is easy, if someone else what to take, feel free to take it
02:45:12 <zhenguo> thanks
02:45:25 <zhenguo> if someone else wants to do it please contact with liusheng :D
02:45:33 <liusheng> hah, sure
02:45:50 <zhenguo> maybe Xinran can have a try
02:46:01 <zhenguo> ok
02:46:11 <zhenguo> litao__: how about the power action failed patch?
02:47:07 <litao__> zhenguo: sorry, I am offline for a while
02:47:23 <zhenguo> litao__: ok, we can discuss later
02:47:30 <litao__> zhenguo: I have update the patch
02:47:45 <shaohe_feng> Xinran: can you take it? it is not hard
02:47:45 <zhenguo> litao__: just found it
02:48:20 <wanghao> me too, internal meeting.   My task is will update the manage-existing patch according zhenguo's review.
02:48:33 <zhenguo> wanghao: ok, thansk
02:48:43 <wanghao> and we need some reviews on cinder client patch.
02:48:51 <wanghao> I will test it ASAP.
02:48:51 <zhenguo> wanghao: sure
02:49:27 <zhenguo> another thing is about the server nics
02:49:27 <liusheng> we will accept the cinder client patche firstly before Pike ?
02:49:45 <zhenguo> liusheng: not sure
02:49:55 <liusheng> zhenguo: ok
02:50:39 <zhenguo> liusheng: another thing is about the server nics
02:51:02 <zhenguo> liusheng: do we need to return all network things to users
02:51:32 <liusheng> zhenguo: oh, the all network things include what ?
02:51:40 <zhenguo> liusheng: and the meening of nics seems should be the ironic port
02:52:13 <zhenguo> liusheng: network id, port_id, fixed_addresses, floating_ips,...
02:52:36 <liusheng> zhenguo: seems currect it including these stuff
02:52:46 <liusheng> zhenguo: * currently
02:53:23 <zhenguo> liusheng: we have another API to return such things /states/networks
02:54:15 <liusheng> zhenguo: oh, I see, you mean we can simplify the nics in response of server body ?
02:54:38 <zhenguo> liusheng: yes, but not sure what should be returned
02:55:04 <zhenguo> liusheng: and should we also return nic without neutron port associated
02:55:14 <zhenguo> liusheng: nic is more about hardware
02:56:09 <zhenguo> oh, seems not much time left
02:56:20 <liusheng> zhenguo: sounds reasonable, ok, we can disscuss later
02:56:22 <zhenguo> we can continue this discussion later
02:56:28 <zhenguo> let's move on
02:56:34 <zhenguo> #topic open discussion
02:56:49 <zhenguo> who's got a thing :)
02:58:04 <zhenguo> ok, thanks everyone for joining the meeting!
02:58:20 <zhenguo> #endmeeting