https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/IOTDM-4 iotdm <p>When content instances are added, its container should keep track of the current values of the entire set of cin's. When the quotea changes for the container, one or more cin's must be removed to reflect the new possibly smaller limits.</p> <p>This will enable filter criteria to work.</p> <p>Operating System: All<br/> Platform: All</p> IOTDM-4

Onem2m container: incorrect tracking of curr_byte_size, curr_nr_instances, and state_tag

Bug Resolved Done John Burns John Burns Thu, 21 May 2015 01:47:03 +0000 Sat, 30 May 2015 17:15:12 +0000 Sat, 30 May 2015 17:15:12 +0000 unspecified General 0 0 <p>The behavior when creating content instances is to <br/> 1) update the state tag of the parent container<br/> 2) use the value of the state tag in the parent as value for content instance state tag<br/> 3) ensure the content instance "fits" in the container ie it will not exceed the value<br/> of the parent container's max_byte_size<br/> 4) ensure max_instances of parent is not zero as then NO content instances will fit<br/> 5) if this new content instance causes the cumulative number of instances to be over<br/> the quota, then post process by removing the "oldest" instance. Also, remove "older"<br/> instances until the cumulative value of the byte_size of the container is under quota.</p> <p>The behavior when updating max_nr_instances (mni), or max_byte_size (mbs) of a container is to re-validate the container's quota and remove "older" instances until the quotas have been met. Obviously this will only happen if the new values for<br/> mni and/or mbs are reduced.</p> <p>Should now be fixed!</p> Development External issue ID 3315 External issue URL Rank 0|i01mk7: