We keep your OpenStack cloud running — Canonical, Red Hat OSP or your own distribution. Our own engineers in EN/ES/FR, with a direct phone line and response in your timezone.
We support clouds someone else deployed, clouds mid-distribution-change, and clouds that have been running on autopilot for years. Vendor-neutral: we are not here to sell you another OpenStack, we are here to keep yours alive.
You have a vendor contract and it works, but you want a local partner who speaks your language, sits in your timezone and understands MicroCloud, Juju and OVN without long escalation chains.
What we doWe complement your Canonical contract with local support in EN/ES/FR or replace it if you prefer to consolidate providers.
Red Hat is closing the traditional OSP line in June 2029. The successor, Red Hat OpenStack Services on OpenShift, changes the whole operating model. Someone has to make the call: stay, jump to RHOSO, or switch distribution.
What we doWe audit your OSP, cost out the three routes with real numbers and see the chosen one through with you.
Your own team or a previous integrator set it up. It works, but the documentation has fallen behind and upgrades feel risky. You don't want to scrap the cloud; you want it stable and maintainable again.
What we doWe rebuild the runbook, close the security gaps, make upgrades reproducible and add an optional on-call rota.
Three models that cover 95% of cases. If your cloud sits in a regulated sector (banking, healthcare, defence) we scope it separately — it will not fit on three cards.
Modality 01
When something is on fire and there's no prior contract. One-off intervention, no commitment, to stabilise and leave the environment documented.
Modality 02
Reference engineer, dedicated ticketing and a regular patching and review cycle. Day-to-day operations covered during business hours.
Modality 03
Everything from the ongoing contract plus monitoring and real on-call cover outside business hours, with our own engineer on the other end of the line.
Every cloud has its own size, distribution and maintenance windows. Before giving a range we want to see the inventory and talk it through — we don't sell closed packages blind.
We would rather show you a working day than list three abstract promises. This is what usually happens on the first shift of the week for a customer in production.
We check Prometheus and RabbitMQ. Two latency warnings on neutron-server on Saturday; neither critical. We log the cause (an OVN agent that dropped and self-recovered) in the runbook.
A CVE lands with a 7.5 score on keystoneauth. Backport available upstream, we apply it in pre-production, validate the customer's SAML federation and schedule the production window for Tuesday night.
Capacity walkthrough: the compute-05 pool is at 78%. We propose adding two hypervisors before the next quarter end. Tenant review: two projects burned through double their quota this quarter — time to rebalance.
placementA developer complains that their GPU VMs will not boot. We look at placement: traits are missing on the new compute node. Fixed in 25 minutes, documented in the runbook for the next hardware onboarding.
Handoff to the evening engineer. Environment state, silenced alerts, Tuesday window prepared. On-call takes over with full context — nobody is discovering your cloud from a 3am ticket.
EOL · OSP 17.1
JUN 2029
Extended Life-cycle Support
~46 months
Red Hat closed the traditional OpenStack Platform line with 17.1. The successor is Red Hat OpenStack Services on OpenShift (RHOSO), which changes the operating model by placing the control plane on Kubernetes. This is an architecture decision that goes beyond a simple contract renewal.
We can audit your OSP and give you the three routes with numbers: licence cost, estimated migration time and operational risk. We are vendor-neutral: each option has its place, and it depends on your context — not on our fees.
We don't list every service one by one — we'd rather talk case by case. We cover OpenStack core services and the adjacent ones each environment needs, focused on what gets operated in practice, not on what sounds good in a catalogue.
We work regularly with Canonical Charmed / Sunbeam, Red Hat OSP 16.2 and 17.1, Kolla-Ansible and DIY deployments on Ubuntu, RHEL or SUSE. For backup we rely on Trilio where it fits, and for training your team we offer official OpenStack courses at partner pricing.
Distribution, hypervisor count, version and what hurts. We come back with a range and a proposal in under 24 business hours.
SIXE ensures that your infrastructures based on IBM®, Red Hat®, Canonical®, and SUSE® technologies remain stable, secure, and optimized for as long as you need them.
At SIXE, we are committed to sustainability. That’s why we help you design, implement, and maintain durable and efficient technological solutions.
