Every release involves manual steps
Preparation, configuration and deployment depend on a sequence of manual operations. The first task is to make that sequence explicit, identifying what to automate and which checks to keep before proceeding.
Vicenza · Veneto · remote across Italy
DevOps consulting for businesses.
Based in Vicenza, I work with businesses across Veneto and remotely throughout Italy to manage configurations and releases with CI/CD pipelines, Docker and Kubernetes. I use Terraform and Ansible to automate infrastructure and connect systems work with development processes.
Vicenza Veneto Remote across Italy
Let’s talk about your project
Explore the work
Introductory call · 30 minutes
Before we make changes
How we scope the initial work.
We trace a release before deciding what to automate. The first workflow, checks and deliverables are agreed with the team, without assuming that existing tools need to be replaced.
- Starting information
- The steps in a current release, target environments, available pipelines and configurations, manual activities and points where the process breaks down.
- Scope to agree
- We choose an application, a pipeline or a set of configurations. We agree the expected behaviour and the checks for the first workflow before extending automation to other environments.
- Deliverables to define
- We define which pipelines or configurations to keep under version control and what instructions to provide for running, checking and maintaining them. Terraform, Ansible and containers are included only if they are relevant to the chosen workflow.
- What is not included
- Replacing the entire platform, adopting Kubernetes and extending the work to every application are not automatic: they require their own scope and checks.
The starting point
When I can help.
Development and operations use different configurations
The application works in one environment but has problems in another. We need to distinguish necessary differences from those introduced over time and define how to version configurations alongside the planned changes.
Containers are already part of the infrastructure
Docker or Kubernetes is in place, but release management remains separate from systems work. We can connect pipelines, configurations and environments, clarifying the steps and operational responsibilities.
The work
What we work on.
Integration and release pipelines
I work with GitLab CI, Jenkins and Git to describe the release process. We define stages, dependencies and checks around the project, avoiding automation of steps that are not yet clear to the team.
Docker and Kubernetes
I support the team in using containers and managing Kubernetes environments. The work addresses the relationship between the application, configuration and infrastructure, taking into account how the service will be released and maintained.
Terraform and Ansible
I use Infrastructure as Code and configuration automation to describe system changes. The code can be versioned and reviewed by the team, alongside the checks needed to apply it in the intended environments.
A shared approach
How we work.
Trace an actual release
We map the path from a code change to the target environment. We identify manual activities, configurations outside the pipeline and points where the process breaks down.
Choose a first workflow
We agree on an application, a pipeline or a set of configurations to work on. We define the expected behaviour and checks before extending automation to other environments.
Fit the process into the team’s work
We implement the agreed steps and document how to run and change them. The team needs to be able to understand the process, recognise errors and know where to act.
Handover to your team
What we define together.
- Version-controlled pipelines and configurations for the agreed workflow.
- Terraform code, Ansible playbooks or container configurations relevant to the work.
- Instructions for running, checking and maintaining the process.
Before we begin
Frequently asked questions.
Do we need Kubernetes to start improving DevOps processes?
No. We can start with a CI/CD pipeline or configuration automation. Whether to use Kubernetes depends on the application and operational needs; it is not a requirement for improving the release process.
Do Terraform and Ansible do the same job?
Their roles can complement each other. Terraform is used to describe and create infrastructure resources; Ansible automates configurations and operations on systems. How they are used needs to be defined in relation to the existing environment.
Do I need to replace the pipeline I already use?
Not necessarily. We can start with the existing process, including GitLab CI or Jenkins, to identify manual steps, configurations to version and checks to integrate. The scope is agreed with the team.
Your technical contact
Eddy Boscolo.
For over 17 years, I have worked with IT infrastructure. My work covers AWS and Azure architecture, Linux administration and automation with Terraform, Ansible, Docker and Kubernetes, alongside technical teams and project managers.
Based in Vicenza, I work with businesses across Veneto and remotely throughout Italy.
The next step
Let’s start with your release process.
In the 30-minute call, tell me how you deploy applications, which tools you use and which steps you would like to automate.