sun-on-sun may not be a hard-and-fast rule at sun, it certainly is part of the sun culture and norm. since i joined sun three years ago through the sevenspace acquisition, we have been taken every opportunities to practice "eat our own dog food" as we continue to invest in our sun managed operations platform.
prior to the acquisition, many of the sevenspace back-end core components were already running on sun hardware and solaris. java was also used extensively in engineering software. in addition, we also had a diverse range of heterogeneous technologies from dell, hp, ibm, redhat, emc and many others. here is the great sun-on-sun journey for managed operations so far:
prior to the acquisition, many of the sevenspace back-end core components were already running on sun hardware and solaris. java was also used extensively in engineering software. in addition, we also had a diverse range of heterogeneous technologies from dell, hp, ibm, redhat, emc and many others. here is the great sun-on-sun journey for managed operations so far:
- dell -> sun x64 based server for the controltower appliance (pdf)
- eclipse -> netbeans
- jboss -> sun java system application server
- oracle cluster -> sun solaris cluster
- sonic jms -> sun java system message queue
- redhat linux -> solaris 10
- emc -> sun storagetek disk system
this all sounds good and logical. so in addition to servicing its partners and customers, what do the sun managed operations people, process, technology and knowledge have to offer the rest of sun? how do we integrate the sun managed operations services to other exciting emerging sun products and services? how does sun IT operations use the sun managed operations technology and process to manage our own sun internal infrastructure?
more on this exciting topic later.
