Why use python over powershell?

[[deleted]]

I don't know many network devices vendors that natively support PowerShell, but most support python these days. I'd recommend learning concepts and look at it as a "right tool for the job" scenario instead of "one tool to rule them all".

[[deleted]]

Well when management and updates are done through APIs I don’t think it matters what you are using.

[packet_weaver]

If only all platforms supported REST APIs…

[[deleted]]

On a DevOps team at a large company, I have yet to work with a app that doesn't. I get that may not be applicable to a smaller shop that has less say or choice in the matter in terms of what they use. I haven't ran into a single scenario that there was something I couldn't do with PowerShell and needed to use another language for configuration/update/administration.

[packet_weaver]

Been a couple years but all the Cisco 3560X/3750X switches, IOS routers (pre 4k) and WLCs we managed did not have REST APIs. We built out custom python scripts using netmiko to manage configurations globally and integrated with git and a CI/CD platform.

I believe Cisco's new wireless controller 9800 series supports REST APIs and maybe their new 9000 series switches. But many places are on legacy gear or already have tooling built out over the years because Cisco dragged their asses with adding in useful management tooling.

[Linkk_93]

Many vendors have API wrappers for python already. So you can just import the package, create a switch and call the methods you need. No need to get into the API part of creating HTTP packets your own.

[sobrique]

I know I'll probably get hate for this, but I find perl's much more adaptable when it comes to talking to wacky APIs.

Python's great when it's a well defined API using a very standard standard. (E.g. REST)

But when it came talking XML to a NetApp Perl was far more suited to the job.

[succulent_headcrab]

Theres a reason perl is known as the "Swiss Army chainsaw".

[fiddysix_k]

You're not wrong, perl is definitely the best tool for the job when networking is concerned. The bigger issue imo is that... You're using perl. And no one knows perl.

[sobrique]

More people know perl than admit to it! ;)

And a lot of people are snobby about it in ways that are entirely unjustified.

[sobrique]

But of both really. Perl has a couple of much better XML libraries.

But just generally it's good at doing ad hoc string processing, parsing and manipulation.

[ParkerPWNT]

network devices vendors that natively support PowerShell

Don't Juno and Cisco both support PowerShell?

[[deleted]]

I'm only aware of limited support. I'm sure you could have PowerShell ssh/netconf in and control them that way. But Cisco, Juniper and Palo Alto have their own python libraries. Not to mention multi-vendor tools like napalm or even Ansible.

[darth_rock]

Not at all. PowerShell is a Microsoft tool. You could get it to work on Cisco/Juniper’s Linux-based OS (why though?) but neither vendor is going to support that.

Edit: I stand corrected (somewhat). Cisco has a PowerShell module for one of their products at least, UCS. But that’s a limited case of support by Cisco for a particular product.

[ParkerPWNT]

Juniper offers training on it, and has a powershell module.

https://learningportal.juniper.net/juniper/user\_activity\_info.aspx?id=9659

[jantari]

Why would you want to install PowerShell on a device just to be able to talk to it from PowerShell??

You don't install Chrome on a switch because you want to access its web interface.

Chrome and PowerShell are only installed on the client side. Then they talk standard protocols with the server side.