← Back to team overview

openstack team mailing list archive

Re: Architecture for Shared Components


My bad, wondering about the concept in general?  ... having a python based config script, that glues the chain together.

-jOrGe W.

On Aug 4, 2010, at 4:01 PM, Michael Gundlach wrote:

Sorry, the "will this work" confused me.  I thought you were asking if we could reuse Chromium's specific scripts in this project. - Michael

On Wed, Aug 4, 2010 at 3:41 PM, Jorge Williams <jorge.williams@xxxxxxxxxxxxx<mailto:jorge.williams@xxxxxxxxxxxxx>> wrote:

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.