Skip to content

[internal/hcs] Migrate package from HCS V1 to V2#2735

Draft
rawahars wants to merge 1 commit into
microsoft:mainfrom
rawahars:migrate_hcs_v1_v2
Draft

[internal/hcs] Migrate package from HCS V1 to V2#2735
rawahars wants to merge 1 commit into
microsoft:mainfrom
rawahars:migrate_hcs_v1_v2

Conversation

@rawahars
Copy link
Copy Markdown
Contributor

Presently, we were using HCS V1 (vmcompute) within internal/hcs but it has been deprecated and therefore, we are moving to use computecore within hcs package.

@rawahars rawahars force-pushed the migrate_hcs_v1_v2 branch 12 times, most recently from 9195869 to c5e671c Compare May 14, 2026 13:03
Presently, the implementation of Start method used computecore i.e. HCS V2 for starting the compute system. However, the same compute system was created using HCS V1 and therefore, due to an incompatibility within HCS between V1 and V2 APIs, this was failing.

Therefore, as a stop gap, we have reverted the Start method to use the HCS V1 API. During our full scale migration to V2 APIs, this will be taken care of properly.

Signed-off-by: Harsh Rawat <harshrawat@microsoft.com>
@rawahars rawahars force-pushed the migrate_hcs_v1_v2 branch from c5e671c to 4b3a066 Compare May 17, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant