Move crates to mono repo

[andreeaflorescu]

This issue tracks the progress of moving the rust-vmm crates to the mono-repo: github.com/rust-vmm/rust-vmm/.

Status

Below are the crates that need to be moved to the mono repo.
Status: Not Started, In Progress, Done.
Priority: 1 to 10, where 1 is highest priority and 10 is lowest priority.

Crate	Status	Priority	Owner	Tracking Issue
vmm-sys-util	In Progress	1	@RuoqingHe	#265
vm-memory	Not Started	2	@andreeaflorescu
vhost-device	Not Started	10	None
linux-loader	Not Started	10	None
vhost	Not Started	10	None
mshv	Not Started	10	None
acpi_tables	Not Started	10	None
vm-virtio	Not Started	10	None
vm-allocator	Not Started	10	None
vfio	Not Started	10	None
seccompiler	Not Started	10	None
kvm	Not Started	10	@phip1611
vm-superio	Not Started	10	None
vm-fdt	Not Started	10	None
event-manager	Not Started	10	None
xen	Not Started	10	None
vm-device	Not Started	10	None

[andreeaflorescu]

Related to rust-vmm/vmm-sys-util#180

[andreeaflorescu]

The proposed approach to handle this is to start with the crates that cause the biggest pain points when doing updates. Right now it looks like these are the 2 leaf crates vm-memory and vmm-sys-util.

We need to pick up the next one after vm-memory. @rbradford could you chime in here? Where are the pain points in Cloud Hypervisor?

[rbradford]

The proposed approach to handle this is to start with the crates that cause the biggest pain points when doing updates. Right now it looks like these are the 2 leaf crates vm-memory and vmm-sys-util.

We need to pick up the next one after vm-memory. @rbradford could you chime in here? Where are the pain points in Cloud Hypervisor?

@andreeaflorescu Welcome back! Thanks for jumping in on this. I think that a monorepo will help a lot since all the releases can be made together. One of the problems we have is that if a crate is bumped to an API breaking release (like linux-loader to the new vm-memory 0.18.0) we can't consume that updated version until all the other crates have moved to vm-memory 0.18.0. This is why I asked that we didn't update that crate until the migration to the monorepo was done (we could have updates all the crates with one PR.)

[phip1611]

Since I've already got my feet wet with https://github.com/rust-vmm/kvm a couple of months ago, I can take care of that! Unfortunately I can't promise any progress in the next 14 days.

[RuoqingHe]

Since I've already got my feet wet with https://github.com/rust-vmm/kvm a couple of months ago, I can take care of that! Unfortunately I can't promise any progress in the next 14 days.

No worries, I we get there and you happen to be busy, I can take care of it 😉

[andreeaflorescu]

We have a wiki with steps to follow for the move to the mono-repo: https://github.com/rust-vmm/rust-vmm/wiki/How-to-migrate-a-repo.

One thing that is still missing is for the crates to specify their dependencies as local path when their dependencies are already part of the mono-repo. This is a bit hard to explain in words, so I'll add an example with a commit to exemplify what needs to be done. I'll do this as part of vm-memory migration.

[bytefire]

Is the list above updated? i.e. the crates which don't have an owner for the move to mono repo are open for owner? I see quite a bit of activity in vfio right now. Is someone pencilled in to move that crate?