Posted in Cloud Computing, OpenStack, Private Cloud

what is OpenStack


what is OpenStack – OpenStack offers open source software to build public and private clouds started by Rackspace (“Cloud Files” platform) and NASA (Nebula) in 2010. Currently more than 150 companies have joined the project such as Intel, Cisco, Dell, HP, AMD, Canonical, SUSE Linux, Red Hat, and IBM.

There are 3 main service families under OpenStack:

Cloud Computing – Download Free EBooks and Whitepapers
Java – Download Free EBooks and Whitepapers
Windows – Download Free EBooks and Whitepapers

1. OpenStack Services

Figure 1: OpenStack Services

Presentation Layer: components here interact with users to accept and present information.

Logic Layer: intelligence and control functionality for cloud.

Resources Layer: Compute, Storage and Network Resources for Cloud.

Compute Infrastructure (Nova)

 OpenStack Architecture

Figure 2: OpenStack Architecture

  • Nova: cloud computing fabric controller
  • Instance life cycle management
  • Management of compute resources
  • Networking and Authorization
  • REST-based API
  • Asynchronous eventually consistent communication
  • Hypervisor agnostic: support for Xen, XenServer/XCP, KVM, UML, VMware vSphere and
  • Hyper-V [No virtualization capabilities by itself; instead, it uses libvirt APIs to interact with the supported hypervisors.]

Use Cases:

v  Service providers offering an IaaS compute platform

v  IT departments provisioning compute resources to teams and projects

v  Processing big data with tools like Hadoop

v  Scaling compute up and down to meet demand for web resources and applications

Storage Infrastructure (Swift)

Swift provides a distributed, eventually consistent virtual object store for OpenStack. It is analogous to Amazon Web Services – Simple Storage Service (S3).

  • Storage of large number of objects
  • Storage of large sized objects
  • Data Redundancy
  • Archival capabilities – Work with large datasets
  • Data container for virtual machines and cloud apps
  • Media Streaming capabilities
  • Secure storage of objects
  • Backup and archival
  • Extreme scalability

Imaging Service (Glance)

OpenStack Imaging Service is a lookup and retrieval system for virtual machine images. It can be configured to use any one of the following 3 storage back-ends:

  • OpenStack Object Store to store images
  • S3 storage directly
  • S3 storage with Object Store as the intermediate for S3 access

Image Management

OpenStack Image Services are used for discovering, registering, and retrieving virtual machine images. The service includes a RESTful API that allows users to query VM image metadata and retrieve the actual image with HTTP requests. VM images made available through OpenStack Image Service can be stored in OpenStack Object Storage project, S3 storage.

Instance Management

An instance is a virtual machine provisioned by OpenStack on one of the nova-compute servers. When you launch an instance, a series of steps are triggered on various components of the OpenStack.

OpenStack Instance Life Cycle

Figure 3: OpenStack Instance Life Cycle

Network Management

In OpenStack, the networking is managed by a component called “nova-network”. This interacts with nova-compute to ensure that the instances have the right kind of networking setup for them to communicate among themselves as well as with the outside world.

  • Flat Network
  • Flat DHCP Network
  • VLAN Network

Identity Service

The OpenStack Identity Service provides services for authenticating and managing user, account, and role information for OpenStack clouds running on OpenStack Compute and as an authorization service for OpenStack Object Storage.

Hypervisors Support

List of the supported hypervisors with links to a relevant web site for configuration and use:

  • Hyper-V 2008 – Use to run Windows-based virtual machines, specifically Windows 2008 R2 Datacenter or Enterprise Edition. You must install and run nova-compute on Windows servers that run the Windows-based virtual machines.
  • KVM – Kernel-based Virtual Machine. The virtual disk formats that it supports it inherit from QEMU since it uses a modified QEMU program to launch the virtual machine. The supported formats include raw images, the qcow2, and VMware formats.
  • LXC – Linux Containers (through libvirt), use to run Linux-based virtual machines.
  • QEMU – Quick EMUlator, generally only used for development purposes.
  • UML – User Mode Linux, generally only used for development purposes.
  • VMWare ESX/ESXi 4.1 update 1, runs VMWare-based Linux and Windows images through a connection with the ESX server.
  • Xen – XenServer 5.5, Xen Cloud Platform (XCP), use to run Linux or Windows virtual machines. You must install the nova-compute service on DomU.
Advertisements
Posted in Cloud Computing, Uncategorized

Nagios Cloud Monitotring


Nagios Cloud Monitotring
Computer Network, Network Monitoring and Management

Figure 1: Computer Network, Network Monitoring and Management

Computers connected with communication channels shares resources and information with each other. Network monitoring supervises all or specific operations of computer network using various network monitoring products. It ensures performance and availability of network services by identifying and reporting failures of network services. Network management refers to the actions, procedures, and tools that are related to keeping network services up and running, keeping track of resources, performing upgrades, and configuring resources of networked systems. Network Management is a superset of network monitoring term.

In this article our focus will be on open source network monitoring and infrastructure monitoring tool known as Nagios. It provides monitoring and reporting for network services such as HTTP, SMTP, SSH, and FTP; host resources such as logs, storage and processor usage. It monitors IT infrastructure, detect the problems before they occur and alerts the stockholders. Web based GUI is available. It is also used to monitor publicly available services. It is very useful for SMBs.

Effective usage of it ensures issue tracking within timely manner; SLAs, which are very critical in today’s dynamic IT world, can be met effectively and it ensures that outages will have minimal effect on organization’s IT infrastructure as it monitors infrastructure extensively.

Nagios Core

