Yes, I’ve heard of ansible…. Another person in our department is touting that as a tool that will save them a lot of time. Will have to keep an ear out for that. I could probably piggyback onto their ansible box to do those things.
--- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354 | [email protected]<mailto:[email protected]> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] From: Ed Leatherman [mailto:[email protected]] Sent: Wednesday, March 21, 2018 4:55 PM To: Lelio Fulgenzi <[email protected]> Cc: voyp list, cisco-voip ([email protected]) <[email protected]> Subject: Re: [cisco-voip] building an API box - what do I need? I'm interested in the topic as well. I just have a Linux vm where I can load python or perl mods that I might want to run. To answer your last question, for the few things I've ever done with it I always ask for the credentials at run-time, that way it is running as whatever CUCM user is doing the operation (on the off chance it's not me). We just had an ansible workshop here yesterday, I might start using that for managing VG2XX's (code upgrades and the like). Not strictly API related, but ansible might be another thing you'd run on a box like that if you're inclined. On Wed, Mar 21, 2018 at 4:17 PM, Lelio Fulgenzi <[email protected]<mailto:[email protected]>> wrote: I'm going to make a (sad) attempt to try my hand at API usage. You know, running those sweet commands against CUCM or WebEx, etc to make my life easier. I'm hoping that by starting with some simple examples, I can build what I need as time goes on. My hope is to build scripts that I can run via CLI, but also create simple web pages with buttons that execute those scripts, with or without arguments. The webpages themselves will be protected appropriately. But I'm starting from scratch. I do have a resource that I'm hoping will help out, but I'm wondering, if you were building an api box from scratch, what sort of things would you want (or need) on it to make things run smoothly? I'm guessing if I want to automate any of these scripts, I'll have no choice but to store the userID/password either in the script or read from a file. I've asked this before of a few people, but there is no real way to store a password securely and decrypt it at time of running the script. For interactive scripts, either CLI or web form, do you use the same userID/password, or are you asking for credentials and use those credentials? I know... a big ask. --- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354<tel:519-824-4120%20Ext.%2056354> | [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs><http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip -- Ed Leatherman
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
