Good morning everyone!
๐
mรฅnยกng
morning
morning
Morning
Morning
whats the word when a bit of cloud software gets moved onto another node, causing a slight blip in performance. would it be correct to call it 'rehoming'? doesn't feel quite right
migration?
osmosis?
migration feels a bit epic its more like a commute
dander
My software dandered over to another node
makes me think of that old macos alert chime
or was it on android? cant remember now
not by choice though
it was forced to
press-ganged?
My software was press-ganged to another node
I do miss the Wild Eep
Failed over is the usual term of art
k8s seems to be using migrate
eg https://cloud.google.com/kubernetes-engine/docs/tutorials/migrating-node-pool
https://cloudify.co/blog/migrating-pods-containerized-applications-nodes-kubernetes-cluster-using-cloudify/
haha like it
now I have to worry about whether my audience shares our sense of humour
you see 'reaped' and 'cold started' or 'reprovisioned' in lambdaland/serverless
Morn'
reprovisioned
was the word on the tips of my fingers
don't think I like it though
its boring
reaped
is a funny one isnt it
its simultaneously both of
โข excellent, we shall eat well this winter
โข OMG we are all going to die right now
depending on which end of the scythe you are looking at
If I have a vector and a var, such as ["abc" "efg"]
, "123"
, is there an easy way to turn that into [{:foo "abc" :bar "123"} {:foo "efg" :bar "123"}]
yus
(map #(vector {:foo % :bar "123"}) references)
any other ways?
naw, doesn't work the way I want it to work
it ends up being [[{....}] [{....}]]
This will work 'tho (into [] (map (fn [reference] {:foo reference :bar "123"}) references)
there's mapv
w00t
even better
ta
a voyage of discovery ๐
a lot of things in life are radically different depending on which end of the scythe you're on :)