[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: oo-install for Origin version 3



Hi Harrison

 

Great news..Thanks a lot.

I re tried the deployment with the new changes—Lot of things got resolved. here are some of issue I am facing

 

On Broker -

1.mco ping not working – this is strange and something really amiss.

 

[root ip-10-91-136-141 ec2-user]# mco ping

bash: mco: command not found

 

2.I had to manually start service httpd restart

 

3.oo-accept-broker is giving one failure which is a little strange

 

INFO: Datastore Host:  MOPED: Could not resolve IP address for broker.cloudshift.com:27017

INFO: Datastore Port:  MOPED: Could not resolve IP address for broker.cloudshift.com:27017

INFO: Datastore User:  MOPED: Could not resolve IP address for broker.cloudshift.com:27017

INFO: Datastore SSL:  MOPED: Could not resolve IP address for broker.cloudshift.com:27017

INFO: Datastore Password has been set to non-default

INFO: Datastore DB Name:  MOPED: Could not resolve IP address for broker.cloudshift.com:27017

INFO: Datastore: mongo db service is remote

INFO: checking mongo db login access

exception: connect failed

FAIL: error logging into mongo db:  MOPED: Could not resolve IP address for broker.cloudshift.com:27017: MOPED: Could not resolve IP address for broker.cloudshift.com:27017/MOPED: --username Could, exit code: 1

INFO: checking services

INFO: checking cloud user authentication

INFO: auth plugin = MOPED: Could not resolve IP address for broker.cloudshift.com:27017

NOTICE: unknown auth class: MOPED: Could not resolve IP address for broker.cloudshift.com:27017

INFO: checking dynamic dns plugin

NOTICE: unknown dns class: MOPED: Could not resolve IP address for broker.cloudshift.com:27017

INFO: checking messaging configuration

NOTICE: unknown messaging class: MOPED: Could not resolve IP address for broker.cloudshift.com:27017

1 ERRORS

 

On Node : I manually changed the BROKER_HOST to elastic ip in /etc/openshift/node and following are the error I get wen I run oo-accept-node –v

But these errors are not that showstoppers and from what I understand can be ignored

 

FAIL: kernel.sem semaphores too low: 128 < 512

INFO: checking cgroups configuration

INFO: checking cgroups processes

INFO: find district uuid: NONE

INFO: determining node uid range: 1000 to 6500

INFO: checking presence of tc qdisc

INFO: checking for cgroup filter

INFO: checking presence of tc classes

INFO: checking filesystem quotas

INFO: checking quota db file selinux label

INFO: checking 0 user accounts

INFO: checking application dirs

INFO: checking system httpd configs

INFO: checking cartridge repository

FAIL: no manifest in the cart repo matches /usr/libexec/openshift/cartridges/php/metadata/manifest.yml

FAIL: no manifest in the cart repo matches /usr/libexec/openshift/cartridges/jenkins-client/metadata/manifest.yml

FAIL: no manifest in the cart repo matches /usr/libexec/openshift/cartridges/perl/metadata/manifest.yml

4 ERRORS

 

From the browser,I am able to login,but unable to create application- An error occurred screen appears.

 

-----Original Message-----
From: N. Harrison Ripps [mailto:hripps redhat com]
Sent: Wednesday, January 15, 2014 10:59 PM
To: Madathilthattantav, S.
Cc: dev lists openshift redhat com; users lists openshift redhat com; Krishna Raman
Subject: Re: oo-install for Origin version 3

 

Hey Shabna--

 

On Jan 15, 2014, at 11:42 , <s madathilthattantav accenture com> <s madathilthattantav accenture com> wrote:

 

> Hi Harrison

>

> Thanks a lot.Let me know if there would be any changes for this- since

> the timelines would have an impact on the current task I am working on.

 

The optional named_ip_address override is in place now. If you rerun oo-install from install.openshift.com, you will see that if you opt to edit your current broker config, you will have the opportunity to set a value for the BIND DNS IP addr that is distinct from the broker's primary IP addr.

 

I am still following up re: setting broker & activemq host info for the node.

 

>

> Shabna

>

> -----Original Message-----

> From: N. Harrison Ripps [mailto:hripps redhat com]

> Sent: Wednesday, January 15, 2014 7:15 PM

> To: Madathilthattantav, S.

> Cc: dev lists openshift redhat com; users lists openshift redhat com;

> Krishna Raman

> Subject: Re: oo-install for Origin version 3

> Importance: High

>

> Hey Shabna--

>

> On Jan 15, 2014, at 4:11 , s madathilthattantav accenture com wrote:

>

>> Hi Harrison

>>

>> I am facing some challenges  with the oo-install uitility while

>> trying to install OpenShiftOrigin version 3 in AWS

>>

>> Issue 1 :Broker Configuration

>>

>> In cased of of aws , broker_ip_addr  √†will be the elastic ip of the

>> instance and named_ip_adrr  -√† should be the eth0 IP address of the

>> broker host

>>

>> But the script is not giving me an option to configure it as different. Looks like the oo-install is assuming and  populating both broker_ip_addr and

>> named_ip_adrr   as the same .

>> This does not work in case of aws,I tried some trails with different config in the scripts but no success - Any work around /manual changes suggested ?

>>

>>

>> Th script config looks like this  -

>>

>> Host Information

>> +----------------+-----------------------+

>> | Host           | broker.cloudshift.com |

>> | Roles          | Broker                |

>> | SSH Host       | localhost             |

>> | User           | root                  |

>> | IP Addr        | 54.221.250.159        |

>> | IP Interface   | eth0                  |

>> | Install Status | new                   |

>> +----------------+-----------------------+

>> +----------------+----------------------+

>> | Host           | node1.cloudshift.com |

>> | Roles          | Node                 |

>> | SSH Host       | 54.204.45.129        |

>> | User           | root                 |

>> | IP Addr        | 54.204.45.129        |

>> | IP Interface   | eth0                 |

>> | Install Status | new                  |

>> +----------------+----------------------+

>>

>> oo_install_configure_broker.cloudshift.com.pp

>>

>> [root ip-10-45-186-170 tmp]# cat

>> oo_install_configure_broker.cloudshift.com.pp

>> class { 'openshift_origin' :

>>  bind_key =>

>> 'rXZhU3SnlJmee+IT0muuZUrlW8QoxiglLJf5iquolicyIVcHJ52PwWvliVFl7y5n7bzE

>> Cd6n6JjeCQO4gDKtUg==',

>>  install_method => 'yum',

>>  named_ip_addr => '54.221.250.159',

>>  datastore_hostname => 'broker.cloudshift.com',  roles =>

>> ['activemq','datastore','broker','named'],

>>  repos_base =>

>> 'http://mirror.openshift.com/pub/origin-server/release/3/rhel-6',

>>  broker_hostname => 'broker.cloudshift.com',  activemq_hostname =>

>> 'broker.cloudshift.com',  named_hostname => 'broker.cloudshift.com', 

>> broker_ip_addr => '54.221.250.159',  jenkins_repo_base =>

>> 'http://pkg.jenkins-ci.org/redhat',

>>  domain => 'cloudshift.com',

>> }

>

> Great point. Previously we hadn't hit any cases where "pinning" the named_ip_addr to the broker_ip_addr was a problem. However, if this is going to come up in every AWS deployment, I will modify oo-install to give the user optional control over that value.

>

>> Issue 2 :Node  Configuration -

>> Do the script provide an option to configure  the following param as

>> ip adresses.For some reason from my previous experience I had to make these as ip address Instead of hostname to get it working for Node in aws.

>>

>> [root ip-10-45-186-170 tmp]# cat

>> oo_install_configure_node1.cloudshift.com.pp

>> class { 'openshift_origin' :

>>  node_ip_addr => '54.204.45.129',

>>  bind_key =>

>> 'rXZhU3SnlJmee+IT0muuZUrlW8QoxiglLJf5iquolicyIVcHJ52PwWvliVFl7y5n7bzE

>> Cd6n6JjeCQO4gDKtUg==',

>>  install_method => 'yum',

>>  named_ip_addr => '54.221.250.159',

>>  datastore_hostname => 'broker.cloudshift.com',  roles => ['node'], 

>> repos_base =>

>> 'http://mirror.openshift.com/pub/origin-server/release/3/rhel-6',

>>  broker_hostname => 'broker.cloudshift.com',  activemq_hostname =>

>> 'broker.cloudshift.com',

>

> oo-install doesn't provide that option right now. Part of the issue is that broker_hostname is used to set the FQDN of the broker host, which could be a problem. Krishna, any thoughts on this one?

>

>>  conf_node_external_eth_dev => 'eth0',  node_hostname =>

>> 'node1.cloudshift.com',  named_hostname => 'broker.cloudshift.com', 

>> broker_ip_addr => '54.221.250.159',  jenkins_repo_base =>

>> 'http://pkg.jenkins-ci.org/redhat',

>>  domain => 'cloudshift.com',

>> }

>>

>> I have attached a sample config that worked using puppet.Any pointers/thought will be appreciated.

>

> I'll put up a change in oo-install for the first issue and follow up with Krishna about the second. Thanks for the great feedback; we really appreciate it!

>

> --Harrison

>

>>

>> Thanks

>> Shabna

>>

>>

>> From: Harrison Ripps [mailto:hripps redhat com]

>> Sent: Tuesday, January 14, 2014 6:50 PM

>> To: Madathilthattantav, S.

>> Cc: dev lists openshift redhat com; users lists openshift redhat com

>> Subject: Re: oo-install for Origin version 3

>>

>> Hi Shabna--

>> We've tested the Origin-3-on-RHEL scenario an it does work. Check the oo-install guide on openshift.github.io for some prerequisites (like Puppet) that you will need to set up on your target host(s). Let me know if you run into any problems.

>>

>> Cheers,

>> Harrison

>>

>> On Jan 14, 2014, at 6:36, <s madathilthattantav accenture com> wrote:

>>

>> Hi All

>>

>> Has anyone tried out Origin v3 install using oo-install utility in

>> AWS

>> ?(RHEL)

>>

>> Thanks

>> Shabna

>>

>>

>> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. .

>> _____________________________________________________________________

>> _

>> ________________

>>

>> www.accenture.com

>> _______________________________________________

>> users mailing list

>> users lists openshift redhat com

>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users

>> <Puppetconfig.docx>

>

>

>

 

 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]