I am trying to deploy service fabric application from powershell. I am able to deploy with service fabric SDK. is it possible to deploy service fabric application from powershell using powershell scripts without having service fabric sdk installed?(Scenario: in a standalone service fabric cluster)
I haven't worked with standalone clusters, but based on my experience just working with a local dev cluster, yes, you need the SDK because it installs both the runtime (without a runtime, what cluster will the scripts connect to?) and the Service Fabric PowerShell module you'll be using (per the docs for the cmdlets).
Related
I have a web assembly application that I deployed to the local azure service fabric cluster on Windows 11. How can I debug the c# code defined in the web assembly page through the browser and/or visual studio?
I have an infrastructure pipeline in Azure DevOps that setup a service fabric cluster. The fabric cluster's key vault and certificate are generated by a custom PowerShell script I wrote, while the cluster and its resources are generated by an ARM template. They are executed as tasks in the pipeline.
However, I am having problems accessing the generated fabric cluster via Service Fabric Explorer using web address: https://myclustername.mylocation.cloudapp.azure.com:19080/Explorer
I also have problem accessing the nodes using RDP:
I tried the following:
Restarted virtual machine scale set.
Checked the ports are open on load balancer: 3389-3391
I don't get this problem if I setup the fabric resource group with visual studio.
I checked the certificate generated and made sure it has a subject that is the same as the fabric cluster url. Does anyone know what might be causing this?
I think I used the ARM template that came with visual studio 2017. The template is old (2016). I updated the template to the recent one and the issue is resolved:
https://github.com/Azure/azure-quickstart-templates/tree/master/service-fabric-secure-cluster-5-node-1-nodetype
I still have some problem for adding a custom internal load balancer, but all the other resources out of the ARM template are working.
I'm trying to determine if it's possible to install a previous version of a Service Fabric application using the online Service Fabric Explorer as opposed to having to use a PowerShell script? In our case, the previous version of the application exists in the cluster and is visible in the list of application versions in the Explorer.
I appreciate any input.
This topic has been raised a few times around SO, short answer is no.
This answer give more details: Service fabric rollback to previous version from visual stuido or service fabric explorer
I would like to know the different approaches to deploy the locally built MobileFirst hybrid application to dedicated Bluemix environment.
I have used containers from public Bluemix environment to create worklight console to deploy wlapp and adapter files. Containers are not available in dedicated Bluemix environment.
Is there anything we can do to deploy the files in dedicated environment?
Thanks in advance.
The ability to use containers in a dedicated Bluemix environment is not supported at this time.
That is correct that the IBM Container Service is not yet available as part of the Bluemix Dedicated offering but we are working on making the Container Service available in the dedicated offering so stay tuned.
Dan
I am trying to deploy a console application to service fabric. I was able to successfully deploy and run the application in local service fabric cluster. But when I am trying with public service fabric cluster, I am seeing below warning in service fabric explorer and the application is not running.
Unhealthy event: SourceId='System.Hosting',
Property='CodePackageActivation:C:EntryPoint', HealthState='Warning',
ConsiderWarningAsError=false.There was an error during CodePackage
activation.The service host terminated with exit code: 3762504530
The most common explanation for code the runs locally but not in Azure is that you're targeting a .NET framework version that is not present on the VMs provisioned in a Service Fabric cluster. They currently provide .NET 4.5.1 out of the box, with .NET 4.5.2 getting added some time this month. Try retargeting your app to 4.5.1.
Update: as of February 2016, VMs provisioned for Service Fabric clusters come with .NET 4.5.2 by default.