from https://purple.telstra.com.au/blog/how-to-deploy-docker-images-to-azure-kubernetes-services-aks In this blog, I will guide you through the process of building and deploying Docker images to the Kubernetes platform hosted on Azure Kubernetes Services (AKS). In addition, I will also show you how to work with service scale-out and high-availability. Docker defines a container as “A standard unit of software that packages up code and all its dependencies, so the application runs quickly and reliably from one computing environment to another” A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.” I will not go further into the concepts of Docker and containers and urge you to do your own reading. To build out our solution, we will need to do the following   Create an Azure container Registry (ACR) Create an Azure Service principal

With Azure File Sync we can make on-premises windows server to act as a cache copy holder for your Azure file share.  It allows users to access files locally using protocol such as SMB, NFS and FTPS. In this blog we going to look in to Azure file sync implementation. Before we start configuration, we need to familiarizes with some terms associated with this feature.  Azure File Sync Agent It is an agent which we need to install in on-premises windows server in order to enable sync with Azure file share. It includes three components,  1. FileSyncSvc.exe – This is the service responsible for monitoring changes in local server initiate sync with Azure file share.  2. StorageSync.sys – This component is responsible for tiering files to Azure files. Cloud tiering is additional feature of Azure File Sync. It can use with not frequently used files greater than 64Kb. When this enabled, local file replaced with url to files in Azure file share. When user access it, in background it recalls the file from Azure file share. End user will not have any difference experience as it all happens in back end.  3. PowerShell cmdlets – This helps to manage Microsoft.StorageSync Azure resource provider using PowerShell commands. These cmdlet files are located in C:\Program Files\Azure\StorageSyncAgent\StorageSync.Management.PowerShell.Cmdlets.dll C:\Program Files\Azure\StorageSyncAgent\StorageSync.Management.ServerCmdlets.dll This agent is only supported in Windows server 2012 R2 / 2016 standard and datacenter versions only. It is not supported on core version either.  Storage Sync

https://www.cnblogs.com/cocowool/p/k8s_base_concept.html Kubernetes是什么 Kubernetes是当今最流行的开源容器管理平台，它就是大名鼎鼎的Google Borg的开源版本。Google在2014年推出了Kubernetes，本文发布时最新的版本是1.11。Kubernetes源于希腊语，意为舵手，K8S是一个简称，因为首尾字母中间正好有8个字母。基于容器技术，Kubernetes可以方便的进行集群应用的部署、扩容、缩容、自愈机制、服务发现、负载均衡、日志、监控等功能，大大减少日常运维的工作量。 Kubernetes is primarily targeted at applications composed of multiple containers. It therefore groups containers using pods and labels into tightly coupled and loosely coupled formations for easy management and discovery. Kubernets所有的操作都可以通过Kubernetes API来进行，通过API来操作Kubernetes中的对象，包括Pod、Service、Volume、Namespace等等。Kubernetes的整体结构如下图所示： Master 也叫做 Cluster Control Plane。 Node Node 可以是一个物理机也可以是虚拟机，每个节点上都运行了可以运行 Pods 的服务。通过Master节点来进行管理。节点实际上是由云供应商提供的，Kubernetes管理中创建节点实际上只是在Kubernetes中创建一个代表节点的对象。 Node 包含以下几方面的信息： Addresses：包括主机名、内部IP、外部IP。 Condition：描述运行的状态，包括OutOfDisk、Ready、MemoryPressure、PIDPressure、DiskPressure、NetworkUnavailable、ConfigOK。 Capacity：描述节点资源的情况，包括CPU, memory and the maximum number of pods that can be scheduled onto the node. Info：包括内核版本、Kubernetes版本、Docker版本、OS等基础信息。 Kubernetes 对象 Objectes