Nagios Core is an open source, infrastructure monitoring system that enables organizations to identify IT infrastructure problems before they have an effect on critical business processes.

Nagios Core provides base for Nagios XI – commercial monitoring solution.

Nagios Core allows to monitor your entire IT infrastructure to ensure IT resources, applications, services, and business processes are functioning appropriately. In the event of a failure, it can alert technical staff of the problem in timely manner which allows them to commence remediation processes before outages affect business processes, end-users, or customers. It is licensed under GNU General Public License.

How it works?

How Nagios Works

Figure 2 – How it Works?

Features

Features of Nagios

Figure 3 – Features

It can empower IT organizations and Cloud Service Providers to identify and resolve issues in a way that outages have minimal impact on IT infrastructure and processes. It provides extensive and detailed monitoring of IT resources, detection of outages, deep visibility into entire infrastructure and detailed report on the status of resources, services and other components. Availability reports, Historical reports and third party addons help into getting insight whether SLAs are being met effectively or not.

Multiple online resources are available which can be useful to the users; support forum, Support portal, and Community mailing lists is also very useful.

Comparison with IBM Tivoli Network Manager and Nimsoft Monitoring Solution

  Nagios Nimsoft Monitoring Solution IBM Tivoli Network Manager
Trend Prediction No Yes Yes
Auto Discovery Plug-in Yes Yes
Syslog Plug-in Yes Yes
Distributed Monitoring Yes Yes Yes
Data Storage Flat file,SQL SQLServer,Oracle MySQL,Oracle Database,DB2
Access Control Yes Yes Yes
License GPL Commercial Commercial

Use Cases

ISPs, Government agencies, Health care, Manufacturing, and financial institutions can use it effectively for network monitoring.

Banking and Finance Industry

It is desirable to have networking monitoring product which is easy to setup, configure and maintain. It must monitor different kind of devices and multiple platforms within adequate budget. Banking and financial industry deals with critical, time bound and monetary transactions which should be made available to customers all the time. Its alerting capabilities help banking and finance industries to decrease the downtime of various services within adequate budget due to its open source availability.

Telecommunication Industry

Telecommunication providers who use various application and system resources monitored by various network monitoring systems can use it to provide deep insight into the complex IT infrastructure. By using single solution in the form of Nagios, operational efficiency and cost benefits can be achieved.

Monitor openSUSE Virtual Machine

To run a Nagios core, you need a machine running Linux or Unix variant, Network accessibility as basic prerequisite.

We can use VMware workstation or VMware Player to create virtual machine; In fact any other product can be used also. Install openSUSE 12.2 operating system on the virtual machine as we will use that linux variant in the below steps. Insert openSuse 12.2 DVD and from VMware workstation, go to Edit Settings of that virtual machine to connect to the openSUSE DVD.

Prerequisite packages:

  • C/C++ development libraries
  • php5
  • apache2
  • apache2-mod_php5

We will use Zypper command to install prerequisite packages. Zypper is a command line package manager.  It uses libzypp and provides functions such as repository access, and package installation. Zypper RPM packages are by default available on standard openSUSE installation media and need not to install the packages manually. It can be used to install/remove/update packages or patches, and plain rpm files; it also provides detailed installation summary.

To install C/C++ development libraries:

zypper install kernel-source make gcc gcc-c++

To install other packages:

zypper install rrdtool php5 php5-gd php5-zlib apache2-mod_php5 perl-SNMP net-snmp-32bit nmap ncpfs libwavpack1 apache2

Download open source  http://www.nagios.org/download/

Nagios XI is a commercial version built on Nagios core; its pre-build packages are available on the its website. VMware virtual machine, vSphere OVF, Microsoft virtual machine and source installer is available.

Login with root, create user, change password and add a group.

linux-5vhd:/home/mitesh # /usr/sbin/useradd -m nagios

linux-5vhd:/home/mitesh # passwd nagios

Changing password for nagios.

New Password:

Password changed.

Add gorup nagcmd

sudo groupadd nagcmd

sudo groupadd Nagios

Add users nagios in group nagcmd  and  nagios  group

sudo usermod  -G nagcmd Nagios

Extract the Nagios core tar file; cd the the extracted folder and execute following commad:

sudo ./configure -with-command-group=nagcmd

Sudo make all

Successful execution will end with “Enjoy!” message.

Installs the init script in /etc/rc.d

linux-5vhd:/home/nagios # sudo make install-init

/usr/bin/install -c -m 755 -d -o root -g root /etc/rc.d

/usr/bin/install -c -m 755 -o root -g root daemon-init /etc/rc.d/nagios

*** Init script installed ***

Installs sample config files in /usr/local/nagios/etc

sudo make install-config

Installs and configures permissions on the directory

linux-5vhd:/home/nagios # sudo make install-commandmode

/usr/bin/install -c -m 775 -o nagios -g nagcmd -d /usr/local/nagios/var/rw

chmod g+s /usr/local/nagios/var/rw

*** External command directory configured ***

Configure Nagios for apache

linux-5vhd:/home/nagios # sudo make install-webconf

/usr/bin/install -c -m 644 sample-config/httpd.conf /etc/apache2/conf.d/nagios.conf

*** Nagios/Apache conf file installed ***

Make a webadmin password for  nagios  admin

linux-5vhd:/home/nagios # htpasswd2 -c /usr/local/nagios/etc/htpasswd.users nagiosadmin

New password: (admin)

Re-type new password:

Adding password for user nagiosadmin

Restart Apache

linux-5vhd:/home/nagios # sudo /etc/init.d/apache2 restart

redirecting to systemctl

linux-5vhd:/home/nagios # service apache2 status

