METHOD FOR MINIMAL SERVICE IMPACT DURING SOFTWARE UPGRADE IN NETWORK ELEMENTS (NES)

• US 20160364231A1
• Filed: 06/10/2015
• Published: 12/15/2016
• Est. Priority Date: 06/10/2015
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: TATI, Srikar, BHARATHI, Vijayaraghavan, OWENS, Peter J.
• Application Number:
  US14/735,483
• Publication Number:
  US 20160364231A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/656 while running

Abstract

Exemplary methods include in response to receiving an indication to perform an in-service software upgrade (ISSU), an init process executing on a current root file system is configured to perform operations comprising: 1) releasing the current root file system by setting an indication that the ISSU is in progress, and terminating processes executing on the current root file system, and 2) switching from the current root file system to a new root file system by moving a root from the current root file system to the new root file system, moving critical system files from the current root file system to the new root file system, unmounting the current root file system, and executing an init process on the new root file system. The init process executing on the new root file system is configured to perform operations comprising starting processes on the new root file system.

Claims

1. A method in a first network device for performing a software upgrade, the method comprising:

receiving, by a first init process executing on a first root file system, an indication to perform an in-service software upgrade (ISSU);

releasing, by the first init process in response to receiving the indication to perform the ISSU, the first root file system by;

setting an indication that the ISSU is in progress, and

terminating processes executing on the first root file system;

switching, by the first init process in response to receiving the indication to perform the ISSU, from the first root file system to a second root file system by;

moving a root from the first root file system to the second root file system, wherein the second root file system includes an upgraded software,

moving critical system files from the first root file system to the second root file system,

unmounting the first root file system, and

executing a second init process on the second root file system; and

initializing, by the second init process executing on the second root file system, the second root file system by;

starting processes on the second root file system.

2. The method of claim 1, wherein releasing the first root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, unmounting of critical system files residing on the first root file system, thereby avoiding rebooting of a kernel.

3. The method of claim 1, wherein releasing the first root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, unloading of loadable kernel modules (LKMs), thereby avoiding resetting of peripheral devices connected to the first network device.

4. The method of claim 1, wherein initializing the second root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, mounting of critical system files on the second root file system.

5. The method of claim 1, wherein initializing the second root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, loading of loadable kernel modules (LKMs).

6. The method of claim 1, wherein initializing the second root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, resetting of hardware devices connected to the first network device.

7. The method of claim 1, wherein releasing the first root file system further comprises executing a halt script, and wherein the halt script is configured to, in response detecting the indication that the ISSU is in progress, prevent unmounting of critical system files residing on the first root file system.

8. The method of claim 1, wherein releasing the first root file system further comprises executing a halt script, and wherein the halt script is configured to, in response detecting the indication that the ISSU is in progress, prevent unloading of loadable kernel modules (LKMs).

9. The method of claim 1, wherein initializing the second root file system further comprises executing an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent mounting of critical system files on the second root file system.

10. The method of claim 1, wherein initializing the second root file system further comprises executing an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent loading of loadable kernel modules (LKMs).

11. The method of claim 1, wherein initializing the second root file system further comprises executing an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent resetting of hardware devices connected to the first network device.

12. A first network device for performing a software upgrade, the first network device comprising:

a set of one or more processors; and

a non-transitory machine-readable storage medium containing code, which when executed by the set of one or more processors, causes the first network device to;

receive, by a first init process executing on a first root file system, an indication to perform an in-service software upgrade (ISSU);

release, by the first init process in response to receiving the indication to perform the ISSU, the first root file system by;

setting an indication that the ISSU is in progress, and

terminating processes executing on the first root file system;

switch, by the first init process in response to receiving the indication to perform the ISSU, from the first root file system to a second root file system by;

moving a root from the first root file system to the second root file system, wherein the second root file system includes an upgraded software,

moving critical system files from the first root file system to the second root file system,

unmounting the first root file system, and

executing a second init process on the second root file system; and

initialize, by the second init process executing on the second root file system, the second root file system by;

starting processes on the second root file system.

13. The first network device of claim 12, wherein releasing the first root file system further comprises the first init process to:

prevent, in response detecting the indication that the ISSU is in progress, unmounting of critical system files residing on the first root file system, thereby avoiding rebooting of a kernel.

14. The first network device of claim 12, wherein releasing the first root file system further comprises the first init process to:

