Skip to content

Commit

Permalink
remove FIXMEs and add clarifications
Browse files Browse the repository at this point in the history
(per feedback)
  • Loading branch information
keichwa committed Oct 7, 2024
1 parent ab4ccec commit 426b310
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 79 deletions.
75 changes: 0 additions & 75 deletions modules/installation-and-upgrade/pages/install-ignition.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,6 @@
= Boot Image Configuration Tools


// FIXME: is labeling name such as Boot Image Configuration Tool correct?
// can we drop clould-init here?
// is combustion available and shall we mention it?

[IMPORTANT]
====
{productname} VM images are prepared with JeOS firstboot configuration dialogs.
Expand Down Expand Up @@ -96,74 +92,3 @@ This particular example is setting the [systemitem]``root`` password to `linux`.
Substitute your password hash for the one in this example.

For more information about [systemitem]``Ignition``, see https://documentation.suse.com/sle-micro/5.4/single-html/SLE-Micro-deployment/#cha-images-ignition.


////
// FIXME: adjust and enable the following, if needed
[[sumavm.cloud_init]]
== {productname} basic configuration using Cloud Init disk
[systemitem]``Cloud Init`` is a provisioning tool that enables you to configure a system according to your specification on the first boot.
When the system is booted for the first time, [systemitem]``Cloud Init service`` is loaded and searches for a configuration file within a specific directory (on a USB flash disk, or you can provide a URL).
[systemitem]``Cloud Init`` uses few configuration files in the YAML format. Used files are named [path]``meta-data``, [path]``network-config`` and [path]``user-data``.
[systemitem]``Cloud Init`` allows numerous sources where to store configuration data.
In this guide we use local iso image with volume id [literal]``cidata`` as a source.
The directory structure must look as follows:
----
<root directory>
└── meta-data
└── network-config
└── user-data
----
If you intend to configure a QEMU/KVM virtual machine, provide the path to the [path]``config.ign`` as an attribute of the qemu command.
For example:
----
-fw_cfg name=opt/com.coreos/config,file=PATH_TO_config.ign
----
The [systemitem]``Cloud Init`` allows many management options. For a complete specification, refer to Cloud Init specification (https://cloudinit.readthedocs.io/en/latest/index.html).
=== Set Up Root Password Using Cloud Init
You need to hash the root password, for example, by using the [command]``openssl`` command:
----
openssl passwd -6
----
The command creates a hash of the password you chose.
Use this hash as the value of the [literal]``password`` attribute.
Prepare the needed configuration files using the following commands:
----
touch network-config
touch meta-data
----
Create a file named [path]``user-data`` with the following content:
----
#cloud-config
chpasswd:
expire: false
users:
- name: root
password: $2a$10$qV298UV11u9lCFDjpHpCUe1cErBiVR.G3shukxs3.2PAO1xhJWs0K
----
Prepare [systemitem]``Cloud Init`` ISO file using the command:
----
mkisofs -rational-rock -joliet -o suma_cloudinit.iso -V cidata network-config meta-data user-data
----
Attach the created [path]``suma_cloudinit.iso`` file as a volume to the creating virtual machine.
This particular example is setting [systemitem]``root`` password to `linux`.
Substitute your password hash for the one in this example
////
5 changes: 1 addition & 4 deletions modules/installation-and-upgrade/pages/install-vm.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -113,12 +113,9 @@ This sections describes VMware configurations, focusing on the creation of an ex

. Make a copy of uploaded [filename]``.vmdk`` file using VMware web interface.
This will convert provided [filename]``.vmdk`` file to the format suitable for vSpere hypervisor.
Use this new copy as a base image for the virtual machine.

. Create and name a new virtual machine based on the Guest OS Family [systemitem]``Linux`` and Guest OS Version {sle} 15 (64-bit).
+

// FIXME: Do we need the following step? I think, in 5.0 we removed it
. In [guimenu]``Customize settings`` browse to the uploaded [filename]``.vmdk`` using [systemitem]``IDE controller 0`` storage device in the [systemitem]``Controller Location``.

. Add an additional [systemitem]``Hard Disk 2`` of 500 GB (or more).

Expand Down

0 comments on commit 426b310

Please sign in to comment.