Modeling environments for Google Cloud Platform

To model a Google Cloud Platform environment, log in with a Google Cloud cloud project and specify the Google Cloud-specific information in a blueprint.

  1. Create the blueprint.
  2. Add resources from the palette to the blueprint, such as virtual images.
    The palette shows resources from the currently connected cloud and region, which is shown in the upper-right corner of the page. You can access Compute Engine resources from only a single project that are available to your current region. See Regions and Zones in the Google Cloud Platform Compute Engine documentation.

    For more information on working with the blueprint designer, see Editing Terraform blueprint diagram and Editing blueprint source code.

  3. Add volumes to the images.
    You can add or create volumes in addition to the boot volume for an image's operating system. Only volumes that are not attached to other virtual machine are visible in the palette. You can also create a new storage volume for the image.
  4. Add resources from the palette to the blueprint, such as virtual images.
    The palette shows resources from the currently connected cloud, which is shown in the upper-right corner of the page. For more information on working with the blueprint designer, see Editing Terraform blueprint diagram and Editing blueprint source code.
  5. Create a configuration file and externalize properties to the file.
  6. In the configuration file, ensure that the core OpenStack types are mapped to Google Cloud Platform types.
    The configuration file must have mapping similar to the following code:
    resource_registry:
      OS::Nova::Server : IBM::Google::Server
      OS::Neutron::Port : IBM::Google::Port
      OS::Neutron::FloatingIP : IBM::Google::PublicIP
      OS::Neutron::FloatingIPAssociation : IBM::Google::PublicIPAssociation
      OS::Cinder::Volume : IBM::Google::Disk
      OS::Cinder::VolumeAttachment : IBM::Google::DiskAttachment

Add the components of your application to the blueprint. See Deploying components with blueprints.