This is the third weekly update from the KubeVirt team.

We are currently driven by

• Being easier to be used on Kubernetes and OpenShift

• Enabling people to contribute

• Node Isolator use-case (more informations soon)

This week we achieved to:

• Renamed VM kind to VirtualMachine (@cynepco3hahue) (https://github.com/kubevirt/kubevirt/pull/452)

• Proposal for VirtualMachineReplicaSet to scale VMs (@rmohr) (https://github.com/kubevirt/kubevirt/pull/453)

• Ephemeral Registry Disk Rewrite (@vossel) (https://github.com/kubevirt/kubevirt/pull/460)

• Fix some race in our CI (@rmohr) (https://github.com/kubevirt/kubevirt/pull/459)

In addition to this, we are also working on:

• Review of the draft code to get layer 3 network connectivity for VMs (@vladikr) (https://github.com/kubevirt/kubevirt/pull/450)

• Review of the draft code for the api server aggregation (@stu-gott) (https://github.com/kubevirt/kubevirt/pull/355)

• Review of the proposal integrate with host networking (@rmohr) (https://github.com/kubevirt/kubevirt/pull/367)

• Converging multiple ansible playbooks for deployment on OpenShift (@petrkotas, @cynepco3hahue, @lukas-bednar) (https://github.com/kubevirt-incubator/kubevirt-ansible)

• Continued discussion of VM persistence and ABI stability (https://groups.google.com/d/topic/kubevirt-dev/G0FpxJYFhf4/discussion)

Take a look at the pulse, to get an overview over all changes of this week: https://github.com/kubevirt/kubevirt/pulse

Finally you can view our open issues at https://github.com/kubevirt/kubevirt/issues

And keep track of events at our calendar 18pc0jur01k8f2cccvn5j04j1g@group.calendar.google.com

If you need some help or want to chat you can find us on <irc://irc.freenode.net/#kubevirt>