[jbosstools-issues] [JBoss JIRA] (JBIDE-11073) OpenShift Express Tool: Create a way to invoke rhc-port-forward functionality which enables users to debug their cloud environments with their local tools
Andre Dietisheim (JIRA)
jira-events at lists.jboss.org
Tue May 8 05:07:19 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andre Dietisheim closed JBIDE-11073.
------------------------------------
Resolution: Done
> OpenShift Express Tool: Create a way to invoke rhc-port-forward functionality which enables users to debug their cloud environments with their local tools
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11073
> URL: https://issues.jboss.org/browse/JBIDE-11073
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Environment: OpenShift Express Tools (on Eclipse)
> Reporter: Nam Duong
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 3.3.0.Beta3
>
> Attachments: 2012-04-13 12.08.bmml, 2012-04-13 12.08.bmml, 2012-04-13 12.08.bmml, 2012-04-13 12.08.png
>
>
> If an OpenShift node that's hosting the user's app is running mysql on port 3306 on 126.0.2.17, you can't access that externally. You need to ssh into the node to run mysql or you need to embed phpmyadmin. rhc-port-forward allows you to access that port and other available ports.
> {quote}
> Usage: /usr/bin/rhc-port-forward
> Forward remote ports to the workstation
> -l | --rhlogin rhlogin Red Hat login (RHN or OpenShift login with OpenShift Express access) (Default: nduong+mac at redhat.com)
> -a | --app Target application (required)
> -p | --password password RHLogin password (optional, will prompt)
> -d | --debug Print Debug info
> -h | --help Show Usage info
> --config path Path of alternate config file
> --timeout # Timeout, in seconds, for connection
> {quote}
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list