Folks,
This is awesome news. We had a use case where we used the ruby icontrol gem to find the front end ip address, which then allows you to query the pool, obtain the pool members, then once you have that you can use the node host names to
go into the chef db, and retrieve, things like jdbc connection strings ( custom ohai plug in to retrieve these from tomcat, Web logic, joss, glassfish ). This then allows you to extract the host name of the db server. Now you have all the things
to draw a near real time network map. This can then be passed to any diagramming package. Cannot think of a better use case. This is invaluable to the ops team.
Great work guys, I will go check out the chef integration.
You guys rock.
Sc0tt...
Sent from ....
-------- Original message --------
From: Marc Chisinevski <
">
>
Date:05/09/2014 23:57 (GMT+00:00)
Subject: [chef-dev] Re: F5 BIG-IP
Thanks Matt!
I'd be happy to discuss this. I've had a few conversations with folks
at F5, but I'll be happy to discuss how we can work together.
Thanks,
Matt Ray
Director of Partner Integration :: Chef
512.731.2218 ::
">
mattray :: GitHub :: IRC :: Twitter
On Fri, Sep 5, 2014 at 5:31 PM, <
">
> wrote:
Hi,
Could you please tell me if you'd be interested in a discussion on using Chef
with F5-BIGIP?
I can provide an update on our integration, APIs etc
I'd really appreciate your feedback on use cases and best practices
Thanks,
Marc