Define "oligopsony"
The post Network Dictionary: oligopsony appeared first on EtherealMind.
Find out what skills and know-how will be essential in enterprise networking this year.
Today, when an oVirt developer pushes a patch to review on oVirt Gerrit, various validations are triggered in CI via the 'check-patch' job, as defined by the project maintainers. Usually these jobs includes 'unit-tests', 'db tests', static analysis checks, and even an occasional 'functional test'. While it might seem that it covers alot and gives a good indication that the patch is good to be merged, unfortunately it is not always the case.
The reason it's not enough lies in oVirt's complexity and the fact it's a Virtualization project, which means the only real way to know if your patch didn't break things is to install oVirt and try running a few basic commands, like 'adding host', 'adding vm', 'creating snapshots', and other tasks you can only do if you have a full oVirt system up and running. Here is where OST comes in!
oVirt system tests is a testing framework written in Python, using 'python-nose' and oVirt Python SDK and runs on auto-generated VMs created by Lago. It is used by the oVirt CI to run post merge end-to-end testing that runs on a fully deployed oVirt environment and has been proven to detect multiple regressions Continue reading
A few days ago I posted a tweet about a new tool I’d (re-)discovered called jrnl
. Someone replied to that tweet, asking me to list my “multi-platform toolbelt.” While it’s still evolving (every day!), I thought it might make for a good blog post. So, here’s a list of my still-evolving multi-platform toolbelt.
Sublime Text: Over the last few years, I’ve moved to creating the vast majority of my content in Markdown (MultiMarkdown, to be more specific). At first I was using OS X-specific text editors (first TextMate 1.x, then BBEdit), but last year I switched to Sublime Text. Sublime Text supports OS X, Linux, and Windows. I don’t have any Windows-based systems, so I only use it on OS X and Linux.
Wire: My use of Wire is still a bit limited, but only because the reach of the platform is also still a bit limited (this is a classical example of network effect). I’m currently using Wire on Linux and OS X, with plans to extend to iOS and Android. (If you’re using Wire, feel free to look me up! My username is “scottslowe”).
IMAP/SMTP: I’ve standardized on using IMAP/SMTP for all my e-mail Continue reading
The post Worth Reading: Monitoring in containers appeared first on 'net work.
On this, the first “real” post of 2017, I thought it would be useful to reflect on the year that has passed, and consider the year that is coming. First off, 2016 in numbers—
These are all conservative numbers for the most part… I’ve not included journal and blog reading, nor have I tried to accurately count my writing output, as I often find it more frustrating than worthwhile. In the coming year, I plan to finish a book with Pearson, record at least one more video series (potentially more), and continue apace with blogging and other writing.
In 2016, I think we started to see the future of the networking market actually take shape. There seem to be three prongs developing; either companies will move their processing to the cloud, they will move to more hyperconverged/vertical solutions (essentially outsourcing design and architecture to vendors and consulting firms), or move to disaggregation. The day of the router as an appliance is done; we are moving to Continue reading