PROFESSIONAL SUMMARY:

• Infrastructure Automation Developer/Engineer since 2000. Including Puppet(Open Source and Enterprise), Chef, SaltStack(these three since 2013), and custom code(since 2000); Virtualization implementation with OpenStack and VirtualBox; Software Process Automation Development; Python, Ruby, and Perl Development; DevOps Engineer; Linux/UNIX Systems Administrator.
• Design and development of SaltStack/OpenStack architectural solution to replace legacy Puppet/Bare - Metal systems management implementation for corporate infrastructure support.
• Design and development of Puppet Open Source transitional solution to replace legacy/archaic systems management practices.
• Designed and developed a build automation framework system that increased Enterprise Software Build throughput from one build each 1.5 days to six+ builds a day (900-1200% improvement).
• Designed and developed an automated patch process solution that overhauled product manual patch creation from hours to a few minutes.
• Exceptional experience in situations requiring analysis, reverse engineering, and automation of complex environments with minimal documentation provided.
• Experience with opportunities having short learning curves, or very brief cross-training periods before commencing duties to performance tune or re-engineer existing environments with automation development.

TECHNICAL SUMMARY:

Programming Languages: Python, Ruby, Perl, Bash

Development/Automation Projects: Chef Cookbook re-engineering for multiple OpenStack cloud instances , Salt, Puppet(Open Source and Enterprise), Design and development of Build Automation Frameworks, Automated Product Patch creation tool, Custom ClearCase Reporting system, Custom Product Installers, Re­engineering of existing complex build environments

Architectural Design: SaltStack re-engineering effort from existing Puppet implementation, Puppet Automation framework, Build Automation Frameworks, Custom product installers, Custom product patch tool, SCM Report system, Custom UNIX Account management redesign, Corporate DesignSync Deployment Standards

Infrastructure Automation: Chef Cookbook re-engineering, Puppet/Ruby module development, Eclipse/Geppetto/Subversive package for Puppet module development

Virtualization Technologies: Docker(Training only), OpenStack(Grizzly and Havana, using Horizon, Nova, Neutron, Keystone), VirtualBox, Vagrant

DevOps: Custom build framework and process development for managing development and operations interactions, re-engineering of large-scale UNIX/Linux account management application

Cluster Technologies: Platform Computing Load Sharing Facility(LSF), Dispatch Queue Manager(Motorola proprietary), Linux Cluster tools(OSCAR, OpenPBS)

SCM/Version Control/Reporting Tools: Git/Stash, Jira, Artifactory, FishEye/Crucible, SVN, Bugzilla

Software Build Management: Ant, Packaging(RPM, pkgadd), Custom Build Framework Development, CruiseControl

Databases: Database Development(MySQL), Database Administration(PostgreSQL, MySQL)

Operating Systems: CentOS 5/6/7, RedHat Enterprise Linux 4/5/6, Solaris 2.5/2.6/7/8/9, Ubuntu 12.04, SLES 11/12

Systems Administration: NFS, DNS, NIS, Sendmail/majordomo/hypermail, rsync, ssh, NetApp, Auspex, Solaris JumpStart, Sun StorEDGE servers Additional details available on request

Additional Tech Interests: Docker, Hadoop/Big Data, AWS, Go(golang).

PROFESSIONAL EXPERIENCE:

Confidential, Plano, TX

DevOps Automation Engineer

Responsibilities:

• DevOps Engineering activities for tools in a Platform as a Service offering bringing Continuous Integration / Continuous Delivery processes to internal customers (Application Owners and their Development Teams).
• Two week intro management self-training on specialized tools including the Build and Deploy components.
• Various other self-training completed includes Docker, Jenkins, Certified Ethical Hacker(CEH), AWS, Ansible, Chef, Python, Puppet, Cloud Computing, Software Defined Networking(SDN)

Confidential, Garland, TX

Sr. Automation Engineer/Chef Developer

Responsibilities:

• Chef and custom software development for automation and support of OpenStack laaS/PaaS infrastructure with Open and Closed/Clearance-Required environments.
• Upgrade of SLES 11 Jump/Landing-Zone platform to SLES 12 hosted on OpenStack laaS/PaaS infrastructure. Landing- Zone platform is the secured entry point to the closed environment.
• Upgrade of SLES 11 OpenFire/Chat-server platform to SLES 12 hosted on OpenStack laaS/PaaS infrastructure. Chat- server platform is the secured Instant Messenger platform in the open and closed environments.
• Development, upgrade, and re-engineering of other OpenStack hosted VM platforms and components as assigned.
• Revision and updating of on-boarding technical documentation wiki, as well as addition of missing processes and procedures for standing-up new OpenStack based VMs by Chef Engineers/Developers.
• Other DevOps Development duties as assigned.

Environment: Chef, Ruby, SLES, Ivy, Gradle, Python, Jira, Stash/git, Jenkins, Artifactory, FishEye/Crucible, KVM, JSON

Confidential, Austin, TX

Sr. Application Developer - Puppet Developer

Responsibilities:

