[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24491:
--------------------------------
Fix Version/s: 4.5.1.AM2
(was: 4.5.x)
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.1.AM2
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-24491:
-----------------------------------
Assignee: Rob Stryker
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24783:
--------------------------------
Fix Version/s: 4.5.1.AM1
(was: 4.5.x)
> Update default registry url for cdk 3
> -------------------------------------
>
> Key: JBIDE-24783
> URL: https://issues.jboss.org/browse/JBIDE-24783
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM1
>
>
> Yesterday I started cdk 3 and it seemed to start ok, but was not really ok.
> The registry command didn't really work:
> {code}
> $ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> The result is that the openshift connection details showed this under Image Registry URL:
> https://hub.openshift.rhel-cdk.10.1.2.2.xip.io
> This seems like the default value for cdk 2. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24873:
-------------------------------------
I've made a commit to the as.mgmt itests stuff. To run it in a single-runtime mode, do the following:
mvn clean install -Djbosstools.test.jre.8=/home/rob/apps/java/java8/jdk1.8.0_05/ -Djbosstools.test.singleruntime.location=/home/rob/apps/jboss/unzipped/wildfly-10.1.0.Final.zip.expanded/ -Djbosstools.test.jboss.home.10.1=/home/rob/apps/jboss/unzipped/wildfly-10.1.0.Final.zip.expanded/
In summary, set the one jdk / jre flag that's required for the runtime type. Also set the -Djbosstools.test.singleruntime.location flag to a proper runtime location, AND set the -Djbosstools.test.jboss.home.xxxxx flag (depending on the runtime) to the same value.
I realize this seems a bit redundant, but it's what I have for now. Let's see if we can make it work.
> Add management itests to eap jbds compatibility jenkins job
> -----------------------------------------------------------
>
> Key: JBIDE-24873
> URL: https://issues.jboss.org/browse/JBIDE-24873
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> The EAP team would like us to add this test
> org.jboss.tools.as.management.itests
> to their compatibility job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
> details here: EAP7-194
> The test to be added is run here:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cc: [~rob.stryker]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off livenessProbe.periodSecond property during debug session
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24868 at 8/22/17 5:16 PM:
-------------------------------------------------------------------
[~rhuss] [~aurelien.pupier] if I understand the documentation right there seem to be no default for the lifenessProbe. There seem to exist 2 strategies to achieve such a probe: a freely custiomizable one and a http based approach. The http variant seem to have a freely definable url. I had a quick look at the nodejs-mongodb template and couldn't find such a check.
What are we in tools supposed to do? Parse pods and find out if and what method is being used? Shouldnt we have settings in the docker image metadata?
was (Author: adietish):
[~rhuss] [~aurelien.pupier] if I understand the documentation right there seem to be no default for the lifenessProbe. There seem to exist 2 way to achieve it and the http approach having a variable url for the check. I had a quick look at the nodejs-mongodb template and couldn't find such a check.
What are we in tools supposed to do? Parse pods and find out which method and what url are being used? Shouldnt we provide settings in the docker image metadata?
> Server adapter: Switch off livenessProbe.periodSecond property during debug session
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-24868
> URL: https://issues.jboss.org/browse/JBIDE-24868
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.x
>
>
> it will avoid to have "debug connections always killed after 30s staying in a breakpoint"
> see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion
> k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4513) Align Breadcrumbs in the UI
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-4513?page=com.atlassian.jira.plugin.... ]
Mohit Suman commented on JBDS-4513:
-----------------------------------
Hi [~crobson]
For the breadcrumbs part, I have made the alignment in the centre just on the lines of the wizard layout we have in patternfly. http://www.patternfly.org/pattern-library/communication/wizard/
The previous design had the start of the breadcrumbs from the corner of the page. Please review and let me know if this works. I have attached the new mockup.
> Align Breadcrumbs in the UI
> ---------------------------
>
> Key: JBDS-4513
> URL: https://issues.jboss.org/browse/JBDS-4513
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Mohit Suman
> Assignee: Mohit Suman
> Priority: Minor
> Fix For: 11.1.0.AM1
>
> Attachments: breadcrumb-fix.png
>
>
> The current breadcrumbs start from the corner of the page layout. Making it more centric to the page in accordance to the wizard mode we have in patternfly wizard template.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4513) Align Breadcrumbs in the UI
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-4513?page=com.atlassian.jira.plugin.... ]
Mohit Suman reassigned JBDS-4513:
---------------------------------
Fix Version/s: 11.1.0.AM1
Story Points: 2
Attachment: breadcrumb-fix.png
Sprint: devex #136 August 2017
Affects: User Experience
Assignee: Mohit Suman
> Align Breadcrumbs in the UI
> ---------------------------
>
> Key: JBDS-4513
> URL: https://issues.jboss.org/browse/JBDS-4513
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Mohit Suman
> Assignee: Mohit Suman
> Priority: Minor
> Fix For: 11.1.0.AM1
>
> Attachments: breadcrumb-fix.png
>
>
> The current breadcrumbs start from the corner of the page layout. Making it more centric to the page in accordance to the wizard mode we have in patternfly wizard template.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4513) Align Breadcrumbs in the UI
by Mohit Suman (JIRA)
Mohit Suman created JBDS-4513:
---------------------------------
Summary: Align Breadcrumbs in the UI
Key: JBDS-4513
URL: https://issues.jboss.org/browse/JBDS-4513
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: platform-installer
Reporter: Mohit Suman
Priority: Minor
The current breadcrumbs start from the corner of the page layout. Making it more centric to the page in accordance to the wizard mode we have in patternfly wizard template.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months