4 ms·

Kinda sucks for images that license to the network interface. They added elastic network interfaces, but you can't use those for eth0 (which a lot of software

by nolite 10y ago

Kinda sucks for images that license to the network interface. They added elastic network interfaces, but you can't use those for eth0 (which a lot of software licenses to), so you're still screwed

Alupis 10y ago
How do you mean? I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...), so I can't fully comment on your situation, but it seems you could find out what specifically the license is attaching to and set that up again (if it's MAC, you just override the MAC, etc...). The software I've used that bound to the CPU (which is silly as well) always had a mechanism to "de-register" the software specifically for migrating to new hardware. So you could setup your vm, install all your software, etc... then de-register the software (but leave it installed). Make your "appliance" image (OVA), import to the new "cloud" and re-register your application.
- sithadmin 10y ago
  >I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...) This is super, super common with legacy software products narrowly scoped to very specific business functions.
- toomuchtodo 10y ago
  Very common with niche analysis/grid computing apps: https://en.wikipedia.org/wiki/FlexNet_Publisher https://en.wikipedia.org/wiki/FlexNet_Publisher
- Keyframe 10y ago
  I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...) This was super super super super fun on IRIX when NIC died. Usually in the midst of work chaos.
technion 10y ago
I'll just be happy when I can stop dealing with products that license by USB dongles. Try putting THAT in AWS.
illumin8 10y ago
I'm not sure you understand what was announced. The VMware Cloud on AWS will use standard vSphere Distributed Switch and NSX overlay networking. This means you can completely control what MAC and IP addresses get assigned to all of your VMs, and can hard code MAC addresses for those troublesome applications that hard-code their license to your NIC's MAC address. tl;dr In the VMware world you've always had the ability to specify your own MAC and IP address. In VMware Cloud on AWS you'll have the same ability.
- nolite 10y ago
  re-reading my comment, I have no idea what I was thinking at the time... thanks

by nolite 10y ago

Kinda sucks for images that license to the network interface. They added elastic network interfaces, but you can't use those for eth0 (which a lot of software licenses to), so you're still screwed

Alupis 10y ago

How do you mean? I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...), so I can't fully comment on your situation, but it seems you could find out what specifically the license is attaching to and set that up again (if it's MAC, you just override the MAC, etc...). The software I've used that bound to the CPU (which is silly as well) always had a mechanism to "de-register" the software specifically for migrating to new hardware. So you could setup your vm, install all your software, etc... then de-register the software (but leave it installed). Make your "appliance" image (OVA), import to the new "cloud" and re-register your application.

sithadmin 10y ago
>I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...) This is super, super common with legacy software products narrowly scoped to very specific business functions.
toomuchtodo 10y ago
Very common with niche analysis/grid computing apps: https://en.wikipedia.org/wiki/FlexNet_Publisher https://en.wikipedia.org/wiki/FlexNet_Publisher
Keyframe 10y ago
I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...) This was super super super super fun on IRIX when NIC died. Usually in the midst of work chaos.

technion 10y ago

I'll just be happy when I can stop dealing with products that license by USB dongles. Try putting THAT in AWS.

illumin8 10y ago

I'm not sure you understand what was announced. The VMware Cloud on AWS will use standard vSphere Distributed Switch and NSX overlay networking. This means you can completely control what MAC and IP addresses get assigned to all of your VMs, and can hard code MAC addresses for those troublesome applications that hard-code their license to your NIC's MAC address. tl;dr In the VMware world you've always had the ability to specify your own MAC and IP address. In VMware Cloud on AWS you'll have the same ability.

nolite 10y ago
re-reading my comment, I have no idea what I was thinking at the time... thanks