• Worked as a Puppet Enterprise Module Developer, supporting the primary Puppet Engineer who was located in Budapest, Hungary. Other team member locations included Cork, Ireland, and Southboro, Massachusetts.
• Project was development of Enterprise Platform as a Service product(Based around VMWare vCloud Suite, vCAC, etc). It was a Cloud/Virtualization self-service fulfillment tool for engineering groups and customers to request and configure virtual system sets on demand.
• Developed new modules from scratch, as well as enhancements to existing modules. Some included RabbitMQ, Hosts, GemFire, NodeJS, MongoDB, Neo4J, and PostgreSQL.
• Created Virtualbox/Vagrant sandbox setup with multi-VM configuration for RHEL images. Allowed for four or more VMs per testbed, with multiple testbeds operational at the same time, all dependent on host(laptop, PC, etc) system disk- space and available memory.

Environment: Puppet, Role-Profile Module, Mcollective, Hiera, Ruby, VMWare Workstation, Vagrant, VirtualBox, RHEL

Confidential, San Antonio, TX

DevOps Automation Engineer

Responsibilities:

• Architected from scratch a SaltStack re-engineering effort from existing Puppet implementation for corporate infrastructure support systems.
• OpenStack instance deployments from scratch to replace existing servers for corporate infrastructure support.
• Designed Salt State architecture that allows for easy transition of Puppet modules from multiple environments to multiple Salt application environments with minimal re-engineering, beyond syntax.
• Assisted with day-to-day DevOps/SysAdmin operations of primary corporate infrastructure systems, but primary focus was the architecture and re-design of replacement support infrastructure with OpenStack, SaltStack, and related technologies.
• Reverse-engineering of Puppet deployment environment(manifest files), re-engineered into SaltStack state files .

Environment: SaltStack, OpenStack, Puppet, Ruby, Python, Vagrant, VirtualBox, DevOps, Ubuntu, CentOS, Systems Admin

Confidential, Austin, TX

Puppet Automation Engineer/Developer

Responsibilities:

• Design and development of Puppet Open Source transitional solution for replacing legacy/archaic systems management practices, including 400+ RedHat Enterprise Linux 6 servers as agents. Puppetmaster and Masterless designs .
• Ruby script development for additional automation development tasks in support of Puppet.
• Created Yum repository for Puppet managed systems.
• Integrated Puppet manifests and modules, NginX, Varnish, and other configuration files into Subversion repository revision tracking for automatic extraction upon new release deployment.
• Upgraded Puppet WEBrick webserver to NginX and Passenger for more robust PuppetMaster web access.
• Development of Puppet modules and generic templates for large-scale systems deployment configuration for website online efforts.
• Vagrant with VirtualBox researched, setup, and implemented for multi-VM Puppet simulations.
• Eclipse/Geppetto used for managing development of Puppet modules.
• Design and development of catch-all Python script to encompass all monitoring web-page targets in one executable and manageable point of reference.

Environment: Puppet, RedHat Enterprise Linux, Ruby, Python, Yum repository creation, NginX, Passenger, Varnish, Subversion, WEBrick, Eclipse, Geppetto, Vagrant, VirtualBox

Confidential, Austin, TX

Build Manager/Automation Developer

Responsibilities:

• Daily monitoring and management of build operations including ClearCase, Build Forge, Ant, and custom Perl and Shell scripts on Linux based physical and VMWare virtual systems.
• Primarily Java code-base implementing ESB technology with legacy code utilizing CORBA Orbix and other technology.
• Coordination of build execution in Build Forge on a rotating basis, verifying in Remedy and with offshore teams via email when builds are needed.
• Process included delivering updated code and deployment to development environments for testing teams.
• Updating of environment Perl, Shell, and Ant/XML scripts as needed .
• Handling of daily developer and management requests for changes to build schedule.
• Automation development of build tasks with Ant and Perl, which is executed from within Build Forge.

Environment: BuildForge, Ant, Perl, Shell, ClearCase, RHEL, VMWare

Confidential, San Antonio, TX

UNIX Systems Automation Developer

Responsibilities:

• Analysis and design of a replacement account management system for 3000+ UNIX-based physical and virtual servers in the environment (coverage included Solaris, HPUX, and RedHat Enterprise Linux).
• Major components of the software development and account management environment included Perl development for Active-Directory and Centrify Direct-Control in addition to systems files used for managing local accounts.
• Activities included reverse engineering legacy Shell-based processes, documenting, and designing in Perl, more efficient procedures utilizing the major components of the customers environment. Legacy code content included 150-200 Korn shell scripts with approximately 40,000 lines.
• Identifying, documenting, and importing of existing legacy code into Subversion.
• Design of the replacement code were Perl modules along with the design of an expansion API for authorized user and administrator access.
• Creation of repository, import of legacy code, filtering of non-essential items, and development of a branch/merge work-flow policy as well as documentation.

Environment: Perl, Perl-Modules, Object-Oriented Perl, Solaris, RHEL, HPUX, Active-Directory, Korn shell, Centrify Direct- Control