Cloud and on premise infrastructure assessment for Camuzzi Gas

Camuzzi Gas distributes natural gas and runs its technology across two coexisting environments: the cloud on Azure and an on premise virtualization platform on VMware.

The company was mid migration, and that is exactly when decisions get made on intuition: without evidence, every change is justified with an opinion and the cost shows up later.

• Oversized resources: disks and services with more capacity than their environment needs, and their cost running every month.
• Unknown exposure: exposed services and unreviewed firewall rules in an environment in transition.
• Unquantified opportunities: consolidating databases saves licensing and maintenance, but nobody had the figure.

Without a diagnosis carrying estimated impact, the migration advances dragging along what should have been fixed first.

An integral assessment was run with deliverables differentiated by platform type, designed to be validated with the technical leads before executing any change.

Every proposed improvement arrived with its estimated impact on cost and performance, which is what separates a diagnosis from an inventory.

Azure cloud assessment

• Storage: resource tagging and verification that each disk performance tier matches its environment, focused on oversizing and quantified savings.
• Network: sizing, structure, private tunnels, address range overlap and environment segmentation, with service exposure treated as a critical finding.
• Servers and platforms: consolidation proposals including database centralization with its maintenance and licensing savings, and patching verification.

On premise assessment

• Hypervisor configuration on an older version being migrated.
• Patching and backup procedures, and general environment status.
• Storage and chassis inventory, including two data centers with no cluster configured and the intention to build one.

Working method

• Adoption of a DevOps scheme to order production releases and align tooling between development and operations.
• Requirements defined upfront: application map of both environments, server farm documentation and a single technical lead on the client side.

Architecture and technology

• Azure and VMware assessed with deliverables differentiated by platform.
• Agile tracking frameworks over the defined DevOps scheme.

Learn more about DevOps and infrastructure.

The migration moved from relying on judgment to relying on documented evidence, with every proposal carrying its impact.

Starting point

• Two environments coexisting mid migration, with no documented diagnosis.
• Oversizing and exposure unquantified.
• Two data centers with no cluster configured.

Strategic impact

• Every improvement arrives with its estimated impact on cost and performance, not as a loose recommendation.
• Exposed services were treated as a critical finding rather than an observation.
• The DevOps scheme orders production releases between development and operations.
• Deliverables were designed to be validated with the technical leads before executing.
• Naming a single technical lead was set as a starting requirement, not a detail.