Re: [Puppet Users] Puppet cloud provisioning and VMware mac address allocation?

[Ohad Levy]

On Sun, Dec 30, 2012 at 7:58 PM, <mbi...@edrans.com> wrote:

Hi all,

I've been working on fully automating the VM provisioning for some months now and one piece I could not resolve yet is to automate the dhcp/dns automation and just because I cannot obtain the VM mac address that vsphere/vcenter will allocate to a new vm.

I am aware of 3rd party tools such as foreman, but in fact, I am concerned they do not follow puppet release cycle, or it's not their priority ;)

Do you mind mentioning what do you mean? The foreman team care a lot about our users and puppet community in general....

 

I am sure that I am not the first one facing this bottleneck when ~200/300 VMs needs to be created. For theas reason I would like to know from those faced this issue and how they worked it out in an efficient manner.

Thanks for sharing your thoughts!

Best,

Martin

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

[mbi...@edrans.com]

Hi Ohad,

Yes, you are right, Foreman team is great with this community - I didn't meant otherwise.

All I want is to explore options to fetch mac addresses assigned by vsphere. that's all.

Anyone can shed some light from experience?

thanks all. 

On Sunday, December 30, 2012 5:58:32 PM UTC, mbi...@edrans.com wrote:

Hi all,

I've been working on fully automating the VM provisioning for some months now and one piece I could not resolve yet is to automate the dhcp/dns automation and just because I cannot obtain the VM mac address that vsphere/vcenter will allocate to a new vm.

I am aware of 3rd party tools such as foreman, but in fact, I am concerned they do not follow puppet release cycle, or it's not their priority ;)

[Ohad Levy]

On Wed, Jan 2, 2013 at 2:58 PM, <mbi...@edrans.com> wrote:

Hi Ohad,

Yes, you are right, Foreman team is great with this community - I didn't meant otherwise.

All I want is to explore options to fetch mac addresses assigned by vsphere. that's all.

Anyone can shed some light from experience?

You can get that kind of info directly from vsphere using its API, or using a ruby library such as rbvmomi or a higher level class such as fog.

good luck,

Ohad 

thanks all. 

On Sunday, December 30, 2012 5:58:32 PM UTC, mbi...@edrans.com wrote:

Hi all,

I've been working on fully automating the VM provisioning for some months now and one piece I could not resolve yet is to automate the dhcp/dns automation and just because I cannot obtain the VM mac address that vsphere/vcenter will allocate to a new vm.

I am aware of 3rd party tools such as foreman, but in fact, I am concerned they do not follow puppet release cycle, or it's not their priority ;)

I am sure that I am not the first one facing this bottleneck when ~200/300 VMs needs to be created. For theas reason I would like to know from those faced this issue and how they worked it out in an efficient manner.

Thanks for sharing your thoughts!

Best,

Martin

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/MTgHLf2RdzkJ.

[mbi...@edrans.com]

Thanks Ohad - much appreciated - I will have a look into that!

M.