When you have installed the
SUSE Manager for Retail Server and the
SUSE Manager Retail Branch Server, you need to set up your environment by following these steps:
Install the build host and register it to SUSE Manager
Configure the build host
Create the required system group
These are the branch server setup steps:
Assign and configure branch server formulas
Synchronize images to the branch servers
Each procedure is detailed in this section.
SUSE Manager for Retail requires system groups for terminals and servers. Manually create these system groups during installation:
Additionally, you will need to create a system group for each branch server, and each terminal hardware type in your environment.
You can create system groups using the SUSE Manager Web UI. Navigate toand click Create System Group.
For more information about system groups, see reference:systems/system-groups.adoc.
Before you configure the branch server, ensure you have decided on networking topology, and know the Salt ID of the branch server.
The branch server can be configured automatically using the
retail_branch_init command, as shown in this section.
If you prefer to manually configure the branch server, you can do so using formulas.
For more information about formulas, see retail:retail-formulas-intro.adoc.
Branch server configuration is performed using the
This command will configure branch server formulas with recommended values. You can use the
retail_branch_init --helpcommand 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. You can do this through the Web UI, or by running this command:
salt <branch_server_salt_id> state.apply
The OS image you use on the SUSE Manager server must be synchronized for use on the branch server.
You can do this with the Salt
On the SUSE Manager server, run this command:
salt <branch_server_salt_id> state.apply image-sync
The image details will be transferred to
/srv/saltbooton the branch server.
POS Terminals based on SUSE Linux Enterprise Server 11 SP 3 can be deployed in much the same way as other terminals, with a few differences.
You must use the SLES 11 template
SLES 11 images need to be activated with the
SLES11 SP3 i586and
SLEPOS 11 SP3 i586channels
Ensure that SLES 11 images are built on the SLES 11 build host, and SLES 12 images are built on the SLES 12 build host. Building on the incorrect build host will cause your build to fail.
If you are building images for SLES 11 using profiles from an HTTPS git repository that uses TLS 1.0 or greater, it will fail. SLES 11 does not support later versions of TLS. You will need to clone the repository locally in order to use it for building.