openstack neutron使用ovn方式部署

admin

Controller nodes
* m- G1 F& A  C- N: X7 f$ BEach controller node runs the Open vSwitch (OVS) service (including dependent services such as ovsdb-server) and ovn-northd. Only a single instance of the ovsdb-server and ovn-northd services can operate in a deployment. However, deployment tools can implement active/passive high-availability using a management tool that monitors service health and automatically starts these services on another node after failure of the primary node. See the Frequently Asked Questions for more information.
0 U+ F/ |: {: |1 |! C% Q
Install the ovn-central and openvswitch packages (RHEL/Fedora).

Install the ovn-central and openvswitch-common packages (Ubuntu/Debian).

6 a$ T1 w% h; @3 c# SStart the OVS service. The central OVS service starts the ovsdb-server service that manages OVN databases.

Using the systemd unit:
8 T, @7 k/ H% s6 u1 F% Q
. Q' a0 z- B2 A* W/ f4 O% [9 n4 {: b" dsystemctl start openvswitch (RHEL/Fedora)
3 ~3 v" b$ r. C" }) rsystemctl start openvswitch-switch (Ubuntu/Debian)
Configure the ovsdb-server component. By default, the ovsdb-server service only permits local access to databases via Unix socket. However, OVN services on compute nodes require access to these databases.

Permit remote database access.
# s  o, Z/ n& P9 i( c/ X' h
+ M& e8 H. Z) ~4 o4 jovn-nbctl set-connection ptcp:6641:0.0.0.0 -- \
7 @" `- N) d5 G: s) {5 F7 \            set connection . inactivity_probe=60000
6 W6 O* A: e9 L" H+ ~ovn-sbctl set-connection ptcp:6642:0.0.0.0 -- \
            set connection . inactivity_probe=60000
if using the VTEP functionality:
ovs-appctl -t ovsdb-server ovsdb-server/add-remote ptcp:6640:0.0.0.0
Replace 0.0.0.0 with the IP address of the management network interface on the controller node to avoid listening on all interfaces.

Note

Permit remote access to TCP ports: 6640 (OVS) to VTEPS (if you use vteps), 6642 (SBDB) to hosts running neutron-server, gateway nodes that run ovn-controller, and compute node services like ovn-controller and ovn-metadata-agent. 6641 (NBDB) to hosts running neutron-server.
# b/ x( @# {! E5 M4 ~5 Q
; |4 ^0 W' }5 h3 KStart the ovn-northd service.
+ o2 M9 N$ b( w, Z' a
Using the systemd unit:
4 ?0 A" ?9 C  [4 m) Q( H' ~
systemctl start ovn-northd
; P; N* [$ w2 ~( vConfigure the Networking server component. The Networking service implements OVN as an ML2 driver. Edit the /etc/neutron/neutron.conf file:

9 u. r" C: n  JEnable the ML2 core plug-in.

: e, i$ ]1 M6 h1 H. K[DEFAULT]
...
core_plugin = ml2
Enable the OVN layer-3 service.
& g2 [* R3 ?6 L1 H& Z# K! t7 }
[DEFAULT]
...
service_plugins = ovn-router
Configure the ML2 plug-in. Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file:
+ i. F, M1 g: _2 u  K3 s, `) L0 x
Configure the OVN mechanism driver, network type drivers, self-service (tenant) network types, and enable the port security extension.
. ~& Y0 E' y6 |2 `
[ml2]
) d7 d2 }3 n# {- v2 N/ ~...
mechanism_drivers = ovn
6 \% _. l+ U+ a) r7 Btype_drivers = local,flat,vlan,geneve
- j9 A9 N1 b) q0 }3 X  ~3 ]; |tenant_network_types = geneve
extension_drivers = port_security
5 m! H7 c, r- R5 Noverlay_ip_version = 4
Note

