diff options
Diffstat (limited to 'docs')
24 files changed, 784 insertions, 334 deletions
diff --git a/docs/development/overview/containerized_compass.rst b/docs/development/overview/containerized_compass.rst index de3ec902..1df570d7 100644 --- a/docs/development/overview/containerized_compass.rst +++ b/docs/development/overview/containerized_compass.rst @@ -4,3 +4,28 @@ Introduction of Containerized Compass ===================================== + +Containerized Compass uses five compass containers instead of a single VM. + +Each container stands for a micro service and compass-core function separates into these five micro services: + + - Compass-deck : RESTful API and DB Handlers for Compass + - Compass-tasks : Registered tasks and MQ modules for Compass + - Compass-cobbler : Cobbler container for Compass + - Compass-db : Database for Compass + - Compass-mq : Message Queue for Compass + +Compass4nfv has several containers to satisfy OPNFV requirements: + + - Compass-tasks-osa : compass-task's adapter for deployment OpenStack via OpenStack-ansible + - Compass-tasks-k8s : compass-task's adapter for deployment Kubernetes + - Compass-repo-osa-ubuntu : optional container to support OPNFV offfline installation via OpenStack-ansible + - Compass-repo-osa-centos : optional container to support OPNFV offfline installation via OpenStack-ansible + +Picture below shows the new architecture of compass4nfv: + +.. figure:: images/compass_arch.png + :alt: New Archietecture of Compass4nfv + :figclass: align-center + + Fig 1. New Archietecture of Compass4nfv diff --git a/docs/development/overview/images/compass_arch.png b/docs/development/overview/images/compass_arch.png Binary files differnew file mode 100644 index 00000000..5881064f --- /dev/null +++ b/docs/development/overview/images/compass_arch.png diff --git a/docs/release/configguide/index.rst b/docs/release/configguide/index.rst deleted file mode 100644 index fae27101..00000000 --- a/docs/release/configguide/index.rst +++ /dev/null @@ -1,13 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -.. _compass4nfv-overview: - -********************************* -Compass4NFV Release Overview -********************************* - -.. toctree:: - :maxdepth: 2 - - containerized_compass.rst diff --git a/docs/release/installation/bmdeploy.rst b/docs/release/installation/bmdeploy.rst index 7bf40714..d584e938 100644 --- a/docs/release/installation/bmdeploy.rst +++ b/docs/release/installation/bmdeploy.rst @@ -199,7 +199,7 @@ IP Settings - ip_ranges -- ip addresses range provided for this network. - - cidr -- the IPv4 address and its associated routing prefix and subnet maskã + - cidr -- the IPv4 address and its associated routing prefix and subnet mask? - gw -- need to add this line only if network is external. @@ -226,11 +226,6 @@ Public VIP - interface -- mostly external. -ONOS NIC -~~~~~~~~ - - - the NIC for ONOS, if there is no ONOS configured, leave it unchanged. - Public Network ~~~~~~~~~~~~~~ @@ -316,127 +311,21 @@ Public Network **The following figure shows the interfaces and nics of JumpHost and deployment nodes in huawei-pod1 network configuration(default one nic for openstack networks).** -.. code-block:: console +.. figure:: images/single_nic.png + :alt: Single nic scenario + :figclass: align-center + Fig 1. Single nic scenario - +--------------JumpHost-------------+ - | | - | +-+Compass+-+ | - | | + +--------+ | External-network - | | eth2+---+br-ext +-+eth0+----------------------+ - | | + +--------+ | | - | | | | | - | | | | | - | | + +--------+ | Install-network | - | | eth1+---+install +-+eth1+-----------------+ | - | | + +--------+ | | | - | | | | | | - | | | | | | - | | + | IPMI-network | | - | | eth0 eth2+-----------+ | | - | | + | | | | - | +---+VM+----+ | | | | - +-----------------------------------+ | | | - | | | - | | | - | | | - | | | - +---------------Host1---------------+ | | | - | | | | | - | eth0+----------------+ | - | | | | | - | mgmt +--------+ | | | | - | | | | | | - | +-----------+ | | | | | - | external+----+ br-prv +----+eth1+---------------------+ - | +-----------+ | | | | | - | | | | | | - | storage +-----+ | | | | - | | | | | - +-----------------------------------+ | | | - | IPMI+-----------+ | | - +-----------------------------------+ | | | - | | | - | | | - | | | - +---------------Host2---------------+ | | | - | | | | | - | eth0+----------------+ | - | | | | - | mgmt +--------+ | | | - | | | | | - | +-----------+ | | | | - | external+----+ br-prv +----+eth1+---------------------+ - | +-----------+ | | | - | | | | - | storage +-----+ | | - | | | - +-----------------------------------+ | - | IPMI+-----------+ - +-----------------------------------+ **The following figure shows the interfaces and nics of JumpHost and deployment nodes in intel-pod8 network configuration(openstack networks are seperated by multiple NICs).** -.. code-block:: console - +.. figure:: images/multi_nics.png + :alt: Multiple nics scenario + :figclass: align-center - +-------------+JumpHost+------------+ - | | - | +-+Compass+-+ | - | | + +--------+ | External-network - | | eth2+---+br-ext +-+eth0+----------------------+ - | | + +--------+ | | - | | | | | - | | | | | - | | + +--------+ | Install-network | - | | eth1+---+install +-+eth1+-----------------+ | - | | + +--------+ | | | - | | | | | | - | | | | | | - | | + | IPMI-network | | - | | eth0 eth2+-----------+ | | - | | + | | | | - | +---+VM+----+ | | | | - +-----------------------------------+ | | | - | | | - | | | - | | | - | | | - +--------------+Host1+--------------+ | | | - | | | | | - | eth0+----------------+ | - | | | | | - | +--------+ | | | | - | external+----+br-prv +-+eth1+---------------------+ - | +--------+ | | | | - | storage +---------------+eth2+-------------------------+ - | | | | | | - | Mgmt +---------------+eth3+----------------------------+ - | | | | | | | - | | | | | | | - +-----------------------------------+ | | | | | - | IPMI+-----------+ | | | | - +-----------------------------------+ | | | | | - | | | | | - | | | | | - | | | | | - | | | | | - +--------------+Host2+--------------+ | | | | | - | | | | | | | - | eth0+----------------+ | | | - | | | | | | - | +--------+ | | | | | - | external+----+br-prv +-+eth1+---------------------+ | | - | +--------+ | | | | - | storage +---------------+eth2+-------------------------+ | - | | | storage-network | - | Mgmt +---------------+eth3+----------------------------+ - | | | mgmt-network - | | | - +-----------------------------------+ | - | IPMI+-----------+ - +-----------------------------------+ + Fig 2. Multiple nics scenario Start Deployment (Bare Metal Deployment) @@ -457,14 +346,14 @@ E.g. or export OS_VERSION=centos7 -1.2. Set ISO image corresponding to your code +1.2. Set tarball corresponding to your code E.g. .. code-block:: bash # Set ISO image corresponding to your code - export ISO_URL=file:///home/compass/compass4nfv.iso + export ISO_URL=file:///home/compass/compass4nfv.tar.gz 1.3. Set hardware deploy jumpserver PXE NIC. (set eth1 E.g.) You do not need to set it when virtual deploy. @@ -491,16 +380,6 @@ nosdn-nofeature scenario deploy sample # NETWORK is your network.yml's path export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml -ocl-nofeature scenario deploy sample - -.. code-block:: bash - - # DHA is your dha.yml's path - export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-ocl-nofeature-ha.yml - - # NETWORK is your network.yml's path - export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network_ocl.yml - odl_l2-moon scenario deploy sample .. code-block:: bash @@ -531,25 +410,15 @@ odl_l3-nofeature scenario deploy sample # NETWORK is your network.yml's path export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml -onos-nofeature scenario deploy sample - -.. code-block:: bash - - # DHA is your dha.yml's path - export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-onos-nofeature-ha.yml - - # NETWORK is your network.yml's path - export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network_onos.yml - -onos-sfc deploy scenario sample +odl-sfc deploy scenario sample .. code-block:: bash # DHA is your dha.yml's path - export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-onos-sfc-ha.yml + export DHA=./deploy/conf/hardware_environment/huawei-pod1/os-odl-sfc-ha.yml # NETWORK is your network.yml's path - export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network_onos.yml + export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml 2. Run ``deploy.sh`` diff --git a/docs/release/installation/featureTable.rst b/docs/release/installation/featureTable.rst index e5ad9776..2cd74a2b 100644 --- a/docs/release/installation/featureTable.rst +++ b/docs/release/installation/featureTable.rst @@ -4,48 +4,51 @@ Features Supported Openstack Version and OS ---------------------------------- -+---------------+----------+-----------+-----------+-----------+ -| | OS | OpenStack | OpenStack | OpenStack | -| | only | Liberty | Mitaka | Newton | -+---------------+----------+-----------+-----------+-----------+ -| CentOS 7 | yes | yes | yes | yes | -+---------------+----------+-----------+-----------+-----------+ -| Ubuntu trusty | yes | yes | yes | no | -+---------------+----------+-----------+-----------+-----------+ -| Ubuntu xenial | yes | no | yes | yes | -+---------------+----------+-----------+-----------+-----------+ ++---------------+----------+-----------+-----------+-----------+-----------+ +| | OS | OpenStack | OpenStack | OpenStack | OpenStack | +| | only | Liberty | Mitaka | Newton | Ocata | ++---------------+----------+-----------+-----------+-----------+-----------+ +| CentOS 7 | yes | yes | yes | yes | no | ++---------------+----------+-----------+-----------+-----------+-----------+ +| Ubuntu trusty | yes | yes | yes | no | no | ++---------------+----------+-----------+-----------+-----------+-----------+ +| Ubuntu xenial | yes | no | yes | yes | yes | ++---------------+----------+-----------+-----------+-----------+-----------+ Supported Openstack Flavor and Features --------------------------------------- -+---------------+--------------+--------------+---------------+ -| | OpenStack | OpenStack | OpenStack | -| | Liberty | Mitaka | Newton | -+---------------+--------------+--------------+---------------+ -| Virtual | Yes | Yes | Yes | -| Deployment | | | | -+---------------+--------------+--------------+---------------+ -| Baremetal | Yes | Yes | Yes | -| Deployment | | | | -+---------------+--------------+--------------+---------------+ -| HA | Yes | Yes | Yes | -| | | | | -+---------------+--------------+--------------+---------------+ -| Ceph | Yes | Yes | Yes | -| | | | | -+---------------+--------------+--------------+---------------+ -| SDN | Yes | Yes | Yes* | -| ODL/ONOS | | | | -+---------------+--------------+--------------+---------------+ -| Compute Node | Yes | Yes | Yes | -| Expansion | | | | -+---------------+--------------+--------------+---------------+ -| Multi-Nic | Yes | Yes | Yes | -| Support | | | | -+---------------+--------------+--------------+---------------+ -| Boot | Yes | Yes | Yes | -| Recovery | | | | -+---------------+--------------+--------------+---------------+ ++---------------+--------------+--------------+---------------+---------------+ +| | OpenStack | OpenStack | OpenStack | OpenStack | +| | Liberty | Mitaka | Newton | Ocata | ++---------------+--------------+--------------+---------------+---------------+ +| Virtual | Yes | Yes | Yes | Yes | +| Deployment | | | | | ++---------------+--------------+--------------+---------------+---------------+ +| Baremetal | Yes | Yes | Yes | Yes | +| Deployment | | | | | ++---------------+--------------+--------------+---------------+---------------+ +| HA | Yes | Yes | Yes | Yes | +| | | | | | ++---------------+--------------+--------------+---------------+---------------+ +| Ceph | Yes | Yes | Yes | Yes | +| | | | | | ++---------------+--------------+--------------+---------------+---------------+ +| SDN | Yes | Yes | Yes | Yes* | +| ODL/ONOS | | | | | ++---------------+--------------+--------------+---------------+---------------+ +| Compute Node | Yes | Yes | Yes | No | +| Expansion | | | | | ++---------------+--------------+--------------+---------------+---------------+ +| Multi-Nic | Yes | Yes | Yes | Yes | +| Support | | | | | ++---------------+--------------+--------------+---------------+---------------+ +| Boot | Yes | Yes | Yes | Yes | +| Recovery | | | | | ++---------------+--------------+--------------+---------------+---------------+ +| SFC | No | No | Yes | Yes | +| | | | | | ++---------------+--------------+--------------+---------------+---------------+ -* ONOS support will Release in Danube 2.0 or 3.0 +* ONOS will not be supported in this release. diff --git a/docs/release/installation/images/architecture.png b/docs/release/installation/images/architecture.png Binary files differnew file mode 100644 index 00000000..0ee8bceb --- /dev/null +++ b/docs/release/installation/images/architecture.png diff --git a/docs/release/installation/images/k8s.png b/docs/release/installation/images/k8s.png Binary files differnew file mode 100644 index 00000000..6af82dcc --- /dev/null +++ b/docs/release/installation/images/k8s.png diff --git a/docs/release/installation/images/multi_nics.png b/docs/release/installation/images/multi_nics.png Binary files differnew file mode 100644 index 00000000..5f48b6c5 --- /dev/null +++ b/docs/release/installation/images/multi_nics.png diff --git a/docs/release/installation/images/single_nic.png b/docs/release/installation/images/single_nic.png Binary files differnew file mode 100644 index 00000000..c3898560 --- /dev/null +++ b/docs/release/installation/images/single_nic.png diff --git a/docs/release/installation/index.rst b/docs/release/installation/index.rst index d678b9df..80d07e86 100644 --- a/docs/release/installation/index.rst +++ b/docs/release/installation/index.rst @@ -17,6 +17,8 @@ Compass4nfv Installation Instructions configure-network.rst bmdeploy.rst vmdeploy.rst + k8s-intro.rst + k8s-deploy.rst offline-deploy.rst expansion.rst references.rst diff --git a/docs/release/installation/installation.rst b/docs/release/installation/installation.rst index 18bac119..05c5e2ef 100644 --- a/docs/release/installation/installation.rst +++ b/docs/release/installation/installation.rst @@ -6,7 +6,7 @@ Compass4nfv configuration ========================= This document describes providing guidelines on how to install and -configure the Danube release of OPNFV when using Compass as a +configure the Euphrates release of OPNFV when using Compass4nfv as a deployment tool including required software and hardware configurations. @@ -21,29 +21,28 @@ networking and Unix/Linux administration. Preconditions ------------- -Before starting the installation of the Danube release of OPNFV, +Before starting the installation of the Euphrates release of OPNFV, some planning must be done. -Retrieving the installation ISO image -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Retrieving the installation Tarball +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -First of all, The installation ISO is needed for deploying your OPNFV -environment, it included packages of Compass, OpenStack, OpenDaylight, ONOS -and so on. +First of all, The installation tarball is needed for deploying your OPNFV +environment, it included packages of compass docker images and OSA repo. -The stable release ISO can be retrieved via `OPNFV software download page <https://www.opnfv.org/software>`_ +The stable tarball can be retrieved via `OPNFV software download page <https://www.opnfv.org/software>`_ -The daily build ISO can be retrieved via OPNFV artifacts repository: +The daily build tarball can be retrieved via OPNFV artifacts repository: http://artifacts.opnfv.org/compass4nfv.html -NOTE: Search the keyword "compass4nfv/Danube" to locate the ISO image. +NOTE: Search the keyword "compass4nfv/Euphrates" to locate the ISO image. E.g. -compass4nfv/Danube/opnfv-2016-09-18_08-15-13.iso +compass4nfv/Euphrates/opnfv-2017-09-18_08-15-13.tar.gz -The name of iso image includes the time of iso building, you can get the daily +The name of tarball includes the time of iso building, you can get the daily ISO according the building time. The git url and sha1 of Compass4nfv are recorded in properties files, According these, the corresponding deployment scripts can be retrieved. @@ -58,9 +57,9 @@ To retrieve the repository of Compass4nfv on Jumphost use the following command: NOTE: PLEASE DO NOT GIT CLONE COMPASS4NFV IN ROOT DIRECTORY(INCLUDE SUBFOLDERS). -To get stable /Danube release, you can use the following command: +To get stable /Euphrates release, you can use the following command: -- git checkout Danube.1.0 +- git checkout Euphrates.1.0 Setup Requirements ------------------ @@ -126,17 +125,17 @@ Network requirements include: - IPMI Network - - Openstack mgmt Network* + - br-mgmt Network* - - Openstack external Network* + - br-vlan Network* - - Openstack tenant Network* + - br-tenant Network* - - Openstack storage Network* + - br-storage Network* 3. Lights out OOB network access from Jumphost with IPMI node enabled (Bare Metal deployment only). -4. External network has Internet access, meaning a gateway and DNS availability. +4. br-vlan network has Internet access, meaning a gateway and DNS availability. **The networks with(*) can be share one NIC(Default configuration) or use an exclusive** **NIC(Reconfigurated in network.yml).** diff --git a/docs/release/installation/introduction.rst b/docs/release/installation/introduction.rst index 7470363a..6ffc3d17 100644 --- a/docs/release/installation/introduction.rst +++ b/docs/release/installation/introduction.rst @@ -5,34 +5,8 @@ Abstract ======== -This document describes how to install the Danube release of OPNFV when +This document describes how to install the Euphrates release of OPNFV when using Compass4nfv as a deployment tool covering it's limitations, dependencies and required system resources. -Version history -=============== - -+--------------------+--------------------+--------------------+---------------------------+ -| **Date** | **Ver.** | **Author** | **Comment** | -| | | | | -+--------------------+--------------------+--------------------+---------------------------+ -| 2017-02-21 | 3.0.0 | Justin chi | Changes for D release | -| | | (HUAWEI) | | -+--------------------+--------------------+--------------------+---------------------------+ -| 2016-09-13 | 2.1.0 | Yuenan Li | Adjusted the docs | -| | | (HUAWEI) | structure | -+--------------------+--------------------+--------------------+---------------------------+ -| 2016-09-12 | 2.0.0 | Yuenan Li | Rewritten for | -| | | (HUAWEI) | Compass4nfv C release | -+--------------------+--------------------+--------------------+---------------------------+ -| 2016-01-17 | 1.0.0 | Justin chi | Rewritten for | -| | | (HUAWEI) | Compass4nfv B release | -+--------------------+--------------------+--------------------+---------------------------+ -| 2015-12-16 | 0.0.2 | Matthew Li | Minor changes & | -| | | (HUAWEI) | formatting | -+--------------------+--------------------+--------------------+---------------------------+ -| 2015-09-12 | 0.0.1 | Chen Shuai | First draft | -| | | (HUAWEI) | | -+--------------------+--------------------+--------------------+---------------------------+ - diff --git a/docs/release/installation/k8s-deploy.rst b/docs/release/installation/k8s-deploy.rst new file mode 100644 index 00000000..65f638cb --- /dev/null +++ b/docs/release/installation/k8s-deploy.rst @@ -0,0 +1,267 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) by Yifei Xue (HUAWEI) and Justin Chi (HUAWEI) + +Installation of K8s on virtual machines +======================================= + +Quick Start +----------- + +Only 1 command to try virtual deployment, if you have Internet access. Just Paste it and Run. + +.. code-block:: bash + + curl https://raw.githubusercontent.com/opnfv/compass4nfv/master/quickstart_k8s.sh | bash + +If you want to deploy noha with1 controller and 1 compute, run the following command + +.. code-block:: bash + + export SCENARIO=k8-nosdn-nofeature-noha.yml + export VIRT_NUMBER=2 + curl https://raw.githubusercontent.com/opnfv/compass4nfv/euphrates/quickstart_k8s.sh | bash + +Installation of K8s on Bare Metal +================================= + +Nodes Configuration (Bare Metal Deployment) +------------------------------------------- + +The below file is the inventory template of deployment nodes: + +"compass4nfv/deploy/conf/hardware_environment/huawei-pod1/k8-nosdn-nofeature-ha.yml" + +You can write your own IPMI IP/User/Password/Mac address/roles reference to it. + + - name -- Host name for deployment node after installation. + + - ipmiVer -- IPMI interface version for deployment node support. IPMI 1.0 + or IPMI 2.0 is available. + + - ipmiIP -- IPMI IP address for deployment node. Make sure it can access + from Jumphost. + + - ipmiUser -- IPMI Username for deployment node. + + - ipmiPass -- IPMI Password for deployment node. + + - mac -- MAC Address of deployment node PXE NIC. + + - interfaces -- Host NIC renamed according to NIC MAC addresses when OS provisioning. + + - roles -- Components deployed. + +**Set TYPE/FLAVOR and POWER TOOL** + +E.g. +.. code-block:: yaml + + TYPE: baremetal + FLAVOR: cluster + POWER_TOOL: ipmitool + +**Set ipmiUser/ipmiPass and ipmiVer** + +E.g. + +.. code-block:: yaml + + ipmiUser: USER + ipmiPass: PASSWORD + ipmiVer: '2.0' + +**Assignment of different roles to servers** + +E.g. K8s only deployment roles setting + +.. code-block:: yaml + + hosts: + - name: host1 + mac: 'F8:4A:BF:55:A2:8D' + interfaces: + - eth1: 'F8:4A:BF:55:A2:8E' + ipmiIp: 172.16.130.26 + roles: + - kube_master + - etcd + + - name: host2 + mac: 'D8:49:0B:DA:5A:B7' + interfaces: + - eth1: 'D8:49:0B:DA:5A:B8' + ipmiIp: 172.16.130.27 + roles: + - kube_node + +Network Configuration (Bare Metal Deployment) +--------------------------------------------- + +Before deployment, there are some network configuration to be checked based +on your network topology.Compass4nfv network default configuration file is +"compass4nfv/deploy/conf/hardware_environment/huawei-pod1/network.yml". +This file is an example, you can customize by yourself according to specific network +environment. + +In this network.yml, there are several config sections listed following(corresponed to the +ordre of the config file): + +Provider Mapping +~~~~~~~~~~~~~~~~ + + - name -- provider network name. + + - network -- default as physnet, do not change it. + + - interfaces -- the NIC or Bridge attached by the Network. + + - type -- the type of the NIC or Bridge(vlan for NIC and ovs for Bridge, either). + + - roles -- all the possible roles of the host machines which connected by this + network(mostly put both controller and compute). + +System Interface +~~~~~~~~~~~~~~~~ + + - name -- Network name. + + - interfaces -- the NIC or Bridge attached by the Network. + + - vlan_tag -- if type is vlan, add this tag before 'type' tag. + + - type -- the type of the NIC or Bridge(vlan for NIC and ovs for Bridge, either). + + - roles -- all the possible roles of the host machines which connected by this + network(mostly put both controller and compute). + +IP Settings +~~~~~~~~~~~ + + - name -- network name corresponding the the network name in System Interface section one by one. + + - ip_ranges -- ip addresses range provided for this network. + + - cidr -- the IPv4 address and its associated routing prefix and subnet mask? + + - gw -- need to add this line only if network is external. + + - roles -- all the possible roles of the host machines which connected by this + network(mostly put both controller and compute). + +Internal VIP(virtual or proxy IP) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + + - ip -- virtual or proxy ip address, must be in the same subnet with mgmt network + but must not be in the range of mgmt network. + + - netmask -- the length of netmask + + - interface -- mostly mgmt. + +Public VIP +~~~~~~~~~~ + + - ip -- virtual or proxy ip address, must be in the same subnet with external + network but must not be in the range of external network. + + - netmask -- the length of netmask + + - interface -- mostly external. + + +Public Network +~~~~~~~~~~~~~~ + + - enable -- must be True(if False, you need to set up provider network manually). + + - network -- leave it ext-net. + + - type -- the type of the ext-net above, such as flat or vlan. + + - segment_id -- when the type is vlan, this should be id of vlan. + + - subnet -- leave it ext-subnet. + + - provider_network -- leave it physnet. + + - router -- leave it router-ext. + + - enable_dhcp -- must be False. + + - no_gateway -- must be False. + + - external_gw -- same as gw in ip_settings. + + - floating_ip_cidr -- cidr for floating ip, see explanation in ip_settings. + + - floating_ip_start -- define range of floating ip with floating_ip_end(this + defined range must not be included in ip range of external configured in + ip_settings section). + + - floating_ip_end -- define range of floating ip with floating_ip_start. + + +**The following figure shows the default network configuration.** + +.. figure:: images/k8s.png + :alt: Kubernetes network configuration + :figclass: align-center + + Fig 5. Kubernetes network configuration + +Start Deployment (Bare Metal Deployment) +---------------------------------------- + +1. Edit deploy.sh + +1.1. Set OS version for deployment nodes. + Compass4nfv supports ubuntu and centos based openstack newton. + +E.g. + +.. code-block:: bash + + # Set OS version for target hosts + # Only CentOS7 supported now + export OS_VERSION=centos7 + +1.2. Set tarball corresponding to your code + +E.g. + +.. code-block:: bash + + # Set ISO image corresponding to your code + export ISO_URL=file:///home/compass/compass4nfv.tar.gz + +1.3. Set hardware deploy jumpserver PXE NIC. (set eth1 E.g.) + You do not need to set it when virtual deploy. + +E.g. + +.. code-block:: bash + + # Set hardware deploy jumpserver PXE NIC + # you need to comment out it when virtual deploy + export INSTALL_NIC=eth1 + +1.4. K8s scenario that you want to deploy + +E.g. + +nosdn-nofeature scenario deploy sample + +.. code-block:: bash + + # DHA is your dha.yml's path + export DHA=./deploy/conf/hardware_environment/huawei-pod1/k8-nosdn-nofeature-ha.yml + + # NETWORK is your network.yml's path + export NETWORK=./deploy/conf/hardware_environment/huawei-pod1/network.yml + +2. Run ``deploy.sh`` + +.. code-block:: bash + + ./deploy.sh diff --git a/docs/release/installation/k8s-intro.rst b/docs/release/installation/k8s-intro.rst new file mode 100644 index 00000000..a3ea4547 --- /dev/null +++ b/docs/release/installation/k8s-intro.rst @@ -0,0 +1,96 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) by Yifei Xue (HUAWEI) and Justin Chi (HUAWEI) + +K8s introduction +================ + +Kubernetes Architecture +----------------------- + +Currently Compass can deploy kubernetes as NFVI in 3+2 mode by default. + +**The following figure shows a typical architecture of Kubernetes.** + +.. figure:: images/architecture.png + :alt: K8s architecture + :figclass: align-center + + Fig 3. K8s architecture + +Kube-apiserver +~~~~~~~~~~~~~~ + +Kube-apiserver exposes the Kubernetes API. It is the front-end for the Kubernetes control plane. +It is designed to scale horizontally, that is, it scales by deploying more instances. + +Etcd +~~~~ + +Etcd is used as Kubernetes' backing store. All cluster data is stored here. Always have a backup +plan for etcd's data for your Kubernetes cluster. + +Kube-controller-manager +~~~~~~~~~~~~~~~~~~~~~~~ + +Kube-controller-manager runs controllers, which are the background threads that handle routine +tasks in the cluster. Logically, each controller is a separate process, but to reduce complexity, +they are all compiled into a single binary and run in a single process. + +These controllers include: + + - Node Controller: Responsible for noticing and responding when nodes go down. + - Replication Controller: Responsible for maintaining the correct number of pods for every + replication controller object in the system. + - Endpoints Controller: Populates the Endpoints object (that is, joins Services & Pods). + - Service Account & Token Controllers: Create default accounts and API access tokens for + new namespaces. + +kube-scheduler +~~~~~~~~~~~~~~ + +Kube-scheduler watches newly created pods that have no node assigned, and selects a node for them +to run on. + +Kubelet +~~~~~~~ + +Kubelet is the primary node agent. It watches for pods that have been assigned to its node (either +by apiserver or via local configuration file) and: + + - Mounts the pod's required volumes. + - Downloads the pod's secrets. + - Runs the pod's containers via docker (or, experimentally, rkt). + - Periodically executes any requested container liveness probes. + - Reports the status of the pod back to the rest of the system, by creating a mirror pod if + necessary. + - Reports the status of the node back to the rest of the system. + +Kube-proxy +~~~~~~~~~~ + +Kube-proxy enables the Kubernetes service abstraction by maintaining network rules on the host and +performing connection forwarding. + +Docker +~~~~~~ + +Docker is used for running containers. + +POD +~~~ + +A pod is a collection of containers and its storage inside a node of a Kubernetes cluster. It is +possible to create a pod with multiple containers inside it. For example, keeping a database container +and data container in the same pod. + +Understand Kubernetes Networking in Compass configuration +--------------------------------------------------------- + +**The following figure shows the Kubernetes Networking in Compass configuration.** + +.. figure:: images/k8s.png + :alt: Kubernetes Networking in Compass + :figclass: align-center + + Fig 4. Kubernetes Networking in Compass diff --git a/docs/release/installation/offline-deploy.rst b/docs/release/installation/offline-deploy.rst index 0acfa180..d35d7e1b 100644 --- a/docs/release/installation/offline-deploy.rst +++ b/docs/release/installation/offline-deploy.rst @@ -3,15 +3,15 @@ Offline Deploy ============== -Compass4nfv uses offline approach to deploy cluster and support complete offline -deployment on a jumphost without access internet. Here is the offline deployment -instruction: +Compass4nfv uses a repo docker container as distro and pip package source +to deploy cluster and support complete offline deployment on a jumphost without +access internet. Here is the offline deployment instruction: Preparation for offline deploy ------------------------------ -1. Download compass.iso from OPNFV artifacts repository (Search compass4nfv in - http://artifacts.opnfv.org/ and download an appropriate ISO. ISO can also be +1. Download compass.tar.gz from OPNFV artifacts repository (Search compass4nfv in + http://artifacts.opnfv.org/ and download an appropriate tarball. Tarball can also be generated by script build.sh in compass4nfv root directory.) 2. Download the Jumphost preparation package from our httpserver. (Download the @@ -25,10 +25,10 @@ Preparation for offline deploy Steps of offline deploy ----------------------- -1. Copy the compass.iso, jh_env_package.tar.gz and the compass4nfv code +1. Copy the compass.tar.gz, jh_env_package.tar.gz and the compass4nfv code repository to your jumphost. -2. Export the local path of the compass.iso and jh_env_package.tar.gz on +2. Export the local path of the compass.tar.gz and jh_env_package.tar.gz on jumphost. Then you can perform deployment on a offline jumphost. E.g. @@ -41,7 +41,13 @@ Export the compass4nfv.iso and jh_env_package.tar.gz path export ISO_URL=file:///home/compass/compass4nfv.iso export JHPKG_URL=file:///home/compass/jh_env_package.tar.gz -Run deploy.sh +3. Open the OSA offline deployment switch on jumphost. + +.. code-block:: bash + + export OFFLINE_DEPLOY=Enable + +4. Run deploy.sh .. code-block:: bash diff --git a/docs/release/installation/preconditions.rst b/docs/release/installation/preconditions.rst index 67c0728a..3ba42ab6 100644 --- a/docs/release/installation/preconditions.rst +++ b/docs/release/installation/preconditions.rst @@ -21,30 +21,30 @@ networking and Unix/Linux administration. Preconditions ------------- -Before starting the installation of the Danube release of OPNFV, +Before starting the installation of the Euphrates release of OPNFV, some planning must be done. -Retrieving the installation ISO image -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Retrieving the installation tarball +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -First of all, The installation ISO is needed for deploying your OPNFV +First of all, The installation tarball is needed for deploying your OPNFV environment, it included packages of Compass, OpenStack, OpenDaylight, ONOS and so on. -The stable release ISO can be retrieved via `OPNFV software download page <https://www.opnfv.org/software>`_ +The stable release tarball can be retrieved via `OPNFV software download page <https://www.opnfv.org/software>`_ -The daily build ISO can be retrieved via OPNFV artifacts repository: +The daily build tarball can be retrieved via OPNFV artifacts repository: http://artifacts.opnfv.org/compass4nfv.html -NOTE: Search the keyword "compass4nfv/Danube" to locate the ISO image. +NOTE: Search the keyword "compass4nfv/Euphrates" to locate the tarball. E.g. -compass4nfv/danube/opnfv-2017-03-29_08-55-09.iso +compass4nfv/euphrates/opnfv-2017-03-29_08-55-09.tar.gz -The name of iso image includes the time of iso building, you can get the daily -ISO according the building time. +The name of tarball includes the time of tarball building, you can get the daily +tarball according the building time. The git url and sha1 of Compass4nfv are recorded in properties files, According these, the corresponding deployment scripts can be retrieved. @@ -58,9 +58,9 @@ To retrieve the repository of Compass4nfv on Jumphost use the following command: NOTE: PLEASE DO NOT GIT CLONE COMPASS4NFV IN ROOT DIRECTORY(INCLUDE SUBFOLDERS). -To get stable /Danube release, you can use the following command: +To get stable/euphrates release, you can use the following command: -- git checkout Danube.1.0 +- git checkout Euphrates.1.0 Setup Requirements ------------------ diff --git a/docs/release/installation/vmdeploy.rst b/docs/release/installation/vmdeploy.rst index 610ff51a..16fb28d3 100644 --- a/docs/release/installation/vmdeploy.rst +++ b/docs/release/installation/vmdeploy.rst @@ -5,6 +5,22 @@ Installation on virtual machines ================================ +Quick Start +----------- + +Only 1 command to try virtual deployment, if you have Internet access. Just Paste it and Run. + +.. code-block:: bash + + curl https://raw.githubusercontent.com/opnfv/compass4nfv/euphrates/quickstart.sh | bash + +If you want to deploy noha with1 controller and 1 compute, run the following command + +.. code-block:: bash + export SCENARIO=os-nosdn-nofeature-noha.yml + export VIRT_NUMBER=2 + curl https://raw.githubusercontent.com/opnfv/compass4nfv/euphrates/quickstart.sh | bash + Nodes Configuration (Virtual Deployment) ---------------------------------------- @@ -129,7 +145,7 @@ Start Deployment (Virtual Deployment) 1. Edit deploy.sh 1.1. Set OS version for deployment nodes. - Compass4nfv supports ubuntu and centos based openstack newton. + Compass4nfv supports ubuntu and centos based openstack ocata. E.g. @@ -148,7 +164,7 @@ E.g. .. code-block:: bash # Set ISO image corresponding to your code - export ISO_URL=file:///home/compass/compass4nfv.iso + export ISO_URL=file:///home/compass/compass4nfv.tar.gz 1.3. Set scenario that you want to deploy @@ -164,16 +180,6 @@ nosdn-nofeature scenario deploy sample # NETWORK is your network.yml's path export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network.yml -ocl-nofeature scenario deploy sample - -.. code-block:: bash - - # DHA is your dha.yml's path - export DHA=./deploy/conf/vm_environment/os-ocl-nofeature-ha.yml - - # NETWORK is your network.yml's path - export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network_ocl.yml - odl_l2-moon scenario deploy sample .. code-block:: bash @@ -204,25 +210,15 @@ odl_l3-nofeature scenario deploy sample # NETWORK is your network.yml's path export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network.yml -onos-nofeature scenario deploy sample +odl-sfc deploy scenario sample .. code-block:: bash # DHA is your dha.yml's path - export DHA=./deploy/conf/vm_environment/os-onos-nofeature-ha.yml + export DHA=./deploy/conf/vm_environment/os-odl-sfc-ha.yml # NETWORK is your network.yml's path - export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network_onos.yml - -onos-sfc deploy scenario sample - -.. code-block:: bash - - # DHA is your dha.yml's path - export DHA=./deploy/conf/vm_environment/os-onos-sfc-ha.yml - - # NETWORK is your network.yml's path - export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network_onos.yml + export NETWORK=./deploy/conf/vm_environment/huawei-virtual1/network.yml 2. Run ``deploy.sh`` diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst index 99e18b54..73825062 100644 --- a/docs/release/release-notes/release-notes.rst +++ b/docs/release/release-notes/release-notes.rst @@ -31,7 +31,7 @@ Release Data | **Release designation** | Euphrates.1.0 | | | | +--------------------------------------+--------------------------------------+ -| **Release date** | September 2017 | +| **Release date** | October 2017 | | | | +--------------------------------------+--------------------------------------+ | **Purpose of the delivery** | OPNFV Euphrates release | @@ -69,13 +69,10 @@ upstream components supported with this release. - Openstack (Ocata release) - - Opendaylight (Nitrogen release) - + - Kubernates (1.7.3) -Document version change -~~~~~~~~~~~~~~~~~~~~~~~ + - Opendaylight (Nitrogen release) -Adjusted the document structure, and you can see document at `OPNFV(Euphrates) Compass4nfv installation instructions <http://artifacts.opnfv.org/compass4nfv/docs/configguide/index.html>`_. Reason for new version ---------------------- @@ -87,16 +84,24 @@ Feature additions | **JIRA REFERENCE** | **SLOGAN** | | | | +--------------------------------------+-----------------------------------------+ -| COMPASS-504 | Open-O deployment with Compass | +| COMPASS-549 | Real Time KVM | | | | +--------------------------------------+-----------------------------------------+ -| COMPASS-362 | OpenDaylight Boron Support | +| | OpenDaylight Nitrogen Support | | | | +--------------------------------------+-----------------------------------------+ -| COMPASS-491 | Support OpenStack Newton | +| COMPASS-542 | Support OpenStack Ocata | +| | | ++--------------------------------------+-----------------------------------------+ +| | Support ODL SFC | +| | | ++--------------------------------------+-----------------------------------------+ +| COMPASS-550 | Support OVS-DPDK | +| | | ++--------------------------------------+-----------------------------------------+ +| COMPASS-495 | Yardstick Integration into Compass4nfv | | | | +--------------------------------------+-----------------------------------------+ - Bug corrections @@ -104,13 +109,13 @@ Bug corrections **JIRA TICKETS:** -+--------------------------------------+--------------------------------------+ -| **JIRA REFERENCE** | **SLOGAN** | -| | | -+--------------------------------------+--------------------------------------+ -| | | -| | | -+--------------------------------------+--------------------------------------+ ++--------------------------------------+----------------------------------------+ +| **JIRA REFERENCE** | **SLOGAN** | +| | | ++--------------------------------------+----------------------------------------+ +| | With no ceph, the cluster will heal | +| | itself after a power failure or reboot | ++--------------------------------------+----------------------------------------+ Known Limitations, Issues and Workarounds @@ -127,25 +132,30 @@ System Limitations **Min Jumphost requirements:** At least 16GB of RAM, 16 core CPU +Scenario Limitations +-------------------- + +**ODL SFC:** In the Euphrates1.0, Compass doesn't integrate OpenStack Tacker +Project yet. However, the SFC related test cases in Functest always use Tacker +as NFVO to delivery VNFFG or SFC related requests to ODL via networking-sfc. +So the odl-sfc scenario of Compass cannot pass the SFC testcases in Functest. +But if you want to use verify SFC in the cluster deployed by Compass, you can +use neutron CLI to achieve the same effect. + Known issues ------------ -+----------------------+-------------------------------+-----------------------+ -| **Scenario** | **Issue** | **Workarounds** | -+----------------------+-------------------------------+-----------------------+ -| os-odl-l3-no-feature | Occasionally failed to assign | Rebuild the instance | -| | floating IP to an instance | and reassign floating | -| | | IP | -+----------------------+-------------------------------+-----------------------+ -| os-odl-l2-no-feature | Occasionally failed to login | Failed in testcase, | -| | instance via ssh | normal in usage | -+----------------------+-------------------------------+-----------------------+ - ++-----------------------+---------------------------------+-----------------------+ +| **Scenario** | **Issue** | **Workarounds** | ++-----------------------+---------------------------------+-----------------------+ +| Ceph Related Scenario | After a power failure or reboot,| Deploy without Ceph | +| | the cluster cannot heal itself | | ++-----------------------+---------------------------------+-----------------------+ Test Result =========== The Euphrates release with the Compass4nfv deployment toolchain has undergone QA test runs with the following results: -Functest: http://testresults.opnfv.org/reporting/functest/release/danube/index-status-compass.html +Functest: http://testresults.opnfv.org/reporting/euphrates/functest/status-compass.html diff --git a/docs/release/scenarios/index.rst b/docs/release/scenarios/index.rst index a00eb44a..131e9852 100644 --- a/docs/release/scenarios/index.rst +++ b/docs/release/scenarios/index.rst @@ -12,4 +12,7 @@ Compass4NFV Scenarios os-nosdn-nofeature-ha.rst os-odl-nofeature-ha.rst + os-odl-sfc-ha.rst + os-nosdn-kvm-ha.rst + k8s-nosdn-nofeature-ha.rst diff --git a/docs/release/scenarios/k8s-nosdn-nofeature-ha.rst b/docs/release/scenarios/k8s-nosdn-nofeature-ha.rst new file mode 100644 index 00000000..d9925cb7 --- /dev/null +++ b/docs/release/scenarios/k8s-nosdn-nofeature-ha.rst @@ -0,0 +1,39 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) Justin Chi (HUAWEI),Yifei Xue (HUAWEI)and Xinhui Hu (FIBERHOME) + +This document introduces scenario descriptions for Euphrates 1.0 of +deployment with no SDN controller and no feature enabled. + +.. contents:: + :depth: 3 + :local: + +====================== +k8s-nosdn-nofeature-ha +====================== + +This scenario is used to deploy an kubernets cluster. + +Scenario components and composition +=================================== + +This scenario includes a set of kubernets services which are kubernets API Server, +Controller Manager, kube-proxy, kubelet,kube-dns,nginx-proxy,kubernetes-dashboard. +Nginx-proxy is used to balance all the services running on 3 control nodes behind +a VIP (Virtual IP address). + +Scenario usage overview +======================= + +To deploy with this scenario, you just need to assign the +k8s-nosdn-nofeature-ha.yaml to DHA file before deployment. + +Limitations, Issues and Workarounds +=================================== + +References +========== + +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/euphrates diff --git a/docs/release/scenarios/os-nosdn-nofeature-ha.rst b/docs/release/scenarios/os-nosdn-nofeature-ha.rst new file mode 100644 index 00000000..6ff3b85c --- /dev/null +++ b/docs/release/scenarios/os-nosdn-nofeature-ha.rst @@ -0,0 +1,41 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) Justin Chi (HUAWEI) and Yifei Xue (HUAWEI) + +This document introduces scenario descriptions for Euphrates 1.0 of +deployment with no SDN controller and no feature enabled. + +.. contents:: + :depth: 3 + :local: + +===================== +os-nosdn-nofeature-ha +===================== + +This scenario is used to deploy an Ocata OpenStack deployment with +Ceph Jewel, and without SDN controller nor any NFV feature enabled. + +Scenario components and composition +=================================== + +This scenario includes a set of common OpenStack services which are Nova, +Neutron, Glance, Cinder, Keystone, Heat, Ceilometer, Gnocchi, Aodh, +Horizon. Ceph is used as the backend of Cinder on deployed hosts. HAproxy +is used to balance all the services running on 3 control nodes behind a +VIP (Virtual IP address). + +Scenario usage overview +======================= + +To deploy with this scenario, you just need to assign the +os-nosdn-nofeature-ha.yaml to DHA file before deployment. + +Limitations, Issues and Workarounds +=================================== + +References +========== + +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/euphrates diff --git a/docs/release/scenarios/os-odl-nofeature-ha.rst b/docs/release/scenarios/os-odl-nofeature-ha.rst new file mode 100644 index 00000000..64e74e04 --- /dev/null +++ b/docs/release/scenarios/os-odl-nofeature-ha.rst @@ -0,0 +1,43 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) Justin Chi (HUAWEI) and Yifei Xue (HUAWEI) + +This document introduces scenario descriptions for Euphrates 1.0 of +deployment with the OpenDaylight controller and no feature enabled. + +.. contents:: + :depth: 3 + :local: + +=================== +os-odl-nofeature-ha +=================== + +This scenario is used to deploy an Ocata OpenStack deployment with +OpenDaylight Nitrogen, Ceph Jewel, and without any NFV feature enabled. + +Scenario components and composition +=================================== + +This scenario includes a set of common OpenStack services which are Nova, +Neutron, Glance, Cinder, Keystone, Heat, Ceilometer, Gnocchi, Aodh, +Horizon. Ceph is used as the backend of Cinder on deployed hosts. HAproxy +is used to balance all the services running on 3 control nodes behind a +VIP (Virtual IP address). OpenDaylight will also be deployed in this +scenario. ODL is also running in HA. Neutron communicates with ODL +through a VIP. + +Scenario usage overview +======================= + +To deploy with this scenario, you just need to assign the +os-odl-nofeature-ha.yaml to DHA file before deployment. + +Limitations, Issues and Workarounds +=================================== + +References +========== + +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/euphrates diff --git a/docs/release/scenarios/os-odl-sfc-ha.rst b/docs/release/scenarios/os-odl-sfc-ha.rst new file mode 100644 index 00000000..7dca2417 --- /dev/null +++ b/docs/release/scenarios/os-odl-sfc-ha.rst @@ -0,0 +1,45 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) Justin Chi (HUAWEI) and Yifei Xue (HUAWEI) + +This document introduces scenario descriptions for Euphrates 1.0 of +deployment with the OpenDaylight controller and SFC feature enabled. + +.. contents:: + :depth: 3 + :local: + +============= +os-odl-sfc-ha +============= + +This scenario is used to deploy an Ocata OpenStack deployment with +OpenDaylight Nitrogen, Ceph Jewel, and SFC feature enabled. + +Scenario components and composition +=================================== + +This scenario includes a set of common OpenStack services which are Nova, +Neutron, Glance, Cinder, Keystone, Heat, Ceilometer, Gnocchi, Aodh, +Horizon. Ceph is used as the backend of Cinder on deployed hosts. HAproxy +is used to balance all the services running on 3 control nodes behind a +VIP (Virtual IP address). OpenDaylight will also be deployed in this +scenario. ODL is also running in HA. Neutron communicates with ODL +through a VIP. Open vSwitch with NSH patched is used instead of native +Open vSwitch to support ODL SFC. Neutron communicates with ODL SFC to +create port pair, classifier, port chain and etc. + +Scenario usage overview +======================= + +To deploy with this scenario, you just need to assign the +os-odl-nofeature-ha.yaml to DHA file before deployment. + +Limitations, Issues and Workarounds +=================================== + +References +========== + +For more information on the OPNFV Euphrates release, please visit +http://www.opnfv.org/euphrates diff --git a/docs/release/userguide/FAQ/faq.rst b/docs/release/userguide/FAQ/faq.rst index 177ff0bb..326b85fe 100644 --- a/docs/release/userguide/FAQ/faq.rst +++ b/docs/release/userguide/FAQ/faq.rst @@ -52,33 +52,38 @@ an additional tagged VLAN is added if uses default network configuration. How to set OpenStack Dashboard login user and password ====================================================== -It uses admin/console as the default user/pass for OpenStack Dashboard, and you can set it in below file: -compass4nfv/deploy/conf/base.conf +It uses admin as the default user for OpenStack Dashboard. The password can be achieved as below: + +.. code-block:: bash + + sudo docker cp compass-tasks:/opt/openrc ./ + sudo cat openrc | grep OS_PASSWORD How to visit OpenStack Dashboard ================================ -You can visit OpenStack Dashboard by URL: http://{puclib_vip}/horizon +For vm deployment, because NAT bridge is used in virtual deployment, horizon can not be access directly +in external IP address. you need to cofigure the related IPtables rule at first. -The public virtual IP is configured in "compass4nfv/deploy/conf/hardware_environment/huawei-pod1/network.yml" -or "compass4nfv_FAQ/deploy/conf/vm_environment/huawei-virtual1/network.yml", defined as below: +.. code-block:: bash -.. code-block:: yaml + iptables -t nat -A PREROUTING -d $EX_IP -p tcp --dport $PORT -j DNAT --to 192.16.1.222:443 - public_vip: - ip: 192.168.50.240 +The $EX_IP here is the server's ip address that can be access from external. +You can use below command to query your external IP address. -How to access controller nodes after deployment -=============================================== +.. code-block:: bash -1. First you should login Compass VM via ssh command on Jumphost by default user/pass root/root. -The default login IP of Compass VM is configured in "compass4nfv/deploy/conf/base.conf", defined as below: + external_nic=`ip route |grep '^default'|awk '{print $5F}' + ip addr show $external_nic +The $PORT here is the one of the port [1- 65535] that does't be used in system. -.. code-block:: bash +After that, you can visit OpenStack Dashboard by URL: http://$EX_IP:$PORT - export MGMT_IP=${MGMT_IP:-192.168.200.2} +How to access controller nodes after deployment +=============================================== -2. Then you can login the controller nodes (host1-3) by default user/pass root/root via the install +You can login the controller nodes (host1-3) by default user/pass root/root via the install network IPs which are configured in "compass4nfv/deploy/conf/base.conf", defined as below: .. code-block:: bash @@ -111,8 +116,13 @@ network IPs which are configured in "compass4nfv/deploy/conf/base.conf", defined Where is OpenStack RC file ========================== -It is located /opt/admin-openrc.sh in each controller node as default. Please source it first if you -want to use OpenStack CLI. +The RC file named openrc is located in /root in utility container on each controller node as default. +Please source it first if you want to use OpenStack CLI. + +.. code-block:: bash + + lxc-attach -n $(lxc-ls | grep utility) + source /root/openrc How to recovery network connection after Jumphost reboot ======================================================== @@ -121,9 +131,44 @@ How to recovery network connection after Jumphost reboot source deploy/network.sh && save_network_info +How to use Kubernetes CLI +========================= + +Login one of the controllers +---------------------------- + +There are 3 controllers referring to host1 to host3 with IPs from 10.1.0.50 to 10.1.0.52. +The username of the nodes is root, and the password is root. + +.. code-block:: bash + + ssh root@10.1.0.50 + +Run the Kubernetes command +-------------------------- + +Kubectl controls the Kubernetes cluster manager. + +.. code-block:: bash + + kubectl help + +Follow the k8s example to create a ngnix service +------------------------------------------------ + +To create a nginx service, please read Ref[2] at the end of this page. + References ========== + +[1] +--- + For more information on the Compass4nfv FAQ, please visit `COMPASS FAQ WIKI Page <https://wiki.opnfv.org/compass4nfv_faq>`_ +[2] +--- + +`K8s Get-Started Page <http://containertutorials.com/get_started_kubernetes/k8s_example.html>`_ |
