Mass Migrate Virtual Machines to Kubevirt with Tool Forklift 2.0
•Transferir como PPTX, PDF•
0 gostou•611 visualizações
There are 6Rs that can help you have Cloud-native workloads running in your Kubernetes deployments: Refactor, Replatform, Rehost, Retire, Retain or Repurchase. Rehosting virtual machines provides less friction than others, while still providing some advantages. One of those advantages being that you can have workloads you don't want to or cannot containerize yet sit alongside your containers through KubeVirt. In this meetup, we'll show you how Forklift 2.0 makes it easy to move them to their new home. And explain why this is a small step for your workloads but a giant leap on your path to the cloud. Presenters: Miguel Pérez Colino, Senior Principal Product Manager & Fabien Dupont, Manager, Software Engineering & Senior Principal Engineer. YouTube recording: https://youtu.be/-w4Afj5-0_g
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Mass Migrate Virtual Machines to Kubevirt with Tool Forklift 2.0
Semelhante a Mass Migrate Virtual Machines to Kubevirt with Tool Forklift 2.0 (20)
Mais de Konveyor Community
Mais de Konveyor Community (18)
Último
Último (20)
Mass Migrate Virtual Machines to Kubevirt with Tool Forklift 2.0
- 1. 1 Accelerate your journey to Kubernetes with the Konveyor Community A community of people passionate about helping others modernize and migrate their applications to the hybrid cloud by building tools and best practices on how to break down monoliths, adopt containers, and embrace Kubernetes. www.konveyor.io
- 3. 3 Rehost virtual machines to KubeVirt Rehost apps between Kubernetes clusters Replatform applications to Kubernetes Refactor applications for Kubernetes Measure software delivery performance
- 4. 4 Why moving VMs to KubeVirt + Kubernetes?
- 9. 9 www.konveyor.io Technical? Join the Konveyor Community A community of people passionate about helping others modernize and migrate their applications to Kubernetes by building tools and discovering patterns of how to break down monoliths, adopt containers, and embrace Kubernetes. Projects Additional community contributors being recruited How I strangled a monolith How I containerized my java app How I created an operator Meetups Migration Toolkit for Containers Migration Toolkit for Virtualization Migration Toolkit for Applications Supported Operators Exploration in progress to obtain CNCF support for the Konveyor community projects
- 11. 11 Migration at Scale Of virtual machines to KubeVirt Mass Migration of VMs Migrate virtual machines at scale to OpenShift Virtualization in a few simple steps. Provide source and destination credentials, map infrastructure, and create migration plans
- 12. 12 Providers Easy to configure source and target providers The providers section allows you to configure the credentials for your source and destination clusters. Multiple source and destinations can be added, and your overall provider information can also optionally be uploaded to cloud.redhat.com for additional information about your overall environment, helping you better plan your migration at scale.
- 13. 13 Infrastructure Mappings Infrastructure mapping allows you to answer questions about source and destination of your VMs from a network and storage point of view. This can be configured once by your network and storage specialist, avoiding redundant questions during the execution of your migrations.
- 14. 14 Migration Plans And pre-migration checks Forklift introduces, as tech preview, new on-premise migration analytic capabilities, helping you find potential migration issues before executing a migration. When selecting your virtual machines, Forklift will automatically inform you of any known potential issue and provide information on how to solve this issue when possible. Virtual machines can be filtered down by names, folders or other parameters to review all VMs related to a specific applications.
- 15. 15 Migration Progress Launch your migration, sit back and relax. We will keep you informed on our progress during the migration.
- 16. 16 Forklift Architecture VMware vSphere OpenShift Virtualization VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM VM Provider Inventory Service (Pod) Validation Service (Pod) User Interface (Pod) Mapping CR Migration Plan CR Migration Run CR Controller (Pod) Virtual Machine Import Operator VM Import CR
- 18. 18 Forklift Roadmap VM migration ● Forklift 2.0 Launched! ○ Warm Migration from VMware vSphere ○ Pre-migration checks (tech preview) ● Forklift 2.1 ○ Cold migration from RHV/oVirt ○ Migration Hooks
- 19. 19 Forklift Roadmap VM migration ● Forklift 2.2 ○ Warm migrations from RHV/oVirt ○ Ansible Hooks Image Builder ○ Pre-migration checks (GA) ● Forklift 2.3 ○ OpenStack Support (Basic)
- 20. 20 Forklift Roadmap VM migration Forklift 2.2 RHV migration (Warm) Pre-migration checks (GA) Ansible Hooks Image Builder Nov 2021 Feb 2022 Forklift 2.3 Basic OpenStack Support Forklift 2.0 VMware migration (Warm) Pre-migration checks (TP) Jun 2021 Aug 2021 Forklift 2.1 RHV migration (Cold) Migration Hooks Mar 2021 Forklift 2.0 Beta VMware migration (Cold)
- 22. 22 Get Involved www.konveyor.io ● Chat #konveyor on slack.k8s.io ● Get Meetup Invites + Tool Updates Subscribe at konveyor.io ● Share Propose a meetup talk (form) ● Contribute Join the next quarterly project planning Invites sent to Konveyor-community list
Notas do Editor
- A movement towards more open and more software-defined technologies
- So where is storage in this evolution? Smaller, yes, and a little bit smarter But storage still has a long way to go
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases
- Warm Migration: users will be able to have a shorter downtime for their VMs when migrating. All disk data will be copied while VM is still running, registering the changes. Once we are ready to complete the migration we shutdown Vm and copy only the changed data. This means being able to migrate more VMs in the same time assigned to an intervention window … or shorter intervention windows for the same number of VMs. Pre-migration checks: forklift will be able to check for characteristics in the virtual machine that may require manual intervention or even render the migration unsuccessful *before* the migration happens. This way we can reduce the number of issues in large migrations and even enable the users to build their own migration rules. RHV/oVirt: adding this provider is important in order to cover more migration cases Migration Hooks: Automate tasks pre or post migration by providing a container image or an Ansible Playbook Ansible Hooks Image Builder: helps you build container images using your own ansible playbooks as stored in a git repository OpenStack: adding this provider is important in order to cover more migration cases