Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-05-31
04:16:29 openstackgerrit Jay Pipes proposed openstack/nova master: placement: Allocation.consumer field https://review.openstack.org/565405
04:16:30 openstackgerrit Jay Pipes proposed openstack/nova master: rework allocation handler _allocations_dict() https://review.openstack.org/565407
04:16:32 openstackgerrit Jay Pipes proposed openstack/nova master: Add a microversion for consumer generation support https://review.openstack.org/565604
04:34:39 openstackgerrit Merged openstack/nova stable/pike: Fix shelving a paused instance https://review.openstack.org/569651
05:13:43 openstackgerrit Vishakha Agarwal proposed openstack/python-novaclient master: No requirement of –all-tenants while listing servers https://review.openstack.org/569090
06:24:42 openstackgerrit Nguyen Hai proposed openstack/nova-specs master: Follow the new PTI for document build https://review.openstack.org/551802
07:08:05 openstackgerrit Jan Gutter proposed openstack/os-vif master: Add multiqueue field to InstanceInfo https://review.openstack.org/570959
07:45:58 openstackgerrit tianhui proposed openstack/nova master: Fix bug to api-ref https://review.openstack.org/571375
08:32:16 naichuans bauzas, Hi, Sylvain. I have some questions about your email: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130783.html. You said keep old and new rps, do you mean we will have an old compute node rp and a new compute node rp? or just a new compute node rp but keep old inventory in it?
08:34:03 bauzas naichuans: no, I was considering to keep the same behaviour for providing the VGPU RC to the compute inventory for the first type
08:34:24 bauzas naichuans: and just create a child RP with a new inventory for a second or more type
08:37:35 naichuans bauzas: got it. But when could we delete it? if we use n-rp as that, the compute node rp will always have the old inventory, it prevent us from use a true n-rp implement.
08:38:14 openstackgerrit jichenjc proposed openstack/nova master: not reraise DiskNotFound if instance is resized https://review.openstack.org/571410
08:38:41 bauzas naichuans: by providing an online migration in Rocky
08:38:57 bauzas naichuans: I mean, upgrading shouldn't modify the existing
08:39:05 openstackgerrit jichenjc proposed openstack/nova master: not reraise DiskNotFound if instance is resized https://review.openstack.org/571410
08:39:28 bauzas naichuans: but then, operators would need to use a CLI online migration for passing the VGPU inventory to a new child in between Rocky and Stein
08:41:26 naichuans bauzas: not sure about "passing the VGPU inventory to a new child", could you explain more? thanks.
08:41:41 bauzas naichuans: do you know about online migrations ?
08:42:36 naichuans bauzas: no, it's something about upgrade?
08:43:21 bauzas naichuans: yup
08:43:43 bauzas naichuans: DB online migrations help operators to modify the DB during a cycle
08:44:40 bauzas instead of needing to upgrade the DB offline, they just need to run the schema upgrades when upgrading offline, but then they can run the online migrations when they want
08:44:50 bauzas after running again the computes
08:46:46 naichuans bauzas: operator use this to modify the DB to remove old inv?
08:48:31 naichuans bauzas: if so, we don't need to return old inv to placement in driver. we can directly move to new n-rp implement, and let operator modify DB after upgrade?
08:51:25 bauzas naichuans: if we do that, operators need to run that upgrade script *before* restarting the compute after upgrading, which is not something we want, right?
08:56:48 naichuans bauzas: could you give a rough flow? modify DB -> upgrade -> retarting service?
08:58:45 openstackgerrit zhulingjie proposed openstack/nova master: Update overriden to overridden https://review.openstack.org/571418
09:00:42 naichuans bauzas: If we modify the driver code to return vGPU inventories both for compute node rp and vGPU node rp, the old inventories would exist in placement db forever. I realy confused about that. Maybe I misunderstand your point,,,
09:01:13 bauzas naichuans: I was thinking of something like 'upgrade additive DB schema modifications' -> upgrade & restart n-cpu -> run the DB online migration tool
09:01:30 bauzas naichuans: lemme point you some code
09:01:46 naichuans bauzas: thanks
09:01:52 bauzas naichuans: first, docs https://docs.openstack.org/nova/latest/user/upgrade.html
09:02:31 bauzas naichuans: I mean https://docs.openstack.org/nova/latest/user/upgrade.html#data-migrations
09:03:28 bauzas naichuans: and then code https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L375
09:04:52 naichuans bauzas: will check it, thanks
09:11:17 bauzas naichuans: replied to the thread with a proposal, lemme give you the link
09:12:21 naichuans bauzas: OK
09:12:51 bauzas naichuans: there it is http://lists.openstack.org/pipermail/openstack-dev/2018-May/130955.html
09:13:23 bauzas naichuans: does Xen support vGPU live migration ?
09:13:34 naichuans bauzas: got it~
09:13:58 bauzas because QEMU folks say it's a very difficult thing to implement because there are a huge number of corner cases to consider
09:22:16 kashyap bauzas: Which part is this?
09:22:29 kashyap Ah, Xen
09:22:36 bauzas kashyap: which part of what ?
09:22:49 kashyap Difficulty in implementing in QEMU
09:23:12 bauzas maybe the wording is inappropriate
09:23:40 bauzas it's not "difficult", it's just quite having a lot of cases to consider
09:30:41 naichuans bauzas: sorry, just saw your message about VGPU live migration. XenServer do support live migration
09:44:14 naichuans bauzas: just finish reading your conversation history about n-rp in vGPU. You are using DB online migration to avoid compute service restart, right?
09:49:49 openstackgerrit Lee Yarwood proposed openstack/nova stable/queens: libvirt: handle DiskNotFound during update_available_resource https://review.openstack.org/571424
09:49:50 openstackgerrit Lee Yarwood proposed openstack/nova stable/queens: libvirt: Skip fetching the virtual size of block devices https://review.openstack.org/571425
09:50:39 openstackgerrit Lee Yarwood proposed openstack/nova stable/pike: libvirt: handle DiskNotFound during update_available_resource https://review.openstack.org/571426
09:50:40 openstackgerrit Lee Yarwood proposed openstack/nova stable/pike: libvirt: Skip fetching the virtual size of block devices https://review.openstack.org/571427
09:56:36 openstackgerrit Balazs Gibizer proposed openstack/nova master: Reject interface attach with QoS aware port https://review.openstack.org/570078
09:56:37 openstackgerrit Balazs Gibizer proposed openstack/nova master: Reject networks with QoS policy https://review.openstack.org/570079
09:58:21 openstackgerrit wanghongtao proposed openstack/nova master: Fix the metadata re to match the unicode https://review.openstack.org/536236
10:07:31 openstackgerrit Merged openstack/nova master: pci: don't consider case when match tags specs https://review.openstack.org/565808
10:16:40 openstackgerrit Lee Yarwood proposed openstack/nova stable/ocata: libvirt: handle DiskNotFound during update_available_resource https://review.openstack.org/571432
10:16:41 openstackgerrit Lee Yarwood proposed openstack/nova stable/ocata: libvirt: Skip fetching the virtual size of block devices https://review.openstack.org/571433
10:20:27 sahid artom: thanks for what you did on the vf trusted serie :)
10:21:00 artom sahid, oh, hah, I'd just apologized on the downstream channel
10:21:47 sahid artom: yes but, please don't, i have appreciated thanks again
10:22:33 artom sahid, cool, you're welcome :)
10:22:44 artom We *really* need to unfsck the metadata API
10:23:15 artom The fact that we're not using templates, and adding/removing stuff based on ifs...
10:23:21 artom *Versioned* templates, I should say
10:23:38 sahid artom: i see, yes that make sense to have such mech
10:24:08 artom sahid, well the "real" API uses those, I believe
10:27:00 sahid artom: i did not get time to look at your serie about the live migration, i saw that it's still in WIP - my understanding is i could wwait a bit more before to start reviewing it
10:27:11 sahid or do you think we should start to make some reviews?
10:27:17 artom sahid, yeah, no worries, there's not much there yet
10:27:23 artom Well
10:28:07 artom https://review.openstack.org/#/c/566398/7 and https://review.openstack.org/#/c/566723/8 and ready
10:28:23 artom The last one is marked WIP because the one below it is
10:28:35 artom It's like a WIP sandwich
11:27:56 openstackgerrit Hironori Shiina proposed openstack/nova master: virt/ironic: Implement rescue and unrescue https://review.openstack.org/416487
11:51:24 openstackgerrit Hironori Shiina proposed openstack/nova master: WIP: virt/ironic: Implement rescue and unrescue https://review.openstack.org/571450
11:57:43 openstackgerrit Jan Gutter proposed openstack/os-vif master: Add virtio_multiqueue field to InstanceInfo https://review.openstack.org/570959
12:34:01 openstackgerrit Zhenyu Zheng proposed openstack/nova master: WIP abort live migration in queue. https://review.openstack.org/568542
12:36:55 openstackgerrit Zhenyu Zheng proposed openstack/nova master: WIP abort live migration in queue. https://review.openstack.org/568542
12:37:33 openstackgerrit Jan Gutter proposed openstack/nova master: Convert vrouter legacy plugging to os-vif https://review.openstack.org/571325
12:37:34 openstackgerrit Jan Gutter proposed openstack/nova master: Use vif.vif_name in _set_config_VIFGeneric https://review.openstack.org/571461
12:37:35 openstackgerrit Jan Gutter proposed openstack/nova master: Pass virtio multiqueue info to os-vif plugins https://review.openstack.org/571462
12:51:44 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: WIP: Adapt _validate_instance_group_policy to new policy model https://review.openstack.org/571465
13:13:47 openstackgerrit Surya Seetharaman proposed openstack/nova master: Delete orphaned RS and IM records of archived instances https://review.openstack.org/560042
13:14:19 openstackgerrit Chen proposed openstack/nova master: WIP Closes-Bug: #1449221 https://review.openstack.org/571472
13:14:20 openstack bug 1449221 in OpenStack Compute (nova) "Nova doesn't allow cleanup of volumes stuck in 'attaching' or 'detaching' status" [High,Confirmed] https://launchpad.net/bugs/1449221
13:50:29 melwitt nova meeting in 10 minutes
13:53:00 mriedem dansmith: can you get this queens backport? https://review.openstack.org/#/c/571425/
13:54:13 mriedem lyarwood: looks like you have something to fix in this one https://review.openstack.org/#/c/571433/
13:57:02 dansmith hmm, not sure why that depends on the update resource patch
13:57:59 lyarwood mriedem: yeah, couldn't run tox locally for Ocata for some reason, I'll get to it later today
13:58:44 lyarwood dansmith: it just keeps the backport clean, I was already looking to backport the resource patch anyway so...
13:59:24 dansmith hmm, okay
14:00:55 openstackgerrit sahid proposed openstack/os-vif master: Add virtio_multiqueue field to InstanceInfo https://review.openstack.org/570959
14:04:13 openstackgerrit Jay Pipes proposed openstack/nova master: placement: always create consumer records https://review.openstack.org/567678
14:04:14 openstackgerrit Jay Pipes proposed openstack/nova master: add consumers generation field https://review.openstack.org/557958
14:04:15 openstackgerrit Jay Pipes proposed openstack/nova master: placement: Allocation.consumer field https://review.openstack.org/565405

Earlier   Later