s7.
brief example:
"com.cloud.agent.api.StartCommand": {
...
"nics": [{
"deviceId" : 2
"ip" : "172.24.2.107"
"mac" : "06:b7:78:00:00:53"
...
"com.cloud.agent.api.routing.IpAssocCommand": {
...
"ipAddresses" : [{
"publicIp" : "172.24.2.107"
"vifMacAddress" : "06:24:7c:00:00:53"
"newNic" : false
...
best regards,
Ran Huang
Greetings All,
For qcow2 format images, when creating a new VM in KVM, the template
image is copied from secondary storage to primary storage, and the root
volume image is created with the template image as a backing file.
But when I break this backing chain on primary(expunge VM or revert to
ology)
you can have i.e. 100 VMs all linking (having it's backing file...) to a
template qcow2 file.
So in other words, it's not supposed to be removed.
Does this make sense?
Cheers
On Fri, 16 Nov 2018 at 22:38, ran huang wrote:
Greetings All,
For qcow2 format images, when
ebo
Cloud Architect
ShapeBlue
On 16/11/2018, 22:51, "ran huang" wrote:
Hi Andrija,
Thanks for the clarification and quick response
regards,
Ran
On 11/16/2018 02:15 PM, Andrija Panic wrote:
> Hi Ran,
>
> templates stays on
n cleaned-up/removed from Primary Storage
if no other VMs/volume use it as it's backing (parent) image.
Makes sense ?
Cheers
On Thu, 22 Nov 2018 at 21:18, ran huang wrote:
Thanks Andrija, just tested myself with expunge and works as expected.
However, for KVM, when I revert a qcow dis
fter volume restored from snapshot - on next storage
scavenger run it will be marked properly for GC and removed...
(volumes of VM deployed from ISO file, also have NULL for "template_id"
filed"
On Thu, 22 Nov 2018 at 22:29, ran huang wrote:
Hi Andrija,
That is precisely th
