The preseed examples in this repo (named lpar_1 in tools/0-preseed/) can be used to manually craft a set of files which will configure an lpar for network connectivity.
This lpar will have a primary disk containing a root and swap partition.
A preseed bundle consists of: lpar_name.ins, parmfile-lpar_name, and preseed-lpar_name.
Please read the heading of each file to see what information you will need.
In general, you will need to know:
- Disk IDs
- Network IDs
- VLAN IDs
- Preseed FTP Server address, directories and file names.
There is also a tool called 'tokenise' included here, which will currently generate a single preseed file based on command line switches. A future version of tokenise will use a yaml to output multiple preseed bundles.
The tokenise tool can be found in tools/0-preseed/tokenise.
There is currently a bug with setting bridge_state after a reboot. It must be set manually after any reboot, e.g.:
$ echo primary > /sys/devices/qeth/0.0.c003/bridge_role
Once your preseed bundles are crafted, each lpar can be "reloaded from removable media" manually and the appropriate preseed selected
Currently, the easiest way to install juju 2 on z is with via a snap:
$ sudo apt-get install snapd
$ sudo snapd install juju --classic
To bootstrap:
$ juju bootstrap manual/Bootstrap_host_IP controller_name --debug --verbose --constraints arch=architecture
e.g.
$ juju bootstrap manual/127.0.0.1 s390x --debug --verbose --constraints arch=s390x
If your controller is behind NAT, you should specify its 'external' or 'public' IP instead of 127.0.0.1
If you have specified a user other than ubuntu in your preseed, change it here. You will also need to know the ip address of each LPAR.
$ juju add-machine ssh:[email protected]
$ juju add-machine ssh:[email protected]
$ juju add-machine ssh:[email protected]
$ juju add-machine ssh:[email protected]
$ juju add-machine ssh:[email protected]
$ git clone https://github.com/ubuntu-openstack/zopenstack
$ cd zopenstack/
$ juju deploy bundles/lpar/focal-ussuri-next.yaml --map-machines=existing
The openstack-charm-testing repo provides scripts and profiles to configure an openstack environment.
simply run
$ tox -e clients
$ . .tox/clients/bin/activate
(clients) $ cd tools/2-configure/
(clients) $ ./configure s390x-multi-lpar-v3
Once the configuration is complete, you can move onto the testing phase
You should be able to launch a nova instance as follows:
(clients) $ # launch some instances
(clients) $ ./tools/instance_launch.sh 5 xenial-s390x
(clients) $ # give these instances public (ext_net) ip addresses
(clients) $ ./tools/float_all.sh
To see if the instance was launched successfully:
(clients) $ nova list
If the instance is ready, use the ssh command provided in the instance_launch output to see if you can ssh to the nova instance, e.g.:
(clients) $ deactivate
$ ssh -i ~/testkey.pem ubuntu@ip_address
WIP
WIP