"Jitterbit makes it clear: Open Source is Enterprise-ready... providing powerful integration at a fraction of the cost of proprietary competitors."
Jitterbit is the Integration Solution of choice for over 5,000 organizations, with customers including Continental Airlines, NASA, and Balfour Beatty Construction.
Whether you're connecting legacy systems, enterprise applications or On-Demand data in the cloud, Jitterbit is designed to simplify even the most complex integration challenges.
Integration Solutions Simplified:
Application Integration
Reduce complexity and dramatically improve reliability, flexibility, and scalability by tying together distributed and incompatible applications and systems. Learn More!
Cloud/SaaS Integration
Realize the true value of your Software-as-a-Service investments by securely and reliably connecting data beyond your firewall with your on-premise infrastructure. Learn More!
ETL & Data Integration
The most critical part of a successful Business Intelligence infrastructure. Retrieve and process data for analysis and reporting quickly, reliably, and accurately. Learn More!
Combining its SIP core capabilities and extensible APIs, building VoIP and Unified Communication Platforms using Kamailio (K) is straightforward.
Some of the features that Kamailio offers:
Robust and Performant SIP (RFC3261) Server flavours
Registrar server
Location server
Proxy server
SIP Application server
Redirect server
Flexibility
small footprint – suitable for embedded devices – the binary file is small size, functionality can be stripped/added via modules
plug&play module interface – ability to add new extensions, without touching the core, therefore assuring a great stability of core components
modular architecture – core, internal libraries and module interface to extend the server’s functionality
impressive extension repository – overall 150 modules are included in the Kamailio source tree
SIP Routing Capabilities
stateless and transactional stateful SIP Proxy processing
serial and parallel forking
NAT traversal support for SIP and RTP traffic
load balancing with many distribution algorithms and failover support
flexible least cost routing
routing failover
replication for High Availability (HA)
Transport Layers
support for communication via UDP, TCP, TLS and SCTP
IPv4 and IPv6
transport layer gatewaying (IPv4 to IPv6, UDP to TLS, a.s.o.)
SCTP multi-homing and multi-streaming
Asynchronous Processing
asynchronous TCP handling
asynchronous SIP message processing
asynchronous inter-process message queues communication system
Secure Communication
Digest SIP User authentication
Authorization via ACL or group membership
IP and Network authentication
TLS support for SIP signaling
transparent handling of SRTP for secure audio
TLS domain name extension support
authentication and authorization against database (MySQL, PostgreSQL, UnixODBC, BerkeleyDB, Oracle, text files), RADIUS and DIAMETER
IP and DNS
support for SRV and NAPTR DNS lookups
SRV DNS failover
ENUM support
internal DNS caching system – avoid DNS blocking
IP level Blacklists
multi-homed and multi-domain support
topology hiding – hide IP addresses in SIP headers to protect your network architecture
Accounting
event based accounting
configurable accounting data details
multi-leg call accounting
storage to database, Radius or Diameter
Configuration File
scripting language for configurations file. With a syntax similar to scripting languages, the configuration offers a powerful and flexible way to deploy custom SIP services.
pseudo-variables to access and manage parts of the SIP messages and attributes specific to users and server
transformations to modify existing pseudo-variables, accessing only the wanted parts of the information
over 1000 parameters, variables and functions exported to config file
runtime update framework – to avoid restarting the SIP server when needing to change the config parameters
External Interaction via
text-based management interface via FIFO file, udp, xmlrpc and unix sockets
RPC control interface – via XMLRPC, UDP or TCP
Rich Communication Services
SIP SIMPLE Presence Server (rich presence)
Presence User Agent
XCAP support
Presence DialogInfo support – SLA/BLA
Instant Messaging
Monitoring and Troubleshooting
SNMP – interface to Simple Network Management Protocol
config file step-by-step debugger
remote control via XMLRPC
internal statistics exported via RPC and SNMP
flexible debug and error message logging system – log custom messages including any header or pseudo-variable and parts of SIP message structure.
Extensibility APIs
Perl Programming Interface – embed your extensions written in Perl
Java SIP Servlet Application Interface – write Java SIP Servlets to extent your VoIP services and integrate with web services
Lua Programming Interface
Python Programming Interface
Multiple Database Backends
(MySQL, PostgreSQL, UnixODBC, BerkeleyDB, Oracle, text files) and other database types which have unixodbc drivers
connections pool
different backends can be used at same time (e.g., accounting to Oracle and authorization against MySQL)
Interconnectivity
straightforward interconnection with PSTN gateways
gateway to sms or xmpp and other IM services
interoperability with SIP enabled devices and applications such as SIP phones (Snom, Cisco, etc.), Media Servers (Asterisk, FreeSwitch, etc.)
Miscellaneous
CPL – Call Processing Language (RFC3880)
Internal generic caching system
Memcached connector
CLI – kamctl and sercmd
Web Management Interface: Siremis
Extensive documentation for both administrators and developers
Scalability:
Kamailio can run on embedded systems, with limited resources – the performances can be up to hundreds of call setups per second
used as load balancer in stateless mode, Kamailio can handle over 5000 call setups per second
on systems with 4GB memory, Kamailio can serve a population over 300,000 online subscribers
System can easily scale by adding more Kamailio servers
Kamailio can be used in geographic distributed VoIP platforms
Kamailio least-cost-routing scales up to millions of routing rules
With the new 4.5 version of the openQRM Data-Center Management and Cloud Computing platform the openQRM team archived another milestone for the project. Next to lots of new features the most visible updates are the new Data-Center Summary start page (screenshot above), a "Visual Cloud Designer" (VCD) and the re-worked UI for all plugins in openQRM.
The new start page gives a lot of useful informations like the load of the complete Data-Center and the consumption of each subsystem plus peaks and trends. Very helful for performance tuning and finding bottle-necks.
Another eye-catcher in openQRM 4.5 is of course the "Visual Cloud Designer". It provides a user friendly drag-and-drop UI to request new systems from the openQRM Cloud by selecting the individual components like VM-type, CPU and Netwwork-card count, server-templates, SLA's, HA, etc. and visually constructing them to a new Cloud system. It feels like the "shopping basket for system-administrator", just pick what you need.
Please find more details about how the openQRM VCD works and looks in our teaser video "Cloud Computing in 5 minutes". Some more highlights of openQRM 4.5 :
A new plugin now integrates with Dell Equallogic Storage to support direct deployment of physical systems or virtual machines from the Equallogic Iscsi Target and to take advantage of its ultra fast SAS disk array
Next to Nagios2 and Nagios3 Zabbix is now the third system- and service-monitoring option available in openQRM 4.5.
With the "Cloud NAT" feature one can hide an openQRM Cloud within a private subnet via network-address-translation (NAT). It enables to run the openQRM Cloud independent from the hosting-providers setup
The automated billing system in the openQRM Cloud was made plug-able and now supports custom calculations including external data-sources
An updated NetApp-plugin connects NetApp Storages with openQRM and provides an automated storage management for using NetApp Filers as Cloud-Storage (tested with ONTAP 7.0)
The Citrix XenServer plugin got re-implemented and is now the 6. virtualization technology supported by openQRM (tested with Citrix XenServer 5.5.0).
With its unique and generic Data-Center abstration layer openQRM is one of the very few solutions which seamlessly supports multiple virtualization technologies
(Xen, KVM, Citrix XenServer, VMware Server 1 + 2, VMware ESX ) plus physical systems.
When it comes to fully dynamic and automated provisioning including P2V ("physical to virtual"), V2P ("virtual to physical") and also V2V ("virtual type A to virtual type B") migration you should definitely take a look at openQRM.
The openQRM Team also provides a free Demo of the openQRM Cloud at : http://www.openqrm.com/?q=node/150
Please download the new 4.5 version of openQRM at Sourceforge.net
oVirt is a virtualization management framework constisting of a small host image, the oVirt Node, that provides the libvirt service to host virtual machines, and a robust vm management software stack, controlled by a web-based management interface, the oVirt Server. This stack provides pxe and other automated vm boot / appliance solutions; various vm operations, task, vnc, and other access; and a secure authentication based on freeIPA.
Current the oVirt Node runs KVM. Patches are welcome to support other hypervisors and work will be underway to support Xen based Nodes in the near future
The Linux KVM hypervisor is gaining steam in the cloud computing market, with two major vendors using the virtualization software to create cloud platforms to compete against Amazon's popular EC2 service.
IBM announced in March that its test-and-dev cloud service uses KVM (Kernel-based Virtual Machine), and now hosting company The Planet has built a cloud service using a version of KVM.
While KVM isn't on the verge of supplanting VMware, Microsoft or the open source Xen hypervisor in the enterprise, Planet officials say KVM offers numerous advantages in commercial cloud offerings.
KVM is easier for Linux developers to use than Xen because "Xen was never really integrated into Linux," says Carl Meadows, senior manager of product marketing for The Planet. "It sits outside Linux as a separate microkernel." KVM, meanwhile, "was built directly into Linux and uses Linux as the host … The KVM is much simpler and more elegant than Xen."
KVM's integration into Linux makes it easier to get patches out to customers, whereas deploying patches from a separate virtualization software requires more legwork, he says. Also, KVM helps The Planet give its cloud customers freedom to customize the kernel running on their virtual servers, while the portability of the software allows virtual machines to be easily migrated to physical servers and vice versa, he says.
"Since KVM operates natively, it's a lot easier for us to create a dynamic hybrid environment than it would be with Xen," Meadows says.
The Planet runs seven co-location data centers worldwide and has 20,000 customers running 15 million Web sites. More than 80% of its customers already use Linux.
But The Planet is a newcomer to the cloud computing space, which consists of virtualized server instances and on-demand storage rather than dedicated hardware. The Planet's cloud service is in public beta and is running more than 500 virtual servers on Intel Nehalem-based dual-core machines shipped by Dell.
Amazon EC2, a giant in the cloud computing market, uses Xen virtualization, but Meadows says he believes KVM will be the open source hypervisor of choice in the long term, and points to IBM's recent deployment to support his argument.
While The Planet uses KVM running on Ubuntu, IBM adopted the Red Hat-branded version of KVM. Red Hat and KVM seem to have won another endorsement from Novell, which said it will support KVM in version 11 of SUSE Linux Enterprise Server.
But Novell still supports Xen, of course, and Citrix CTO Simon Crosby writes in his blog that Novell's support of KVM is to be expected because KVM comes with the mainline Linux kernel.
Citrix, which purchased XenSource in 2007, is the key vendor in the Xen community, but Crosby acknowledges that KVM has some advantages.
"It's important to realize that for a Linux vendor, KVM significantly simplifies the engineering, testing and packaging of the distro," Crosby writes. "KVM is a driver in the kernel, whereas Xen … requires the vendor to pick a particular release of Xen and its tool stack, and then integrate that with a specific kernel.org kernel, and exhaustively test them together -- rather than just getting a pre-integrated kernel and hypervisor from kernel.org."
But ultimately, user preferences are what matter, Crosby continues. Xen wins out, he writes, in part because it offers compatibility with multiple operating systems and hypervisors.
"If the use case involves the customer buying, installing and running Linux to achieve virtualization, KVM will eventually do a fine job," Crosby writes. "If on the other hand, the user expects to deploy a virtualization platform that is entirely guest OS agnostic, using a complete virtual infrastructure platform then a type-1 hypervisor that is OS agnostic … is what they will go for."
Although Citrix has a strong partnership with Microsoft, Crosby writes that relying on an operating system vendor is problematic because "no OS vendor has yet done a good job of virtualizing its competitors' products, and indeed strategically is never likely to do so."
In the case of The Planet, the debate is less Xen-vs-KVM than it is Xen-vs.-VMware. The Planet offers a managed hosting service that uses VMware in addition to its KVM-based public cloud.
VMware is popular with customers looking to The Planet to host a private cloud because they are often running VMware internally to begin with. KVM does have many of the major features that VMware does, including live migration and RAM deduplication, Meadows says. KVM's development also moves faster than VMware's because of the open source community, but KVM is still way behind in management tools, one of the main reasons VMware is more expensive than rival virtualization software.
"KVM management tools are non-existent compared to VMware's," Meadows says.
To create a local ISO Repository for XenServer you can use any directory on the filesystem. The Problem is that the Operating System has normally about 2GB free space left which is too less.
To use the "Local Storage" LVM space you can do it in the following way:
Create LVM Space for ISO Repository
First create a LVM, in this example I use 50GB for ISO space:
# lvcreate -L 50G -n ISO VG_XenStorage-4f9efb1c-2dde-777b-bebf-1f73e99e104c
Please note that your Volume Group is named differentially. To figure out your VG name do the following:
# pvscan
PV /dev/md2 VG VG_XenStorage-4f9efb1c-2dde-777b-bebf-1f73e99e104c lvm2 [458.11 GB / 298.11 GB free]
Total: 1 [458.11 GB] / in use: 1 [458.11 GB] / in no VG: 0 [0 ]
This example works for RedHat and CentOS, the instructions are slightly different for SLES and Debian.
As a condition for paravirtualization to work, a kernel that supports the Xen hypervisor needs to be installed and booted in the virtual machine.
Installing the XenServer Supported Kernel:
1. After importing the vm as HVM, boot the virtual machine and open the console.
2. (optional) update the modules within the vm to the latest revision
a. If the kernel-xen package is installed from an online repository – best practice is to fully update the distribution to avoid problems between package build revisions.
3. Install the Linux Xen kernel.
a. yum install kernel-xen and follow Step 7 , 8 and 9 to boot new kernel.
i. the xen aware kernel is installed and entries are created in grub but you should follow step 7 , 8 and 9 .
4. Build a new initrd without the SCSI drivers and with the xen PV drivers
a. cd /boot
b. mkinitrd --omit-scsi-modules --with=xennet --with=xenblk --preload=xenblk initrd-$(uname -r)xen-no-scsi.img $(uname -r)xen
i. This builds a new initrd for booting with pygrub that does not include SCSI drivers which are known to cause issues with pygrub and Xen virtual disk devices.
5. Modify the grub boot loader menu (the default entries are not pygrub compatible)
Open /boot/grub/menu.lst in the editor of your choice
a. Remove the kernel entry with ‘gz’ in the name
b. Rename the first “module” entry to “kernel”
c. Rename the second “module” entry to “initrd”
i. SuSE and Debian require that entries that point to root device locations described by a direct path such as: “/dev/hd*” or “/dev/sd*” be modified to point to /dev/xvd*
d. Correct the *.img pointer to the new initrd*.img created in step 4
e. (optional) Modify the title of this entry
f. Edit the line “default=” to point to the modified xen kernel entry
i. The entries begin counting at 0 – the first entry in the list is 0, the second entry is 1 and so on
ii. In our example the desired default entry “0”
g. (optional) Comment the “hiddenmenu” line if it is there (this will allow a kernel choice during boot if needed for recovery)
h. Save your changes
6. Shut down the guest but do not reboot.
a. Shutdown now -h
Edit the VM record of the CentOS VM to convert it to PV boot mode
In this example the VM is named “centos”
7. From the console of the XenServer host execute the following xe commands:
a. xe vm-list name-label=centos params=uuid(retrieve the UUID of the vm)
b. xe vm-param-set uuid= HVM-boot-policy="" (clear the HVM boot mode)
c. xe vm-param-set uuid= PV-bootloader=pygrub (set pygrub as the boot loader)
d. xe vm-param-set uuid= PV-args="console=tty0 xencons=tty"
(set the display arguments)
i. Other possible options are: “console=hvc0 xencons=hvc” or “console=tty0” or “console=hvc0”
8. xe vm-disk-list uuid= (this is to discover the UUID of the interface of the virtual disk)
9. xe vbd-param-set uuid= bootable=true (this sets the disk device as bootable)
The vm should now boot paravirtualized using a Xen aware kernel.
When booting the virtual machine, it should start up in text-mode with the high-speed PV kernel. If the virtual machine fails to boot, the most likely cause is an incorrect grub configuration; run the xe-edit-bootloader (i.e. xe-edit-bootloader –n centos) script at the XenServer host console to edit the grub.conf of the virtual machine until it boots.
Note: If the VM boots and mouse and keyboard control does not work properly, closing and re-opening XenCenter generally resolves this issue. If the issue is still not resolved, try other console settings for PV-args, being sure to reboot the vm and close and re-open XenCenter between each setting change. Installing the XenServer Tools within the virtual machine:
Install the XenServer tools within the guest:
1. Boot the paravirtualized VM (if not already running) into the xen kernel.
2. Select the console tab of the VM
3. Select and right-click the name of the virtual machine and click "Install XenServer Tools"
4. Acknowledge the warning.
5. At the top of the console window you will notice that the "xs-tools.iso" is attached to the DVD drive. And the Linux device id within the vm.
6. Within the console of the virtual machine:
a. mkdir /media/cdrom (Create a mount point for the ISO)
b. mount /dev/xvdd /media/cdrom (mount the DVD device)
c. cd /media/cdrom/Linux (change to the dvd root / Linux folder)
d. bash install.sh (run the installation script)
e. answer “y” to accept the changes
f. cd ~ (to return to home)
g. umount /dev/xvdd (to cleanly dismount the ISO)
h. In the DVD Drive, set the selection to “”
i. reboot (to complete the tool installation)
7. Following reboot the general tab of the virtual machine should report the Virtualization state of the virtual machine as “Optimized”
Note :: Sometimes you find two vbd values , you need to set one Virtual Block Devices (VBDs) bootable if there are more than one .
Reverse the bootable option if your VM not working properly and edit /boot/grub/menu.lst
In computing, paravirtualization is a virtualization technique that presents a software interface to virtual machines that is similar but not identical to that of the underlying hardware.
The intent of the modified interface is to reduce the portion of the guest's execution time spent performing operations which are substantially more difficult to run in a virtual environment compared to a non-virtualized environment. The paravirtualization provides specially defined 'hooks' to allow the guest(s) and host to request and acknowledge these tasks, which would otherwise be executed in the virtual domain (where execution performance is worse.) Hence, a successful paravirtualized platform may allow the virtual machine monitor (VMM) to be simpler (by relocating execution of critical tasks from the virtual domain to the host domain), and/or reduces the overall performance degradation of machine-execution inside the virtual-guest.
Paravirtualization requires the guest operating system to be explicitly ported for the para-API -- a conventional O/S distribution which is not paravirtualization-aware cannot be run on top of a paravirtualized VMM. However, even in cases where the operating system cannot be modified, components may be available which confer many of the significant performance advantages of paravirtualization; for example, the XenWindowsGplPv project provides a kit of paravirtualization-aware device drivers, licensed under GPL, that are intended to be installed into a Microsoft Windows virtual-guest running on the Xen hypervisor.
There’s still a lot of work to do before it’s available for public consumption, but that’s all the proof we need for now. For those of you lucky enough to have your hands on one of the 700.000 iPad’s sold on launch day, it wont be long before you can start applying your own themes, sounds, and a whole host of other things I’m sure will become available soon after it’s out there for the masses
Fring
Put the video call functionality to nokia device include e72 , now am gonna do video call , we started rolling out video call support for more devices over the last few weeks.
And good news! Nokia E72 & E75 (and all other Symbian 9.3) users who can also video call with their friends on fring and Skype for free!
Vyatta's open, software-based approach to networking has created a complete network OS that can connect and secure physical networks as well as virtual and cloud computing infrastructures. Vyatta software and appliances offer users a flexible, affordable alternative to proprietary, hardware-based routers, firewalls, VPN concentrators and intrusion prevention devices.
Vyatta can help you:
Affordably scale large BGP implementations
Keep your network safe with a stateful-inspection firewall
Securely connect remote offices with VPN
Scale from DSL to 10-Gbps with a single software package
Avoid costly proprietary networking upgrades
Run virtualized networking environments in Xen and VMware
Add networking and security to blade servers in your data center
Offer network-based managed security services
Add network redundancy regardless of vendor equipment
Build your own best-of-breed Branch office solution
The next system software update for the PlayStation 3 (PS3) system will be released on April 1, 2010 (JST), and will disable the “Install Other OS” feature that was available on the PS3 systems prior to the current slimmer models, launched in September 2009. This feature enabled users to install an operating system, but due to security concerns, Sony Computer Entertainment will remove the functionality through the 3.21 system software update.
In addition, disabling the “Other OS” feature will help ensure that PS3 owners will continue to have access to the broad range of gaming and entertainment content from SCE and its content partners on a more secure system.
Consumers and organizations that currently use the “Other OS” feature can choose not to upgrade their PS3 systems, although the following features will no longer be available;
Ability to sign in to PlayStation Network and use network features that require signing in to PlayStation Network, such as online features of PS3 games and chat
Playback of PS3 software titles or Blu-ray Disc videos that require PS3 system software version 3.21 or later
Playback of copyright-protected videos that are stored on a media server (when DTCP-IP is enabled under Settings)
Use of new features and improvements that are available on PS3 system software 3.21 or later
For those PS3 users who are currently using the “Other OS” feature but choose to install the system software update, to avoid data loss they first need to back-up any data stored within the hard drive partition used by the “Other OS,” as they will not be able to access that data following the update.
PSP 6.20 firmware save game exploit has been released leaked by Malloxis, something he wasn’t meant to do till the eLoader is good and ready. Anyway we know now the demo, its Patapon 2 and we also have Wololo’s hello world to go with it. I’ve tested this and it works fine, Hello world running right there on my PSP Go. Homebrew is just a step away? Or is it? We hope the actions of one person doesn’t effect an eLoader been made for this 6.20 save game exploit.
Here’s what you have to do to get it running on your PSP Go, Copy the edited save game UCUS98732_DATA02 folder to your save game data and then the demo to PSP/GAME on your mass memory. Remember to copy over the whole folder UCUS98734. Now the binary h.bin needs to be placed in your mass memory root.
