Revision history [back]

click to hide/show revision 1
initial version

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

and replace "kvm" with "qemu" and had to delete the SATA controller, since I got:

[stack@tripleo ~]$ sudo virsh start instack
error: Failed to start domain instack
error: unsupported configuration: SATA is not supported with this QEMU binary

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

and replace "kvm" with "qemu" in the root tag from <domain type='kvm'> to <domain type='qemu'>
and had to delete the SATA controller, since I got:

got:
 [stack@tripleo ~]$ sudo virsh start instack
 error: Failed to start domain instack
 error: unsupported configuration: SATA is not supported with this QEMU binary

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

and replace "kvm" with "qemu" in the root tag from <domain type='kvm'> to <domain type='qemu'>
and had to delete the SATA controller, since I got:

    [stack@tripleo ~]$ sudo virsh start instack
    error: Failed to start domain instack
    error: unsupported configuration: SATA is not supported with this QEMU binary

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

and get the IP address of the instack VM:

[stack@tripleo ~]$ cat /var/lib/libvirt/dnsmasq/default.leases | grep $(tripleo get-vm-mac instack) | awk '{print $3;}'
192.168.122.165

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

 and replace replaced "kvm" with "qemu" in the root tag from <domain type='kvm'> to <domain type='qemu'>
 and had to delete the SATA controller, controller tag, since I got:

     [stack@tripleo ~]$ sudo virsh start instack
     error: Failed to start domain instack
     error: unsupported configuration: SATA is not supported with this QEMU binary

And changed <target dev='sda' bus='sata'/> to <target dev='vda' bus='ide'/>

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

and get the IP address of the instack VM:

[stack@tripleo ~]$ cat /var/lib/libvirt/dnsmasq/default.leases | grep $(tripleo get-vm-mac instack) | awk '{print $3;}'
192.168.122.165

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

    and replaced "kvm" with "qemu" in the root tag from <domain type='kvm'> to <domain type='qemu'>
    and had to delete the SATA controller tag, since I got:

        [stack@tripleo ~]$ sudo virsh start instack
        error: Failed to start domain instack
        error: unsupported configuration: SATA is not supported with this QEMU binary

And changed <target dev='sda' bus='sata'/> to <target dev='vda' bus='ide'/>

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

and get the IP address of the instack undercloud VM:

[stack@tripleo ~]$ cat /var/lib/libvirt/dnsmasq/default.leases | grep $(tripleo get-vm-mac instack) | awk '{print $3;}'
192.168.122.165

and finally cloud proceed to the next step to deploy the undercloud described here:

http://openstack.redhat.com/Deploying_an_RDO_Undercloud_with_Instack

and got to Step 5 running as my stack user:

[stack@instack ~] instack-install-undercloud-packages

in the hope that could get "install-undercloud Complete!" as described on that page, the installation took near to 2 hours :-) and I can see that all OpenStack Services are running in my instack VM, but the installation aborted I guess by the last step by installing tuskar:

    2014-05-04 07:38:34.124 29752 INFO sqlalchemy.engine.base.Engine [-] SELECT migrate_version.repository_id, migrate_version.repository_path, migrate_version.version 
FROM migrate_version 
WHERE migrate_version.repository_id = ?
2014-05-04 07:38:34.142 29752 INFO sqlalchemy.engine.base.Engine [-] ('tuskar',)
+ service openstack-tuskar-api restart
Redirecting to /bin/systemctl restart  openstack-tuskar-api.service
+ sleep 5
+ tuskar overcloud-role-create controller --description 'Controller Node' --image-name overcloud-control
ERROR:tuskarclient.shell:Exiting due to an error:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 224, in main
    TuskarShell(sys.argv[1:]).run()
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 71, in run
    args.func(tuskar_client, args)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles_shell.py", line 45, in do_overcloud_role_create
    overcloud_role = tuskar.overcloud_roles.create(**overcloud_role_dict)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles.py", line 70, in create
    return self._create(self._path(), fields)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/base.py", line 78, in _create
    resp, body = self.api.json_request('POST', url, body=body)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 196, in json_request
    resp, body_iter = self._http_request(url, method, **kwargs)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 158, in _http_request
    'endpoint': self.endpoint, 'e': e})
CommunicationError: Error communicating with http://localhost:8585/ [Errno 111] Connection refused
[2014-05-04 07:39:31,342] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/post-configure.d']' returned non-zero exit status 1]

