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
    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.
    abacus-irc-bot
    @abacus-irc-bot
    slackbot5 <rajkiranrbala> @dr.max @hsiliev Kevin and I have been busy and we were not able to spend time on the Abacus project for the last 3 weeks
    slackbot5 <rajkiranrbala> Sorry that we didn’t update you guys earlier.
    abacus-irc-bot
    @abacus-irc-bot
    slackbot5 <hsiliev> @rajkiranrbala Are you joining zoom today?
    slackbot5 <rajkiranrbala> I am on an other call
    slackbot5 <rajkiranrbala> At work. So I will not be able to join.
    slackbot5 <rajkiranrbala> Sorry
    slackbot5 <hsiliev> Ok. Let’s then post here in Slack
    abacus-irc-bot
    @abacus-irc-bot
    slackbot5 <hsiliev> !here|@here This week the team in Sofia was busy with: eval with timeout hangs on node 6 and node 7 (vm & vm2), but so far seems working on node 8. Disabled timeout by default npm 5 breaks Abacus on CF and so does node 8. Disabled use of npm 5 until we adapt to node 8/npm 5 combo as it will be LTS release * we started looking at providing shrinkwrap by default for Abacus to have reproducible build out of the box
    slackbot5 <hsiliev> We want to disable the use of API endpoint to fetch UAA coordinates. This should allow us to use oauth module for both CF and non-CF OAuth servers, plus should reduce the number of roundtrips. If you have any objections please comment on cloudfoundry-incubator/cf-abacus#639
    abacus-irc-bot
    @abacus-irc-bot
    slackbot5 1.0
    slackbot5 <hsiliev> @dr.max !here|@here We did “risk analysis” and “cloud qualities” workshops and identified as top prio items, that we need to improve the availability check (and we are already working on healthcheck aggregator) ability to do blue-green (or red-black) update * scalability The update & scalability issues seems to us connected to the fact that we have app-level partitioning, so I would propose to meet on th
    slackbot5 <hsiliev> Having said that… I don’t think we should go for 1.0 before either fixing or at least building a plan on how to approach the issues we already faced.
    abacus-irc-bot
    @abacus-irc-bot
    slackbot5 <hsiliev> !here|@here One more thing. We're facing problems with reporting. It cannot handle orgs with more than 2000 consumers (restarted/restaged apps basically). Any idea if this is only our installation or a general problem?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot5 <hsiliev> !here|@here: Can you please have a look at PR cloudfoundry-incubator/cf-abacus#652 We intend to fix the module dependencies. This perhaps is just the first step towards reproducible build
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <keviny> @dr.max Raj is on vacation this week and next week :S
    slackbot6 <dr.max> Ok, thx @keviny, about week after next?
    slackbot6 <keviny> We should be available by then
    abacus-irc-bot
    @abacus-irc-bot
    slackbot5 <dr.max> Cool thx @keviny can we book July 12th @ 11a?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot5 <keviny> I'll be free July 12th. Not sure about Raj though. Will get back to you once I know his schedule
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <dr.max> Since we are in the cusp of a very long weekend here in :flag-us: let's just do status here
    slackbot6 <dr.max> For me two things to highlight: 1. Various acceptance 2. I got a proposal from @hsliev for two commiters from his team (one a replacement As previous left SAP). I am doing reviewing and might run a vote later today unless I have questions
    slackbot6 <dr.max> Please chime in when you have a minute and send questions to me about ^^^
    slackbot6 <dr.max> Finally, IBM team looking forward to chatting on July 12th @ 11a. Can someone schedule the normal room we've used in the past in Foster City. Thx
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <hsiliev> !here|@here Team was busy fixing: 1. negative usage caused by bridge due to a) restart using stop&start events with the same timeout, b) events reported with seconds accuracy by CC, therefore we might get events with same timestamp 2. reporting timeout due to a) reporting killed since heartbeat & healthcheck fail b) request timeout. Both are caused by event loop occupied by summary/charge for > 3000 consumers
    slackbot6 <hsiliev> Both bugs imho are prerequisites for 1.0 release
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <dr.max> Hi, <here>, remember our call at 10a PDT today. Just joined by clicking on this zoom URL: https://zoom.us/j/788691850
    slackbot6 <dr.max> See you soon. Cheers
    abacus-irc-bot
    @abacus-irc-bot
    chihyi88 Hello, I am new to Abacus, I am trying time-based example, and has a question about "failed to send a measuring usage to abacus",
    chihyi88 For example, I shall send usage # 1, usage # 2, usage #3 to abacus, but for some reason, I failed to send usage #2, If it is a discrete type, I only lost usage #2
    chihyi88 But if it is a time-based, the charge at report would go crazy. My question is, for this problem, is there a way that I can recovery from this, and avoid the charge go crazy ?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <hsiliev> You can submit usage #2 till the end of the month (+slack window) and get the things right.
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <david.wu> Thanks for reply, got it, May I ask, in the design of Abacus, if I submit usage # 2 today, and query the usage report right after. Would I get correct charge immediately? Or I will need to wait until end of month to get the right charge.
    slackbot6 <hsiliev> You need to wait a bit for the doc to go through the pipeline and end up processed in the final database. This usually takes up to 2 minutes