[manager-beta] Unable to install system with yomi

[Alberto Planas Dominguez]

> I am using the sles15 version. I will receive a pop-up how to register
> against SCC but no system will be registered with SALT.

I do not get this. You mean the yomi image via PXE boot? If so this pop up was fixed some weeks ago. There is a new jeos-firstboot and a new image with this new version that fix this issue.

> Then logging into that server I see that the master has been set to 
> salt. This means that you have to have a DNS entry for salt. This is in 
> my opinion a very bad idea. The master should be given with a parameter 
> during boot.

Right. You can change that adding "master=server.example.org" in the kernel command line, during the cobbler registration.

For the "salt" default name, I was under the idea that this is the recommended default for SUMA.

In any case this is a point that needs be better documented in SUMA, I will add a note to address this.

> Configuring the formulas show that there is still a lot to be done. Some 
> examples:

> Yomi Storage:

> - when selecting btrfs for /, I would expect that the default 
> sub-volumes are set automatically. This is not the case.

This is a limitation of the formula infrastructure. And I agree. There are a lot of defaults that can be set depending on previous user selections.

> - filesystem xfs is not present. And this is mostly used especially for 
> data volumes.

Ahhh good point! I will add this ASAP.

> Yomi Software:

> - I would expect that I can select software channels that are present in 
> SUSE Manager. I think we should use what is available as distribution 
> repositories. They can then be used during installation.

Channel is a concept of SUMA? I will take note, as the integration is still very minimal. In this stage Yomi is only the installer, and the pillars are only for the installation part. In this sense is like autoyast today (AFAIK you cannot set SUMA concepts in the autoyast profile)

This is an area that I want to extend, separating yomi and yomi-suma states. I will take note for this one.

> - If then the channels are selected from within SUSE Manager, it should 
> be easy to display the available patterns to be installed. This should 
> be done via checkboxes.

AFAIK this is far for what the forms can do today using the declarative YAML file. I will take notes to ask to the right developers about how this can be addressed.

> Yomi Services:

> - If you select to install salt-minion, there should be a drop down box 
> that allow to select the activation key. The needed configuration files 
> (normally done during bootstrap) should then also be created accordingly.

This activation key is also a SUMA concept. But I agree, this should be possible to set. This is related with the bootstrap process.

Did you try to manually bootstrap the node after the provisioning? If so, did you find problems there?

> Please feel free to contact me if you have more questions or need 
> assistance. I like this way of setting up servers, but we also would 
> need automation in the next step.

Yes please, this is super good feedback. I do not know much about SUMA, and how it is used by an admin.

If you see other areas of better integration, please provide the information and I will address them.