Deployment of Litmus Edge Manager on Azure

you can deploy litmus edge manager directly from the azure marketplace choose between the consumption and site deployment models depending on your licensing preferences and infrastructure requirements the key differences involve licensing, billing, and access control important for cloud deployment before you activate the license, make sure all hardware or vm configuration steps are complete—including adding or replacing network interface controllers (nics) changing the vm hardware configuration after licensing may invalidate your license settings consumption model the consumption model is designed for organizations that want a fully managed deployment with automatic licensing and usage based billing with this model your license is automatically activated when you deploy and is valid for five years from deployment your tag usage is tracked and billed through azure marketplace litmus maintains the virtual machine through a managed resource group you have limited access to the underlying vm infrastructure site model the site model gives you full control over your infrastructure and requires you to manage your own licensing with this model you deploy the infrastructure but no license is included you request a license separately from the litmus account team tag consumption is not monitored or billed you maintain full control over your virtual machines litmus has no access to your environment comparison of models consumption model site model license automatic (valid for 5 years request from litmus team billing usage based (tags reported to azure) request from litmus team vm access limited customer access full customer access litmus access full access via managed resource group no access tag monitoring tracked and billed not monitored before you begin for both deployment models ensure you have access to https //portal azure com/ review the https //docs litmus io/edgemanager/quickstart guide/system requirements for sizing guidance review the https //docs litmus io/edgemanager/quickstart guide/system requirements#mxuhl for site model deployments request a license from the litmus account team before deployment if deploying on an existing network, grant the network contributor role on the subnet to thed ms app service principal az role assignment create \\ \ assignee "\<user or sp id>" \\ \ role "network contributor" \\ \ scope "/subscriptions/\<subscription id>/resourcegroups/\<resource group>/providers/microsoft network/virtualnetworks/\<virtual network name>/subnets/\<subnet name>" where \<user or sp id> is the object id of the user, group, or service principal (for example, principal id of a managed identity) \<subscription id> is the id of the azure subscription that contains the resource group \<resource group> is the name of the resource group that contains the virtual network \<virtual network name> is the name of the virtual network that hosts the subnet \<subnet name> is the name of the subnet to which you assign the network contributor role deploy litmus edge manager the deployment process is similar for both models the main difference is which offering you select in the azure marketplace step 1 find litmus edge manager in azure marketplace log in to https //portal azure com/ select create a resource in the search services and marketplace bar , enter litmus from the search results, select the consumption or site model litmus edge manager consumption model for usage based billing litmus edge manager site model for customer managed licensing click the card and navigate to https //portal azure com/#view/microsoft azure marketplace/galleryitemdetailsbladenopdl/id/litmusautomation1582760223280 litmus sitebased/selectionmode /false/resourcegroupid//resourcegrouplocation//dontdiscardjourney /false/selectedmenuid/home/launchingcontext /%7b%22galleryitemid%22%3a%22litmusautomation1582760223280 litmus sitebasedsitemodel%22%2c%22source%22%3a%5b%22galleryfeaturedmenuitempart%22%2c%22virtualizedtiledetails%22%5d%2c%22menuitemid%22%3a%22home%22%2c%22submenuitemid%22%3a%22search%20results%22%2c%22telemetryid%22%3a%2244813dfe 1489 43d1 a668 877f2f604a8a%22%7d/searchtelemetryid/69cf4d1d d536 43d5 819d 2c18d0167e46 or https //portal azure com/#view/microsoft azure marketplace/galleryitemdetailsbladenopdl/id/litmusautomation1582760223280 lem litmus azure/selectionmode /false/resourcegroupid//resourcegrouplocation//dontdiscardjourney /false/selectedmenuid/home/launchingcontext /%7b%22galleryitemid%22%3a%22litmusautomation1582760223280 lem litmus azuredata tag per hour2%22%2c%22source%22%3a%5b%22galleryfeaturedmenuitempart%22%2c%22virtualizedtiledetails%22%5d%2c%22menuitemid%22%3a%22home%22%2c%22submenuitemid%22%3a%22search%20results%22%2c%22telemetryid%22%3a%222d07ba25 0421 4148 bcc5 4cad0dedcb2f%22%7d/searchtelemetryid/65b39d51 e71c 4b4b a9ac 34d1fb266a39 in the litmus edge manager configuration model or site model page, define the following settings resource group define a resource group for deployment region define a region for deployment size see the https //docs litmus io/edgemanager/quickstart guide/system requirements for minimum & recommended sizing managed resource group select managed resource group from the options click review + create review your configuration, then agree to the terms & conditions and provide contact information on the next page click create check the inbound firewall rules in the virtual network once the application is deployed successfully 443/tcp lem ui access 8446/tcp lem admin console ui access 8883/tcp le to lem mqtt connection 51820/udp le to lem remote access connection depending on desired network and architecture, you can define specific ranges of ip for sources and destinations review all required and optional inbound and outbound litmus edge manager https //docs litmus io/edgemanager/quickstart guide/system requirements#mxuhl navigate back to the overview page in the essentials section, find the ip address associated to your litmus edge manager instance by azure \[optional] configure dns enter the ip or dns in a browser to docid\ w3uhzq4tsrh7oljhult0a web ui note user access to ui will be determined by network & firewall configuration