Ansible NXOS

Started by wintermute000, July 03, 2017, 01:46:43 AM

Previous topic - Next topic

wintermute000

Anyone played around with the latest NXOSv and Ansible?


Is it just me, or the bug reports, or are things horrifically buggy with these particular modules? I never recalled having this kind of mess with Arista or even ios_config/ios_template.


https://github.com/ansible/ansible/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20%20NXOS


I'm having issues such as OSPF flat out not configuring even with static variables in the play using syntax straight copypasta from the documentation, and NXAPI transport not working for some modules (but CLI transport works, and then NXAPI works for other modules....)


Either that or I have suddenly become really crap with ansible syntax

burnyd

Just use the NTC ansible modules.

wintermute000

I can't, they don't expose the same functionality, and I don't want to netconf or NAPALM or whatever CLI templates that I'm jinja-ing - I want straight declarative API calls or YANG models.

FWIW burnyd I've been on slack to networktocode - there's been major bugs in going from 2.2 to 2.3 which others corroborate and i confirmed via my 2.2 venv. They say many fixes in 2.4, but now others are piling on and finding new bugs in 2.4. Its not looking promising to be honest - I hope the YANG models are more robust, though at least with that we have vendor support.

Cisco automation: two steps forwards, one step back (though in this case I suppose the blame really is the open source community lol)

burnyd

Yeah all of this is correct lol.  I am on the ntc slack channel and most of the bugs submitted on ansible's network automation 2.3 site is from the ntc site.  So yeah not good.

But just go out and create you're own.  Figure out how to get the right api calls going and just make you're own its a good way to learn.