Skip to content
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.

A best practice guide, on publishing your marketplace application.

License

Notifications You must be signed in to change notification settings

gridscale/marketplace-guide

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

19 Commits
 
 
 
 
 
 

Repository files navigation

This repository has been archived

Marketplace Application How-To

Even though our Marketplace supports all Operating Systems, this guide focuses on Linux based operating systems. If you want to maintain the application through regular releases we recommend programatically publishing your app with provisioning tools like Ansible, or alternatively our Terraform integration. We are working on a Packer integration, which will further simplify this process.

The Publish Process:

Create Server + Storage

  • Connect the server to the public network, with an IP address.
  • The configuration of the server can be lower than what the application needs, the required cores and RAM will be set later when publishing the app.

Install the application

  • Install the application to the point where the user would run further install scripts, or before something dynamic like the servers IP address is required.
  • Once installed take a note of important variables already set, and these should be echo'd to the terminal once the user logs in, this can be done via the message of the day or any executable script and adding an execution line to /root/.bashrc.

Cleanup the image

  • Run the cleanup.sh script to do a soft cleanup of the Storage.

Take a Snapshot

  • Once taken, export the snapshot to your Object Storage.

Requirements

  • Send an email to [email protected] - requesting to become a marketplace application publisher. Include as much information as you can, such as what application you would like to publish and some information about who you are. Make sure to include the email address of your gridscale.io account - so we know which contract to activate.

  • Take advantage of our firstboot script service, this a secure way to generate the root password upon boot, as well as communicate it to the enduser. To use this script, pwgen will need to be installed. To activate the script, make sure firstboot script exists and lives in the root directory, and add the firstboot.service to the /etc/systemd/system/ directory. Aftwards, active the service with systemctl enable firstboot.service.

Recommendations

  • Before taking the final snapshot, run the cleanup.sh script.

  • Update all repositories.

  • Setup a standard firewall, that allows just enough for the application, and provide this confiration to the user.

  • Add a message of the day, this can increase the user experience and also provides an advertisement opportunity (with ASCII art).

  • Keep any scripts and custom files that should be removed later on together, for example in /opt/<application_name>. This makes cleanup easier before running cleanup.sh.

  • You should customize the cleanup script, to remove any files, and the script itself.

  • Unneccessary installation tools, that are not necessary to run the appication (git, cURL), should be removed to keep things lightweight.

Publish to the marketplace

Once published - we will review the application and let you know once it has been published.

Updating / Deprecating the Application

Once accepted, the application can no longer be edited for security reasons. To update the application you will simply need to make the changes to your storage, create another snapshot and export it to S3, from there you can publish the new application version to the marketplace. As the application creator, you are welcome to remove the app at anytime.

About

A best practice guide, on publishing your marketplace application.

Topics

Resources

License

Stars

Watchers

Forks

Languages