apache2.service – apache

Loaded: loaded (/lib/systemd/system/apache2.service; disabled)

Active: active (running) since Tue, 06 Nov 2012 01:18:16 +0530; 1min 47s ago

Process: 18724 ExecStart=/usr/sbin/start_apache2 -D SYSTEMD -k start (code=exited, status=0/SUCCESS)

Main PID: 18743 (httpd2-prefork)

CGroup: name=systemd:/system/apache2.service

├ 18743 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start

├ 18744 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start

├ 18745 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start

├ 18746 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start

├ 18747 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start

└ 18748 /usr/sbin/httpd2-prefork -f /etc/apache2/httpd.conf -D SYSTEMD -k start

Nov 06 01:18:04 linux-5vhd start_apache2[18724]: httpd2-prefork: apr_sockaddr_info_get() failed for linux-5vhd

Nov 06 01:18:04 linux-5vhd start_apache2[18724]: httpd2-prefork: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1 for ServerName

Download the Nagios plugin from http://www.nagios.org/download/plugins/

Extract the file

cd nagios-plugins-1.4.15

sudo ./configure –with-user=nagios –with-group=nagcmd

sudo make

Wait for 10-15 minutes approximately – Checking of various parameters until the command finishes the execution.

sudo make install

Add Nagios to the list of system services to make it automatically start when the system starts.

chkconfig –add nagios

chkconfig nagios on

Verify the sample Nagios configuration files.

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

If there are no errors, start Nagios.

service nagios start

Open Browser and Access http://localhost/nagios

Nagios Web Interface

Figure 4 – Nagios Web Interface

Network Outage details from Nagios

Nagios Web Interface - Tactical Monitoring Overview

Figure 5 – Nagios Web Interface – Tactical Monitoring Overview

Current Network Status

Current Network Status

Figure 6 – Current Network Status

Alert History in Nagios Web Interface

Alert History

Figure 7 – Alert History

Verify Performance information.

Performance Information

Figure 8 – Performance Information

Information on Scheduling Queues

Check Scheduling Queues

Figure 9 – Check Scheduling Queues

Nagios Checker-Mozilla Firefox add-ons for Nagios

Mozilla Firefox add-ons for Nagios provide status bar display to provide information on the status of resources from Nagios. Nagios web interface information is parsed and information is made available to the indicator. Add-on has been successfully verified with Nagios 3, 2.5+, 2.0b4, 1.5, 1.3 and 1.2.

Add the Nagios Checker from https://addons.mozilla.org/en-US/firefox/addon/nagios-checker/ to Firefox. Restart Firefox. Right click on the “N” sign in status bar and click on settings option. Provide Nagios web URL, Username and Password.

 Nagios Checker Settings - Web Interface

Figure 10 – Nagios Checker Settings – Web Interface

Provide Static Script URL.

Nagios Checker Settings - Script URL

Figure 11 – Nagios Checker Settings – Script URL

Click Ok and within seconds, you will be able to see the status provided by Nagios on the status bar.

Nagios Checker Status

Figure 12 – Nagios Checker Status

Cloud Monitoring with nagios

As per NIST’s definition, Cloud computing is a model for enabling

  • Ubiquitous,
  • Convenient,
  • On-demand network access

to a shared pool of    configurable computing resources

  • Networks
  • Servers
  • Storage

that can be rapidly provisioned and de-provisioned with minimal management effort. Virtualization is the core of Cloud Computing considering it provides, Cost saving by reducing upfront investment in infrastructure. In Virtualization, we create multiple virtual environments on a single physical resource by decoupling OS from hardware, create an abstraction between OS and the hardware and optimize resource utilization with the use of virtualization product.

When we say Cloud Monitoring, it is in the context of monitoring resources available in Cloud or provided by Cloud service providers.

In virtual world monitoring of resources is not only necessary but crucial also to provide high availability and fault tolerance, and to avoid single point failure since resources are shared. Monitoring of virtual system is dynamic cince the resources are vitual and can be treated in similar way to files. Reource monitoring for scaling up and scaling down is also critical considering the huge capacity (virtyally unlimited) provided by Cloud service providers.

Public Cloud Monitoring

Cloud monitoring refers to the monitoring of the performance of physical or virtual servers, storage, networks, and the applications running on them. Cloud monitoring tools are employed can collect data and illustrate patterns that might be difficult to spot otherwise in dynamic infrastructure and services provided by Cloud service providers. It used to achieve high availability.

Nagios provides monitoring of Cloud resources; compute, storage and network services. Nagios is proficient of monitoring a variety of servers and operating systems in both physical and virtual environment. We have seen an example where we have used Nagios to monitor virtual machine created in VMware workstation. With Nagios, it is easy to detect Cloud Computing environment issues, detection of network outages and application availability.

Benefits and Limitations

Implementing effective Cloud monitoring with Nagios offers multiple benefits:

  • High Availability: Increased server, services, and application availability
  • Fault Tolerance: Fast detection of network outages
  • SLA compliance: Fast detection of cloud computing environment problems
  • Data availability: Fast detection of storage subsystem problems

Amazon Web Services (AWS) Monitoring

Nagios provides monitoring of Amazon EC2, Amazon Simple Storage Services etc. Nagios solutions that provide Cloud monitoring capabilities and benefits are Nagios XI and Nagios Core.

Reference

http://compnetworking.about.com/od/itinformationtechnology/f/net_monitoring.htm

Nagios Core Documentation: http://nagios.sourceforge.net/docs/nagioscore/3/en/toc.html

http://library.nagios.com/library/products/nagiosxi/manuals

https://addons.mozilla.org/en-US/firefox/addon/nagios-checker/

