Re: [PVE-User] Proxmox VE 3.4 - Support Lifecycle

[Denys Duchier]

Denys Duchier  writes:

> Mikhail  writes:
>
>> Can you share what's the problem with iSCSI in current 4.1 PVE? We're
>> looking to install new cluster based on latest PVE, and we're going to
>> rely on iSCSI in terms of storage.
>
> The problem is you can't write to your SAN (if it uses SMR-HDDs, I
> gathered).  Our setup is a Dell PowerVault 3200i + iSCSI/multipath, and
> our servers just seem to DOS themselves to death with queued
> reconnection attempts.
>
> I suspect it has been fixed in this commit:
>
> https://git.proxmox.com/?p=pve-kernel.git;a=commit;h=ef5f1ab894d7d400308a4a38b2d0cdf1458f
>
> but I haven't been able to confirm it (I compiled the current pve-kernel,
> but it is entirely possible that I didn't do it right - so far I can't
> see my LUNs).

that last bit was because I had forgotten to update my host group
(controlling LUN access) with the new initiator id after reinstallation
of PVE 4.1.  Now, not only can I see my LUNs, but I can also restore VMs
on it. So the new pve-kernel does indeed fix the bug.

Cheers,
--Denys
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Proxmox VE 3.4 - Support Lifecycle

[Denys Duchier]

Michael Rasmussen  writes:

> If you are talking about the iSCSI/LVM bug then a fix for this has been
> found and should come to a repo near you soon;-)

That would be great :-)
Cheers,
--Denys
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Proxmox VE 3.4 - Support Lifecycle

[Denys Duchier]

Mikhail  writes:

> Can you share what's the problem with iSCSI in current 4.1 PVE? We're
> looking to install new cluster based on latest PVE, and we're going to
> rely on iSCSI in terms of storage.

The problem is you can't write to your SAN (if it uses SMR-HDDs, I
gathered).  Our setup is a Dell PowerVault 3200i + iSCSI/multipath, and
our servers just seem to DOS themselves to death with queued
reconnection attempts.

I suspect it has been fixed in this commit:

https://git.proxmox.com/?p=pve-kernel.git;a=commit;h=ef5f1ab894d7d400308a4a38b2d0cdf1458f

but I haven't been able to confirm it (I compiled the current pve-kernel,
but it is entirely possible that I didn't do it right - so far I can't
see my LUNs).

Cheers,
--Denys
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Proxmox VE 3.4 - Support Lifecycle

[Michael Rasmussen]

On Thu, 25 Feb 2016 17:49:04 +0100
Denys Duchier  wrote:

> 
> due to the iSCSI bug in PVE 4.1, this is currently not a great option if
> you have one of the affected SANs (which we do).
> 
If you are talking about the iSCSI/LVM bug then a fix for this has been
found and should come to a repo near you soon;-)

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
signal(i, SIG_DFL); /* crunch, crunch, crunch */
-- Larry Wall in doarg.c from the perl source code


pgpOyrJ8JaPan.pgp
Description: OpenPGP digital signature
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Proxmox VE 3.4 - Support Lifecycle

[Denys Duchier]

Martin Maurer  writes:

> If you are still running on Proxmox VE 3.4, we recommend to move to the 
> current
> Proxmox VE 4.x as soon as possible.

due to the iSCSI bug in PVE 4.1, this is currently not a great option if
you have one of the affected SANs (which we do).

Cheers,
--Denys
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[PVE-User] Proxmox VE 3.4 - Support Lifecycle

[Martin Maurer]

- Mainstream support

The end date of Proxmox VE 3.4 mainstream support is April 30, 2016. On 
this date, also the Debian Wheezy security support is ending.


- Extended Support

Proxmox VE 3.4 will get security updates until February 28, 2017. This 
is only for security fixes. No new features will be implemented.


Debian LTS team https://wiki.debian.org/LTS/ will provide security 
updates for selected Wheezy packages. For more details regarding LTS and 
supported packages, see https://wiki.debian.org/LTS/FAQ


If you are still running on Proxmox VE 3.4, we recommend to move to the 
current Proxmox VE 4.x as soon as possible.


--

Best Regards,

Martin Maurer

Proxmox VE project leader

mar...@proxmox.com
http://www.proxmox.com

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user