On 2014年09月18日 18:57, Sean Dague wrote:
On 09/18/2014 06:38 AM, Christopher Yeoh wrote:
On Sat, 13 Sep 2014 06:48:19 -0400
Sean Dague s...@dague.net wrote:
On 09/13/2014 02:28 AM, Kenichi Oomichi wrote:
Hi Chris,
Thanks for bring it up here,
-Original Message-
From: Chris St.
On 2014年08月23日 18:29, Christopher Yeoh wrote:
On Sat, 23 Aug 2014 03:56:27 -0500
Joe Cropper cropper@gmail.com wrote:
Hi Folks,
Would anyone be opposed to adding the 'action' checking to the v2/v3
authorizers? This would allow administrators more fine-grained
control over who can read
When I startup nova-network, it stuck at trying get lock for ebtables.
@utils.synchronized('ebtables', external=True)
def ensure_ebtables_rules(rules, table='filter'):
.
Checking the code found that invoke utils.synchronized without parameter
lock_path, the code will try to use
posix
Software Park, Haidian
District, Beijing 100193, PRC
Inactive hide details for Alex Xu ---08/07/2014 04:54:09 PM---When I
startup nova-network, it stuck at trying get lock for ebtaAlex Xu
---08/07/2014 04:54:09 PM---When I startup nova-network, it stuck at
trying get lock for ebtables
Software Park, Haidian
District, Beijing 100193, PRC
Inactive hide details for Alex Xu ---08/07/2014 04:54:09 PM---When I
startup nova-network, it stuck at trying get lock for ebtaAlex Xu
---08/07/2014 04:54:09 PM---When I startup nova-network, it stuck at
trying get lock for ebtables
Oops, thanks
On 2014年08月07日 22:08, Ben Nemec wrote:
Unfortunately this is a known issue. We're working on a fix:
https://bugs.launchpad.net/oslo/+bug/1327946
On 08/07/2014 03:57 AM, Alex Xu wrote:
When I startup nova-network, it stuck at trying get lock for ebtables.
@utils.synchronized
You can search nested kvm on the web to get more info, or you can try
just use qemu not kvm on 2nd level.
On 2014?08?06? 11:32, Chen CH Ji wrote:
Thanks a lot for your suggestions , I guess it might be 2nd level
configuration issue ... will take more time on it , thanks
my 1st level host
Maybe we can implement this goal by another way, adding new API
'confirm_before_migration' that's similar with 'confirm_resize'. This
also can resolve Chris Friesen's concern.
On 2014年07月23日 00:13, Jay Pipes wrote:
On 07/21/2014 11:16 PM, Jay Lau wrote:
Hi Jay,
There are indeed some China
Question about swap volume, swap volume's implementation is very similar
with live snapshot.
Both implemented by blockRebase. But swap volume didn't check any
libvirt and qemu version.
Should we add version check for swap_volume now? That means swap_volume
will be disable also.
On 2014?06?26?
+1
On 2014年06月14日 06:40, Michael Still wrote:
Greetings,
I would like to nominate Ken'ichi Ohmichi for the nova-core team.
Ken'ichi has been involved with nova for a long time now. His reviews
on API changes are excellent, and he's been part of the team that has
driven the new API work we've
Hi, guys
There are some BPs working on improve the usability of API policy. Initially
those BP just for v2.1/v3 API. For v2 API, we just want to it keep the same
as before.
But in Juno design summit, we get some complain about policy is hard to use.
On 2014年04月17日 05:25, Jiang, Yunhong wrote:
Hi, Christopher,
I have some question to the API changes related to
https://review.openstack.org/#/c/80707/4/nova/api/openstack/compute/plugins/v3/hypervisors.py
, which adds a property to the hypervisor information.
Hi, Yunhong, Chris may
On 2014年03月21日 17:04, Christopher Yeoh wrote:
On Thu, 20 Mar 2014 15:45:11 -0700
Dan Smith d...@danplanet.com wrote:
I know that our primary delivery mechanism is releases right now, and
so if we decide to revert before this gets into a release, that's
cool. However, I think we need to be
Hi, Jeremy, the discussion at here
http://lists.openstack.org/pipermail/openstack-dev/2013-August/013688.html
Thanks
Alex
On 2014年03月07日 10:29, Liuji (Jeremy) wrote:
Hi, all
Current openstack seems not support to snapshot instance with memory and dev
states.
I searched the blueprint and
Any time except 15-22 UTC
On 2014年03月07日 08:45, Christopher Yeoh wrote:
Hi,
I'd like to start a weekly IRC meeting for those interested in
discussing Nova API issues. I think it would be a useful forum for:
- People to keep up with what work is going on the API and where its
headed.
-
On 2014?02?28? 13:40, Chris Friesen wrote:
On 02/27/2014 06:00 PM, Alex Xu wrote:
Does mean our code looks like as below?
if client_version 2:
elif client_version 3
...
elif client_version 4:
...
elif client_version 5:
...
elif client_version 6:
..
And we need test
On 2014?02?28? 00:05, Dan Smith wrote:
Sure, but that's still functionally equivalent to using the /v2 prefix.
So we could chuck the current /v3 code and do:
/v2: Current thing
/v3: invalid, not supported
/v4: added simple task return for server create
/v5: added the event extension
/v6:
On 2014年02月26日 18:40, Thierry Carrez wrote:
Kenichi Oomichi wrote:
From: Christopher Yeoh [mailto:cbky...@gmail.com]
So the problem here is what we consider a bug becomes a feature from
a user of the API point of view. Eg they really shouldn't be passing
some data in a request, but its ignored
On 2014年02月25日 21:17, Ken'ichi Ohmichi wrote:
2014-02-25 19:48 GMT+09:00 Thierry Carrez thie...@openstack.org:
Sean Dague wrote:
So, that begs a new approach. Because I think at this point even if we
did put out Nova v3, there can never be a v4. It's too much, too big,
and doesn't fit in the
Russell, that's much appreciated. I'm also very thankful to
everyone who has worked on the V3 API either through patches and/or
reviews, especially Alex Xu and Ivan Zhu who have done a lot of work on
it in Havana and Icehouse.
Thank you, Chris, hope we get a great v3 api.
Chris
Hi, guys,
I'm working neutron network stuff in nova V3 API. We will only pass port
ids when create server, and
Nova won't proxy any neutron call in the future. I plan to add new v3
network extension, that only
accept port ids as parameters. And it will pass those port ids in the
old
On 2014?02?12? 17:15, Alex Xu wrote:
Hi, guys,
I'm working neutron network stuff in nova V3 API. We will only pass
port ids when create server, and
Nova won't proxy any neutron call in the future. I plan to add new v3
network extension, that only
accept port ids as parameters
On 2014年02月04日 19:36, Christopher Yeoh wrote:
On Tue, 04 Feb 2014 11:37:29 +0100
Thierry Carrez thie...@openstack.org wrote:
Christopher Yeoh wrote:
On Tue, Feb 4, 2014 at 12:03 PM, Joe Gordon joe.gord...@gmail.com
mailto:joe.gord...@gmail.com wrote:
John and I discussed a third possibility:
On 2014?01?08? 23:12, Jay Lau wrote:
Thanks Russell, OK, will file a bug for first issue.
For second question, I want to show some of my comments here. I think
that we should disable cold migration for an ACTIVE VM as cold
migrating will first destroy the VM then re-create the VM when using
On 2014年01月14日 20:04, Ken'ichi Ohmichi wrote:
Hi,
2014/1/14 Alex Xu x...@linux.vnet.ibm.com:
+1 for drop xml. But if we can't drop it, can we think about use
XMLDictSerializer instead of XmlTemplate? We spend a lot of time to maintain
XmlTemplate, and it make xml
format inconsistent(some
+1 for drop xml. But if we can't drop it, can we think about use
XMLDictSerializer instead of XmlTemplate? We spend a lot of time to
maintain XmlTemplate, and it make xml
format inconsistent(some of resouce's attribute is output as xml
sub-element, some of them is output as xml element's
I replied some comments on the gerrit also. If we have patch for
demonstrate pecan style extension, that will be great.
Thanks
Alex
On 2013年12月18日 05:08, Ryan Petrello wrote:
So any additional feedback on this patch? I’d love to start working on porting
some of the other extensions to pecan,
On 2013年12月12日 04:41, Ryan Petrello wrote:
Hello,
I’ve spent the past week experimenting with using Pecan for Nova’s API, and
have opened an experimental review:
https://review.openstack.org/#/c/61303/6
…which implements the `versions` v3 endpoint using pecan (and paves the way for
other
? Seems better than keeping
it in the wiki so that you can update with code changes.
Anne
On Wed, Nov 13, 2013 at 11:11 PM, Alex Xu x...@linux.vnet.ibm.com
mailto:x...@linux.vnet.ibm.com wrote:
On 2013?11?14? 07:09, Christopher Yeoh wrote:
On Thu, Nov 14, 2013 at 7:52 AM, David Kranz
On 2013?12?01? 21:39, Christopher Yeoh wrote:
Hi,
At the summit we agreed to split out lock/unlock, pause/unpause,
suspend/unsuspend
functionality out of the V3 version of admin actions into separate
extensions to make it easier for deployers to only have loaded the
functionality that they
Hi, guys,
Looks like ratelimits is not really useful. The reason already pointed
out by this patch:
https://review.openstack.org/#/c/34821/ , Thanks Joe for point it out.
So v3 API is a chance to cleanup those stuff. If there isn't anyone
object it. I will send patch
to get ride of
On 2013?09?08? 21:34, Christopher Yeoh wrote:
Hi,
The following 3 changesets in the queue:
https://review.openstack.org/#/c/43274/
https://review.openstack.org/#/c/43278/
https://review.openstack.org/#/c/43280/
make keypairs, scheduler hints and console output part of the V3 core
api. This
+1
On 2013年09月05日 17:51, John Garbutt wrote:
+1 I meant to raise that myself when I saw some changes there the other day.
On 4 September 2013 15:52, Thierry Carrez thie...@openstack.org wrote:
Russell Bryant wrote:
On 09/04/2013 10:26 AM, Dan Smith wrote:
Hi all,
As someone who has felt
On 2013年08月17日 00:14, Vishvananda Ishaya wrote:
On Aug 15, 2013, at 5:58 PM, Melanie Witt melw...@yahoo-inc.com wrote:
On Aug 15, 2013, at 1:13 PM, Joe Gordon wrote:
+1 from me as long as this wouldn't change anything for the EC2 API's security
groups support, which I assume it won't.
On 2013?08?16? 14:34, Christopher Yeoh wrote:
On Fri, Aug 16, 2013 at 10:28 AM, Melanie Witt melw...@yahoo-inc.com
mailto:melw...@yahoo-inc.com wrote:
On Aug 15, 2013, at 1:13 PM, Joe Gordon wrote:
+1 from me as long as this wouldn't change anything for the EC2
API's security
On 2013年08月08日 13:49, Zhu Bo wrote:
On 2013年08月07日 21:42, Alex Xu wrote:
On 2013年08月07日 17:38, John Garbutt wrote:
multi-nic added an extra virtual interface on a seprate network, like
adding a port:
http://docs.openstack.org/trunk/openstack-compute/admin/content/using-multi-nics.html
Hi, guys,
When I'm cleaning up v3 api. I found limits extension will return
absolute_limit. I think that already
done by extension quota_sets. And I can't guess the reason why we keep
that in limits. For ensure,
I didn't missing something, I bring it to here. If we haven't any reason
for
On 2013年08月07日 22:24, John Garbutt wrote:
Hey,
On 7 August 2013 14:42, Alex Xu x...@linux.vnet.ibm.com wrote:
On 2013年08月07日 17:38, John Garbutt wrote:
multi-nic added an extra virtual interface on a seprate network, like
adding a port:
http://docs.openstack.org/trunk/openstack-compute/admin
Hi, guys,
Currently we have one core and two extensions that related network in
Nova API v3.
They are ips, attach_interface and multinic. I have two questions for them.
The first question is about ips and attach_interface. The below was the
index's response
of ips and attach_interface:
ips:
to provide networking
information, so there will be a nova-api that has to proxy info from
neutron, but I agree we should reduce where we can.
John
On 7 August 2013 10:08, Alex Xu x...@linux.vnet.ibm.com wrote:
Hi, guys,
Currently we have one core and two extensions that related network in Nova
API
301 - 340 of 340 matches
Mail list logo
