Open Stack

Thanks, Michael. Very reassuring. I’ll have a look and comment back.

> On 27 May 2022, at 20:11, Michael Johnson <johnsomor at gmail.com> wrote:
> 
> Hi Tim,
> 
> This should work fine. You will want a localrc/local.conf file to
> configure devstack. I didn't see that mentioned in your steps.
> See this section in the docs:
> https://docs.openstack.org/devstack/latest/#create-a-local-conf
> 
> The only caveat I would mention is the VM instances in Nova will run
> super slow on virtualbox as it lacks the required "nested
> virtualization" support and will run them all in software emulation.
> 
> To find the root cause of the issue in nova, I would look through the
> devstack at n-cpu log file (journal -u devstack at n-cpui) and the
> devstack at n-sch logs.
> 
> Also, you might have a look at one of the nova test localrc file as an example:
> https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_da7/843127/6/check/tempest-integrated-compute-centos-9-stream/da7bebc/controller/logs/local_conf.txt
> 
> Michael
> 
> 
> On Fri, May 27, 2022 at 4:16 AM <tim+openstack.org at coote.org> wrote:
>> 
>> Hullo
>> 
>> 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 `stack.sh` as user `vagrant` (this fails 1/3 of the time as some repo or other resets a connection. `stack.sh` 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 launchpad.net 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?
>> 
>> tia
>> Tim