or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
promoter tests
tags: promoter design
https://tree.taiga.io/project/tripleo-ci-board/us/1705?milestone=264741
WIP
TO-DO
mol promoter - done
simplify credentials handling (expect keys on user home dir, not root) (MERGED)https://review.rdoproject.org/r/28655 New _ensure_credentials (MERGED)https://review.rdoproject.org/r/28656 Use _ensure_credentials in mol-promoter and staging jobs (not yet in all molecule scenarios) (MERGED)https://review.rdoproject.org/r/28683 Run molecule scenarios on promoter changes (MERGED)https://review.rdoproject.org/r/#/c/28623/ move provision/staging to py3 (MERGED)https://review.rdoproject.org/r/28597 Move mol-promoter to python3 (MERGED)https://review.rdoproject.org/r/28587 switch mol-promoter job to voting (MERGED)https://review.rdoproject.org/r/28553 Run mol-promoter as unprivileged user (MERGED)https://review.rdoproject.org/r/28552 Split promoter scenario test_sequence (MERGED)Isolate legacy code - done
(RFOLCO) rename all current jobs and playbooks to legacy-*https://review.rdoproject.org/r/28353 >> Move existing molecule playbooks to legacy dir (MERGED)https://review.rdoproject.org/r/28355 >> Rename molecule-post to mol/post.yml (MERGED)NOTE: The original idea was to rename the jobs, but since we are creating new mol jobs, we just move the legacy playbooks to a legacy/ dir and don; t touch the current molecule files (except the promoter proviosion one that was moved to molecule/promoter as it wasn't running in any job, so nothing has been affected by this move). For the other scenarios, new molecule files need to be created, so we don't touch the old legacy ones.abandoned:
https://review.rdoproject.org/r/#/c/28293/ >> rename to legacyhttps://review.rdoproject.org/r/#/c/28294/ >> update rdo-jobshttps://review.rdoproject.org/r/#/c/28295/ >> delete original namesInitial design discussions (use as reference)
LATER: DO
1 option : mv main.yaml -> main-legacy.yaml, update current job to use main-legacy.yamlLATER: Investigate
deploy credentials
making ci-config code deployment idempotent
create configuration engine that works accross all promotion environment
SOMETIME: Things to consider
NEVER: Things to avoid
Code Deduplication
Summary of changes
Create new empty molecule jobs to replace legacy ones
remove all legacy code
Job level: playbooks
molecule-delegated-pre.yml
molecule-delegated-promote-images-pre.yml
molecule-delegated.yml
staging.yml (end-to-end promotion integration test)
test-pythonpromoter_venv? virtualenvKeep in the job's pre playbook ONLY what is common to all molecule jobs.
molecule-delegated.ymldelegated scenarios are converted to non-delegatedall molecule scenarios are executed by toxno need to specify command in run playbookmolecule-delegated-promote-images-pre.ymlDUP: content absorved by other partsmolecule-level: scenarios
https://github.com/rdo-infra/ci-config/tree/master/ci-scripts/infra-setup/roles/promoter/molecule
Add this private role to setup docker-ce for all container scenarios
container-push
Split into separate scenarios:
scenario 1: disable target registry push
scenario 2: secure registry, manifest disabled
scenario 3: insecure registry, multiarch manifests
scenario 4: insecure registry, multiarch, ppc disabled
promote-images
tripleo-common-integration
defaultpromoter_provisiondefaultpromoterconverge.ymlsetup stagingcan be removed ???(not implemented) check if setup is ok