Bug 1088155 - Kubic: docker.service is inactive by default instead of CaaSP
Kubic: docker.service is inactive by default instead of CaaSP
Status: RESOLVED WORKSFORME
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kubic
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Kubic Bugs
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-04 17:48 UTC by Mikhail Kasimov
Modified: 2018-04-05 13:38 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Kubic_docker_service_by_default (9.38 KB, image/png)
2018-04-04 17:48 UTC, Mikhail Kasimov
Details
CaaSP_docker_service_by_default (16.39 KB, image/png)
2018-04-04 17:48 UTC, Mikhail Kasimov
Details
kubic_microos_by_default (50.79 KB, image/png)
2018-04-04 20:39 UTC, Mikhail Kasimov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Kasimov 2018-04-04 17:48:04 UTC
Created attachment 765995 [details]
Kubic_docker_service_by_default

Hello!

Subj

======================================
Kubic: systemctl status docker.service (see Kubic_docker_service_by_default.png)

CaaSP: systemctl status docker.service (see CaaSP_docker_service_by_default.png)
======================================
Comment 1 Mikhail Kasimov 2018-04-04 17:48:27 UTC
Created attachment 765996 [details]
CaaSP_docker_service_by_default
Comment 2 Richard Brown 2018-04-04 18:51:23 UTC
Which system role?

Kubic installs MicroOS by default

MicroOS should not have a container runtime enabled by default

If you chose MicroOS during installation, your comparison to CaaSP isn't helpful, as it only has roles where a container runtime is enabled by default.
Comment 3 Mikhail Kasimov 2018-04-04 19:03:45 UTC
(In reply to Richard Brown from comment #2)
> Which system role?
> 
> Kubic installs MicroOS by default
> 
> MicroOS should not have a container runtime enabled by default
> 
> If you chose MicroOS during installation, your comparison to CaaSP isn't
> helpful, as it only has roles where a container runtime is enabled by
> default.

Is there some helper in Kubic/CaaSP like get-current-server-role in cli to have such info quickly?

All settings both for K and CP were by default on installation.

As I remember, for CP it was Administrative Node (fist option in list).
Comment 4 Thorsten Kukuk 2018-04-04 19:12:59 UTC
(In reply to Mikhail Kasimov from comment #3)

> Is there some helper in Kubic/CaaSP like get-current-server-role in cli to
> have such info quickly?

No, you should know what you select during installation...

If kubernetes is installed, it's either the Admin-Node, Cluster-Node or Plain System node. If kubernetes is not installed, it's MicroOS.

> All settings both for K and CP were by default on installation.
> 
> As I remember, for CP it was Administrative Node (fist option in list).

Kubic is not CaaSP and has different or better more options.

Since docker is not enabled, it was either Plain System or MicroOS you did install.
Comment 5 Mikhail Kasimov 2018-04-04 19:25:56 UTC
(In reply to Thorsten Kukuk from comment #4)
> (In reply to Mikhail Kasimov from comment #3)
> 
> > Is there some helper in Kubic/CaaSP like get-current-server-role in cli to
> > have such info quickly?
> 
> No, you should know what you select during installation...

And I can forget this in a hour, 2 hours, in a week after all... Without any possibility form system to remind it myself via something like 'get-current-server-role' command in cli. Need I file the separate report for that? But do not push me to fate.opensuse. org, please... :)

 
> If kubernetes is installed, it's either the Admin-Node, Cluster-Node or
> Plain System node. If kubernetes is not installed, it's MicroOS.
> 
> > All settings both for K and CP were by default on installation.
> > 
> > As I remember, for CP it was Administrative Node (fist option in list).
> 
> Kubic is not CaaSP and has different or better more options.
> 
> Since docker is not enabled, it was either Plain System or MicroOS you did
> install.

Honestly, I don't remember (see my note above) this nuance... Everything what I really remember -- that all setting (except GUI language) were by default.

Now I'm taking a pause to re-install K to refresh my mind... Will reply later.
Comment 6 Mikhail Kasimov 2018-04-04 20:38:36 UTC
(In reply to Thorsten Kukuk from comment #4)
> (In reply to Mikhail Kasimov from comment #3)
> 
> > Is there some helper in Kubic/CaaSP like get-current-server-role in cli to
> > have such info quickly?
> 
> No, you should know what you select during installation...
> 
> If kubernetes is installed, it's either the Admin-Node, Cluster-Node or
> Plain System node. If kubernetes is not installed, it's MicroOS.
> 
> > All settings both for K and CP were by default on installation.
> > 
> > As I remember, for CP it was Administrative Node (fist option in list).
> 
> Kubic is not CaaSP and has different or better more options.
> 
> Since docker is not enabled, it was either Plain System or MicroOS you did
> install.

Seems, yes, you're right: the first option for K is openSUSE MicroOS (see kubic_microos_by_default.png).
Comment 7 Mikhail Kasimov 2018-04-04 20:39:10 UTC
Created attachment 766030 [details]
kubic_microos_by_default
Comment 8 Thorsten Kukuk 2018-04-05 13:38:13 UTC
That docker is not running by default in the MicroOS system role is correct.