From: "Zoran Popović" <shoom013@gmail.com>
To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list"
<rhelv5-list@redhat.com>
Cc: smooge@gmail.com, ia64dave@gmail.com,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
t35t0r@gmail.com,
ia64 Fedora Core Development <fedora-ia64-list@redhat.com>,
Xen User-List <xen-users@lists.xensource.com>,
xen-ia64-devel@lists.xensource.com
Subject: Re: [rhelv5-list] Itanium support ...
Date: Tue, 16 Feb 2010 12:50:46 +0100 [thread overview]
Message-ID: <96b40cab1002160350l42ea51fcqb552769b8dea539e@mail.gmail.com> (raw)
In-Reply-To: <6b75ae111001160533l1913f4c3h2f1a00dd7c803db5@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3946 bytes --]
The problem is they won't start dying, they were made not to - it was meant
to support what (mission) critical business is ... but I am not here for
that.
I would like to hear, people, what do you think the future of commercial
linux distros on Itanium is one hand, and on the other - what is the future
of Xen in commercial distros ?
Is Xen going to be supported on Suse on Itanium in future ?
What #$%&! is going on ?
Red Hat is the most respectable player having linux as business model, and
so to say it is the leader in open source community. But it has given
confusing signals about Xen, and now Itanium. I should've understood better
what happened with cowboyhat linux and fedora ... nevertheless, what I have
is a comitted software vendor like SAP who supports open source (as much a
proprietary one can - SAP supports officially trend of moving from Unix to
Linux), and Oracle does, too (with Sun and human power involved in Xen on
ia64 additionally) - it is not a small thing to have official support for
Xen or KVM virtualization by a big name such as SAP, and many commercial
distros (they have to be like that because of the nature of the business)
including Red Hat and Suse. Now I find that HP supports on their highly
competitive BladeSystem matrix control software only VMWare, Hyper-V and
XenServer - KVM and Xen not even announced, while Red Hat is involved in
making Insight Orchestration Designer templates for RHEL, JBoss and stuff
(something like virtual appliances, but story is bigger than that) but not
with RHEV ?!?! Is that the price of abandoning Xen in RHEL6 (HP treats that
as a clear signal), and leaving Itanium after that was a bit scary ... I've
been browsing through SAP sd2tier, TPC-C and TPC-H benchmarks and now I am
even more convinced that something wrong is going on. I can understand that
market share is important, but different vendors (including SAP) obviously
have different perspectives (Intel has more or less equal income from ia64
and non-ia64, so it is here to stay !!!), and I won't tell now how it
actually looks like to me ... I think that HP lost good competitors, but
above all, I am afraid that important part of open source community is in a
bigger loss ... __"I feel blue"__ ...
ZP.
PS.
Just look what I have here, tell me what you think, and more is coming on
very soon:
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17592
2010/1/16 t35t0r <t35t0r@gmail.com>
> 2010/1/15 Zoran Popović <shoom013@gmail.com>:
> > I feel deceived :( ... Itanium is not going to be supported after March
> 2014
> > and in RHEL 6 ?!!?!?!! I know this probably is a bit late reaction, I
> have
> > also a SR open with this question and a business case officially
> documented
> > in my company (I can send it gladly to anyone interested) with proposal
> > based on RHEL and HP Integrity blades (Itanium). I will open another SR
> if
>
> Sure, I'm interested in looking at your business case. We have two SGI
> itanium altix 350's (8 node/16p total) and another with 2 nodes/4p and
> all I know is that replacement parts are expensive, the warranty
> contracts are expensive, and the systems are expensive, and they have
> a bigger rack and environmental footprint. The 1.5GHz 16p system has
> lower performance than a single node 16p 2.93GHz Xeon nehalem system
> (for our computational work loads). Let's just say we're not replacing
> the itaniums as the nodes start dieing. Ours used to run RHEL3 but SGI
> made us switch to SLES9 or 10, perhaps that's another option if you
> really want itanium support (don't know about novell's plans).
>
> In any case, even SGI's new "UV" large shared memory/many cores system
> uses nehalem CPUs.
>
> HTH
>
> _______________________________________________
> rhelv5-list mailing list
> rhelv5-list@redhat.com
> https://www.redhat.com/mailman/listinfo/rhelv5-list
>
[-- Attachment #1.2: Type: text/html, Size: 4607 bytes --]
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
next parent reply other threads:[~2010-02-16 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96b40cab1001151415k2cce0a95idea5fa9a7eca32b3@mail.gmail.com>
[not found] ` <6b75ae111001160533l1913f4c3h2f1a00dd7c803db5@mail.gmail.com>
2010-02-16 11:50 ` Zoran Popović [this message]
2010-02-16 12:23 ` [rhelv5-list] Itanium support Pasi Kärkkäinen
2010-02-16 12:36 ` Zoran Popović
[not found] ` <alpine.LRH.2.00.1002161510340.3203@ruoska.mthd.net>
[not found] ` <96b40cab1002160911y5e46a438y507a3ebceff388c3@mail.gmail.com>
[not found] ` <1266344761.10081.60.camel@iso-8590-lx>
2010-02-16 23:47 ` Zoran Popović
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96b40cab1002160350l42ea51fcqb552769b8dea539e@mail.gmail.com \
--to=shoom013@gmail.com \
--cc=fedora-ia64-list@redhat.com \
--cc=ia64dave@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rhelv5-list@redhat.com \
--cc=smooge@gmail.com \
--cc=t35t0r@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).