HCP Chargeback Collector Documentation

Transcription

1 HCP Chargeback Collector Documentation Release Thorsten Simons Jun 27, 2017

2 Contents 1 Setup Pre-requisites Dependencies Installation Usage Arguments: Configuration The configuration file explained Example configuration file after first run Archive Structure Output file content overlap Charts Exemplary charts Release History 21 7 License / Trademarks The MIT License (MIT) Trademarks and Copyrights of used material About 24 i

3 Hitachi Content Platform (HCP) allows to generate chargeback reports from either the HCP System Management Console or through the Management API (MAPI). A chargeback report contains current and historical storage usage statistics for HCP tenants and their namespaces. For each chargeback report, you specify the start and end dates of the report period, which is the time period that s covered by the report, and select the reporting interval, which determines whether HCP generates hourly, daily, or total storage usage statistics for the specified report period. Whereas the System Management Console allows for chargeback reports to be generated for the past 30 days, this tool can go back up to 180 day, and it stores the reports locally to allow for investigation over the HCPs lifetime, given that the reports have been collected on a regular basis. Chargeback reports are a good source of information for system analysis, enabling you to adjust storage and bandwidth allocations based on usage patterns. These reports can also serve as input to billing systems that need to determine charges for capacity and bandwidth usage at the tenant or namespace level. Chargeback reports cover only HCP tenants and their namespaces. They do not include the default tenant or its namespace. Contents 1

4 CHAPTER 1 Setup Pre-requisites HCP running at least version 5.0 A system-level admin account having at least the Monitor role MAPI enabled at system-level and within each Tenant for which chargeback reports are to be collected If the chargeback reports are to be archived to an HCP Namespace: a data access user having at least write access to that Namespace Dependencies You need to have at least Python 3.4 installed to run hcpcbc. It depends on the hcpsdk 1 to access HCP and XlsxWriter 2 for chart generation. Tip: It s suggested to use a virtual environment to fence the dependency from your primary Python environment. Installation Make sure you have Python 3.4 (or better) installed In case it s not installed, get it here 3. There are two ways to install hcpcbc: 1. system-wide

5 -or- Install hcpcbc by running: $ pip install hcpcbc Get the source from gitlab.com 4 either by downloading the source archive, or by cloning the repository: $ git clone Install locally, including the dependency: $ python setup.py install 2. in a virtual environment WINDOWS Create a fresh virtual environment: C:\>\Python35\Tools\scripts\pyvenv.py c:\temp\_venv_hcpcbc Activate the virtual environment: C:\>cd temp C:\temp>\temp\_venv_hcpcbc\Scripts\activate.bat (_venv_hcpcbc) C:\temp> Install hcpcbc: (_venv_hcpcbc) C:\Temp>pip install hcpcbc Collecting hcpcbc Downloading hcpcbc tar.gz Collecting hcpsdk>=0.9.4.post0 (from hcpcbc==2.1.0) Downloading hcpsdk post1.tar.gz Collecting XlsxWriter>=0.7.7 (from hcpcbc==2.1.0) Downloading XlsxWriter py2.py3-none-any.whl (133kB) Collecting dnspython3== (from hcpsdk>=0.9.4.post0->hcpcbc) Downloading dnspython zip (226kB) Installing collected packages: dnspython3, hcpsdk, hcpcbc Running setup.py install for dnspython3 Running setup.py install for hcpsdk Running setup.py install for hcpcbc Successfully installed XlsxWriter dnspython \ hcpcbc hcpsdk post1 Now you can run hcpcbc as long as you have the virtual environment activated: (_venv_hcpcbc) C:\temp>hcpcbc A configuration file is not available. Do you want me to create a template for you (y/n)? y Creation of template config file "hcpcbc_config.ini" was successfull You need to edit it to fit your needs! Linux Create a fresh virtual environment: Installation 3

