Enterprises are adopting an automation-driven IT as a Service (ITaaS) approach to deliver services to their organization. This approach is a means to improve operational efficacies, drive down costs, and provide service delivery when and where needed.
To enable the move to ITaaS, admins are using techniques learned from DevOps by utilizing automation to deliver services. These services are enabled by using APIs and creating complex workflows with those APIs. Admins can implement the workflows within several solutions such as a custom portal, service management software like ServiceNow, open-source automation tools such as Ansible, or home-grown scripts built with software tools like Python or PowerShell.
Veritas is pleased to announce our new Veritas Developer Open-Source Collective (VDOC) program. A place where customers, partners, and Veritas employees can discuss, share, and collaborate on all things API and automation. Join us here on our VOX user group and the Veritas GitHub repository to participate in the collection.
Your first stop to finding available resources on APIs within Veritas products is the Veritas.com API solutions page. There you can learn about things like our RBAC enabled API Users schemes, or our API documentation enabled via swagger.
The VOX Developer Open-Source Collective group page is a space to connect and keep up with the latest announcements, discoveries, and conversations around all things open-source and automation at Veritas.
The Veritas GitHub repository is a library of code samples, free for anyone to download or contribute their own samples for others in the community to use. Typical workflows can range from a simple query and data parser to a complex multi-step ansible playbook to automate common NetBackup deployment and operational management tasks
Benefits of the VDOC Community
The benefit of the Veritas Developer Open-Source Collective is that customers, partners, and Veritas Employees can come together to learn, educate, contribute, and support other members as they progress with their use of APIs, playbooks, and their automation journey.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.