Set Up the SUSE Manager for Retail Environment with dedicated network for terminal using bundled scripts
To set up the SUSE Manager for Retail environment, you will need to have already installed and configured:
-
SUSE Manager for Retail Server
-
one or more SUSE Manager for Retail branch server proxies
-
one or more POS images built
1. Assumptions
This guide works only with non-containerized SUSE Manager for Retail branch proxy 4.3 |
In this example we consider architecture with dedicated network for POS terminals where branch server provides all required services including DHCP and DNS.
For dedicated network we assume 192.168.86.0/24 network.
In this example we provide salt
and ftp
CNAMEs for Saltboot service discovery.
We assume to have one regular branch server with salt minion id branch1.mystore.com
, which is equal to the branch server fully qualified domain name, and branch id B0001
.
As a terminal we assume to have one terminal with hardware manufacturer TerminalOEM
and model T1000
.
For POS image we assume to have one with name POS_Image_JeOS7
.
This example covers two configuration methods with both of them achieving same result.
2. Quick set up of SUSE Manager for Retail using for Retail tools
-
SUSE Manager for Retail provides command line tool
retail_branch_init
-
SUSE Manager for Retail provides mass import command line tool
retail_yaml
The branch server can be configured automatically using the retail_branch_init
command, as shown in this section.
-
Run following command on SUSE Manager Server:
retail_branch_init branch1.mystore.com --dedicated-nic eth1 \ --branch-prefix B0001 \ --server-domain branch1.mystore.com \ --branch-ip 192.168.86.1 \ --dyn-range 192.168.86.10 192.168.86.250 \ --netmask 255.255.255.0
You can use the
retail_branch_init --help
command for additional options. -
Verify that your changes have been configured correctly by checking the SUSE Manager Web UI branch server system formulas.
-
Apply highstate on the branch server.
Similar results can be achieved by using mass import command line tool.
-
Prepare branch specific YAML file:
For example, create
branch.yaml
file with content:branches: branch1.mystore.com: branch_prefix: B0001 server_domain: branch1.mystore.com nic: eth1 dedicated_nic: true configure_firewall: true branch_ip: 192.168.86.1 netmask: 255.255.255.0 dyn_range: - 192.168.86.10 - 192.168.86.250
For more information about mass import tool, see Mass Configuration.
-
Import branch information from YAML file to SUSE Manager
retail_yaml --from-yaml branch.yaml
-
Verify that your changes have been configured correctly by checking the SUSE Manager Web UI branch server system formulas.
-
Apply highstate on the branch server.
Both |
After the initial configuration done by command line tools, branch server configuration can be further adjusted in SUSE Manager Web UI through branch server formulas.
3. Setup partitioning
Follow 시스템 그룹 to create HWType:TerminalOEM-T1000
system group.
Partitioning is specific to the hardware type and configured using Saltboot
formula.
-
Navigate to
-
Select group
HWType:TerminalOEM-T1000
, which is our hardware type group -
Select the
Formulas
tab once in group details -
You should see list of formulas in
Configuration
sub-tab -
In displayed list select
Saltboot
-
Save assigned formulas by clicking Save in top right corner
-
Select Saltboot formula from
HWType:TerminalOEM-T1000
group formula list -
Set
Disk Symbolic ID
toDisk1
-
Set
Device Type
toDISK
-
Set
Disk Device
to*
-
Set
Partition table type
togpt
-
Click + to add a partition
-
Set
Partition Symbolic ID
top1
-
Set
Partition Size (MiB)
to512
-
Set
Device Mount Point
to/boot/efi
-
Set
Filesystem Format
tovfat
-
Set
Partition Flags
toboot
-
-
Click + to add a partition
-
Set
Partition Symbolic ID
top2
-
Set
Device Mount Point
to/
-
Set
OS Image to Deploy
toPOS_Image_JeOS7
-
-
Save the formula
After all procedures are done, apply highstate on the branch server.
4. Synchronize images
After highstate is applied, we proceed with synchronizing images as usual with apply image-sync
state.
Terminal can now be started and will be automatically provisioned, pending salt key acceptance.