02:00:31 <zhenguo> #startmeeting nimble
02:00:32 <openstack> Meeting started Thu Dec 15 02:00:31 2016 UTC and is due to finish in 60 minutes.  The chair is zhenguo. Information about MeetBot at http://wiki.debian.org/MeetBot.
02:00:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
02:00:35 <openstack> The meeting name has been set to 'nimble'
02:00:42 <zhenguo> o/
02:00:47 <RuiChen> o/
02:00:58 <liusheng> o/
02:01:00 <shaohe_feng> o/
02:01:21 <zhenguo> yuntongjin, luyao: are you around?
02:01:38 <luyao> zhenguo: yes
02:01:47 <zhenguo> ok
02:01:53 <zhenguo> the agenda:
02:01:56 <zhenguo> https://wiki.openstack.org/wiki/Meetings/Nimble#Agenda_for_next_meeting
02:02:05 <zhenguo> let's jump in
02:02:16 <zhenguo> #topic Announcements and reminders
02:02:38 <zhenguo> I have nearly finished the create instance taskflow refactor work, will add more tests today
02:02:51 <shaohe_feng> Nice
02:03:04 <liusheng> awesome works
02:03:09 <RuiChen> sounds great
02:03:22 <zhenguo> please help to tests
02:03:39 <zhenguo> thanks luyao for draft the initial patch
02:04:15 <zhenguo> Our tempest gate is still broken with the tests, I will work with liusheng to address that later :(
02:04:36 <zhenguo> really hard to debug ironic things
02:04:42 <liusheng> zhenguo: hope you can address it :)
02:04:49 <zhenguo> liusheng: hah
02:05:06 <shaohe_feng> zhenguo: luyao is busy on hers master's thesis
02:05:39 <zhenguo> shaohe_feng: oh, that's important
02:05:44 <liusheng> so she will reduce time on Nimble ?
02:06:08 <shaohe_feng> liusheng: these days.
02:06:11 <RuiChen> thesis about nimble :-)?
02:06:17 <zhenguo> lol
02:06:18 <liusheng> hah
02:06:34 <shaohe_feng> RuiChen: about performance optimization
02:06:42 <liusheng> cool!
02:06:58 <zhenguo> may help to us later, hah
02:07:22 <zhenguo> ok, let's continue
02:07:34 <luyao> zhenguo: yes
02:07:40 <zhenguo> After discussion, we decide to allow duplicate instance names, liusheng is working on that
02:08:08 <zhenguo> luyao: hope everything goes well
02:08:33 <luyao> zhenguo, I hope so,thank you!:)
02:08:43 <zhenguo> luyao: hah
02:08:55 <zhenguo> ok, not much of announcement, anyone else have a thing here?
02:09:00 <RuiChen> yes, zhenguo, i think depulicate name match most openstack project behavior
02:09:15 <zhenguo> RuiChen: yes,
02:09:27 <liusheng> yes, and will add copy Nova's implementation to add an option to enalbe/disable
02:09:47 <zhenguo> RuiChen: and with that we can avoid many unneeded concerns
02:10:06 <liusheng> I cannot open the link, since something wrong with my blue cloud :(
02:10:07 <zhenguo> liusheng: cool
02:10:27 <RuiChen> yeah, uuid is unique key
02:10:31 <zhenguo> liusheng: what link
02:10:35 <zhenguo> RuiChen: yes
02:10:38 <liusheng> zhenguo: the patch's link
02:11:08 <zhenguo> liusheng: hah, you can use your yellow cloud instead
02:11:10 <shaohe_feng> yes, uuid is for machine
02:11:21 <shaohe_feng> name is for human
02:11:51 <liusheng> zhenguo: really ?
02:11:56 <liusheng> zhenguo: let me try
02:11:57 <RuiChen> blue/yellow cloud are magic words, I think not everybody knew it, hah
02:12:12 <liusheng> zhenguo: I am acessing the bluecloud by VNC :(
02:12:13 <zhenguo> shaohe_feng: yes, but many duplicate name may not easy to distinguish for human
02:12:27 <zhenguo> RuiChen: lol
02:12:42 <zhenguo> liusheng: why using VNC
02:13:08 <liusheng> zhenguo: I cannot acess my bluecloud..
02:13:15 <zhenguo> liusheng: hah
02:13:21 <liusheng> zhenguo: but VNC tool is available
02:13:44 <zhenguo> liusheng: it's not easy to use
02:13:53 <liusheng> lol
02:14:00 <zhenguo> OK, let's continue
02:14:08 <RuiChen> yeah, move on
02:14:17 <zhenguo> the contribution report:
02:14:28 <zhenguo> #link http://stackalytics.com/report/contribution/nimble/90
02:15:06 <zhenguo> ok, anything else?
02:15:13 <liusheng> zhenguo: I am stuck by the tempest patch a totally week! :P
02:15:31 <shaohe_feng> zhenguo: so, user should rename by himself  to distinguish his instances.
02:15:50 <zhenguo> liusheng: yes, so please just stop it, lol
02:16:02 <liusheng> zhenguo: :P
02:16:13 <zhenguo> shaohe_feng: like nova, we will have an option to enable/disable duplicate names
02:16:27 <liusheng> shaohe_feng: name should be able to update
02:16:43 <zhenguo> shaohe_feng: I thinkg that should be ok, because a cloud not usually used by human, but other machines or scripts
02:17:31 <shaohe_feng> yes.
02:18:00 <zhenguo> shaohe_feng: ok, we can keep this way until someone request us to change
02:18:25 <zhenguo> ok, what's next
02:18:32 <zhenguo> #topic Task tracking
02:18:40 <_liusheng> let's chose a new name for our Nimble ?
02:18:54 <zhenguo> _liusheng: next agent is that
02:18:57 <zhenguo> :P
02:18:58 <RuiChen> \o/ naming day
02:19:17 <zhenguo> Task tracking topic first, sorry
02:19:17 <shaohe_feng> mogan
02:19:28 <zhenguo> wait, wait, wait....
02:19:34 <zhenguo> hah
02:19:36 <_liusheng> zhenguo: hah
02:19:48 <zhenguo> #link https://etherpad.openstack.org/p/nimble-task
02:19:54 <RuiChen> exciting event
02:19:58 <zhenguo> hah
02:20:07 <zhenguo> Thanks shaohe_feng for creating the etherpad
02:20:33 <zhenguo> everyone please feel free to add the task you are working on or the task you plan to do there
02:20:50 <zhenguo> also need to register a bp first
02:21:34 <_liusheng> zhenguo: I have filed a bp for supporting notification in Nimble
02:22:02 <zhenguo> _liucheng: cool
02:22:38 <zhenguo> _liusheng: it's your familiar fields, ceilometer guy :P
02:23:02 <_liusheng> :)
02:23:23 <RuiChen> ^^ notification powered
02:23:31 <RuiChen> :-)
02:23:49 <zhenguo> yeah, it's coming...
02:23:50 <shaohe_feng> _liusheng: experter on notification
02:23:50 <_liusheng> RuiChen: lol
02:24:25 <zhenguo> ok, so we can follow the task list, everyone can coorparate with with the owner if you want
02:25:15 <shaohe_feng> OK
02:25:20 <zhenguo> seems everyone can't wait to start the new name topic
02:25:34 <zhenguo> so let's move on
02:25:42 <zhenguo> #topic New project name
02:26:15 <_liusheng> may need to start a irc voting ? lol
02:26:37 <zhenguo> _liusheng: not today
02:26:49 <_liusheng> zhenguo: ok
02:26:50 <zhenguo> _liusheng: we should ask the lawyer first. lol
02:26:58 <RuiChen> so the whole name list is ?
02:27:05 <_liusheng> that should be
02:27:26 <zhenguo> seems now we have a few options: Mogan, Melter, Skua, ...
02:27:57 <zhenguo> anything else?
02:28:17 <shaohe_feng> zhenguo: JF has asked YanLin to consult the intel's lawyer
02:28:19 <RuiChen> no from me
02:28:58 <zhenguo> shaohe_feng: cool
02:28:58 <RuiChen> thank you shaohe_feng and JF
02:29:30 <zhenguo> shaohe_feng: so we can wait for a while
02:29:59 <zhenguo> I will meet JF this afternoon at Intels party, lol
02:30:16 <RuiChen> party?
02:30:24 <zhenguo> RuiChen: yes
02:30:26 <RuiChen> cool
02:30:37 <zhenguo> hah
02:30:38 <shaohe_feng> meal  party
02:30:50 <RuiChen> who is the owner of Skua?
02:30:52 <_liusheng> zhenguo: sounds great
02:30:58 <zhenguo> RuiChen: me
02:31:37 <RuiChen> can you give some intrducation about it?
02:32:01 <zhenguo> RuiChen: a bird name, not much meanings...
02:33:02 <zhenguo> RuiChen: but seems all other projects' name doesn't mean what they are doing
02:33:02 <RuiChen> heh, it's fine
02:33:48 <zhenguo> so the list is Mogan, Melter, Skua, right
02:34:08 <zhenguo> anyone else want to add more
02:34:21 <liusheng> seems people like Mogan :)
02:34:27 <zhenguo> yes
02:35:03 <RuiChen> \o/
02:35:08 <liusheng> means "摸黑儿干" lol
02:35:17 <zhenguo> lol
02:35:30 <RuiChen> waiting the final lawyer choose
02:35:40 <zhenguo> Fred gives it an interesting meaning
02:36:10 <RuiChen> match the project status,heh
02:36:30 <zhenguo> ok, if we have more than one option after the consult for lawer, then we will vote for the final name
02:37:20 <zhenguo> ok, next
02:37:33 <zhenguo> #topic Shorten Nimble OSC commands
02:37:58 <liusheng> zhenguo: OK, thanks, I have added the agenda
02:38:05 <zhenguo> I discussed with liusheng about the current osc command, he thinks it's too long and not easy to use
02:38:35 <zhenguo> liusheng: thanks
02:38:35 <liusheng> zhenguo: IMO, the current commands looks too long, and a bit inhuman :)
02:38:54 <RuiChen> openstack baremetal compute xxx
02:39:10 <zhenguo> seems instance should be replaced with server
02:39:34 <zhenguo> RuiChen: can we remove the 'compute'
02:39:53 <liusheng> RuiChen: yes, and I think Nova manage virtual machine, we Nimble manage baremetal machine
02:39:59 <RuiChen> let me check,  i think ironic catch it
02:40:07 <liusheng> so maybe openstack baremetal server xxx
02:40:36 <zhenguo> RuiChen: ironic use openstack baremetal node
02:40:52 <zhenguo> so maybe it's ok for use to take 'openstack baremetal server'
02:40:58 <RuiChen> http://docs.openstack.org/developer/python-openstackclient/plugin-commands.html#ironic
02:41:02 <liusheng> they guys care node, we care server, lol
02:41:52 <RuiChen> | openstack.baremetal.v1           | ['baremetal set', 'baremetal create', 'baremetal list', 'baremetal unset', 'baremetal show', 'baremetal delete']
02:42:05 <zhenguo> there isn't a server concept in ironic
02:42:25 <RuiChen> deprecated name, but exist now
02:42:56 <liusheng> yes
02:43:45 <liusheng> but I am not sure, the 'friend' to end users
02:43:49 <RuiChen> osc PTL suggest more distingish name than server
02:43:58 <liusheng> sorry, the server is friend to end users
02:44:09 <zhenguo> yes,
02:44:29 <liusheng> RuiChen: any reference ?
02:44:52 <zhenguo> RuiChen: I don't quite familiar with the rule of osc name
02:45:22 <RuiChen> I talk about that with him servral months
02:45:23 <zhenguo> RuiChen: as we are not offical now, how to avoid othe project use the same name with us
02:45:52 <RuiChen> baremetal server and server
02:46:01 <liusheng> the OSC cli don't care about the specific project and the specific service, it only care the resource, e.g. image, network, server
02:46:31 <zhenguo> so we should belongs to server
02:46:41 <RuiChen> if nimble come to offical project, osc have jenkins job to check name
02:46:50 <zhenguo> RuiChen: ok
02:47:25 <zhenguo> The best choice is 'openstack baremetal server create'
02:48:22 <RuiChen> I think we are discuss shorten name, baremetal => bm? thought?
02:48:58 <zhenguo> as we have already have a baremetal in osc namespace,
02:49:15 <zhenguo> seems it's a bit confused to have both bm and baremetal,
02:49:59 <RuiChen> actually, i think if we use osc interactive mode, the CLI auto complete may have help
02:50:29 <liusheng> RuiChen: yes
02:50:34 <RuiChen> and if the not interactive mode, linux alias is a choose
02:50:46 <zhenguo> RuiChen: yes, it's ok.
02:51:28 <liusheng> RuiChen: but our currently "baremetal compute", looks a bit meaningless
02:51:29 <RuiChen> alias "openstack baremetal compute"="openstack bm server", hehe
02:51:38 <zhenguo> maybe we can send a email to the dev-list to discuss
02:52:08 <liusheng> we may should consider, the CLI is for end users
02:52:20 <zhenguo> but wait for a while to finish our configdive and taskflow work
02:52:43 <RuiChen> yeah, 8 minutes left
02:52:59 <zhenguo> yes,
02:53:25 <zhenguo> #topic open discussion
02:53:39 <zhenguo> one thing here, the flavor and instance_type
02:54:39 <liusheng> it is also releated the last topic :P
02:54:51 <zhenguo> liusheng: hah
02:54:54 <liusheng> if we support openstack baremetal server xxx
02:55:12 <zhenguo> openstack baremetal flavor
02:55:27 <liusheng> the openstack baremetal type xxx is easy to mislead
02:55:51 <zhenguo> ironic will change to use 'openstack baremetal list' directly, right?
02:56:11 <zhenguo> and nova is 'openstack server list'?
02:56:20 <liusheng> zhenguo: ironic has deprected this usage
02:56:49 <RuiChen> yes, nova use server list
02:57:24 <zhenguo> so we should maybe thing out another resouce name
02:57:34 <RuiChen> so in the future, all the ironic commands looks like: baremetal node xxx? zhenguo
02:57:35 <zhenguo> openstack xxx list
02:57:55 <zhenguo> RuiChen: not sure, maybe just baremetal list
02:57:56 <RuiChen> i'm not sure
02:58:17 <liusheng> root@liusheng:~# openstack baremetal list
02:58:17 <liusheng> This command is deprecated. Instead, use 'openstack baremetal node list'.
02:58:17 <liusheng> +--------------------------------------+--------+---------------+-------------+--------------------+-------------+
02:58:17 <liusheng> | UUID                                 | Name   | Instance UUID | Power State | Provisioning State | Maintenance |
02:58:17 <liusheng> +--------------------------------------+--------+---------------+-------------+--------------------+-------------+
02:58:20 <liusheng> | 9f2c7b47-32fd-434d-bbf0-abb10f7893ed | node-0 | None          | power off   | available          | False       |
02:58:23 <liusheng> | 3b8b50e2-f292-45a7-a587-89ad35aa888b | node-1 | None          | power off   | available          | False       |
02:58:26 <liusheng> | 0fe83120-4132-49ae-90b7-835198e6f155 | node-2 | None          | power off   | available          | False       |
02:58:29 <liusheng> +--------------------------------------+--------+---------------+-------------+--------------------+-------------+
02:59:06 <zhenguo> if they use openstack baremetal node xxx, seems it's ok for use to use openstack baremetal server xxx
03:00:11 <liusheng> if we can find a new an more meaningful name, it is better
03:00:24 <liusheng> or use openstack baremetal server xxx ?
03:00:30 <zhenguo> ....
03:00:35 <zhenguo> not time left
03:00:44 <zhenguo> thanks all for joining
03:00:50 <liusheng> \o
03:00:54 <zhenguo> #endmeeting