I am gradually moving to the stage where I would like to deploy some small seaside applications. These would be commercial applications, so seasidehosting.st isn't appropriate.
What I am looking for is a company that will manage the OS stack, and let me concentrate on the Seaside application. I am not at the stage of needing a whole server, I am looking for the equivalent of Engine Yard for Seaside.
Does anyone know of a company doing that? Cheers Andy
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Maybe you can run a webvelocity ami on Amazon EC2? I am also working on some commercial seaside applications and planning to hire some Virtual Private Servers for a few euro's a month to get started. Once traffic is up, I'll probably move to EC2. Downside of VPS is that you'll need to configure everything yourself and maintain it as well.
Regards, Bart
2010/8/23 Andy Burnett <[hidden email]> I am gradually moving to the stage where I would like to deploy some small seaside applications. These would be commercial applications, so seasidehosting.st isn't appropriate. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Andy Burnett
Bart Veenstra said <<< Maybe you can run a webvelocity ami on Amazon EC2? I am also working on some commercial seaside applications and planning to hire some Virtual Private Servers for a few euro's a month to get started. Once traffic is up, I'll probably move to EC2. Downside of VPS is that you'll need to configure everything yourself and maintain it as well. >>> I wondered about the AMI option as well. I am half way through setting up an Amazon account - just got stopped by the public private key bit (need to read the instructions).
I wonder how difficult it is to create an AMI of Seaside/Pharo - and ideally Andreas' SSL classes. It would seem like a useful thing to have so that people could get a bit more serious with Seaside.
Is it just a question of money? If so, I would be happy to 'sponsor' someone to do it, provided we could then make it publicly available. The key bit is that it would have to be kept up to date, otherwise it would be a wasted effort.
Also, I got an email from the sales people at Rackspace. Apparently I was misinformed and they could do a Seaside instance on their cloud stack, so that might be an interesting approach as well. Randal did a Floss show about Openstack (a few weeks back). Perhaps we should target that instead of AMI?
Cheers
Andy
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
I am playing with Amazon Web Services as well, EC2 AMI's (especially EBS backed ones) are very cool. The new web interface console is also very nice. This is definitively very useful and promising technology.
The only downside is that you are somewhat trapped in their environment, but less so than with some others. Sven On 24 Aug 2010, at 20:23, Andy Burnett wrote: > > Bart Veenstra said > <<< > Maybe you can run a webvelocity ami on Amazon EC2? I am also working on some > commercial seaside applications and planning to hire some Virtual Private > Servers for a few euro's a month to get started. Once traffic is up, I'll > probably move to EC2. Downside of VPS is that you'll need to configure > everything yourself and maintain it as well. > >>> > > I wondered about the AMI option as well. I am half way through setting up an Amazon account - just got stopped by the public private key bit (need to read the instructions). > > I wonder how difficult it is to create an AMI of Seaside/Pharo - and ideally Andreas' SSL classes. It would seem like a useful thing to have so that people could get a bit more serious with Seaside. > > Is it just a question of money? If so, I would be happy to 'sponsor' someone to do it, provided we could then make it publicly available. The key bit is that it would have to be kept up to date, otherwise it would be a wasted effort. > > Also, I got an email from the sales people at Rackspace. Apparently I was misinformed and they could do a Seaside instance on their cloud stack, so that might be an interesting approach as well. Randal did a Floss show about Openstack (a few weeks back). Perhaps we should target that instead of AMI? > > Cheers > Andy > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hi there, I am one of the developers of WebVelocity.
For what it's worth, I've been experimenting with EC2 instances that have VisualWorks 7.7.1 NC installed with postgresql database for a Store repository and Seaside loaded and preconfigured. So far it looks promising, and depending on the feedback and support I receive from my colleagues and our product management, a public AMI could be available soon. Depending on platform, people would be able to access it via VNC or RDP. Jerry Kott Senor Software Engineer Cincom Systems On 24-08-2010, at 12:20 PM, Sven Van Caekenberghe wrote: > I am playing with Amazon Web Services as well, EC2 AMI's (especially EBS backed ones) are very cool. The new web interface console is also very nice. This is definitively very useful and promising technology. > > The only downside is that you are somewhat trapped in their environment, but less so than with some others. > > Sven > > On 24 Aug 2010, at 20:23, Andy Burnett wrote: > >> >> Bart Veenstra said >> <<< >> Maybe you can run a webvelocity ami on Amazon EC2? I am also working on some >> commercial seaside applications and planning to hire some Virtual Private >> Servers for a few euro's a month to get started. Once traffic is up, I'll >> probably move to EC2. Downside of VPS is that you'll need to configure >> everything yourself and maintain it as well. >>>>> >> >> I wondered about the AMI option as well. I am half way through setting up an Amazon account - just got stopped by the public private key bit (need to read the instructions). >> >> I wonder how difficult it is to create an AMI of Seaside/Pharo - and ideally Andreas' SSL classes. It would seem like a useful thing to have so that people could get a bit more serious with Seaside. >> >> Is it just a question of money? If so, I would be happy to 'sponsor' someone to do it, provided we could then make it publicly available. The key bit is that it would have to be kept up to date, otherwise it would be a wasted effort. >> >> Also, I got an email from the sales people at Rackspace. Apparently I was misinformed and they could do a Seaside instance on their cloud stack, so that might be an interesting approach as well. Randal did a Floss show about Openstack (a few weeks back). Perhaps we should target that instead of AMI? >> >> Cheers >> Andy >> _______________________________________________ >> seaside mailing list >> [hidden email] >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Andy Burnett
Hello,
I have created an EC2 image with Pharo and Smalltalk in the past. If people are interested I can bring it up to date and make it public so everybody can try it out.
There are other cloud computing options besides Amazon's AWS EC2. For example from Rackspace. But I think AWS is the most mature and has the most features.
Jan.
On 8/24/10, Andy Burnett <[hidden email]> wrote:
-- Jan van de Sandt gsm: +31 (0)6 3039 5998 _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hello,
I have been running my Pier based blog on EC2 instance for over a year. The EC2 setup has been created by friend of mine who does linux installations on regular basis, but looking at it in retrospective, it seems that creating basic Seaside ami would not be that difficult especially now when there are EBS based images. However more advanced setups that would provide SSL, load balancing and similar stuff might prove to be significantly more complex to create But I guess even plain vanilla Seaside or Pier ami would be a great thing. Though it would need to be maintained on regular to keep basis it up to date with latest seaside images. Also, maybe Gemstone folks might find motivation to publish their GLASS appliance in ami form as well? rush http://www.cloud208.com/blogica/Internal+plumbing _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On 8/25/10, Davorin Rusevljan <[hidden email]> wrote:
But I guess even plain vanilla Seaside or Pier ami would be a great Creating an AMI image takes quit some time. I is not very efficient to create a new AMI every time there is an update to the Seaside image. It is better to run a startup script when the AMI is started. This startup script can copy an up-to-date Smalltalk image from some well known location.
Great that you are already running a Pier setup on EC2 for a year. What are your experiences with uptime? And how do you make sure that you don.'t lose any data when the EC2 image goes down? I guess by saving the image regularly on EBS or S3 Jan.
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On Wed, Aug 25, 2010 at 2:42 PM, Jan van de Sandt <[hidden email]> wrote:
> Creating an AMI image takes quit some time. I is not very efficient to > create a new AMI every time there is an update to the Seaside image. It is > better to run a startup script when the AMI is started. This startup script > can copy an up-to-date Smalltalk image from some well known location. Good point, though I am not sure script should be started each time ami is started, since image might be used for persistency. But maybe script could be used once to "finalize" ami with latest version before user starts to customize it. With EBS based ami, that would be no problem, since it would not be necessary to create a new ami after the customization. > Great that you are already running a Pier setup on EC2 for a year. What are > your experiences with uptime? And how do you make sure that you don.'t lose > any data when the EC2 image goes down? I guess by saving the image regularly > on EBS or S3 I do not have much load on it only a few visits per day, so it has never been put under the stress, but in recent year it has been restarted only once (by some Amazon house keeping I assume). As for persisting data, I am keeping Pier image on ebs mounted volume. Unfortunately when image was created there was no option to make whole machine EBS based, since that would result in less complicated and more flexible machine. I have it on my long term list to migrate everything on new ebs based instance, with ubuntu lucid lynx and latest pier and nginx, but as everyone else, my wish list is far longer than "could realistically do in given time" list :) rush http://www.cloud208.com/ _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Andy Burnett
Jan van de Sandt said <<<
Hello, I have created an EC2 image with Pharo and Smalltalk in the past. If people are interested I can bring it up to date and make it public so everybody can try it out. There are other cloud computing options besides Amazon's AWS EC2. For example from Rackspace. But I think AWS is the most mature and has the most features. >>> Thanks Jan, that would be great if you could produce an up to date image. I would love to try it.
Cheers
Andy _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Andy Burnett
Jerry Kott said <<<
Hi there, I am one of the developers of WebVelocity. For what it's worth, I've been experimenting with EC2 instances that have VisualWorks 7.7.1 NC installed with postgresql database for a Store repository and Seaside loaded and preconfigured. So far it looks promising, and depending on the feedback and support I receive from my colleagues and our product management, a public AMI could be available soon. Depending on platform, people would be able to access it via VNC or RDP. >>> Thanks Jerry, I must finish the AWS account set up so that I can try the beta image that is on the service.
One thing I would like to know about Web Velocity is whether I can upload a 'normal' seaside application into Web Velocity, and then manage it/continue to develop it via the WV interface.
Cheers
Andy
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Andy Burnett
Davorin Rusevljan said <<<
Hello, I have been running my Pier based blog on EC2 instance for over a year. The EC2 setup has been created by friend of mine who does linux installations on regular basis, but looking at it in retrospective, it seems that creating basic Seaside ami would not be that difficult especially now when there are EBS based images. ... >>> I am curious to know two things:
Cheers
Andy
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On Wed, Aug 25, 2010 at 5:51 PM, Andy Burnett
<[hidden email]> wrote: > I am curious to know two things: > > How big a 'slice' does your site require? The various cloud hosting > services offer slices of different sizes and I suddenly realised that I had > no idea what is reasonable for a Seaside image. I know it must vary based on > load etc,. so I am curious to know what yours needs - just as a practical > example on amazon, you get to choose between few standard instance types: small, large, extra large .. etc. I am using small instance since my requirements are small. List of available instance types can be found here: http://aws.amazon.com/ec2/instance-types/ > What is an EBS image? Well, it is something that you would expect to have, but at the beginning of ec2 you did not have :) . In the beginnigs of ec2 your disks were not actually persistent, when you restarted the machine, the changes to the disk were lost, and the state of the machine would be reverted to the state as configured in ami. So if you would for instance add user to your running machine, it would be gone once you restarted the machine. You could mount EBS (elastic block storage) device to your machine and data stored on it would persist, so that was a place where one could store changing important data. But the machine would itself always boot from the partition that was fried inside ami, into the state you have save once while you created the ami. So you had to make various rain dance rituals to make sure that your changing data is actually placed on ebs volume. Now available ebs based images, do what you would expect them to do, your main boot partition is persistent and you can count that changes to it are going to survive restart of the machine. I hope that my explanation was at least semi clear :) Taking yet another tangent, one thing related to ec2 that would be very interesting to have sometime in the future is seaside integration with amazon's elastic load balancer. rush http://www.cloud208.com/ _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2010/8/25 Davorin Rusevljan <[hidden email]>:
> On Wed, Aug 25, 2010 at 5:51 PM, Andy Burnett > <[hidden email]> wrote: >> I am curious to know two things: >> >> How big a 'slice' does your site require? The various cloud hosting >> services offer slices of different sizes and I suddenly realised that I had >> no idea what is reasonable for a Seaside image. I know it must vary based on >> load etc,. so I am curious to know what yours needs - just as a practical >> example > > on amazon, you get to choose between few standard instance types: > small, large, extra large .. etc. I am using small instance since my > requirements are small. List of available instance types can be found > here: > > http://aws.amazon.com/ec2/instance-types/ > > >> What is an EBS image? > > Well, it is something that you would expect to have, but at the > beginning of ec2 you did not have :) . In the beginnigs of ec2 your > disks were not actually persistent, when you restarted the machine, > the changes to the disk were lost, and the state of the machine would > be reverted to the state as configured in ami. So if you would for > instance add user to your running machine, it would be gone once you > restarted the machine. You could mount EBS (elastic block storage) > device to your machine and data stored on it would persist, so that > was a place where one could store changing important data. But the > machine would itself always boot from the partition that was fried > inside ami, into the state you have save once while you created the > ami. So you had to make various rain dance rituals to make sure that > your changing data is actually placed on ebs volume. > > Now available ebs based images, do what you would expect them to do, > your main boot partition is persistent and you can count that changes > to it are going to survive restart of the machine. > > I hope that my explanation was at least semi clear :) > > Taking yet another tangent, one thing related to ec2 that would be > very interesting to have sometime in the future is seaside integration > with amazon's elastic load balancer. What's missing? What would have to be done? From what I get from the docs, it should just work. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On 26 Aug 2010, at 10:34, Philippe Marschall wrote: > What's missing? What would have to be done? From what I get from the > docs, it should just work. Yes, with your Seaside-Cluster package it would be possible (although in my reading of the docs you would have to use session cookies instead of parameters). Still, actually doing it would be a nice hack ;-) The AWS load balancing is over EC2 instances, so by definition that is already a heavier setup. A single Seaside image is quite small (using -mmap 32m works fine) so you could put a couple of them on a single instance. But it all depends on the application of course. Sven _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |