Statement:
This blog welcome forwarding, but please keep the original author information !
Blog Address: Http://blog.csdn.net/halcyonbaby
The content of my study, research and summary, if there is similar, it is honored!
Nova-docker status
The Nova-docker plug-in h version appears, but is removed from Nova in the I version and is cultivated as a incubation project.
The explanation at the time was that it was hoped that iterative development would be faster, supporting cinder and neutron. And is scheduled to be re-entered at version K release.
Architecture of the Nova-docker
The current architecture is as follows (where Docker registry is no longer needed).
As can be seen, this method of use, Docker is equivalent to a new hypervisor.
Use the container as a virtual machine.
The container image is stored in a tar package via Docker save and placed on the glance management.
When the container is created, the container image is downloaded from the glance and the container image is loaded and started using (Docker load).
Support Features
Support for container creation/deletion/Soft Delete/restart/pause/Cancel tentative/stop/start.
Support for snapshot creation on containers, support for snapshot-based recovery containers.
Supports setting up a plug-in adapter for a container.
Query the cpu/memory usage/query available nodes on the Docker node.
Query the Docker container.
Query container console output.
Support Neutron network/nova-network network.
Support for binding floating IPs.
Shared storage is not supported.
The mount/dismount operation is not supported.
Migration, rescue, etc. are not supported.
Setting security group rules is not supported. (from a code perspective, there is a framework, but it is not supported at this time.) The noopfirewalldriver used. )
The container is using local storage and cannot use cinder shared storage.
Network implementation
To view the namespace of a container:
[[email protected] ~]# Docker PS--no-trunccontainer ID IMAGE COMMAND CREATED STATUS PORTS Names54ba6c67de05b8c5ddb824497eae0071f902dcdea05ce93109d9791453dfeb17 tutum/wordpress:latest "/run.sh" hours ago Up hours nova-ee2edd99-a64c-4701-84ad-faccd3b1a246[[email protected] ~]# IP netns List54ba6c67de05b8c5ddb824497eae0071f902dcdea05ce93109d9791453dfeb17qdhcp-78277811-dc20-47c0-8319-58894843e3d43ce4e73bcfe B64b994a5bf87c7f49553ca3583308b93878a07679a742661b0a4qdhcp-bc557a68-425e-4f24-bb6c-627500647856ee3b2cc56a0ccae387371cf8eb 6ad7f43712cf1cbdc66bf46af77f3c929be34aqrouter-818c4149-355d-4409-8dda-f412da898ff0
To view the network in namespace:
[[Email protected] ~]# IP netns exec 54ba6c67de05b8c5ddb824497eae0071f902dcdea05ce93109d9791453dfeb17 IP addr1:lo: < Loopback,up,lower_up> MTU 65536 qdisc noqueue State UNKNOWN link/loopback 00:00:00:00:00:00 BRD 00:00:00:00:00:00 inet 127.0.0.1/8 Scope host lo valid_lft forever Preferred_lft Forever Inet6:: 1/128 Scope host Valid_lft forever preferred_lft forever28:nse54c9783-26: <BROADCAST,MULTICAST,UP,LOWER_UP> MTU Qdisc pfifo_fast State up Qlen link/ether fa:16:3e:d8:9b:e8 brd ff:ff:ff:ff:ff:ff inet 10.0.0.2/24 brd 1 0.0.0.255 Scope Global nse54c9783-26 valid_lft forever Preferred_lft forever Inet6 fe80::f816:3eff:fed8:9be8/ Scope link Valid_lft forever preferred_lft Forever
View the association of device 28 Veth pair:
[[Email protected] ~]# IP netns exec 54ba6c67de05b8c5ddb824497eae0071f902dcdea05ce93109d9791453dfeb17 ethtool-s Nse54c9783-26nic Statistics: peer_ifindex:29[[email protected] ~]# IP addr ... 29:TAPE54C9783-26: <BROADCAST,MULTICAST,UP,LOWER_UP> MTU qdisc pfifo_fast Master Ovs-system State up Qlen 1000 link/ether 82:31:7f:dc:e3:8f brd ff:ff:ff:ff:ff:ff inet6 fe80::8031:7fff:fedc:e38f/64 scope link valid_ LfT Forever Preferred_lft Forever ...
View device 29 associated device: (device hangs on Br-int of OvS Bridge)
[[email protected] ~]# ovs-vsctl show2368aead-599b-4cd8-b2a1-dd01041e5635 Bridge br-ex Port Br-ex Interface br-ex type:internal Port "qg-83cd012e-53" Interface "qg-83cd012e-53" Type:internal Bridge br-int fail_mode:secure Port "tapbf138559-94" Tag:3 Interface "tapbf138559-94" Port "tape54c9783-26" tag:1 Interface "tape54c9783-26" Po RT "TAP7687FCEC-F0" Tag:2 Interface "tap7687fcec-f0" Port br-int Interface Br-int Type:internal Port "qr-9712c2ca-1f" tag:1 Interface "qr-9712c2ca-1f" Type:internal Port Patch-tun Interface Patch-tun type:patch opt Ions: {peer=patch-int} Port "Tap5f8409aa-f9" Tag:3 Interface "Tap5f8409aa-f9" Type:internal POrt "tapeb9206a8-85" tag:1 Interface "tapeb9206a8-85" type:internal Bridge br-tu n Port patch-int Interface patch-int type:patch options: {Peer=patch-tun} Port Br-tun Interface Br-tun type:internal ovs_version: "2.0.0"
Note: Because it is a single-machine environment, no specific physical NIC is configured for Br-int.
Container DHCP service with bind floating IP:
DHCP Service for 10.0.0.0/24 network segment [[email protected] ~]# IP netns exec qdhcp-78277811-dc20-47c0-8319-58894843e3d4 IP addr1: Lo: <LOOPBACK,UP,LOWER_UP> MTU 65536 qdisc noqueue State UNKNOWN link/loopback 00:00:00:00:00:00 BRD 00:00:00:00: 00:00 inet 127.0.0.1/8 Scope host lo valid_lft forever Preferred_lft Forever Inet6:: 1/128 Scope Host VA Lid_lft Forever preferred_lft forever27:tapeb9206a8-85: <BROADCAST,UP,LOWER_UP> MTU qdisc Noqueue State Unkno WN link/ether fa:16:3e:6e:1b:13 brd ff:ff:ff:ff:ff:ff inet 10.0.0.3/24 BRD 10.0.0.255 Scope Global tapeb9206a8-85 Valid_lft Forever Preferred_lft Forever inet6 fe80::f816:3eff:fe6e:1b13/64 scope link Valid_lft forever Prefe Rred_lft forever//can see through the router will internal 10.0.0.0/24 network with the external 172.24.4.0/24 two IPs through [[email protected] ~]# IP netns exec QROUTER-818C4149-355D-4409-8DDA-F412DA898FF0 IP addr1:lo: <LOOPBACK,UP,LOWER_UP> MTU 65536 qdisc noqueue State UN Known Link/loopback 00:00:00:00:00:00 BRD 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever Preferred_lft Forever Inet6:: 1/128 SC Ope host Valid_lft Forever Preferred_lft forever19:qr-9712c2ca-1f: <BROADCAST,UP,LOWER_UP> MTU Qdisc NOQ Ueue State UNKNOWN link/ether fa:16:3e:50:18:19 BRD ff:ff:ff:ff:ff:ff inet 10.0.0.1/24 BRD 10.0.0.255 Scope Global Q r-9712c2ca-1f Valid_lft Forever Preferred_lft forever inet6 fe80::f816:3eff:fe50:1819/64 Scope link valid_l FT Forever preferred_lft forever20:qg-83cd012e-53: <BROADCAST,UP,LOWER_UP> MTU qdisc Noqueue State UNKNOWN Link/ether fa:16:3e:0d:4e:c2 BRD ff:ff:ff:ff:ff:ff inet 172.24.4.2/24 BRD 172.24.4.255 Scope Global qg-83cd012e-53 Valid_lft Forever Preferred_lft Forever inet 172.24.4.6/32 BRD 172.24.4.6 scope Global qg-83cd012e-53 Valid_lft Forever Preferred_lft Forever Inet6 fe80::f816:3eff:fe0d:4ec2/64 scope link Valid_lft forever preferred_lft fore VER//IP bound NAT rules [[EMAIL&Nbsp;protected] ~]# IP netns exec qrouter-818c4149-355d-4409-8dda-f412da898ff0 iptables-save-a neutron-l3-agent-prerouting-d 172.24.4.6/32-j DNAT--to-destination 10.0.0.2-a neutron-l3-agent-float-snat-s 10.0.0.2/32-j SNAT--to-source 172.24.4.6
Reference:
1. http://www.opencontrail.org/openstack-docker-opencontrail/
2. http://technodrone.blogspot.com/2014/10/nova-docker-on-juno.html
[Openstack]nova-docker Status