[2014-05-04 07:39:31,799] (os-refresh-config) [ERROR] Aborting...

And here was the installation aborted, but I as I mentioned all services where running.

So decided to proceed to the next step preparing the overcloud (adjusted the authorized_keys, so that the stack user has passwordless access to the VM host):

[stack@instack ~] instack-prepare-for-overcloud

and got finally:

[stack@instack ~]$ source stackrc 
[stack@instack ~]$ source tripleo-undercloud-passwords 
[stack@instack ~]$ instack-prepare-for-overcloud
+ IMG_SOURCE_URL=http://repos.fedorapeople.org/repos/openstack-m/tripleo-images-rdo-icehouse
+ OS_AUTH_URL=http://localhost:5000/v2.0
+ '[' -z http://localhost:5000/v2.0 ']'
+ '[' '!' -f /home/stack/.ssh/id_rsa ']'
+ nova keypair-show default
ERROR: HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno 111] Connection refused)
+ tripleo user-config
ERROR: HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno 111] Connection refused)

So, all in all I think the whole thing might run on a bare metal, but if someone would like to reproduce my bugs or point me what I'm doing wrong, I'd be thankful to know about it.

Thanks, -Arash

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

    and replaced "kvm" with "qemu" in the root tag from <domain type='kvm'> to <domain type='qemu'>
    and had to delete the SATA controller tag, since I got:

        [stack@tripleo ~]$ sudo virsh start instack
        error: Failed to start domain instack
        error: unsupported configuration: SATA is not supported with this QEMU binary

And changed <target dev='sda' bus='sata'/> to <target dev='vda' bus='ide'/>

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

and get the IP address of the undercloud VM:

[stack@tripleo ~]$ cat /var/lib/libvirt/dnsmasq/default.leases | grep $(tripleo get-vm-mac instack) | awk '{print $3;}'
192.168.122.165

and finally cloud proceed to the next step to deploy the undercloud described here:

http://openstack.redhat.com/Deploying_an_RDO_Undercloud_with_Instack

and got to Step 5 running as my stack user:

[stack@instack ~] instack-install-undercloud-packages

in the hope that could get "install-undercloud Complete!" as described on that page, the installation took near to 2 hours :-) and I can see that all OpenStack Services are running in my instack VM, but the installation aborted I guess by the last step by installing tuskar:

    2014-05-04 07:38:34.124 29752 INFO sqlalchemy.engine.base.Engine [-] SELECT migrate_version.repository_id, migrate_version.repository_path, migrate_version.version 
FROM migrate_version 
WHERE migrate_version.repository_id = ?
2014-05-04 07:38:34.142 29752 INFO sqlalchemy.engine.base.Engine [-] ('tuskar',)
+ service openstack-tuskar-api restart
Redirecting to /bin/systemctl restart  openstack-tuskar-api.service
+ sleep 5
+ tuskar overcloud-role-create controller --description 'Controller Node' --image-name overcloud-control
ERROR:tuskarclient.shell:Exiting due to an error:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 224, in main
    TuskarShell(sys.argv[1:]).run()
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 71, in run
    args.func(tuskar_client, args)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles_shell.py", line 45, in do_overcloud_role_create
    overcloud_role = tuskar.overcloud_roles.create(**overcloud_role_dict)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles.py", line 70, in create
    return self._create(self._path(), fields)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/base.py", line 78, in _create
    resp, body = self.api.json_request('POST', url, body=body)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 196, in json_request
    resp, body_iter = self._http_request(url, method, **kwargs)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 158, in _http_request
    'endpoint': self.endpoint, 'e': e})
CommunicationError: Error communicating with http://localhost:8585/ [Errno 111] Connection refused
[2014-05-04 07:39:31,342] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/post-configure.d']' returned non-zero exit status 1]

[2014-05-04 07:39:31,799] (os-refresh-config) [ERROR] Aborting...

And here was the installation aborted, but I as I mentioned all services where running.

So decided to proceed to the next step preparing the overcloud (adjusted the authorized_keys, so that the stack user has passwordless access to the VM host):

[stack@instack ~] instack-prepare-for-overcloud

and got finally:

[stack@instack ~]$ source stackrc 
[stack@instack ~]$ source tripleo-undercloud-passwords 
[stack@instack ~]$ instack-prepare-for-overcloud
+ IMG_SOURCE_URL=http://repos.fedorapeople.org/repos/openstack-m/tripleo-images-rdo-icehouse
+ OS_AUTH_URL=http://localhost:5000/v2.0
+ '[' -z http://localhost:5000/v2.0 ']'
+ '[' '!' -f /home/stack/.ssh/id_rsa ']'
+ nova keypair-show default
ERROR: HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno 111] Connection refused)
+ tripleo user-config
ERROR: HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno 111] Connection refused)

