On Wed, Jul 27, 2011 at 11:05:28AM -0400, Jason Guiditta wrote:
On Wed, 2011-07-27 at 10:43 -0400, Hugh Brock wrote:
> On Wed, Jul 27, 2011 at 10:26:08AM -0400, Jason Guiditta wrote:
> > Hello list (and Steve), I have been tasked with looking into the
> > following nebulous feature item for consideration of being included in
> > Iteration 4:
> > '* HA configuration available?'
> >
> > This is from an 'infrastructure around aeolus' perspective, if that
> > helps context at all.
> >
> > There was brief discussion of this in an extremely broad way on a recent
> > call, and given my lack of involvement with anything HA, I find myself
> > with absolutely no idea how to describe what might need doing here, let
> > alone how it might be done. I will be looking through the list archives
> > to see what has been discussed, but all the threads I recall seeing were
> > very long and detailed, and I would rather get a synopsis if someone can
> > summarize the current thinking in this area. Also, any links to specific
> > threads or documentation/designs would be much appreciated. Thanks for
> > any direction here,
>
> Sure.
>
> One of the requirements the SAs brought up is that it should be
> possible to make Conductor and its attendant pieces highly
> available. I'm not sure this is something we need to actually
> implement for release 0.4.0, but it would be nice to at least have a
> design for it by then. At a minimum we would need the entire app to be
> able to run in failover mode on two machines. We don't have to provide
> the infrastructure to deal with the failover, but the app needs to
> handle being failed over gracefully without data loss or (much)
> service interruption.
>
> Does that help at all?
>
> --Hugh
>
If that is really the gist, then yes, it is a start, thanks. Sounds
like a feature to see how to best setup rails/$backing-db to be
clustered, and possibly separate tasks to research same some some of the
other components (iwhd seems a likely candidate). However, I have this
feeling there is much more to it than that. Perhaps this task/feature
is a combination of documenting how to do some of these thing, and
writing up what what does and does not currently exist for this kind of
scenario? Also, probably something around 'what is going to be the
aeolus story for HA, and what does it mean?'.
If all we got done was that, I'd be delighted.
--H
--
== Hugh Brock, hbrock(a)redhat.com ==
== Engineering Manager, Cloud BU ==
== Aeolus Project: Manage virtual infrastructure across clouds. ==
==
http://aeolusproject.org ==
"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey