By User12608550-Oracle on Sep 23, 2012
So You Want To Build a SPARC Cloud
Oracle Solaris 11 System Administration - The Complete Reference
by Michael Jang, Harry Foxwell, Christine Tran, and Alan Formy-Duval
The well-known characteristics and tiers of cloud computing have spawned myriad implementations by a host of vendors and system integrators. One of these, Oracle's Exalogic Elastic Cloud, part of Oracle's family of Engineered Systems, is a key component of Oracle's public and private cloud computing solutions, providing critical PaaS (Platform as a Service) features for cloud developers. These developers need guidance to take advantage of Exalogic's extensive capabilities, and the Oracle Exalogic Elastic Cloud Handbook, written by three highly experienced Oracle technologists, provides that guidance.
Part One of the book covers Exalogic's hardware and software components, and includes a very useful chapter on deployment examples, describing best practices for scalabiity, availability, backup and recovery, and multi-tenant security, including integration with other Oracle Engineered Systems and products such as Exadata and storage subsystems.
Part Two is a thorough guide to Exalogic installation features, configuration and monitoring, packaged application software management, and scalable application development.
The book also provides an extensive list of online resources, including pointers to Web sites, whitepapers, instructional videos, and other Oracle documentation.
So, if you're planning to implement Exalogic as part of your cloud infrastructure, or are considering such, you'll find lots of sage advice and best practices in this handbook.
We often focus on server virtualization when we discuss cloud computing, but just as often we neglect to consider some of the critical implications of that technology. The ability to create virtual environments (or VEs ) means that we can create, destroy, activate and deactivate, and more importantly, MOVE them around within the cloud infrastructure. This elasticity and mobility has profound implications for how network services are defined, managed, and used to provide cloud services. It's not just servers that benefit from virtualization, it's the network as well.
Network virtualization is becoming a hot topic, and not just for discussion but for companies like Oracle and others who have recently acquired net virtualization companies [2,3]. But even before this topic became so prominent, Solaris engineers were working on technologies in Solaris 11 to virtualize network services, known as Project Crossbow .
And why is network virtualization so important? Because old assumptions about network devices, topology, and management must be re-examined in light of the self-service, elasticity, and resource sharing requirements of cloud computing infrastructures. Static, hierarchical network designs, and inter-system traffic flows, need to be reconsidered and quite likely re-architected to take advantage of new features like virtual NICs and switches, bandwidth control, load balancing, and traffic isolation. For example, traditional multi-tier Web services (Web server, App server, DB server) that share net traffic over Ethernet wires can now be virtualized and hosted on shared-resource systems that communicate within a larger server at system bus speeds, increasing performance and reducing wired network traffic. And virtualized traffic flows can be monitored and adjusted as needed to optimize network performance for dynamically changing cloud workloads. Additionally, as VEs come and go and move around in the cloud, static network configuration methods cannot easily accommodate the routing and addressing flexibility that VE mobility implies; virtualizing the network itself is a requirement.
Oracle Solaris 11  includes key network virtualization technologies needed to implement cloud computing infrastructures. It includes features for the creation and management of virtual NICs and switches, and for the allocation and control of the traffic flows among VEs . Additionally it allows for both sharing and dedication of hardware components to network tasks, such as allocating specific CPUs and vNICs to VEs, and even protocol-specific management of traffic.
So, have a look at your current network topology and management practices in view of evolving cloud computing technologies. And don't simply duplicate the physical architecture of servers and connections in a virtualized environment…rethink the traffic flows among VEs and how they can be optimized using Oracle Solaris 11 and other Oracle products and services.
 I use the term "virtual environment" or VE here instead of the more commonly used "virtual machine" or VM, because not all virtualized operating system environments are full OS kernels under the control of a hypervisor…in other words, not all VEs are VMs. In particular, VEs include Oracle Solaris zones, as well as SPARC VMs (previously called LDoms), and x86-based Solaris and Linux VMs running under hypervisors such as OEL, Xen, KVM, or VMware.
 Oracle follows VMware into network virtualization space with Xsigo purchase; http://www.mercurynews.com/business/ci_21191001/oracle-follows-vmware-into-network-virtualization-space-xsigo
 Oracle Buys Xsigo; http://www.oracle.com/us/corporate/press/1721421
 Oracle Solaris 11 Networking Virtualization Technology, http://www.oracle.com/technetwork/server-storage/solaris11/technologies/networkvirtualization-312278.html
 Oracle Solaris 11; http://www.oracle.com/us/products/servers-storage/solaris/solaris11/overview/index.html
 For example, the Solaris 11 'dladm' command can be used to limit the bandwidth of a virtual NIC, as follows: dladm create-vnic -l net0 -p maxbw=100M vnic0
