From tobi at oetiker.ch  Mon Nov  5 12:45:54 2018
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Mon, 5 Nov 2018 13:45:54 +0100 (CET)
Subject: [OmniOS-discuss] OmniOSce r151028 with production ready Bhyve
	hypervisor released.
Message-ID: <858063106.123778.1541421954504.JavaMail.zimbra@oetiker.ch>

OmniOSce - r151028 - released
=============================

New Features
------------

The OmniOSce team and the illumos community have been very active in creating new features and improving existing ones over the last 6 months. Highlights of this new release include:

* Production-ready Bhyve hypervisor. For years, OmniOS has provided a linux kvm based hypervisor. With this release, we are adding a second option. The bhyve hypervisor from the BSD world has been made a first class illumos component through the combined efforts of Pluribus networks and Joyent with extra help from the FreeBSD community. It provides massively faster disk and network io than the kvm hypervisor as it does not rely on qemu emulation for these services but comes with a super optimised native driver implementation.

* Branded zones for bhyve and KVM virtual machines. Running a virtual machine inside a zone provides an additional layer of security as any success in breaking out of the virtual machine container will only result in access to the branded zone which itself guarantees strong isolation from the global zone. On top of added security, zones also provide protection against hyper-threading attacks such as L1TF and Portsmash, and allow strict resource controls for cpu, disk and network access. Our website contains documentation (https://omniosce.org/info/bhyve_kvm_brand) on how to make use of these new zone types.

* ZFS support for mounting filesystems in parallel. This significantly improves boot time for systems with many filesystems.

* All userland tools are now compiled with gcc7 and several 32-bit only packages have been moved to 64-bit only.

* Many packages have been updated to newer releases like Python 3.5, Perl 5.28, OpenSSL 1.1. And developers can now start using gcc 8 on OmniOS.


New Hardware Support
--------------------

* Emulex 31000/32000-based Fibrechannel cards.
* ATTO Celerity FC-162E Gen 5 and Celerity FC-162P Gen 6 Fibrechannel cards.
* QLogic 16Gb/s Gen5/6 fibrechannel cards.
* QLogic QL41000/45000 series devices.
* NVMe 1.3 devices.
* SMB access to some HP scanner models.

OmniOSce Newsletter
-------------------

Since the start of OmniOS Community Edition project, we have predominantly announced our new releases via twitter. With r151028 we are now also offering a newsletter with announcements of updates, bug fixes and new releases. You can subscribe here http://eepurl.com/dL1z7k

Release Notes and Upgrade Instructions
--------------------------------------

This is only a small selection of the new features, and bug fixes in the new release; review the release notes at https://omniosce.org/releasenotes for full details and find upgrade instructions at https://omniosce.org/upgrade

Commercial Support
-------------------

Have you ever wondered how OmniOS development gets financed? You may have noticed that there is no big company bankrolling it all. The way we keep afloat is by the companies who rely on OmniOS powered servers taking out support contracts for their hardware. How about you? Visit https://omniosce.org/support for more details and to generate a quote. If you aren?t in a position to take a support contract, please consider becoming an OmniOS patron to help secure its future - https://omniosce.org/patron.

cheers
tobi

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch tobi at oetiker.ch +41 62 775 9902

From omnios at citrus-it.net  Tue Nov  6 23:45:18 2018
From: omnios at citrus-it.net (Andy Fiddaman)
Date: Tue, 6 Nov 2018 23:45:18 +0000 (UTC)
Subject: [OmniOS-discuss] Recommend any FC Gen 5 or Gen 6 HBAs?
In-Reply-To: <1540312420138.46091@auburn.edu>
References: <26c689c3d4fd48dfbf1f5f5de466686c@ex7.auburn.edu>,
	<777c92942d5f4ba3a4ba9f6d5e4af912@ex7.auburn.edu>
	<OF68EC1DAB.394138C4-ONC125832E.005297D7-C125832E.005297D9@inse.com>,
	<OF8ED60DF7.15BE5A5C-ONC125832E.00577614-C125832E.00577616@inse.com>
	<1540312420138.46091@auburn.edu>
Message-ID: <nycvar.TFB.7.76.1811062340470.3152@erncre.pvgehf-vg.arg>


On Tue, 23 Oct 2018, Phil Forrest wrote:

; I found another Fibre Channel card that does not work in OmniOS CE r151026: Qlogic QLE2740
;
; root at claw:~# prtconf -D | grep pci1077
;             pci1077,299

...

; My failures so far:
;
; Qlogic QLE2672
; Emulex LPe32000 (Lancer)
; Qlogic QLE2740
;

Just to close the loop on this one, thanks to Phil's assistance with access
to hardware for development and testing, the recently released OmniOS r151028
includes new support for all three cards listed above.

https://github.com/omniosorg/omnios-build/blob/r151028/doc/ReleaseNotes.md#hardware-support

~A.

-- 
Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123


From tobi at oetiker.ch  Tue Nov 13 14:32:22 2018
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Tue, 13 Nov 2018 15:32:22 +0100 (CET)
Subject: [OmniOS-discuss] ANNOUNCEMENT omnios-discuss is moving to topicbox
Message-ID: <931849508.99879.1542119542785.JavaMail.zimbra@oetiker.ch>

Dear OmniOS Friends

It's been 18 months now since we started the OmniOS Community Edition and with the third stable release under our belt we are finalising the transfer of the remaining services from OmniTI.

To that end, the existing OmniOS mailing lists (including this one) will be closed down at the end of December.

With thanks to Topicbox and the illumos project, we have a new omnios-discuss list which can be found at:

        https://illumos.topicbox.com/groups/omnios-discuss

Subscriptions to this list will NOT be transferred automatically so please head over there to subscribe.

We also have a new Newsletter mailing list for keeping up to date with the latest news; you can subscribe to that at:

        http://eepurl.com/dL1z7k

cheers
tobi

-- 
Tobi Oetiker
tobi at omniosce.org

From johan.kragsterman at capvert.se  Wed Nov 14 15:57:36 2018
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Wed, 14 Nov 2018 16:57:36 +0100
Subject: [OmniOS-discuss] Vbf: [SSSD-users] Re: SSSD in AIX
Message-ID: <OFE30CF00C.AB509D02-ONC1258345.00579186-C1258345.0057ABCF@inse.com>

Hi!


For your information, the SSSD application, the  "System Security Services Daemon", seems to be in a process to be ported to AIX.

This might be of interest for the Illumos community, since if it is ported to AIX, it would help very much to port it to Illumos.

Background is probably that IBM now acquired RedHat, and that they see considerable value in SSSD. So do I, that's why I inform the community of this.


https://github.com/SSSD/sssd



Best regards from/Med v?nliga h?lsningar fr?n

Johan Kragsterman

Capvert


-----Vidarebefordrat av Johan Kragsterman/Capvert 2018-11-14 16:50 -----
Till: "End-user discussions about the System Security Services Daemon" <sssd-users at lists.fedorahosted.org>
Fr?n: "Frank Pikelner" <frank.pikelner at gmail.com>
Datum: 2018-11-14 15:26
?rende: [SSSD-users] Re: SSSD in AIX

I would concur that SSSD on AIX would be very welcome as an OS option.
Appreciate the effort.

Frank Pikelner
On Wed, Nov 14, 2018 at 4:36 AM Jakub Hrozek <jhrozek at redhat.com> wrote:
>
> On Mon, Nov 12, 2018 at 05:24:54PM +0530, Ayappan wrote:
> > On Mon, Nov 12, 2018 at 4:56 PM Jakub Hrozek <jhrozek at redhat.com> wrote:
> > >
> > > On Mon, Nov 12, 2018 at 03:57:53PM +0530, Ayappan wrote:
> > > > Hi,
> > > >
> > > > I am from AIX OS development team here in IBM. We have some customers
> > > > who are interested in running SSSD in AIX. So i basically invested
> > > > some amount of time to first build SSSD in AIX. I built the recent
> > > > version 1.16.3 after working around some build issues. Below is the
> > > > configure options.
> > > > ./configure --prefix=/opt/freeware --disable-cifs-idmap-plugin
> > > > --without-nfsv4-idmapd-plugin --disable-rpath --with-manpages=no
> > > > --without-python3-bindings --with-selinux=no --with-semanage=no
> > > > --with-crypto=libcrypto --without-secrets --without-kcm
> > > >
> > > > I started the daemon but then it failed later with no stderr / logs
> > > > produced anywhere.
> > > >
> > > > # /opt/freeware/sbin/sssd -i -d4
> > >
> > > Are there also no messages if you run with -d 10 ?
> > >
> >
> > I just ran it and attached the output. It is showing lot of messges
> > with "ldb" tag. Not sure how to interpret it.
>
> Hmm, this is strange, for some reson the ldb library debug hooks work,
> but not the sssd debugging itself? I don't know what to make of it
> because both should be routed to the sss_vdebug_fn() function. I guess
> it should be possible to gdb the monitor process and see what gets
> called e.g. inside server_setup() when one of the DEBUG messages is
> reached?
>
> >
> > > On Linux, I would have said that strace with -ff would be also helpful,
> > > but I have no idea if something like this exists on AIX.
> > >
> >
> > AIX strace seems to be different. But it has truss command which is
> > similar to Linux strace. Just ran that as well. It provides
> > good deal of info. Seems like i need to analyze the output to make out
> > anything meaningful.
> >
> > > >
> > > > (1) root @ fvt-p7a2-lp16: /
> > > >
> > > > I see it invokes two other child process which also failed
> > > > /opt/freeware/libexec/sssd/sssd_be --domain implicit_files --uid 0
> > > > --gid 0 -d 0x01f0 --logger=stderr
> > > > /opt/freeware/libexec/sssd/sssd_nss --uid 0 --gid 0 -d 0x01f0 --logger=stderr
> > > >
> > > > Any help would be appreciated.
> > > >
> > > > Thanks
> > > > Ayappan P
> > > > _______________________________________________
> > > > sssd-users mailing list -- sssd-users at lists.fedorahosted.org
> > > > To unsubscribe send an email to sssd-users-leave at lists.fedorahosted.org
> > > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > > List Archives: https://lists.fedorahosted.org/archives/list/sssd-users at lists.fedorahosted.org
> > > _______________________________________________
> > > sssd-users mailing list -- sssd-users at lists.fedorahosted.org
> > > To unsubscribe send an email to sssd-users-leave at lists.fedorahosted.org
> > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives: https://lists.fedorahosted.org/archives/list/sssd-users at lists.fedorahosted.org
>
> > _poll(0x20057788, 4, 1928)                      = 4
> > _enrecvmsg(10, 0x2FF22358, 0, 0x00000000)       = 1
> > getpeereid(10, 0x2FF22380, 0x2FF2237C)          Err#76 ENOTCONN
> > kread(10, " A U T H   E X T E R N A".., 2048)   = 18
> > _poll(0x20057788, 4, 1926)                      = 4
> > _esend(10, 0x200575F8, 46, 256, 0x00000000)     Err#32 EPIPE
> >     Received signal #20, SIGCHLD [caught]
>
> Here the child process (sssd_be) tries to connect to the sssd main
> processes' D-Bus socket, sends the AUTH EXTERNAL command to try to
> authenticate, but when the sssd tries to reply, the send
> call returns EPIPE..this indicates the sssd_be process is exiting after
> startup.
>
> I can't tell from the truss output what makes the sssd_be fail. It would
> be best to first figure out why the logger is not working..
> _______________________________________________
> sssd-users mailing list -- sssd-users at lists.fedorahosted.org
> To unsubscribe send an email to sssd-users-leave at lists.fedorahosted.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedorahosted.org/archives/list/sssd-users at lists.fedorahosted.org
_______________________________________________
sssd-users mailing list -- sssd-users at lists.fedorahosted.org
To unsubscribe send an email to sssd-users-leave at lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/sssd-users at lists.fedorahosted.org





From softwareinforjam at gmail.com  Wed Nov 28 18:23:52 2018
From: softwareinforjam at gmail.com (SoftwareInforJam)
Date: Wed, 28 Nov 2018 13:23:52 -0500
Subject: [OmniOS-discuss] How to Update Zones
Message-ID: <5bfedd36.1c69fb81.c04cc.2303@mx.google.com>

Hi All
I am running OmniOS v11 r151022ca on my global zone. I did a pkg update and that is now the latest version. I want to know the recommended way to update the non-global zones. Last time I logged into the non-global zone and ran pkg update, strangely, the entire box rebooted. Not sure if I did it the right way. I also tried pkg update -r -C 0 but only the global zone updated. The non global zone still has OmniOS v11 r151022bc


Best Regards
SI

Sent from Mail for Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20181128/8cab223e/attachment.html>

From groenveld at acm.org  Thu Nov 29 17:40:11 2018
From: groenveld at acm.org (John D Groenveld)
Date: Thu, 29 Nov 2018 12:40:11 -0500
Subject: [OmniOS-discuss] How to Update Zones
In-Reply-To: Your message of "Wed, 28 Nov 2018 13:23:52 -0500."
	<5bfedd36.1c69fb81.c04cc.2303@mx.google.com>
References: <5bfedd36.1c69fb81.c04cc.2303@mx.google.com>
Message-ID: <201811291740.wATHeBvC023626@groenveld.us>

In message <5bfedd36.1c69fb81.c04cc.2303 at mx.google.com>, SoftwareInforJam write
s:
>te the non-global zones. Last time I logged into the non-global zone and ra=
>n pkg update, strangely, the entire box rebooted. Not sure if I did it the =

Is that repeatable?

Did you get a crashdump?

John
groenveld at acm.org

From softwareinforjam at gmail.com  Fri Nov 30 16:26:02 2018
From: softwareinforjam at gmail.com (SoftwareInforJam)
Date: Fri, 30 Nov 2018 11:26:02 -0500
Subject: [OmniOS-discuss] How to Update Zones
In-Reply-To: <201811291740.wATHeBvC023626@groenveld.us>
References: <5bfedd36.1c69fb81.c04cc.2303@mx.google.com>
	<201811291740.wATHeBvC023626@groenveld.us>
Message-ID: <5c016499.1c69fb81.aec1a.6806@mx.google.com>

Well it happened to me twice in one day when I was upgrading to v22 bc. I sent the crash dump off to Andy but he said it didn?t have enough info. So I guess it didn?t have enough that he could use to pinpoint a root cause. I wondered if maybe I did something wrong. I am going to try upgrading them to v22 ca today after hours and see if it happens again.

Sent from Mail for Windows 10

From: John D Groenveld
Sent: Thursday, November 29, 2018 12:46 PM
To: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] How to Update Zones

