Giter Site home page Giter Site logo

azure-samples / service-fabric-mesh Goto Github PK

View Code? Open in Web Editor NEW
62.0 41.0 68.0 8.14 MB

Samples repository for Azure Service Fabric Mesh

License: MIT License

C# 3.78% CSS 36.09% JavaScript 33.56% Shell 0.43% Batchfile 0.06% HTML 24.94% Ruby 0.79% PowerShell 0.09% Dockerfile 0.27%

service-fabric-mesh's Introduction

languages products page_type
csharp
yaml
azure
azure-service-fabric
sample

Mesh-01

Service Fabric Mesh Samples

This repository contains samples that showcase what you can do with Service Fabric Mesh Applications.

For more details about Service Fabric Mesh public preview in Azure, refer to this blog post - https://azure.microsoft.com/en-us/blog/azure-service-fabric-mesh-is-now-in-public-preview/

Structure of this repo

This repository has two main folders:

  • src contains source code samples. Some of these are built using the Visual Studio Tools for Mesh. Use these samples if you want to build the code from source, publish container images and deploy the app to Mesh.

  • templates contains samples with ARM templates ready to deploy to Azure Mesh. Use these templates if you want to deploy an application using existing container images and deployment templates

Both folders contain instructions on how to work with the samples.

Useful links

Feedback and issues

We look forward to hearing your feedback about Mesh.

Please use this repo's Issues to raise issues with the samples.

For any other issue you encounter with Mesh, please use the Issues in this repo https://github.com/Azure/seabreeze-preview-pr/ to inform us of any bugs you come across, or improvements you would like to request.


*This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.*

service-fabric-mesh's People

Contributors

anantshankar17 avatar armantajback avatar ashishnegi avatar athinanthny avatar dkkapur avatar erikadoyle avatar jeffj6123 avatar kavyako avatar mattrowmsft avatar microsoftopensource avatar msftgits avatar raunakpandya avatar rwike77 avatar suhuruli avatar supernova-eng avatar tbertenshaw avatar tylermsft avatar vipul-modi avatar wangcai0124 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

service-fabric-mesh's Issues

Insufficient Capacity Issue

Please provide us with the following information:

This issue is for a: (mark with an x)

I have a microservice application which contains multiple microservices (around 20 microservice). When I try to deploy using ARM templates. I can see the deployment status failed with message "ClusterAllocationInsufficientCapacity","message":"Insufficient capacity is available in this region. "Our team tried with multiple regions, Then also we get this issue.

  • bug report -> please search issues before submitting
  • feature request
  • documentation issue or request
  • regression (a behavior that used to work and stopped in a new release)

### Minimal steps to reproduce
>

### Any log messages given by the failure
>

### Expected/desired behavior
>

### OS and Version?
> Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

### Versions
>

### Mention any other details that might be useful

> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

Error deploying base linux template

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Try to deploy the base linux template:

az mesh deployment create --resource-group vmeshrg --template-uri https://raw.githubusercontent.com/Azure-Samples/service-fabric-mesh/2018-09-01-preview/templates/visualobjects/visualobjects.base.linux.json --parameters {'location': {'value': 'eastus'}}

Any log messages given by the failure