prevent, in response detecting the indication that the ISSU is in progress, unloading of loadable kernel modules (LKMs), thereby avoiding resetting of peripheral devices connected to the first network device.

15. The first network device of claim 12, wherein initializing the second root file system further comprises the second init process to:

prevent, in response detecting the indication that the ISSU is in progress, mounting of critical system files on the second root file system.

16. The first network device of claim 12, wherein initializing the second root file system further comprises the second init process to:

prevent, in response detecting the indication that the ISSU is in progress, loading of loadable kernel modules (LKMs).

17. The first network device of claim 12, wherein initializing the second root file system further comprises the second init process to:

prevent, in response detecting the indication that the ISSU is in progress, resetting of hardware devices connected to the first network device.

18. The first network device of claim 12, wherein releasing the first root file system further comprises the first init process to execute a halt script, and wherein the halt script is configured to, in response detecting the indication that the ISSU is in progress, prevent unmounting of critical system files residing on the first root file system.

19. The first network device of claim 12, wherein releasing the first root file system further comprises the first init process to execute a halt script, and wherein the halt script is configured to, in response detecting the indication that the ISSU is in progress, prevent unloading of loadable kernel modules (LKMs).

20. The first network device of claim 12, wherein initializing the second root file system further comprises the second init process to execute an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent mounting of critical system files on the second root file system.

21. The first network device of claim 12, wherein initializing the second root file system further comprises the second init process to execute an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent loading of loadable kernel modules (LKMs).

22. The first network device of claim 12, wherein initializing the second root file system further comprises the second init process to execute an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent resetting of hardware devices connected to the first network device.

23. A non-transitory machine-readable storage medium having computer code stored therein, which when executed by a set of one or more processors of a first network device for performing a software upgrade, causes the first network device to perform operations comprising:

receiving, by a first init process executing on a first root file system, an indication to perform an in-service software upgrade (ISSU);

releasing, by the first init process in response to receiving the indication to perform the ISSU, the first root file system by;

setting an indication that the ISSU is in progress, and

terminating processes executing on the first root file system;

switching, by the first init process in response to receiving the indication to perform the ISSU, from the first root file system to a second root file system by;

moving a root from the first root file system to the second root file system, wherein the second root file system includes an upgraded software,

moving critical system files from the first root file system to the second root file system,

unmounting the first root file system, and

executing a second init process on the second root file system; and

initializing, by the second init process executing on the second root file system, the second root file system by;

starting processes on the second root file system.

24. The non-transitory machine-readable storage medium of claim 23, wherein releasing the first root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, unmounting of critical system files residing on the first root file system, thereby avoiding rebooting of a kernel.

25. The non-transitory machine-readable storage medium of claim 23, wherein releasing the first root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, unloading of loadable kernel modules (LKMs), thereby avoiding resetting of peripheral devices connected to the first network device.

26. The non-transitory machine-readable storage medium of claim 23, wherein initializing the second root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, mounting of critical system files on the second root file system.

27. The non-transitory machine-readable storage medium of claim 23, wherein initializing the second root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, loading of loadable kernel modules (LKMs).

28. The non-transitory machine-readable storage medium of claim 23, wherein initializing the second root file system further comprises:

preventing, in response detecting the indication that the ISSU is in progress, resetting of hardware devices connected to the first network device.

29. The non-transitory machine-readable storage medium of claim 23, wherein releasing the first root file system further comprises executing a halt script, and wherein the halt script is configured to, in response detecting the indication that the ISSU is in progress, prevent unmounting of critical system files residing on the first root file system.

30. The non-transitory machine-readable storage medium of claim 23, wherein releasing the first root file system further comprises executing a halt script, and wherein the halt script is configured to, in response detecting the indication that the ISSU is in progress, prevent unloading of loadable kernel modules (LKMs).

31. The non-transitory machine-readable storage medium of claim 23, wherein initializing the second root file system further comprises executing an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent mounting of critical system files on the second root file system.

32. The non-transitory machine-readable storage medium of claim 23, wherein initializing the second root file system further comprises executing an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent loading of loadable kernel modules (LKMs).

33. The non-transitory machine-readable storage medium of claim 23, wherein initializing the second root file system further comprises executing an init script, and wherein the init script is configured to, in response detecting the indication that the ISSU is in progress, prevent resetting of hardware devices connected to the first network device.