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
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-bridgeon “missing” linux-container plan due to network issues. Proposed a fix in PR fine-
slackbot2<hsiliev> @rajkiranrbala Yep. Might be quite useful
slackbot7<rajkiranrbala> i should update the lock module too
Guest47444I 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)
Guest47444The question is I dont know how to fill in
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
Guest47444Also, 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
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
slackbot7<rajkiranrbala> I will review this today
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
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.
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.
slackbot5<rajkiranrbala> Sorry that we didn’t update you guys earlier.
slackbot5<rajkiranrbala> I am on an other call
slackbot5<rajkiranrbala> At work. So I will not be able to join.
slackbot5<hsiliev> Ok. Let’s then post here in Slack
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
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.
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?
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
slackbot6<dr.max> Ok, thx @keviny, about week after next?
slackbot6<keviny> We should be available by then