阿里云產(chǎn)品十一月刊 2024- 云端智慧點(diǎn)亮數(shù)字未來(lái)

卷首語(yǔ) 5 30 44 148 17255產(chǎn)品速遞模型上新模型特點(diǎn)模型表現(xiàn)77Qwen2.5-Turbo在長(zhǎng)文本、短文本任務(wù)評(píng)測(cè)集上均表現(xiàn)優(yōu)秀Qwen2.5-Turbo推理速度可提升4.3倍88API調(diào)用方式base_url="/compatible-mode)completion=client.chatmodel="qwen-turbo-latest",)針對(duì)于長(zhǎng)篇小說(shuō)理解針對(duì)于代碼倉(cāng)庫(kù)理解針對(duì)于多篇論文理解通義靈碼代碼解釋功能支持圖形化展示代碼邏輯??！地址：/r-spacex/SpaceX-API標(biāo)準(zhǔn)測(cè)評(píng)ITU-TF.AICP系列標(biāo)準(zhǔn)作為國(guó)內(nèi)唯一在ITU-TSG16阿里云人工智能平臺(tái)PAI產(chǎn)品介紹2.模型訓(xùn)練服務(wù)：PAI-DLC大規(guī)模分布式任務(wù)3.模型推理服務(wù)：PAI-EAS模型部署與在線服務(wù)、PAI-Blade推理加速5.AI與大數(shù)據(jù)一體化：智能標(biāo)注PAI-iTag、多種場(chǎng)景數(shù)據(jù)處理、AI血緣全鏈路追溯等6.企業(yè)級(jí)能力：工作空間與權(quán)限管理、資源與資產(chǎn)管理、安全與可信AI等器算力ACK集群對(duì)接方式Pod與集群中真實(shí)節(jié)點(diǎn)上的Pod之間網(wǎng)絡(luò)互通。建議前提條件v2.13.0-beta.2及以上(2)通過(guò)Label（/compute-class:計(jì)算類型）指定創(chuàng)建ACSPodkubectlkubectlgetnodevirtual-kubelet-）：apiVersionapiVersion:v1kind:Nodemetadata:labels:kubernetes.io/hostname:/exclude-node:"true"/ztopology.kubernetes.io/retopology.kubernetes.io/zoname:virtual-kubelet-cn-hangzhou-kspec:taints:apiVersionapiVersion:apps/v1kind:Deploymentmetadata:labels:app:nginxspec:selector:matchLabels:template:metadata:labels:spec:nodeSelector:tolerations:containers:image:/openanolis/nginx:1.14.1-8.6resources:limits:requests:預(yù)期輸出：deployment.apps/nginxcreated0virtual-kubelet-cn-han0virtual-kubelet-cn-hankubectlkubectldescribepodnginx-9cdf7bbf9-s****）：Annotations:Annotations:ProviderCreate:/client-token:///request-id:A0EF3BF3-37E7-5A07-AC2D-68A0CFC//user-id:kubernetes.io/preferred-scheduling-node:virtual-kubelet-cn-hangz輸出的Pod內(nèi)容中存在注解/instance-id:acs-2ze008giupcyaq為什么選擇操作系統(tǒng)控制臺(tái)功能特性集異常事件告警對(duì)異常事件進(jìn)行一鍵式診斷，并生成相應(yīng)的診斷報(bào)斷，能夠在實(shí)例級(jí)別進(jìn)行診斷并生成相應(yīng)的診斷報(bào)支持丟包診斷功能，具備實(shí)例級(jí)別的診斷能力，并夠在特定時(shí)長(zhǎng)及抖動(dòng)閾值下進(jìn)行診斷并生成相應(yīng)的進(jìn)程熱點(diǎn)追蹤用于單個(gè)實(shí)例在特定時(shí)刻的熱點(diǎn)分析。支持生成進(jìn)熱點(diǎn)對(duì)比分析用于單個(gè)實(shí)例在不同時(shí)刻、不同實(shí)例在同一或不同opilot命令輔助執(zhí)行腳本/代碼生成場(chǎng)景化系統(tǒng)支持查看組件的版本等相關(guān)信息，以及實(shí)例的安裝AlibabaClo對(duì)象存儲(chǔ)圖形化管理工具ossbrowser2.0發(fā)布新增功能/規(guī)格云盤簡(jiǎn)介云盤優(yōu)勢(shì)應(yīng)用場(chǎng)景傳統(tǒng)的數(shù)據(jù)庫(kù)部署方案是通過(guò)主備復(fù)制實(shí)現(xiàn)跨可用區(qū)的高可用/容災(zāi)，該方案存在主備計(jì)費(fèi)說(shuō)明使用限制地域限制實(shí)例規(guī)格限制功能限制云盤基本功能創(chuàng)建/查看/修改/釋放是是云盤共享掛載是云盤異步復(fù)制創(chuàng)建快照/快照極速可用是是是否是是是否ESSD同城冗余云盤僅支持作為數(shù)據(jù)是是否否否云盤性能50,000/2,30024使用ESSD同城冗余云盤創(chuàng)建ESSD同城冗余云盤通過(guò)ESSD同城冗余云盤實(shí)現(xiàn)容災(zāi)恢復(fù)城多活、異地多活容災(zāi)多集群網(wǎng)關(guān)概述產(chǎn)品架構(gòu)負(fù)載均衡和MSE云原生網(wǎng)關(guān)兩種類型的多集群網(wǎng)關(guān)。網(wǎng)關(guān)詳細(xì)信息及對(duì)比請(qǐng)參見(jiàn)產(chǎn)品優(yōu)勢(shì).毫秒級(jí)/秒級(jí)Fallback，在某個(gè)集群后端發(fā)生故障時(shí)，多集群網(wǎng)關(guān)能夠平滑地將流多集群網(wǎng)關(guān)關(guān)類型支持協(xié)議提交工單聯(lián)系容器支持后端服務(wù)B混合云/跨云多活使用以要使用云企業(yè)網(wǎng)打多容災(zāi)（支持Under下類型集lay和Overlay容群網(wǎng)關(guān)要使用專線打通網(wǎng)E關(guān)同城多活/主備容混合云/跨云容災(zāi)（支持UnderlayMSE多集群網(wǎng)關(guān)默下對(duì)多個(gè)集群進(jìn)行要對(duì)同一地域中不過(guò)云企業(yè)網(wǎng)將兩個(gè)暫不支持跨地域的暫不支持Overlay支持后端服務(wù)使用以下類型普通實(shí)例快速入門構(gòu)建同城容災(zāi)系統(tǒng)容災(zāi)概述.跨地域多活容災(zāi)：跨地域多活容災(zāi)對(duì)于網(wǎng)絡(luò)延遲相對(duì)較高，但可以防范地域性質(zhì)的功能優(yōu)勢(shì)方案架構(gòu)前提條件步驟一：使用GitOps或應(yīng)用分發(fā)部署應(yīng)用到多個(gè)集群(2)在多集群應(yīng)用頁(yè)面左上角，單擊艦隊(duì)名稱后的按鈕，在下拉列表中選擇目標(biāo)艦apiVersionapiVersion:argoproj.io/v1alpha1kind:ApplicationSetmetadata:namespace:argocdspec:template:metadata:name:'{{.metadata.annotations.cluster_ispec:destination:source:repoURL:/AliyunContainerService/gitopath:manifests/helm/wehelm:valueFiles:parameters:value:'{{.metadata.annotations.clustersyncPolicy:syncOptions:generators:-clusters:selector:matchExpressions:-values:-values:goTemplateOptions:syncPolicy:步驟二：在艦隊(duì)中通過(guò)kubectl創(chuàng)建ALB多集群網(wǎng)關(guān)apiVersionapiVersion:/v1kind:AlbConfigmetadata:annotations:alb.ingress.kubernetes.io/remote-clusters:${cluster1},${cluster2}spec:config:zoneMappings:listeners:protocol:HTTP---apiVersiIngressClassmetadata:name:albspec:controller:ingress.parameters:metadata.na是metadata.analb.ingress.kubernetes.io/是表。此處所填的是已經(jīng)關(guān)聯(lián)到艦隊(duì)實(shí)例的集spec.config.n否spec.config.a否應(yīng)用型負(fù)載均衡通過(guò)綁定彈性公網(wǎng)IP進(jìn)行spec.config.z是spec.listeners否監(jiān)聽(tīng)定義了流量進(jìn)入負(fù)載均衡的方式和規(guī)kubectlkubectlgetalbconf-ojsonpath='{.status.loadBalancer.subClusters}'步驟三：使用Ingress實(shí)現(xiàn)同城容災(zāi)。多個(gè)alb.ingress.kubernetes.io/cluster-wei。通過(guò)域名下的/svc1路由規(guī)則暴露后端服務(wù)service1。請(qǐng)先替apiVersionapiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:alb.ingress.kubernetes.alb.ingress.kubernetes.io/cluster-weight.${cluster1-id}:"20"alb.ingress.kubernetes.io/cluster-weight.${cluster2-id}:"80"namespace:gateway-demospec:rules:http:paths:backend:service:port:步驟四：驗(yàn)證同城多活容災(zāi)效果alb-xxxx.<regionid>.:<liste:8001/svc1;某個(gè)集群應(yīng)用異常時(shí)流量自動(dòng)平滑遷移:8001/svc1構(gòu)建混合云容災(zāi)系統(tǒng)混合云同城容災(zāi)系統(tǒng)架構(gòu)創(chuàng)建混合云同城容災(zāi)系統(tǒng)流程如果您的注冊(cè)集群需要將工作負(fù)載彈性地遷移到云上，請(qǐng)參見(jiàn)構(gòu)建混合彈性容器集群apiVersionapiVersion:argoproj.io/v1alpha1kind:ApplicationSetmetadata:namespace:argocdspec:template:metadata:name:'{{.metadata.annotations.cluster_ispec:destination:source:repoURL:/AliyunContainerService/gitopath:manifests/helm/wehelm:valueFiles:parameters:value:'{{.metadata.annotations.clustersyncPolicy:syncOptions:generators:-clusters:selector:matchExpressions:-values:-values:goTemplateOptions:syncPolicy:apiVersionapiVersion:argoproj.io/v1alpha1kind:ApplicationSetmetadata:namespace:argocdspec:template:metadata:name:'{{.metadata.annotations.cluster_id}}-web-spec:destination:source:repoURL:/AliyunContainerService/gitopath:manifests/helm/wehelm:valueFiles:parameters:value:"{{.values.isNodePort}}"value:'{{.metadata.annotations.clustersyncPolicy:syncOptions:generators:-clusters:selector:matchLabels:values:-clusters:selector:matchLabels:values:goTemplateOptions:syncPolicy:ALB多集群網(wǎng)關(guān)求轉(zhuǎn)發(fā)到后端Service中。它由應(yīng)用型負(fù)載均衡ALB完全托管。相比于NginxapiVersionapiVersion:/v1kind:AlbConfigmetadata:annotations:alb.ingress.kubernetes.io/remote-clusters:${cluster1},${cluster2}spec:config:zoneMappings:listeners:是metadata.annotations：alb.ingress.kubernetes.io/remo是集群列表。此處所填的是已經(jīng)關(guān)聯(lián)到否spec.config.addressType否公網(wǎng)提供應(yīng)用型負(fù)載均衡服務(wù)，公網(wǎng)例將收取彈性公網(wǎng)IP的實(shí)例費(fèi)與帶提供應(yīng)用型負(fù)載均衡服務(wù)，公網(wǎng)不可是應(yīng)用型負(fù)載均衡支持多可用區(qū)部署，spec.listeners否監(jiān)聽(tīng)定義了流量進(jìn)入負(fù)載均衡的方式您需要另行創(chuàng)建監(jiān)聽(tīng)才可使用ALBI管理南北流量apiVersionapiVersion:/v1kind:AlbConfigmetadata:annotations:alb.ingress.kubernetes.io/remote-clusters:${cluster1},${cluster2}spec:config:zoneMappings:listeners:protocol:HTTP---apiVersiIngressClassmetadata:name:albspec:controller:ingress.parameters:是否是metadata.annotatioalb.ingress.kubernetes.io/remote-clusters是表示待添加到ALB多集群網(wǎng)關(guān)的關(guān)否spec.config.addressT否）：應(yīng)用型負(fù)載均衡通過(guò)綁定彈性公網(wǎng)Ispec.config.zoneMa是指定的交換機(jī)必須在ALB當(dāng)前所支spec.listeners否監(jiān)聽(tīng)定義了流量進(jìn)入負(fù)載均衡的方則您需要另行創(chuàng)建監(jiān)聽(tīng)才可使用ALkubectlkubectlgetalbconf-ojsonpath='{.status.loadBalancer.subClusters}'apiVersionapiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:alb.ingress.kubernetes.namespace:demospec:rules:http:paths:backend:service:port:通過(guò)alb.ingress.kubernetes.io/cluster-weight.{clusapiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:alb.ingress.kubernetes.alb.ingress.kubernetes.io/cluster-weight.c63a55242bnamespace:demospec:rules:http:paths:backend:service:port:通過(guò)alb.ingress.kubernetes.io/cluster-weight.{clusterID}動(dòng)態(tài)通過(guò)alb.ingress.kubernetes.io/condition.{}動(dòng)態(tài)注解來(lái)注apiVersionapiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:alb.ingress.kubernetes.|"key":"stage",]}alb.ingress.kubernetes.io/cluster-weight.c63a55242bnamespace:demospec:rules:http:paths:backend:service:port:通過(guò)alb.ingress.kubernetes.io/cluster-weight注解對(duì)多后端服務(wù)進(jìn)行流量分配，權(quán)apiVersionapiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:alb.ingress.kubernetes.alb.ingress.kubernetes.io/cluster-weight.c63a55242balb.ingress.kubernetes.io/cluster-weight.cd174e5d93namespace:demospec:rules:http:paths:backend:service:port:實(shí)現(xiàn)多集群gRPC服務(wù)的路由轉(zhuǎn)發(fā).已獲取到可信的數(shù)字證書。您可以如果您暫未擁有證書，您可參照此步驟生成自簽名證書，示例中使用grpc.(1)創(chuàng)建并拷貝以下內(nèi)容至/tmp/f文件中。distinguished_name=req_disbasicConstraints=CAkeyUsage=nonRepudiation,digitalSig"/C=CN/ST=Zhejiang/L=Hangzhou/O=A"(2)在多集群應(yīng)用頁(yè)面左上角，單擊艦隊(duì)名稱后的按鈕，在下拉列表中選擇目標(biāo)艦apiVersionapiVersion:argoproj.io/v1alpha1kind:ApplicationSetmetadata:namespace:argocdspec:template:metadata:name:'{{.metadata.annotations.clusterspec:destination:source:repoURL:/ivanpath:manifests/directorsyncPolicy:syncOptions:generators:-clusters:selector:matchExpressions:-values:-values:goTemplateOptions:syncPolicy:apiVersionapiVersion:/v1kind:AlbConfigmetadata:annotations:alb.ingress.kubernetes.io/remote-clusters:${cluster1},${cluster2}spec:config:zoneMappings:listeners:protocol:HTTPS---apiVersion:networking.k8s.io/v1kind:IngressClassmetadata:name:albspec:controller:ingress.parameters:對(duì)應(yīng)的alb.ingress.kubernetes.io/listen-ports。并且引用步書。apiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:alb.ingress.kubernetes.[{"HTTPS":443}]alb.ingress.kubernetenamespace:gateway-demospec:rules:http:paths:-backend:service:port:tls:-hosts:alb-*****grpcurl-insecure-authoritygrpc.reflection.v1alpha.Sgrpc.reflection.v1alpha.S管理網(wǎng)關(guān){{{"mse:AddBlackWhiteList","mse:AddGateway","mse:AddServiceSource","mse:CreateApplication","mse:DeleteGateway","mse:DeleteServiceSource","mse:GetBlackWhiteList","mse:GetGateway","mse:GetGatewayDetail","mse:GetGatewayOption","mse:ListServiceSource","mse:ListTagResources","mse:ModifyLosslessRule","mse:TagResources","mse:UntagResources","mse:UpdateBlackWhiteList","mse:UpdateGatewayOption","mse:UpdateServiceSourc{"log:CloseProductDataCollection","log:OpenProductDataCollection","log:GetProductDataCollectio"acs:mse:*:*:instance/*","acs:log:*:*:project/*/logstore/mse_{"Action":"ram:CreateServiceLinkedRole","audit.log.aliyuncs.co]}}<YOUR_FLEET_CLUSTERID>apiVersion:apiVersion:mse.alibabacloudMseIngressConfigmetad#annotations:#/r${cluster1},${cluster2}spec:common:instance:network:vSwitches:ingress:local:kubectlkubectlgetmseingresannotationsannotations:/remote-clusters:${cluster1-id},${cluster2管理南北流量背景信息.MSEIngress已支持Nginx-Ingress核心和常用的Annotation，并推出額外的.已開(kāi)啟多集群網(wǎng)關(guān)。annotationsannotations:/remote-clusters:${cluster1-id},${cluster2。RepositoryURL設(shè)置為/AliyunContainerService/gito。Path設(shè)置為manifests/helm/web-demoapiVersionapiVersion:apps/v1kind:Deploymentmetadata:labels:app.kubernetes.io/instance:namespace:web-demospec:selector:matchLabels:template:metadata:labels:spec:containers:image:-hangzhou.cr.aliyuple-clusters/web-demoenv:value:cluster1---apiVersion:v1kind:Servicemetadata:namespace:web-demospec:ports:selector:apiVersion:networking.k8s.io/v1kind:Ingressmetadata:namespace:web-demospec:rules:http:paths:backend:service:port:-ojsonpath="{.status.loadBalancer}"(1)使用以下內(nèi)容，創(chuàng)建ingress-demo-cluster-one.yaml文件。以下Ingress對(duì)象e-subset、mse.ingress.kubernetes.io/subset-labels以實(shí)現(xiàn)域名example.co。mse.ingress.kubernetes.io/service-subset：服務(wù)的子版本名稱。建議定義。mse.ingress.kubernetes.io/subset-labels：指定目標(biāo)集群的ID。apiVersionapiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:mse.ingress.kubernetes.io/service-subset:cluster-demse.ingress.kubernetes.io/subset-labeltopology.istio.io/clunamespace:web-demospec:rules:http:paths:backend:service:port:-ojsonpath="{.status.loadBalancer}"apiVersionapiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:mse.ingress.kubernetes.io/service-subset:cluster-demse.ingress.kubernetes.io/subset-labeltopology.istio.io/clustnginx.ingress.kubernetes.io/canary:"true"nginx.ingress.kubernetes.io/canary-by-header:"stage"nginx.ingress.kubernetes.io/canary-by-header-value:"gray"namespace:web-demospec:rules:http:paths:backend:service:port:-ojsonpath="{.status.loadBalancer}"執(zhí)行以下命令，查看流量的路由情況。替換以下XX.XX.XX.XX為上一步獲群網(wǎng)關(guān)管理了兩個(gè)關(guān)聯(lián)的ACK集群的流量，如果其中一個(gè)集群的服務(wù)異?；虮粍h除，-ojsonpath="{.status.loadBalancer}"執(zhí)行以下命令，查看流量的路由情況。替換以下XX.XX.XX.XX為上一步獲域名下的/svc1-w路由規(guī)則暴露后端服務(wù)service1。mse.ingress.kubernetes.io/service-subset：服務(wù)的子版本名稱。建議定義為與目標(biāo)。nginx.ingress.kubernetes.io/canary-weight：請(qǐng)求到該集群的流量百分比apiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:mse.ingress.kubernetes.io/service-subset:cluster-demse.ingress.kubernetes.io/subset-labeltopology.istio.io/cluster${clusnamespace:web-demospec:rules:http:paths:backend:service:port:number:80---apiVersion:networking.k8s.io/v1kind:Ingressmetadata:annotations:mse.ingress.kubernetes.io/service-subset:cluster-demse.ingress.kubernetes.io/subset-labelnginx.ingress.kubernetes.io/canary:"true"nginx.ingress.kubernetes.io/canary-weight:"10"namespace:web-demospec:rules:http:paths:backend:service: -ojsonpath="{.status.loadBalancer}"型實(shí)例已支持升級(jí)至7.0新增功能/規(guī)格可通過(guò)大版本升級(jí)功能將現(xiàn)存的Tair企業(yè)版內(nèi)存型5.0/6.0實(shí)例升級(jí)至7.0云上實(shí)踐2.運(yùn)行環(huán)境要求模型部署和調(diào)用模型微調(diào)訓(xùn)練[[{的實(shí)施體育運(yùn)動(dòng)和鍛練高血壓的患者還應(yīng)當(dāng)在醫(yī)生的指導(dǎo)下口服降血{}][[{hurtyourself,mentallyorphysically."{}模型評(píng)測(cè)[{"question":"請(qǐng)問(wèn)室溫超導(dǎo)技術(shù)的難點(diǎn)在哪里,人類在什么時(shí)候可以實(shí)現(xiàn)室溫超導(dǎo)?",的材料或者理論模型，通過(guò)現(xiàn)有的技術(shù)制備高質(zhì)量的樣品也是非常困難出一個(gè)確切的時(shí)間表。室溫超導(dǎo)是物理學(xué)中的一個(gè)激動(dòng)人心但又極具挑屬指的是地殼中含量較少、分布不均或開(kāi)采困難的金屬扮演著非常重要的角色。全球需求的排序可能因時(shí)間和技術(shù)查爺爺是否有呼吸和脈搏：\n-如果沒(méi)有模型壓縮戶可以更加輕松地部署和優(yōu)化這些模型。本解決方案從全方位解析了在PAI平臺(tái)使用相關(guān)資源鏈接DistilQwen2介紹：/article/1633882阿里云人工智能平臺(tái)PAI：/product/bigdata/learnPAI快速開(kāi)始：/zh/pai/user-guide/quick-start-overvie使用社區(qū)開(kāi)源的redis、postgres以及weaviate。如果您對(duì)這些基礎(chǔ)組件有更高的性enabled、postgresql.enabled、weaviate.enabled均設(shè)置為false。externalRedis:host:"r-***********.redis.rds.aliyuncs.coport:username:password:externalPostgres:address:"pgm-*********."externalAnalyticDB:instanceId:"gp-*************"accountPassword:"********"namespacePassword:"difyhelmPassword"worker.replicas:22.副本打散:為了避免單節(jié)點(diǎn)、或者單az故障對(duì)應(yīng)用整體服務(wù)不可用，我們通常需要apiapi.affinity:podAntiAffinity:preferredDuringSchedulingIgnoredDuringExecution:podAffinityTerm:labelSelector:matchExpressions:values:worker.affinity:podAntiAffinity:preferredDuringSchedulingIgnoredDuringExecution:podAffinityTerm:labelSelector:matchExpressions:values:web.affinity:podAntiAffinity:preferredDuringSchedulingIgnoredDuringExecution:podAffinityTerm:labelSelector:matchExpressions:values:sandbox.affinity:podAntiAffinity:preferredDuringSchedulingIgnoredDuringExecution:podAffinityTerm:labelSelector:matchExpressions:values:woker:woker:autoscaling:metrics:resource:target:NODENOMINATEDNOD86cn-hangzhou.192.1cn-hangzhou.0<78cn-hangzhou.192.83cn-hangzhou.192.3cn-hangzhou.0<00ack-dify-workerDeployment/ack-dify-workermemory:ingressingress:#nginx.ingress.kubernetes.io/#nginx.ingress.kubernetes.i#nginx.ingress.kubernetes.io/ssl