Bug 39206 - systemUUID handling in Docker
systemUUID handling in Docker
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Docker
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1
Assigned To: Stefan Gohmann
Arvid Requate
: interim-1
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-17 11:26 CEST by Stefan Gohmann
Modified: 2015-11-17 12:11 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2015-08-17 11:26:38 CEST
If the UCS docker container is started by the App Center, the system uuid of the UCS host system is used.
Comment 1 Philipp Hahn univentionstaff 2015-08-18 09:35:28 CEST
(In reply to Stefan Gohmann from comment #0)
> If the UCS docker container is started by the App Center, the system uuid of
> the UCS host system is used.

So what?
- should a different UUID be used per container?
- or is this not implemented yet (is -> should)?
- why is this bad?
Comment 2 Stefan Gohmann univentionstaff 2015-09-11 07:37:44 CEST
(In reply to Philipp Hahn from comment #1)
> (In reply to Stefan Gohmann from comment #0)
> > If the UCS docker container is started by the App Center, the system uuid of
> > the UCS host system is used.
> 
> So what?
> - should a different UUID be used per container?
> - or is this not implemented yet (is -> should)?

I don't know the current state. It has to be checked. I've described the target state.

> - why is this bad?

We need to know the real number of UCS installations for various reasons. If every App installation in a docker container is counted, the number does not match the real UCS installation number. For example if all Apps are delivered as  Docker container and I've installed seven Apps on my UCS, the old count handling would count eight different systems.

On the other hand, if I install a UCS DC Master and a UCS DC Backup as Docker container, these installations should be counted as two systems.
Comment 3 Stefan Gohmann univentionstaff 2015-09-11 07:55:48 CEST
(In reply to Stefan Gohmann from comment #2)
> We need to know the real number of UCS installations for various reasons. If
> every App installation in a docker container is counted, the number does not
> match the real UCS installation number. For example if all Apps are
> delivered as  Docker container and I've installed seven Apps on my UCS, the
> old count handling would count eight different systems.

Maybe we should just use the identifier for the differentiation. I guess it will be a problem for the current count handling if we have two different systems with the same UUID and different UCS versions.
Comment 4 Daniel Tröder univentionstaff 2015-09-11 09:11:31 CEST
What about a more generalized solution that takes into account, that UCS is headed for the cloud:

Identify
* UCS as simple host
* UCS as UVMM
* UCS in VM
* UCS in container
and in each its role.

Build it as a tree:

customer
|
+-Vmware
|   |
|   +-UCS VM (backup)
|   |
|   +-UCS VM (slave)
|   |  |
|   |  +-UCS container (member)
|   |  +-UCS container (slave)
|   |
|   +-UCS VM (backup)
|
+-UCS host (master)
|
+-UCS UVMM (slave)
   |
   +-UCS container (member)
   +-UCS VM (member)
      |
      +-UCS container (member)

Encode all as b64(json) or scheme/lisp or similar so it can fit into a URL (or however this is usually transfered).

This view will allow to understand better how UCS is used by cloud providers.
Comment 5 Stefan Gohmann univentionstaff 2015-09-11 13:49:18 CEST
(In reply to Daniel Tröder from comment #4)
> What about a more generalized solution that takes into account, that UCS is
> headed for the cloud:

Nice idea. I guess it will be hard to get all the information, for example to determine the hypervisor but it should be possible.
Nevertheless, it is a little bit out of scope. The goal of this issue is to get reliable numbers about the UCS installation basis after the release of UCS 4.1.

Fixed with r63640
UUID reporting: r63641

Changelog is not needed because the docker integration is new.
Comment 6 Daniel Tröder univentionstaff 2015-09-11 14:16:49 CEST
hypervisor detection: http://people.redhat.com/~rjones/virt-what/
Comment 7 Stefan Gohmann univentionstaff 2015-09-27 20:16:01 CEST
I've added 80_docker/61_app_updater_identify to test the variable. Still marked as WIP, waiting for Bug #39413.
Comment 8 Arvid Requate univentionstaff 2015-10-07 19:45:17 CEST
Ok, the UCR variable updater/identify gets set to "Docker App".
The reporting filters out systems identifying as such.
Comment 9 Stefan Gohmann univentionstaff 2015-11-17 12:11:26 CET
UCS 4.1 has been released:
 https://docs.software-univention.de/release-notes-4.1-0-en.html
 https://docs.software-univention.de/release-notes-4.1-0-de.html

If this error occurs again, please use "Clone This Bug".