Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
Akshay's right, tox -egenconfig does the neutron git repo clone, will someone clarify if it's normal? .tox/genconfig/log/genconfig-1.log:+ pip install -U -egit+https://git.openstack.org/openstack/neutron#egg=neutron .tox/genconfig/log/genconfig-1.log:Obtaining neutron from git+https://git.openstack.org/openstack/neutron#egg=neutron .tox/genconfig/log/genconfig-1.log: Cloning https://git.openstack.org/openstack/neutron to ./.tox/genconfig/src/neutron .tox/genconfig/src/neutron/.git/config:url = https://git.openstack.org/openstack/neutron On 2016年05月26日 19:06, Vikas Choudhary wrote: As per my understanding, it should not be cloning neutron repo. Anyways PFA -Vikas On Thu, May 26, 2016 at 4:06 PM, Akshay Kumar Sanghai> wrote: Hi Vikas, Thanks for the command. I don't understand why the command clones the neutron repo. Can i directly download kuryr.conf from somewhere else? or tox does more than creating kuryr_sample.conf? Thanks Akshay On Thu, May 26, 2016 at 9:08 AM, Vikas Choudhary > wrote: Hi Akshay, Sorry about that. You need to run "tox -e genconfig" . After this inside kuryr/etc "kuryr.conf_sample" file will get generated. Copy this file to /etc/kuryr/ after renaming to kuryr.conf. Documentation will be updated soon. -Vikas . On Wed, May 25, 2016 at 8:44 PM, Akshay Kumar Sanghai > wrote: Hi, Thanks Jaume and Antoni. I tried the installation by git cloning the kuryr repo. I did pip install -r requirements.txt. After that I did pip install . . But it doesn't end successfully. There are no config files in /etc/kuryr directory. root@compute1:~/kuryr# pip install . Unpacking /root/kuryr Running setup.py (path:/tmp/pip-4kbPa8-build/setup.py) egg_info for package from file:///root/kuryr [pbr] Processing SOURCES.txt warning: LocalManifestMaker: standard file '-c' not found [pbr] In git context, generating filelist from git warning: no previously-included files matching '*.pyc' found anywhere in distribution Requirement already satisfied (use --upgrade to upgrade): kuryr==0.1.0.dev422 from file:///root/kuryr in /usr/local/lib/python2.7/dist-packages Requirement already satisfied (use --upgrade to upgrade): pbr>=1.6 in /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): Babel>=2.3.4 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): Flask<1.0,>=0.10 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): jsonschema!=2.5.0,<3.0.0,>=2.0.0 in /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): netaddr!=0.7.16,>=0.7.12 in /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): oslo.concurrency>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): oslo.log>=1.14.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): oslo.serialization>=1.10.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): oslo.utils>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): python-neutronclient>=4.2.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): pyroute2>=0.3.10 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): os-client-config>=1.13.1 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade):
Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
As per my understanding, it should not be cloning neutron repo. Anyways PFA -Vikas On Thu, May 26, 2016 at 4:06 PM, Akshay Kumar Sanghai < akshaykumarsang...@gmail.com> wrote: > Hi Vikas, > Thanks for the command. I don't understand why the command clones the > neutron repo. Can i directly download kuryr.conf from somewhere else? or > tox does more than creating kuryr_sample.conf? > > Thanks > Akshay > > On Thu, May 26, 2016 at 9:08 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> Hi Akshay, >> >> Sorry about that. You need to run "tox -e genconfig" . After this inside >> kuryr/etc "kuryr.conf_sample" file will get generated. Copy this file to >> /etc/kuryr/ after renaming to kuryr.conf. >> >> Documentation will be updated soon. >> >> -Vikas >> . >> >> On Wed, May 25, 2016 at 8:44 PM, Akshay Kumar Sanghai < >> akshaykumarsang...@gmail.com> wrote: >> >>> Hi, >>> Thanks Jaume and Antoni. >>> I tried the installation by git cloning the kuryr repo. I did pip >>> install -r requirements.txt. After that I did pip install . . But it >>> doesn't end successfully. There are no config files in /etc/kuryr >>> directory. >>> root@compute1:~/kuryr# pip install . >>> Unpacking /root/kuryr >>> Running setup.py (path:/tmp/pip-4kbPa8-build/setup.py) egg_info for >>> package from file:///root/kuryr >>> [pbr] Processing SOURCES.txt >>> warning: LocalManifestMaker: standard file '-c' not found >>> >>> [pbr] In git context, generating filelist from git >>> warning: no previously-included files matching '*.pyc' found >>> anywhere in distribution >>> Requirement already satisfied (use --upgrade to upgrade): >>> kuryr==0.1.0.dev422 from file:///root/kuryr in >>> /usr/local/lib/python2.7/dist-packages >>> Requirement already satisfied (use --upgrade to upgrade): pbr>=1.6 in >>> /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): Babel>=2.3.4 >>> in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> Flask<1.0,>=0.10 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> jsonschema!=2.5.0,<3.0.0,>=2.0.0 in /usr/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> netaddr!=0.7.16,>=0.7.12 in /usr/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> oslo.concurrency>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> oslo.log>=1.14.0 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> oslo.serialization>=1.10.0 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> oslo.utils>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> python-neutronclient>=4.2.0 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> pyroute2>=0.3.10 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> os-client-config>=1.13.1 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> neutron-lib>=0.1.0 in /usr/local/lib/python2.7/dist-packages (from >>> kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): Werkzeug>=0.7 >>> in /usr/local/lib/python2.7/dist-packages (from >>> Flask<1.0,>=0.10->kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): Jinja2>=2.4 in >>> /usr/lib/python2.7/dist-packages (from >>> Flask<1.0,>=0.10->kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): >>> itsdangerous>=0.21 in /usr/local/lib/python2.7/dist-packages (from >>> Flask<1.0,>=0.10->kuryr==0.1.0.dev422) >>> Requirement already satisfied (use --upgrade to upgrade): markupsafe in >>> /usr/lib/python2.7/dist-packages (from >>> Jinja2>=2.4->Flask<1.0,>=0.10->kuryr==0.1.0.dev422) >>> Cleaning up... >>> root@compute1:~/kuryr# >>> >>> >>> Thanks >>> Akshay >>> >>> >>> >>> >>> On Wed, May 25, 2016 at 4:24 PM, Antoni Segura Puimedon < >>> toni+openstac...@midokura.com> wrote: >>> On Wed, May 25, 2016 at 11:20 AM, Jaume Devesawrote: > Hello Akshay, > > responses inline: > > On Wed, 25 May 2016 10:48, Akshay Kumar Sanghai wrote: > > Hi, > > I have a 4 node openstack setup (1 controller, 1 network, 2 compute >
Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
Hi Vikas, Thanks for the command. I don't understand why the command clones the neutron repo. Can i directly download kuryr.conf from somewhere else? or tox does more than creating kuryr_sample.conf? Thanks Akshay On Thu, May 26, 2016 at 9:08 AM, Vikas Choudharywrote: > Hi Akshay, > > Sorry about that. You need to run "tox -e genconfig" . After this inside > kuryr/etc "kuryr.conf_sample" file will get generated. Copy this file to > /etc/kuryr/ after renaming to kuryr.conf. > > Documentation will be updated soon. > > -Vikas > . > > On Wed, May 25, 2016 at 8:44 PM, Akshay Kumar Sanghai < > akshaykumarsang...@gmail.com> wrote: > >> Hi, >> Thanks Jaume and Antoni. >> I tried the installation by git cloning the kuryr repo. I did pip install >> -r requirements.txt. After that I did pip install . . But it doesn't end >> successfully. There are no config files in /etc/kuryr directory. >> root@compute1:~/kuryr# pip install . >> Unpacking /root/kuryr >> Running setup.py (path:/tmp/pip-4kbPa8-build/setup.py) egg_info for >> package from file:///root/kuryr >> [pbr] Processing SOURCES.txt >> warning: LocalManifestMaker: standard file '-c' not found >> >> [pbr] In git context, generating filelist from git >> warning: no previously-included files matching '*.pyc' found anywhere >> in distribution >> Requirement already satisfied (use --upgrade to upgrade): >> kuryr==0.1.0.dev422 from file:///root/kuryr in >> /usr/local/lib/python2.7/dist-packages >> Requirement already satisfied (use --upgrade to upgrade): pbr>=1.6 in >> /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): Babel>=2.3.4 in >> /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> Flask<1.0,>=0.10 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> jsonschema!=2.5.0,<3.0.0,>=2.0.0 in /usr/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> netaddr!=0.7.16,>=0.7.12 in /usr/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> oslo.concurrency>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> oslo.log>=1.14.0 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> oslo.serialization>=1.10.0 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> oslo.utils>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> python-neutronclient>=4.2.0 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> pyroute2>=0.3.10 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> os-client-config>=1.13.1 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> neutron-lib>=0.1.0 in /usr/local/lib/python2.7/dist-packages (from >> kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): Werkzeug>=0.7 >> in /usr/local/lib/python2.7/dist-packages (from >> Flask<1.0,>=0.10->kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): Jinja2>=2.4 in >> /usr/lib/python2.7/dist-packages (from >> Flask<1.0,>=0.10->kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): >> itsdangerous>=0.21 in /usr/local/lib/python2.7/dist-packages (from >> Flask<1.0,>=0.10->kuryr==0.1.0.dev422) >> Requirement already satisfied (use --upgrade to upgrade): markupsafe in >> /usr/lib/python2.7/dist-packages (from >> Jinja2>=2.4->Flask<1.0,>=0.10->kuryr==0.1.0.dev422) >> Cleaning up... >> root@compute1:~/kuryr# >> >> >> Thanks >> Akshay >> >> >> >> >> On Wed, May 25, 2016 at 4:24 PM, Antoni Segura Puimedon < >> toni+openstac...@midokura.com> wrote: >> >>> >>> >>> On Wed, May 25, 2016 at 11:20 AM, Jaume Devesa >>> wrote: >>> Hello Akshay, responses inline: On Wed, 25 May 2016 10:48, Akshay Kumar Sanghai wrote: > Hi, > I have a 4 node openstack setup (1 controller, 1 network, 2 compute nodes). > I want to install kuryr in liberty version. I cannot find a package in > ubuntu repo. There is not yet official version of Kuryr. You'll need to install using the current master branch of the repo[1] (by cloning it, install dependencies and `python setup.py
Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
Hi Akshay, Sorry about that. You need to run "tox -e genconfig" . After this inside kuryr/etc "kuryr.conf_sample" file will get generated. Copy this file to /etc/kuryr/ after renaming to kuryr.conf. Documentation will be updated soon. -Vikas . On Wed, May 25, 2016 at 8:44 PM, Akshay Kumar Sanghai < akshaykumarsang...@gmail.com> wrote: > Hi, > Thanks Jaume and Antoni. > I tried the installation by git cloning the kuryr repo. I did pip install > -r requirements.txt. After that I did pip install . . But it doesn't end > successfully. There are no config files in /etc/kuryr directory. > root@compute1:~/kuryr# pip install . > Unpacking /root/kuryr > Running setup.py (path:/tmp/pip-4kbPa8-build/setup.py) egg_info for > package from file:///root/kuryr > [pbr] Processing SOURCES.txt > warning: LocalManifestMaker: standard file '-c' not found > > [pbr] In git context, generating filelist from git > warning: no previously-included files matching '*.pyc' found anywhere > in distribution > Requirement already satisfied (use --upgrade to upgrade): > kuryr==0.1.0.dev422 from file:///root/kuryr in > /usr/local/lib/python2.7/dist-packages > Requirement already satisfied (use --upgrade to upgrade): pbr>=1.6 in > /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): Babel>=2.3.4 in > /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): Flask<1.0,>=0.10 > in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > jsonschema!=2.5.0,<3.0.0,>=2.0.0 in /usr/lib/python2.7/dist-packages (from > kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > netaddr!=0.7.16,>=0.7.12 in /usr/lib/python2.7/dist-packages (from > kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > oslo.concurrency>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from > kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): oslo.log>=1.14.0 > in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > oslo.serialization>=1.10.0 in /usr/local/lib/python2.7/dist-packages (from > kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > oslo.utils>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from > kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > python-neutronclient>=4.2.0 in /usr/local/lib/python2.7/dist-packages (from > kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): pyroute2>=0.3.10 > in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > os-client-config>=1.13.1 in /usr/local/lib/python2.7/dist-packages (from > kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > neutron-lib>=0.1.0 in /usr/local/lib/python2.7/dist-packages (from > kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): Werkzeug>=0.7 in > /usr/local/lib/python2.7/dist-packages (from > Flask<1.0,>=0.10->kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): Jinja2>=2.4 in > /usr/lib/python2.7/dist-packages (from > Flask<1.0,>=0.10->kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): > itsdangerous>=0.21 in /usr/local/lib/python2.7/dist-packages (from > Flask<1.0,>=0.10->kuryr==0.1.0.dev422) > Requirement already satisfied (use --upgrade to upgrade): markupsafe in > /usr/lib/python2.7/dist-packages (from > Jinja2>=2.4->Flask<1.0,>=0.10->kuryr==0.1.0.dev422) > Cleaning up... > root@compute1:~/kuryr# > > > Thanks > Akshay > > > > > On Wed, May 25, 2016 at 4:24 PM, Antoni Segura Puimedon < > toni+openstac...@midokura.com> wrote: > >> >> >> On Wed, May 25, 2016 at 11:20 AM, Jaume Devesawrote: >> >>> Hello Akshay, >>> >>> responses inline: >>> >>> On Wed, 25 May 2016 10:48, Akshay Kumar Sanghai wrote: >>> > Hi, >>> > I have a 4 node openstack setup (1 controller, 1 network, 2 compute >>> nodes). >>> > I want to install kuryr in liberty version. I cannot find a package in >>> > ubuntu repo. >>> >>> There is not yet official version of Kuryr. You'll need to install using >>> the >>> current master branch of the repo[1] (by cloning it, install >>> dependencies and >>> `python setup.py install` >>> >> >> Or you could run it dockerized. Read the "repo info" in [2] >> >> We are working on having the packaging ready, but we are splitting the >> repos first, >> so it will take a while for plain distro packages. >> >> >>> > -How do i install kuryr? >>> If the README.rst file of the repository is not enough for you in terms >>> of >>> installation and configuration, please let us know what's not clear. >>> >>> > - what are
Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
From: Antoni Segura Puimedon [mailto:toni+openstac...@midokura.com] Sent: May-25-16 6:55 AM To: OpenStack Development Mailing List (not for usage questions); Gal Sagie; openstack-operators Subject: Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup On Wed, May 25, 2016 at 11:20 AM, Jaume Devesa <devv...@gmail.com<mailto:devv...@gmail.com>> wrote: Hello Akshay, responses inline: On Wed, 25 May 2016 10:48, Akshay Kumar Sanghai wrote: > Hi, > I have a 4 node openstack setup (1 controller, 1 network, 2 compute nodes). > I want to install kuryr in liberty version. I cannot find a package in > ubuntu repo. There is not yet official version of Kuryr. You'll need to install using the current master branch of the repo[1] (by cloning it, install dependencies and `python setup.py install` Or you could run it dockerized. Read the "repo info" in [2] We are working on having the packaging ready, but we are splitting the repos first, so it will take a while for plain distro packages. > -How do i install kuryr? If the README.rst file of the repository is not enough for you in terms of installation and configuration, please let us know what's not clear. > - what are the components that need to be installed on the respective > nodes? You need to run the kuryr libnetwork's service in all the nodes that you use as docker 'workers' and your chosen vendor's neutron agents. For example, for MidoNet it's midolman, for ovs it would be the neutron ovs agent. > - Do i need to install magnum for docker swarm? Not familiar with Magnum.. Can not help you here. If you want to run docker swarm in bare metal, you do not need Magnum. Only keystone and Neutron. You'd put docker swarm, neutron and keystone running in one node, and then have N nodes with docker engine, kuryr/libnetwork and the neutron agents of the vendor of your choice. [Hongbin Lu] Yes, Magnum is optional if you prefer to install swarm/k8s/mesos manually or by other tools. What Magnum offers is basically an automation of deployment plus a few management operations (i.e. scaling the cluster at runtime). From my point of view, if you prefer to skip Magnum, the main disadvantage is the missing of ability to get a tenant-scoped swarm/k8s/mesos cluster on-demand. In such case, you might have a static k8s/swarm/mesos cluster that is shared across multiple tenants. > - Can i use docker swarm, kubernetes, mesos in openstack without using > kuryr? You can use swarm and kubernetes in OpenStack with Kuryr using Magnum. It will use neutron networking for providing nets to the VMs that will run the swarm/kubernetes cluster. Inside the VMs, another overlay done by flannel will be used (in k8s, in swarm I have not tried it). [Hongbin Lu] Yes, I think Flannel is an alternative of Kuryr. If using Magnum, Flannel is supported in k8s and swarm. Magnum supports 3 Flannel backends: udp, vxlan, and host-gw. If you want an overlay solution, you can choose udp or vxlan. If you want a high-performance solution, the host-gw backend should work well. What will be the disadvantages? The disadvantages are that you do not get explicit Neutron networking for your containers, you get less networking isolation for your VMs/containers and if you want the highest performance, you have to change the default flannel mode. [Hongbin Lu] That is true. If using Magnum, the default flannel backend is “udp”. Users need to turn on the “host-gw” backend to get the highest performance. We are discussing if it makes sense to change the default to “host-gw”, so that users will get the non-overlay performance by default. In addition, Magnum team is working with Kuryr team to bring Kuryr as the second network driver. For the comparison between Flannel and Kuryr, I think the main disadvantage of Flannel is not about performance (because the flannel host-gw backend should provide a similar performance as Kuryr), but is the ability to tightly integrate containers with Neutron. Only docker swarm right now. The kubernetes one will be addressed soon. > > Thanks > Akshay Thanks to you for giving it a try! > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev There are a bunch of people much more experienced than me in Kuryr. I hope I haven't said anything stupid. Best regards, [1]: http://github.com/openstack/kuryr [2] https://hub.docker.com/r/kuryr/libnetwork/ -- Jaume Devesa Software Engineer at Midokura PGP key: 35C2D6B2 @ keyserver.ubuntu.com<http://keyserver.ubuntu.com> __
Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
Hi, Thanks Jaume and Antoni. I tried the installation by git cloning the kuryr repo. I did pip install -r requirements.txt. After that I did pip install . . But it doesn't end successfully. There are no config files in /etc/kuryr directory. root@compute1:~/kuryr# pip install . Unpacking /root/kuryr Running setup.py (path:/tmp/pip-4kbPa8-build/setup.py) egg_info for package from file:///root/kuryr [pbr] Processing SOURCES.txt warning: LocalManifestMaker: standard file '-c' not found [pbr] In git context, generating filelist from git warning: no previously-included files matching '*.pyc' found anywhere in distribution Requirement already satisfied (use --upgrade to upgrade): kuryr==0.1.0.dev422 from file:///root/kuryr in /usr/local/lib/python2.7/dist-packages Requirement already satisfied (use --upgrade to upgrade): pbr>=1.6 in /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): Babel>=2.3.4 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): Flask<1.0,>=0.10 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): jsonschema!=2.5.0,<3.0.0,>=2.0.0 in /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): netaddr!=0.7.16,>=0.7.12 in /usr/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): oslo.concurrency>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): oslo.log>=1.14.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): oslo.serialization>=1.10.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): oslo.utils>=3.5.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): python-neutronclient>=4.2.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): pyroute2>=0.3.10 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): os-client-config>=1.13.1 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): neutron-lib>=0.1.0 in /usr/local/lib/python2.7/dist-packages (from kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): Werkzeug>=0.7 in /usr/local/lib/python2.7/dist-packages (from Flask<1.0,>=0.10->kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): Jinja2>=2.4 in /usr/lib/python2.7/dist-packages (from Flask<1.0,>=0.10->kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): itsdangerous>=0.21 in /usr/local/lib/python2.7/dist-packages (from Flask<1.0,>=0.10->kuryr==0.1.0.dev422) Requirement already satisfied (use --upgrade to upgrade): markupsafe in /usr/lib/python2.7/dist-packages (from Jinja2>=2.4->Flask<1.0,>=0.10->kuryr==0.1.0.dev422) Cleaning up... root@compute1:~/kuryr# Thanks Akshay On Wed, May 25, 2016 at 4:24 PM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > > > On Wed, May 25, 2016 at 11:20 AM, Jaume Devesawrote: > >> Hello Akshay, >> >> responses inline: >> >> On Wed, 25 May 2016 10:48, Akshay Kumar Sanghai wrote: >> > Hi, >> > I have a 4 node openstack setup (1 controller, 1 network, 2 compute >> nodes). >> > I want to install kuryr in liberty version. I cannot find a package in >> > ubuntu repo. >> >> There is not yet official version of Kuryr. You'll need to install using >> the >> current master branch of the repo[1] (by cloning it, install dependencies >> and >> `python setup.py install` >> > > Or you could run it dockerized. Read the "repo info" in [2] > > We are working on having the packaging ready, but we are splitting the > repos first, > so it will take a while for plain distro packages. > > >> > -How do i install kuryr? >> If the README.rst file of the repository is not enough for you in terms of >> installation and configuration, please let us know what's not clear. >> >> > - what are the components that need to be installed on the respective >> > nodes? >> >> You need to run the kuryr libnetwork's service in all the nodes that you >> use as >> docker 'workers' >> > > and your chosen vendor's neutron agents. For example, for MidoNet it's > midolman, for ovs it would be the neutron ovs agent. > > >> >> > - Do i need to install magnum for docker swarm? >> >> Not familiar with Magnum.. Can not help you here. >> > > > If you want to run docker swarm in bare metal, you do not need Magnum. Only > keystone and
Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
On Wed, May 25, 2016 at 11:20 AM, Jaume Devesawrote: > Hello Akshay, > > responses inline: > > On Wed, 25 May 2016 10:48, Akshay Kumar Sanghai wrote: > > Hi, > > I have a 4 node openstack setup (1 controller, 1 network, 2 compute > nodes). > > I want to install kuryr in liberty version. I cannot find a package in > > ubuntu repo. > > There is not yet official version of Kuryr. You'll need to install using > the > current master branch of the repo[1] (by cloning it, install dependencies > and > `python setup.py install` > Or you could run it dockerized. Read the "repo info" in [2] We are working on having the packaging ready, but we are splitting the repos first, so it will take a while for plain distro packages. > > -How do i install kuryr? > If the README.rst file of the repository is not enough for you in terms of > installation and configuration, please let us know what's not clear. > > > - what are the components that need to be installed on the respective > > nodes? > > You need to run the kuryr libnetwork's service in all the nodes that you > use as > docker 'workers' > and your chosen vendor's neutron agents. For example, for MidoNet it's midolman, for ovs it would be the neutron ovs agent. > > > - Do i need to install magnum for docker swarm? > > Not familiar with Magnum.. Can not help you here. > If you want to run docker swarm in bare metal, you do not need Magnum. Only keystone and Neutron. You'd put docker swarm, neutron and keystone running in one node, and then have N nodes with docker engine, kuryr/libnetwork and the neutron agents of the vendor of your choice. > > - Can i use docker swarm, kubernetes, mesos in openstack without using > > kuryr? You can use swarm and kubernetes in OpenStack with Kuryr using Magnum. It will use neutron networking for providing nets to the VMs that will run the swarm/kubernetes cluster. Inside the VMs, another overlay done by flannel will be used (in k8s, in swarm I have not tried it). > What will be the disadvantages? > The disadvantages are that you do not get explicit Neutron networking for your containers, you get less networking isolation for your VMs/containers and if you want the highest performance, you have to change the default flannel mode. > > Only docker swarm right now. The kubernetes one will be addressed soon. > > > > > Thanks > > Akshay > > Thanks to you for giving it a try! > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > There are a bunch of people much more experienced than me in Kuryr. I hope > I > haven't said anything stupid. > > Best regards, > > [1]: http://github.com/openstack/kuryr [2] https://hub.docker.com/r/kuryr/libnetwork/ > > > -- > Jaume Devesa > Software Engineer at Midokura > PGP key: 35C2D6B2 @ keyserver.ubuntu.com > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
Hello Akshay, responses inline: On Wed, 25 May 2016 10:48, Akshay Kumar Sanghai wrote: > Hi, > I have a 4 node openstack setup (1 controller, 1 network, 2 compute nodes). > I want to install kuryr in liberty version. I cannot find a package in > ubuntu repo. There is not yet official version of Kuryr. You'll need to install using the current master branch of the repo[1] (by cloning it, install dependencies and `python setup.py install` > -How do i install kuryr? If the README.rst file of the repository is not enough for you in terms of installation and configuration, please let us know what's not clear. > - what are the components that need to be installed on the respective > nodes? You need to run the kuryr libnetwork's service in all the nodes that you use as docker 'workers' > - Do i need to install magnum for docker swarm? Not familiar with Magnum.. Can not help you here. > - Can i use docker swarm, kubernetes, mesos in openstack without using > kuryr? What will be the disadvantages? Only docker swarm right now. The kubernetes one will be addressed soon. > > Thanks > Akshay > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev There are a bunch of people much more experienced than me in Kuryr. I hope I haven't said anything stupid. Best regards, [1]: http://github.com/openstack/kuryr -- Jaume Devesa Software Engineer at Midokura PGP key: 35C2D6B2 @ keyserver.ubuntu.com signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup
Hi, I have a 4 node openstack setup (1 controller, 1 network, 2 compute nodes). I want to install kuryr in liberty version. I cannot find a package in ubuntu repo. -How do i install kuryr? - what are the components that need to be installed on the respective nodes? - Do i need to install magnum for docker swarm? - Can i use docker swarm, kubernetes, mesos in openstack without using kuryr? What will be the disadvantages? Thanks Akshay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev