I don't see WildFly in the list of cartridges that can be used to create an application using rhc command. Here is the complete list shown: Short Name Full name ========== ========= 10gen-mms-agent-0.1 10gen Mongo Monitoring Service Agent cron-1.4 Cron 1.4 diy-0.1 Do-It-Yourself 0.1 jbossas-7 JBoss Application Server 7 jboss-dv-6.0.0 JBoss Data Virtualization 6 jbosseap-6 JBoss Enterprise Application Platform 6 jenkins-client-1 Jenkins Client jenkins-1 Jenkins Server mongodb-2.4 MongoDB 2.4 mysql-5.1 MySQL 5.1 mysql-5.5 MySQL 5.5 nodejs-0.10 Node.js 0.10 nodejs-0.6 Node.js 0.6 metrics-0.1 OpenShift Metrics 0.1 perl-5.10 Perl 5.10 php-5.3 PHP 5.3 zend-5.6 PHP 5.3 with Zend Server 5.6 php-5.4 PHP 5.4 zend-6.1 PHP 5.4 with Zend Server 6.1 phpmyadmin-4 phpMyAdmin 4.0 postgresql-8.4 PostgreSQL 8.4 postgresql-9.2 PostgreSQL 9.2 python-2.6 Python 2.6 python-2.7 Python 2.7 python-3.3 Python 3.3 rockmongo-1.1 RockMongo 1.1 ruby-1.8 Ruby 1.8 ruby-1.9 Ruby 1.9 ruby-2.0 Ruby 2.0 switchyard-0 SwitchYard 0.8.0 jbossews-1.0 Tomcat 6 (JBoss EWS 1.0) jbossews-2.0 Tomcat 7 (JBoss EWS 2.0) jboss-vertx-2.1 Vert.x 2.1 haproxy-1.4 Web Load Balancer However this app can be created using the console. This is a discrepancy and needs to be fixed.
Jake / Nick, looks like although WildFly is a community cartridge it could be added to the cartridges list on the broker, the same way we have Vert.x. Thoughts?
We're discussing this in email but if we want it registered i can take care of it.
I've created a card to track this RFE: https://trello.com/c/7FAVAu7l/328-register-wildfly-cartridge
Yeah let's do it. Right now we have a QuickStart as a hack to get that in the console. Also, is this OpenShift Team supported?
Not really. I mean we'll give it more attention than a random community cart, and work with the wildfly team as needed, but it's not an official cartridge like jbossas/eap.
Reopening the as the cartridge is still not available. Here is what I see: javaee7-samples> rhc app-create chatserver wildfly-wildfly-8 Short Name Full name ========== ========= 10gen-mms-agent-0.1 10gen Mongo Monitoring Service Agent cron-1.4 Cron 1.4 diy-0.1 Do-It-Yourself 0.1 jbossas-7 JBoss Application Server 7 jboss-dv-6.0.0 JBoss Data Virtualization 6 jbosseap-6 JBoss Enterprise Application Platform 6 jenkins-client-1 Jenkins Client jenkins-1 Jenkins Server mongodb-2.4 MongoDB 2.4 mysql-5.1 MySQL 5.1 mysql-5.5 MySQL 5.5 nodejs-0.10 Node.js 0.10 perl-5.10 Perl 5.10 php-5.3 PHP 5.3 php-5.4 PHP 5.4 zend-6.1 PHP 5.4 with Zend Server 6.1 phpmyadmin-4 phpMyAdmin 4.0 postgresql-8.4 PostgreSQL 8.4 postgresql-9.2 PostgreSQL 9.2 python-2.6 Python 2.6 python-2.7 Python 2.7 python-3.3 Python 3.3 rockmongo-1.1 RockMongo 1.1 ruby-1.8 Ruby 1.8 ruby-1.9 Ruby 1.9 ruby-2.0 Ruby 2.0 switchyard-0 SwitchYard 0.8.0 jbossews-1.0 Tomcat 6 (JBoss EWS 1.0) jbossews-2.0 Tomcat 7 (JBoss EWS 2.0) jboss-vertx-2.1 Vert.x 2.1 haproxy-1.4 Web Load Balancer There are no cartridges that match 'wildfly-wildfly-8'.
Which environment are you looking at? I don't think this has made it to prod yet, may be another day or two.
OpenShift Online. Can we keep this open until we see the changes live ?
Sure. Vojtech please set this back to ON_QA once the release finishes.
Wildfly and Vert.x have been deployed in STG and will go out as part of the PROD deploy. $ rhc cartridges --config ~/.openshift/express-stg.conf jbossas-7 JBoss Application Server 7 web jboss-dv-6.0.0 (!) JBoss Data Virtualization 6 web jbosseap-6 (*) JBoss Enterprise Application Platform 6 web jenkins-1 Jenkins Server web nodejs-0.10 Node.js 0.10 web perl-5.10 Perl 5.10 web php-5.3 PHP 5.3 web php-5.4 PHP 5.4 web zend-6.1 PHP 5.4 with Zend Server 6.1 web python-2.6 Python 2.6 web python-2.7 Python 2.7 web python-3.3 Python 3.3 web ruby-1.8 Ruby 1.8 web ruby-1.9 Ruby 1.9 web ruby-2.0 Ruby 2.0 web jbossews-1.0 Tomcat 6 (JBoss EWS 1.0) web jbossews-2.0 Tomcat 7 (JBoss EWS 2.0) web jboss-vertx-2.1 (!) Vert.x 2.1 web jboss-vertx-2.1.2 (!) Vert.x 2.1 web jboss-wildfly-8 (!) WildFly Application Server 8.1.0.Final web diy-0.1 Do-It-Yourself 0.1 web 10gen-mms-agent-0.1 10gen Mongo Monitoring Service Agent addon cron-1.4 Cron 1.4 addon jenkins-client-1 Jenkins Client addon mongodb-2.4 MongoDB 2.4 addon mysql-5.1 MySQL 5.1 addon mysql-5.5 MySQL 5.5 addon phpmyadmin-4 phpMyAdmin 4.0 addon postgresql-8.4 PostgreSQL 8.4 addon postgresql-9.2 PostgreSQL 9.2 addon rockmongo-1.1 RockMongo 1.1 addon switchyard-0 SwitchYard 0.8.0 addon haproxy-1.4 Web Load Balancer addon
jboss-wildfly-8 is a confusing name. JBoss is used only for commercial offering, WildFly is only community project. Similarly, jboss-vertx is confusing name as well. The fact that these projects are in middleware should not be confused with the cartridge names.
the "jboss" piece is the vendor who created the cartridge, in this case the vendor is the JBoss organization within Red Hat. (The other cartridges do not have this because they are the default redhat vendor, because they are created/maintained by the OpenShift organization directly).
This is an internal piece of information and the user of these cartridges does not need to know that. Vert.x does not need any component of jboss and so associating that with jboss is very confusing. I don't see a need of including author/owner of a cartridge in the name itself. This can be stored in some other meta tag. The naming seems to be inconsistent anyway: jbossas-7 JBoss Application Server 7 web jboss-dv-6.0.0 (!) JBoss Data Virtualization 6 web jbosseap-6 (*) JBoss Enterprise Application Platform 6 web jbossews-1.0 Tomcat 6 (JBoss EWS 1.0) web jbossews-2.0 Tomcat 7 (JBoss EWS 2.0) web jboss-vertx-2.1 (!) Vert.x 2.1 web jboss-vertx-2.1.2 (!) Vert.x 2.1 web jboss-wildfly-8 (!) WildFly Application Server 8.1.0.Final web Some are using jboss-XXX while others are jbossXXX.
As I said, the format is vendor-cartridgename. "jbosseap" is a cartridge named "jbosseap" with a vendor of redhat(the openshift team). "jboss-wildfly" is a cartridge named "wildfly" with a vendor of "jboss" And vendor information is not internal information, it's potentially relevant to a user who wants to know who provided a given cartridge they are considering using.
Vrified with PROD jboss-wildfly-8 is shown in prod now. # rhc cartridge-list jbossas-7 JBoss Application Server 7 web jboss-dv-6.0.0 (!) JBoss Data Virtualization 6 web jbosseap-6 (*) JBoss Enterprise Application Platform 6 web jbossews-1.0 Tomcat 6 (JBoss EWS 1.0) web jbossews-2.0 Tomcat 7 (JBoss EWS 2.0) web jboss-vertx-2.1 (!) Vert.x 2.1 web jboss-wildfly-8 (!) WildFly Application Server 8.1.0.Final web diy-0.1 Do-It-Yourself 0.1 web
Confirmed, can see the value.