Service Fabric 6.0 Release


Service Fabric version 6.0 of the runtime and .NET SDK 2.8 is now available, packed with new features, improvements, and bug fixes.

Updated: This post has been updated on 9/28 with link to a release notes document and more high level info about the release.

General availability of Service Fabric on Linux

As part of this release we are happy to announce the general availability of Service Fabric as a container orchestrator on Linux. The Linux environment is identical to the Windows runtime for container orchestration and Service Fabric fully supports containerized applications running on Linux. We currently support Ubuntu 16.04 for the Linux clusters, other Linux OSes including Red Hat Enterprise Linux are on the roadmap. For more information please see this Azure blog post.

Container and Resource Governance Improvements

We've made a lot of improvements to our container support and resource governance across all hosted workloads in Service Fabric (Reliable Services, Guest executables and containers).

SDK Previews for Java and .NET

In this release there is also a preview of the both the Java 1.0 and the .NET 3.0 SDK. The previews include features across Linux and Windows for Reliable Services written in Java or using .NET core 2.0. You can now build reliable stateless services, reliable stateful services and reliable Actors using .NET core 2.0 (targeting both Windows and Linux), using Java targeting Linux and using .NET Framework targeting Windows.

Service Remoting v2

A new version of Service Remoting is now available for reliable services and actors. The new version works the same as the current service remoting, but introduces several features and improvements, including custom serialization and memory use optimizations such as buffer pooling and reduction of buffer copying.

Compose Deployments

Compose deployments now support upgrades, enabling you to take advantage of Service Fabric rolling upgrades for your containerized workloads using compose, like any other application in Service Fabric. The compose APIs have changed in this release, but the runtime still supports 2.7 SDKs for deploying compose applications.

Service Fabric CLI

A new cross platform Service Fabric CLI - sfctl - has been released. Sfctl supports all clusters running in Azure, on-premises, in any other cloud and locally and is even available in Azure Cloud Shell, so you can control your Service Fabric clusters directly from within the Azure Portal - using sfctl.

Release Notes

The release notes for this release, including direct download links and repository references can be found here: Microsoft-Azure-Service-Fabric-Release-Notes-SDK-2.8.0-Runtime-6.0.0

Cluster Upgrade

Version 6.0.120 (Linux) and 6.0.211 (Windows) of the runtime is available for new and existing clusters in Azure now. Existing Windows clusters will not be upgraded automatically with these releases. To upgrade your cluster, change the upgrade setting to manual and choose this version to start the upgrade. Linux clusters on any version prior to 6.0.120 are not upgradeable.

Standalone Package

The standalone package for Windows version 6.0 will be available in the next few weeks. Check back here later for information.

Learn more about Service Fabric 6.0 release

Head over to our docs landing page for great quickstarts and tutorials: https://docs.microsoft.com/en-us/azure/service-fabric

Try Service Fabric in a Party Cluster: https://try.servicefabric.azure.com

A lot of the features in this release have been presented at the Microsoft Ignite conference this week. Check out these YouTube videos to view a recording of the talks:

All the best,

The Service Fabric Team


