I did the same, originally planned on UniFi but since i couldn’t get any i tried Omada. It’s very nice, the only issue i’ve had is my mesh not connecting, but i solved that by reorienting the target AP and boosting the source APs radio. I think i have some tuning left though because my devices don’t switch APs as fast as i’d like.
> Why doesn't 'software architect' get the same criticism for not being an architect?
I'm married to an Architect, it bugs them too.
In most states - Legally they can't call themselves Architects until they've passed the AREs. You can't take the AREs until you have enough IDP hours (which takes about 3 years). You can't start IDP unless you have a Masters (or more recently a "professional bachelors"). Oh, and you have to take a new test for every state / country you want to practice Architecture in (Reciprocity is getting better but not quickly)
So it's that sense that they have to scratch and claw to get the title where we can just sort of make it up that bugs them.
I think we should switch to a different title scheme. I'm going to be a Doctor of Site Reliability (you know since I'm already doing operations....)
> My real complaint is that none of these give you a way to do persistence that doesn't destroy some other really nice properties of containers.
100% agree with you there.
> It mostly just keeps them even with Kubernetes at best. And an imitation of it at worst.
Personally, when I looked at kubernetes, mesos, etc and saw the xml hell that i'd be living in and said "no way".
If i have to run something as complex as those to have docker then it's not worth it to me.
When I look at the new docker swarm stuff. For the first time I think that docker is a viable thing (assuming it all works). because I'm not adding additional complexity to get my docker simplicity.
In docker 1.12 you can 'tag' a node and tell a 'service' to only run on the tagged nodes.
Not saying that's a good idea, but it is getting closer.
You could, for example, have a node that's only for DBs that has volumes on it. You could then use DRBD on the host to clone that data to a secondary node. then in the event that node 1 dies swarm would bring the DB up on node2.
With the mesh network stuff they've added the endpoint would remain the same, so all your apps would need to do would be re-connect.
I'm impressed that the reporter did a whois search and tried various domains. That's not something I would expect from a standard US reporter now-a-days.
Lynch's Dune is one of my all time favourite movies. I watched it a lot growing up and it didn't make a lick of sense to me, but I still loved the world it created. Later on I saw the extended edition (on laser disk baby!) and it became a lot more clear. And then finally I read the book and it all made sense to me.
Yes the SyFy Mini-Series is more true to the book, but their pronunciations make it unbearable to watch for me. "Hark-e-nin" vs "Har-ko-nin" drives me up the wall.
Another thing I love about it is how surreal Lynch creates the future. To me it's one of the most immersive sci-fi movies that really takes you out of this reality and into it's own and it does it with minimal flash and special effects.
The Guild navigators are gross and amazing. The Lynch Baron Harkonin is possibly my favourite Sci-fi villain of all time.
DNS was precisely the area where we got bit by it.
We were using a Non-AWS DNS resolver (aka Google) and we would often get dns resolution errors despite our NAT not being remotely taxed by the traffic.
Well, Docker is big news and people are interested in what the performance impact of "using docker" is.
Whether it's accurate or not, people associate Docker with the functionality if facilitates. (i.e., cgroups, namespaces, etc.) so i think it's valid to show the performance impact of running an application from within docker.
Based on my data, they're not 1:1 native performance. I suggest you consider the data before dismissing it.
Baan still exists as Infor ERP Ln