Azure / hpcpack

The repo to track public issues for Microsoft HPC Pack product.
MIT License
30 stars 12 forks source link

Upgrade to .NET 5.0 #18

Open abx78 opened 3 years ago

abx78 commented 3 years ago

Problem Description

When linking the nuget packages to the project I get this warning:

warning NU1701: Package 'Microsoft.HPC.SDK 6.0.7205' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework 'net5.0'. This package may not be fully compatible with your project.

Steps to Reproduce

When using the library various compatibility issues get raised. For example, calling the method ConnectServiceAsClient on the Scheduler raise an exception as Microsoft.Threading.Tasks, Version 1.0.12.0 cannot be found.

YutongSun commented 2 years ago

Hi abx78,

HPC Pack SDK does not support .Net 5 yet. The support is still on our roadmap.

MarcoEnxuto commented 2 years ago

Hi, @YutongSun . Are we still on track? Thanks. I guess we might need to consider .Net 6 or 7.

YutongSun commented 2 years ago

Yes, we shall consider .Net 7.

MarcoEnxuto commented 2 years ago

Thanks for the reply @YutongSun. Do you have an approximate ETA? Just to manage our expectations. Thanks.

JDA88 commented 1 year ago

We will update our HPC farms early next year and the framwork will be base on .NET Core 7. Compatibility of the Microsoft.HPC.SDK with .NET Core would be very helpfull

MarcoEnxuto commented 1 year ago

Hi @YutongSun , do you have anything to share with us? Seems quite a while with no news at all.

YutongSun commented 1 year ago

@MarcoEnxuto @JDA88 Yes, we are planning a preview release later this year.

YutongSun commented 1 year ago

@MarcoEnxuto @JDA88 @abx78 , since we are working on the .Net 6 or .NetStandard 2.0 SDKs, could you help comment on the requirements? E.g. are you running the client on Windows? Is there any requirement for the client to run on Linux?

JDA88 commented 1 year ago

On our side, running the client on Windows. Using mostly to connect to HeadNode, get job list, status and create / start / stop jobs.

Blok-Dev1 commented 1 year ago

@MarcoEnxuto @JDA88 @abx78 , since we are working on the .Net 6 or .NetStandard 2.0 SDKs, could you help comment on the requirements? E.g. are you running the client on Windows? Is there any requirement for the client to run on Linux?

I assume the SOA(WCF) will be deprecated and replaced with what?

MarcoEnxuto commented 1 year ago

Hi @YutongSun, is the same as @JDA88 said. Here's a quick question regarding this, are you planning adding events to the event viewer? Linux does not have event viewer, but has something similar....

YutongSun commented 1 year ago

@MarcoEnxuto @JDA88 @abx78 , since we are working on the .Net 6 or .NetStandard 2.0 SDKs, could you help comment on the requirements? E.g. are you running the client on Windows? Is there any requirement for the client to run on Linux?

I assume the SOA(WCF) will be deprecated and replaced with what?

We plan to continue to support SOA(WCF) in this new SDK release. And in the long run, we will provide an alternative SOA implementation.

YutongSun commented 1 year ago

Hi @YutongSun, is the same as @JDA88 said. Here's a quick question regarding this, are you planning adding events to the event viewer? Linux does not have event viewer, but has something similar....

We have limited events in event viewer and most detailed service logs can be found the service .bin log files. There is no plan to add back detailed events for the duplication.

abx78 commented 1 year ago

@MarcoEnxuto @JDA88 @abx78 , since we are working on the .Net 6 or .NetStandard 2.0 SDKs, could you help comment on the requirements? E.g. are you running the client on Windows? Is there any requirement for the client to run on Linux?

The scenarios listed by @JDA88 sum it up. This is the typical way we post jobs is the following

var scheduler = new Scheduler();
scheduler.ConnectServiceAsClient(hpcCluster, () => username, username, password);
var job = scheduler.CreateJob();
job.OnJobState += (sender, arg) => OnJobStateChanged(sender, arg, job);
scheduler.AddJob(job);
scheduler.SubmitJobById(job.Id, username, password);

Thanks in advance

Blok-Dev1 commented 1 year ago

@MarcoEnxuto @JDA88 @abx78 , since we are working on the .Net 6 or .NetStandard 2.0 SDKs, could you help comment on the requirements? E.g. are you running the client on Windows? Is there any requirement for the client to run on Linux?

I assume the SOA(WCF) will be deprecated and replaced with what?

We plan to continue to support SOA(WCF) in this new SDK release. And in the long run, we will provide an alternative SOA implementation.

Thank you very much, appreciate.

MarcoEnxuto commented 1 year ago

Hi @YutongSun, is the same as @JDA88 said. Here's a quick question regarding this, are you planning adding events to the event viewer? Linux does not have event viewer, but has something similar....

We have limited events in event viewer and most detailed service logs can be found the service .bin log files. There is no plan to add back detailed events for the duplication.

Ok. We're using event viewer to register every job passing through the Filters feature. Any updates regarding the expected roadmap? image

YutongSun commented 1 year ago

We are still working on the roadmap planning.

YutongSun commented 11 months ago

FYI. We just released .Net SDK preview. Check it out here.