Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

puppetdb node classification group map [SOLARCH-543] #51

Open
abuxton opened this issue Jan 17, 2020 · 3 comments
Open

puppetdb node classification group map [SOLARCH-543] #51

abuxton opened this issue Jan 17, 2020 · 3 comments

Comments

@abuxton
Copy link
Contributor

abuxton commented Jan 17, 2020

Use Case

it would be really useful to have a default inventory with groups for the pe infrastructure classification groups.

Describe the Solution You Would Like

Work out a PuppetDB query such as https://puppet.com/docs/bolt/latest/bolt_connect_puppetdb.html#practical-usage
that will query PuppetDB based on the assigned classes and create a suitable inventory.yaml that can be used with bolt directly or as the query for Bolt with the orchestrator.

Describe Alternatives You've Considered

parse puppet resource pe_node_group and render the inventory.yaml from the pe infrastructure node groups tree parent and children.

Additional Context

we can handball it, but it's a pain it's useful to have for customers to prefill in as a template before setup, it is valuable to have post-deploy for reference and can be used for Plan target_nodes

@abuxton abuxton added the enhancement New feature or request label Jan 17, 2020
@ody
Copy link
Member

ody commented Jan 17, 2020

In autope this is facilitated by Terraform, you do not need to touch the shipped default inventory.yaml at all for either xl or large architectural deployments. This is done by adding nodes to the pe_adm_nodes group from within the plan.

If I was doing this sans Terraform and building something more generic, I'd still try to deliver a solution that kept the user away from the complexities of the inventory.yaml file. Would probably use something like Bolt's YAML inventory plugin to reduce the requirements on the user to the simplest definition of a list for initial deployments.

For post-deployment, is the vision for a PuppetDB query more interesting for execution of work from within the PE console or Bolt CLI?

@abuxton
Copy link
Contributor Author

abuxton commented Feb 10, 2020

@ody with the new interface where you can now save your pql to the console (which was not a released capability when i filed this request) its now valid for both. But the initial idea was to have something we would put in the bolt project that meant post deploy they did not have to update inventory but some sort of smart query that followed the classification used in PEADM to expose the various groups so they could be easily used as --target @groups (or what ever that syntax is)
i'm of the same mind you are and managing inventory statically is difficult and error-prone.
i did have in mind something that can be used with PE/or native bolt (incase of DR req)

@abuxton
Copy link
Contributor Author

abuxton commented Apr 9, 2020

@reidmv this query would be useful for someone to generate the inventory from aa manually deployed PE so they can then run convert task/upgrade task

@timidri timidri added feature jira and removed enhancement New feature or request labels Jul 15, 2021
@timidri timidri changed the title puppetdb node classification group map puppetdb node classification group map [SOLARCH-543] Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants