#solum

(i mean, outside of exception traces)

Gotta run in 3 min…

paulmo if we make a neat system this could be used by Heat too

so it's is not lost work

Please nudge me int he right directions then to meet Heat's use cases. :)

(possibly lots of other openstack projects) - lets get it right

sure

hmm

Apologies, have to run for a meeting, thanks for discussing all and I'll read back if anything more comes up.

it would appear that you have to do that sort of thing manually regardless

paulmo: ok

so, I am still leaning toward B because that is generally the best pattern when you have a lot of uncertainty around the underlying implementation

(i.e., the "adapter pattern")

worst case, we try it and then we find that it isn't adding any value beyond just calling log.info directly and we have to rip that out

but that is no worse than doing log.info first and finding it is bad and we have to go the other way

best case, ( B ) works out and we don't have to rip it out, and it gives us lots of flexibility to experiment and stuff for years to come

so... I guess we should meet back soon and take a vote

bbl

added my notes to etherpad below adrian_otto's

Arati Mahimane proposed a change to stackforge/solum: Service DB schema and object model https://review.openstack.org/70168