Plugins » Foreman Remote Execution

Yes, that seems like it can work, and I can automatically make sure the SSH key is installed on the servers when they provision with Digital Ocean.

I believe I got the plugin installed successfully as well. I guess I'd just be uncertain of how I proceed after this from the list of DO Compute Resources VMs to getting it added as a host with the puppet_setup snip, but prob need to read the docs first. (=

Thanks for the quit response!

OK, so I installed remote execution plugin. It seemed to install successfully but now the Foreman front-end crashes. I just used the apt-get instructions for ubuntu, so not sure what went wrong - I can probably figure it out.

However - reading through the instructions, it appears that remote-execution templates are used through existing Hosts, which I am not able to create yet.

I would like the ability to use the available access data from our compute-resources VMs to run puppet-setup and import those servers as new Hosts, without needing to SSH into those servers by hand. (To my sense needing to log into the servers defeats the purpose of using an automation tool.)

Is there some way of running the remote-execution puppet-setup snip on a compute-resources VM, rather than running it via Hosts?

Thank you for your help with this!

OK I resolved the plugin install issue from this info: https://community.theforeman.org/t/error-column-version-of-relation-dynflow-schema-info-already-exists/8791/4

Going to see if I can figure out how I might be able to get this working.

Sorry but I'm still new to puppet and not entirely sure what are actual limitations and what is just my perception.

So I've been exploring everything I can.

But I don't see a way to use remote-execution on a non-host.

This does seem like a great tool for my use-case, but I'd need to be able to run it on a non-host. The whole point is to get puppet setup, which then imports it as a host.

I looked into creating a host without provisioning, but it seems like a mess - this isn't designed for non-provisioning. If I could simply uncheck "enable host for provisioning" and then the required fields didn't matter that would let me run the remote job, get puppet installed, and voila the info is populated. But why do I need to dig up the MAC when getting puppet setup solves everything.

So... it seems like it should be easy to use Foreman to work with pre-provisioned servers, and get puppet setup with a couple clicks, then voila.

I know I can do the puppet setup manually, and it isn't hard. But I'm trying to make this as seamless and simple as possible, so I can train people who aren't comfortable on the command line. If it is possible to get this added as feature, that would be amazing! And I do see other requests for this too when I search, so I think others would like it as well. Thanks!

Sorry I guess I misunderstood your original request then. I though you're fine with associating the VM from compute resource manually, which creates unmanaged host object. On this host, you could then run REX job. You're right, there's no good way of creating unmanaged host through UI, but it's very easy to do so from hammer (CLI), something like

hammer host create --name something.example.com --managed false --build false

should work. Perhpahs I forgot one or two params. The same could be achieved using REST API.

Thanks for your help. Adding a host via cli is much easier to work with.

I'll see if I can get it going from here.