| |
@@ -46,7 +46,7 @@
|
| |
* <<Atomic IoT (likely useful in numerous other Atomic ideas) host upgrade daemon>>
|
| |
* <<Fedora Dockerfile linter leveraging Container Best Practices>>
|
| |
* <<Advanced test cases for images running in OpenShift using conu>>
|
| |
- * <<New container backends for conu>>
|
| |
+ * <<Complete support for OpenShift and Kubernetes as a backend in conu>>
|
| |
* <<Open Ideas From Previous Years>>
|
| |
|
| |
=== Improve GPIO support in Fedora in general and particularly on the Raspberry Pi
|
| |
@@ -300,16 +300,18 @@
|
| |
- Contacts (IRC & email): ttomecek (ttomecek @redhat.com), dhodovsk (dhodovsk @redhat.com)
|
| |
|
| |
==== Description
|
| |
- https://github.com/fedora-modularity/conu[Conu] is a library which provides Python API to interact with a selected container runtime. It simplifies writing of tests for container images. However, the project currently lacks support for OpenShift.
|
| |
+ https://github.com/fedora-modularity/conu[Conu] is a library which provides Python API to interact with a selected container runtime. It simplifies writing of tests for container images. However, the project currently lacks support for OpenShift and Kubernetes.
|
| |
|
| |
==== Deliverables
|
| |
|
| |
- Your primary goal will be to deliver at least 10 new functions that will enable the users to write tests for OpenShift scenarios.
|
| |
- Your secondary goal will be to write test for at least 5 images (eg mariadb, mysql, postgresql, golang, rust) using conu’s full capabilities.
|
| |
|
| |
+
|
| |
'''
|
| |
|
| |
- === New container backends for conu
|
| |
+ === Complete support for OpenShift and Kubernetes as a backend in conu
|
| |
+
|
| |
|
| |
- Skill level: Intermediate - Expert
|
| |
- Skills required: python, containers
|
| |
@@ -318,11 +320,13 @@
|
| |
|
| |
==== Description
|
| |
|
| |
- https://github.com/fedora-modularity/conu/[conu] defines a generic API to interact with containers and container engines. To make the project more usable, we would like add implementation of another container runtimes, such as Container Runtime Interface (see the http://blog.kubernetes.io/2016/12/container-runtime-interface-cri-in-Kubernetes.html[Kubernetes blog post] and the https://github.com/vbatts/python-kubernetes-cri[Github repo]) of Kubernetes project. CRI is a generic interface defined by Kubernetes project which container engines need to implement in order to communicate with Kubernetes. Adding implementation for this interface into conu project will make it easy for conu users to interact with variety of container runtimes and perform operations which would be executed inside Kubernetes.
|
| |
+ https://github.com/fedora-modularity/conu/[conu] defines a generic API to interact with containers and container engines. To make the project more usable, we would like to add implementation of well known container orchestration systems — Kubernetes and OpenShift.
|
| |
|
| |
==== Deliverables
|
| |
|
| |
- Write a series of pull requests to implement selected container runtime into conu project.The newly added functionality needs to have integration tests which can run inside CI environment.
|
| |
+ - Write a series of pull requests to add support for Kubernetes and OpenShift in conu project.
|
| |
+ - The newly added functionality needs to have integration tests which can run inside CI environment and are passing.
|
| |
+ - And finally, the feature should be demonstrated it works well by at least 3 real examples.
|
| |
|
| |
'''
|
| |
|
| |
ttomecek
commented 6 years ago
Signed-off-by: Tomas Tomecek ttomecek@redhat.com