Global/Dashboard visibility of external IP addresses

[tmart]

`twould be nice to, from the dashboard or some other global view, be able to see Internet-exposed IP configurations… for example, it’d really be nice to see across apps from the dashboard what exposed IP addresses are being used by the different apps, and what state they are in (running/configured-but-down/running app-but IP address is only in standby right now), etc. You already have most (if not all) of this already available via the command-line status, but it would be easier and more meaningful to see it in the context of the dashboard or some global app view.

It would also probably be good to be able to see what apps have what components using Raw interfaces - and how those are configured (IP config info).

The above would help facilitate speedy debugging a problematic app re/startup, which might be being cycled for a quick change of a production environment – where minimal cycle time is critical… and also to help self-document a grid. Since two apps on the same grid could have conflicting but independently valid configurations, it would be great to be able to see this info prior to a console error/warning upon failed startup attempt.

Thanks again!

[PeterNic]

tmart,

This will be cool and useful... In the current version, the only universal support I think can be implemented is for running apps -- essentially going through the "interface info <app>:<comp>.external". If you assume that all IP address properties end on "_ip", you can also list the static ones (non-running).

Most likely we are going to look at this in a slightly different way and expand the way we deal with IP addresses, including tracking which addresses are assigned, in use, even auto-assign external IPs. As soon as the approach is finalized, we can post it here for discussion.

In the meantime, in a less-than-universal way, the desired queries can be run from a script over ssh to the controller -- if you are interested, we can help you do it; I'll also talk with our app engineers to see if they can create them.

Regards,
-- Peter

[Dmitry@Rivermine]

As a workaround I've been using "Description" field to list the IP address that's being assigned to the app. Since I don't change applications IPs once I configure them it's not a problem. The 2.3.9 version also shows the application state (among CPU and Mem) in the AppLogic gui.