[Disroot staging] - How to implement a disroot node ? #666

Closed
opened 2023-10-03 23:10:19 +02:00 by meaz · 4 comments
Owner

Start thinking about how to implement a disroot node that could be use as a staging area that other team members could have access to test, but also a good way for us to make sure everything works before we switch to prod.

Little explanation.
The idea is to deploy a server similar to the two local test machines used by me and @meaz but accessible to other team members as well. This machine would be setup in similar way to the disroot production and the test servers. But unlike those machines, this node would be passively pulling roles and host_vars from staging branches and would constantly run all playbooks. In that way we could pre-test the updates before they hit production on a live server, test new features and upstream changes, but also start working towards a setup where we could remotely manage number of nodes in totally automated fashion.

Start thinking about how to implement a disroot node that could be use as a staging area that other team members could have access to test, but also a good way for us to make sure everything works before we switch to prod. Little explanation. The idea is to deploy a server similar to the two local test machines used by me and @meaz but accessible to other team members as well. This machine would be setup in similar way to the disroot production and the test servers. But unlike those machines, this node would be passively pulling roles and host_vars from staging branches and would constantly run all playbooks. In that way we could pre-test the updates before they hit production on a live server, test new features and upstream changes, but also start working towards a setup where we could remotely manage number of nodes in totally automated fashion.
Owner

I think the easiest solution would be hosting on a machine (desktop) we could easily access just in case things go wrong and hosted somewhere where we dont have to pay extra costs. I will try to look into a desktop I could put in the house perhpas.

I think the easiest solution would be hosting on a machine (desktop) we could easily access just in case things go wrong and hosted somewhere where we dont have to pay extra costs. I will try to look into a desktop I could put in the house perhpas.
Owner

I am on the hunt for a desktop for my house, so will try to score another one for this project. I will see what price range we should be aiming at, but for sure second hand desktop with decent RAM and cpu.

I am on the hunt for a desktop for my house, so will try to score another one for this project. I will see what price range we should be aiming at, but for sure second hand desktop with decent RAM and cpu.
muppeth changed title from [Disroot node] - How to implement this ? to [Disroot staging] - How to implement this ? 2023-11-21 22:14:33 +01:00
muppeth added this to the 23.12 - December milestone 2023-11-21 22:14:36 +01:00
Owner

Just got nice machine (HP-Prodesk i3-6100T; 16GB RAM) so we are ready to start working on it next month \o/

Just got nice machine (HP-Prodesk i3-6100T; 16GB RAM) so we are ready to start working on it next month \o/
meaz changed title from [Disroot staging] - How to implement this ? to [Disroot staging] - How to implement a disroot node ? 2023-11-26 12:40:18 +01:00
Author
Owner

I'm closing this as we're already working on this.

I'm closing this as we're already working on this.
meaz closed this issue 2023-12-16 18:43:26 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#666
No description provided.