• Administrator overview
• Managing users and permissions
  • User roles and access permissions
  • Creating users
  • Editing users
  • Unlocking a user account
  • Resending a user activation link
  • Deleting or deactivating users
  • Using groups
  • Managing departments
  • Managing passwords and password policies
  • Setting account-wide access policies
  • Changing a resource owner
  • Using Single Sign-On (SSO)
    • Using Single Sign-on (SSO) with Azure Active Directory (AAD)
    • Configuring an ADFS claim rule for SSO
• Managing account-wide settings
  • Adding container registries
• Managing public IP addresses
• Managing WANs
  • Overview: VPNs
    • Creating a VPN
      • VPN configuration parameters
        • AWS VPC: VPN configuration example
        • Azure VPN: VPN configuration example
        • Cisco ASA: VPN configuration example
        • Cisco IOS: VPN configuration example
        • Juniper SRX: VPN configuration example
        • pfSense: VPN configuration example
        • strongSwan: VPN configuration example
  • Overview: Skytap on Azure ExpressRoute connections
    • Creating a Skytap on Azure ExpressRoute connection
    • Creating a customer-managed Skytap on Azure ExpressRoute connection
  • Testing the WAN
    • Troubleshooting VPN test failures
  • Connecting an environment network to a WAN
  • Configuring WAN access controls
  • Editing an existing WAN connection
  • Disable a WAN
• Managing Metered RAM and storage usage
  • How usage is calculated
  • Viewing current usage and enabling pay-as-you-go capacity
  • Reserved capacity for Skytap on Azure
  • Reserved capacity for Skytap on IBM Cloud
  • Setting usage limits
  • Setting up notifications
  • VM pinning
• Reporting overview
  • Viewing and exporting user information
  • Viewing and exporting group information
  • Generating department reports
  • Generating audit reports
    • Configuring the webhook service for audit data
  • Viewing usage data
    • Using labels for in-depth reporting
    • Creating usage label categories
    • Configuring the webhook service for usage data
  • Enabling other users to generate reports
• Security best practices
• Other best practices
• Sharing templates with users in other Skytap accounts
• Finding the source environment from a sharing portal URL
• Including your logo in the Skytap interface

VM pinning

For customers that have installed software on Power VMs that is licensed by host serial number and LPAR ID, Skytap allows customers to pin individual LPARs to a host. When a VM is pinned, it will always use the same host serial number and LPAR ID, whether it’s running or not.

Make sure to pin a VM before you activate any software licenses.

• To guarantee that computer resources are available, pinned VMs consume compute resources whether the VM is running or not, and those resources are billed regardless of the run-state of the pinned LPARs.
• If you disable and then re-enable VM pinning for a VM, Skytap can’t guarantee that the VM will run with the same host serial number and LPAR ID as before.
• If you save a pinned environment as a template, the VM pinning settings aren’t stored with the template.

• If you copy a pinned environment, the VM pinning settings aren’t saved with the copy.

  If you reduce the resources of a pinned VM, and then want to increase those resources later, there may not be enough capacity on the host to provide the additional resources.

To pin a VM

Enable VM pinning from the Hardware tab of the VM Settings page.

Where is that?

1. In the Licensing section, select Enable VM pinning.

   

   You can enable VM pinning only when the VM is powered off.

2. Start the VM. Skytap assigns the LPAR to a host, and records both the host serial number and the LPAR ID to ensure that every time the LPAR is turned off and back on again, it always runs on the same host with the same LPAR ID.

   When you start a pinned VM for the first time, it’s assigned to a host. After the VM is assigned to a host, the compute resources for that VM are billed as though the VM were running, regardless of the actual power-state of the VM. This is necessary to guarantee that compute resources for the VM are always available.

3. Activate the software license with the host serial number and LPAR ID displayed on the VM Settings page.