Could this be a difference between gflags in ini? Maybe it's the case that you
do this with ini files:
force_dhcp_release=True
And you do this with gflags:
--force_dhcp_release
That would explain why somebody reported this as a bug, because it doesn't
work(?):
--force_dhcp_release=True
Ca
Hi, same True/False being more explicit.When this has been implemented ? The RC0 of Essex ?Razique
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com
Le 1 juin 2012 à 19:01, Anne Gentle a écrit :Thanks for the clarification - the latest review copy of the installguide has force_dhcpelease=True
I'll add it to the doc convention page.
Take care,
Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
On Jun 1, 2012, at 1:01 PM, Anne Gentle wrote:
> Thanks for the clarification - the latest review copy of the install
> guide has force_dh
Thanks for the clarification - the latest review copy of the install
guide has force_dhcpelease=True in the nova.conf file. When I tested
the nova.conf the old way, it didn't work anyway, so great catch!
Anne
On Fri, Jun 1, 2012 at 12:48 AM, Tom Fifield wrote:
> Speaking as someone who's deploye
Speaking as someone who's deployed OpenStack and had a lot of fun with
the negation, I agree with you on Format #1, especially as the 'default
value' can be made clearer.
Regards,
Tom
On 06/01/2012 02:18 AM, Lorin Hochstein wrote:
The config files (helpfully?) support two different formats f
The config files (helpfully?) support two different formats for specifying
boolean flags:
Format 1:
force_dhcpelease=True
force_dhcpelease=False
Format 2:
force_dhcpelease
noforce_dhcpelease
I think we should standardize on one of these conventions for the docs (with a
note in the docs ab
6 matches
Mail list logo