http://searchenterpriselinux.techtarget.com/definition/Nagios

Posted in How To..., Linux

How to install C/C++ development libraries on openSUSE 12.2


Insert openSUSE 12.2 installation media which contains various packages and execute following command to install C/C++ development library.

zypper install kernel-source make gcc gcc-c++

Cloud Computing – Download Free EBooks and Whitepapers
Java – Download Free EBooks and Whitepapers
Windows – Download Free EBooks and Whitepapers

Verify the installation:

linux-5vhd:/home/nagios # gcc –version

gcc (SUSE Linux) 4.7.1 20120723 [gcc-4_7-branch revision 189773]

Copyright (C) 2012 Free Software Foundation, Inc.

This is free software; see the source for copying conditions.  There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

 

linux-5vhd:/home/nagios # which gcc

/usr/bin/gcc

linux-5vhd:/home/nagios #

 

Posted in How To..., Linux

openSUSE 12.2 – Configure: error: no acceptable C compiler found in $PATH


openSUSE is an operating system built on top of the Linux kernel. It is sponsored by SUSE and a number of other companies and developed by the community-supported openSUSE Project. Novell decided to release the SUSE Linux Professional product as a 100% open source project the current stable release is openSUSE 13.1. It comes in several editions for the x86 and x86-64 architectures such as Download Edition, Retail Edition or Box, FTP, Factory, and Tumbleweed.

Features:

  • YaST Control Center:  installation and administration program
  • AutoYaST: for automatic installation
  • ZYpp package management: Linux software management engine
  • Build Service: tool to compile, release and publish their software
  • Desktop innovation
  • Xgl and Compiz: for graphics
  • KDE Desktop innovations

While installing any package or while installing any product on SUSE operation system, when you get the error

Configure: error: no acceptable C compiler found in $PATH

you need to install C/C++ development libraries to solve the issue.

Solution:

insert openSUSE 12.2 installation media which contains various packages and execute following command to install C/C++ development library.

zypper install kernel-source make gcc gcc-c++

openSUSE
openSUSE

 

Posted in How To..., Others

Installation and Overview of openSUSE 12.2


Installation and Overview of openSUSE 12.2

openSUSE is an operating system built on top of the Linux kernel 3.4.

Developed by the community-supported openSUSE Project and sponsored by SUSE. Novell acquired SUSE Linux in January 2004 and decided to release the SUSE Linux Professional product as a 100% open source project.

Initial Release: Beta version of SUSE Linux 10.0

Latest Stable Version: openSUSE 12.2

System Requirements

  • openSUSE 12.2 supports 32-bit i586 and 64-bit x86-64 PC hardware.
  • CPU: Intel PIII 500 MHz or higher, P4 2.4 GHZ / AMD64 / Intel64 CPU.
  • RAM: 1 GB
  • Disk: 3 GB for minimal system; 5 GB for standard system

New Features

  • Privilege separation and sandboxing by OpenSSH 6.0
  • DNSSEC support by Bind 9.9
  • TLS version 1.1 and 1.2 support
Download Free EBooks and Whitepapers on Big DATA
Cloud Computing – Download Free EBooks and Whitepapers
Java – Download Free EBooks and Whitepapers
Windows – Download Free EBooks and Whitepapers

Website

http://www.opensuse.org/en/

opensuse.org Website
opensuse.org Website

How to Download?

http://software.opensuse.org/122/en

Download OpenSUSE 12.2
Download OpenSUSE 12.2

Now… Insert bootable DVD, Change the Boot order if needed from the BIOS settings…

openSUSE Screen
openSUSE Screen
openSUSE Installation Program - Starting udev
openSUSE Installation Program – Starting udev

Select Language, Keyboard Layout and Accept License Agreement!!

openSUSE Installation Preparation - Welcome
openSUSE Installation Preparation – Welcome
openSUSE Installation - System Analysis
openSUSE Installation – System Analysis

Select Installation Mode

openSUSE Installation - Installation Mode
openSUSE Installation – Installation Mode

Select Clock and Timezone as per preferences…

openSUSE Installation - Time Zone
openSUSE Installation – Time Zone

Select a Desktop, We select KDE Desktop

openSUSE Installation - Desktop Selection
openSUSE Installation – Desktop Selection

Suggest Partitioning, you can create, import or edit Partition setup as desired.

openSUSE Installation - Disk
openSUSE Installation – Disk

Create New User

openSUSE Installation - User Setting
openSUSE Installation – User Setting

YaST2- Retrieving cracklib-dict-full.rpm

openSUSE Installation - User Setting - YaST2
openSUSE Installation – User Setting – YaST2

Installation Settings

openSUSE Installation - Overview
openSUSE Installation – Overview

YaST2 – Confirm Installation

openSUSE Installation - Confirm Installation
openSUSE Installation – Confirm Installation

Now…Automatic Configuration

openSUSE Installation - Automatic Configuration
openSUSE Installation – Automatic Configuration

Get

openSUSE Desktop in Seconds 1
openSUSE Desktop in Seconds 1

Set

openSUSE Desktop in Seconds 2
openSUSE Desktop in Seconds 2

Go

openSUSE Desktop
openSUSE Desktop

My Computer in openSUSE

openSUSE - My Computer
openSUSE – My Computer

Done!!!

Posted in Java, JEE / J2EE / JSP / Servlets, Tomcat

Install Tomcat 6 in CentOS 6.3


1) Install CentOS 6.3 -> How to install CentOS 6.3 ;

2) Create a Local Yum Repository in CentOS 6.3 -> Create a Local Yum Repository in CentOS 6.3 in 5 steps