add Windows Performance Counters Process(*)\ID Process     Perf | where ObjectName == "Process"   and CounterName == "ID Process"  // | where CounterName contains "Processor Time"   | where Computer == "pc-vm-websrv1"  // | where  Computer == "pc-vm-logicsrv2"  // | where  Computer == "pc-vm-dbsrv3"  // | distinct  InstanceName  | where InstanceName == "fdm" or InstanceName =="sakura"  or InstanceName =="7zFM"        | summarize arg_max(TimeGenerated, *) by Computer, InstanceName   | project TimeGenerated, Computer, ProcessName = InstanceName  | order by TimeGenerated desc  A common question when working with Azure Monitor is monitoring of Windows services and processes running on Windows servers. In Azure Monitor we can monitor Windows Services and other processes the same way; by looking at process ID as a performance counter. Even if a process can be monitored by looking at events, it is not always a reliable source. The challenge is that there is no “active monitoring” checking if the process is running at the moment when looking at only events.  Each process writes a number of performance counters. None of these are collected by default in Azure Monitor, but easy to add under Windows Performance Counters.

from: https://www.cloudsma.com/2018/07/adding-azure-log-analytics-performance-counters/ https://techcommunity.microsoft.com/t5/azure-monitor/monitoring-processes/m-p/250947# First, in your Azure Portal Log Analytics workspace, go to advanced settings, Data, Windows Performance Counters. Note you can do the same for Linux, but this example covers Windows. Click add to add the default suggested counters. You’ll see them added with purple lines, meaning they haven’t been saved to your workspace yet. Also note, depending on your subscription type, the sample rate can be as high as 10 seconds. You can certainly tune these to different intervals, just be aware that these are global settings. Adding Additional Counters

form https://www.cloudsma.com/2020/01/azure-monitor-alerting-at-scale-iaas/ In this post I will expand upon the methods I showed here and show you how I do IaaS Alerting in Azure Monitor. As a refresher I believe alerting at scale is: Programmatic Alert Creation Automatically adds/removes resources Having read my previous posts you’ll also know that I prefer a Log Analytics workspace for Metric alerts. I prefer this for a few reasons, which I’ll go into below. PowerShell Modules and Commands To create our alerts we’ll need the following modules: Az.Monitor Az.OperationalInsights We’ll also need the following commands:

ExpandProperty http://www.datawan.net/web/index.php/cloud/45-powershell-expandproperty As most of you already know the "-ExpandProperty" parameter let's you enumerate the values of an incoming object as single value.  For example, if you run the command below without the "-ExpandProperty". Get-AzLocalNetworkGateway -ResourceGroupName "network-rg" You will get output like this:↓↓↓↓↓ Name                     : my-lng ResourceGroupName        : network-pd-rg Location                 : southcentralus Id                       : /subscriptions/GUID/resourceGroups/network-pd-rg/providers/Microsoft.Network/localNetworkGateways/qco-houdc-lng Etag                     : W/"GUID" ResourceGuid             : GUID ProvisioningState        : Succeeded Tags                     : ・・・ GatewayIpAddress         : 4.50.4.28 LocalNetworkAddressSpace : {                              "AddressPrefixes": [                                "10.100.0.0/16",                                "10.101.0.0/16",                                "10.102.0.0/16",                                "10.103.0.0/16",                                "10.104.0.0/16",                              ]                            } BgpSettings              : null But what if you just want a simple list of all LocalNetworkAddressSpace?  You can use -ExpandProperty but the trick is you have to use it twice!  See sample below.  If you only pass it once you will still not get desired list, you must expand the properties two times because the expanded property is a list in this case. Get-AzLocalNetworkGateway -ResourceGroupName "network-rg" | Select -ExpandProperty LocalNetworkAddressSpace | Select -ExpandProperty AddressPrefixes | FT

