[{"_1":2,"_167":-5,"_168":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_142":143},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_135":-5,"_136":11,"_137":17,"_138":11,"_139":-5,"_140":141},"canonicalUrl","https://hub.docker.com/r/limao/kuryr-libnetwork-dev/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","limao","reponame","kuryr-libnetwork-dev","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":17,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2017-03-05T03:14:25.493365Z","description","This repo is used for test kuryr-libnetwork dev","is_private","last_updated","2017-03-23T08:55:08.086583Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",390,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","========================\nTeam and repository tags\n========================\n\n.. image:: http://governance.openstack.org/badges/kuryr-libnetwork.svg\n :target: http://governance.openstack.org/reference/tags/index.html\n\n.. Change things from this point on\n\n===============================\nkuryr-libnetwork\n===============================\n\n.. image:: https://raw.githubusercontent.com/openstack/kuryr/master/doc/images/kuryr_logo.png\n :alt: Kuryr mascot\n :align: center\n\n\nDocker for OpenStack Neutron\n\nKuryr-libnetwork is `Kuryr's `_ Docker\nlibnetwork driver that uses Neutron to provide networking services. It provides\ncontainerised images for the common Neutron plugins.\n\nThis repo provides libnetwork specific functionalities such as handler methods\nfor libnetwork apis. All the logic/utilities that can be shared among\ndifferent container networking frameworks such as Docker's libnetwork,\nK8s's CNI and so on, is maintained in separate Kuryr repo as a common library.\n\n\n* Free software: Apache license\n* Documentation: http://docs.openstack.org/developer/kuryr-libnetwork\n* Source: http://git.openstack.org/cgit/openstack/kuryr-libnetwork\n* Bugs: http://bugs.launchpad.net/kuryr-libnetwork\n\nFeatures\n--------\n\n* Docker libnetwork remote driver\n\n* Docker libnetwork IPAM driver\n\n* Support for Linux Bridge, Open vSwitch, Midonet, and IOvisor port bindings\n\n* Support for using existing Neutron networks::\n\n docker network create -d kuryr --ipam-driver=kuryr --subnet=10.10.0.0/24 --gateway=10.10.0.1 \\\n -o neutron.net.uuid=d98d1259-03d1-4b45-9b86-b039cba1d90d mynet\n\n docker network create -d kuryr --ipam-driver=kuryr --subnet=10.10.0.0/24 --gateway=10.10.0.1 \\\n -o neutron.net.name=my_neutron_net mynet\n\n* Support for using existing Neutron ports::\n\n docker run -it --net=kuryr_net --ip=10.0.0.5 ubuntu\n\n if a port in the corresponding subnet with the requested ip address\n already exists and it is unbound, that port is used for the\n container.\n\n* Support for the Docker \"expose\" option::\n\n docker run --net=my_kuryr_net --expose=1234-1238/udp -it ubuntu\n\n This feature is implemented by using Neutron security groups.\n\nLimitations\n~~~~~~~~~~~\n\n* Docker 1.12 with SwarmKit (the new Swarm) does not support remote\n drivers. Therefore, it cannot be used with Kuryr. This limitation is\n to be removed in Docker 1.13.\n\nGetting it running with a service container\n-------------------------------------------\n\nPrerequisites\n~~~~~~~~~~~~~\n\nThe necessary components for an operating environment to run Kuryr are:\n\n* Keystone (preferably configured with Keystone v3),\n* Neutron (preferably mitaka or newer),\n* DB management system such as MySQL or Mariadb (for Neutron and Keystone),\n* Neutron agents for the vendor you choose,\n* Rabbitmq if the Neutron agents for your vendor require it,\n* Docker 1.9+\n\nBuilding the container\n~~~~~~~~~~~~~~~~~~~~~~\n\nThe Dockerfile in the root of this repository can be used to generate a wsgi\nKuryr Libnetwork server container with docker build::\n\n docker build -t your_docker_username/libnetwork:latest .\n\nAdditionally, you can pull the upstream container::\n\n docker pull kuryr/libnetwork:latest\n\nNote that you can also specify the tag of a stable release for the above\ncommand instead of *latest*.\n\nHow to run the container\n~~~~~~~~~~~~~~~~~~~~~~~~\n\nFirst we prepare Docker to find the driver::\n\n sudo mkdir -p /usr/lib/docker/plugins/kuryr\n sudo curl -o /usr/lib/docker/plugins/kuryr/kuryr.spec \\\n https://raw.githubusercontent.com/openstack/kuryr-libnetwork/master/etc/kuryr.spec\n sudo service docker restart\n\nThen we start the container::\n\n docker run --name kuryr-libnetwork \\\n --net=host \\\n --cap-add=NET_ADMIN \\\n -e SERVICE_USER=admin \\\n -e SERVICE_PROJECT_NAME=admin \\\n -e SERVICE_PASSWORD=admin \\\n -e SERVICE_DOMAIN_NAME=Default \\\n -e USER_DOMAIN_NAME=Default \\\n -e IDENTITY_URL=http://127.0.0.1:35357/v3 \\\n -v /var/log/kuryr:/var/log/kuryr \\\n -v /var/run/openvswitch:/var/run/openvswitch \\\n kuryr/libnetwork\n\nWhere:\n\n* SERVICE_USER, SERVICE_PROJECT_NAME, SERVICE_PASSWORD, SERVICE_DOMAIN_NAME,\n USER_DOMAIN_NAME are OpenStack credentials\n* IDENTITY_URL is the url to the OpenStack Keystone v3 endpoint\n* A volume is created so that the logs are available on the host\n* NET_ADMIN capabilities are given in order to perform network operations on\n the host namespace like ovs-vsctl\n\nOther options you can set as '-e' parameters in Docker run:\n\n* CAPABILITY_SCOPE can be \"local\" or \"global\", the latter being for when there\n is a cluster store plugged into the docker engine.\n* LOG_LEVEL for defining, for example, \"DEBUG\" logging messages.\n* PROCESSES for defining how many kuryr processes to use to handle the\n libnetwork requests.\n\nNote that you will probably have to change the 127.0.0.1 IDENTITY_URL address\nfor the address where your Keystone is running. In this case it is 127.0.0.1\nbecause the example assumes running the container with *--net=host* on an all\nin one deployment where Keystone is also binding locally.\n\nAlternatively, if you have an existing kuryr.conf, you can use it for the\ncontainer::\n\n docker run --name kuryr-libnetwork \\\n --net host \\\n --cap-add NET_ADMIN \\\n -v /etc/kuryr:/etc/kuryr:ro \\\n -v /var/log/kuryr:/var/log/kuryr:rw \\\n -v /var/run/openvswitch:/var/run/openvswitch:rw \\\n kuryr/libnetwork\n\n\nGetting it from source\n----------------------\n\n::\n\n $ git clone https://git.openstack.org/openstack/kuryr-libnetwork\n $ cd kuryr-libnetwork\n\n\nPrerequisites\n~~~~~~~~~~~~~\n\n::\n\n $ sudo pip install -r requirements.txt\n\n\nInstalling Kuryr's libnetwork driver\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nRunning the following will grab the requirements and install kuryr::\n\n $ sudo pip install .\n\n\nConfiguring Kuryr\n~~~~~~~~~~~~~~~~~\n\nGenerate sample config, `etc/kuryr.conf.sample`, running the following::\n\n $ ./tools/generate_config_file_samples.sh\n\n\nRename and copy config file at required path::\n\n $ cp etc/kuryr.conf.sample /etc/kuryr/kuryr.conf\n\n\nFor using Keystone v3, edit the Neutron section in `/etc/kuryr/kuryr.conf`, replace ADMIN_PASSWORD::\n\n [neutron]\n auth_url = http://127.0.0.1:35357/v3/\n username = admin\n user_domain_name = Default\n password = ADMIN_PASSWORD\n project_name = service\n project_domain_name = Default\n auth_type = password\n\n\nAlternatively, for using Keystone v2, edit the Neutron section in `/etc/kuryr/kuryr.conf`, replace ADMIN_PASSWORD::\n\n [neutron]\n auth_url = http://127.0.0.1:35357/v2.0/\n username = admin\n password = ADMIN_PASSWORD\n project_name = service\n auth_type = password\n\n\nIn the same file uncomment the `bindir` parameter with the path for the Kuryr\nvif binding executables. For example, if you installed it on Debian or Ubuntu::\n\n [DEFAULT]\n bindir = /usr/local/libexec/kuryr\n\n\nRunning Kuryr\n~~~~~~~~~~~~~\n\nCurrently, Kuryr utilizes a bash script to start the service.\nMake sure that you have installed `tox` before the execution of\nthe following commands:\n\nIf SSL needs to be enabled follow this step or skip to next step::\n\n $tox -egenconfig\n\n Add these 3 parameters in generated file[etc/kuryr.conf.sample]:\n ssl_cert_file \n ssl_key_file \n enable_ssl \n\n $export SSL_ENABLED=True\n\n Add the path names in [contrib/tls/kuryr.json]:\n InsecureSkipVerify \n CAFile: \n CertFile: \n KeyFile: \n\n Placement of cert files:\n By default Kuryr places it certs in /var/lib/kuryr/certs directory,\n Please make sure that certs are on proper location as mentioned in kuryr.conf\n\n Verification of kuryr.json:\n Please make sure that your kuryr.json look similar to below sample\n with appropiate paths of certs updated, and remove older .spec files\n if any exists.\n and https configuration url::\n {\n \"Name\": \"kuryr\",\n \"Addr\": \"https://127.0.0.1:23750\",\n \"TLSConfig\": {\n \"InsecureSkipVerify\": false,\n \"CAFile\": \"/var/lib/kuryr/certs/ca.pem\",\n \"CertFile\": \"/var/lib/kuryr/certs/cert.pem\",\n \"KeyFile\": \"/var/lib/kuryr/certs/key.pem\"\n }\n }\n\n Optional:\n For locally generating and testing, please refer to below link:\n http://tech.paulcz.net/2016/01/secure-docker-with-tls/\n\nRun Kuryr Server from command below::\n\n $ sudo ./scripts/run_kuryr.sh\n\nAfter Kuryr starts, please restart your Docker service, e.g.::\n\n $ sudo service docker restart\n\nThe bash script creates the following file if it is missing:\n\n* ``/usr/lib/docker/plugins/kuryr/kuryr.json``: Json spec file for libnetwork.\n\nNote the root privilege is required for creating and deleting the veth pairs\nwith `pyroute2 `_ to run.\n\n\nHow to try out nested-containers locally\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n1. Installing OpenStack running devstack with the desired local.conf file but\n including the next to make use of OVS-firewall and enabling Trunk Ports::\n\n [[post-config|/$Q_PLUGIN_CONF_FILE]]\n\n [DEFAULT]\n service_plugins=trunk\n\n [securitygroup]\n firewall_driver=openvswitch\n\n2. Launch a VM with `Neutron trunk port.\n `\n\n3. Inside the VM install kuryr and kuryr-libnetwork following the normal\n installation steps (see above steps at `Installing Kuryr's libnetwork\n driver`).\n\n4. Reconfigure kuryr inside the VM to point to the neutron server and to use the\n vlan driver:\n\n - Configure `/etc/kuryr/kuryr.conf`::\n\n [binding]\n driver = kuryr.lib.binding.drivers.vlan\n link_iface = eth0 # VM vNIC\n\n [neutron]\n auth_url = http://KEYSTONE_SERVER_IP:35357/v3/\n username = admin\n user_domain_name = Default\n password = ADMIN_PASSWORD\n project_name = service\n project_domain_name = Default\n auth_type = password\n\n - Restart kuryr service inside the VM\n\n\nKnown nested-containers limitations\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n1. Due to the `Neutron Trunk service implementation choice `_\n deployments with iptables hybrid security groups driver do not support\n trunk service.\n\n2. QoS rules are not applied properly on sub-ports due to a `Neutron bug\n `_, i.e. nested-container\n port.\n\n\nTesting Kuryr\n-------------\n\nFor a quick check that Kuryr is working, create a IPv4 network::\n\n $ docker network create --driver kuryr --ipam-driver kuryr \\\n --subnet 10.10.0.0/16 --gateway=10.10.0.1 test_v4_net\n 785f8c1b5ae480c4ebcb54c1c48ab875754e4680d915b270279e4f6a1aa52283\n $ docker network ls\n NETWORK ID NAME DRIVER SCOPE\n 785f8c1b5ae4 test_v4_net kuryr local\n\nOr you can test with a dual-stack network::\n\n $ docker network create --driver kuryr --ipam-driver kuryr \\\n --subnet 10.20.0.0/16 --gateway=10.20.0.1 --ipv6 --subnet 2001:db8:a0b:12f0::/64 \\\n --gateway 2001:db8:a0b:12f0::1 test_net\n 81e1a12eedfb168fbe73186faec4db5088aae4457244f960f38e14f4338e5760\n $ docker network ls\n NETWORK ID NAME DRIVER SCOPE\n 81e1a12eedfb test_net kuryr local\n\nKnown IPv6 network limitations\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nDue to the `Docker --ipv6 tag bug `_ version\n1.12 and 1.13 have problem to create network only with IPv6.\n\n\nTo test it with tox::\n\n $ tox\n\nYou can also run specific test cases using the ``-e`` flag, e.g., to only run\nthe *fullstack* test case::\n\n $ tox -e fullstack\n\nAlso you can run *fullstack* test using credentials from openrc config file,\nthis requires you source openrc file in your DevStack or production environment.\nIn DevStack, you can using command \"source openrc admin\" in your devstack directory.\nFor production environment, please refer \"Create OpenStack client environment scripts\"\nin OpenStack install guide.\n\nGenerating Documentation\n------------------------\n\n\nWe use `Sphinx `_ to maintain the\ndocumentation. You can install Sphinx using pip::\n\n $ pip install -U Sphinx\n\nIn addition to Sphinx you will also need the following requirements\n(not covered by `requirements.txt`)::\n\n $ pip install oslosphinx reno 'reno[sphinx]'\n\nThe source code of the documentation are under *doc*, you can generate the\nhtml files using the following command. If the generation succeeds,a\n*build/html* dir will be created under *doc*::\n\n $ cd doc\n $ make html\n\nNow you can serve the documentation at http://localhost:8080 as a simple\nwebsite::\n\n $ cd build/html\n $ python -m SimpleHTTPServer 8080\n\nLimitations\n-----------\n\nTo create Docker networks with subnets having same/overlapping cidr, it is\nexpected to pre-create Neutron subnetpool and pass the pool name for each\nsuch network creation Docker command. Docker cli options -o and --ipam-opt\nshould be used to pass pool names as shown below::\n\n $ neutron subnetpool-create --pool-prefix 10.0.0.0/24 neutron_pool1\n $ sudo docker network create --driver=kuryr --ipam-driver=kuryr \\\n --subnet 10.0.0.0/16 --gateway=10.0.0.1 --ip-range 10.0.0.0/24 \\\n -o neutron.pool.name=neutron_pool1 \\\n --ipam-opt=neutron.pool.name=neutron_pool1 \\\n foo\n eddb51ebca09339cb17aaec05e48ffe60659ced6f3fc41b020b0eb506d364\n\nNow Docker user creates another network with same cidr as the previous one,\ni.e 10.0.0.0/16, but with different pool name, neutron_pool2::\n\n $ neutron subnetpool-create --pool-prefix 10.0.0.0/24 neutron_pool2\n $ sudo docker network create --driver=kuryr --ipam-driver=kuryr \\\n --subnet 10.0.0.0/16 --gateway=10.0.0.1 --ip-range 10.0.0.0/24 \\\n -o neutron.pool.name=neutron_pool2 \\\n --ipam-opt=neutron.pool.name=neutron_pool2 \\\n bar\n 397badb51ebca09339cb17aaec05e48ffe60659ced6f3fc41b020b0eb506d786\n\nAlternatively, Docker user can pass an existing pool uuid if there are multiple\npools with the same name::\n\n $ sudo sudo docker network create --driver=kuryr --ipam-driver=kuryr \\\n --subnet 10.0.0.0/16 --gateway=10.0.0.1 --ip-range 10.0.0.0/24 \\\n -o neutron.pool.uuid=2d5767a4-6c96-4522-ab1d-a06d7adc9e23 \\\n --ipam-opt=neutron.pool.uuid=2d5767a4-6c96-4522-ab1d-a06d7adc9e23 \\\n bar\n 0aed1efbe21f6c29dc77eccd0dd17ba729274f9275070e1469230c864f9054ff\n\n\nExternal Resources\n------------------\n\nThe latest and most in-depth documentation is available at:\n \n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",486532372,"orgData","recentTags",[87,125],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},"content_type","creator",432960,"full_size",71657077,"id",8692157,"images",[97],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:20d5752b0ce61a7877ca67504474ebd3bbd7dfa9a5cfd3a28c4fd2b7c2a8bc2f","features","","last_pulled","2026-09-18T20:00:38.905313228Z","last_pushed","2017-03-23T08:55:08Z","os","linux","os_features","os_version","size","variant","2017-03-23T08:55:07.800978Z","last_updater","last_updater_username","media_type","latest","repository",1299395,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_88":40,"_89":90,"_91":126,"_93":127,"_95":128,"_46":133,"_115":90,"_116":29,"_117":52,"_53":134,"_119":120,"_121":131,"_122":133,"_123":62,"_124":17},71657019,8692143,[129],{"_98":99,"_100":130,"_102":103,"_104":131,"_106":132,"_108":109,"_110":103,"_111":-5,"_112":126,"_59":62,"_113":-5},"sha256:86ddf3060fb5f0184a01bf7fcd7ce13c4bd7b209d841ef534831fd1293d08d55","2026-09-01T21:55:50.744911595Z","2017-03-23T08:51:07Z","2017-03-23T08:51:06.147999Z","limao-develop","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":144,"_151":152,"_140":165,"_166":11},{"_36":145,"_38":146,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":147,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":148,"_75":17,"_76":150,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":149},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_153":154,"_155":-5,"_156":-5,"_157":158},"count",2,"next","previous","results",[159,162],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":160,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},[161],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},{"_88":40,"_89":90,"_91":126,"_93":127,"_95":163,"_46":133,"_115":90,"_116":29,"_117":52,"_53":134,"_119":120,"_121":131,"_122":133,"_123":62,"_124":17},[164],{"_98":99,"_100":130,"_102":103,"_104":131,"_106":132,"_108":109,"_110":103,"_111":-5,"_112":126,"_59":62,"_113":-5},[],"canDeleteTags","actionData","errors"]

limao/kuryr-libnetwork-dev

Tags for limao/kuryr-libnetwork-dev