Difference between revisions of "History"
(fixed typo, added ref link) |
(fix English) |
||
Line 3: | Line 3: | ||
== 1999 == | == 1999 == | ||
− | * 1999, Nov: Alexander Tormasov visited Singapore and | + | * 1999, Nov: Alexander Tormasov visited Singapore and proposed a new direction to Sergey Beloussov: container virtualization. He formulated three main components: containers as a set of processes with namespace isolation, file system to share code/ram and isolation in resources. |
* {{Quote|Indeed it was 1999 when our engineers started adding bits and pieces of containers technology to Linux kernel 2.2. Well, not exactly "containers", but rather "virtual environments" at that time -- as it often happens with new technologies, the terminology was different (the term "container" was coined by Sun only five years later, in 2004).|Kir Kolyshkin|http://openvz.livejournal.com/49158.html}} | * {{Quote|Indeed it was 1999 when our engineers started adding bits and pieces of containers technology to Linux kernel 2.2. Well, not exactly "containers", but rather "virtual environments" at that time -- as it often happens with new technologies, the terminology was different (the term "container" was coined by Sun only five years later, in 2004).|Kir Kolyshkin|http://openvz.livejournal.com/49158.html}} |
Revision as of 16:09, 22 April 2015
Here we list major project milestones.
Contents
[hide]1999
- 1999, Nov: Alexander Tormasov visited Singapore and proposed a new direction to Sergey Beloussov: container virtualization. He formulated three main components: containers as a set of processes with namespace isolation, file system to share code/ram and isolation in resources.
Indeed it was 1999 when our engineers started adding bits and pieces of containers technology to Linux kernel 2.2. Well, not exactly "containers", but rather "virtual environments" at that time -- as it often happens with new technologies, the terminology was different (the term "container" was coined by Sun only five years later, in 2004).
—Kir Kolyshkin, http://openvz.livejournal.com/49158.html
2000
- Feb, 2000: we are open office at MIPT and start working on first mockup version of Virtuozzo.
- Jul 2000 (may be other time): connect two computers to Internet, one with vz 0.1, 5k VE during summer.
- Nov, 2000: Limited public beta testing (providing free VEs to people to run their stuff).
2001
- end of 2001 - beginning of 2002: start working on VZWin
2002
- Jan, 2002: SWsoft (now known as Odin) initially released a product for Linux named Virtuozzo[1]
2004
- Dec, 2004: Initial release of Virtuozzo for Windows [2]
2005
- 2005: SWsoft created the OpenVZ Project to release the core of Virtuozzo under GNU GPL. [3]
- ~2005: SWsoft buy software development company with FreeBSD similar staff, do develop it and later drop (small number of clients).
2006
- 4 Aug, 2006: OpenVZ is available in Debian Linux [4]
- 16 Aug, 2006: OpenVZ rebased to RHEL 4 kernel [5]
- Oct, 2006: OpenVZ ported to SPARC[6] and PPC[7]
- Nov, 2006: OpenVZ adds live migration capability [8]
2007
- 13 Mar, 2007: Port to RHEL5 kernel [9]
2008
- 17 Apr, 2008: Rebase to kernel 2.6.25[10]
- Oct, 2008: Port to ARM [11]. Parallels company is in Top 10 Linux kernel contributors with their patches for Linux containers. Our contributions to the kernel at that time was PID, IPC, and network namespaces, with the last one being the biggest.
2011
- Jul 15, 2011: Pavel Emelyanov sent initial RFC and code[12]. The idea of CRIU of course came up earlier when we figured we (or anyone else, for that matter) can't possibly merge in-kernel checkpoint/restore. Re-implementing it in userspace looked crazy for everyone including me, and Andrew Morton's and Linus Torvalds' initial reaction was similar ("some crazy russians").
- Sep 23, 2011: Cyrill Gorcunov made [13] first commit to CRIU project
2012
- Jul 23, 2012: CRIU v0.1 is available [14]
- Oct, 2012: vzctl for upstream Linux kernel is available
2013
- May, 2013: OpenVZ maintenance partnership [15]
2014
- Nov, 2014: Parallels announced merging OpenVZ and Parallels Cloud Server into single common open source codebase[16]
2015
Surprise! Stay tuned.
References
- Jump up ↑ SWsoft Releases Virtuozzo 2.0, Bringing Mainframe-Inspired Functionality to Intel-Based Servers
- Jump up ↑ SWsoft Announces Virtuozzo for Windows Controlled Release
- Jump up ↑ SWsoft offers free, open source version of Virtuozzo
- Jump up ↑ Debian Linux Adopts OpenVZ Virtualization Software
- Jump up ↑ OpenVZ for RHEL4
- Jump up ↑ Open Source Virtualization for Sun UltraSPARC T1
- Jump up ↑ OpenVZ Virtualization Software Available for Power Processors
- Jump up ↑ OpenVZ adds live migration capability
- Jump up ↑ OpenVZ software for Red Hat Enterprise Linux 5
- Jump up ↑ 2.6.25 is out; memory controller and network namespaces are in
- Jump up ↑ OpenVZ ported to ARM (Gumstix Overo)
- Jump up ↑ Checkpoint/restore mostly in the userspace
- Jump up ↑ First commit to CRIU (Checkpoint and Restore in Userspace)
- Jump up ↑ First CRIU public release
- Jump up ↑ Announcing the OpenVZ Maintenance Partnership
- Jump up ↑ OpenVZ past and future
External links
- History of CRIU project
- Linux Kernel Development. How Fast it is Going, Who is Doing It, What They are Doing, and Who is Sponsoring It: An August 2009 Update
- http://lwn.net/Articles/264872/
- http://lwn.net/Articles/251968/
- http://lwn.net/Articles/169972/
- http://lwn.net/Articles/178429/
- http://lwn.net/Articles/204275/
- http://lwn.net/Articles/194259/
- http://lwn.net/Articles/195780/
- http://lwn.net/Articles/207716/
- http://lwn.net/Articles/209377/
- http://lwn.net/Articles/216079/
- http://lwn.net/Articles/222750/
- http://lwn.net/Articles/225990/
- http://lwn.net/Articles/229062/
- http://lwn.net/Articles/234354/