move enc data to consul #389

Open
opened 2025-09-07 16:44:10 +10:00 by unkinben · 0 comments
Owner

reasons:

  • cobbler has failed in the past (single point of failure)
  • cobbler is great at pxeboot and kickstart management
  • cannot terraform adding management roles

Why use consul?

  • consul is highly available
  • can terraform consul kv
  • consul is fast
  • consul api is easier to work with (python modules for example)

Plan? None really.

  • Store hostname, mgmt_class and a params hash in json format.
  • Create a script that can read these values and produce an enc-formatted-yaml output.

Streach goals:

  • manage consul roles/policies from terraform
  • generate consul tokens from Vault
reasons: - cobbler has failed in the past (single point of failure) - cobbler is great at pxeboot and kickstart management - cannot terraform adding management roles Why use consul? - consul is highly available - can terraform consul kv - consul is fast - consul api is easier to work with (python modules for example) Plan? None really. - Store hostname, mgmt_class and a params hash in json format. - Create a script that can read these values and produce an enc-formatted-yaml output. Streach goals: - manage consul roles/policies from terraform - generate consul tokens from Vault
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 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: unkin/puppet-prod#389
No description provided.