redat00

I've overlooked too much the optimization in the workload that get dispatched and just looked at the scheduling part. Thanks for the explanation!

It just describes the platform they built for scheduling workloads, and running those workloads. After a second thought it is not that impressive and probably doesn't deserve any kind of hype. It's the same kind of setup AWS is running for Lambda, as well as anyone else basically running SLURM clusters out there.

Still giving them credit because creating such as scheduler/platform from scratch is quite complex, and I know that they probably struggled a lot to get it right.

Still very impressive! Love how it's done!

So.. serverless ?

Hi!

Some companies do use Ansible at an higher usage level, on big infrastructure, and where change iterations happens quickly.

In this context the Ansible model might not scale well : Your deployment time is bound by both the network you're using to contact the nodes you're managing, where you literally feel any round-trip your packets have to make, and by the number of nodes you have to perform actions on (which is somewhat solved by the use of mitogen with Ansible for example).

On top of that, for advanced usage, you're still dependent on the fact that Python is present on the system you're targeting with Ansible, which makes the idea that "ansible does not require anything on the target host" a bit false, although most distributions ships with Python by default.

Peekl is targeted towards organizations that requires good scaling capabilities, and high velocity in changes deployments. Having to actively be deploying in this context, instead of passively deploying, can be challenging.

Peekl is an alternative to Ansible, but would probably not be as good as an alternative for small individuals/companies who don't manage an important fleet, or do not have an high number of changes going through.

So your point is valid, note everyone would find Peekl a good Ansible alternative.

I'm building Peekl, an alternative to Puppet and Ansible that aims to be faster, more reliable, and easier to work with.

Happy to answer any questions you might have :)

Seems like it's targeted at students. They're probably expecting to sell a bunch of them at the time of "back to school" and they'll increase the price after.

At least for Europe, and more specifically France, laptop use in classrooms in high school, is still not a thing. So that would explain why they don't do it everywhere the same and the huge price difference.

The current issue with battery replacement is mainly the fact that they're glued to the phone. Which make them very dangerous to replace, as newbie might try to pry off the battery with metal tools (and you don't want to know what happens when a lithium battery is pierced.)

The only thing that will change as far as I know is that battery won't be glued anymore. You'll still have to open the phone with screw like you did before.

Yes the pub/sub model gets way faster than the Ansible push model, especially at scale : When you start having a few hundreds of servers, you'll see that you just spend so much time waiting for the playbook to run.

It's also heavily bound to network connectivity, if your server your reaching has 100ms of latency, every time Ansible does something, you will feel those 100ms.

In the case of Peekl, it's easy : The server will read the content from the local disk (depending on what roles you have, your groups, and also load the variables.) And simply sends the "compiled catalog" to your agent who will go through all of it and performs actions as needed.

?