Thursday, January 29, 2015

ICO all-in-one deployment doesn't install Workload Deployer

The ICO 2.4 and 2.4.0.1 Deployment Server installers are definitely great pieces of software. They check prerequisites correctly and install without a hitch. They are really, really nice.

This post is about one of the options in the 'ds wizard' script options. Specifically, when you take the path:

[0] New IBM Cloud Orchestrator deployment.
[0] Demo
[1] All In One
[2] All In One IBM Cloud Orchestrator Deployment
   - Deploys IBM Cloud Orchestrator all-in-one in one machine.


This path actually deploys the template sco-devstack (/opt/ico_install/topology_templates/sco_devstack.json), which does NOT install the IBM Workload Deployer component. The effect that this has is that you do NOT have a PATTERNS option in the Administrator GUI (https://machine.fqdn:8443/), and so you can't create, view or use any patterns.

So if you want an all-in-one deployment, you should take a different option. Specifically, the path you should take through the wizard is:

[0] New IBM Cloud Orchestrator deployment.
[0] Demo
[1] All In One
[2] All In One IBM Cloud Orchestrator Deployment 
[0] All In One with addtional KVM compute node
   - Deploys IBM Cloud Orchestrator all-in-one KVM topology with an additional KVM compute node where components use a shared 
   - internal database.

And when it asks you for the FQDNs of the three servers, specify the FQDN of the ONE server that you'll be using in each of those three places.

9 comments:

bEJLEU said...

Hi, like you blog. did you manage to install ICO 2.4 - all in one in VMWare? Thanks in advance. any hints would be greatly appreciated

Frank Tate said...

I haven't tried it on VMWare, but where are you having issues - I might know the solution or I can ask one of my guys.

Mario Somma said...

Hi Frank,

I'm wondering if it is supported to have ICO2.4 FP1 deployment where both the Managed From and the Managed To are on the same ESX..

Thanks a lot in advance..have a nice day..Ciao..Mario.

Frank Tate said...

Yes, Mario, that is an option. Make sure to read all of the Installation Planning documentation to make sure you understand exactly which pieces need to be installed where.

ഏകാന്തപഥികന്‍ said...

HI, did u face this error anytime? I am trying to install ICO 2.4. Managed to install deployement service, but ds wizard for all in one kvm fails with below erros.
[root@PICLOUDCC21 ds]# ds job-show e58fdf45-d6d2-41fe-bbc6-d2dc7b722901
+-------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+-------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| created_at | 2015-04-09T13:49:57.401887 |
| deleted_at | None |
| fault | { |
| | "message": "Failed to execute task from running:chef : run chef client on node", |
| | "exception": [ |
| | "Traceback (most recent call last):\n", |
| | " File \"/usr/lib/python2.6/site-packages/ds/engine/deploy/task_runner.py\", line 70, in execute\n res = task.execute(self.context, logger)\n", |
| | " File \"/usr/lib/python2.6/site-packages/ds/engine/deploy/common/chef_runner.py\", line 107, in execute\n self.execute_chef(cmd, srv_name, context, logger)\n", |
| | " File \"/usr/lib/python2.6/site-packages/ds/engine/deploy/common/chef_runner.py\", line 159, in execute_chef\n unsuccessfully\")\n", |
| | "DeployTaskFailed: Failed to execute deployment task: running:chef, error message: bootstrap exit unsuccessfully\n" |
| | ] |
| | } |

ഏകാന്തപഥികന്‍ said...

Hi ,

Did u faced the below errors anytime when u were installing ICO 2.4??

I was trying to install ICO 2.4 on my test machiens and managed to install deployment service without any erros. But getting below errors while creating demo orchastrator (all-in-one kvm) using ds wizard.

[root@PICLOUDCC21 ds]# ds job-show e58fdf45-d6d2-41fe-bbc6-d2dc7b722901
+-------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+-------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| created_at | 2015-04-09T13:49:57.401887 |
| deleted_at | None |
| fault | { |
| | "message": "Failed to execute task from running:chef : run chef client on node", |
| | "exception": [ |
| | "Traceback (most recent call last):\n", |
| | " File \"/usr/lib/python2.6/site-packages/ds/engine/deploy/task_runner.py\", line 70, in execute\n res = task.execute(self.context, logger)\n", |
| | " File \"/usr/lib/python2.6/site-packages/ds/engine/deploy/common/chef_runner.py\", line 107, in execute\n self.execute_chef(cmd, srv_name, context, logger)\n", |
| | " File \"/usr/lib/python2.6/site-packages/ds/engine/deploy/common/chef_runner.py\", line 159, in execute_chef\n unsuccessfully\")\n", |
| | "DeployTaskFailed: Failed to execute deployment task: running:chef, error message: bootstrap exit unsuccessfully\n" |
| | ] |
| | } |

ഏകാന്തപഥികന്‍ said...

ds wizard errors --->
==> ds-engine.log <==
2015-04-09 21:55:45.258 2245 ERROR heat.openstack.common.rpc.impl_qpid [-] HT-55EF133 Failed to consume message from queue: connection aborted
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid Traceback (most recent call last):
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid File "/usr/lib/python2.6/site-packages/heat/openstack/common/rpc/impl_qpid.py", line 541, in ensure
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid return method(*args, **kwargs)
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid File "/usr/lib/python2.6/site-packages/heat/openstack/common/rpc/impl_qpid.py", line 598, in _consume
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid nxt_receiver = self.session.next_receiver(timeout=timeout)
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid File "", line 6, in next_receiver
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line 676, in next_receiver
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid if self._ecwait(lambda: self.incoming, timeout):
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line 51, in _ecwait
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid result = self._ewait(lambda: self.closed or predicate(), timeout)
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line 581, in _ewait
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid result = self.connection._ewait(lambda: self.error or predicate(), timeout)
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line 220, in _ewait
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid self.check_error()
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line 213, in check_error
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid raise e
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid ConnectionError: connection aborted
2015-04-09 21:55:45.258 2245 TRACE heat.openstack.common.rpc.impl_qpid

==> ds-api.log <==
2015-04-09 21:55:45.263 2233 ERROR heat.openstack.common.rpc.impl_qpid [-] HT-6A9F94C Unable to connect to AMQP server: connection aborted. Sleeping 1 seconds

==> ds-engine.log <==
2015-04-09 21:55:45.264 2245 ERROR heat.openstack.common.rpc.impl_qpid [-] HT-6A9F94C Unable to connect to AMQP server: connection aborted. Sleeping 1 seconds
2015-04-09 21:55:45.264 2245 ERROR heat.openstack.common.rpc.impl_qpid [-] HT-6A9F94C Unable to connect to AMQP server: connection aborted. Sleeping 1 seconds

==> ds-api.log <==
2015-04-09 21:55:46.270 2233 ERROR heat.openstack.common.rpc.impl_qpid [-] HT-6A9F94C Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Sleeping 2 seconds

==> ds-engine.log <==
2015-04-09 21:55:46.276 2245 ERROR heat.openstack.common.rpc.impl_qpid [-] HT-6A9F94C Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Sleeping 2 seconds
2015-04-09 21:55:46.277 2245 ERROR heat.openstack.common.rpc.impl_qpid [-] HT-6A9F94C Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Sleeping 2 seconds

ഏകാന്തപഥികന്‍ said...


==> ds-engine-e58fdf45-d6d2-41fe-bbc6-d2dc7b722901.log <==
[2015-04-09 21:55:46,470] PICLOUDCC21.lab.com * service[qpidd] action restart

[2015-04-09 21:55:46,470] PICLOUDCC21.lab.com - restart service service[qpidd]

[2015-04-09 21:55:46,470] PICLOUDCC21.lab.com

[2015-04-09 21:55:46,470] PICLOUDCC21.lab.com Recipe: service-ip::db2_service_ip
[2015-04-09 21:55:46,501] PICLOUDCC21.lab.com * script[configure ip PICLOUDCC21.lab.com/255.255.255.0 on eth0] action run

[2015-04-09 21:55:46,501] PICLOUDCC21.lab.com - execute configure ip PICLOUDCC21.lab.com/255.255.255.0 on eth0

[2015-04-09 21:55:46,501] PICLOUDCC21.lab.com

[2015-04-09 21:55:46,502] PICLOUDCC21.lab.com Recipe: openstack-telemetry::identity_registration

[2015-04-09 21:55:46,778] PICLOUDCC21.lab.com * openstack-identity_register[Register Service Tenant] action create_tenant[2015-04-09T21:55:46+08:00] ERROR: Unable to create tenant 'service'
[2015-04-09 21:55:46,779] PICLOUDCC21.lab.com [2015-04-09T21:55:46+08:00] ERROR: Error was: Could not lookup uuid for tenant:name=>service. Error was KS-117430E An unexpected error prevented the server from fulfilling your request. (OperationalError) ibm_db_dbi::OperationalError: [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001 SQLCODE=-30082 None None (HTTP 500)

[2015-04-09 21:55:46,779] PICLOUDCC21.lab.com (1)

[2015-04-09 21:55:46,779] PICLOUDCC21.lab.com (up to date)

[2015-04-09 21:55:47,031] PICLOUDCC21.lab.com * openstack-identity_register[Register Service User] action create_user[2015-04-09T21:55:47+08:00] ERROR: Unable to create user 'ceilometer' for tenant 'service'

[2015-04-09 21:55:47,032] PICLOUDCC21.lab.com [2015-04-09T21:55:47+08:00] ERROR: Error was: Could not lookup uuid for tenant:name=>service. Error was KS-117430E An unexpected error prevented the server from fulfilling your request. (OperationalError) ibm_db_dbi::OperationalError: [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001 SQLCODE=-30082 None None (HTTP 500)

[2015-04-09 21:55:47,032] PICLOUDCC21.lab.com (1)

Mario Somma said...

Hi Frank, Thx a lot for your comments and reply.. Ciao..Mario.