diff options
author | Bin Hu <bh526r@att.com> | 2015-12-24 23:02:33 -0800 |
---|---|---|
committer | Bin Hu <bh526r@att.com> | 2015-12-24 23:02:33 -0800 |
commit | a656b64800ee935870d8417ac72d3030aeb595bc (patch) | |
tree | abaed1b98900a2e95e2c11854b8f47f8ade50933 /docs/setupservicevm/index.rst | |
parent | 28ad68808e0ad96bbb3ae4adb2e5b63209f68275 (diff) |
JIRA: IPVSIX-29
Change-Id: I3e911337530ac006ec8457fa87c6a175cac23562
Signed-off-by: Bin Hu <bh526r@att.com>
Diffstat (limited to 'docs/setupservicevm/index.rst')
-rw-r--r-- | docs/setupservicevm/index.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/setupservicevm/index.rst b/docs/setupservicevm/index.rst index bc72f31..e9e7f8f 100644 --- a/docs/setupservicevm/index.rst +++ b/docs/setupservicevm/index.rst @@ -13,15 +13,15 @@ an IPv6 vRouter in OPNFV environment, i.e. integrated OpenStack with Open Daylig environment. There are three scenarios. * Scenario 1 is pre-OPNFV environment, i.e. a native OpenStack environment -without Open Daylight Controller. + without Open Daylight Controller. * Scenario 2 is an OPNFV environment where OpenStack is integrated with -Open Daylight Official Lithium Release. In this setup we use ODL for "Layer 2 connectivity" -and Neutron L3 agent for "Layer 3 routing". Because of a bug, which got fixed recently -and is not part of ODL SR3, we will have to manually execute certain commands to simulate -an external IPv6 Router in this setup. + Open Daylight Official Lithium Release. In this setup we use ODL for "Layer 2 connectivity" + and Neutron L3 agent for "Layer 3 routing". Because of a bug, which got fixed recently + and is not part of ODL SR3, we will have to manually execute certain commands to simulate + an external IPv6 Router in this setup. * Scenario 3 is similar to Scenario 2. However, we use an Open Daylight Lithium -controller which is built from the latest stable/Lithium branch which includes the fix. -In this scenario, we can fully automate the setup similar to Scenario 1. + controller which is built from the latest stable/Lithium branch which includes the fix. + In this scenario, we can fully automate the setup similar to Scenario 1. .. toctree:: :numbered: |