Will the clouds save Novell in a way that Linux has not yet done? The company certainly hopes so. Today, the company is kicking out its Cloud Manager tool, which has been under development for more than a year. Novell built itself a tidy little $2bn business from networking x86-based servers in the 1980s and 1990s, but for a lot …
Since clouds by their very definition is vapor, this MUST be vaporware...
A Question of Board Novell
"The Cloud Manager stack uses SOAP-based APIs for create the Web services that link into hypervisors and their respective consoles and uses standard Internet protocols for communication."
That sentence needs to be rewritten to make any sense at all.
And it can be rewritten in two ways, each of which tells a similar, and some would even say identical, leading story.
The Cloud Manager stack uses SOAP-based APIs for the Web to create services that link into hypervisors and their respective consoles and uses standard Internet protocols for communication.
The Cloud Manager stack uses SOAP-based APIs for services to create the Web that link into hypervisors and their respective consoles and uses standard Internet protocols for communication.
Both of them though require the same thing of the Cloud Manager ..... a Chief Virtual Operating System Officer to Provide Novel Intellectual Property for Reign and Perfect Tempest Storms*. A Must Have Control Operative for any and all Self Respecting, Model Empire, Future Builders.
Now if that is what Novell Cloud Management is all about ..... Remote Virtualised Control/CyberSpace Control of Earthed Governance Functions, Facilities and Utilities ..... then is the Future Guaranteed a NEUKlearer HyperRadioProActive CHAOS Order with Clouds Hosting Advanced Operating Systems.
And do you think it is a Post Modernist Capitalist Order of Swiss DNAI too .... for Dynamic Neutral Applications of Intelligence which Favours and dDelivers Excellence to All in this Age of Virtualisation?
* Tempest/TEMPEST is a Sublime Facility thought able to compromise Utilities. The exact nature of whatever it is thought to be able to provide are never disclosed for reasons of considerable overwhelming wealth advantage and international security presumably.
The other reason...
There was another reason for Novells' decline--price gouging. I maintained NetWare servers in the '90s, and remember submitting $3,500 requisitions--for a NW3 TCP/IP stack. That was _in addition_ to the OS itself. With NT 4.0 going for ~ $1100 (TCP/IP included) at the time, it's no wonder they lost market share.
The fact that NetWare was rock solid and NT 4.0 was BSODing crap was lost on management, who only looked at the price.
I hope they watch their back....
I have been playing in the x86/x64 virtualizaiton space for a while now (ten years), longer on other platforms. As such, I keep track of who's doing what to which system and how. In this case, Novell had better keep a weather eye on Microsoft since SCVMM (System Center Virtual Machine Manager) is already set up to work with Hyper-V and ESX. Extending it to manage Azure is a no brainer. I know Novell is supposed to have some relationship with Microsoft but I wouldn't put too much reliance on it. While the notion of an über-orchestrator appeals to anyone who must manage a heterogeneous virtualization environment, I do wonder what the final cost will be, over and above the individual virtualization solution consoles.
It would be far better if Novell's tool manipulated systems directly but they may have avoided that for now rather than throw down a gauntlet. Finally an interesting space to watch now.