Ticket ##: Add docker file + start to create kubernetes file with ETCD discovery method

Author: habarthierry-hue

EventMeshApiDockerFile

@@ -1,11 +1,14 @@
-FROM mcr.microsoft.com/dotnet/aspnet:5.0
+FROM mcr.microsoft.com/dotnet/aspnet:6.0
 
-COPY build/results/services/EventMeshServer/ App/
-ENV ASPNETCORE_URLS=http://*:5001
+COPY build/results/eventMeshService/ App/
 
-EXPOSE 5001
-EXPOSE 4000
+RUN apt-get update
+RUN apt-get --yes --force-yes install libc6-dev libsnappy-dev
+
+EXPOSE 4000/udp
+EXPOSE 5672/tcp
+EXPOSE 2803/tcp
 
 WORKDIR /App
 
-ENTRYPOINT ["dotnet", "FaasNet.EventMesh.Runtime.Website.dll"]
+ENTRYPOINT ["dotnet", "FaasNet.EventMesh.Service.dll"]

EventMeshDockerFile

@@ -10,7 +10,7 @@ For project documentation, please visit [docs](https://simpleidserver.github.io/
 
 | Command                     | Description                             |
 | --------------------------  | --------------------------------------- |
-| psake publishWebsite 		  | Publish website                         |
+| psake publishWebsite 		| Publish website                       	|
 | psake publishDockerCI       | Build and publish docker images         |
 | psake packTemplate          | Build template package                  |
 
@@ -33,4 +33,10 @@ psake publishWebsite
 
 ```
 psake packTemplate
-```
+```
+
+## Deploy EventMesh - Docker
+
+psake publishDockerEventMeshService
+docker build -t eventmesh -f EventMeshDockerFile .
+docker run --name eventmesh -p 4000:4000/udp eventmesh

README.md

@@ -60,18 +60,16 @@ task publishDocker {
 	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Runtime.Website\FaasNet.EventMesh.Runtime.Website.csproj -c $config -o $result_dir\services\EventMeshServer }
 }
 
-task publishEventMeshPlugins {
-	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Protocols.AMQP\FaasNet.EventMesh.Protocols.AMQP.csproj -c $config -o $result_dir\protocolPlugins\FaasNet.EventMesh.Protocols.AMQP }
-	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Protocols.WebSocket\FaasNet.EventMesh.Protocols.WebSocket.csproj -c $config -o $result_dir\protocolPlugins\FaasNet.EventMesh.Protocols.WebSocket }
-	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Sink.AMQP\FaasNet.EventMesh.Sink.AMQP.csproj -c $config -o $result_dir\sinkPlugins\FaasNet.EventMesh.Sink.AMQP }
-	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Sink.Kafka\FaasNet.EventMesh.Sink.Kafka.csproj -c $config -o $result_dir\sinkPlugins\FaasNet.EventMesh.Sink.Kafka }
-	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Sink.VpnBridge\FaasNet.EventMesh.Sink.VpnBridge.csproj -c $config -o $result_dir\sinkPlugins\FaasNet.EventMesh.Sink.VpnBridgea }
-	exec { dotnet publish $source_dir\RaftConsensus\FaasNet.RaftConsensus.Discovery.Config\FaasNet.RaftConsensus.Discovery.Config.csproj -c $config -o $result_dir\discoveryPlugins\FaasNet.RaftConsensus.Discovery.Config }
-	exec { dotnet publish $source_dir\RaftConsensus\FaasNet.RaftConsensus.Discovery.Etcd\FaasNet.RaftConsensus.Discovery.Etcd.csproj -c $config -o $result_dir\discoveryPlugins\FaasNet.RaftConsensus.Discovery.Etcd }
-}
-
-task publishEventMeshService {
+task publishDockerEventMeshService {
+	rd "$result_dir\eventMeshService" -recurse -force  -ErrorAction SilentlyContinue | out-null
 	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Service\FaasNet.EventMesh.Service.csproj -c $config -o $result_dir\eventMeshService }
+	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Protocols.AMQP\FaasNet.EventMesh.Protocols.AMQP.csproj -c $config -o $result_dir\eventMeshService\protocolPlugins\FaasNet.EventMesh.Protocols.AMQP }
+	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Protocols.WebSocket\FaasNet.EventMesh.Protocols.WebSocket.csproj -c $config -o $result_dir\eventMeshService\protocolPlugins\FaasNet.EventMesh.Protocols.WebSocket }
+	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Sink.AMQP\FaasNet.EventMesh.Sink.AMQP.csproj -c $config -o $result_dir\eventMeshService\sinkPlugins\FaasNet.EventMesh.Sink.AMQP }
+	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Sink.Kafka\FaasNet.EventMesh.Sink.Kafka.csproj -c $config -o $result_dir\eventMeshService\sinkPlugins\FaasNet.EventMesh.Sink.Kafka }
+	exec { dotnet publish $source_dir\EventMesh\FaasNet.EventMesh.Sink.VpnBridge\FaasNet.EventMesh.Sink.VpnBridge.csproj -c $config -o $result_dir\eventMeshService\sinkPlugins\FaasNet.EventMesh.Sink.VpnBridgea }
+	exec { dotnet publish $source_dir\RaftConsensus\FaasNet.RaftConsensus.Discovery.Config\FaasNet.RaftConsensus.Discovery.Config.csproj -c $config -o $result_dir\eventMeshService\discoveryPlugins\FaasNet.RaftConsensus.Discovery.Config }
+	exec { dotnet publish $source_dir\RaftConsensus\FaasNet.RaftConsensus.Discovery.Etcd\FaasNet.RaftConsensus.Discovery.Etcd.csproj -c $config -o $result_dir\eventMeshService\discoveryPlugins\FaasNet.RaftConsensus.Discovery.Etcd }
 }
 
 task publishEventMeshCLI {

default.ps1

@@ -0,0 +1 @@
+# Architecture

docs/documentation/eventmesh/architecture.md

@@ -1,6 +1,6 @@
 # Command-line interface
 
-`FaasNet.EventMeshCTL.CLI.exe` is the CLI tool that ships with EventMeshServer. It supports a wide range of operations, mostly administrative in nature.
+`FaasNet.EventMeshCTL.CLI.exe` is the CLI tool that ships with EventMesh. It supports a wide range of operations, mostly administrative in nature.
 This includes
 
 * Access to cluster status.

docs/documentation/eventmesh/cli.md

@@ -1,10 +1,10 @@
 # Clustering
 
-An EventMesh cluster is a logical grouping of one or several peers, each sharing Clients, Virtual Private Network, Sessions.
-Any node present in the cluster must be able to process any type of request such as: add VPN client, create subscription session.
+An EventMesh cluster is a logical grouping of one or several peer nodes, each sharing Clients, Virtual Private Network, Sessions.
+Any peer present in the cluster must be able to process any type of request such as: add VPN client, create subscription session.
 Only queues are not replicated everywhere.
 
-Because queues are not replicated among all the nodes but only on a specific amount. The queue availability cannot be guaranteed on all the nodes.
+Because queues are not replicated among all the peers but only on a specific amount. The queue availability cannot be guaranteed on all the peers.
 
 Two types of data can easily be identified:
 * Server data : data needed by a peer to process a request.

docs/documentation/eventmesh/clustering.md

@@ -0,0 +1,45 @@
+# EventMesh glossary and concepts
+
+## Peer node
+
+A Peer Node is a communication endpoint capable of treating EventMesh, Raft and Gossip request.
+
+Two or more Peers can form a cluster, they all share the same functionality.
+
+## Cluster
+
+A cluster network is two or more services working together for a common purpose.
+
+These networks take advantage of the parallel processing power. In addition to the increased processing power, can also provide scalability, high availability and failover capabilities.
+
+## Client
+
+Any types of application that implement the EventMesh protocol.
+
+A client is capable of sending and/or receiving messages.
+
+## Session
+
+A session is a communication channel established between one Peer Node and a client.
+
+It is used to send and receive messages.
+
+There are two kinds of session :
+* **Subscription** : Subscribe to one or more topics.
+* **Publish** : Publish one or more messages.
+
+## Topic
+
+Topic is a mean of classifying information. 
+
+## Message Virtual Private Network (VPN)
+
+Allows for the segregation of topic space and clients. Message VPNs also group clients connecting to a network of event broker, such that messages published within a particular group are only visible to that group's clients.
+
+## Message VPN bridge
+
+Link two Message VPNs so that messages published to one message VPN that match the topic subscriptions set for the bridge are also delivered to the linked message VPN.
+
+## CloudEvent
+
+Specification for describing event data in a common way.