Skip to main content


How to increase the log retention in Orchestrator Server ( server.log)

When you are debugging the Orchestrator related issues in mid/large deployments , it is expected that the server.log file rotates rapidly.  In this case we need to increase the log file size and the rotation interval. Below are the steps to make changes to the config file to capture large number of files for troubleshooting.  Config File Location :  Appliance deployment:  /etc/vco/app-server/log4j.xml Windows deployment:  <install_Location>\app-server\conf\log4j.xml Steps:  1. Edit the file  log4j.xml 2. Locate the  <appender class="org.apache.log4j.RollingFileAppender" name="FILE">  section 3. Increase the size of the log file to 10 MB   <param name="MaxFileSize" value="10240KB"/>    4. Increase the  number files to be retained before rotation  <param name="MaxBackupIndex" value="5"/> Cheers :-) 

Configuring SNMP traps for the vCenter Server

Steps to configure the vCenter Server to generate SNMP traps: A.In the Home page of vSphere Client B.Select vCenter Server Settings  C.Select SNMP configuration D.Enable one of the SNMP receivers E. Provide the details for :  Receiver URL : Provide the host name of the Management Server (target SNMP server / monitoring tool) which will be connected to the VMware vCenter Server. (VMware vCenter Server sends the SNMP traps to this Management Server) Configure port 162 as the SNMP port. Community String: Provide community string (default string is "public")  SNMP versions v1/v2/v3 are supported That is all that is needed for the configuration.  Now you need to configure alarm for generating SNMP traps in the vCenter server. When ever there is a change in the environment ( host state change, VM state change ,etc) the trigger will be generated and send an alert to the monitoring server.  Configure the Alarms After you have setup the external SNMP server, v

Explore vsphere 6.0

VVols Perhaps the most wanted feature in vSphere 6 is Virtual Volumes, or VVOLs. VVOLs extends the VMware software-defined storage (SDS) story to its storage partners, and completely changes the way its hypervisor consumes storage; it radically changes how storage is presented, consumed and managed by the hypervisor. No longer is virtual machine (VM) storage bound by the attributes of the LUN, as each VM disk (VMDK) can have its own policy-driven SLA. VMware has a passel of storage vendors on board to equip its storage, with the ability to offer VVOLs storage to the VMware hypervisor. I'm sure this feature will get much press and customer attention in the coming days. vMotion vSphere vMotion just got 10 times better, and a lot more interesting. For one thing, it supports live VM migration  across vCenter servers, and over long distances. It used to support round trip times (RTTs) of 10 ms, but now supports RTTs of 100 ms. A ping from Portland, Ore., to Boston, Mass., is 90 ms;

Whats new in vSphere 6.0

Here is a list of feature comparison of 5.5 and 6.0

Cloud Computing ( Public vs Private cloud)

Today we had a (friendly ;-) ) conversation with my colleagues which moved to an argument about the cloud computing. We were discussing (arguing) about the types of cloud services and its pro's / con's which lead me to write this blog post.  The Cloud Computing is now a trend and a hot discussion in every IT group.  The reason behind is that the cloud infrastructure can offer advantages over traditional datacenters in the areas of performance, scalability, and even security. There is a vast differences between private, public and hybrid clouds for enterprise. The type of cloud service is defined based on the types of data they store.  Sometimes these differences narrow, but each type of cloud has different levels of security and varying degrees of management. One may be more flexible or scalable, while another might be more affordable.  Here we’ll talk about private, public and hybrid cloud computing and some of their primary differences. What is a public cloud?  A pu

vVOLS (Virtual Volumes)

# Jagadeesh Devaraj #vVols I believe its a hot and trending topic now in internet. By now you guys might heard a lot about the vVols at VMworld 2014 or through various forums and the reason it is important to manage the end-to-end Infrastructure. The vVols takes cares of end-to-end Infra from compute of storage at the virtual machine (VM) and its VMDK ( vDisk) level. Virtualization meant VMs and vDisks are the unit of management at the compute layer. VMware® Virtual Volumes is meant to bridge the gap by extending the paradigm to storage specifically on VMware vSphere® deployments. What is vVols :  VVOLs is a provisioning feature for vSphere 6 that changes how virtual machines (VMs) are stored and managed. ( Information source : VVOLs is an out-of-band communication protocol between vSphere and storage. It allows VMware to associate VMs and vDisks with storage entities, and allows vSphere to offload some storage management functions, like provisioning of VM's

Cloud computing architecture

What is the use of defining cloud architecture? Cloud architecture is a software application that uses on demand services and access pool of resources from the cloud. Cloud architecture act as a platform on which the applications are built. It provides the complete computing infrastructure and provides the resources only when it is required. It is used to elastically scale up or down the resources according to the job that is being performed. How does cloud architecture overcome the difficulties faced by traditional architecture? Cloud architecture provide large pool of dynamic resources that can be accessed any time whenever there is a requirement, which is not being given by the traditional architecture. In traditional architecture it is not possible to dynamically associate a machine with the rising demand of infrastructure and the services. Cloud architecture provides scalable properties to meet the high demand of infrastructure and provide on-demand access to the user.

Introduction to Cloud Computing

What is Hypervisor in Cloud Computing and its types? The hypervisor is a virtual machine monitor (VMM) that manages resources for virtual machines. The name hypervisor is suggested as it is a supervisory tool for the virtual machines. There are mainly two types of hypervisors : • Type-1: the guest Vm runs directly over the host hardware, e.g Xen, Hyper-V, VmWare ESXi • Type-2: the guest Vm runs over hardware through a host OS, e.g Kvm, Oracle virtualbox Are Type-1 Hypervisors better in performance than Type-2 Hypervisors and Why? Yes the Type-1 Hypervisors are better in performance as compared to Type-2 hypervisors because Type-1 hypervisors does not run through a host OS, they utilize all resources directly from Host hardware. In cloud implementation Type-1 hypervisors are used rather than Type-2 because Cloud servers need to run multiple OS images and it should be noted that if OS images are run on host a OS as in case of Type-2, the resources will get wasted. What are

Cloud Computing interview questions and answers ( Career Ride)

How does cloud computing provides on-demand functionality? Cloud computing is a metaphor used for internet. It provides on-demand access to virtualized IT resources that can be shared by others or subscribed by you. It provides an easy way to provide configurable resources by taking it from a shared pool. The pool consists of networks, servers, storage, applications and services. What is the difference between scalability and elasticity? Scalability is a characteristic of cloud computing through which increasing workload can be handled by increasing in proportion the amount of resource capacity. It allows the architecture to provide on demand resources if the requirement is being raised by the traffic. Whereas, elasticity is being one of the characteristic provide the concept of commissioning and decommissioning of large amount of resource capacity dynamically. It is measured by the speed by which the resources are coming on demand and the usage of the resources. What are the

Hardware Virtualization-The Nuts and Bolts

Author:     Johan  De  Gelas Page 1 Introduction First dual-core in 2005, then quad-core in 2007: the multi-core snowball is rolling. The desktop market is still trying to find out how to wield all this power; meanwhile, the server market is eagerly awaiting the octal-cores in 2009. The difference is that the server market has a real killer application, hungry for all that CPU power: virtualization. While a lot has been written about the opportunities that virtualization brings (consolidation, hosting legacy applications, resource balancing, faster provisioning...), most publications about virtualization are rather vague about the "nuts and bolts". We talked to several hypervisor architects at VMWorld 2008. In this article, we'll delve a bit deeper as we look to understand the impact of virtualization on performance. Performance? Isn't that a non-issue? Modern virtualization solutions surely do not lose more than a few percent in performance, right? We'l