opendev/system-config
Code Issues Proposed changes

Updates to running-your-own CI docs: Initial setup section

Browse Source 
This patch updates the Initial setup section from running-your-own
document. Other sections will be updated in separate patches to
make the reviwes short.

Change-Id: I6915b0f39e8eb17c39ab72df7a93d300625a208d
This commit is contained in:
Rafael Folco 2015-02-13 15:30:35 -02:00
parent 1e85b84a43
commit f3ebde7d5e
1 changed files with 19 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/source/running-your-own.rst
View File

@ -38,12 +38,27 @@ Requirements
Initial setup Initial setup
============= =============
1. Clone the CI config repository and adjust it as necessary. #. Manually boot a machine or VM with 2G+ of ram to be the puppetmaster.
Average memory consumption is between 1GB-1.5GB with random peaks around
2GB for puppetdb and ruby processes.
1. Manually boot a machine with ~2G of ram to be the puppetmaster. #. Clone the CI config repository and adjust it as necessary. Avoiding forks
and overriding the default config from Infra is a good practice to
customize your CI system. The CI config is split in 2 projects:
a) `system-config <http://git.openstack.org/cgit/openstack-infra/system-config/>`_
Contains information on how systems are operated.
b) `project-config <http://git.openstack.org/cgit/openstack-infra/project-config/>`_
Contains configuration data used by OpenStack projects and services.
For more details on the config repo split, read the following spec:
`http://specs.openstack.org/openstack-infra/infra-specs/specs/config-repo-split.html`
1. Follow http://ci.openstack.org/puppet.html#id2 but use your repository #. Follow http://ci.openstack.org/puppet.html#id2 and use your repository
rather than the OpenStack CI repository. in addition to the OpenStack CI repository. This is appropriate to stay in
sync with OpenStack Infra team rolling out new functionality and at the same
time applying the necessary customizations through the config overrides.
This step consists in configuring puppetmaster to load CI config into
modulepath for both Infra projects and your custom CI repository.
The necessary changes are explained in the sections below.
Changes required Changes required
================ ================