Virtual machine defaults

Hi,

I've had Foreman running for a while now (and it's awesome!) but am having
an issue with virtual machine deployment, in that there is no way of
setting defaults for virtual machines, either via the host groups or the
compute resources section. For example, when deploying to a KVM host, some
users need to use a specific bridge interface for the VM to come up on the
network correctly, but as there is no way of setting a default, they have
to manually select the correct interface whenever they deploy. This would
also be useful for the default CPU/RAM count for example.

Is there a way of setting defaults for virtual machines that I'm missing?

Thanks,

Andy

> Hi,
>
> I've had Foreman running for a while now (and it's awesome!) but am having
> an issue with virtual machine deployment, in that there is no way of
> setting defaults for virtual machines, either via the host groups or the
> compute resources section. For example, when deploying to a KVM host, some
> users need to use a specific bridge interface for the VM to come up on the
> network correctly, but as there is no way of setting a default, they have
> to manually select the correct interface whenever they deploy. This would
> also be useful for the default CPU/RAM count for example.
>
> Is there a way of setting defaults for virtual machines that I'm missing?
>

the initial Libvirt support actually had what you are asking for, but
since we moved to a multi provider impementation we still did not address
this properly.

the overall plan is to:

  1. remove hw defaults from hostgroups (old libvirt hypervisors)
  2. add a matrix of hostgroup <-> hw defaults (or minimum requirement) per
    provider
  3. add all location specific info (such as subnet mapping to vm network
    name)

1 and 2 can be done today, 3 is pending until our new multi location /
multi orgs / tenants work is merged, hopefully during the next couple of
weeks.

as workarounds, you can do a couple of things

  1. use the old hypervisors code, they would allow you to have a default
    hypervisor and vm attributes per hostgroup
  2. change the xml templates we use (they would be found under your fog gem
    inside lib/libvirt/model/compute/templates
  3. use the pull request patch which only sets the default network (only
    valid for debian).

thanks,
Ohad

··· On Thu, Oct 25, 2012 at 5:33 PM, Andy Taylor wrote:

Thanks,

Andy


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/E6VxX9htNNsJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

Hi Ohad,

Thank you very much for the detailed reply, that's very helpful. :slight_smile:

Thanks!

Andy

··· On Sunday, 28 October 2012 08:02:13 UTC, ohad wrote: > > > > On Thu, Oct 25, 2012 at 5:33 PM, Andy Taylor <andyta...@gmail.com > > wrote: > >> Hi, >> >> I've had Foreman running for a while now (and it's awesome!) but am >> having an issue with virtual machine deployment, in that there is no way of >> setting defaults for virtual machines, either via the host groups or the >> compute resources section. For example, when deploying to a KVM host, some >> users need to use a specific bridge interface for the VM to come up on the >> network correctly, but as there is no way of setting a default, they have >> to manually select the correct interface whenever they deploy. This would >> also be useful for the default CPU/RAM count for example. >> >> Is there a way of setting defaults for virtual machines that I'm missing? >> > > the initial Libvirt support actually had what you are asking for, but > since we moved to a multi provider impementation we still did not address > this properly. > > the overall plan is to: > > 1. remove hw defaults from hostgroups (old libvirt hypervisors) > 2. add a matrix of hostgroup <-> hw defaults (or minimum requirement) per > provider > 3. add all location specific info (such as subnet mapping to vm network > name) > > 1 and 2 can be done today, 3 is pending until our new multi location / > multi orgs / tenants work is merged, hopefully during the next couple of > weeks. > > as workarounds, you can do a couple of things > 1. use the old hypervisors code, they would allow you to have a default > hypervisor and vm attributes per hostgroup > 2. change the xml templates we use (they would be found under your fog gem > inside lib/libvirt/model/compute/templates > 3. use the pull request patch which only sets the default network (only > valid for debian). > > thanks, > Ohad > >> Thanks, >> >> Andy >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/foreman-users/-/E6VxX9htNNsJ. >> To post to this group, send email to forema...@googlegroups.com >> . >> To unsubscribe from this group, send email to >> foreman-user...@googlegroups.com . >> For more options, visit this group at >> http://groups.google.com/group/foreman-users?hl=en. >> > >