On Thu, 2013-11-14 at 10:02 -0800, Andrew Grimberg wrote:

Greetings folks,

I finally have the test lab available for access. The current layout is
very similar to the Ericsson lab. I've already allocated access rights
to all folks that have committer status to the Integration project.
Those that have not yet actually logged into Gerrit, or at least haven't
configured an SSH pubkey in Gerrit, will need to do so to be able to
access the lab.

Here's the writeup I've done:

https://wiki.opendaylight.org/view/CrossProject:Integration_Group:ODL_Test_Lab

Please note, I do not presently have any graphical desktop applications
on test01 (the tools system). If you believe we need this please let me
know and I'll go about getting Gnome, Firefox and VNC on it.

Also, having looked over the End to End inventory wiki
( https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin::End_to_End_Inventory ) and seeing that to do OF 1.3 we needed Open vSwitch 1.10 or greater I made sure that 1.11 was installed on our mininet system. Mininet is at v2.0.0 not, 2.1.0 as I've had difficulties getting it to build properly for EL6 thankfully the wiki page there indicates that 2.0.0 should work.

You will notice that I've started attaching slaves to the Jenkins silo.
I've got them tagged as requiring a job be specifically tied to a given
tag for them to accept the job, the reason for this is that the test
systems do not presently have any of the build environments on them so
they can't just share build processing.

One final note, Jenkins has an account on all the VMs with the same
rights as any user that gets shell access, this should make it easier to
build out jobs :)

-Andy-

-----Original Message-----
From: integration-dev-bounces@... [mailto:integration-dev-bounces@...] On Behalf Of Andrew Grimberg
Sent: Thursday, November 14, 2013 10:12 AM
To: integration-dev@...
Subject: Re: [integration-dev] ODL Test lab access

As an additional note, the user facing firewalls on the systems are
still pretty tight. I'll need to know what we need to open to make this
useful to folks. The backside network interfaces have no firewalling so
there won't be anything there for us to deal with.

On Thu, 2013-11-14 at 10:02 -0800, Andrew Grimberg wrote:

Greetings folks,

I finally have the test lab available for access. The current layout is
very similar to the Ericsson lab. I've already allocated access rights
to all folks that have committer status to the Integration project.
Those that have not yet actually logged into Gerrit, or at least haven't
configured an SSH pubkey in Gerrit, will need to do so to be able to
access the lab.

Here's the writeup I've done:

https://wiki.opendaylight.org/view/CrossProject:Integration_Group:ODL_Test_Lab

Please note, I do not presently have any graphical desktop applications
on test01 (the tools system). If you believe we need this please let me
know and I'll go about getting Gnome, Firefox and VNC on it.

Also, having looked over the End to End inventory wiki
( https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin::End_to_End_Inventory ) and seeing that to do OF 1.3 we needed Open vSwitch 1.10 or greater I made sure that 1.11 was installed on our mininet system. Mininet is at v2.0.0 not, 2.1.0 as I've had difficulties getting it to build properly for EL6 thankfully the wiki page there indicates that 2.0.0 should work.

You will notice that I've started attaching slaves to the Jenkins silo.
I've got them tagged as requiring a job be specifically tied to a given
tag for them to accept the job, the reason for this is that the test
systems do not presently have any of the build environments on them so
they can't just share build processing.

One final note, Jenkins has an account on all the VMs with the same
rights as any user that gets shell access, this should make it easier to
build out jobs :)

-Andy-

--
Andrew J Grimberg
Systems Administrator
The Linux Foundation

-----Original Message-----
From: integration-dev-bounces@... [mailto:integration-dev-bounces@...] On Behalf Of Luis Gomez
Sent: Thursday, November 14, 2013 11:48 AM
To: Andrew Grimberg; integration-dev@...
Subject: Re: [integration-dev] ODL Test lab access

Thanks Andrew, Carol and I will take a look on all these this afternoon.

-----Original Message-----
From: integration-dev-bounces@... [mailto:integration-dev-bounces@...] On Behalf Of Andrew Grimberg
Sent: Thursday, November 14, 2013 10:12 AM
To: integration-dev@...
Subject: Re: [integration-dev] ODL Test lab access

As an additional note, the user facing firewalls on the systems are still pretty tight. I'll need to know what we need to open to make this useful to folks. The backside network interfaces have no firewalling so there won't be anything there for us to deal with.

On Thu, 2013-11-14 at 10:02 -0800, Andrew Grimberg wrote:

Greetings folks,

I finally have the test lab available for access. The current layout
is very similar to the Ericsson lab. I've already allocated access
rights to all folks that have committer status to the Integration project.
Those that have not yet actually logged into Gerrit, or at least
haven't configured an SSH pubkey in Gerrit, will need to do so to be
able to access the lab.

Here's the writeup I've done:

https://wiki.opendaylight.org/view/CrossProject:Integration_Group:ODL_
Test_Lab

Please note, I do not presently have any graphical desktop
applications on test01 (the tools system). If you believe we need this
please let me know and I'll go about getting Gnome, Firefox and VNC on it.

