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

Re: oo-install for Origin version 3



On 16/01/14 17:07 +0000, s madathilthattantav accenture com wrote:
The error remains though

[root ip-10-91-136-141 conf.d]# oo-mco ping
connect to broker.cloudshift.com failed: Connection refused - connect(2) will retry(#0) in 5
connect to broker.cloudshift.com failed: Connection refused - connect(2) will retry(#1) in 5
^C
The ping application failed to run, use -v for full error details: Could not connect to Stomp Server:

Make sure that activemq is running, verify the plugin.activemq.pool.1.host
in /opt/rh/ruby193/root/etc/mcollective/client.cfg is pointing to the
right dns name, and that the dns name properly resolves from the host
you are running oo-mco from.
--
Jason


Shabna

-----Original Message-----
From: Madathilthattantav, S.
Sent: Thursday, January 16, 2014 10:34 PM
To: 'Jason DeTiberus'; 'N. Harrison Ripps'
Cc: 'users lists openshift redhat com'; 'Krishna Raman'; 'dev lists openshift redhat com'
Subject: RE: oo-install for Origin version 3

Please ignore-- my bad !!that was typo in config file

-----Original Message-----
From: Madathilthattantav, S.
Sent: Thursday, January 16, 2014 10:32 PM
To: 'Jason DeTiberus'; N. Harrison Ripps
Cc: users lists openshift redhat com; Krishna Raman; dev lists openshift redhat com
Subject: RE: oo-install for Origin version 3

Hi Jason

Thanks a lot for the pointers -I am using RHEL

[root ip-10-91-136-141 conf.d]# oo-mco ping Failed to generate application list: RuntimeError: Unknown config parameter toprefix


Something amiss.Any clue why this exception ?Any checkpoints for the same?

Thanks
Shabna

-----Original Message-----
From: Jason DeTiberus [mailto:jdetiber redhat com]
Sent: Thursday, January 16, 2014 10:26 PM
To: N. Harrison Ripps
Cc: Madathilthattantav, S.; users lists openshift redhat com; Krishna Raman; dev lists openshift redhat com
Subject: Re: oo-install for Origin version 3

On 16/01/14 11:48 -0500, N. Harrison Ripps wrote:
Hey Shabna--

On Jan 16, 2014, at 11:35 , <s madathilthattantav accenture com> <s madathilthattantav accenture com> wrote:

Thanks a lot !
After doing the checklist in Node - tats one error down.All other errors are related to cart..not an issue as of now.

So Node looks good now

Glad that helped! Props to The Dude!

[root node1 ~]# oo-accept-node -v
INFO: using default accept-node extensions
INFO: loading node configuration file /etc/openshift/node.conf
INFO: loading resource limit file /etc/openshift/resource_limits.conf
INFO: finding external network device
INFO: checking node public hostname resolution
INFO: checking selinux status
INFO: checking selinux openshift-origin policy
INFO: checking selinux booleans
INFO: checking package list
INFO: checking services
INFO: checking kernel semaphores >= 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.ym
l
FAIL: no manifest in the cart repo matches
/usr/libexec/openshift/cartridges/perl/metadata/manifest.yml
3 ERRORS


On Broker though,as I mentioned to Harrison, the mcollective was not
installed in Broker after running oo-install I did it manually and
something got messed up

Make sure that you are looking in the right place for mcollective, the output leads me to believe you are an a RHEL type system and not Fedora, so you are using an SCL'ized version of mcollective (ruby193-mcollective is the service script, and oo-mco will invoke the mco binary properly)

--
Jason DeTiberus


To me, the only way that this is possible is if the puppet operation failed to complete on the Broker. I would like to try to create the same environment that you are using to test this. Can you let me know:

1. What base AMI are you using? If it is public, I'd like to use the same one; if not, could you instead let me know which OS & OS version you are starting with?
2. I think you are using only two hosts - a "basic Broker" (broker + named + mongodb + activemq) and a "basic Node" (node only). Is that correct?

Anything else that is unique to your test configuration that you can share would be really helpful, too.

Thanks,
Harrison


[root ip-10-91-136-141 conf.d]# mco ping connect to
broker.cloudshift.com failed: Connection refused - connect(2) will
retry(#0) in 5 ^C The ping application failed to run, use -v for full
error details: Could not connect to Stomp Server:



[root ip-10-91-136-141 conf.d]# oo-diagonostics -vv
bash: oo-diagonostics: command not found
[root ip-10-91-136-141 conf.d]# oo-diagnostics -vv
INFO: loading list of installed packages
INFO: OpenShift broker installed.
INFO: Loading the broker rails environment.
INFO: running: prereq_dns_server_available
INFO: checking that the first server in /etc/resolv.conf responds
INFO: running: prereq_domain_resolves
INFO: checking that we can resolve our application domain
INFO: running: test_enterprise_rpms
INFO: skipping test_enterprise_rpms
INFO: running: test_selinux_policy_rpm
INFO: rpm selinux-policy installed with at least version
3.7.19-195.el6_4.4
INFO: running: test_selinux_enabled
INFO: running: test_broker_cache_permissions
INFO: broker application cache permissions appear fine
INFO: running: test_node_profiles_districts_from_broker
INFO: checking node profiles via MCollective
FAIL: rescue in block in run_tests
error running test_node_profiles_districts_from_broker:
#<OpenShift::NodeException: Unknown config parameter toprefix>
INFO: running: test_broker_accept_scripts
INFO: running oo-accept-broker
FAIL: run_script
oo-accept-broker had errors:
--BEGIN OUTPUT--
NOTICE: SELinux is Enforcing
NOTICE: SELinux is  Enforcing
FAIL: Did not get expected HTTP 200 response from
https://localhost/broker/rest/cartridges
1 ERRORS  ---I know this error ,broker not able to communicate to
node

--END oo-accept-broker OUTPUT--
INFO: running oo-accept-systems -w 2
FAIL: run_script
oo-accept-systems -w 2 had errors:
--BEGIN OUTPUT--
/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.18.0.1/lib/openshift/mcollective_application_container_proxy.rb:3360:in `rescue in get_rpc_client': Unknown config parameter toprefix (OpenShift::NodeException)
        from /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.18.0.1/lib/openshift/mcollective_application_container_proxy.rb:3355:in `get_rpc_client'
        from /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.18.0.1/lib/openshift/mcollective_application_container_proxy.rb:2305:in `rpc_exec'
        from /opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.18.0.1/lib/openshift/mcollective_application_container_proxy.rb:3205:in `rpc_get_fact'
        from /usr/sbin/oo-accept-systems:80:in `check_nodes_public_hostname'
        from /usr/sbin/oo-accept-systems:211:in `<main>'

--END oo-accept-systems -w 2 OUTPUT--
INFO: running: test_node_accept_scripts
INFO: skipping test_node_accept_scripts
INFO: running: test_broker_httpd_error_log
INFO: running: test_broker_passenger_ps
INFO: checking the broker application process tree
INFO: running: test_for_nonrpm_rubygems
INFO: skipping test_for_nonrpm_rubygems
INFO: running: test_for_multiple_gem_versions
INFO: checking for presence of gem-installed rubygems
INFO: running: test_node_httpd_error_log
INFO: running: test_node_containerization_plugin
INFO: skipping test_node_containerization_plugin
INFO: running: test_node_mco_log
INFO: skipping test_node_mco_log
INFO: running: test_pam_openshift
INFO: skipping test_pam_openshift
INFO: running: test_services_enabled
INFO: checking that required services are running now
INFO: checking that required services are enabled at boot
INFO: running: test_node_quota_bug
INFO: skipping test_node_quota_bug
INFO: running: test_vhost_servernames
INFO: checking for vhost interference problems
INFO: running: test_altered_package_owned_configs
WARN: test_altered_package_owned_configs
           RPM package owned configuration files have been altered:
             /etc/ssh/sshd_config.rpmnew
/etc/yum.repos.d/redhat-rhui-client-config.repo.rpmsave
/etc/yum.repos.d/redhat-rhui.repo.rpmsave

           Ensure any package-owned configuration files which have been
           altered are accurate. This may require a manual merge of
           your previous alterations. Once you are comfortable with the merge,
           remove the reported .rpm* configuration file (or you will continue
           to see this warning each time you run the diagnostic test).

INFO: running: test_broken_httpd_version
INFO: running: test_usergroups_enabled
INFO: skipping test_usergroups_enabled
INFO: running: test_mcollective_context
INFO: skipping test_mcollective_context
INFO: running: test_mcollective_bad_facts Failed to generate
application list: RuntimeError: Unknown config parameter toprefix
INFO: running: test_auth_conf_files
INFO: running: test_broker_certificate
WARN: test_broker_certificate
Using a self-signed certificate for the broker
INFO: running: test_abrt_addon_python
INFO: skipping test_abrt_addon_python
INFO: running: test_node_frontend_clash
INFO: skipping test_node_frontend_clash
INFO: running: test_yum_configuration
2 WARNINGS
3 ERRORS

Appreciate your help.

Shabna
-----Original Message-----
From: The Dude [mailto:michael mcconachie hotmail com]
Sent: Thursday, January 16, 2014 9:44 PM
To: Madathilthattantav, S.; hripps redhat com
Cc: users lists openshift redhat com; kraman redhat com;
dev lists openshift redhat com
Subject: RE: oo-install for Origin version 3

Howdy Shabna --

I have been heads down at work, but wanted to validate having to restart httpd after the build/reboot.  In fact, I'm putting together a checklist of stuff that I do (and will share it when I'm done). The intent will be to be able to use the installer, reboot, and then pretty much copy/paste to get the rest of it working. Sounds like you sorted much of it already.

Here's a shortlist of what I do to get any number of nodes working after a build and reboot.


Node stuff:
-------------------
service cgred restart; chkconfig cgred on service cgconfig restart;
chkconfig cgconfig on echo "kernel.sem = 250  32000 32  4096">>
/etc/sysctl.conf; sysctl -p service mcollective restart
oo-accept-node

Broker stuff:
------------------
host=$(hostname -f)
chkconfig httpd on
sed -i '/VirtualHost/,/VirtualHost/ d' /etc/httpd/conf.d/ssl.conf sed
-i 's/localhost/${host}/'
/etc/httpd/conf.d/000002_openshift_origin_broker_servername.conf
yum -y install mlocate
service openshift-broker restart
oo-diagnostics -vv

If you don't wanna use NetworkManager:
--------------------------------------
grep -l NM_CONTROLLED /etc/sysconfig/network-scripts/ifcfg-* | xargs perl -p -i -e '/NM_CONTROLLED/ && s/yes/no/i'


Thanks,


Michael J. McConachie



________________________________
> From: s madathilthattantav accenture com
> To: hripps redhat com
> Subject: RE: oo-install for Origin version 3
> Date: Thu, 16 Jan 2014 06:29:10 +0000
> CC: users lists openshift redhat com; kraman redhat com;
> dev lists openshift redhat com
>
>
> 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.
>
> [https://bay172.afx.ms/att/GetInline.aspx?messageid=93fc9e06-7e78-1
> 1e3
> -a701-00215ad9b8c2&attindex=0&cp=-1&attdepth=0&imgsrc=cid%3aimage00
> 1.p
> ng%4001CF12B2.375C53B0&cid=b78b6bdcd5dd4d99&hm__login=michael.mccon
> ach
> ie&hm__domain=hotmail.com&ip=10.111.80.8&d=d4205&mf=32&hm__ts=Thu%2
> c%2
> 016%20Jan%202014%2016%3a02%3a45%20GMT&st=michael.mcconachie&hm__ha=
> 01_
> 7b476f6627dfd34f26a57bbfeb709ce30750804a19243f798df848307dbcf6c7&on
> ere
> dir=1]
>
>
>
> -----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<mailto:s madathilthattantav acc
> ent
> ure.com>>
> <s madathilthattantav accenture com<mailto:s madathilthattantav acc
> ent
> ure.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<mailto:dev lists openshift redhat co
> m>;
> users lists openshift redhat com<mailto:users lists openshift redha
> t.c
> om>;
>
> > 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<mailto:s madathilthattantav acce
> ntu
> re.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+IT0muuZUrlW8QoxiglLJf5iquolicyIVcHJ52PwWvliVFl7y5
> >> n7b
> >> zE
>
> >> 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+IT0muuZUrlW8QoxiglLJf5iquolicyIVcHJ52PwWvliVFl7y5
> >> n7b
> >> zE
>
> >> 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<mailto:dev lists openshift redhat co
> m>;
> users lists openshift redhat com<mailto:users lists openshift redha
> t.c
> om>
>
> >> 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<mailto:s madathilthattantav acc
> ent
> ure.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<http://www.accenture.com>
>
> >> _______________________________________________
>
> >> users mailing list
>
> >> users lists openshift redhat com<mailto:users lists openshift re
> >> dha
> >> t.com>
>
> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
> >> <Puppetconfig.docx>
>
> >
>
> >
>
> >
>
>
>
>
>
> _______________________________________________ users mailing list
> users lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users


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



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