6 $ pyvenv _venv_hcpcbc Activate the virtual environment: $ source _venv_hcpcbc/bin/activate Install hcpcbc: (_venv_hcpcbc) $ pip install hcpcbc Collecting hcpcbc Downloading hcpcbc tar.gz Collecting hcpsdk>=0.9.4.post0 (from hcpcbc==2.1.0) Downloading hcpsdk post1.tar.gz Collecting XlsxWriter>=0.7.7 (from hcpcbc==2.1.0) Downloading XlsxWriter py2.py3-none-any.whl (133kB) Collecting dnspython3== (from hcpsdk>=0.9.4.post0->hcpcbc) Downloading dnspython zip (226kB) Installing collected packages: dnspython3, hcpsdk, hcpcbc Running setup.py install for dnspython3 Running setup.py install for hcpsdk Running setup.py install for hcpcbc Successfully installed XlsxWriter dnspython \ hcpcbc hcpsdk post1 Now you can run hcpcbc as long as you have the virtual environment activated: (_venv_hcpcbc) $ hcpcbc A configuration file is not available. Do you want me to create a template for you (y/n)? y Creation of template config file "hcpcbc_config.json" was successfull You need to edit it to fit your needs! 1.3. Installation 4

7 CHAPTER 2 Usage HCP Chargeback Collector is a command line tool. $ hcpcbc --help usage: hcpcbc [-h] [--version] [-i config.json] [-u] [-c] [--pastdays PASTDAYS] hcpcbc downloads the chargeback reports from one or multiple HCP systems, as setup in the config file. It keeps a timestamp of the last successfull download and excludes everything prior to the last time hcpcbc has been run. optional arguments: -h, --help show this help message and exit --version show program's version number and exit -i config.json path/name of the file containing the configuration (defaults to the current directory) -u update the Tenant list(s) and stop afterwards -c create charts from existing reports, only (do nothing else) --pastdays PASTDAYS start collection x days in the past Arguments: -i configfile.json is relevant if your config file is not hcpcbc_config.json in the current directory. -u allows to update the Tenant list(s) only, without collecting any reports. -c create charts from the already available reports, not updating the Tenant list(s) or collecting new reports. --pastdays PASTDAYS start collection PASTDAYS in the past - once for each Tenant that was not collected before. Tip: If you don t have a configuration file yet, just run the tool without arguments; it will create a template config file for you: 5

