红帽全球峰会此内容没有您所选择的语言版本。
Chapter 4. New Features and Enhancements
4.1. Improved OpenShift 3 and Docker Tools
4.1.1. OpenShift Server Adapter Enhanced Flexibility
OpenShift server adapter is a great tool that allows developers to synchronize local changes in the Eclipse workspace with running pods in the OpenShift cluster. It also allows you to remotely debug those pods when the server adapter is launched in the Debug mode. The supported stacks are Java and NodeJS.
As pods are ephemeral OpenShift resources, the server adapter definition was earlier based on an OpenShift service resource and the pods were then dynamically computed from the service selector.
This has a major drawback as it allows to use this feature only for pods that are part of a service, which may be logical for Web based applications as a route (and thus a service) is required in order to access the application.
It is now possible to create a server adapter from the following OpenShift resources:
- Service (as before)
- Deployment config
- Replication controller
- Pod
If a server adapter is created from a pod, it will be created from the associated OpenShift resource in the preferred order:
- Service
- Deployment config
- Replication controller
The OpenShift Explorer used to display OpenShift resources that were linked to a service. This has been enhanced. It now displays resources linked to a deployment configuration or replication controller. The following image shows an example of a deployment with no service i.e. a deployment configuration.
An OpenShift server adapter can be created from different kind of resources. The type of associated resource is displayed when creating the OpenShift server adapter.
Once created, the type of OpenShift resource adapter is also displayed in the Servers view.
This information is also available from the server editor.
Related JIRA: JBIDE-23490
When you use the OpenShift tooling to connect to an OpenShift API server, the certificate of the OpenShift API server is first validated. The connection is established if the issuer authority is a known one. If the issuer is an unknown one, a validation dialog is first shown to the user with the details of the OpenShift API server certificate and the details of the issuer authority. The connection is established if the user accepts it. There is also an option to store the certificate in a database so that next time a connection is attempted to the same OpenShift API server, the certificate will be considered valid and no validation dialog will be show again.
Security vulnerabilty existed due to the wrongly stored certificate. Not all attributes, but it was partially stored; we may interpret that in these cases a certificate that was not meant to be validated was validated.
The format of the certificate database was changed. As the certificates stored in the previous database were not entirelly stored, there was no way to provide a migration path. As a result, after the upgrade, the certificate database will be empty. So, if you had previously accepted some certificates, then you need to accept them again and fill the certificate database again.
Related JIRA: JBIDE-24312
4.2. CDK 3 Server Adapter
The CDK 3 server adapter that was released as Technology Preview because CDK 3 was not officially released, is now officiallly available. While the server adapter has limited functionality, it is able to start and stop the CDK virtual machine via its minishift binary. Press Ctrl+3 (Cmd+3 on OSX) and type CDK to display a command to setup and/or launch the CDK server adapter. You should see the old CDK 2 server adapter along with the new CDK 3 one, labeled Red Hat Container Development Kit 3.
To set a new server, set the credentials for your Red Hat account, the location of the CDK minishift binary file, and the type of virtualization hypervisor.
After its creation, the new CDK Server adapter is created and listed in the Servers view.
After the server is started, Docker and OpenShift connections appear in their respective views, allowing the user to quickly create a new Openshift application and begin developing their AwesomeApp in a highly-replicatable environment.
Related JIRA: JBIDE-23505
4.3. OpenShift Container Platform 3.5 Support
OpenShift Container Platform (OCP) 3.5 is announced by Red Hat. For details, see Red Hat Brings Kubernetes to New Application Workloads with Latest Version of Red Hat OpenShift Container Platform. JBoss Developer Studio is validated against OCP 3.5.
4.3.1. OpenShift Server Adapter Extensibility
The OpenShift server adapter had support for EAP/Wildfly and NodeJS based deployments. This server adpater also synchronizes local workspace changes to remote deployments on OpenShift which have been standardized through images metadata (labels). But each runtime has its own specifics. For example, Wildfly/EAP deployments require that a re-deploy trigger is sent after the files have been synchronized.
In order to reduce the technical debt and allow support for other runtimes (many in the microservice world), the OpenShift server adapter is refractored so that each runtime specific is now isolated and that it will be easy and safe to add support for new runtime.
For in-depth description, see this wiki page.
Related JIRA: JBIDE-23900
4.3.2. Pipeline Builds Support
Pipeline based builds are now supported by the OpenShift tooling. When creating an application, if using a template, if one of the builds is based on pipeline, you can view the detail of the pipeline.
When your application is deployed, you can see the details of the build configuration for the pipeline based builds.
We are improving the pipeline support in the OpenShift tooling.
Related JIRA: JBIDE-24146
4.4. Update of Docker Client
The level of the underlying com.spotify.docker.client plug-in used to access the Docker daemon has been upgraded to 3.6.8.
4.4.1. Run Image Network Support
A new page has been added to the Docker Run Image wizard and Docker Run Image Launch configuration that allows the end-user to specify the network mode to use. A user can choose from Default, Bridge, Host, None, Container, or Other. If Container is selected, the user must choose from an active Container to use the same network mode. If Other is specified, a named network can be specified.
4.4.2. Refresh Connection
Users can now refresh the entire connection from the Docker Explorer view. You can refresh the connection in any one of the following two ways:
- Using the right-click context menu from the connection
- Using the Refresh menu button when the connection is selected
4.5. Server Tools
4.5.1. API Change in New Connection Wizard of JMX UI
Extenders must be aware that the API for adding connection types to the New JMX Connection wizard in the JMX Navigator has changed. Specifically, the org.jboss.tools.jmx.ui.providerUI extension point is changed. Previously it had a child element called wizardPage. It now requires a wizardFragment.
A wizardFragment is part of the TaskWizard framework first used in WTP’s ServerTools, which is used throughout JBossTools. This framework allows wizard workflows where the set of pages to be displayed can change based on what selections are made on previous pages.
This change was made as a direct result of a bug caused by the addition of the Jolokia connection type in which some standard workflows could no longer be completed.
This change only affects adopters and extenders, and should have no noticable change for the users, other than that the bug has been fixed.
Related JIRA: JBIDE-24029
4.6. Hibernate Tools
4.6.1. Hibernate Runtime Provider Updates
A number of additions and updates have been performed on the available Hibernate runtime providers.
4.6.2. Hibernate Runtime Provider Updates
The Hibernate 5.0 runtime provider now incorporates Hibernate Core version 5.0.12.Final and Hibernate Tools version 5.0.5.Final.
The Hibernate 5.1 runtime provider now incorporates Hibernate Core version 5.1.4.Final and Hibernate Tools version 5.1.3.Final.
The Hibernate 5.2 runtime provider now incorporates Hibernate Core version 5.2.8.Final and Hibernate Tools version 5.2.2.Final.
Related JIRAs: JBIDE-24281, JBIDE-24279, JBIDE-24272
4.7. Forge Tools
4.7.1. Forge Runtime Updated to 3.6.1.Final
The included Forge runtime is now 3.6.1.Final. Read the official announcement here.
Related JIRA: JBIDE-24189
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}