[placement][ptg] Placement Over The Parapet
You might be interested in:
in particular Rego (https://www.openpolicyagent.org/docs/v0.10.7/how-do-i-write-policies) Which is inspired by Datalog which is a subset of Prolog
So there are other places in the stack reevaluating older tools for use in new places. :)
From: Ed Leafe [ed at leafe.com]
Sent: Wednesday, April 10, 2019 12:50 PM
To: openstack-discuss at lists.openstack.org
Subject: Re: [placement][ptg] Placement Over The Parapet
On Apr 9, 2019, at 12:08 PM, Chris Dent <cdent+os at anticdent.org> wrote:
> It's a whole big world out there, people doing all sorts of things
> that maybe look a bit like what placement does. What can we learn
> from them? What can they learn from us? In what ways can we expand
> placement world dominance and improve its ecosystem diversity?
I think we need to establish world dominance before we plot on how to expand it. :)
> We are often so busy in the depths of OpenStack that it is hard to
> remain aware of what is out there. What is?
I've shared this blog post  on the etherpad, but perhaps a wider audience might find it interesting. It caught my eye because last year in Dublin as we started to dig deeper into nested resource providers, the way things fit together reminded me of some of the things I had played around with when I looked into graph databases. I ran a series of experiments that I wrote about in my blog (series beginning with ), and am seriously thinking about digging deeper before we get too far down the nested rabbit hole. Even though the blog post was dealing with tracking security groups, it was reassuring to find someone else who also saw cloud resource management as being best modeled as a graph.
So maybe this response isn't what you were looking for (how can we integrate Placement into the wilds of the non-OpenStack world?), but rather how can we integrate some of the lessons of the non-OpenStack world into Placement?
-- Ed Leafe