![]() Subsequent requests from end-user devices for content come from the cache.An MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers content to the client.Microsoft end-user devices make range requests for content from the MCC node.Client policy is configured in your management solution to point to the IP address or FQDN of the cache server.The MCC container is deployed and provisioned to a server using the installer provided in the portal.The Azure Management Portal is used to create MCC nodes.The following steps describe how MCC is provisioned and used. See figure 1 below for a summary of the architecture of MCC, built using IoT Edge.įor more information about Azure IoT Edge, see What is Azure IoT Edge. To deploy a functional MCC to your device, you must obtain the necessary keys that will provision the Connected Cache instance to communicate with Delivery Optimization services and enable the device to cache and deliver content. Reports MCC health and usage to the cloud for remote monitoring.Maintains Azure IoT Edge security standards on your edge device.Installs and updates MCC on your edge device.The runtime performs the following important functions to manage MCC on your edge device: The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. MCC will be a Linux IoT Edge module running on the Windows Host OS.Įven though your MCC scenario isn't related to IoT, Azure IoT Edge is used as a more generic Linux container, deployment, and management infrastructure. It’s built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. IoT Edge for Linux on Windows (EFLOW) was chosen because it's a secure, reliable container management infrastructure. MCC is a hybrid (a mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module it's a Docker compatible Linux container that is deployed to your Windows devices. Cache nodes are created in the cloud portal and are configured by applying a client policy using your management tool, such as Intune. MCC can be deployed to as many physical servers or VMs as needed, and is managed from a cloud portal. Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within Enterprise networks. For more information, see Supplemental Terms of Use for Microsoft Azure Previews. This phase does not include formal support, and should not be used for production workloads. During this phase we invite customers to take part in early access for testing purposes. ![]() Microsoft Connected Cache is currently a private preview feature. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |