A docker registry service in the cloud that integrates with Pulp and the Red Hat ecosystem. Using a Pulp server the service deploys docker image layers to cloud storage (AWS S3) and OpenShift (Crane).

Below is a typical use of the raas tool. The following global options may be used:
--configenv dev|stage|master This is an important feature of raas. This enables the user to seemlessly switch between environments that are configured and managed completely separate from each other.--log DEBUG|INFO--nocommit This is typically only used in development or testing. You may wish to run status command with --nocommit since status makes no changes to the configuration, only log files.NOTE: The commands below assume the container has been launched in interactive shell mode, i.e. run raas then enter the commands below. However you may wish to pass arguments to the container. For example, raas raas status <isv>. The first "raas" is the docker run container alias; the second "raas" is the tool.
Prerequisites
docker save <some/image> > some-image.tarNOTE: the tar file must be mounted into the container. The installation procedure specifies using /run/docker_uploads but another directory path may be used.
raas pulp-upload <isv> /run/docker_uploads/<some-image>.tar
Prerequisites
raas setup <isv> --oodomain <domain> --s3bucket <bucket>
/v1/_pingPrerequisites
raas publish <isv> <some/image>
raas status <isv> -a [<some/image>] [--pulp]
rhc clone .../v1/_pingThe container packaging of this tool has additional troubleshooting tools installed.
[sudo] docker pull aweiteka/raas
See below for docker run command.
Enter the container interactively and initialize the tools:
# init <environment>
Use the command-line tools to inspect the system.
raas --log DEBUG status ...aws s3 ls s3://mybucket --recursive...pulp docker repo listrhc ...cd /tmp/isv-cert-raas and look aroundThe raas tool is intended to be run as a container. State is maintained by the configuration repository. In this way multiple users, including automated processes, can use raas to manage and troubleshoot the registry without workstation dependencies.
The container provides raas, pulp, aws, rhc and git tools. You may need to edit ~/.openshift.express.conf to add your username for the rhc client to work.
NOTE: Most of these steps will be automated with the introduction of the atomic install|run tool.
Pull container image. The 'latest' tag (assumed) tracks the stable release of the project.
sudo docker pull aweiteka/raas
Create directory for uploading content to pulp
sudo mkdir -p /run/docker_uploads
Set selinux context for directories mounted into the container:
sudo chcon -Rv -u system_u -t svirt_sandbox_file_t /run/docker_uploads
sudo chcon -Rv -u system_u -t svirt_sandbox_file_t $HOME/.ssh
Edit your $HOME/.bashrc file. This sets an environment variable of read+write private repository and adds an alias for running the container.
export RAAS_CONF_REPO=ssh://[email protected]:user/private-raas-config.git
alias raas='sudo docker run -it --rm \
-e RAAS_CONF_REPO=$RAAS_CONF_REPO \
-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa \
-v $HOME/.ssh/known_hosts:/root/.ssh/known_hosts \
-v /run/docker_uploads:/run/docker_uploads \
aweiteka/raas'
Source the .bashrc file
source .bashrc
Content type
Image
Digest
sha256:49681b901…
Size
159.8 MB
Last updated
almost 11 years ago
docker pull aweiteka/raas