How A2 works?

An Overview

A2 is a radically simple IT automation solution that automates application builds, continuous testing, data parsing & processing, report generation, batch processing, job scheduling, and many other IT needs.

Designed for multi-tier deployments since day one, A2 models your batch processing needs of IT infrastructure by describing how all of your business processes inter-relate, rather than just managing one application at a time.

It uses no agents and no additional custom security infrastructure, so it's easy to deploy - and most importantly, it uses a very simple language (YAML, in the form of A2 Apps(Jobs) Definitions) that allow you to describe your automation in a way that approaches plain English.

Here, we'll give you a really quick overview so you can see things in context.

Efficient Architecture

Atgen Automation A2 works by connecting to your nodes and pushing out small programs, called "A2 Apps" to them. These programs are written to be resource models of the desired execution on the system. A2 then executes these modules (over SSH or WINRM by default), and removes them when finished.

Your library of apps can reside on A2 server, and there are no databases required. Typically you'll work with your favorite terminal program, a text editor, and probably a version control system to keep track of changes to your A2 Apps.

SSH Keys Are Your Friends

Passwords are supported, but SSH keys with ssh-agent are one of the best ways to use A2. These SSH Keys are over encrypted by A2 security, so adds more to security of systems by using A2 Self Generated Certificates. Lots of options! Root logins are not required, you can login as any user, and then execute your 'A2 Apps'.

Atgen Automation A2's "certificates" are great way to use A2 to control what machines can access what hosts. Other options, like WINRM are too available for windows machines.

Apps: A Simple+Powerful Automation Language

Apps can finely orchestrate multiple slices of your processes topology, with very detailed control over how multiple applications over many machines to tackle at a time. This is where A2 starts to get most interesting.

A2's approach to application processes is one of finely-tuned simplicity, as we believe your automation code should make perfect sense to you years down the road and there should be very little to remember about special syntax or features.

Here's what a app looks like.

---
- name: 'WorkingDay_FourTime_DailyBox'
  type: 'box'
  box: 'none'
  user: 'root'
  node: 'none'
  cmd: 'none'
  date: '1,2,3,4,5,8,9,10,11,12,15,16,17,18,19,22,23,24,25,26,29,30,31'
  times: '06:05,12:05,18:05,00:05'
  days: 'mon, tue,wed,thu,fri'
  months: 'all'
  condition: 'none'

- name: 'WorkingDay_FourTime_DailyApp'
  type: 'cmd'
  box: 'WorkingDay_FourTime_DailyBox'
  user: 'root'
  node: 'atgen001'
  cmd: '/root/a2sample/sampleprocess.sh'
  date: 'all'
  times: 'all'
  days: 'all'
  months: 'all'
  condition: 'none'