azure redhat vm初期设置 重置root用户密码 sudo passwd root 切换到root用户 查看主机信息 [root@pc-vm-dbsrv3 src]# hostnamectl    Static hostname: pc-vm-dbsrv3          Icon name: computer-vm            Chassis: vm         Machine ID: 7fef26f2ae4642a19e8c1bdde589500e            Boot ID: 2c4aa41a19454d41a1bd77bcbeb2fcac     Virtualization: microsoft   Operating System: Red Hat Enterprise Linux 8.1 (Ootpa)        CPE OS Name: cpe:/o:redhat:enterprise_linux:8.1:GA             Kernel: Linux 4.18.0-147.32.1.el8_1.x86_64       Architecture: x86-64 [root@pc-vm-dbsrv3 src]# 查看timezone timedatectl >>[root@pc-vm-dbsrv3 log]# timedatectl >>               Local time: Sun 2020-12-06 11:25:13 UTC >>           Universal time: Sun 2020-12-06 11:25:13 UTC >>                 RTC time: Sun 2020-12-06 11:25:13 >>                Time zone: Etc/UTC (UTC, +0000) >>System clock synchronized: yes >>              NTP service: active >>          RTC in local TZ: no >> 列出所有timezone timedatectl list-timezones 修改timezone timedatectl set-timezone Asia/Tokyo 在开始安装之前，确保正在运行最新版本的RHEL 8 系统。您可以运行yum update命令以获取最新更新。 sudo yum -y update sudo systemctl reboot 安装repos前确认启用的存储库列表。 sudo dnf repolist >>[root@pc-vm-dbsrv3 ~]# sudo dnf repolist >>Last metadata expiration check: 0:02:31 ago on Sun 06 Dec 2020 09:35:43 AM UTC. >>repo id                                                 repo name                                                                                                  status >>microsoft-azure-rhel8-eus                               Microsoft Azure RPMs for RHEL8 Extended Update Support                                                         3 >>rhel-8-for-x86_64-appstream-eus-rhui-rpms               Red Hat Ent

Azure SQL Database is a PaaS offering and therefore some of its features differ from the on-premises SQL Server. Some of the important features that differ are as follows: Backup and Restore Conventional database backup and restore statements aren't supported. Backups are automatically scheduled and start within a few minutes of the database provisioning. Backups are consistent, transaction-wise, which means that you can do a point-in-time restore. There is no additional cost for backup storage until it goes beyond 200% of the provisioned database storage. You can reduce the backup retention period to manage backup storage costs. You can also use the long-term retention period feature to store backups in the Azure vault for a much lower cost for a longer duration. Apart from automatic backups, you can also export the Azure SQL Database bacpac or dacpac file to Azure storage. Recovery Model The default recovery model of an Azure SQL database is FULL and it can't be modified to any other recovery model as in on-premises recovery models. The recovery model is set when the master database is created, meaning when an Azure SQL server is provisioned, the recovery model can't be modified because the master database is read-only. To view the recovery model of an Azure SQL database, execute the following query: SELECT name, recovery_model_desc FROM sys.databases;

Azure SQL Database brought many new features to SQL Server. Features such as Dynamic Data Masking, Always Encrypted, Row-Level Security, Query Store, and more. However, Azure SQL Database was built on a database scoped configuration model and has certain limitations compared to on-premises SQL Server. With the introduction of Managed Instance, we see most of those limitations removed. Managed Instance helps bridge the gap between Azure SQL Database and on-premises SQL Server due to being built on an instance scoped configuration model. In this session, we compare Azure SQL Database and Managed Instance in relation to on-premises functionality so that you will get a solid understanding of what Managed Instance has to offer. What is Azure SQL Managed Instance? https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview

https://zhuanlan.zhihu.com/p/95147895 过去10年间，企业在经历了公有云的洗礼之后，从需求的角度重新衡量了“云”与业务的关系，上云并不是目的，而是提升业务创新或是效率的方式，上云并不是万能的，用合理的方式上云成为企业的共识。 这就是混合云存在的意义。 在2019年的Ignite大会上， 微软CEO Satya发布了一系列Azure新的混合云产品和服务， 而混合和多云平台Azure Arc无疑是最重磅的产品， 在Keynote里宣布了产品的公测及微软在混合云方面新的战略方向。至此在混合云的技术栈里微软不仅拥有了Azure Stack和IoT Edge， Azure云平台可以和任何数据中心， 任何云环境内的服务器资源进行管理整合。 我们来了解下什么是Azure Arc？为什么福布斯会宣称这是微软一款改变了游戏规则的产品? Azure Arc是一系列的成熟技术， 它可以帮助用户将Azure云端成熟的管理功能扩展到任何的基础架构， 而且还能够将Azure的服务运行于本地数据中心， 跨云环境和边缘节点上。成功实现了将Azure的服务和管理带到任何的基础架构。 Azure Arc在第一版的发布中会共包含了三个功能模块， 分别为跨云服务器支持， 跨云容器支持和Azure数据库服务的跨云支持， 目前跨云服务器支持已经在Azure全球版（Global Azure）提供了公测， 另两个服务正在进行内测， 在不久的将来也会和公众见面。

from https://blog.csdn.net/thinktik/article/details/81165858 输入字符串表达式时，可以使用单引号(”)或双引号(“”)括住字符串，但PowerShell解析单引号和双引号中字符串的方式是不同的。更多请看（www.omob.cc） 一、单引号括住的字符串，字符串被精确地传递到命令，字符串中包含的任何表达式都不会被计算，只会被解释成文本。例如： $varA=200 Write-host 'The value of $varA is $varA.' 1 2 3 输出为： The value of $varA is $varA. 1 变量$varA不会被相应的值替换。 二、双引号括住的字符串，在字符串传递到命令执行前，变量名会被变量值替代，表达式也会被计算。例如： 例1： $varA=200 Write-host "The value of $varA is $varA." 1 2 3 输出为： The value of 200 is 200. 1 变量$varA相应的值200替换。 例2： "The value of $(100+100) is 200" 1 输出为： The value of 200 is 200. 1 表达式$(100+100)被计算，并且结果被插入字符串中。 要避免双引号中的字符串被变量值/表达式值替换，需要在变量名/表达式前使用反单引号()。例如： $varA=200 Write-host "The value of `$varA is $varA." 1 2 3 输出为： The value of $varA is 200. 1 三、如果字符串使用单引号括起来，同时被括起的字符串中包含单引号，则需使用两个单引号，例如： 'He doesn''t want to go home.' 1 如果字符串使用双引号括起来，同时被括起的字符串中包含双引号，则需使用两个双引号，例如： "He said, ""How are you?""" 1 当然，也可以使用反单引号(`)字符来强制PowerShell将单引号或双引号解释为文本，例如： "He doesn`'t want to go home." "He said, `"How are you?`""

https://qiita.com/dz_/items/508ce475cd267dbd950e https://stackoverflow.com/questions/47516018/creating-a-kubernetes-cluster-in-azure-fails 上記のエラーが発生したとき、 ${HOME}/.azure/acsServicePrincipal.json がある場合は、すでに Service Principal ができてるようです。 cat ${HOME}/.azure/acsServicePrincipal.json | jq {   "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx": {     "client_secret": "xxxxxxxxxxxxxxxxxxxx",     "service_principal": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"   } } Thanks for the feedback. I managed to resolve the issue by deleting my .azure folder and retrying. According to your error message, please do the follow steps to re-create AKS: 1.Check ${HOME}/.azure/.azure/acsServicePrincipal.json, find the service principal: [root@jasoncli@jasonye .azure]# pwd /root/.azure [root@jasoncli@jasonye .azure]# ls accessTokens.json  acsServicePrincipal.json  az.json  az.sess  azureProfile.json  clouds.config  config [root@jasoncli@jasonye .azure]# cat acsServicePrincipal.json {"5384xxxx-xxx-xxxx-xxxx-xxxxe29axxxx": {"client_secret": "6fc7cdff5eaf0axxxx8f", "service_principal": "6b73deca-xxxx-4a6d-ab54-73963cb78059"}} 2.Use this command to check your Service Principal, make sure the service principal exist or not: az ad sp show --id <service_principal> If the service principal not exist, we can follow this article to create it. If the service principal exist, we can follow specify the service principal and --client-secret to create AKS, like this: az aks create -g <resource_group>-n <aks name> --node-count 1 --service-principal <service_principal> --client-secret <client_secret> ----generate-ssh-key Hope this helps.

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.