Plugin should use 'subscription-manager version' to determine whether the VM is already registered

[hferentschik]

If it is registered, there is no need to call registration again.

[pvalena]

If you set .force = false, it won't register again. The default behavior for now is to re-register if already registered to ensure the subscription is valid.

[hferentschik]

If you set .force = false, it won't register again.

I want to improve the user experience w/o adding/using additional configuration in the Vagrantfile

The default behavior for now is to re-register if already registered to ensure the subscription is valid.

The problem is that registration takes a very long time. If we can find a faster way to verify that a VM is already registered (for example by using subscription-manager version which seems faster`), we will improve the overall user experience.

[pvalena]

Yes, i think there can be some general enhancement in way we work with subscription-manager. I will check with subscription-manager maintainers.

If we can find a faster way to verify that a VM is already registered

It will not affect current (default) behavior, as it will register anyway.

[hferentschik]

It will not affect current (default) behavior, as it will register anyway.

Maybe it does not have to. We introduce a validity re-check interval. Just as an example. Bottom line, right now subscription is very slow, probably one of the biggest time consumers in a 'vagrant up'. Also, for most users, there is no reason why one would un-register and register on each up/halt cycle.

There are already several options which control the registration behavior, but I believe they have the wrong default. The majority of users will have a single ADB/CDK box which needs to be registered once. We should optimize for this use case. If someone really want to have multiple setups and swtich between them, he can use config.registration.unregister_on_halt = true to make sure his single license gets released.

[hferentschik]

See also #72