| *** l4yerffeJ has quit IRC | 00:51 | |
| *** l4yerffeJ has joined #openstack-nimble | 00:51 | |
| *** kevinz has joined #openstack-nimble | 01:08 | |
| zhenguo | morning nimble! | 02:07 |
|---|---|---|
| *** yuntongjin has joined #openstack-nimble | 02:08 | |
| shaohe_feng | zhenguo: morning | 02:10 |
| zhenguo | shaohe_feng: o/ | 02:10 |
| zhenguo | shaohe_feng: have you consulted the lawyer about our new name Mogan :P | 02:11 |
| *** l4yerffeJ has quit IRC | 02:15 | |
| zhenguo | liusheng: wrt https://review.openstack.org/#/c/412350/ , why other core projects all maintain a native context ? | 02:15 |
| *** l4yerffeJ has joined #openstack-nimble | 02:16 | |
| liusheng | zhenguo: I think there are two reasons:1. the project need specific requirements; 2. there is no person to update the code since many functionalities the native context implementated has been supportted in oslo_context | 02:17 |
| zhenguo | liusheng: hah, so we don't need specific requirements? | 02:18 |
| liusheng | zhenguo: as I found in Nimble, all the functionlities can be directly support by oslo_context | 02:18 |
| zhenguo | liusheng: yes, seems not | 02:18 |
| zhenguo | liusheng: ok, thanks for the clean up, but I'm curious about what specific requirements like, will we need in future? | 02:19 |
| liusheng | zhenguo: at least we don't need currently :), but if we have specifc requiremet, we should also implement based on the current oslo_context | 02:19 |
| zhenguo | liusheng: yes, agree | 02:20 |
| liusheng | zhenguo: thanks for pay attention to that with your valuable time, hah :) | 02:21 |
| liusheng | zhenguo: FYI, I am try to add support for console in Nimble | 02:22 |
| zhenguo | liusheng: hah, seems I'm free from the POC | 02:22 |
| liusheng | zhenguo: really, good news | 02:22 |
| zhenguo | liusheng: thanks, but for console, do you plan to use nova console proxy? | 02:22 |
| liusheng | zhenguo: I don't know, I am just starting to study the nova implementation now | 02:23 |
| liusheng | zhenguo: do you have any suggestion ? | 02:23 |
| zhenguo | liusheng: in fact, I have a solution about ironic console | 02:24 |
| zhenguo | liusheng: and I have finished the nova proxy, and it works | 02:24 |
| liusheng | zhenguo: really? cool | 02:24 |
| zhenguo | liusheng: but that based on shellinabox, and it's used in our product | 02:24 |
| liusheng | zhenguo: how about decoup from nova-proxy | 02:24 |
| zhenguo | liusheng: but the community didn't accept it finally, and use another solution | 02:25 |
| liusheng | zhenguo: :( | 02:25 |
| zhenguo | liusheng: I think we need to reuse the nova-proxy | 02:25 |
| zhenguo | liusheng: there are a few proxy types, currently ironic leverage serialconsole-proxy | 02:26 |
| liusheng | zhenguo: so we cannot to get rid of nova-proxy ? | 02:26 |
| zhenguo | liusheng: unless you copy it here :P | 02:26 |
| liusheng | zhenguo: :( | 02:28 |
| zhenguo | liusheng: hah | 02:28 |
| zhenguo | liusheng: before the console work, seems we still don't have your functional tests landed yet :( | 02:28 |
| zhenguo | liusheng: about the instance related tests | 02:29 |
| liusheng | zhenguo: sounds like I should put that console task aside temporarily | 02:29 |
| liusheng | zhenguo: yes | 02:29 |
| liusheng | zhenguo: you mean functional tests or tempest ? | 02:30 |
| zhenguo | liusheng: functional | 02:30 |
| liusheng | zhenguo: i think the tempest is realy urgent | 02:30 |
| zhenguo | liusheng: hah | 02:30 |
| liusheng | zhenguo: oh, I can fix the patch later | 02:30 |
| zhenguo | liusheng: thanks, I will dig out why the tempest doesn't work | 02:31 |
| liusheng | zhenguo: thanks | 02:31 |
| *** l4yerffeJ has quit IRC | 02:32 | |
| *** l4yerffeJ_ has joined #openstack-nimble | 02:32 | |
| zhenguo | liusheng: but maybe after I finish the current task :D | 02:33 |
| * liusheng need to devote himself to coding, since he has set a big FLAG (commits 100+) :( | 02:34 | |
| liusheng | zhenguo: L) | 02:34 |
| liusheng | zhenguo: which task is high priority now :) | 02:35 |
| zhenguo | liusheng: I think config drive and floating ip | 02:36 |
| zhenguo | liusheng: and maybe we need to add keypair related API | 02:37 |
| zhenguo | liusheng: does nova manage keypair itself | 02:37 |
| liusheng | zhenguo: yes | 02:38 |
| liusheng | zhenguo: ok, I will pick one firstly | 02:38 |
| zhenguo | liusheng: thanks | 02:38 |
| *** yuntongjin has quit IRC | 03:22 | |
| zhenguo | liusheng: I will try to help you reach commits 100+ ASAP :P | 03:34 |
| liusheng | zhenguo: haha | 03:34 |
| liusheng | zhenguo: thanks a lot | 03:35 |
| shaohe_feng | zhenguo: I'm back. | 03:35 |
| zhenguo | shaohe_feng: welcome back!!!! | 03:35 |
| liusheng | shaohe_feng: welcome! | 03:35 |
| shaohe_feng | zhenguo: yutong talks with me about some nimble status. | 03:35 |
| shaohe_feng | zhenguo: I'm just leave an hours. so passionate welcome. Haha | 03:36 |
| shaohe_feng | liusheng: ^ | 03:36 |
| zhenguo | liusheng: lol, then you are well deserved to be a nimble core! | 03:36 |
| liusheng | zhenguo: hah, thanks | 03:37 |
| zhenguo | shaohe_feng: haha | 03:37 |
| liusheng | shaohe_feng: always welcome you | 03:37 |
| liusheng | zhenguo: :) | 03:37 |
| shaohe_feng | haha | 03:38 |
| shaohe_feng | zhenguo: I looks into bifrost. seems it looks like a deploying tools. | 03:42 |
| zhenguo | shaohe_feng: yes, it's used to deploy for standalone mode | 03:44 |
| zhenguo | shaohe_feng: it seems like can also deploy node by leveraging ansible | 03:44 |
| shaohe_feng | zhenguo: so no configdrive can be leveraged. :( | 03:45 |
| zhenguo | shaohe_feng: you can see how nova use it | 03:46 |
| zhenguo | shaohe_feng: with configdrive, we can support keypair and password | 03:47 |
| shaohe_feng | zhenguo: yes. But's sometimes I try to avoid nova. because other project launched later than nova. So They do better than nova | 03:47 |
| zhenguo | shaohe_feng: hah | 03:48 |
| zhenguo | shaohe_feng: yes, but we should stand on top of nova instead of doing everything ourselves | 03:48 |
| shaohe_feng | zhenguo: yes. avoid repetition of rolling | 03:49 |
| zhenguo | shaohe_feng: yes | 03:49 |
| shaohe_feng | zhenguo: we can see, such as the authorization framework and quotas, neutron has do improvement. | 03:50 |
| zhenguo | shaohe_feng: yes, neutron and cinder are copied from nova at first, but they both do improvement | 03:52 |
| * zhenguo away | 03:53 | |
| shaohe_feng | zhenguo: also the taskflow in cinder. :) | 03:57 |
| openstackgerrit | Merged openstack/nimble: Fix the instance type extra related APIs https://review.openstack.org/413053 | 04:04 |
| openstackgerrit | Merged openstack/nimble: Correct the api samples of type extra APIs https://review.openstack.org/413056 | 04:04 |
| openstackgerrit | Merged openstack/python-nimbleclient: Remove python2.4 compatibility support https://review.openstack.org/412697 | 04:59 |
| openstackgerrit | Merged openstack/python-nimbleclient: Add Python 3.5 classifier and venv https://review.openstack.org/412700 | 05:02 |
| *** yuntongjin has joined #openstack-nimble | 05:21 | |
| *** yuntongjin has quit IRC | 05:28 | |
| *** yuntongjin has joined #openstack-nimble | 05:50 | |
| *** l4yerffeJ has joined #openstack-nimble | 06:17 | |
| *** Jeffrey4l has quit IRC | 06:20 | |
| *** l4yerffeJ_ has quit IRC | 06:21 | |
| liusheng | zhenguo: hi zhenguo, wichi API or command you tested with https://review.openstack.org/#/c/412350/ that show many KeyError 'user_id' ? | 06:21 |
| zhenguo | liusheng: when start nimble-engine it shows KeyError, seems every API can cause many errors | 06:25 |
| zhenguo | liusheng: it's ok in your env? | 06:26 |
| liusheng | zhenguo: yes | 06:26 |
| liusheng | zhenguo: I cannot find any keyerror | 06:27 |
| zhenguo | liusheng: oh, that's weired | 06:27 |
| zhenguo | liusheng: I will check again | 06:27 |
| zhenguo | liusheng: I have pasted the log there | 06:33 |
| openstackgerrit | Merged openstack/nimble: Refactor network APIs https://review.openstack.org/413154 | 06:34 |
| *** Jeffrey4l has joined #openstack-nimble | 06:35 | |
| liusheng | zhenguo: I can create isntance sucessfully with that patch, maybe I know the reason of the "KeyError", seems is because your log format configurations | 06:37 |
| zhenguo | liusheng: it doesn't affect functionalities, yes seems just when logging | 06:37 |
| zhenguo | liusheng: yes, I can find user_id in my loging_context_format_string | 06:38 |
| liusheng | zhenguo: let mye try | 06:38 |
| liusheng | zhenguo: does the user_id in your nimble.conf ? | 06:39 |
| zhenguo | liusheng: yes, | 06:39 |
| zhenguo | liusheng: but logging_context_format_string is by default | 06:39 |
| liusheng | zhenguo: yes, but it should be user and tenant than user_id and project_id | 06:39 |
| liusheng | zhenguo: just reference the ironic.conf | 06:40 |
| liusheng | zhenguo: since I have removed the lines of logging format in my nimble.conf, lol | 06:40 |
| zhenguo | liusheng: haha | 06:40 |
| zhenguo | liusheng: why ironic use a different format | 06:41 |
| liusheng | zhenguo: can your please paste the lines in nimble.conf about the logging formant ? | 06:41 |
| liusheng | zhenguo: I don't know, but I think the ironic's configuration is correct | 06:42 |
| zhenguo | liusheng: user_id, project_id, instance, message | 06:42 |
| zhenguo | liusheng: agree, but how could we handle that | 06:43 |
| liusheng | zhenguo: seems the lines is automatically added when installed devstack, but it won't be added in the jenkins' job's devstac, that is why the jobs didn | 06:45 |
| liusheng | didn't failed | 06:45 |
| zhenguo | liusheng: seems it is | 06:46 |
| liusheng | logging_exception_prefix = %(color)s%(asctime)s.%(msecs)03d TRACE %(name)s ^[[01;35m%(instance)s^[[00m | 06:46 |
| liusheng | logging_debug_format_suffix = ^[[00;33mfrom (pid=%(process)d) %(funcName)s %(pathname)s:%(lineno)d^[[00m | 06:46 |
| liusheng | logging_default_format_string = %(asctime)s.%(msecs)03d %(color)s%(levelname)s %(name)s [^[[00;36m-%(color)s] ^[[01;35m%(instance)s%(color)s%(message)s^[[00m | 06:46 |
| liusheng | logging_context_format_string = %(asctime)s.%(msecs)03d %(color)s%(levelname)s %(name)s [^[[01;36m%(request_id)s ^[[00;36m%(user)s %(tenant)s%(color)s] ^[[01;35m%(instance)s%(color)s%(message)s^[[00m | 06:46 |
| liusheng | 06:46 | |
| liusheng | zhenguo: can please paste the lines like these in nimble.conf for me ? | 06:46 |
| zhenguo | liusheng: sorry, I can't copy/paste from blue cloud to yellow cloud :( | 06:46 |
| liusheng | zhenguo: :( | 06:46 |
| liusheng | zhenguo: you use irc in yellow cloud, lol | 06:47 |
| zhenguo | liusheng: seems the only different is user_id/user and project_id/project | 06:47 |
| zhenguo | lusheng: yes, hah | 06:47 |
| liusheng | zhenguo: yes, it is should be user and tenant than user_id and project_id | 06:47 |
| liusheng | zhenguo: I will try to find the reason | 06:48 |
| zhenguo | liusheng: yes, I find glance also use user and project instead of xx_id | 06:48 |
| zhenguo | liusheng: aha, it's because we set user_id in our devstack plugin | 06:49 |
| liusheng | zhenguo: where ? | 06:49 |
| liusheng | if [ "$LOG_COLOR" == "True" ] && [ "$SYSLOG" == "False" ]; then | 06:50 |
| liusheng | setup_colorized_logging ${NIMBLE_CONF_FILE} DEFAULT "project_id" "user_id" | 06:50 |
| liusheng | fi | 06:50 |
| liusheng | zhenguo: maybe here, hah | 06:50 |
| zhenguo | liusheng: yes | 06:50 |
| zhenguo | liusheng: please update it with your patch, hah | 06:51 |
| liusheng | if [ "$LOG_COLOR" == "True" ] && [ "$SYSLOG" == "False" ]; then | 06:51 |
| liusheng | setup_colorized_logging $IRONIC_CONF_FILE DEFAULT tenant user | 06:51 |
| liusheng | fi | 06:51 |
| liusheng | zhenguo: this is the ironic's | 06:51 |
| liusheng | zhenguo: ok | 06:51 |
| zhenguo | liusheng: hah | 06:52 |
| openstackgerrit | liusheng proposed openstack/nimble: Use oslo context instead of the native context implementation https://review.openstack.org/412350 | 06:52 |
| liusheng | zhenguo: thanks for review and finding the bug :) | 06:53 |
| zhenguo | liusheng: hah, it's my duty :) | 06:54 |
| *** openstackgerrit has quit IRC | 07:48 | |
| shaohe_feng | zhenguo: liusheng: have you seen this provisioning states. http://docs.openstack.org/developer/ironic/dev/states.html | 08:11 |
| zhenguo | shaohe_feng: it's ironic's state machine | 08:13 |
| shaohe_feng | zhenguo: yes. it looks complex | 08:14 |
| zhenguo | shaohe_feng: ironic needs it | 08:14 |
| shaohe_feng | zhenguo:In the docs: There are a few other API-initiated-transitions that are possible from non-stable states. | 08:15 |
| shaohe_feng | zhenguo: so which are thes API-initiated-transitions? | 08:15 |
| shaohe_feng | clean wait | 08:15 |
| shaohe_feng | zhenguo: clean wait | 08:15 |
| shaohe_feng | zhenguo: clean wait -> clean failed | 08:16 |
| zhenguo | shaohe_feng: means via API, hah | 08:16 |
| shaohe_feng | zhenguo: is an example, | 08:17 |
| zhenguo | shaohe_feng: you mean clean wait to clean failed is API-initiated-transition? | 08:18 |
| shaohe_feng | zhenguo: API-initiated-transitions from non-stable states, usually we are abort or interrupt something. | 08:18 |
| shaohe_feng | zhenguo: I means is API-initiated-transitions from non-stable states. | 08:18 |
| shaohe_feng | zhenguo: seems like nimble, the building status is non-stable states during creating . | 08:19 |
| zhenguo | shaohe_feng: yes, sometimes the sate is stuck on non-stable, so we should have a way to make it transition | 08:19 |
| zhenguo | shaohe_feng: but we are not that complex | 08:19 |
| shaohe_feng | zhenguo: and we can API-initiated-transitions to delete the instance. | 08:20 |
| zhenguo | shaohe_feng: if we can catch exceptions we can move it from building to error | 08:20 |
| shaohe_feng | zhenguo: yes. we have not abort operation. | 08:20 |
| shaohe_feng | zhenguo: yes. | 08:20 |
| zhenguo | shaohe_feng: and we can delete instance in any state, lol, that's the difference | 08:21 |
| zhenguo | shaohe_feng: ironic must follow the state machine to do delete operation | 08:21 |
| shaohe_feng | zhenguo: Nice, both stable and unstable state. | 08:21 |
| shaohe_feng | zhenguo: MAAS can not delete the instance in unstable state. | 08:21 |
| zhenguo | shaohe_feng: I'm now refactoring the deleting instance part | 08:21 |
| shaohe_feng | zhenguo: This is a good feature than MAAS. | 08:22 |
| zhenguo | shaohe_feng: hah, but that will bring some issues to us as well, like deleting when building | 08:22 |
| shaohe_feng | zhenguo: you need boast this feature when promoting nimble. | 08:23 |
| zhenguo | shaohe_feng: but nova support this as well, they will compare us with nova instead of MAAS | 08:24 |
| shaohe_feng | zhenguo: Yes. we need to address these issues. that's why we are better than MAAS. :) | 08:24 |
| shaohe_feng | zhenguo: OK. How does nova address these issues? | 08:25 |
| shaohe_feng | zhenguo: what's the issues? | 08:25 |
| zhenguo | shaohe_feng: nova check whether instance exists in every phase | 08:25 |
| shaohe_feng | zhenguo: o, you have mention it to me before. | 08:26 |
| zhenguo | shaohe_feng: not sure how to handle exception and how to revert | 08:26 |
| shaohe_feng | zhenguo: I"m too older to remember many things. | 08:27 |
| zhenguo | shaohe_feng: hah | 08:27 |
| zhenguo | shaohe_feng: have you started working on configdrive ? | 08:28 |
| shaohe_feng | zhenguo: yes. | 08:30 |
| zhenguo | shaohe_feng: excelent | 08:30 |
| shaohe_feng | zhenguo: it http://developer.openstack.org/api-ref/baremetal/?expanded=create-node-detail,change-node-provision-state-detail | 08:30 |
| shaohe_feng | zhenguo: provision support configdrive. | 08:31 |
| shaohe_feng | zhenguo: and I read up the provision docs I find this status machine | 08:32 |
| zhenguo | shaohe_feng: yes, you can pass configdrive with it, I would suggest you refer to nova. | 08:32 |
| shaohe_feng | zhenguo: for delete, I think maybe 2 ways. | 08:32 |
| shaohe_feng | zhenguo: 1. maybe let task flow to rember the network and other info, that need to destroy | 08:33 |
| shaohe_feng | if we do not support deleted fields in instance DB. | 08:33 |
| shaohe_feng | zhenguo: 2. add deleted fields in instance DB | 08:34 |
| shaohe_feng | we delete request, destroy all and return 200, then instance in not in building. | 08:34 |
| zhenguo | shaohe_feng: currently I doubt whether we need to introduce taskflow to delete instance | 08:35 |
| shaohe_feng | return 201, if instance in building, and mark the deleted as Ture. | 08:35 |
| zhenguo | shaohe_feng: do we have to revert anything when deleting | 08:36 |
| zhenguo | liusheng: are you around? let's talk about deleting instance again | 08:36 |
| liusheng | zhenguo: yes | 08:36 |
| shaohe_feng | delete request again or other operations request, return No Instance if no instance in DB or deleted as Ture | 08:37 |
| liusheng | about instance deletion with taskflow ? | 08:37 |
| zhenguo | liusheng, shaohe_feng: currently, I don't think we need to introduce t taskflow to delete instnace | 08:37 |
| zhenguo | liusheng: yes | 08:37 |
| shaohe_feng | zhenguo: agree. we can introduce it on demand. | 08:37 |
| zhenguo | liusheng, shaohe_feng: seems we don't need to revert when there's exception when deleting an instance | 08:38 |
| liusheng | zhenguo: shaohe_feng, hmm, I agree we can introduce anything only when we really want | 08:39 |
| shaohe_feng | zhenguo: an edge case maybe not in really scenario, for products have HA. | 08:40 |
| liusheng | zhenguo: agree that seems we don't need it in deletion now | 08:40 |
| zhenguo | liusheng, shaohe_feng: but we really need to refactor deleting now, it's too simple.... too young | 08:40 |
| liusheng | zhenguo: lol | 08:40 |
| liusheng | zhenguo: we only provide functionalities now | 08:41 |
| zhenguo | liusheng: yes, it doesn't change since the demo | 08:42 |
| shaohe_feng | zhenguo: what's delete routine? when destroy the network, something wrong with neutron | 08:42 |
| zhenguo | shaohe_feng: maybe just log a warning like what nova does | 08:43 |
| shaohe_feng | zhenguo: ignore the error, and continue? | 08:43 |
| shaohe_feng | zhenguo: Got it. Log("something wrong with delete network, maybe it still exist"), and continue to delete the instance. | 08:44 |
| zhenguo | shaohe_feng, liusheng: but there will be some potential problems, as we use MAC to create neutron port, if failed to delete it, then the ironic node will never to used again | 08:44 |
| liusheng | shaohe_feng: that is like what Nova implemented | 08:44 |
| zhenguo | shaohe_feng, liusheng: and now we ignore rescheduleing for network error, so it may just raise an exception for user's create request | 08:45 |
| shaohe_feng | liusheng: zhenguo: so there will be some zombie resource in nova, if nova does these ways. | 08:46 |
| shaohe_feng | liusheng: zhenguo: and admin need to reap these zombies by manually. | 08:46 |
| shaohe_feng | zhenguo: zhenguo: right? | 08:46 |
| zhenguo | shaohe_feng: yes, I think zombie resources are OK, as long as it doesn't affect us | 08:47 |
| liusheng | shaohe_feng, zhenguo I just think that we may don't need to sonsider too many edge scenarios ? | 08:47 |
| zhenguo | shaohe_feng: as we have lots and lots of resouces in a cloud, lol | 08:47 |
| liusheng | shaohe_feng, zhenguo right ? | 08:47 |
| zhenguo | liusheng: agree | 08:47 |
| shaohe_feng | zhenguo: OK, in cloud zombie resources can not be avoided. | 08:48 |
| yuntongjin | we can use periodly sync | 08:52 |
| shaohe_feng | zhenguo: yuntongjin tells me, nova can reap the zombies. | 08:52 |
| shaohe_feng | liusheng: ^ | 08:53 |
| zhenguo | yuntongjin, shaohe_feng, liusheng: currently we delete the instance from DB, so there's no any record about what's the zombie resouces | 08:54 |
| liusheng | zhenguo: yeah, seems nova record the resources | 08:59 |
| *** openstackgerrit has joined #openstack-nimble | 08:59 | |
| openstackgerrit | Merged openstack/nimble: Use oslo context instead of the native context implementation https://review.openstack.org/412350 | 08:59 |
| zhenguo | liusheng: all sub resouces in nova is in a seperate db table | 09:00 |
| liusheng | zhenguo: yes | 09:06 |
| * zhenguo brb | 09:10 | |
| shaohe_feng | liusheng: zhenguo: yuntongjin: send a email about the zombie. we can continue in the thread whenever we want to discuss it. | 09:23 |
| shaohe_feng | IRC is an instant messaging service, email is good to track a long term dicussion. | 09:26 |
| *** yuntongjin has quit IRC | 09:40 | |
| shaohe_feng | zhenguo: do we need to support an provision API? | 10:01 |
| shaohe_feng | zhenguo: http://developer.openstack.org/api-ref/baremetal/?expanded=create-node-detail,change-node-provision-state-detail | 10:01 |
| shaohe_feng | zhenguo: IMHO, we should not. | 10:01 |
| zhenguo | shaohe_feng: no, we shouldn't | 10:02 |
| shaohe_feng | zhenguo: but maybe we can add to split this provision API | 10:02 |
| zhenguo | shaohe_feng: our create and delete API is like that | 10:03 |
| *** kevinz has quit IRC | 10:03 | |
| shaohe_feng | zhenguo: confige drivers should be pass with instance create. and self-healing mechanism internal for nimble to change the provision status, for example un-stable status. | 10:06 |
| shaohe_feng | zhenguo: and some are need to merge the nimble instance action? | 10:06 |
| zhenguo | shaohe_feng: we don't quite care about ironic provision state, like it's in clean failed or something like that | 10:07 |
| zhenguo | shaohe_feng: that should be fixed on ironic side | 10:07 |
| shaohe_feng | zhenguo: call you. | 10:08 |
| shaohe_feng | by wechat. | 10:08 |
| zhenguo | shaohe_feng: we just use ironic's available nodes and release them when delete instance | 10:08 |
| shaohe_feng | zhenguo: who will maintain the ironic? | 10:09 |
| openstackgerrit | liusheng proposed openstack/nimble: Add instance CURD related functional tests https://review.openstack.org/398068 | 10:13 |
| zhenguo | shaohe_feng: I have some internal stuff, will ping you back | 10:14 |
| * zhenguo away | 10:14 | |
| *** Kevin_Zheng has quit IRC | 10:15 | |
| *** Kevin_Zheng has joined #openstack-nimble | 10:15 | |
| openstackgerrit | liusheng proposed openstack/nimble: Add support for updating instance type https://review.openstack.org/386439 | 10:32 |
| *** Jeffrey4l has quit IRC | 11:36 | |
| *** l4yerffeJ_ has joined #openstack-nimble | 13:00 | |
| *** l4yerffeJ has quit IRC | 13:04 | |
| *** liusheng has quit IRC | 13:25 | |
| *** liusheng has joined #openstack-nimble | 13:36 | |
| *** liusheng has quit IRC | 15:00 | |
| *** liusheng has joined #openstack-nimble | 15:11 | |
| openstackgerrit | Zhenguo Niu proposed openstack/nimble: Refactor delete_instance https://review.openstack.org/413677 | 15:19 |
| *** Jeffrey4l has joined #openstack-nimble | 15:54 | |
| zhenguo | liusheng, shaohe_feng: hi, please help to look at this https://review.openstack.org/#/c/413677/ when you are available. | 16:03 |
| *** Kevin_Zheng has quit IRC | 16:27 | |
| *** openstackstatus has joined #openstack-nimble | 17:00 | |
| *** ChanServ sets mode: +v openstackstatus | 17:00 | |
| *** openstackstatus has quit IRC | 17:02 | |
| *** openstack has quit IRC | 17:02 | |
| *** openstack has joined #openstack-nimble | 17:07 | |
| -openstackstatus- NOTICE: Gerrit is being restarted to update its OpenID SSO configuration | 17:58 | |
| *** l4yerffeJ has joined #openstack-nimble | 21:32 | |
| *** Jeffrey4l has quit IRC | 21:35 | |
| *** l4yerffeJ_ has quit IRC | 21:35 | |
| *** l4yerffeJ has quit IRC | 23:09 | |
| *** l4yerffeJ has joined #openstack-nimble | 23:09 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!