# l3 {) D9 @; y; A, v5 yTo enable VLAN self-service networks, make sure that OVN version 2.11 (or higher) is used, then add vlan to the tenant_network_types option. The first network type in the list becomes the default self-service network type.
1 L  `( x9 Z1 V$ ?
To use IPv6 for all overlay (tunnel) network endpoints, set the overlay_ip_version option to 6.
1 R2 A# y0 _& F: f
Configure the Geneve ID range and maximum header size. The IP version overhead (20 bytes for IPv4 (default) or 40 bytes for IPv6) is added to the maximum header size based on the ML2 overlay_ip_version option.
& p0 c4 _; t  M4 v( x) [, S
[ml2_type_geneve]
" R2 `2 `3 t8 t# `3 M8 X...
vni_ranges = 1:65536
8 {6 i  `& l+ m+ L- ^$ ?max_header_size = 38
Note
2 ~+ N; g- r$ ^5 J- |" Q) o7 G$ _0 }
( Z9 i! e7 u' \! s/ C5 f2 V+ r7 BThe Networking service uses the vni_ranges option to allocate network segments. However, OVN ignores the actual values. Thus, the ID range only determines the quantity of Geneve networks in the environment. For example, a range of 5001:6000 defines a maximum of 1000 Geneve networks. On the other hand, these values are still relevant in Neutron context so 1:1000 and 5001:6000 are not simply interchangeable.

Warning
4 M8 c: J+ [6 e5 r9 t
5 h% \, s/ p3 x3 AThe default for max_header_size, 30, is too low for OVN. OVN requires at least 38.

' ~1 D% b4 U8 i- ^0 v7 j& dOptionally, enable support for VXLAN type networks. Because of limited space in VXLAN VNI to pass over the needed information that requires OVN to identify a packet, the header size to contain the segmentation ID is reduced to 12 bits, that allows a maximum number of 4096 networks. The same limitation applies to the number of ports in each network, that are also identified with a 12 bits header chunk, limiting their number to 4096 ports. Please check [1] for more information.
* f" b4 h4 ?) W6 X1 x% E6 Z& ?
! f1 ?7 B/ T3 |+ j[ml2]
...
: S! }: k& I0 Ytype_drivers = geneve,vxlan
! Q8 `1 e( ^) W2 {& b) o
[ml2_type_vxlan]
- S# p$ u( R' hvni_ranges = 1001:1100
Optionally, enable support for VLAN provider and self-service networks on one or more physical networks. If you specify only the physical network, only administrative (privileged) users can manage VLAN networks. Additionally specifying a VLAN ID range for a physical network enables regular (non-privileged) users to manage VLAN networks. The Networking service allocates the VLAN ID for each self-service network using the VLAN ID range for the physical network.
. s8 K5 M6 E9 k2 P/ Y" c
[ml2_type_vlan]
...
network_vlan_ranges = PHYSICAL_NETWORK:MIN_VLAN_ID:MAX_VLAN_ID
# \+ [$ y* K! N" ?3 sReplace PHYSICAL_NETWORK with the physical network name and optionally define the minimum and maximum VLAN IDs. Use a comma to separate each physical network.
/ ?: L% r$ A$ r. \- ?- H3 ~3 c; L
For example, to enable support for administrative VLAN networks on the physnet1 network and self-service VLAN networks on the physnet2 network using VLAN IDs 1001 to 2000:

+ N* T2 A' D, q- x/ }network_vlan_ranges = physnet1,physnet2:1001:2000
Enable security groups.

[securitygroup]
...
- U4 [& {2 s  r8 C9 m6 eenable_security_group = true
Note
5 v1 b1 r( p' a5 m4 L" l+ q
, k2 X- L# Y+ vThe firewall_driver option under [securitygroup] is ignored since the OVN ML2 driver itself handles security groups.
! e4 h) x& }- ~
/ w; X, K& `  J; lConfigure OVS database access and L3 scheduler
0 [& k" x9 B: C( X
[ovn]
$ F* E. l! T& A4 i6 U9 R. ~( I...
( {- W$ e8 u9 W/ e' `- t. W8 ~ovn_nb_connection = tcp:IP_ADDRESS:6641
5 ]8 ~; d) }2 b$ N# m: ]ovn_sb_connection = tcp:IP_ADDRESS:6642
& m  ?9 J* N) e$ N. \: l; kovn_l3_scheduler = OVN_L3_SCHEDULER
0 {  F2 v  O" }2 [9 `9 z Note

# F1 x; S" L6 Z8 h# R* B$ JReplace IP_ADDRESS with the IP address of the controller node that runs the ovsdb-server service. Replace OVN_L3_SCHEDULER with leastloaded if you want the scheduler to select a compute node with the least number of gateway ports or chance if you want the scheduler to randomly select a compute node from the available list of compute nodes.
& I' z) B' L4 s
; l6 Z0 m% F, }; b/ DSet ovn-cms-options with enable-chassis-as-gw in Open_vSwitch table’s external_ids column. Then if this chassis has proper bridge mappings, it will be selected for scheduling gateway routers.
8 P& U4 o0 z7 m0 C4 S
/ p$ e. B! U5 |. G1 A% {5 v' J- u$ w8 _ovs-vsctl set open . external-ids:ovn-cms-options=enable-chassis-as-gw
Start, or restart, the neutron-server service.

+ r' O. k$ ?4 @- k1 K6 P9 j$ PUsing the systemd unit:

6 h# ]  Q% \7 t% }- [/ d9 Qsystemctl start neutron-server
/ H7 a- \+ D- F, vNetwork nodes
4 R: e% {. i: b% rDeployments using OVN native layer-3 and DHCP services do not require conventional network nodes because connectivity to external networks (including VTEP gateways) and routing occurs on compute nodes.
2 M/ _- ~& T; D# Z* X
# k$ E5 X- E! d: ^Compute nodes
Each compute node runs the OVS and ovn-controller services. The ovn-controller service replaces the conventional OVS layer-2 agent.

Install the ovn-host, openvswitch and neutron-ovn-metadata-agent packages (RHEL/Fedora).
# \+ t7 Q- o2 V: L" ]* [- x
Install the ovn-host, openvswitch-switch and neutron-ovn-metadata-agent packages (Ubuntu/Debian).
; C! M) ^% Z1 k; q' P) z/ q" y
! ]0 Q9 l, l; ~5 r2 ^/ Q/ [2 tStart the OVS service.
: w* z1 r! N$ ?8 U3 G0 L
Using the systemd unit:

( l8 i& s4 L( ?) d% M5 B, Esystemctl start openvswitch (RHEL/Fedora)
systemctl start openvswitch-switch (Ubuntu/Debian)
+ a6 S/ b0 c- m4 vConfigure the OVS service.

Use OVS databases on the controller node.

: j2 v$ d" K& Z1 _/ {" @9 covs-vsctl set open . external-ids:ovn-remote=tcp:IP_ADDRESS:6642
+ L3 x: v- H7 F6 E$ c4 L( q4 J7 v( q: P: lReplace IP_ADDRESS with the IP address of the controller node that runs the ovsdb-server service.

7 }6 J5 ~$ @. K. c  i6 @Enable one or more overlay network protocols. At a minimum, OVN requires enabling the geneve protocol. Deployments using VTEP gateways should also enable the vxlan protocol.
; N/ H& F3 I# `* r
ovs-vsctl set open . external-ids:ovn-encap-type=geneve,vxlan
' X# i( ]+ D# ]0 M% p Note
2 u- b& D: s. x7 o, M, g
  m! E4 W) J; K/ h3 u' S7 r/ dDeployments without VTEP gateways can safely enable both protocols.

Configure the overlay network local endpoint IP address.
: X. ~9 g" e1 T
ovs-vsctl set open . external-ids:ovn-encap-ip=IP_ADDRESS
Replace IP_ADDRESS with the IP address of the overlay network interface on the compute node.

Start the ovn-controller and neutron-ovn-metadata-agent services.

Using the systemd unit:

systemctl start ovn-controller neutron-ovn-metadata-agent
7 p8 w) {1 K  U& bVerify operation¶
Each compute node should contain an ovn-controller instance.
* L, |* H8 L5 i: e; x) r
* v: g% D" Z2 K& I8 q$ j0 U( `ovn-sbctl show
  n! O! c9 P) P1 X  <output>
