Menu
I found the following API
await fabricClient.ClusterManager.ProvisionFabricAsync(null, "testMani.xml");
but have not figured out where to store the new manifest.xml file?
using it as listed here it will throw exception that the file testMani.xml do not exist in the store.
How can one after deployment manipulate the cluster manifest.
644
A single Service Fabric node type/scale set can not contain more than 100 nodes/VMs. To scale a cluster beyond 100 nodes, add additional node types.
Copy or download the standalone package for Service Fabric for Windows Server to the VM/machine and unzip the package. Run PowerShell with elevated privileges and go to the location of the unzipped package. Run the AddNode. ps1 script with the parameters describing the new node to add.
During an upgrade, Service Fabric compares the new application manifest with the previous version and determines which services in the application require updates.
The cluster manifest and APIs that reference it are artifacts of Service Fabric's internal usage at Microsoft. Manipulating the manifest is not recommended nor supported.
For Azure deployments, you should make all changes to your cluster through an ARM template. For local development, the cluster configuration is currently fixed but we will eventually support additional flexibility there as well so that you can make your onebox look more like your real environment, especially for concepts like placement constraints. In that case, the cluster definition will likely take the same form as we'll use for on-premise deployments.
84
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
