1. 13 Jul, 2016 1 commit
  2. 17 Jun, 2016 1 commit
    • David Johnson's avatar
      Several changes to openstack slothd gatherer. · 3b8bde10
      David Johnson authored
      Added the entire epoch as a period named '__EPOCH__'
      Stopped collecting cpu_util, network.(incoming,outgoing).bytes.rate
      meters for periods, and collect 'instance' meters per period (these just
      show how many instances were on each hypervisor during the period).
      Stopped collecting port.(delete,create,update) events -- far too many
      and they essentially relate n-to-1 with VMs (where n is usually 1, 1
      port per VM).
      Handle some weird inconsistencies in resource metadata (it seemed that
      for some VMs, some of the metadata wasn't set and thus we were not
      including said VMs in the primary VM info dict -- and this seemed to
      cause problems for the javascript graph stuff).
      Also, if a resource/meter value isn't associated with a hostname, use
      the 'UNKNOWN' hostname instead of None/null.  For whatever reason, this
      occurs with image.update now; funny.
      Get rid of the __FLATTEN__ stuff; that was just a lingering turd.
  3. 09 Jun, 2016 1 commit
  4. 01 Jun, 2016 2 commits
  5. 31 May, 2016 2 commits
  6. 26 May, 2016 1 commit
  7. 21 May, 2016 2 commits
    • David Johnson's avatar
      Reorg top level; add more resource info; add timestamp/runtime metadata. · acbf5767
      David Johnson authored
      Now the top-level keys are: 'META' (metadata about the collection run,
      so that whoever pulls this file back to boss doesn't have to check its
      ctime/mtime to know how stale the data is -- times in GMT); 'info',
      which has keys like 'images', 'vms', 'networks', 'subnets', 'ports',
      'routers', and a UUID->dict where the dict has a 'name' field (HRN),
      'status' (if the resource has status; all do); and 'deleted' (True
      or False).  Then the periods (which were previously top-level keys)
      are now keys in the 'periods' top-level dict.
    • David Johnson's avatar
      Add network in/out byte rate meters, and API meters. · f77aac78
      David Johnson authored
      Openstack reports in/out byte rates for each vm and for each device
      on those VMs, but I aggregate the per-device stats into per-VM in/out
      Currently, I'm reporting these API calls:
        * (network,subnet,port,router).(create,update,delete)
        * (image).(upload,update)
      API calls are reported from which "host" they were issued (I think);
      if there is no host info logged (like for images), the hostname is
  8. 20 May, 2016 1 commit
    • David Johnson's avatar
      A simple cpu_util statistics gatherer. · 5300a37f
      David Johnson authored
      This collects openstack cpu_util stats, grouped by hypervisor, and dumps
      them into a JSON file.  The JSON file will be written into
      /root/setup/cloudlab-openstack-stats.json . Currently it gets written
      every 2 minutes (however, openstack by default collects CPU stats only
      every 600 seconds...).
      The format is quite simple. It's a dict of time periods -- currrently
      the last 10 minutes, last hour, last 6 hours, last day, and last
      week. Each period is also a dict, currently with two keys: vm_info and
      cpu_util. vm_info contains a dict for each physical hypervisor node, and
      that dict contains a mapping of openstack VM uuid to VM
      shortname. cpu_util also contains a dict for each physical hypervisor
      node, and that dict contains two keys: a total of the average cpu utils
      for all the VMs on that node; and a "vms" dict containing the avg cpu
      util for each VM.