Jump to content

rPath

From Wikipedia, the free encyclopedia
This article is about the technology company. For the computer science term, see rpath.

rPath, Inc. was a technology company based in Raleigh, North Carolina, that developed technology to automate the process of constructing (or packaging), deploying, and updating software.[1] rPath modeled and managed components and dependencies under version control.[2] It acted as a model-driven and version-controlled repository, as well as a software distribution hub.[3]

In November, 2012, rPath was acquired by SAS Institute.[4] Shortly after the acquisition, rPath Linux was discontinued.[5]

History

[edit]

rPath was founded in April 2005,[6] and was originally known for packaging applications as virtual appliances for its independent software vendors (ISVs) and end-user customers.[3] It was co-founded by Erik Troan, co-author of Red Hat Package Manager (RPM), a popular Linux package management system.[7] Troan had left Red Hat in 2004 to create a company called Specifix. The first CEO was Bill Marshall.[8] Original investors were North Bridge Venture Partners and General Catalyst Partners, with $6.4 million in funding disclosed in September 2005.[9] A $9.1 million investment in February 2007 including a new investor Wakefield Group was disclosed.[10] A $10 million investment was disclosed on June 24, 2008.[11] A $7 million investment was disclosed during October, 2010.[12] The company was headquartered in Raleigh, North Carolina.

rPath was one of the first companies to market a software appliance.[13] In 2009, rPath made a transition to selling its products to enterprise IT organizations. IT automation was seen as the codification of runbooks by some,[14] but rPath industrialized the operational aspects of the data center by modelling software configurations.[15] rPath provided a commercial version control platform for deployed software systems. rPath was not a source code management system, but rather, an operational management system that applies the principles and disciplines of source code control to the management of deployable software systems—specifically, system manifests, packages, binaries, policies and system configurations. Version control aids systems to be quickly reproduced, patched and updated, rollback-ed and reported on.[16]

rPath provided a system inventory. This inventory described the desired state of every file, binary, application component, and software stack on every production system—with complete information about applied policies and dependencies—as version-controlled system manifests. These manifests were actionable models for managing the complete lifecycle of deployed systems, providing the basis for understanding change impact and controlling change. Also, rather than applying universal updates, patches and updates could be targeted to only the systems that require change.[16]

rPath allowed definition of systems as layered variants of common base platforms. For example, the standard corporate web server stack may start with a standard build of Red Hat Enterprise Linux (RHEL) but add a specific custom version of the Apache HTTP Server and remove all availability of FTP. With this feature, rPath enabled IT groups to define and automatically enforce build-time policies that govern how systems are constructed.[17]

When rPath imported new or existing software artefacts into system version control, it automatically analyzed each software artifact to discover its entire software supply chain, including operating system (OS) components, middleware and libraries. This information enabled build-time system construction, validation and reduced the number of maintenance failures and outages that result from missing dependencies and conflicting components. "Ovum considers the automated dependency-checking capability to be an extremely useful and often overlooked feature that all such tools should employ.[18]" rPath ensured a consistent system definition, eliminating the risk of system "drift" between lifecycle stages and enabling a clean software build environment.[17]

rPath developed Conary, an open-source software package management and configuration software that formed the core of rBuilder.[19] It allowed rollbacks, incremental ("changeset") updates, and distributed downloading which removes the need for programs such as apt or yum.

rPath supported Microsoft Windows Server 2008 and 2003, Red Hat Enterprise Linux 4 and 5, SUSE Linux Enterprise Server 10, and CentOS. It was also marketed as software as a service.[20]

The NRE Alliance was a coalition of newScale, rPath and Eucalyptus Systems to promote private and hybrid cloud computing. The coalition was announced on August 24, 2010.[21] It had an live web site through August 2012.[22]

On November 30, 2012, the business analytics company SAS Institute announced that it acquired key rPath assets, including technology and staff.[4]

References

[edit]
  1. ^ Craig, Julie. "Cloud Coalition: rPath, newScale, and Eucalyptus Systems Partner on Self-Service Public and Private Cloud". Enterprise Management Associates, 2010, p. 2.
  2. ^ Hubbert, Evelyn. "The Low-Hanging Fruit That Service Operations Teams Should Consider Now". Forrester Research, 2009, p. 5.
  3. ^ a b Chalmers, Rachel. "Eucalyptus Systems, newScale and rPath join to build integrated cloud on-ramp". The 451 Group, 2010, p. 1.
  4. ^ a b "SAS Acquires Key rPath Assets for Broader Deployment of SAS Solutions". Press release. SAS Institute. November 30, 2012. Archived from the original on November 30, 2012. Retrieved October 29, 2016.
  5. ^ "rPath Linux". Linux distribution history. DistroWatch.
  6. ^ "Form D: Notice of Sale of Securities" (PDF). US SEC. July 27, 2005. Retrieved October 29, 2016.
  7. ^ Waldman, Brett. Gillen, Al. "IDC MarketScape: Worldwide Software Appliance 2009 Vendor Analysis". IDC, 2009, p. 12.
  8. ^ Paula Rooney (August 19, 2005). "Ex-Red Hat Execs To Launch rPath". Information Week. Retrieved October 29, 2016.
  9. ^ "rPath, a Startup Led by Ex-Red Hat Executives, Raises $6.4M". osdir. September 13, 2005. Retrieved October 29, 2016.
  10. ^ "Form D: Notice of Sale of Securities" (PDF). US SEC. November 14, 2006. Retrieved October 29, 2016.
  11. ^ Nik Cubrilovic (June 24, 2008). "rPath Raises $10M Series C Round To Further Build Out Cloud Platform". Tech Crunch. Retrieved October 29, 2016.
  12. ^ Nik Cubrilovic (October 26, 2010). "Growth, hiring in rPath's future". Raleigh News & Observer. Archived from the original on October 29, 2010. Retrieved October 29, 2016.
  13. ^ Waldman, Brett. Gillen, Al. "IDC MarketScape: Worldwide Software Appliance 2009 Vendor Analysis". IDC, 2009, p. 11.
  14. ^ Illsley, Roy. "rPath—rBuilder". Ovum, 2010, p. 1.
  15. ^ Illsley, Roy. "rPath—rBuilder". Ovum, 2010, p. 5.
  16. ^ a b Illsley, Roy. "rPath—rBuilder". Ovum, 2010, p. 3.
  17. ^ a b Illsley, Roy. "rPath—rBuilder". Ovum, 2010, p. 4.
  18. ^ Illsley, Roy. "rPath—rBuilder". Ovum, 2010, p. 4-5.
  19. ^ Bruce Byfield (2006-04-12). "Package management meets version control in rPath". linux.com.
  20. ^ Illsley, Roy. "rPath—rBuilder". Ovum, 2010, p. 7.
  21. ^ Burns, Paul. "Four Keys to the Enterprise Cloud". Neovise, 2010, p. 1.
  22. ^ "Delivering Self-Service Private/Hybrid Cloud". Former web site. NRE Alliance. Archived from the original on August 17, 2012. Retrieved October 29, 2016.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=RPath&oldid=1246295992"