Ansible : Playbooks, Inventory, Module index

Popular topics: (note1)

MaxthonSnap20170324170029

  • Module index (note2)

MaxthonSnap20170324170336 

  • Playbooks (note3)

Playbooks are Ansible’s configuration, deployment, and orchestration language. They can describe a policy you want your remote systems to enforce, or a set of steps in a general IT process. //其實就像是編劇的劇本

相當多, 需要什麼 再查什麼 (note3)

  • Inventory (note4)

MaxthonSnap20170324173010

 

(note1:http://docs.ansible.com/)

(note2:http://docs.ansible.com/ansible/modules_by_category.html)

(note3:http://docs.ansible.com/ansible/playbooks.html)

(note4:http://docs.ansible.com/ansible/intro_inventory.html)

 

廣告

Ansible

繼續

MaxthonSnap20170324084449

  • 架構

MaxthonSnap20170324084809

  • Playbooks

MaxthonSnap20170324085631

  • Variables

MaxthonSnap20170324085812

  • Answer Tower

ansible tower

先到這.

(note1:https://www.ansible.com/quick-start-video)

(Ansible documentation //http://docs.ansible.com/)

 

Ansible 初探

Ansible (note1)

  • an open-source automation engine that automates software provisioning, configuration management, and application deployment (note2)
  • IT automation engine for using to drive complexity out of their environments and accelerate DevOps initiatives.
  • Ansible, an open source community project sponsored by Red Hat, is the simplest way to automate IT.
  • Ansible is the only automation language that can be used across entire IT teams – from systems and network administrators to developers and managers.
  • Ansible by Red Hat provides enterprise-ready solutions to automate your entire application lifecycle – from servers to clouds to containers and everything in between.
  • Ansible Tower by Red Hat is a commercial offering that helps teams manage complex multi-tier deployments by adding control, knowledge, and delegation to Ansible-powered environments.

The goal of automation process is for update without impact of operational capacity

IT automation, Agile development, DevOps, Deployment, Applicaiton update, Testing,

  • CD,CI (Continus Delivery, Continus Integration)  

CI systems are build systems that watch various source control
repositories for changes, run any applicable tests, and automatically build (and ideally test) the
latest version of the application from each source control change, such as Jenkins (jenkins.io).

The key handoff for CD is that the build system can invoke Ansible upon a successful build.
Users who also run unit or integration tests on code as a result of the build will also be one step ahead of the game.

Jenkins can utilize Tower to deploy the built artifact into multiple environments,

but a QA/stage environment modeled after production ups the ante and substantially improved predictability along the lifecycle. The data provided back by Ansible can then be referenced, and directly correlated to a Tower job in the Build Systems job.

Ansible’s unique multi-tier, multi-step orchestration capabilities, combined with its push-based architecture, allow for extremely rapid execution of these types of complex workflows

  • Ansible feature (note3)

MaxthonSnap20170324083511

  • What is Ansible?

 

  • Ansible 自動化組態技巧

 

 

(note1: www.ansible.com)

(note2: https://en.wikipedia.org/wiki/Ansible_(software))

(Why Ansible : https://www.ansible.com/it-automation)

(http://www.slideshare.net/joeywchou/ansible-73452143)

(note3: What is Ansible? // https://www.ansible.com/quick-start-video)

%d 位部落客按了讚: