summaryrefslogtreecommitdiffstats
path: root/docs
AgeCommit message (Collapse)AuthorFilesLines
2018-10-23Gambia Branch Configuration for Docs and GitreviewTrevor Bramwell1-1/+3
Update the docs to use 'Gambia' as the version and release, and sets the default gitreview branch to 'stable/gambia' so it doesn't need to be explicly passed every time. Change-Id: Id5cbfb581cb232af5541f58df8c95e4b0918713e Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-10-03Local Documentation BuildsAric Gardner4-0/+30
This adds configuration for performing local documentation builds with the following simple command: tox -e docs This patch is part of our documentation effor to Move away from submodules https://docs.opnfv.org/en/latest/how-to-use-docs/local-build-transition.html added index.rst so that docs build succsesfully Change-Id: I2d28f03ad4d5c9c14de095dc544257af9d1e51d9 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org> (cherry picked from commit 9666d8bb3df726d88d08d5811d2a99e713908396)
2018-08-23Adds deployment via snapshotTim Rozet1-6/+73
New arguments are added to allow snapshot deployment: --snapshot, --snap-cache The previous tripleo-quickstart code has been removed/replaced with the snapshot option. Snapshot deployments are supported on CentOS and Fedora, and snapshot artifacts use a similar caching system as the standard deployment. Snapshots are produced daily by Apex, and include latest as well as n-1 OpenStack versions. The os-odl-nofeature scenario is used for the snapshots. Additionally multiple topology verions of Snapshots are available. The Snapshot pulled at deploy time depends on the deploy-settings and number of virtual-computes used at deploy time. Since there is only one network used with snapshot deployments (admin), there is no reason to pass in network settings for snapshot deployments. That argument is now optional. Previously we required even in Standard virtual deployments that the network settings be provided. However that is also unnecessary, as we can default to the virtual network settings. Includes minor fix to the tox.ini to allow specifying test cases to run (useful for developers writing tests). Default behavior of tox is unchanged. JIRA: APEX-548 Change-Id: I1e08c4e54eac5aae99921f61ab7f69693ed12b47 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-08-10Allow all in one deploymentsTim Rozet3-10/+17
This patch adds the ability to deploy all in one single nodes (Control + Compute). To enable this functionality do the following for each deployment type: - Baremetal: do not tag any nodes as compute in the inventory file - Virtual: use argument '--virtual-computes 0' JIRA: APEX-548 Change-Id: I22525c9eb21d331129c819449316c26a6fcf522d Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-07-06Add support for kubernetes deploymentZenghui Shi2-0/+59
This patch adds capability to deploy kubernetes cluster instead of openstack. Kubernetes will be deployed using kubespray and is run after TripleO bookstraps overcloud nodes. JIRA: APEX-574 Change-Id: If9c171620c933a052b719e7112a50e22bbab667f Signed-off-by: Feng Pan <fpan@redhat.com> Signed-off-by: Zenghui Shi <zshi@redhat.com>
2018-05-21Migrates master to use direct upstreamTim Rozet1-6/+2
We now move master to deploy from upstream. That means we do not need to build undercloud/overcloud images anymore. Changes-Include: - Remove bash build scripts as we do not need to build anything other than the python package anymore - Remove building images or iso from build.py - Remove building of images and iso from Makefile - Rename/refactor deploy settings files for nosdn and odl. The new convention is that the typical scenario names we use will deploy master. We also support n-1 OS, so in that case we use the branch name for the "feature" in the scenario name: os-odl-queens-noha. - Tacker/Congress are disabled in settings files until we fix that with upstream. Containers are now enabled by default. - Disable TLS for undercloud (was changed upstream to default enabled) - Fix environments docker directory for master THT (was changed upstream) - Includes fix for LP#1768901 - Includes workaround for LP#1770692 - Moves to docker.io for container images as it is more stable and should contain the same images - Removes the term 'common' from apex packaging for referencing the Python Apex package Change-Id: If6b433860b3ff882686c78d0f24a2f0c52b9b57a Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-25Updates documentation for Fraser releaseTim Rozet22-476/+189
Change-Id: I19bfaa5b2778baf458df60a4a53d135e57859e04 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-03-16Enables containerized overcloud deploymentsTim Rozet1-0/+126
Changes Include: - For upstream deployments, Docker local registry will be updated with latest current RDO containers, regular deployments will use latest stable - Upstream container images will then be patched/modified and then re-uploaded into local docker registry with 'apex' tag - Deployment command modified to deploy with containers - Adds a --no-fetch deployment argument to disable pulling latest from upstream, and instead using what already exists in cache - Moves Undercloud NAT setup to just after undercloud is installed. This provides internet during overcloud install which is now required for upstream container deployments. - Creates loop device for Ceph deployment when no device is provided in deploy settings (for container deployment only) - Updates NIC J2 template to use the new format in OOO since the os-apply-config method is now deprecated in > Queens JIRA: APEX-566 JIRA: APEX-549 Change-Id: I0652c194c059b915a942ac7401936e8f5c69d1fa Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-03-15Adding SRIOV scenarioRicardo Noriega1-2/+6
This scenario should enable SRIOV interfaces to be used by Neutron. Only will be supported in baremetal deployments with SRIOV capable NICs. The name of the interface must be known in advance and the physnet of the SRIOV network is set as nfv_sriov. Change-Id: Ie4295413e0be2197bd9ada4f887f6b47cd486765 Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2018-03-08Merge "Fix URL anchor in apex document."Feng Pan2-4/+4
2018-02-07Adding L2GW ScenarioRicardo Noriega1-0/+4
This scenario allows you to install L2GW Neutron driver and point to OpenDaylight as service provider. apex-tripleo-heat-templates: I37039207bc7cf9965d26e6dfa034e84bf9b7224d Change-Id: I0dfd37bcc5060f0ad8caa95e1f87a7411bd6e723 Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2018-02-01Fix URL anchor in apex document.Tomofumi Hayashi2-4/+4
The latest OPNFV document template makes html file separately, hence index.html#<something> is invalid. This fix changes anchor URL to support separate file. Change-Id: Ic48c062e118d2faede53e8c9eaecbb99e58fddfb Signed-off-by: Tomofumi Hayashi <tohayash@redhat.com>
2017-12-12docs: fix default password and yum.repo.dRyota MIBU2-3/+3
- password for root in debug mode is defined in DEBUG_OVERCLOUD_PW document has to be updated - '/etc/yum.repo.d' is the right yum repo directory in Cent OS 7 Change-Id: Ia97e3878bd30d562bd3c3b7776e80440b20a4111 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-11-16Migrates Apex to PikeTim Rozet1-1/+1
JIRA: APEX-544 Change-Id: Ibee2068e782da75268ed76beb36ccb5dcd1847d6 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-10-19Fix releasenotes label and include paths for docsTrevor Bramwell2-3/+3
Change-Id: I50a8f35165954b9b4bdf62864055ad475843c179 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-10-18More updates to docs for EuphratesTim Rozet11-65/+2
Changes Include: - SFC HA will not be supported in 5.0 - Table of Contents removed from release-notes/scenarios - Version table removed - Release date updated Change-Id: Ifbd766b578717320ba1924678839c7d48bbce041 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-10-17Updates docs and scenarios for EuphratesTim Rozet15-128/+337
Change-Id: I2da89d7a6ab4b0549edded908acc760b949231e1 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-10-09Fix licenses to be Apache 2.0Tim Rozet1-1/+1
Change-Id: I53f3596685b83e995498b5fdb804561fed6dc38b Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-06Removes build.shTim Rozet1-1/+1
We now have build.py which handles all the building and build.sh was just a wrapper to include ansible playbook. Now that we have built in apex libs to run ansible there is no reason to keep build.sh anymore. Also simplifies the logic to determine apex root by using the git properties. Change-Id: I00d2e5c7c198e549d21936bb1e9b562ba93d3010 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-29Updates preliminary docs for EuphratesTim Rozet11-61/+63
Change-Id: I4e3e78e60756824c1294ab067a325311bc2ac8f2 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-24Updates RPM specs and buildingTim Rozet1-12/+12
Changes Include: - Disables ONOS from rpm and image building - Fixes opnfv-apex package dependency for python34-opnfv-apex - Updates requirements for python34-opnfv-apex - Updates docs - Removes temporary build qcow2 for odl which was being bundled into our dev tars unnecessarily Change-Id: Ief668067181fc35a54553ae118b7950bddce1940 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-17Small correction in docs.Taseer Ahmed1-1/+1
Change-Id: Iec9a401759de5953d4a8ca05c4f1c32b163343ba Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
2017-08-14Fixes OpenDaylight versionTim Rozet1-1/+1
The default version is now Carbon with the option of using nitrogen (master) for puppet-odl and opendaylight. JIRA: APEX-500 Change-Id: I44d02ec0db5fb8e6342e5ab6802a5a3f302b8511 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-15Removing sdn_l3 and _l2 scenario featuresDan Radez1-13/+7
JIRA: APEX-429 Change-Id: Ifb28bb27f8e58ac5b180454719dfb329c3edf000 Signed-off-by: Dan Radez <dradez@redhat.com>
2017-04-04RPM version update / ovs_dpdk renameDan Radez1-4/+4
- updating RPM version numbers for Euphrates - renaming ovs scenario to ovs_dpdk JIRA: APEX-434 Change-Id: I75e1d96bd613ea04e2ffd12bd41b3a536ff75d7f Signed-off-by: Dan Radez <dradez@redhat.com>
2017-04-03Merge "Euphrates Docs update w odl scenario name cleanups"Dan Radez5-8/+8
2017-03-30More doc updates for DanubeTim Rozet4-12/+38
Change-Id: I125548acde034d8c4c85cce93fb001ba06c8ab33 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-03-30Merge "Adds apex owned scenario release notes"Dan Radez14-0/+472
2017-03-30Adds apex owned scenario release notesTim Rozet14-0/+472
Change-Id: Ia7b50b99b82a01d347ba673e354d80cbb65e608f Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-03-30Updates release notes for DanubeTim Rozet1-198/+123
Change-Id: Id3a90d1ba53502bc28db3e04d2795e9806f42eed Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-03-30Euphrates Docs update w odl scenario name cleanupsDan Radez5-8/+8
- updating docs to reference Euphrates - removing the odl_l2-nofeature scenario, it's obsolete - renameing odl_l3 to odl, it's default for odl now - adding symlinks to files to _l3 files so CI doesn't break will remote those once CI is updated to use new names Change-Id: I9f2646fc5dac443042c5f4be8cca7d2df5dca663 Signed-off-by: Dan Radez <dradez@redhat.com>
2017-03-30Updating docs for DanubeDan Radez8-49/+68
Change-Id: I7eb2d7bb62d61ca1ab7177332bb27329da85ad48 Signed-off-by: Dan Radez <dradez@redhat.com>
2017-03-07Adding LabelsShubhamRathi2-0/+4
Labels serve as anchors/ refs when referenced from other documents This patch adds labels to docs/*/*/index.rst Change-Id: Ia891cbe2866acceb626730b778585b5620cb2ff0 Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
2017-02-18Add support for odl-fdio scenarioFeng Pan1-0/+3
Changes: - Kernel parameters are now set through first-boot.yaml during deployment. No custom images will be built. Note that all nodes will be configured the same way, we only use compute's kernel parameter settings currently (from deploy settings file) - Add support for VPP interface type in network settings file, it is now possible to specify vpp_interface type and uio_driver for tenant nic in network settings file. A new example config, network_settings_vpp.yaml is added. - Add support for odl_l2-fdio scenario. Limitations: - Physical NIC names must be specified in network settings file, numbered nic names such as nic1 are not supported for fdio scenarios. - The same kernel parameters will be configured for all nodes. The paramters will be taken from compute kernel parameter section in deploy settings file. opnfv-tht-pr: 104 opnfv-puppet-tripleo-pr: 12 os-net-config-pr: 3 Change-Id: Ie9d6151e6e58d11da3c66fbcabe4a0886c3fa152 Signed-off-by: Feng Pan <fpan@redhat.com>
2017-02-17Doc updates for MS6Sofia Wallin13-0/+0
Updated the docs structure according to directives and MS6 Change-Id: I36e92cbc58328528ebb91ff4f54ee701f5477443 Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
2017-01-26[BGPVPN] Remove l2 in Name; Enable ODL BoronNikolas Hermanns3-3/+3
Since Boron ODL servers always the l3 usecase so the l2 differentiation does not make sense anymore. Depends: https://gerrit.opnfv.org/gerrit/27605 Change-Id: I8bb55387001dfc81845134639ab4e913072f9a27 Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
2017-01-25Merge "Changes to Installation Procedure docs"Tim Rozet1-1/+1
2016-12-20Adds declaring disk device to use on overcloud nodesTim Rozet1-0/+9
Now in inventory file a user can declare 'disk_device' which will allow the user to specify which disk on their overcloud server to use for installation. The variable can be a comma delimited list, which will search in order post-introspection for the first device on the node that exists. The default disk used will be sda for deployments. Currently defining a per node disk is not supported by OSCLI, so although defined that way in Apex inventory, only the last definition will be used for all nodes. Other changes include: - Various fixes in inventory parsing - Makes bash writing a common function - Introspection now enabled for baremetal deployments JIRA: APEX-296 Change-Id: I330d91eb17408ccfceb7a99c25edbae5ce6d848d Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-12-02Merge "Fixes using single network (previously called flat) for deploy"Feng Pan1-1/+1
2016-12-02spelling mistakeDan Radez1-1/+1
Change-Id: I4b8e377003f81f615f044cac4b6de4aeadff766e Signed-off-by: Dan Radez <dradez@redhat.com>
2016-12-02Fixes using single network (previously called flat) for deployTim Rozet1-1/+1
Also contains various network parsing fixes. JIRA: APEX-361 Change-Id: I5e40ed67267d5ded85adc2982a8726ebbceaeae5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-12-01Adding a release RPMDan Radez2-12/+27
JIRA: APEX-351 Change-Id: I9b8b74073287005221a7a3f6dfe2d52a7d1cf667 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-11-30Add release notes for os-nosdn-fdio-nohaFrank Brockners1-0/+27
Change-Id: I8db7f968be881bc129f15b9812c8e0aab09ae56b Signed-off-by: Frank Brockners <fbrockne@cisco.com>
2016-11-22Changes to Installation Procedure docsSai Sindhur Malleni1-1/+1
When doing a virtual deploy the -i option for inventory file shouldn't be passed. Changing docs to reflect this. Change-Id: Ic51b8020fd26b19d6f86ffa66fb700b071b1a7a3 Signed-off-by: Sai Sindhur Malleni <smalleni@redhat.com>
2016-11-17Allow passing a device name to cephDan Radez1-0/+7
JIRA: APEX-347 Change-Id: Ibc6d141e20faf613e0f6314286b55aff01ce862e Signed-off-by: Dan Radez <dradez@redhat.com>
2016-10-31Fix links in Apex install manualTomofumi Hayashi2-4/+4
JIRA: APEX-338 Due to the change of DOCS-156, OPNFV document html is now 'single HTML' file, instead of multiple HTMLs. This fix changes hyperlinks of document. Change-Id: Ifbb12cdeb8edad1b7444f8c7d25ced0eef94eb14 Signed-off-by: Tomofumi Hayashi <tohayash@redhat.com>
2016-10-20Adding inventory.yaml values to docsDan Radez1-5/+7
JIRA: APEX-297 Change-Id: I897c1921b51233864e0c26e7b71783976c855a43 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-10-12Consolidate ODL SFC RPM into ODL RPMDan Radez2-5/+3
OVS NSH can be installed at deploy time. Change-Id: Ie875ada99053df95c6534e269f4dd627396489bc JIRA: APEX-324 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-10-03Merge "Adding developer/troubleshooting section to Installation Instructions"Tim Rozet2-0/+145
2016-09-30Adding developer/troubleshooting section to Installation InstructionsRicardo Noriega2-0/+145
Updating with suggestions and comments Change-Id: Ida7357eba0b2ed5d59f89b91603c8149a6fbcf7a Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>