Blog post: Provisioning 100 GitLab Spot Runners on AWS in less than 10 minutes using less than 10 clicks (Aug 13)
Triage (REQUIRED)
This issue fulfills one of these goals:
-
Drive traffic to our website -
Convert traffic into leads -
Thought leadership/share expertise -
Build relationships with potential customers -
Drive long-term results (please explain below in your proposal) -
Announcement Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)
-
Cross-functional support Link to OKR (required if this box is checked)
Proposal
A blog post with content similar to the video: Provisioning 100 GitLab Spot Runners on AWS in less than 10 minutes using less than 10 clicks + then updating them all in 10 minutes. Easy provisioning and managing of any runner fleet size!
That video shows a small part of what this automation is capable of which is outlined here: https://gitlab.com/guided-explorations/aws/gitlab-runner-autoscaling-aws-asg/-/blob/main/README.md and here: https://gitlab.com/guided-explorations/aws/gitlab-runner-autoscaling-aws-asg/-/blob/main/FEATURES.md
While I have been encouraged that a blog post about this would be needed by @pete_goldberg, @vsilverthorne provided the encouragement that got me to complete this issue.
Roles and Responsibilities
Person | Role |
---|---|
@DarwinJS |
requestor |
@person |
editor |
@person |
approver (optional) |
Checklist
-
If you have a specific publish date in mind (please allow 3 weeks' lead time) -
Include it in the issue title and apply the appropriate marketing milestone (e.g. Mktg: 2021-03-28
) -
Give the issue a due date of a minimum of 2 working days prior -
If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
-
-
If time sensitive -
Add ~"Blog: Priority" label and supplied rationale in description
-
-
If wide-spread customer impacting or sensitive, mention @nwoods
to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue -
If the post is about one of GitLab's Technology Partners, including integration partners, mention @dpduncan
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts Copy: @pete_goldberg @dpduncan -
If the post is about one of GitLab's customers, mention @FionaOKeeffe
, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts -
Indicate if supporting an event or campaign -
Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)
Production
-
Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) -
Issue sent through triage for consideration (approve, backlog, deny) -
Issue assigned to requestor to draft blog post and open MR -
MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete
Edited by Sara Kassabian