ubicloud VS foreman

The docs still say the Elastic license is used but looking at https://github.com/ubicloud/ubicloud/blob/main/LICENSE it looks like the project might have switched to GNU Affero General Public License v3.0 in the last day.

At Ubicloud, we have 100% line and branch coverage that is mandated on every PR (https://github.com/ubicloud/ubicloud). We also have an E2E test suite that we run periodically and with every commit. We did not really feel like our tests are slowing us down, it actually makes us faster since we have a higher trust to the payload and many manual checks that would need to be done is safely skipped.

> Taken from here: https://ubicloud.com/

Am I the only one getting a certificate error browsing there?

Link to our project: https://github.com/ubicloud/ubicloud

We’re choosing Elastic V2 for three reasons: (1) We’re planning to monetize through a managed service and we’d like the license to support that, (2) Later if we change our mind, we think it’s easier on our users if we go from a restrictive license to a more permissive one, and (3) The Elastic V2 license is much simpler than its cousin, Server Side Public License (SSPL).

That said, Elastic V2 is a new license and doesn’t seem to as popular as SSPL. Also, some projects out there mix and match multiple licenses in their repo to be able to call themselves open source.

Any insights / feedback on Elastic V2 or software licenses in general?

I was confused because there is https://github.com/ddollar/foreman and https://github.com/theforeman/foreman

In case you're unable to use intune, a free approach might be https://theforeman.org/ That works well for provisioning baremetal windows (with discovery image or pxe boot) once you've set it up. It supports script access as well as a nice hierarchy for configurations. But it's really not as well documented as it should be.

I use the foreman with puppet and pxe/kickstart scripts to automate VM/baremetal provisioning etc.

It comes from the remote execution user snippet: https://github.com/theforeman/foreman/blob/develop/app/views/unattended/provisioning_templates/snippet/remote_execution_ssh_keys.erb

KVM & Foreman

Might want to look into https://theforeman.org/ if it's not too complex for you

The iso images are typically locked at a certain verison. The update repositories sounds like what you are looking for to cache updates. Look into theforeman.org and specifically the plugin Katello. This is an upstream for Red Hat's Satellite product. Another option would be Canonical's MAAS. Both of these options Sound like what you are headed for unless you really just mean synchronize into a folder and store the images in which case yeah.....just use rsync.

Alternatively, you can use Foreman+Katello, the upstream base of Satellite, to get started in learning the platform. You can also use the component matrix to use the versions that most closely resemble Satellite.