[jbosstools-issues] [JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

[Denis Golovin (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Golovin updated JBIDE-14341:
----------------------------------

    Labels:   (was: to_jbt_4.2.x)

    
> Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-14341
>                 URL: https://issues.jboss.org/browse/JBIDE-14341
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>            Reporter: Joe Fernandes
>            Priority: Optional
>             Fix For: 4.2.x
>
>
> OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. 
> This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE.  This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings.
> Some key information on the new OpenShift v2 cartridge format:
> -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June).  All current cartridges are being migrated to the new v2 cartridge format.
> -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them.  That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL.  That is really the core feature of being able to start a cartridge ecosystem.
> -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular.  Main goal there was to try and simplify, cleanup and better document the process.  H
> -Here are some of the docs:
> Technical docs:
> https://github.com/openshift/origin-server/blob/master/node/README.writing_cartridges.md
> https://github.com/openshift/origin-server/blob/master/node/README.node_module_design.md
> https://github.com/openshift/origin-server/blob/master/node/README.writing_applications.md
> Getting Started:
> https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1
> https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2
> If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-and-puppet) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know.

--
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