1 _2 u6 E7 k2 K0 r

Deployment steps
5 H$ E9 O+ f# f) sDownload the quickstart.sh script with curl:

curl -O https://raw.githubusercontent.co ... aster/quickstart.sh
Install the necessary dependencies by running:

% E, ^* Z  \# A# h4 E: y2 Abash quickstart.sh --install-deps
, @) v4 Q$ A& j3 Z+ `3 UClone the tripleo-quickstart and neutron repositories:

/ p' q2 m! i9 w+ S0 Z1 fgit clone https://opendev.org/openstack/tripleo-quickstart
git clone https://opendev.org/openstack/neutron
Once you’re done, run quickstart as follows (3 controller HA + 1 compute):
8 j' L" n. B8 Z
3 e8 l% U4 Z7 k6 L& f; vExporting the tags is a workaround until the bug
' m- Q( u4 r' S5 r8 C" q2 m: b5 Xhttps://bugs.launchpad.net/tripleo/+bug/1737602 is resolved

export ansible_tags="untagged,provision,environment,libvirt,\
undercloud-scripts,undercloud-inventory,overcloud-scripts,\
1 T% H, D5 _4 ]+ I. |( |5 C5 r; kundercloud-setup,undercloud-install,undercloud-post-install,\
3 c( t# {: A/ J- e1 novercloud-prep-config"

bash ./quickstart.sh --tags $ansible_tags --teardown all \
3 p0 @& B) ?( N: e0 z. ?--release master-tripleo-ci \
+ r$ _8 o) s* F! F% t--nodes tripleo-quickstart/config/nodes/3ctlr_1comp.yml  \
--config neutron/tools/tripleo/ovn.yml \
: c& i0 b; z) w/ o3 nVIRTHOST
* f7 T+ K/ d3 G/ K' h Note
( M9 X! l- G6 ~+ z- b
When deploying directly on localhost use the loopback address 127.0.0.2 as your $VIRTHOST. The loopback address 127.0.0.1 is reserved by ansible. Also make sure that 127.0.0.2 is accessible via public keys:

6 _' p6 {, _; @+ G# `5 \) M$ O( U$ \% c$ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
' t3 q7 a0 F7 K8 r/ w8 {9 B7 c3 |' j Note

You can adjust RAM/VCPUs if you want by editing config/nodes/3ctlr_1comp.yml before running the above command. If you have enough memory stick to the defaults. We recommend using 8GB of RAM for the controller nodes.
2 n  v& {! h: o  f
: u: d) i) C, ]% g* O: M/ hWhen quickstart has finished you will have 5 VMs ready to be used, 1 for the undercloud (TripleO’s node to deploy your openstack from), 3 VMs for controller nodes and 1 VM for the compute node.
$ k' k1 N  G! [
Log in into the undercloud:
4 e9 Z! f5 v- R% H) @
ssh -F ~/.quickstart/ssh.config.ansible undercloud
Prepare overcloud container images:
' k- e) a; O, B3 o; ^
./overcloud-prep-containers.sh
Run inside the undercloud:

  {* t; O4 ]/ m0 Y! y2 ~./overcloud-deploy.sh
