On 27 October 2016 at 05:00, Travis Ross <[email protected]> wrote:
> Thanks for the quick response Greg - I'm traveling in India so my timezone > is a bit off. > > Images - These were my initial thought of use with oVirt until I started > thinking about post deployment. I want there to be as little work > necessary on the VM's as they will be for SQC and Engineering Developers to > quickly test features and dispose of the VM. As you mentioned Foreman > *could* still work with the Template - but how would it connect. I could > technically have a static IP that gets changed after build - but what > happens when 2 users try and create a VM at the same time. That's likely > not the best solution. > In addition to Lukas' reply for iPXE, another option for image/template-based booting is this - Foreman 1.13 supports using user-data with oVirt images. In this scenario, Foreman doesn't need to SSH to the box, so it works even if Foreman can't know the IP. In return though, the VMs need to be able to reach Foreman (they'll make a call to /unattended/built when they're done). Might be worth investigating :) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
