A couple questions ( on configuration )
by Pigi
Hi all,
I have a couple question on configuration.
The first one ( maybe the easiest ) is: can I change the IP plan that is used to build the undercloud ?
I would like to not have the whole undercloud on 192.168.24.x ( as it is ) but on othen plan address. Can it be done ?
Should it be done before starting quickstart or I need to change after quickstart has completed ?
The second is more complex ( but always on network ). On my evironment I have two nets: one for the administration and one for the baremetal/
provisioning stuffs.
This second one is not routed and live on different ethernet interfaces either on the undercloud than on baremetals machines. I know that quickstart build
an environment on control and compute node as virtualmachine but my idea is to integrate this with some physical machines ( compute and control).
To achieve this I need to use the provisioning network and then I need to make either the NIC than the network available to undercloud host.
Any hint on how to get this ?
Thanks in advance
Pierluigi
5 years, 9 months
Trouble with quistart.sh
by Pigi
Hi all,
I'm trying to setup an environment for test using quickstart.sh
On my previous attempt I was on vmware and had quite a lot of trouble, then I deided to go with physical servers.
Everything seemed to be fine until I hit an error:
TASK [overcloud-prep-images : Prepare the overcloud images for deploy] *******************************************************************************************************************************************
task path: /root/.quickstart/usr/local/share/ansible/roles/overcloud-prep-images/tasks/overcloud-prep-images.yml:2
Wednesday 30 January 2019 17:55:26 +0100 (0:00:08.814) 3:19:01.327 *****
fatal: [undercloud]: FAILED! => {
"changed": true,
"cmd": "set -o pipefail && /home/stack/overcloud-prep-images.sh 2>&1 | awk '{ print strftime(\"%Y-%m-%d %H:%M:%S |\"), $0; fflush(); }' > /home/stack/overcloud_prep_images.log",
"delta": "0:00:55.437392",
"end": "2019-01-30 16:56:22.968243",
"rc": 1,
"start": "2019-01-30 16:55:27.530851"
}
MSG:
non-zero return code
Now I have to questions:
1) How do I can trace the error to understand and fix what's happening ?
2) How can I avoid to start all over again with quickstart.sh, being that my hardware is quite slow and it took my more than 4 hours to get there ?
( I know quickstart has tags, but I can't find any info on which ones are, and how to use them )
Thanks in advance
Pierluigi
5 years, 9 months