Minor Update: Comparing my KVM vs LXC attempts, my last post mainly applies to running in a KVM Guest. Surprisingly (but maybe not completely based on what I see in the script), the systemd nova services are created in the LXC container attempt. In any case though, that's the only minor upside. Without <really> knowing whether all the nova services are supposed to be running, I went ahead and manually started them all(except vncproxy) in both the KVM Guest and LXC container attempts, and then re-ran the Quickstart Demo Setup. In both cases, they arrived at the same command in the original post and again are still having nova authentication problems, but at least I know that nova is listening on the port that command is connecting to so it really does seem to be an authentication issue and not a networking issue or whether something is listening. BTW - Although I find the organization and comments in the Quickstart Demo Setup really well done, I would strongly recommend including code that tests whether a service/component is functioning properly... Can be a telnet probe, a ping, checking whether a dependency exists, etc. If that code is included in the script, then those tests can be disabled by commenting out (or enabled for testing). Could help immensely in troubleshooting by using standardized tools both the User and the Coder would understand. Tony On Tue, Aug 27, 2013 at 8:41 AM, Tony Su <tonysu@su-networking.com> wrote:
OK, I'm pretty sure I pinned down the problem but don't have a resolution. Should I submit a bugzilla or will simply posting this email be sufficient for proper eyes to work on this to get a resolution?
My most recent steps to test and verify: Re-ran the Quickstart Demo Setup Script in a new LXC container and a new KVM Container Also, re-ran the scripts with <no> pre-installation of OpenStack patterns or packages for dependencies, letting the Quickstart Demo Setup script install everything.
A significant change noticed in the Demo Script (diff from Folsom) Comments about how "net create" has been changed from the Nova setup section to the Quantum section. This is likely the very command that is hanging.
<The actual Problem> Nova is not setup and configured properly and apparently this is required for Quantum to run this command. When I check for running services I find Quantum but nothing related to Nova has started. I found all relevant files in /etc/init.d/openstack-nova-* And I started at least the nova-compute service and configured as a systemd service but that's not sufficient. Do I need to start <all> the openstack-nova* services individually? There is no "master init script" that starts them all? - Or, is there a reason for some to start but not others?
Also, at this point I've only determined that there is a problem with Nova just <starting>, I don't know if Nova requires any configuration beyond the config file I assume would be read when Nova starts.
In any case, I suspect this issue might be because I'm running on openSUSE and not SLES where I <think> systemd has not been implemented so <if> the Quickstart Demo Setup script works on SLES, it sure doesn't on openSUSE.
Hoping for some input on what is needed to get Nova setup and running properly which will hopefully allow the script to complete, Tony
On Mon, Aug 26, 2013 at 4:01 PM, Tony Su <tonysu@su-networking.com> wrote:
Was unexpectedly able to put some more time into this.
Re-ran the "quantum net-create" command manually again, this time with verbosity turned on.
Looks like whatever is supposed to be listening on localhost:5000 isn't. The quantum service is running fine, IP forwarding has been verified enabled in all locations I know for both IPv4 and IPv6 (although I see IPv4 networks are the only ones being configured), the SUSE FW is disabled and all the bridge filters are verified disabled.
My early investigation at this point seems to indicate that the Nova service also is supposed to listen on that port, I don't know specifically what is supposed to be the primary component or service that is supposed to be listening on that port.
Have verified using telnet and a web browser that nothing is listening on that port (localhost:5000).
The command and results follow.
Tony
# quantum -v net-create fixed --shared --provider:network_type flat --provider:physical_network root-bridge DEBUG: quantumclient.quantum.v2_0.network.CreateNetwork get_data(Namespace(admin_state_down=True, columns=[], formatter='table', name='fixed', prefix='', request_format='json', shared=True, tenant_id=None, variables=[])) DEBUG: quantumclient.client REQ: curl -i http://127.0.0.1:5000/v2.0/tokens -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-quantumclient" -d '{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin", "password": "openstack"}}}'
DEBUG: quantumclient.client RESP:{'status': '400', 'content-length': 30, 'content-type': 'text/plain'} [Errno 111] Connection refused
ERROR: quantumclient.shell [Errno 111] Connection refused DEBUG: quantumclient.shell clean_up CreateNetwork DEBUG: quantumclient.shell got an error: [Errno 111] Connection refused
On Sat, Aug 24, 2013 at 3:37 PM, Tony Su <tonysu@su-networking.com> wrote:
Curiously, I'm getting different errors installing different ways... In this message I'll just post the error when installing into a KVM Guest. Later, after trying to install into KVM I'll re-visit the issues I ran into installing into LXC.
If someone has an idea how to address, appreciate the ideas. Otherwise, if someone really has been successful running the quickstart on openSUSE 12.3 on bare metal or any type of VM, I'd appreciate the <exact> steps you might have done to conclusion.
Thx, Tony *****************************************************************************
KVM Guest openSUSE 12.3/XFCE with one processor and 1.6GB RAM and 8GB disk space, fully updated (zypper up)
Normal 12.3/XFCE install and update, then Installed Apache, configured to run as a service and started Installed Mariadb, configured to run as a service and started Installed postgresql-server, configured to run as a service and started
Note: I <did not> create admin/root accounts for use on MariaDB or PostgreSQL, to my knowledge that should not be done.
Listed the OpenStack patterns (with the Grizzly repo installed) zypper se openstack | grep patterns
Then, using zypper installed <all> the patterns and openstack-quickstart without issue.
Then ran openstack-quickstart, it runs just fine until it tries to read the quantum network configuration (btw - isn't it supposed to be called neutrino now?) I can post the entire stdout but the following is the critical part... Starting with line line 306 where quantum is restarted
+ insserv openstack-quantum + /etc/init.d/openstack-quantum restart redirecting to systemctl restart openstack-quantum + . /etc/bash.bashrc.local ++ export HOST_IP=127.0.0.1 ++ HOST_IP=127.0.0.1 ++ . /etc/bash.openstackrc +++ export NOVA_URL=http://127.0.0.1:5000/v2.0/ +++ NOVA_URL=http://127.0.0.1:5000/v2.0/ +++ export NOVA_VERSION=1.1 +++ NOVA_VERSION=1.1 +++ export NOVA_REGION_NAME=RegionOne +++ NOVA_REGION_NAME=RegionOne +++ export NOVA_AUTH_STRATEGY=keystone +++ NOVA_AUTH_STRATEGY=keystone +++ export EC2_URL=http://127.0.0.1:8773/services/Cloud +++ EC2_URL=http://127.0.0.1:8773/services/Cloud +++ export SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0 +++ SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0 ++ setcreds admin openstack ++ export NOVA_PROJECT_ID=admin ++ NOVA_PROJECT_ID=admin ++ '[' -z admin ']' ++ export NOVA_USERNAME=admin ++ NOVA_USERNAME=admin ++ export NOVA_API_KEY=openstack ++ NOVA_API_KEY=openstack ++ '[' -z openstack ']' ++ export EC2_ACCESS_KEY=admin ++ EC2_ACCESS_KEY=admin ++ export EC2_SECRET_KEY=openstack ++ EC2_SECRET_KEY=openstack ++ export OS_AUTH_USER=admin ++ OS_AUTH_USER=admin ++ export OS_USERNAME=admin ++ OS_USERNAME=admin ++ export OS_TENANT_NAME=admin ++ OS_TENANT_NAME=admin ++ export OS_AUTH_KEY=openstack ++ OS_AUTH_KEY=openstack ++ export OS_PASSWORD=openstack ++ OS_PASSWORD=openstack ++ export OS_AUTH_TENANT=admin ++ OS_AUTH_TENANT=admin ++ export OS_AUTH_URL=http://127.0.0.1:5000/v2.0/ ++ OS_AUTH_URL=http://127.0.0.1:5000/v2.0/ ++ export OS_AUTH_STRATEGY=keystone ++ OS_AUTH_STRATEGY=keystone + cnt=0 + : + [[ 0 -gt 6 ]] + quantum net-list {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}} + [[ 1 -eq 0 ]] + cnt=1 + sleep 2 + : + [[ 1 -gt 6 ]] + quantum net-list {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}} + [[ 1 -eq 0 ]] + cnt=2 + sleep 2 + : + [[ 2 -gt 6 ]] + quantum net-list {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}} + [[ 1 -eq 0 ]] + cnt=3 + sleep 2 + : + [[ 3 -gt 6 ]] + quantum net-list {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}} + [[ 1 -eq 0 ]] + cnt=4 + sleep 2 + : + [[ 4 -gt 6 ]] + quantum net-list {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}} + [[ 1 -eq 0 ]] + cnt=5 + sleep 2 + : + [[ 5 -gt 6 ]] + quantum net-list {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}} + [[ 1 -eq 0 ]] + cnt=6 + sleep 2 + : + [[ 6 -gt 6 ]] + quantum net-list {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}} + [[ 1 -eq 0 ]] + cnt=7 + sleep 2 + : + [[ 7 -gt 6 ]] + echo 'Can'\''t reach quantum server. Exiting !!!' Can't reach quantum server. Exiting !!! + exit 1 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org