Since Azure App Services are too expensive, we would like to build our own App Service Cluster so we can deploy Docker images to custom cloud VMs/workers from different service providers.
It should cover functionalities like:
Deployment Center: selecting Docker images (Docker hub, gitlab) and deploy them to our cloud workers by tag
Scalability (like App Service Plan): add workers
Load balancing
SSL/Domain Management
FW Integration
Logging Streams
Does there exist already an open source framework with a GUI for this type of "private cloud" that can be deployed via docker swarm for instance?
thankz!
I have a nodeJS application running as a microservice and there are two scenarios:
when a developer is doing development on his machine. nodeJS application should register to eureka service and be able to communicate with other microservices without specifying URL or port to those services
when nodeJS application is deployed to kubernetes cluster, it should not register to Eureka and instead use existing kubernetes Services within the cluster to communicate with other services, again without specifying URL or port, only kubernetes service name
I was thinking of maybe using some env var that will tell the nodeJS service how to behave depending on the environment it is being started in
I am developing a single node js application which will create/delete a cluster and also a VM in Azure.
What is the preferred node package create HDI cluster and VM, etc in Azure?
I have create cordapp in azure VM. now i want to deploy that cordapp into Azure cloud server so that client from anywhere can hit cordapp. but i confused whether i have to use webapps or inbuilt Blockchain module in marketplace. if so, how to do deploy?
You can deploy a node to a cloud server by following the instructions here: https://docs.corda.net/deploying-a-node.html.
You can then interact with your node remotely, using either:
An RPC client (e.g. https://github.com/corda/cordapp-template-java/blob/release-V3/clients/src/main/java/com/template/Client.java)
A server (e.g. https://github.com/corda/cordapp-template-java/tree/release-V3/clients/src/main/java/com/template/webserver)
The node shell over SSH (Corda V3 onwards - see https://docs.corda.net/head/shell.html#the-shell-via-ssh)
I have just started exploring Azure Service Fabric & I'm finding the concepts involved a little overwhelming
Consider these 2 statements -
"Service Fabric is agnostic to the underlying hosting provider. You
can run it in Azure, you can run it on AWS, you can run it on 5
laptops - it doesn't matter."
"Azure Service Fabric for Windows Server..can be used
to..provision Service Fabric clusters in their own datacenters or
other cloud providers, and run production workloads"...any Windows Server environment...there is no real lock-in to Azure as a cloud platform
As per my understanding,
1) in Azure, app can be deployed to "Azure Service Fabric" PaaS platform.
2) On a local development machine, it can be deployed to physical or virtual machine(S) that support Azure Service Fabric SDK
3) On "other cloud providers", "Azure Service Fabric for Windows Server" has to be installed(?) on VMs before app can be deployed.
So when an app runs on Azure, it is the "Azure Service Fabric" PaaS platform but if it is deployed to any other cloud provider, it is in an IaaS mode and the maintenance of the SF infrastructure & supporting functions have to be done by deployer of the app
Is my understanding correct?
Is there any documentation on running Service Fabric on non-Azure cloud like AWS?
Can someone elaborate on the purpose of "Azure Service Fabric for Windows Server" & Azure Service Fabric SDK?
When using Azure as the cloud platform to host your Service Fabric cluster then you get some benefits from being able to setup and manage (some aspects of) your cluster directly in the Azure portal, as well as connecting it to other Azure resources such as Azure Key Vault for storing your cluster certificate securely and OMS/Azure Log Analytics for analyzing your log data from the cluster. You still get a set of IaaS resources created for you though when you set up a Service Fabric cluster in Azure, a minimum of the following IaaS resources are at least created for you:
Virtual Machine Scaleset
Public IP address
Virtual Network
Load Balancer
Storage accounts
Depending on the number of nodes and nodetypes there may be multiple instances of these. Each of the nodes are in turn a VM running (by default) Windows Server 2012 R2 Datacenter (you can change that in your template as well).
Running Azure Service Fabric on Azure is not really a PaaS solution, you are far to much in contact with the supporting infrastucture for that to be true. It is a mix of IaaS and PaaS I would say.
On you local development machine you can run a local development cluster that emulates running a 1 or 5 nodes cluser on you local machine. It is only intended for development and there are some features of this local cluster that will behave differently (for instance, you cannot run a reverse proxy there). https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started
If you want to run Service Fabric on any other platform than Azure, such as an on premice data center or in another cloud platform (AWS for instance), then you should look at Create and manage a cluster running on Windows Server. You will then need to create an infrastructure similar to the infrastructure created by Azure when you create an Azure Service Fabric resource directly in Azure. You will need to create a number of VMs (or physical machines) with Windows Server 2012 R2 (or later) that are connected on the same network (virtual or physical) and you will likely need some form of load balancer. When you run Azure Service Fabric in this way you are yourself responsible for maintaining your infrastructure in terms of monitoring and maintaining them (patching the OS on your VM's, monitoring the network for vulnerabilities, etc.).
There is also a preview for running Service Fabric on Linux machines but it does not support Standalone installations yet. https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-linux-overview.
When you have your Service Fabric cluster running on either Azure, local development cluster or as a Standalone cluster, then you could in a way consider that installation as your PaaS platform for adding new microservices.