search

SUSE / manager-build-profiles

Example profiles for building images and systems with SUSE Manager and Uyuni
15 stars 44 forks source link

Add kiwi-desc-saltboot requirement #3

Closed aaannz closed 6 years ago

mbologna commented 6 years ago

Maybe we can also add in which repo kiwi-desc-saltboot?

aaannz commented 6 years ago

The repo is internal only. This remark can be left here even when kiwi-desc-saltboot is released.

abhinav-puri commented 6 years ago

It may help to add the following statement:

The kiwi-desc-saltboot package, as well as the reference templates for POS images, will be made available in the Manager:Tools channel with the release of SUSE Manager for Retail 3.2.

Thoughts? @mbologna @aaannz @joesusecom @kkaempf

kkaempf commented 6 years ago

@aaannz please add a reasonable description

If it's a package, where is it needed ? If on the server, then it needs to go into Manager-Update If on the client, then it needs to go into Manager-Tools

In any case, please get in contact with @juliogonzalez

aaannz commented 6 years ago

@kkaempf This it nothing new, there is already approved ECO for this and issue https://github.com/SUSE/spacewalk/issues/5202 which I planned to do this sprint, but was postponed due to running MU.

abhinav-puri commented 6 years ago

@kkaempf

This is related to the following issue: https://github.com/SUSE/spacewalk/issues/5202

mbologna commented 6 years ago

To summarize: to build the public example profile here the customer needs to have kiwi-desc-saltboot installed in the OS Image build host. Until the package will be published in Manager:Tools (because it's needed on the client), the package lives inside an internal repo: Devel:SLEPOS:SUSE-Manager-Retail:Head How can the customer install kiwi-desc-saltboot if the package is installable only from an internal repo?

aaannz commented 6 years ago

How can the customer install kiwi-desc-saltboot if the package is installable only from an internal repo?

They cannot. Customer can build images of other boot types - oem, iso, containers I guess. Just not the saltboot one. Customer can even build netboot based images used in previous SLEPOS/SMR3.1 product. Some of the boot types is a subject of installing corresponding kiwi-desc-* packages available on SLES12SP3 system:

> zypper se kiwi-desc-*
Loading repository data...
Reading installed packages...

S | Name              | Summary                                          | Type
--+-------------------+--------------------------------------------------+--------
  | kiwi-desc-isoboot | KIWI - Live ISO boot templates                   | package
  | kiwi-desc-netboot | KIWI - PXE network boot templates                | package
  | kiwi-desc-oemboot | KIWI - Expandable Virtual Machine boot templates | package
  | kiwi-desc-vmxboot | KIWI - Virtual Machine boot templates            | package

For e.g. Tumbleweed provided Uyuni, boot type descriptions are in package kiwi-boot-descriptions

It is true, that for these other boot types there are no examples in this repository. As an experiment, JeOS templates can be taken from OBS, but who will then maintain these examples?

abhinav-puri commented 6 years ago

If there is no way that the customer can install the kiwi-desc-saltboot package, and the customer can only build images for other boot types, then it should be documented that this feature is unsupported at the moment.

We can only support images as long as they are based on the POS-* templates.

mbologna commented 6 years ago

I agree with @abhinav-puri and I think we should rephrase the message presented in the README.

aaannz commented 6 years ago

Ok, I updated readme with disclaimer and also added note about image deployment.

mbologna commented 6 years ago

Feel free to merge, thanks!

aaannz commented 6 years ago

@mbologna Thanks for review, I however can't merge. Seems like I lack some permissions.