| *** wanghao has joined #openstack-mogan | 00:21 | |
| *** wanghao has quit IRC | 00:35 | |
| *** wanghao has joined #openstack-mogan | 00:47 | |
| *** litao__ has joined #openstack-mogan | 01:12 | |
| wanghao | liusheng: thanks God sheng to update the client patch, I'd like the current format of json. thanks! | 01:25 |
|---|---|---|
| liusheng | wanghao: lol, np :D | 01:25 |
| zhenguo | liusheng: why there's no '--' with the node_uuid here https://review.openstack.org/#/c/501777/13/moganclient/osc/v1/manageable_server.py ? | 01:36 |
| liusheng | zhenguo: I don't think we need that | 01:36 |
| zhenguo | liusheng: why | 01:36 |
| liusheng | zhenguo: why need ? | 01:37 |
| zhenguo | liusheng: name and uuid are both without -- | 01:37 |
| liusheng | zhenguo: yes | 01:37 |
| zhenguo | liusheng: is there any other command seems like that? | 01:37 |
| liusheng | zhenguo: only them are the main parameter, many commands in openstack CLI like that | 01:37 |
| zhenguo | liusheng: like what? | 01:38 |
| zhenguo | liusheng: but when I use that, seems confused | 01:38 |
| zhenguo | liusheng: not sure which one is name and which one is node | 01:38 |
| liusheng | zhenguo: the help message is explict, and it is explict if you only type "openstack baremetalcompute server manage" | 01:39 |
| zhenguo | liusheng: not sure is easy to use | 01:40 |
| liusheng | zhenguo: many openstack commands like this, and we save the --node_uuid to make the command more concise | 01:41 |
| zhenguo | liusheng: ok | 01:42 |
| liusheng | zhenguo: and because this command only have the two main parameters, description and metadata are optional, I think it is suite to make the command like this | 01:43 |
| zhenguo | liusheng: ok, just keep the current implementation | 01:45 |
| liusheng | zhenguo: ok | 01:46 |
| zhenguo | liusheng: seems we forgot to format the addresses for server creation response | 01:48 |
| zhenguo | liusheng: creation could be empty, so no need to format, but managing seems not | 01:49 |
| liusheng | zhenguo: seems yes, | 01:49 |
| zhenguo | liusheng: just format it? | 01:50 |
| zhenguo | liusheng: oh, seems hard to format | 01:50 |
| liusheng | zhenguo: let me check the managing reponse | 01:50 |
| zhenguo | liusheng: as it may not belongs to neutron | 01:50 |
| liusheng | zhenguo: yes | 01:50 |
| zhenguo | liusheng: but if it's not belongs to neutron, we just ignore that, so it's empty, right? | 01:51 |
| zhenguo | liusheng: so seems it's ok to just follow the current addresses formater | 01:52 |
| liusheng | zhenguo: may don't, the manage API is a sync call, right ? | 01:52 |
| zhenguo | liusheng: yes | 01:52 |
| liusheng | zhenguo: if so, not sure if the reponse will always include the network info | 01:54 |
| zhenguo | liusheng: it's an rpc call, so it alwasy with that | 01:54 |
| liusheng | zhenguo: for server creation, because it is a cast method, before creating network, we return it | 01:54 |
| zhenguo | liusheng: no | 01:54 |
| zhenguo | liusheng: for creation, we always don't return the netowrk | 01:54 |
| liusheng | zhenguo: yes, I mean in the creating process, we return after sent the cast invoke | 01:55 |
| zhenguo | liusheng: yes | 01:55 |
| liusheng | zhenguo: before constructing the network info, right ? | 01:56 |
| zhenguo | liusheng: sure | 01:56 |
| zhenguo | liusheng: but manaing is different | 01:56 |
| liusheng | zhenguo: but for manage API, we will return after all the processing | 01:56 |
| liusheng | zhenguo: yes | 01:56 |
| liusheng | zhenguo: so maybe for managing, it will always return the network info, right ? | 01:56 |
| zhenguo | liusheng: sure | 01:56 |
| zhenguo | liusheng: aren't we just taking about this? hah | 01:57 |
| liusheng | zhenguo: hah | 01:57 |
| zhenguo | liusheng: but for managing, if it's not have neutron port, we don't save it | 01:58 |
| liusheng | zhenguo: is it possible a server without neutron port after managing ? | 01:59 |
| zhenguo | liusheng: yes | 01:59 |
| liusheng | zhenguo: oh, if so | 01:59 |
| zhenguo | liusheng; so the formatter should also take this into account | 01:59 |
| liusheng | zhenguo: maybe we don't need to format | 01:59 |
| zhenguo | liusheng: ?] | 01:59 |
| zhenguo | liusheng: you can ignore the formater only if there's no addresses return | 02:00 |
| liusheng | zhenguo: oh, got it | 02:00 |
| zhenguo | liusheng: hah | 02:01 |
| liusheng | zhenguo: may we need to extract these formatters for common use | 02:03 |
| zhenguo | liusheng: seems yes, at least for addresses formatter | 02:03 |
| liusheng | zhenguo: yes, and seems we lack of rebuild command for now, it will also use the formatters | 02:04 |
| zhenguo | liusheng: oh, yes | 02:04 |
| liusheng | zhenguo: I can cook another patch for extract all these formatters | 02:05 |
| zhenguo | liusheng: oh | 02:05 |
| zhenguo | liusheng: ok | 02:05 |
| zhenguo | liusheng: so, this one is ready to go? | 02:05 |
| liusheng | zhenguo: I think so, up to you, hah | 02:05 |
| zhenguo | liusheng: hah, will +2 that | 02:06 |
| liusheng | zhenguo: ok | 02:06 |
| zhenguo | liusheng: you can +A now, lol | 02:06 |
| liusheng | zhenguo: ok | 02:07 |
| zhenguo | liusheng: I still have 3 patches not landed yet https://review.openstack.org/#/q/project:openstack/mogan+owner:self+status:open | 02:08 |
| zhenguo | liusheng: please have a look when you got time | 02:08 |
| zhenguo | liusheng: then we can prepare the release | 02:08 |
| liusheng | zhenguo: oh, sorry, will review now | 02:08 |
| zhenguo | liusheng: thanks | 02:08 |
| openstackgerrit | Merged openstack/python-moganclient master: Add the CLI for managing server https://review.openstack.org/501777 | 02:11 |
| openstackgerrit | Merged openstack/mogan master: Updated from global requirements https://review.openstack.org/502671 | 02:15 |
| litao__ | liusheng: Thanks for merging and update the patch, cool | 02:34 |
| liusheng | litao__: np :) | 02:35 |
| zhenguo | liusheng: seems we can't create stable/pike | 02:40 |
| zhenguo | liusheng: but a release under queens | 02:40 |
| liusheng | zhenguo: hmm, what's your way ? | 02:41 |
| zhenguo | liusheng: like this https://review.openstack.org/#/c/498479/ | 02:41 |
| liusheng | zhenguo: can we non-official project use releases repo to release ? | 02:42 |
| zhenguo | liusheng: seems yes | 02:42 |
| liusheng | zhenguo: not sure, if so maybe we miss the deadline of Pike :( | 02:42 |
| zhenguo | liusheng: yes | 02:42 |
| liusheng | zhenguo: :( | 02:43 |
| zhenguo | liusheng: anyway, it's ok, we can just tag a 0.1.0 under queens | 02:43 |
| liusheng | zhenguo: hah, that is ok | 02:44 |
| zhenguo | liusheng: https://github.com/openstack/sushy | 02:45 |
| zhenguo | liusheng: it's not an official project | 02:45 |
| liusheng | zhenguo: seems we cannot create the main version, but the small version is ok | 02:45 |
| zhenguo | liusheng: yes | 02:45 |
| liusheng | zhenguo: oh | 02:45 |
| zhenguo | liusheng: but you can find sushy under openstack/releases | 02:46 |
| zhenguo | liusheng: I will put a patch to add mogan and moganclient | 02:46 |
| zhenguo | liusheng: then we can release | 02:46 |
| liusheng | zhenguo: ok, cool | 02:46 |
| zhenguo | liusheng: let me try to see if we can add there | 02:46 |
| zhenguo | liusheng: but under queens | 02:47 |
| liusheng | zhenguo: you need to add the user openstackci as a maintainer of the pypi repo | 02:47 |
| zhenguo | liusheng: yes | 02:47 |
| zhenguo | liusheng: it's a must when you create project under openstack | 02:47 |
| liusheng | zhenguo: oh | 02:48 |
| openstackgerrit | Merged openstack/mogan master: Check usable portgroups and ports https://review.openstack.org/502410 | 02:48 |
| zhenguo | liusheng: another way, we can release under _independent instead of pike, queens, ... | 02:56 |
| openstackgerrit | Merged openstack/mogan master: Add preserve_on_delete to server nic object https://review.openstack.org/501940 | 02:56 |
| zhenguo | shaohe_feng: please have a look at this https://review.openstack.org/#/c/502379/ when you are online | 02:57 |
| liusheng | zhenguo: that seems for the independent release project, a project with independent release tag | 02:57 |
| zhenguo | liusheng: yes | 02:58 |
| liusheng | zhenguo: but we are not independent release project | 02:58 |
| zhenguo | liusheng: but seems we'd better not independent, hah | 02:58 |
| liusheng | zhenguo: yes | 02:58 |
| zhenguo | liusheng: so we wil underneath queens | 02:58 |
| zhenguo | liusheng: seems you can +A this https://review.openstack.org/#/c/502741/ | 02:59 |
| liusheng | zhenguo: done | 03:00 |
| liusheng | zhenguo: hah | 03:00 |
| zhenguo | liusheng; hah | 03:00 |
| liusheng | zhenguo: I think it is ok | 03:00 |
| zhenguo | liusheng: ok | 03:01 |
| openstackgerrit | Merged openstack/python-moganclient master: Updated from global requirements https://review.openstack.org/502741 | 03:06 |
| zhenguo | liusheng: do we need to build a release notes link on RTD? | 03:10 |
| liusheng | zhenguo: does other projects do this ? | 03:10 |
| zhenguo | liusheng: not sure | 03:12 |
| zhenguo | liusheng: official projects do | 03:12 |
| liusheng | zhenguo: not sure if it can work with RTD | 03:12 |
| zhenguo | liusheng: lol | 03:12 |
| zhenguo | liusheng: don't be afraid of RTD | 03:13 |
| liusheng | zhenguo: hah | 03:13 |
| zhenguo | liusheng: let me try | 03:13 |
| liusheng | zhenguo: ok | 03:14 |
| zhenguo | liusheng: http://mogan.readthedocs.io/projects/releasenotes/en/latest/unreleased.html | 03:23 |
| liusheng | zhenguo: cool | 03:23 |
| openstackgerrit | liusheng proposed openstack/python-moganclient master: Extract the formatter methods as common utils https://review.openstack.org/502884 | 03:47 |
| openstackgerrit | Merged openstack/mogan master: Return node name with server API object https://review.openstack.org/502379 | 04:26 |
| openstackgerrit | Zhenguo Niu proposed openstack/mogan master: Set server node for managed servers https://review.openstack.org/502890 | 05:42 |
| zhenguo | liusheng: seems we can't use relesenotes as we will not create a branch | 06:20 |
| liusheng | zhenguo: oh, maybe it combine with a release | 06:21 |
| zhenguo | liusheng: yes | 06:21 |
| zhenguo | liusheng: https://github.com/openstack/ironic/blob/master/releasenotes/source/pike.rst | 06:21 |
| zhenguo | liusheng: we will just tag the current branch | 06:21 |
| zhenguo | liusheng: seems zun also don't have a releasenotes yet https://github.com/openstack/zun/tree/master/releasenotes/notes | 06:26 |
| liusheng | zhenguo: hah, they are already official | 06:26 |
| zhenguo | liusheng: yes | 06:26 |
| liusheng | zhenguo: I think we have do better than many official projects | 06:27 |
| zhenguo | liusheng: lol | 06:27 |
| liusheng | zhenguo: many official projects are inactive and may don't have enriched features. hah | 06:28 |
| zhenguo | liusheng: but releasenotes seems used to track the current release stuff(pike, queens, ...) | 06:29 |
| zhenguo | liusheng: we don't have such a release | 06:29 |
| liusheng | zhenguo: even 0.1.0 cannot ? | 06:30 |
| zhenguo | liusheng: you mean tag? | 06:30 |
| liusheng | zhenguo: yes | 06:30 |
| zhenguo | liusheng: no | 06:30 |
| liusheng | zhenguo: :( | 06:30 |
| zhenguo | liusheng: release project will help to create the specific branch's source file | 06:30 |
| zhenguo | liusheng: we don't have any branch | 06:31 |
| liusheng | zhenguo: can we just add a branch ? | 06:31 |
| zhenguo | liusheng: how | 06:31 |
| liusheng | zhenguo: oh, maybe we can only create branch by change in releases repo .. | 06:33 |
| zhenguo | liusheng: you can't | 06:33 |
| liusheng | zhenguo: cannot propose change in stable/pike of releases repo, right ? | 06:34 |
| zhenguo | liusheng: seems yes, you can check the patch comments I sent yu | 06:34 |
| zhenguo | liusheng: this one https://review.openstack.org/#/c/498479/ | 06:35 |
| zhenguo | liusheng: check ttx's comments | 06:35 |
| liusheng | zhenguo: oh, unless we are cycle-with-intermediary | 06:36 |
| zhenguo | liusheng: tag seems enough for us | 06:37 |
| zhenguo | liusheng: do we really need a branch? | 06:37 |
| wanghao | liusheng: ping | 06:38 |
| liusheng | zhenguo: not sure, but maybe we need a release, that users can use mogan in pypi | 06:38 |
| zhenguo | liusheng: yes, tag will cause a release | 06:38 |
| zhenguo | liusheng: which like a stacit branch | 06:39 |
| wanghao | liusheng: I found we should update the doc of uwsgi | 06:39 |
| wanghao | On deb-based systems copy or symlink the file ``apache-mogan.template`` to | 06:39 |
| wanghao | ``/etc/apache2/sites-available/mogan.conf``. For rpm-based systems the file | 06:39 |
| wanghao | should go into ``/etc/httpd/conf.d/mogan.conf``. | 06:39 |
| zhenguo | liusheng: branch will go on but tag won't, that's the difference | 06:39 |
| wanghao | liusheng: I saw now it should be mogan-api-wsgi.conf, right? | 06:40 |
| liusheng | wanghao: actually, I think the name is unrelated | 06:41 |
| liusheng | wanghao: maybe in productive deployment, the name of file may be not like devstack env | 06:43 |
| wanghao | liusheng: yes, I see, but I feel mogan-api-wsgi.conf is more clear. | 06:43 |
| * zhenguo brb | 06:44 | |
| wanghao | liusheng: anyway, it is fine too, but I found another bug: tee/etc/tmpfiles.d/uwsgi.conf | 06:45 |
| liusheng | wanghao: not sure, but I may prefer mogan.conf is more like in productive usages. current the mogan-api-wsgi.conf is just set by devstack scripts | 06:45 |
| wanghao | there is no blank between tee and /etc/... | 06:45 |
| wanghao | : ) | 06:45 |
| liusheng | wanghao: hah, it has been fixed by shaohe | 06:45 |
| liusheng | wanghao: you can check the latest code | 06:45 |
| wanghao | liusheng: : ) cool | 06:45 |
| shaohe_feng | zhenguo: sorry, just online. | 06:55 |
| zhenguo | shaohe_feng: please take a look at this https://review.openstack.org/#/c/502884/ | 07:02 |
| zhenguo | liusheng, shaohe_feng, wanghao, litao__, Xinran: seems we can only create a release under queens, a tag instead of a branch | 07:05 |
| zhenguo | regarding the releasenotes, do you have suggestions, should be under queens | 07:07 |
| *** kong has quit IRC | 07:08 | |
| openstackgerrit | liusheng proposed openstack/mogan master: Add more notifications for server create/delete https://review.openstack.org/502898 | 07:08 |
| shaohe_feng | zhenguo: in really physical evn, should I config the dell swith plugin for neturon | 07:08 |
| zhenguo | shaohe_feng: no | 07:08 |
| zhenguo | shaohe_feng: enable networking-generic-switch | 07:09 |
| zhenguo | liusheng: anyway, I can build a releasenotes for 0.1.0 like this http://mogan.readthedocs.io/projects/releasenotes/en/latest/unreleased.html | 07:12 |
| liusheng | zhenguo: that looks cool | 07:13 |
| zhenguo | liusheng: ok | 07:13 |
| liusheng | zhenguo: it is 0.0.0, hah | 07:13 |
| zhenguo | liusheng: we need to manually create a 0.1.0 under private repo | 07:13 |
| liusheng | zhenguo: oh, yes | 07:14 |
| openstackgerrit | Merged openstack/python-moganclient master: Extract the formatter methods as common utils https://review.openstack.org/502884 | 07:14 |
| zhenguo | liusheng: in fact, release project will help to create that | 07:14 |
| zhenguo | liusheng: but we can't leverage that | 07:14 |
| liusheng | zhenguo: yes | 07:14 |
| zhenguo | liusheng: as we missed the time for Pike | 07:14 |
| openstackgerrit | liusheng proposed openstack/mogan master: Add more notifications for server create/delete https://review.openstack.org/502898 | 07:14 |
| zhenguo | liusheng: is therea delete error notification? | 07:15 |
| liusheng | zhenguo: just checked nova, there isn't | 07:15 |
| zhenguo | liusheng; oh | 07:15 |
| liusheng | zhenguo: I was thinking that maybe we need to enrich the notification payload for the different actions, we only include basic server info now | 07:16 |
| zhenguo | liusheng: seems yes | 07:17 |
| liusheng | zhenguo: ok, in nova, the nofication payload almost includes all the info of server | 07:17 |
| zhenguo | liusheng: yes please follow that, lol | 07:17 |
| liusheng | zhenguo: ok | 07:18 |
| zhenguo | liusheng: should we mark managed server nics as preserve_on_delete? | 07:20 |
| liusheng | zhenguo: after managing, it is a normal server, user may delete the server and release the node for reuse, maybe it is better don't, otherwise, users need to clean the ports, right ? | 07:22 |
| liusheng | zhenguo: maybe ask wanghao and litao, not sure, hah | 07:22 |
| zhenguo | liusheng: seems yes, wanghao, litao__, do you have concerns if I remove the ports for managed server when deleting it | 07:23 |
| wanghao | zhenguo: you mean delete a managed server, right | 07:26 |
| zhenguo | wanghao: yes | 07:26 |
| wanghao | zhenguo: if you want to delete it, I think you should clean the ports like other servers. | 07:26 |
| zhenguo | wanghao: yes | 07:26 |
| wanghao | zhenguo: since we will introduce another feature, unmanage server, that will not remove the ports. | 07:27 |
| wanghao | in Queens. | 07:27 |
| zhenguo | wanghao: hah, ok | 07:27 |
| zhenguo | wanghao: btw, we can't create branch for pike | 07:27 |
| zhenguo | wanghao: our first release will under queens | 07:28 |
| wanghao | zhenguo: .... | 07:28 |
| wanghao | zhenguo: why can't create branch? | 07:28 |
| zhenguo | wangaho: as pike was released :( | 07:28 |
| zhenguo | wanghao: they don't accept us to create a release under pike now | 07:29 |
| zhenguo | wanghao: but anyway, a release under queens also ok | 07:29 |
| wanghao | zhenguo: emm, that's okay | 07:29 |
| wanghao | zhenguo: at least we know that what time we should create a release now... hahhaha | 07:30 |
| zhenguo | wanghao: lol | 07:30 |
| zhenguo | wanghao: but we need to handle the releasenotes ourselves | 07:30 |
| zhenguo | wanghao: release project will not help to create a releasentoes until we cut queens | 07:31 |
| wanghao | zhenguo: you mean we need create a pike releasenote by ourselves now? | 07:33 |
| zhenguo | wanghao: not pike | 07:33 |
| zhenguo | wanghao: but 0.1.0 | 07:33 |
| zhenguo | wanghao: not sure if that | 07:34 |
| zhenguo | wanghao: like this http://mogan.readthedocs.io/projects/releasenotes/en/latest/unreleased.html#new-features | 07:34 |
| zhenguo | wanghao: when we announce the first release with this | 07:34 |
| wanghao | zhenguo: this page is made from our releasenotes automatically. right? | 07:37 |
| openstackgerrit | Zhenguo Niu proposed openstack/mogan master: Following up patch of 26508fd131bdfacbe4e2ed20fa636d19a8d00e88 https://review.openstack.org/502890 | 07:37 |
| shaohe_feng | zhenguo: who determine to create the branch? | 07:37 |
| shaohe_feng | zhenguo: Our code is on github. | 07:38 |
| shaohe_feng | zhenguo: Why cat not create a branch. | 07:39 |
| shaohe_feng | s/cat/can | 07:39 |
| zhenguo | wanghao: no, I build it manually | 07:43 |
| zhenguo | wanghao: by leveraging readthedocs | 07:44 |
| zhenguo | shaohe_feng: openstack | 07:44 |
| zhenguo | shaohe_feng: in fact, we are not the owner of the repo | 07:44 |
| zhenguo | liusheng, shaohe_feng, wanghao: this https://review.openstack.org/#/c/502890/ is the last thing I want to clean up before we cutting release | 07:45 |
| litao__ | zhenguo: Yes, I agree to delete network , and unmanage doesn't remove network | 07:46 |
| zhenguo | litao__: ok, already update the patch | 07:46 |
| zhenguo | liusheng, wanghao: I will update the releasenotes to only include features that cant't get from current openstack ecosystem, wdyt? | 08:03 |
| wanghao | zhenguo: emmmm, this sounds not like other project did. | 08:05 |
| zhenguo | liusheng, wanghao: yes | 08:05 |
| zhenguo | wanghao: we are not real release | 08:05 |
| wanghao | zhenguo: or we can split those releasenotes to two parts. | 08:05 |
| liusheng | zhenguo: why don't just like current ? | 08:06 |
| zhenguo | wanghao: as I understand we just want to highlight the advanced features | 08:06 |
| liusheng | zhenguo: it looks good for me, hah | 08:06 |
| zhenguo | liusheng: as there would be more | 08:06 |
| liusheng | zhenguo: any problem if more ? | 08:06 |
| wanghao | zhenguo: one: feature only we have, two: other import features that means mogan has grow up. | 08:06 |
| zhenguo | wanghao: but we can't, there's no such approach | 08:06 |
| zhenguo | liusheng: no body want to read that more | 08:07 |
| wanghao | zhenguo: we can edit our releasenotes in code tree. | 08:07 |
| zhenguo | liusheng, wanghao: we really done many things with the first release | 08:07 |
| liusheng | zhenguo: oh, currently, the release notes only can be classfy by branch, right ? | 08:07 |
| zhenguo | wanghao; there's no that tree | 08:08 |
| zhenguo | wanghao: that's done by openstack/release | 08:08 |
| liusheng | zhenguo: indeed | 08:08 |
| zhenguo | liusheng: yes | 08:08 |
| zhenguo | liusheng, wanghao: I don't want to show what openstack can provide in our release notes | 08:08 |
| zhenguo | liusheng, wanghao: I mean only for this release | 08:09 |
| wanghao | zhenguo: a, I see, we must make a releasenotes by ourself using readthdocs | 08:09 |
| zhenguo | liusheng, wanghao: we can follow others from queens | 08:09 |
| zhenguo | wanghao: yes | 08:09 |
| liusheng | zhenguo: ok | 08:09 |
| wanghao | zhenguo: that's fair, sure | 08:09 |
| zhenguo | ok, so just highligh some advanced features | 08:10 |
| liusheng | zhenguo: yes | 08:10 |
| wanghao | +1 | 08:10 |
| zhenguo | and from next cycle, we need to be add releasenotes like other projects | 08:10 |
| zhenguo | first release always hard, hah | 08:10 |
| wanghao | zhenguo: if we can follow the branch, we just need to add releasenotes in our code tree. right? | 08:28 |
| wanghao | openstack/release will create the releasenotes for every projects according the releasenotes docs. | 08:28 |
| wanghao | right? | 08:28 |
| zhenguo | wanghao: yes | 08:28 |
| wanghao | zhenguo: okay | 08:29 |
| zhenguo | wanghao: next release will leverage that | 08:29 |
| openstackgerrit | Merged openstack/mogan master: Following up patch of 26508fd131bdfacbe4e2ed20fa636d19a8d00e88 https://review.openstack.org/502890 | 08:57 |
| zhenguo | liusheng: anything more want to be added with the notifications patch? | 09:01 |
| liusheng | zhenguo: just want to make the notification payload including more info, like nics | 09:03 |
| zhenguo | liusheng: ok | 09:04 |
| liusheng | zhenguo: sorry, need to attend zhuli's pre-defence | 09:04 |
| * liusheng brb | 09:04 | |
| zhenguo | liusheng: ok | 09:04 |
| openstackgerrit | Zhenguo Niu proposed openstack/mogan master: Update release notes https://review.openstack.org/502924 | 09:06 |
| shaohe_feng | zhenguo: This releas note is the last patch of this release? | 09:08 |
| zhenguo | shaohe_feng: for our 0.1.0 | 09:19 |
| *** wanghao has quit IRC | 09:32 | |
| *** wanghao has joined #openstack-mogan | 09:32 | |
| openstackgerrit | Zhenguo Niu proposed openstack/mogan master: Correct typos on docs https://review.openstack.org/502931 | 09:33 |
| *** wanghao has quit IRC | 09:33 | |
| *** wanghao has joined #openstack-mogan | 09:33 | |
| *** wanghao has quit IRC | 09:34 | |
| *** wanghao has joined #openstack-mogan | 09:34 | |
| *** wanghao has quit IRC | 09:34 | |
| *** wanghao has joined #openstack-mogan | 09:35 | |
| *** wanghao has quit IRC | 09:35 | |
| *** wanghao has joined #openstack-mogan | 09:36 | |
| *** wanghao has quit IRC | 09:36 | |
| *** wanghao has joined #openstack-mogan | 09:36 | |
| *** wanghao has quit IRC | 09:37 | |
| *** wanghao has joined #openstack-mogan | 09:37 | |
| *** wanghao has quit IRC | 09:38 | |
| *** wanghao has joined #openstack-mogan | 09:38 | |
| openstackgerrit | Zhenguo Niu proposed openstack/mogan master: [DOC] Add flavor manage and customize instructions https://review.openstack.org/502959 | 11:26 |
| zhenguo | liusheng: can we change the 'list availabiliy zone' column name? | 11:47 |
| zhenguo | liusheng: it's 'availability_zone' now | 11:47 |
| zhenguo | liusheng: maybe something like 'Zone Name' ? | 11:48 |
| *** litao__ has quit IRC | 11:51 | |
| liusheng | zhenguo: sonds good | 11:53 |
| *** Kevin_Zheng has joined #openstack-mogan | 15:30 | |
| *** wanghao has quit IRC | 16:35 | |
| *** Kevin_Zheng has quit IRC | 18:59 | |
| *** kong has joined #openstack-mogan | 23:33 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!