Also, having looked over the End to End inventory wiki (
https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin::End_to_End_Inventory ) and seeing that to do OF 1.3 we needed Open vSwitch 1.10 or greater I made sure that 1.11 was installed on our mininet system. Mininet is at v2.0.0 not, 2.1.0 as I've had difficulties getting it to build properly for EL6 thankfully the wiki page there indicates that 2.0.0 should work.

You will notice that I've started attaching slaves to the Jenkins silo.
I've got them tagged as requiring a job be specifically tied to a
given tag for them to accept the job, the reason for this is that the
test systems do not presently have any of the build environments on
them so they can't just share build processing.

One final note, Jenkins has an account on all the VMs with the same
rights as any user that gets shell access, this should make it easier
to build out jobs :)

-Andy-

--
Andrew J Grimberg
Systems Administrator
The Linux Foundation
_______________________________________________
integration-dev mailing list
integration-dev@...
https://lists.opendaylight.org/mailman/listinfo/integration-dev

-----Original Message-----
From: integration-dev-bounces@... [mailto:integration-dev-bounces@...] On Behalf Of Andrew Grimberg
Sent: Thursday, November 14, 2013 10:02 AM
To: integration-dev@...
Subject: [integration-dev] ODL Test lab access

Greetings folks,

I finally have the test lab available for access. The current layout is
very similar to the Ericsson lab. I've already allocated access rights
to all folks that have committer status to the Integration project.
Those that have not yet actually logged into Gerrit, or at least haven't
configured an SSH pubkey in Gerrit, will need to do so to be able to
access the lab.

Here's the writeup I've done:

https://wiki.opendaylight.org/view/CrossProject:Integration_Group:ODL_Test_Lab

Please note, I do not presently have any graphical desktop applications
on test01 (the tools system). If you believe we need this please let me
know and I'll go about getting Gnome, Firefox and VNC on it.

Also, having looked over the End to End inventory wiki
( https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin::End_to_End_Inventory ) and seeing that to do OF 1.3 we needed Open vSwitch 1.10 or greater I made sure that 1.11 was installed on our mininet system. Mininet is at v2.0.0 not, 2.1.0 as I've had difficulties getting it to build properly for EL6 thankfully the wiki page there indicates that 2.0.0 should work.

You will notice that I've started attaching slaves to the Jenkins silo.
I've got them tagged as requiring a job be specifically tied to a given
tag for them to accept the job, the reason for this is that the test
systems do not presently have any of the build environments on them so
they can't just share build processing.

One final note, Jenkins has an account on all the VMs with the same
rights as any user that gets shell access, this should make it easier to
build out jobs :)

-Andy-

--
Andrew J Grimberg
Systems Administrator
The Linux Foundation

-----Original Message-----
From: integration-dev-bounces@... [mailto:integration-dev-bounces@...] On Behalf Of Andrew Grimberg
Sent: Thursday, November 14, 2013 10:12 AM
To: integration-dev@...
Subject: Re: [integration-dev] ODL Test lab access

As an additional note, the user facing firewalls on the systems are
still pretty tight. I'll need to know what we need to open to make this
useful to folks. The backside network interfaces have no firewalling so
there won't be anything there for us to deal with.

On Thu, 2013-11-14 at 10:02 -0800, Andrew Grimberg wrote:

Greetings folks,

I finally have the test lab available for access. The current layout is
very similar to the Ericsson lab. I've already allocated access rights
to all folks that have committer status to the Integration project.
Those that have not yet actually logged into Gerrit, or at least haven't
configured an SSH pubkey in Gerrit, will need to do so to be able to
access the lab.

Here's the writeup I've done:

https://wiki.opendaylight.org/view/CrossProject:Integration_Group:ODL_Test_Lab

Please note, I do not presently have any graphical desktop applications
on test01 (the tools system). If you believe we need this please let me
know and I'll go about getting Gnome, Firefox and VNC on it.

Also, having looked over the End to End inventory wiki
( https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin::End_to_End_Inventory ) and seeing that to do OF 1.3 we needed Open vSwitch 1.10 or greater I made sure that 1.11 was installed on our mininet system. Mininet is at v2.0.0 not, 2.1.0 as I've had difficulties getting it to build properly for EL6 thankfully the wiki page there indicates that 2.0.0 should work.

You will notice that I've started attaching slaves to the Jenkins silo.
I've got them tagged as requiring a job be specifically tied to a given
tag for them to accept the job, the reason for this is that the test
systems do not presently have any of the build environments on them so
they can't just share build processing.

One final note, Jenkins has an account on all the VMs with the same
rights as any user that gets shell access, this should make it easier to
build out jobs :)

-Andy-

--
Andrew J Grimberg
Systems Administrator
The Linux Foundation

On Thu, 2013-11-14 at 20:20 +0000, Luis Gomez wrote:

Hi Andrew, which CentOS package do we need for sshuttle?

[odluser@odl-controller ~]$ sshuttle
-bash: sshuttle: command not found
[odluser@odl-controller ~]$
[odluser@odl-controller ~]$
[odluser@odl-controller ~]$ yum search sshuttle
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
* base: centos.sonn.com
* extras: linux.mirrors.es.net
* updates: mirror.hmc.edu
Warning: No matches found for: sshuttle
No Matches found

-----Original Message-----
From: integration-dev-bounces@... [mailto:integration-dev-bounces@...] On Behalf Of Andrew Grimberg
Sent: Thursday, November 14, 2013 10:02 AM
To: integration-dev@...
Subject: [integration-dev] ODL Test lab access

Greetings folks,

I finally have the test lab available for access. The current layout is
very similar to the Ericsson lab. I've already allocated access rights
to all folks that have committer status to the Integration project.
Those that have not yet actually logged into Gerrit, or at least haven't
configured an SSH pubkey in Gerrit, will need to do so to be able to
access the lab.

Here's the writeup I've done:

https://wiki.opendaylight.org/view/CrossProject:Integration_Group:ODL_Test_Lab

Please note, I do not presently have any graphical desktop applications
on test01 (the tools system). If you believe we need this please let me
know and I'll go about getting Gnome, Firefox and VNC on it.

Also, having looked over the End to End inventory wiki
( https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin::End_to_End_Inventory ) and seeing that to do OF 1.3 we needed Open vSwitch 1.10 or greater I made sure that 1.11 was installed on our mininet system. Mininet is at v2.0.0 not, 2.1.0 as I've had difficulties getting it to build properly for EL6 thankfully the wiki page there indicates that 2.0.0 should work.

You will notice that I've started attaching slaves to the Jenkins silo.
I've got them tagged as requiring a job be specifically tied to a given
tag for them to accept the job, the reason for this is that the test
systems do not presently have any of the build environments on them so
they can't just share build processing.

One final note, Jenkins has an account on all the VMs with the same
rights as any user that gets shell access, this should make it easier to
build out jobs :)

-Andy-

On Thu, 2013-11-14 at 20:49 +0000, Luis Gomez wrote:

Hi Andrew,

I got sshuttle installed but now I have another issue accessing the environment:

[odluser@odl-test-tools .ssh]$ ssh -p 29418 ecelgp@...

**** Welcome to Gerrit Code Review ****

Hi Luis Gomez, you have successfully connected over SSH.

Unfortunately, interactive shells are disabled.
To clone a hosted Git repository, use:

git clone ssh://ecelgp@...:29418/REPOSITORY_NAME.git

Connection to git.opendaylight.org closed.
[odluser@odl-test-tools .ssh]$
[odluser@odl-test-tools .ssh]$
[odluser@odl-test-tools .ssh]$
[odluser@odl-test-tools .ssh]$ sudo sshuttle -r ecelgp@... 172.17.198.24/29 -H --seed-hosts test01
Address 140.211.169.26 maps to git.opendaylight.org, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
client: fatal: failed to establish ssh session (2)

Am I missing anything?

BR/Luis



-----Original Message-----
From: integration-dev-bounces@... [mailto:integration-dev-bounces@...] On Behalf Of Andrew Grimberg
Sent: Thursday, November 14, 2013 10:12 AM
To: integration-dev@...
Subject: Re: [integration-dev] ODL Test lab access

As an additional note, the user facing firewalls on the systems are
still pretty tight. I'll need to know what we need to open to make this
useful to folks. The backside network interfaces have no firewalling so
there won't be anything there for us to deal with.

On Thu, 2013-11-14 at 10:02 -0800, Andrew Grimberg wrote:

Greetings folks,

I finally have the test lab available for access. The current layout is
very similar to the Ericsson lab. I've already allocated access rights
to all folks that have committer status to the Integration project.
Those that have not yet actually logged into Gerrit, or at least haven't
configured an SSH pubkey in Gerrit, will need to do so to be able to
access the lab.

Here's the writeup I've done:

https://wiki.opendaylight.org/view/CrossProject:Integration_Group:ODL_Test_Lab

Please note, I do not presently have any graphical desktop applications
on test01 (the tools system). If you believe we need this please let me
know and I'll go about getting Gnome, Firefox and VNC on it.

Also, having looked over the End to End inventory wiki
( https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin::End_to_End_Inventory ) and seeing that to do OF 1.3 we needed Open vSwitch 1.10 or greater I made sure that 1.11 was installed on our mininet system. Mininet is at v2.0.0 not, 2.1.0 as I've had difficulties getting it to build properly for EL6 thankfully the wiki page there indicates that 2.0.0 should work.

You will notice that I've started attaching slaves to the Jenkins silo.
I've got them tagged as requiring a job be specifically tied to a given
tag for them to accept the job, the reason for this is that the test
systems do not presently have any of the build environments on them so
they can't just share build processing.

One final note, Jenkins has an account on all the VMs with the same
rights as any user that gets shell access, this should make it easier to
build out jobs :)

-Andy-