|Component||Description or Requirement||Example Solution|
|Solution Name||The official product name used in partner marketing materials should be used
for the solution name.
Do not specify the billing type (i.e., usage-based or BYOL) in the solution name, UNLESS you have both a usage-based and a BYOL listing for the same solution. In this case, specify in the solution name of the BYOL listing that it is BYOL.
|Partner Name||This should be the official company name used in partner marketing materials.|
|Tagline||This should be a phrase not a sentence (no period at the end). Avoid using a sales tone in the tagline. Instead, construct a short phrase that describes the solution. This should be a tagline for the product, not the partner.||Example|
|Overview & About Partner:|
|Overview||The overview should include an in-depth description of the product and its
key features. This is an overview of the solution, not the partner.
Proofread for any spelling or grammatical errors. Avoid using a sales tone.
|Learn More Link||The overview section includes a "Learn More" link that launches to a page on the partner's site. This link should be specific to the product being listed on Marketplace.||Example|
|About Partner||This section should provide a description about the partner, including
company focus, mission, or history.
Proofread for any selling or grammatical errors.
|Category||Choose one or more categories that are relevant to the solution. Do not select "Other" as a category unless there is no relevant category that fits the solution type.||Example|
|Version||This should display the solution's correct version and must be formatted with dots (i.e. 10.4.6).||Example|
|Operating System||The base OS on the image must be listed in the OS section of the tech stack.||Example|
|Package Contents||List any software components included in the solution image. (Optional, but recommended)||Example|
|Tutorials & Documentation:|
|Getting Started Guide||Every solution on Marketplace must have a link to a Google-specific Getting
Started Guide. The Getting Started Guide must include screenshots walking the
user through deploying the solution on Marketplace. This should describe the ideal
deployment configuration for the solution, and any actions needed to
get the solution up and running.
The Getting Started Guide must be hosted on the partner's website - not a linked PDF or document.
|Additional Documentation||Any additional documentation - like user guides, drivers, architecture diagrams, etc. - should be linked here.||Example|
|Maintenance & Support:|
|Support Text||This section should include support resources - such as a support email address or phone number - and/or support instructions for the given solution.||Example|
|Support Learn More Link||This links directly to a support resource on the partner's site where the user can easily get support for the solution. This should not be the same as the general Learn More link from the Overview.|
|Terms of Service:|
|EULA Link||Almost every partner should have a EULA to include here.||Example|
|Link Format||All URLs and email addresses displayed in any section of the solution listing should be clickable hyperlinks.|
|Search Keywords||Search keywords will be reviewed as part of the standard Partner Portal
review process. Keywords should adhere to the following guidelines:
Image & deployment
|All software must included on the image||The image must include all software required to use your product, so that your image can be scanned for vulnerabilities. This also prevents customers from launching an incomplete image.||Build your VM image|
|Admin Password||If there is an admin portal used in your solution, the password
must be randomly generated for each instance.
For security, you cannot use a default password and ask users to change it. Users also cannot create their own passwords.
Please see our documentation for steps to set and retrieve automatically-generated passwords.
|Setting and retrieving application user credentials|
|License Keys||Each VM image must have two license keys attached to it.
1) OS license (already present on base VM image)
2) Software license (added by partner)
You can check that the license keys are present with the following command:
curl -s -H "Metadata-Flavor: Google" http://metadata.google.internal/computeMetadata/v1/instance/licenses/?recursive=true
|Create the base solution VM|
|OSPO Compliance||The license text and source code must be present on the image in the location you specified in your OSPO compliance doc. Ensure that the license text and source code is present for every required component.||Open source compliance|
|Next Steps||It almost always makes sense to list 1-2 Next Steps for the user to get
started with your solution.
These should be concise instructions for completing first-time configuration steps.
|Clean VM Image||Your final image should be clean of any unnecessary user accounts and SSH keys. Please remove these when you are done development.||Step 5: Create the base solution VM|
|Firewall Rules||Open as few ports as possible for your solution to function. If you need to open many additional ports, please let us know why.|
|Default Machine Configuration||The default machine selected should be performant enough to handle your solution, but as low-cost as possible for the user.|
|Connect Button Text||By default, the Connect button reads "SSH" for all solutions, regardless of the operating system. For Windows-based solutions, please change this to read "RDP". This is configurable in Partner Portal.|