ngcp-panel

Commit Graph

Author	SHA1	Message	Date
Rene Krenn	3b3cab1616	MT#16045 notopup expiry for balance intervals output including "timely" topup periods. +for /api/balanceintervals +and for panel UI, "Contract Balance" contract details section reworked api_dump.pl was simplified accordingly. Change-Id: Ib0c4942b1db059b4fe8ee3343838f516662ca166 (cherry picked from commit `fa2c02ee5f`)	10 years ago
Rene Krenn	cc4ee33e74	MT#16109 update "prepaid" pref correctly Change-Id: I6285db0776a87e4537961fb8a79430d093016b45 (cherry picked from commit `59ec368233`)	10 years ago
Rene Krenn	0cc54ba8c5	MT#15759 fix contract balance catchup DST problem +basically, the fix means to set billing.contract_balances.start billing.contract_balances.end billing.contracts.create_timestamp billing.contracts.modify_timestamp to the 'local' timezone. +test cases added Change-Id: I203f8fc93df2b53c1cfe89bb1a90cdf6388e20b3 (cherry picked from commit `0009520a84`)	10 years ago
Rene Krenn	609eeb68ad	MT#15399 allow editing profiles, networks, packages Change-Id: Iaa989ee18d10a3ea7e871ae99d78d6a2e1e9d40a (cherry picked from commit `8545089145`)	10 years ago
Rene Krenn	7f7e3332d1	MT#15477 topup log any attempt of a top-up request should be logged. +create top-up log records for api in order to record failed top-up requests as well, the somewhat tricky thing is to have two separate transactions here +propery casting of topup request json field values to numbers etc., so the transaction for creating the log entry cannot fail and e.g. requests with subscriber_id='blah' are recorded correctly +new "request_token" parameter for /api/topupvoucher and /api/topupcash, to identify and filter for particular requests. +topup log api resource +topup log api tests +fix to correctly reject used vouchers +topup log panel UI +fix for balanceintervals.t threaded tests Change-Id: I86eb845f6173803705b12cc7e5cdbac9a3153a0a	10 years ago
Rene Krenn	4272b25eee	MT#15477 balance intervals UI Change-Id: Ia6abd434870370e08fc7b136e198cbd6d57def2e	10 years ago
Rene Krenn	8494b5a91f	MT#14255 consider balance discard with infinite-end intervals +refactoring recent failing api-balanceintervals.t test to need only two concurrent transactions (instead of three, see https://bugtracker.sipwise.com/view.php?id=15277 Change-Id: I4902e616c3adfae81676194fa5e2b99e4b516ed1	10 years ago
Rene Krenn	33e5f4e71f	MT#14255 initial balance_intervals catchup when starting at 1st of month Change-Id: I9f22ffc112386da1bdac5e3fedb5b69e4a09fcfa	10 years ago
Rene Krenn	25f54603fb	MT#14255 notopup_expiry calculation only when required Change-Id: I79acf1acea6174e4d9f72fccfa01ad9196833fd4	10 years ago
Rene Krenn	07c9d1955d	MT#14255 add cash_balance underrun logic in short: whenever the contract_balances "cash_balance" is about to decrease, it might drop below thresholds defined by a contract's profile package. in that case, subscribers are to be locked and/or underrun billing profile sets are to be applied. this commit also contains some minor fixes: +when creating/editing profile packages, all billing profiles of initial, topup, underrun sets must show the same interval_free_cash and interval_free_time values. there was also a problem with adding profile sets to packages that use profile with prepaid = 1 (see ticket 14301) +when editing packages using the panel UI, the validation was not properly invoked (!) +the frequency of topups has to be limited to 1 per second. +updating the "lock" subscriber prior to editing or viewing it in the panel UI was added. +topup cash and topup voucher panel UI added +when aquiring multiple contract row locks at once, no joined tables are used any mure. the number of row locks is therefore minimal now (see ticket 14903) +rework of updating prepaid subscriber preference Change-Id: Ideb0fec2404ca10b3ac5d8735f53620d0c3a24ed	10 years ago
Rene Krenn	c7b3d74a21	MT#14317 passing now() to interval catchup and resize formerly, the contract_balance catchup (and resize) procedures used contracts.modified_timestamp, whose value was intended to be set explicitly upon update operations. it turns out that mysql ON UPDATE current_timestamp columns effectively ignore the explicit timestamp value, unless it exactly matches the old timestamp value. while this is not an issue for the logic in production usage, this seems to be the reason why the api-balance_intervals.t test fails occassionally with its time-warp cases. Change-Id: I504dd98548b88c99079e071598806d884c4422eb	10 years ago
Rene Krenn	ff75e75138	MT#14317 add debug info of panel interval catchups Change-Id: I1d37ec624c6642f54187ba463cf1121df4eb19a4	10 years ago
Rene Krenn	bef06dce91	MT#14301 deleting prof packages instead of terminating +profile package details view to overlook associations +voucher count is properly checked before deleting a package +package_id filters for /api/customers and /api/vouchers +Fake::Time replaced by Time::Warp for balance_interval tests +cleanup Change-Id: Idc34220a9d29c115453eeee2907e70a71cf9f0cc	10 years ago
Rene Krenn	ca908406a1	MT#13903 enable applying profile package Change-Id: I74b57b80599575e9685e01924b234c8da6c2fe49	10 years ago
Rene Krenn	f3b711a050	MT#13903 disable applying profile package This is a patcht introducing a variable to disable setting profile_package_id's in in the contracts table. The code should therefore behave as before, as long rate-o-mat and libswrate are ready. Not once set to 1 and contract balances are written to a database once, disabling this constant will mess up contract_balances! Change-Id: I080460395627202f3f5a386022de643577f4f3c2	10 years ago
Rene Krenn	d54bd5d360	MT#13903 "topup_interval" start mode impl The prior "topup" start mode for balance intervals (contract_balances) creates intervals for each top-up using a voucher, resulting in dynamic length. This new "topup_interval" start mode will just align the first balance interval upon the topup. Subsequent intervals use the constant interval unit+count specified in the profile package. Melita user story is completely covered now. Change-Id: I0a8b8d73a7fbf054d0aa8b2b1e73a54609fdeee0	10 years ago
Rene Krenn	bd9f67040d	MT#13903 topupvoucher and topupcash +applying profile package and billing mappings +testcase in api-balanceintervals.t +caveats: to meet melita's user story, an additional 'topup_interval' interval start mode will be required. the currently implemented 'topup' start mode restarts intervals upon every topup and therefore does not provide constantinterval lengths. Change-Id: I0a4898783c023749994e94e6909833a42debe259	10 years ago
Rene Krenn	c378681a24	MT#13903 balance interval catchup and resize WIP + synchronized contract balance catchup + balance interval resizing upon profile package transitions + dynamic interval length, interval start, carry-over propagation, .. + end-of-month 'preserve' mode correction for strictly aligned month intervals for start_mode=customer "create" timestamp + new api/balanceintervals resource to inspect contracts' balance interval histories + updated affected panel UI controllers + test case with time warps using Time::Fake caveats: - creating an invoice for a given 'period' (month) has to be refactored to select a disitnct balance interval. right now it takes the last interval in the month specified. - generate_invoice.pl is broken and needs a major refactoring Change-Id: I7bb54a83b76e510b1baa573a986d05400a7fec1e	10 years ago
Rene Krenn	2537819f0d	MT#12643 billing networks and multi bill prof WIP -properly validate billing mapping intervals -api/contracts and api/customers complete +the problem with updating the "prepaid" preference remains at the moment +billing_mappings field contains future (editable) mappings only, the full schedule is given in a separate field +hal-links to all occurring billing profiles and networks -extended tests: api-customer.t and api-contract.t -api-billingnetworks.t test -billing networks panel controller +search by enclosed IP address -panel UIs for billing networks, customers, contracts +past billing mapping intervals that cannot be edited are displayed by a seperate hfh "block" part of the billing_profiles repeatable -profile packages api, UI +terminating billing profiles (MT#8645) will be broken +fixed now: profile cannot be terminated unless there are: -zero non-terminated customers, whose mappings contain the profile with future or open end -zero profile packages, that link to the profile in either one of their initial-, underrun- or topup profile sets +panel edit should work, termination wip +topup_profiles w/o amounts +contracts/customers API profile_package_id field: +apply the package's initial profiles +api/customer and api/contract profile definition modes (id/profiles/package) +api OK, api-customer.t tests +customer and contract panel UI with selector to specify actual billing mapping, schedule or profile package (same as api) +terminate logic harmonized: profiles, networks, packages +api tests updated +prepare for merging: cleanup, enable tests Change-Id: I6c0dec72f490b5731fc673cd393d6aeb08dd8143	10 years ago

19 Commits (3b3cab16161175c4ab07dfce55db19810a01c250)