In message <5bfedd36.1c69fb81.c04cc.2303 at mx.google.com>, SoftwareInforJam write
s:
>te the non-global zones. Last time I logged into the non-global zone and ra=
>n pkg update, strangely, the entire box rebooted. Not sure if I did it the =

Is that repeatable?

Did you get a crashdump?

John
groenveld at acm.org
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20181130/fe469db4/attachment-0001.html>

From bfriesen at simple.dallas.tx.us  Fri Nov 30 16:56:23 2018
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Fri, 30 Nov 2018 10:56:23 -0600 (CST)
Subject: [OmniOS-discuss] How to Update Zones
In-Reply-To: <5c016499.1c69fb81.aec1a.6806@mx.google.com>
References: <5bfedd36.1c69fb81.c04cc.2303@mx.google.com>
	<201811291740.wATHeBvC023626@groenveld.us>
	<5c016499.1c69fb81.aec1a.6806@mx.google.com>
Message-ID: <alpine.GSO.2.20.1811301052480.8494@scrappy.simplesystems.org>

On Fri, 30 Nov 2018, SoftwareInforJam wrote:

> Well it happened to me twice in one day when I was upgrading to v22 
> bc. I sent the crash dump off to Andy but he said it didn?t have 
> enough info. So I guess it didn?t have enough that he could use to 
> pinpoint a root cause. I wondered if maybe I did something wrong. I 
> am going to try upgrading them to v22 ca today after hours and see 
> if it happens again.

The upgrade instructions normally say that the zones should be 
minimally updated before they are booted because part of the zone 
management software is part of the zone.

It would be very unusual for the whole OS to crash and reboot due to 
starting a zone.

Why are these postings to the old mailing list which is scheduled to 
be shut down?

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
Public Key,     http://www.simplesystems.org/users/bfriesen/public-key.txt

