Runtime environment

[Benedikt Haug (benedikt-haug)]

Dear developers,
I'm unsure about the runtime environment for this tool.
Is a requirement for migratekit that it must be running in the migration-target OpenStack, given the following error?
Error: Get "http://169.254.169.254/openstack/latest/meta_data.json": dial tcp 169.254.169.254:80: i/o timeout

I found that bit of code here and it seems to be hardcoded:

migratekit/internal/openstack/util.go

Line 20 in a1bc82e

req, err := http.NewRequest("GET", "http://169.254.169.254/openstack/latest/meta_data.json", nil)

I'd ideally like to run it on some machine that can reach both OpenStack and VMware. Is that supported?

Kind regards,
Benedikt

[Michael Salo (michael-salo)]

Migrator VM must be running on Openstack and http://169.254.169.254/openstack/latest/meta_data.json is default Openstack Metadata URL.

"I'd ideally like to run it on some machine that can reach both OpenStack and VMware. Is that supported?" - Migrator VM have to have access to VMware env.

[Mohammed Naser (mnaser)]

The reason its this way is because we can create a Cinder volume and attach and copy to it and then move it to the target system.

There is no other way other than this. If we take another approach then we need the thing to run as admin and have access to the storage backend and implement ability to mount all sorts of backend.