This presentation describes the way to create commits of VM, for versioning and rollback of complete applications environment.

1. Vm_commit
or How to Easily Handle
An Infinite Number of Versions
of Running QEMU/KVM
Virtual Machines
Dominique Rodrigues
Cloud Expo 2015 – Santa Clara

2. Nanocloud Software?

4. Turn any software into a
cloud solution.
Any legacy application. Any device. Any cloud.

5. HOW WE DO IT

6. • Cloud
• Virtualization
• Scalability
• API
• Multi-tenant
• Collaborative
• Statistics usage
• HTML5 display
Main technologies used
Open source version: https://github.com/Nanocloud

7. About Virtualization

8. VIRTUALIZATION USE
Server consolidation
Foundation for elasticity & instant deployment
in cloud computing
Massively used in enterprises

9. About Containerization

10. DOCKER

11. DOCKER
New orchestration of containers
° clone, pull/push, run, commit °
Hub to share application based containers
VCS oriented (like git)
° edit, share, deploy applications °

12. Versioning?

13. GIT

14. GIT
THE VCS software!
° git clone / commit / push / pull / merge / rebase °

15. Could VMs be versioned
à la git
or like a Docker container?

16. INTRODUCING NC_POWER
Internal Nanocloud tools suite
for QEMU & KVM
(Linux based)
CLI
Written in C++

17. NC_POWER GOALS
Help our developers to fast run any VM
Internal needs of Nanocloud
KISS based

18. NC_POWER FEATURES
VM management (create, run, stop)
Vm_commit

19. VM COMMIT - GOALS
Keep a version for any change in a VM
Rollback to any version
Make only incremental changes
Replay any version
All on the fly

20. Using NC_Power
(some examples)

21. CREATING A VM
JSON definition file (vm.json)
{
"VMs": [
{
"client_id": "docky",
"instance": "nano",
"persistent": "no",
"rental_mod": "free_use",
"os": "linux",
"osversion": "coreos",
"osrelease": "717.3.0",
"local_ip": "",
"public_ip": ""
}
]
}
nc_create_vm --file vm.json

22. ENTERING A VM

23. ENTERING A VM

24. ENTERING A VM

25. ENTERING A VM

26. ENTERING A VM

27. ENTERING A VM

28. RUNNING IN A VM

29. RUNNING IN A VM

30. RUNNING IN A VM

31. RUNNING IN A VM

32. RUNNING IN A VM

33. RUNNING IN A VM

34. RUNNING IN A VM

35. RUNNING IN A VM

36. RUNNING IN A VM

37. RUNNING IN A VM

38. RUNNING IN A VM

39. RUNNING IN A VM

40. RUNNING IN A VM

41. RUNNING IN A VM

42. RUNNING IN A VM

43. RUNNING IN A VM

44. RUNNING IN A VM

45. RUNNING IN A VM

46. RUNNING IN A VM

47. RUNNING IN A VM

48. RUNNING IN A VM

49. RUNNING IN A VM

50. RUNNING IN A VM

51. RUNNING IN A VM

52. RUNNING IN A VM

53. RUNNING IN A VM

54. RUNNING IN A VM

55. RUNNING IN A VM

56. VM_COMMIT

57. VM COMMIT - HELP

58. VM_COMMIT
building blocks

59. BUILDING BLOCK #1: QEMU-IMG
qemu-img create -f qcow2
-b vm_basis.qcow2
vm_delta_commit.qcow2

64. BUILDING BLOCK #2: QEMU CONSOLE
echo
'snapshot_blkdev -n vm_delta_commit.qcow2'
| socat stdio unix:vm.socket

68. VM COMMIT

69. VM COMMIT

70. VM COMMIT

71. VM COMMIT

72. VM COMMIT

73. VM COMMIT

74. VM COMMIT

75. VM COMMIT

76. VM COMMIT

77. VM COMMIT -> VM ENV

78. VM COMMIT -> VM ENV

79. VM COMMIT -> VM ENV

80. VM COMMIT -> VM ENV

81. VM COMMIT -> VM ENV

82. VM COMMIT -> VM ENV

83. VM COMMIT -> VM ENV

84. VM COMMIT -> VM ENV

85. VM COMMIT -> VM ENV

86. VM COMMIT -> VM ENV

87. VM COMMIT -> VM ENV

88. VM COMMIT -> VM ENV

89. VM COMMIT -> VM ENV

90. VM COMMIT -> VM ENV

100. VM COMMIT - ROLLBACK

101. VM COMMIT - ROLLBACK

102. VM COMMIT - ROLLBACK

103. VM COMMIT - ROLLBACK

104. VM COMMIT - ROLLBACK

105. VM COMMIT - ROLLBACK

106. VM COMMIT - ROLLBACK

107. VM COMMIT - ROLLBACK

108. VM COMMIT - ROLLBACK

109. VM COMMIT - ROLLBACK

110. VM COMMIT - ROLLBACK

111. VM COMMIT - ROLLBACK

112. VM COMMIT - ROLLBACK

113. VM COMMIT - REBASE

114. USE CASES
Incremental backups (on the fly, as in Docker)
Application development (versioning, as in Git)
OS upgrades (rollback in case of trouble)

115. POSSIBILITIES
Backup strategy
Use VMs the same way as containers

116. Thanks for your attention!
dominique.rodrigues@nanocloud.com
Please commit your (last) questions 