Methods for network change tracking and rollback of changes based on change tickets

A system comprising:

• one or more processors;
• and
• one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform actions comprising:
• creating, by a first user, a change ticket for making one or more changes at a network object of a network:
• making, by the first user, the one or more changes within a network controller of the network:
• submitting, by the first user to a second user, the change ticket for approval:
• based at least in part on approval of the change ticket, deploying, by a third user, the one or more changes at the network object:
• determining that at least one change of the one or more changes needs to be undone:
• based at least in part on the change ticket, determining, by the first user, a plan to undo the at least one change of the one or more changes associated with the change ticket, wherein the plan includes one or more actions to undo only the at least one change of the one or more changes at the network object:
• creating, by the first user, a rollback ticket to implement the plan to undo the at least one change of the one or more changes at the network object:
• based at least on the plan, implementing, by the first user, the one or more actions to undo only the at least one change of the one or more changes at the network object within the network controller of the network:
• submitting, by the first user to the second user, the rollback ticket for approval;
• and
• based at least in part on approval of the rollback ticket, deploying, by the third user, the one or more actions to undo only the at least one change of the one or more changes at the network object.

One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform actions comprising:

• creating, by a first user, a change ticket for making one or more changes at a network object of a network;
• making, by the first user, the one or more changes within a network controller of the network;
• submitting, by the first user to a second user, the change ticket for approval;
• based at least in part on approval of the change ticket, deploying, by a third user, the one or more changes at the network object;
• determining that at least one change of the one or more changes needs to be undone;
• based at least in part on the change ticket, determining, by the first user, a plan to undo the at least one change of the one or more changes associated with the change ticket, wherein the plan includes one or more actions to undo only the at least one change of the one or more changes at the network object;
• creating, by the first user, a rollback ticket to implement the plan to undo the at least one change of the one or more changes at the network object;
• based at least on the plan, implementing, by the first user, the one or more actions to undo only the at least one change of the one or more changes at the network object within the network controller of the network;
• submitting, by the first user to the second user, the rollback ticket for approval;
• and
• based at least in part on approval of the rollback ticket, deploying, by the third user, the one or more actions to undo only the at least one change of the one or more changes at the network object.