Comments (40)

  1. Had lots of hassle installing this on VS2017. Ended up having to remove the Service Fabric Tools from within VS and uninstalling all previous versions of Service Fabric and the SDK and then installing – just thought I’d put this here in case anyone else has any problems

    1. Vijay Devappa says:

      What did you do to get this thing to install? It failed me everywhere. Saying cannot delete file, etc.

      1. Gor Rustamyan says:

        I was getting same issue, with cant uninstall old fabric version. What i found, that all fabric files was deleted except LeasLayr.sys and KtlLogger.sys drivers located under C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code . So i restarted under under safe mode and deleted them manualy.

        1. For install issues – these are now fixed as part of the Web Platform Installer. Please see this issue for tracking: https://github.com/Azure/service-fabric-issues/issues/483 If you still encounter issues, please follow up on GitHub. Thank You.

          1. Jef Schraag says:

            The fix via Web Platform Installer did not solve my problem. I reported it in the thread on https://github.com/Azure/service-fabric-issues/issues/483

  2. Seb says:

    Are there any plans for the Service Fabric to be released for Linux on premise?

    1. Deep Kapur says:

      Hi Seb, regarding Service Fabric for Linux on prem – we are currently working towards it and will have an update in the coming months. Thanks!

  3. Bert says:

    But where are the release notes? What’s the point of announcing with NO details?

    1. Juho Hanhimäki says:

      Hope the notes come soon as promised 🙂

      Can’t really do any upgrading before seeing the changes.

    2. Demetri says:

      I was quite surprised to see that 6.0 is available for immediate install on azure clusters with no detailed release notes. I am eagerly await the detailed notes as well!

      1. Apologies for the release notes to come in late – they will be posted today. We have not started upgrading existing cluster to 6.0. At this point it’s a manual upgrade if you choose to do so.

  4. Vijay Devappa says:

    It blew my old SDK and failed to install. This sucks.

  5. Vijay Devappa says:

    Ok, I managed to get it installed by booting into command prompt only mode and deleting the C:\Program Files\Microsoft Service Fabric folder. Otherwise, even if nothing is actually using it, it will not install the SDK.

  6. Vijay Devappa says:

    As Microsoft will not provide any help with the install. The best way to get this version to install is to first uninstall the older SDK and Runtime from Programs and then install the new SDK and run time from Web PI. Otherwise it will fail.

    1. Service Fabric issues that are not production critical issues in Azure are handled on GitHub. Please check this article for information about how to get support: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-support
      For the install issue wit the 2.8 SDK – please take a look at this issue:https://github.com/Azure/service-fabric-issues/issues/483

  7. John Garland says:

    Problems with uninstall are documented here : https://github.com/Azure/service-fabric-issues/issues/483
    WebPI installer is being updated to fix.

  8. Jack Bond says:

    Literally the worst major version launch IN HISTORY. Did the Ignite show take you guys by surprise? Is there going to be a document which outlines what changed, or should we just fire up Object Browser?

    1. Granville Schmidt says:

      Please provide release notes.

  9. When will the upgrade to 6 be available for the standalone / on premises installs of Service Fabric?

    I’ve read some people have had success doing a manual upgrade in Azure but standalone seems to be still stuck on 5.7 at this point.

    Details:
    For my on premises clusters Service Fabric Explorer does not show a warning that an upgrade is available.

    When I run the powershell command Get-ServiceFabricRegisteredClusterCodeVersion on a node to view available versions 5.7 is the highest version.

    When I try to download the current standalone installer the https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-standalone-deployment-preparation page returns a document named “Microsoft.Azure.ServiceFabric.WindowsServer.5.7.198.9494.zip”.

    When I try to download the CAB file to do a manual upgrade the https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-creation-for-windows-server page returns a file named “MicrosoftAzureServiceFabric.5.7.198.9494.cab”.

    1. Deep Kapur says:

      Hi Scott, we have not yet released a version 6.0 for the standalone offering yet. We needed to do some additional testing and thus delayed the release by a little bit. Please continue to follow this blog for announcements on releases. When a new version is released, the links you mentioned and the APIs will be updated to reflect the new version number.

      1. I noticed my clusters are telling me that CodeVersion 6.0.219.9494 is now available if this is still a concern for anyone.

  10. Granville Schmidt says:

    Please provide release notes.

  11. Rhino says:

    Where can the 3.0 SDK Preview be downloaded? Link?

    1. The 3.0 SDK Preview is a set of NuGet packages. The links are in the release notes linked in this blog post.

  12. At present, it appears that the 3.0.211-preview version of the Microsoft.ServiceFabric.*.Wcf NuGet packages have not been published to nuget.org. The latest version is 2.8.211. The 2.8.211 version of the Wcf packages cannot be used with the other v3 preview NuGet packages.

    1. Hi Charles, the 3.0-preview packages are there for .Net 2.0 standard support. WCF does not comply with the .Net 2.0 standard specification, so we did not include that package in the preview version. In the RTO release of 3.0 there will be an updated package.

  13. Jimmy Sorting says:

    Awesome guys, we’ve really been looking forward to this release! I want to thank the Service Fabric team for this amazing product that enables my team to continuously deliver great reliable software to our customer many times a day without downtime. Thank you, sincerely!

    1. Thank you Jimmy – appreciate your feedback!

  14. Nick Randell says:

    From some experiments, it looks netstandard2.0 is not supported for a windows azure cluster, or for debugging on a local development cluster. All the samples that talk about netstandard2.0 have a deploy.cmd or deploy.sh that runs dotnet. It doesn’t look like dotnet is installed on the azure cluster as part of the upgrade.
    Is this correct or have I missed something?
    Is there a correct way of building a visual studio solution for a service fabric application that fully supports netcoreapp2.0?

    1. Hi Nick, There are multiple things that need to align here :-). First .net 2.0 has to be installed on the cluster and your local dev box. Currently they are not part of SF clusters created in Azure, but we are working on this – tracking here: https://github.com/Azure/service-fabric-issues/issues/500. You can install the runtime via a VMSS extension: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/extensions-customscript. On your dev box the same apply – you need the SDK installed: https://www.microsoft.com/net/download/core.

      As for Visual Studio – this week we expect to release an update to the Service Fabric tooling, which will give you Visual Studio templates that support.net core 2.0 services.

      1. Nick Randell says:

        Thanks for the reply! It looks like my previous comments on releases apply here – please document these sort of things in the release notes. I’m really impressed with SF, but sometimes the new releases seem to take some time to stabilise, or there are some black holes in the information. Keep up the good work though!

  15. Xiaodong Li says:

    After installed latest SDK, I tried preview nuget packages targeting netcore2.0, seems local debugging (F5) is not working, after published sfproj to cluster, debugging from VS by attaching to process works.

    I also tried VS preview (2017.4) and had the same problem. Is this a known issue? thanks!

    1. Hi Xiaodong Li,

      You will need the preview of VS2017 Update 5 for the full support. We expect it to release this week.

  16. Jamie says:

    I’ve upgraded my Azure cluster to 6.0.211.9494, and one (of 16) services to use targetframework netcoreapp2.0 then updated all nuget packages for that particular project.

    VSTS builds fine, but my deployment fails with:

    2017-10-03T22:35:06.3472075Z ##[error]The my.aspnet.core.app.exe is not found.

    Am I being slow here?
    Do I need to upgrade all services to netcoreapp2.0?

    help! (please!)

    1. Jamie says:

      sorry – the error was actually:

      2017-10-03T22:35:06.3472075Z ##[error]The EntryPoint my.aspnet.core.app.exe is not found.

      1. Nick Randell says:

        Hi Jamie

        Looks like Mikkel responded to this earlier – the azure clusters don’t have dotnet core installed on them. It can be done, but is a bit painful at the moment. I’ve just upgrade the nuget packages, but still running net461 until this gets a bit easier.

  17. MonDeveloper says:

    Hi guys, this release seems very promising, such a long waited features!
    Anyway, it is not appreciated as it should because of the frustration it provide to the community.
    I mean:
    – it promised .net core (but you cannot delivery on Azure because the Azure SF Cluster don’t run .net core 2.0)
    – it promised many features (but not on prem because many tests are still in progress)
    – etc…

    So, I’m not writing this comment to offend anyone, we all know how much is complex this work, just to ask you to be more carefull with this kind of deploy 🙂

    By the way, do you have a roadmap (even unofficial) about the release date of the on prem installer?

    thanks in advance!

  18. Graham McAnany says:

    When I deploy a Service Fabric application with a stateful ASP.NET Core service to my local Service Fabric instance, the service fails to start stating that System.IO.FileSystem.AccessControl.dll or one of its dependencies cannot be found. Stateless ASP.NET Core services deploy ok.
    I’m using Microsoft Azure Service Fabric 6.0.211.9494 and SDK 2.8.211.9494. The NuGet package versions are as follows:

    I’ve tried Visual Studio 2017 v15.3.5 and v15.5 Preview and both exhibit the same behaviour. If I downgrade the NuGet packages to the previous stable versions, the deployment of stateful ASP.NET Core service works again, but won’t support .Net Standard 2.0.
    Is anyone else getting these errors and is there a fix? Full Diagnostic Error available on request.

    1. Graham McAnany says:

      Package versions resulting in error: Microsoft.AspNetCore Version=”2.0.0″, Microsoft.ServiceFabric Version=”6.1.211-preview”, Microsoft.ServiceFabric.AspNetCore.Kestrel Version=”3.0.211-preview”, Microsoft.ServiceFabric.Data Version=”3.0.211-preview”, Microsoft.ServiceFabric.Services Version=”3.0.211-preview”

Skip to main content