Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Herding Cattle with Azure Container Service (ACS)

5.875 Aufrufe

Veröffentlicht am

Your pet program has been containerized and is now part of the herd of microservices that work together to deliver a high quality production application. Spinning up containers on Docker hosts was the easy part, but everyone knows your application is as vulnerable as its weakest link. Having a single host isn't going to work. Although myriad options exist to orchestrate containers across hosts, including DC/OS, Docker Swarm, and Kubernetes, someone has to allocate the resources, configure the hosts and stand up the virtual environment. The open source Azure Container Services engine works with these popular orchestration tools to manage clusters and infrastructure to make it easier to, well, herd cattle. Learn about ACS, how to get up and running with a cluster that is ready to address elasticity and fail-over in minutes, and how ACS works with existing open source tools like Kubernetes (K8S) to give you a well known path to manage your application while easing management of the underlying infrastructure.

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Herding Cattle with Azure Container Service (ACS)

  1. 1. One ring to rule them all …
  2. 2. https://aka.ms/acsinfo https://github.com/Azure/acs- engine
  3. 3. az acs create -n my-acs-instance -g my-resource- group -t dcos -d my-host -l westus --generate-ssh- keys --agent-count 3 --agent-vm-size Standard_D2_V2
  4. 4. Click Here
  5. 5. az acs create -n my-acs-swarm -g my-resource-group -t swarm az acs create -n my-acs-swarm -g my-resource-group
  6. 6. https://aka.ms/acsinfo https://cloudacademy.com/azu re/introduction-to-azure- container-service-acs-course/ http://bit.ly/coderblog @JeremyLikness