[Starlingx-discuss] Installation_Guide_Virtual_Environment / Ubuntu Specific

scottk at optimcloud.com scottk at optimcloud.com
Fri Sep 7 12:15:19 UTC 2018


ok so, Ive gotten my ISO built finally and decided to move forward, it did actually install and run under kvm on fedora 28, alas it would not let me run
i hunted around and got the interface up on dhcp and logged in... 

sudo config_controller as it requires 4 interfaces to start up

so hunted the wiki a bit and found this guide

https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment (https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Duplex)

where it plainly states

Software Requirements
A workstation computer with:

Operating System: Freshly installed Ubuntu 16.04 LTS 64-bit
Proxy settings configured (if applies)
Git
KVM/VirtManager
Libvirt Library
QEMU Full System Emulation Binaries
<stx-deployment> project
StarlingX ISO Image
Deployment Environment Setup
This section describes how to set up a StarlingX Controller Storage system in a workstation computer. After completing these steps, you will be able to deploy and run your StarlingX system on the following Linux distribution:

Ubuntu 16.04 LTS 64-bit

... Now <RANT> I have to ask Why.... Seriously? </RANT>

We dont all use Ubuntu... StarlingX isnt even based on Ubuntu.... and you actualy put more effort into making it ubuntu specific then was needed to allow for other hosts operating systems. Okay, any way to proceed i ran networking config, no worries, went to run 

./setup_allinone.sh -i bootimage.iso

and sorry failed..... read the script... WTF ??

dont need this....

 diff -ruN setup_allinone.sh.orig setup_allinone.sh 
--- setup_allinone.sh.orig 2018-09-07 13:25:06.514256691 +0200
+++ setup_allinone.sh 2018-09-07 13:25:23.148154595 +0200
@@ -28,10 +28,6 @@
 ISOIMAGE=$(readlink -f "$ISOIMAGE")
 FILETYPE=$(file --mime-type -b ${ISOIMAGE})
-if ([ "$FILETYPE" != "application/x-iso9660-image" ]); then
- echo "$ISOIMAGE is not an application/x-iso9660-image type"
- exit -1
-fi
 BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr}
 CONTROLLER=${CONTROLLER:-controller-allinone}

edited, run it again, gui pops up ... console says

 ./setup_allinone.sh -i bootimage.iso   13:36  07.09.18  45.93G RAM 
Formatting '/var/lib/libvirt/images/controller-allinone-0-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Formatting '/var/lib/libvirt/images/controller-allinone-0-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16
error: Failed to define domain from vms/controller-allinone-0.xml
error: operation failed: domain 'controller-allinone-0' already exists with uuid 8414049f-c910-4605-a880-05fc8d35b683

error: Failed to start domain controller-allinone-0
error: unsupported configuration: Unable to find security driver for model apparmor

Formatting '/var/lib/libvirt/images/controller-allinone-1-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Formatting '/var/lib/libvirt/images/controller-allinone-1-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16
error: Failed to define domain from vms/controller-allinone-1.xml
error: operation failed: domain 'controller-allinone-1' already exists with uuid f66ed9f5-226b-47ce-ab23-47ee99b2f257

OMG... KILL ME NOW.... edit edit edit

 ./setup_allinone.sh -i bootimage.iso   13:39  07.09.18  45.88G RAM 
Formatting '/var/lib/libvirt/images/controller-allinone-0-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Formatting '/var/lib/libvirt/images/controller-allinone-0-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Domain controller-allinone-0 defined from vms/controller-allinone-0.xml

error: Failed to start domain controller-allinone-0
error: internal error: process exited while connecting to monitor: 2018-09-07T11:40:02.994268Z qemu-system-x86_64: -machine pc-i440fx-xenial,accel=kvm,usb=off,dump-guest-core=off: unsupported machine type
Use -machine help to list supported machines

Formatting '/var/lib/libvirt/images/controller-allinone-1-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Formatting '/var/lib/libvirt/images/controller-allinone-1-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Domain controller-allinone-1 defined from vms/controller-allinone-1.xml

REALLY NOW.... EDIT EDIT EDIT.....
./setup_allinone.sh -i bootimage.iso   13:44  07.09.18  45.86G RAM 
Formatting '/var/lib/libvirt/images/controller-allinone-0-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Formatting '/var/lib/libvirt/images/controller-allinone-0-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Domain controller-allinone-0 defined from vms/controller-allinone-0.xml

Domain controller-allinone-0 started

Formatting '/var/lib/libvirt/images/controller-allinone-1-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Formatting '/var/lib/libvirt/images/controller-allinone-1-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Domain controller-allinone-1 defined from vms/controller-allinone-1.xml

and ... TADA..... functionally working on Fedora 28 and actually installing at this moment..... so... seriously i have to ask....

when do you want to offer me a job..... because this shouldnt be happening..... anyway..... I find it awesome that you used CentOS for the platform, great choice...
but why would you force uus to use Ubuntu as the host... personally from an R&D perspective, We all know theres more then one decent desktop distribution. I would alone ask that some attention maybe be paid to making it more distro friendly, because i can almost guarantee I wount be the first one to go down this path.

Maybe im ranting a bit... but 5 days to get to this point on something you would like to be considered as a viable openstack platform.... Yes, i understand its development, its always in flux, though I fought to achieve just getting this far.... I am almost positive others wount be as patient, because we all know when a corporation delivers something new and shiny, users well... they just want it to work... and if it doesnt its going to potentially give the distro and the company behind it a black eye....

This is just my observations.... from a senior level management perspective of what Ive seen in the industry... if yyou want to be accepted, I belive you will maybe need more polishh... but so fgar great work, in sight of a few things maybe over looked.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180907/063341c7/attachment.html>


More information about the Starlingx-discuss mailing list