Implementation using Nomad<\/h2>\n\n\n\n
While using the IIS plugin, we evaluated that there’re some gaps that needed to be filled. So we decided to add those features by ourselves. Additional features which we have added are:-<\/p>\n\n\n\n
- Resource Limit on IIS<\/li>
- Recycle Parameters<\/li>
- Environment Variables<\/li><\/ul>\n\n\n\n
Basic features of an orchestration engine was already supported by Nomad like:-<\/p>\n\n\n\n
- Scaling\/Autoscaling<\/li>
- Failover<\/li>
- Metrics Monitoring<\/li>
- Service Discovery<\/li>
- Service Mesh<\/li><\/ul>\n\n\n\n
The plugin is available here<\/a>.<\/p>\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2021\/05\/nomad-architecture.png?w=1024\")
<\/figure>\n\n\n\nSince we are assuming Nomad and Consul are already part of the setup, we can directly jump to the configuration part of the IIS Job. If you haven’t and want to setup Nomad quickly, please refer to this document<\/a>.<\/a><\/p>\n\n\n\n
job \"iis-test\" {\n datacenters = [\"dc1\"]\n type = \"service\"\n\n group \"iis-test\" {\n count = 1\n restart {\n attempts = 10\n interval = \"5m\"\n delay = \"25s\"\n mode = \"delay\"\n }\n task \"iis-test\" {\n driver = \"win_iis\"\n\n artifact {\n source = \"https:\/\/github.com\/iamabhishek-dubey\/nomad-driver-iis\/releases\/download\/v0.4\/test-hello-world.zip\"\n }\n config {\n path = \"${NOMAD_TASK_DIR}\\\\netcoreapp2.1\"\n\n apppool_identity {\n identity = \"NetworkService\"\n }\n\n bindings {\n type = \"http\"\n resource_port = \"httplabel\"\n }\n }\n resources {\n cpu = 100\n memory = 20\n network {\n port \"httplabel\" {}\n }\n }\n service {\n name = \"iis-test\"\n tags = [\"iis-test\", \"windows-iis-test\"]\n port = \"httplabel\"\n check {\n type = \"tcp\"\n interval = \"10s\"\n timeout = \"2s\"\n }\n }\n }\n }\n}\n<\/pre>\n\n\n\nOnce the job configuration is complete, we can create the job using the Nomad UI in our cluster.<\/p>\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2021\/05\/image-3.png?w=685\")
<\/figure>\n\n\n\nNow, if you try to open the service on your browser, the content will look like this:-<\/p>\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2021\/05\/image-4.png?w=606\")
<\/figure>\n\n\n\nSo as we can see the application is working fine here, now let’s see the service health on consul as well.<\/p>\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2021\/05\/image-5.png?w=1024\")
<\/figure>\n\n\n\nAs we can see the service looks healthy. Further, we can still try the orchestrator’s functionality, like, scaling. Scale the iis-test count and see what changes have been made by Nomad and Consul.<\/p>\n\n\n\n
![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2021\/05\/image-6.png?w=568\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/opstree.com\/blog\/\/wp-content\/uploads\/2021\/05\/image-7.png?w=638\")
<\/figure>\n\n\n\nOnce we have scaled the application count to 2, the nomad has started another IIS process for the application and the consul registered it as a second replica of the service. If we try to kill the process as well, the nomad will create another replica of the process just like Kubernetes ;). <\/p>\n\n\n\n
If you want to access the code of the blog, please check this repository<\/a>. All the configuration files for nomad and consul are present inside the repository. Also, if you want to test out this setup quickly, there is a Vagrantfile in the repository. To execute the vagrant we simply need to run:-<\/p>\n\n\n\n
vagrant up<\/pre>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
By thinking out of the box, we solved the issue for non-containerized-based applications as well and we have achieved some basic functionalities of an orchestration engine like- scaling, failover, management, service discovery, etc. for Windows-based applications.<\/p>\n\n\n\n
But again, it doesn’t mean that this approach is restricted for Windows-based applications only, by using this plug-n-play method of Nomad we can solve a lot of issues.<\/p>\n\n\n\n
I hope you guys have enjoyed the reading but if you have any feedback or suggestions, please reach out to me. In my upcoming blog, I will discuss the production parameters for Nomad and Consul and how we can integrate autoscaling in nomad.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Blog Pundit:<\/strong> Adeel Ahmad<\/strong><\/a> & Sandeep Rawat<\/strong><\/a> <\/p>\n\n\n\n
Opstree is an End to End DevOps solution provider<\/p>\n\n\n\n