So, all in all I think the whole thing might run on a bare metal, but if someone would like to reproduce my bugs or point me what I'm doing wrong, I'd be thankful to know about it.

Thanks, -Arash

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

    and replaced "kvm" with "qemu" in the root tag from <domain type='kvm'> to <domain type='qemu'>
    and had to delete the SATA controller tag, since I got:

        [stack@tripleo ~]$ sudo virsh start instack
        error: Failed to start domain instack
        error: unsupported configuration: SATA is not supported with this QEMU binary

And changed <target dev='sda' bus='sata'/> to <target dev='vda' bus='ide'/>

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

and get the IP address of the undercloud VM:

[stack@tripleo ~]$ cat /var/lib/libvirt/dnsmasq/default.leases | grep $(tripleo get-vm-mac instack) | awk '{print $3;}'
192.168.122.165

and finally cloud proceed to the next step to deploy the undercloud described here:

http://openstack.redhat.com/Deploying_an_RDO_Undercloud_with_Instack

and got to Step 5 running as my stack user:user on the instack VM (I renamed it from localhost to instack and here was my failure (read on what happens):

[stack@instack ~] instack-install-undercloud-packages

in the hope and hoped that could I could get "install-undercloud Complete!" at the End as described on that page, the installation took near to 2 hours :-) and I can see that all OpenStack Services are running in my instack VM, but the installation aborted I guess by the last step by installing tuskar:

    2014-05-04 07:38:34.124 29752 INFO sqlalchemy.engine.base.Engine [-] SELECT migrate_version.repository_id, migrate_version.repository_path, migrate_version.version 
FROM migrate_version 
WHERE migrate_version.repository_id = ?
2014-05-04 07:38:34.142 29752 INFO sqlalchemy.engine.base.Engine [-] ('tuskar',)
+ service openstack-tuskar-api restart
Redirecting to /bin/systemctl restart  openstack-tuskar-api.service
+ sleep 5
+ tuskar overcloud-role-create controller --description 'Controller Node' --image-name overcloud-control
ERROR:tuskarclient.shell:Exiting due to an error:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 224, in main
    TuskarShell(sys.argv[1:]).run()
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 71, in run
    args.func(tuskar_client, args)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles_shell.py", line 45, in do_overcloud_role_create
    overcloud_role = tuskar.overcloud_roles.create(**overcloud_role_dict)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles.py", line 70, in create
    return self._create(self._path(), fields)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/base.py", line 78, in _create
    resp, body = self.api.json_request('POST', url, body=body)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 196, in json_request
    resp, body_iter = self._http_request(url, method, **kwargs)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 158, in _http_request
    'endpoint': self.endpoint, 'e': e})
CommunicationError: Error communicating with http://localhost:8585/ [Errno 111] Connection refused
[2014-05-04 07:39:31,342] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/post-configure.d']' returned non-zero exit status 1]

[2014-05-04 07:39:31,799] (os-refresh-config) [ERROR] Aborting...

And here was the installation aborted, but as I mentioned all services where running.

So decided to proceed to the next step preparing the overcloud (adjusted the authorized_keys, so that the stack user has passwordless access to the VM host):

[stack@instack ~] instack-prepare-for-overcloud

and got finally:

[stack@instack ~]$ source stackrc 
[stack@instack ~]$ source tripleo-undercloud-passwords 
[stack@instack ~]$ instack-prepare-for-overcloud
+ IMG_SOURCE_URL=http://repos.fedorapeople.org/repos/openstack-m/tripleo-images-rdo-icehouse
+ OS_AUTH_URL=http://localhost:5000/v2.0
+ '[' -z http://localhost:5000/v2.0 ']'
+ '[' '!' -f /home/stack/.ssh/id_rsa ']'
+ nova keypair-show default
ERROR: HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno 111] Connection refused)
+ tripleo user-config
ERROR: HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno 111] Connection refused)

So, conecction refused to local host, oh no, I renamed the instack VM to instack (it was localhost before), so set hostname to localhost and re-ran "instack-prepare-for-overcloud"

[stack@localhost ~] instack-prepare-for-overcloud

