I think this can so easily be done via other methods (e.g. yum update in cron) it's unnecessary for Plesk to offer this, and dangerous if it's using yum/apt repos as configured on the server by the admin. If you do add this, we will need a way to completely hide this functionality from our managed hosting customers as we will handle this for them outside of Plesk for sure - and we don't want our customers breaking their server by installing updates themselves via Plesk UI.

This is so really important issue. All security related updates should be accessible via Plesk GUI.
- selcted packages, optionally scheduled and automatic
- notifications by email if security updates are available/installed/
- staus success / failed / failed and rollback and so on
- with rollback option, as well as Plesk updates too, if something goes wrong
- why not all updates if they are avalable from stadard respositiory

@Tozz: My server is actually managed through plesk because I have all the necessary information and tool with plesk (web, mail, user,...).
At the begin when I asked if there was a risk to do an update directly from the server, nobody answer, somes said that yes there is a risk, others no .... well no clear answer about this point.

The problem is that plesk use a lot of package so what append if i do an update and lost the panel ?
That's why I ask to plesk to include just an option to do the update directly from the panel, so if there is some possible conflict with some package and plesk, plesk can decide to don't update.

By the way, plesk is really powerfull so adding this kind of option seems to be very important as it is a hosting control panel and the security is for me an important point regarding hosting.

Like Sergey said, of course I don't want to have a full update, for example, perahps having a place to define what do you want to update (php/apache/mysql..) and adding some other package if possible.

Like this, you just need to go to plesk, manage your web services and sometimes doing the update or manually, or automatically, as you want.

But in my mind, It's just a option, if you don't want to use it, you just don't clic on the "update" button ;)

@Lolo: Could you please tell me why you need this in Plesk? We actually monitor the availability of security updates with Nagios, and if there are updates we run a script that upgrades the package on all our machines. This could theoretically be done in cron.

With the current state of MySQL this would be a bad idea, as MySQL is not beeing patched anymore, but is upgraded (due to Oracle's new security policy). It is also a bad idea because it can interfere with administrators.

eg. what if I add a new repository to sources.list because I need some kind of bleeding edge version of some tool, and while I am busy configuring apt pinning Plesk starts to do upgrades. It would cripple my machine. I think this might cause more harm then good.

I also do not see the need for this. If you trust Plesk to run "apt-get upgrade" for you, why not run this command in a cronjob? Ubuntu actually has tools that do automated upgrades. Perhaps Debian and/or CentOS has this as well, dont know.

I feel this has already been implemented in distributions, and there is no need to do this in Plesk.

Sergey,

Good to know. Of course, plesk is not suppose to manage all the packages, but the main functionality must be include because for me security and a server up-to-date is very important in my point of view.

Hi, we are considering this function. Maybe not whole server, but at least main services like PHP/Apache/MySQL - which are not a part of Plesk technically, but yet important to be updated.

Tozz,

Yes it's a web hosting control panel, but as this panel manage a lot of thing, there is a risk when you do a update to broke some link or functionnality.
That's why if this option is available the update can be done by plesk itself and avoid a lot's of problem in case of update or event upgrade.

I don't want to change plesk in a server manager, just add an option to update the server and limited the problem of a bad update because one package is finally not compatible with plesk.

With this kind of update plesk managed itself the update and all the user will be sure to keep their server up-to-date with an minimuim of risk.

And for me even if it is "only" a web hosting CP, security is one of the most important point when you have a web site.

This is a bad idea. Plesk is a web hosting control panel. it is _not_ and should not become some sort of "server manager". It would be nice if I could vote negative votes :)

Which updates are breaking Plesk? I do yum updates all the time. There are only a few packages that you need to exclude.
http://kb.parallels.com/en/234

Following, the link to the post on the forum : http://forum.parallels.com/showthread.php?291694-apt-get-and-plesk

Could you add the link to the forum into the description? It will all other visitors can follow it up and read