text stringlengths 9 408 |
|---|
[739.52 --> 740.44] Couldn't agree more. |
[740.76 --> 740.94] Yeah. |
[741.24 --> 747.90] So I think, you know, speaking of things that people shouldn't do, turning Ansible into a programming language is probably up there, right? |
[748.02 --> 750.36] I mean, you can do some pretty crazy stuff in Ansible. |
[750.72 --> 753.92] And my day job is related to OpenShift at Red Hat. |
[754.10 --> 759.02] And a lot of the OpenShift installer stuff for version three, the last major version, |
[759.72 --> 764.76] there was some pretty crazy hacky stuff going on in those Ansible playbooks and stuff like that. |
[764.92 --> 767.98] But what's the most crazy thing that you've seen with Ansible? |
[767.98 --> 772.76] I think it's the abuse of the when condition in tasks. |
[773.44 --> 778.16] When your when condition is longer than the rest of your Ansible task for a given piece of automation, |
[778.52 --> 779.84] I think that's where you've failed. |
[780.46 --> 784.38] At that point, in Ansible, you can write modules in Python. |
[784.58 --> 789.76] You can actually, there are ways to write modules in other languages too, but typically you'd write it in Python. |
[790.30 --> 794.74] And if you're going to use complex logic to determine whether to do something or how to do something, |
[794.74 --> 796.58] that should be in Python. |
[796.88 --> 802.90] At that point, you're getting into advanced Ansible usage that requires you to have some of that programming knowledge. |
[803.48 --> 806.30] Programming in YAML is a terrible, terrible idea. |
[806.54 --> 807.22] Never do it. |
[807.62 --> 812.18] Every time I have gone further than an if-then or an if-else type condition, |
[812.36 --> 813.46] I've regretted it. |
[813.52 --> 814.62] And the maintenance is a nightmare. |
[814.62 --> 820.28] And then there's always the ginger 2 stuff that people do, the crazy templating, for loops, all that kind of stuff. |
[820.60 --> 821.12] So yeah. |
[821.52 --> 823.30] Anyway, should we talk about Ansible 3 for a minute? |
[823.54 --> 826.96] There's been a big release in the last few weeks of Ansible 3.0, |
[827.04 --> 830.58] which brings a lot of changes to the way in which modules are delivered to users. |
[830.86 --> 832.52] What do you make of all that change? |
[832.52 --> 834.80] It's been an interesting transition. |
[835.18 --> 840.78] And I think it's ongoing and will be ongoing for another period of time, six months to a year, probably. |
[841.36 --> 847.72] Mostly because Ansible 2.9, which is the previous major version of what you would get when you installed Ansible |
[847.72 --> 850.52] using PIP or a package manager or something like that. |
[851.06 --> 853.62] Ansible 2.9 will still be supported for a while. |
[853.62 --> 859.58] Ansible, mostly because I think there's just a lot of people who the transition to the new version of Ansible |
[859.58 --> 863.50] does introduce some changes that could impact people's workflows a little bit. |
[864.04 --> 867.94] The good thing about the transition is that all my existing playbooks, |
[868.00 --> 870.54] and I have a ton of playbooks that do a ton of different things, |
[871.04 --> 876.54] they all work fine if I just upgrade Ansible using PIP, which is the Python package manager. |
[876.94 --> 881.82] There are other ways to install Ansible that might not work with Ansible 3 the same way anymore. |
[881.82 --> 883.28] So you have to watch out for that. |
[883.46 --> 886.96] And that's why I always recommend using PIP to install it. |
[887.16 --> 889.92] It's a Python program and PIP is the preferred way. |
[890.66 --> 898.72] But the big, big change is that collections of modules used to all be maintained in one giant code base. |
[899.26 --> 902.06] And there were various reasons that was not very sustainable. |
[902.76 --> 906.58] There were something like 4,000 or 5,000 different plugins and modules. |
[906.84 --> 910.28] And the core team of developers who managed the releases and things, |
[910.28 --> 911.66] it was just a lot to coordinate. |
[912.28 --> 917.30] So the main goal was to move all of that content out into smaller collections |
[917.30 --> 921.34] that could be maintained by people with more knowledge of just the modules in that collection. |
[921.50 --> 927.90] Like, there's no reason why a, let's say, an F5 network load balancing module |
[927.90 --> 935.86] should be under the same maintenance umbrella as a, I don't know, like a email script thing. |
[935.86 --> 941.66] All these different modules were lumped together from network vendors and storage vendors and cloud vendors and Linux and Windows. |
[941.96 --> 943.56] So now it's all broken out. |
[944.18 --> 950.88] But the challenge has been making it all come together back into what we install if we do a PIP install Ansible. |
[950.88 --> 957.16] And the nice thing is it all works, but the downside is there are a few little bumps, |
[957.26 --> 959.36] especially if you have specialized use cases. |
[959.62 --> 966.94] But another cool side effect is you could install Ansible without all that stuff and just add in the few things you need. |
[967.04 --> 971.26] So if you just do Linux administration, you can install Ansible plus the Linux modules |
[971.26 --> 975.16] and not install Windows, not install networking, not install cloud. |
[975.16 --> 981.00] So it does offer some flexibility, but I think there's going to be some growing pains over the next year. |
[981.40 --> 983.50] We've seen that trend quite a lot in technology at the moment. |
[983.84 --> 987.98] You know, Docker being an example with Podman coming along to kind of break that out into, |
[988.22 --> 992.18] you know, being less of a monolith type deployment model. |
[992.64 --> 994.12] So I think it's a good thing personally. |
[994.50 --> 998.14] And, you know, the work that's gone in has clearly been very well thought out. |
[998.14 --> 1005.48] Are there any particularly good resources that you'd recommend people visit to get their head around what the major changes are? |
[1005.92 --> 1010.08] The documentation is the best place to know what's going on. |
[1010.16 --> 1014.32] There's not only is there a guide for upgrading Ansible in the release notes. |
[1015.18 --> 1022.06] And if you are involved in using Ansible, I would highly recommend subscribing to the Ansible project mailing list on Google Groups. |
[1022.28 --> 1025.94] But the guides and the documentation are by far the best. |
[1025.94 --> 1032.10] They encapsulate everything that I could ever think of that people could be that could affect someone's workflow. |
[1032.96 --> 1035.84] And also, I did update my book recently. |
[1035.84 --> 1042.64] So if you are interested in learning Ansible and you don't know it yet, Ansible for DevOps has a major second revision. |
[1042.84 --> 1045.22] I've actually revised it 25 times now. |
[1045.72 --> 1051.00] But a major revision happened to incorporate some of the information about collections, especially. |
[1051.00 --> 1056.96] And I'm still working on fully revising the book to be up to date with Ansible 3. |
[1057.60 --> 1058.30] It all works. |
[1058.38 --> 1060.90] It's just there are some things that could be optimized a little more. |
[1060.90 --> 1065.12] Datadog.com slash self-hosted. |
[1065.28 --> 1072.00] Analyze code level performance across your entire environment and troubleshoot issues faster with Datadog. |
[1072.38 --> 1078.60] Datadog has a continuous profiler that automatically collects profiles from your production servers all the time. |
[1078.68 --> 1083.50] So you can then analyze your data quickly with minimal overhead when you need. |
[1083.50 --> 1088.68] Get a snapshot in time and troubleshoot and then visualize it with their beautiful dashboards. |
[1088.68 --> 1096.58] Get a unified picture of your environment by correlating code performance metrics with your other monitoring data with real-time dashboards. |
[1096.66 --> 1097.86] You've got to see these dashboards. |
[1097.98 --> 1103.34] Go to datadog.com slash self-hosted to get a free trial and to see these beautiful dashboards. |
[1103.56 --> 1106.18] And you'll get a free t-shirt when you sign up a trial and create a dashboard. |
[1106.18 --> 1117.46] With tightly integrated APM, tracing, log management, and continuous profiler products in one single platform, Datadog enables you to pinpoint the root cause of issues faster than ever. |
[1117.46 --> 1124.14] Are you seeing the value here when you can visualize everything at once down to the application level, server stuff, even website performance? |
[1124.26 --> 1125.90] It's all in Datadog. |
[1126.02 --> 1127.90] And you can get smart alerts as well. |
[1128.38 --> 1135.48] Try Datadog's products for free for 14 days by visiting datadog.com slash self-hosted for a limited time. |
[1135.56 --> 1139.66] If you start a free trial and create one dashboard, you'll get a free Datadog t-shirt. |
[1139.88 --> 1141.18] And who doesn't love free swag? |
[1141.44 --> 1144.78] So that's datadog.com slash self-hosted. |
[1144.78 --> 1148.84] So Jeff, I've been watching on your YouTube channel. |
[1148.96 --> 1152.36] You've been doing the impossible with Raspberry Pis. |
[1152.46 --> 1156.88] I'm talking like, I think one of your setups was like 10 SATA disks. |
[1157.36 --> 1158.74] 16 hard drives. |
[1159.08 --> 1160.02] How is this possible? |
[1160.14 --> 1161.72] How is this madness accomplished? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.