lts need to be a unique 1-1
>>>> mapping to a datastore version as they will vary across versions not just
>>>> the datastore type. You may have a configurable parameter that exists in
>>>> MySQL 5.6 that does not exist in MySQL 5.1 or vice versa. Or am I
>>>&
that does not exist in MySQL 5.1 or vice versa. Or am I
>>> misunderstanding?
>>>
>>> Thanks,
>>> Daniel
>>>
>>>
>>> From: Craig Vyvial
>>> Reply-To: "OpenStack Development Mailing List (not for usage
>>
stions)"
>>
>> Date: Thursday, January 23, 2014 10:55 AM
>> To: "OpenStack Development Mailing List (not for usage questions)" <
>> openstack-dev@lists.openstack.org>
>>
>> Subject: Re: [openstack-dev] [Trove] how to list available configurati
-dev@lists.openstack.org>
> Date: Thursday, January 23, 2014 10:55 AM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
>
> Subject: Re: [openstack-dev] [Trove] how to list available configuration
> parameters fo
g List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, January 23, 2014 10:55 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Trove] how
routes
>>>
>>> /datastores//configuration/ would be the collection of all
>>> parameters
>>> /datastores//configuration/:parameter would be an individual
>>> setting.
>>>
>>> - kpom
>>>
>>> ----------
>>&g
>> --
>> *From:* Craig Vyvial [cp16...@gmail.com]
>> *Sent:* Wednesday, January 22, 2014 4:11 PM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [Trove] how to list available
>>
ter would be an individual
> setting.
>
> - kpom
>
> --
> *From:* Craig Vyvial [cp16...@gmail.com]
> *Sent:* Wednesday, January 22, 2014 4:11 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Trove] ho
o: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Trove] how to list available configuration
parameters for datastores
Ok with overwhelming support for #3.
What if we modified #3 slightly because looking at it again seems like we could
shorten th
res//configuration/:parameter would be an individual
> setting.
>
> - kpom
>
> --
> *From:* Craig Vyvial [cp16...@gmail.com]
> *Sent:* Wednesday, January 22, 2014 4:11 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subj
[cp16...@gmail.com]
Sent: Wednesday, January 22, 2014 4:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Trove] how to list available configuration
parameters for datastores
Ok with overwhelming support for #3.
What if we modified #3 slightly because
Ok with overwhelming support for #3.
What if we modified #3 slightly because looking at it again seems like we
could shorten the path since /datastores//configuration doesnt
do anything.
instead of
#1
/datastores//configuration/parameters
maybe:
#2
/datastores//parameters
#3
/datastores//configu
Another +1 for option 3.
Greg
On Jan 22, 2014, at 2:27 PM, Denis Makogon
mailto:dmako...@mirantis.com>> wrote:
Goodday to all.
#3 looks more than acceptable.
/datastores//configuration/parameters.
According to configuration parameters design, a configuration set must be
associated to exactly
Goodday to all.
#3 looks more than acceptable.
/datastores//configuration/parameters.
According to configuration parameters design, a configuration set must be
associated to exactly one datastore.
Best regards, Denis Makogon.
2014/1/22 Michael Basnight
> On Jan 22, 2014, at 10:19 AM, Kaleb Po
On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote:
> My thoughts so far:
>
> /datastores//configuration/parameters (Option Three)
> + configuration set without an associated datastore is meaningless
> + a configuration set must be associated to exactly one datastore
> + each datastore must have
blueprint for this feature soon, so I'd like any
feedback anyone has.
- kpom
From: Craig Vyvial [cp16...@gmail.com]
Sent: Wednesday, January 22, 2014 10:10 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Trove] how to list availabl
I like #4 over #5 because it seems weird to have to create a configuration
first to see what parameters are allowed. With #4 you could look up what is
allowed first then create your configuration.
Robert
On Jan 22, 2014 10:18 AM, "Craig Vyvial" wrote:
> Hey everyone I have run into an issue with
Hey everyone I have run into an issue with the configuration parameter URI.
I'd like some input on what the URI might look like for getting the list
configuration parameters for a specific datastore.
Problem: Configuration parameters need to be selected per datastore.
Currently: Its setup to use
18 matches
Mail list logo
