7 posts tagged with "API"

The Nutanix Frame platform offers customers the option to create multiple user interfaces through the use of Frame Launchpads. These Launchpads allow customers to customize their environment and create custom apps that are tailored to specific end users and workflows. Each account can have multiple Launchpads to cater to different use cases and workloads (Read more about Frame Launchpads here).

We can further customize a user's experience by using PowerShell scripts to modify the remote Windows environment. These scripts can be used to automate tasks and customize the appearance and functionality of the user interface. These scripts are called FGA Scripts (More about FGA Scripts).

Continuous Deployment (CD) is a software development practice which aims to ensure that code changes or software updates can be safely and quickly deployed to a production environment. CD is only part of a common industry practice called Continuous Integration / Continuous Delivery/Deployment (CI/CD). The goal of CI/CD is to automate the build, test, and deployment of software applications, by using a set of tools and practices.

Frame® Desktop-as-a-Service (DaaS) provides a detailed scheduling capability to ensure that Frame accounts are able to deliver just-in-time production capacity while minimizing the additional cost of having idle cloud capacity. However, Frame does not currently have the built-in feature to alert administrators when an existing production pool is running out of provisioned capacity. This might lead to users not being able to connect to a session because all of the VMs in the production pool are in use at a moment in time. This blog will demonstrate how the Frame Admin API can be used to monitor the actual number of concurrent sessions and send a message to a Slack® channel when the number of active sessions reaches a certain percentage of the provisioned capacity of a Frame production pool.

The Nutanix Frame™ Platform records session and audit log information on what actions users and administrators are doing in the Frame Desktop-as-a-Service (DaaS). This session and audit log information is available for download from the Frame Console. Enterprises often want to combine this session and audit event data with information from other sources within their Security Information and Event Management (SIEM) solution in order to obtain a more comprehensive view of what is occurring in their enterprise. In this blog, we will demonstrate how Frame Admin API can be used within a PowerShell script to retrieve audit data from Frame and insert it into the Splunk® event manager, one of the more popular SIEM's on the market.

Welcome to part two of Building a Frame Web Application! In the previous blog post we focused on making sure we had the proper development environment set up. We also made our first API call, which successfully connected to the Frame backplane to provide us with information about a resource we controlled. It's now time to develop a deeper understanding of how we're making these API calls, and putting them together to do something that's actually useful.

There are contexts in which managing your Frame account by hand isn't enough. Sometimes you need a deeper integration to seamlessly manage all of your services. That's where Frame APIs come in.

In this two-part blog series we will introduce you to the Frame API, both what it is and how to use it. Some programming knowledge is helpful, but not strictly required. The only requirement is knowing your way around a computer.

Cloud-based infrastructure has empowered IT managers with the ability to provide their users with virtually unlimited on-demand compute and storage resources from datacenters across the world. Successful capacity management is key to balancing the cost versus user experience equation. Running and pre-provisioned machines make for quick connections for users, but also consume infrastructure costs by keeping the cloud meter running.