<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Thanks for starting this thread Nicolas. I think it’ll be very useful for other projects.</div>
<div class=""><br class="">
</div>
<div class="">I am currently helping with some of the work for the Atlas of Living Scotland (AoLS) which we hope to have running in September.</div>
<div class="">This will be ran on EC2 and Im putting together the deployment. </div>
<div class="">I plan to document/blog about this deployment so others can use it for reference with the used specs of the EC2 machines etc.</div>
<div class=""><br class="">
</div>
<div class="">To address the points:</div>
<div class=""><br class="">
</div>
<div class="">
<div class=""> * Were those requirements sufficient for you?</div>
<div class="">These specs are only suitable to get a demo up and running and are not sufficient for production. </div>
<div class=""><br class="">
</div>
<div class=""> * Did you deploy everything on a single server or did you use a more splitted infrastructure? If so, did you wrote your own ansible scripts to match your configuration?</div>
<div class="">We do not recommend everything is installed on a single server for production. Specifically, SOLR and Cassandra both benefit from running on their own dedicated machine.</div>
<div class="">The work for AoLS has made me realise that while the demo ansible playbook [1] is useful for folks doing a quick demonstrator, it isn’t very helpful as a starting point for starting production deployments.</div>
<div class="">The ALA developers use separate playbooks for each component [2] and we need some documentation around these playbooks. I think we need a "Getting Started” for production deployments which would give a list of unusable playbooks to run.</div>
<div class=""><br class="">
</div>
<div class=""> * Did you use physical servers? Or Amazon EC2 instances ? Or another cloud providers?</div>
<div class="">I think EC2/Digital Ocean/other-colour-provider instances should be fine.</div>
<div class=""><br class="">
</div>
<div class=""> * Is there anything you'd do differently if you had to do it again tomorrow?</div>
<div class="">Any other comments or remark?</div>
<div class="">I guess I'll leave this for my blog/documentation.</div>
</div>
<div class=""><br class="">
</div>
<div class="">Thanks again,</div>
<div class=""><br class="">
</div>
<div class="">Dave</div>
<div class=""><br class="">
</div>
<div class="">[1] <a href="https://github.com/AtlasOfLivingAustralia/ala-install/blob/master/ansible/ala-demo.yml" class="">https://github.com/AtlasOfLivingAustralia/ala-install/blob/master/ansible/ala-demo.yml</a></div>
<div class="">[2] <a href="https://github.com/AtlasOfLivingAustralia/ala-install/tree/master/ansible" class="">https://github.com/AtlasOfLivingAustralia/ala-install/tree/master/ansible</a></div>
<div class=""><br class="">
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 19 Aug 2015, at 10:26 am, Nicolas Noé <<a href="mailto:n.noe@biodiversity.be" class="">n.noe@biodiversity.be</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><font size="-1" class=""><font face="Verdana" class="">Hi guys,<br class="">
<br class="">
I'm still evaluating how to deploy an ALA instance for Belgium at the end of this year and was interested in hearing your first hands experience about the infrastructure you run the portal on.
<br class="">
<br class="">
I'm especially interested about the experience of countries like France and Spain that did it recently and who have a volume of data of the same order of magnitude as Belgium.<br class="">
<br class="">
The documentation (<a class="moz-txt-link-freetext" href="https://github.com/AtlasOfLivingAustralia/documentation/wiki/Essential-tools-and-environmental-requirements">https://github.com/AtlasOfLivingAustralia/documentation/wiki/Essential-tools-and-environmental-requirements</a>)
recommends the following server configuration:<br class="">
<br class="">
- 100Gb SSD<br class="">
- 32GB RAM<br class="">
- 2x CPU<br class="">
<br class="">
My questions are:<br class="">
</font></font>
<ul class="">
<li class=""><font size="-1" class=""><font face="Verdana" class="">Were those requirements sufficient for you?</font></font>
</li><li class=""><font size="-1" class=""><font face="Verdana" class="">Did you deploy everything on a single server or did you use a more splitted infrastructure? If so, did you wrote your own ansible scripts to match your configuration?</font></font>
</li><li class=""><font size="-1" class=""><font face="Verdana" class="">Did you use physical servers? Or Amazon EC2 instances ? Or another cloud providers?<br class="">
</font></font></li><li class=""><font size="-1" class=""><font face="Verdana" class="">Is there anything you'd do differently if you had to do it again tomorrow?</font></font>
</li><li class=""><font size="-1" class=""><font face="Verdana" class="">Any other comments or remark?</font></font>
</li></ul>
<p class=""><font size="-1" class=""><font face="Verdana" class="">Thanks a lot for your collaboration!<br class="">
</font></font></p>
<p class=""><font size="-1" class=""><font face="Verdana" class="">Nicolas<br class="">
</font></font></p>
<p class=""><br class="">
</p>
<font size="-1" class=""><font face="Verdana" class=""><br class="">
<br class="">
</font></font></div>
_______________________________________________<br class="">
Ala-portal mailing list<br class="">
<a href="mailto:Ala-portal@lists.gbif.org" class="">Ala-portal@lists.gbif.org</a><br class="">
http://lists.gbif.org/mailman/listinfo/ala-portal<br class="">
</div>
</blockquote>
</div>
<br class="">
</body>
</html>