Cloud Migration

Yes. Containerized applications on Kubernetes are inherently portable, making cloud migrations dramatically faster. If your workloads run on EKS, AKS, or GKE, migrating to Leafcloud's OpenStack infrastructure is primarily a configuration change, not a code rewrite.

Why containerization accelerates migration:

Kubernetes provides a consistent abstraction layer across all cloud providers. Your application manifests, Helm charts, and Kubernetes operators work identically whether running on AWS EKS, Azure AKS, Google GKE, or Leafcloud's Gardener managed Kubernetes.

Migration timeline for containerized workloads:

• Kubernetes to Kubernetes: 1-4 weeks for most applications (EKS → Gardener)
• Container images: No changes required—pull from same registries (Docker Hub, ECR, GCR, private registries)
• Persistent storage: Kubernetes CSI drivers handle Cinder block storage transparently
• Load balancing: Service type LoadBalancer provisions Octavia load balancers automatically
• GPU workloads: NVIDIA GPUs (H100, A100, A30, RTX 6000) available as Kubernetes node resources

What stays the same:

• Application code: Zero changes to containerized applications
• Deployment manifests: kubectl apply, Helm charts, and Kustomize work identically
• CI/CD pipelines: Update kubeconfig context—workflows remain unchanged
• Monitoring: Prometheus, Grafana, and cloud-native observability tools work identically
• Service mesh: Istio, Linkerd, and Cilium function the same on OpenStack infrastructure

Examples of fast migrations:

• ML/AI workloads: Containerized models on EKS migrate to Gardener with GPU support (H100, A100) in 2-4 weeks
• Microservices: API services with stateless containers migrate in 1-2 weeks
• Data pipelines: Argo Workflows, Apache Airflow, and Spark on Kubernetes move without refactoring

When migration takes longer:

Even with containerization, some dependencies may extend timelines:

• Managed services: Using AWS-specific services (RDS, ElastiCache, SQS) alongside Kubernetes requires replacing with self-managed or open-source alternatives
• Persistent data: Large databases or stateful workloads need careful migration planning for data transfer
• Custom integrations: Applications tightly coupled to hyperscaler APIs need refactoring

Not containerized yet?

If your workloads run directly on EC2, Azure VMs, or GCP Compute Engine, consider containerizing before migrating. You'll gain:

• Faster migration: Kubernetes-to-Kubernetes is weeks instead of months
• Future portability: Move between any OpenStack provider or back to hyperscalers without lock-in
• Modern orchestration: Auto-scaling, rolling updates, and declarative infrastructure
• Cost efficiency: Better resource utilization with container density

Leafcloud provides Gardener managed Kubernetes with full GPU support, integrated with OpenStack infrastructure (Nova VMs, Cinder storage, Neutron networking, Octavia load balancers). Your containerized workloads migrate quickly while gaining EU sovereignty and eliminating egress fees.

Yes. Leafcloud uses standard OpenStack APIs and supports common orchestration tools like Kubernetes, and IaC solutions like Terraform and Ansible making migration straightforward.

Yes. Leafcloud, which runs on OpenStack, provides similar IaaS capabilities to AWS, and many workloads can migrate with reasonable effort. The complexity depends on your AWS service usage.

Easy to migrate (OpenStack equivalents):

• EC2 → Nova: Virtual machines with similar instance types and APIs
• EBS → Cinder: Block storage volumes with snapshots
• VPC/Security Groups → Neutron: Software-defined networking with security groups
• S3 → Swift: Object storage with S3-compatible API
• ELB/ALB → Octavia: Load balancing with similar capabilities
• Route53 → Designate: DNS management
• EKS → Gardener/Magnum: Managed Kubernetes on OpenStack

Moderate effort (requires refactoring):

• Lambda → Kubernetes Jobs: Replace serverless functions with containerized jobs
• RDS → Self-managed databases: Deploy PostgreSQL/MySQL/MongoDB on Nova instances or managed DBaaS
• SQS/SNS → RabbitMQ/Kafka: Message queuing with open-source alternatives
• CloudWatch → Prometheus/Grafana: Monitoring with open-source observability stack

Open-source alternatives (escape vendor lock-in):

• SageMaker → Kubeflow: 2-4 weeks for containerized ML workloads on GPU infrastructure (H100, A100, A30)
• DynamoDB → Cassandra/MongoDB: 2-6 weeks depending on data model complexity
• API Gateway → Kong/Traefik: 1-2 weeks with Kubernetes-native ingress controllers
• Step Functions → Argo Workflows: 1-3 weeks depending on workflow complexity

Migration strategy:

1. Audit AWS usage: Identify which services you actually use (EC2, S3, RDS vs. proprietary services)
2. Lift-and-shift compatible workloads: Start with EC2 instances that can move directly to Nova
3. Refactor database tier: Migrate RDS to self-managed or OpenStack DBaaS offerings
4. Replace proprietary services: Containerize Lambda functions, migrate to open-source alternatives
5. Update Infrastructure-as-Code: Convert AWS Terraform/CloudFormation to OpenStack Terraform provider
6. Test thoroughly: Run parallel environments during migration window

What makes migration easier:

