-dev
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail: natsume.taka...@lab.ntt.co.jp
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
there are objections, I'll plan on adding Takashi to the
python-novaclient-core group next week.
I've added Takashi to python-novaclient-core:
https://review.openstack.org/#/admin/groups/572,members
Thanks everyone.
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail
#/c/528201/
api-ref: Example verification for servers.inc
https://review.openstack.org/#/c/529520/
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail: natsume.taka...@lab.ntt.co.jp
__
OpenStack Development Mailing
/nova/+bug/1732581
When a spec file is added or modified, the 'openstack-tox-py27' job
should be executed.
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail: natsume.taka...@lab.ntt.co.jp
__
OpenStack Developme
ug.
https://bugs.launchpad.net/nova/+bug/1721179
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail: natsume.taka...@lab.ntt.co.jp
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
e the host record in
'host_mappings' table?
I couldn't find it.
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail: natsume.taka...@lab.ntt.co.jp
__
OpenStack Development Mailing List (not for usage questions)
U
*.
-
[1] https://review.openstack.org/#/c/494173/
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail: natsume.taka...@lab.ntt.co.jp
__
OpenStack Development Mailing List
On 2017/07/04 21:12, Alex Xu wrote:
2017-07-04 15:40 GMT+08:00 Ghanshyam Mann <ghanshyamm...@gmail.com>:
On Mon, Jul 3, 2017 at 1:38 PM, Takashi Natsume
<natsume.taka...@lab.ntt.co.jp> wrote:
In Nova API reference, there is inconsistency in
whether to define parameters
://developer.openstack.org/api-ref/compute/?expanded=list-server-groups-detail#list-server-groups
In the case that the parameter is always included in the response after
a certain microversion,
should it be defined as 'required' instead of 'optional'?
Regards,
Takashi Natsume
NTT Software Innovation
On 2017/06/05 22:19, Sean Dague wrote:
On 06/05/2017 01:06 AM, Takashi Natsume wrote:
But IMO, it is better to fix citations in specs (*4)
rather than capping the sphinx version.
Thank you for the patch, I just merged *4.
Thank you.
It is no longer necessary to cap the sphinx version
tps://bugs.launchpad.net/nova/+bug/1695127
*4: Fix citation references (Sphinx 1.6.x compatibility)
https://review.openstack.org/#/c/470252/
-
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail: natsume.taka...@lab.ntt.co
On 2017/01/10 20:35, Sean Dague wrote:
On 01/10/2017 01:39 AM, Takashi Natsume wrote:
Hi Nova developers.
In Nova API Reference(*1),
the following parameters' values are 'null' in HTTP request body samples.
And their parameter types are defined as 'string'.
* 'confirmResize' parameter
efined as 'none'.
* 'trigger_crash_dump' in "Trigger Crash Dump In Server"
IMO, there is inconsistency of parameter types.
Should they be unified as 'none'?
*1: Compute API Reference
http://developer.openstack.org/api-ref/compute/
Reg
g work or I'll defer the blueprint out of tracking for Ocata so
reviewers can focus on what's planned to get done.
If by January 12th we still have changes which haven't started I'll
probably just automatically defer them.
Please let me know if there are any questions.
[1] https://blueprints.l
migration
https://review.openstack.org/#/c/247767/
[5] Enable volume owners to execute migrate_volume_completion
https://review.openstack.org/#/c/253363/
Regards,
Takashi Natsume
NTT Software Innovation Center
E-mail: natsume.taka...@lab.ntt.co.jp
w if there were other situations that were different
> here between the old policy enforcement and
> the new one.
If I find another case, I will report it.
Regards,
Takashi Natsume
NTT Software Innovation Center
Tel: +81-422-59-4399
E-mail: natsume.taka...@lab.ntt.co.jp
> -Orig
://bugs.launchpad.net/nova/+bug/1539351
Regards,
Takashi Natsume
NTT Software Innovation Center
Tel: +81-422-59-4399
E-mail: natsume.taka...@lab.ntt.co.jp
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
that was gotten in 4..
Are these bugs?
Or are there any reasons to implement these ways?
Regards,
Takashi Natsume
NTT Software Innovation Center
Tel: +81-422-59-4399
E-mail: natsume.taka...@lab.ntt.co.jp
___
OpenStack-dev mailing list
OpenStack-dev
Dolph,
Thank you so much.
I understand that using OS-REVOKE Extension will solve these issues.
Regards,
Takashi Natsume
NTT Software Innovation Center
Tel: +81-422-59-4399
E-mail: natsume.taka...@lab.ntt.co.jp
From: Dolph Mathews [mailto:dolph.math...@gmail.com]
Sent: Thursday, June 26, 2014
19 matches
Mail list logo