Max wait time for task to start else skip task (was Bind a certain task to a certain priority)

Max wait time for task to start else skip task (was Bind a certain task to a certain priority)

Refined idea:

Define a max wait time for the task to start out of the scheduling queue else skip the task.  This will ensure that tasks don't start past the end of the change window for the operation.

Below was the original idea, but evolved to above:

Currently our NA system has a following property set:
scheduler/serialtaskadminrestrictedpriority = 4

We would like an option to bind a certain task type to a certain priority. In our case, we want to bind the "Reboot Device" task to priority 1.

We think that the only two tasks for which it makes sense to run in serial are "Update Software" and "Reboot Device".
Our regular scheduled tasks are running with priority 5, so normally the serial tasks ran with priority 4 will get in front in the queue and start running immediately.

However we face a potential problem if one of our Operators decides to manually run a serial task with priority 1,2 or 3. Then it will pause the execution of the reboot task, which could lead to an operational risk. We want a way to bind "Reboot Device" so it will always start with a priority 1, and no other task would be able to pause its progress and move in front of it in the queue.

Tags (1)
5 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at this stage and we expect the community to help prioritize the idea with comments and community support (votes/kudos)..

Micro Focus Expert
Micro Focus Expert
Status changed to: Accepted

The idea has received enough support from the community and been reviewed by the Micro Focus product team. It is officially on the roadmap for development and delivery. (Subject to change, and not a commitment.)

Joerg_T Honored Contributor.
Honored Contributor.

Basically what we would like to have is an option to control that a scheduled task is not run if the NA system is not able to do within a specific time window.
At some sites, mostly manufacturing/production sites we have very short maintenance windows. Only in that time windows it is possible to reboot devices or perform some special configurations.
For example, if a device reboot is scheduled for Sunday 10am-11am the reboot needs to be done within that time window. If NA is for some reason not able to do it in that time window and e.g. starts the reboot at 11:30am, it would cause a production outage.
So in addition to the normal task settings like specifying a start time, we also need to configure an end time or a time window. Whenever that time window is crossed, the task should not be started

Micro Focus Expert
Micro Focus Expert

Exactly Joerg.  The way we are thinking about this ER is to define a max waiting time from the scheduled start time that is permitted (or last timestamp allowed) for NA to still start the task, else skip the task.

Renaming the idea as such if this make sense.

Micro Focus Expert
Micro Focus Expert
Status changed to: Delivered

This idea is delivered now as part of NA 2018.08 release.

More details on documentation and downloads:

 

https://docs.microfocus.com/itom/Network_Automation:2018.08/Home

 

Software Licenses and Downloads

The Software Licenses and Downloads Portal will require the user to login to an order to activate entitlements and download software.

About the Author
Senior Solutions Consultant in Micro Focus Customer Assist organization - with overall 12 plus years of experience working in HP(E) / Microfocus R&D organization. For past several years, I have been working as a customer facing R&D engineer with product expertise in Network Management area and have recently started working on Operations Bridge products. Primary activities involve assistance to field teams (Sales, Customer Success, Support, Professional Services): Technical assistance in product demos and POCs, Deployment consultancy, Product audit and best practice guidance, Assistance in Escalations and working with Product Management and R&D architects on translating customer feedback into relevant and appropriate product requirement (CR, ER, New Feature etc).
Most "Liked" Contributors
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.