3) Run yum install tomcat6 and Tomcat will be installed!!! Done!!!

Cloud Computing – Download Free EBooks and Whitepapers
Java – Download Free EBooks and Whitepapers
Windows – Download Free EBooks and Whitepapers

[root@localhost ~]# yum install tomcat6

Loaded plugins: fastestmirror, refresh-packagekit, security

Loading mirror speeds
from cached hostfile

Setting up Install Process

Resolving Dependencies

–> Running transaction check

—> Package
tomcat6.noarch 0:6.0.24-45.el6 will be installed

base/filelists
| 4.4 MB00:01

–> Processing Dependency: tomcat6-lib = 6.0.24-45.el6 for package:tomcat6-6.0.24-45.el6.noarch

–> Processing Dependency: mx4j for package: tomcat6-6.0.24-45.el6.noarch

–> Processing Dependency: log4j for package: tomcat6-6.0.24-45.el6.noarch

–> Processing Dependency: log4j for package: tomcat6-6.0.24-45.el6.noarch

–> Processing Dependency: jakarta-commons-pool for package: tomcat6-6.0.24-45.el6.noarch

–> Processing Dependency: jakarta-commons-logging for package: tomcat6-6.0.24-45.el6.noarch

–> Processing Dependency: jakarta-commons-dbcp for package: tomcat6-6.0.24-45.el6.noarch

–> Processing Dependency: jakarta-commons-daemon for package: tomcat6-6.0.24-45.el6.noarch

–> Processing Dependency: jakarta-commons-collections for package: tomcat6-6.0.24-45.el6.noarch

–> Running transaction check

—> Package jakarta-commons-collections.noarch 0:3.2.1-3.4.el6 will be installed

—> Package jakarta-commons-daemon.i686 1:1.0.1-8.9.el6 will be installed

–> Processing Dependency: libgcj_bc.so.1 for package: 1:jakarta-commons-daemon-1.0.1-8.9.el6.i686

–> Processing Dependency: java-gcjcompat for package: 1:jakarta-commons-daemon-1.0.1-8.9.el6.i686

–> Processing Dependency: java-gcjcompat for package: 1:jakarta-commons-daemon-1.0.1-8.9.el6.i686

—> Package jakarta-commons-dbcp.noarch 0:1.2.1-13.8.el6 will be installed

—> Package jakarta-commons-logging.noarch 0:1.0.4-10.el6 will be installed

—> Package jakarta-commons-pool.i686 0:1.3-12.7.el6 will be installed

—> Package log4j.i686 0:1.2.14-6.4.el6 will be installed

–> Processing Dependency: xml-commons-apis for package: log4j-1.2.14-6.4.el6.i686

—> Package mx4j.noarch 1:3.0.1-9.13.el6 will be installed

–> Processing Dependency: javamail >= 1.2-5jpp for package: 1:mx4j-3.0.1-9.13.el6.noarch

–> Processing Dependency: bcel >= 5.0 for package: 1:mx4j-3.0.1-9.13.el6.noarch

–> Processing Dependency: axis >= 1.1 for package: 1:mx4j-3.0.1-9.13.el6.noarch

–> Processing Dependency: xml-commons-resolver for package: 1:mx4j-3.0.1-9.13.el6.noarch

–> Processing Dependency: jaf for package: 1:mx4j-3.0.1-9.13.el6.noarch

—> Package tomcat6-lib.noarch 0:6.0.24-45.el6 will be installed

–> Processing Dependency: tomcat6-servlet-2.5-api = 6.0.24-45.el6 for package: tomcat6-lib-6.0.24-45.el6.noarch

–> Processing Dependency: tomcat6-jsp-2.1-api = 6.0.24-45.el6 for package: tomcat6-lib-6.0.24-45.el6.noarch

–> Processing Dependency: tomcat6-el-2.1-api = 6.0.24-45.el6 for package: tomcat6-lib-6.0.24-45.el6.noarch

–> Processing Dependency: ecj for package: tomcat6-lib-6.0.24-45.el6.noarch

–> Running transaction check

—> Package axis.noarch 0:1.2.1-7.2.el6 will be installed

–> Processing Dependency: wsdl4j for package: axis-1.2.1-7.2.el6.noarch

–> Processing Dependency: jakarta-commons-httpclient for package: axis-1.2.1-7.2.el6.noarch

–> Processing Dependency: jakarta-commons-discovery for package: axis-1.2.1-7.2.el6.noarch

—> Package bcel.i686 0:5.2-7.2.el6 will be installed

–> Processing Dependency: regexp for package: bcel-5.2-7.2.el6.i686

—> Package classpathx-jaf.i686 0:1.0-15.4.el6 will be installed

—> Package classpathx-mail.noarch 0:1.1.1-9.4.el6 will be installed

—> Package ecj.i686 1:3.4.2-6.el6 will be installed

—> Package java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6 will be installed

–> Processing Dependency: sinjdoc for package: java-1.5.0-gcj-1.5.0.0-29.1.el6.i686

—> Package libgcj.i686 0:4.4.6-4.el6 will be installed

—> Package tomcat6-el-2.1-api.noarch 0:6.0.24-45.el6 will be installed

—> Package tomcat6-jsp-2.1-api.noarch 0:6.0.24-45.el6 will be installed

—> Package tomcat6-servlet-2.5-api.noarch 0:6.0.24-45.el6 will be installed

—> Package xml-commons-apis.i686 0:1.3.04-3.6.el6 will be installed

—> Package xml-commons-resolver.i686 0:1.1-4.18.el6 will be installed

–> Running transaction check

—> Package jakarta-commons-discovery.noarch

1:0.4-5.4.el6 will be installed

—> Package jakarta-commons-httpclient.i686 1:3.1-0.6.el6 will be installed

—> Package regexp.i686 0:1.5-4.4.el6 will be installed

—> Package sinjdoc.i686 0:0.5-9.1.el6 will be installed

–> Processing Dependency: java_cup >= 0.10 for package: sinjdoc-0.5-9.1.el6.i686

—> Package wsdl4j.noarch 0:1.5.2-7.8.el6 will be installed

–> Running transaction check

—> Package java_cup.i686 1:0.10k-5.el6 will be installed

–> Finished
Dependency Resolution

Dependencies Resolved

 

=================================================================================

PackageArchVersionRepositorySize

=================================================================================

Installing:

tomcat6noarch 6.0.24-45.el6 base87 k

Installing for dependencies:

axisnoarch 1.2.1-7.2.el6 base1.5 M

bceli6865.2-7.2.el6 base1.2 M

classpathxjafi6861.0-15.4.el6base92 k

classpathx-mailnoarch1.1.1-9.4.el6base479 k

ecj i6861:3.4.2-6.el6 base2.5 M

jakarta-commons-collections noarch3.2.1-3.4.el6base523 k

jakarta-commons-daemoni6861:1.0.1-8.9.el6base43 k

jakarta-commons-dbcpnoarch1.2.1-13.8.el6base116 k

jakarta-commons-discoverynoarch1:0.4-5.4.el6base73 k

jakarta-commons-httpclienti6861:3.1-0.6.el6base519 k

jakarta-commons-loggingnoarch1.0.4-10.el6base52 k

jakarta-commons-pooli6861.3-12.7.el6base110 k

java-1.5.0-gcji6861.5.0.0-29.1.el6base138 k

java_cupi6861:0.10k-5.el6base178 k

libgcji6864.4.6-4.el6base17 M

log4ji6861.2.14-6.4.el6base603 k

mx4jnoarch 1:3.0.1-9.13.el6 base1.1 M

regexpi6861.5-4.4.el6base97 k

sinjdoci6860.5-9.1.el6base646 k

tomcat6-el-2.1-apinoarch6.0.24-45.el6base43 k

tomcat6-jsp-2.1-apinoarch6.0.24-45.el6base80 k

tomcat6-libnoarch6.0.24-45.el6base2.8 M

tomcat6-servlet-2.5-apinoarch6.0.24-45.el6base94 k

wsdl4jnoarch1.5.2-7.8.el6base157 k

xml-commons-apisi6861.3.04-3.6.el6base388 k

xml-commons-resolveri6861.1-4.18.el6base128 k

 

Transaction Summary

==================================================================================

Install27 Package(s)

 

Total download size: 31 M

Installed size: 84 M

Is this ok [y/N]: y

Downloading Packages:

(1/27):axis-1.2.1-7.2.el6.noarch.rpm | 1.5 MB00:00

(2/27): bcel-5.2-7.2.el6.i686.rpm| 1.2 MB00:00

(3/27): classpathx-jaf-1.0-15.4.el6.i686.rpm |92 kB00:00

(4/27): classpathx-mail-1.1.1-9.4.el6.noarch.rpm| 479 kB00:00

(5/27): ecj-3.4.2-6.el6.i686.rpm | 2.5 MB00:04

(6/27): jakarta-commons-collections-3.2.1-3.4.el6.noarch.rpm| 523 kB 00:00

(7/27):jakarta-commons-daemon-1.0.1-8.9.el6.i686.rpm|43 kB00:00

(8/27): jakarta-commons-dbcp-1.2.1-13.8.el6.noarch.rpm | 116 kB 00:00

(9/27): jakarta-commons-discovery-0.4-5.4.el6.noarch.rpm|73 kB00:00

(10/27): jakarta-commons-httpclient-3.1-0.6.el6.i686.rpm| 519 kB 00:00

(11/27): jakarta-commons-logging-1.0.4-10.el6.noarch.rpm|52 kB00:00

(12/27): jakarta-commons-pool-1.3-12.7.el6.i686.rpm| 110 kB 00:00

(13/27): java-1.5.0-gcj-1.5.0.0-29.1.el6.i686.rpm| 138 kB 00:00

(14/27): java_cup-0.10k-5.el6.i686.rpm | 178 kB 00:00

(15/27): libgcj-4.4.6-4.el6.i686.rpm|17 MB00:10

(16/27): log4j-1.2.14-6.4.el6.i686.rpm| 603 kB 00:00

(17/27): mx4j-3.0.1-9.13.el6.noarch.rpm | 1.1 MB00:00

(18/27): regexp-1.5-4.4.el6.i686.rpm |97 kB00:00

(19/27): sinjdoc-0.5-9.1.el6.i686.rpm | 646 kB 00:00

(20/27): tomcat6-6.0.24-45.el6.noarch.rpm |87 kB00:00

(21/27): tomcat6-el-2.1-api-6.0.24-45.el6.noarch.rpm |43 kB00:00

(22/27): tomcat6-jsp-2.1-api-6.0.24-45.el6.noarch.rpm |80 kB00:00

(23/27): tomcat6-lib-6.0.24-45.el6.noarch.rpm | 2.8 MB00:02

(24/27): tomcat6-servlet-2.5-api-6.0.24-45.el6.noarch.rpm|94 kB00:00

(25/27): wsdl4j-1.5.2-7.8.el6.noarch.rpm| 157 kB 00:00

(26/27): xml-commons-apis-1.3.04-3.6.el6.i686.rpm| 388 kB 00:00

(27/27): xml-commons-resolver-1.1-4.18.el6.i686.rpm| 128 kB 00:00

—————————————————————————————————————————–

Total
1.4 MB/s |31

MB00:21

warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature,
key ID c105b9de: NOKEY

Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

Importing GPG key 0xC105B9DE:

Userid : CentOS-6 Key (CentOS 6 Official Signing Key)
<centos-6-key@centos.org>

Package:
centos-release-6-3.el6.centos.9.i686 (@anaconda-CentOS-201207051201.i386/6.3)

From: /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

 

Is this ok [y/N]: y

Running rpm_check_debug

Running Transaction Test

Transaction Test Succeeded

Running Transaction

Warning: RPMDB altered outside of yum.

Installing : jakarta-commons-logging-1.0.4-10.el6.noarch

1/27

Installing : jakarta-commons-collections-3.2.1-3.4.el6.noarch

2/27

Installing : tomcat6-servlet-2.5-api-6.0.24-45.el6.noarch

3/27

Installing : tomcat6-jsp-2.1-api-6.0.24-45.el6.noarch

4/27

Installing : 1:jakarta-commons-discovery-0.4-5.4.el6.noarch

5/27

Installing : tomcat6-el-2.1-api-6.0.24-45.el6.noarch
6/27

Installing : libgcj-4.4.6-4.el6.i686

7/27

Installing : java-1.5.0-gcj-1.5.0.0-29.1.el6.i686

8/27

Installing : 1:java_cup-0.10k-5.el6.i686

9/27

Installing : sinjdoc-0.5-9.1.el6.i686
10/27

Installing : jakarta-commons-pool-1.3-12.7.el6.i686

11/27

Installing : xml-commons-apis-1.3.04-3.6.el6.i686
12/27

Installing : log4j-1.2.14-6.4.el6.i686


13/27

Installing : classpathx-jaf-1.0-15.4.el6.i686
14/27

Installing : classpathx-mail-1.1.1-9.4.el6.noarch

15/27

Installing : jakarta-commons-dbcp-1.2.1-13.8.el6.noarch

16/27

Installing : wsdl4j-1.5.2-7.8.el6.noarch

17/27

Installing : xml-commons-resolver-1.1-4.18.el6.i686

18/27

Installing : 1:jakarta-commons-httpclient-3.1-0.6.el6.i686


19/27

Installing : axis-1.2.1-7.2.el6.noarch

20/27

Installing : 1:jakarta-commons-daemon-1.0.1-8.9.el6.i686

21/27

Installing : 1:ecj-3.4.2-6.el6.i686

22/27

Installing : regexp-1.5-4.4.el6.i686

23/27

Installing : bcel-5.2-7.2.el6.i686

24/27

Installing : 1:mx4j-3.0.1-9.13.el6.noarch

25/27

Installing : tomcat6-lib-6.0.24-45.el6.noarch

26/27

Installing : tomcat6-6.0.24-45.el6.noarch

27/27

Verifying: tomcat6-el-2.1-api-6.0.24-45.el6.noarch

1/27

Verifying: classpathx-mail-1.1.1-9.4.el6.noarch

2/27

Verifying: 1:jakarta-commons-httpclient-3.1-0.6.el6.i686

3/27

Verifying: 1:jakarta-commons-discovery-0.4-5.4.el6.noarch

4/27

Verifying: tomcat6-lib-6.0.24-45.el6.noarch

5/27

Verifying: jakarta-commons-pool-1.3-12.7.el6.i686

6/27

Verifying: jakarta-commons-collections-3.2.1-3.4.el6.noarch

7/27

Verifying: xml-commons-resolver-1.1-4.18.el6.i686

8/27

Verifying: tomcat6-servlet-2.5-api-6.0.24-45.el6.noarch

9/27

Verifying: tomcat6-6.0.24-45.el6.noarch

10/27

Verifying: 1:java_cup-0.10k-5.el6.i686

11/27

Verifying: sinjdoc-0.5-9.1.el6.i686

12/27

Verifying: libgcj-4.4.6-4.el6.i686

13/27

Verifying: jakarta-commons-logging-1.0.4-10.el6.noarch

14/27

Verifying: wsdl4j-1.5.2-7.8.el6.noarch

15/27

Verifying: axis-1.2.1-7.2.el6.noarch

16/27

Verifying: 1:jakarta-commons-daemon-1.0.1-8.9.el6.i686

17/27

Verifying: java-1.5.0-gcj-1.5.0.0-29.1.el6.i686
18/27

Verifying: bcel-5.2-7.2.el6.i686

19/27

Verifying: xml-commons-apis-1.3.04-3.6.el6.i686
20/27

Verifying: tomcat6-jsp-2.1-api-6.0.24-45.el6.noarch

21/27

Verifying: log4j-1.2.14-6.4.el6.i686

22/27

Verifying: 1:ecj-3.4.2-6.el6.i686

23/27

Verifying : 1:mx4j-3.0.1-9.13.el6.noarch

24/27

Verifying: jakarta-commons-dbcp-1.2.1-13.8.el6.noarch

25/27

Verifying: classpathx-jaf-1.0-15.4.el6.i686

26/27

Verifying: regexp-1.5-4.4.el6.i686

27/27

Installed:

tomcat6.noarch 0:6.0.24-45.el6

 

Dependency Installed:

axis.noarch 0:1.2.1-7.2.el6

bcel.i686 0:5.2-7.2.el6

classpathx-jaf.i686 0:1.0-15.4.el6classpathx-mail.noarch 0:1.1.1-9.4.el6

ecj.i686 1:3.4.2-6.el6jakarta-commons-collections.noarch

0:3.2.1-3.4.el6

jakarta-commons-daemon.i686
1:1.0.1-8.9.el6jakarta-commons-dbcp.noarch
0:1.2.1-13.8.el6

jakarta-commons-discovery.noarch 1:0.4-5.4.el6
jakarta-commons-httpclient.i686 1:3.1-0.6.el6

jakarta-commons-logging.noarch

0:1.0.4-10.el6
jakarta-commons-pool.i686 0:1.3-12.7.el6

java-1.5.0-gcj.i686
0:1.5.0.0-29.1.el6
java_cup.i686 1:0.10k-5.el6

libgcj.i686 0:4.4.6-4.el6log4j.i686
0:1.2.14-6.4.el6

mx4j.noarch 1:3.0.1-9.13.el6regexp.i686 0:1.5-4.4.el6

sinjdoc.i686 0:0.5-9.1.el6
tomcat6-el-2.1-api.noarch 0:6.0.24-45.el6

tomcat6-jsp-2.1-api.noarch

0:6.0.24-45.el6
tomcat6-lib.noarch 0:6.0.24-45.el6

tomcat6-servlet-2.5-api.noarch
0:6.0.24-45.el6
wsdl4j.noarch 0:1.5.2-7.8.el6

xml-commons-apis.i686

0:1.3.04-3.6.el6
xml-commons-resolver.i686 0:1.1-4.18.el6

Complete!

Get Tomcat related Information
after Successful Installation!!!

[root@localhost
~]#

 

[root@localhost ~]# yum info tomcat6

Loaded plugins: fastestmirror, refresh-packagekit, security

Loading mirror speeds from cached hostfile

Installed Packages

Name: tomcat6

Arch: noarch

Version:6.0.24

Release: 45.el6

Size: 188 k

Repo:installed

From repo:base

Summary:Apache Servlet/JSP Engine, RI for Servlet 2.5/JSP 2.1 API

URL: http://tomcat.apache.org/

License: ASL 2.0

Description : Tomcat is the servlet container that is used in the official Reference :
Implementation for the Java Servlet and JavaServer Pages technologies. :
The Java Servlet and JavaServer
Pages specifications are developed by :
Sun under the Java Community Process.:: Tomcat is developed in an open and participatory environment and : released under the Apache Software License version 2.0. Tomcat is intended : to be a collaboration of the best-of-breed developers from around the world.

[root@localhost ~]#

================================================================================

Posted in How To...

Create a Local Yum Repository in CentOS 6.3 in 5 steps


Create a Local Yum Repository in CentOS 6.3 in 5 steps

1) Install CentOS 6.3 -> How to install CentOS 6.3 ; In CentOS6.3 Desktop Installation, Apache is installed in built. Verify

Cloud Computing – Download Free EBooks and Whitepapers
Java – Download Free EBooks and Whitepapers
Windows – Download Free EBooks and Whitepapers
Apache status in CentOS 6.3
Apache status in CentOS 6.3

2) Insert DVD/ISO into DVD-Drive. 3) Create Directory with mkdir -pv /var/www/html/centos/6.3/i386/RPMS/ and copy all RPM files from the DVD (Part-I, Part-II)

ifconfig - verify the IP Address of the Machine
ifconfig – verify the IP Address of the Machine

cp /var/www/html/centos6.3/i386/createrepo* /tmp/repo/

cp /var/www/html/centos6.3/i386/deltarpm* /tmp/repo/cp /var/www/html/centos6.3/i386/python-deltarpm* /tmp/repo/cp /var/www/html/centos6.3/i386/libxml2-python* /tmp/repo/
RPMs needed to run create Repository command createrepo
RPMs needed to run create Repository command createrepo
Run the RPMs
RPMs needed to run create Repository command createrepo 1
RPMs needed to run create Repository command createrepo 1
[root@localhost admin]# rpm-ivh /tmp/repo/deltarpm-3.5-0.5.20090913git.el6.i686.rpm
[root@localhost admin]# rpm -ivh /tmp/repo/python-deltarpm-3.5-0.5.20090913git.el6.i686.rpm[root@localhost admin]# rpm -ivh /tmp/repo/libxml2-python-2.7.6-4.el6_2.4.i686.rpm [root@localhost admin]# rpm -ivh /tmp/repo/createrepo-0.9.8-5.el6.noarch.rpm
createrepo - Create repomd (xml-rpm-metadata) repository
createrepo  is a program that creates a repomd (xml-based rpm metadata)
       repository from a set of rpms.
4) [root@localhost admin]# createrepo /var/www/html/centos6.3/i386/
createrepo command
createrepo command

[root@localhost admin]# createrepo /var/www/html/centos6.3/i386/2559/4776 – php-tidy-5.3.3-3.el6_2.8.i686.rpm

iso-8859-1 encoding on Ville Skytt� <ville.skytta@iki.fi> – 2.8.24776/4776 – diffutils-2.8.1-28.el6.i686.rpm
Saving Primary metadata Saving file lists metadata Saving other metadata [root@localhost admin]#

Use Rsync to create the updates-released repository (Not tried) 5) Change baseurl as per assigned IP address or use Localhost; Make sure that you change baseurl in all sections in the /etc/yum.repos.d/CentOS-Base.repo file (Hint: You need to make sure that baseurl is correct else it will give error for repodata/repomd.xml file; If createrepo command will run successfully then this directory along with files will be created where all RPMs are located or where you have created repository. ).

edit -etc-yum.repos.d-CentOS-Base.repo
edit -etc-yum.repos.d-CentOS-Base.repo

Done!!!