[openstack-dev] [nova] Discussions for ivshmem support in OpenStack Nova

2017-07-26 Thread TETSURO NAKAMURA
-making in our project. Thanks in advance, Tetsuro Nakamura On 2017/05/08 22:09, Daniel P. Berrange wrote: On Fri, Apr 28, 2017 at 09:38:38AM +0100, sfinu...@redhat.com wrote: On Fri, 2017-04-28 at 13:23 +0900, TETSURO NAKAMURA wrote: Hi Nova team, I'm writing this e-mail because I'd like to have

Re: [openstack-dev] [srv-apl-arch:7353] Re: [nova] Discussions for ivshmem support in OpenStack Nova

2017-07-26 Thread TETSURO NAKAMURA
On 2017/07/27 0:58, Daniel P. Berrange wrote: On Wed, Jul 26, 2017 at 11:53:06AM -0400, Jay Pipes wrote: On 07/26/2017 09:57 AM, Daniel P. Berrange wrote: On Wed, Jul 26, 2017 at 09:50:23AM -0400, Jay Pipes wrote: On 07/26/2017 03:06 AM, TETSURO NAKAMURA wrote: Hi Nova team, It has been

[openstack-dev] [nova] Discussions for DPDK support in OpenStack

2017-04-27 Thread TETSURO NAKAMURA
apps/spp/ [2] http://openvswitch.org/support/dist-docs-2.5/INSTALL.DPDK.md.html#L446-L490 [3] https://blueprints.launchpad.net/nova/+spec/libvirt-options-for-dpdk Sincerely, -- Tetsuro Nakamura <nakamura.tets...@lab.ntt.co.jp> NTT Network Service Systems Laboratories TEL:0422 59 6914(National)/+81 42

Re: [openstack-dev] [srv-apl-arch:7386] Re: [nova] Discussions for ivshmem support in OpenStack Nova

2017-07-30 Thread TETSURO NAKAMURA
On 2017/07/27 20:53, Mooney, Sean K wrote: -Original Message- From: TETSURO NAKAMURA [mailto:nakamura.tets...@lab.ntt.co.jp] Sent: Thursday, July 27, 2017 2:13 AM To: Daniel P. Berrange <berra...@redhat.com>; Mooney, Sean K <sean.k.moo...@intel.com> Cc: Jay Pipes <jay

Re: [openstack-dev] [nova] Discussions for DPDK support in OpenStack

2017-05-08 Thread TETSURO NAKAMURA
Thank you for reply! On 2017/04/28 4:38, sfinu...@redhat.com wrote: On Fri, 2017-04-28 at 13:23 +0900, TETSURO NAKAMURA wrote: Hi Nova team, I'm writing this e-mail because I'd like to have a discussion about DPDK support at OpenStack Summit in Boston. We have developed a dpdk-based patch

Re: [openstack-dev] [nova] Discussions for DPDK support in OpenStack

2017-05-08 Thread TETSURO NAKAMURA
uot; https://lists.linuxfoundation.org/pipermail/virtualization/2014-June/026767.html On 2017/05/08 9:09, Daniel P. Berrange wrote: On Fri, Apr 28, 2017 at 09:38:38AM +0100, sfinu...@redhat.com wrote: On Fri, 2017-04-28 at 13:23 +0900, TETSURO NAKAMURA wrote: Hi Nova team, I'm writing this e-mail because I'd li

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

2018-05-28 Thread TETSURO NAKAMURA
enStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Tetsuro Nakamura NTT Network Service Systems Laboratories TEL:0422 59 6914(National)/+81 422 59 6

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

2018-08-20 Thread TETSURO NAKAMURA
So my hope is that (in no particular order) Jay Pipes, Eric Fried, Takashi Natsume, Tetsuro Nakamura, Matt Riedemann, Andrey Volkov, Alex Xu, Balazs Gibizer, Ed Leafe, and any other contributor to placement whom I'm forgetting [1] would express their preference on what they'd like to see happen

Re: [openstack-dev] [nova] [placement] placement update 18-10

2018-03-11 Thread Tetsuro Nakamura
# Questions > What's the status of shared resource providers? Did we even talk > about that in Dublin? In terms of bug fixes related to allocation candidates, I'll try to answer that question :) Most of the bugs that have been reported in https://bugs.launchpad.net/nova/+bug/1731072 are sorted

Re: [openstack-dev] [nova] [placement] placement update 18-14

2018-04-08 Thread TETSURO NAKAMURA
should +2 on this without discussions. Thanks! -- Tetsuro Nakamura <nakamura.tets...@lab.ntt.co.jp> NTT Network Service Systems Laboratories TEL:0422 59 6914(National)/+81 422 59 6914(International) 3-9-11, Midori-Cho Musashino-Shi, Toky

Re: [openstack-dev] [nova][placement] Placement requests and caching in the resource tracker

2018-11-05 Thread Tetsuro Nakamura
Thus we should only read from placement: > * at compute node startup > * when a write fails > And we should only write to placement: > * at compute node startup > * when the virt driver tells us something has changed I agree with this. We could also prepare an interface for

Re: [openstack-dev] [placement] Tetsuro Nakamura now core

2018-09-28 Thread TETSURO NAKAMURA
/listinfo/openstack-dev -- Tetsuro Nakamura NTT Network Service Systems Laboratories TEL:0422 59 6914(National)/+81 422 59 6914(International) 3-9-11, Midori-Cho Musashino-Shi, Tokyo 180-8585 Japan __ OpenStack Development