Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

On 22.12.2015 21:12, Yuriy Taraday wrote: > Hello, everybody. > > It's a week old thread and I should've jumped in earlier. Better late > than never. > > On Wed, Dec 16, 2015 at 2:04 AM Dmitriy Shulyak > wrote: > > Hello folks, > >

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hello, everybody. It's a week old thread and I should've jumped in earlier. Better late than never. On Wed, Dec 16, 2015 at 2:04 AM Dmitriy Shulyak wrote: > Hello folks, > > This topic is about configuration storage which will connect data sources >

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hi Oleg, I understand the concern, but in case of integration specifically with Solar, I don't see any reasons to add ConfigDB, because Solar by itself is a ConfigDB. At the same time I would agree that there might be a case, when user uses Zookeeper/Puppet Master/CMDB as a data store, in this

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

The problem with this approach is that we can't manage the interfaces between components without changing the code of 2+ components (i.e. one that provides the data and all that consume it). I also don't like polling model for data processors. In my understanding, components should push their

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Comments inline. On Mon, Dec 21, 2015 at 1:42 PM, Oleg Gelbukh wrote: > The problem with this approach is that we can't manage the interfaces > between components without changing the code of 2+ components (i.e. one > that provides the data and all that consume it). >

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

I definitely agree with what Evgeniy said. @Oleg could you make a step-by-step how do you imagine this integration (with separate ConfigDB) ? To me this adds at least one component / integration point. > The point is that for Solar integration, we still need integration points, > and the less

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

On 21.12.2015 11:42, Oleg Gelbukh wrote: > The problem with this approach is that we can't manage the interfaces > between components without changing the code of 2+ components (i.e. one > that provides the data and all that consume it). What code is supposed to be changed in an example LDAP data

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hi, The idea behind configdb is that it is independent component that defines data flows between other components of the system. It has no knowledge about those components or specifics of their data. Data formats are defined by components themselves via schemas/templates and can be changed at any

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hi Dmitry, I also don't think that we should duplicate the data in configdb, because in this case there will be +2 additional interfaces which will require to covert the data into configdb and after that from configdb to Solar, which seems redundant overhead. But we should be able to put the

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

+1 for Lukasz concerns. But if we really need operate with "solar resources database" as a kv store, then we could implement service on top of it, It could be then separate project, which would work as separate service. Would it fulfill the requirements ? (we could implement it using some already

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hi Dima, On Wed, Dec 16, 2015 at 12:03 AM, Dmitriy Shulyak wrote: > Hello folks, > > This topic is about configuration storage which will connect data sources > (nailgun/bareon/others) and orchestration. And right now we are developing > two projects that will overlap a

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

On Wed, Dec 16, 2015 at 12:40 PM, Bogdan Dobrelya wrote: > Data resources shall fill the configdb by results of the fetched data > shaped by data processors aka serializers. The shaping process assumes > applying of all versioning and schema transformations knowledge

[openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hello folks, This topic is about configuration storage which will connect data sources (nailgun/bareon/others) and orchestration. And right now we are developing two projects that will overlap a bit. I understand there is not enough context to dive into this thread right away, but i will