Followed the incredibly easy startup guide from Keith Mayer, superstar – http://blogs.technet.com/b/keithmayer/archive/2014/10/03/quick-start-guide-building-highly-available-linux-servers-in-the-cloud-on-microsoft-azure.aspx
The Powerpoint deck is about 20 slides or so, incredibly easy to follow. But here’s a Cliff notes version for us Linux newbies out there:
- Log onto the Azure management portal. https://manage.windowsazure.com/ – the new one is fine.
- Create an Affinity Group (Settings -> Affinity Group). Call it something like LinuxForDemoDH or the like.
- Create a Storage Account. Click + (New), Create a Storage Account, then Data Services -> Storage -> Quick Create. Select your Affinity Group.
- Create a Virtual Network. (Network Services -> Virtual Network, Quick Create).
- Create a Cloud Service. (Compute, Cloud Service, Quick Create). Select your affinity group! I called this “linuxwebapp” in my example.
Add a new VM from the Gallery.
- In this case I chose Ubuntu, Ubuntu Server 14.04 LTS.
- Called it “linuxwebapp01” but it really doesn’t matter since the frontend is set in #5 above.
- Uncheck the SSH key, and check Provide a password.
- Select your Cloud Service and your Virtual Network / Storage Account.
- Select the option to Create an Availability Set (call it Linuxwebapp or the like)
- Follow the above steps to add a second VM. Call it lxwebapp02 or the like. Only you won’t need 6e, just point to what you created then.
Select your App01 VM and browse to the dashboard, then point to Endpoints and select + Add.
- Add a standalone Endpoint
- Call it HTTP – and select TCP | 80 |80.
- Select the option to create a load balanced set. Call it LB_HTTP.
- Follow the steps above for WebApp02, only hook up to an existing LB set.
- Look at the dashboard and note the name/port of the environment under the SSH DETAILS portion. Connect to it using a SSH client like bitvise, and use the azureuser account you specified last time. A Linux shell prompt will open. Enter the following: run sudo apt-get install apache2
- Follow the same steps on the second webserver.
- Now to test. Open up the App01 web server in Azure management portal and select the Dashboard, then look at the DNS name. Try to open it in a new browser window. If you can view the following, you’re golden!
That’s it for now. I’m going to try more automatic provisioning of my new highly available and scalable Linux webservers later today.
<news flash>Well I just got brought in on another firefighting task so my IAC (Infrastructure As Code) efforts will have to wait. See this post for the script I was going to follow: http://blogs.technet.com/b/keithmayer/archive/2014/12/01/step-by-step-automated-provisioning-for-linux-in-the-cloud-with-microsoft-azure-xplat-cli-json-and-node-js-part-2.aspx