Allow to setup OPSI product outside of profiles

Requirements

• Filling out the template is required. Any Enhancement request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
• All new code requires tests to ensure against regressions

Descriptive title for this enhancement

Allow to activate products on an OPSI system without going through a profile

Actual behavior

not implemented

Expected behavior

Be able to deploy a specific package on a OPSI client

Step by step description of new behaviour

1. Go to the opsi client tab
2. Select a software to be installed / updated from the software list on the opsi client tab
3. This software is stored on the client/group
4. More than one software can be in this software list
5. When going to action trigger install, the profile is merged with the list of software from the opsi tab

Benefits

Easy to use for installing/updating a specific package without need to create or update a profile, or when you only need to deploy/update a specific package in a opsi client

Possible Drawbacks

desynchronization between profile list of software and the action that has been done, because the software is not inside a software list

Applicable Issues

every situation where you have to update / install only a software on a opsi client

The "on-demand" tab must display all the localboot of the OPSI server that is set in the OPSI client tab.

Example:

localboot name | version | status (cannot be changed) | icon to launch the on-demand action

The action ask from the webservice is the "on-demand" action.

(from redmine: written on 2017-06-13)

added technical discussion and removed Bugs labels

changed the description

added 5m of time spent

So for future reference, as I had a hard time understanding what was what, it appears there are two things named on-demand in OPSI. What we show as "OPSI ondemand list" in FD is called "Software-on-Demand" in OPSI. There is also an event called "on_demand" which is used to trigger the application of the OPSI config. This is what is used by our very own Argonaut Server OPSI module when applying a profile that does not need a reboot: $res = $self->launch('hostControl_fireEvent',['on_demand', $self->{'fqdn'}]);

I still do not understand how would an on_demand tab or feature work in FD as it would install/remove stuff outside of the profile system, so these actions would most likely be canceled by the profile application later. (When applying the profile any software which is not in the profile will be removed)

http://download.uib.de/opsi_stable/doc/html/en/opsi-manual/opsi-manual.html

changed the description

changed title from Have a new tab for OPSI on-demand to Allow to setup OPSI product outside of profiles

changed the description

created branch 5596-allow-to-setup-opsi-product-outside-of-profiles

mentioned in issue argonaut/argonaut#5699

mentioned in commit 503588e5

added 2h of time spent

added To Be Tested label

Hello, I tried to add 2 localboots software on a workstation and validate but it crash.

 Fatal error: Uncaught Exception: DateTime::__construct(): Failed to parse time string (T:) at position 1 (:): Unexpected character in /usr/share/fusiondirectory/include/simpleplugin/attributes/class_DateAttribute.inc:216 Stack trace: #0 /usr/share/fusiondirectory/include/simpleplugin/attributes/class_DateAttribute.inc(216): DateTime->__construct('T:', Object(DateTimeZone)) #1 /usr/share/fusiondirectory/include/simpleplugin/attributes/class_CompositeAttribute.inc(134): TimeHisAttribute->readValues('09:00') #2 /usr/share/fusiondirectory/include/simpleplugin/attributes/class_CompositeAttribute.inc(137): CompositeAttribute->inputValue('09:00') #3 /usr/share/fusiondirectory/include/simpleplugin/attributes/class_CompositeAttribute.inc(165): CompositeAttribute->inputValue('09:00-11:00') #4 /usr/share/fusiondirectory/include/simpleplugin/attributes/class_SetAttribute.inc(139): CompositeAttribute->setValue('09:00-11:00') #5 /usr/share/fusiondirectory/include/simpleplugin/class_simplePlugin.inc(1476): SetAttribute->check() #6 /usr/ in /usr/share/fusiondirectory/include/simpleplugin/attributes/class_DateAttribute.inc on line 216

added Bugs and removed To Be Tested labels

added To Be Tested and removed Bugs labels

Sorry my fault. It was because I tested on an old workstation with bad values in the timeframe tab.

added 47m of time spent

added 3h 10m of time spent

The functionality is working like expected on 1.3-dev.

closed

removed To Be Tested label

added Changed label

added Added and removed Changed labels

removed technical discussion label