Hello World MSMQ! …from Windows Containers

[Server Man]

Hello from Microsoft Hackathon!!!

What are we hacking? Containerizing MSMQ! Let me tell you more…

MSMQ (Microsoft Message Queuing) is one of the top asks from Enterprise customers who are lifting and shifting traditional apps with Windows Containers. We are hearing that in our conversations with customers directly, especially with major financial institutions. It is a blocker in their containerization journey. We are also seeing the same ask in online communities like the following on User Voice and MSDN Forum:

• Create base container image with MSMQ-Server
• MSMQ-Server - Is it supported?

Back in January, I blogged that we fixed the issue that MSMQ didn’t install at all in Windows Server Core containers. With Windows Server version 1803 release, MSMQ now installs. As the old saying, devils are in the details. In our effort to make the end-to-end scenarios work with MSMQ in containers, we learned that there is a long list of components, features, technologies and teams involved to make it fully working end-to-end for typical Enterprise customer scenarios. To name a few: Container Networking, Active Directory, Group Managed Service Accounts. And it also brings another top customer ask supporting MSDTC in Windows containers to the spot light. So, I decided to take this challenge to our internal Hackathon!

In the first a few hours when we started the Hackathon, we identified a prioritized scenario list we’ll target to hack on. I will share the details of the scenarios in future blogs. But first I am happy to share that today we validated the first scenario working. It’s a very “Hello World” alike scenario that sends messages from a Window container using MSMQ. Here is the basics of the scenario:

• Set-up
  • Container Host: Windows Server v1803 or higher, OR, Windows 10 April 2018 Updates or higher
    • A quick note: In today’s Hackathon, my teammate who validated the scenario was actually on the most recent build of Windows 10 which is not even out for Insiders yet but we did test on Windows Server version 1803 and version 1809 pre-release builds before
  • Container Image: Windows Server v1803 Server Core container
• MSMQ Configurations
  • Queue Scope: Private
  • Message Type: Transactional
  • 2 Simple apps using MSMQ to simulate the most basic send/receive operations:
    • MSMQSenderTest.exe
    • MSMQReceiveTest.exe
  • Queue Location: on the same container as the Sender/Receiver.
  • Where the sender and receive sit: to simplify things, both the sender and receiver testing apps run directly inside the above mentioned Container Image. This is far away from a real-world scenario but remember we are starting with baby steps.

And Voila… we can send and receive messages in a Windows container!




Is it too basic? Yes it is. We know. As mentioned early on, we have worked on this on and off, and have tested a few other scenarios. Here is a quick glimpse of what we have tested or are still testing on. We will share more details in future blogs.

Scope Transactional Container OS Container Host OS Queue Location Send Works Receive Works
Private Yes Windows Server version 1803 Windows Server version 1803 On the container Yes. Yes.
Public Yes Windows Server version 1803 Windows Server version 1803 On the Domain Controller (DC) Yes. There are some security caveats we’d like to address. Haven’t tested
Public No Windows Server version 1803 Windows Server version 1803 Not on the container, or the container host, or the DC, but another box Yes. There are some security caveats we’d like to address. Haven’t tested
Public Yes Windows Server version 1803 Windows Server version 1803 Not on the container, or the container host, or the DC, but another box No. Haven’t tested



The top 2 rows are more basic scenarios for us to get started and troubleshoot. The last 2 rows in our view are most close to what Enterprise customers might be using. Is it true? We’d love to hear your validation.

We didn’t test the scenario where the queue is a Private one and the messages are non-transactional. We believe as the scenario of a private queue with transactional messages works, a private queue with non-transactional one should work too as it’s less complex.

As we peel the onions layers by layers, it’s becoming more and more obvious that we can use all the help inside and outside Microsoft to get this going, as MSMQ is a technology out for a long time, and there are lots of you who are experts on this. We’ll look into to ways we can sort of “crowdsource” or “group-think” to get the community involved. We will share more details on that in future blogs.

OK, this is for now and I need to get back to the Hackathon! Wish me and my teammates (Andy, Jane, and Ross) good luck!



Weijuan

P.S. I am building up my Twitter presence which seems a popular place to keep people updated. I’ll share updates more frequently there. Follow me @WeijuanLand

Continue reading...