openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #00026
Re: Architecture for Shared Components
On Aug 4, 2010, at 1:05 PM, Michael Gundlach wrote:
On Wed, Aug 4, 2010 at 12:08 PM, Jorge Williams <jorge.williams@xxxxxxxxxxxxx<mailto:jorge.williams@xxxxxxxxxxxxx>> wrote:
You executed the configurations script to start the application. The app came bundled with a whole bunch of scripts that people could customize. There was a network protocol involved in transmitting configuration options to other nodes. Will this work?
I'm not very strong on deployment, so I probably can't answer well. It seems odd to be coming up with a specific protocol for transmitting config options around... deployment tools like Fabric might be simpler, where a Nova user just sets some options in a Fabric config file (for each wsgi layer, should it be independent or glommed onto its neighbor?) and says "fab deploy" from then on out.
I'm not suggesting we develop a specific protocol for this, I was describing Chromium.
-jOrGe W.
Follow ups
References
-
Architecture for Shared Components
From: Eric Day, 2010-07-30
-
Re: Architecture for Shared Components
From: Michael Gundlach, 2010-07-30
-
Re: Architecture for Shared Components
From: Jorge Williams, 2010-07-31
-
Re: Architecture for Shared Components
From: Michael Gundlach, 2010-08-02
-
Re: Architecture for Shared Components
From: Jorge Williams, 2010-08-02
-
Re: Architecture for Shared Components
From: Eric Day, 2010-08-02
-
Re: Architecture for Shared Components
From: Michael Gundlach, 2010-08-03
-
Re: Architecture for Shared Components
From: Jorge Williams, 2010-08-03
-
Re: Architecture for Shared Components
From: Eric Day, 2010-08-03
-
Re: Architecture for Shared Components
From: Jorge Williams, 2010-08-04
-
Re: Architecture for Shared Components
From: Michael Gundlach, 2010-08-04
-
Re: Architecture for Shared Components
From: Jorge Williams, 2010-08-04
-
Re: Architecture for Shared Components
From: Michael Gundlach, 2010-08-04