1. Overview
   1. Cloud Marketplace enables users to deploy production grade solutions from third party vendors
   2. With the Marketplace, there is no need to manually configure resources
   3. Most Marketplace images provide estimates of monthly charges
   4. Image pricing does not estimate networking costs
   5. Google cloud updates base images for software packages
   6. Google cloud does not update software after it has been deployed
   7. Cloud Marketplace applications can be scaled when additional capacity is required
   8. Each solution has a details page that describes the VM type, operating system, estimated costs, and more
   9. Users can search for a package and select one that meets their business needs
   10. GCP Marketplace can deploy to Anthos clusters no matter where they are running
   11. GCP Marketplace solutions have direct integration with GCP billing and are supported by the software vendor
   12. Some packages allow users to specify the number of virtual machine instances to use in a cluster
2. Support
   1. Support contacts can be found on the package details pages
   2. Support can also be obtained from the broader community on Stack Overflow
   3. Users can suggest new software packages or provide feedback on the existing offerings
   4. Technology Partner membership is required to sell software on Google Cloud Marketplace
3. Deployment
   1. Tools can be used to view, modify, and monitor deployments
   2. Deployment are created with default labels used to organize the deployment
   3. Service options can be updated directly from the Google Cloud Marketplace solution page
   4. Users can SSH directly into a VM instance or manage the instance from the VM Instances page
   5. Users can connect to instances to manually install additional software or modify the software packages
   6. Multiple solutions cannot be deployed to a single instance
   7. Google Cloud Monitoring can be used to track performance and availability
   8. Monitoring agents can be configured with solution-specific dashboards and alerts
   9. When a deployment is deleted, it removes all of the instances and any persistent disks
   10. Cloud Storage resources may not be deleted when a deployment is deleted
   11. Google Cloud Storage resources can be viewed and deleted from the Cloud Storage browser
   12. A custom image of an instance can be created and included in an instance template
   13. Instance templates can be used to deploy instances or groups of instances
4. Failures
   1. Deployments may fail where a project does not have enough CPU quota
   2. Remaining quota for projects can be checked, and additional quota requested if necessary
   3. Most solutions provide logging so software installation failures can be investigated
   4. Users might receive a HTTP 404 error when firewall is not properly configured
   5. Google Compute Engine does not allow outbound connections on port 25
   6. To send email from the instances, use a cloud email service
5. Billing
   1. Billing administrators can create a billing plan
   2. Users are charged for marketplace software and Cloud resources used
   3. The software usage fees appear on the monthly Google Cloud invoice as a separate item.
   4. VM Usage fees is based on vCPUs, memory, or GPUs
   5. VM supports Bring Your Own License (BYOL)
   6. Google bills user for infrastructure separately
   7. Users see an estimate of the costs to be incurred
   8. Estimate are based on minimum recommended configuration
   9. Usage fees are based on measurements set by the vendor
   10. Monthly subscriptions, or a subscription for a specific period, such as a year or longer.
   11. Users can increase the service level or choose a longer subscription period at any time.
   12. Downgrade or service cancellation changes takes effect after the subscription period is complete.
   13. Usage-based subscription is based on measurements set by the vendor.
   14. Pricing can be based on a combination of subscription and usage fees.
   15. Some solutions include Monitoring, which collects metrics, events, and metadata
   16. If the free monitoring usage allotment is exceeded, a fee is charged
   17. Monitoring agent can be disabled
   18. Vendors might offer trials of their software on Google Cloud Marketplace
   19. During the trial, users pay only for the infrastructure
   20. Users can sign up for one trial for every billing account
   21. Trials include a trial period and usage credit, set by the vendor
   22. Trial ends when the credit limit is reached, or when the trial period expires, whichever comes first
   23. If additional resources are allocated, users might reach credit limit before trial period expires
   24. The status of the trial can be viewed in the Google Cloud Console Billing page
   25. After a trial has ended, users are billed when they continue using the solution
   26. To end a trial before the trial period expires, users can cancel the subscription