[
https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi...
]
Mark Drilling edited comment on JBIDE-16720 at 3/10/14 3:27 PM:
----------------------------------------------------------------
Heres explanation from Ben Parees (OpenShift) on the current state of cartridges
v========================================v
So essentially there are 3 types of cartridges now:
1) system cartridges (rpm based, maintained by openshift team) - appear on the web page
and in rhc cartridge list
2) imported downloadable cartridges (downloadable cartridge, but imported so they show up
in the same places as system cartridges)
3) non-imported downloadable cartridges - these do not explicitly show up anywhere. The
historic way to promote a downloadable cartridge was to create a quickstart based on it,
and promote the quickstart.
Unfortunately there is currently no obvious distinction for a user between #1 and #2.
Both the site and command line indicate cartridges which do not receive automatic security
updates, which for now is effectively the same as being an imported downloadable
cartridge, but it's not explicit that the cartridge is downloadable.
========================================
I think 2) is a new feature and seems to be the way they prefer to register the cartridges
now. I'm not sure how the import works, but it will apparently then show up same as
system cartridges. If that is the case, it will be available in the wizard's
drop-down with everything else.
And yes about the localhost issue. (Can't use the openshift hostname because of the
port forwarding.)
was (Author: mdrillin):
Heres explanation from Ben Parees (OpenShift) on the current state of cartridges
v========================================v
So essentially there are 3 types of cartridges now:
1) system cartridges (rpm based, maintained by openshift team)
- appear on the web page and in rhc cartridge list
2) imported downloadable cartridges (downloadable cartridge, but imported so they show up
in the same places as system cartridges)
3) non-imported downloadable cartridges - these do not explicitly show up anywhere. The
historic way to promote a downloadable cartridge was to create a quickstart based on it,
and promote the quickstart.
Unfortunately there is currently no obvious distinction for a user between #1 and #2.
Both the site and command line indicate cartridges which do not receive automatic security
updates, which for now is effectively the same as being an imported downloadable
cartridge, but it's not explicit that the cartridge is downloadable.
^========================================^
I think 2) is a new feature and seems to be the way they prefer to register the cartridges
now. I'm not sure how the import works, but it will apparently then show up same as
system cartridges. If that is the case, it will be available in the wizard's
drop-down with everything else.
And yes about the localhost issue. (Can't use the openshift hostname because of the
port forwarding.)
Allow easier access to openshift operations from jboss servers
--------------------------------------------------------------
Key: JBIDE-16720
URL:
https://issues.jboss.org/browse/JBIDE-16720
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift, server
Affects Versions: 4.1.1.Final
Reporter: Mark Drilling
We currently have a couple issues with connecting to an OpenShift Data Virtualization
instance from the tooling. I'm aware that issues are being addressed for future
release, others I'm not sure. This is intended to help guide your development to
accommodate this use case.
Our expected usage with Data Virtualization is a bit different than some others. With DV
we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV
instance as a remote server. We typically would not deploy using git push.
Currently, we connect to an OpenShift DV instance like this:
1) Deploy DV cartridge via OpenShift web console.
2) Port forward from command line using rhc port-forward
3) Set up EAP server instance in the tooling, mark as externally managed and start it.
From there we can connect to the DV instance and continue with modeling and deployments in
Teiid Designer perspective
The issues we observed:
1) Creation of the OpenShift 'server' forces a git repo to be copied locally.
We'd like to simply create the 'OpenShift server' without cloning the repo.
2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is
now (or will soon) allow downloadable carts to be registered, so this problem should be
solved as the cart will show up in the cartridge list.
Our current method of connecting is ok for now, but a simpler usage of the OpenShift
server adapter would allow us to more easily manage the instance (e.g. port-forward
without going to the command line, viewing logs, etc.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira