Add support for creating cloned UVMs.#838
Add support for creating cloned UVMs.#838ambarve merged 5 commits intouser/ambarve/lcpr1_vmcomputefrom
Conversation
ambarve
changed the title
ambarve
force-pushed
the
user/ambarve/lcpr2_clone_uvm
branch
from
3849558 to
e010e37
Compare
ambarve
force-pushed
the
user/ambarve/lcpr2_clone_uvm
branch
2 times, most recently
from
d71a09d to
5ba0510
Compare
ambarve
changed the title
|
Please rebase these commits into a more curated set for review and check-in. |
|
What is inherited from the template VM, versus being specified by the new HCS document? e.g. if the VM already had a given VHD attached to it, does the clone also attempt to connect that VHD? |
|
@kevpar The resources that can be hot-added are always cloned (as of now it's VSMB and SCSI). So even if a VHD was added in the HCS document of the template VM we will still add it via the cloning process instead of adding it into the HCS document of the cloned VM. Everything else will be specified in the HCS document of the clone. |
I see that we explicitly do a "clone" operation for some resources, but I'm wondering about what things are naturally inherited from the template via HCS. If we just created a new VM compute system with a template ID, what resources or other characteristics would be inherited from the template? |
|
HCS doesn't automatically inherit any properties from the template but you still need to make sure that configuration doc of the clone is identical (except for some parameters) to the configuration doc of the template (Otherwise clone startup fails). And so most of the properties that are defined in the template configuration doc will automatically be copied over to the clone. I don't know exactly which properties can be altered in the configuration doc of the clone but I can find that out. |
ambarve
force-pushed
the
user/ambarve/lcpr2_clone_uvm
branch
from
9ab44b4 to
4fc5e7e
Compare
ambarve
force-pushed
the
user/ambarve/lcpr2_clone_uvm
branch
from
4fc5e7e to
562bfc4
Compare
ambarve
force-pushed
the
user/ambarve/lcpr2_clone_uvm
branch
from
562bfc4 to
3076f21
Compare
This is one of the many small PRs that enable the support for late cloning. This commit adds the template and clone creation support in the uvm module. Signed-off-by: Amit Barve <ambarve@microsoft.com>
This is one of the many small PRs that enable the support for late cloning. This commit adds the set of functions required for adding network namespace and network endpoints to cloned UVMs. Signed-off-by: Amit Barve <ambarve@microsoft.com>
ambarve
force-pushed
the
user/ambarve/lcpr1_vmcompute
branch
from
1558e2d to
c112ff9
Compare
ambarve
force-pushed
the
user/ambarve/lcpr2_clone_uvm
branch
from
3076f21 to
aa48bc3
Compare
This is one of the many small PRs that enable the support for late cloning.This commit adds the set of functions that expose the late cloning functionality from hcsshim and adds new annotations for clients to use the late cloning feature. Signed-off-by: Amit Barve <ambarve@microsoft.com>
…aner Add support for creating late clones via hcsshim
…changes Add support for creating network namespaces inside cloned uvms.
4 participants
This is one of the many small PRs that enable the support for late cloning.
This commit adds the template and clone creation support in the uvm module.
Signed-off-by: Amit Barve ambarve@microsoft.com