Request #3599

Sunstone init script should not manage novnc

Added by Arnold Bechtoldt almost 5 years ago. Updated almost 5 years ago.

Status:NewStart date:02/15/2015
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:Packaging
Target version:-
Pull request:

Description

I think adding init commands like 'start-sunstone|stop-sunstone|restart-sunstone' doesn't make any sense in real-world production setups. You won't be able to address those commands from your configuration mgmt system like saltstack, puppet or any other. Managing novnc in the sunstone init script also causes a problem when you want to stop the dev-webserver of sunstone but novnc should be running.

Please don't manage novnc with the sunstone init script. People that are able to exec 'service opennebula-sunstone start' are able to exec 'service opennebula-novnc start', too.

Refer to https://github.com/OpenNebula/one/commit/bbce1ab1ab47f664a1777da5638a131d5199c188.

History

#1 Updated by Ruben S. Montero almost 5 years ago

  • Status changed from Pending to New
  • Target version set to Release 4.12

#2 Updated by Jaime Melis almost 5 years ago

  • Tracker changed from Bug to Request
  • Assignee set to Javi Fontan
  • Target version deleted (Release 4.12)

Also available in: Atom PDF