Logged Conversation (all times UTC)
[04:51] <stellar-slack> is that grafana?
[05:05] <stellar-slack> yeah
[05:06] <stellar-slack> just getting started with it. but really nice so far
[05:06] <stellar-slack> the way templates work across annotations & metrics is kinda awesome
[05:06] <stellar-slack> gonna have to get deployments wired into this as well
[05:07] <stellar-slack> still not quite sure what to do about alerts, but I have some ideas involving hekad there
[05:19] <stellar-slack> you using influxdb backend then?
[05:43] <stellar-slack> hey
[05:43] <stellar-slack> hi hi
[05:43] <stellar-slack> ok, really appreciate the help
[05:44] <stellar-slack> one other super dumb question (sorry, complete noob)-- do I need to run horizon infront of stellar-core to use a client?
[05:45] <stellar-slack> horizon provides just a nice API in front of stellar-core for clients to program to
[05:46] <stellar-slack> for instance im writing the javascript client library against horizon api right now
[05:46] <stellar-slack> that web clients will then be able to use
[05:46] <stellar-slack> owlsley: that’s influx yeah. I’m also double publishing to netflix/atlas in hopes of using that when it’s ready
[05:47] <stellar-slack> huh
[05:47] <stellar-slack> does that screw your performance to hell
[05:47] <stellar-slack> or what?
[05:48] <stellar-slack> alexpolvi: so right now im developing with stellar-core running one node, using --forcescp to close ledgers itself. then i'm running horizon with IMPORT_HISTORY=true and programming to its REST api
[05:48] <stellar-slack> not from what I can tell. Hekad handles the translation/publishing and adding atlas only added a couple extra ms to the filter duration
[05:48] <stellar-slack> each node publishes once a minute, so a few ms per minute seems pretty viable to me
[05:49] <stellar-slack> andrew: again, total noob over here, what is "closing the ledger" ? will I be able to test transactions?
[05:50] <stellar-slack> andrew: alexpolvi: I haven’t tried this myself, but I believe you’d need to handle the XDR yourself if you wanted to test without horizon in place
[05:50] <stellar-slack> yes this will allow you to submit transactions in xdr form
[05:50] <stellar-slack> closing the ledger simply means applying the next set of transactions to accounts
[05:51] <stellar-slack> ok. so horizon is http-xdr-stellar-core. --forcescp creates a new database all together?
[05:51] <stellar-slack> btw if this is all RTFM please tell me, I'm picking up parts of it here and there. https://github.com/stellar/stellar-core/blob/master/docs/testnet.md talks about forcescp
[05:52] <stellar-slack> @matschaffer: huh, well that's good, i'd have expected a bit more i guess
[05:52] <stellar-slack> turns out hekad is pretty quick :simple_smile:
[05:52] <stellar-slack> you like influx or are you planning on looking at other nosql solutions?
[05:53] <stellar-slack> so client creates a transaction, encodes it in xdr, sends to horizon (/transactions?tx=xdr), horizon sends to stellar-core, stellar-core responds with an xdr encoded TransactionResult, horizon sends that back to client
[05:53] <stellar-slack> atlas is still my favorite time series solution. But the OSS version doesn’t handle persistence yet. So planning to keep both around until it’s ready
[05:53] <stellar-slack> stellar-core exposes a small http interface that horizon uses to submit transactions
[05:54] <stellar-slack> but horizon provides a much more rich api to get account state, transatcions, history, etc
[05:54] <stellar-slack> matschaffer: you mean it's mem only?
[05:54] <stellar-slack> yeah
[05:55] <stellar-slack> but on the plus side it can hand you thousands of time series in <10s :simple_smile:
[05:55] <stellar-slack> that sounds not so fault tolerant haha
[05:55] <stellar-slack> maybe not the best alone for finance software
[05:56] <stellar-slack> andrew: any chance you'd be willing to share you .cfg for your 1-node test stellar-core?
[05:56] <stellar-slack> yep
[05:56] <stellar-slack> one sec
[05:57] <stellar-slack> owlsley: yeah, hence the double publishing
[05:57] <stellar-slack> oh
[05:57] <stellar-slack> have you looked at http://druid.io|druid.io
[05:57] <stellar-slack> cause if you want something for the short term
[05:57] <stellar-slack> druid could handle that in one pipeline
[05:58] <stellar-slack> like you publish the shit with an api, some other soft i don't remember, short term data stays on realtime nodes for quick study, and gets published to a backend as well
[06:01] <stellar-slack> could be worth a try
[06:01] <stellar-slack> on the plus side now that the heka pipeline is in place, also pushing data to druid would be pretty doable
[06:01] <stellar-slack> in the mean time influx seems to be holding up well enough
[06:01] <stellar-slack> erm... "---did you forget a '#'? at line 1 [main.cpp:350]TAL Failed to parse 'stellar-core.cfg' :Unidentified trailing character"
[06:02] <stellar-slack> i just pulled master
[06:02] <stellar-slack> the only thing I changed was to sqlite per https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L63
[06:02] <stellar-slack> andrew: ^
[06:04] <stellar-slack> hmm not sure what the parse error is coming from, it's working for me
[06:04] <stellar-slack> alexpolvi: half wondering if it’s the space after =
[06:04] <stellar-slack> the postgres change you'll need to make has to do with horizon
[06:04] <stellar-slack> it looks at that postgres db for history
[06:04] <stellar-slack> matschaffer: yeah, heard influx is good
[06:04] <stellar-slack> alexpolvi: I just started a build of https://github.com/stellar/vagrant-examples/tree/master/single-peer here, will let you know how it pans out
[06:05] <stellar-slack> matschaffer: druid could just eventually be more simple, though i'm not sure abt this
[06:05] <stellar-slack> https://github.com/stellar/horizon/blob/master/.env.development#L2
[06:05] <stellar-slack> I should probably update my mac’s copy while I’m at it
[06:06] <stellar-slack> matschaffer: oh nice! i'll just use vagrant
[06:06] <stellar-slack> that example is stellar-core only
[06:06] <stellar-slack> https://github.com/stellar/vagrant-examples/pull/3 has some stuff for horizon as well
[06:07] <stellar-slack> but it’s been awhile since I updated the vagrant box that setup uses
[06:07] <stellar-slack> no problem, maybe I can recreate with CoreOS+containers
[06:07] <stellar-slack> i was trying to get it to run on my mac directly
[06:07] <stellar-slack> alexpolvi: containers for stellar-core is actually right at the top of my backlog
[06:07] <stellar-slack> alexpolvi were you able to build it on mac?
[06:08] <stellar-slack> andrew: yeah, it built. had some warnings
[06:08] <stellar-slack> it was working last time i tried too
[06:08] <stellar-slack> so my pull might have broken it
[06:08] <stellar-slack> i just was unable to figure out what the heck was going on
[06:09] <stellar-slack> one other question, if I want to run a gateway, are there any handy things like horizon to get started?
[06:09] <stellar-slack> exchange gateway
[06:12] <stellar-slack> so to run a gateway, at a high level you need minimum you need a way to send transactions, and to be notified when you receive new transactions. this corresponds to you receiving a deposit from a customer, and crediting them for that deposit on the network (sending a transaction), and receiving back a credit from that customer, and sending them back their deposit (receiving a transaction)
[06:14] <stellar-slack> right now, js-stellar-lib makes it easy to create a transaction in javascript, and it will take care of all the xdr stuff for you and submit it to horizon. horizon also provides endpoints (/accounts/transactions) to get transaction history for an account (js-stellar-lib also provides interfaces for this in javascript)
[06:14] <stellar-slack> now all of these libraries and services are in active development
[06:14] <stellar-slack> js-stellar-lib for javascript client side: https://github.com/stellar/js-stellar-lib
[06:16] <stellar-slack> so you use a client to build a gateway? i thought the protocol had native support for exchanges somehow
[06:17] <stellar-slack> right, so account's can create "orders" to buy and sell currencies
[06:17] <stellar-slack> this is done via a transaction, which creates an order object in the ledger for that account, and the currencies it's buying and selling
[06:17] <stellar-slack> also, a gateway is different than an exchange
[06:18] <stellar-slack> a gateway simple bridges external systems and stellar4
[06:19] <stellar-slack> exchanges provide software to buy and sell currencies through the protocol's distributed exchange. exchanges are just client software themselves
[06:20] <stellar-slack> so horizon is a gateway then?
[06:20] <stellar-slack> no gateway is a business concept not a technical thing
[06:21] <stellar-slack> uhh
[06:21] <stellar-slack> alexpolvi here's a video that might help explain some basic concepts: https://www.youtube.com/watch?v=mMEEZBKGcu0
[06:21] <stellar-slack> that's debateable
[06:22] <stellar-slack> jed: the concept of the default gateway is certainly not non technical thing
[06:22] <stellar-slack> alexpolvi: heh, you’ll probably get a kick out of this
[06:22] <stellar-slack> oh fml
[06:22] <stellar-slack> guessing slack or something along the way put in r's
[06:23] <stellar-slack> well this vagrant box is almost up!
[06:23] <stellar-slack> :thumbsup:
[06:24] <stellar-slack> anyway all im headed out, talk to you tomorrow
[06:24] <stellar-slack> thank you guys so much for the help!
[06:24] <stellar-slack> i see my root account on my vagrant box
[06:24] <stellar-slack> good to go
[06:25] <stellar-slack> added a comment to https://github.com/stellar/stellar-core/issues/82 to cover that crlf oddity
[06:25] <stellar-slack> and my osx build is working after a dos2unix
[06:25] <stellar-slack> just FYI
[06:25] <stellar-slack> :thumbsup: :thumbsup:
[06:26] <stellar-slack> alexpolvi: I started poking at a dockerfile, but I think it’ll make a lot more sense to have builds publish debs first
[06:26] <stellar-slack> otherwise you end up with both compile time and runtime assets inside the image which is kind of a bummer
[06:26] <stellar-slack> yeah, we have this crazy thing which will build minimal containers
[06:26] <stellar-slack> https://github.com/appc/goaci/pull/17#issuecomment-94003787
[06:26] <stellar-slack> not quiet done yet
[06:26] <stellar-slack> quite*
[06:27] <stellar-slack> but we are building minimal maria db containers with it
[06:27] <stellar-slack> nice!
[06:27] <stellar-slack> App Container is much more of a RPM/deb replacement
[06:27] <stellar-slack> with full dependencies
[06:27] <stellar-slack> soo containers meet RPM
[06:27] <stellar-slack> I’m sure people will want debs anyway so will probably just do fpm -> package source, then build docker containers from that
[06:27] <stellar-slack> true true
[06:28] <stellar-slack> ok, thanks again, I'm out as well
[06:29] <stellar-slack> have a good night!
About StellarVerse IRC Logger
StellarValue IRC Logger
is part of