Re: [Ryu-devel] [PATCH v3 2/2] install_docker_test_pkg: Move pip pacakges to test-requires
Hi Iwase-san, On Tue, 29 Nov 2016 15:00:12 +0900 Iwase Yusukewrote: > Hi Kakuma-San, > > Sorry for the delay. > > > On 2016年11月29日 09:24, fumihiko kakuma wrote: > > Hi Iwase-san, > > > > On Mon, 28 Nov 2016 14:05:48 +0900 > > IWASE Yusuke wrote: > > > >> Signed-off-by: IWASE Yusuke > >> --- > >> .../common/install_docker_test_pkg_common.sh | 18 > >> ++ > >> .../common/install_docker_test_pkg_for_travis.sh | 1 - > >> tools/test-requires| 4 +++- > >> 3 files changed, 13 insertions(+), 10 deletions(-) > >> > >> diff --git a/ryu/tests/integrated/common/install_docker_test_pkg_common.sh > >> b/ryu/tests/integrated/common/install_docker_test_pkg_common.sh > >> index 08b059a..44a3e10 100644 > >> --- a/ryu/tests/integrated/common/install_docker_test_pkg_common.sh > >> +++ b/ryu/tests/integrated/common/install_docker_test_pkg_common.sh > >> @@ -4,7 +4,6 @@ set -ex > >> function init_variables { > >> APTLINE_DOCKER=0 > >> DIR_BASE=/tmp > >> -SUDO_PIP="" > >> } > >> > >> function process_options { > >> @@ -21,17 +20,20 @@ function process_options { > >> shift; ((i++)) > >> DIR_BASE=$1 > >> ;; > >> --s|--sudo-pip) > >> -SUDO_PIP=sudo > >> -;; > >> esac > >> shift; ((i++)) > >> done > >> } > >> > >> +function install_pipework { > >> +if ! which /usr/local/bin/pipework >/dev/null > >> +then > >> +sudo rm -rf $DIR_BASE/pipework > >> +git clone https://github.com/jpetazzo/pipework.git > >> $DIR_BASE/pipework > >> +sudo install -m 0755 $DIR_BASE/pipework/pipework > >> /usr/local/bin/pipework > >> +fi > >> +} > >> + > >> function install_depends_pkg { > >> -sudo rm -rf $DIR_BASE/pipework > >> -git clone https://github.com/jpetazzo/pipework.git $DIR_BASE/pipework > >> -sudo install -m 0755 $DIR_BASE/pipework/pipework > >> /usr/local/bin/pipework > >> -$SUDO_PIP pip install pycrypto nsenter > > > > I want to install a minimal packages to avoid a package dependency trouble. > > In a test in openstack I'm going to install only packages from > > install_depends_pkg. So I wanted to leave this line. > > > > But I found that pycrypto and nsenter are unnecessary while I check > > the scenario test tools. Currently we can remove these packages from > > packages to be installed. > > Thank you for pointing out. > > You mean; "pycrypto" and "nsenter" are not required, we can remove them, > right? That’s right. > I will post the updated patch to remove them. Thanks. > > BTW, can we move "install_docker_test_pkg_for_travis.sh" into .travis.yml? > Is it required in tox.ini for OpenStack project? > Yes we can. Openstack does not refer to the ryu’s tox.ini. Thanks, kakuma > Thanks, > Iwase > > > > > > Thanks, > > kakuma > > > >> +install_pipework > >> } > >> diff --git > >> a/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh > >> b/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh > >> index 9128c77..d8c3b49 100644 > >> --- a/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh > >> +++ b/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh > >> @@ -7,7 +7,6 @@ source ${RYU_PATH}/install_docker_test_pkg_common.sh > >> > >> init_variables > >> process_options "$@" > >> -SUDO_PIP="" > >> > >> sudo apt-get update > >> install_depends_pkg > >> diff --git a/tools/test-requires b/tools/test-requires > >> index 9d59a70..8c28d90 100644 > >> --- a/tools/test-requires > >> +++ b/tools/test-requires > >> @@ -1,6 +1,8 @@ > >> coverage > >> mock > >> nose > >> +nsenter # integrated tests (Docker) > >> pep8 > >> +pycrypto # integrated tests (Docker) > >> pylint > >> -formencode > >> +formencode # unit tests (OF-Config) > >> -- > >> 2.7.4 > >> > >> > >> -- > >> ___ > >> Ryu-devel mailing list > >> Ryu-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/ryu-devel > > -- fumihiko kakuma -- ___ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
Re: [Ryu-devel] [PATCH v3 2/2] install_docker_test_pkg: Move pip pacakges to test-requires
Hi Kakuma-San, Sorry for the delay. On 2016年11月29日 09:24, fumihiko kakuma wrote: > Hi Iwase-san, > > On Mon, 28 Nov 2016 14:05:48 +0900 > IWASE Yusukewrote: > >> Signed-off-by: IWASE Yusuke >> --- >> .../common/install_docker_test_pkg_common.sh | 18 >> ++ >> .../common/install_docker_test_pkg_for_travis.sh | 1 - >> tools/test-requires| 4 +++- >> 3 files changed, 13 insertions(+), 10 deletions(-) >> >> diff --git a/ryu/tests/integrated/common/install_docker_test_pkg_common.sh >> b/ryu/tests/integrated/common/install_docker_test_pkg_common.sh >> index 08b059a..44a3e10 100644 >> --- a/ryu/tests/integrated/common/install_docker_test_pkg_common.sh >> +++ b/ryu/tests/integrated/common/install_docker_test_pkg_common.sh >> @@ -4,7 +4,6 @@ set -ex >> function init_variables { >> APTLINE_DOCKER=0 >> DIR_BASE=/tmp >> -SUDO_PIP="" >> } >> >> function process_options { >> @@ -21,17 +20,20 @@ function process_options { >> shift; ((i++)) >> DIR_BASE=$1 >> ;; >> --s|--sudo-pip) >> -SUDO_PIP=sudo >> -;; >> esac >> shift; ((i++)) >> done >> } >> >> +function install_pipework { >> +if ! which /usr/local/bin/pipework >/dev/null >> +then >> +sudo rm -rf $DIR_BASE/pipework >> +git clone https://github.com/jpetazzo/pipework.git >> $DIR_BASE/pipework >> +sudo install -m 0755 $DIR_BASE/pipework/pipework >> /usr/local/bin/pipework >> +fi >> +} >> + >> function install_depends_pkg { >> -sudo rm -rf $DIR_BASE/pipework >> -git clone https://github.com/jpetazzo/pipework.git $DIR_BASE/pipework >> -sudo install -m 0755 $DIR_BASE/pipework/pipework /usr/local/bin/pipework >> -$SUDO_PIP pip install pycrypto nsenter > > I want to install a minimal packages to avoid a package dependency trouble. > In a test in openstack I'm going to install only packages from > install_depends_pkg. So I wanted to leave this line. > > But I found that pycrypto and nsenter are unnecessary while I check > the scenario test tools. Currently we can remove these packages from > packages to be installed. Thank you for pointing out. You mean; "pycrypto" and "nsenter" are not required, we can remove them, right? I will post the updated patch to remove them. BTW, can we move "install_docker_test_pkg_for_travis.sh" into .travis.yml? Is it required in tox.ini for OpenStack project? Thanks, Iwase > > Thanks, > kakuma > >> +install_pipework >> } >> diff --git >> a/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh >> b/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh >> index 9128c77..d8c3b49 100644 >> --- a/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh >> +++ b/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh >> @@ -7,7 +7,6 @@ source ${RYU_PATH}/install_docker_test_pkg_common.sh >> >> init_variables >> process_options "$@" >> -SUDO_PIP="" >> >> sudo apt-get update >> install_depends_pkg >> diff --git a/tools/test-requires b/tools/test-requires >> index 9d59a70..8c28d90 100644 >> --- a/tools/test-requires >> +++ b/tools/test-requires >> @@ -1,6 +1,8 @@ >> coverage >> mock >> nose >> +nsenter # integrated tests (Docker) >> pep8 >> +pycrypto # integrated tests (Docker) >> pylint >> -formencode >> +formencode # unit tests (OF-Config) >> -- >> 2.7.4 >> >> >> -- >> ___ >> Ryu-devel mailing list >> Ryu-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/ryu-devel > -- ___ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
Re: [Ryu-devel] [PATCH v3 2/2] install_docker_test_pkg: Move pip pacakges to test-requires
Hi Iwase-san, On Mon, 28 Nov 2016 14:05:48 +0900 IWASE Yusukewrote: > Signed-off-by: IWASE Yusuke > --- > .../common/install_docker_test_pkg_common.sh | 18 > ++ > .../common/install_docker_test_pkg_for_travis.sh | 1 - > tools/test-requires| 4 +++- > 3 files changed, 13 insertions(+), 10 deletions(-) > > diff --git a/ryu/tests/integrated/common/install_docker_test_pkg_common.sh > b/ryu/tests/integrated/common/install_docker_test_pkg_common.sh > index 08b059a..44a3e10 100644 > --- a/ryu/tests/integrated/common/install_docker_test_pkg_common.sh > +++ b/ryu/tests/integrated/common/install_docker_test_pkg_common.sh > @@ -4,7 +4,6 @@ set -ex > function init_variables { > APTLINE_DOCKER=0 > DIR_BASE=/tmp > -SUDO_PIP="" > } > > function process_options { > @@ -21,17 +20,20 @@ function process_options { > shift; ((i++)) > DIR_BASE=$1 > ;; > --s|--sudo-pip) > -SUDO_PIP=sudo > -;; > esac > shift; ((i++)) > done > } > > +function install_pipework { > +if ! which /usr/local/bin/pipework >/dev/null > +then > +sudo rm -rf $DIR_BASE/pipework > +git clone https://github.com/jpetazzo/pipework.git $DIR_BASE/pipework > +sudo install -m 0755 $DIR_BASE/pipework/pipework > /usr/local/bin/pipework > +fi > +} > + > function install_depends_pkg { > -sudo rm -rf $DIR_BASE/pipework > -git clone https://github.com/jpetazzo/pipework.git $DIR_BASE/pipework > -sudo install -m 0755 $DIR_BASE/pipework/pipework /usr/local/bin/pipework > -$SUDO_PIP pip install pycrypto nsenter I want to install a minimal packages to avoid a package dependency trouble. In a test in openstack I'm going to install only packages from install_depends_pkg. So I wanted to leave this line. But I found that pycrypto and nsenter are unnecessary while I check the scenario test tools. Currently we can remove these packages from packages to be installed. Thanks, kakuma > +install_pipework > } > diff --git > a/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh > b/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh > index 9128c77..d8c3b49 100644 > --- a/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh > +++ b/ryu/tests/integrated/common/install_docker_test_pkg_for_travis.sh > @@ -7,7 +7,6 @@ source ${RYU_PATH}/install_docker_test_pkg_common.sh > > init_variables > process_options "$@" > -SUDO_PIP="" > > sudo apt-get update > install_depends_pkg > diff --git a/tools/test-requires b/tools/test-requires > index 9d59a70..8c28d90 100644 > --- a/tools/test-requires > +++ b/tools/test-requires > @@ -1,6 +1,8 @@ > coverage > mock > nose > +nsenter # integrated tests (Docker) > pep8 > +pycrypto # integrated tests (Docker) > pylint > -formencode > +formencode # unit tests (OF-Config) > -- > 2.7.4 > > > -- > ___ > Ryu-devel mailing list > Ryu-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ryu-devel -- fumihiko kakuma -- ___ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
[Ryu-devel] Question about switch memory and finding out about flow size
Hello all, I am new to SDN and Ryu controller world, so I have couple of questions: 1. How can I find out about switch TCAM capacity and available memory? 2. How can I find out about a flow size before installing the flow-rules in the switches and establishing the path between the source and the destination? Thanks in advance -- ___ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
Re: [Ryu-devel] [PATCH 0/2] Imporove the scenario test
Hi, Iwase-san, As I wrote in a previous mail, I think that the scenario test tool is used from an other project (mainly openstack). So I want to have mechanism installing only packages required by scenario test tool. Thanks, kakuma On Mon, 28 Nov 2016 13:39:39 +0900 Iwase Yusukewrote: > Hi Kakuma-San, > > I want to move pip requirements to "tools/test-requires" in the following > patch. >[PATCH 0/2] tox: Move dependencies installation to .travis.yml > > Would you mind my applying my patches (I am planning to send the updated > patch soon) after you patches? > > Thanks, > Iwase > > > > On 2016年11月28日 13:21, fumihiko kakuma wrote: > > The following patches improve the scenario test using a docker. > > > > fumihiko kakuma (2): > > Delete an unnecessary function > > Get some debug information > > > > ryu/tests/integrated/common/docker_base.py| 19 > > ++- > > .../common/install_docker_test_pkg_common.sh | 2 +- > > ryu/tests/integrated/common/ryubgp.py | 1 + > > 3 files changed, 8 insertions(+), 14 deletions(-) > > -- fumihiko kakuma -- ___ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
[Ryu-devel] Receive VxLAN header in RYU Controller
Hi all, When I receive a VxLAN packet from OVS to the controller, I receive de-capsulated packet in RYU controller. Is this a desired behavior? Or is there a way I can get the VxLAN header till the controller? Cheers Sudhendu -- ___ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel