| shaohe_feng | zhenguo: $ openstack baremetal compute instance show 2ff1bf8b-08c0-486f-8691-05f45fe98f57 -c created_at -c status -f json | 00:31 |
|---|---|---|
| shaohe_feng | zhenguo: { | 00:31 |
| shaohe_feng | "status": "building", | 00:31 |
| shaohe_feng | "created_at": "2016-12-15T03:38:19+00:00" | 00:31 |
| shaohe_feng | } | 00:31 |
| shaohe_feng | zhenguo: $ date | 00:32 |
| shaohe_feng | Thu Dec 15 20:25:30 CST 2016 | 00:32 |
| shaohe_feng | Y | 00:32 |
| shaohe_feng | zhenguo: I has build to long times | 00:33 |
| shaohe_feng | zhenguo: IMHO, something wrong with the instance | 00:33 |
| shaohe_feng | zhenguo: maybe network or volume | 00:34 |
| zhenguo | shaohe_feng: with the taskflow patch? | 00:34 |
| shaohe_feng | zhenguo: In these scenario, what should user do? | 00:34 |
| shaohe_feng | zhenguo: yes | 00:34 |
| zhenguo | shaohe_feng: the only way is to delete it | 00:35 |
| zhenguo | shaohe_feng: I have tested with the taskflow many times and it worked | 00:36 |
| shaohe_feng | zhenguo: so, there is no way for users to know what's wrong? | 00:36 |
| zhenguo | shaohe_feng: yes, we should make sure it goes to error state | 00:37 |
| zhenguo | shaohe_feng: you can test without the taskflow patch first to make sure your env is ok | 00:37 |
| shaohe_feng | zhenguo: so I need to test these cases: 1. create the instance as normal 2. terminate the creating process, such as delete. 3. delete the instance during creating 4. restart the nimble-engine during creating | 00:39 |
| shaohe_feng | zhenguo: any other cases? | 00:39 |
| shaohe_feng | zhenguo: 5. make the network error during creating | 00:40 |
| zhenguo | shaohe_feng: please don't test delete related cases now as we haven't refactor delete now | 00:40 |
| shaohe_feng | zhenguo: so 1, 4, 5 | 00:41 |
| zhenguo | shaohe_feng: and stop ironic during creating | 00:42 |
| shaohe_feng | zhenguo: OK. 6. stop ironic | 00:42 |
| zhenguo | shaohe_feng: ok, thanks | 00:43 |
| shaohe_feng | zhenguo: now, let discuss my scenario, Do you think, user should know some details about the creating, so they can know why it takes long time in building status? | 00:45 |
| shaohe_feng | zhenguo: or we has miss some edge case. In my scenario, the nimble should mark this as error, it should perceive there's something wrong with the create. | 00:48 |
| *** kevinz has joined #openstack-nimble | 01:10 | |
| *** yuntongjin has joined #openstack-nimble | 01:38 | |
| *** yuntongjin has quit IRC | 01:53 | |
| shaohe_feng | zhenguo: I'm in office now | 01:53 |
| zhenguo | shaohe_feng: hi | 01:57 |
| *** yuntongjin has joined #openstack-nimble | 01:57 | |
| shaohe_feng | zhenguo: Hi. | 02:06 |
| shaohe_feng | zhenguo: re-test. | 02:06 |
| shaohe_feng | zhenguo: report error. I'm debug it. | 02:06 |
| shaohe_feng | zhenguo: Failed to retrieve node by instance_uuid 0c95c2b8-0ff4-44e8-8529-bdef65│·········································· | 02:07 |
| shaohe_feng | 2257af from ironic api: Remote error: NotFound Not Found (HTTP 404) | 02:07 |
| shaohe_feng | zhenguo: $ openstack baremetal node list -f json -c UUID |grep UUID | 02:08 |
| shaohe_feng | zhenguo: "UUID": "f3289f56-f272-4695-b699-eb1033eb278f" | 02:08 |
| shaohe_feng | "UUID": "26f4524b-a1a9-48d9-b598-fc7bc104c3f4" | 02:09 |
| shaohe_feng | "UUID": "c83ee6e7-0d46-4451-a2f1-613ca73611f6" | 02:09 |
| shaohe_feng | zhenguo: but I run the ironic command, it can get the node. | 02:09 |
| zhenguo | shaohe_feng: with the taskflow patch? | 02:09 |
| zhenguo | shaohe_feng: that's because I have cleaned the instance_info from ironic node | 02:10 |
| zhenguo | shaohe_feng: so you can list the nodes but can't get it by instance_uuid :( | 02:10 |
| zhenguo | liusheng: if you are available, please help to test the taskflow patch as well, thanks! | 02:13 |
| liusheng | zhenguo: ok, will do that later | 02:14 |
| zhenguo | as it changes the basic codes, may block many other works | 02:14 |
| zhenguo | liusheng: thanks | 02:14 |
| shaohe_feng | zhenguo: OK. Ironic node: f3289f56-f272-4695-b699-eb1033eb278 | 02:15 |
| shaohe_feng | f virtual to physical interface count mismatch (Vif count: 2, Pif count: 1) | 02:15 |
| liusheng | zhenguo: np | 02:15 |
| shaohe_feng | zhenguo: I config two network. so it can not works. | 02:15 |
| shaohe_feng | zhenguo: I need to remove one of the network | 02:16 |
| zhenguo | shaohe_feng: yes, it will raise an exception in the network task, but not revert, only setinstanceinfo task revert | 02:16 |
| zhenguo | shaohe_feng: no, it's a test case | 02:16 |
| zhenguo | shaohe_feng: so you are stuck on the builing status , right? | 02:16 |
| shaohe_feng | zhenguo: it reports error. This is OK. | 02:17 |
| zhenguo | shaohe_feng: and the instance is set to be error? | 02:17 |
| shaohe_feng | zhenguo: testcase 7. with wrong parameters to create, for 2 networks. The instance status is "error" | 02:18 |
| shaohe_feng | zhenguo: yes. | 02:18 |
| zhenguo | shaohe_feng: nice | 02:18 |
| zhenguo | shaohe_feng: on yesterday's party, some china mobile guy said they will have more than 30000 bare metals in future, really exciting actually | 02:22 |
| shaohe_feng | zhenguo: really a good news. | 02:23 |
| shaohe_feng | zhenguo: https://etherpad.openstack.org/p/nimble-testcases-for-create | 02:23 |
| shaohe_feng | zhenguo: liusheng: we can add our manually tests in this link. | 02:24 |
| zhenguo | shaohe_feng: ok, I'm adding UT now, but can't tests the real flow work, only mock execute and revert in a single task. | 02:25 |
| shaohe_feng | zhenguo: How long does it take for building? | 02:32 |
| zhenguo | shaohe_feng: just a few miniutes | 02:32 |
| shaohe_feng | zhenguo: It has passed 4 minutes, still in building status | 02:32 |
| zhenguo | shaohe_feng: you can check the engine logs, it will looping call ironic to get the node status | 02:32 |
| shaohe_feng | zhenguo: yes. | 02:33 |
| shaohe_feng | zhenguo: 2016-12-15 22:27:00.785 DEBUG nimble.engine.flows.create_instance [-] Current ironic node state is wait call-back from (pid=18104) _wait_for_active /opt/stack/nimble/nimble/engine/flows/create_instance.py:298 | 02:34 |
| zhenguo | shaohe_feng: hah | 02:35 |
| shaohe_feng | zhenguo: $ sudo virsh list --all | 02:35 |
| shaohe_feng | Id Name State | 02:36 |
| shaohe_feng | ---------------------------------------------------- | 02:36 |
| shaohe_feng | 2 node-0 running | 02:36 |
| shaohe_feng | zhenguo: the node-0 is on running, sonmething wrong? | 02:36 |
| zhenguo | shaohe_feng: that means it's power on, and wait_call_back means it's still deploying | 02:37 |
| zhenguo | shaohe_feng: so, it's still in wait-call-back? | 02:38 |
| shaohe_feng | zhenguo: yes. | 02:40 |
| shaohe_feng | zhenguo: but, in mysql | 02:40 |
| shaohe_feng | zhenguo: mysql> select node_uuid from instances where UUID="4010b1f7-ac43-4d73-bfeb-8c9d22f71b52"; | 02:40 |
| shaohe_feng | +-----------+ | 02:40 |
| shaohe_feng | | node_uuid | | 02:40 |
| shaohe_feng | +-----------+ | 02:40 |
| shaohe_feng | | NULL | | 02:40 |
| shaohe_feng | +-----------+ | 02:40 |
| zhenguo | shaohe_feng: so the instance status is ? | 02:41 |
| *** openstackgerrit has joined #openstack-nimble | 02:41 | |
| openstackgerrit | liusheng proposed openstack/python-nimbleclient: Add support for updating instance https://review.openstack.org/411591 | 02:41 |
| shaohe_feng | zhenguo: $ openstack baremetal compute instance show 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52 -f json -c status | 02:41 |
| shaohe_feng | zhenguo: { "status": "building" } | 02:42 |
| zhenguo | shaohe_feng: that's weird, some exceptions in engine logs? | 02:42 |
| zhenguo | shaohe_feng: I think it triggers the setinstanceinfo revert to clean instance_info and instance_uuid from the ironic node | 02:43 |
| zhenguo | shaohe_feng: maybe loopingcall timeout is raised | 02:43 |
| shaohe_feng | zhenguo: many logs on "Current ironic node state is wait call-back" | 02:44 |
| zhenguo | shaohe_feng: no other logs? | 02:44 |
| shaohe_feng | zhenguo: some many logs, let me find other clue | 02:45 |
| shaohe_feng | zhenguo: another log "Running periodic task EngineManager._sync_node_resources" | 02:46 |
| shaohe_feng | zhenguo: this is not an error | 02:47 |
| zhenguo | shaohe_feng: so no any error log? | 02:47 |
| zhenguo | shaohe_feng: you can show the ironic node to see wheter it has instance_uuid and instance_info | 02:48 |
| shaohe_feng | zhenguo: yes, and other logs for AMQP, recieve msg, and reply msg. | 02:48 |
| shaohe_feng | zhenguo: yes, good idea. | 02:48 |
| shaohe_feng | zhenguo: in mysql or cmd-line? | 02:49 |
| zhenguo | shaohe_feng: CLI | 02:49 |
| zhenguo | ironic node-show | 02:49 |
| liusheng | zhenguo: shaohe_feng I can create instance sucessfully with the taskflow patch | 02:51 |
| zhenguo | liusheng: nice | 02:51 |
| zhenguo | liusheng: and maybe need to test with some exceptions | 02:52 |
| liusheng | zhenguo: I assume the current Nimble cannot work with most exception scenarios, hah | 02:54 |
| zhenguo | liusheng: hah, | 02:55 |
| shaohe_feng | zhenguo: $ openstack baremetal node list |grep f3289f56-f272-4695-b699-eb1033eb278f | 02:55 |
| shaohe_feng | zhenguo: | f3289f56-f272-4695-b699-eb1033eb278f | node-0 | 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52 | power on | wait call-back | | 02:55 |
| zhenguo | liusheng: yes, although it can't work, I want to see whether it reverts to a state we expected. | 02:55 |
| shaohe_feng | zhenguo: it has instance UUID 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52, that's right | 02:56 |
| zhenguo | shaohe_feng:ｙｅｓ | 02:56 |
| shaohe_feng | zhenguo: and it is "wait call-back" | 02:56 |
| zhenguo | shaohe_feng：there is still no error log in you engine log? | 02:57 |
| zhenguo | shaohe_feng: and you instance doesn't associate with any node? | 02:57 |
| shaohe_feng | zhenguo: $ openstack baremetal compute instance list |grep 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52 | 02:58 |
| shaohe_feng | zhenguo: | 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52 | test_instance1 | | building | | | 02:58 |
| shaohe_feng | zhenguo: yes. let me try the mysql again | 02:58 |
| liusheng | zhenguo, shaohe_feng: which exception scenario do you want to expect to test ? | 03:01 |
| zhenguo | liusheng: https://etherpad.openstack.org/p/nimble-testcases-for-create | 03:01 |
| liusheng | zhenguo: ok | 03:02 |
| shaohe_feng | zhenguo: $ openstack baremetal node list | 03:02 |
| shaohe_feng | zhenguo: the status of first node, node-0 is "clean wait" | 03:03 |
| shaohe_feng | zhenguo: the status node-1 is "wait call-back" | 03:03 |
| zhenguo | shaohe_feng: so there's a rescheduling occurred | 03:04 |
| zhenguo | shaohe_feng: if so, there must be some logs | 03:04 |
| shaohe_feng | zhenguo: does this is right, when "wait call-back", we should not assign the node-uuid to instance | 03:04 |
| shaohe_feng | zhenguo: yes, some logs | 03:07 |
| shaohe_feng | zhenguo: first there is a bug: | 03:08 |
| shaohe_feng | zhenguo: Failed to provision instance 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52: Timeout reached while waiting for call | 03:08 |
| shaohe_feng | back for node f3289f56-f272-4695-b699-eb1033eb278f | 03:08 |
| liusheng | zhenguo, shaohe_feng the *error* state of instance after creating instance with two netowrks is expected ? | 03:09 |
| liusheng | Ironic node: 0fe83120-4132-49ae-90b7-835198e6f155 virtual to physical interface count mismatch (Vif count: 2, Pif count: 1) | 03:10 |
| liusheng | transitioned into state 'FAILURE' from state 'RUNNING' | 03:10 |
| liusheng | NoValidNode: Exceeded max scheduling attempts 3 for instance 33db0e39-e7d9-4ea9-ae16-a084195a4b00 | 03:10 |
| zhenguo | shaohe_feng: Tiemout triggers the rescheduling process, but the new node-uuid should be set to the instance | 03:10 |
| shaohe_feng | zhenguo: yes, then do rescheduing find another node. | 03:11 |
| zhenguo | liusheng: yes, we just have one physical interface in ironic node | 03:11 |
| liusheng | zhenguo: so it seems works ok | 03:12 |
| zhenguo | liusheng: we expect the ironic node instance info and instance uuid has been cleaned in this scenario | 03:12 |
| zhenguo | shaohe_feng: yes, find another node and set it to the instance | 03:12 |
| liusheng | zhenguo: the instance uuid didn't be set to the ironic node in my env | 03:13 |
| zhenguo | liusheng: yes, because SetInstance task revert to clean it | 03:13 |
| liusheng | zhenguo: so it is OK! | 03:14 |
| zhenguo | liusheng: yes, and the instance status is error, right? | 03:14 |
| liusheng | zhenguo: yes | 03:14 |
| zhenguo | liusheng:ｎｉｃｅ | 03:14 |
| zhenguo | liusheng: if instance_info and instance_uuid left in the ironic node, the node will be never used again | 03:15 |
| liusheng | zhenguo: yes | 03:15 |
| * zhenguo brb | 03:16 | |
| shaohe_feng | zhenguo: so we must clean the instance_info and instance_uuid when no instance associated to this node. | 03:17 |
| shaohe_feng | zhenguo: Task 'nimble.engine.flows.create_instance.ScheduleCreateInstanceTask;instance:create' (43507aae-5419-4a4e-a5ca-2716e643cc18) transitioned into state 'SUCCESS' from state 'RUNNING' with result 'None' | 03:18 |
| shaohe_feng | zhenguo: So here, 43507aae-5419-4a4e-a5ca-2716e643cc18 is the uuid of a task? but I did not find a task db in mysql | 03:19 |
| shaohe_feng | zhenguo: and the state 'SUCCESS' or 'RUNNING' is also the tasks? | 03:19 |
| shaohe_feng | zhenguo: seem all log is OK. and it reports find a port successfully for the node. | 03:21 |
| shaohe_feng | zhenguo: until this error: | 03:23 |
| shaohe_feng | l InstanceDeployFailure: Failed to provision instance 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52: Timeout reached while waiting for callback for node f3289f56-f272-4695-b699-eb1033eb278f | 03:23 |
| zhenguo | shaohe_feng: yes | 03:27 |
| *** yuntongjin has quit IRC | 03:28 | |
| zhenguo | shaohe_feng: if InstanceDeployFailure, it will trigger revert, first the CreateInstance task revert then Network revert and then SetInstanceinfo revert and trigger the OnfailureRescheulding revert to cast a rpc call to create_instance again | 03:29 |
| shaohe_feng | zhenguo: why Timeout? | 03:29 |
| zhenguo | shaohe_feng: then if max attempts of rescheduling reached, the Schedule task revert will clean the node_uuid | 03:29 |
| zhenguo | shaohe_feng: because the node status is in wait call back for a long time | 03:30 |
| shaohe_feng | zhenguo: sounds reasonable. | 03:30 |
| shaohe_feng | zhenguo: why can not call back? | 03:30 |
| zhenguo | shaohe_feng: there's many reasons, | 03:31 |
| zhenguo | shaohe_feng: like when ironic node starts but can't get an IP from the neutron network | 03:31 |
| zhenguo | shaohe_feng: or something wrong with the IPA during depoying | 03:32 |
| zhenguo | shaohe_feng: there must be something wrong with your env, but we should also handle that error | 03:33 |
| zhenguo | shaohe_feng: so currently you only get one Timeout exception and rescheduling then no new node uuid associated the instance, but the node is in wait call back state? | 03:34 |
| zhenguo | shaohe_feng: during revering we also cleaned the create ports in neutron, and clean the port association information in ironic | 03:34 |
| zhenguo | s/revering/ reverting | 03:35 |
| shaohe_feng | zhenguo: yes. | 03:40 |
| shaohe_feng | zhenguo: I can seen unplug log. | 03:40 |
| shaohe_feng | zhenguo: now another error: | 03:41 |
| zhenguo | shaohe_feng: so the instance status is still in building and without a node associate it, right? | 03:41 |
| shaohe_feng | zhenguo: 2016-12-15 23:24:04.818 TRACE taskflow.engines.action_engine.engine NetworkError: Could not remove VIF 93405cd4-0f8e-4cfa-b0fb-385c6fb8a161 of instance 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52, possibly a network issue: auth_url was not provided to the Neutron client | 03:41 |
| shaohe_feng | zhenguo: let me check | 03:41 |
| shaohe_feng | zhenguo: it is still in building | 03:42 |
| shaohe_feng | zhenguo: I find my keystone use fernet-key this time to build the evn by devstack | 03:43 |
| zhenguo | shaohe_feng: I find a issue, because after OnFailureRescheduleTask cast a create instance rpc, the ScheduleTask revert will clean the node_uuid, there a race | 03:44 |
| zhenguo | shaohe_feng: maybe it's not proper to add the clean node_uuid action to ScheduleTask revert | 03:45 |
| zhenguo | shaohe_feng: I will find another place to clean the instance node_uuid, and the reason why I want to clean this is that, I don't want to do the clean resouces work again if our revert is successfully | 03:47 |
| * zhenguo away for lunch | 04:04 | |
| *** yuntongjin has joined #openstack-nimble | 06:02 | |
| openstackgerrit | liusheng proposed openstack/nimble: Fix the AttributeError when list available zones https://review.openstack.org/411655 | 06:59 |
| shaohe_feng | zhenguo: still building. | 07:07 |
| zhenguo | shaohe_feng: the ironic node status is...? | 07:07 |
| shaohe_feng | zhenguo: IMHO, the scheduler has tried all nodes, and failed, so it should be error. | 07:08 |
| shaohe_feng | zhenguo: let me check. | 07:08 |
| shaohe_feng | zhenguo: You think, there is race, so the node-uuid does not attched to instance? | 07:09 |
| shaohe_feng | zhenguo: $ openstack baremetal node list | 07:10 |
| shaohe_feng | | UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance | | 07:10 |
| shaohe_feng | | f3289f56-f272-4695-b699-eb1033eb278f | node-0 | None | power off | clean failed | True | | 07:10 |
| shaohe_feng | | 26f4524b-a1a9-48d9-b598-fc7bc104c3f4 | node-1 | None | power off | clean failed | True | | 07:10 |
| shaohe_feng | | c83ee6e7-0d46-4451-a2f1-613ca73611f6 | node-2 | None | power off | available | False | | 07:11 |
| *** yuntongjin has quit IRC | 07:11 | |
| shaohe_feng | zhenguo: call you by wechat? | 07:12 |
| zhenguo | shaohe_feng: so it's still in building status? seems it didn't try all nodes, as node-2 is still availble | 07:27 |
| zhenguo | shaohe_feng: you can call my phone | 07:28 |
| zhenguo | shaohe_feng: so I think there are two Timeout exceptions in your log, and rescheduling doesn't reach the max attempts, right? | 07:29 |
| openstackgerrit | Merged openstack/nimble: Replace six.iteritems() with .items() https://review.openstack.org/407824 | 07:29 |
| shaohe_feng | zhenguo: why does the scheduler stop try? | 07:30 |
| zhenguo | shaohe_feng: not sure | 07:32 |
| zhenguo | shaohe_feng: any new clue in your log? | 07:32 |
| zhenguo | shaohe_feng: please remove the revert method in ScheduleTask, and try again | 07:33 |
| shaohe_feng | zhenguo: Could not remove VIF 93405cd4-0f8e-4cfa-b0fb-385c6fb8a161 of instance 4010b1f7-ac43-4d73-bfeb-8c9d22f71b52, possibly a network issue: auth_url was not provided to the Neutron client | 07:37 |
| shaohe_feng | zhenguo: Traceback | 07:37 |
| shaohe_feng | 2016-12-15 23:24:04.801 TRACE nimble.common.neutron NoAuthURLProvided: auth_url was not provided to the Neutron client | 07:37 |
| zhenguo | shaohe_feng: maybe something wrong with your keystone | 07:37 |
| shaohe_feng | zhenguo: so, scheduler stop is also this reason? | 07:38 |
| zhenguo | shaohe_feng: I read some openttack insight report this moring, it said keystone has changed it's default token type, maybe that's the cause of your problem | 07:39 |
| zhenguo | shaohe_feng: no, | 07:39 |
| shaohe_feng | zhenguo: I update all project repo before run the devstack | 07:40 |
| zhenguo | shaohe_feng: you can search the scheduler retries information in your logs to see why, it will present how many times of the retries | 07:40 |
| zhenguo | shaohe_feng: maybe that's the problem | 07:40 |
| shaohe_feng | zhenguo: what's the default value. | 07:40 |
| zhenguo | shaohe_feng: let me check | 07:41 |
| zhenguo | shaohe_feng: changed from uuid to fernet | 07:43 |
| shaohe_feng | zhenguo: Oh, got it. I did not upgrade the devstack | 07:47 |
| shaohe_feng | zhenguo: so the devstack should help me to create the fernet dir and key. | 07:47 |
| zhenguo | shaohe_feng: not sure, but you can try to upgrade devstack first | 07:48 |
| shaohe_feng | zhenguo: yes. | 07:48 |
| shaohe_feng | zhenguo: I should fix it manually. | 07:48 |
| zhenguo | shaohe_feng:ｙｅｓ | 07:49 |
| shaohe_feng | zhenguo: I should not fix it manually. | 07:49 |
| zhenguo | shaohe_feng: oh, yes, haha | 07:49 |
| shaohe_feng | so bad. | 07:50 |
| zhenguo | shaohe_feng: I talked with some guys at yesterday's party, seems they are curious about what capabilites we can provide in O release | 07:53 |
| zhenguo | and liusheng :P | 07:54 |
| zhenguo | shaohe_feng, liusheng: and someone invited me to introduce nimble on next Beijing OpenStack Meetup activities. | 07:56 |
| liusheng | zhenguo: :) | 07:57 |
| zhenguo | liusheng: hah | 07:58 |
| *** yuntongjin has joined #openstack-nimble | 07:58 | |
| liusheng | zhenguo: I am coding, what are you talking about, lol | 07:58 |
| zhenguo | liusheng: lol | 07:59 |
| liusheng | zhenguo: it is a good chance to introduce Nimble to more people | 07:59 |
| zhenguo | liusheng: yes, maybe attract new contributors | 08:00 |
| liusheng | zhenguo: yeah, really hope more new comers | 08:01 |
| zhenguo | liusheng: not that easy, they said many big tent projects or even core projects don't have many contributor as before now | 08:02 |
| liusheng | zhenguo: yes, that is current situation | 08:03 |
| zhenguo | liusheng: yes, so actually we are active than many big tent projects | 08:06 |
| liusheng | zhenguo: hah, if there is real requirement, I think more contributor will be insterested in it | 08:09 |
| zhenguo | liusheng: yes, hah | 08:12 |
| shaohe_feng | zhenguo: call again | 08:13 |
| zhenguo | shaohe_feng: our espace can't call that number :( | 08:13 |
| shaohe_feng | zhenguo: let me call you | 08:13 |
| zhenguo | shaohe_feng: ok | 08:13 |
| shaohe_feng | zhenguo: you number? | 08:14 |
| zhenguo | shaohe_feng: oh, I don't have a number, only my phone number, lol | 08:14 |
| shaohe_feng | zhenguo: espace number? | 08:15 |
| zhenguo | shaohe_feng: I remeber JF used a web conference tool before | 08:15 |
| shaohe_feng | zhenguo: +1 (861) 832-9035 | 08:15 |
| zhenguo | shaohe_feng: no, it's a internal chat tools | 08:15 |
| shaohe_feng | zhenguo: you can call me | 08:15 |
| openstackgerrit | liusheng proposed openstack/python-nimbleclient: Support availability zone in nimbleclient https://review.openstack.org/411690 | 08:15 |
| zhenguo | shaohe_feng: let me try | 08:16 |
| openstackgerrit | liusheng proposed openstack/nimble: Fix the AttributeError when list available zones https://review.openstack.org/411655 | 08:22 |
| zhenguo | liusheng: have you tested the 'uuid as primary key' patch | 08:34 |
| liusheng | zhenguo: yes | 08:35 |
| zhenguo | liusheng: ok, thanks | 08:35 |
| zhenguo | liusheng: thanks for taking over the client work, really appreciate :) | 09:05 |
| liusheng | zhenguo: np:) | 09:14 |
| *** yuntongjin has quit IRC | 09:16 | |
| openstackgerrit | Merged openstack/nimble: Use uuid as the primary key https://review.openstack.org/405165 | 09:17 |
| openstackgerrit | Merged openstack/nimble: Fix the AttributeError when list available zones https://review.openstack.org/411655 | 09:20 |
| openstackgerrit | liusheng proposed openstack/python-nimbleclient: Add support for setting power state for instance https://review.openstack.org/411729 | 09:41 |
| openstackgerrit | liusheng proposed openstack/python-nimbleclient: Add support for setting power state for instance https://review.openstack.org/411729 | 09:49 |
| *** kevinz has quit IRC | 10:02 | |
| openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add create instance taskflow https://review.openstack.org/403555 | 10:06 |
| shaohe_feng | zhenguo: still not assign node uuid. I need go throgh the patch. | 10:15 |
| *** openstackgerrit has quit IRC | 10:18 | |
| *** openstackgerrit has joined #openstack-nimble | 11:31 | |
| openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add create instance taskflow https://review.openstack.org/403555 | 11:31 |
| openstackgerrit | Zhenguo Niu proposed openstack/nimble: Remove unused fake_constants.py https://review.openstack.org/411767 | 11:35 |
| *** shihanzhang has quit IRC | 13:12 | |
| openstackgerrit | Merged openstack/nimble: Remove unused fake_constants.py https://review.openstack.org/411767 | 14:40 |
| openstackgerrit | Zhenguo Niu proposed openstack/nimble: Add create instance taskflow https://review.openstack.org/403555 | 15:15 |
| *** liusheng has quit IRC | 18:58 | |
| *** liusheng has joined #openstack-nimble | 19:21 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!