当前位置: 首页 > 软件库 > 云计算 > 云原生 >

acs-engine

WE HAVE MOVED: Please join us at Azure/aks-engine!
授权协议 MIT License
开发语言 Google Go
所属分类 云计算、 云原生
软件类型 开源软件
地区 不详
投 递 者 陆绪
操作系统 跨平台
开源组织
适用人群 未知
 软件概览

Pardon our Dust!

This codebase has been deprecated in favor of aks-engine, the natural evolution from acs-engine:

https://github.com/Azure/aks-engine

All future development and maintenance will occur there as an outcome of this deprecation. We're sorry for any inconvenience!

We've moved the Kubernetes code over 100% as-is (with the exception of the boilerplate renaming overhead that accompanies such a move); we're confident this housekeeping manouver will more effectively track the close affinity between the AKS managed service and the "build and manage your own configurable Kubernetes" stories that folks use this tool for.

See you at https://github.com/Azure/aks-engine!

The historical documentation remains below.

Microsoft Azure Container Service Engine - Builds Docker Enabled Clusters

Overview

The Azure Container Service Engine (acs-engine) generates ARM (Azure Resource Manager) templates for Docker enabled clusters on Microsoft Azure with your choice of DC/OS, Kubernetes, OpenShift, Swarm Mode, or Swarm orchestrators. The input to the tool is a cluster definition. The cluster definition (or apimodel) is very similar to (in many cases the same as) the ARM template syntax used to deploy a Microsoft Azure Container Service cluster.

The cluster definition file enables you to customize your Docker enabled cluster in many ways including:

  • Choice of DC/OS, Kubernetes, OpenShift, Swarm Mode, or Swarm orchestrators
  • Multiple agent pools where each agent pool can specify:
    • Standard or premium VM Sizes, including GPU optimized VM sizes
    • Node count
    • Virtual Machine ScaleSets or Availability Sets
    • Storage Account Disks or Managed Disks
    • OS and distro
  • Custom VNET
  • Extensions

More info, including a thorough walkthrough is here.

User guides

These guides show how to create your first deployment for each orchestrator:

These guides cover more advanced features to try out after you have built your first cluster:

Usage

Generate Templates

Usage is best demonstrated with an example:

$ vim examples/kubernetes.json

# insert your preferred, unique DNS prefix
# insert your SSH public key

$ ./acs-engine generate examples/kubernetes.json

This produces a new directory inside _output/ that contains an ARM template for deploying Kubernetes into Azure. (In the case of Kubernetes, some additional needed assets are generated and placed in the output directory.)

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

  • root@debian1:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 8 (jessie)" NAME="Debian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=debian HOME_URL="http://www.debian.org/" SUPPORT_URL="http:

  • Cisco Secure Access Control System (ACS) 5.2 and User Change Password (UCP) As the ACS evolved, one of the less known features of ACS has also evolved at a significant level: User Change Password (UCP

  • 解决方法0: $ ps axf | grep docker | grep -v grep | awk '{print "kill -9 " $1}' | sudo sh  $ nohup dockerd & 解决方法1: $ ps axf | grep docker | grep -v grep | awk '{print "kill -9 " $1}' | sudo sh  $ sudo sys

 相关资料
  • AKS Engine - Units of Kubernetes on Azure! Project status This project is stable, meaning the pace of new features is intentionally low. AKS Engine is maintained by teams who depend on it including AK

  • Azure Kubernetes Service (AKS) Baseline Cluster This reference implementation demonstrates the recommended starting (baseline) infrastructure architecture for a general purpose AKS cluster. This imple

  • Azure Container Hackfest Delivering modern cloud native applications with ​open source technologies on Azure​ NOTE: We have moved this content over to a new and updated repository https://github.com/A

  • 我正试图让Shibboleth SP在我的实验室中使用OneLogin[SAML测试连接器(IdP w/attr)]。我能够使用testshib IdP实现所有功能,但当我更改元数据提供程序并更新SSO实体ID时,我只收到以下错误: 随POST一起传递到错误服务器URL的SAML邮件 当查看我的元数据文件时,我看到我的ACS是: 超文本传输协议://testserver/Shibboleth.ss

  • 我们在Azure中实现Web应用程序和主机。然后我们希望使用Microsoft Azure ACS支持的SSO功能。查看我们网站的条件是用户只需在整个登录IdP过程中提供电子邮件地址。当我们实施和配置Web应用程序时,我们会按照网站上的所有说明进行操作,如下所示http://blog.2mas.xyz/configuring-windows-azure-active-directory-acces

  • 这是我的secret-class.yml文件(keyvault的名称是正确的)。另外,xxx-xxxx-xxx-xxx-xxx-xxx-xxx-xxx-xxx4b5ec83是AKS托管标识(SonarQubeHelm-agentpool)的对象 这是我的deployment.yml文件 我为AKS托管标识分配了正确的权限,以便访问keyvault(XXX-XXXXX-XXX-XXX-XXXX4B5