{
"id": "/subscriptions/hidden****/resourceGroups/vmeshrg/providers/Microsoft.Resources/deployments/visualobjects.base.linux",
"location": null,
"name": "visualobjects.base.linux",
"properties": {
"correlationId": "hidden***",
"debugSetting": null,
"dependencies": [
{
"dependsOn": [
{
"id": "/subscriptions/hidden***/resourceGroups/vmeshrg/providers/Microsoft.ServiceFabricMesh/networks/visualObjectsNetwork",
"resourceGroup": "vmeshrg",
"resourceName": "visualObjectsNetwork",
"resourceType": "Microsoft.ServiceFabricMesh/networks"
}
],
"id": "/subscriptions/hidden***/resourceGroups/vmeshrg/providers/Microsoft.ServiceFabricMesh/gateways/visualObjectsGateway",
"resourceGroup": "vmeshrg",
"resourceName": "visualObjectsGateway",
"resourceType": "Microsoft.ServiceFabricMesh/gateways"
},
{
"dependsOn": [
{
"id": "/subscriptions/hidden***/resourceGroups/vmeshrg/providers/Microsoft.ServiceFabricMesh/networks/visualObjectsNetwork",
"resourceGroup": "vmeshrg",
"resourceName": "visualObjectsNetwork",
"resourceType": "Microsoft.ServiceFabricMesh/networks"
}
],
"id": "/subscriptions/hidden***/resourceGroups/vmeshrg/providers/Microsoft.ServiceFabricMesh/applications/visualObjectsApp",
"resourceGroup": "vmeshrg",
"resourceName": "visualObjectsApp",
"resourceType": "Microsoft.ServiceFabricMesh/applications"
}
],
"duration": "PT2H1M8.5072598S",
"error": {
"code": "DeploymentFailed",
"details": [
{
"code": "BadRequest",
"message": "{\r\n "error": {\r\n "code": "UnsupportedProperty",\r\n "message": "Property: .properties.services[].location is not supported.",\r\n "details": [\r\n {\r\n "code": "Exception",\r\n "message": "Microsoft.ServiceFabric.Rp.Errors.WrpException: Property: .properties.services[].location is not supported.\r\n at Microsoft.ServiceFabric.Rp.Model.Public.ExternalApiEntityValidator.Validate(String schema, IEnumerable1 additionalPropertiesPaths, IEnumerable1 apiVersions)\r\n at Microsoft.ServiceFabric.Rp.Common.WrpJsonFormatter.<>c__DisplayClass8_0.b__0() in F:\\aw\\1\\s\\src\\Common.Web\\WrpJsonFormatter.cs:line 104\r\n at System.Threading.Tasks.Task1.InnerInvoke()\\r\\n at System.Threading.Tasks.Task.Execute()\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\\r\\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n at System.Net.Http.HttpContentExtensions.<ReadAsAsyncCore>d__171.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.ModelBinding.FormatterParameterBinding.d__18.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Controllers.HttpActionBinding.d__12.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Controllers.ActionFilterResult.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__15.MoveNext()"\r\n }\r\n ]\r\n }\r\n}"
},
{
"code": "RequestTimeout",
"message": "{\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource provision operation did not complete within the allowed timeout period."\r\n }\r\n}"
}
],
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details."
},
"mode": "Incremental",
"onErrorDeployment": null,
"outputs": null,
"parameters": {
"location": {
"type": "String",
"value": "eastus"
}
},
"parametersLink": null,
"providers": [
{
"id": null,
"namespace": "Microsoft.ServiceFabricMesh",
"registrationPolicy": null,
"registrationState": null,
"resourceTypes": [
{
"aliases": null,
"apiVersions": null,
"capabilities": null,
"locations": [
"eastus"
],
"properties": null,
"resourceType": "networks"
},
{
"aliases": null,
"apiVersions": null,
"capabilities": null,
"locations": [
"eastus"
],
"properties": null,
"resourceType": "gateways"
},
{
"aliases": null,
"apiVersions": null,
"capabilities": null,
"locations": [
"eastus"
],
"properties": null,
"resourceType": "applications"
}
]
}
],
"provisioningState": "Failed",
"template": null,
"templateHash": "17174931897256797389",
"templateLink": {
"contentVersion": "1.0.0.0",
"uri": "https://raw.githubusercontent.com/Azure-Samples/service-fabric-mesh/2018-09-01-preview/templates/visualobjects/visualobjects.base.linux.json"
},
"timestamp": "2020-04-02T05:44:41.723517+00:00"
},
"resourceGroup": "vmeshrg",
"type": "Microsoft.Resources/deployments"
}

Expected/desired behavior

sucessful mesh deployment

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
running from mac os. However getting same result from ci/cd azure hosted pipeline agent.

Versions

latest branch & latest azure cli

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Service Fabric 6.4 : How to achieve Support for Service Fabric Reliable Volumes that provide high availability through built-in replication?

I could not find information on how to achieve Support for Service Fabric Reliable Volumes that provide high availability through built-in replication. I'm using Visual Studio 2017 and Service Fabric Mesh SDK in Windows 10 V1709, what are the changes I need to do in volume.yaml and service.yaml. Please help/guide.

Counter App for Service Fabric Reliable Volumes is mentioned at https://docs.microsoft.com/en-us/azure/service-fabric-mesh/service-fabric-mesh-howto-find-samples <- It does not have information on how to achieve Support for Service Fabric Reliable Volumes that provide high availability through built-in replication.

