| *** yuntongjin has joined #openstack-nimble | 00:36 | |
| *** yuntongjin has quit IRC | 00:55 | |
| *** devlaps has quit IRC | 00:59 | |
| *** devlaps has joined #openstack-nimble | 01:02 | |
| *** kevinz has joined #openstack-nimble | 01:24 | |
| liusheng | morning nimble | 01:31 |
|---|---|---|
| liusheng | will the meeting be hold in irc channel today ? | 01:32 |
| zhenguo | liusheng: morning, | 01:41 |
| zhenguo | liusheng: yes, | 01:41 |
| *** Kevin_Zheng has joined #openstack-nimble | 01:46 | |
| *** lei-zh has joined #openstack-nimble | 01:54 | |
| zhenguo | #startmeeting nimble | 02:00 |
| openstack | Meeting started Thu Dec 8 02:00:48 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 02:00 |
| openstack | The meeting name has been set to 'nimble' | 02:00 |
| zhenguo | hi all | 02:00 |
| lei-zh | o/ | 02:01 |
| zhenguo | liusheng, luyao, RuiChen, shaohe_feng, shihanzhang: are you around? | 02:01 |
| liusheng | o/ | 02:02 |
| lei-zh | seems 10am is still too eary : ) | 02:02 |
| zhenguo | lei-zh: hah | 02:02 |
| zhenguo | ok, the agenda: | 02:03 |
| zhenguo | #link https://wiki.openstack.org/wiki/Meetings/Nimble#Agenda_for_next_meeting | 02:03 |
| RuiChen | o/ | 02:03 |
| zhenguo | RuiChen: o/ | 02:03 |
| shaohe_feng | zhenguo: hi | 02:03 |
| zhenguo | shaohe_feng: o/ | 02:04 |
| luyao | zhenguo: hi | 02:04 |
| zhenguo | luyao: o/ | 02:04 |
| zhenguo | hah, seems we are all here | 02:04 |
| zhenguo | ok, let's jump in | 02:04 |
| zhenguo | #topic announcements and reminders | 02:04 |
| zhenguo | I have added the engine manager unit tests, but need to add more, if anyone is interested in that, please take over :P | 02:05 |
| liusheng | awesome :) | 02:05 |
| zhenguo | liusheng: hah | 02:06 |
| zhenguo | Our tempest check still failed with the instance create tests, but seems we have got the reason, thanks liusheng for working on it | 02:06 |
| liusheng | zhenguo: yes, I am still stucked in it | 02:07 |
| shaohe_feng | zhenguo: a linke to address this task | 02:07 |
| liusheng | I have installed a devstack secucessfully, but it cannot creat a instance also | 02:07 |
| zhenguo | liusheng, shaohe_feng: seems it's failed in neutron port create task | 02:08 |
| RuiChen | any details? liusheng | 02:08 |
| shaohe_feng | zhenguo: any one interested in it, can take it, and mark it WIP | 02:08 |
| zhenguo | #link https://review.openstack.org/#/c/404552/ | 02:08 |
| shaohe_feng | zhenguo: any log? | 02:08 |
| liusheng | but it was not met the error in my devstack | 02:08 |
| zhenguo | shaohe_feng: yes, you can get the full logs from nimble, ironic and neutron | 02:09 |
| shaohe_feng | zhenguo: let me check it. | 02:09 |
| liusheng | zhenguo: it was timeout to wait in "building" state | 02:09 |
| zhenguo | shaohe_feng: thanks for the help | 02:09 |
| liusheng | shaohe_feng: thanks | 02:09 |
| zhenguo | liusheng: maybe we need to add more time for it :P | 02:09 |
| RuiChen | any error exist in neutron side log ? | 02:10 |
| zhenguo | RuiChen: I will dig later | 02:10 |
| RuiChen | thank you zhenguo | 02:10 |
| zhenguo | we still lack the basic abilities of powering instance in our nimbleclient :P | 02:11 |
| zhenguo | it's really appreciate if someone can take over it | 02:11 |
| zhenguo | shihanzhang: are you still working on nimbleclient? | 02:12 |
| zhenguo | oh, seems he is absent :( | 02:13 |
| RuiChen | sorry, I work on other things in this week | 02:13 |
| zhenguo | RuiChen: np, I would like to encourage more nimble guys also work on client things :) | 02:13 |
| liusheng | zhenguo: I can take over that after the tempest works :) | 02:14 |
| zhenguo | liusheng: really appreciate! | 02:14 |
| RuiChen | thanks liusheng, I can share the client experiencs with you | 02:15 |
| shaohe_feng | zhenguo: Maybe we realy need a wiki to track our task. | 02:15 |
| liusheng | RuiChen: thanks:) | 02:15 |
| shaohe_feng | zhenguo: such a ethpad | 02:15 |
| zhenguo | shaohe_feng: yes, but we have launchpad, which seems more general, but etherpad is a good place | 02:15 |
| zhenguo | #link https://github.com/openstack/nimble/blob/master/doc/source/api.rst | 02:16 |
| shaohe_feng | zhenguo: any one can mark the task item if he interest in it and take it. | 02:16 |
| zhenguo | do you remember this file? | 02:16 |
| liusheng | may we can file more bps :) | 02:16 |
| zhenguo | shaohe_feng: yes, I also like a checklist to track everyone's work :P | 02:16 |
| zhenguo | liusheng: yes, and bugs as well | 02:17 |
| RuiChen | drafting a BP to track features, I think we can start from simple BP describe | 02:17 |
| shaohe_feng | zhenguo: yes. task list can also be a track checklist | 02:17 |
| zhenguo | shaohe_feng: yes, or we can create a new trello dashboard | 02:18 |
| RuiChen | it's just common place to let others know what we are working | 02:18 |
| zhenguo | RuiChen: yes | 02:18 |
| shaohe_feng | zhenguo: trello is also OK. is it public? | 02:18 |
| zhenguo | shaohe_feng: sure, | 02:19 |
| liusheng | The bp in launchpad is nice, any new pache related to the bp will be automatically recorded in its whiteboard | 02:19 |
| liusheng | s/pache/patch | 02:19 |
| RuiChen | liusheng: good point! | 02:19 |
| zhenguo | liusheng, RuiChen: yes, we can use launchpad + trello | 02:20 |
| zhenguo | and specs | 02:20 |
| liusheng | zhenguo: maybe and releasenote, hah | 02:20 |
| zhenguo | I have added gerrit notification for nimble-specs yesterday, and will add the initial patch today | 02:20 |
| zhenguo | liusheng: hah, yes we have to think about when we should use releasenote | 02:21 |
| zhenguo | liusheng: do we plan to have a first release in Ocata? | 02:22 |
| RuiChen | thank you zhenguo, notification is important for reviewing | 02:22 |
| zhenguo | RuiChen: yes :P | 02:22 |
| openstackgerrit | Merged openstack/nimble: Updated from global requirements https://review.openstack.org/408106 | 02:22 |
| zhenguo | ok, not much of announcement, anyone else have a thing here? | 02:23 |
| RuiChen | hmmm, I think we need a new project name then first release, thought? | 02:23 |
| zhenguo | RuiChen: oh, yes, we need to change our project name | 02:23 |
| liusheng | RuiChen: I just want to point that :) | 02:23 |
| RuiChen | yeah, avoid the confusion, hah | 02:24 |
| zhenguo | the cinder PTL points out that nimble is a company name, and we have a nimble driver in cinder | 02:24 |
| RuiChen | any idea about new name? | 02:25 |
| zhenguo | I talked about the new name with liusheng last week | 02:25 |
| RuiChen | we might get some suggestion from community? like existed name list? | 02:25 |
| RuiChen | I'm not sure, but we can try to contract with community | 02:26 |
| zhenguo | RuiChen: seems like they don't have a list for that | 02:26 |
| zhenguo | we need to refer to our lawyer for the new name | 02:26 |
| shaohe_feng | We are good at giving Chinese Name: -P | 02:27 |
| RuiChen | that's shame, still exist big risk to get existed again | 02:27 |
| zhenguo | maybe it's ok if not conflict with big companies or product | 02:28 |
| zhenguo | shaohe_feng: agree | 02:28 |
| zhenguo | like we also have a phone named nova, lol | 02:28 |
| RuiChen | :-) | 02:29 |
| zhenguo | chinese name is a good option | 02:29 |
| zhenguo | or maybe some metals name like chrome :P | 02:29 |
| zhenguo | or some star name like supernova, lol | 02:30 |
| RuiChen | +1 for supernova :-) | 02:31 |
| zhenguo | RuiChen: lol | 02:31 |
| zhenguo | ok, we can discuss the new name later, | 02:32 |
| zhenguo | what's next | 02:32 |
| zhenguo | #topic open discussion | 02:32 |
| RuiChen | seriously, we have any alternative? | 02:32 |
| shaohe_feng | zhenguo: Intel has a project named nova | 02:33 |
| shaohe_feng | named supernova | 02:33 |
| liusheng | lol | 02:33 |
| zhenguo | Ruichen: not yet | 02:33 |
| zhenguo | shaohe_feng: hah | 02:33 |
| shaohe_feng | an opensource project, it means better than nova | 02:34 |
| zhenguo | shaohe_feng: that's a good name | 02:34 |
| zhenguo | how about using some metals name in the star? | 02:35 |
| liusheng | zhenguo: many words have been used :( | 02:35 |
| zhenguo | liusheng: yes, maybe using some rare work is a good option | 02:36 |
| zhenguo | s/work/word | 02:36 |
| shaohe_feng | zhenguo: prefix with metal? | 02:37 |
| shaohe_feng | zhenguo: metal_nova? | 02:37 |
| zhenguo | shaohe_feng: no, metals name like chrome, gold, silver, or something else | 02:38 |
| RuiChen | I found this reference http://governance.openstack.org/reference/service-project-naming.html | 02:38 |
| RuiChen | zhenguo: good idea, wide choose scope of metals name | 02:39 |
| zhenguo | RuiChen: thanks for the link, it also have a legal issues FAQ there | 02:40 |
| liusheng | osmium caesium | 02:41 |
| liusheng | they are used as a software name, it is OK ? | 02:42 |
| zhenguo | liusheng: does it used in pypi or launchpad? | 02:43 |
| liusheng | or change the caesium to caese like chromium to chrome | 02:43 |
| zhenguo | https://pypi.python.org/pypi/osmium/2.10.2 | 02:43 |
| liusheng | zhenguo: lol | 02:44 |
| liusheng | zhenguo: the caesium is the opposite of chrom | 02:44 |
| liusheng | zhenguo: the caesium is the opposite of chromium | 02:44 |
| zhenguo | liusheng: the base requirement is not conflict on pypi and launchpad | 02:45 |
| zhenguo | https://pypi.python.org/pypi/Caesium/0.3.1 | 02:45 |
| zhenguo | they are both occupied :( | 02:46 |
| liusheng | zhenguo: I mean may we can change it to caese, but it seems not a english word | 02:47 |
| zhenguo | liusheng: I think it's ok to create a new word, but which can be pronounced by english speakers | 02:48 |
| zhenguo | chinese pinyin like luoji, lol | 02:49 |
| shaohe_feng | seance prounce like caese | 02:49 |
| zhenguo | ok, I think everyone can provide two options for the new name before next meeting and we can make a decision then, wdyt? | 02:51 |
| shaohe_feng | coaster？ | 02:52 |
| liusheng | zhenguo: OK | 02:52 |
| RuiChen | +1 | 02:52 |
| zhenguo | shaohe_feng: coaster is also a company name, you can google it | 02:53 |
| RuiChen | https://zh.wikipedia.org/wiki/元素周期表 | 02:54 |
| RuiChen | hah | 02:54 |
| shaohe_feng | zhenguo: oh, hard for name | 02:54 |
| zhenguo | RuiChen: hah | 02:54 |
| zhenguo | shaohe_feng: yes | 02:55 |
| liusheng | zhenguo: I have read it, lol | 02:55 |
| zhenguo | hah, I think Zun is a good example | 02:56 |
| shaohe_feng | zhenguo: maybe a planet name or fixed star name | 02:57 |
| shaohe_feng | zhenguo: such as venus | 02:57 |
| shaohe_feng | zhenguo: what does zun means? | 02:57 |
| zhenguo | shaohe_feng: yes, but famus start name seems all occupied | 02:58 |
| zhenguo | china zun is a container for wine, | 02:58 |
| shaohe_feng | zhenguo: got it. | 02:58 |
| zhenguo | Kevin_zheng suggested we can use china ding, hah | 02:59 |
| liusheng | zhenguo: hah, just thought it | 02:59 |
| zhenguo | liusheng: lol | 02:59 |
| zhenguo | oh time is up | 03:00 |
| zhenguo | thanks y'all | 03:00 |
| zhenguo | #endmeeting | 03:01 |
| openstack | Meeting ended Thu Dec 8 03:01:07 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 03:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/nimble/2016/nimble.2016-12-08-02.00.html | 03:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nimble/2016/nimble.2016-12-08-02.00.txt | 03:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/nimble/2016/nimble.2016-12-08-02.00.log.html | 03:01 |
| shaohe_feng | shaohe_feng: saucer or tray or salver | 03:01 |
| shaohe_feng | zhenguo: chinese "碟子托盘" | 03:02 |
| zhenguo | shaohe_feng: does Intel have a rule or requirement for project name? | 03:02 |
| shaohe_feng | zhenguo: seems no. | 03:02 |
| zhenguo | shaohe_feng: for open source project, do you have legal issue? | 03:03 |
| shaohe_feng | zhenguo: any, but supernova, openstack do not like this name, so rename it. | 03:04 |
| shaohe_feng | zhenguo: no, we are otc | 03:04 |
| shaohe_feng | zhenguo: opensource technical center | 03:04 |
| zhenguo | shaohe_feng: ok, got it | 03:06 |
| shaohe_feng | zhenguo: saucer or tray or salver means it is a essential vessel, we can put other things on it | 03:10 |
| shaohe_feng | zhenguo: like baremetal, is also a essential apparatus, we support it. and then other application can run on it. | 03:11 |
| zhenguo | shaohe_feng: yes, we can check whether it confilict with other first and ask the lawyers | 03:13 |
| *** lei-zh has quit IRC | 03:19 | |
| *** lei-zh has joined #openstack-nimble | 03:21 | |
| zhenguo | RuiChen, liusheng, shaohe_feng: seems someone from china mobile would like to tests Nimble for their baremetal management | 03:36 |
| liusheng | zhenguo: good news | 03:36 |
| zhenguo | liusheng: hah | 03:37 |
| zhenguo | I remember china mobile has about 4000 servers, the biggest baremetal cluster all over the world. | 03:38 |
| liusheng | zhenguo: may they can contribute Nimble also :) | 03:39 |
| zhenguo | liusheng: not sure, but they may contribute bugs and requirements for us :P | 03:40 |
| liusheng | zhenguo: we never lack bugs ;-P | 03:41 |
| zhenguo | liusheng: lol | 03:41 |
| openstackgerrit | liusheng proposed openstack/nimble: Add tempest tests for instance creation(WIP) https://review.openstack.org/404552 | 03:44 |
| zhenguo | liusheng: I think we should add more debug logs instead of temporarily adding test logs, wdyt? | 03:50 |
| liusheng | zhenguo: yes, agree | 03:50 |
| zhenguo | liusheng: thanks | 03:50 |
| liusheng | zhenguo: expecially, the except Exception: xxx return, that is hard to debug :( | 03:51 |
| zhenguo | liusheng: yes, it's really bad for debugging, and that's the reason we don't solve the tempest gate failure yet, hah | 03:52 |
| zhenguo | liusheng: seems our functional api tests still not works | 03:54 |
| liusheng | zhenguo: which functional test ? | 03:55 |
| zhenguo | liusheng: instance related api | 03:56 |
| zhenguo | liusheng: I have to go for lunch, ttyl | 03:56 |
| * zhenguo away | 03:56 | |
| liusheng | zhenguo: enjoy :) | 03:56 |
| *** devlaps has quit IRC | 05:13 | |
| openstackgerrit | Zhenguo Niu proposed openstack/nimble: [WIP] Add update instance support https://review.openstack.org/407912 | 05:34 |
| openstackgerrit | liusheng proposed openstack/nimble: Add tempest tests for instance creation(WIP) https://review.openstack.org/404552 | 06:22 |
| zhenguo | ls | 06:59 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron [req-c013ff64-cd74-44a0-a5cb-a8405ea56dd4 tempest-BaremetalComputeAPIInstancesTest-560369720 tempest-BaremetalComputeAPIInstancesTest-560369720 - - -] (u'Could not create neutron port on network %(net)s for instance %(instance)s. %(exc)s', {'instance': 'ff283b3d-9fb0-4775-93ec-318a2621df45', 'net': u'dfd63917-7792-42cd-b2c3-68f94a5d47d3', 'exc': Forbidden()}) | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron Traceback (most recent call last): | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron File "/opt/stack/new/nimble/nimble/common/neutron.py", line 73, in create_port | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron port = client.create_port(body) | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 750, in create_port | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron return self.post(self.ports_path, body=body) | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 365, in post | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron headers=headers, params=params) | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 300, in do_request | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron self._handle_fault_response(status_code, replybody, resp) | 07:16 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 275, in _handle_fault_response | 07:17 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron exception_handler_v20(status_code, error_body) | 07:17 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 91, in exception_handler_v20 | 07:17 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron request_ids=request_ids) | 07:17 |
| liusheng | 2016-12-08 06:42:49.283 21802 ERROR nimble.common.neutron Forbidden: {'binding:host_id': <neutron_lib.constants.Sentinel object at 0x7f242ceab950>, 'description': '', 'allowed_address_pairs': <neutron_lib.constants.Sentinel object at 0x7f242ceab950>, 'admin_state_up': True, u'network_id': u'dfd63917-7792-42cd-b2c3-68f94a5d47d3', 'tenant_id': u'7b04ee63a0cb44e79514b027b8d70d6d', 'extra_dhcp_opts': None, 'name': '', 'device_owner': '', | 07:17 |
| liusheng | 'binding:vnic_type': 'normal', u'mac_address': u'52:54:00:18:d7:a5', 'binding:profile': <neutron_lib.constants.Sentinel object at 0x7f242ceab950>, 'port_security_enabled': <neutron_lib.constants.Sentinel object at 0x7f242ceab950>, 'project_id': u'7b04ee63a0cb44e79514b027b8d70d6d', 'fixed_ips': <neutron_lib.constants.Sentinel object at 0x7f242ceab950>, u'network:tenant_id': u'ff86326f8588442bb3137b85653a7abd', 'security_groups': | 07:17 |
| liusheng | <neutron_lib.constants.Sentinel object at 0x7f242ceab950>, 'device_id': ''} is disallowed by policy rule (rule:create_port and rule:create_port:mac_address) with {'domain': None, 'project_name': u'tempest-BaremetalComputeAPIInstancesTest-560369720', 'user_id': u'f10f019741434a4e877a1c845201509e', 'roles': [u'_member_', u'Member'], 'user_domain_id': None, 'project_domain': None, 'tenant_id': u'7b04ee63a0cb44e79514b027b8d70d6d', | 07:17 |
| liusheng | 'is_admin_project': True, 'project_id': u'7b04ee63a0cb44e79514b027b8d70d6d', 'is_admin': False, 'user': u'f10f019741434a4e877a1c845201509e', 'tenant_name': u'tempest-BaremetalComputeAPIInstancesTest-560369720', 'user_domain': None, 'user_name': u'tempest-BaremetalComputeAPIInstancesTest-560369720', 'tenant': u'7b04ee63a0cb44e79514b027b8d70d6d', 'project_domain_id': None} | 07:17 |
| liusheng | zhenguo: sorry for log flooding, lol, but could you find the reason ? | 07:17 |
| zhenguo | liusheng: hah | 07:17 |
| zhenguo | liusheng: seems like we are forbidden to create a port in the specified network | 07:19 |
| liusheng | zhenguo: it seems because the tempest user and project is not allowed to create port | 07:19 |
| liusheng | zhenguo: yes | 07:19 |
| zhenguo | liusheng: can we create a tenant work ourself | 07:20 |
| zhenguo | s/work/network | 07:20 |
| liusheng | zhenguo: and that may because we specified the private network, not dynamically create network in the tempest project | 07:20 |
| liusheng | zhenguo: because we cannot get tenant network which issue we met before | 07:21 |
| zhenguo | liusheng: maybe we should figure out why we can't get tenant network, as we still can't use the fixed network | 07:22 |
| liusheng | zhenguo: another question, I found before creating a port, it need to init a neutronclient, the neutronclient object will inited by the context.token | 07:23 |
| zhenguo | liusheng: yes | 07:24 |
| zhenguo | liusheng: you mean something wrong with to token? | 07:24 |
| liusheng | zhenguo: why don't use a group of service credentials config options like other projects | 07:24 |
| liusheng | zhenguo: the token include the tempest project and user | 07:24 |
| zhenguo | liusheng: we need to use the token to request neutron | 07:25 |
| liusheng | zhenguo: if we use service credentials, it will perform with admin role | 07:25 |
| zhenguo | liusheng: why we want admin role here | 07:25 |
| zhenguo | liusheng: like tempest project shouldn't create port on other tenants network, it's fair | 07:26 |
| zhenguo | liusheng: we only use admin credentials for ironic. | 07:27 |
| liusheng | zhenguo: AFAK, projects interact with another projects use the 'service' project and the {service_name} user, right ? | 07:27 |
| zhenguo | liusheng: not sure | 07:28 |
| liusheng | zhenguo: it is that in Ceilometer, but I am also not sure in other porjects | 07:28 |
| zhenguo | liusheng: I think it's ok here, | 07:29 |
| zhenguo | liusheng: it's not safe if you can use nova to create networks or ports in other projects | 07:29 |
| zhenguo | liusheng: you can only use the networks or images or volumes belong to you | 07:30 |
| liusheng | zhenguo: fair enough | 07:31 |
| liusheng | zhenguo: maybe it because ceilometer need to query all the resource in other projects, so it need to be performed in admin roles | 07:31 |
| zhenguo | liusheng: yes, I think so | 07:32 |
| liusheng | zhenguo: so, we still need to fix the "no tannant network" error. :( | 07:32 |
| zhenguo | liusheng: yes, I'm afraid we have to | 07:34 |
| openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add update instance support https://review.openstack.org/407912 | 07:38 |
| zhenguo | liusheng, shaohe_feng, lei-zh: before we decided to get instance power_state from ironic every time we try to get instance, I remember there's another option that we will cache the nodes from ironic, right? | 07:40 |
| liusheng | zhenguo: you means self.node_cache in the manager.py ? | 07:42 |
| liusheng | zhenguo: there is a periodic task to refresh the cache | 07:42 |
| zhenguo | liusheng: that's only cache for available nodes, I mean to add another list for active nodes | 07:42 |
| zhenguo | liusheng: yes | 07:43 |
| zhenguo | liusheng: then we don't need to fetch power_state from ironic via API every time we get instance | 07:43 |
| liusheng | zhenguo: I didn't remember a option like that | 07:44 |
| zhenguo | liusheng: hah, maybe you didn't contribute to nimble yet :P | 07:45 |
| liusheng | zhenguo: I guess so, hah | 07:46 |
| zhenguo | liusheng: haha, but cache that nodes, will also consuming resources as we need to periodically list all nodes from ironic | 07:46 |
| liusheng | zhenguo: that is sort of duplicated with the existed periodic task | 07:49 |
| zhenguo | liusheng: we can use one periodic task | 07:49 |
| zhenguo | liusheng: then we divided them into two groups, one is for scheduler, one is for instance states | 07:50 |
| liusheng | zhenguo: sounds reasonable | 07:51 |
| zhenguo | liusheng: Let's see what others think | 07:52 |
| liusheng | zhenguo: we need to create port with specified mac address, right ? | 07:53 |
| zhenguo | liusheng: yes | 07:53 |
| liusheng | zhenguo: "create_port:mac_address": "rule:context_is_advsvc or rule:admin_or_network_owner", in neutron's policy.json | 07:54 |
| zhenguo | liusheng: so the private network is public, but we can't create port with mac address, right? | 07:54 |
| liusheng | zhenguo: yes | 07:54 |
| liusheng | zhenguo: the user and project are created by tempest | 07:55 |
| zhenguo | liusheng: but how nova handle this? | 07:56 |
| zhenguo | liusheng: the neutron policy is just for gate devstack or it's the default rule | 07:57 |
| liusheng | zhenguo: I guess nova can get tenant work created by tempest it self | 07:57 |
| liusheng | zhenguo: it is the default rule | 07:57 |
| zhenguo | liusheng: I don't mean for tempest | 07:57 |
| zhenguo | liusheng: in the case that nova manage ironic node, but users specify a public network | 07:58 |
| liusheng | zhenguo: so the users may have admin role or the ower of the network, or have role 'advsvc' | 07:59 |
| zhenguo | liusheng: what does advsvc means? | 08:00 |
| liusheng | zhenguo: "context_is_advsvc": "role:advsvc", | 08:00 |
| liusheng | zhenguo: the definition of "rule:context_is_advsvc | 08:00 |
| zhenguo | liusheng: not sure what does that means, but anyway, we don't have a role like that | 08:01 |
| liusheng | zhenguo: yes | 08:02 |
| zhenguo | liusheng: tempest disable the tenant network creation explicitly for ironic, right? | 08:05 |
| liusheng | zhenguo: there is a option "fixed_network_name" that we added to specify the "private" network to user | 08:06 |
| liusheng | s/user/use | 08:06 |
| liusheng | zhenguo: it is a work around after we cannot fix the "no tenant network" error | 08:06 |
| zhenguo | liusheng: but it's not created by tempest project :( | 08:07 |
| liusheng | zhenguo: yes | 08:07 |
| zhenguo | liusheng: I rememeber you said templest will check some ironic options, then disable tenant network creation | 08:08 |
| liusheng | zhenguo: let me try again, and manully config the create_isolated_networks option as True | 08:10 |
| zhenguo | liusheng: good luck | 08:11 |
| liusheng | zhenguo: haha | 08:12 |
| openstackgerrit | liusheng proposed openstack/nimble: Add tempest tests for instance creation(WIP) https://review.openstack.org/404552 | 08:12 |
| liusheng | zhenguo: https://github.com/openstack/ironic/blob/master/devstack/lib/ironic#L1704-L1709 | 08:16 |
| liusheng | zhenguo: may you can check this in ironic | 08:16 |
| liusheng | zhenguo: I am not familar with ironic | 08:17 |
| zhenguo | liusheng: ok | 08:17 |
| zhenguo | liusheng: not sure why ironic disables multitenant network tests in tempest | 08:19 |
| liusheng | zhenguo: because it set create_isolated_networks to False, tempest won't create tenant network | 08:19 |
| zhenguo | liusheng: does tempest default to run all plugins? | 08:23 |
| zhenguo | liusheng: or we can make tempest only for nimble plugin | 08:23 |
| liusheng | zhenguo: no, it just run nimble's | 08:24 |
| zhenguo | liusheng: but why it configure ironic tempest | 08:24 |
| liusheng | if is_service_enabled tempest; then | 08:24 |
| liusheng | echo_summary "Configuring Tempest for Ironic needs" | 08:24 |
| liusheng | ironic_configure_tempest | 08:24 |
| liusheng | fi | 08:24 |
| liusheng | zhenguo: because we enabled tempest, and we enabled ironic, this script will always be run | 08:24 |
| zhenguo | liusheng: oh, shit | 08:24 |
| liusheng | the ironic_configure_tempest function will config the option to False | 08:24 |
| zhenguo | liusheng: but if we have many projects enabled, every one configure_tempest themselves, how to keep the order | 08:26 |
| liusheng | zhenguo: maybe we can fix it in Ironic, according the NOTE | 08:26 |
| zhenguo | liusheng: maybe it's not easy to fix it in ironic, as their multitenant gate also broken sometime | 08:27 |
| liusheng | zhenguo: :( | 08:27 |
| zhenguo | liusheng: we enable ironic plugin before nimble plugin in the tempest gate defination | 08:28 |
| zhenguo | liusheng: so if we enable that option in our devstack, I think it can change it back. | 08:28 |
| zhenguo | liusheng: you can have a try | 08:29 |
| zhenguo | if it works, adding a NOTE to explain the reason for it | 08:29 |
| liusheng | zhenguo: hope so, but I am afraid, there is reason why ironic disable the option, if we simply enable it, may broken somethin | 08:29 |
| zhenguo | liusheng: as we don't run ironic tempest plugin at all, so there shouldn't be any bad thing happen, | 08:30 |
| liusheng | zhenguo: another thing, when I search the option in whole tempest, I found: | 08:31 |
| liusheng | create_networks=(CONF.auth.create_isolated_networks and not | 08:31 |
| liusheng | CONF.baremetal.driver_enabled), | 08:31 |
| liusheng | zhenguo: the option seems related with the baremetal.driver_enabled option | 08:32 |
| liusheng | zhenguo: not sure | 08:32 |
| zhenguo | liusheng: what's create_networks? | 08:33 |
| liusheng | tempest/common/credentials_factory.py:67 | 08:33 |
| zhenguo | liusheng: I think if we only run nimble plugins, we can change anything we want in tempest, as it will not affect any other project | 08:34 |
| liusheng | zhenguo: yes, lets try | 08:35 |
| zhenguo | liusheng: change anything that blocks us :P | 08:35 |
| liusheng | zhenguo: I have manully enabled the create_isolated_networks in newest PS, but I am not sure what's order of nimble and ironic | 08:35 |
| zhenguo | liusheng: not sure as well | 08:36 |
| zhenguo | liusheng: but seems it will work | 08:36 |
| liusheng | zhenguo: god bless :P | 08:36 |
| * zhenguo brb | 08:40 | |
| openstackgerrit | liusheng proposed openstack/nimble: Add tempest tests for instance creation(WIP) https://review.openstack.org/404552 | 08:41 |
| zhenguo | hi all, as we will rename our project soon, do we need to use nimble-specs now or create a newname-specs later? | 08:58 |
| liusheng | zhenguo: seems it support to rename the repo | 09:12 |
| zhenguo | liusheng: but not automatically, need to wait gerrit downtime, and the admin rename it manually :( | 09:13 |
| zhenguo | liusheng: maybe need to wait for months | 09:13 |
| liusheng | zhenguo: :( | 09:13 |
| openstackgerrit | liusheng proposed openstack/nimble: Add tempest tests for instance creation(WIP) https://review.openstack.org/404552 | 09:15 |
| zhenguo | liusheng: does the tenant network created with the tempest config in nimble? | 09:16 |
| liusheng | zhenguo: yes, :) | 09:16 |
| zhenguo | liusheng: hah | 09:17 |
| liusheng | zhenguo: but it is timeout to wait active status, I change the timeout from 180s to 900s now | 09:17 |
| zhenguo | liusheng: ok | 09:17 |
| *** kevinz has quit IRC | 09:52 | |
| *** liusheng has quit IRC | 10:00 | |
| *** liusheng has joined #openstack-nimble | 10:01 | |
| *** liusheng has quit IRC | 10:06 | |
| *** liusheng has joined #openstack-nimble | 10:07 | |
| *** lei-zh has quit IRC | 10:46 | |
| zhenguo | luyao, shaohe_feng: are you around? | 11:05 |
| zhenguo | why we use graph flow instead of linear flow | 11:05 |
| liusheng | zhenguo: 2016-12-08 10:55:26.123 19793 ERROR ironic.conductor.utils [req-8d78f96c-f99b-4399-9dfd-fc6296d0b1b1 - - - - -] Timeout reached while waiting for callback for node 90abeb65-b1af-467b-8e39-7526eee355bd | 11:51 |
| liusheng | zhenguo: cannot find the reason :( | 11:51 |
| zhenguo | liusheng: really hard to debug | 11:53 |
| zhenguo | liusheng: is there something wrong in neutron logs? | 11:54 |
| liusheng | zhenguo: didn't find something wrong in Neutron | 11:57 |
| zhenguo | liusheng: do we get the heartbeat from ironic python agent? | 11:58 |
| zhenguo | liusheng: it's really hard to debug as we can't get ipa logs | 11:58 |
| liusheng | zhenguo: what is ipa | 11:59 |
| zhenguo | liusheng: http://logs.openstack.org/52/404552/16/check/gate-nimble-dsvm-tempest-plugin/1100dbf/logs/ironic-bm-logs/ | 11:59 |
| liusheng | zhenguo: it is run on the node ? | 11:59 |
| zhenguo | liusheng: it's the agent that boot when the node is deploying | 12:00 |
| liusheng | zhenguo: what the hell the log is.... lol | 12:01 |
| zhenguo | liusheng: seems not human readable, lol | 12:02 |
| zhenguo | liusheng: it's the node console log | 12:02 |
| liusheng | zhenguo: can you still craete nimble instance in your devstack ? | 12:06 |
| zhenguo | liusheng: I haven't test it | 12:06 |
| zhenguo | liusheng: and my env is too old | 12:06 |
| zhenguo | liusheng: is there some problems in you new env? | 12:07 |
| liusheng | zhenguo: I also cannot create instance sucessfully, it also show deploy failed in ironic | 12:07 |
| liusheng | zhenguo: looks like same issue | 12:07 |
| zhenguo | liusheng: that's wired | 12:07 |
| zhenguo | s/wired/weird | 12:08 |
| *** kevinz has joined #openstack-nimble | 13:35 | |
| *** kevinz has quit IRC | 14:30 | |
| *** kevinz has joined #openstack-nimble | 14:31 | |
| *** RuiChen has quit IRC | 14:46 | |
| *** kevinz has quit IRC | 14:46 | |
| *** kevinz has joined #openstack-nimble | 14:48 | |
| *** lei-zh has joined #openstack-nimble | 14:52 | |
| *** lei-zh has left #openstack-nimble | 15:00 | |
| *** kevinz has quit IRC | 15:11 | |
| *** kevinz has joined #openstack-nimble | 15:12 | |
| *** kevinz has quit IRC | 15:35 | |
| openstackgerrit | Merged openstack/nimble: Add update instance support https://review.openstack.org/407912 | 17:04 |
| *** liusheng has quit IRC | 21:11 | |
| *** liusheng has joined #openstack-nimble | 21:12 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!