<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
pve-manager has a branch for 3.x it's the stable-3 branch use:<br>
<br>
<blockquote type="cite">git fetch origin stable-3<br>
git checkout stable-3</blockquote>
<br>
to get it locally. As OpenVZ get's deprecated in PVE4 it maybe
doesn't makes sense to put to much of development power in there, in
my opinion.<br>
<br>
PVE 3.4 is surely not deprecated as it's our current stable release.
<br>
<br>
<br>
<div class="moz-cite-prefix">On 08/21/2015 11:23 AM, Gerhard Lausser
wrote:<br>
</div>
<blockquote cite="mid:035e01d0dbf3$1a1d7b60$4e587220$@consol.de"
type="cite">
<pre wrap="">Hi,
i patched /usr/share/perl5/PVE/OpenVZ.pm and
/usr/share/perl5/PVE/API2/OpenVZ.pm on my Proxmox 3.4, so one can add
features when creating a container with pvesh create.
pvesh create /nodes/... -vmid 100 -features "nfs:on"
When i checked out the pve-magager.git, i saw there is no 3.x branch, it's
all moving forward in a single master branch. So does it mean, 3.x (and
especially the openvz functionality) can be considered as deprecated and it
is not worth to spend any effort on it?
Gerhard
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
pve-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pve-devel@pve.proxmox.com">pve-devel@pve.proxmox.com</a>
<a class="moz-txt-link-freetext" href="http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel">http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>