diff --git a/windows/deployment/do/mcc-ent-private-preview.md b/windows/deployment/do/mcc-ent-private-preview.md index 83b9aaa5aa..d80c08f02f 100644 --- a/windows/deployment/do/mcc-ent-private-preview.md +++ b/windows/deployment/do/mcc-ent-private-preview.md @@ -12,13 +12,15 @@ appliesto: ms.date: 06/03/2024 --- -# Microsoft Connected Cache for Enterprise and Education Private Preview -If you participated in the Connected Cache early preview, thank you for your collaboration and feedback. +# Microsoft Connected Cache for Enterprise and Education (early preview) -To continue using Connected Cache, we strongly recommend that you upgrade your existing cache nodes to the Public Preview release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the Connected Cache Azure service. +If you participated in the early preview program, thank you for your collaboration and feedback. + +To continue using supported version of Microsoft Connected Cache, we strongly recommend that you upgrade your existing cache nodes to the new release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the Microsoft Connected Cache Azure service. + +We strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCC caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. -As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the Connected Cache software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. ## Next step diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index aa3cdec687..bbd76a511d 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -16,24 +16,30 @@ ms.date: 09/27/2024 # Release Notes for Microsoft Connected Cache for Enterprise and Education -This article contains details about the latest releases of Connected Cache. Since Connected Cache is a Preview service, some releases may contain breaking changes that will be highlighted as such. +This article contains details about the latest releases of Connected Cache. Since Connected Cache is a preview service, some releases may contain breaking changes. -## Release v0.1.0 (Public Preview launch) +## Release v0.1.0 (public preview launch) -- Released on **10/17/2024** -- Contains breaking changes -- Contains service changes -- Contains client changes -- Affects Linux, Windows host machines +The public preview released on **10/30/2024** -### Change notes +For customers that installed earlier versions of Connected Cache, this release contains: +- Breaking changes +- Service changes +- Client changes +These changes affect Linux and Windows host machines. -- Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface -- Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface -- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same Connected Cache Azure resource -- Added Azure CLI support for programmatic creation and management of Connected Cache Azure resources and cache nodes -- Added support for unauthenticated proxy and cloud proxy integration -- Added ability to set each cache node's Update Ring to govern cadence of Connected Cache container updates + +### Feature updates + +- **Metrics and charts in Azure portal**: You can now visualize "Outbound egress" and "Volume by Content type" charts for your cache node on Azure portal. You can also create custom monitoring charts for your cache nodes. This capability is under the **Metrics** tab on Azure portal. +- **Cache nodes for Windows or Linux host machines**: Cache nodes can now be created and deployed to Windows host machine or Linux host machines by simply choosing the OS when creating cache nodes. +- **Ubuntu 22.04 LTS**: Cache nodes can now be deployed on Ubuntu 22.04 LTS. +- **Azure CLI support**: Cache nodes can now be created and managed via Azure CLI. +- **Proxy**: We added support for unauthenticated proxy and cloud proxy integration. +- **Updates**: Your cache nodes are now updated automatically and we also added the capability to set each cache node's update ring to govern the cadence of Micoroft Connected Cache container updates. + +### Fixes +- We fixed various bugs to achieve smoother install experience. ## Related content diff --git a/windows/deployment/do/mcc-isp.md b/windows/deployment/do/mcc-isp.md index 0d3426ca7a..5baf7d7209 100644 --- a/windows/deployment/do/mcc-isp.md +++ b/windows/deployment/do/mcc-isp.md @@ -20,594 +20,20 @@ appliesto: # Microsoft Connected Cache for Internet Service Providers (early preview) > [!IMPORTANT] -> This document is for Microsoft Connected Cache (early preview). Microsoft Connected Cache for ISPs is now in Public Preview - for our early preview customers, we highly encourage you to onboard onto our Public Preview program. For instructions on signing up and onboarding please visit [Operator sign up and service onboarding for Microsoft Connected Cache](mcc-isp-signup.md). +> Microsoft Connected Cache for ISPs is now in Public Preview - for our early preview customers, and early preview version is no longer supported. We highly encourage you to onboard onto our Public Preview program. For instructions on signing up and onboarding, visit [Operator sign up and service onboarding for Microsoft Connected Cache](mcc-isp-signup.md). ## Overview -Microsoft Connected Cache preview is a software-only caching solution that delivers Microsoft content within operator networks. Connected Cache can be deployed to as many physical servers or VMs as needed and is managed from a cloud portal. Microsoft cloud services handle routing of consumer devices to the cache server for content downloads. +Microsoft Connected Cache preview is a software-only caching solution that delivers Microsoft content within operator networks. Connected Cache can be deployed to as many physical servers or VMs as needed and is managed from a cloud portal. Microsoft cloud services handle routing of consumer devices to the cache server for content downloads. For more information, visit [Microsoft Connected Cache for ISP](mcc-isp-overview.md). -Microsoft Connected Cache is a hybrid application, in that it's a mix of on-premises and cloud resources. It's composed of a Docker-compatible Linux container deployed to your server and a cloud management portal. Microsoft chose Azure IoT Edge as a secure and reliable control plane. For more information on IoT Edge, see the [Appendix](#appendix). Even though your scenario isn't related to IoT, Azure IoT Edge is our secure Linux container deployment and management infrastructure. - -## How Connected Cache works - -:::image type="content" source="./images/mcc-isp-diagram.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="./images/mcc-isp-diagram.png"::: - -The following steps describe how Connected Cache is provisioned and used: - -1. The Azure Management Portal is used to create and manage Connected Cache nodes. - -1. A shell script is used to provision the server and deploy the Connected Cache application. - -1. A combination of the Azure Management Portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the Connected Cache server. - - - The publicly accessible IPv4 address of the server is configured on the portal. - - - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the Connected Cache node. - - - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the Connected Cache node. - - > [!NOTE] - > Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error. - -1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding Connected Cache node. - -1. Microsoft clients make the range requests for content from the Connected Cache node. - -1. A Connected Cache node gets content from the CDN, seeds its local cache stored on disk, and delivers the content to the client. - -1. Subsequent requests from end-user devices for content will be served from cache. - -1. If the Connected Cache node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers. - -## ISP requirements for Connected Cache Microsoft Connected Cache for Internet Service Providers is now in Public Preview! To get started, visit [Azure portal](https://www.portal.azure.com) to sign up for Microsoft Connected Cache for Internet Service Providers. Please see [Operator sign up and service onboarding for Microsoft Connected Cache](mcc-isp-signup.md) for more information on the requirements for sign up and onboarding. - - - - - - -## Verify properly functioning Connected Cache server - -### Verify client side - -Sign in to the Connected Cache server or use SSH. Run the following command from a terminal to see the running modules (containers): - -```bash -sudo iotedge list -``` - -:::image type="content" source="./images/mcc-isp-running-containers.png" alt-text="Screenshot of the terminal output of iotedge list command, showing the running containers." lightbox="./images/mcc-isp-running-containers.png"::: - -If it lists the **edgeAgent** and **edgeHub** containers, but doesn't include **MCC**, view the status of the IoT Edge security manager using the command: - -```bash -sudo journalctl -u iotedge -f -``` - -For example, this command provides the current status of the starting and stopping of a container, or the container pull and start: - -:::image type="content" source="./images/mcc-isp-edge-journalctl.png" alt-text="Terminal output of journalctl command for iotedge." lightbox="./images/mcc-isp-edge-journalctl.png"::: - -### Verify server side - -It can take a few minutes for the container to deploy. - -To validate a properly functioning Connected Cache, run the following command in the terminal of the cache server or any device in the network. Replace `` with the IP address of the cache server. - -```bash -wget http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com -``` - -The following screenshot shows a successful test result: - -:::image type="content" source="./images/mcc-isp-wget.png" alt-text="Screenshot of the terminal output of successful test result with wget command to validate a Microsoft Connected Cache." lightbox="./images/mcc-isp-wget.png"::: - -Similarly, enter the following URL into a web browser on any device on the network: - -```http -http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com -``` - -If the test fails, for more information, see the [common issues](#common-issues) section. - -## Common Issues - -### Microsoft Connected Cache is no longer serving traffic -If you did not migrate your cache node then your cache node may still be on early preview version. -Microsoft Connected Cache for Internet Service Providers is now in Public Preview! To get started, visit [Azure portal](https://www.portal.azure.com) to sign up for Microsoft Connected Cache for Internet Service Providers. Please see [Operator sign up and service onboarding for Microsoft Connected Cache](mcc-isp-signup.md) for more information on the requirements for sign up and onboarding. -
-
-
- -> [!NOTE] -> This section only lists common issues. For more information on additional issues you may encounter when configuring IoT Edge, see the [IoT Edge troubleshooting guide](/azure/iot-edge/troubleshoot). - -Use the following command to check the IoT Edge journal: - -```bash -sudo journalctl -u iotedge -f -``` - -### DNS needs to be configured - -Run the following IoT Edge install state check: - -```bash -sudo iotedge check --verbose -``` - -If you see issues with ports 5671, 443, and 8883, your IoT Edge device needs to update the DNS for Docker. - -To configure the device to work with your DNS, use the following steps: - -1. Use `ifconfig` to find the appropriate NIC adapter name. - - ```bash - ifconfig - ``` - -1. Run `nmcli device show ` to show the DNS name for the ethernet adapter. For example, to show DNS information for **eno1**: - - ```bash - nmcli device show eno1 - ``` - - :::image type="content" source="images/mcc-isp-nmcli.png" alt-text="Screenshot of a sample output of nmcli command to show network adapter information." lightbox="./images/mcc-isp-nmcli.png"::: - -1. Open or create the Docker configuration file used to configure the DNS server. - - ```bash - sudo nano /etc/docker/daemon.json - ``` - -1. Paste the following string into the **daemon.json** file, and include the appropriate DNS server address. For example, in the previous screenshot, `IP4.DNS[1]` is `10.50.10.50`. - - ```bash - { "dns": ["x.x.x.x"]} - ``` - -1. Save the changes to daemon.json. If you need to change permissions on this file, use the following command: - - ```bash - sudo chmod 555 /etc/docker/daemon.json - ``` - -1. Restart Docker to pick up the new DNS setting. Then restart IoT Edge. - - ```bash - sudo systemctl restart docker - sudo systemctl daemon-reload - sudo restart IoTEdge - ``` - - - - - - - - -## Uninstalling Connected Cache - -In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls Connected Cache and all the related components. Before you run this script, contact the Connected Cache team. Only run it if you're facing issues with Connected Cache installation. - -> [!WARNING] -> Be cautious before running this script. It will also erase existing IoT workflows in this VM. - -The **uninstallmcc.sh** script removes the following components: - -- IoT Edge -- Edge Agent -- Edge Hub -- Connected Cache -- Moby CLI -- Moby engine - -To run the script, use the following commands: - -```bash -sudo chmod +x uninstallmcc.sh -sudo ./uninstallmcc.sh -``` - -## Appendix - -### Steps to obtain an Azure subscription ID - - -[!INCLUDE [Get Azure subscription](includes/get-azure-subscription.md)] - -### Performance of Connected Cache in virtual environments - -In virtual environments, the cache server egress peaks at around 1.1 Gbps. If you want to maximize the egress in virtual environments, it's critical to change the following two settings: - -1. Enable **SR-IOV** in the following three locations: - - - The BIOS of the Connected Cache VM - - The Connected Cache VM's network card properties - - The hypervisor for the Connected Cache VM - - Microsoft has found these settings to double egress when using a Microsoft Hyper-V deployment. - -2. Enable "high performance" in the BIOS instead of energy savings. Microsoft has found this setting nearly doubled egress in a Microsoft Hyper-V deployment. - -### Grant other users access to manage your Connected Cache - -More users can be given access to manage Microsoft Connected Cache, even if they don't have an Azure account. Once you've created the first cache node in the portal, you can add other users as **Owners** of the Microsoft Connected Cache resource group and the Microsoft Connected Cache resource. - -For more information on how to add other users as an owner, see [Grant a user access to Azure resources using the Azure portal](/azure/role-based-access-control/quickstart-assign-role-user-portal). Make sure to do this action for both the *Connected Cache resource* and *Connected Cache resource group*. + \ No newline at end of file