Operating system layering

Patent metadata

Field	Value
Publication number	US-9898354-B2
Application number	US-201615076277-A
Country	US
Kind code	B2
Filing date	Mar 21, 2016
Priority date	Mar 21, 2016
Publication date	Feb 20, 2018
Grant date	Feb 20, 2018

Abstract

Techniques for implementing operating system layering are described herein. In one example, a method includes managing one or more container temporary storage spaces and one or more container runtime environments. Furthermore, the method includes loading, one or more drivers to provide compatibility between a container operating system and a host operating system, the one or more drivers comprising application program interface (API) compatibility libraries to enable API compatibility between the container operating system and the host operating system; metadata arbitration logic to enable compatibility between the container operating system and the host operating system by modifying container operating system references; and file arbitration logic to modify operating system file locations accessed by the container operating system and the host operating system.

First claim

What is claimed is:

1. A system to support operating system layering, comprising: a memory device comprising a host operating system and one or more container runtime environments that execute a container operating system, wherein the host operating system is a different operating system than the container operating system, the memory device further comprising one or more container temporary storage spaces; and a processor to: manage, via a container facility, the one or more container temporary storage spaces and the one or more container runtime environments; and load, via the container facility, one or more drivers to provide compatibility between the container operating system and the host operating system, wherein the processor is to identify the one or more drivers based on a comparison of drivers stored in a source selected from a group consisting of a local driver store, drivers available for download from an update service, and drivers acquired from an image file, and wherein the comparison comprises determining a container operating system version or a container operating system type and determining a host operating system version or a host operating system type, the one or more drivers comprising: application program interface (API) compatibility libraries to enable API compatibility between the container operating system and the host operating system, wherein the API compatibility libraries comprise a mapping table to map a system call executed by the container operating system to a kernel API in the host operating system, wherein the mapping table is to support the container operating system being different from the host operating system; metadata arbitration logic to enable compatibility between the container operating system and the host operating system by modifying container operating system references; and file arbitration logic to modify operating system file locations accessed by the container operating system and the host operating system.

2. The system of claim 1 , wherein the one or more drivers implement a data structure that maps an API to a compiled file for a specific operating system type.

3. The system of claim 1 , wherein the processor is to load the one or more drivers and use data in the one or more drivers to execute a system call.

4. The system of claim 3 , wherein the processor is to detect a failed execution of the system call from the container operating system and return a compatible exception and/or event.

5. The system of claim 3 , wherein the processor is to detect a successful execution of the system call from the container operating system and return a compatible response.

6. The system of claim 1 , wherein the processor is to monitor failed system calls and collect telemetry data.

7. The system of claim 1 , wherein the processor is to determine that the one or more drivers are not stored in the memory device; and download an updated driver or load the updated driver that is embedded in an image file.

8. The system of claim 1 , wherein the processor is to load the one or more drivers based on metadata corresponding to the host operating system, the container operating system, API compatibility libraries, driver packages, and application software.

9. The system of claim 1 , wherein the processor is to modify the system call to a function and a file name corresponding to the host operating system and transmit the modified system call to a kernel driver of the host operating system.

10. A method for operating system layering, comprising: managing one or more container temporary storage spaces and one or more container runtime environments; and loading, one or more drivers to provide compatibility between a container operating system and a host operating system, wherein the host operating system is a different operating system than the container operating system, wherein the one or more drivers are identified based on a comparison of drivers stored in a source selected from a group consisting of a local driver store, drivers available for download from an update service, and drivers acquired from an image file, and wherein the comparison comprises determining a container operating system version or a container operating system type and determining a host operating system version or a host operating system type, the one or more drivers comprising: application program interface (API) compatibility libraries to enable API compatibility between the container operating system and the host operating system, wherein the API compatibility libraries comprise a mapping table to map a system call executed by the container operating system to a kernel API in the host operating system, wherein the mapping table is to support the container operating system being different from the host operating system; metadata arbitration logic to enable compatibility between the container operating system and the host operating system by modifying container operating system references; and file arbitration logic to modify operating system file locations accessed by the container operating system and the host operating system.

11. The method of claim 10 , wherein the one or more drivers implement a data structure that maps an API to a compiled file for a specific operating system type.

12. The method of claim 10 , comprising loading the one or more drivers and use data in the one or more drivers to execute a system call.

13. The method of claim 12 , comprising detecting a failed execution of the system call from the container operating system and return a compatible exception and/or event.

14. The method of claim 12 , comprising detecting a successful execution of the system call from the container operating system and return a compatible response.

15. The method of claim 10 , comprising loading the one or more drivers based on metadata corresponding to the host operating system, the container operating system, API compatibility libraries, driver packages, and application software.

16. The method of claim 10 , comprising loading one or more image files based on monitoring information, policy information, configuration information, or information stored with each image file.

17. The method of claim 10 , comprising inspecting one or more image files for duplicate binary information and notifying the host operating system to de-duplicate the one or more image files with duplicate binary information.

18. One or more computer-readable storage devices for operating system layering comprising a plurality of instructions that, based at least on execution by a processor, cause the processor to: manage, via a container facility, one or more container temporary storage spaces and one or more container runtime environments; and load, via the container facility, one or more drivers to provide compatibility between a container operating system and a host operating system, wherein the host operating system is a different operating system than the container operating system, wherein the processor is to identify the one or more drivers based on a comparison of drivers stored in a source selected from a group consisting of a local driver store, drivers available for download from an update service, and drivers acquired from an image file, and wherein the comparison comprises determining a container operating system version or a container operating system type and determining a host operating system version or a host operating system type, the one or more drivers comprising: application program interface (API) compatibility libraries to enable API compatibility between the container operating sy

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Engel Jeffrey M
• Smith Frederick J
• Pulapaka Hari R
• Schultz Benjamin M
• Iyigun Mehmet
• Richardson John
• Stark Taylor

Classifications

• G06F2009/45579

  I/O management, e.g. providing access to device drivers or storage · CPC title

• G06F8/65

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• G06F9/44536

  Selecting among different versions · CPC title

• G06F9/541 Primary

  via adapters, e.g. between incompatible applications · CPC title