From: "Frank Ch. Eigler" <fche@redhat.com>
To: cti-tac@lists.linuxfoundation.org
Subject: Re: CTI TAC Meeting Notes 2024-06-26
Date: Thu, 27 Jun 2024 10:25:32 -0400 [thread overview]
Message-ID: <20240627142532.GA2948@redhat.com> (raw)
In-Reply-To: <a1e31779-b3c3-4016-ae69-27aced5971e9@redhat.com>
Hi -
> [...] Routing issues to the colo.
> * David: The SLA is within the LF, with the OpenSSF funding, and the OpenSSF saying this is important from a security perspective.
> * Bennett: We have redundancy and is that something we want to publish?
> * Konstantin: We do mention that already. We can also put in the design of the platform. Automatic failover.
> * Carlos: Yes please.
> * Konstantin: OK, I'll put it into the part.
> [...]
Given that the routing issues mentioned were upstream of the
colocation facility itself, effective improvements in failover would
have to work in a cross-colo way. Is the intent to have
failover-capable servers in multiple colo facilities?
- FChE
next prev parent reply other threads:[~2024-06-27 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 16:01 CTI TAC Meeting Notes 2024-06-26 Carlos O'Donell
2024-06-27 14:25 ` Frank Ch. Eigler [this message]
2024-06-28 18:50 ` Carlos O'Donell
2024-06-28 22:00 ` Frank Ch. Eigler
2024-06-29 13:36 ` Carlos O'Donell
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=20240627142532.GA2948@redhat.com \
--to=fche@redhat.com \
--cc=cti-tac@lists.linuxfoundation.org \
/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.