public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH manager v2 0/2] Ceph API update return schemas
Date: Mon, 16 Jan 2023 16:35:06 +0100	[thread overview]
Message-ID: <37c40bca-9ca5-086a-6392-4501b679be99@proxmox.com> (raw)
In-Reply-To: <20221223095915.3035857-1-a.lauterer@proxmox.com>

Am 23/12/2022 um 10:59 schrieb Aaron Lauterer:
> by adding more precise return definitions.
> 
> Patch 3/3 from the last version [0] is split into two patches.
> 
> The first handles a few small updates while the second one is a bit
> larger, adding more infos for the cluster/ceph/metadata return schemas.
> 
> 
> 
> [0] https://lists.proxmox.com/pipermail/pve-devel/2022-December/055268.html
> 
> Aaron Lauterer (2):
>   api: ceph: update return schemas
>   api: ceph: metadata: update return schema
> 
>  PVE/API2/Ceph.pm         |   7 +-
>  PVE/API2/Ceph/MON.pm     |  11 ++-
>  PVE/API2/Ceph/OSD.pm     |  10 +++
>  PVE/API2/Cluster/Ceph.pm | 171 ++++++++++++++++++++++++++++++++++++++-
>  4 files changed, 195 insertions(+), 4 deletions(-)
> 


applied both patches, thanks!




      parent reply	other threads:[~2023-01-16 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23  9:59 [pve-devel] " Aaron Lauterer
2022-12-23  9:59 ` [pve-devel] [PATCH manager v2 1/2] api: ceph: " Aaron Lauterer
2022-12-23  9:59 ` [pve-devel] [PATCH manager v2 2/2] api: ceph: metadata: update return schema Aaron Lauterer
2023-01-16 15:35 ` Thomas Lamprecht [this message]

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=37c40bca-9ca5-086a-6392-4501b679be99@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=a.lauterer@proxmox.com \
    --cc=pve-devel@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal