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
    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
    slackbot6 <hsiliev> Then the doc would be accumulated/aggregated right away
    slackbot6 <david.wu> Got it. Thank you very much.
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <dr.max> Hi, <here>, remember our call at 10a PDT today. I have a small conflict, would it be possible to delay 30 mins? Sorry about the late notice. Please chime here. If not possible let's do status/update here and next week we can do live since I'll be at Foster City. Thx!!
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <dr.max> I'll assume we do status here. My status is twofold: 1. Doing some acceptance and clean up and adding the new committers from SAP 2. Using abacus as test for new cf-Extensions project so you will see a few commits from me adding metadata to repo. I plan to discuss this at the cf-Extensions PMC call Monday 7/31 if you can join
    slackbot6 <dr.max> Let me know if you are waiting on me for anything. For the IBM folks I am looking forward to chatting in person in foster city. However, don't have invite. Can someone send. We agreed Th or Friday 11a
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <rajkiranrbala> I haven’t finished updating the document yet. I might do over the weekend.
    abacus-irc-bot
    @abacus-irc-bot
    slackbot6 <hsiliev> Status update from the team: doing some profiling of reporting. Seems most of the time is spent in vm/vm2 sandbox. We applied caching and managed to reduce the time for generating a report from 2:40 minutes to 0:25 seconds. started productizing our internal Service Bridge MVP prepared a demo recording for Abacus Broker. Should be available next week hidden in youtube. Will send a link to the team for comments g
    slackbot6 describing different aspects of Abacus for Resource Providers
    abacus-irc-bot
    @abacus-irc-bot
    slackbot1 <dr.max> <here> I assume we are all back and can update at top of the hour?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot1 <dr.max> https://zoom.us/j/788691850
    slackbot1 <dr.max> <here> anyone else joining? I am on
    abacus-irc-bot
    @abacus-irc-bot
    slackbot1 <hsiliev> !here|@here I'm on vacation the whole month. Sorry for the late notice.
    slackbot1 <hsiliev> Not sure the plan really has previous and current. @keviny Is this normal in your pov?
    abacus-irc-bot
    @abacus-irc-bot
    slackbot1 <keviny> No, with 10 and 10 it should be 20. Can you replicate it @carrolp? clean the db and send the same two records.
    slackbot1 <hsiliev> It may happen if we have retries after the collector
    slackbot1 <hsiliev> Actually after the meter
    abacus-irc-bot
    @abacus-irc-bot
    slackbot1 <keviny> The only way this happen is if it succeeded posting the accumulated doc, but failed at the duplicate doc. It would retries and decides it is not a duplicate, and accumulate it again.
    slackbot1 <carrolp> retrying now....