Monday May 16, 2005 Wait and See
Not much of note in the match I refereed yesterday. The only incident which sticks is one where the team behind me (I worked on the sidelines yesterday for a change) thought I'd called a penalty on them, when in fact I'd called it on the other team. (Nothing to do with the fact that they were behind me, but because the sidelines are not involved in the play, the reactions are often bigger.) Of course, once they'd got the signals, they changed their tune a little. They got themselves all worked up because they instinctively reacted by jumping to a (wrong) conclusion. A little patience can help sometimes.Wait and see, guys. Wait and see
( May 16 2005, 03:32:27 PM BST ) Permalink Comments [0]
Oracle and Containers in Solaris 10
It's good to see changes in available technology reflected in how services are paid for by the people who pay my salary - the customer.Check out the document on partitioning available here. It talks about how a Solaris 10 Container is considered a "hard partitioning" technology for Oracle licensing purposes.
So long as your Solaris 10 Container is tied to a resource pool limited to a number of CPUs which is less than the total number in the server, you only have to license for the number of CPUs which can be in the resource pool, not the whole server.
Since Containers are available on any server running Solaris 10, you don't need a system capable of being partitioned in hardware in order to take advantage of this feature.
( May 16 2005, 03:11:43 PM BST ) Permalink Comments [4]
Sun-MS Interoperability
While not involved directly in the ongoing interoperability work, it is not hard to understand the benefits of having one definitive source of information on the network.If you're familiar with Solaris, you will be aware of the /etc/hosts and /etc/inet/hosts files, both of which are used to translate between IP addresses and host names. (The reason for having two is for reasons of Unix history.) Ignoring the ipnodes file which now exists in Solaris (and can complicate things further), the fact is that utilities on Solaris will access one or the other of the hosts files depending on their heritage and history. We want all of these utilities to have the same view of the network irrespective of the interface (i.e. the file in this case) that they use to access the information. In Solaris this is done by having /etc/hosts being a symbolic link to /etc/inet/hosts so that whichever interface you use to access the information, you end up going to the single central information source of /etc/inet/hosts (whether you know this or not - and do you really want to care anyway so long as you get the information you need).
Having the ability to access a single directory in a heterogeneous environment (which is an essential feature of a large data centre which has to support different workload types) is a useful thing to have. Hopefully we are getting closer to the day where customers can choose the best platform and application for the task at hand (as there is no "one size fits all" compute solution) without having to worry about how they are going to integrate with their existing infrastructure. Everything should just be able to talk to everything (assuming they have permission, of course 
).
( May 16 2005, 11:00:48 AM BST ) Permalink Comments [0]