[jitsi-dev] Multiple Instances of Jibri


#1

Hi All,

We are currently running Jitsi and Jibri instances on AWS. As for now we
can only record a single room at a time. Is there any documented guide to
configure multiple Jibri Instances with jitsi ?

···

--
Buddhika Jayawardhana
Principle Engineer | Meetrix.IO


#2

Hi,

You just need to deploy multiple jibri instances, and as they are
entering a room and jicofo will see multiple instances there will use
the next available one.

Regards
damencho

···

On Wed, Dec 13, 2017 at 7:24 PM, Buddhika Jayawardhana <jay@meetrix.io> wrote:

Hi All,

We are currently running Jitsi and Jibri instances on AWS. As for now we can
only record a single room at a time. Is there any documented guide to
configure multiple Jibri Instances with jitsi ?

--
Buddhika Jayawardhana
Principle Engineer | Meetrix.IO

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

But we have to defined a specific room name in jibri and jicofo
configurations, this makes jibri available only for one room. Any guide to
making jibri pool available for all the rooms ?

···

On Fri, Dec 15, 2017 at 3:16 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

You just need to deploy multiple jibri instances, and as they are
entering a room and jicofo will see multiple instances there will use
the next available one.

Regards
damencho

On Wed, Dec 13, 2017 at 7:24 PM, Buddhika Jayawardhana <jay@meetrix.io> > wrote:
> Hi All,
>
> We are currently running Jitsi and Jibri instances on AWS. As for now we
can
> only record a single room at a time. Is there any documented guide to
> configure multiple Jibri Instances with jitsi ?
>
> --
> Buddhika Jayawardhana
> Principle Engineer | Meetrix.IO
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
*Buddhika Jayawardhana*
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#4

Damian,

Can you share the configuration of the jibri instance meet.jit.si is using.
CPU, RAM, bandwidth. Are you able to use autoscaler with jibri?

···

On December 14, 2017 at 2:20 PM Damian Minkov <damencho@jitsi.org> wrote:

No, the room name you supply to jicofo and jibri is the same on all
jibri instances you will deploy. This is a control room(brewery) where
all jibris connect and advertise their availability so jicofo can use
the available(not recording at the moment) ones and use them for new
jibri requests.

On Thu, Dec 14, 2017 at 4:10 PM, Buddhika Jayawardhana > <buddhika.anushka@gmail.com> wrote:
> But we have to defined a specific room name in jibri and jicofo
> configurations, this makes jibri available only for one room. Any guide to
> making jibri pool available for all the rooms ?
>
> On Fri, Dec 15, 2017 at 3:16 AM, Damian Minkov <damencho@jitsi.org> wrote:
>>
>> Hi,
>>
>> You just need to deploy multiple jibri instances, and as they are
>> entering a room and jicofo will see multiple instances there will use
>> the next available one.
>>
>> Regards
>> damencho
>>
>>
>> On Wed, Dec 13, 2017 at 7:24 PM, Buddhika Jayawardhana <jay@meetrix.io> > >> wrote:
>> > Hi All,
>> >
>> > We are currently running Jitsi and Jibri instances on AWS. As for now we
>> > can
>> > only record a single room at a time. Is there any documented guide to
>> > configure multiple Jibri Instances with jitsi ?
>> >
>> > --
>> > Buddhika Jayawardhana
>> > Principle Engineer | Meetrix.IO
>> >
>> > _______________________________________________
>> > dev mailing list
>> > dev@jitsi.org
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/dev
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
>
>
>
> --
> Buddhika Jayawardhana
> buddhika.anushka@gmail.com | LinkedIn
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

No, the room name you supply to jicofo and jibri is the same on all
jibri instances you will deploy. This is a control room(brewery) where
all jibris connect and advertise their availability so jicofo can use
the available(not recording at the moment) ones and use them for new
jibri requests.

···

On Thu, Dec 14, 2017 at 4:10 PM, Buddhika Jayawardhana <buddhika.anushka@gmail.com> wrote:

But we have to defined a specific room name in jibri and jicofo
configurations, this makes jibri available only for one room. Any guide to
making jibri pool available for all the rooms ?

On Fri, Dec 15, 2017 at 3:16 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

You just need to deploy multiple jibri instances, and as they are
entering a room and jicofo will see multiple instances there will use
the next available one.

Regards
damencho

On Wed, Dec 13, 2017 at 7:24 PM, Buddhika Jayawardhana <jay@meetrix.io> >> wrote:
> Hi All,
>
> We are currently running Jitsi and Jibri instances on AWS. As for now we
> can
> only record a single room at a time. Is there any documented guide to
> configure multiple Jibri Instances with jitsi ?
>
> --
> Buddhika Jayawardhana
> Principle Engineer | Meetrix.IO
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Buddhika Jayawardhana
buddhika.anushka@gmail.com | LinkedIn

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#6

Hey Aaron,

