upsycle-send () {
local host=$1
local port=$2
local line
while read line; do
nc "$host" "$port" <<< "$line"
done
}
cat > file.txt # e.g. n<enter>S<enter><ctrl-d>
cat file.txt | upsycle-send 127.0.0.1 7001
But to make a nice demo you probably want to send a few commands to the message router A, then to service A1, then to the message router or another service, etc. It might an idea to make a little DSL for this.
s-a1 j # join multicast groups
sleep 5
s-a1 m # send multicast update
mr-a S
with mappings mr-a=mr-a.dream.public.cat:7001, s-a1=dmc-1.dream.public.cat:nnnn in another file.
and then eventually
s-a1 join-multicast-groups <key1> <key2>
sleep 5
s-a1 send-multicast <key1> "hello this is a DMC update"
mr-a show-state
Am I really to answer this question? There are at least two threads to move out of this particular topic into their own topic.
I want to be able to copy the certificates from one VM to the next so they match their expected routers. I guess I cannot generate certificates and expect the configurations to magically match each other.
Mm, no. C should be able to run without B running. You can try it on debian with the localhost example.
It only says ‘trying to connect to B’ or something like that.
You can control where they get generated: try bin/gen-keys-and-certs -h.
It will indeed hang trying to connect to B the way we have it now. Try changing the remote-routers line in -c.yaml to an empty array: remote-routers: []
Hi, so we finished the README and (as far as we’re concerned) the announcement page.
The API docs are hosted (due to time-constraints) on an Alleycat server here. Tonight I will revise them and then apply the 0.1.0-alpha1 tag to the repo.
Please note that I’m not working tomorrow. Feel free to ask questions (if I can’t answer I won’t) and I can try to take a look at something in the evening but this is basically it for the release!
Next steps: Arie and I have a few programming todos left. We will work in a separate branch and merge next week with the tag 0.1.0-alpha2, without an announcement.
And after that … the understanding we have with the project now (see previous posts, recent conversations etc.) is that we will take a week or two now that this part is finished and decide whether and if so how we will continue with DREAM.
I’m available for a meeting if P.S. wants to organise one to talk about this release, just not on Tuesdays. Would be nice if @tg-x is there too since it’s his design.
