On 6/13/2013 2:40 PM, Rick Troth wrote:
Or maybe a compiled smiucv should also be on the Downloads page?
...
I'll talk to Leland about shipping a prebuilt one, though
-- no need to force a toolchain install if not needed.
CORRECT.
And for "external facing" or "cloud" guests, it's important
>> Or maybe a compiled smiucv should also be on the Downloads page?
...
> I'll talk to Leland about shipping a prebuilt one, though
> -- no need to force a toolchain install if not needed.
CORRECT.
And for "external facing" or "cloud" guests, it's important to NOT
have the toolchain available.
> > 1) a section on setting up the CMS SSL server to provide secure
> management traffic transport.
> > 2) a section on enabling SMAPI and the use of smaclient to manipulate
> the images.
>
> We had talked about the SSL server early. Apparently this is a complicated
> install. Given the quantity
Chris,
> ./smaclient smiucv will compile it and place it in the current
directory.
Yes, that worked! Thanks.
For some reason, I thought that process was done auto-magically.
"Mike MacIsaac"
--
For LINUX-390 subscribe / signof
Of Michael
MacIsaac
Sent: Thursday, June 13, 2013 12:42 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: More words on "The Virtualization Cookbook" Redbook residency
David,
> 1) a section on setting up the CMS SSL server to provide secure
management traffic transport.
> 2) a section o
David,
> 1) a section on setting up the CMS SSL server to provide secure
management traffic transport.
> 2) a section on enabling SMAPI and the use of smaclient to manipulate
the images.
We had talked about the SSL server early. Apparently this is a
complicated install. Given the quantity of ma
help generate interest by a larger audience.
Kurt Acker
IBM Smarter Planet, Smarter Data Centers
Virtualization and Enterprise System Management Technologies
From:
David Boyes
To:
LINUX-390@vm.marist.edu,
Date:
06/12/2013 10:39 AM
Subject:
Re: More words on "The Virtualization Cookbook" Re
> Is there already zVM/zLinux documentation contrasting benefits/costs of
> Hipersockets vs shared OSA offload? I believe OSA offload can also be an
> approach that is a differentiator with Z. So might as well add that too?
> Unless Hipersockets is always superior, though I'm not sure that's the
> Any more suggestions or comments of what else you'd like to see in this
> book?
If it's not already there:
1) a section on setting up the CMS SSL server to provide secure management
traffic transport.
2) a section on enabling SMAPI and the use of smaclient to manipulate the
images.
Is there already zVM/zLinux documentation contrasting benefits/costs of
Hipersockets vs shared OSA offload? I believe OSA offload can also be an
approach that is a differentiator with Z. So might as well add that too?
Unless Hipersockets is always superior, though I'm not sure that's the case
Since that is a fairly key differentiator for the Z environment, and
something that management can probably understand (hey, look, cross memory
"networking"), you should really try to have a page or two on setting it up.
On Wed, Jun 12, 2013 at 9:46 AM, Michael MacIsaac wrote:
> John,
>
> > you
@VM.MARIST.EDU
Subject: More words on "The Virtualization Cookbook" Redbook residency
Hello lists,
Thought I'd blog a bit more on "The Virtualization Cookbook" residency.
The first week we got a z/VM ESP system installed in a 2-node SSI cluster.
We defined an IDENTITY (aka an
John,
> you might include a (sub)chapter on setting up a Hipersockets network.
Thanks for the input - we will add it to the (wish) list...
"Mike MacIsaac"
--
For LINUX-390 subscribe / signoff / archive access instructions,
send
> -Original Message-
> From: Linux on 390 Port On Behalf Of Michael MacIsaac
>
> Hello lists,
>
> Thought I'd blog a bit more on "The Virtualization Cookbook" residency.
> [ snip ]
>
> Today starts work day 8 of 20 and we still have many items "on our plate"
> that we'll try to address (
Hello lists,
Thought I'd blog a bit more on "The Virtualization Cookbook" residency.
The first week we got a z/VM ESP system installed in a 2-node SSI cluster.
We defined an IDENTITY (aka an MCVM) named LNXADMIN with the system on one
member being focused on RHEL and the other on SLES (addressing
15 matches
Mail list logo
