You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by "seba.wagner@gmail.com" <se...@gmail.com> on 2013/09/25 08:40:26 UTC
[DRAFT] Spec for OpenMeetings Demo Server
We have to agree on some kind of hardware spec for the a potential
OpenMeetings Demo server.
See the "Goals" section of that spec:
We really don't want to make a commercial/end user offering with that demo
server. The server should be a primary functional reference, that tells us
how the application works, to run automated test and to improve the quality
of the product.
That might include opening it up for volunteers to test, but usage should
stay inside reasonable boundaries.
I would propose the following specification / letter for Infra team:
---------
Goals of the demo server:
The goal of the demo server is to have a functional reference where
developers and testers can run verification tests of OpenMeetings
functionality.
Those tests might happen manually or automated with tools like Selenium.
Hardware requirements:
2-4 vcpus
4-8 GB RAM max
100GB disk
reasonable use of bandwidth
Software requirements:
Any linux distro (preferred is Ubuntu, Debian)
Root access, OpenMeetings has a number of software requirements that the
OpenMeetings PMC can install on their own (see:
http://openmeetings.apache.org/installation.html)
Estimated load:
An average daily peak of 10-20, on a quartly year peak there might be up to
50 concurrent user sessions.
---------
If you agree to this agenda please vote or otherwise comment.
If we have some kind of consens we will forward that to @infra
Thanks,
Sebastian
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: [DRAFT] Spec for OpenMeetings Demo Server
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I will forward the spec now to the Apache Infra team.
Thanks for all the votes and comments
Sebastian
2013/9/26 seba.wagner@gmail.com <se...@gmail.com>
> Hallo Joseph,
>
> we basically apply for a single server sponsored by the Apache Software
> Foundation. That is what this spec is good for.
>
> There will be no second or third server instance at this stage. However we
> might install multiple instances of the OpenMeetings webapp into a single
> Tomcat server. We actually don't need to have 3 physical servers to run 3
> different versions.
>
> Sebastian
>
>
>
>
>
> 2013/9/26 Joseph Karwat <jk...@jellnet.com>
>
>> My thinking is that you need 3 identical servers (or equivalent cloud
>> based
>> virtual servers) as follows:
>>
>> 1) Current official release. That way if a bug crops up in a dev release
>> one can test to see if it's a function of the new code. Also, bug fixes
>> to
>> the official release can be tested here. In today's terms this would be
>> running 2.0 or perhaps 2.1
>>
>> 2) Next official release candidate. This would represent 2.1.1 or 2.2 in
>> today's environment.
>>
>> 3) Future release candidate. OM3.x in today's terms.
>>
>> For this to work well there would also have to be a commitment to make
>> sure
>> that before the group endorses a release as the official current release,
>> there is an easy to use method (see how WordPress does it) to upgrade both
>> the software and the user database) to the next release.
>>
>> I'm not sure how we would pay for 3 cloud servers (the cost per month is
>> not
>> that significant). Perhaps we could pass the hat or find some corporate
>> sponsors.
>>
>> Also, we have been running OM on AWS using Ubuntu and it works really
>> well.
>>
>>
>>
>> Joseph Karwat |415-462-0263 | JellVideo | www.jellnet.com |
>> JELL NETWORKS, INC.
>> Enterprise Video Collaboration Solutions
>>
>> Click Here to Register for your JellVideo Collaboration Account
>>
>>
>> -----Original Message-----
>> From: Vasiliy Degtyarev [mailto:vasya@unipro.ru]
>> Sent: Wednesday, September 25, 2013 1:21 AM
>> To: dev@openmeetings.apache.org
>> Subject: Re: [DRAFT] Spec for OpenMeetings Demo Server
>>
>> +1
>>
>> On 25.09.2013 13:40, seba.wagner@gmail.com wrote:
>> > We have to agree on some kind of hardware spec for the a potential
>> > OpenMeetings Demo server.
>> >
>> > See the "Goals" section of that spec:
>> >
>> > We really don't want to make a commercial/end user offering with that
>> > demo server. The server should be a primary functional reference, that
>> > tells us how the application works, to run automated test and to
>> > improve the quality of the product.
>> >
>> > That might include opening it up for volunteers to test, but usage
>> > should stay inside reasonable boundaries.
>> >
>> > I would propose the following specification / letter for Infra team:
>> >
>> > ---------
>> >
>> > Goals of the demo server:
>> >
>> > The goal of the demo server is to have a functional reference where
>> > developers and testers can run verification tests of OpenMeetings
>> > functionality.
>> > Those tests might happen manually or automated with tools like Selenium.
>> >
>> > Hardware requirements:
>> > 2-4 vcpus
>> > 4-8 GB RAM max
>> > 100GB disk
>> > reasonable use of bandwidth
>> >
>> > Software requirements:
>> >
>> > Any linux distro (preferred is Ubuntu, Debian) Root access,
>> > OpenMeetings has a number of software requirements that the
>> > OpenMeetings PMC can install on their own (see:
>> > http://openmeetings.apache.org/installation.html)
>> >
>> > Estimated load:
>> >
>> > An average daily peak of 10-20, on a quartly year peak there might be
>> > up to
>> > 50 concurrent user sessions.
>> >
>> > ---------
>> >
>> > If you agree to this agenda please vote or otherwise comment.
>> >
>> > If we have some kind of consens we will forward that to @infra
>> >
>> > Thanks,
>> > Sebastian
>> >
>> >
>>
>>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: [DRAFT] Spec for OpenMeetings Demo Server
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Hallo Joseph,
we basically apply for a single server sponsored by the Apache Software
Foundation. That is what this spec is good for.
There will be no second or third server instance at this stage. However we
might install multiple instances of the OpenMeetings webapp into a single
Tomcat server. We actually don't need to have 3 physical servers to run 3
different versions.
Sebastian
2013/9/26 Joseph Karwat <jk...@jellnet.com>
> My thinking is that you need 3 identical servers (or equivalent cloud based
> virtual servers) as follows:
>
> 1) Current official release. That way if a bug crops up in a dev release
> one can test to see if it's a function of the new code. Also, bug fixes to
> the official release can be tested here. In today's terms this would be
> running 2.0 or perhaps 2.1
>
> 2) Next official release candidate. This would represent 2.1.1 or 2.2 in
> today's environment.
>
> 3) Future release candidate. OM3.x in today's terms.
>
> For this to work well there would also have to be a commitment to make sure
> that before the group endorses a release as the official current release,
> there is an easy to use method (see how WordPress does it) to upgrade both
> the software and the user database) to the next release.
>
> I'm not sure how we would pay for 3 cloud servers (the cost per month is
> not
> that significant). Perhaps we could pass the hat or find some corporate
> sponsors.
>
> Also, we have been running OM on AWS using Ubuntu and it works really well.
>
>
>
> Joseph Karwat |415-462-0263 | JellVideo | www.jellnet.com |
> JELL NETWORKS, INC.
> Enterprise Video Collaboration Solutions
>
> Click Here to Register for your JellVideo Collaboration Account
>
>
> -----Original Message-----
> From: Vasiliy Degtyarev [mailto:vasya@unipro.ru]
> Sent: Wednesday, September 25, 2013 1:21 AM
> To: dev@openmeetings.apache.org
> Subject: Re: [DRAFT] Spec for OpenMeetings Demo Server
>
> +1
>
> On 25.09.2013 13:40, seba.wagner@gmail.com wrote:
> > We have to agree on some kind of hardware spec for the a potential
> > OpenMeetings Demo server.
> >
> > See the "Goals" section of that spec:
> >
> > We really don't want to make a commercial/end user offering with that
> > demo server. The server should be a primary functional reference, that
> > tells us how the application works, to run automated test and to
> > improve the quality of the product.
> >
> > That might include opening it up for volunteers to test, but usage
> > should stay inside reasonable boundaries.
> >
> > I would propose the following specification / letter for Infra team:
> >
> > ---------
> >
> > Goals of the demo server:
> >
> > The goal of the demo server is to have a functional reference where
> > developers and testers can run verification tests of OpenMeetings
> > functionality.
> > Those tests might happen manually or automated with tools like Selenium.
> >
> > Hardware requirements:
> > 2-4 vcpus
> > 4-8 GB RAM max
> > 100GB disk
> > reasonable use of bandwidth
> >
> > Software requirements:
> >
> > Any linux distro (preferred is Ubuntu, Debian) Root access,
> > OpenMeetings has a number of software requirements that the
> > OpenMeetings PMC can install on their own (see:
> > http://openmeetings.apache.org/installation.html)
> >
> > Estimated load:
> >
> > An average daily peak of 10-20, on a quartly year peak there might be
> > up to
> > 50 concurrent user sessions.
> >
> > ---------
> >
> > If you agree to this agenda please vote or otherwise comment.
> >
> > If we have some kind of consens we will forward that to @infra
> >
> > Thanks,
> > Sebastian
> >
> >
>
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
RE: [DRAFT] Spec for OpenMeetings Demo Server
Posted by Joseph Karwat <jk...@jellnet.com>.
My thinking is that you need 3 identical servers (or equivalent cloud based
virtual servers) as follows:
1) Current official release. That way if a bug crops up in a dev release
one can test to see if it's a function of the new code. Also, bug fixes to
the official release can be tested here. In today's terms this would be
running 2.0 or perhaps 2.1
2) Next official release candidate. This would represent 2.1.1 or 2.2 in
today's environment.
3) Future release candidate. OM3.x in today's terms.
For this to work well there would also have to be a commitment to make sure
that before the group endorses a release as the official current release,
there is an easy to use method (see how WordPress does it) to upgrade both
the software and the user database) to the next release.
I'm not sure how we would pay for 3 cloud servers (the cost per month is not
that significant). Perhaps we could pass the hat or find some corporate
sponsors.
Also, we have been running OM on AWS using Ubuntu and it works really well.
Joseph Karwat |415-462-0263 | JellVideo | www.jellnet.com |
JELL NETWORKS, INC.
Enterprise Video Collaboration Solutions
Click Here to Register for your JellVideo Collaboration Account
-----Original Message-----
From: Vasiliy Degtyarev [mailto:vasya@unipro.ru]
Sent: Wednesday, September 25, 2013 1:21 AM
To: dev@openmeetings.apache.org
Subject: Re: [DRAFT] Spec for OpenMeetings Demo Server
+1
On 25.09.2013 13:40, seba.wagner@gmail.com wrote:
> We have to agree on some kind of hardware spec for the a potential
> OpenMeetings Demo server.
>
> See the "Goals" section of that spec:
>
> We really don't want to make a commercial/end user offering with that
> demo server. The server should be a primary functional reference, that
> tells us how the application works, to run automated test and to
> improve the quality of the product.
>
> That might include opening it up for volunteers to test, but usage
> should stay inside reasonable boundaries.
>
> I would propose the following specification / letter for Infra team:
>
> ---------
>
> Goals of the demo server:
>
> The goal of the demo server is to have a functional reference where
> developers and testers can run verification tests of OpenMeetings
> functionality.
> Those tests might happen manually or automated with tools like Selenium.
>
> Hardware requirements:
> 2-4 vcpus
> 4-8 GB RAM max
> 100GB disk
> reasonable use of bandwidth
>
> Software requirements:
>
> Any linux distro (preferred is Ubuntu, Debian) Root access,
> OpenMeetings has a number of software requirements that the
> OpenMeetings PMC can install on their own (see:
> http://openmeetings.apache.org/installation.html)
>
> Estimated load:
>
> An average daily peak of 10-20, on a quartly year peak there might be
> up to
> 50 concurrent user sessions.
>
> ---------
>
> If you agree to this agenda please vote or otherwise comment.
>
> If we have some kind of consens we will forward that to @infra
>
> Thanks,
> Sebastian
>
>
Re: [DRAFT] Spec for OpenMeetings Demo Server
Posted by Vasiliy Degtyarev <va...@unipro.ru>.
+1
On 25.09.2013 13:40, seba.wagner@gmail.com wrote:
> We have to agree on some kind of hardware spec for the a potential
> OpenMeetings Demo server.
>
> See the "Goals" section of that spec:
>
> We really don't want to make a commercial/end user offering with that demo
> server. The server should be a primary functional reference, that tells us
> how the application works, to run automated test and to improve the quality
> of the product.
>
> That might include opening it up for volunteers to test, but usage should
> stay inside reasonable boundaries.
>
> I would propose the following specification / letter for Infra team:
>
> ---------
>
> Goals of the demo server:
>
> The goal of the demo server is to have a functional reference where
> developers and testers can run verification tests of OpenMeetings
> functionality.
> Those tests might happen manually or automated with tools like Selenium.
>
> Hardware requirements:
> 2-4 vcpus
> 4-8 GB RAM max
> 100GB disk
> reasonable use of bandwidth
>
> Software requirements:
>
> Any linux distro (preferred is Ubuntu, Debian)
> Root access, OpenMeetings has a number of software requirements that the
> OpenMeetings PMC can install on their own (see:
> http://openmeetings.apache.org/installation.html)
>
> Estimated load:
>
> An average daily peak of 10-20, on a quartly year peak there might be up to
> 50 concurrent user sessions.
>
> ---------
>
> If you agree to this agenda please vote or otherwise comment.
>
> If we have some kind of consens we will forward that to @infra
>
> Thanks,
> Sebastian
>
>
Re: [DRAFT] Spec for OpenMeetings Demo Server
Posted by Maxim Solodovnik <so...@gmail.com>.
+1
On Wed, Sep 25, 2013 at 1:40 PM, seba.wagner@gmail.com <
seba.wagner@gmail.com> wrote:
> We have to agree on some kind of hardware spec for the a potential
> OpenMeetings Demo server.
>
> See the "Goals" section of that spec:
>
> We really don't want to make a commercial/end user offering with that demo
> server. The server should be a primary functional reference, that tells us
> how the application works, to run automated test and to improve the quality
> of the product.
>
> That might include opening it up for volunteers to test, but usage should
> stay inside reasonable boundaries.
>
> I would propose the following specification / letter for Infra team:
>
> ---------
>
> Goals of the demo server:
>
> The goal of the demo server is to have a functional reference where
> developers and testers can run verification tests of OpenMeetings
> functionality.
> Those tests might happen manually or automated with tools like Selenium.
>
> Hardware requirements:
> 2-4 vcpus
> 4-8 GB RAM max
> 100GB disk
> reasonable use of bandwidth
>
> Software requirements:
>
> Any linux distro (preferred is Ubuntu, Debian)
> Root access, OpenMeetings has a number of software requirements that the
> OpenMeetings PMC can install on their own (see:
> http://openmeetings.apache.org/installation.html)
>
> Estimated load:
>
> An average daily peak of 10-20, on a quartly year peak there might be up to
> 50 concurrent user sessions.
>
> ---------
>
> If you agree to this agenda please vote or otherwise comment.
>
> If we have some kind of consens we will forward that to @infra
>
> Thanks,
> Sebastian
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
--
WBR
Maxim aka solomax
Re: [DRAFT] Spec for OpenMeetings Demo Server
Posted by Irina Arkhipets <ir...@gmail.com>.
+1
Regards,
Irina
On Wed, Sep 25, 2013 at 1:40 PM, seba.wagner@gmail.com <
seba.wagner@gmail.com> wrote:
> We have to agree on some kind of hardware spec for the a potential
> OpenMeetings Demo server.
>
> See the "Goals" section of that spec:
>
> We really don't want to make a commercial/end user offering with that demo
> server. The server should be a primary functional reference, that tells us
> how the application works, to run automated test and to improve the quality
> of the product.
>
> That might include opening it up for volunteers to test, but usage should
> stay inside reasonable boundaries.
>
> I would propose the following specification / letter for Infra team:
>
> ---------
>
> Goals of the demo server:
>
> The goal of the demo server is to have a functional reference where
> developers and testers can run verification tests of OpenMeetings
> functionality.
> Those tests might happen manually or automated with tools like Selenium.
>
> Hardware requirements:
> 2-4 vcpus
> 4-8 GB RAM max
> 100GB disk
> reasonable use of bandwidth
>
> Software requirements:
>
> Any linux distro (preferred is Ubuntu, Debian)
> Root access, OpenMeetings has a number of software requirements that the
> OpenMeetings PMC can install on their own (see:
> http://openmeetings.apache.org/installation.html)
>
> Estimated load:
>
> An average daily peak of 10-20, on a quartly year peak there might be up to
> 50 concurrent user sessions.
>
> ---------
>
> If you agree to this agenda please vote or otherwise comment.
>
> If we have some kind of consens we will forward that to @infra
>
> Thanks,
> Sebastian
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>