Novice question at at
Fri May 27 11:08:03 UTC 2022

Naïve question follows. Sorry.
I’m trying a minimal OS install on a Virtualbox VM on a mac. I’d like to get to the point where I can launch a compute node.  I’ve failed with `packstack` and I’m trying `devstack`.
Should this work out of the box: ie
Spin up a vm with vagrant: I’m using Centos Stream 9 to ensure that I get a current(ish) version of Python. It has 9GB RAM
Ensure that SELinux and firewalls are turned off
Clone devstack, cd to the directory and run `` as user `vagrant` (this fails 1/3 of the time as some repo or other resets a connection. `` doesn’t seem to be idempotent as reinvoking it may or may not install and run the OS environment
Upload a ssh keypair through the web interface
Use the web interface to launch the m1.nano flavor with Cirros image (I think that this flavor is quite new as some of the documentation refers to creating such a flavor with 64MB, whereas this one has 128MB. I did try the 64MB route  [with `packstack`] and concluded that at least 96MB was needed and the documentation was wrong. I couldn’t log into <> to report this ☹
At this point the launch process fails with the error message: “Build of instance 157bfa1d-7f8c-4a6c-ba3a-b02fb4f4b6a9 aborted: Failed to allocate the network(s), not rescheduling.” In the web ui
Afaict, the vm has enough memory (just: it’s using a bit of swap, but more cache, so it could reclaim that).  I’d expected the instance to launch, and I can well believe that I’ve missed something, but the documentation seems to point all over the place for various logs.
Should this approach work? Is there an alternative that’s better (e.g. use Ubuntu: I’m not keen on apt/dpkg/.deb based distros as I’ve been tripped up in the past over the dependency handling and systemd integration, so I’ve avoided this, but I can see that Canonical is spending money on OS. But so is IBM/Redhat)?  Where can I find info on how to trouble shoot the failing process?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openstack-discuss mailing list