• I went on with ACI as a contractor on a project to introduce
  active-hotstandby cross-datacenter traffic switchover model.
  The project goal was to reduce customer-facing incident impact during major platform outages. In case of major incident in live processing datacenter, the automated solution is supposed to detect failure condition and switchover complete processing stack to disaster recovery datacenter.
• My particular responsibility was to implement project tooling for manual and automated switchovers, as well as monitoring solution coupled with rule engine, that would trigger processing switchover on particular predefined condition.
• The tooling was implemented by me in Go and consists of CLI interface for various platform components to assist manual switchover, and witness daemon for proactive monitoring and incident detection. Part of witness daemon is a rule engine, that detects failure condition and performs automated failover if condition is met

• At ACI/PAY.ON my core activities were around improving tooling and infrastructure
• Over the last years I was using implementing my vision by preparing and driving forward DevOps roadmap and mentoring new hires, strengthening interactions among teams and nurturing DevOps culture

Completed projects with direct involvement:

• Migration of source code base from Subversion to Git
• Setup and maintenance of Gerrit instances
• Setup and maintenance of Artifactory instances
• Migration of Jenkins jobs to Jenkins Job DSL
• Setup and maintenance of dev Jenkins clusters
• Introduction and maintenance of Vagrant-based Development VM for 50+ developers
• In-house release tooling improvements and maintenance
• Production environment migration to new datacenter
• Datacenter switchovers and creating of tooling for it
• Jira migration to ACI active directory
• UltraDNS/pingdom management CLI in Go (reliable and fast live traffic redirection)

I am always very active on innovations track, including internal
hackatons, code retreats and proof-of-concept works, crossdepartment knowledge sharing, including but not limited to:

• Kubernetes (PoC for dev infrastructure, comparing docker and crio)
• vmware automation PoC (creating vms from compliant templates with Ansible)
• OpenStack internal hackaton topic (creating vms from templates with OS)
• Containerization internal hackaton (running one of our core projects on Kubernetes)
• Jenkins Xray plugin PoC (tracks code Test coverage for every Git commit)
• Ansible dynamic inventory PoC (provides Ansible with entries from or internal server inventory database)
• Release orchestration from Jira (To trigger and coordinate Jenkins jobs with Jira transitions)
• Docker Swarm PoC (prototyped our complete dev infra in containers)
• Unified server/dev vm template that can be continuously delivered (to provide developers and operations with single compliant base vm template, that can be reused in vagrant and in vmware)
• Corosync binding in Go

• I was covering web frontend, backend. database, servers’ healthcare, webops and devops.
• Our system evolves around iOS application, that is managed by Web UI
• Backoffice stack consists of Angular, Spring, JasperReports and PostgreSQL+Mongo.
• Using Chef, Jenkins, Munin and Nagios and a lot of other stuff for dev/web operations.