[jbosstools-issues] [JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

[Dmitrii Bocharov (JIRA)]

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

Dmitrii Bocharov commented on JBIDE-22965:
------------------------------------------

As i was asked on the last meeting, i'm providing here all the information about current status of the JIRA.

h3. Here is the step-by-step instructions of how i tested proxy for CDK. So if anything is not clear from the description of the current JIRA, come here.
I tested on Fedora 24, used libvirt box
1) As a sudo user do: _iptables-save > iptables-rules_
2) Run the script [^create_proxy-test_env.sh], which was created according to https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25
3) Do _service iptables restart_
4) According to [this description|https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/docs/installing.rst#setting-up-adb-behind-an-http-proxy] set env vriables:
export PROXY="10.70.49.109:3128"
export PROXY_USER="ask me if you need it"
export PROXY_PASSWORD="sk me if you need it"
5) Then set _http_proxy_ and _https_proxy_ env vars - they have different meaning from the vars described in 4. See the quote from [~lalatendum] in the JIRA description
export http_proxy="10.70.49.109:3128"
export https_proxy="10.70.49.109:3128"
6) Do _service libvirtd restart_, as this is a know bug for Fedora/libvirt and it won't work without restarting libvirtd
7) Then i ran _vagrant up_, which was finished fine, even with registration and i could access OS via oc
8) I ran the server adapter for CDK, did registration, OS and docker connection were created and was able to create docker image and deploy it to OS.
9) Do _iptables-restore iptables-rules_ and _service iptables restart_ to restore all the network data that was before step 2.

[~lalatendum], [~rob.stryker], [~kumarpraveen], [~jeffmaury] is everything correct? Or did i configured and test anything wrong?

h3. The last status of email correspondence, which was "Sounds good" for many :)
{quote}
I discussed with [~mmalina], [~mlabuda], [~rhopp] and [~odockal] our plans on testing CDK.  The first most important steps that are currently in progress and need to be finished are
1) create integration tests for CDK
2) solve problem with Nested virtualization in Central CI: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151

After these problems will be solved, we'll think about dedicating machines for testing proxy. We have 2 machines in Brno that can be installed in our Mini Lab. In our opinion one will be for Windows and the other one for RHEL.
{quote}

As i can see, step 1 is done: https://github.com/jbosstools/jbosstools-integration-tests/tree/master/plugins/org.jboss.tools.cdk.reddeer
However last messages of the issue from step 2 are not so good. That's why we can't run even CDK integration tests without proxy on central CI. When we can, we'll need to do the same but on the machines with configured proxies.

[~akazakov], [~ldimaggio], [~budhrg], does it still sound good or do we need to plan/do anything else?

h3. The other bugs and testing proxy on other operating systems and VMs.
[~jeffmaury], [~adietish], [~lalatendum] are there any? How did you test proxy? And how did you configured the environment step-by-step?

I'm also adding [~hardy.ferentschik] and [~optak].
Please, everybody feel free to comment and add any information about testing CDK proxy here. And let all discussions be here, as it turned out that emails are easily forgotten and are hard to give the link to.

> CDK tools should work behind proxy
> ----------------------------------
>
>                 Key: JBIDE-22965
>                 URL: https://issues.jboss.org/browse/JBIDE-22965
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: cdk
>            Reporter: Alexey Kazakov
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 4.4.2.AM2
>
>         Attachments: create_proxy-test_env.sh
>
>
> Proxy support has been added in CDK vagrant box and in vagrant-registration plugin.
> We should make sure our CDK tooling supports it too.
> In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/docs/installing.rst#setting-up-adb-behind-an-http-proxy
> Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982
> + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25
> Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]:
> {noformat}
> lalatenduM: we exepect customers workstation is configured to porixy server 
> that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work 
> lalatenduM: on a customer worksttaion 
> lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information
> lalatenduM: vagrant-registration uses subscription manager for registraton
> lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/docs/using.rst#using-the-adb-behind-http-proxy it will make openshift, docker and vagrant-registration aware of proxy server info
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)