Well written. But some harsh words in there for the new DevOps, microservices nirvana :-) ++ anyway!
Kidding aside, I don't think it's all that bad ... although 20+ years as a network engineer, I've seen a lot of wheels re-invented and lots of the Docker, Kubernetes, microservices ecosystems re-invents a lot - like DNS and overlay networking. I'm all for change if it makes things better, but change for change's sake - I (and I think the collective "we") can do without.
I always lament the biggest advancement in network automation over the past 20 years is moving from screen-scraping Telnet with Perl to screen-scraping SSH with Python. Not that I'm down on Ansible, it provides way more than my little Perl script (better templating, more device support, etc.) but the software abstraction band-aid did not solve the underlying problem - network devices do not have a common language. Maybe the Ansible development effort would have been time better spent in pushing forward NETCONF or similar open standards for network device data model abstraction instead of interface abstraction.
Cheers.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
