| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-06-16 | |||
| 07:31:43 | openstackgerrit | Chris Friesen proposed openstack/python-novaclient master: 2.47: Show flavor info in server details https://review.openstack.org/435141 | |
| 07:43:48 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Verify parameters in os-migrations.inc https://review.openstack.org/474879 | |
| 07:59:55 | openstackgerrit | sahid proposed openstack/nova master: libvirt: update the logic to configure volume with scsi controller https://review.openstack.org/459741 | |
| 07:59:56 | openstackgerrit | sahid proposed openstack/nova master: libvirt: update logic to configure device for scsi controller https://review.openstack.org/459740 | |
| 08:05:59 | openstackgerrit | sahid proposed openstack/nova master: libvirt: refresh info_cache before creating devices metadata https://review.openstack.org/468758 | |
| 08:06:36 | openstackgerrit | Zhenyu Zheng proposed openstack/nova master: Support tag instances when boot(4/4) https://review.openstack.org/469800 | |
| 08:21:49 | openstackgerrit | Rodolfo Alonso Hernandez proposed openstack/nova master: Add datapath type information to OVS vif objects https://review.openstack.org/474892 | |
| 08:30:58 | bauzas | p!spy | |
| 08:31:03 | openstackgerrit | Andrey Volkov proposed openstack/nova master: api-ref: Add X-OpenStack-Request-Id description https://review.openstack.org/474847 | |
| 08:54:34 | openstackgerrit | Alex Xu proposed openstack/nova master: Remove multiple create from stevedore https://review.openstack.org/474909 | |
| 08:59:55 | kashyap | sfinucan: In rST for directory paths, what do you use? ``literal``, or *italics*? (I'd go with italics) | |
| 09:07:01 | mdbooth | Can anybody tell me why openstack client is suddenly outputting what looks like debug info about its http requests? | |
| 09:09:34 | openstackgerrit | Rodolfo Alonso Hernandez proposed openstack/os-vif master: Read datapath_type from VIF object https://review.openstack.org/474914 | |
| 09:12:12 | sfinucan | kashyap: Depends on the context. I'd probably go for literals myself though | |
| 09:12:21 | sfinucan | In most situations, that is | |
| 09:12:39 | sfinucan | mdbooth: Do you have OS_DEBUG (I think that's it) set? | |
| 09:12:47 | kashyap | sfinucan: Ah, right, thought so. Context is: Patch to a script in the source directory | |
| 09:12:51 | mdbooth | sfinucan: Nope | |
| 09:13:18 | mdbooth | sfinucan: It started after I upgraded it with pip | |
| 09:13:26 | mdbooth | Yesterday | |
| 09:13:26 | sfinucan | kashyap: I tend to favour literals for all things | |
| 09:13:52 | sfinucan | mdbooth: Hmm, then I'm not sure. This is python-openstackclient, right? I didn't see anything go in about that recently, but that doesn't mean much, heh | |
| 09:13:57 | mdbooth | Yep | |
| 09:14:01 | kashyap | sfinucan: Likewise. It seperates the prose and code-like stuff clearly | |
| 09:14:26 | sfinucan | indeed | |
| 09:16:37 | kashyap | sfinucan: One more. If have 1200 lines of rST, do people normally split it? | |
| 09:16:43 | kashyap | s/If/If you/ | |
| 09:16:58 | sfinucan | Um, I wouldn't say so? | |
| 09:17:07 | sfinucan | Unless you want to duplicate some sections in other docs | |
| 09:17:24 | sfinucan | Other than that, so long as it's consistent and properly sectioned, I think it's good | |
| 09:21:37 | kashyap | sfinucan: Yeah, not splitting it. No, I don't want to duplicate. | |
| 09:21:54 | kashyap | And yep, working at the consistency part. | |
| 09:35:35 | openstackgerrit | sahid proposed openstack/nova master: libvirt: fix memory locking limit https://review.openstack.org/472633 | |
| 09:41:59 | openstackgerrit | Alex Xu proposed openstack/nova master: Use plain routes list for os-remote-consoles instead of stevedore https://review.openstack.org/474930 | |
| 09:42:15 | openstack | Launchpad bug 1697452 in python-novaclient "openstack client dumps debug info on console even without specifying --debug option" [High,Fix released] - Assigned to Sean Dague (sdague) | |
| 09:42:15 | klipka | sfinucan: mdbooth: isn't it this bug: https://bugs.launchpad.net/python-openstackclient/+bug/1697452 | |
| 09:42:43 | mdbooth | klipka: Certainly sounds like it, thanks | |
| 09:50:32 | openstackgerrit | Zhenyu Zheng proposed openstack/nova master: Support tag instances when boot(4/4) https://review.openstack.org/469800 | |
| 09:58:31 | ricolin | Hi dear Nova cores, this issue now break heat's gate, can someone please help to give a check on it?:) | |
| 09:58:36 | openstack | Launchpad bug 1698290 in OpenStack Compute (nova) "detaching network adapter failed" [Undecided,New] | |
| 09:58:36 | ricolin | https://bugs.launchpad.net/nova/+bug/1698290 | |
| 09:59:28 | ricolin | alex_xu, TGIF | |
| 10:01:50 | alex_xu | ricolin: :) | |
| 10:08:28 | bauzas | do you folks remember where we document all possible actions Nova provides, like live-migrate etc. ? | |
| 10:09:13 | bauzas | my brain is getting me some problems | |
| 10:11:28 | bauzas | hah, the ops guide | |
| 10:54:16 | openstackgerrit | Maciej Kucia proposed openstack/nova-specs master: Extended PCI alias https://review.openstack.org/474218 | |
| 11:07:42 | openstackgerrit | Merged openstack/nova master: Transform keypair.create notification https://review.openstack.org/408689 | |
| 11:29:27 | openstackgerrit | NidhiMittalHada proposed openstack/nova master: Nova treats hostname as pattern https://review.openstack.org/474949 | |
| 12:08:30 | sahid | hello jaypipes | |
| 12:08:50 | sahid | i noticed that you -1ed https://review.openstack.org/#/c/459740/ | |
| 12:09:17 | sahid | i replied to you but did not get any news | |
| 12:09:58 | sahid | perhaps you did not have noticed my response, so i just wanted to kindly let you know that :) | |
| 12:10:28 | sahid | and if you need any more information, please let me know | |
| 12:23:09 | openstackgerrit | Vladyslav Drok proposed openstack/nova master: Do not remove baremetal ports in deallocate_for_instance https://review.openstack.org/473873 | |
| 12:43:05 | cdent | avolkov: I only pretend to be a native speaker, my real language is gibberish. but yeah, I'll look | |
| 12:47:38 | moshele | sean-k-mooney, jaypipes: hi, can you review https://review.openstack.org/#/c/460278/ ? all the ovs patches are merged upstream | |
| 12:49:42 | avolkov | cdent: :), thanks | |
| 13:26:21 | efried | ttx Help a noob out: What's a "client library" vs. a "non-client library"? | |
| 13:28:00 | ttx | efried: client library = python-novaclient | |
| 13:28:14 | ttx | i.e. the Python libraries around APIs | |
| 13:28:23 | ttx | non-client libraries are all other libs | |
| 13:28:38 | ttx | we give client libs an extra week since they sometimes need to reflect late-landed features | |
| 13:29:07 | ttx | In glance terms, the client lib is python-glanceclient, the non-client libs would be glance-store | |
| 13:29:24 | ttx | In nova terms, python-novaclient vs. os-vif | |
| 13:29:38 | ttx | efried: does that clarify ? | |
| 13:30:21 | efried | ttx Very much, thanks. Do e.g. oslo* fall under the "non-client libs" umbrella for this deadline? | |
| 13:30:30 | ttx | yes | |
| 13:31:05 | ttx | we give an extra week for python-${PROJECT}client so that they can catch up with late-landed features in $PROJECT | |
| 13:31:34 | ttx | for everything else it's the other way around | |
| 13:31:52 | ttx | we give an extra week to $PROJECT to catch up with feature late-landed in $lib | |
| 13:32:00 | efried | Makes sense. Deadlines move in the direction of the dependency chains. | |
| 13:32:15 | efried | Merci bien, Thierry. | |
| 13:32:25 | ttx | you got it. Makes more sense the way you summarized it :) | |
| 14:00:56 | sdague | mriedem: https://review.openstack.org/#/c/474961/ | |
| 14:01:54 | sdague | mriedem: in looking at the bug pile I noticed that bugs on stable series are remaining at "Fix Committed" not "Fix Released" - https://bugs.launchpad.net/nova/mitaka/+bugs | |
| 14:02:12 | sdague | mriedem: is that intentional, or did a tool not do the right thing there? | |
| 14:02:48 | mriedem | sdague: i thought the release tooling was supposed to flip those to fix released once a stable point release was done | |
| 14:04:14 | mriedem | sdague: my guess is ttx or doug would know which script in https://github.com/openstack-infra/release-tools does that | |
| 14:05:38 | efried | I thought "Fix Committed" was not used at all anymore. | |
| 14:05:54 | efried | Everything just flipped to "Fix Released" as soon as it merged. | |
| 14:06:08 | efried | Not saying I agree that's the way it *should* be done, esp. for stable branches, but... | |
| 14:08:50 | mriedem | efried: that's what happens on master yes | |
| 14:09:06 | sdague | yeh, I don't actually see where it's being done. | |
| 14:16:16 | sdague | mriedem: the process bugs tool only works for milestones | |
| 14:17:15 | mriedem | sdague: ok i figured it would be something like that | |
| 14:17:37 | mriedem | since we stopped using milestones for client/lib releases in LP long ago | |
| 14:18:37 | cfriesen | mriedem: https://review.openstack.org/435141 is ready for re-review, has the namespaced flavor output | |
| 14:19:00 | sdague | mriedem: ok, so I guess the question is, given that we've got a reasonable number of "still open bugs" for nova on stable branches, how would you like that handled? | |
| 14:19:44 | sdague | this is also complicated by the fact that you can't search on a series, so you actually just have to search all bugs, then look for tasks on a series | |
| 14:22:55 | mriedem | sdague: still open as in fix committed but not fixed relased? | |
| 14:22:58 | mriedem | *released? | |
| 14:23:48 | sdague | yes | |
| 14:24:26 | sdague | mriedem: so I took the liberty to bulk process them all on liberty, there were 73 bugs in "Fix Committed" | |
| 14:25:29 | sdague | there are 76 bugs in mitaka in "open" state, about 70 of those are fix committed | |
| 14:25:43 | mriedem | ok i didn't realize we considered fix committed as open | |
| 14:25:50 | sdague | launchpad does | |
| 14:25:56 | sdague | fix committed is an open state | |
| 14:25:58 | mriedem | melwitt: do you know if a user can create the "default" security group in nova? | |
| 14:26:35 | mriedem | sdague: ok so i guess we just mark them as fix released - although since we don't have milestones for stable branch releases we can't point them at a release milestone | |