• Containerized workloads: Kubernetes-based apps migrate seamlessly (EKS → Gardener)
• Standard APIs: Apps using PostgreSQL, Redis, Kafka, S3-compatible storage have direct equivalents
• Minimal managed services: Less dependency on AWS Lambda, SageMaker, DynamoDB means easier migration

OpenStack benefits after migration:

• No egress fees (save $0.12/GB on outbound traffic)
• Transparent pricing (no surprise charges)
• EU sovereignty (Leafcloud in Amsterdam, not subject to US CLOUD Act)
• Vendor independence (switch providers without lock-in)

Leafcloud provides OpenStack infrastructure with GPU support (H100, A100, A30, RTX 6000 Blackwell), managed Kubernetes (Gardener), and S3-compatible object storage to support AWS workload migrations.

Yes, migrating from hyperscaler VMs to Leafcloud is straightforward thanks to OpenStack's standard APIs and broad tooling support. Most migrations can be completed with minimal downtime using standard Linux tools or OpenStack utilities.

Migration Methods:

For cloud-to-cloud migrations, you have several options:

• Image import: OpenStack provides native import tools that work with common VM formats (QCOW2, RAW, VMDK)
• Export and import: Export your existing VM image from AWS EC2, Azure VMs, or GCP Compute Engine, then import it directly to Leafcloud using the OpenStack CLI or Horizon dashboard
• Live migration: For running workloads, tools like rsync or block-level replication minimize downtime during cutover

VM Compatibility:

Leafcloud runs industry-standard x86-64 processors (AMD EPYC 9755 128-Core Processor). Any Linux distribution or Windows Server version that runs on AWS, Azure, or GCP will run on Leafcloud without modification.

Supported operating systems:

• Ubuntu, Debian, CentOS, Rocky Linux, AlmaLinux
• Windows Server 2016-2022
• Custom kernel configurations and drivers work identically

Network & Storage:

Network configurations translate directly:

• Networking: VPC-style networking on AWS/Azure/GCP maps to OpenStack's Neutron networking with private networks, security groups, and floating IPs
• Storage: NVMe SSD local volumes (equivalent to AWS instance storage) or network block storage (equivalent to EBS/Azure Disk)
• Provisioning: You can provision identical storage layouts to your existing infrastructure

No Vendor Lock-In:

Unlike proprietary hyperscaler APIs, OpenStack is open-source with standardized APIs. This means:

• Move workloads freely between any OpenStack cloud or back to AWS/Azure/GCP if needed
• Terraform, Ansible, and other IaC tools work identically across providers using OpenStack's standard APIs

Migration Support:

Our Amsterdam-based team provides migration assistance including:

• Architecture reviews
• Data transfer guidance
• Cutover planning

For complex migrations involving multiple VMs or applications, we offer hands-on support to ensure smooth transitions. Email hello@leaf.cloud or schedule a call to discuss your specific migration needs.

Cost Savings:

Most customers see 20-50% cost reduction after migrating from hyperscalers, particularly for EU workloads. Leafcloud's pricing starts at €0.02/hour (€14.60/month) with:

• No hidden fees
• No data egress charges within EU infrastructure
• No complex pricing tiers
• You pay for compute and storage—that's it

OpenStack provides open-source cloud infrastructure without vendor lock-in, giving you full control over your infrastructure, APIs, and data. Here's how it compares to hyperscalers:

Vendor Lock-in:

• Hyperscalers: Proprietary APIs (AWS Lambda, Azure Functions, Google Cloud Run) make migration expensive and complex
• OpenStack: Standard APIs supported by multiple providers worldwide - switch providers without refactoring

Cost Structure:

• Hyperscalers: Egress fees (up to $0.12/GB), hidden charges, complex pricing with 200+ SKUs
• OpenStack: No egress fees, transparent pricing, predictable costs

Data Sovereignty:

• Hyperscalers: US-owned companies subject to CLOUD Act, even in EU regions
• OpenStack: Provider-dependent, but enables true EU sovereignty (e.g., Leafcloud in Amsterdam)

API and Tool Compatibility:

• Hyperscalers: Require provider-specific SDKs and services
• OpenStack: Works with standard tooling (Terraform, Ansible, cloud-init, Packer)

Kubernetes Integration:

• Hyperscalers: Managed Kubernetes with proprietary extensions (EKS, AKS, GKE)
• OpenStack: Standards-based Kubernetes (Gardener, Magnum) with full control

When to choose OpenStack:

1. Regulatory compliance: NIS2, DORA, CSRD, or HAVEN+ requirements for EU sovereignty
2. Cost optimization: High egress traffic or predictable workloads make fixed pricing attractive
3. Multi-cloud strategy: Avoid dependency on single vendor's proprietary APIs
4. Large-scale deployments: Proven at massive scale (CERN, Bloomberg, Walmart)
5. AI/ML workloads: GPU infrastructure without egress fees for model training data

When hyperscalers make sense:

• Extensive use of proprietary managed services (SageMaker, BigQuery, Azure Cognitive Services)
• Small-scale prototyping with free tiers
• Teams deeply invested in hyperscaler-specific tooling

Leafcloud provides OpenStack-based infrastructure in Amsterdam with EU sovereignty, no egress fees, and full compatibility with standard cloud tooling.