Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <keviny> it would forward it to the partition based on that
    slackbot2 <hsiliev> Thanks. I want to dig deeper, so I'll add some tests on top of your PR. Would be a good excercise
    slackbot2 <hsiliev> Good day/night :slightly_smiling_face:
    slackbot2 <keviny> I’ll add a test on the case where no sink is configured when i get the chance. Have some urgent stuff to do :(
    slackbot2 <keviny> Good night and thanks
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <hsiliev> @jsdelfino Any progress with npm publishing?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <hsiliev> If you think an account/org in npm can help, SAP can cover the costs
    slackbot2 <keviny> @hsiliev I added the test for my PR yesterday :slightly_smiling_face:
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <hsiliev> @keviny Thanks. I had these half the way done :slightly_smiling_face:
    slackbot2 <hsiliev> At least I know what this part of the tests do
    slackbot2 <hsiliev> !here|@here We investigated an issue with 401 from provisioning plugin. If we mark a doc as "error" and later submit the same usage we'll get 409 I guess?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <hsiliev> I can see we call dataflow.replay on app start, but we are not calling it with timer or something
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <keviny> Wait I meant just now, not yesterday
    slackbot2 <keviny> 401 is authorization issue though
    slackbot2 <keviny> We don't mark doc as error. it is stored in the error db
    slackbot2 <keviny> yeah, if we don't configure the replay, we actually is not calling the replay
    slackbot2 <keviny> so if we don't pass time or env.REPLAY it is not going to attempt to replay
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <hsiliev> And this replay is only going to be executed once on start?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <keviny> Yeah
    slackbot2 <keviny> It is basically to take care of stuff that might not processed succesfully when cf restart the app
    slackbot2 <hsiliev> I see. Thanks
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <dr.max> All, FYI, the following blog post on micro services using CF container networking. Might help inspire how to configure Abacus micro services when deploying as many services. Perhaps solving pert issues?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <hsiliev> !here|@here Anyone joining the meeting?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot2 <rajkiranrbala> Am sorry
    slackbot2 <rajkiranrbala> Have a meeting here
    slackbot2 <rajkiranrbala> I forgot to thank you @hsiliev
    slackbot2 <rajkiranrbala> I havent explored the Codacy fully yet
    slackbot2 <rajkiranrbala> But it looks really cool
    slackbot2 <hsiliev> Our status: Broker: working on a new integration tests module to allow interaction with cf and uaa clients added create & update of plans and mappings still having issues with abacus module dependencies Abacus: reported a bug for error detection. Thanks to @keviny for fixing it business errors not handled by cf-bridge on “missing” linux-container plan due to network issues. Proposed a fix in PR fine-
    slackbot2 BATCH_SIZE and REPLAY
    slackbot2 <hsiliev> @rajkiranrbala Yep. Might be quite useful
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <hsiliev> !here|@here Anyone joining http://appear.in|appear.in ?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <hsiliev> SAP team status: @stoyanr hardened the eval sandbox proposal to move the /healthcheck endpoint from eureka to webapp. WDYT?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <rajkiranrbala> I was working on customizing the breaker module so that different names can be passed instead of using the function names
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <hsiliev> @rajkiranrbala is this the breaker or the lock module?
    slackbot7 <rajkiranrbala> breaker
    slackbot7 <rajkiranrbala> i should update the lock module too
    abacus-irc-bot
    @abacus-irc-bot
    Guest47444 Hello everyone, I'm Ricky from Taiwan.
    Guest47444 I deployed Abacus on my CF. Trying to use Abacus. I write three plans (basic-object-storage-v2, object-rating-plan-v2 and object-pricing-basic-v2)
    Guest47444 The question is I dont know how to fill in resource_id and plan_id (when POST /v1/metering/collected/usage) I guess i missing some steps, but I already read all document on cf-abacus's github
    Guest47444 Also, I tried this API (POST|GET|PUT /v1/provisioning/resources/:resource_id/config) from slide cf-abacus-v0.7.0 But it didn't works. Although the latest API document is removed this API (https://github.com/cloudfoundry-incubator/cf-abacus/blob/master/doc/api.md) Please excuse my poor English. Many thanks. Ricky
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <hsiliev> Hey you need to add the plans to the mappings as well: https://github.com/cloudfoundry-incubator/cf-abacus/tree/master/lib/config/mappings/src/plans
    slackbot7 <hsiliev> then restart Abacus
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <hsiliev> @rajkiranrbala @keviny Can you please review cloudfoundry-incubator/cf-abacus#609 ? Do you mind moving healthcheck to webapp?
    slackbot7 <rajkiranrbala> I will review this today
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <hsiliev> And since you are using CF you'll need to rebuild and redeploy it. To make plan developer's life easier we started a new project: https://github.com/cloudfoundry-incubator/cf-abacus-broker Might want to use it (or at least parts of it). Still in development though
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <hsiliev> @rajkiranrbala Thanks. We need it to fix a security issue + add the ability to monitor uptime & health with tools like 24x7. Any feedback is appreciated
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <stoyanr> !here|@here We added a new PR to export some helper functions from abacus-usage-reporting, since we need to use them in another module, cloudfoundry-incubator/cf-abacus#615. Please review.
    abacus-irc-bot
    @abacus-irc-bot
    slackbot7 <dr.max> !here|@here, I talked to Chip yesterday and I think we should be able to push forward to moving Abacus to become an active project (that is out of incubation). I would like to discuss this, next release (finally) , and sync up this Friday. I am back from Beijing and our meeting won't be at 2a like it was when I was there so should be able to do it. Let me know if you can attend.