v0.1.2

What's Changed

• Upgrade min version to v0.1.1 by @tanaypf9 in #71
• Use version as tag for release event by @tanaypf9 in #72
• Added React Query to cache data, refactored MigrationForm component, and added error handling to MigrationForm by @knnguy in #69
• Add FAQs by @tanaypf9 in #74
• Fix for incomplete transfer of changed blocks by @tanaypf9 in #75
• Add Video Demo by @tanaypf9 in #73
• Add vCenter role perms and port req by @tanaypf9 in #76
• Adding additional network port prereqs for NBDkit by @jeremymv2 in #77
• replaced vCenter Role permissions with more comprehensive list from R… by @jeremymv2 in #78
• update README with table for prereqs by @jeremymv2 in #79
• Add debug logs to v2v-helper by @tanaypf9 in #80
• UI: Fixes by @knnguy in #87
• Remove unused VMInfo field by @tanaypf9 in #82
• Add ephemeral storage req and limits by @tanaypf9 in #119
• Compress nmcli scripts by @tanaypf9 in #120
• Wait for volume mount for up to a minute by @tanaypf9 in #121
• Disable healthchecks by default by @tanaypf9 in #122
• Update healthcheck in README by @tanaypf9 in #124
• Mapped OS_PROJECT_DOMAIN_NAME to OS_DOMAIN_NAME and OS_PROJECT_NAME t… by @patil-pratik-87 in #130
• add IpAddress and VM state info to migrationtemplate status by @OmkarDeshpande7 in #133
• 106 - disabled stopped VMs from migrating and notified with a tooltip by @patil-pratik-87 in #136
• Allowed one to many network mappings from VMware to Openstack by @patil-pratik-87 in #137
• UI: If the form is not submitted CRs created, should be deleted by @patil-pratik-87 in #139
• UI: Handle VM refresh with additional put call to migration template and add adjust the timeout needed for it to reflect latest detail by @patil-pratik-87 in #142
• check if disks have os installed in lexical order (release) by @OmkarDeshpande7 in #140

Known Issues

• If the VM to be migrated has an LV spanning multiple physical devices used as boot volume unless both are mounted simultaneously to the OS-VM, vJailbreak cannot detect whether it is bootable, or not. (issue link)
• If a user turns on a VM on VCenter after migration and tries to migrate it again, the migration object will not be created. In this case, the user should delete the VM from PCD/Openstack before trying the migration again. This error will be pushed up the stack for visibility.

New Contributors

• @patil-pratik-87 made their first contribution in #130
• @OmkarDeshpande7 made their first contribution in #133

Full Changelog: v0.1.1...16.01