Formatting of the new CW (installation using RAW image) #3423
Conversation
|
@dvosburg -- please add any feedback here. Thanks. |
modules/common-workflows/pages/workflow-install-from-raw-image.adoc
Outdated
Show resolved
Hide resolved
modules/common-workflows/pages/workflow-install-from-raw-image.adoc
Outdated
Show resolved
Hide resolved
|
|
||
| . *Make Image Accessible:* Copy the image to a web server (preferred), NFS server, or expand the [literal]``.raw`` file to add directly as a disk in a virtual environment (if supported). | ||
| . *Boot Media:* Provide a bootable ISO ({sles} 15 SPX or {sle-micro} 5.5) to access the "Rescue System." | ||
| Add [literal]``netsetup=1`` on the kernel command line for networking, or configure IP via [command]``ifcfg``. | ||
| . *Target Disk Setup:* In VMware, create: |
There was a problem hiding this comment.
This is generic workflow, so no specific hypervisor should be here.
| . *Target Disk Setup:* In VMware, create: | |
| . *Target Disk Setup:* If applicable, in virtual machine hypervisor, create: |
|
|
||
| . *Make Image Accessible:* Copy the image to a web server (preferred), NFS server, or expand the [literal]``.raw`` file to add directly as a disk in a virtual environment (if supported). | ||
| . *Boot Media:* Provide a bootable ISO ({sles} 15 SPX or {sle-micro} 5.5) to access the "Rescue System." | ||
| Add [literal]``netsetup=1`` on the kernel command line for networking, or configure IP via [command]``ifcfg``. |
There was a problem hiding this comment.
| Add [literal]``netsetup=1`` on the kernel command line for networking, or configure IP via [command]``ifcfg``. |
This step is happening during boot, i.e. next step, not during preparation.
| .. Add the following on the command line to enable network configuration. | ||
|
|
||
| + | ||
| ---- | ||
| netsetup=1 |
There was a problem hiding this comment.
This may work now, but AFAIK SLE16 (and I wonder if SL-Micro 6.1) does not ship linuxrc.
How about using ip= from dracut ( https://manpages.opensuse.org/Tumbleweed/dracut/dracut.cmdline.7.en.html#Network )
e.g. ip=dhcp for automatic assignment.
There was a problem hiding this comment.
We are talking about SUSE Manager 5.0 here, and are recommending people boot from SLE15/SLE Micro 5.X generation rescue media. The dracut command does not work from the linuxrc offered there.
We are not supporting SL Micro 6.1 nor SLE 16 media for these purposes until a later release of SUSE Manager.
Quite often customers may not have DHCP available. By choosing 'netsetup=1' they are prompted to either choose DHCP or configure manual settings. Alternatively they can follow the linuxrc 'ifcfg' configuration referenced here:
https://en.opensuse.org/SDB:Linuxrc#Using_ifcfg
There was a problem hiding this comment.
Well of course, I was hoping to have something which will work later as well. Still we can recommend SLE15 boot media till 2037, so I guess we are good.
| .. Use [command]``fdisk`` to confirm the root device name. | ||
| + | ||
| ---- | ||
| fdisk -l |
There was a problem hiding this comment.
This step can be skipped since we have the same information in the lsblk output when we omit device name.
| @@ -67,44 +66,34 @@ fdisk -l | |||
| ---- | |||
| blockdev --getpbsz /dev/sda | |||
There was a problem hiding this comment.
Let's use $device to be consistent with the curl command later.
| blockdev --getpbsz /dev/sda | |
| blockdev --getpbsz $device |
| @@ -67,44 +66,34 @@ fdisk -l | |||
| ---- | |||
| blockdev --getpbsz /dev/sda | |||
| ---- | |||
| + | |||
|
|
|||
| + | |||
| ---- | |||
| lsblk -o NAME,PHY-SEC /dev/sda | |||
There was a problem hiding this comment.
If we skip device name, lsblk will show all and we can choose the right one. This command should be moved up to replace fdisk -l command.
| lsblk -o NAME,PHY-SEC /dev/sda | |
| lsblk -o NAME,PHY-SEC |
| . *Finalize Boot and Configuration* | ||
|
|
||
| .. Power off the instance, remove the virtual CD from the boot sequence, and start it again to boot from the newly created instance. | ||
| .. Follow on-screen installation directions and, if needed, register with {scc}, adding the SUSE Manager Server Extension. |
There was a problem hiding this comment.
| .. Follow on-screen installation directions and, if needed, register with {scc}, adding the SUSE Manager Server Extension. | |
| .. Follow on-screen installation directions and, if needed, register with {scc}, adding the {productname} Server Extension. |
| + | ||
| ---- | ||
| mgr-storage-server $device | ||
| ---- | ||
| + | ||
| Ensure $device points to the fast, persistent storage added in VMware. | ||
| Ensure [literal]``$device`` points to the fast, persistent storage added in VMware. |
There was a problem hiding this comment.
| Ensure [literal]``$device`` points to the fast, persistent storage added in VMware. | |
| Ensure [literal]``$device`` points to the fast, persistent storage. |
|
|
||
| . *Boot Media:* Provide a bootable ISO ({sles} 15 SPX or {sle-micro} 5.5) to access the "Rescue System." Add netsetup=1 on the kernel command line for networking, or configure IP via ifcfg. | ||
|
|
||
| . *Make Image Accessible:* Copy the image to a web server (preferred), NFS server, or expand the [literal]``.raw`` file to add directly as a disk in a virtual environment (if supported). |
There was a problem hiding this comment.
We should remove the NFS server from this list - as the instructions are more complicated, and copying it to a webserver is not an onerous requirement.
We should include the 'dd' instructions if we give the option to direct mount the '.raw' disk - as this doc does not yet contain those steps.
….adoc Co-authored-by: Ondřej Holeček <[email protected]>
….adoc Co-authored-by: Ondřej Holeček <[email protected]>
This PR aligned the existing contribution (PR#3418) with the documentation writing guidelines.
Target branches