can you step in and give more details here.

Thanks

···

On Thu, Dec 14, 2017 at 5:37 PM, Roy Blogger <royblog@comcast.net> wrote:

Damian,

Can you share the configuration of the jibri instance meet.jit.si is using.
CPU, RAM, bandwidth. Are you able to use autoscaler with jibri?

On December 14, 2017 at 2:20 PM Damian Minkov <damencho@jitsi.org> wrote:

No, the room name you supply to jicofo and jibri is the same on all
jibri instances you will deploy. This is a control room(brewery) where
all jibris connect and advertise their availability so jicofo can use
the available(not recording at the moment) ones and use them for new
jibri requests.

On Thu, Dec 14, 2017 at 4:10 PM, Buddhika Jayawardhana >> <buddhika.anushka@gmail.com> wrote:
> But we have to defined a specific room name in jibri and jicofo
> configurations, this makes jibri available only for one room. Any guide to
> making jibri pool available for all the rooms ?
>
> On Fri, Dec 15, 2017 at 3:16 AM, Damian Minkov <damencho@jitsi.org> wrote:
>>
>> Hi,
>>
>> You just need to deploy multiple jibri instances, and as they are
>> entering a room and jicofo will see multiple instances there will use
>> the next available one.
>>
>> Regards
>> damencho
>>
>>
>> On Wed, Dec 13, 2017 at 7:24 PM, Buddhika Jayawardhana <jay@meetrix.io> >> >> wrote:
>> > Hi All,
>> >
>> > We are currently running Jitsi and Jibri instances on AWS. As for now we
>> > can
>> > only record a single room at a time. Is there any documented guide to
>> > configure multiple Jibri Instances with jitsi ?
>> >
>> > --
>> > Buddhika Jayawardhana
>> > Principle Engineer | Meetrix.IO
>> >
>> > _______________________________________________
>> > dev mailing list
>> > dev@jitsi.org
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/dev
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
>
>
>
> --
> Buddhika Jayawardhana
> buddhika.anushka@gmail.com | LinkedIn
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#7

Thanks Damian

···

On Fri, Dec 15, 2017 at 5:10 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hey Aaron,

can you step in and give more details here.

Thanks

On Thu, Dec 14, 2017 at 5:37 PM, Roy Blogger <royblog@comcast.net> wrote:
> Damian,
>
> Can you share the configuration of the jibri instance meet.jit.si is
using.
> CPU, RAM, bandwidth. Are you able to use autoscaler with jibri?
>
>
>
>> On December 14, 2017 at 2:20 PM Damian Minkov <damencho@jitsi.org> > wrote:
>>
>>
>> No, the room name you supply to jicofo and jibri is the same on all
>> jibri instances you will deploy. This is a control room(brewery) where
>> all jibris connect and advertise their availability so jicofo can use
>> the available(not recording at the moment) ones and use them for new
>> jibri requests.
>>
>> On Thu, Dec 14, 2017 at 4:10 PM, Buddhika Jayawardhana > >> <buddhika.anushka@gmail.com> wrote:
>> > But we have to defined a specific room name in jibri and jicofo
>> > configurations, this makes jibri available only for one room. Any
guide to
>> > making jibri pool available for all the rooms ?
>> >
>> > On Fri, Dec 15, 2017 at 3:16 AM, Damian Minkov <damencho@jitsi.org> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> You just need to deploy multiple jibri instances, and as they are
>> >> entering a room and jicofo will see multiple instances there will use
>> >> the next available one.
>> >>
>> >> Regards
>> >> damencho
>> >>
>> >>
>> >> On Wed, Dec 13, 2017 at 7:24 PM, Buddhika Jayawardhana < > jay@meetrix.io> > >> >> wrote:
>> >> > Hi All,
>> >> >
>> >> > We are currently running Jitsi and Jibri instances on AWS. As for
now we
>> >> > can
>> >> > only record a single room at a time. Is there any documented guide
to
>> >> > configure multiple Jibri Instances with jitsi ?
>> >> >
>> >> > --
>> >> > Buddhika Jayawardhana
>> >> > Principle Engineer | Meetrix.IO
>> >> >
>> >> > _______________________________________________
>> >> > dev mailing list
>> >> > dev@jitsi.org
>> >> > Unsubscribe instructions and other list options:
>> >> > http://lists.jitsi.org/mailman/listinfo/dev
>> >>
>> >> _______________________________________________
>> >> dev mailing list
>> >> dev@jitsi.org
>> >> Unsubscribe instructions and other list options:
>> >> http://lists.jitsi.org/mailman/listinfo/dev
>> >
>> >
>> >
>> >
>> > --
>> > Buddhika Jayawardhana
>> > buddhika.anushka@gmail.com | LinkedIn
>> >
>> > _______________________________________________
>> > dev mailing list
>> > dev@jitsi.org
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/dev
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
*Buddhika Jayawardhana*
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>