On Fri, Jun 13, 2014 at 3:27 AM, Jamie Lennox
wrote:
>
> > And as we're going to have to live with this for a while, I'd rather use
> > the more clear version of this in keystone instead of the Heat stanzas.
>
> Anyone else have an opinion on this?
>
I like keeping sections' names simple and cle
On Wed, 2014-06-11 at 19:52 -0400, Sean Dague wrote:
> On 06/11/2014 07:47 PM, Jamie Lennox wrote:
> > On Thu, 2014-06-12 at 09:13 +1200, Steve Baker wrote:
> >> On 12/06/14 08:18, Mark McLoughlin wrote:
> >>> On Wed, 2014-06-11 at 16:57 +1200, Steve Baker wrote:
> On 11/06/14 15:07, Jamie Len
On 2014-06-12, 7:18 AM, Sean Dague wrote:
On 06/11/2014 08:12 PM, Mathieu Gagné wrote:
On 2014-06-11, 7:52 PM, Sean Dague wrote:
I'm concerned about the [nova] section being (one day) overloaded with
options unrelated to the actual nova client configuration. Although my
concern could be wrong.
On 06/11/2014 08:12 PM, Mathieu Gagné wrote:
> On 2014-06-11, 7:52 PM, Sean Dague wrote:
>>
>> Honestly, I really like
>>
>> [nova]
>>
>> better than
>>
>> [clients_nova]
>>
>> And as we're going to have to live with this for a while, I'd rather use
>> the more clear version of this in keystone ins
On 2014-06-11, 7:52 PM, Sean Dague wrote:
Honestly, I really like
[nova]
better than
[clients_nova]
And as we're going to have to live with this for a while, I'd rather use
the more clear version of this in keystone instead of the Heat stanzas.
What about [novaclient] or [nova_client] ?
On Wed, 2014-06-11 at 04:43 +, Angus Salkeld wrote:
> On 11/06/14 13:10, Jamie Lennox wrote:
> > Among the problems cause by the inconsistencies in the clients is that
> > all the options that are required to create a client need to go into the
> > config file of the service. This is a pain to
On 06/11/2014 07:47 PM, Jamie Lennox wrote:
> On Thu, 2014-06-12 at 09:13 +1200, Steve Baker wrote:
>> On 12/06/14 08:18, Mark McLoughlin wrote:
>>> On Wed, 2014-06-11 at 16:57 +1200, Steve Baker wrote:
On 11/06/14 15:07, Jamie Lennox wrote:
> Among the problems cause by the inconsistencie
On Thu, 2014-06-12 at 09:13 +1200, Steve Baker wrote:
> On 12/06/14 08:18, Mark McLoughlin wrote:
> > On Wed, 2014-06-11 at 16:57 +1200, Steve Baker wrote:
> >> On 11/06/14 15:07, Jamie Lennox wrote:
> >>> Among the problems cause by the inconsistencies in the clients is that
> >>> all the options
On 12/06/14 08:18, Mark McLoughlin wrote:
> On Wed, 2014-06-11 at 16:57 +1200, Steve Baker wrote:
>> On 11/06/14 15:07, Jamie Lennox wrote:
>>> Among the problems cause by the inconsistencies in the clients is that
>>> all the options that are required to create a client need to go into the
>>> con
On Wed, 2014-06-11 at 16:57 +1200, Steve Baker wrote:
> On 11/06/14 15:07, Jamie Lennox wrote:
> > Among the problems cause by the inconsistencies in the clients is that
> > all the options that are required to create a client need to go into the
> > config file of the service. This is a pain to co
On 11/06/14 15:07, Jamie Lennox wrote:
> Among the problems cause by the inconsistencies in the clients is that
> all the options that are required to create a client need to go into the
> config file of the service. This is a pain to configure from the server
> side and can result in missing optio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/06/14 13:10, Jamie Lennox wrote:
> Among the problems cause by the inconsistencies in the clients is that
> all the options that are required to create a client need to go into the
> config file of the service. This is a pain to configure from th
Among the problems cause by the inconsistencies in the clients is that
all the options that are required to create a client need to go into the
config file of the service. This is a pain to configure from the server
side and can result in missing options as servers fail to keep up.
With the sessio
13 matches
Mail list logo
