Next challenge: getting Adhearsion to run on EC2?
Philippe Creytens
I am glad some of you got Asterisk to work on EC2.
This might open up new paths there... having an application monitoring traffic and 'adding' Asterisk' on the fly.
I am well aware that I could easily add Adhearsion --this the Adhearsion group afterall, right?-- onto the EC2 image where the Asterisk resides.
Some basic scripts should be able sort out AGI/AMI references needed by AHN on startup.
As a concept, I would be very eager to learn more on how we could use AHN in a load-balanced/hot backup way as an EC2 image, connecting to a (fluctuating) pool of Asterisk servers.
Finally, if we can add database support with Amazon's Persistent Storage Volumes, we could have a complete system built in the 'cloud'.
(And beat Google Engine because we as developers control everything)
Any thoughts there?
Philippe
Tim Uckun
This is exactly where we want to go with our service one day.
The hardest part is the database but here is kind of how I see things working...
You have to create pools of everything. A cluster of asterisk servers,
a cluster of ahn servers (you could put them on the asterisk server),
a cluster of database servers. The database and ahn servers need to
be behind a load balancer.
If the databases are truly clustered you should be able to lose any
one and still go along fine.
You keep everything syncronized by either git, rsync or powerfolder
except the databases.
You communicate between the ahn servers using rinda/ring, spread, or
the amazon queue service (pay per message).
As I said the hardest thing is the database. If you can put down the
relational database crack pipe you could "outsource" that to amazon
too.
BTW if anybody wants to work on such a project I would love to work with you.