From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 771B17238B for ; Tue, 25 May 2021 08:11:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6BD8C28953 for ; Tue, 25 May 2021 08:11:45 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id D858528946 for ; Tue, 25 May 2021 08:11:44 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id B0E594212A; Tue, 25 May 2021 08:11:44 +0200 (CEST) Message-ID: Date: Tue, 25 May 2021 08:11:43 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Thunderbird/89.0 Content-Language: en-US To: Proxmox VE development discussion , wb References: <02c8e0ce3079939415c742edf16c0966@mwinf5d78.me-wanadoo.net> From: Thomas Lamprecht In-Reply-To: <02c8e0ce3079939415c742edf16c0966@mwinf5d78.me-wanadoo.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL -0.244 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years NICE_REPLY_A -0.001 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] =?utf-8?q?RE=C2=A0=3A_pve-devel_Digest=2C_Vol_132=2C?= =?utf-8?q?_Issue_53?= X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2021 06:11:45 -0000 On 24.05.21 23:45, wb wrote: > However, since I am starting on a new installation, I am surprised to g= et this kind of answer. > =C2=AB=C2=A0Your cluster fs is not working (pmxcfs). See you run on a b= roken installation.=C2=A0=C2=BB > Or=20 > =C2=AB=C2=A0You need a working PVE installation before doing any API ca= lls...=C2=A0=C2=BB >=20 > With the following command, I have the process up! >=20 > ps aux | grep pmxcfs >=20 running does not mean working... What's the output/status of: # systemctl status pve-cluster=20 # touch /etc/pve/foo # findmnt /etc/pve >=20 > I think I have enough knowledge about SAML and Perl to do it, however, = the support of a dev would be ideal at least on the lock part. >=20 Nobody questioned that.. > I'm trying to implement a new api so that Proxmox authentication works = with SAMLv2. Yes, as you stated in the initial mail.. >=20 > I would have preferred to have more info on the following part=C2=A0: > # this is just a readonly copy, the relevant one is in status.c from pm= xcfs > # observed files are the one we can get directly through IPCC, they are= cached > # using a computed version and only those can be used by the cfs_*_file= methods >=20 I'd suggest ignoring the pmxcfs internal optimized cache-using part, you = do not need that for a start, just use the common file_get_content / file_set_content= helper from the PVE::Tools module, you could do everything with those for now and onl= y then migrate to a optimized cfs_*_{read,write} helper. > To try to bring a little more element, I added a file to the following = list in the PVE::Cluster file > my=C2=A0$observed=C2=A0=3D=C2=A0{ > =C2=A0=C2=A0=C2=A0=C2=A0'request.tmp'=C2=A0=3D>=C2=A01, >=20 > Still in the PVE::Cluster file, It is well in the following part that i= t blocks=C2=A0: >=20 >=20 > If I take the error message from the first email, > =C2=AB=C2=A0 error during cfs-locked \'file-request_tmp\' operation: pv= e cluster filesystem not online /etc/pve/priv/lock.=C2=A0=C2=BB > If I test the dir /etc/pve/priv/lock, it exists! Existence is not a problem, pmxcfs is a clustered realtime configuration = filesystem, it either may not be mounted (and again, running is not always a 100% gua= rantee that it is still mounted) or in a cluster (or thinking that's in a cluster due= to `/etc/corosync/corosync.conf` and/or `/etc/pve/corosync.conf` existing) b= ut has no quorum, i.e., read-only >=20 > Do the files we add in PVE::Cluster file need to be listed in /var/lib/= pve-cluster/config.db, if so, any spec please? no, that's the backing DB, I'd heavily recommend not modifying that one d= irectly if unsure. Those files get always created on the FUSE VFS layer (besides the= very barebone initial one we create with a small helper). Note: you need the correct permissions in your service, it must be in www= -data group to be able to read/test directory existance and run as root for writing.