Hm, API Services no longer present or suggested? I don't think so. It is, I can see it in the SW download page:
OnCommand API Services 1.2 (GA)
New in this release
OnCommand API Services 1.2 includes the following new features:
Adding storage systems directly to the API server Provisioning capabilities using APIs Protection capabilities using APIs Jobs Configuration checker in the installer bundle Support for OnCommand Performance Manager headroom and cluster metrics Bug fixes
NetApp SLM 1.0 is currently a) only available for Linux and b) RC2 status. It doesn't express clearly anywhere that I have been able to find that API Service will be replaced completely by the new SLM (that may be the case?). It just says:
* Platform-specific device APIs for storage management * SLO-based APIs for service level management of storage resources * Access to pre-defined Storage Service Lvls by using the web UI and APIs * Automatic mapping of SSLs to storage resources * Automatic provisioning as per the storage service level by using APIs * Monitoring and regulating based on used or allocated capacity
So the point #1 may be what is in actual fact a replacement, or inclusion of the current API Services. I don't know, there's nothing anywhere that says this explicitly.
Anyone knows any more details around the plans fort his? Will API Services be decommissioned in the future (far or near)?
I'm a customer so the Field Portal doesn't really tell me anything
/M
On 2017-02-24 16:28, Milazzo Giacomo wrote:
Hi,
pay attention that API server is no longer present and/or suggested to use. The new SLM 1.0 integrates in it "also" the old API functionalities but at the same time offer a lot of tools to generate actions such as provisioning, tiering and monitoring with a "device agnostic" point of view. This is one of the step that NetApp moved toward its DataFabric vision, and cloud.
More on FieldPortal.
-----Messaggio originale----- Da: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Per conto di Ehrenwald, Ian Inviato: venerdì 24 febbraio 2017 04:16 A: toasters@teaparty.net Cc: Larsen, Royroy.larsen@hbgusa.com Oggetto: WFA vs OnCommand API Services vs NMSDK vs ..
Hello My coworkers would like to integrate volume-related tasks (creation, sizing, mounting, offlining, destroying) into their Salt-based automation/devops stack. They want to use a well documented REST interface if at all possible. I was asked to do some research into the best way for them to go about doing this and I think I'm more confused now vs when I started. NetApp has a handful of ways to skin this cat. I found:
NMSDK is really raw, and support for Python seems pretty weak compared to PowerShell or Perl. We'd basically have to roll our own "thing". Too much time and effort reinventing the wheel.
Some stuff on Github that kinda sorta might work, but was last updated years ago.
Workflow Automation, but that seems overkill and pricy for what the (current) requirements are.
ONTAP API Services which seems closest to what they want, but then gets tangled up in OCUM/OCPM? I guess this actually isn't a huge deal, as we do have OCUM 6.4P1 and OCPM 2.1.0P1 integrated together and looking at all of our clusters.
What are other people doing for automation of various storage related tasks?
Ian Ehrenwald Senior Infrastructure Engineer Hachette Book Group, Inc.