<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<blockquote type="cite"
cite="mid:CAEnL8_cJvmDrVGiYso=Sb8KX+5hLXaHuJV1uF+AKqbNFSwivGw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>I'm happy to set up a Jitsi server on AWS temporarily. I've
got plenty of credits to burn, so I'm not super concerned with
cost.<br>
</div>
</div>
</blockquote>
<p>If we want to have a convenient emergency option 😉, then I'd
prefer BBB for its constant recording with an option to fix events
and replay event at your leisure for video editing. I don't know
about recording in Jitsi. So if we do it in ten minutes, the
protocol would be, someone records an event from their own screen
(OBS) keeping scene setup in real time. Hence, BBB.</p>
<p>And then we just want to have a protocol/procedure spelled out.
Something along the following lines:</p>
1. bring fresh vm up with proper cpu, memory and disk,
<p>2. note IP of vm.</p>
<p>3. setup DNS of webconference.kwlug.org A record (Paul, can we
have a short TTL on it?). Or for less seamless experience, set
other domain name, that should be communicated.<br>
</p>
<p>4. run BBB setup with BBB's own very nice script. It will ask for
domain.</p>
<p>5. setup BBB admin account, and a room. (May be this can be in a
script, but script may get stale with newer BBB version.) Inject
KWLUG branding 🙂.</p>
<p>6. check experience as a participant, coming from another private
browser frame</p>
<p>7. have an event, recording it</p>
<p>8. leisurely play back, recording streams for editing</p>
<p>9. kill vm, closing associated accounting, if any.</p>
<p><br>
</p>
<p>I'd be lovely to have a dormant system with just an on/off
procedure. But, at least LE's certificate should be updated ever
so often, making long lying vm image in need of LE TLC before
usage. Then, we may not want to store in a cloud a few gigs that
may never be used.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAEnL8_cJvmDrVGiYso=Sb8KX+5hLXaHuJV1uF+AKqbNFSwivGw@mail.gmail.com">
<div dir="ltr">
<div>If we're OK with hosting it in the cloud, it would be
easier from a bandwidth constraint situation.<br>
<br>
</div>
<div>@Mark if you have any recommendations or guides on setting
up the server, that would be appreciated. I'm looking into
how I can configure it now.<br>
<br>
Cheers,<br>
Jason</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Oct 3, 2024 at 3:16 PM
Mark Steffen <<a href="mailto:mark@steffen.ca"
moz-do-not-send="true" class="moz-txt-link-freetext">mark@steffen.ca</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I
have a Jitsi server, happy to volunteer it for a backup if
needed, <br>
assuming the bandwidth requirements are a fit.<br>
<br>
How much bandwidth do you think that would use symmetrically?Â
I only <br>
have symmterical gigabit presently, so I wouldn't want it to
use more <br>
than about 500mbps to leave room for other things.<br>
<br>
Would also need to load test, it was mainly used for family
"gatherings" <br>
during covid, maybe 10-12 connections tops.<br>
<br>
Mark<br>
<br>
On 2024-10-03 3:05 p.m., Mikalai Birukou via kwlug-disc wrote:<br>
>> As of now (and since Oct 1) it looks like our
BigBlueButton server has<br>
>> been inaccessible, because Datacity is having an
internet outage at<br>
>> its datacentre. (I cannot imagine its paying
customers are very happy<br>
>> right now.)<br>
> I suspect most of their customers have moved to their
Waterloo location<br>
> with two different fibers to Front Street. I will 😳.<br>
><br>
> I don't think we should expect another truck accident
near Roger fibers<br>
> this coming Monday. We have already witnessed once in a
blue moon streak<br>
> of fiber cuts. I am hopeful, cause this isn't Texas 🙂.
Fiber cut has<br>
> been fixed. And yes, it took Rogers 24 hours.<br>
><br>
>> I imagine this will be fixed by Monday. If not: does
anybody have<br>
>> access to a different videoconferencing solution we
could use for<br>
>> Monday? It should be able to support 15-20
participants. Open source<br>
>> (BBB, Jitsi, ???) is ideologically nicer, but a
proprietary service<br>
>> might work in the worst case. We would have to test
such a setup<br>
>> Friday or Saturday.<br>
> For this kind of backup, let's note that we have 15-20
non-video-cam<br>
> participant, with only two presenting streams. This
should instruct a<br>
> required bandwidth.<br>
><br>
> I wonder, if this can be some kind of vm, rolled out in
case of emergency.<br>
><br>
> We can put BBB and greenlight behind existing haproxy
(using an almost<br>
> copy paste of BBB's own haproxy settings). If there is
possibility in<br>
> case of emergency to spawn up and down vm where <a
href="http://kwlug.org" rel="noreferrer" target="_blank"
moz-do-not-send="true">kwlug.org</a> is located,<br>
> then in an emergency colocated vm process can be started.<br>
><br>
>> My understanding is that <a
href="http://meet.jit.si" rel="noreferrer" target="_blank"
moz-do-not-send="true">meet.jit.si</a> has limitations now?<br>
>><br>
>> I don't like opening this can of worms but it is
important to me that<br>
>> we maintain good accessibility for people who prefer
to participate<br>
>> online.<br>
>><br>
>> - Paul<br>
>><br>
>> _______________________________________________<br>
>> kwlug-disc mailing list<br>
>> To unsubscribe, send an email to <a
href="mailto:kwlug-disc-leave@kwlug.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">kwlug-disc-leave@kwlug.org</a><br>
>> with the subject "unsubscribe", or email<br>
>> <a href="mailto:kwlug-disc-owner@kwlug.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">kwlug-disc-owner@kwlug.org</a>
to contact a human being.<br>
><br>
> _______________________________________________<br>
> kwlug-disc mailing list<br>
> To unsubscribe, send an email to <a
href="mailto:kwlug-disc-leave@kwlug.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">kwlug-disc-leave@kwlug.org</a><br>
> with the subject "unsubscribe", or email<br>
> <a href="mailto:kwlug-disc-owner@kwlug.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">kwlug-disc-owner@kwlug.org</a>
to contact a human being.<br>
<br>
_______________________________________________<br>
kwlug-disc mailing list<br>
To unsubscribe, send an email to <a
href="mailto:kwlug-disc-leave@kwlug.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">kwlug-disc-leave@kwlug.org</a><br>
with the subject "unsubscribe", or email<br>
<a href="mailto:kwlug-disc-owner@kwlug.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">kwlug-disc-owner@kwlug.org</a>
to contact a human being.<br>
</blockquote>
</div>
</blockquote>
</body>
</html>