Stephan Wenderlich wrote: > > Bryan Smith babbled: > > In addition to the LPI Levels ... > > - 300 Architect > > - 200 Senior Administrator (2x exams) > > - 100 [Junior] Administrator (2x exams) > >> - 000 'Hello World' Essentials <=== We are here ;) > >> There is this reality ... > >> - 100-200 exams: (x2 exams) 60 (so 120 total) questions in 90 (180 > >> total) minutes > >> - 000 exams: 40 questions in 60 minutes <=== We are here ;) > > What about the -700 exams (DevOps and BSD)? How do they fare? > > Entry-level? Essentials? Sysad? Architect? Or am I comparing apples > > and oranges? > DevOps Exam is surface scratching for the most people in my humble > opinion. Someone needs years of experience with Linux and Networks > before he can work professionally with DevOps topics.
I don't disagree at all. In addition to my 5 FTE years (plus more contracted) in Red Hat in Consulting, I also spent 2 years in Partner enablement on both OpenShift as well as OpenStack, primarily around Software Defined Storage and Networking. I then spent another year 100% customer-facing during HP's ramp-up with its Container Development solution (based on Pivitol) atop of OpenStack (HP Helion vertical stack). I spent weeks at household name American corporations going through a lot of this with their technologists, and many just wanted to 'bring it in-house' instead of dealing with a vendor, *because* of all the complexity that vendor solutions 'couldn't mitigate.' At HP, unlike Red Hat, I had great difficulty getting Sales to understand this as well. So yes, it's daunting for anyone not a deep, seasoned GNU/Linux system administrator / engineer to try to tackle either. Dashboards don't do much other than for general interfacing, although it has moved forward leaps'n bounds in just the last 5 years ... but still. But ... from what I've seen, the LPI DevOps exam (I have *not* taken it, but I was part of the 'final review' of it post-objectives) does try to address many 'awareness' topics, far less 'configuration.' It's definitely fairly good in that regard, which is why the LPI DevOps exam is geared towards stakeholders more than implementers. That's why it's outside the GNU/Linux track. > Some developers believe they can do copy&paste of some configs they > found at the internet...but this is just unprofessional. Correct. The 'cookbook' method doesn't really work outside of a Proof-of-Concept (PoC) when it comes to cloud and/or stateless instances like containers. Getting people to understand the raw, basic fundamentals, which are heavily built on GNU/Linux internals of kernel facilities (e.g., cgroups, namespace, etc...) as well as networking and storage, especially dynamic solutions (even Kubernetes doesn't do a number of them well either), is like trying to get people to understand basic engineering statics without having a calculus foundation. E.g., the NIST 9/11 report, with the ASCE+ASME on the Twin Towers, comes to mind). So ... does that mean we abandon everyone? No. I'll use the 9/11 - Twin Towers analogy again ... E.g., the US Media lied when it said heat melted steel (most US Media journalists cannot pass 3rd grade science these days, and fail even basic arithmetic that 3rd graders find obvious -- like dividing US$500M by 327M -- same units, millions), but I can teach someone -- a non-engineer -- about the fundamentals of steel's tensile strength, and how heat weakens it. I can then take them back to their gradeschool physical science about a 'fulcrum,' and by drawing the 'supports' of the Towers -- several now removed -- show them how an off-axis load requires less force (weight) to take down a support of another. So ... that's what LPI DevOps does. > Either you understand servers in and out (Lpic-2 and more) or simply > don't touch the system. And do you understand Fabian et al. have done an absolutely fantastic job of creating a number of new LPIC-3 specialities that now 'break out' containers, storage, etc... from virtualization and traditional technologies? ;) Let's all 'be familiar' with *all* of what LPI provides. Then again, that's a good discussion right there. I.e., maybe there's merit in taking 2-3 LPIC-3 specialities and turning them into a LPIC-3 'DevOps Architect' title? Fabian, Matt ... what you guys think? Especially after the newest LPIC-3 exams come out? -- Bryan J Smith - http://www.linkedin.com/in/bjsmith E-mail: b.j.smith at ieee.org or me at bjsmith.me _______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