Add scenario/tutorial that shows best practices how to build&deploy with Azure Pipelines

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ x ] feature request
- [ x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

see title

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Endpoint 'counterServiceListener' not referenced in network

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

AzureFiles volume sample. Put in your storage account name/key etc and then do a local F5 debug in Visual Studio 2017.

Any log messages given by the failure

New-SFMeshResourceDeployment : 'counterApp.counterService': Endpoint 'counterServiceListener' not referenced in network
Refs.
At line:1 char:157

  • ... -SFCluster; New-SFMeshResourceDeployment -ResourceDescriptionList 'C: ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : NotSpecified: (:) [New-SFMeshResourceDeployment], ServiceFabricException
    • FullyQualifiedErrorId : DeployMeshResourcesErrorId,Microsoft.ServiceFabric.Powershell.Http.DeployMeshResourcesCm

Expected/desired behavior

Expected behavior is to be able to run this app locally after putting in all of the storage account information

OS and Version?

Windows 10 Enterprise 1803

Mention any other details that might be useful

Just trying to figure out why the name of the listener is listed in the service.yaml and gateway.yaml file but it is saying that the listener is not referenced in the network. What does that mean?


Thanks! We'll be in touch soon.

Wrong region on the documentation to deploy the HelloWord

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deploy the HelloWord linux sample here https://github.com/Azure-Samples/service-fabric-mesh/tree/master/templates/helloworld

Any log messages given by the failure

ERROR: The provided location 'eastus' is not available for resource type 'Microsoft.ServiceFabricMesh/gateways'. List of available regions for the resource type is 'eastasia'.

Expected/desired behavior

The resource being deployed

OS and Version?

Windows 10, Powershell

Versions

10

Mention any other details that might be useful

You need to update the documentation to use eastasia as a region


Thanks! We'll be in touch soon.

Release Linux/ARM64 docker image for ‘seabreeze/azure-mesh-counter’


This issue is for a: (mark with an x)

- [x ] feature request - Support for Linux/ARM64 docker image

Minimal steps to reproduce

Run build.linux.sh file in Linux/ARM64 machine.

Any log messages given by the failure

docker build src -f src/counterService/linux.Dockerfile -t azure-mesh-counter:dev-alpine
Sending build context to Docker daemon 81.41kB
Step 1/16 : FROM microsoft/aspnetcore:2.0 AS base
2.0: Pulling from microsoft/aspnetcore
no matching manifest for linux/arm64/v8 in the manifest list entries

Expected/desired behavior

Docker Image must be generated for Linux/ARM64 machine

OS and Version?

Linux (Debian, Ubuntu)

Versions

Latest

Mention any other details that might be useful

I tried to create a container on the Linux/AMD64 machine, using seabreeze/azure-mesh-counter:0.5-alpine docker image but I am getting the below exceptions and the container does not get started. Please refer to the logs below for more details.

“Unhandled Exception: System.FormatException: Unrecognized argument format: 'bash'.
at Microsoft.Extensions.Configuration.CommandLine.CommandLineConfigurationProvider.Load()
at Microsoft.Extensions.Configuration.ConfigurationRoot..ctor(IList`1 providers)
at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
at Microsoft.ServiceFabricMesh.Samples.Counter.Service.Controllers.Program.Main(String[] args) in /src/counterService/Program.cs:line 15”

Please let me know if you have any suggestions to fix this.

I also tried to build the docker image by running the build.linux.sh file. The build was successful in the Linux/AMD64 machine but it failed in Linux/ARM64 machine. The ARM64 build was failing since the counterservice uses dotnet framework version 2.0 which does not have an ARM64 support.

I made some changes in the dockerfile and in the repository to upgrade the dotnet framework to the latest version 5.0. With these changes, I am able to build docker images on Linux/ARM64 machines.

However, in the docker image, the counterservice.dll is for intel and not for ARM64. May I know how you are building this dll?

Do you have any plans on adding arm64 support and releasing arm64 images?

If required, I am happy to contribute.


Counter Sample Volumes

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Build and publish counter sample from VS 2017, I'd expect clear steps to make this application working, however I can't. Cloning the repo and building the app succeeds, however I'm not quite sure how to get the volume attached to the image.

You've got volume.yaml file in the solution that is supposed to take file share from parameters:

volume:
  schemaVersion: 1.0.0-preview1
  name: counterVolume
  properties:
    description: Azure Files storage volume for counter App.
    provider: SFAzureFile
    azureFileParameters: 
        shareName: "[parameters('azurefile-shareName')]"
        accountName: "[parameters('azurefile-accountName')]"
        accountKey: "[parameters('azurefile-accountKey')]"

In case we are deploying from VS, where does one provide those parameters? The file share is already deployed, however I should be able to pass the parameters somehow externally? ARM gets generated automatically, however it doesn't mention volume resource at all.

In the counterService, service.yaml there are no references to a volume either, so I'm not quite sure where it's supposed to be attached. FileStoreUtility is trying to get STORE_ROOT from an environment variable, could you please point where it's created?

I'm happy to contribute to the documentation if you can point me in the right direction please.

Any log messages given by the failure

no errors.

OS and Version?

Windows 10

Versions

Latest SF SDK and Mesh SDK available from WPI. Latest official Docker.

The server name or address could not be resolved in ToDoListApp

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1 Create SF Mesh App and Service base of this article: https://docs.microsoft.com/en-us/azure/service-fabric-mesh/service-fabric-mesh-tutorial-create-dotnetcore
2 Try to Debug this app base of this article: https://docs.microsoft.com/en-us/azure/service-fabric-mesh/service-fabric-mesh-tutorial-debug-service-fabric-mesh-app

Any log messages given by the failure

Get a error in this line of IndexModel.cs

using (HttpResponseMessage response = client.GetAsync(backendUrl).GetAwaiter().GetResult())

The server name or address could not be resolved

Expected/desired behavior

Get right dns address

OS and Version?

Windows 10 1803

Versions

SF 6.3.162.9494

Mention any other details that might be useful

I try to change ServiceName to ToDoService.todolistapp, it's not working yet.

Cannot Delete Mesh Gateway and Network

I was referred here by Azure support. But I cannot delete my Service Fabric Mesh Gateway and Network. The Mesh application itself has been deleted, but the network & gateway timeout whenever I try to delete.

I've tried the portal, PowerShell, and resource.azure.com. I've tried deleting the resources individually, both at the same time, and even the entire resource group.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.