Grab a coffee, that may take around 1 hour (depending on your hardware).
- w! w. ~& Z: H/ y# V, G
  S% y1 U# b* bIf anything goes wrong, go to IRC on OFTC, and ask on #oooq

Description of the environment
Once deployed, inside the undercloud root directory two files are present: stackrc and overcloudrc, which will let you connect to the APIs of the undercloud (managing the openstack node), and to the overcloud (where your instances would live).
4 x' |/ D, N3 U; g0 f3 z
We can find out the existing controller/computes this way:
8 f! r5 L7 d# ~0 e
* v/ }7 a0 G( Z3 Z* [, W- [source stackrc
1 ]0 L2 a* ^  W0 w, \ openstack server list -c Name -c Networks -c Flavor
+-------------------------+------------------------+--------------+
| Name                    | Networks               | Flavor       |
+-------------------------+------------------------+--------------+
| overcloud-controller-1  | ctlplane=192.168.24.16 | oooq_control |
9 E- {$ O/ c0 @; z- x% I, f| overcloud-controller-0  | ctlplane=192.168.24.14 | oooq_control |
; n, `0 U& y3 D- L0 p, N8 }5 v| overcloud-controller-2  | ctlplane=192.168.24.12 | oooq_control |
5 e* V; \# f$ \! s+ X| overcloud-novacompute-0 | ctlplane=192.168.24.13 | oooq_compute |
; }, `6 x4 p0 X+ B9 D+-------------------------+------------------------+--------------+
Network architecture of the environment
TripleO Quickstart single NIC with vlans
Connecting to one of the nodes via ssh
( G1 M3 m( f5 n) n' YWe can connect to the IP address in the openstack server list we showed before.

ssh heat-admin@192.168.24.16
  C6 R+ a4 p) E2 h% M9 kLast login: Wed Feb 21 14:11:40 2018 from 192.168.24.1
: q% `( e2 q: V5 U
ps fax | grep ovn-controller
20422 ?        S<s   30:40 ovn-controller unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --no-chdir --log-file=/var/log/openvswitch/ovn-controller.log --pidfile=/var/run/openvswitch/ovn-controller.pid --detach
/ M$ l- d+ L& `0 @2 \$ {6 @
1 L  h! s1 \  |, M+ d4 C) G7 O' qsudo ovs-vsctl show
bb413f44-b74f-4678-8d68-a2c6de725c73
2 T4 a" b" P4 w* ZBridge br-ex
  fail_mode: standalone
  ...
; N& w" H1 V3 N) J8 `) I$ H: q  Port "patch-provnet-84d63c87-aad1-43d0-bdc9-dca5145b6fe6-to-br-int"
5 K5 G1 x6 G5 Q" }      Interface "patch-provnet-84d63c87-aad1-43d0-bdc9-dca5145b6fe6-to-br-int"
! [7 O* c9 F# Y; {; p$ D          type: patch
# |6 e; J; g. ?# ?% V$ {0 C          options: {peer="patch-br-int-to-provnet-84d63c87-aad1-43d0-bdc9-dca5145b6fe6"}
  Port "eth0"
- X4 U8 |! }- Q/ {( i      Interface "eth0"
  ...
. y9 h, }% v+ s$ iBridge br-int
  fail_mode: secure
. m" B# K# h" x' k4 F   Port "ovn-c8b85a-0"
   Interface "ovn-c8b85a-0"
/ @8 g; z  E3 O8 y/ P       type: geneve
       options: {csum="true", key=flow, remote_ip="172.16.0.17"}
( _1 J9 y6 C7 @# U# a  ?0 ~0 y3 W/ q   Port "ovn-b5643d-0"
      Interface "ovn-b5643d-0"
; e) ]% h1 Z% m) a2 C2 m          type: geneve
          options: {csum="true", key=flow, remote_ip="172.16.0.14"}
   Port "ovn-14d60a-0"
      Interface "ovn-14d60a-0"
0 `/ @0 r* B2 s; Q. Y! V5 R( Y          type: geneve
) m2 z/ Y/ H( W# P$ ^4 W0 Y          options: {csum="true", key=flow, remote_ip="172.16.0.12"}
   Port "patch-br-int-to-provnet-84d63c87-aad1-43d0-bdc9-dca5145b6fe6"
' B7 U# p' \# t" \" _      Interface "patch-br-int-to-provnet-84d63c87-aad1-43d0-bdc9-dca5145b6fe6"
          type: patch
7 \5 a3 F( F7 `          options: {peer="patch-provnet-84d63c87-aad1-43d0-bdc9-dca5145b6fe6-to-br-int"}
   Port br-int
      Interface br-int
# B) f2 A4 e; T5 Q          type: internal
, D* H  `) i, R% l$ z& NInitial resource creation
8 F9 @! n1 Q& Q: S$ LWell, now you have a virtual cloud with 3 controllers in HA, and one compute node, but no instances or routers running. We can give it a try and create a few resources:

Initial resources we can create
You can use the following script to create the resources.
6 W' S( P3 L% U0 Y5 C2 E$ h, j* G
ssh -F ~ /.quickstart/ssh.config.ansible undercloud
5 S7 b% G5 X# T2 t
source ~/overcloudrc

curl http://download.cirros-cloud.net ... 5.1-x86_64-disk.img \
  > cirros-0.5.1-x86_64-disk.img
openstack image create "cirros" --file cirros-0.5.1-x86_64-disk.img   \
               --disk-format qcow2 --container-format bare --public
  c% L2 `8 B5 a' j+ y
$ z2 W" }- X$ hopenstack network create public --provider-physical-network datacentre \
/ ~' N7 \" G0 z, b7 |/ P                                --provider-network-type vlan \
' U) V# A5 E2 p                                --provider-segment 10 \
                                --external --share
. @' R8 Q: C$ {" Q* g
openstack subnet create --network public public --subnet-range 10.0.0.0/24 \
( Z- d5 f1 H& \$ n! `                         --allocation-pool start=10.0.0.20,end=10.0.0.250 \
% T0 i+ S8 O' D$ s- [& k5 e' o                         --dns-nameserver 8.8.8.8 --gateway 10.0.0.1 \
# O, R1 K0 g, d3 r8 E7 ^                         --no-dhcp

* o$ e0 ~! m6 hopenstack network create private
3 P( O/ z4 Q- xopenstack subnet create --network private private \
                        --subnet-range 192.168.99.0/24
openstack router create router1

; y, p7 b6 h% mopenstack router set --external-gateway public router1
openstack router add subnet router1 private

- M+ n: J% I% t' Topenstack security group create test
. @. U: W. [) V; l% e: r2 dopenstack security group rule create --ingress --protocol tcp \
                                     --dst-port 22 test
! y; s. W2 M# C1 |9 |' Qopenstack security group rule create --ingress --protocol icmp test
$ i; |* s  @- Q1 [openstack security group rule create --egress test
7 q2 Q6 d. F" d, [% N' R
openstack flavor create m1.tiny --disk 1 --vcpus 1 --ram 64

PRIV_NET=$(openstack network show private -c id -f value)

openstack server create --flavor m1.tiny --image cirros \
3 l1 j4 W; [& l: x* I6 R/ `                        --nic net-id=$PRIV_NET --security-group test \
% o- R5 h) @% I. A/ R! N                        --wait cirros

openstack floating ip create --floating-ip-address 10.0.0.130 public
openstack server add floating ip cirros 10.0.0.130
" M% c; j/ R5 Q/ T- d) x7 [, R Note

$ U( d4 o1 Z7 B9 t$ \5 `' hYou can now log in into the instance if you want. In a CirrOS >0.4.0 image, the login account is cirros. The password is gocubsgo.
% G" \' Z2 u' Y: p. |
ssh cirros@10.0.0.130
cirros@10.0.0.130's password:

4 T0 @2 m! i- R- q/ [ip a | grep eth0 -A 10
1 f' F+ s1 S  v2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc pfifo_fast qlen 1000
6 w! z  L, e: e  I) a    link/ether fa:16:3e:85:b4:66 brd ff:ff:ff:ff:ff:ff
    inet 192.168.99.5/24 brd 192.168.99.255 scope global eth0
* Q( n1 U4 u: j- Q* k8 @+ _- W1 U       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe85:b466/64 scope link
- [; R+ a% |! l! `- ?5 Y- M% O       valid_lft forever preferred_lft forever

- y1 Y5 _1 t( x+ k! V4 J2 iping 10.0.0.1
PING 10.0.0.1 (10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: seq=0 ttl=63 time=2.145 ms
2 {4 f; c5 y7 [3 N3 M+ G64 bytes from 10.0.0.1: seq=1 ttl=63 time=1.025 ms
# W/ T/ P$ l- W- r# {$ M5 @64 bytes from 10.0.0.1: seq=2 ttl=63 time=0.836 ms
4 \! Q, t9 q# P! b1 [^C
, \; g& E5 ~; h7 b6 u- Q; e--- 10.0.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.836/1.335/2.145 ms
) w; l: ]4 d6 [: h+ ]3 X
ping 8.8.8.8
# r+ t' Q$ s; e( b* GPING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=52 time=3.943 ms
64 bytes from 8.8.8.8: seq=1 ttl=52 time=4.519 ms
3 @: W- [9 K& {3 \64 bytes from 8.8.8.8: seq=2 ttl=52 time=3.778 ms
2 z" i$ c( r( ]4 d0 u1 K
' x; }/ I  ^+ O8 V+ d; wcurl http://169.254.169.254/2009-04-04/meta-data/instance-id
( ?& B4 t0 r" Y  Ei-00000002
) {2 t% ?/ z* n& e& ?" L
+ H* l/ [6 `3 G* a7 b+ ]: e: L% q
/ @* Q8 l$ w4 J( X9 T# E- z2 h
7 c9 B6 R# \8 F  v  y& J& r