Package: openstack-deploy Version: 0.15 Severity: minor After running "openstack-deploy all-in-one", I find that I do have something resembling a working openstack installation. Thanks for that!
Unfortunately, however, after all that has happened, one sits there with a "now what" feeling: - The installation asks for a number of things. What do these things mean? (just hitting "enter" to everything *seems* to work, except for the "keystone endpoint IP, for which I just entered 127.0.0.1 in this test environment). - Something is running, but where? (localhost:80, it turns out, with non-SSL HTTP redirected to its SSL version) - After fiddling with apache SSL settings so that those work (this was on a pristine VM to test with), I need to log on. What with? (the value of RC_KEYSTONE_ADMINPASS in /root/osinstallrc, it turns out) I realize that the goal of openstack-deploy is probably to support openstack-tempest-ci rather than to support users; but since it's packaged in Debian, and since it seems to have several modes, all of which should support larger installations too, it seems like a prime candidate for "look at this if you want to build your own cloud" If only it were a bit better documented. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unreleased'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, m68k, arm64 Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openstack-deploy depends on: ii ipcalc 0.41-5 pn openstack-pkg-tools <none> pn python-keystoneclient <none> openstack-deploy recommends no packages. openstack-deploy suggests no packages.
