mirrors/ctrl
mirrors/ctrl
1
0
Fork 0
mirror of https://github.com/postmannen/ctrl.git synced 2024-12-14 12:37:31 +00:00
Code Activity

updated doc

Browse source
This commit is contained in:
postmannen 2021-02-03 08:28:21 +01:00
parent fea2d576a4
commit d6d77e6b02
2 changed files with 35 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
README.md
View file

@ -1,6 +1,32 @@
# steward
Async management of Edge units.
Async management of Edge Cloud units.
The idea is to build and use a pure message passing architecture for the control traffic back and forth from the Edge cloud units. The message passing backend used is <https://nats.io>
```text
┌─────────────────┐
│ │
│ │
│ ┌────────────┐ │
│ │ Edge Unit │ │
┌─────────────────┐ ┌─────────────────┐ │ └────────────┘ │
│ │ │ │ ────Event────▶ │ │
│ ┌────────────┐ │ ─────Event────▶ │ ┌───────────┐ │ ◀────ACK ───── │ │
│ │ Management │ │ │ │ Message │ │ └─────────────────┘
│ │ station │ │ │ │ broker │ │ ┌─────────────────┐
│ │ │ │ │ └───────────┘ │ │ │
│ └────────────┘ │ ◀─────ACK ───── │ │ ────Event────▶ │ │
│ │ │ │ ◀────ACK ───── │ ┌────────────┐ │
└─────────────────┘ └─────────────────┘ │ │ Edge Unit │ │
│ └────────────┘ │
│ │
│ │
└─────────────────┘
```
## Disclaimer
All code in this repository are to be concidered not-production-ready. The code are the attempt to concretize the idea of a purely async management system where the controlling unit is decoupled from the receiving unit, and that that we know the state of all the receiving units at all times.
## Concepts/Ideas
@ -18,7 +44,7 @@ Async management of Edge units.
Subject naming are case sensitive, and can not contain the space are the tab character.
`<nodename>.<command/event>.<method>`
`<nodename>.<command/event>.<method>.<domain>`
Nodename: Are the hostname of the device. This do not have to be resolvable via DNS, it is just a unique name for the host to receive the message.
@ -26,12 +52,14 @@ Command/Event: Are type of message sent. `command` or `event`. Description of th
Method: Are the functionality the message provide. Example could be `shellcommand` or `syslogforwarding`
Domain: Are used to describe what domain the method are for. For example there can be several logging services on an installation, but rarely there are several logging services in place for the same Domain using the same logging method. By having a specific Domain field we will be able to differentiate several loggers having for example `method=syslogforwarding` where one might be for `domain=nginx` and another for `domain=apache`.
##### Complete subject example
For syslog of type event to a host named "ship1"
`ship1.event.syslogforwarding`
`ship1.event.syslogforwarding.nginx`
and for a shell command of type command to a host named "ship2"
`ship2.command.shellcommand`
`ship2.command.shellcommand.operatingsystem`

4
publisher.go
View file

@ -156,7 +156,9 @@ type subject struct {
// process are represent the communication to one individual host
type process struct {
messageID int
// the subject used for the specific process
// the subject used for the specific process. One process
// can contain only one sender on a message bus, hence
// also one subject
subjects subject
// Put a node here to be able know the node a process is at.
// NB: Might not be needed later on.