and now I can see that the images are been downloaded and hope to get the rest working, stay tuned :-)

So, all in all, RDO Instack is a great work and thanks to all I think the whole thing might run on a bare metal, but if someone would like to reproduce my bugs or point me what I'm doing wrong, I'd be thankful to know about it.

Thanks, -Arash

awesome developers who made this available.

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

    and replaced "kvm" with "qemu" in the root tag from <domain type='kvm'> to <domain type='qemu'>
    and had to delete the SATA controller tag, since I got:

        [stack@tripleo ~]$ sudo virsh start instack
        error: Failed to start domain instack
        error: unsupported configuration: SATA is not supported with this QEMU binary

And changed <target dev='sda' bus='sata'/> to <target dev='vda' bus='ide'/>

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

and get the IP address of the undercloud VM:

[stack@tripleo ~]$ cat /var/lib/libvirt/dnsmasq/default.leases | grep $(tripleo get-vm-mac instack) | awk '{print $3;}'
192.168.122.165

and finally cloud proceed to the next step to deploy the undercloud described here:

http://openstack.redhat.com/Deploying_an_RDO_Undercloud_with_Instack

and got to Step 5 running as my stack user on the instack VM (I renamed it from localhost to instack and here was my failure (read on what happens):

[stack@instack ~] instack-install-undercloud-packages

and hoped that could I could I'd get "install-undercloud Complete!" at the End as described on that page, the installation took near to 2 hours :-) and I can see that all OpenStack Services are running in my instack VM, but the installation aborted at the End, I guess by the last step by installing tuskar:

    2014-05-04 07:38:34.124 29752 INFO sqlalchemy.engine.base.Engine [-] SELECT migrate_version.repository_id, migrate_version.repository_path, migrate_version.version 
FROM migrate_version 
WHERE migrate_version.repository_id = ?
2014-05-04 07:38:34.142 29752 INFO sqlalchemy.engine.base.Engine [-] ('tuskar',)
+ service openstack-tuskar-api restart
Redirecting to /bin/systemctl restart  openstack-tuskar-api.service
+ sleep 5
+ tuskar overcloud-role-create controller --description 'Controller Node' --image-name overcloud-control
ERROR:tuskarclient.shell:Exiting due to an error:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 224, in main
    TuskarShell(sys.argv[1:]).run()
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 71, in run
    args.func(tuskar_client, args)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles_shell.py", line 45, in do_overcloud_role_create
    overcloud_role = tuskar.overcloud_roles.create(**overcloud_role_dict)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles.py", line 70, in create
    return self._create(self._path(), fields)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/base.py", line 78, in _create
    resp, body = self.api.json_request('POST', url, body=body)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 196, in json_request
    resp, body_iter = self._http_request(url, method, **kwargs)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 158, in _http_request
    'endpoint': self.endpoint, 'e': e})
CommunicationError: Error communicating with http://localhost:8585/ [Errno 111] Connection refused
[2014-05-04 07:39:31,342] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/post-configure.d']' returned non-zero exit status 1]

[2014-05-04 07:39:31,799] (os-refresh-config) [ERROR] Aborting...

And here was the installation aborted, but as I mentioned all services where running.

So decided to proceed to the next step preparing the overcloud (adjusted the authorized_keys, so that the stack user has passwordless access to the VM host):

and got finally:

[stack@instack ~]$ source stackrc 
[stack@instack ~]$ source tripleo-undercloud-passwords 
[stack@instack ~]$ instack-prepare-for-overcloud
+ IMG_SOURCE_URL=http://repos.fedorapeople.org/repos/openstack-m/tripleo-images-rdo-icehouse
+ OS_AUTH_URL=http://localhost:5000/v2.0
+ '[' -z http://localhost:5000/v2.0 ']'
+ '[' '!' -f /home/stack/.ssh/id_rsa ']'
+ nova keypair-show default
ERROR: HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno 111] Connection refused)
+ tripleo user-config
ERROR: HTTPConnectionPool(host='localhost', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by <class 'socket.error'>: [Errno 111] Connection refused)

So, conecction refused to local host, oh no, I renamed the instack VM to instack (it was localhost before), so set hostname to localhost and re-ran "instack-prepare-for-overcloud"

[stack@localhost ~] instack-prepare-for-overcloud

and now I can see that the images are been downloaded and hope to get the rest working, stay tuned :-)

So, all in all, RDO Instack is a great work and thanks to all awesome developers who made this available.