From: Richard Hanley <rhanley@google.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: Patrick Williams <patrick@stwcx.xyz>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: corosync?
Date: Thu, 26 Mar 2020 17:37:20 -0700 [thread overview]
Message-ID: <CAH1kD+Yw2AcigiDcxpUfHB_M7C3u2s8RdqG3dbyHwuJXyS0gng@mail.gmail.com> (raw)
In-Reply-To: <318AF56E-3DC0-4B3E-9B41-E49C51A1F3B3@fuzziesquirrel.com>
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
We looked into getting Envoy as a proxy for a distributed BMC network. The
idea was that Envoy could be used for discoverability and creating long
lived authenticated channels with HTTP/2. That work got mostly shelved
because it was really hard to get the build system to work on 32-bit arm
(not to mention getting it to work with bitbake).
I'm not too familiar with corosync. I remember reading a bit about it when
Vishwa mentioned aggregating BMCs a few months ago. It looks like it
should be relatively easy to build (at least compared to envoy).
Unfortunately we never got a chance to see how much cpu usage is used when
Envoy is run on a Poleg. In terms of sheer craziness, corosync isn't any
less crazy than what we were thinking about, and I was relatively
optimistic that it could work on current generation hardware.
- Richard
On Tue, Mar 24, 2020 at 9:22 AM Brad Bishop <bradleyb@fuzziesquirrel.com>
wrote:
> at 12:06 PM, Patrick Williams <patrick@stwcx.xyz> wrote:
>
> > On Tue, Mar 24, 2020 at 11:33:23AM -0400, Brad Bishop wrote:
> >> Is anyone using corosync/pacemaker on a BMC? Is that a crazy idea? :-)
> >>
> >> thx - brad
> >
> > Can you elaborate on what you'd be trying to accomplish?
>
> Thanks Patrick. Yes I will definitely do that at some point. I’m not
> ready to do this right now though simply because I myself am not sure
> what
> I am trying to accomplish.
>
> In this moment I’m just curious if anyone has any experience with it, or
> similar tools or frameworks, in a "BMC-like" distributed system, and the
> sorts of problems that were solved with it/them.
>
> thx - brad
>
[-- Attachment #2: Type: text/html, Size: 2182 bytes --]
next prev parent reply other threads:[~2020-03-27 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 15:33 corosync? Brad Bishop
2020-03-24 16:06 ` corosync? Patrick Williams
2020-03-24 16:20 ` corosync? Brad Bishop
2020-03-27 0:37 ` Richard Hanley [this message]
2020-03-30 16:25 ` corosync? Brad Bishop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH1kD+Yw2AcigiDcxpUfHB_M7C3u2s8RdqG3dbyHwuJXyS0gng@mail.gmail.com \
--to=rhanley@google.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.