Merge pull request #79056 from MicrosoftDocs/release-ga-servicefabric-6-5

Release ga servicefabric 6 5

Author: huypub

articles/service-fabric/media/fabric.png

@@ -0,0 +1,84 @@
+---
+title: Azure Service Fabric releases
+description: Release notes for the latest features and improvements in Service Fabric.
+author: athinanthny
+manager: chackdan
+ms.author: atsenthi
+ms.date: 6/10/2019
+ms.topic: conceptual
+ms.service: service-fabric
+hide_comments: true
+hideEdit: true
+---
+
+# Service Fabric releases
+
+| <a href="https://github.com/Azure/Service-Fabric-Troubleshooting-Guides" target="blank">Troubleshooting Guides</a> 
+| <a href="https://github.com/Azure/service-fabric-issues" target="blank">Issue Tracking</a> 
+| <a href="https://docs.microsoft.com/azure/service-fabric/service-fabric-support" target="blank">Support Options</a> 
+| <a href="https://docs.microsoft.com/azure/service-fabric/service-fabric-versions" target="blank">Supported Versions</a> 
+| <a href="https://azure.microsoft.com/resources/samples/?service=service-fabric&sort=0" target="blank">Code Samples</a>
+
+This article provides more information on the latest releases and updates to the Service Fabric runtime and SDKs.
+
+## **What's new in Service Fabric**
+
+### Service Fabric 6.5
+
+The latest Service Fabric release includes supportability, reliability, performance improvements, new features, bug fixes, and enhancements to ease cluster and application lifecycle management.
+
+#### Breaking changes
+
+- Service Fabric 6.5 is the final release with Service Fabric tools support in Visual Studio 2015. Customers are advised to move to [Visual Studio 2019](https://visualstudio.microsoft.com/vs/compare/) going forward.
+
+- TraceViewer, the tool for parsing Service Fabric trace logs has been updated to be CSV compliant for the Service Fabric 6.5 release. This breaking change could impact you in two ways:  
+    1. Any custom tools that depend on TraceViewer will require updates for the new logging format.
+    2. If you use TraceViewer, you'll need to upgrade it to the newer version shipped with Service Fabric 6.5.
+
+Here's what's new in Service Fabric 6.5:
+
+#### New features for Windows
+
+- Patch Orchestration Application (POA) version 1.4.0 includes many self-diagnostic improvements. Customers of POA are recommended to move to this version.
+
+- Service Fabric Explorer now also includes applications uploaded to image store.
+
+- SDK Service Fabric runtime installer now supports the `/force` flag to automatically close conflicting processes.  
+
+- SDK Service Fabric runtime installer now supports the `/uninstall` flag for command-line uninstallation.
+
+- [EventStore Service is enabled by default](service-fabric-visualizing-your-cluster.md#event-store) for Service Fabric 6.5 clusters unless a customer has opted out.
+
+- Added [replica lifecycle events](service-fabric-diagnostics-event-generation-operational.md#replica-events) for stateful services.
+
+- Better visibility of seed node status, including cluster-level warnings if a seed node is unhealthy (*Down*, *Removed* or *Unknown*).
+
+- [Service Fabric Application Disaster Recovery Tool](https://github.com/Microsoft/Service-Fabric-AppDRTool) allows users of Service Fabric stateful services to get back live soon in case the primary cluster encounters a disaster. The tool constantly synchronizes the data from the application running on the primary cluster on the standby application on secondary using periodic backup and restore.
+
+#### New features for Linux
+
+- Visual Studio support for [publishing .NET Core apps to Linux-based clusters](service-fabric-how-to-publish-linux-app-vs.md).
+
+- [Azure Service Fabric CLI (SFCTL)](https://docs.microsoft.com/azure/service-fabric/service-fabric-cli) will be installed automatically for Service Fabric 6.5 (and later versions) when you upgrade or create new clusters.
+
+- [SFCTL](https://docs.microsoft.com/azure/service-fabric/service-fabric-cli) is installed by default on MacOS/Linux OneBox clusters.
+
+- General machine bootstrap script provided to set up prerequisites for Service Fabric Linux nodes for deployment & upgrade scenarios.
+
+- Added [replica lifecycle events](service-fabric-diagnostics-event-generation-operational.md#replica-events) for stateful services.
+
+- Better visibility of seed node status, including cluster-level warnings if a seed node is unhealthy (*Down*, *Removed* or *Unknown*).
+
+## Previous versions
+
+### Service Fabric 6.4 releases
+
+| Release date | Release | More info |
+|---|---|---|
+| November 30, 2018 | [Azure Service Fabric 6.4 (RTO)](https://blogs.msdn.microsoft.com/azureservicefabric/2018/11/30/azure-service-fabric-6-4-release/)  | [Release notes](https://msdnshared.blob.core.windows.net/media/2018/12/Service-Fabric-6.4-Release.pdf)|
+| December 12, 2018 | [Azure Service Fabric 6.4 refresh for Windows clusters (CU2)](https://blogs.msdn.microsoft.com/azureservicefabric/2018/12/12/azure-service-fabric-6-4-refresh-for-windows-clusters/)  | [Release notes](https://msdnshared.blob.core.windows.net/media/2018/12/Links.pdf)  |
+| February 4, 2019 | [Azure Service Fabric 6.4 CU3](https://blogs.msdn.microsoft.com/azureservicefabric/2019/02/04/azure-service-fabric-6-4-refresh-release/) | [Release notes](https://msdnshared.blob.core.windows.net/media/2019/02/Service-Fabric-6.4CU3-Release-Notes.pdf) |
+| March 4, 2019 | [Azure Service Fabric 6.4 CU4](https://blogs.msdn.microsoft.com/azureservicefabric/2019/03/12/azure-service-fabric-6-4-refresh-release-2/) | [Release notes](https://msdnshared.blob.core.windows.net/media/2019/03/Service-Fabric-6.4CU4-Release-Notes.pdf)
+| April 8, 2019 | [Azure Service Fabric 6.4 CU5](https://blogs.msdn.microsoft.com/azureservicefabric/2019/04/08/azure-service-fabric-6-4-refresh-release-5/) | [Release notes](https://msdnshared.blob.core.windows.net/media/2019/04/Service-Fabric-6.4CU5-ReleaseNotes3.pdf)
+| May 2, 2019 | [Azure Service Fabric 6.4 CU6](https://blogs.msdn.microsoft.com/azureservicefabric/2019/05/02/azure-service-fabric-6-4-refresh-release-3/) | [Release notes](https://msdnshared.blob.core.windows.net/media/2019/05/Service-Fabric-64CU6-Release-Notes-V2.pdf)
+| May 28, 2019 | [Azure Service Fabric 6.4 CU7](https://blogs.msdn.microsoft.com/azureservicefabric/2019/05/28/azure-service-fabric-6-4-refresh-release-4/) | [Release notes](https://msdnshared.blob.core.windows.net/media/2019/05/Service_Fabric_64CU7_Release_Notes1.pdf)

articles/service-fabric/media/service-fabric-how-to-vs-remote-linux-cluster/build-application-remote-linux.png

@@ -92,7 +92,7 @@ For more information on how to configure the SetupEntryPoint, see [Configure the
 </Settings>
 ```
 
-A Service Fabric Service **Endpoint** is an example of an Service Fabric Resource; A Service Fabric Resource can be declared/changed without changing the compiled code. Access to the Service Fabric Resources that are specified in the service manifest can be controlled through the **SecurityGroup** in the application manifest. When an Endpoint Resource is defined in the service manifest, Service Fabric assigns ports from the reserved application port range when a port isn't specified explicitly. Read more about [specifying or overriding endpoint resources](service-fabric-service-manifest-resources.md).
+A Service Fabric Service **Endpoint** is an example of a Service Fabric Resource. A Service Fabric Resource can be declared/changed without changing the compiled code. Access to the Service Fabric Resources that are specified in the service manifest can be controlled through the **SecurityGroup** in the application manifest. When an Endpoint Resource is defined in the service manifest, Service Fabric assigns ports from the reserved application port range when a port isn't specified explicitly. Read more about [specifying or overriding endpoint resources](service-fabric-service-manifest-resources.md).
 
 
 <!--
@@ -160,7 +160,11 @@ Within the ServiceManifestImport, you override configuration values in Settings.
 
 **Certificates** (not set in the preceding example) declares the certificates used to [setup HTTPS endpoints](service-fabric-service-manifest-resources.md#example-specifying-an-https-endpoint-for-your-service) or [encrypt secrets in the application manifest](service-fabric-application-secret-management.md).
 
-**Policies** (not set in the preceding example) describes the log collection, [default run-as](service-fabric-application-runas-security.md), [health](service-fabric-health-introduction.md#health-policies), and [security access](service-fabric-application-runas-security.md) policies to set at the application level.
+**Policies** (not set in the preceding example) describes the log collection, [default run-as](service-fabric-application-runas-security.md), [health](service-fabric-health-introduction.md#health-policies), and [security access](service-fabric-application-runas-security.md) policies to set at the application level, including whether the service(s) have access to the Service Fabric runtime.
+
+> [!NOTE] 
+> By default, Service Fabric applications have access to the Service Fabric runtime, in the form of an endpoint accepting application-specific requests, and environment variables pointing to file paths on the host containing Fabric and application-specific files. Consider disabling this access when the application hosts untrusted code (i.e. code whose provenance is unknown, or which the application owner knows not to be safe to execute). For more information, please see [security best practices in Service Fabric](service-fabric-best-practices-security.md#platform-isolation). 
+>
 
 **Principals** (not set in the preceding example) describe the security principals (users or groups) required to [run services and secure service resources](service-fabric-application-runas-security.md).  Principals are referenced in the **Policies** sections.
 

articles/service-fabric/media/service-fabric-how-to-vs-remote-linux-cluster/create-application-remote-linux.png

@@ -240,6 +240,18 @@ By default, Windows Defender antivirus is installed on Windows Server 2016. For
 > Refer to your Antimalware documentation for configuration rules if you are not using Windows Defender. 
 > Windows Defender isn't supported on Linux.
 
+## Platform Isolation
+By default, Service Fabric applications are granted access to the Service Fabric runtime itself, which manifests itself in different forms: [environment variables](service-fabric-environment-variables-reference.md) pointing to file paths on the host corresponding to application and Fabric files, an inter-process communication endpoint which accepts application-specific requests, and the client certificate which Fabric expects the application to use to authenticate itself. In the eventuality that the service hosts itself untrusted code, it is advisable to disable this access to the SF runtime - unless explicitly needed. Access to the runtime is removed using the following declaration in the Policies section of the application manifest: 
+
+```xml
+<ServiceManifestImport>
+    <Policies>
+        <ServiceFabricRuntimeAccessPolicy RemoveServiceFabricRuntimeAccess="true"/>
+    </Policies>
+</ServiceManifestImport>
+
+```
+
 ## Next steps
 
 * Create a cluster on VMs, or computers, running Windows Server: [Service Fabric cluster creation for Windows Server](service-fabric-cluster-creation-for-windows-server.md).

articles/service-fabric/media/service-fabric-how-to-vs-remote-linux-cluster/create-service-remote-linux.png

@@ -101,6 +101,40 @@ More details on application upgrades can be found [here](service-fabric-applicat
 | --- | --- | ---| --- | --- | --- |
 | 18940 | PartitionReconfigured | LifeCycle | A partition reconfiguration has completed | RA | Informational | 
 
+## Replica events
+
+**Replica lifecycle events**
+
+| EventId | Name | Category | Description |Source (Task) | Level |
+| --- | --- | ---| --- | --- | --- |
+| 61701 | ReliableDictionaryOpened | LifeCycle | Reliable dictionary has opened | DistributedDictionary | Informational |
+| 61702 | ReliableDictionaryClosed | LifeCycle | Reliable dictionary has closed | DistributedDictionary | Informational |
+| 61703 | ReliableDictionaryCheckpointRecovered | LifeCycle | Reliable dictionary has recovered its checkpoint | DistributedDictionary | Informational |
+| 61704 | ReliableDictionaryCheckpointFilesSent | LifeCycle | Replica has sent reliable dictionary's checkpoint files | DistributedDictionary | Informational |
+| 61705 | ReliableDictionaryCheckpointFilesReceived | LifeCycle | Replica has received reliable dictionary's checkpoint files | DistributedDictionary | Informational |
+| 61963 | ReliableQueueOpened | LifeCycle | Reliable queue has opened | DistributedQueue | Informational |
+| 61964 | ReliableQueueClosed | LifeCycle | Reliable queue has closed | DistributedQueue | Informational |
+| 61965 | ReliableQueueCheckpointRecovered | LifeCycle | Reliable queue has recovered its checkpoint | DistributedQueue | Informational |
+| 61966 | ReliableQueueCheckpointFilesSent | LifeCycle | Replica has sent reliable queue's checkpoint files | DistributedQueue | Informational |
+| 63647 | ReliableQueueCheckpointFilesReceived | LifeCycle | Replica has received reliable queue's checkpoint files | DistributedQueue | Informational |
+| 63648 | ReliableConcurrentQueueOpened | LifeCycle | Reliable concurrent queue has opened | ReliableConcurrentQueue | Informational |
+| 63649 | ReliableConcurrentQueueClosed | LifeCycle | Reliable concurrent queue has closed | ReliableConcurrentQueue | Informational |
+| 63650 | ReliableConcurrentQueueCheckpointRecovered | LifeCycle | Reliable concurrent queue has recovered its checkpoint | ReliableConcurrentQueue | Informational |
+| 61687 | TStoreError | Failure | Reliable collection has received an unexpected error | TStore | Error |
+| 63831 | PrimaryFullCopyInitiated | LifeCycle | Primary replica has initiated a full copy | TReplicator | Informational |
+| 63832 | PrimaryPartialCopyInitiated | LifeCycle | Primary replica has initiated a partial copy | TReplicator | Informational |
+| 16831 | BuildIdleReplicaStarted | LifeCycle | Primary replica has started building idle replica | Replication | Informational |
+| 16832 | BuildIdleReplicaCompleted | LifeCycle | Primary replica has completed building idle replica | Replication | Informational |
+| 16833 | BuildIdleReplicaFailed | LifeCycle | Primary replica has failed building idle replica | Replication | Warning |
+| 16834 | PrimaryReplicationQueueFull | Health | Primary replica's replication queue is full | Replication | Warning |
+| 16835 | PrimaryReplicationQueueWarning | Health | Primary replica's replication queue is near full | Replication | Warning |
+| 16836 | PrimaryReplicationQueueWarningMitigated | Health | Primary replica's replication queue is okay | Replication | Informational |
+| 16837 | SecondaryReplicationQueueFull | Health | Secondary replica's replication queue is full | Replication | Warning |
+| 16838 | SecondaryReplicationQueueWarning | Health | Secondary replica's replication queue is near full | Replication | Warning |
+| 16839 | SecondaryReplicationQueueWarningMitigated | Health | Secondary replica's replication queue is okay | Replication | Informational |
+| 16840 | PrimaryFaultedSlowSecondary | Health | Primary replica has faulted a slow secondary replica | Replication | Warning |
+| 16841 | ReplicatorFaulted | Health | Replica has faulted | Replication | Warning |
+
 ## Container events
 
 **Container lifecycle events**