Skip to content

raharper/appd-virtual-appliance

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 

Repository files navigation

appd-virtual-appliance

AppD Virtual Appliance (VA) Deployment Utils

VA AWS deployment reference scripts

Set of reference deployment scripts (deploy/aws) are provided to deploy VA on AWS. Scripts use AWS CLI. Scripts are numbered in the order to be executed.

Typical deployment steps below. Steps can be skipped if existing resources (e.g existing VPC) are used.

  1. Configure config.cfg with custom config as needed.
  2. Create an AWS profile (01-aws-create-profile.sh). Skip if a profile exists
  3. Create VPC (02-aws-add-vpc.sh). Skip if an existing VPC is used
  4. Create S3 bucket to upload va raw disk image (03-aws-create-image-bucket.sh). Skip if an existing S3 bucket is used.
  5. Create IAM role to provide access to S3 bucket (04-aws-import-iam-role.sh).
  6. Upload va raw disk image (05-aws-upload-image.sh) to S3 bucket.
  7. Import a disk image to EBS snapshot (06-aws-import-snapshot.sh).
  8. Register snapshot as AMI (07-aws-register-snapshot.sh).
  9. Now proceed to create the VMs using the AMI (08-aws-create-vms.sh)

Typical upgrade steps below. Upgrade involves reusing the network interface and data disk of existing VMs to a new VM.

  1. Capture the current running VM details (01-aws-get-vm-details.sh). Reads the network interface identifier and data disk details.
  2. Terminate the current VMs (02-aws-terminate-vms.sh).
  3. Validate if VMs are terminate (03-aws-get-vm-status.sh).
  4. Create new VMs and attach an existing network interface and data disk. (04-aws-create-vms.sh)

VA Azure deployment reference scripts

Set of reference deployment scripts (deploy/vhd) are provided to deploy VA on Azure. Scripts use Azure CLI. Scripts are numbered in the order to be executed.

  1. Configure config.cfg with custom config as needed.
  2. Create an Azure resource group. (01-azure-create-rg.sh). Skip if an existing resource group is being used.
  3. Create a network security group. (02-azure-create-nsg.sh). Skip if an existing network security group is being used.
  4. Create a virtual network. (03-azure-vnet.sh). Skip if an existing virtual network is being used.
  5. Create a storage account (04-azure-storage-account.sh). Skip if an existing storage account is used.
  6. Upload the va image and create a disk image (05-azure-create-disk.sh).
  7. Create a image gallery (06-azure-image-gallery.sh). Skip if an existing image gallery is used.
  8. Create the image definition (07-azure-shared-image-def.sh).
  9. Create the image version (08-azure-shared-image-version.sh).
  10. Now proceed to create the VMs using the image definition (09-azure-vm-create.sh).

Typical upgrade steps below. Upgrade involves reusing the network interface and data disk of existing VMs to a new VM.

  1. Capture the current running VM details (01-azure-get-vm-details.sh). Reads the network interface identifier and data disk details.
  2. Power off the VMs (02-azure-power-off-vm.sh).
  3. Associate a dummy NIC to enable dis-association of the primary NIC (03-azure-associate-dummy-nic.sh)
  4. Dis-associate NIC and data disk (04-azure-disassociate-nic-and-data-disk.sh)
  5. Delete the VMs (05-azure-delete-vms.sh).
  6. Create new VMs and attach an existing network interface and data disk. (06-azure-create-vms.sh)

About

AppDynamics Virtual Appliance Deployment Utils

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 100.0%