From henk at yapc.amsterdam Wed Jan 4 16:38:37 2017 From: henk at yapc.amsterdam (Henk van Oers) Date: Wed, 4 Jan 2017 16:38:37 +0100 (CET) Subject: [Act] Taking http://perlconference.amsterdam/ info production Message-ID: The Perl Conference in Amsterdam needs to go into production fase. What steps do I have to take? TIA, Henk From th.j.v.hoesel at gmail.com Wed Jan 4 17:11:44 2017 From: th.j.v.hoesel at gmail.com (Theo van Hoesel) Date: Wed, 4 Jan 2017 16:11:44 +0000 Subject: [Act] Taking http://perlconference.amsterdam/ info production In-Reply-To: References: Message-ID: <9774CA2D-4EE5-40C6-963D-1606F873548B@gmail.com> If everything is stable... you need to create a new branch 'production' and merge your changes from master into production ... that's it > On Jan 4, 2017, at 3:38 PM, Henk van Oers wrote: > > > The Perl Conference in Amsterdam needs to go into production fase. > > What steps do I have to take? > > TIA, > Henk > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act From elbeho at boivin.eu Wed Jan 4 23:26:26 2017 From: elbeho at boivin.eu (L Boivin) Date: Wed, 4 Jan 2017 23:26:26 +0100 Subject: [Act] Taking http://perlconference.amsterdam/ info production In-Reply-To: <9774CA2D-4EE5-40C6-963D-1606F873548B@gmail.com> References: <9774CA2D-4EE5-40C6-963D-1606F873548B@gmail.com> Message-ID: Hello, I merge master to production on github And run the commands to have the site live. http://perlconference.amsterdam/ (redirect to http://act.perlconference.org/tpc-2017-amsterdam/) Kind Regards Laurent On 04/01/2017 17:11, Theo van Hoesel wrote: > If everything is stable... > > you need to create a new branch 'production' and merge your changes from master into production ... that's it > >> On Jan 4, 2017, at 3:38 PM, Henk van Oers wrote: >> >> >> The Perl Conference in Amsterdam needs to go into production fase. >> >> What steps do I have to take? >> >> TIA, >> Henk >> _______________________________________________ >> Act mailing list >> Act at mongueurs.net >> http://listes.mongueurs.net/mailman/listinfo/act > > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act > -- Laurent Boivin -- mailto:elbeho at boivin.eu Member of Mongueurs de Perl -- http://www.mongueurs.net/ Member of YAPC::Europe Foundation -- http://www.yapceurope.org/ Member of OSDC.fr -- http://osdc.fr/ From henk at yapc.amsterdam Tue Jan 10 14:31:51 2017 From: henk at yapc.amsterdam (Henk van Oers) Date: Tue, 10 Jan 2017 14:31:51 +0100 (CET) Subject: [Act] [Orga] Signup, you are attending (fwd) Message-ID: Can you help me with this? TIA, Henk ---------- Forwarded message ---------- On Tue, 10 Jan 2017, Melinda Kiss wrote: > I'm not getting any email when I sign up, is that normal? No, that's not normal. Also requesting a passwordreset doesn't send a link. I'l ask the french admins. -- Henk From sebastien at aperghis.net Tue Jan 10 20:32:19 2017 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Tue, 10 Jan 2017 20:32:19 +0100 (CET) Subject: [Act] [Orga] Signup, you are attending (fwd) In-Reply-To: Message-ID: <1485472950.657185581.1484076739725.JavaMail.root@spooler3-g27.priv.proxad.net> Henk van Oers wrote: > Can you help me with this? Can you provide her email address? I'm afraid Act very terse logs will be of little help, but I can try to grep through the mailer logs or search for her user in the database. > ---------- Forwarded message ---------- > > On Tue, 10 Jan 2017, Melinda Kiss wrote: > > > I'm not getting any email when I sign up, is that normal? > > No, that's not normal. > Also requesting a passwordreset doesn't send a link. > > I'l ask the french admins. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From th.j.v.hoesel at gmail.com Wed Jan 25 14:47:06 2017 From: th.j.v.hoesel at gmail.com (Theo van Hoesel) Date: Wed, 25 Jan 2017 13:47:06 +0000 Subject: [Act] Act server: state of the situation In-Reply-To: <1197498944.579162423.1483058602803.JavaMail.root@spooler3-g27.priv.proxad.net> References: <1197498944.579162423.1483058602803.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <28E6F2F6-9C36-4070-A75C-967D094C6105@gmail.com> Hey S?bastien, Hop you are all doing well - and 'HAPPY NEW YEAR' to you (i know it's a bit late now) S?bastien, i am greatly worried about the current state of Act and it's future. North America has stepped away already and some voices in the Perl Conference Amsterdam team are going up and suggest looking at the way Dancer did their stuff. Please do not let this happen. We all love the features that Act offers and i am very willing to pickup the Act Voyager once things are smooth again. I even had a discussion with a developer willing to try to add another payment gateway, so people have more options to pay (like iDeal in the Netherlands) I can understand that this is all not primary concern and that priorities and limited resources or other restraints can make progress slow and difficult. But could you please update me what is holding back, and how we can make improvements in stability. And where possible, will gladly help to get it all back in a state that is acceptable Theo > On 30 Dec 2016, at 00:43, S?bastien Aperghis-Tramoni wrote: > > Hello all, > > > First, sorry, I know I should have made this mail earlier. > > So, here is the current situation with regards to the Act server. > When spectre suddenly disappeared from the internets, we switched > over the remaining service to phantom, which has been prepared for > this since a few months. However, it appears that phantom is way > too light to handle all the services. As a result, Act is regularly > crashing, and I now keep a constant eye on the logs, and restart > it whenever it needs to (3-4 times each day). That's mostly for the > time being. > > We have decided to rent a bigger server (12 CPU threads, 32 GB RAM), > with the following plan of actions: > > - make it a host for VMs: > - one VM for Act (Varnish, Apache + mod_perl, PostgreSQL) > - one VM for the rest (static sites, SVN, Mailman) > > - migrate Act ASAP to its dedicated VM > - migrate the rest of the services > - release phantom > > Using VM (Qemu/KVM) will hopefully ease backup & moving the servers > to a new host, when needed. > > Work has already begun. VMs are already installed. Thanks to a > friend, I've resolved a network issue I was having with NetFilter. > I am now preparing the Act VM to run Act (Apache 1.3, mod_perl 1.31, > Perl 5.8.9 or 5.12.4). > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > Technical specifications > ------------------------ > * host server > CPU: Xeon D-1531 (6 C / 12T @ 2,2 GHz) > RAM: 32 GB DDR4 ECC > HD: 2 x 250 GB SSD > OS: Debian jessie > > * VM for Act > vCPU: 8 > RAM: 16 GB > OS: FreeBSD 11.0 > > * VM for the rest > vCPU: 2 > RAM: 4 GB > OS: FreeBSD 11.0 > > -- > S?bastien Aperghis-Tramoni > > Close the world, txEn eht nepO. > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act From elbeho at boivin.eu Wed Jan 25 22:29:26 2017 From: elbeho at boivin.eu (L Boivin) Date: Wed, 25 Jan 2017 22:29:26 +0100 Subject: [Act] Act server: state of the situation In-Reply-To: <28E6F2F6-9C36-4070-A75C-967D094C6105@gmail.com> References: <1197498944.579162423.1483058602803.JavaMail.root@spooler3-g27.priv.proxad.net> <28E6F2F6-9C36-4070-A75C-967D094C6105@gmail.com> Message-ID: Hi Theo, S?bastien is currently working on the new server for Act (ghost) as the current one (phantom) is too light (I'm restarting it twice a day, Sebastien probably restarts it in the meantime too). The main problem with Act is its age. It's an 10+ year old code, stuck on Apache 1.3 / mod_perl1 / perl 5.8 (although most of the feature seems OK on perl 5.12.4) No one never had the will or the energy to try to keep it up to date with perl, nor mod_perl, nor Apache, nor postgresql. So moving it to a new server is a pain. And S?bastien (who was never involved in the development of the code) is doing it for the 2nd time in less than one year. As soon as S?bastien will take interest in beers, it'll cost me a lot! :-) If anyone is brave enough to port Act to Perl 5.20+, Apache 2.2 or 2.4, a [dr]ecent version of postgres (with a conversion of the DB from the current version), it will a first step before thinking of adding new features. Maybe. A brand new Act could be cool too. I just haven't seen anything since the Act-athon in Lyon 2 years ago, but I was not looking very carefully. In the meantime, please be patient. Kind Regards Laurent On 25/01/2017 14:47, Theo van Hoesel wrote: > Hey S?bastien, > > Hop you are all doing well - and 'HAPPY NEW YEAR' to you (i know it's a bit late now) > S?bastien, i am greatly worried about the current state of Act and it's future. North America has stepped away already and some voices in the Perl Conference Amsterdam team are going up and suggest looking at the way Dancer did their stuff. > > Please do not let this happen. We all love the features that Act offers and i am very willing to pickup the Act Voyager once things are smooth again. I even had a discussion with a developer willing to try to add another payment gateway, so people have more options to pay (like iDeal in the Netherlands) > > I can understand that this is all not primary concern and that priorities and limited resources or other restraints can make progress slow and difficult. > > But could you please update me what is holding back, and how we can make improvements in stability. > > And where possible, will gladly help to get it all back in a state that is acceptable > > Theo > > >> On 30 Dec 2016, at 00:43, S?bastien Aperghis-Tramoni wrote: >> >> Hello all, >> >> >> First, sorry, I know I should have made this mail earlier. >> >> So, here is the current situation with regards to the Act server. >> When spectre suddenly disappeared from the internets, we switched >> over the remaining service to phantom, which has been prepared for >> this since a few months. However, it appears that phantom is way >> too light to handle all the services. As a result, Act is regularly >> crashing, and I now keep a constant eye on the logs, and restart >> it whenever it needs to (3-4 times each day). That's mostly for the >> time being. >> >> We have decided to rent a bigger server (12 CPU threads, 32 GB RAM), >> with the following plan of actions: >> >> - make it a host for VMs: >> - one VM for Act (Varnish, Apache + mod_perl, PostgreSQL) >> - one VM for the rest (static sites, SVN, Mailman) >> >> - migrate Act ASAP to its dedicated VM >> - migrate the rest of the services >> - release phantom >> >> Using VM (Qemu/KVM) will hopefully ease backup & moving the servers >> to a new host, when needed. >> >> Work has already begun. VMs are already installed. Thanks to a >> friend, I've resolved a network issue I was having with NetFilter. >> I am now preparing the Act VM to run Act (Apache 1.3, mod_perl 1.31, >> Perl 5.8.9 or 5.12.4). >> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> >> Technical specifications >> ------------------------ >> * host server >> CPU: Xeon D-1531 (6 C / 12T @ 2,2 GHz) >> RAM: 32 GB DDR4 ECC >> HD: 2 x 250 GB SSD >> OS: Debian jessie >> >> * VM for Act >> vCPU: 8 >> RAM: 16 GB >> OS: FreeBSD 11.0 >> >> * VM for the rest >> vCPU: 2 >> RAM: 4 GB >> OS: FreeBSD 11.0 >> >> -- >> S?bastien Aperghis-Tramoni >> >> Close the world, txEn eht nepO. >> _______________________________________________ >> Act mailing list >> Act at mongueurs.net >> http://listes.mongueurs.net/mailman/listinfo/act > > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act > -- Laurent Boivin -- mailto:elbeho at boivin.eu Member of Mongueurs de Perl -- http://www.mongueurs.net/ Member of YAPC::Europe Foundation -- http://www.yapceurope.org/ Member of OSDC.fr -- http://osdc.fr/ From th.j.v.hoesel at gmail.com Wed Jan 25 22:59:36 2017 From: th.j.v.hoesel at gmail.com (Theo van Hoesel) Date: Wed, 25 Jan 2017 21:59:36 +0000 Subject: [Act] Act server: state of the situation In-Reply-To: References: <1197498944.579162423.1483058602803.JavaMail.root@spooler3-g27.priv.proxad.net> <28E6F2F6-9C36-4070-A75C-967D094C6105@gmail.com> Message-ID: Hi Laurent, Yes... it's me you can blame...! So, as i got it from the mail before this one, the way he tries to solve it, is by running it on a VM on a big machine. Not totally sure and I guess it has been tried already, what about only running Act is self inside on VM and a separate thing for running the databases? I mean, Act only talks to the Postgres DB, isn't it? That can be on any machine with sufficient power or even in a Master Slave.... and we could have multiple Act' servers in their ow tiny VM talk to them? right? Getting the DB out of the VM would be super... guess they still run in the VM of the hosting provider anyway. Another thing that might be extremely helpful... instead of me (and others) complaining that it is again down for toooo long... what about having me join the 'kick start reboot team'. I assume that you can write down the procedure on how to do so. Guess an extra pair off hands will be welcome here. I was already planning on setting up a 'server down alert' And of course, I gladly come to the beautiful city of Paris (or something easy to travel to by train from London) to spend a weekend making it all more stable with you and S?bastien. For me, there is tooo much on stake for the Perl Community to leave Act behind. Act was a wonderful Idea, let's not go back into age and people reinventing servers and websites. Let's spent time and other resources wisely. Closing this email, two things, what has been done since december? and secondly.... Super thank you for replying so quickly! Theo And yes, the ? are on me! Sent from my iPhone > On 25 Jan 2017, at 21:29, L Boivin wrote: > > Hi Theo, > > S?bastien is currently working on the new server for Act (ghost) as the > current one (phantom) is too light (I'm restarting it twice a day, > Sebastien probably restarts it in the meantime too). > > The main problem with Act is its age. > It's an 10+ year old code, stuck on Apache 1.3 / mod_perl1 / perl 5.8 > (although most of the feature seems OK on perl 5.12.4) > No one never had the will or the energy to try to keep it up to date with perl, nor mod_perl, nor Apache, nor postgresql. > > So moving it to a new server is a pain. > And S?bastien (who was never involved in the development of the code) > is doing it for the 2nd time in less than one year. > > As soon as S?bastien will take interest in beers, it'll cost me a lot! > :-) > > If anyone is brave enough to port Act to Perl 5.20+, Apache 2.2 or 2.4, > a [dr]ecent version of postgres (with a conversion of the DB from the > current version), it will a first step before thinking of adding new > features. Maybe. > A brand new Act could be cool too. I just haven't seen anything since > the Act-athon in Lyon 2 years ago, but I was not looking very carefully. > > In the meantime, please be patient. > > Kind Regards > Laurent > >> On 25/01/2017 14:47, Theo van Hoesel wrote: >> Hey S?bastien, >> >> Hop you are all doing well - and 'HAPPY NEW YEAR' to you (i know it's a bit late now) >> S?bastien, i am greatly worried about the current state of Act and it's future. North America has stepped away already and some voices in the Perl Conference Amsterdam team are going up and suggest looking at the way Dancer did their stuff. >> >> Please do not let this happen. We all love the features that Act offers and i am very willing to pickup the Act Voyager once things are smooth again. I even had a discussion with a developer willing to try to add another payment gateway, so people have more options to pay (like iDeal in the Netherlands) >> >> I can understand that this is all not primary concern and that priorities and limited resources or other restraints can make progress slow and difficult. >> >> But could you please update me what is holding back, and how we can make improvements in stability. >> >> And where possible, will gladly help to get it all back in a state that is acceptable >> >> Theo >> >> >>> On 30 Dec 2016, at 00:43, S?bastien Aperghis-Tramoni wrote: >>> >>> Hello all, >>> >>> >>> First, sorry, I know I should have made this mail earlier. >>> >>> So, here is the current situation with regards to the Act server. >>> When spectre suddenly disappeared from the internets, we switched >>> over the remaining service to phantom, which has been prepared for >>> this since a few months. However, it appears that phantom is way >>> too light to handle all the services. As a result, Act is regularly >>> crashing, and I now keep a constant eye on the logs, and restart >>> it whenever it needs to (3-4 times each day). That's mostly for the >>> time being. >>> >>> We have decided to rent a bigger server (12 CPU threads, 32 GB RAM), >>> with the following plan of actions: >>> >>> - make it a host for VMs: >>> - one VM for Act (Varnish, Apache + mod_perl, PostgreSQL) >>> - one VM for the rest (static sites, SVN, Mailman) >>> >>> - migrate Act ASAP to its dedicated VM >>> - migrate the rest of the services >>> - release phantom >>> >>> Using VM (Qemu/KVM) will hopefully ease backup & moving the servers >>> to a new host, when needed. >>> >>> Work has already begun. VMs are already installed. Thanks to a >>> friend, I've resolved a network issue I was having with NetFilter. >>> I am now preparing the Act VM to run Act (Apache 1.3, mod_perl 1.31, >>> Perl 5.8.9 or 5.12.4). >>> >>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >>> >>> Technical specifications >>> ------------------------ >>> * host server >>> CPU: Xeon D-1531 (6 C / 12T @ 2,2 GHz) >>> RAM: 32 GB DDR4 ECC >>> HD: 2 x 250 GB SSD >>> OS: Debian jessie >>> >>> * VM for Act >>> vCPU: 8 >>> RAM: 16 GB >>> OS: FreeBSD 11.0 >>> >>> * VM for the rest >>> vCPU: 2 >>> RAM: 4 GB >>> OS: FreeBSD 11.0 >>> >>> -- >>> S?bastien Aperghis-Tramoni >>> >>> Close the world, txEn eht nepO. >>> _______________________________________________ >>> Act mailing list >>> Act at mongueurs.net >>> http://listes.mongueurs.net/mailman/listinfo/act >> >> _______________________________________________ >> Act mailing list >> Act at mongueurs.net >> http://listes.mongueurs.net/mailman/listinfo/act >> > > > -- > Laurent Boivin -- mailto:elbeho at boivin.eu > Member of Mongueurs de Perl -- http://www.mongueurs.net/ > Member of YAPC::Europe Foundation -- http://www.yapceurope.org/ > Member of OSDC.fr -- http://osdc.fr/ > > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act From elbeho at boivin.eu Thu Jan 26 07:52:27 2017 From: elbeho at boivin.eu (L Boivin) Date: Thu, 26 Jan 2017 07:52:27 +0100 Subject: [Act] Act server: state of the situation In-Reply-To: References: <1197498944.579162423.1483058602803.JavaMail.root@spooler3-g27.priv.proxad.net> <28E6F2F6-9C36-4070-A75C-967D094C6105@gmail.com> Message-ID: <024a4b48-7e49-3711-8d68-56188d3acc67@boivin.eu> Hi Theo, Don't get me wrong. I don't blame anyone. The Act-athon in Lyon was not the 1st attempt for a new Act. I was hyped by Voyager but don't do anything by myself. For the system aspects, I'm clearly not the best one to answer, but what I can see is that mailman is consumming a lot of ressources on phantom. I'm about to restart a plan we had years ago but that we were not able to setup because of technical issues (that have been solved in the meantime): having the mailing list hosted by Sympa (rather than mailman) somewhere else (my current target is Strasbourg University). I just had the info it could be feasible. I'll let you know. KR Laurent Le 25/01/2017 ? 22:59, Theo van Hoesel a ?crit : > Hi Laurent, > > Yes... it's me you can blame...! > > So, as i got it from the mail before this one, the way he tries to solve it, is by running it on a VM on a big machine. > > Not totally sure and I guess it has been tried already, what about only running Act is self inside on VM and a separate thing for running the databases? I mean, Act only talks to the Postgres DB, isn't it? That can be on any machine with sufficient power or even in a Master Slave.... and we could have multiple Act' servers in their ow tiny VM talk to them? right? > > Getting the DB out of the VM would be super... guess they still run in the VM of the hosting provider anyway. > > Another thing that might be extremely helpful... instead of me (and others) complaining that it is again down for toooo long... what about having me join the 'kick start reboot team'. I assume that you can write down the procedure on how to do so. Guess an extra pair off hands will be welcome here. I was already planning on setting up a 'server down alert' > > And of course, I gladly come to the beautiful city of Paris (or something easy to travel to by train from London) to spend a weekend making it all more stable with you and S?bastien. > > For me, there is tooo much on stake for the Perl Community to leave Act behind. Act was a wonderful Idea, let's not go back into age and people reinventing servers and websites. Let's spent time and other resources wisely. > > Closing this email, two things, what has been done since december? and secondly.... > > Super thank you for replying so quickly! > > Theo > > And yes, the ? are on me! > > > > Sent from my iPhone > >> On 25 Jan 2017, at 21:29, L Boivin wrote: >> >> Hi Theo, >> >> S?bastien is currently working on the new server for Act (ghost) as the >> current one (phantom) is too light (I'm restarting it twice a day, >> Sebastien probably restarts it in the meantime too). >> >> The main problem with Act is its age. >> It's an 10+ year old code, stuck on Apache 1.3 / mod_perl1 / perl 5.8 >> (although most of the feature seems OK on perl 5.12.4) >> No one never had the will or the energy to try to keep it up to date with perl, nor mod_perl, nor Apache, nor postgresql. >> >> So moving it to a new server is a pain. >> And S?bastien (who was never involved in the development of the code) >> is doing it for the 2nd time in less than one year. >> >> As soon as S?bastien will take interest in beers, it'll cost me a lot! >> :-) >> >> If anyone is brave enough to port Act to Perl 5.20+, Apache 2.2 or 2.4, >> a [dr]ecent version of postgres (with a conversion of the DB from the >> current version), it will a first step before thinking of adding new >> features. Maybe. >> A brand new Act could be cool too. I just haven't seen anything since >> the Act-athon in Lyon 2 years ago, but I was not looking very carefully. >> >> In the meantime, please be patient. >> >> Kind Regards >> Laurent >> >>> On 25/01/2017 14:47, Theo van Hoesel wrote: >>> Hey S?bastien, >>> >>> Hop you are all doing well - and 'HAPPY NEW YEAR' to you (i know it's a bit late now) >>> S?bastien, i am greatly worried about the current state of Act and it's future. North America has stepped away already and some voices in the Perl Conference Amsterdam team are going up and suggest looking at the way Dancer did their stuff. >>> >>> Please do not let this happen. We all love the features that Act offers and i am very willing to pickup the Act Voyager once things are smooth again. I even had a discussion with a developer willing to try to add another payment gateway, so people have more options to pay (like iDeal in the Netherlands) >>> >>> I can understand that this is all not primary concern and that priorities and limited resources or other restraints can make progress slow and difficult. >>> >>> But could you please update me what is holding back, and how we can make improvements in stability. >>> >>> And where possible, will gladly help to get it all back in a state that is acceptable >>> >>> Theo >>> >>> >>>> On 30 Dec 2016, at 00:43, S?bastien Aperghis-Tramoni wrote: >>>> >>>> Hello all, >>>> >>>> >>>> First, sorry, I know I should have made this mail earlier. >>>> >>>> So, here is the current situation with regards to the Act server. >>>> When spectre suddenly disappeared from the internets, we switched >>>> over the remaining service to phantom, which has been prepared for >>>> this since a few months. However, it appears that phantom is way >>>> too light to handle all the services. As a result, Act is regularly >>>> crashing, and I now keep a constant eye on the logs, and restart >>>> it whenever it needs to (3-4 times each day). That's mostly for the >>>> time being. >>>> >>>> We have decided to rent a bigger server (12 CPU threads, 32 GB RAM), >>>> with the following plan of actions: >>>> >>>> - make it a host for VMs: >>>> - one VM for Act (Varnish, Apache + mod_perl, PostgreSQL) >>>> - one VM for the rest (static sites, SVN, Mailman) >>>> >>>> - migrate Act ASAP to its dedicated VM >>>> - migrate the rest of the services >>>> - release phantom >>>> >>>> Using VM (Qemu/KVM) will hopefully ease backup & moving the servers >>>> to a new host, when needed. >>>> >>>> Work has already begun. VMs are already installed. Thanks to a >>>> friend, I've resolved a network issue I was having with NetFilter. >>>> I am now preparing the Act VM to run Act (Apache 1.3, mod_perl 1.31, >>>> Perl 5.8.9 or 5.12.4). >>>> >>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >>>> >>>> Technical specifications >>>> ------------------------ >>>> * host server >>>> CPU: Xeon D-1531 (6 C / 12T @ 2,2 GHz) >>>> RAM: 32 GB DDR4 ECC >>>> HD: 2 x 250 GB SSD >>>> OS: Debian jessie >>>> >>>> * VM for Act >>>> vCPU: 8 >>>> RAM: 16 GB >>>> OS: FreeBSD 11.0 >>>> >>>> * VM for the rest >>>> vCPU: 2 >>>> RAM: 4 GB >>>> OS: FreeBSD 11.0 >>>> >>>> -- >>>> S?bastien Aperghis-Tramoni >>>> >>>> Close the world, txEn eht nepO. >>>> _______________________________________________ >>>> Act mailing list >>>> Act at mongueurs.net >>>> http://listes.mongueurs.net/mailman/listinfo/act >>> >>> _______________________________________________ >>> Act mailing list >>> Act at mongueurs.net >>> http://listes.mongueurs.net/mailman/listinfo/act >>> >> >> >> -- >> Laurent Boivin -- mailto:elbeho at boivin.eu >> Member of Mongueurs de Perl -- http://www.mongueurs.net/ >> Member of YAPC::Europe Foundation -- http://www.yapceurope.org/ >> Member of OSDC.fr -- http://osdc.fr/ >> >> _______________________________________________ >> Act mailing list >> Act at mongueurs.net >> http://listes.mongueurs.net/mailman/listinfo/act > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act > From jt at plainblack.com Thu Jan 26 08:41:09 2017 From: jt at plainblack.com (JT Smith) Date: Thu, 26 Jan 2017 01:41:09 -0600 Subject: [Act] Act server: state of the situation In-Reply-To: <024a4b48-7e49-3711-8d68-56188d3acc67@boivin.eu> References: <1197498944.579162423.1483058602803.JavaMail.root@spooler3-g27.priv.proxad.net> <28E6F2F6-9C36-4070-A75C-967D094C6105@gmail.com> <024a4b48-7e49-3711-8d68-56188d3acc67@boivin.eu> Message-ID: <6B0ABC5F-023B-4819-8577-D5CAB41404A0@plainblack.com> This may not be my place, but there is already a 100% modern Perl built replacement for Act called Tabletop.Events. Last week it handled registration for 2000 simultaneous users all buying badges and tickets to events. I can foresee 4 possible complaints A) it's not act. Can't help you there. B) it doesn't have the act logins and historical data. Give me the logins and I'll import them for you. As for the rest of the data, there is a full API if you want to import it. https://Tabletop.Events/developer/ C) it's not open source. True, but it has seen and will continue to see far more development than act has because it is profitable and has full time staff. D) it has no wiki True, but if that is all that is needed for adoption by the perl community then consider it done. And it may not have a wiki, but it does have a hell of a lot of features act doesn't have. Suggested with love from the organizer of YAPC::NA 2012. JT > On Jan 26, 2017, at 12:52 AM, L Boivin wrote: > > Hi Theo, > > Don't get me wrong. > I don't blame anyone. > The Act-athon in Lyon was not the 1st attempt for a new Act. > I was hyped by Voyager but don't do anything by myself. > > For the system aspects, I'm clearly not the best one to answer, > but what I can see is that mailman is consumming a lot of ressources > on phantom. > I'm about to restart a plan we had years ago but that we were not > able to setup because of technical issues (that have been solved in > the meantime): having the mailing list hosted by Sympa (rather than mailman) somewhere else (my current target is Strasbourg University). > I just had the info it could be feasible. > I'll let you know. > > KR > Laurent > > >> Le 25/01/2017 ? 22:59, Theo van Hoesel a ?crit : >> Hi Laurent, >> >> Yes... it's me you can blame...! >> >> So, as i got it from the mail before this one, the way he tries to solve it, is by running it on a VM on a big machine. >> >> Not totally sure and I guess it has been tried already, what about only running Act is self inside on VM and a separate thing for running the databases? I mean, Act only talks to the Postgres DB, isn't it? That can be on any machine with sufficient power or even in a Master Slave.... and we could have multiple Act' servers in their ow tiny VM talk to them? right? >> >> Getting the DB out of the VM would be super... guess they still run in the VM of the hosting provider anyway. >> >> Another thing that might be extremely helpful... instead of me (and others) complaining that it is again down for toooo long... what about having me join the 'kick start reboot team'. I assume that you can write down the procedure on how to do so. Guess an extra pair off hands will be welcome here. I was already planning on setting up a 'server down alert' >> >> And of course, I gladly come to the beautiful city of Paris (or something easy to travel to by train from London) to spend a weekend making it all more stable with you and S?bastien. >> >> For me, there is tooo much on stake for the Perl Community to leave Act behind. Act was a wonderful Idea, let's not go back into age and people reinventing servers and websites. Let's spent time and other resources wisely. >> >> Closing this email, two things, what has been done since december? and secondly.... >> >> Super thank you for replying so quickly! >> >> Theo >> >> And yes, the ? are on me! >> >> >> >> Sent from my iPhone >> >>> On 25 Jan 2017, at 21:29, L Boivin wrote: >>> >>> Hi Theo, >>> >>> S?bastien is currently working on the new server for Act (ghost) as the >>> current one (phantom) is too light (I'm restarting it twice a day, >>> Sebastien probably restarts it in the meantime too). >>> >>> The main problem with Act is its age. >>> It's an 10+ year old code, stuck on Apache 1.3 / mod_perl1 / perl 5.8 >>> (although most of the feature seems OK on perl 5.12.4) >>> No one never had the will or the energy to try to keep it up to date with perl, nor mod_perl, nor Apache, nor postgresql. >>> >>> So moving it to a new server is a pain. >>> And S?bastien (who was never involved in the development of the code) >>> is doing it for the 2nd time in less than one year. >>> >>> As soon as S?bastien will take interest in beers, it'll cost me a lot! >>> :-) >>> >>> If anyone is brave enough to port Act to Perl 5.20+, Apache 2.2 or 2.4, >>> a [dr]ecent version of postgres (with a conversion of the DB from the >>> current version), it will a first step before thinking of adding new >>> features. Maybe. >>> A brand new Act could be cool too. I just haven't seen anything since >>> the Act-athon in Lyon 2 years ago, but I was not looking very carefully. >>> >>> In the meantime, please be patient. >>> >>> Kind Regards >>> Laurent >>> >>>> On 25/01/2017 14:47, Theo van Hoesel wrote: >>>> Hey S?bastien, >>>> >>>> Hop you are all doing well - and 'HAPPY NEW YEAR' to you (i know it's a bit late now) >>>> S?bastien, i am greatly worried about the current state of Act and it's future. North America has stepped away already and some voices in the Perl Conference Amsterdam team are going up and suggest looking at the way Dancer did their stuff. >>>> >>>> Please do not let this happen. We all love the features that Act offers and i am very willing to pickup the Act Voyager once things are smooth again. I even had a discussion with a developer willing to try to add another payment gateway, so people have more options to pay (like iDeal in the Netherlands) >>>> >>>> I can understand that this is all not primary concern and that priorities and limited resources or other restraints can make progress slow and difficult. >>>> >>>> But could you please update me what is holding back, and how we can make improvements in stability. >>>> >>>> And where possible, will gladly help to get it all back in a state that is acceptable >>>> >>>> Theo >>>> >>>> >>>>> On 30 Dec 2016, at 00:43, S?bastien Aperghis-Tramoni wrote: >>>>> >>>>> Hello all, >>>>> >>>>> >>>>> First, sorry, I know I should have made this mail earlier. >>>>> >>>>> So, here is the current situation with regards to the Act server. >>>>> When spectre suddenly disappeared from the internets, we switched >>>>> over the remaining service to phantom, which has been prepared for >>>>> this since a few months. However, it appears that phantom is way >>>>> too light to handle all the services. As a result, Act is regularly >>>>> crashing, and I now keep a constant eye on the logs, and restart >>>>> it whenever it needs to (3-4 times each day). That's mostly for the >>>>> time being. >>>>> >>>>> We have decided to rent a bigger server (12 CPU threads, 32 GB RAM), >>>>> with the following plan of actions: >>>>> >>>>> - make it a host for VMs: >>>>> - one VM for Act (Varnish, Apache + mod_perl, PostgreSQL) >>>>> - one VM for the rest (static sites, SVN, Mailman) >>>>> >>>>> - migrate Act ASAP to its dedicated VM >>>>> - migrate the rest of the services >>>>> - release phantom >>>>> >>>>> Using VM (Qemu/KVM) will hopefully ease backup & moving the servers >>>>> to a new host, when needed. >>>>> >>>>> Work has already begun. VMs are already installed. Thanks to a >>>>> friend, I've resolved a network issue I was having with NetFilter. >>>>> I am now preparing the Act VM to run Act (Apache 1.3, mod_perl 1.31, >>>>> Perl 5.8.9 or 5.12.4). >>>>> >>>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >>>>> >>>>> Technical specifications >>>>> ------------------------ >>>>> * host server >>>>> CPU: Xeon D-1531 (6 C / 12T @ 2,2 GHz) >>>>> RAM: 32 GB DDR4 ECC >>>>> HD: 2 x 250 GB SSD >>>>> OS: Debian jessie >>>>> >>>>> * VM for Act >>>>> vCPU: 8 >>>>> RAM: 16 GB >>>>> OS: FreeBSD 11.0 >>>>> >>>>> * VM for the rest >>>>> vCPU: 2 >>>>> RAM: 4 GB >>>>> OS: FreeBSD 11.0 >>>>> >>>>> -- >>>>> S?bastien Aperghis-Tramoni >>>>> >>>>> Close the world, txEn eht nepO. >>>>> _______________________________________________ >>>>> Act mailing list >>>>> Act at mongueurs.net >>>>> http://listes.mongueurs.net/mailman/listinfo/act >>>> >>>> _______________________________________________ >>>> Act mailing list >>>> Act at mongueurs.net >>>> http://listes.mongueurs.net/mailman/listinfo/act >>>> >>> >>> >>> -- >>> Laurent Boivin -- mailto:elbeho at boivin.eu >>> Member of Mongueurs de Perl -- http://www.mongueurs.net/ >>> Member of YAPC::Europe Foundation -- http://www.yapceurope.org/ >>> Member of OSDC.fr -- http://osdc.fr/ >>> >>> _______________________________________________ >>> Act mailing list >>> Act at mongueurs.net >>> http://listes.mongueurs.net/mailman/listinfo/act >> _______________________________________________ >> Act mailing list >> Act at mongueurs.net >> http://listes.mongueurs.net/mailman/listinfo/act >> > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act From sebastien at aperghis.net Sun Jan 29 02:47:15 2017 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Sun, 29 Jan 2017 02:47:15 +0100 (CET) Subject: [Act] Act server: state of the situation In-Reply-To: <1197498944.579162423.1483058602803.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <1396324768.8538476.1485654435592.JavaMail.root@spooler3-g27.priv.proxad.net> Hello all, For information, Act is now technically running on the new host, ghost, and proxified via Varnish on phantom in order to keep everything transparent. We'll keep it that way for a few days to make sure things works correctly, then migrate the domains to point to ghost. Given that the new server has much more memory, is back to Perl 5.8.9 (much more akin to mod_perl1 than 5.12), and that I fixed some problems rising from the old version of Wiki::Toolkit not aware about DBD::Pg 3.0+, Act should be back to the stability it offered before being on phantom. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From th.j.v.hoesel at gmail.com Sun Jan 29 15:44:02 2017 From: th.j.v.hoesel at gmail.com (Theo van Hoesel) Date: Sun, 29 Jan 2017 14:44:02 +0000 Subject: [Act] Act server: state of the situation In-Reply-To: <1396324768.8538476.1485654435592.JavaMail.root@spooler3-g27.priv.proxad.net> References: <1396324768.8538476.1485654435592.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <96D8D9FE-D255-4F0D-9F97-063FFD5DC5EA@gmail.com> \o/ S?bastien ++ well done and thank you very much for making sure that we can keep using Act. It is the main platform for taking care of accepting presentation, allowing people to register, scheduling, payments, news and all this other nice features it offers. This really takes away a lot of unrest and I'm looking forward to see how our web-team of the Perl Conference in Amsterdam will make it look awesome and fill it with all that useful info our attendees want. Thank you once more Theo > On 29 Jan 2017, at 01:47, S?bastien Aperghis-Tramoni wrote: > > Hello all, > > For information, Act is now technically running on the new host, > ghost, and proxified via Varnish on phantom in order to keep > everything transparent. We'll keep it that way for a few days to > make sure things works correctly, then migrate the domains to > point to ghost. > > Given that the new server has much more memory, is back to Perl > 5.8.9 (much more akin to mod_perl1 than 5.12), and that I fixed > some problems rising from the old version of Wiki::Toolkit not > aware about DBD::Pg 3.0+, Act should be back to the stability > it offered before being on phantom. > > -- > S?bastien Aperghis-Tramoni > > Close the world, txEn eht nepO. > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act