爱奇艺 iqiyi.com qiyi.com aiqiyicloud.com qiyi.cn 谷歌关联 start----------------------- google.com findyoutube.net/ googlevideo.com/ ytimg.com/ youtube.com/ googleapis.com/ youtu.be gstatic.com googleusercontent.com googlevideo.com youtu.be youtube.com.br youtube.co.nz youtube.de youtube.es youtube.googleapis.com youtubei.googleapis.com youtube.it youtube.nl youtube-nocookie.com youtube.ru video-stats.l.google.com ytimg.l.google.com rewind.youtube blog.youtube 谷歌关联 end-----------------------

https://stackoverflow.com/questions/39657391/login-azurermaccount-cant-login-to-azure-using-pscredential/39675182#39675182 Atf's answer has a point but however, this is not only the issue. We cannot directly sign in non-interactively using Hotmail or Outlook account. You must use domain of your account to sign in. See a similar issue posted in server fault : https://serverfault.com/questions/746557/add-azureaccount-unknown-user-type-unknown-user-type-on-azure-automation/746673 It mentions: Make sure the credential asset name (not username) is a simple string. Also make sure the credential asset username is a valid OrgID user (ex: abc@fdgdf.onmicrosoft.com), not a Microsoft / Live account (joe@gmail.com).

性能测试工具LoadRunner32-LR之windows性能监控Perfmon Perfmon是啥？ 　　Perfmon提供了图表化的系统性能实时监视器、性能日志和警报管理，可以用于监视CPU使用率、内存使用率、硬盘读写速度、网络速度等   性能分析方法 　内存分析方法 　　内存分析用于判断系统有无内存瓶颈，是否需要通过增加内存等手段提高系统性能表现。 　　主要方法和步骤： 　　1.首先查看Memory:%Committed Bytes in Use指标 　　　　如果该指标比例比较大，系统可能出现了内存方面的问题，需要继续下面步骤进一步分析。另外也可以查看Available Bytes，如果该值小说明可用内存不足，存在性能瓶颈。 　　2.注意Pages/sec、Pages Read/sec和Page Faults/sec的值 　　　　操作系统会利用磁盘较好的方式提高系统可用内存量或者提高内存的使用效率。这三个指标直接反应了操作系统进行磁盘交换的频度。 　　　　Pages/sec值持续高于几百，可能有内存问题。Pages/sec值不一定大就表明有内存问题，可能是运行使用内存映射文件的程序所致。 　　　　Page Faults/sec说明每秒发生页面失效次数，页面失效次数越多，说明操作系统向内存读取的次数越多。此时需要查看Page Read/sec的计数值，该计数器的阀值为5，如果计数值超过5，则可以判断存在内存方面的问题。   处理器分析方法 　　1.首先看System：%Total Processor Time性能计数器的计数值  　　　　该计数器的值提现服务器整体处理器利用率，对多处理器的系统而言，该计数器提醒所有CPU的平均利用率。如果该值持续超过90%，则说明整个系统面临着处理器方面的瓶颈，需要通过增加处理器来提高性能。 　　2.其次查看每个CPU的%User Time 　　　　%User Time是系统非核心操作消耗的CPU时间，如果该值较大，可以考虑是否能通过友好算法等方法降低这个值。如果该服务器是数据库服务器，%User Time值大的原因很可能是数据库的排序或是函数操作消耗了过多的CPU时间，此时可以考虑对数据库系统进行优化。  　　3.研究系统处理器瓶颈  　　　　查看System:Processor Queue Length计数器的值，当该计数器的值大于CPU数量的总数+1时，说明产生了处理器阻塞。在处理器的%Process Time很高时，一般都随处理器阻塞，但产生处理器阻塞时，Processor：%Processor Time计数器的值并不一定很大，此时就必须查找处理器阻塞的原因。    磁盘I/O分析方法 　　1.计算每磁盘的I/O数 　　　　每磁盘的I/O数可用来与磁盘的I/O能力进行对比，如果经过计算得到的每磁盘I/O数超过了磁盘标称的I/O能力，则说明确实存在磁盘的性能瓶颈。