OpenShift Online
Installing and configuring the OpenShift Online client tools
Legal Notice
Copyright © 2014 Red Hat.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
The OpenShift Online Client Tools Installation Guide provides instructions on how to install and configure the client tools on workstations with supported operating systems. Installing the client tools allows developers and administrators to create, build, and deploy applications on OpenShift Online.
1. Document Conventions
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
1.1. Typographic Conventions
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
Mono-spaced Bold
Used to highlight system input, including shell commands, file names and paths. Also used to highlight keys and key combinations. For example:
To see the contents of the filemy_next_bestselling_novelin your current working directory, enter thecat my_next_bestselling_novelcommand at the shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a key, all presented in mono-spaced bold and all distinguishable thanks to context.
Key combinations can be distinguished from an individual key by the plus sign that connects each part of a key combination. For example:
Press Enter to execute the command.Press Ctrl+Alt+F2 to switch to a virtual terminal.
The first example highlights a particular key to press. The second example highlights a key combination: a set of three keys pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in
mono-spaced bold. For example:
File-related classes includefilesystemfor file systems,filefor files, anddirfor directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialog-box text; labeled buttons; check-box and radio-button labels; menu titles and submenu titles. For example:
Choose → → from the main menu bar to launch Mouse Preferences. In the Buttons tab, select the Left-handed mouse check box and click to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).To insert a special character into a gedit file, choose → → from the main menu bar. Next, choose → from the Character Map menu bar, type the name of the character in the Search field and click . The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the button. Now switch back to your document and choose → from the gedit menu bar.
The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
To connect to a remote machine using ssh, typessh username@domain.nameat a shell prompt. If the remote machine isexample.comand your username on that machine is john, typessh john@example.com.Themount -o remount file-systemcommand remounts the named file system. For example, to remount the/homefile system, the command ismount -o remount /home.To see the version of a currently installed package, use therpm -q packagecommand. It will return a result as follows:package-version-release.
Note the words in bold italics above: username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
Publican is a DocBook publishing system.
1.2. Pull-quote Conventions
Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in
mono-spaced roman and presented thus:
books Desktop documentation drafts mss photos stuff svn books_tests Desktop1 downloads images notes scripts svgs
Source-code listings are also set in
mono-spaced roman but add syntax highlighting as follows:
static int kvm_vm_ioctl_deassign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0;
struct kvm_assigned_dev_kernel *match;
mutex_lock(&kvm->lock);
match = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
assigned_dev->assigned_dev_id);
if (!match) {
printk(KERN_INFO "%s: device hasn't been assigned before, "
"so cannot be deassigned\n", __func__);
r = -EINVAL;
goto out;
}
kvm_deassign_device(kvm, match);
kvm_free_assigned_device(kvm, match);
out:
mutex_unlock(&kvm->lock);
return r;
}1.3. Notes and Warnings
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
Note
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
Important
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled “Important” will not cause data loss but may cause irritation and frustration.
Warning
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
2. Getting Help and Giving Feedback
2.1. Do You Need Help?
If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at http://access.redhat.com. Through the customer portal, you can:
- search or browse through a knowledgebase of technical support articles about Red Hat products.
- submit a support case to Red Hat Global Support Services (GSS).
- access other product documentation.
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at https://www.redhat.com/mailman/listinfo. Click on the name of any mailing list to subscribe to that list or to access the list archives.
2.2. We Need Feedback!
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the product OpenShift Online.
When submitting a bug report, be sure to mention the manual's identifier: Docs Client Tools Installation Guide
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
Chapter 1. Introduction to OpenShift Online
OpenShift Online by Red Hat is a Platform as a Service (PaaS) that provides developers and IT organizations with an auto-scaling, cloud application platform for deploying new applications on secure, scalable resources with minimal configuration and management overhead. OpenShift Online supports a wide selection of programming languages and frameworks, such as Java, Ruby, and PHP. Integrated developer tools, such as Eclipse integration, JBoss Developer Studio, and Jenkins, support the application life cycle.
Built on Red Hat Enterprise Linux, OpenShift Online provides a secure and scalable multi-tenant operating system for today's enterprise-class applications while providing integrated application runtimes and libraries.
Chapter 2. OpenShift Client Tools
2.1. About OpenShift Client Tools
There are two ways to interact with OpenShift Online: the Management Console or the Client Tools.
The OpenShift Online Management Console is a graphical interface accessed with a web browser and is best suited for:
- Setting up, administering and managing accounts
- Launching new applications
- Managing and monitoring applications
The OpenShift Online CLI tools, or more commonly referred to as the client tools, are used to manage a cloud environment using a command line interface, and provide features that are not currently available in the Management Console. The client tools are best suited for:
- Coding
- Debugging
- Advanced application management
For example, although you can create an application using the Management Console, the application must be cloned to your workstation to make any code changes, and then redeployed to the remote server using the client tools.
The subsequent sections of this book describe how to install the OpenShift Online client tools on various operating systems.
2.2. Installing Client Tools
2.2.1. Installing on Windows
This section describes how to install the OpenShift Online client tools on Windows operating systems. Instructions are also provided to install the necessary software that is required before the client tools can be installed.
Supported Windows Operating Systems
- Windows 7
- Windows Vista
- Windows XP
- Windows 2000
2.2.1.1. Prerequisites
Sufficient privileges are required to install software on Windows systems. Depending on specific user permissions, disabling the User Account Control (UAC) on Windows Vista or Windows 7 operating systems may be necessary.
2.2.1.2. Installing Required Software
Before installing the OpenShift Online client tools on Windows operating systems, you must download and install the following software:
- RubyInstaller
Git: software version control system.
Instructions to install the required software are provided in the subsequent sections.
2.2.1.2.1. Installing RubyInstaller
Follow the instructions below to install RubyInstaller for Windows.
- From rubyinstaller.org, download and save the latest RubyInstaller package for Windows to your desired directory.
- Double-click the executable RubyInstaller file downloaded in the previos step to launch the RubyInstaller installation wizard. Accept the Ruby License Agreement and click Next.
- Select the Add Ruby executables to your PATH check box, and click Install to begin the installation.
- Click Finish when the install completes.
2.2.1.2.2. Installing Git Version Control
After installing RubyInstaller, follow the instructions below to install Git version control for Windows.
- From http://msysgit.github.com/, download and save the latest version of Git for Windows to your desired directory.
- Double-click the executable Git file downloaded in the previous step to launch the Git installation wizard. Click Next until you are prompted to adjust the PATH environment.
- Select the Run Git and included UNIX tools from the Windows Command Prompt check box and click Next. This is so that you can use the default Windows command prompt for Git and SSH operations.
- Select the Checkout Windows-style, commit Unix-style line endings check box, and click Next.
- Click Finish when the install completes.
2.2.1.3. Installing Client Tools
When
RubyInstaller and Git have been successfully installed, use the following instructions to install the client tools.
- Open Windows Command Prompt.
- Click
Start, typecmdin the Start Search text box, and then clickcmd.
- Run the following command to install the client tools:
$
gem install rhcWhen the installation completes, proceed to Section 2.3, “Configuring Client Tools” to configure the client tools using the interactive setup wizard.
2.2.2. Installing on Mac OS X
This section describes how to install the OpenShift Online client tools on Mac OS X operating systems.
2.2.2.2. Installing Required Software
Before installing the OpenShift Online client tools on Mac OS X, you must download and install the following software:
Ruby: interpreted object-oriented scripting language.Git: software version control system.
Installing Ruby
Mac OS X Lion ships with Ruby 1.8.7 preinstalled. Previous versions of OS X included Ruby as part of the Xcode integrated development environment. If you are installing the client tools on a version of OS X that did not ship with Ruby preinstalled, you can install it one of two ways:
- Use the OS X installation CD
- Download and install the Xcode integrated development environment from the Apple website
Alternatively, if you are experienced with Mac OS software development, you can also:
- Download and install
Rubyfrom the MacRuby website, or - Visit http://www.ruby-lang.org/en/downloads/ for help installing
Rubywith homebrew
After
Ruby is installed, run the following command to verify that it has installed correctly:
$ ruby -e 'puts "Welcome to Ruby"'
Welcome to Ruby
Installing Git
Although there are a number of options available to install Git version control on Mac OS X, Red Hat
recommends to download and install the latest version from here: http://code.google.com/p/git-osx-installer/.
When installation is complete, run the following command to verify that
Git has installed correctly:
$ git --version
git version 1.7.11.1
where the version number returned is the version that was installed.
2.2.2.3. Installing Client Tools
When
Ruby and Git have been successfully installed, run the following command to install the client tools:
$ sudo gem install rhc
When the installation completes, proceed to Section 2.3, “Configuring Client Tools” to configure the client tools using the interactive setup wizard.
2.2.3. Installing on Ubuntu and Debian
This section describes how to install the OpenShift Online client tools on Ubuntu or other Debian distributions. Instructions are also provided to install the necessary software that is required before the client tools can be installed.
2.2.3.1. Prerequisites
- Sudoer or root access
Note
The
sudo command only works if the particular user is listed in the sudoers file. As an alternative to sudo access, you can activate a root terminal with the su command and the root password. If you activate a root terminal, omit sudo from the commands shown in the examples. Be sure to close the root terminal after the installation completes.
2.2.3.2. Installing Required Software
Before installing the OpenShift Online client tools on Ubuntu or other Debian distributions, you must download and install the following software:
Ruby: interpreted object-oriented scripting language.RubyGems: Ruby standard for publishing and managing third party libraries.Git: software version control system.
Installing Ruby
From terminal, run the following command to install Ruby:
$ sudo apt-get install ruby-full
Run the following command to verify that
Ruby has installed correctly:
$ ruby -e 'puts "Welcome to Ruby"'
Welcome to Ruby
Installing RubyGems
Run the following command to install RubyGems:
$ sudo apt-get install rubygems
Installing Git
Run the following command to install Git version control:
$ sudo apt-get install git-core
After installation completes, run the following command to verify that
Git has installed correctly:
$ git --version
git version 1.7.11.1
where the version number returned is the version that was installed.
2.2.3.3. Installing Client Tools
When the required software has been successfully installed, run the following command to install the client tools:
$ sudo gem install rhc
2.2.3.4. Installation Issues and Tips
Executing Client Tool Commands from Any Directory
On Ubuntu and other Debian based distributions, the OpenShift Online client tools by default are stored in the /var/lib/gems/1.8/bin directory. Therefore, all client tool commands must be executed from this directory, and you must append ./ to each command.
However, this behavior can be changed by adding the client tools to the PATH environment variable so that you can run client tool commands from any directory. Run the following command to add the client tools to the PATH environment variable, and make it persistent for an entire terminal session:
$ sudo export PATH=/var/lib/gems/1.8/bin:$PATH
Now you can run client tool commands from any directory in the current Terminal session. Note that you must do this each time you close the current Terminal session and start a new one.
For a more permanent solution, add the
export PATH=/var/lib/gems/1.8/bin:$PATH command to your .bashrc file. Therefore, each time a new Terminal session is started, the client tools are automatically added to the PATH environment variable. You can then run all client tool commands from any directory in Terminal.
Making Client Tools Available to All Users
Initially the OpenShift Online client tools are only available to the user installed them. Run the following command to make the client tools available for all users on an Ubuntu system:
$ sudo ln -s /var/lib/gems/1.8/bin/rhc* /usr/bin/
This creates a symbolic link to the client tools binaries in the default search path, and make the client tools available to all users on that system.
When the installation completes, proceed to Section 2.3, “Configuring Client Tools” to configure the client tools using the interactive setup wizard.
2.2.4. Installing on openSUSE
This section describes how to install the OpenShift Online client tools on openSUSE. Instructions are also provided to install the necessary software that is required before the client tools can be installed.
2.2.4.1. Prerequisites
- Sudoer or root access
Note
The
sudo command only works if the particular user is listed in the sudoers file. As an alternative to sudo access, you can activate a root terminal with the su command and the root password. If you activate a root terminal, omit sudo from the commands shown in the examples. Be sure to close the root terminal after the installation completes.
2.2.4.2. Installing Required Software
Before installing the OpenShift Online client tools on OpenSUSE, you must download and install the following software:
Ruby: interpreted object-oriented scripting language.RubyGems: Ruby standard for publishing and managing third party libraries.Git: software version control system.
Installing Ruby
From terminal, run the following command to install Ruby:
$ sudo zypper install ruby
Run the following command to verify that
Ruby has installed correctly:
$ ruby -e 'puts "Welcome to Ruby"'
Welcome to Ruby
Installing RubyGems
Run the following command to install RubyGems:
$ sudo zypper install rubygems
Installing Git
Run the following command to install Git version control:
$ sudo zypper install git-core
After installation completes, run the following command to verify that
Git has installed correctly:
$ git --version
git version 1.7.11.1
where the version number returned will be the version that was installed.
2.2.4.3. Installing Client Tools
When the required software has been successfully installed, run the following command to install the client tools:
$ sudo gem install rhc
When the installation completes, proceed to Section 2.3, “Configuring Client Tools” to configure the client tools using the interactive setup wizard.
2.2.5. Installing on Fedora
This section describes how to install OpenShift Online client tools on Fedora operating systems.
2.2.5.1. Prerequisites
- Fedora 16 or later
- Sudoer or root access
Note
The
sudo command only works if the particular user is listed in the sudoers file. As an alternative to sudo access, you can activate a root terminal with the su command and the root password. If you activate a root terminal, omit sudo from the commands shown in the examples. Be sure to close the root terminal when the installation process is complete.
2.2.5.2. Installing the Client Tools
There are two ways to install the client tools on Fedora operating systems:
- Install the RPM using YUM package manager
- Install the gem using
gem install
Note
The RPM version of the client tools is not updated as frequently as the gem maintained by the OpenShift Online development team.
Installing with YUM Package Manager
Run the following command to install the client tools and all other required dependencies:
$ sudo yum install rubygem-rhc
Installing with Gem
Run the following command to install Ruby and RubyGems if they are not already installed:
$ sudo yum install rubygems
Run the following command to install the client tools and all other required dependencies:
$ sudo gem install rhc
2.2.5.3. Installation Issues and Tips for Fedora
Automatic Completion Using the Tab Key
The OpenShift Online client tools for Fedora support the automatic completion feature of the bash shell. Run the rhc setup --autocomplete command and follow the instructions to enable automatic completion.
$ rhc setup --autocomplete
You may have to close your current terminal session, and open a new session to automatically source the bash completion script.
If the automatic completion feature is not persistent when you open a new terminal session, the automatic completion script for the client tools must be sourced in the
.bashrc file in your home directory. Do this by adding source /etc/bash_completion.d/rhc to your .bashrc file.
When the installation completes, proceed to Section 2.3, “Configuring Client Tools” to configure the client tools using the interactive setup wizard.
2.2.6. Installing on Red Hat Enterprise Linux
This section describes how to install the OpenShift Online client tools on Red Hat Enterprise Linux operating systems.
2.2.6.1. Prerequisites
- Red Hat Enterprise Linux 6 or later
- Sudoer or root access
RubyandRubyGemsinstalled (includingrubygem-jsonandrubygem-parseconfig)
Note
The
sudo command only works if the particular user is listed in the sudoers file. As an alternative to sudo access, you can activate a root terminal with the su command and the root password. If you activate a root terminal, omit sudo from the commands shown in the examples. Be sure to close the root terminal after the installation completes.
If the
RubyGems package is not already installed, you must enable the Red Hat Enterprise Linux optional repository channel. By enabling the optional channel, the RubyGems package dependencies are automatically resolved during the client tools installation process.
If you are using the Certificate-Based Red Hat Network (RHN) tooling, use the following command to enable the optional channel:
$ sudo yum-config-manager --enable rhel-6-[architecture]-[operating_system]-optional-6
If you are using the classic RHN subscription, use the following command to enable the optional channel:
$ sudo rhn-channel --add --channel=rhel-[architecture]-[operating_system]-optional-6
- architecture: your system architecture. Enter either
i386orx86_64. - operating system: type of operating system installed. Enter either
workstationorserver.
For example, if you have Red Hat Enterprise Linux Workstation 6 or later installed on a 64-bit x86 computer, and you are using the classic Red Hat Network subscription, run the following command to enable the optional repository:
$ sudo rhn-channel --add --channel=rhel-x86_64-workstation-optional-6
2.2.6.2. Installing Client Tools
Ensure that the
RubyGems software package is installed on your system. Otherwise, if your system is registered on RHN, enable the optional repository channel as described in Section 2.2.6.1, “Prerequisites”.
Procedure 2.1. To Install the OpenShift Online Client Tools on Red Hat Enterprise Linux:
- Run the following command to install the client tools:
$
sudo gem install rhc - Update client tools to the latest version:
$
sudo gem update rhc
The following example shows a typical installation on a Red Hat Enterprise Linux operating system. Some information has been removed for clarification purposes.
Example 2.1. Installation Process on Red Hat Operating System
$ sudo gem install rhc
Freeing read locks for locker 0x1: 2360/140216412567296
........
Resolving Dependencies
--> Running transaction check
........
Complete!
2.2.6.3. Installation Issues and Tips for Red Hat Enterprise Linux
Automatic Completion Using the Tab Key
The OpenShift Online client tools for Red Hat Enterprise Linux support the automatic completion feature of the bash shell. Run the rhc setup --autocomplete command and follow the instructions to enable automatic completion.
$ rhc setup --autocomplete
You may have to close your current terminal session, and open a new session to automatically source the bash completion script.
If the automatic completion feature is not persistent when you open a new terminal session, the automatic completion script for OpenShift Online client tools must be sourced in the
.bashrc file in your home directory. Do this by adding source /etc/bash_completion.d/rhc to your .bashrc file.
When the installation completes, proceed to Section 2.3, “Configuring Client Tools” to configure the client tools using the interactive setup wizard.
2.3. Configuring Client Tools
When you have successfully installed the OpenShift Online client tools, they must be configured. The interactive setup wizard walks you through the steps by asking several questions to help you configure the client tools.
Important
You must run the interactive setup wizard after installing the client tools so that your workstation is correctly configured to communicate with the remote OpenShift server.
The following is a sample walk through of the setup wizard, and some general information to assist you with the initial configuration. It assumes you have installed the latest version of the client tools. Use
rhc --version to verify the installed version, or see Section 2.4, “Updating Client Tools” for instructions on how to update the client tools.
Note
The following setup wizard example was run on Windows 7. Screen outputs may vary depending on the operating system.
Starting the Setup Wizard
Run the rhc setup command to launch the setup wizard:
$ rhc setup
OpenShift Client Tools (RHC) Setup Wizard
This wizard will help you upload your SSH keys, set your application namespace, and check that other programs like Git are properly installed.
Login Information
The setup wizard next prompts you for the login credentials that were used to sign up for an OpenShift Online account. Alternatively, you can also use your Red Hat login credentials.
Login to openshift.redhat.com: user@myemail.com Password: password
Authorization Tokens
You are then prompted to generate an authorization token. Answering yes will store a token in your home directory to be used on subsequent requests. When it expires, you are prompted for your password again.
OpenShift Online
can create and store a token on disk which allows to you to access the server without using your password. The key is stored in your home directory and should be kept secret. You can delete the key at any time by running 'rhc logout'.
Generate a token now? (yes|no) yes
Generating an authorization token for this client ... lasts about 1 day
Configuration File
With your login credentials, the setup wizard creates the express.conf configuration file in your home directory. In the following example, the express.conf file is created in the C:\Users\User1\.openshift directory.
Saving configuration to C:\Users\User1\.openshift\express.conf ... done
SSH Keys
Next, the setup wizard configures the SSH keys so that your system can authenticate with the remote server. Because this is the initial configuration, it is assumed no existing SSH keys are found on your system. Therefore, the setup wizard generates a new pair of SSH keys, named id_rsa and id_rsa.pub, and saves them in your home directory. In the following example the SSH keys are generated and saved in the C:\Users\User1\.ssh directory.
No SSH keys were found. We will generate a pair of keys for you. Created: C:\Users\User1\.ssh\id_rsa.pubAfter the new SSH keys are generated, the public key,
id_rsa.pub, must be uploaded to the OpenShift Online server to authenticate your system to the remote server. Enter a name to use for your key, or leave it blank to use the default name. In the following example the default name is used.
Your public ssh key must be uploaded to the OpenShift server to access code. Upload now? (yes|no) yes Since you do not have any keys associated with your OpenShift account, your new key will be uploaded as the 'default' key Uploading key 'default' from C:\Users\User1\.ssh\id_rsa.pub ... done
Installed Software
The setup wizard verifies if Git version control software is installed on your system. Git is required to create and deploy applications to the OpenShift Online cloud environment. It is assumed that all the required software for your operating system is already installed as described in the earlier sections of this document. In the example below, the setup wizard verifies that Git for Windows is installed correctly.
In order to fully interact with OpenShift you will need to install and configure a git client if you have not already done so. Documentation for installing other tools you will need for OpenShift can be found at https://openshift.redhat.com/community/developers/install-the-client-tools We recommend these free applications: * Git for Windows - a basic git command line and GUI client https://github.com /msysgit/msysgit/wiki/InstallMSysGit * TortoiseGit - git client that integrates into the file explorer http://code. google.com/p/tortoisegit/
Domain
The setup wizard next verifies whether a domain already exists for your cloud environment. The example below assumes that a domain does not exist, and one must be created. If you did create a domain when you signed up for an OpenShift Online account, it is displayed here. To create a domain at this time, enter the desired name when prompted. Alternatively, you can create a domain using the OpenShift Online Management Console, or using the rhc domain create command later. The domain named MyDomain is created in the following example.
Checking for a domain ... none Your domain is unique to your account and is the suffix of the public URLs we assign to your applications. You may configure your domain here or leave it blank and use 'rhc domain create' to create a domain later. You will not be able to create applications without first creating a domain. Please enter a domain (letters and numbers only) |<none>|: MyDomain Your domain name 'MyDomain' has been successfully created
Important
A domain must be created before you can create OpenShift Online applications.
Applications
Finally, the setup wizard verifies whether any applications exist under your domain. Any applications created with the Management Console are displayed here. In the example below, no applications have been created. In this case the setup wizard shows the types of applications that can be created with the associated commands. The setup wizard then completes by displaying the current gear consumption along with the gear sizes available to the given user.
Checking for applications ... none Run 'rhc app create' to create your first application. Do-It-Yourself rhc app create <app name> diy-0.1 JBoss Application Server 7.1 rhc app create <app name> jbossas-7 JBoss Enterprise Application Platform 6.0 rhc app create <app name> jbosseap-6.0 Jenkins Server 1.4 rhc app create <app name> jenkins-1.4 Node.js 0.10 rhc app create <app name> nodejs-0.10 PHP 5.3 rhc app create <app name> php-5.3 PHP 5.4 rhc app create <app name> php-5.4 Perl 5.10 rhc app create <app name> perl-5.10 Python 2.6 rhc app create <app name> python-2.6 Python 2.7 Community Cartridge rhc app create <app name> python-2.7 Python 3.3 Community Cartridge rhc app create <app name> python-3.3 Ruby 1.8 rhc app create <app name> ruby-1.8 Ruby 1.9 rhc app create <app name> ruby-1.9 Ruby 2.0 rhc app create <app name> ruby-2.0 Tomcat 6 (JBoss EWS 1.0) rhc app create <app name> jbossews-1.0 Tomcat 7 (JBoss EWS 2.0) rhc app create <app name> jbossews-2.0 Zend Server 5.6 rhc app create <app name> zend-5.6 You are using 0 of 3 total gears The following gear sizes are available to you: small Your client tools are now configured.
The OpenShift Online client tools are now configured on your system.
2.4. Updating Client Tools
If the client tools were installed with the
gem install method, run the gem update command to update the client tools:
$ gem update rhc
Alternatively, if the client tools were installed with the
yum install method, run the yum update command to update the client tools, and replace packagename with rubygem-rhc for Fedora or rhc for Red Hat Enterprise Linux:
$ yum update packagename2.5. Where To Go From Here
Visit the Get Started on OpenShift web page to get more information and access the OpenShift Online quick start guides. The quick start guides help you create and deploy applications, and provide information on managing your OpenShift Online cloud environment.
Further information on creating, deploying, and managing applications can also be found in the OpenShift Online User Guide at https://access.redhat.com/site/documentation.
| Revision History | |||||
|---|---|---|---|---|---|
| Revision 1.0.50-0 | Mon 15 Sep 2014 | ||||
| |||||
| Revision 1.0.36-0 | Thu Nov 28 2013 | ||||
| |||||
| Revision 1.0.31-0 | Tue Aug 06 2013 | ||||
| |||||
| Revision 1.0.29-3 | Thu Jun 13 2013 | ||||
| |||||






