AzureExtensionManager

Topics: Core
May 9, 2012 at 6:31 PM

Would the AzureShellSettingsManager: IShellSettingsManager approach also work for ExtensionManager enabling modules to be installed dynamically from the gallery in while hosted on multiple Azure instances? Assuming it looks both locally for the deployed modules and on blob storage for those dynamically added?

Coordinator
May 9, 2012 at 6:37 PM

It would be nice to find a solution. You can customize any dependency to run specifically on Azure. The issue here is to signal to all nodes that a new module has to be downloaded, and also to reload them when the node is refreshed or restarted, as the VM doesn't have them. Storing downloaded packages in the blobs would be part of the solution. It would also require some db state to define what modules should be added too, maybe using a background task to observe the modules.

May 9, 2012 at 7:20 PM

Initial thought is a topic with subscription per instance, but thats seems a bit over kill.

Anyone care to pitch on simplest and most elegant way to signal to all nodes/instances?

May 9, 2012 at 8:12 PM
Edited May 10, 2012 at 5:17 PM

Is this the correct? 

namespace Custom.MyNameSpace
[OrchardSuppressDependency("Orchard.Environment.Extensions.ExtensionManager")]
public class AzureExtensionManager : IExtensionManager {
    //my AzureExtensionManager implementation
}

May 10, 2012 at 5:17 PM

I've tried this approach and the class never gets loaded, any help / direction is appreciated.