8 $ hcpcbc A configuration file is not available. Do you want me to create a template for you (y/n)? y Creation of template config file "hcpcbc_config.json" was successfull You need to edit it to fit your needs! Make sure you edit the file to fit your needs! (see Configuration for details) hcpcbc is made to run regularly. You might want to run it once a week or so, to build up a pool of report data for later investigation. A run s output: 1 01/06 21:32:06 [INFO ] started run (user "sm") 2 01/06 21:32:06 [INFO ] updating the Tenant list for "hcp72.archivas.com" 3 01/06 21:32:08 [INFO ] updating the Tenant list for "hcp73.archivas.com" 4 01/06 21:32:08 [WARNING ] Default Tenant found - no chargeback support 5 01/06 21:32:10 [INFO ] working on target "hcp72.archivas.com" (idx=0) 6 01/06 21:32:10 [INFO ] collecting from Tenant "m" 7 01/06 21:32:31 [INFO ] tranfering reports to local store 8 01/06 21:32:31 [INFO ] collecting from Tenant "s3" 9 01/06 21:32:37 [INFO ] tranfering reports to local store 10 01/06 21:32:37 [INFO ] collecting from Tenant "s3erlei" 11 01/06 21:32:49 [INFO ] tranfering reports to local store 12 01/06 21:32:49 [INFO ] collecting from Tenant "swifttest" 13 01/06 21:32:50 [INFO ] tranfering reports to local store 14 01/06 21:32:50 [INFO ] collecting from Tenant "testtenant" 15 01/06 21:32:50 [INFO ] --> unable to collect namespace details 16 01/06 21:32:53 [INFO ] tranfering reports to local store 17 01/06 21:32:53 [INFO ] collecting from Tenant "swifty" 18 01/06 21:32:59 [INFO ] tranfering reports to local store 19 01/06 21:32:59 [INFO ] collecting from Tenant "x" 20 01/06 21:32:59 [INFO ] --> unable to collect namespace details 21 01/06 21:32:59 [INFO ] tranfering reports to local store 22 01/06 21:32:59 [INFO ] working on target "hcp73.archivas.com" (idx=1) 23 01/06 21:32:59 [INFO ] collecting from Tenant "aw21" 24 01/06 21:33:03 [INFO ] tranfering reports to local store 25 01/06 21:33:03 [INFO ] collecting from Tenant "m" 26 01/06 21:33:11 [INFO ] tranfering reports to local store 27 01/06 21:33:11 [INFO ] collecting from Tenant "s3" 28 01/06 21:33:16 [INFO ] tranfering reports to local store 29 01/06 21:33:16 [INFO ] collecting from Tenant "swifttest" 30 01/06 21:33:32 [INFO ] tranfering reports to local store 31 01/06 21:33:32 [INFO ] collecting from Tenant "s3erlei" 32 01/06 21:33:39 [INFO ] tranfering reports to local store 33 01/06 21:33:39 [INFO ] creating charts for HCP "hcp72.archivas.com" 34 01/06 21:33:39 [INFO ] working on Tenant "m" 35 01/06 21:33:56 [INFO ] working on Tenant "s3" 36 01/06 21:34:02 [INFO ] working on Tenant "s3erlei" 37 01/06 21:34:16 [INFO ] working on Tenant "swifttest" 38 01/06 21:34:18 [INFO ] working on Tenant "testtenant" 39 01/06 21:34:18 [INFO ] working on Tenant "swifty" 40 01/06 21:34:28 [INFO ] working on Tenant "x" 41 01/06 21:34:29 [INFO ] working on Tenant comparison charts 42 01/06 21:34:52 [INFO ] creating charts for HCP "hcp73.archivas.com" 43 01/06 21:34:52 [INFO ] working on Tenant "aw21" 44 01/06 21:34:56 [INFO ] working on Tenant "m" 45 01/06 21:35:08 [INFO ] working on Tenant "s3" 2.1. Arguments: 6

9 46 01/06 21:35:15 [INFO ] working on Tenant "swifttest" 47 01/06 21:35:43 [INFO ] working on Tenant "s3erlei" 48 01/06 21:35:54 [INFO ] working on Tenant comparison charts 49 01/06 21:36:04 [INFO ] finished run (user "sm") A few things to notice: lines 2-3: line 4: as a first action, a list of existing Tenants is acquired from each configured HCP system the Default Tenant doesn t provide chargeback reports starting at line 5, line 15,20: collection for the first configured HCP system begins, Tenant by Tenant. if the HCP user account used by hcpcbc doesn t have access to the Tenant, Tenant summaries are collectable, only 2.1. Arguments: 7

10 CHAPTER 3 Configuration hcpcbc uses a JSON 5 file to read its configuration from. The loader does some basic consistency checks, but it s required to make sure that the configuration file strictly complies to the syntax rules for JSON files. It is highly suggested not to change the structure of the file. Warning: Even simple errors in the JSON file might trigger errors like this: Parsing the config file "hcpcbc_config.json" failed: hint: Expecting property name enclosed in double quotes: line 66 column 13 (char 2602) Luckily, the position given points fairly exact to where the error is - in this case, it s just a comma too much: 58 }, 59 "x": { 60 "0 enable collection": true, 61 "1 adminallowed": false, 62 "2 user": "", 63 "3 password": "", 64 "4 systemvisibledescription": "", 65 "9 last collected": " T20:36: " 66 }, 67 } A fresh configuration file configures access to the HCP system(s) using a system-level user, only. At the very beginning of each run, hcpcbc queries the HCP systems for a list of configured Tenants. At the end of a run, the configuration file is refreshed with this gained details. If there are Tenants where the user account used has no access to, a different (Tenant-level) user account can be configured for that specific Tenant by simply filling the provided (empty) fields with the users name and password. Warning: As the configuration file contains user credentials, make sure that it is stored in a secure location with propper permission settings, not to disclose it to nosy eyes! 5 8