Canada: Building "Service Canada" cloud for all citizen services, but raised the issue of data location...cloud data must be within Canada border, so they will not focus on public clouds where they don't know or can't control data location.
Japan: In response to the massive destruction of the Great East Japan Earthquake, Japan is building nation-wide cloud services to support disaster relief, data recovery, and support for rebuilding new communities.
US Ambassador Philip Verveer discussed the need for international cooperation and standards development to enable interoperability of cloud services, keeping in mind cultural and political differences. Additionally, an industry panel reported on cloud standards development, including some actual interoperability testing at http://www.cloudplugfest.org. Much of the first two days of the workshop covered progress and action plans around the 10 High-Priority Requirements to Further USG Agency Cloud Computing Adoption.
Thursday's sessions will cover the work of the various NIST Cloud Computing Working Groups on
Oracle's recently introduced Solaris 11 has been touted as "The First Cloud OS". Interesting claim, but what exactly does it mean? To answer that, we need to recall what characteristics define a cloud and then see how Solaris 11's capabilities map to those characteristics.
By now, most cloud computing professionals have at least heard of, if not adopted, the National Institute of Standards and Technology (NIST) Definition of Cloud Computing, including its vocabulary and conceptual architecture. NIST says that cloud computing includes these five characteristics:
For cloud computing developers, add to that the next generation of Java, and you've got the NIST requirements covered. The results, or one of them anyway, are services like the new Oracle Public Cloud. And Solaris is the ideal platform for running your Java applications.
So, if you want to develop for cloud computing, for IaaS, PaaS, or SaaS, start with an operating system designed to support cloud's key requirements…start with Solaris 11.
There were international participants at the event, with much friendly discussion of "openness", "interoperability", and an idealistic "One Cloud" vision of a "Cloud Without Borders". A very hopeful perspective, but perhaps a bit overly optimistic one given the current political state of the world and various governments' control of Internet access and resources.
One issue that concerns me in all this rush to cloud computing is the question of where the expertise will come from to design, build, and manage massive cloud infrastructures? Concepts such as parallel programming, scalability, virtualization, and cache management need to be integrated into CS curricula from the start, maybe even starting in high school but certainly at the undergraduate level. I don't yet see sufficient emphasis on those areas in the CS courses and textbooks offered by many universities. Without a continuous stream of knowledgeable graduates, the lack of cloud computing experience and expertise will slow the adoption of this transformative technology.
Security and trust in the cloud remain primary concerns; the NIST Cloud Computing Security Working Group has released a draft publication outlining 17 key requirement areas for cloud security ( http://collaborate.nist.gov/twiki-cloud-computing/pub/CloudComputing/Documents/NIST_Security_Requirements_for_US_Government_Cloud.pdf ). Yet in spite of the current lack of mature security solutions and interoperability/development standards, it was still recommended that agencies start their cloud deployments with the expectation that expertise will evolve through experimentation, trial, and (inevitably) error.
Humans tend to attribute magical properties to things they don't understand. Throughout history, this tendency has often resulted in fear of technology, admittedly sometimes justified. Hollywood movies have exploited this fear for decades, creating frightening tales of radiation-induced monsters and maniacal computers.
Computing industry luminaries have addressed peoples' unease with rapidly advancing technology, sometimes with a cautionary, warning approach such as Bill Joy's widely read Wired article in April 2000, Why the future doesn't need us, and sometimes positive and optimistic like Ray Kurzweil's The Singularity is Near. I think each of these represent the extremes in thinking about the risks and benefits of technologies such as cloud computing.
The popular assumption often made about the evolution of machine intelligence is that we will create a form of computer consciousness vastly superior in every way to that of humans. But even after decades of research in cognitive science, AI, and brain modeling at such leading centers as the the Krasnow Institute, and the Santa Fe Institute, scientists are a very long way from creating even the simplest simulations of anything we could reasonably call consciousness in large, complex, massively-connected systems . And when they do, very likely they will produce the mental equivalent of a child, and will then have to deal with the issues of how conscious minds learn and grow, how they form opinions, beliefs, and biases, and how they make mistakes, to say nothing of how they self-maintain and self-repair, none of which we yet fully understand. Quite likely, we will not only create a very primitive kind of artificial consciousness, but along with it will come artificial stupidity, credulity, and other imperfections of the human mind.
So, no, the Cloud is not and is very unlikely to ever become Skynet. Nevertheless, I will continue to watch Hollywood's entertaining attempts to excite us with aliens, monsters, and crazy computers, and I will enjoy the dazzling special effects that modern computing enables. If I have any concerns at all, it's with our demonstrated inability to create absolutely reliable systems coupled with our increasing reliance on the Internet and the Cloud. Our complex, technology-dependent society has much more to fear from accidental and intentional connectivity failures and security issues than from any chance that the Cloud will become "self-aware".
But that's not all; JCP, the caretakers of the Java technical standards, recently approved the Java EE 7 Platform Java Specification Request which will enable Java EE applications to support the multi-tenant and elastic features required for cloud computing solutions. Oracle's developers and customers, along with those of IBM, Red Hat, and even SAP, are pleased to see the continuing evolution and support of Java technology into "the Cloud".
Hmmm..."Write Once, Run in the Cloud" has a nice ring to it, don't you think?
The purpose of this blog is to highlight and to explore general issues around "Cloud Computing" -- its benefits, risks, and component technologies -- and how they are evolving. I'll also periodically comment (of course!) on Oracle's Cloud Computing capabilities, resources, and cloud-related events. -- Harry J Foxwell, PhD, Principal Consultant for Cloud Computing, Oracle Public Sector HW