| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-20 | |||
| 22:22:34 | mriedem | unless you're crazy | |
| 22:28:49 | openstackgerrit | Eric Fried proposed openstack/nova master: PowerVM Driver: SSP emphemeral disk support https://review.openstack.org/443189 | |
| 22:34:50 | mriedem | efried: https://review.openstack.org/#/c/427380/ failed powervm in-tree ci | |
| 22:34:55 | mriedem | error: could not apply fb15915... PowerVM Driver: spawn/destroy #3: TaskFlow | |
| 22:35:28 | mriedem | you need to rebase that change don't you? | |
| 23:08:05 | openstackgerrit | christopher.uhler proposed openstack/nova master: Libvirt volume driver for Veritas HyperScale https://review.openstack.org/443951 | |
| 23:11:02 | mriedem | smcginnis: what is https://www.openstack.org/summit/boston-2017/summit-schedule/events/18681/track-chairs-recap-and-discussion ? | |
| 23:38:03 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Using max api version in notification sample test https://review.openstack.org/443686 | |
| 23:38:04 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Adding auto_disk_config field to InstancePayload https://review.openstack.org/419185 | |
| 23:38:05 | openstackgerrit | Matt Riedemann proposed openstack/nova master: add tags field to instance.update notification https://review.openstack.org/407228 | |
| 23:39:32 | mriedem | gibi: for your morning coffee, the rebuild notifications in this change have duplicate entries for auto_disk_config https://review.openstack.org/#/c/419185/21/doc/notification_samples/instance-rebuild-end.json | |
| 23:41:45 | mriedem | maybe just a carried over typo | |
| 23:47:23 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Adding auto_disk_config field to InstancePayload https://review.openstack.org/419185 | |
| 23:48:40 | openstackgerrit | Takashi NATSUME proposed openstack/python-novaclient master: Microversion 2.43 - Enable cold migration with target host https://review.openstack.org/406707 | |
| 23:48:55 | openstackgerrit | Takashi NATSUME proposed openstack/python-novaclient master: Microversion 2.43 - List/Show all server migration types https://review.openstack.org/430839 | |
| #openstack-nova - 2017-04-21 | |||
| 00:09:17 | openstackgerrit | Sean Dague proposed openstack/nova master: PowerVM Driver: power_on/off and reboot https://review.openstack.org/427380 | |
| 01:43:18 | openstackgerrit | Huan Xie proposed openstack/nova master: WIP: XenAPI use os-xenapi v2 in nova https://review.openstack.org/453493 | |
| 02:04:28 | chatter29 | hey guys | |
| 02:04:31 | chatter29 | allah is doing | |
| 02:04:37 | chatter29 | sun is not doing allah is doing | |
| 02:04:39 | chatter29 | to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger | |
| 02:23:23 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Fix parameters in servers-action-console-output https://review.openstack.org/458713 | |
| 02:24:01 | openstackgerrit | Lei Zhang proposed openstack/nova master: Add sync traits command for placement https://review.openstack.org/450125 | |
| 03:00:30 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Use 'note' directive https://review.openstack.org/458717 | |
| 03:15:30 | openstackgerrit | Ghanshyam Mann proposed openstack/nova master: Explicitly define enum type as string in schema https://review.openstack.org/456430 | |
| 03:21:33 | openstackgerrit | Zhenyu Zheng proposed openstack/nova master: Support tag instances when boot https://review.openstack.org/394321 | |
| 04:19:18 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (2/4) https://review.openstack.org/455568 | |
| 04:19:35 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (3/4) https://review.openstack.org/455570 | |
| 04:19:58 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (4/4) https://review.openstack.org/455573 | |
| 04:20:16 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Example verification for servers-actions.inc https://review.openstack.org/454565 | |
| 05:53:45 | openstackgerrit | Alex Xu proposed openstack/python-novaclient master: Add `instance-uuid` flag to the migration-list https://review.openstack.org/458728 | |
| 06:02:55 | Dinesh_Bhor | alex_xu: Hi, if you have time then may I have your attention on this? https://review.openstack.org/#/c/457890/ | |
| 06:49:26 | openstackgerrit | Zhenyu Zheng proposed openstack/nova master: Support tag instances when boot https://review.openstack.org/394321 | |
| 06:51:18 | openstackgerrit | Alex Xu proposed openstack/nova master: Move all the deprecated server actions together into the bottom of doc https://review.openstack.org/458738 | |
| 06:51:18 | openstackgerrit | Alex Xu proposed openstack/nova master: Deprecate Multinic, floatingip action and os-virtual-interface API https://review.openstack.org/457181 | |
| 06:51:19 | openstackgerrit | Alex Xu proposed openstack/nova master: Adjust the order of server actions in api-ref https://review.openstack.org/458739 | |
| 06:58:15 | openstackgerrit | Zhenyu Zheng proposed openstack/nova master: Add description to policies in hypervisors.py https://review.openstack.org/451294 | |
| 07:12:27 | alex_xu | johnthetubaguy: how about rename all of those titles in api-ref as URL, for example https://developer.openstack.org/api-ref/compute/#servers-run-an-action-servers-action rename to '/servers/{server_uuid}/action' | |
| 07:48:13 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: WIP: Specify keymap on server boot (1/2) https://review.openstack.org/458752 | |
| 07:55:14 | johnthetubaguy | alex_xu: I was thinking about those when I was going through your patches yesterday... | |
| 07:55:46 | johnthetubaguy | alex_xu: I think we probably should reorganise based around the URL patterns, maybe we should etherpad out some possible ways to arrange those | |
| 07:56:57 | johnthetubaguy | alex_xu: https://etherpad.openstack.org/p/nova-api-ref-organisation | |
| 08:03:29 | johnthetubaguy | alex_xu: I take that back, its basically there | |
| 08:23:17 | sfinucan | cfriesen: I am now | |
| 08:36:21 | openstack | Launchpad bug 1664032 in os-brick "iSCSI Multipath may leave residual paths due to race condition" [Undecided,Fix released] - Assigned to Gorka Eguileor (gorka) | |
| 08:36:21 | mdbooth | imacdonn lyarwood: https://bugs.launchpad.net/os-brick/+bug/1664032 | |
| 08:37:01 | openstackgerrit | Bhagyashri Shewale proposed openstack/nova master: Don't create instance backup image if rotation is 0 https://review.openstack.org/409644 | |
| 08:39:53 | lyarwood | mdbooth: nice, so limiting the rescans would help for iSCSI but I wonder how many other backends could still race? | |
| 08:40:11 | mdbooth | lyarwood: Well the issue is peculiar to a global rescan | |
| 08:40:55 | mdbooth | lyarwood johnthetubaguy: While I was thinking about this, though, a couple of things occurred to me | |
| 08:41:18 | mdbooth | Namely that os-brick probably should explicitly know about terminate connection | |
| 08:41:48 | mdbooth | And that the required scope of locks is always going be be driver-specific | |
| 08:41:55 | johnthetubaguy | it does feel like we need to have a more well understood relationship with os-brick | |
| 08:42:08 | johnthetubaguy | I like the idea of negotiation about locking | |
| 08:42:21 | lyarwood | well, terminate connection no longer exists in v3 | |
| 08:42:44 | mdbooth | lyarwood: The function exists, though | |
| 08:42:50 | mdbooth | Delete attachment, presumably? | |
| 08:43:05 | lyarwood | right, but that's terminate connection and detach | |
| 08:43:11 | lyarwood | in v2 | |
| 08:44:28 | mdbooth | johnthetubaguy: The problem with having differing scope of locks is that it's hard to represent that across an api boundary | |
| 08:45:17 | mdbooth | I mean, if backend A requires X to be serialised only with itself, backend B requires X and Y to be serialised, and backend C has no such restrictions | |
| 08:45:39 | mdbooth | How do you abstract that for the caller? | |
| 08:46:03 | mdbooth | I think the locking would need to live in the backend | |
| 08:46:41 | asettle | cdent: you around? :) | |
| 08:46:52 | cdent | asettle: I just showed up, what's up? | |
| 08:46:58 | asettle | Magic@ | |
| 08:47:03 | asettle | Placement API :( | |
| 08:47:28 | openstack | Launchpad bug 1683585 in openstack-manuals "Placement endpoint configuration incorrect as written" [Undecided,New] - Assigned to Brian Moss (bmoss) | |
| 08:47:28 | asettle | Any chance you could take a look at this bug to help out Brian and myself? https://bugs.launchpad.net/openstack-manuals/+bug/1683585 | |
| 08:48:11 | lyarwood | mdbooth: so just serialise all volume operations (both local n-cpu and remote via c-api) for all backends? | |
| 08:48:31 | mdbooth | lyarwood: You could do that, but that's a big hammer | |
| 08:48:48 | mdbooth | Akin to a GIL ;) | |
| 08:49:01 | lyarwood | GBDML | |
| 08:49:11 | cdent | asettle: ah, that. Yeah, so the issue is that there hasn't been consensus between nova, devstack, deb packagers, rpm packages on "where" placement is supposed to live | |
| 08:49:19 | mdbooth | hehe | |
| 08:49:37 | lyarwood | but yeah, massive hammer, slows everything down | |
| 08:49:38 | asettle | cdent: yep. Which is causing issues, it's our second bug of the same nature. We're going to have to chat about reversing it, I think. IT's just not working. | |
| 08:49:41 | cdent | asettle: I would guess that what needs to happen is find out from the packages where they are putting it (it can go wherever they like), and make the docs reflect that | |
| 08:49:56 | cdent | s/packages/packagers/ | |
| 08:50:17 | mdbooth | Suspect the problem would mostly be that 1 slow/malfunctioning thing would kill everything | |
| 08:50:34 | cdent | asettle: I can reflect this on the bug report too | |
| 08:50:37 | asettle | cdent: who can we get to sort out the packaging then? | |
| 08:51:22 | cdent | asettle: I don't have the names at the top of my head. johnthetubaguy and mdbooth you know who the contacts are for ubuntu and rdo packages? | |
| 08:51:59 | mdbooth | lyarwood: ^^^ ? | |
| 08:53:55 | mdbooth | cdent: You looking for a default port number? | |
| 08:54:15 | cdent | mdbooth: no | |
| 08:54:41 | cdent | looking for agreement between the various parties on where it will be placed, or at least authoritative statements on how things are current configured | |
| 08:55:09 | asettle | cdent: thanks for looking into it. Contextually, could you please explain to me why this was implemented without consensus? Am I msising something? :/ | |
| 08:55:21 | cdent | hmmm | |
| 08:55:45 | cdent | I'm pretty sure that the rpm and debs use the same port. | |
| 08:55:45 | mdbooth | cdent: Being dim, just trying to understand what 'where' means in this context. | |
| 08:55:51 | mdbooth | where == port number? | |
| 08:55:58 | asettle | Okay, well, that's good? | |
| 08:56:15 | alex_xu | johnthetubaguy: yea, agree with that. begin to do some cleanup https://review.openstack.org/458738 https://review.openstack.org/458739 | |
| 08:56:50 | bauzas | asettle: mmm I do remember a problem with RDO packaging for the above bug, sec | |
| 08:57:06 | asettle | bauzas: The same issue we were fiddling with a few weeks back? | |
| 08:57:06 | cdent | The issue entered into the discussion because there is a movement to stop using ports for hosting each of the individual services and instead put them on default http (80) or https (443) ports on the same controller host, distinguishing between services by a path prefix | |
| 08:57:16 | bauzas | not using ports means you have to have your virtualhost able to accept on this location | |
| 08:57:24 | openstackgerrit | jichenjc proposed openstack/nova master: [placement] Add doc for resource provider usages https://review.openstack.org/450105 | |
| 08:57:49 | cdent | asettle, bauzas: there have been a few different bugs related to the configuration, for example, needing <Directory> | |