We implemented something like DHCP, bound to the guest name, not the MAC
address. It's working for 3 years now, and it's very low maintenance.
We had a USER CONFIG file on a MAINT630 disk, and every guest can link that
disk. The USER CONFIG is a simple text file containing this info:
GUEST IPADDR
All,
Just FYI, but here at SUSE we're contemplating creating a systemd unit file and
associated scripts so that our systems running on various hypervisors can do
whatever sort of "cleanup" each one might require to exploit the features of
that hypervisor. For example, in the z/VM case, one of
We create a user in the VM directory called '191USER' who's sole purpose is
to be a container for Linux system 191 A disks that get shared read only.
This allows us to keep all the CMS PROFILE EXEC automation in one place and
have it shared by all the Linux systems that need it. Since it is owned b
We have to use static MACIDs because our servers are behind load balancers that
require it. But SSI is very convenient and lets us work on hardware and zVM
without taking application outages. You do have to remember to do the SYSTEM
CONFIG work to set up your EQIDs for your VSWITCHes.
uary 22, 2016 6:51 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SSI guest best practice
>Managing MACIDs is actually way *less* complicated than IPs since you
>don't have to worry about global uniqueness or subnet boundaries.
The network people worry about global uniqueness
-- San Francisco 49ers CEO Jed York
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Alan
Altmark
Sent: Friday, January 22, 2016 18:29
To: LINUX-390@vm.marist.edu
Subject: Re: SSI guest best practice
On Saturday, 01/23/2016 at 01:13 GMT, "O&
On Saturday, 01/23/2016 at 01:13 GMT, "O'Brien, Dennis L"
wrote:
> Like Marcy said, I don't see anything to gain by involving the DHCP
people.
> Managing MACID's is no less complicated than managing IP addresses.
Managing MACIDs is actually way *less* complicated than IPs since you
don't have
ed York
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Marcy
Cortes
Sent: Friday, January 22, 2016 15:52
To: LINUX-390@vm.marist.edu
Subject: Re: SSI guest best practice
Alan wrote:
>I am wondering if people are looking at using persistent D
Redbook will bring it
up.
Tks,
Eduardo C. Oliveira
Sent from IBM Verse via Smartphone
van Sleeuwen, Berry --- SSI guest best practice ---
From:"van Sleeuwen, Berry"
To:LINUX-390@VM.MARIST.EDUDate:Fri, Jan 22, 2016
3:41 PMSubject:SSI guest best practice
Hi All,We want t
Alan wrote:
>I am wondering if people are looking at using persistent DHCP for this. To
>make it work you have to use layer 2 VSWITCHes and you have to manage
>MACIDs on the NICDEFs. Your automation tools have to "manufacture" a new
>MACID for every new NICDEF and put it there or on COMMAND D
lly stolen from James/Rick at NW :)
It's good to SHARE.
Marcy
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of van
Sleeuwen, Berry
Sent: Friday, January 22, 2016 2:58 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SSI guest best practic
oet/With kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan
Altmark
Sent: Friday, January 22, 2016 11:37 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SSI guest best practice
On Friday, 01/22/2016 at
nt: Friday, January 22, 2016 2:20 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SSI guest best practice
Thanks, That's indeed helpful. In the past we tested a provisioning tool that
couldn't handle our CMS setup (both Linux PROFILE EXEC and AUTOLOG1 PROFILE
EXEC) so I will take suc
On Friday, 01/22/2016 at 10:29 GMT, Marcy Cortes
wrote:
> We do other necessary stuff from CMS. Mainly checking of where we are
and
> writing various parms that a linux boot script uses to configure IP,
hostname,
> etc.
I am wondering if people are looking at using persistent DHCP for this. T
On Friday, 01/22/2016 at 10:10 GMT, "van Sleeuwen, Berry"
wrote:
> So the question is what would be the best way to configure the new
setup.
> Either remove CMS dependency altogether or detach the disks after we
don't need
> CMS anymore (in the PROFILE EXEC or after Linux IPL has been completed
22, 2016 2:20 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SSI guest best practice
Thanks, That's indeed helpful. In the past we tested a provisioning tool that
couldn't handle our CMS setup (both Linux PROFILE EXEC and AUTOLOG1 PROFILE
EXEC) so I will take such items into ac
day, January 22, 2016 11:05 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SSI guest best practice
That's what we do.
But we also still mkswap and swapon on the Linux side. That way if changes are
made to the swap signature info there, no worries.
Also we had to change the vdisk in the directo
0:48 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SSI guest best practice
You can still use CMS to run swapgen. When you IPL Linux, CMS is no longer
there.
This e-mail and the documents attached are confidential and intended solely for
the addressee; it may also be privileged. If you receive this
egards/Mit freundlichen Grüßen,
Berry van Sleeuwen
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rich
Smrcina
Sent: Friday, January 22, 2016 10:48 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SSI guest best practice
You can still use CMS to run swapgen
Regarding the last part of your message, zPro has no restrictions on directory entry
contents. What ever is in the directory is replicated to the destination server.
On 01/22/2016 03:39 PM, van Sleeuwen, Berry wrote:
Hi All,
We want to move our Linux environment into an SSI cluster. We have lo
90@VM.MARIST.EDU] On Behalf Of O'Brien,
Dennis L
Sent: Friday, January 22, 2016 1:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SSI guest best practice
Immediately before you IPL Linux, detach the CMS disks (190 19D 19E) in
xpert.” -- San Francisco 49ers CEO Jed York
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Rich
Smrcina
Sent: Friday, January 22, 2016 13:48
To: LINUX-390@vm.marist.edu
Subject: Re: SSI guest best practice
You can still use CMS to run swapgen. Whe
You can still use CMS to run swapgen. When you IPL Linux, CMS is no longer
there.
On 01/22/2016 03:39 PM, van Sleeuwen, Berry wrote:
Hi All,
We want to move our Linux environment into an SSI cluster. We have local
resources that I need to get rid of in order for guests to use LGR. The most
o
Hi All,
We want to move our Linux environment into an SSI cluster. We have local
resources that I need to get rid of in order for guests to use LGR. The most
obvious are the CMS minidisks (190, 19E). Most commands in the PROFILE EXEC are
CP commands so these can be moved into the directory. But
24 matches
Mail list logo
