Static back-end IPs

[tmart]

We have a growing need to be able to assign static IP addresses for the back-end AppLogic network (hosted environment). Basically, we don't care about selecting them, but once set, we'd like those addresses to persist (until deliberately changed). Maybe some means of communicating from standard AppLogic constructs/descriptors with the controller to negotiate a set of IP addresses that could be selected statically, but dynamically issued via DHCP as they are now?

Among other things, this will allow certain products to work properly that require "registration" to an IP address.

I know that there has been discussion about static IP address assignment. Has there been any progress on it along these lines?

[JAnttila]

tmart,

Can you not use the RFC 1918 192.168.0.0/16 address space that is available on the public network interfaces? This should allow you to have VM's communicate with each other over a private network and fully manage it with application and appliance boundaries which can then be extended to the application as properties.

I have used the 192.168.0.0/16 address space to successfully link together 2 applications that where working as one with one handling all of the java application services and the other operating as a large NAS / filter store for the java app servers. Contact our support team if you need assistance with getting a RFC 1918 192.168.0.0/16 range assigned to your grid backbone.

Thanks,

Jeremy

[PeterNic]

Tim,

Can you clarify the use case -- the only one I do get clearly is the ability to run software that uses IP address as part of its copy/license protection. There was already a discussion on this somewhere else on the forums; there is an (admittedly un-pretty) workaround.

There are several ways to implement this; having some more use cases/workflow will help.

Regards,
-- Peter

[tmart]

Jeremy, We use the RFC-1918 address space in many other situations, but this is one case that I'd like to avoid.

Licensing is one example, as Peter described, where we'd like to have access to fixed IP addresses (but still dynamically assigned, if that's the best way). Another example is for logging. I think that Windows might be another such example, to avoid the Windows 2003 server from getting new IPs. I can't think of too many other use cases - some software / implementations just don't work well when you cannot anticipate IP addresses... you either need this feature or you don't.