Ich habe mir 2 Subscriptions für Testzwecke geholt. ich will damit alles mögliche ausprobieren. Kann ich problemlos die Subscriptions auf immer wieder neuen VMs verwenden? Oder wird mir Suse irgend wann “Game Over” sagen?
GrüÃe
Nobbe
Hi and welcome to the Forum 
The primary language for these forums is English, but google translate indicates you have two test subscriptions and wish to create multiple Virtual machines.
Ref: https://www.suse.com/support/programs/subscriptions/
From: https://www.suse.com/products/terms_and_conditions.pdf
Page 10:
I would just do your tests, de-register with SUSEConnect VM and create your new VM, register that test etc.
[QUOTE=malcolmlewis;54195]Hi and welcome to the Forum 
The primary language for these forums is English, but google translate indicates you have two test subscriptions and wish to create multiple Virtual machines.
Ref: https://www.suse.com/support/programs/subscriptions/
From: https://www.suse.com/products/terms_and_conditions.pdf
Page 10:
I would just do your tests, de-register with SUSEConnect VM and create your new VM, register that test etc.[/QUOTE]
OK, I need one VM for some Tests, but always a clean one. So there will be never more than one VM actually existing. But if I do that I must always first delete the former subscription, or? It will not get overwritten.
greetings.
Hi
Yes, you will just need to de-register, this will remove the
allocation from SCC (https://scc.suse.com/) so your free to use on a
new setup/system.
I would create a base install and register that, then create a snapshot
of the VM to use for your tests… complete your test, the de-register
for the next tests…
SUSEConnect -d
-d, --de-register
De-registers the system and base product, or in conjunction with
--product, a single extension, and removes all its services installed
by SUSEConnect. After de-registration the system no longer consumes a
subscription slot in SCC.–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.16-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
nobbe1964 wrote:
[color=blue]
OK, I need one VM for some Tests, but always a clean one. So there
will be never more than one VM actually existing.[/color]
Why can you not reuse the same VM?
After you build your VM, register it, and apply any needed updates:
-
Take a snapshot then revert to that snapshot when you need a new VM.
-
Make a backup and restore the backup.
-
Shutdown the VM and make a copy of the whole VM. Make a copy of your
copy each time you need a new VM.
Any of these approaches will give you a new VM each time you need one
but it will be a new copy of the same VM: already registered, patched,
and ready to go!
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
On 02/09/18 15:36, Kevin Boyle wrote:
[color=blue]
Why can you not reuse the same VM?
After you build your VM, register it, and apply any needed updates:
Take a snapshot then revert to that snapshot when you need a new VM.
Make a backup and restore the backup.
Shutdown the VM and make a copy of the whole VM. Make a copy of your
copy each time you need a new VM.Any of these approaches will give you a new VM each time you need one
but it will be a new copy of the same VM: already registered, patched,
and ready to go![/color]
It’s probably worth noting that you should only run one copy of the VM
at any one time and also not a good idea to patch each “copied” VM
separately (i.e. patch the master then re-clone/copy rather than patch
each clone individually).
HTH.
Simon
SUSE Knowledge Partner