You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by "Joy P. Ku" <jo...@stanford.edu> on 2014/07/17 23:24:35 UTC
Running Allura on virtual machines
We are considering migrating our current software forge to Allura but
would very much like to set up the new site with components distributed to
different virtual machines. In our current site, we run everything off of
one server but find that approach is limiting in terms of flexibility for
maintaining the site (e.g., being able to just take one component like the
wiki off line for updates). It also means that if one part breaks, the
whole site goes down. So we'd very much like to migrate to a set-up where
the internal components could be set up on virtual machines. Is it
possible to get this to work for Allura and maintain performance? Have
others done this before, and if so, what have their experiences been?
Thanks for any input you can provide!
Joy
---
Joy P. Ku, PhD
Director, <http://simbios.stanford.edu/> Simbios
Director of Communications & Training, <http://opensim.stanford.edu/>
NCSRR
Stanford University
(w) 650.736.8434, (f) 650.723.7461
Email: <ma...@stanford.edu> joyku@stanford.edu
Re: Running Allura on virtual machines
Posted by Dave Brondsema <da...@brondsema.net>.
Not really. In Allura, the tools (wiki, blog, tickets, code browser, etc) are
separate components but the core of allura pulls them together in a sense, so
you can't run them separately. If you do have to do some maintenance on a tool
(rare in my experience) or a tool is having an error, those generally do not
"spill over" and affect other tools, so even though they all run together if one
is down for a reason, the rest should be accessible.
On 7/22/14 4:57 PM, Joy P. Ku wrote:
> Thanks, Dave!
>
> Does it make any sense to break out the components of the webapp? For
> instance, if we wanted to do updates to the wiki or blog, would we be able
> to set up the infrastructure so that the wiki runs on one VM which we
> would take off-line for maintenance while the rest of the site stays up
> and running?
>
> Joy
>
> -----Original Message-----
> From: Dave Brondsema [mailto:dave@brondsema.net]
> Sent: Friday, July 18, 2014 8:29 AM
> To: dev@allura.apache.org
> Subject: Re: Running Allura on virtual machines
>
> Hi Joy,
>
> Yes this is possible. An allura system has 4 main services:
>
> * mongo database
> * solr
> * allura taskd (background job service)
> * allura webapp
>
> You can run those on separate machines, and you can run multiple instances
> of taskd and the webapp if you want to scale out and have redundancy.
> Mongo and solr need to have one master server, but can be configured with
> secondary slaves ready for failover. We run a configuration like that at
> SourceForge and it works well.
>
> If you're going to run git, mercurial or subversion services, those also
> can be on separate machines, with a shared directory so that Allura can
> display the repositories.
>
> Let us know if you have any other questions, I know the docs don't cover
> everything, but we'll be glad to help here.
>
> -Dave
>
> On 7/17/14 5:24 PM, Joy P. Ku wrote:
>> We are considering migrating our current software forge to Allura but
>> would very much like to set up the new site with components
>> distributed to different virtual machines. In our current site, we
>> run everything off of one server but find that approach is limiting in
>> terms of flexibility for maintaining the site (e.g., being able to
>> just take one component like the wiki off line for updates). It also
>> means that if one part breaks, the whole site goes down. So we'd very
>> much like to migrate to a set-up where the internal components could
>> be set up on virtual machines. Is it possible to get this to work for
>> Allura and maintain performance? Have others done this before, and if
> so, what have their experiences been?
>>
>>
>>
>> Thanks for any input you can provide!
>>
>> Joy
>>
>>
>>
>> ---
>>
>> Joy P. Ku, PhD
>>
>> Director, <http://simbios.stanford.edu/> Simbios
>>
>> Director of Communications & Training, <http://opensim.stanford.edu/>
>> NCSRR
>>
>> Stanford University
>>
>>
>>
>> (w) 650.736.8434, (f) 650.723.7461
>>
>> Email: <ma...@stanford.edu> joyku@stanford.edu
>>
>>
>>
>>
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
RE: Running Allura on virtual machines
Posted by "Joy P. Ku" <jo...@stanford.edu>.
Thanks, Dave!
Does it make any sense to break out the components of the webapp? For
instance, if we wanted to do updates to the wiki or blog, would we be able
to set up the infrastructure so that the wiki runs on one VM which we
would take off-line for maintenance while the rest of the site stays up
and running?
Joy
-----Original Message-----
From: Dave Brondsema [mailto:dave@brondsema.net]
Sent: Friday, July 18, 2014 8:29 AM
To: dev@allura.apache.org
Subject: Re: Running Allura on virtual machines
Hi Joy,
Yes this is possible. An allura system has 4 main services:
* mongo database
* solr
* allura taskd (background job service)
* allura webapp
You can run those on separate machines, and you can run multiple instances
of taskd and the webapp if you want to scale out and have redundancy.
Mongo and solr need to have one master server, but can be configured with
secondary slaves ready for failover. We run a configuration like that at
SourceForge and it works well.
If you're going to run git, mercurial or subversion services, those also
can be on separate machines, with a shared directory so that Allura can
display the repositories.
Let us know if you have any other questions, I know the docs don't cover
everything, but we'll be glad to help here.
-Dave
On 7/17/14 5:24 PM, Joy P. Ku wrote:
> We are considering migrating our current software forge to Allura but
> would very much like to set up the new site with components
> distributed to different virtual machines. In our current site, we
> run everything off of one server but find that approach is limiting in
> terms of flexibility for maintaining the site (e.g., being able to
> just take one component like the wiki off line for updates). It also
> means that if one part breaks, the whole site goes down. So we'd very
> much like to migrate to a set-up where the internal components could
> be set up on virtual machines. Is it possible to get this to work for
> Allura and maintain performance? Have others done this before, and if
so, what have their experiences been?
>
>
>
> Thanks for any input you can provide!
>
> Joy
>
>
>
> ---
>
> Joy P. Ku, PhD
>
> Director, <http://simbios.stanford.edu/> Simbios
>
> Director of Communications & Training, <http://opensim.stanford.edu/>
> NCSRR
>
> Stanford University
>
>
>
> (w) 650.736.8434, (f) 650.723.7461
>
> Email: <ma...@stanford.edu> joyku@stanford.edu
>
>
>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: Running Allura on virtual machines
Posted by Dave Brondsema <da...@brondsema.net>.
Hi Joy,
Yes this is possible. An allura system has 4 main services:
* mongo database
* solr
* allura taskd (background job service)
* allura webapp
You can run those on separate machines, and you can run multiple instances of
taskd and the webapp if you want to scale out and have redundancy. Mongo and
solr need to have one master server, but can be configured with secondary slaves
ready for failover. We run a configuration like that at SourceForge and it
works well.
If you're going to run git, mercurial or subversion services, those also can be
on separate machines, with a shared directory so that Allura can display the
repositories.
Let us know if you have any other questions, I know the docs don't cover
everything, but we'll be glad to help here.
-Dave
On 7/17/14 5:24 PM, Joy P. Ku wrote:
> We are considering migrating our current software forge to Allura but
> would very much like to set up the new site with components distributed to
> different virtual machines. In our current site, we run everything off of
> one server but find that approach is limiting in terms of flexibility for
> maintaining the site (e.g., being able to just take one component like the
> wiki off line for updates). It also means that if one part breaks, the
> whole site goes down. So we'd very much like to migrate to a set-up where
> the internal components could be set up on virtual machines. Is it
> possible to get this to work for Allura and maintain performance? Have
> others done this before, and if so, what have their experiences been?
>
>
>
> Thanks for any input you can provide!
>
> Joy
>
>
>
> ---
>
> Joy P. Ku, PhD
>
> Director, <http://simbios.stanford.edu/> Simbios
>
> Director of Communications & Training, <http://opensim.stanford.edu/>
> NCSRR
>
> Stanford University
>
>
>
> (w) 650.736.8434, (f) 650.723.7461
>
> Email: <ma...@stanford.edu> joyku@stanford.edu
>
>
>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><