On 09/18/2014 08:49 PM, Clint Byrum wrote:
> Excerpts from Christopher Yeoh's message of 2014-09-18 16:57:12 -0700:
>> On Thu, 18 Sep 2014 12:12:28 -0400
>> Sean Dague wrote:
When we can return the json-schema to user in the future, can we say
that means API accepting utf8 or utf8mb4 is
On 09/18/2014 07:57 PM, Christopher Yeoh wrote:
> On Thu, 18 Sep 2014 12:12:28 -0400
> Sean Dague wrote:
>>> When we can return the json-schema to user in the future, can we say
>>> that means API accepting utf8 or utf8mb4 is discoverable? If it is
>>> discoverable, then we needn't limit anything
Excerpts from Christopher Yeoh's message of 2014-09-18 16:57:12 -0700:
> On Thu, 18 Sep 2014 12:12:28 -0400
> Sean Dague wrote:
> > > When we can return the json-schema to user in the future, can we say
> > > that means API accepting utf8 or utf8mb4 is discoverable? If it is
> > > discoverable, th
On 09/17/2014 10:44 AM, Day, Phil wrote:
>> -Original Message-
>> From: Jay Pipes [mailto:jaypi...@gmail.com]
>> Sent: 12 September 2014 19:37
>> To: openstack-dev@lists.openstack.org
>> Subject: Re: [openstack-dev] [nova] Expand resource name allowed
>>
On Thu, 18 Sep 2014 12:12:28 -0400
Sean Dague wrote:
> > When we can return the json-schema to user in the future, can we say
> > that means API accepting utf8 or utf8mb4 is discoverable? If it is
> > discoverable, then we needn't limit anything in our python code.
>
> Honestly, we should accept
On Thu, 18 Sep 2014 13:45:42 +0200
Flavio Percoco wrote:
> On 09/18/2014 01:28 PM, Sean Dague wrote:
> > On 09/18/2014 07:19 AM, Ken'ichi Ohmichi wrote:
> >> 2014-09-18 19:57 GMT+09:00 Sean Dague :
> >>> On 09/18/2014 06:38 AM, Christopher Yeoh wrote:
> On Sat, 13 Sep 2014 06:48:19 -0400
> >
>>>>> Hi Chris,
>>>>>
>>>>> Thanks for bring it up here,
>>>>>
>>>>>> -Original Message-
>>>>>> From: Chris St. Pierre [mailto:stpie...@metacloud.com]
>>>>>> Sent: Satur
[mailto:stpie...@metacloud.com]
Sent: Saturday, September 13, 2014 2:53 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [nova] Expand resource name allowed
characters
We have proposed that the allowed characters for all resource
names in Nova (flavors, aggregates, etc.) be expanded to all
On Thu, Sep 18, 2014 at 4:19 AM, Ken'ichi Ohmichi
wrote:
> Correct validation history is
>
> Essex: "use anything you want!"
> Folsom: "strict asci!"
> [..]
> Juno: "strict asci!"
>
I'm not sure that's quite right. My patch doesn't actually add Unicode
support; that was already added in
825499ff
On 09/18/2014 01:28 PM, Sean Dague wrote:
> On 09/18/2014 07:19 AM, Ken'ichi Ohmichi wrote:
>> 2014-09-18 19:57 GMT+09:00 Sean Dague :
>>> On 09/18/2014 06:38 AM, Christopher Yeoh wrote:
On Sat, 13 Sep 2014 06:48:19 -0400
Sean Dague wrote:
>>>
>>> We have proposed that the allowe
On 09/18/2014 07:19 AM, Ken'ichi Ohmichi wrote:
> 2014-09-18 19:57 GMT+09:00 Sean Dague :
>> On 09/18/2014 06:38 AM, Christopher Yeoh wrote:
>>> On Sat, 13 Sep 2014 06:48:19 -0400
>>> Sean Dague wrote:
>>
>> We have proposed that the allowed characters for all resource
>> names in Nova
2014-09-18 19:57 GMT+09:00 Sean Dague :
> On 09/18/2014 06:38 AM, Christopher Yeoh wrote:
>> On Sat, 13 Sep 2014 06:48:19 -0400
>> Sean Dague wrote:
>
> We have proposed that the allowed characters for all resource
> names in Nova (flavors, aggregates, etc.) be expanded to all
> pr
gt; -Original Message-
>>>> From: Chris St. Pierre [mailto:stpie...@metacloud.com]
>>>> Sent: Saturday, September 13, 2014 2:53 AM
>>>> To: openstack-dev@lists.openstack.org
>>>> Subject: [openstack-dev] [nova] Expand resource name allowed
>>
acloud.com]
> >> Sent: Saturday, September 13, 2014 2:53 AM
> >> To: openstack-dev@lists.openstack.org
> >> Subject: [openstack-dev] [nova] Expand resource name allowed
> >> characters
> >>
> >> We have proposed that the allowed characters
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: 12 September 2014 19:37
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Expand resource name allowed
> characters
>
> Had to laugh about the PILE OF POO char
Linking clearly isn't my strong suit:
https://review.openstack.org/#/c/119741/
On Mon, Sep 15, 2014 at 1:58 PM, Chris St. Pierre
wrote:
> On Mon, Sep 15, 2014 at 11:16 AM, Jay Pipes wrote:
>
>> I believe I did:
>>
>> http://lists.openstack.org/pipermail/openstack-dev/2014-
>> September/045924.h
On Mon, Sep 15, 2014 at 11:16 AM, Jay Pipes wrote:
> I believe I did:
>
> http://lists.openstack.org/pipermail/openstack-dev/2014-
> September/045924.html
Sorry, missed your explanation. I think Sean's suggestion -- to keep ID
fields restricted, but de-restrict name fields -- walks a nice middl
On 09/15/2014 10:21 AM, Chris St. Pierre wrote:
On Mon, Sep 15, 2014 at 4:34 AM, Daniel P. Berrange mailto:berra...@redhat.com>> wrote:
To arbitrarily restrict the user is a bug.
QFT.
This is why I don't feel like a blueprint should be necessary -- this is
a fairly simple changes that fix
On 09/15/2014 10:31 AM, Daniel P. Berrange wrote:
> On Mon, Sep 15, 2014 at 09:21:45AM -0500, Chris St. Pierre wrote:
>> On Mon, Sep 15, 2014 at 4:34 AM, Daniel P. Berrange
>> wrote:
>>
>>> To arbitrarily restrict the user is a bug.
>>>
>>
>> QFT.
>>
>> This is why I don't feel like a blueprint sh
On Mon, Sep 15, 2014 at 09:21:45AM -0500, Chris St. Pierre wrote:
> On Mon, Sep 15, 2014 at 4:34 AM, Daniel P. Berrange
> wrote:
>
> > To arbitrarily restrict the user is a bug.
> >
>
> QFT.
>
> This is why I don't feel like a blueprint should be necessary -- this is a
> fairly simple changes t
On Mon, Sep 15, 2014 at 4:34 AM, Daniel P. Berrange
wrote:
> To arbitrarily restrict the user is a bug.
>
QFT.
This is why I don't feel like a blueprint should be necessary -- this is a
fairly simple changes that fixes what's pretty undeniably a bug. I also
don't see much consensus on whether o
On Fri, Sep 12, 2014 at 01:52:35PM -0400, Chris St. Pierre wrote:
> We have proposed that the allowed characters for all resource names in Nova
> (flavors, aggregates, etc.) be expanded to all printable unicode characters
> and horizontal spaces: https://review.openstack.org/#/c/119741
>
> Current
ts.openstack.org
>> Subject: [openstack-dev] [nova] Expand resource name allowed characters
>>
>> We have proposed that the allowed characters for all resource names in Nova
>> (flavors, aggregates, etc.) be expanded to
>> all printable unicode characters and horizonta
Hi Chris,
Thanks for bring it up here,
> -Original Message-
> From: Chris St. Pierre [mailto:stpie...@metacloud.com]
> Sent: Saturday, September 13, 2014 2:53 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [nova] Expand resource name allowed cha
Had to laugh about the PILE OF POO character :) Comments inline...
On 09/12/2014 01:52 PM, Chris St. Pierre wrote:
We have proposed that the allowed characters for all resource names in
Nova (flavors, aggregates, etc.) be expanded to all printable unicode
characters and horizontal spaces: https:
We have proposed that the allowed characters for all resource names in Nova
(flavors, aggregates, etc.) be expanded to all printable unicode characters
and horizontal spaces: https://review.openstack.org/#/c/119741
Currently, the only allowed characters in most resource names are
alphanumeric, spa
26 matches
Mail list logo
