Skip to content
Snippets Groups Projects
Commit 4f78b17d authored by Dave Pigott's avatar Dave Pigott
Browse files

Upoad first code to new repo

parent 1b3f8f80
No related branches found
No related tags found
1 merge request!2Upoad first code to new repo
Hide whitespace changes
Inline Side-by-side
README.md
+ 4
− 87
View file @ 4f78b17d
# Lava Reports
Tools to generate reports of various sorts on a LAVA instance and it's front end CIs
## Available tools
## Getting started
Currently:
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://gitlab.collabora.com/lava/lava-reports.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.collabora.com/lava/lava-reports/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
job_start_stats - generate a report on a per device-type basis, with analysis of the average times taken from submission to starting execution. It also provides information on the longest wait time, standard distribution, submitter and job priority.
job_start_stats 0 → 100755
+ 136
− 0
View file @ 4f78b17d
#!/usr/bin/env python3
# Copyright 2023 Collabora Litd
# Author: Dave Pigott <dave.pigott@collabora.com>
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
# MA 02110-1301, USA.
#
# Generate a report on how long jobs are being queued
import argparse
import json
import logging
import os
import requests
import sys
from datetime import datetime, timedelta
from email.message import EmailMessage
from netrc import netrc
from smtplib import SMTP
from urllib import parse
from urllib.parse import urlsplit
class NullAuth(requests.auth.AuthBase):
def __call__(self, r):
return r
def chop_ms(delta):
return delta - timedelta(microseconds=delta.microseconds)
def main():
parser = argparse.ArgumentParser(description="Report on device usage in a given instance", add_help=False)
parser.add_argument('--help', action='help', help='Show this help message and exit')
parser.add_argument("-d", "--days", default=7, type=int, help="Number of days to report on (default=7)")
parser.add_argument("-h", "--host", required=True, help="LAVA host url")
parser.add_argument("-l", "--loglevel", default="INFO", choices=["DEBUG", "INFO", "WARNING", "ERROR", "CRITICAL"], help="Log level")
parser.add_argument("-t", "--token", default=os.environ.get("LAVA_TOKEN"), help="LAVA access token")
parser.add_argument("-u", "--username", default="localadmin", help="LAVA username associated with the token")
parser.add_argument("-v", "--version", default="v0.2", help="LAVA API version (default v0.2)")
args = parser.parse_args()
logging.basicConfig(level=logging.getLevelName(args.loglevel))
host_parts = parse.urlparse(args.host)
host = "%s://%s" % (host_parts.scheme, host_parts.netloc)
if args.token == None or args.username == None:
try:
netrcauth = netrc()
username, _, token = netrcauth.authenticators(host_parts.netloc)
except FileNotFoundError:
logging.warning(".netrc file not available")
sys.exit(1)
except TypeError:
logging.warning("No token available for this instance in .netrc")
sys.exit(1)
except:
logging.warning("Unknown error parssing .netrc")
sys.exit(1)
else:
username = args.username
token = args.token
auth_dict = {"Authorization": "Token %s" % token}
api_version = args.version
devicetype_url = parse.urljoin(host, "api/v0.2/devicetypes/?display=true&ordering=name")
logging.debug("Requesting %s" % devicetype_url)
device_types = requests.get(devicetype_url, headers=auth_dict, auth=NullAuth())
# start_time = datetime.utcnow() - timedelta(days=args.days)
start_time = datetime.utcnow() - timedelta(hours=args.days)
jobs_url = parse.urljoin(host, "api/%s/jobs/?health_check=false&submit_time__gt=%s&ordering=submit_time" % (api_version, start_time))
results = {}
total = 0
while True:
jobs_data = requests.get(jobs_url, headers=auth_dict, auth=NullAuth())
if jobs_data.status_code == 200:
jobs = jobs_data.json()
for job in jobs["results"]:
start_time = job["start_time"]
if start_time == None:
continue
start_time = datetime.fromisoformat(start_time.replace("Z","+00:00"))
submit_time = datetime.fromisoformat(job["submit_time"].replace("Z", "+00:00"))
wait_time = start_time - submit_time
try:
results[job["requested_device_type"]]["time_total"] += wait_time
results[job["requested_device_type"]]["job_count"] += 1
if results[job["requested_device_type"]]["max_time"] < wait_time:
results[job["requested_device_type"]]["max_time"] = wait_time
results[job["requested_device_type"]]["bell_data"].append(int(wait_time.total_seconds()/60))
except KeyError:
results[job["requested_device_type"]] = {}
results[job["requested_device_type"]]["time_total"] = wait_time
results[job["requested_device_type"]]["job_count"] = 1
results[job["requested_device_type"]]["max_time"] = wait_time
results[job["requested_device_type"]]["bell_data"] = [int(wait_time.total_seconds()/60)]
total += 1
print("%s\r" % total, end='')
jobs_url = jobs["next"]
if jobs_url == None:
break
for i in results:
print()
print(i, end='')
print("\tTotal jobs: %s" % results[i]["job_count"])
print("\tAverage: %s" % str(chop_ms(results[i]["time_total"]/results[i]["job_count"])), end='')
print("\tMax: %s" % str(chop_ms(results[i]["max_time"])))
print(results[i]["bell_data"])
if __name__ == '__main__':
main()
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment