I think it'd make more sense the other way round. If localrc does not exist, and we've created a localrc.generated create localrc with just "source localrc.generated". That way anyone using localrc directly will get the right information. A quick grep suggests that all uses in devstack source the localrc, therefore that should work?
It'd be easy to add a comment in the localrc or in the docs for local.conf that say only stack.sh will update localrc.generated so if you want live changes in other scripts you have to modify localrc? Bob From: Dean Troyer [mailto:dtro...@gmail.com] Sent: 18 September 2013 15:04 To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [DevStack] Generalize config file settings On Wed, Sep 18, 2013 at 7:49 AM, Bob Ball <bob.b...@citrix.com<mailto:bob.b...@citrix.com>> wrote: In which case, would a simple fix of adding a "localrc.generated" be sufficient? Produce a localrc which simply imports localrc.generated and replace localrc.generated in all cases - still allowing users to override it if needed? OK, how about this: - always extract localrc section from local.conf into localrc.generated (if it exists) - append localrc (if it exists) to localrc.generated This works for stack.sh, but localrc is used in a _lot_ of places, do we re-generate each time? We have to to keep the current semantics of localrc edits being effective immediately. I want to keep this as simple as possible... dt -- Dean Troyer dtro...@gmail.com<mailto:dtro...@gmail.com>
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
