Installing OGDI version 5 on Azure – Part 1

Posted by on May 5, 2013 in OGDI DataLab

This article describes the installation using Azure Portal ver.2 – August 2012 (updated February 2012)

Configuring a Windows Azure Account

This set of articles will walk you through the setup of the Windows Azure account you will use to install the OGDI platform. It will explain how to setup a Cloud Service, which will host the OGDI web and worker roles. It will also explain how to create the two Storages needed for the configuration tables and the data storage itself.

To be able to install OGDI on Azure you need to setup one Cloud Service and two Storages. If you do not have your Azure account, you need to sign up for it using a Windows Live ID.

For our walkthrough we will use a trial account of Windows Azure, which provides the same functionality as a paid one, except it is time-limited. All screens below are shown as examples and you should use your own information to create the required services and accounts. Please note that all screenshots are based on Visual Studio 2010 and Windows Azure Management Portal released in 2012:

https://manage.windowsazure.com/


may 2013 Installing OGDI version 5 on Azure - Part 1 picture 01

Creating the Cloud Service

The Cloud service will run the data provider accessible to the public, which will expose the catalogues (datasets) to any consumer – client app or a direct http request.
To create a Cloud Service:

  1. Start the Windows Azure Portal Management Portal.
  2. Select Cloud Services on the left sidebar.
  3. Click on New at the left corner of the bottom toolbar.

may 2013 Installing OGDI version 5 on Azure - Part 1 picture 02

  1. In the new menu select Cloud Service, Quick Create, and then type a URL of your new site. It will be the one that your users will see unless you have a domain name to assign it to, so be cautious when choosing a name.
  2. You need to also choose a region or affinity group so all your storages and cloud services are in the same geographic location. This will decrease data traffic and speed up your services. If you do not have an affinity group already, you will not see any in the drop-down selection.
  3. Click Create Cloud Service and wait for the process to finish.

After a few seconds you will see the newly created Cloud Service in the list.
may 2013 Installing OGDI version 5 on Azure - Part 1 picture 03
This is all you need to prepare the Cloud Service on Windows Azure.

Creating two storages

For the OGDI v.5, you need two storages:

  • A configuration storage, where the OGDI project keeps the data endpoints;
  • A data storage, where the actual data is stored, which will be available for the public.

To create the two storages:

  1. Start the Windows Azure Portal Management Portal, if you haven’t done so yet.
  2. Select Storage.
  3. Click on New at the left corner of the bottom toolbar.
  4. Select Storage and then Quick Create

may 2013 Installing OGDI version 5 on Azure - Part 1 picture 04

  1. Enter a prefix of the URL that will be used to connect to the account. We suggest using the word config in it, so you can easily recognise this account later.
  2. Do not forget to select the same region or affinity group in which you put the Cloud Service. This will make both servers to be in the same geographic location.
  3. Click Create Storage Account to create the account.

Perform the same steps for creating Storage for the data, which will hold the publically exposed catalogues. The difference should be that in Step 5 you will put the word data in the prefix. We also suggest you use the same structure of the prefix. In our example we used myopencityconfig and myopencitydata.

Please note that these are public URLs and if the names are already taken, the Management Portal will notify you and ask to choose different ones.

At the end, the Storage panel will display the two new accounts (config and data) you have just created.

may 2013 Installing OGDI version 5 on Azure - Part 1 picture 05
These are all the steps you need to perform to create the needed Cloud Service and the Storages.

Next page >