Hi guys,
I need your help regarding setting up the hipersocket between the Ubuntu
and zACI lpars , the Ubuntu is directly installed on the LPAR something as
shown below.
Regards,
Archana
On Tue, Oct 25, 2016 at 10:11 PM, Mark Post wrote:
> >>> On 10/25/2016 at 10:35 AM, Archana P wrote:
> >
We (SNA) are customizing the OpenShift stuff and will be offering it for
support and publishing images on dockerhub. We have recently published
some hyperledger images if people are interested in experimenting with
this technology. See https://hub.docker.com/u/sinenomine for all our
images and
htt
Just a thought:
Have you seem Origin Openshift? The community version can be built on Linux for
z Systems:
https://github.com/linux-on-ibm-z/docs/wiki/Building-OpenShift-Origin
IBM actually did all the heavy lifting porting the components from x86 to s390x.
Origin Openshift can help you to manag
On Tue, 25 Oct 2016, PHILIP TULLY wrote:
> We are looking to implement Docker on Z, as we have begun the testing
> part of the issue is to be able to grow a docker engine and growing it
> dynamically based on it's current needs especially when a node in the
> Docker cluster fails.
>
> So the quest
You could define it big and run Rob's cmmflush on a periodic basis - once a
day? after each shift?
I think the writeup is here somewhere
https://zvmperf.wordpress.com/
but i can't verify at the moment since it seems we have it blocked :(
Alternatively, you could write a velocity macro and p
We are looking to implement Docker on Z, as we have begun the testing
part of the issue is to be able to grow a docker engine and growing it
dynamically based on it's current needs especially when a node in the
Docker cluster fails.
So the question is does anyone see a way for the VM system to se
I'm beginning to think everyone is right concerning LVM.
I went down that path because it was the first image that failed and when I
look at the fstab.conf, the root drive was "by path". So I assumed it was
drives with LVM.
However, now I see that the zipl.conf still has the "by id" in it:
[ipl]
>>> On 10/24/2016 at 04:15 PM, "Duerbusch, Tom"
>>> wrote:
> I got caught this weekend.
> We were converting from a DS6800 to a DS8884 using metro mirror.
>
> This is on Suse 11, pretty much maintained by yast.
>
> When I brought up the Linux images, some failed due to "device path" not
> bein
>>> On 10/24/2016 at 05:55 PM, Alan Altmark wrote:
> This pattern of behavior by Linux has now officially become annoying.
> Binding a file system to a specific set of spinning devices is just silly.
> Harrumph.
It shouldn't be doing that for the mainframe, it should be by-path, or by UUID
f
