It’s been a little while since I’ve posted screenshots, so here’s the work in progress. I explain how to implement this stuff in chapter 11 of my book (Manning).
App overview page
Applications are a central concept in Zkybase. This is how the app overview page looks so far. (It’s just a start.) The concept behind it is that if you want a 360 degree view of an app (dev view, test view, release view and ops view), you come to the app details page and then you can start looking at different views.
App repository commits page
Here’s a repo commit history for a given app. Right now it’s just integrated with GitHub, but the idea is to provide integrations with other providers too (e.g. BitBucket).
App repository watchers page
Again, an app details view. This time it’s GitHub watchers for a given app repo.
Region details page
Visualizations are one of the more exciting features that a CMDB can offer. One of the huge advantages of putting your configuration management data in a database is that you can move away from Visio documents and Gliffy diagrams, and move instead toward data modeling and automatically generating views. Here I’m using a graph library to generate an interactive graph visualization. It is a great complement to the underlying graph database.
Automation view
This might strike you as a strange screenshot, but in reality it’s an example of the most important view–the automation view. The main reason we want to manage configuration data in a database is that we can build web services (Zkybase supports both JSON and XML views) that simultaneously drive automation and human consumable views of the sort that a support team would use. And the data is accurate because it’s what brings the environment into being–no more chasing your environment around trying to document it.
If you’re interested in checking it out or even getting involved in development, see the.
Archive note. The screenshots described in this entry are no longer present in the original site archive. The text is preserved as written.