Currently, deploying the Actor Framework to Windows Azure requires downloading our source code and using a special plugin to upload code to Azure. Please grab a copy of the source tree, carefully picking a changeset that matches the release you've installed (instructions can be found on our Notes on Syncing Installed Code with Built Code page). We also assume you have an Azure account name, and have retrieved the Account Key from the Azure portal. After you've synced the Actor Framework source, here are the further instructions to set up the Azure plugin.
  1. Download the file.
  2. Extract the contents of the file into a temporary directory locally.
  3. In the "AzurePlugin/AzurePlugin/WindowsFabric" folder, edit ClusterManifest.xml so that the ImageManagementConnectionString value has the proper settings for AccountName, AccountKey, and Container.
    • Container should be "imagestore". The other two are custom to your Azure storage account.
    • Make sure you remove any []'s in the file, filling those in with real values. Do not include the or around your values.
  4. Copy the "AzurePlugin/AzurePlugin/WindowsFabric" folder to "C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\v2.0\bin\plugins".
  5. In Visual Studio, open the ActorBasics solution from the Actor Framework source tree (ie, {ACTORFX_SOURCE_ROOT}\main\src\NET\ActorBasics\ActorBasicsSolution.sln)
  6. In the AzureFxAzureCluster project, edit ServiceDefinition.csdef.
    • Uncomment "<Import moduleName="WindowsFabric"/>".
  7. In the AzureFxAzureCluster project, edit ServiceConfiguration.Cloud.cscfg
    • Edit the Connection string to include your account name and account key, like this:
<Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="DefaultEndpointsProtocol=https;AccountName=fabricstoragedev;AccountKey=abcdef123456==" />
  1. Right click on the AzureFxAzureCluster project and click Publish.

Publishing will take about 5 to 8 minutes, and it may take another ~1 to 2 minutes for the Actor Framework to completely load on your machines. The next steps are to use the Actor Runtime Manager to deploy a gateway application (so clients can communicate with your cluster), then to deploy an application like a list or dictionary.

Last edited Nov 13, 2013 at 12:16 AM by joehoag, version 2


No comments yet.