Thursday, 2016-01-28

*** salmon_ has quit IRC01:24
*** dshulyak has joined #openstack-solar07:01
*** salmon_ has joined #openstack-solar08:44
*** tzn has quit IRC09:10
openstackgerritJedrzej Nowak proposed openstack/solar: Increase riak test timeout to 600
openstackgerritMerged openstack/solar: Increase riak test timeout to 600
*** tzn has joined #openstack-solar11:30
*** salmon_ has quit IRC14:00
*** salmon_ has joined #openstack-solar14:26
pigmejdshulyak: can we have documentation for recent feautres ? :)15:31
*** angdraug has joined #openstack-solar15:53
dshulyakpigmej: sure17:02
dshulyaknext week :D17:02
dshulyaki will write it tommorow probably17:05
openstackgerritLukasz Oles proposed openstack/solar: Use yaml to load data in solar create
openstackgerritLukasz Oles proposed openstack/solar: Allow to use any IPs with fuel-devops
pigmejdshulyak: ;P incorrect answer :P17:10
dshulyaki wanted to finish stevedore part and then work on docs17:11
pigmejyeah it's fine :)17:15
pigmeji was joking :P17:15
dshulyakany news from meetings?17:15
pigmejit depends17:16
pigmejfrom solar perspective and all that DP, DR, policy engine nothing changed17:16
pigmejthere are some major issues with rollbacks17:17
pigmejor reverts17:17
tznno reverts ;)17:17
pigmejyeah that's the result of the discussion :)17:17
pigmejwe will for sure make a summary, so don't worry dshulyak you will be aware of everything :)17:22
dshulyakok, i would like to take a look at problems you found with reverts17:24
tznmaybe we should spend some time with Dima tomorrow17:25
tznsummarize the problems17:25
pigmejthe thing is that we didn't find the problems in solar17:25
dshulyaki like pigmej variant much more17:25
pigmejwe found the problem in the bigger picture17:26
pigmejnot solar itself dshulyak17:26
dshulyakyeah, i understand what you are talking about17:26
pigmejdshulyak: the major problem is that when we have multiple data sources (let's say IP data in network manager), with separate databases (each component has it's own database), we cannot control state, because when you change ip from to you *may* be unable to revert this change, because of many reasons17:28
pigmejone could be is already taken by some other service, there is no even anymore in configured network ranges17:28
pigmejand because we cannot force everyone to use solar as a db store, it's impossible to detect those scenarios without continuous online synchronic replication engine like let's say Datomic17:30
pigmejand having this thingy would be veeeeeeeeeeeeeeeeeeeeery complicated and hard to both maintain use and write17:31
dshulyaki think it is doable if revert will be initiated in the application that is the source of the data, in this case in network manager itself, it means ofcourse that application itself will need to keep history of changes17:46
dshulyakwhat is this datomic is doing? this is some kind of transcations app?17:46
*** angdraug has quit IRC17:47
dshulyaki thought that we will maintain consistency using some kind of cross-app transaction, so lets say data is changed in network manager - network manager will initiate transcation, every other service will be aware (including solar), and after solar will say ok i made necessary change - we can proceed with other actions, e.g. deployment17:50
dshulyakit is more like events and aggregation of events before next action17:50
*** dshulyak has quit IRC18:02
*** salmon_ has quit IRC18:31
*** tzn has quit IRC19:00
*** angdraug has joined #openstack-solar19:18
*** tzn has joined #openstack-solar20:50
*** tzn has quit IRC20:50
*** tzn has joined #openstack-solar20:50
*** tzn has quit IRC22:49
*** salmon_ has joined #openstack-solar23:12
*** tzn has joined #openstack-solar23:13
*** tzn has quit IRC23:47

Generated by 2.14.0 by Marius Gedminas - find it at!