[PKG-Openstack-devel] first install notes - debconf inconsistencies in neutron-metadata-agent etc

[Thomas Goirand]

On 06/05/2016 04:47 PM, Turbo Fredriksson wrote:
> I'm installing Openstack on one of my new blade servers and noticed
> a small inconsistency in the debconf questions:
> 
>   ┌────┤ Configuring neutron-metadata-agent ├─────┐
>   │                                               │
>   │                                               │
>   │ Auth server password:                         │
>   │                                               │
>   │ ********************_________________________ │
>   │                                               │
>   │                    <Ok>                       │
>   │                                               │
>   └───────────────────────────────────────────────┘
> 
> On all the other packages, it looks like:
> 
>   ┌─────────────────────┤ Configuring heat-common ├─────────────────────┐
>   │ Please specify the password to use with the authentication server.  │
>   │                                                                     │
>   │ Authentication server password:                                     │
>   │                                                                     │
>   │ ********************_______________________________________________ │
>   │                                                                     │
>   │                               <Ok>                                  │
>   │                                                                     │
>   └─────────────────────────────────────────────────────────────────────┘
> 
> I'd use "reportbug", but it doesn't work at the moment (because I'm having
> problems with some packages, including neutron-metadata-agent, not being
> configured properly).

Thanks, this is now fixed. This shouldn't impact the installation
procedure however, it's just text which wasn't updated correctly.

> I'm getting a lot of failed installs/configure. See http://bayour.com/misc/screenlog-openstack_install.txt

Well, you've been selecting SQLite, which is known to fail with some of
the services (in your case, Barbican, Neutron, and Ironic failed because
of that. There's no packaging error in this case. You *must* use MySQL
for them.

> The command line I used (see attachment bladeA01-install_openstack_packages.sh)

This command line is wrong. You're installing things which aren't
related to an OpenStack deployment, like ironic-fa-deploy and such.
You're also installing absolutely all Neutron agent, which isn't what
you ant to do, really...

> on a freshly installed Jessie, with Testing added to the sources.list.d dir:

WHAT?!? You *cannot* mix Jessie and Testing this way. This will lead to
*many* breakage. If you want to use Jessie, then you can add the
repositories described here:

http://mitaka-jessie.pkgs.mirantis.com/

These are unofficial, but not-modified packages (just rebuilt for
Jessie). I'm currently in the process of uploading all to
jessie-backports, which is what you will want to use next.

> PS. I knew that rabbitmq was needed before I even started (see, I DID
>     read documentation! :), so I had to add that manually because I
>     noticed that it wasn't pulled in automatically.
> 
>     I think it would be a good idea (?) to either add RabbitMQ as
>     a Depends, or more appropriate I guess, as a Suggests to all (?)
>     packages.

No, this isn't a good idea.

Also, I wonder what documentation you've been reading. No documentation
suggest to blindly install all of the packages you attempted to install
in this way.

> Because of my use-case (which might be idiotic, but this is the first time
> I even look at Openstack in more detail so bare with me :)

Sure!

>, I'm installing _EVERYTHING_

*BAD* idea to do it this way. You should learn what you need. If you
don't, then you can rely on the openstack-meta-packages and simply do:
apt-get install openstack-proxy-node

for your controler machine, and:
apt-get install openstack-compute-node

There's also a magic "openstack-deploy" package which contains a helper
to install everything at once.

> Just looking at "top" and there's quite a nice load average! Might not be
> the best idea I've had in a while:
> 
>   bladeA01:/usr/src# uptime 
>    15:38:47 up 19:43,  2 users,  load average: 15.67, 15.75, 15.50
> 
> This is a HP G6, dual Intel Xeon Quad Core E5530 @ 2.40GHz (total 16 "cpus"
> according to /proc/cpuinfo - but that might count the threads as well?) and
> 16GB memory (I'm going to siphon the other blade center for more memory)
> running in "Energy Saving Mode" (at the moment, until I get everything working,
> I'm more interested in saving on the heating and electricity bill :).
> 
> The BIOS claims that it's running at 1.6GHz, but I can't verify that in /proc/cpuinfo.
> 
> The load average of almost 16 is the highest sustained load I've ever seen
> though :D. Doesn't seem to matter, everything seems quite responsive.

Well, if things don't work, that's what you get. FYI, for an all-in-one
OpenStack deployment, with no activity in the cloud, you normally get a
load average of 1, not 16, and on my deployment, this is mostly because
of swift replicating itself regularly.

> Unfortunately, since "keystone" is one of the packages that doesn't configure
> correctly, I can't login and look at the brand spanking new and pretty
> Openstack install. So I'd appreciate some pointers on how to get this show
> on the road..

I hope the above will help.

Cheers,

Thomas Goirand (zigo)