Orientdb is an open source graph/document database. It supports various language bindings and plug-ins.
On top of that, it supports TinkerPop Blueprints and Java Data Objects(JDO). The TinkerPop Blueprints are particularly interesting as they provide a graph database Domain Specific Language (DSL) to operate directly on the graph structure.
This all looks like a solid foundation for a Configuration Management Data Base (CMDB), starting with capturing infrastructure information (server connections, service dependencies) in a graph, using a standardized information model structure, and storing configuration item (CI) details as documents.
Goal for the week is to have all the classes of the current CIM model reflected in the database.
This project is part of:
Hack Week 10
Activity
Comments
-
about 12 years ago by kwk | Reply
This plugin connects OrientDB with Pacer for easy graph manipulation and traversal in Ruby
-
about 12 years ago by kwk | Reply
OrientDB supports a graph and a database model. When setting up the database, one has to choose one model. This presentation recommends to use the graph model for our purpose.
-
about 12 years ago by kwk | Reply
Install OrientDB from here. Then (as root) edit /usr/share/orientdb/config/orientdb-server-config.xml and insert
between the tags. Then (as root) systemctl start orientdb.service
Run the console with orientdb
Connect to database with connect remote:localhost MyUser MyPassword
-
about 12 years ago by kwk | Reply
Install OrientDB from here. Then (as root) edit /usr/share/orientdb/config/orientdb-server-config.xml and insert
<user name="MyUser" password="MyPassword" resources="*"/>between the <users> tags.Then (as root)
systemctl start orientdb.serviceRun the console with
orientdbConnect to database with
connect remote:localhost MyUser MyPassword -
-
-
about 12 years ago by kwk | Reply
I consider this project done. The importer code is not perfect but creates classes and parent relationships.
Next step: Class properties, then instances, then instance associations
-
-
about 12 years ago by bmaryniuk | Reply
Most of the time I was looking how to store the actual instances into the Graph database and recursively traverse a CIM instance. The current SrMF project (https://github.com/isbm/srmf) already can clone the system with KIWI as well as it can describe the whole service, as long all XML definitions and XSL transformations are there to the basic CIM providers.
The extension from the Hackweek now also allows to store the data into Object Database (Orient DB in this case) and manipulate it there. The next step for SrMF would be to distribute the database into a grid, where each local node describes only itself but the client tool queries the entire grid. There are plans to support Titan distributed graph database for really big scales (http://thinkaurelius.github.io/titan/) which is running on top of Hadoop. However, the primary focus is to support CMDB in smaller cases within the Orient DB cluster, which is already capable to hold billions of vertexes anyway. :)
Please note, that an alternative attempt to re-implement SrMF (https://github.com/isbm/srmf) once again is "Project Alfred".
Similar Projects
Time-travelling topology on the Rocks by fvanlankvelt
Description
The current implementation of the Time-Travelling Topology database, StackGraph, has served SUSE Observability well over the years. But it is dependent on a number of complex components - Zookeeper, HDFS, HBase, Tephra. These lead to a large number of failure scenarios and parameters to tweak for optimal performance.
The goal of this project is to take the high-level requirements (time-travelling topology, querying over time, transactional changes to topology, scalability) and design/prototype key components, to see where they would lead us if we were to start from scratch today.
An example would be to use Kafka Streams to consolidate topology history (and its index) in sharded RocksDB key-value stores (native to stateful stream processors). A distributed transaction manager (DTM) should also be possible, by using a single Kafka partition for atomic writes.
Persistence with RocksDB would allow time travelling by using the merge operator.
Goals
Determine feasibility of implementing the model on a whole new architecture. E.g. a proof of concept for a DTM, find out how hard it is to do querying over time (merge operator?), howto route fetch requests to the correct instance, etcetera.
Resources
Backend developers, preferably experienced in distributed systems / stream processing. Programming language: scala 3 with some C++ for low-level.
Recipes catalog and calculator in Rails 8 by gfilippetti
My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.
TO DO
- Index page
- Product page
- Admin area -- Supplies calculator based on orders -- Orders notification
- Authentication
- Payment
- Deployment
Day 1
As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.
Day 2
Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.
Hackweek 24
For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.
Day 1