The fundamental problem with a CMDB implementation as I see it, is you are effectively in need of a shared comm services for fast action small meta data sets.
That becomes a project all in it's own right. -matt On Wed, May 6, 2015 at 10:36 PM, Allamaraju, Subbu <[email protected]> wrote: > Hi Tom, > > Thanks for adding this slot. > > We do have a fairly full-fledged CMDB in house that keeps tracks of all > our infra and apps. Unfortunately none of that team is going to be able to > make it to the Summit, but I’m trying to have someone do a demo remotely > and participate on EtherPad. > > Subbu > > > On May 6, 2015, at 3:04 AM, Tom Fifield <[email protected]> wrote: > > > > Hi, > > > > Is anyone interested enough in CMDB to run a working session on it at > > the design summit? > > > > > https://libertydesignsummit.sched.org/event/553947ceb7c1c223fa689da188abb9a9 > > > > It was suggested on the planning etherpad, but so far we've found no-one > > interested in running it. > > > > > > Regards, > > > > > > Tom > > > > _______________________________________________ > > OpenStack-operators mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
