all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexey Melezhik via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Alexey Melezhik <melezhik@gmail.com>
Subject: [pve-devel] Contribution into QA automation for VE
Date: Tue, 7 Oct 2025 13:21:34 +0300	[thread overview]
Message-ID: <mailman.748.1759912527.390.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 5423 bytes --]

From: Alexey Melezhik <melezhik@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: Contribution into QA automation for VE
Date: Tue, 7 Oct 2025 13:21:34 +0300
Message-ID: <CAL7UUk9et-uwVHN8Bd5A9=CThSMc2EPK3vb8qpdSvU=Lv_tzJw@mail.gmail.com>

Hi! I am open source enthusiast and author of some open source automation
tools and frameworks. I am looking for opportunity to contribute into VE QA
automation , possible test scenarios could be :

- bootstrap kvm instances and test that some  Linux distribution ( Debian,
Ubuntu , etc ) work correctly ( automation tests for  packages , services
etc )
- bootstrap kvm instances with specific Linux kernels
- bootstrap kvm instances with specific file systems, storages
- bootstrap kvm instances with specific network settings

Etc

These are just examples what I can do


If provide some contacts I will be happy to discuss


Alexey

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

                 reply	other threads:[~2025-10-08  8:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mailman.748.1759912527.390.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=melezhik@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal