Age | Commit message (Collapse) | Author | Files | Lines |
|
XCI baremetal is a big feature which will require a lot of patches and lines of
code. Before starting the contributions, a spec will allow us to discuss and
agree on the general aspects of its architecture and implementation. That will
hopefully facilitate and increase the velocity of its reviews.
This patch provides a spec with the general design ideas for the infra_manager
tool which will allow XCI to be deployed on baremetal. Its architecture is
based on the contributions from David. All the content of the spec is questionable
even the structure of the spec :)
Change-Id: Ie4b096482c8150a04d3d3b2df0e2ca8a280aad10
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Please note that the document you are about to review contains information
about the existing CI Loops and promotion criterias applied by XCI in order
to record the current state of affairs.
Once this change gets merged, a new change will be proposed and that change
will be the one where the existing criterias will be updated and the new ones
will be introduced.
This document is created to start the conversation around determining
the promotion criterias (test scopes) for each of the current and upcoming
CI Loops XCI uses.
The expectation with this document is to update it collaboratively with
scenario owners, projects, XCI Team, Test Projects, and Release Management
to find the necessary level of testing as much as possible.
The information this document contains and the criterias set in it will be
superseded by the CD-Based Release model once it becomes available.
Change-Id: I7b4afd87a4f7694eb78c996e7870b8dc1e833fbf
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
1. Introduce the installer used to deploy kubernetes
2. Introduce XCI how to deploy the kubernetes
Change-Id: I052b4547d763d19b8d6136a48d4804443921b021
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
The OPNFV_RELENG_DEV_PATH variable was used to point to a releng-xci
development repository. However, people normally set the current
directory as the development one and they almost always want to
test the current code in XCI. Using an secondary releng-xci tree
as development repo is a very obscure case and it normally complicates
things. As such, let drop this option and always use the current
repository for development purposes.
Change-Id: If111bf29a32a5f6ea28694f191645af0c6a87abc
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Change-Id: I9c552930b46dad2bf9720595d44208b393dba643
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: If6a0c9d498324a5edec38a442f5c3d23f9796130
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I23405aec19a7e9bfce1c58d770b80b1c9c550d00
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I35aefb46661a89615b207398341705dd483b6797
Signed-off-by: rpaik <rpaik@linuxfoundation.org>
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I550860f574765a3035e9025e254f6d7ba110e0e4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I95fd4efe4d1a47ce682489ffd7c2ce588a1764e5
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change adds the user guide and sandbox information.
The documentation is created by using the information we
have on Wiki and README.rst.
Wiki pages and README.rst will be removed once all the
documentation is moved to docs.opnfv.org.
Parts of the README.rst such as more advanced ways to use
the sandbox will be placed in developer guide and it is
accessible by a link placed in user guide.
Change-Id: I7214a53d7ab39125d2164c5b3468b1ba18933b31
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change puts the initial structure for the documentation.
Change-Id: I4ff075874815bfcd1834049ae205a02b72bae75f
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|