Revision as of 17:01, 18 July 2021

TO BE DEPRECATED: When you see this, please consider moving the logic model below from Template:Logic Model to Template:LogicModel

1. Context	After defining the scope, the project should be specified so that it is precise enough for implementation.
2. Goal	To specify the system using a formal/semi-formal specification and Logic model.
3. Success Criteria	The specification completely covers the system The specification can be compiled correctly The goal is reached before end time
4. Outputs	5. Process	6. Inputs
Project specification		The knowledge from project scoping
7. Boundary Conditions

All kinds of workflows

The workflows are managed in Manual namespaces.

By Jenkins Remote Access API :

Download the Docker Image and build the PKC instance by up.sh. Then a docker container instance is built.
For any updates, save the new image file in docker registry with a named TAG.
Push the registered local image on the docker hub.
The image should be tested and then deployed for use.

For each workflow, how do we track the event? How do we describe the management for each resources in a high-level?

@@ Line 30: / Line 30: @@
 === Docker workflow ===
-[https://hub.docker.com/r/xlp0 Docker Image Repository]
+Resource :[https://hub.docker.com/r/xlp0 Docker Image Repository]
 * Download the [https://hub.docker.com/r/xlp0/mariadb Docker Image] and build the PKC instance by up.sh. Then a docker container instance is built.
 * For any updates, save the new image file in [https://docs.docker.com/registry/ docker registry] with a named TAG.
 * Push the registered local image on the docker hub.
 * The image should be tested and then deployed for use.
 === Backup and Restore Workflow ===