Hi, Unlike the monitorization, the accounting is not done in intervals. All the actions on the VMs are stored, with the exact time of deployment, shutdown, migration, etc.
The accounting is done for each history entry, meaning that a VM with a migration will have 2 different accounting entries. To get the exact number of seconds a VM is active, use STIME (Start Time) and ETIME (End Time). This includes the disk files transfer times, but you can also get more detailed times: PSTIME PETIME: Prolog (files copied to the Host) start and end time RSTIME RETIME: Running start and end time ESTIME EETIME: Epilog (files copied back to the datastores) start and end time See the accounting reference here [1] I'm afraid I can't answer the networking questions, that is implemented using wizardry as far as I know. Regards [1] http://opennebula.org/documentation:rel3.6:accounting -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula<http://twitter.com/opennebula><[email protected]> On Mon, Oct 8, 2012 at 9:26 AM, Gandalf Corvotempesta < [email protected]> wrote: > Let's assume a standard configuration with 2 networks: public and internal. > - Is possibile to configure multiple filtering types on the same cloud > and on the same virtual instance? > (ebtable for public, vlan/openvswitch for the internal) > > I'm asking this because I would like to avoid a public vlan for each > customers on the public side (this will need a router reconfiguration > every time, to add the proper gateway on the same broadcast domain of > customer in each vlan) > > - Is possibile, for a customer, to create a sort of PVLAN where a part > of its internal network will be isolated from other virtual machines > (same customer and same vlan). For example, let's assume that > customer1 has 5 VPS: vps1, vps2...vps5. > VPS1 should communicate only with VPS4 in a sort of custom vlan. I > have a VLAN, on private side, for each customers and I would like to > give customers the capability to create some communication groups. > > - Accounting: on which frequency accounting data are saved on DB? This > is much important for us, as we will use this to invoice customers. > Will be possibile to touch the real number of seconds that an instance > was ON and the real number of seconds that an instance was paused but > with data still present on the node (no cpu/ram utilization but only > disk utilization) > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
