The document discusses automated testing and proposes improvements to the current workflow. It notes cons of the current approach, including a lack of full virtualization and testing things that don't need to be tested. The future workflow envisions full virtualization support, an application container catalog, intelligent testing, and declarative environments. YAML examples are provided for OpenShift pods and OpenStack resources to demonstrate connecting Windows instances to OpenShift networks.

1. Automated Testing
06.10.2017

2. 2
Used Software
● Openshift – containers platform
● Openstack – private cloud
● Kuryr – bridge between Openshift and
Openstack

3. 3
Current Workflow

4. 4
Cons
● Lack of full virtualization (Astra Linux, FreeBSD,
SLES, Solaris, Windows).
● Testing things that don’t need be tested.

5. 5
Future Workflow

6. 6
Pros
● Full virtualization, perspective of ARM/MIPS
support
● Containers Application Catalog
● Intelligent Testing
● Declarative Environments

7. 7
Openshift YAML
- apiVersion: "v1"
kind: "Pod"
metadata:
name: "nginx"
labels:
name: "nginx"
conf: "nginx"
spec:
containers:
-
name: "nginx"
image: "nginx:latest"
securityContext:
privileged: true

8. 8
Openstack YAML
heat_template_version: 2017-02-24
resources:
windows_port:
type: OS::Neutron::Port
properties:
network: "openshift-pod"
name: "windows"
fixed_ips: [{"subnet_id": "openshift-pod"}]
windows:
type: OS::Nova::Server
properties:
name: windows
image: w7
flavor: m1.medium
networks:
- port: { get_resource: windows_port }

9. 9
QCOW Backing File

10. 10
DEMO