nodejs / nodejs/build

Should we use ansible to create the packer images for macos ORKA templates?

Open
#4,327 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jinja
Stars
542
Forks
185
Avg merge
22h 15m
Merged PRs (30d)
4

Description

At the moment the images which we deploy in orka are generated in packer using the code in https://github.com/nodejs/build/tree/main/orka/templates

This does not utilise the nodejs playbooks which means we have a different approach to machine setup on macos vs everything else, and also that the macos roles in the playbook will become increasingly out of date and potentially not work if we ever wanted to set up on a macos machine outside orka.

How feasible would it be to run the node.js ansible playbooks within the packer files instead of duplicating all of the setup within the packer files? The last project I worked on ran ansible locally within the packer files so in theory it could work ...

Noting that we state: "All machines in the clusters are managed using Ansible" which perhaps need clarified as it is not the case for macos.

FYI @UlisesGascon (since I think you put some of this in place originally) and @ryanaslett

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the ORKA templates in orka/templates and the Node.js Ansible playbooks, then compare how macOS machine setup is handled in each. Check doc/jenkins-guide.md#ansible for the claim that all machines are managed with Ansible. Done means establishing a clear approach for creating macOS ORKA images and clarifying the documentation if needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, macos
Domain
build-system, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.