summaryrefslogtreecommitdiffstats
path: root/docs/infrastructure/overview.rst
blob: ed4dc11d97a927fa206d45b32251111c3b6192d0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
.. _overview:

.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. SPDX-License-Identifier: CC-BY-4.0
.. (c) Open Platform for NFV Project, Inc. and its contributors

=======================
Infrastructure Overview
=======================

Anuket develops, operates, and maintains infrastructure which is used by the Anuket
Community for development, integration, and testing purposes.

Anuket is working towards a model whereby we have a seamless pipeline
for handing resource requests from the Anuket community for both development and
Continuous Integration perspectives. Automation of requests and integration to
existing automation tools is a primary driver in reaching this model. In Anuket,
we imagine a model where the Infrastructure Requirements that are
specified by a Feature, Installer or otherrelevant projects within Anuket are
requested, provisioned, used, reported on and subsequently torn down with no (or
minimal) user intervention at the physical/infrastructure level.

Objectives of Anuket are

* Deliver efficiently dimensions resources to Anuket community needs on request
  in a timely manner that ensure maximum usage (capacity) and maximum density
  (distribution of workloads)
* Satisfy the needs of the twice-yearly release projects, this includes being
  able to handle load (amount of projects and requests) as well as need
  (topology and different layouts)
* Support Anuket community users.  As the INFRA group, we are integral to all
  aspects of the Anuket Community (since it starts with the Hardware) - this
  can mean troubleshooting any element within the stack
* Provide a method to expand and adapt as Anuket community needs grow and
  provide this to Hosting Providers (lab providers) for input in growth
  forecast so they can better judge how best to contribute with their resources.
* Work with reporting and other groups to ensure we have adequate feedback to
  the end-users of the labs on how their systems, code, feature performs.

The details of what is provided as part of the infrastructure can be seen in
following chapters.


Software Infrastructure
-----------------------

- :ref:`releng:software-infrastructure`