Wheezy by default generates ecdsa keys too, so ssh_gen_host_keys needs
to recreate them on first startup.
The following patch will correct this problem:
diff -rupN ssh_old/ssh_gen_host_keys ssh_new/ssh_gen_host_keys
--- ssh_old/ssh_gen_host_keys 2012-10-04 13:50:31.0 -0400
+++ ssh_new/ss
Not sure about it...
I try to find an vsphere iso to see how it's work, I'm a bit overloaded too ;)
I'll keep you in touch !
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 4 Octobre 2012 16:41:54
Objet: RE: [pve-devel]
> I don't know how it's works on the storage side (maybe they do implicit clone
> or snapshots, when converting from/to template)
They simply make full copies?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/l
> they have 2 ways to create template:
>
> 1) transform vm as template. (just rename the vm as template, so original vm
> is no more displayed as vm)
>
> 2) copy the vm to template. (original vm is available)
>
> seem more easy, they are no vm with clones, so we can delete them without
> any pro
more vmware infos:
http://www.vmwarehub.com/Working-with-templates-clones.html
they allow to transform a vm to a template,
but also a template to vm to make the modification
and again reconvert the template to vm
"
How to Edit a Template:
You can edit templates. You might want to edit templates t
I'm reading the vmware vsphere cloning documentation,
they have 2 ways to create template:
1) transform vm as template. (just rename the vm as template, so original vm is
no more displayed as vm)
2) copy the vm to template. (original vm is available)
seem more easy, they are no vm with clones,
>>I want to delete the original, not the snapshot.
I don't see how it's possible,the snapshot by itself, it's just a referecence
in a point of time.
if you have a simple schema like this
10GB DATAS
baseimage->snap1
|
|-> clone1
> >>why not (we have a snaphot)? - those drivers do not allow that?
>
> Not sure for sheepdog, but rbd,nexenta you can't delete a snapshot if clone
> exist on the snasphot.
I want to delete the original, not the snapshot.
>(or storage should have some method to copy
> baseimage datas in each clo
>>Yes. Maybe we let user choose 'templateid'
>>we need to find a good template naming schema.
Templatename could be defined in the template config file.
So user can rename the template, without renaming the volume
snapname=templateid;
>>What is that (we talked about 'Copy VM', not 'Copy Templat
> >>When you create a template, you only need to create a volume snapshot.
> >>
> >>Is that more clear now?
>
> Yes,ok. So snapshot tabs on vm only display live-snapshots, and not all
> volume snapshots.
yes.
> For implementation, that give us something like this (oversimplified): ?
>
>
> cre
>>We need to define the terms we use:
>>
>>a.) live-snapshot (qemu-server snapshot, saved inside VM configuration)
>>b.) volume snapshot (storage internal snapshot of a volume)
>>
>>When you create a template, you only need to create a volume snapshot.
>>
>>Is that more clear now?
Yes,ok. So
> could you give an example for sheepdog,rbd? (as we need a snapshot of the
> disk) What happen to the original vm when you create the template ?
>
> Does it create a snapshot of the disks, and snapshot name(on the storage) is
> the template name ?
We need to define the terms we use:
a.) live-sn
>>I dont want to create template from snapshots.
>>I want to create templates form stopped VM
could you give an example for sheepdog,rbd? (as we need a snapshot of the disk)
What happen to the original vm when you create the template ?
Does it create a snapshot of the disks, and snapshot name(o
> one more question:
>
> to create a template from a snapshot,
> do you want:
I dont want to create template from snapshots.
I want to create templates form stopped VM
sub create_template(vmid) ...
> 1) create a snapshot
> 2) create a template
>
> or do it in 1 step:
>
> 1)create template (w
>>We can define our own Terms ;-)
>>clone:
>>- uses storage cloning features.
>>- a clone is always on the same storage
>>copy:
>>- is simply a copy of all data
>>- you can copy data to any other storage
>>So those are slightly different things.
Yes, I agree with that.
That seem to be
15 matches
Mail list logo
