Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

BloxOne host can be deployed through the Google Cloud Portal (GCP). The process of deploying GCP consists of the following configuration:

  • Downloading the package for GCP from CSP.

  • Configuring GCP.

  • Resizing the disk capacity.

  • Accessing the GCP serial console.

  • Deploying using CLI.

Downloading the package for GCP

Complete the following steps to download the package:

  1. Go to Administration > Downloads.

  2. Go to the On-Prem Hosts pane and select Download package for GCP.

  3. Click Download Package and save the .tar.gz file on your system.

Configuring GCP

Complete the following steps to configure GCP:

  1. Upload the .tar.gz file.

    1. Go to Bucket on GCP.

    2. Click Upload file.

    3. Choose the .tar.gz file you downloaded from the Cloud Services Portal.

  2. Create an image.

    1. Go to the image folder.

    2. Click Create a new image.

    3. Choose the cloud storage file, and upload your .tar.gz file from your bucket.

  3. Choose the machine configuration to be used.

    1. The recommended resources required for virtual appliance deployment are 8 vCPU and 16 GB of memory. For details, see BloxOne Connectivity and Service Requirements.Please select respective flavors which have recommended resources or  e2-standard-4 in GCP

    2. Ensure that your deployment environment meets the minimum deployment requirements.

  4. If you require to open port 443 and port 80, click Allow HTTP traffic and Allow HTTPS traffic check box.

  5. You can specify network configuration in the Network section. Multiple network interfaces can be added from this section. Note: You might need to configure multiple networks with different subnets to use in multiple interfaces. 

  6. Go to the Management section and click Add Item to provide the JOINTOKEN. Specify user-data as the key with the following value:
    #cloud-config
    host_setup:
      jointoken: "your BloxOne join token"

  7. Click Create to create the instance.

Once the host is deployed, it is visible in Cloud Services Portal.

  • You can filter GCP hosts using advanced filters. The Host type is GCP.

  • Tags related to GCP are visible in the Cloud Services Portal.

When GCP is deployed with multiple interfaces, the Allow HTTP and HTTPS traffic option will not be available. You can open ports 443 and port 80 after deployment.

Resizing the disk capacity

BloxOne hosts deployed with this image will have a default disk size of 59 GB. To increase the disk capacity.

Complete the following steps to increase the disk capacity:

  1. When creating an instance in GCP, click Change for the boot disk.

  2. Select the image from the custom images folder.

  3. Specify 750 in the Size field.

Accessing GCP Serial Console

Complete the following steps to access the serial console:

  1. Edit the GCP host and enable connecting to the serial port on GCP.

  2. Once you click the Connect to Serial Console check box, the serial console is launched in two minutes.

Deploy using CLI

Complete the following steps to deploy the BloxOne host via CLI:

  1. Install qemu-utils. Run the following command on Ubuntu:
    sudo apt-get install qemu-utils

  2. Install gcloud. Follow the steps mentioned to install Google Cloud. https://cloud.google.com/sdk/docs/install#deb.

  3. Download the package:

    1. Go to Administration > Downloads.

    2. Go to the On-Prem Hosts pane and select Download package for GCP.

    3. Click Download Package and save the .tar.gz file on your system.

  4. Log in to your Google Cloud account:
    gcloud auth login

  5. Set up your project:
    gcloud config set project <project_name>

  6. Upload archive file to bucket:
    gsutil cp <Image_Name> gs:<Bucket_Name>

  7. Create image:
    gcloud compute images create <Image_Name>--source-uri gs://<Bucket_Name>/<ImageFullName>

  8. Create Instance:
    gcloud compute instances create <Instance_Name> --image  <Image_Name> --metadata-from-file user-data=cloud-init.yaml --zone us-central1-a

  • No labels