[CR] - Pair Programming VPS for Content Engineering Devs

[scb6]

@m1yag1 commented on Thu Feb 06 2020

Description

Content Engineering would like an Ubuntu 18.04 VPS in the Rice DC we can use for pair programming. We'd like to set it up with tmux and try out shared sessions. Additionally, we want permission to install dev tools on the server. This is a new experimental thing for us so don't want to constantly barrage DevOps w/ change requests for package installs. We think hive.cnx.org is a good URL for it ;).

Acceptance Criteria

• A server exists that all CE devs can log into with the URL hive.cnx.org
• CE devs have the ability to install software tools on the server.
• A shared session can be created that two developers can interact with and do pair programming.

Acceptance Tests

Checklist for Done

1A-PreDesign

• [ ] Description is complete
• [ ] High-level natural language acceptance criteria is complete
• [ ] A high-level solution (development approach for the code change) is added to the issue
• [ ] If prototype code is generated, it is linked to the issue.
• [ ] If tech briefs are generated, they are linked to the issue.

1B-Decomp

• [ ] The work is broken into reasonable and consistent work items.
• [ ] Story issues are created for the work items, with Description, Acceptance, the label story, and an Estimate.
• [ ] The original issue is changed to an epic with labels Epic and story. The child story issues are linked to it.
• [ ] The work item issues are moved to 1C-NextActions.
• [ ] The story epic issue is moved to Track/Epics.

1C-NextActions

• [ ] Distilled acceptance tests are added to the issue, if created.

2A-InProgress

If the issues' fix is a code change:

• [ ] The assigned DevOps engineer will open a pull request, and the automated pull request checks pass.
• [ ] The acceptance tests is finalized.
• [ ] Documentation of the change has been created and placed in the DevOps Wiki.

If the issue's fix is not a code change:

• [ ] Assigned DevOps engineer will verify the fix passes all acceptance criteria and test.
• [ ] Documentation of the change has been created and placed in the DevOps Wiki.

3A-CompleteVerify

If the issue's fix is a code change

• [ ] The pull request has been approved and merged by another DevOps engineer.
• [ ] The assigned DevOps engineer will perform the tasks to deploy/execute and the acceptance criteria is verified.
• [ ] The reviewing DevOps engineer closes the issue.

If the issue's fix is not a code change:

• [ ] The reviewing DevOps engineer will perform the actions required to verify the acceptance criteria is met.
• [ ] The reviewing DevOps engineer closes the issue.

---

@scb6 commented on Thu Feb 13 2020

@m1yag1 We would like this server to be as locked down as possible since it does not have the security controls that and AWS instance would. (i.e. dedicated VPC with no other access). I know this can be tedious with SSH since there is a hop from bastion required even the sandbox instances, so I can see why having the instance in the RDC would make sense.

I expect that we can install all of the tools you need on this instance, but I would prefer that DevOps stay in control.

[scb6]

Note that DevOps has changed and how this is set up should be a team decision.