[jboss-jira] [JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images

[Kevin Earls (JIRA)]

    [ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555587#comment-13555587 ] 

Kevin Earls commented on SWSQE-113:
-----------------------------------

Hi [~gbaufake] and [~fbrychta].  I've created the "jaeger-test" project on b11 for this, but I need a couple of modifications in order to be able to deploy ElasticSearch correctly.  These are:

1. oc adm policy add-role-to-user admin system:serviceaccount:jaeger-test:jenkins
2. I'm not sure exactly how to do this, as my notes apply to minishift.  These were: "minishift ssh 'echo "sysctl -w vm.max_map_count=262144" | sudo tee -a /var/lib/boot2docker/bootlocal.sh'".  Obviously we aren't running minishift here, but I need the same changes applied.  Unfortunately I think this may require a cluster restart.



> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
>                 Key: SWSQE-113
>                 URL: https://issues.jboss.org/browse/SWSQE-113
>             Project: Kiali QE
>          Issue Type: QE Task
>            Reporter: Kevin Earls
>            Assignee: Filip Brychta
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images.  I have already started working with [~fbrychta] but we have not completely resolved this yet.  
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible.  In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)