Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Use Path Outage with Schedule Outage

Description

Suppose you have a long chain of path outage dependency. If you want to schedule an outage on the root chain that would impact all the elements in the chain you would want a way to simply add in one click the root service with all the depending nodes.

Actually you have to add all the nodes depending manually.

Environment

all

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Show:

Antonio Russo September 26, 2012 at 6:53 AM

this has been fixed in features/TN branch on repository...the branch is based on 1.8

commit 3942d9c926e8b23a824ded3081330682fef6c841
Author: Antonio <rssntn67@yahoo.it>
Date: Sat Jan 7 17:21:34 2012 +0100

Fixed Use Path Outage with Schedule Outage

It is possible now to select a radio button to
add a node or an interface with all depencency tree

Should be cherrypicked in master!

Antonio Russo January 16, 2012 at 8:59 AM

Sorry for misunderstanding!
I've not commited this changes on the shared repository.
They are in a local branch.
The changes I made are quick and dirty! Just want to know if you are interested
in this feature. Then I can add to master!

Antonio Russo January 7, 2012 at 11:15 AM

This is a simple screen shot of the page, if you select the radio button when you click add you add automatically all dependency nodes.

Antonio Russo January 7, 2012 at 11:11 AM

I've resolved this in 1.8. Just let me know if you want this functionality there.
It is easy and done with radio button.

Antonio Russo January 5, 2012 at 7:50 AM

The idea is to enhance the Scheduled outages pages adding a checkbox (add with path outage dependency).

So when you check the previous box and you select an interface or a node to add, automatically when you click add
all the service/node dependencies are added.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

Parent

PagerDuty

Created January 5, 2012 at 7:47 AM
Updated February 13, 2013 at 3:39 AM
Resolved February 11, 2013 at 7:08 AM