11 The file must be write-able by the tool itself, as it uses it to remember state between its runs. The configuration file explained 1 { This is the template configuration file hcpcbc is able to create for convenience, if no configuration file is available. 2 "0 comment": [ 3 "This it the configuration file for **hcpcbc**. For a detailed", 4 "description visit * 5 ], Target section This section describes the HCP system(s) from which chargeback data is to be collected. Any number of HCP systems can be defined. The user needs to be a system-level user having the Monitor role. The folder is a sub-folder below the path(s) declared in the store sections. 6 "1 targets": [ 7 { 8 "0 comment": [ 9 "An HCP system to collect from. *User* needs to be a", 10 "system-level user that has the *Monitor* role enabled." 11 ], 12 "1 fqdn": "hcp72.archivas.com", 13 "2 user": "monitor", 14 "3 password": "monitor01", 15 "4 folder": "hcp72", 16 "9 tenants": {} 17 }, 18 { 19 "0 comment": [ 20 "An HCP system to collect from. *User* needs to be a", 21 "system-level user that has the *Monitor* role enabled." 22 ], 23 "1 fqdn": "hcp73.archivas.com", 24 "2 user": "monitor", 25 "3 password": "monitor01", 26 "4 folder": "hcp73", 27 "9 tenants": {} 28 } 29 ], Parameter section The periode sets the granularity of the collected data. A list of one, two or three values (out of hour, day, total ) may be given. collection limit declares how many days worth of data shall be gathered in a single run. If hcpcbc fails with timeout errors, lower the value from the default of 181 days down to some 3.1. The configuration file explained 9

12 ten days. Then run hcpcbc multiple times until the collection has reached the actual date. timeout defines the TCP connection timeout in seconds. 30 "2 parameters": { 31 "0 comment": [ 32 "*1 periode* defines the reports granularity,", 33 "*2 collection limit* defines for how many days collection", 34 "takes place, starting from the last collection time." 35 "*3 timeout* defines the tcp connection timeout" 36 ], 37 "1 periode": [ 38 "total", 39 "day", 40 "hour" 41 ], 42 "2 collection limit": 181, 43 "3 timeout": }, Stores section In this section, storage locations are defined for: temporary storage - this will be used to store reports during processing local storage - a local directory in which the collected reports will be stored compliant storage - an HCP Namespace to store the reports, if required with a retention periode set path - a full qualified path to the Namespace user - needs to have write access to the Namespace retention - see HCP manual Using a Namespace for valid retention patterns store raw - store the raw reports (beside the split-up reports for Tenant summary and Namespaces) 45 "3 stores": { 46 "1 temporary": { 47 "0 comment": [ 48 "The temporary directory in which the downloaded", 49 "reports are stored during processing." 50 ], 51 "1 tempdir": "./_hcpcbc.dir" 52 }, 53 "2 local": { 54 "0 comment": [ 55 "The directory in which processed reports are", 56 "stored locally." 57 ], 58 "1 enable": true, 59 "2 path": "./_hcpcbc.dir", 60 "9 store raw": true 61 }, 62 "3 compliant": { 63 "0 comment": [ 64 "This is the HCP Namespace to which the processed reports", 65 "can be stored for long-term preservation" 66 ], 67 "1 enable": false, 3.1. The configuration file explained 10

13 68 "2 path": " 69 "3 user": "n", 70 "4 password": "n01", 71 "5 retention": "0", 72 "9 store raw": true 73 } 74 }, Charts section This section defines which charts shall be created, if at all. path can be the same as for local store; report and chart folder structure are made to allow overlap without interference. linear and log enable charts with linear and/or logarithmic scale. 75 "4 charts": { 76 "0 comment": [ 77 "Chart creation", 78 "*hourly charts* will use the hour reports to create charts", 79 "*daily charts* will do the same using the day reports." 80 ], 81 "1 enable": true, 82 "2 path": "./_hcpcbc.charts", 83 "3 hourly charts": true, 84 "6 daily charts": true, 85 "a linear": true, 86 "b log": true 87 }, Logging section This section defines how logging shall take place. 88 "9 logging": { 89 "0 comment": [ 90 "This defines how hcpcbc does logging." 91 ], 92 "1 log to stdout": true, 93 "2 log to file": false, 94 "3 logfile": "./_hcpcbc.dir/_hcpcbc.log", 95 "4 rotate MB": 10, 96 "5 backups": 9, 97 "6 debug": false 98 } 99 } Example configuration file after first run 1 { After a run, the configuration file is updated with the Tenants configured per HCP system. 2 "0 comment": [ 3 "This it the configuration file for **hcpcbc**. For a detailed", 4 "description visit * 5 ], 6 "1 targets": [ 7 { 8 "0 comment": [ 9 "An HCP system to collect from. *User* needs to be a", 3.2. Example configuration file after first run 11

14 10 "system-level user that has the *Monitor* role enabled." 11 ], 12 "1 fqdn": "hcp72.archivas.com", 13 "2 user": "monitor", 14 "3 password": "monitor01", 15 "4 folder": "hcp72", 16 "9 tenants": { Tenant section In this section, hcpcbc stores a list of all Tenants configured in HCP. enable collection - if set to false, the Tenant will not be collected. This is usefull if you either don t have access to the Tenant or you don t want to collect it as it s a never-accessed replica, for example. adminallowed - if true, system-level users has been granted access to Tenant management, so that no Tenant-level user is needed to access Namespace-level reports. user, password - not required if adminallowed = true; otherwise, if manually added, will allow to collect Namespace-level reports. systemvisibledescription - for convenience last collected - the timestamp of the last collection from the Tenant 17 "m": { 18 "0 enable collection": true, 19 "1 adminallowed": true, 20 "2 user": "", 21 "3 password": "", 22 "4 systemvisibledescription": "Der ueblicherweise als erstes erzeugte Tenant...", 23 "9 last collected": " T06:49: " 24 }, 25 "s3": { 26 "0 enable collection": true, 27 "1 adminallowed": true, 28 "2 user": "", 29 "3 password": "", 30 "4 systemvisibledescription": "", 31 "9 last collected": " T06:49: " 32 }, 33 "s3erlei": { 34 "0 enable collection": true, 35 "1 adminallowed": true, 36 "2 user": "", 37 "3 password": "", 38 "4 systemvisibledescription": "", 39 "9 last collected": " T06:48: " 40 }, 41 "swifttest": { 42 "0 enable collection": true, 43 "1 adminallowed": true, 44 "2 user": "", 45 "3 password": "", 46 "4 systemvisibledescription": "", 47 "9 last collected": " T06:48: " 48 }, 49 "swifty": { 50 "0 enable collection": true, 51 "1 adminallowed": true, 52 "2 user": "", 53 "3 password": "", 3.2. Example configuration file after first run 12

15 54 "4 systemvisibledescription": "", 55 "9 last collected": " T06:49: " 56 }, 57 "testtenant": { 58 "0 enable collection": true, 59 "1 adminallowed": false, 60 "2 user": "", 61 "3 password": "", 62 "4 systemvisibledescription": "", 63 "9 last collected": " T06:49: " 64 }, 65 "x": { 66 "0 enable collection": true, 67 "1 adminallowed": false, 68 "2 user": "", 69 "3 password": "", 70 "4 systemvisibledescription": "", 71 "9 last collected": " T06:49: " 72 } 73 } 74 }, 75 { 76 "0 comment": [ 77 "An HCP system to collect from. *User* needs to be a", 78 "system-level user that has the *Monitor* role enabled." 79 ], 80 "1 fqdn": "hcp73.archivas.com", 81 "2 user": "monitor", 82 "3 password": "monitor01", 83 "4 folder": "hcp73", 84 "9 tenants": { 85 "aw21": { 86 "0 enable collection": true, 87 "1 adminallowed": true, 88 "2 user": "", 89 "3 password": "", 90 "4 systemvisibledescription": "", 91 "9 last collected": " T06:49: " 92 }, 93 "m": { 94 "0 enable collection": true, 95 "1 adminallowed": true, 96 "2 user": "", 97 "3 password": "", 98 "4 systemvisibledescription": "Der ueblicherweise als erstes erzeugte Tenant...", 99 "9 last collected": " T06:50: " 100 }, 101 "s3": { 102 "0 enable collection": true, 103 "1 adminallowed": true, 104 "2 user": "", 105 "3 password": "", 106 "4 systemvisibledescription": "", 107 "9 last collected": " T06:49: " 108 }, 109 "s3erlei": { 110 "0 enable collection": true, 111 "1 adminallowed": true, 112 "2 user": "", 113 "3 password": "", 114 "4 systemvisibledescription": "", 115 "9 last collected": " T06:49: " 3.2. Example configuration file after first run 13

16 116 }, 117 "swifttest": { 118 "0 enable collection": true, 119 "1 adminallowed": true, 120 "2 user": "", 121 "3 password": "", 122 "4 systemvisibledescription": "", 123 "9 last collected": " T06:50: " 124 } 125 } 126 } 127 ], 128 "2 parameters": { 129 "0 comment": [ 130 "*1 periode* defines the reports granularity,", 131 "*2 collection limit* defines for how many days collection", 132 "takes place, starting from the last collection time.", 133 "*3 timeout* defines the tcp connection timeout" 134 ], 135 "1 periode": [ 136 "total", 137 "day", 138 "hour" 139 ], 140 "2 collection limit": 181, 141 "3 timeout": }, 143 "3 stores": { 144 "1 temporary": { 145 "0 comment": [ 146 "The temporary directory in which the downloaded", 147 "reports are stored during processing." 148 ], 149 "1 tempdir": "./_hcpcbc.dir" 150 }, 151 "2 local": { 152 "0 comment": [ 153 "The directory in which processed reports are", 154 "stored locally." 155 ], 156 "1 enable": true, 157 "2 path": "./_hcpcbc.dir", 158 "9 store raw": true 159 }, 160 "3 compliant": { 161 "0 comment": [ 162 "This is the HCP Namespace to which the processed reports", 163 "can be stored for long-term preservation" 164 ], 165 "1 enable": false, 166 "2 path": " 167 "3 user": "n", 168 "4 password": "n01", 169 "5 retention": "0", 170 "9 store raw": true 171 } 172 }, 173 "4 charts": { 174 "0 comment": [ 175 "Chart creation", 176 "*hourly charts* will use the hour reports to create charts", 177 "*daily charts* will do the same using the day reports." 178 ], 3.2. Example configuration file after first run 14

17 179 "1 enable": true, 180 "2 path": "./_hcpcbc.charts", 181 "3 hourly charts": true, 182 "6 daily charts": true, 183 "a linear": true, 184 "b log": true 185 }, 186 "9 logging": { 187 "0 comment": [ 188 "This defines how hcpcbc does logging." 189 ], 190 "1 log to stdout": true, 191 "2 log to file": false, 192 "3 logfile": "./_hcpcbc.dir/_hcpcbc.log", 193 "4 rotate MB": 10, 194 "5 backups": 9, 195 "6 debug": false 196 } 197 } 3.2. Example configuration file after first run 15

18 CHAPTER 4 Archive Structure The collected chargeback reports are stored in a way that makes it somewhat easy to process them later on. ['3 stores']['2 local' '3 compliant']['2 path']/ ['1 targets'][idx]['4 folder']/ <tenant>/ raw/ day/ hour/ total/ tenant/ day/ hour/ total/ <namespace>/ day/ hour/ total/ <namespace>/ day/ hour/ total/ Example: 16

19 Output file content overlap Subsequent reports will likely show some overlap. For example, you might find the time portion of the last record s endtime to be different from 23:59:59. The next report will then have a first record where the starttime s time portion is 00:00:00, overlapping with the later one. When processing the reports, you need to make sure to check for this overlap and skip all records not having a full hour (or full day) Output file content overlap 17

20 CHAPTER 5 Charts New in version As seen in the Configuration section, hcpcbc is able to create charts right after it downloaded new Chargeback reports. For convenience, these charts are provided as Excel workbooks. This is a bit a drawback, as tools like mathplotlib would be better suited (and faster, as well). Unfortunately, mathplotlib doesn t install well using pip, as it needs to be compiled locally under certain cicumstances. So the decision was made to stay with Excel workbooks. The output structure is quite close to the one used for the reports itself (in fact, they can overlay each other without interfering each other): ['4 charts']['2 path']/ ['1 targets'][idx]['4 folder']/ system/ charts/ day/ hour/ <tenant>/ charts/ day/ hour/ <tenant>/ charts/ day/ hour/ The system folder holds charts that compare the available Tenants against each other, whereas the tenant folder compare the Tenants own Namespaces. As of the time of writing this, charts cover the entire timeframe for which reports are available. Example: 18

21 Exemplary charts System-level charts 5.1. Exemplary charts 19

22 Tenant-level charts (not available in the PDF documentation - see the hcpcbc documentation: org) 5.1. Exemplary charts 20

23 CHAPTER 6 Release History Removed the dependency for Python now works with Python Re-factored the code to allow for binary creation using pyinstaller Fixed: A bug that caused the tool to fail while having no access to a Tenant Fixed: A bug that caused chart creation to fail in case at least one Tenant was disabled for report collection Another bug that cause the tool to fail if no report data is available at all Added: Ability to switch off Tenants from collection (config file) Ability to just update the Tenant list w/o collection (-u) Ability to generate charts without downloading reports (-c) Ability to start collection defineable days in the past - once for each Tenant that was not collected before (--pastdays) Documentation fixes Added: Chart creation 21

24 Fixed: Report file names (removed : s to make sure not to conflict with Windows rules) Changed: rebuilt from scratch to get rid of the sqlite3 database used in version 1.x now using the hcpsdk now storing the reports in a folder structure added possibility to store to HCP 22

25 CHAPTER 7 License / Trademarks The MIT License (MIT) Copyright (c) Thorsten Simons (sw@snomis.de) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software ), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARIS- ING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Trademarks and Copyrights of used material Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, Hitachi Content Platform, Hitachi Content Platform Anywhere and Hitachi Data Ingestor are registered trademarks of Hitachi Data Systems Corporation. All other trademarks, service marks, and company names in this document or web site are properties of their respective owners. The logo used in the documentation is based on the picture found at pixabay.com 6, where it is declared under CC0 Public Domain 7 license

26 CHAPTER 8 About About the Developer The developer serves for Hitachi Data Systems since 2007, with a main focus on Hitachi Content Platform and its family of related products. Being a presales consultant with HDS Germany for more than six years, he actually works for the HCP engineering department as an HCP Technologist for the EMEA region. Prior to HDS, he served for eight years as a presales manager for a major storage vendor in Germany. Before that, he worked for ten years as a software developer, system programmer, project manager and technical architect for a major German manufacturing company. In his spare time, he develops tools around HCP that make his own (and hopefully) others life easier. You can contact him per at sw@snomis.de 24