Skip to end of metadata
Go to start of metadata

This page guides you through downloading, installing, and configuring a basic Repose configuration for production use.

 

Deployment options 

Proxy Server (Valve) installation instructions

  • Repose is run as a standalone proxy server which will sit between the requester and the origin service. This deployment strategy runs Repose on a different port or different host than the origin service.
  • Proxy Server (Valve) is a jar file.

ROOT.war installation instructions

  • Repose will run inside a third party servlet container (e.g. tomcat or glasshfish). This deployment allows Repose to run on the same container as the origin service.
  • The ROOT.war artifact is a Web application ARchive (WAR). It contains all the components needed to install Repose into a running application container. One of these components is a default web.xml that can start up Repose in the standard configuration model.
  • NOTE When deploying on Glassfish, be sure to remove the default-web.xml file located in domains/your_domain/config.  This file contains a default servlet that interferes with the routing between Repose and the origin service.

 

Docker installation instructions

  • Repose Valve will run inside a docker container

 

Configuration management

Check out our Configuration Management repositories:

Build Repose from GitHub

Repose can be downloaded from https://github.com/rackerlabs/repose and built with Maven. 

~/src/repose$ mvn compile package

Once built, the following binaries are created for the different installations:

  • Root.WAR - The ROOT.war is built at repose-aggregator/core/web-application/target/ROOT.war.

  • Valve Proxy Server - The Valve jar file is located at repose-aggregator/core/valve/target/repose-valve.jar

Repose sandbox

The Repose Sandbox Instructions provide a quick non-production method of installing Repose for informational use only. 


Maven Artifact Verification

Starting soon (see Release Notes) we'll have signed artifacts that we upload to maven.research.rackspacecloud.com and you'll be able to verify the java artifacts used to produce the RPMs and DEBs.
We don't have signing (yet) of the RPMs and DEBs.

Our public key is available on the keyservers and may be as easy to obtain as issuing the following:

gpg --keyserver pgp.mit.edu --recv-key 389195C8E7C89BBB

To download it from http://pgp.mit.edu/pks/lookup?op=get&search=0x389195C8E7C89BBB and automatically import it.

If not, then it is also available below:

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2

mQENBFT2J8oBCADCxveqtm4+/1VOU2e+eJeUZBJ12dnwCH2P7PNveDaG7mA6FLpL
iZ9BwPqrED34IQMfZHoTAxUSeSe3zn0Y08gRUb/ZtjuOaSJrsI36GS+HsEweMnzX
wUARKTG/j46Z3vwJBN621GbXIKhjx5PxtMtnjAXRHKrUtrO6wPCTW4m+FVDFDGZe
Sx05IKMt9WWlHi+zjA0AXwi61h8XewOad+HQuVhevdtOpunMcv0QsU6MDUsPG+4N
EYETZDcK1t6y67ySEZludz48vqhaYgeS+v2AmMhnzxOtTRyLvONP533By5i9YGW5
NiW6utvl3wUwlA5M1CQSBdJJy9NtN/TrHiefABEBAAG0K1JlcG9zZVNpZ25pbmdL
ZXkgPFJlcG9zZUNvcmVAcmFja3NwYWNlLmNvbT6JATcEEwEIACEFAlT2J8oCGwMF
CwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQOJGVyOfIm7uTMwf/Qy8M/xNdaIni
wKt7qo1NX6Mdo4MyjJ6WCgKSSFvOpc1QfIlAdhnxk31iyMlchtKBpGZQb9kmKtJj
nDKGbSCmprDnKcSzJf/OXvJs1N1xWrjhlkrgnhJ6bJXEct2+g5hZ9CE8yAaCt/E7
O500mkzZ8Ctj4jCSFsUchlSW6tUBGGNRM2B1PaqWI1EZWpOfLCHStI5YVR8n6fJ+
SKhE6s5sStWiKJpMEeDv7juPXWHCyyKjFQBv/L6NAuinP2sdvGL+N+B/tQsYmbKb
RAvlb4lIXClHyKHPfPDX/Xcg0Ig+W6nbAxaM8Kka7abW/LFrL4c9NkvhuTbw5CRD
K+GdF6JdlQ==
=mfDI
-----END PGP PUBLIC KEY BLOCK-----

To verify the integrity of an artifact after importing the key you can:

  • RPM
    • rpm --verbose --checksig <ARTIFACT>.rpm
  • DEB
    • dpkg-sig --verbose --verify <ARTIFACT>.deb
  • Jar/Ear/War
    • gpg --verify <ARTIFACT>.[j|e|w]ar.asc <ARTIFACT>.[j|e|w]ar
  • No labels