On Thu, Oct 2, 2014 at 6:04 AM, Ken'ichi Ohmichi ken1ohmi...@gmail.com
wrote:
Thanks for your advice, that is very useful input for me.
I read both keystone-specs and ietf draft-spec for JSON-Home.
I have a question.
JSON-Home is useful for advertising API URL paths to clients, I guess
On 10/02/2014 09:54 AM, Brant Knudson wrote:
When discussing the document schema I think we're planning to use
JSONSchema... In Keystone, we've got J-S implemented on some parts (I
don't think it covers all resources yet). I also don't think our
JSONSchema is discoverable yet (i.e., you can't
-Original Message-
From: Brant Knudson [mailto:b...@acm.org]
Sent: Thursday, October 02, 2014 10:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
implementation
Thanks for your advice
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Wednesday, September 24, 2014 12:47 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
implementation
On 09/22/2014 04:27 PM, Brant Knudson wrote:
On Fri
On 09/24/2014 05:26 AM, Kenichi Oomichi wrote:
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Wednesday, September 24, 2014 12:47 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version implementation
On 09/22/2014
vNext seems an interesting idea, I thought the implementation way for Nova
a little. API Route Discoverability is a nice design, but a root / URL
will conflict on current list versions API.
Maybe there would be a workaround.
Completely agreed, Ken'ichi. The root URL that returns the
-Original Message-
From: Brant Knudson [mailto:b...@acm.org]
Sent: Thursday, September 25, 2014 12:04 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
implementation
vNext seems
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Wednesday, September 24, 2014 1:09 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
implementation
(1) Input/Output attribute names
(1.1) These names
: [openstack-dev] [Nova] Some ideas for micro-version
implementation
On 09/22/2014 04:27 PM, Brant Knudson wrote:
On Fri, Sep 19, 2014 at 1:39 AM, Alex Xu x...@linux.vnet.ibm.com
mailto:x...@linux.vnet.ibm.com wrote:
Close to Kilo, it is time to think about what's next for
nova API
On Mon, 22 Sep 2014 09:29:26 +
Kenichi Oomichi oomi...@mxs.nes.nec.co.jp wrote:
Before discussing how to implement, I'd like to consider what we
should implement. IIUC, the purpose of v3 API is to make consistent
API with the backwards incompatible changes. Through huge discussion
in
On Mon, 22 Sep 2014 09:47:50 -0500
Anne Gentle a...@openstack.org wrote:
(1) Input/Output attribute names
(1.1) These names should be snake_case.
eg: imageRef - image_ref, flavorRef - flavor_ref, hostId -
host_id (1.2) These names should contain extension names if they
are provided
On Mon, 22 Sep 2014 15:27:47 -0500
Brant Knudson b...@acm.org wrote:
Did you consider JSON Home[1] for this? For Juno we've got JSON Home
support in Keystone for Identity v3 (Zaqar was using it already). We
weren't planning to use it for microversioning since we weren't
planning on doing
On 2014年09月23日 17:12, Christopher Yeoh wrote:
On Mon, 22 Sep 2014 09:29:26 +
Kenichi Oomichi oomi...@mxs.nes.nec.co.jp wrote:
Before discussing how to implement, I'd like to consider what we
should implement. IIUC, the purpose of v3 API is to make consistent
API with the backwards
On 09/22/2014 04:27 PM, Brant Knudson wrote:
On Fri, Sep 19, 2014 at 1:39 AM, Alex Xu x...@linux.vnet.ibm.com
mailto:x...@linux.vnet.ibm.com wrote:
Close to Kilo, it is time to think about what's next for nova API.
In Kilo, we
will continue develop the important feature
On 09/22/2014 05:29 AM, Kenichi Oomichi wrote:
-Original Message-
From: Alex Xu [mailto:x...@linux.vnet.ibm.com]
Sent: Friday, September 19, 2014 3:40 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Nova] Some ideas for micro-version implementation
Close to Kilo
On Tue, 2014-09-23 at 12:09 -0400, Jay Pipes wrote:
I'd like to say finally that I think there should be an OpenStack API
working group whose job it is to both pull together a set of OpenStack
API practices as well as evaluate new REST APIs proposed in the
OpenStack ecosystem to provide
On 09/23/2014 01:15 PM, Kevin L. Mitchell wrote:
On Tue, 2014-09-23 at 12:09 -0400, Jay Pipes wrote:
I'd like to say finally that I think there should be an OpenStack API
working group whose job it is to both pull together a set of OpenStack
API practices as well as evaluate new REST APIs
On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote:
I've been thinking along very similar lines, but I don't think each current
API needs to be replaced. I would very much like to see a unified API
project that could be responsible for managing requests to boot an instance
with this
On Tue, 2014-09-23 at 18:39 +0100, Louis Taylor wrote:
On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote:
I've been thinking along very similar lines, but I don't think each current
API needs to be replaced. I would very much like to see a unified API
project that could be
On 09/23/2014 02:10 PM, Kevin L. Mitchell wrote:
On Tue, 2014-09-23 at 18:39 +0100, Louis Taylor wrote:
On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote:
I've been thinking along very similar lines, but I don't think each current
API needs to be replaced. I would very much like to
On 09/23/2014 12:19 PM, Sean Dague wrote:
On 09/23/2014 02:10 PM, Kevin L. Mitchell wrote:
On Tue, 2014-09-23 at 18:39 +0100, Louis Taylor wrote:
On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote:
I've been thinking along very similar lines, but I don't think each current
API needs
On Tue, Sep 23, 2014 at 1:19 PM, Sean Dague s...@dague.net wrote:
So today we have a proxy API in Nova which does some of this. I guess
the question is is it better to do this in Nova in the future or divorce
it from there.
A stand-alone, production-quality configurable proxy would be useful
-Original Message-
From: Christopher Yeoh [mailto:cbky...@gmail.com]
Sent: Tuesday, September 23, 2014 7:39 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
implementation
On Mon, 22 Sep 2014 09
Hi Alex,
Thank you for doing this.
-Original Message-
From: Alex Xu [mailto:x...@linux.vnet.ibm.com]
Sent: Friday, September 19, 2014 3:40 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Nova] Some ideas for micro-version implementation
Close to Kilo
: [openstack-dev] [Nova] Some ideas for micro-version
implementation
Close to Kilo, it is time to think about what's next for nova API. In
Kilo, we
will continue develop the important feature micro-version.
In previous v2 on v3 propose, it's include some implementations can be
used
On Fri, Sep 19, 2014 at 1:39 AM, Alex Xu x...@linux.vnet.ibm.com wrote:
Close to Kilo, it is time to think about what's next for nova API. In
Kilo, we
will continue develop the important feature micro-version.
In previous v2 on v3 propose, it's include some implementations can be
used for
On 2014年09月23日 04:27, Brant Knudson wrote:
On Fri, Sep 19, 2014 at 1:39 AM, Alex Xu x...@linux.vnet.ibm.com
mailto:x...@linux.vnet.ibm.com wrote:
Close to Kilo, it is time to think about what's next for nova API.
In Kilo, we
will continue develop the important feature
mailto:x...@linux.vnet.ibm.com]
Sent: Friday, September 19, 2014 3:40 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Nova] Some ideas for micro-version
implementation
Close to Kilo, it is time to think about what's next for nova
API. In
Kilo, we
Close to Kilo, it is time to think about what's next for nova API. In
Kilo, we
will continue develop the important feature micro-version.
In previous v2 on v3 propose, it's include some implementations can be
used for micro-version.
29 matches
Mail list logo