Tech Radar blog
Viewing entries posted in 2011
What is actually holding Alberta back from becoming the next Silicon Valley? A lack of resources? Or its own inhibitions? This was a major issue for discussion at the Tech Futures Summit 2011, held in Banff from August 29-31 by Alberta Innovates — Technology Futures.
Alberta is not without its Open Government movements, but we have yet to see a provincial open data initiative in Alberta similar to what was launched in B.C., and there are no indications that such a system will be developed…
There has been a wider push towards Open Government in recent years, a phenomenon that has grown worldwide…
This month’s 11 Questions interview is with Perry Kinkaide. He is currently on a leave of absence from his role as President of ABCtech as he’s currently working to create a technology industry association for Alberta.
Once a writer or painter or photographer or videographer’s work is published to an online forum — say Amazon or YouTube or iStock — who owns the rights to it?
Cybera Senior Developer Everett Toews was recently in Melbourne, AU, collaborating with the National eResearch Collaboration Tools and Resources (NeCTAR) team and other Australian groups interested in cloud technologies. Here, Everett shares some insights on the visit as well as advice for the development of research clouds.
There are many options for deploying OpenStack, such as Crowbar, StackOps and Nebula. However, none of these advanced options were very mature when we needed to put OpenStack into production, so we had to roll up our sleeves and start scripting. Plus, a great way to learn about a system is by deploying it directly from its package repositories.
The fine folks at CANARIE, whom we built the DAIR cloud for, were amenable to making the scripts Open Source, so you can find all of the scripts we used to deploy OpenStack Cactus here. Important note! These scripts were written with the requirements for the multi-region DAIR project in mind. While they were mostly generalized, many of our design decisions may not be suitable for your cloud (e.g. using VLANManager networking mode). Use at your own risk!
Also note that we simply used dsh to do concurrent installations across all of our compute/volume and storage nodes.
A brief explanation of the directories in Github:
/admin – Admin scripts that we wrote to simplify the creation of projects and ease administrative functions.
/cloudpipe – Scripts to set up the cloudpipe (VPN) server. Optional.
/common – Scripts we run on machines before installing any OpenStack components on them. Optional.
/dashboard – Scripts for installing the OpenStack Dashboard. Optional.
/glance – Scripts for installing Glance.
/ldap – Scripts for installing LDAP. Optional.
/misc – Stuff. Mostly used for image creation.
/nova – Scripts for installing Nova. The important ones are nova-CC-install.sh and nova-NODE-install.sh.
/stress-test – An attempt to stress test Nova and Swift.
/swift – Scripts for installing Swift. The important ones are swift-proxy-installer.sh and swift-node-installer.sh.
My primary bit of advice is to take these scripts with a grain of salt. Definitely give them a good read through before even thinking about running them. If nothing else, they’re an example of how you can install OpenStack Cactus.
Enter to win a free 2011 Summit registration by answering this question: Why is the cloud community as important as the technology itself?
If there is an abundance of technology available to professors, and it is known to be helpful in the classroom, why aren’t more professors using it to its full potential when teaching?
By Matt Delaney, DevOp at Cybera