Difference between revisions of "History"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(fix English)
(Factual and English fixes, another try to unify date format)
Line 3: Line 3:
 
== 1999 ==
 
== 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.
+
* Nov 1999: 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}}
Line 9: Line 9:
 
== 2000 ==
 
== 2000 ==
  
* Feb, 2000: we are open office at MIPT and start working on first mockup version of Virtuozzo.
+
* Feb 2000: office at MIPT is established, 5 people started working on the first mockup version of Virtuozzo (namespaces, isolation, vzfs).
  
* Jul 2000 (may be other time): connect two computers to Internet, one with vz 0.1, 5k VE during summer.
+
* Jul 2000: limited public beta testing: two public servers (Virtuozzo 0.1 and control panels), 5000 VEs during summer
  
* Nov, 2000: Limited public beta testing (providing free VEs to people to run their stuff).
+
* Sep 2000: Andrey Savochkin from MSU started working on User Beancounters.
  
 
== 2001 ==
 
== 2001 ==
  
* end of 2001 - beginning of 2002: start working on VZWin
+
* Dec 2001: Virtuozzo for Windows project started
  
 
== 2002 ==
 
== 2002 ==
  
* Jan, 2002: SWsoft (now known as Odin) initially released a product for Linux named Virtuozzo<ref>[http://www.odin.com/news/id,6987 SWsoft Releases Virtuozzo 2.0, Bringing Mainframe-Inspired Functionality to Intel-Based Servers]</ref>
+
* Jan 2002: SWsoft (now known as Odin) initially released a product for Linux named Virtuozzo<ref>[http://www.odin.com/news/id,6987 SWsoft Releases Virtuozzo 2.0, Bringing Mainframe-Inspired Functionality to Intel-Based Servers]</ref>
 +
* Feb 2002: first clients in Silicon Valley
  
 
== 2004 ==
 
== 2004 ==
  
* Dec, 2004: Initial release of Virtuozzo for Windows <ref>[http://www.odin.com/news/id,7095 SWsoft Announces Virtuozzo for Windows Controlled Release]</ref>
+
* Dec 2004: Initial release of Virtuozzo for Windows <ref>[http://www.odin.com/news/id,7095 SWsoft Announces Virtuozzo for Windows Controlled Release]</ref>
  
 
== 2005 ==
 
== 2005 ==
  
 
* 2005: SWsoft created the OpenVZ Project to release the core of Virtuozzo under GNU GPL. <ref>[http://archive09.linux.com/feature/51173 SWsoft offers free, open source version of Virtuozzo]</ref>
 
* 2005: SWsoft created the OpenVZ Project to release the core of Virtuozzo under GNU GPL. <ref>[http://archive09.linux.com/feature/51173 SWsoft offers free, open source version of Virtuozzo]</ref>
* ~2005: SWsoft buy software development company with FreeBSD similar staff, do develop it and later drop (small number of clients).
+
* 2005: SWsoft acquired a hosting/development company "Express" with their own containers for FreeBSD (it was later dropped due to small number of clients).
  
 
== 2006 ==
 
== 2006 ==
  
* 4 Aug, 2006: OpenVZ is available in Debian Linux <ref>[https://lwn.net/Articles/194259/ Debian Linux Adopts OpenVZ Virtualization Software]</ref>
+
* Aug 2006: OpenVZ is available in Debian Linux <ref>[https://lwn.net/Articles/194259/ Debian Linux Adopts OpenVZ Virtualization Software]</ref>
* 16 Aug, 2006: OpenVZ rebased to RHEL 4 kernel <ref>[https://lwn.net/Articles/195780/ OpenVZ for RHEL4]</ref>
+
* Aug 2006: OpenVZ rebased to RHEL 4 kernel <ref>[https://lwn.net/Articles/195780/ OpenVZ for RHEL4]</ref>
* Oct, 2006: OpenVZ [http://openvz.livejournal.com/10610.html ported] to SPARC<ref>[https://lwn.net/Articles/216079/ Open Source Virtualization for Sun UltraSPARC T1]</ref> and PPC<ref>[https://lwn.net/Articles/204275/ OpenVZ Virtualization Software Available for Power Processors]</ref>
+
* Oct 2006: OpenVZ [http://openvz.livejournal.com/10610.html ported] to SPARC<ref>[https://lwn.net/Articles/216079/ Open Source Virtualization for Sun UltraSPARC T1]</ref> and PPC<ref>[https://lwn.net/Articles/204275/ OpenVZ Virtualization Software Available for Power Processors]</ref>
* Nov, 2006: OpenVZ adds live migration capability <ref>[https://lwn.net/Articles/209377/ OpenVZ adds live migration capability]</ref>
+
* Nov 2006: OpenVZ adds live migration capability <ref>[https://lwn.net/Articles/209377/ OpenVZ adds live migration capability]</ref>
  
 
== 2007 ==
 
== 2007 ==
  
* 13 Mar, 2007: Port to RHEL5 kernel <ref>[https://lwn.net/Articles/225990/ OpenVZ software for Red Hat Enterprise Linux 5]</ref>
+
* Mar 2007: Port to RHEL5 kernel <ref>[https://lwn.net/Articles/225990/ OpenVZ software for Red Hat Enterprise Linux 5]</ref>
  
 
== 2008 ==
 
== 2008 ==
  
* 17 Apr, 2008: Rebase to kernel 2.6.25<ref>[http://openvz.livejournal.com/21817.html 2.6.25 is out; memory controller and network namespaces are in]</ref>
+
* Apr 2008: Rebase to kernel 2.6.25<ref>[http://openvz.livejournal.com/21817.html 2.6.25 is out; memory controller and network namespaces are in]</ref>
* Oct, 2008: Port to ARM <ref>[http://openvz.livejournal.com/24651.html OpenVZ ported to ARM (Gumstix Overo)]</ref>. 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.
+
* Oct 2008: Port to ARM <ref>[http://openvz.livejournal.com/24651.html OpenVZ ported to ARM (Gumstix Overo)]</ref>.  
 +
 
 +
* 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.<ref>[http://www.linuxfoundation.org/sites/main/files/publications/whowriteslinux.pdf 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]</ref>
  
 
== 2011 ==
 
== 2011 ==
  
* Jul 15, 2011: Pavel Emelyanov sent initial RFC and code<ref>[http://lwn.net/Articles/451916/ Checkpoint/restore mostly in the userspace]</ref>. 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").
+
* Jul 2011: Pavel Emelyanov sent initial RFC and code<ref>[http://lwn.net/Articles/451916/ Checkpoint/restore mostly in the userspace]</ref>. 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 <ref>[https://github.com/xemul/criu/commit/523de236244946a0de127dfc9954369963819ef7 First commit to CRIU (Checkpoint and Restore in Userspace)]</ref> first commit to CRIU project
+
* Sep 2011: Cyrill Gorcunov made <ref>[https://github.com/xemul/criu/commit/523de236244946a0de127dfc9954369963819ef7 First commit to CRIU (Checkpoint and Restore in Userspace)]</ref> first commit to CRIU project
  
 
== 2012 ==
 
== 2012 ==
  
* Jul 23, 2012: CRIU v0.1 is available <ref>[http://criu.org/Download/criu#v._0.1 First CRIU public release]</ref>
+
* Jul 2012: CRIU v0.1 is available <ref>[http://criu.org/Download/criu#v._0.1 First CRIU public release]</ref>
* Oct, 2012: [http://wiki.openvz.org/Vzctl_for_upstream_kernel vzctl for upstream Linux kernel] is available
+
* Oct 2012: [http://wiki.openvz.org/Vzctl_for_upstream_kernel vzctl for upstream Linux kernel] is available
  
 
== 2013 ==
 
== 2013 ==
  
* May, 2013: OpenVZ maintenance partnership <ref>[http://openvz.livejournal.com/44228.html Announcing the OpenVZ Maintenance Partnership]</ref>
+
* May 2013: OpenVZ maintenance partnership <ref>[http://openvz.livejournal.com/44228.html Announcing the OpenVZ Maintenance Partnership]</ref>
  
 
== 2014 ==
 
== 2014 ==
  
* Nov, 2014: Parallels announced merging OpenVZ and Parallels Cloud Server into single common open source codebase<ref>[http://openvz.livejournal.com/49158.html OpenVZ past and future]</ref>
+
* Nov 2014: Parallels announced merging OpenVZ and Parallels Cloud Server into single common open source codebase<ref>[http://openvz.livejournal.com/49158.html OpenVZ past and future]</ref>
  
 
== 2015 ==
 
== 2015 ==
  
 
Surprise! Stay tuned.
 
Surprise! Stay tuned.
 
  
 
== References ==
 
== References ==
Line 77: Line 80:
  
 
* [http://criu.org/History History of CRIU project]
 
* [http://criu.org/History History of CRIU project]
* [https://www.linuxfoundation.org/sites/main/files/publications/whowriteslinux.pdf 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/264872/
 
* http://lwn.net/Articles/251968/
 
* http://lwn.net/Articles/251968/

Revision as of 00:20, 23 April 2015

Here we list major project milestones.

1999

  • Nov 1999: 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).

2000

  • Feb 2000: office at MIPT is established, 5 people started working on the first mockup version of Virtuozzo (namespaces, isolation, vzfs).
  • Jul 2000: limited public beta testing: two public servers (Virtuozzo 0.1 and control panels), 5000 VEs during summer
  • Sep 2000: Andrey Savochkin from MSU started working on User Beancounters.

2001

  • Dec 2001: Virtuozzo for Windows project started

2002

  • Jan 2002: SWsoft (now known as Odin) initially released a product for Linux named Virtuozzo[1]
  • Feb 2002: first clients in Silicon Valley

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 acquired a hosting/development company "Express" with their own containers for FreeBSD (it was later dropped due to small number of clients).

2006

  • Aug 2006: OpenVZ is available in Debian Linux [4]
  • 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

  • Mar 2007: Port to RHEL5 kernel [9]

2008

  • 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.[12]

2011

  • Jul 2011: Pavel Emelyanov sent initial RFC and code[13]. 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 2011: Cyrill Gorcunov made [14] first commit to CRIU project

2012

2013

  • May 2013: OpenVZ maintenance partnership [16]

2014

  • Nov 2014: Parallels announced merging OpenVZ and Parallels Cloud Server into single common open source codebase[17]

2015

Surprise! Stay tuned.

References

External links