Create a clear process, which outlines ownership throughout each sub-flow, with a breakdown of mid-level tasks, order of execution, timelines for delivery and standards for process management.
Strategic Partnerships - Relationship, direction & project
Omnibus team - Packing and maintaining
Partner Marketing team - Announcements and promotions
Due to lack of available resources in the packaging team, Eliran Mesika, Director
of Strategic Partnerships, will be the temporary maintainer of the available cloud images. Once hiring
will complete for the packaging team they will reinstate their ownership as maintainers of the images.
Project Building Blocks
Progress Tracking: GitLab issue
Project Storage: Omnibus repository
Documentation: Omnibus section documentation
Partnership Details & Contacts: dedicated partnership Google Doc
Credential Management of Cloud Services: GitLab Images 1Password vault
Marketing Resources: need information of where logos are stored (to add to the process)
First Time Images
Project Owner: Strategic Partnerships
Introduction & Scope - initiated by Strategic Partnerships:
Create issue for first time image
Gathering of documentation on integrating with the Cloud Partner
Understand joint marketing efforts opportunities for collaboration on launch
Set up GitLab account on Cloud Partner’s system
Optional: Initiate technical call with Omnibus team member and partner tech/product lead (at request of Omnibus team)
Introduce Partner Marketing to marketing contacts from Cloud Partner
Technical Implementation - led by Omnibus team:
Scope level of effort
Update issue with Assignee and Due Date
Upload image to cloud service - see it through partner testing:
Follow-up with Cloud Partner’s support team, if needed
If Cloud Partner’s support team is unresponsive, escalate to Strategic Partnerships
Create new section in documentation - align MR with marketing launch
Marketing - led by Partner Marketing:
Create marketing issue
Align on joint marketing activities with partner marketing from Cloud Partner:
Joint blog posts (on GitLab and Cloud Partner blogs)
Social network burst
Write image description that will be part of the image on the cloud service (seek assistance from technical writer if necessary)
Align release to market with Product Lead from Cloud Partner
Customer story/quote - locate an existing GitLab customer who would use this feature for a marketing quote or story
Process flow: step 1 must be complete before step 2 & 3 begin. Steps 2 & 3 can start and progress simultaneously.
Maintaining Existing Images
If an omnibus package has been uploaded - maintenance won’t be necessary for version or security updates.
Image update/maintenance catalysts:
Timeline: an image update should be released within 3 business days following the release
Security vulnerability update
Implementation - led by Omnibus team:
Create new issue
Technical Info - led by marketing:
Update image description and documentation on cloud partner platform
Submit to AWS Marketplace for review before publishing.
Monitor the status of your submission by visiting the Self-Service Listings dashboard.
Once the listing information has been provided (either through SSL or through email), and AMI ID have been received, the AWS operations team will begin processing the request. If they encounter any issues or when the product page is ready for review, they will contact you via the e-mail alias firstname.lastname@example.org.
With any questions you can refer to the Seller Guide as a reference and if you are unable to find an answer, you can email their support.
Manage the account and details on the publisher portal, choose 'Personal' account
to continue the login.
Once logged in, you can view the images and the marketing information for the account there