From darrent at akurit.com.au  Mon May 26 00:20:39 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 26 May 2014 16:20:39 +1000
Subject: [sles-beta] Install_server and Apache2 default settings and missing
	"imagemap" module
Message-ID: <CAEUhfEdyXRgVYjDLjvhU2a+7uPWXd=ELEvr-xA0OKRoeKOcP2w@mail.gmail.com>

Team

On SLES12B7

I could not get access to the contents of the "Install server" despite what
looked like a valid configuration that was generated by the YaST2
"install_server" module.

I had to modify the httpd.conf file to get this to work (I added Order and
Deny stanzas and "#" the "Require all denied" stanza):

e.g.

# forbid access to the entire filesystem by default
<Directory />
    Options None
    AllowOverride None
#    Require all denied
    Order deny,allow
    Deny from all
</Directory>

Also, the Apache2 module "imagemap" is reported as not installed, so the
file list display looks wrong (see screenshot)


-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140526/4eab2f6b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140526/4eab2f6b/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Install_server_directory_list_looks_wrong.png
Type: image/png
Size: 15223 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140526/4eab2f6b/attachment.png>

From lmb at suse.com  Mon May 26 01:36:37 2014
From: lmb at suse.com (Lars Marowsky-Bree)
Date: Mon, 26 May 2014 09:36:37 +0200
Subject: [sles-beta] GEO Clusters, where to get basic information
In-Reply-To: <3261cdbdcf6c9a3cd57d3c63b542280c@suse.de>
References: <CAEUhfEfzjD8Y2Jk7n34Y8=8TA3hCWG6-4QNnsT9RhQruzNvt2w@mail.gmail.com>
	<3261cdbdcf6c9a3cd57d3c63b542280c@suse.de>
Message-ID: <20140526073637.GD18618@suse.de>

On 2014-05-25T10:01:05, Richard Brown <rbrown at suse.de> wrote:

Hi Richard,

an excellent description - there's a career in our documentation group
for you too! ;-)

Only a few additional details:

> GEO introduces the concept of 'Tickets' - Tickets are tokens which can be
> granted/revoked from a Cluster, and used as a dependency for the operation
> of Cluster Resources.

Actually, 'tickets' are part of pacemaker even in SLE HA itself, but
fail-over for Geo scenarios isn't supported without the Geo extension.

It should be noted that there can be multiple tickets, not just one. And
that sites can host resources that depend on tickets or none; e.g., one
could have "local" resources that don't fail-over too.

> eg. a ticket called TicketA might be required by all the Resources
> that are typically at Site A. When the Ticket is revoked from Site A
> and granted to the Cluster at Site B, Site B is then the only cluster
> able to operate the services that rely on TicketA's presence.

By default, pacemaker will immediately fence nodes which host resources
which depend on a revoked ticket, to reduce the needed time before a
ticket can be re-granted elsewhere.

> Arbitrators are special machines running Booth but not running HA Clusters.
> This allows you to avoid split brain scenarios by having a 3rd independent
> server arbitrate about the status of the other Sites. Arbitrators are not
> necessary if you have an odd number of Clusters in your Geo Cluster.

There can even be multiple arbitrators if the admin is thus inclined.

> As the details depend totally on the structure of your network and the local
> resources you want to enable for Geo clustering, templates are a tricky
> thing to provide.

Right. Though we do have a resource agent that handles IP fail-over via
dynamic DNS updates, since ARP updates don't work across multiple
network segments.

Also, this might be best discussed on the sleha-beta list.


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 21284 (AG N?rnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde


From jreidinger at suse.com  Mon May 26 02:54:27 2014
From: jreidinger at suse.com (Josef Reidinger)
Date: Mon, 26 May 2014 10:54:27 +0200
Subject: [sles-beta] SLES12 Beta7 not installable with autoyast
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99D5E2@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F99D5E2@HXMB12.pnet.ch>
Message-ID: <20140526105427.6730ff9d@dhcp150.suse.cz>

On Mon, 26 May 2014 08:48:43 +0000
<urs.frey at post.ch> wrote:

> Hi
> 
> There is a weird error when installing SLES12 Beta7 x86_64 using
> autoyast
> 
> I got this message on point: - create partition plans
> Error
> Internal error: Please report a bug report with logs
> Details: no implicit conversion of String into integer
> Caller: /mounts/mp_0001/usr/share/YaST2/include/autoinstall/autopart.rb:131:in
> '[]'
> 
> 
> 

Hi, you are the second one reporting this issue on this mailing list
so looks like we break something. Please create bug report for it, so we
can check where exactly is problem. Looks like some xml parsing error.

Josef

> 
> 
> I state installation of SLES12 Beta7 using autoyast is not possible
> 
> Best regards
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
> 
> 
> 


From jreidinger at suse.cz  Mon May 26 03:00:17 2014
From: jreidinger at suse.cz (Josef Reidinger)
Date: Mon, 26 May 2014 11:00:17 +0200
Subject: [sles-beta] Disc config error in Autoyast execution
In-Reply-To: <CAEUhfEcfm+d1t8o0xBxrZ8-8KOrJLkBbgddsPx+ue2mzeCUPMg@mail.gmail.com>
References: <CAEUhfEcfm+d1t8o0xBxrZ8-8KOrJLkBbgddsPx+ue2mzeCUPMg@mail.gmail.com>
Message-ID: <20140526110017.7afb7a64@dhcp150.suse.cz>

Hi Darren,
I check the problematic code and problem is in autoyast code, so syntax
is correct. Just parsing xml have bug introduced by adding specific
hardware support.

Josef


On Mon, 26 May 2014 14:44:48 +1000
"Darren Thompson" <darrent at akurit.com.au> wrote:

> Team
> 
> I did a default SLES12B7 install.
> 
> I then took the autoinstall.xml file, opened it in the
> "autoinstallation" yast2 module. (BTW, it looks like there is a type
> on the Yast2 option as it seems to be called autoinstallatior <=
> notice the ending 'r' and not 'n' )
> 
> I made minor modifications (cloned the machines actual disk config,
> added a couple of users, set Root password and change language
> setting).
> 
> All of this passed the "syntax parser" of the "autoinstalltion"
> module.
> 
> When I do an autoyast install using the resulting autoyast file it
> errors on the disk configuration (see attached screen shot and copy
> of autoyast file).
> 
> Could someone more familiar with these files please review to see if
> the syntax is correct etc.
> 
> If syntax is correct then there is a bug in the autoyast installer,
> when processing config files.
> 
> If the symtax is incorrect then there is a bug in the
> "autoinstallation" yast2 module, in that it allows the creation of an
> invalid syntax file.
> 
> I can raise a SR but would like confirmation as to which of these two
> options it should be raised against.
> 
> Regards
> Darren
> 


From Dick.Waite at softwareag.com  Mon May 26 03:00:17 2014
From: Dick.Waite at softwareag.com (Waite, Dick)
Date: Mon, 26 May 2014 09:00:17 +0000
Subject: [sles-beta] sysconfig/system/cron
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D53834610@hqmbx6.eur.ad.sag>

Grand Very Wet Morning,

/etc/sysconfig/system/cron in the past used to have a number a helpful variables for keeping ones environment clean and tidy. One looks at SLES v12 to set them up and yet another change, they have all gone or are they in a new place. I have created a SR 10894124441. This would be another are an upgrade / update would have a wobbly or would it know what to do.

I have also created SR 10894113321 with some low priority stuff.

I would like my to keep my environments clean and tidy (Ship Shape and Bristol Fashion) so SUSE if you have moved these, please make sure Update knows where they are and fills them in correctly.

If you don't mind me saying so, some of these changes seem to be for the sake of change. If you do want to change basic stuff like this SUSE one should think of the grand saying "Change is grand, but by evolution, not revolution". Why not have your new idea's in openSUSE for some time, getting all the bugs out and we can try them out, then at the next major SLES / SLED have them in, but keeping backward compatibility, and then if they work, deprecation is the path to follow. This Big Bang has not gone down too well in our shop.

__R


Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140526/0b17a79b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Ostia-11-3-1-2014-05-26-10-17-36.png
Type: image/png
Size: 679355 bytes
Desc: Ostia-11-3-1-2014-05-26-10-17-36.png
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140526/0b17a79b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Ostia-12-0-2-2014-05-26-10-23-02.png
Type: image/png
Size: 392680 bytes
Desc: Ostia-12-0-2-2014-05-26-10-23-02.png
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140526/0b17a79b/attachment-0001.png>

From urs.frey at post.ch  Mon May 26 03:49:13 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Mon, 26 May 2014 09:49:13 +0000
Subject: [sles-beta] SLES12 Beta7 not installable with autoyast
In-Reply-To: <20140526105427.6730ff9d@dhcp150.suse.cz>
References: <40637DBB36AF3941B243A286A432CA0B0F99D5E2@HXMB12.pnet.ch>
	<20140526105427.6730ff9d@dhcp150.suse.cz>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F99D64C@HXMB12.pnet.ch>

Hi Josef

The entire autoyast process is broken. 
Even if I manage to get some partitioning, the autoyast phase 2 with configuration is omitted completely leaving an unconfigured server

So for me testing not possible
SLES12 Beta7 unusable

Best regards

Urs Frey????????????????????????????????????????????? 
Post CH AG
Informationstechnologie
IT Betrieb 
Webergutstrasse 12 
3030 Bern (Zollikofen) 
Telefon : ++41 (0)58 338 58 70 
FAX???? : ++41 (0)58 667 30 07 
E-Mail:?? urs.frey at post.ch


-----Urspr?ngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Josef Reidinger
Gesendet: Monday, May 26, 2014 10:54 AM
An: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 Beta7 not installable with autoyast

On Mon, 26 May 2014 08:48:43 +0000
<urs.frey at post.ch> wrote:

> Hi
> 
> There is a weird error when installing SLES12 Beta7 x86_64 using
> autoyast
> 
> I got this message on point: - create partition plans
> Error
> Internal error: Please report a bug report with logs
> Details: no implicit conversion of String into integer
> Caller: /mounts/mp_0001/usr/share/YaST2/include/autoinstall/autopart.rb:131:in
> '[]'
> 
> 
> 

Hi, you are the second one reporting this issue on this mailing list
so looks like we break something. Please create bug report for it, so we
can check where exactly is problem. Looks like some xml parsing error.

Josef

> 
> 
> I state installation of SLES12 Beta7 using autoyast is not possible
> 
> Best regards
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
> 
> 
> 

_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

From meissner at suse.de  Mon May 26 05:57:54 2014
From: meissner at suse.de (Marcus Meissner)
Date: Mon, 26 May 2014 13:57:54 +0200
Subject: [sles-beta] SLES12 Beta7 x86_64 vmtoolsd now
	activated	automatically?
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99D6DE@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F99D6DE@HXMB12.pnet.ch>
Message-ID: <20140526115754.GB2284@suse.de>

Hi,

The autostart was actually requested by our partner VMWare itself.

Ciao, Marcus
On Mon, May 26, 2014 at 11:51:55AM +0000, urs.frey at post.ch wrote:
> Hi
> 
> When installing SLES12 x86_64 Beta7 on VMware ESX I can see that the vmtoolsd gets activated automatically
> 
> I state that this is unwanted, as the support state of the SLES12 included open-vm-tools is not clear with VMware
> Within the changelog Beta6-> Beta7 there is nothing mentioned.
> 
> -----------------------------------------------------------------------------
> 
> o Updated open-vm-tools (security/bugfix/feature)       [x86_64]
> 
> - Modify vmware-user-autostart-wrapper to unconditionally start
>   vmware-user-suid-wrapper, and no longer delay for vmblock-fuse
>   if under systemd. (bnc#876074)
> - added forgotten %pre snippet for service addition, this made
>   systemd service not auto-start. bnc#870737
> - Set ExclusiveArch to x86_64 only (for SLE-12).
> 
> -----------------------------------------------------------------------------
> 
> With SLES12 I need to have a platform working on VMware ESX in a supported state.
> Today with open-vm-tools I still have the "unsupported, third party state" in the v-sphere console
> 
> This is not feasible for production environment
> 
> If I need to install the professional VMwareTools coming with ESX there should be an easy way to remove, or to lock the installation of open-vm-tools
> No automatic activation of open-vm-tools please.
> 
> Best regards
> 
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
> 
> 
> 

> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta


From gjn at gjn.priv.at  Mon May 26 06:06:50 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Mon, 26 May 2014 14:06:50 +0200
Subject: [sles-beta] Kernel crash.
Message-ID: <1533950.UTi0Gaixhr@gjn.priv.at>

Hello,

is there a way to disable same Programs on start time.

I make a new install witn KVM and 2 Clients now after the last Boot I have a 
kernel crash and reboot usw.

now I like to disable on Boot Time systemd libvirt_guest is there a way (?), 
to find out the Problem.

In older times I start from a stick and delete the File in "/init.d" ;)
 
-- 
mit freundlichen Gr??en / best Regards,

  G?nther J. Niederwimmer

From kdupke at suse.com  Mon May 26 07:04:19 2014
From: kdupke at suse.com (Kai Dupke)
Date: Mon, 26 May 2014 15:04:19 +0200
Subject: [sles-beta] SLES12 Beta7 x86_64 vmtoolsd now activated
	automatically?
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99D6DE@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F99D6DE@HXMB12.pnet.ch>
Message-ID: <53833BD3.9050703@suse.com>

Hi Urs,

this is per the request of VMware, to select and install the
open-vm-tools when a VMware hypervisor is identified. This also includes
the auto-activation of the tools, when installed.

I expect to move the support status from external supported to supported
soon. Hopefully this will ease potential concerns.

In case you don't want the tools installed, please deselect them.

Regarding the message in the virtual center, where the tools are
displayed as 3rd party (even this is maintained by VMware), all I can
tell you is that VMware is aware of this and I hope a solution will be
available for this without waiting too long.

greetings kai




On 05/26/2014 01:51 PM, urs.frey at post.ch wrote:
> Hi
> 
> When installing SLES12 x86_64 Beta7 on VMware ESX I can see that the vmtoolsd gets activated automatically
> 
> I state that this is unwanted, as the support state of the SLES12 included open-vm-tools is not clear with VMware
> Within the changelog Beta6-> Beta7 there is nothing mentioned.
> 
> -----------------------------------------------------------------------------
> 
> o Updated open-vm-tools (security/bugfix/feature)       [x86_64]
> 
> - Modify vmware-user-autostart-wrapper to unconditionally start
>   vmware-user-suid-wrapper, and no longer delay for vmblock-fuse
>   if under systemd. (bnc#876074)
> - added forgotten %pre snippet for service addition, this made
>   systemd service not auto-start. bnc#870737
> - Set ExclusiveArch to x86_64 only (for SLE-12).
> 
> -----------------------------------------------------------------------------
> 
> With SLES12 I need to have a platform working on VMware ESX in a supported state.
> Today with open-vm-tools I still have the "unsupported, third party state" in the v-sphere console
> 
> This is not feasible for production environment
> 
> If I need to install the professional VMwareTools coming with ESX there should be an easy way to remove, or to lock the installation of open-vm-tools
> No automatic activation of open-vm-tools please.
> 
> Best regards
> 
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
> 
> 
> 
> 
> 
> 
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
> 



Kai Dupke
Senior Product Manager
Server Product Line
-- 
Phone:  +49-(0)5102-9310828     Mail: kai.dupke at suse.com
Mobile: +49-(0)173-5876766      WWW:  www.suse.com

SUSE Linux Products GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany)
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG Nurnberg)

From Klaus.Gmeinwieser at oce.com  Mon May 26 07:39:57 2014
From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser)
Date: Mon, 26 May 2014 15:39:57 +0200
Subject: [sles-beta] SLES12 Beta7 not installable with autoyast
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99D64C@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F99D5E2@HXMB12.pnet.ch>
	<20140526105427.6730ff9d@dhcp150.suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F99D64C@HXMB12.pnet.ch>
Message-ID: <5383442D.7090503@oce.com>

Hi all,

as unattended installation is (completely?) broken, does it makes sense
to try any unattended again? As the unattended installation is a main
issue to me (much much work to redo it in attended mode for component
tests) I am worried about my testresults.

How is this to be fixed? Is another Beta7 iso to be delivered (soon), or
is this to be fixed in in RC1 only? Is there a workaround which makes
any kind of Unattended installs possible...

Please let me know, how to proceed on this particular issue...

Thanks a lot in advance
Klaus

Am 26.05.2014 11:49, schrieb urs.frey at post.ch:
> Hi Josef
>
> The entire autoyast process is broken.
> Even if I manage to get some partitioning, the autoyast phase 2 with configuration is omitted completely leaving an unconfigured server
>
> So for me testing not possible
> SLES12 Beta7 unusable
>
> Best regards
>
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch
>
>
> -----Urspr?ngliche Nachricht-----
> Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Josef Reidinger
> Gesendet: Monday, May 26, 2014 10:54 AM
> An: sles-beta at lists.suse.com
> Betreff: Re: [sles-beta] SLES12 Beta7 not installable with autoyast
>
> On Mon, 26 May 2014 08:48:43 +0000
> <urs.frey at post.ch> wrote:
>
>> Hi
>>
>> There is a weird error when installing SLES12 Beta7 x86_64 using
>> autoyast
>>
>> I got this message on point: - create partition plans
>> Error
>> Internal error: Please report a bug report with logs
>> Details: no implicit conversion of String into integer
>> Caller: /mounts/mp_0001/usr/share/YaST2/include/autoinstall/autopart.rb:131:in
>> '[]'
>>
>>
>>
>
> Hi, you are the second one reporting this issue on this mailing list
> so looks like we break something. Please create bug report for it, so we
> can check where exactly is problem. Looks like some xml parsing error.
>
> Josef
>
>>
>>
>> I state installation of SLES12 Beta7 using autoyast is not possible
>>
>> Best regards
>> Urs Frey
>> Post CH AG
>> Informationstechnologie
>> IT Betrieb
>> Webergutstrasse 12
>> 3030 Bern (Zollikofen)
>> Telefon : ++41 (0)58 338 58 70
>> FAX     : ++41 (0)58 667 30 07
>> E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
>>
>>
>>
>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>

--
Klaus Gmeinwieser
T +49 (0)8121 72 4358 F +49 (0)8121 72 3173
E klaus.gmeinwieser at oce.com W www.oce.com

Oc? Printing Systems GmbH & Co. KG ? A Canon Group Company
P.O. Box 1260 ? 85581 Poing
Siemensallee 2 ? 85586 Poing ? Germany

Oc? enables its customers to manage their documents efficiently and
effectively by offering
innovative print and document management products and services for
professional
environments.

Oc? Printing Systems GmbH & Co. KG
The company is a limited partnership with its registered office in Poing
? Trade Register HRA 100955 (Amtsgericht M?nchen) ? WEEE-Reg.-No. DE 888
05 443

General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH
Registered Office: Poing ? Trade Register HRB 206480 (Amtsgericht M?nchen)
Executive Officer: Andr? Mittelsteiner
This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.

From urs.frey at post.ch  Mon May 26 07:54:49 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Mon, 26 May 2014 13:54:49 +0000
Subject: [sles-beta] SLES12 Beta7 not installable with autoyast
In-Reply-To: <5383442D.7090503@oce.com>
References: <40637DBB36AF3941B243A286A432CA0B0F99D5E2@HXMB12.pnet.ch>
	<20140526105427.6730ff9d@dhcp150.suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F99D64C@HXMB12.pnet.ch>
	<5383442D.7090503@oce.com>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F99D7B0@HXMB12.pnet.ch>

Hi Klaus

The same issue here. Autoyast is completely broken. 
No configuration done, many packages missing. After having done a manual partitioning.
I tried to boot from Beta6 versus my network install server with Beta7.
But there still the same issue. 
So the problem is in a downloaded autoyast RPM
Manual Installation does also have some unsustainable issues, I only have to wait for too long

I guess I will terminate here.
SLES12 without autoyast is not usable for me

Best regards

Urs Frey????????????????????????????????????????????? 
Post CH AG
Informationstechnologie
IT Betrieb 
Webergutstrasse 12 
3030 Bern (Zollikofen) 
Telefon : ++41 (0)58 338 58 70 
FAX???? : ++41 (0)58 667 30 07 
E-Mail:?? urs.frey at post.ch


-----Urspr?ngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Klaus Gmeinwieser
Gesendet: Monday, May 26, 2014 3:40 PM
An: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 Beta7 not installable with autoyast

Hi all,

as unattended installation is (completely?) broken, does it makes sense
to try any unattended again? As the unattended installation is a main
issue to me (much much work to redo it in attended mode for component
tests) I am worried about my testresults.

How is this to be fixed? Is another Beta7 iso to be delivered (soon), or
is this to be fixed in in RC1 only? Is there a workaround which makes
any kind of Unattended installs possible...

Please let me know, how to proceed on this particular issue...

Thanks a lot in advance
Klaus

Am 26.05.2014 11:49, schrieb urs.frey at post.ch:
> Hi Josef
>
> The entire autoyast process is broken.
> Even if I manage to get some partitioning, the autoyast phase 2 with configuration is omitted completely leaving an unconfigured server
>
> So for me testing not possible
> SLES12 Beta7 unusable
>
> Best regards
>
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch
>
>
> -----Urspr?ngliche Nachricht-----
> Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Josef Reidinger
> Gesendet: Monday, May 26, 2014 10:54 AM
> An: sles-beta at lists.suse.com
> Betreff: Re: [sles-beta] SLES12 Beta7 not installable with autoyast
>
> On Mon, 26 May 2014 08:48:43 +0000
> <urs.frey at post.ch> wrote:
>
>> Hi
>>
>> There is a weird error when installing SLES12 Beta7 x86_64 using
>> autoyast
>>
>> I got this message on point: - create partition plans
>> Error
>> Internal error: Please report a bug report with logs
>> Details: no implicit conversion of String into integer
>> Caller: /mounts/mp_0001/usr/share/YaST2/include/autoinstall/autopart.rb:131:in
>> '[]'
>>
>>
>>
>
> Hi, you are the second one reporting this issue on this mailing list
> so looks like we break something. Please create bug report for it, so we
> can check where exactly is problem. Looks like some xml parsing error.
>
> Josef
>
>>
>>
>> I state installation of SLES12 Beta7 using autoyast is not possible
>>
>> Best regards
>> Urs Frey
>> Post CH AG
>> Informationstechnologie
>> IT Betrieb
>> Webergutstrasse 12
>> 3030 Bern (Zollikofen)
>> Telefon : ++41 (0)58 338 58 70
>> FAX     : ++41 (0)58 667 30 07
>> E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
>>
>>
>>
>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>

--
Klaus Gmeinwieser
T +49 (0)8121 72 4358 F +49 (0)8121 72 3173
E klaus.gmeinwieser at oce.com W www.oce.com

Oc? Printing Systems GmbH & Co. KG . A Canon Group Company
P.O. Box 1260 . 85581 Poing
Siemensallee 2 . 85586 Poing . Germany

Oc? enables its customers to manage their documents efficiently and
effectively by offering
innovative print and document management products and services for
professional
environments.

Oc? Printing Systems GmbH & Co. KG
The company is a limited partnership with its registered office in Poing
- Trade Register HRA 100955 (Amtsgericht M?nchen) - WEEE-Reg.-No. DE 888
05 443

General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH
Registered Office: Poing - Trade Register HRB 206480 (Amtsgericht M?nchen)
Executive Officer: Andr? Mittelsteiner
This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

From gjn at gjn.priv.at  Mon May 26 08:12:51 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Mon, 26 May 2014 16:12:51 +0200
Subject: [sles-beta] os-prober working ?
Message-ID: <1416771.Rh72FZ9t6Y@gjn.priv.at>

Hello,

should os-prober find a EFI Installation from SLES 12 B7 ?

or is this the old Bug from 13.1 with raid partitions?

On my system SLES 12 don't find a other SLES 12, but I remember the older Beta 
found a SLES 11.

I mean a new Bug.... :(.
-- 
mit freundlichen Gr??en / best Regards,

  G?nther J. Niederwimmer

From jreidinger at suse.com  Mon May 26 09:05:42 2014
From: jreidinger at suse.com (Josef Reidinger)
Date: Mon, 26 May 2014 17:05:42 +0200
Subject: [sles-beta] SLES12 Beta7 x86_64 Register Extensions and Modules
 Waiting Time
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99D665@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F99D665@HXMB12.pnet.ch>
Message-ID: <20140526170542.70174eaa@dhcp150.suse.cz>

Hi Urs,
please report it. I think problem is not in new menu for offline
addons, but step after it which tries to do local search, even if
registration is skipped.

Josef

On Mon, 26 May 2014 10:11:00 +0000
<urs.frey at post.ch> wrote:

> Hi
> 
> When doing a manual installation with SLES12 Beta7 x86_64, there is a
> new Menu Point allowing Register Extensions and Modules I miss a SKIP
> Button there! Now again I have to wait for the Firewall Timeout for
> Minutes..
> 
> SLES12 Manual Installation is a constant waiting time for me, a real
> No-Go
> 
> Please put in a SKIP Button in the Menu Point when Register Extensions
> 
> Thanks
> 
> Best regards
> 
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
> 
> 
> 


From Dick.Waite at softwareag.com  Mon May 26 09:12:20 2014
From: Dick.Waite at softwareag.com (Waite, Dick)
Date: Mon, 26 May 2014 15:12:20 +0000
Subject: [sles-beta] SLES 12 Beta7 on a Physical Machine
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D53837860@hqmbx6.eur.ad.sag>

Grand Afternoon,

          All my testing is done with VMware Workstation software on physical machines. Reading other peoples stories I don?t here ?workstation? so I went into the cellar and found an old x86_64 and added some memory, let the vacuum cleaner have some time and switched on.

          A basic install using defaults, I kept away from XFS as others and myself have issues there and it?s looking grand. It compiles and builds, the browser works. If I do the same on a VMware Workstation 10.0.2 I get issues as per the SR?s. Network is working without giving it some TLC.

          Well it?s a line in the sand. We have lots of Workstations and even more ESX stuff. I have a feeling in my water I?d better get some VMware good people involved in this. But we still have issues installing on zLinux and that only has grand z/VM under it. More on that later this week, but Thursday is a German / European holiday so there goes Friday too.

__R


___________________________________________
Dick Waite
Senior R&D Consultant
Phone:  +49 6151 92-1505
Mobile: +49 171 8393 769
Software AG
Uhlandstr. 12 | 64297 Darmstadt | Germany
www.softwareag.com<http://www.softwareag.com/>
___________________________________________



Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140526/bbb373b8/attachment.htm>

From rbrown at suse.de  Mon May 26 10:52:40 2014
From: rbrown at suse.de (Richard Brown)
Date: Mon, 26 May 2014 18:52:40 +0200
Subject: [sles-beta] NCC => SCC ?? novell/center invalid??
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99DB0E@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F99DB0E@HXMB12.pnet.ch>
Message-ID: <1401123160.31434.8.camel@ibrokeit.suse.de>

On Mon, 2014-05-26 at 15:56 +0000, urs.frey at post.ch wrote:
> Hi 
> I am desperately trying to log in tot he already longtime known URL
> http://www.novell.com/center
> Login not possible. URL seems to be dead
>  
> BUT when I try to log in to https://scc.suse.com I get an
> authentication mask from SUSE and after successful login I am in my
> NCC account!
>  
> HOW and why this? 
> Why without communication?
>  
> This is really not nice. I have something I need to do or to message
> in NCC and then just because SCC and NCC is messed up I need to play
> test-rabbit?
>  
> I do not like that. Please issue a change, when productive environment
> gets modified.
> NCC is productive for all of us having servers registered
>  
> Thanks
> Best regards
> 

I am able to login to both NCC using the URL you provided and SCC using
the URL you provided

I do not believe there has been any intentional 'shutdown' of NCC, and
as I've been able to successfully login to NCC from both my work, home,
and an independent 3rd connection, I suspect your problems might be a
local issue.

Can you get to
https://secure-www.novell.com/center/regadmin/jsps/home_app.jsp ?

Hope this helps

- Richard


-- 
-------------------------------------------------------------------
  Richard Brown, QA Engineer
  Phone +4991174053-361,  Fax +4991174053-483
  SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
  Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
  HRB 16746 (AG Nuernberg)
-------------------------------------------------------------------



From mpost at suse.com  Mon May 26 12:17:31 2014
From: mpost at suse.com (Mark Post)
Date: Mon, 26 May 2014 12:17:31 -0600
Subject: [sles-beta] SLES 12 Beta7 on a Physical Machine
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D53837860@hqmbx6.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D53837860@hqmbx6.eur.ad.sag>
Message-ID: <53834CFB0200006D00162778@prv-mh.provo.novell.com>

>>> On 5/26/2014 at 11:12 AM, "Waite, Dick" <Dick.Waite at softwareag.com> wrote: 
> But we still have issues installing on zLinux and that only has grand z/VM 
> under it. 

Details?  I've been doing a _lot_ of installs with very little problem.  So, exact parms used, etc., etc.


Mark Post


From darrent at akurit.com.au  Mon May 26 13:26:31 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Tue, 27 May 2014 05:26:31 +1000
Subject: [sles-beta] SLES12 Beta7 not installable with autoyast
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99D64C@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F99D5E2@HXMB12.pnet.ch>
	<20140526105427.6730ff9d@dhcp150.suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F99D64C@HXMB12.pnet.ch>
Message-ID: <CAEUhfEcrfAhZDv6u7t+kEgLazJvPuQ2VHyeBna0XiuoBK_oG7w@mail.gmail.com>

Team

I had "partial success" in that if I set partitioning to use defaults it
does the initial install.

I then get an incomplete secondary stage, which seems to hang, upon
rebooting it does seem to complete and produces a fairly usable install
(though I have not specifically checked if everything is
configured/installed).

Darren


On 26 May 2014 19:49, <urs.frey at post.ch> wrote:

> Hi Josef
>
> The entire autoyast process is broken.
> Even if I manage to get some partitioning, the autoyast phase 2 with
> configuration is omitted completely leaving an unconfigured server
>
> So for me testing not possible
> SLES12 Beta7 unusable
>
> Best regards
>
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail:   urs.frey at post.ch
>
>
> -----Urspr?ngliche Nachricht-----
> Von: sles-beta-bounces at lists.suse.com [mailto:
> sles-beta-bounces at lists.suse.com] Im Auftrag von Josef Reidinger
> Gesendet: Monday, May 26, 2014 10:54 AM
> An: sles-beta at lists.suse.com
> Betreff: Re: [sles-beta] SLES12 Beta7 not installable with autoyast
>
> On Mon, 26 May 2014 08:48:43 +0000
> <urs.frey at post.ch> wrote:
>
> > Hi
> >
> > There is a weird error when installing SLES12 Beta7 x86_64 using
> > autoyast
> >
> > I got this message on point: - create partition plans
> > Error
> > Internal error: Please report a bug report with logs
> > Details: no implicit conversion of String into integer
> > Caller:
> /mounts/mp_0001/usr/share/YaST2/include/autoinstall/autopart.rb:131:in
> > '[]'
> >
> >
> >
>
> Hi, you are the second one reporting this issue on this mailing list
> so looks like we break something. Please create bug report for it, so we
> can check where exactly is problem. Looks like some xml parsing error.
>
> Josef
>
> >
> >
> > I state installation of SLES12 Beta7 using autoyast is not possible
> >
> > Best regards
> > Urs Frey
> > Post CH AG
> > Informationstechnologie
> > IT Betrieb
> > Webergutstrasse 12
> > 3030 Bern (Zollikofen)
> > Telefon : ++41 (0)58 338 58 70
> > FAX     : ++41 (0)58 667 30 07
> > E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>
> >
> >
> >
>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>



-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140527/6a788f8e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140527/6a788f8e/attachment.jpg>

From swehnert at suse.com  Tue May 27 01:02:10 2014
From: swehnert at suse.com (Sascha Wehnert)
Date: Tue, 27 May 2014 09:02:10 +0200
Subject: [sles-beta] NCC => SCC ?? novell/center invalid??
In-Reply-To: <1401123160.31434.8.camel@ibrokeit.suse.de>
References: <40637DBB36AF3941B243A286A432CA0B0F99DB0E@HXMB12.pnet.ch>
	<1401123160.31434.8.camel@ibrokeit.suse.de>
Message-ID: <53843872.9020509@suse.com>

Hi Richard, Hi Urs,

currently the login buttons on some of our websites don't function, I
reported this issue already and wait for it to get resolved. In the mean
time, please don't use the login button but press enter in the password
field. That grants at least for me access to the mentioned sites I try
to log in to.

If this does not do the trick for you please ping me off list so we can
take a closer look at it.

Cheers,
Sascha
-- 
Sascha Andree Wehnert, Senior Technical Support Engineer
Email: swehnert at suse.com

Attachmate Group Germany GmbH, N?rdlicher Zubringer 9-11,
40470 D?sseldorf, HRB 202401 (AG M?nchen)
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer

From fcrozat at suse.com  Tue May 27 02:09:28 2014
From: fcrozat at suse.com (Frederic Crozat)
Date: Tue, 27 May 2014 10:09:28 +0200
Subject: [sles-beta] Kernel crash.
In-Reply-To: <1533950.UTi0Gaixhr@gjn.priv.at>
References: <1533950.UTi0Gaixhr@gjn.priv.at>
Message-ID: <1401178168.16414.107.camel@par-r81vxc7.par.novell.com>

Le lundi 26 mai 2014 ? 14:06 +0200, G?nther J. Niederwimmer a ?crit :
> Hello,
> 
> is there a way to disable same Programs on start time.
> 
> I make a new install witn KVM and 2 Clients now after the last Boot I have a 
> kernel crash and reboot usw.
> 
> now I like to disable on Boot Time systemd libvirt_guest is there a way (?), 
> to find out the Problem.

systemctl disable libvirt_guest.service (if that is the name of the
service).

You could also still use chkconfig libvirt_guess off (as in SLE11.)

> In older times I start from a stick and delete the File in "/init.d" ;)

This is NEVER needed with systemd. If you really want to "hide" a
service, use "systemctl mask service_name"


-- 
Frederic Crozat
Project Manager Enterprise Desktop
SUSE


From sarsene at suse.com  Tue May 27 02:46:14 2014
From: sarsene at suse.com (Simona Arsene)
Date: Tue, 27 May 2014 10:46:14 +0200
Subject: [sles-beta] NCC => SCC ?? novell/center invalid??
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99DB0E@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F99DB0E@HXMB12.pnet.ch>
Message-ID: <53846CF602000022001715A0@smtp.nue.novell.com>

Hi Urs, 

I just want to ensure you that we have not changed anything. SCC and NCC use 
a common solution acting as a SSO (single sign on) and it looks like last evening the 
NCC parts was not working properly. 

This is an issue with our current Customer Center and one of the reasons
why we have invested a lot of time in cleaning this up and building SCC. 

I want to ensure you that we have not removed any access to NCC and 
we'll not do that without communication. 

I would like to encourage you to contact Sascha directly so that he can work on 
the login issue that we're facing. 

Once again, I would like to apologize for this inconvenient, I know that this 
should never happen and I understand your position. At the moment, I can 
assure you that the SCC team is working really hard in putting together the 
pieces for the new SUSE customer center. 

Thank you for your understanding, 
Simona 


>>> On 5/26/2014 at 05:56 PM, in message
<40637DBB36AF3941B243A286A432CA0B0F99DB0E at HXMB12.pnet.ch>, <urs.frey at post.ch>
wrote: 
> Hi 
> I am desperately trying to log in tot he already longtime known URL  
> http://www.novell.com/center 
> Login not possible. URL seems to be dead 
>   
> BUT when I try to log in to https://scc.suse.com I get an authentication  
> mask from SUSE and after successful login I am in my NCC account! 
>   
> HOW and why this? 
> Why without communication? 
>   
> This is really not nice. I have something I need to do or to message in NCC  
> and then just because SCC and NCC is messed up I need to play test-rabbit? 
>   
> I do not like that. Please issue a change, when productive environment gets  
> modified. 
> NCC is productive for all of us having servers registered 
>   
> Thanks 
> Best regards 
>   
> Urs Frey                                              
> Post CH AG 
> Informationstechnologie 
> IT Betrieb 
> Webergutstrasse 12 
> 3030 Bern (Zollikofen) 
> Telefon : ++41 (0)58 338 58 70 
> FAX     : ++41 (0)58 667 30 07 
> E-Mail:   urs.frey at post.ch 




From urs.frey at post.ch  Tue May 27 03:05:38 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Tue, 27 May 2014 09:05:38 +0000
Subject: [sles-beta] NCC => SCC ?? novell/center invalid??
In-Reply-To: <53846CF602000022001715A0@smtp.nue.novell.com>
References: <40637DBB36AF3941B243A286A432CA0B0F99DB0E@HXMB12.pnet.ch>
	<53846CF602000022001715A0@smtp.nue.novell.com>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F99DCF8@HXMB12.pnet.ch>

Hello Simona

Thank you very much for your kind answer.
See I am working in a high productivity environment.
Absolutely no service interrupt without official change.
So please accept my apologies for my harsh reaction yesterday.
There were too many things not working with Beta7 and NCC and and..

Best regards

Urs Frey????????????????????????????????????????????? 
Post CH AG
Informationstechnologie
IT Betrieb 
Webergutstrasse 12 
3030 Bern (Zollikofen) 
Telefon : ++41 (0)58 338 58 70 
FAX???? : ++41 (0)58 667 30 07 
E-Mail:?? urs.frey at post.ch

-----Urspr?ngliche Nachricht-----
Von: Simona Arsene [mailto:sarsene at suse.com] 
Gesendet: Tuesday, May 27, 2014 10:46 AM
An: sles-beta at lists.suse.com; Frey Urs, IT222
Betreff: Re: [sles-beta] NCC => SCC ?? novell/center invalid??

Hi Urs, 

I just want to ensure you that we have not changed anything. SCC and NCC use 
a common solution acting as a SSO (single sign on) and it looks like last evening the 
NCC parts was not working properly. 

This is an issue with our current Customer Center and one of the reasons
why we have invested a lot of time in cleaning this up and building SCC. 

I want to ensure you that we have not removed any access to NCC and 
we'll not do that without communication. 

I would like to encourage you to contact Sascha directly so that he can work on 
the login issue that we're facing. 

Once again, I would like to apologize for this inconvenient, I know that this 
should never happen and I understand your position. At the moment, I can 
assure you that the SCC team is working really hard in putting together the 
pieces for the new SUSE customer center. 

Thank you for your understanding, 
Simona 


>>> On 5/26/2014 at 05:56 PM, in message
<40637DBB36AF3941B243A286A432CA0B0F99DB0E at HXMB12.pnet.ch>, <urs.frey at post.ch>
wrote: 
> Hi 
> I am desperately trying to log in tot he already longtime known URL  
> http://www.novell.com/center 
> Login not possible. URL seems to be dead 
>   
> BUT when I try to log in to https://scc.suse.com I get an authentication  
> mask from SUSE and after successful login I am in my NCC account! 
>   
> HOW and why this? 
> Why without communication? 
>   
> This is really not nice. I have something I need to do or to message in NCC  
> and then just because SCC and NCC is messed up I need to play test-rabbit? 
>   
> I do not like that. Please issue a change, when productive environment gets  
> modified. 
> NCC is productive for all of us having servers registered 
>   
> Thanks 
> Best regards 
>   
> Urs Frey                                              
> Post CH AG 
> Informationstechnologie 
> IT Betrieb 
> Webergutstrasse 12 
> 3030 Bern (Zollikofen) 
> Telefon : ++41 (0)58 338 58 70 
> FAX     : ++41 (0)58 667 30 07 
> E-Mail:   urs.frey at post.ch 


From gjn at gjn.priv.at  Tue May 27 05:33:28 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Tue, 27 May 2014 13:33:28 +0200
Subject: [sles-beta] autoinst.xml
Message-ID: <4032527.mCaYXyPQbu@gjn.priv.at>

Hello	,

should it be possible to install with a autoinst.xml on a UEFI system?

I can't found in YaST2 a place to load the autoinst.xml.

-- 
mit freundlichen Gr??en / best Regards,

  G?nther J. Niederwimmer

From aginies at suse.com  Tue May 27 14:31:27 2014
From: aginies at suse.com (Antoine Ginies)
Date: Tue, 27 May 2014 22:31:27 +0200
Subject: [sles-beta] static libraries
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
Message-ID: <20140527203127.GA24153@linux-w520.guibland.com>

Wendy Palm:
> We ran into a problem trying to build some of our internal tests.
> It looks like SLES12 no longer includes libc.a or libpthread.a.
> 
> Is it planned that static libraries will no longer be provided?

hello,
static libraries are provided in the SLE-12-SDK-DVD iso.
"glibc-devel-static*.rpm" will provide you libc.a and libpthread.a.

Regards.

Antoine



-- 
Antoine Ginies <aginies at suse.com>
Project Manager
SUSE France

From wendy at cray.com  Tue May 27 14:38:56 2014
From: wendy at cray.com (Wendy Palm)
Date: Tue, 27 May 2014 20:38:56 +0000
Subject: [sles-beta] static libraries
In-Reply-To: <20140527203127.GA24153@linux-w520.guibland.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
Message-ID: <D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>

Thanks.  we hadn't noticed those.

> -----Original Message-----
> From: Antoine Ginies [mailto:aginies at suse.com]
> Sent: Tuesday, May 27, 2014 3:31 PM
> To: Wendy Palm
> Cc: sles-beta at lists.suse.com
> Subject: Re: [sles-beta] static libraries
> 
> Wendy Palm:
> > We ran into a problem trying to build some of our internal tests.
> > It looks like SLES12 no longer includes libc.a or libpthread.a.
> >
> > Is it planned that static libraries will no longer be provided?
> 
> hello,
> static libraries are provided in the SLE-12-SDK-DVD iso.
> "glibc-devel-static*.rpm" will provide you libc.a and libpthread.a.
> 
> Regards.
> 
> Antoine
> 
> 
> 
> --
> Antoine Ginies <aginies at suse.com>
> Project Manager
> SUSE France

From wendy at cray.com  Tue May 27 15:20:32 2014
From: wendy at cray.com (Wendy Palm)
Date: Tue, 27 May 2014 21:20:32 +0000
Subject: [sles-beta] static libraries
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
Message-ID: <D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>

Ok, what about libbz2.a?

It's not included in glibc-devel-static (at least as of beta 6.  We're still in the process of downloading beta7).


> -----Original Message-----
> From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> bounces at lists.suse.com] On Behalf Of Wendy Palm
> Sent: Tuesday, May 27, 2014 3:39 PM
> To: Antoine Ginies
> Cc: sles-beta at lists.suse.com
> Subject: Re: [sles-beta] static libraries
> 
> Thanks.  we hadn't noticed those.
> 
> > -----Original Message-----
> > From: Antoine Ginies [mailto:aginies at suse.com]
> > Sent: Tuesday, May 27, 2014 3:31 PM
> > To: Wendy Palm
> > Cc: sles-beta at lists.suse.com
> > Subject: Re: [sles-beta] static libraries
> >
> > Wendy Palm:
> > > We ran into a problem trying to build some of our internal tests.
> > > It looks like SLES12 no longer includes libc.a or libpthread.a.
> > >
> > > Is it planned that static libraries will no longer be provided?
> >
> > hello,
> > static libraries are provided in the SLE-12-SDK-DVD iso.
> > "glibc-devel-static*.rpm" will provide you libc.a and libpthread.a.
> >
> > Regards.
> >
> > Antoine
> >
> >
> >
> > --
> > Antoine Ginies <aginies at suse.com>
> > Project Manager
> > SUSE France
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta

From darrent at akurit.com.au  Tue May 27 21:20:28 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 13:20:28 +1000
Subject: [sles-beta] ISCSI issues with SLES12B7 - part1 ( ISCSI Target
	driver)
Message-ID: <CAEUhfEdnGu96m3LSqLLtyDF7s=Z9ayyw+-9w199xF+hEayBD8Q@mail.gmail.com>

Team

The new "ISCSI LIO Target" configuration tool does not appear to allow
multiple IP addresses to be bound to new targets.

There is a "pull down" which allows a single address to be assigned only.

With SLES11 SP3, I could have the ISCSI Targets bound to multiple host IP
addresses. This allow a "multipath" configuration to be used (assuming both
the Host and 'initiator' clients have multiple NIC' configured on separate
subnets).

With the ISCSI target available on multiple IP addresses, the client could
have multiple, separate, connections to the same target. The clients
multipath driver would then identify these as the same destination and
would configure path redundancy, removing "single point of failue" risk
associated with ISCSI resources from a single NIC/Network/path.

I cannot see how this same configuration can be done under SLES12B7

Regards
Darren

-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/434eedb1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/434eedb1/attachment.jpg>

From darrent at akurit.com.au  Tue May 27 21:33:16 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 13:33:16 +1000
Subject: [sles-beta] ISCSI issues with SLES12B7 - part2 ( ISCSI
	'initiator' driver)
Message-ID: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>

Team

The ISCSI "initiator" does not seem to login/connect to a working ISCSI
Target (I tested both a SLES12B7 trarget server and a "know good/working"
SLES11SP3 server).

The ISCSI "discovery" works but I cannot then connect/login to the actual
targer.

Regards
Darren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/1016211d/attachment.htm>

From darrent at akurit.com.au  Wed May 28 00:35:25 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 16:35:25 +1000
Subject: [sles-beta] A working autoyast example for SLES12B7
Message-ID: <CAEUhfEctLYKwPSHFNJGJK12DmWAXZ9a+ETO+eg428-GsXt2asA@mail.gmail.com>

Team

Please find attached a "mostly working" example autoyast file for SLES12B7

Notes:
1. It pauses at the "confirm configuration" screen, you need to press
"install" button to continue. (what setting is required to stop this?)
2. I have configured the HA option to install as an add-on, please adapt or
remove as suits your site/testing
3. Clearly names, network card configurations, IP addresses, DNS zone etc
will need to be customised for your site.

To use this you need to create a "network install" server (using the YAST2
installserver option) and import SLES12B7 (and optionally SLES12-HA-B7)

1. Boot from a preconfigured PXE or the
"SLE-12-Server-MINI-ISO-x86_64-Beta7-DVD" media
2. use arrow keys and select "install" DO NOT HIT RETURN KEY AT THIS POINT
3. enter the optional peramiters:
install=http://{yourinstallserveripaddress}/{pathtoinstallmedia}/CD1
autoyast=http://
{yourinstallserveripaddress}/{pathtoautoyastfile/node1-autoyast.xml

I hope others find this useful as it's taken me a long while to get this
far...


-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/8566fd59/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/8566fd59/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: node1-autoyast.xml
Type: text/xml
Size: 9422 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/8566fd59/attachment.xml>

From darrent at akurit.com.au  Wed May 28 00:40:56 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 16:40:56 +1000
Subject: [sles-beta] A working autoyast example for SLES12B7
In-Reply-To: <CAEUhfEctLYKwPSHFNJGJK12DmWAXZ9a+ETO+eg428-GsXt2asA@mail.gmail.com>
References: <CAEUhfEctLYKwPSHFNJGJK12DmWAXZ9a+ETO+eg428-GsXt2asA@mail.gmail.com>
Message-ID: <CAEUhfEcnu8BijRP7tr+h9vz3t-VSjiykye_YK=vy8YGVrA5s1A@mail.gmail.com>

Team

Oops, forgot to mention... the root password in the example file is
"novell". Probably not a good choice in production environments.

Darren


On 28 May 2014 16:35, Darren Thompson <darrent at akurit.com.au> wrote:

> Team
>
> Please find attached a "mostly working" example autoyast file for SLES12B7
>
> Notes:
> 1. It pauses at the "confirm configuration" screen, you need to press
> "install" button to continue. (what setting is required to stop this?)
> 2. I have configured the HA option to install as an add-on, please adapt
> or remove as suits your site/testing
> 3. Clearly names, network card configurations, IP addresses, DNS zone etc
> will need to be customised for your site.
>
> To use this you need to create a "network install" server (using the YAST2
> installserver option) and import SLES12B7 (and optionally SLES12-HA-B7)
>
> 1. Boot from a preconfigured PXE or the
> "SLE-12-Server-MINI-ISO-x86_64-Beta7-DVD" media
> 2. use arrow keys and select "install" DO NOT HIT RETURN KEY AT THIS POINT
> 3. enter the optional peramiters: install=http://{yourinstallserveripaddress}/{pathtoinstallmedia}/CD1
> autoyast=http://
> {yourinstallserveripaddress}/{pathtoautoyastfile/node1-autoyast.xml
>
> I hope others find this useful as it's taken me a long while to get this
> far...
>
>
> --
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au <steve at akurit.com.au>
> Web: www.akurit.com.au
>



-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/efd1c4fc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/efd1c4fc/attachment.jpg>

From urs.frey at post.ch  Wed May 28 01:12:19 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Wed, 28 May 2014 07:12:19 +0000
Subject: [sles-beta] A working autoyast example for SLES12B7
In-Reply-To: <CAEUhfEctLYKwPSHFNJGJK12DmWAXZ9a+ETO+eg428-GsXt2asA@mail.gmail.com>
References: <CAEUhfEctLYKwPSHFNJGJK12DmWAXZ9a+ETO+eg428-GsXt2asA@mail.gmail.com>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F99DF1F@HXMB12.pnet.ch>

Hi Darren

>1. It pauses at the "confirm configuration" screen, you need to press "install" button to continue. (what setting is required to stop this?)
In autoyast there is a section called <general> including some global definitions
Please observe the first line under the tag <mode>
      <confirm config:type="boolean">true</confirm>
If you set this to false, it won?t stop anymore on the yast config screen


  <general>
    <mode>
      <confirm config:type="boolean">true</confirm>
      <forceboot config:type="boolean">false</forceboot>
      <halt config:type="boolean">false</halt>
      <second_stage config:type="boolean">true</second_stage>
    </mode>
    <signature-handling>
      <accept_unsigned_file         config:type="boolean">true</accept_unsigned_file>
      <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum>
      <accept_verification_failed   config:type="boolean">true</accept_verification_failed>
      <accept_unknown_gpg_key       config:type="boolean">true</accept_unknown_gpg_key>
      <import_gpg_key               config:type="boolean">true</import_gpg_key>
      <accept_non_trusted_gpg_key   config:type="boolean">true</accept_non_trusted_gpg_key>
    </signature-handling>
    <storage>
      <partition_alignment config:type="symbol">align_optimal</partition_alignment>
      <start_multipath config:type="boolean">false</start_multipath>
    </storage>
  </general>

>I hope others find this useful as it's taken me a long while to get this far...
Thank you very much, indeed.

Best regards

Urs Frey
Post CH AG
Informationstechnologie
IT Betrieb
Webergutstrasse 12
3030 Bern (Zollikofen)
Telefon : ++41 (0)58 338 58 70
FAX     : ++41 (0)58 667 30 07
E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>

Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Darren Thompson
Gesendet: Wednesday, May 28, 2014 8:35 AM
An: sles-beta at lists.suse.com; SUSE Linux Enterprise High Availability Authorized Beta Program
Betreff: [sles-beta] A working autoyast example for SLES12B7

Team

Please find attached a "mostly working" example autoyast file for SLES12B7

Notes:
1. It pauses at the "confirm configuration" screen, you need to press "install" button to continue. (what setting is required to stop this?)
2. I have configured the HA option to install as an add-on, please adapt or remove as suits your site/testing
3. Clearly names, network card configurations, IP addresses, DNS zone etc will need to be customised for your site.

To use this you need to create a "network install" server (using the YAST2 installserver option) and import SLES12B7 (and optionally SLES12-HA-B7)

1. Boot from a preconfigured PXE or the "SLE-12-Server-MINI-ISO-x86_64-Beta7-DVD" media
2. use arrow keys and select "install" DO NOT HIT RETURN KEY AT THIS POINT
3. enter the optional peramiters: install=http://{yourinstallserveripaddress}/{pathtoinstallmedia}/CD1 autoyast=http://{yourinstallserveripaddress}/{pathtoautoyastfile/node1-autoyast.xml

I hope others find this useful as it's taken me a long while to get this far...


--

Darren Thompson

Professional Services Engineer / Consultant

 [cid:image001.jpg at 01CB7C0C.6C6A2AE0]

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au<mailto:steve at akurit.com.au>
Web: www.akurit.com.au<http://www.akurit.com.au/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/441ac163/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: image001.jpg
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/441ac163/attachment.jpg>

From darrent at akurit.com.au  Wed May 28 01:37:14 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 17:37:14 +1000
Subject: [sles-beta] A working autoyast example for SLES12B7
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99DF1F@HXMB12.pnet.ch>
References: <CAEUhfEctLYKwPSHFNJGJK12DmWAXZ9a+ETO+eg428-GsXt2asA@mail.gmail.com>
	<40637DBB36AF3941B243A286A432CA0B0F99DF1F@HXMB12.pnet.ch>
Message-ID: <CAEUhfEd1w9_X4==J0NT4y1s_CfoE7XFGLMCvQo8SikgZtiEdbA@mail.gmail.com>

Urs

Thank you... it seems so simple/obvious in hindsight but I just could not
see it.

Darren


On 28 May 2014 17:12, <urs.frey at post.ch> wrote:

>  Hi Darren
>
>
>
> >1. It pauses at the "confirm configuration" screen, you need to press
> "install" button to continue. (what setting is required to stop this?)
>
> In autoyast there is a section called <general> including some global
> definitions
>
> Please observe the first line under the tag <mode>
>
>       <confirm config:type="boolean">true</confirm>
>
> If you set this to false, it won?t stop anymore on the yast config screen
>
>
>
>
>
>   <general>
>
>     <mode>
>
>       <confirm config:type="boolean">true</confirm>
>
>       <forceboot config:type="boolean">false</forceboot>
>
>       <halt config:type="boolean">false</halt>
>
>       <second_stage config:type="boolean">true</second_stage>
>
>     </mode>
>
>     <signature-handling>
>
>       <accept_unsigned_file
> config:type="boolean">true</accept_unsigned_file>
>
>       <accept_file_without_checksum
> config:type="boolean">true</accept_file_without_checksum>
>
>       <accept_verification_failed
> config:type="boolean">true</accept_verification_failed>
>
>       <accept_unknown_gpg_key
> config:type="boolean">true</accept_unknown_gpg_key>
>
>       <import_gpg_key
> config:type="boolean">true</import_gpg_key>
>
>       <accept_non_trusted_gpg_key
> config:type="boolean">true</accept_non_trusted_gpg_key>
>
>     </signature-handling>
>
>     <storage>
>
>       <partition_alignment
> config:type="symbol">align_optimal</partition_alignment>
>
>       <start_multipath config:type="boolean">false</start_multipath>
>
>     </storage>
>
>   </general>
>
>
>
> >I hope others find this useful as it's taken me a long while to get this
> far...
>
> Thank you very much, indeed.
>
>
>
> Best regards
>
>
>
> Urs Frey
>
> Post CH AG
>
> Informationstechnologie
>
> IT Betrieb
>
> Webergutstrasse 12
>
> 3030 Bern (Zollikofen)
>
> Telefon : ++41 (0)58 338 58 70
>
> FAX     : ++41 (0)58 667 30 07
>
> E-Mail:   urs.frey at post.ch
>
>
>
> *Von:* sles-beta-bounces at lists.suse.com [mailto:
> sles-beta-bounces at lists.suse.com] *Im Auftrag von *Darren Thompson
> *Gesendet:* Wednesday, May 28, 2014 8:35 AM
> *An:* sles-beta at lists.suse.com; SUSE Linux Enterprise High Availability
> Authorized Beta Program
> *Betreff:* [sles-beta] A working autoyast example for SLES12B7
>
>
>
> Team
>
>
>
> Please find attached a "mostly working" example autoyast file for SLES12B7
>
>
>
> Notes:
>
> 1. It pauses at the "confirm configuration" screen, you need to press
> "install" button to continue. (what setting is required to stop this?)
>
> 2. I have configured the HA option to install as an add-on, please adapt
> or remove as suits your site/testing
>
> 3. Clearly names, network card configurations, IP addresses, DNS zone etc
> will need to be customised for your site.
>
>
>
> To use this you need to create a "network install" server (using the YAST2
> installserver option) and import SLES12B7 (and optionally SLES12-HA-B7)
>
>
>
> 1. Boot from a preconfigured PXE or the
> "SLE-12-Server-MINI-ISO-x86_64-Beta7-DVD" media
>
> 2. use arrow keys and select "install" DO NOT HIT RETURN KEY AT THIS POINT
>
> 3. enter the optional peramiters: install=http://{yourinstallserveripaddress}/{pathtoinstallmedia}/CD1
> autoyast=http://
> {yourinstallserveripaddress}/{pathtoautoyastfile/node1-autoyast.xml
>
>
>
> I hope others find this useful as it's taken me a long while to get this
> far...
>
>
>
>
> --
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au <steve at akurit.com.au>
> Web: www.akurit.com.au
>



-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/28b56ba5/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/28b56ba5/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/28b56ba5/attachment-0001.jpg>

From rbrown at suse.de  Wed May 28 02:15:01 2014
From: rbrown at suse.de (Richard Brown)
Date: Wed, 28 May 2014 10:15:01 +0200
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
Message-ID: <1401264901.31434.25.camel@ibrokeit.suse.de>

On Wed, 2014-05-28 at 13:33 +1000, Darren Thompson wrote:
> Team
> 
> 
> 
> The ISCSI "initiator" does not seem to login/connect to a working
> ISCSI Target (I tested both a SLES12B7 trarget server and a "know
> good/working" SLES11SP3 server).
> 
> 
> The ISCSI "discovery" works but I cannot then connect/login to the
> actual targer.
> 
> 
> Regards
> Darren 
> _______________________________________________
> sleha-beta mailing list
> sleha-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sleha-beta

Hi Darren,

In SLE 12 we have only the iSCSI LIO Target and not the ietd iSCSI
Target also available in previous versions

One of the new features of the LIO Target is that it supports proper LUN
mapping - the ability to decide which LUNs are presented to which
Clients/Initiators as which LUN numbers

This *requires* you to fill in the LUN mapping section of the iSCSI LIO
Target in YaST on your target - it pops up after you configure a target,
but if you're not aware of why it's so important, I understand you might
just click next and leave the Initiator/LUN mapping table blank (I did
the same first time round..)

Failure to do this, results in the behaviour you're noticing.

You'll need the 'initiator name' for each iSCSI initiator connecting to
your target, that can be found in /etc/iscsi/initiatorname on each of
your initiators.

Hope this helps,

- Richard

-- 
-------------------------------------------------------------------
  Richard Brown, QA Engineer
  Phone +4991174053-361,  Fax +4991174053-483
  SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
  Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
  HRB 16746 (AG Nuernberg)
-------------------------------------------------------------------



From aginies at suse.com  Wed May 28 02:21:50 2014
From: aginies at suse.com (Antoine Ginies)
Date: Wed, 28 May 2014 10:21:50 +0200
Subject: [sles-beta] static libraries
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
Message-ID: <20140528082150.GB6568@linux-w520.guibland.com>

Wendy Palm:
> Ok, what about libbz2.a?
> 
> It's not included in glibc-devel-static (at least as of beta 6.  We're still in the process of downloading beta7).

We do not provide bzip2-devel-static libraries in SLE12. I have done a check in
SLE11SP3 and it seems we don't provide it also.

Regards.

Antoine

> > -----Original Message-----
> > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> > bounces at lists.suse.com] On Behalf Of Wendy Palm
> > Sent: Tuesday, May 27, 2014 3:39 PM
> > To: Antoine Ginies
> > Cc: sles-beta at lists.suse.com
> > Subject: Re: [sles-beta] static libraries
> > 
> > Thanks.  we hadn't noticed those.
> > 
> > > -----Original Message-----
> > > From: Antoine Ginies [mailto:aginies at suse.com]
> > > Sent: Tuesday, May 27, 2014 3:31 PM
> > > To: Wendy Palm
> > > Cc: sles-beta at lists.suse.com
> > > Subject: Re: [sles-beta] static libraries
> > >
> > > Wendy Palm:
> > > > We ran into a problem trying to build some of our internal tests.
> > > > It looks like SLES12 no longer includes libc.a or libpthread.a.
> > > >
> > > > Is it planned that static libraries will no longer be provided?
> > >
> > > hello,
> > > static libraries are provided in the SLE-12-SDK-DVD iso.
> > > "glibc-devel-static*.rpm" will provide you libc.a and libpthread.a.
> > >
> > > Regards.
> > >
> > > Antoine
> > >
> > >
> > >
> > > --
> > > Antoine Ginies <aginies at suse.com>
> > > Project Manager
> > > SUSE France
> > _______________________________________________
> > sles-beta mailing list
> > sles-beta at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/sles-beta
> 

-- 
Antoine Ginies <aginies at suse.com>
Project Manager
SUSE France

From darrent at akurit.com.au  Wed May 28 02:31:45 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 18:31:45 +1000
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <1401264901.31434.25.camel@ibrokeit.suse.de>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
	<1401264901.31434.25.camel@ibrokeit.suse.de>
Message-ID: <CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>

Richard

That partially explains things at the SLES12B7 target end but why can't I
connect to a "know good" SLES11 SP3 ISCSI target?

Darren


On 28 May 2014 18:15, Richard Brown <rbrown at suse.de> wrote:

> On Wed, 2014-05-28 at 13:33 +1000, Darren Thompson wrote:
> > Team
> >
> >
> >
> > The ISCSI "initiator" does not seem to login/connect to a working
> > ISCSI Target (I tested both a SLES12B7 trarget server and a "know
> > good/working" SLES11SP3 server).
> >
> >
> > The ISCSI "discovery" works but I cannot then connect/login to the
> > actual targer.
> >
> >
> > Regards
> > Darren
> > _______________________________________________
> > sleha-beta mailing list
> > sleha-beta at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/sleha-beta
>
> Hi Darren,
>
> In SLE 12 we have only the iSCSI LIO Target and not the ietd iSCSI
> Target also available in previous versions
>
> One of the new features of the LIO Target is that it supports proper LUN
> mapping - the ability to decide which LUNs are presented to which
> Clients/Initiators as which LUN numbers
>
> This *requires* you to fill in the LUN mapping section of the iSCSI LIO
> Target in YaST on your target - it pops up after you configure a target,
> but if you're not aware of why it's so important, I understand you might
> just click next and leave the Initiator/LUN mapping table blank (I did
> the same first time round..)
>
> Failure to do this, results in the behaviour you're noticing.
>
> You'll need the 'initiator name' for each iSCSI initiator connecting to
> your target, that can be found in /etc/iscsi/initiatorname on each of
> your initiators.
>
> Hope this helps,
>
> - Richard
>
> --
> -------------------------------------------------------------------
>   Richard Brown, QA Engineer
>   Phone +4991174053-361,  Fax +4991174053-483
>   SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
>   Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
>   HRB 16746 (AG Nuernberg)
> -------------------------------------------------------------------
>
>
>


-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/454398d2/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/454398d2/attachment.jpg>

From rbrown at suse.de  Wed May 28 02:36:43 2014
From: rbrown at suse.de (Richard Brown)
Date: Wed, 28 May 2014 10:36:43 +0200
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
	<1401264901.31434.25.camel@ibrokeit.suse.de>
	<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>
Message-ID: <1401266203.31434.30.camel@ibrokeit.suse.de>

On Wed, 2014-05-28 at 18:31 +1000, Darren Thompson wrote:
> Richard
> 
> 
> That partially explains things at the SLES12B7 target end but why
> can't I connect to a "know good" SLES11 SP3 ISCSI target?
> 
> 
> Darren

For that, I have no clue - I've just tested it, but telling you that 'it
works here' is probably of little comfort. 

Any clues in /var/log/messages from the target or initiators?

- Richard
> 
> 
> On 28 May 2014 18:15, Richard Brown <rbrown at suse.de> wrote:
>         On Wed, 2014-05-28 at 13:33 +1000, Darren Thompson wrote:
>         > Team
>         >
>         >
>         >
>         > The ISCSI "initiator" does not seem to login/connect to a
>         working
>         > ISCSI Target (I tested both a SLES12B7 trarget server and a
>         "know
>         > good/working" SLES11SP3 server).
>         >
>         >
>         > The ISCSI "discovery" works but I cannot then connect/login
>         to the
>         > actual targer.
>         >
>         >
>         > Regards
>         > Darren
>         > _______________________________________________
>         > sleha-beta mailing list
>         > sleha-beta at lists.suse.com
>         > http://lists.suse.com/mailman/listinfo/sleha-beta
>         
>         Hi Darren,
>         
>         In SLE 12 we have only the iSCSI LIO Target and not the ietd
>         iSCSI
>         Target also available in previous versions
>         
>         One of the new features of the LIO Target is that it supports
>         proper LUN
>         mapping - the ability to decide which LUNs are presented to
>         which
>         Clients/Initiators as which LUN numbers
>         
>         This *requires* you to fill in the LUN mapping section of the
>         iSCSI LIO
>         Target in YaST on your target - it pops up after you configure
>         a target,
>         but if you're not aware of why it's so important, I understand
>         you might
>         just click next and leave the Initiator/LUN mapping table
>         blank (I did
>         the same first time round..)
>         
>         Failure to do this, results in the behaviour you're noticing.
>         
>         You'll need the 'initiator name' for each iSCSI initiator
>         connecting to
>         your target, that can be found in /etc/iscsi/initiatorname on
>         each of
>         your initiators.
>         
>         Hope this helps,
>         
>         - Richard
>         
>         --
>         -------------------------------------------------------------------
>           Richard Brown, QA Engineer
>           Phone +4991174053-361,  Fax +4991174053-483
>           SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
>           Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix
>         Imendoerffer,
>           HRB 16746 (AG Nuernberg)
>         -------------------------------------------------------------------
>         
>         
> 
> 
> 
> 
> -- 
> Darren Thompson
> 
> Professional Services Engineer / Consultant
> 
>  cid:image001.jpg at 01CB7C0C.6C6A2AE0
> 
> Level 3, 60 City Road
> 
> Southgate, VIC 3006
> 
> Mb: 0400 640 414
> 
> Mail: darrent at akurit.com.au
> Web: www.akurit.com.au
> 
> 


-- 
-------------------------------------------------------------------
  Richard Brown, QA Engineer
  Phone +4991174053-361,  Fax +4991174053-483
  SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
  Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
  HRB 16746 (AG Nuernberg)
-------------------------------------------------------------------



From darrent at akurit.com.au  Wed May 28 03:18:37 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 19:18:37 +1000
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <1401266203.31434.30.camel@ibrokeit.suse.de>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
	<1401264901.31434.25.camel@ibrokeit.suse.de>
	<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>
	<1401266203.31434.30.camel@ibrokeit.suse.de>
Message-ID: <CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>

Richard

That leaves a couple of posibilites:
1. I have just got all my configurations wrong at both ends (sadly, highly
possible)
2. The SLES12 initiator is no longer compatible with the SLES11 target (bad)
3. There is a bug that i have discovered somewhere which you are not seeing.

I will do some more testing to see which of these is the most likely cause.

Can you send through screenshots of the "correct configuration" so i have
something to compare against :-) please.

Darren


On 28 May 2014 18:36, Richard Brown <rbrown at suse.de> wrote:

> On Wed, 2014-05-28 at 18:31 +1000, Darren Thompson wrote:
> > Richard
> >
> >
> > That partially explains things at the SLES12B7 target end but why
> > can't I connect to a "know good" SLES11 SP3 ISCSI target?
> >
> >
> > Darren
>
> For that, I have no clue - I've just tested it, but telling you that 'it
> works here' is probably of little comfort.
>
> Any clues in /var/log/messages from the target or initiators?
>
> - Richard
> >
> >
> > On 28 May 2014 18:15, Richard Brown <rbrown at suse.de> wrote:
> >         On Wed, 2014-05-28 at 13:33 +1000, Darren Thompson wrote:
> >         > Team
> >         >
> >         >
> >         >
> >         > The ISCSI "initiator" does not seem to login/connect to a
> >         working
> >         > ISCSI Target (I tested both a SLES12B7 trarget server and a
> >         "know
> >         > good/working" SLES11SP3 server).
> >         >
> >         >
> >         > The ISCSI "discovery" works but I cannot then connect/login
> >         to the
> >         > actual targer.
> >         >
> >         >
> >         > Regards
> >         > Darren
> >         > _______________________________________________
> >         > sleha-beta mailing list
> >         > sleha-beta at lists.suse.com
> >         > http://lists.suse.com/mailman/listinfo/sleha-beta
> >
> >         Hi Darren,
> >
> >         In SLE 12 we have only the iSCSI LIO Target and not the ietd
> >         iSCSI
> >         Target also available in previous versions
> >
> >         One of the new features of the LIO Target is that it supports
> >         proper LUN
> >         mapping - the ability to decide which LUNs are presented to
> >         which
> >         Clients/Initiators as which LUN numbers
> >
> >         This *requires* you to fill in the LUN mapping section of the
> >         iSCSI LIO
> >         Target in YaST on your target - it pops up after you configure
> >         a target,
> >         but if you're not aware of why it's so important, I understand
> >         you might
> >         just click next and leave the Initiator/LUN mapping table
> >         blank (I did
> >         the same first time round..)
> >
> >         Failure to do this, results in the behaviour you're noticing.
> >
> >         You'll need the 'initiator name' for each iSCSI initiator
> >         connecting to
> >         your target, that can be found in /etc/iscsi/initiatorname on
> >         each of
> >         your initiators.
> >
> >         Hope this helps,
> >
> >         - Richard
> >
> >         --
> >
> -------------------------------------------------------------------
> >           Richard Brown, QA Engineer
> >           Phone +4991174053-361,  Fax +4991174053-483
> >           SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
> >           Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix
> >         Imendoerffer,
> >           HRB 16746 (AG Nuernberg)
> >
> -------------------------------------------------------------------
> >
> >
> >
> >
> >
> >
> > --
> > Darren Thompson
> >
> > Professional Services Engineer / Consultant
> >
> >  cid:image001.jpg at 01CB7C0C.6C6A2AE0
> >
> > Level 3, 60 City Road
> >
> > Southgate, VIC 3006
> >
> > Mb: 0400 640 414
> >
> > Mail: darrent at akurit.com.au
> > Web: www.akurit.com.au
> >
> >
>
>
> --
> -------------------------------------------------------------------
>   Richard Brown, QA Engineer
>   Phone +4991174053-361,  Fax +4991174053-483
>   SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
>   Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
>   HRB 16746 (AG Nuernberg)
> -------------------------------------------------------------------
>
>
>


-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/3abfa06b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/3abfa06b/attachment.jpg>

From bjoern.lotz at suse.com  Wed May 28 03:32:06 2014
From: bjoern.lotz at suse.com (Bjoern Lotz)
Date: Wed, 28 May 2014 11:32:06 +0200
Subject: [sles-beta] ISCSI issues with SLES12B7 - part2 ( ISCSI
 'initiator' driver)
In-Reply-To: <1401264901.31434.25.camel@ibrokeit.suse.de>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
	<1401264901.31434.25.camel@ibrokeit.suse.de>
Message-ID: <5385AD16.40606@suse.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28.05.2014 10:15, Richard Brown wrote:
> Hi Darren,
> 
> In SLE 12 we have only the iSCSI LIO Target and not the ietd iSCSI 
> Target also available in previous versions
> 
> One of the new features of the LIO Target is that it supports
> proper LUN mapping - the ability to decide which LUNs are presented
> to which Clients/Initiators as which LUN numbers
> 
> This *requires* you to fill in the LUN mapping section of the iSCSI
> LIO Target in YaST on your target - it pops up after you configure
> a target, but if you're not aware of why it's so important, I
> understand you might just click next and leave the Initiator/LUN
> mapping table blank (I did the same first time round..)
> 
> Failure to do this, results in the behaviour you're noticing.
> 
> You'll need the 'initiator name' for each iSCSI initiator
> connecting to your target, that can be found in
> /etc/iscsi/initiatorname on each of your initiators.
> 
> Hope this helps,

I had similar problems as Darren, but I finally managed to connect the
Initiator on Beta7 to a target on Beta7, without authentication.

However, when I turn on authentication I get the following log entries
on the target server:

2014-05-28T11:17:52.376035+02:00 linux-co7n kernel: [  650.374639]
Initiator is requesting CSG: 1, has not been successfully
authenticated, and the Target is enforcing iSCSI Authentication, login
failed.


2014-05-28T11:17:52.376056+02:00 linux-co7n kernel: [  650.374652]
iSCSI Login negotiation failed.

As I wasn't sure if this is because I mismatched outgoing and incoming
on target and initiator, I simply used the same username and password
on all - but the result is above.

Any suggestions are welcome, or is this considered a bug I should report?

Kind regards,

Bj?rn

- -- 
Dr. Bj?rn Lotz, Instructional Designer, CISSP
SUSE Linux GmbH, Maxfeldstrasse 5, 90409 N?rnberg
Tel: +49 89 8639 9664  Mobil: +49 173 5876724
bjoern.lotz at suse.com       PGP-ID: 0xD437D363
- ------------------
SUSE Linux GmbH, N?rnberg; HRB 21284 (AG N?rnberg)
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlOFrQ4ACgkQKZToxtQ302NfrQCeIgb1wKcVCup6+4IpZAnv58yP
D5cAn2Kgy21I8VlyEKJ0xcxxaBtvWT/3
=/Cv3
-----END PGP SIGNATURE-----

From gjn at gjn.priv.at  Wed May 28 05:06:39 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Wed, 28 May 2014 13:06:39 +0200
Subject: [sles-beta] Bugzilla Broken ?
Message-ID: <10539408.16TdeL1e3J@gjn.priv.at>

Hello,

I can't never login in Bugzilla, now 7 hours ?

 
-- 
mit freundlichen Gr??en / best Regards,

  G?nther J. Niederwimmer

From meissner at suse.de  Wed May 28 05:14:04 2014
From: meissner at suse.de (Marcus Meissner)
Date: Wed, 28 May 2014 13:14:04 +0200
Subject: [sles-beta] Bugzilla Broken ?
In-Reply-To: <10539408.16TdeL1e3J@gjn.priv.at>
References: <10539408.16TdeL1e3J@gjn.priv.at>
Message-ID: <20140528111404.GB16459@suse.de>

On Wed, May 28, 2014 at 01:06:39PM +0200, G?nther J. Niederwimmer wrote:
> Hello,
> 
> I can't never login in Bugzilla, now 7 hours ?

It works fine. The login button itself did not work, but just press return in the password or login field.

Ciao, Marcus

From lchiquitto at suse.com  Wed May 28 05:14:27 2014
From: lchiquitto at suse.com (Leonardo Chiquitto)
Date: Wed, 28 May 2014 08:14:27 -0300
Subject: [sles-beta] Bugzilla Broken ?
In-Reply-To: <10539408.16TdeL1e3J@gjn.priv.at>
References: <10539408.16TdeL1e3J@gjn.priv.at>
Message-ID: <20140528081427.45c7a3f1@down.l.ngdn.org>

On Wed, 28 May 2014 13:06:39 +0200, G?nther J. Niederwimmer
<gjn at gjn.priv.at> wrote:
> Hello,
> 
> I can't never login in Bugzilla, now 7 hours ?

Works for me. What error do you get? Have you tried to remove cookies
from domains *novell.com, *attachmategroup.com?

Leonardo

From urs.frey at post.ch  Wed May 28 05:21:44 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Wed, 28 May 2014 11:21:44 +0000
Subject: [sles-beta] Bugzilla Broken ?
In-Reply-To: <20140528111404.GB16459@suse.de>
References: <10539408.16TdeL1e3J@gjn.priv.at> <20140528111404.GB16459@suse.de>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F99E0BC@HXMB12.pnet.ch>

Hi
My experience today
- IE-9.0.27 works even on the login button
- Firefox 29, there the login button did not work until I deleted the entire Firefox cache & history some minutes ago.

Best regards

Urs Frey????????????????????????????????????????????? 
Post CH AG
Informationstechnologie
IT Betrieb 
Webergutstrasse 12 
3030 Bern (Zollikofen) 
Telefon : ++41 (0)58 338 58 70 
FAX???? : ++41 (0)58 667 30 07 
E-Mail:?? urs.frey at post.ch


-----Urspr?ngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Marcus Meissner
Gesendet: Wednesday, May 28, 2014 1:14 PM
An: G?nther J. Niederwimmer
Cc: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] Bugzilla Broken ?

On Wed, May 28, 2014 at 01:06:39PM +0200, G?nther J. Niederwimmer wrote:
> Hello,
> 
> I can't never login in Bugzilla, now 7 hours ?

It works fine. The login button itself did not work, but just press return in the password or login field.

Ciao, Marcus
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

From Christoph.Schumacher at porsche.de  Wed May 28 05:39:11 2014
From: Christoph.Schumacher at porsche.de (Christoph Schumacher)
Date: Wed, 28 May 2014 13:39:11 +0200
Subject: [sles-beta] btrfs & tooling
Message-ID: <OF3BA81409.8D8F2A9D-ONC1257CE6.003EA759-C1257CE6.00400350@porsche.de>

Hey there,

I've got some things that are ugly:

- on subvolume with limits/quota df always shows the size of the parent 
volume also for all subvolumes
IMHO it should either show the limited size or not show the subvolume at 
all because it's only disturbing

- i can't figure out how to show the quota of a btrfs volume easily and 
clearly ..... what the common known btrfs-tools show is cr....not good.

- also after "mirroring" a btrfs with a raid1 df shows the sum of both 
volumes in the btrfs despite the real size


Will the tooling for btrfs be adopted in the next time, so btrfs can be 
used conveniently?

Dipl.-Inf. Christoph Schumacher
FAI5 Competence Center Dezentrale Server
Dr. Ing. h.c. F. Porsche AG
Porscheplatz 1, D-70435 Stuttgart Zuffenhausen
Telefon:  +49 (0)711/911-23729
Fax:      +49 (0)711/911-23171
E-Mail:   christoph.schumacher at porsche.de

Dr. Ing. h.c. F.  Porsche Aktiengesellschaft
Sitz der Gesellschaft: Stuttgart
Registergericht: Amtsgericht Stuttgart HRB-Nr. 730623
Vorsitzender des Aufsichtsrats: Dr. Wolfgang Porsche
Vorstand: Matthias M?ller, Vorsitzender
Thomas Edig, stv. Vorsitzender
Dr. Oliver Blume, Wolfgang Hatz, Bernhard Maier, Lutz Meschke, Uwe-Karsten St?dter

Die vorgenannten Angaben werden jeder E-Mail automatisch hinzugef?gt. Dies ist kein Anerkenntnis, 
dass es sich beim Inhalt dieser E-Mail um eine rechtsverbindliche Erkl?rung der Porsche AG handelt. 
Erkl?rungen, die die Porsche AG verpflichten, bed?rfen jeweils der Unterschrift durch zwei zeichnungs-
berechtigte Personen der AG.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/48eefe3f/attachment.htm>

From darrent at akurit.com.au  Wed May 28 05:44:23 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 21:44:23 +1000
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
	<1401264901.31434.25.camel@ibrokeit.suse.de>
	<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>
	<1401266203.31434.30.camel@ibrokeit.suse.de>
	<CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>
Message-ID: <CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>

Richard

With your help I can now connect a SLES12B7 ISCSI Initiator to a SLES12B7
ISCSI target (Thank you) so It's looking like option 1 of my possible
causes list so far ;-)

I'm still not able to work out how to bing a single SCSI target to multiple
IP addresses (on a mutihomed host). Any hints here on how to do that part
(it was easy in SLES11 as it just bound on all configured IP addresses by
default).

Darren


On 28 May 2014 19:18, Darren Thompson <darrent at akurit.com.au> wrote:

> Richard
>
> That leaves a couple of posibilites:
> 1. I have just got all my configurations wrong at both ends (sadly, highly
> possible)
> 2. The SLES12 initiator is no longer compatible with the SLES11 target
> (bad)
> 3. There is a bug that i have discovered somewhere which you are not
> seeing.
>
> I will do some more testing to see which of these is the most likely cause.
>
> Can you send through screenshots of the "correct configuration" so i have
> something to compare against :-) please.
>
> Darren
>
>
> On 28 May 2014 18:36, Richard Brown <rbrown at suse.de> wrote:
>
>> On Wed, 2014-05-28 at 18:31 +1000, Darren Thompson wrote:
>> > Richard
>> >
>> >
>> > That partially explains things at the SLES12B7 target end but why
>> > can't I connect to a "know good" SLES11 SP3 ISCSI target?
>> >
>> >
>> > Darren
>>
>> For that, I have no clue - I've just tested it, but telling you that 'it
>> works here' is probably of little comfort.
>>
>> Any clues in /var/log/messages from the target or initiators?
>>
>> - Richard
>> >
>> >
>> > On 28 May 2014 18:15, Richard Brown <rbrown at suse.de> wrote:
>> >         On Wed, 2014-05-28 at 13:33 +1000, Darren Thompson wrote:
>> >         > Team
>> >         >
>> >         >
>> >         >
>> >         > The ISCSI "initiator" does not seem to login/connect to a
>> >         working
>> >         > ISCSI Target (I tested both a SLES12B7 trarget server and a
>> >         "know
>> >         > good/working" SLES11SP3 server).
>> >         >
>> >         >
>> >         > The ISCSI "discovery" works but I cannot then connect/login
>> >         to the
>> >         > actual targer.
>> >         >
>> >         >
>> >         > Regards
>> >         > Darren
>> >         > _______________________________________________
>> >         > sleha-beta mailing list
>> >         > sleha-beta at lists.suse.com
>> >         > http://lists.suse.com/mailman/listinfo/sleha-beta
>> >
>> >         Hi Darren,
>> >
>> >         In SLE 12 we have only the iSCSI LIO Target and not the ietd
>> >         iSCSI
>> >         Target also available in previous versions
>> >
>> >         One of the new features of the LIO Target is that it supports
>> >         proper LUN
>> >         mapping - the ability to decide which LUNs are presented to
>> >         which
>> >         Clients/Initiators as which LUN numbers
>> >
>> >         This *requires* you to fill in the LUN mapping section of the
>> >         iSCSI LIO
>> >         Target in YaST on your target - it pops up after you configure
>> >         a target,
>> >         but if you're not aware of why it's so important, I understand
>> >         you might
>> >         just click next and leave the Initiator/LUN mapping table
>> >         blank (I did
>> >         the same first time round..)
>> >
>> >         Failure to do this, results in the behaviour you're noticing.
>> >
>> >         You'll need the 'initiator name' for each iSCSI initiator
>> >         connecting to
>> >         your target, that can be found in /etc/iscsi/initiatorname on
>> >         each of
>> >         your initiators.
>> >
>> >         Hope this helps,
>> >
>> >         - Richard
>> >
>> >         --
>> >
>> -------------------------------------------------------------------
>> >           Richard Brown, QA Engineer
>> >           Phone +4991174053-361,  Fax +4991174053-483
>> >           SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
>> >           Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix
>> >         Imendoerffer,
>> >           HRB 16746 (AG Nuernberg)
>> >
>> -------------------------------------------------------------------
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Darren Thompson
>> >
>> > Professional Services Engineer / Consultant
>> >
>> >  cid:image001.jpg at 01CB7C0C.6C6A2AE0
>> >
>> > Level 3, 60 City Road
>> >
>> > Southgate, VIC 3006
>> >
>> > Mb: 0400 640 414
>> >
>> > Mail: darrent at akurit.com.au
>> > Web: www.akurit.com.au
>> >
>> >
>>
>>
>> --
>> -------------------------------------------------------------------
>>   Richard Brown, QA Engineer
>>   Phone +4991174053-361,  Fax +4991174053-483
>>   SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
>>   Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
>>   HRB 16746 (AG Nuernberg)
>> -------------------------------------------------------------------
>>
>>
>>
>
>
> --
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au <steve at akurit.com.au>
> Web: www.akurit.com.au
>



-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/4274a589/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/4274a589/attachment.jpg>

From rbrown at suse.de  Wed May 28 05:53:31 2014
From: rbrown at suse.de (Richard Brown)
Date: Wed, 28 May 2014 13:53:31 +0200
Subject: [sles-beta] btrfs & tooling
In-Reply-To: <OF3BA81409.8D8F2A9D-ONC1257CE6.003EA759-C1257CE6.00400350@porsche.de>
References: <OF3BA81409.8D8F2A9D-ONC1257CE6.003EA759-C1257CE6.00400350@porsche.de>
Message-ID: <1401278011.31434.37.camel@ibrokeit.suse.de>

Hello Christoph,

I'm afraid I can't answer all your questions, but I'll take a stab at a
few that I believe I know the answer to

On Wed, 2014-05-28 at 13:39 +0200, Christoph Schumacher wrote:
> - on subvolume with limits/quota df always shows the size of the
> parent volume also for all subvolumes 
> IMHO it should either show the limited size or not show the subvolume
> at all because it's only disturbing 

> - also after "mirroring" a btrfs with a raid1 df shows the sum of both
> volumes in the btrfs despite the real size 

Because of the nature of how btrfs works, df isn't the best tool to use

btrfs has it's own tools for the purpose, such as 'btrfs fi show' which
shows you the raw disk usage, and 'btrfs fi df <filepath>' which will
show you the equivalent of df, taking into account things like btrfs
RAID, for the subvolume selected by <filepath>

> - i can't figure out how to show the quota of a btrfs volume easily
> and clearly ..... what the common known btrfs-tools show is cr....not
> good. 

'btrfs qgroup show <filepath>' where <filepath> is a location for your
btrfs volume/subvolume, should give you the information you require.

Hope this helps,

- Rich

-- 
-------------------------------------------------------------------
  Richard Brown, QA Engineer
  Phone +4991174053-361,  Fax +4991174053-483
  SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
  Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
  HRB 16746 (AG Nuernberg)
-------------------------------------------------------------------



From gjn at gjn.priv.at  Wed May 28 05:58:27 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Wed, 28 May 2014 13:58:27 +0200
Subject: [sles-beta] Bugzilla Broken ?
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F99E0BC@HXMB12.pnet.ch>
References: <10539408.16TdeL1e3J@gjn.priv.at> <20140528111404.GB16459@suse.de>
	<40637DBB36AF3941B243A286A432CA0B0F99E0BC@HXMB12.pnet.ch>
Message-ID: <27479550.kcRA8nzZOI@gjn.priv.at>

Hello All,

Am Mittwoch, 28. Mai 2014, 11:21:44 schrieb urs.frey at post.ch:
> Hi
> My experience today
> - IE-9.0.27 works even on the login button
> - Firefox 29, there the login button did not work until I deleted the entire
> Firefox cache & history some minutes ago.

This was the correct hint, Thanks.

> -----Urspr?ngliche Nachricht-----
> Von: sles-beta-bounces at lists.suse.com
> [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Marcus Meissner
> Gesendet: Wednesday, May 28, 2014 1:14 PM
> An: G?nther J. Niederwimmer
> Cc: sles-beta at lists.suse.com
> Betreff: Re: [sles-beta] Bugzilla Broken ?
> 
> On Wed, May 28, 2014 at 01:06:39PM +0200, G?nther J. Niederwimmer wrote:
> > Hello,
> > 
> > I can't never login in Bugzilla, now 7 hours ?
> 
> It works fine. The login button itself did not work, but just press return
> in the password or login field.
> 
> Ciao, Marcus
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta

-- 
mit freundlichen Gr??en / best Regards,

  G?nther J. Niederwimmer

From Christoph.Schumacher at porsche.de  Wed May 28 06:00:41 2014
From: Christoph.Schumacher at porsche.de (Christoph Schumacher)
Date: Wed, 28 May 2014 14:00:41 +0200
Subject: [sles-beta] btrfs & tooling
In-Reply-To: <1401278011.31434.37.camel@ibrokeit.suse.de>
References: <OF3BA81409.8D8F2A9D-ONC1257CE6.003EA759-C1257CE6.00400350@porsche.de>
	<1401278011.31434.37.camel@ibrokeit.suse.de>
Message-ID: <OF2CAA5FCA.8C066AAB-ONC1257CE6.004190B6-C1257CE6.0041FB5F@porsche.de>

Hi Richard,

Honestly it'll be a mess to dismiss "df" for a lot of people, especially 
the guys coming from any UNIX.

As i mentioned: on my beta7 install the commands you issued do not work 
well or hard to read:

For example btrfs fi df shows a lot of information and it's hard to filter 
at a glance.

btrfs qgroup show does not work for me at all....what's the quota? have a 
guess!

# btrfs qgroup show /tmp
qgroupid rfer       excl 
-------- ----       ---- 
0/5      16384      16384 
0/257    2359185408 2359185408 
0/258    16384      16384 
0/259    102576128  102576128 
0/260    16384      16384 
0/261    16384      16384 
0/262    16384      16384 
0/263    97067008   97067008 



Dipl.-Inf. Christoph Schumacher
FAI5 Competence Center Dezentrale Server
Dr. Ing. h.c. F. Porsche AG
Porscheplatz 1, D-70435 Stuttgart Zuffenhausen
Telefon:  +49 (0)711/911-23729
Fax:      +49 (0)711/911-23171
E-Mail:   christoph.schumacher at porsche.de



From:   Richard Brown <rbrown at suse.de>
To:     sles-beta at lists.suse.com
Date:   28/05/2014 13:53
Subject:        Re: [sles-beta] btrfs & tooling
Sent by:        sles-beta-bounces at lists.suse.com



Hello Christoph,

I'm afraid I can't answer all your questions, but I'll take a stab at a
few that I believe I know the answer to

On Wed, 2014-05-28 at 13:39 +0200, Christoph Schumacher wrote:
> - on subvolume with limits/quota df always shows the size of the
> parent volume also for all subvolumes 
> IMHO it should either show the limited size or not show the subvolume
> at all because it's only disturbing 

> - also after "mirroring" a btrfs with a raid1 df shows the sum of both
> volumes in the btrfs despite the real size 

Because of the nature of how btrfs works, df isn't the best tool to use

btrfs has it's own tools for the purpose, such as 'btrfs fi show' which
shows you the raw disk usage, and 'btrfs fi df <filepath>' which will
show you the equivalent of df, taking into account things like btrfs
RAID, for the subvolume selected by <filepath>

> - i can't figure out how to show the quota of a btrfs volume easily
> and clearly ..... what the common known btrfs-tools show is cr....not
> good. 

'btrfs qgroup show <filepath>' where <filepath> is a location for your
btrfs volume/subvolume, should give you the information you require.

Hope this helps,

- Rich

-- 
-------------------------------------------------------------------
  Richard Brown, QA Engineer
  Phone +4991174053-361,  Fax +4991174053-483
  SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
  Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
  HRB 16746 (AG Nuernberg)
-------------------------------------------------------------------


_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta



Dr. Ing. h.c. F.  Porsche Aktiengesellschaft
Sitz der Gesellschaft: Stuttgart
Registergericht: Amtsgericht Stuttgart HRB-Nr. 730623
Vorsitzender des Aufsichtsrats: Dr. Wolfgang Porsche
Vorstand: Matthias M?ller, Vorsitzender
Thomas Edig, stv. Vorsitzender
Dr. Oliver Blume, Wolfgang Hatz, Bernhard Maier, Lutz Meschke, Uwe-Karsten St?dter

Die vorgenannten Angaben werden jeder E-Mail automatisch hinzugef?gt. Dies ist kein Anerkenntnis, 
dass es sich beim Inhalt dieser E-Mail um eine rechtsverbindliche Erkl?rung der Porsche AG handelt. 
Erkl?rungen, die die Porsche AG verpflichten, bed?rfen jeweils der Unterschrift durch zwei zeichnungs-
berechtigte Personen der AG.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/63bf8ffc/attachment.htm>

From rbrown at suse.de  Wed May 28 06:15:36 2014
From: rbrown at suse.de (Richard Brown)
Date: Wed, 28 May 2014 14:15:36 +0200
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
	<1401264901.31434.25.camel@ibrokeit.suse.de>
	<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>
	<1401266203.31434.30.camel@ibrokeit.suse.de>
	<CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>
	<CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>
Message-ID: <1401279336.31434.44.camel@ibrokeit.suse.de>

On Wed, 2014-05-28 at 21:44 +1000, Darren Thompson wrote:

> I'm still not able to work out how to bing a single SCSI target to
> multiple IP addresses (on a mutihomed host). Any hints here on how to
> do that part (it was easy in SLES11 as it just bound on all configured
> IP addresses by default).

Darren,

I'm not in a position to test this right now, however I'm 99% sure that
you can use the following command on your Target server to add
additional IP addresses to your target

"lio_node --addnp=<target name> <ip address>:<port>"

<target name> is that long string that is shown in YaST in the Targets
list
(LIO supports multiple targets, so you might have multiple IP's
allocated to only 1 or a few of your target..nifty feature..)

eg "lio_node
--addnp=iqn.2014-05.suse.qa:ca790687-c098-4dcb-9f12-b0aea1c1a899
10.122.2.65:3260" will add IP address 10.122.2.65 on Port 3260 to the
Target named iqn.2014-05.suse.qa:ca790687-c098-4dcb-9f12-b0aea1c1a899

You should then be able to confirm it's working by 

"lio_node --listendpoints"

Which should show you the target name, it's status, it's IP addresses
(aka Network Portals), and it's LUNS

I would be really surprised if YaST didn't co-exist with such manual
settings, but if you could test that and report back, that would be a
great help :)

Kind Regards,

- Richard


> On 28 May 2014 19:18, Darren Thompson <darrent at akurit.com.au> wrote:
>         Richard
>         
>         
>         That leaves a couple of posibilites:
>         1. I have just got all my configurations wrong at both ends
>         (sadly, highly possible)
>         2. The SLES12 initiator is no longer compatible with the
>         SLES11 target (bad)
>         3. There is a bug that i have discovered somewhere which you
>         are not seeing.
>         
>         
>         I will do some more testing to see which of these is the most
>         likely cause.
>         
>         
>         Can you send through screenshots of the "correct
>         configuration" so i have something to compare against :-)
>         please.
>         
>         
>         Darren
>         
>         
>         On 28 May 2014 18:36, Richard Brown <rbrown at suse.de> wrote:
>                 On Wed, 2014-05-28 at 18:31 +1000, Darren Thompson
>                 wrote:
>                 > Richard
>                 >
>                 >
>                 > That partially explains things at the SLES12B7
>                 target end but why
>                 > can't I connect to a "know good" SLES11 SP3 ISCSI
>                 target?
>                 >
>                 >
>                 > Darren
>                 
>                 For that, I have no clue - I've just tested it, but
>                 telling you that 'it
>                 works here' is probably of little comfort.
>                 
>                 Any clues in /var/log/messages from the target or
>                 initiators?
>                 
>                 - Richard
>                 >
>                 >
>                 > On 28 May 2014 18:15, Richard Brown <rbrown at suse.de>
>                 wrote:
>                 >         On Wed, 2014-05-28 at 13:33 +1000, Darren
>                 Thompson wrote:
>                 >         > Team
>                 >         >
>                 >         >
>                 >         >
>                 >         > The ISCSI "initiator" does not seem to
>                 login/connect to a
>                 >         working
>                 >         > ISCSI Target (I tested both a SLES12B7
>                 trarget server and a
>                 >         "know
>                 >         > good/working" SLES11SP3 server).
>                 >         >
>                 >         >
>                 >         > The ISCSI "discovery" works but I cannot
>                 then connect/login
>                 >         to the
>                 >         > actual targer.
>                 >         >
>                 >         >
>                 >         > Regards
>                 >         > Darren
>                 >         >
>                 _______________________________________________
>                 >         > sleha-beta mailing list
>                 >         > sleha-beta at lists.suse.com
>                 >         >
>                 http://lists.suse.com/mailman/listinfo/sleha-beta
>                 >
>                 >         Hi Darren,
>                 >
>                 >         In SLE 12 we have only the iSCSI LIO Target
>                 and not the ietd
>                 >         iSCSI
>                 >         Target also available in previous versions
>                 >
>                 >         One of the new features of the LIO Target is
>                 that it supports
>                 >         proper LUN
>                 >         mapping - the ability to decide which LUNs
>                 are presented to
>                 >         which
>                 >         Clients/Initiators as which LUN numbers
>                 >
>                 >         This *requires* you to fill in the LUN
>                 mapping section of the
>                 >         iSCSI LIO
>                 >         Target in YaST on your target - it pops up
>                 after you configure
>                 >         a target,
>                 >         but if you're not aware of why it's so
>                 important, I understand
>                 >         you might
>                 >         just click next and leave the Initiator/LUN
>                 mapping table
>                 >         blank (I did
>                 >         the same first time round..)
>                 >
>                 >         Failure to do this, results in the behaviour
>                 you're noticing.
>                 >
>                 >         You'll need the 'initiator name' for each
>                 iSCSI initiator
>                 >         connecting to
>                 >         your target, that can be found
>                 in /etc/iscsi/initiatorname on
>                 >         each of
>                 >         your initiators.
>                 >
>                 >         Hope this helps,
>                 >
>                 >         - Richard
>                 >
>                 >         --
>                 >
>                 -------------------------------------------------------------------
>                 >           Richard Brown, QA Engineer
>                 >           Phone +4991174053-361,  Fax
>                 +4991174053-483
>                 >           SUSE LINUX Products GmbH,  Maxfeldstr. 5,
>                  D-90409 Nuernberg
>                 >           Geschaeftsfuehrer: Jeff Hawn, Jennifer
>                 Guild, Felix
>                 >         Imendoerffer,
>                 >           HRB 16746 (AG Nuernberg)
>                 >
>                 -------------------------------------------------------------------
>                 >
>                 >
>                 >
>                 >
>                 >
>                 >
>                 > --
>                 > Darren Thompson
>                 >
>                 > Professional Services Engineer / Consultant
>                 >
>                 >  cid:image001.jpg at 01CB7C0C.6C6A2AE0
>                 >
>                 > Level 3, 60 City Road
>                 >
>                 > Southgate, VIC 3006
>                 >
>                 > Mb: 0400 640 414
>                 >
>                 > Mail: darrent at akurit.com.au
>                 > Web: www.akurit.com.au
>                 >
>                 >
>                 
>                 
>                 --
>                 -------------------------------------------------------------------
>                   Richard Brown, QA Engineer
>                   Phone +4991174053-361,  Fax +4991174053-483
>                   SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409
>                 Nuernberg
>                   Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix
>                 Imendoerffer,
>                   HRB 16746 (AG Nuernberg)
>                 -------------------------------------------------------------------
>                 
>                 
>         
>         
>         
>         
>         -- 
>         Darren Thompson
>         
>         Professional Services Engineer / Consultant
>         
>          cid:image001.jpg at 01CB7C0C.6C6A2AE0
>         
>         Level 3, 60 City Road
>         
>         Southgate, VIC 3006
>         
>         Mb: 0400 640 414
>         
>         Mail: darrent at akurit.com.au
>         Web: www.akurit.com.au
>         
>         
> 
> 
> 
> 
> -- 
> Darren Thompson
> 
> Professional Services Engineer / Consultant
> 
>  cid:image001.jpg at 01CB7C0C.6C6A2AE0
> 
> Level 3, 60 City Road
> 
> Southgate, VIC 3006
> 
> Mb: 0400 640 414
> 
> Mail: darrent at akurit.com.au
> Web: www.akurit.com.au
> 
> 


-- 
-------------------------------------------------------------------
  Richard Brown, QA Engineer
  Phone +4991174053-361,  Fax +4991174053-483
  SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
  Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
  HRB 16746 (AG Nuernberg)
-------------------------------------------------------------------



From bjoern.lotz at suse.com  Wed May 28 07:09:18 2014
From: bjoern.lotz at suse.com (Bjoern Lotz)
Date: Wed, 28 May 2014 15:09:18 +0200
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <1401279336.31434.44.camel@ibrokeit.suse.de>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>	<1401264901.31434.25.camel@ibrokeit.suse.de>	<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>	<1401266203.31434.30.camel@ibrokeit.suse.de>	<CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>	<CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>
	<1401279336.31434.44.camel@ibrokeit.suse.de>
Message-ID: <5385DFFE.2010807@suse.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Richard,

On 28.05.2014 14:15, Richard Brown wrote:
> On Wed, 2014-05-28 at 21:44 +1000, Darren Thompson wrote:
> 
>> I'm still not able to work out how to bing a single SCSI target 
>> to multiple IP addresses (on a mutihomed host). Any hints here
>> on how to do that part (it was easy in SLES11 as it just bound
>> on all configured IP addresses by default).
> 
> Darren,
> 
> I'm not in a position to test this right now, however I'm 99% sure 
> that you can use the following command on your Target server to add
> additional IP addresses to your target
> 
> "lio_node --addnp=<target name> <ip address>:<port>"

Error message is: addnp requires 3 arguments, help says:
- --addnp=TARGET_IQN TPGT IP:PORT

I assumed TPGT refers to the portal group, which the yast interface
listed as 1 - adding a 1 to the commandline between iqn and IP worked.

> <target name> is that long string that is shown in YaST in the 
> Targets list (LIO supports multiple targets, so you might have 
> multiple IP's allocated to only 1 or a few of your target..nifty 
> feature..)
> 
> eg "lio_node 
> --addnp=iqn.2014-05.suse.qa:ca790687-c098-4dcb-9f12-b0aea1c1a899 
> 10.122.2.65:3260" will add IP address 10.122.2.65 on Port 3260 to 
> the Target named 
> iqn.2014-05.suse.qa:ca790687-c098-4dcb-9f12-b0aea1c1a899
> 
> You should then be able to confirm it's working by
> 
> "lio_node --listendpoints"

Worked for me - and with yast on the initiator side the target is
discovered and the message that one should use multipathing appears as
it did with SLES11.

> Which should show you the target name, it's status, it's IP 
> addresses (aka Network Portals), and it's LUNS
> 
> I would be really surprised if YaST didn't co-exist with such 
> manual settings, but if you could test that and report back, that 
> would be a great help :)

YaST didn't complain when I started the LIO target module afterwards.

I think you saved me hours of pointless searching for a solution.

Is there some documentation on this somewhere? lio_node --help brings
up a log of options, but there is no manual page for it.

Still unresolved for me is the authentication piece. Connecting to the
target without authentication works, but I didn't manage to connect
when authentication is turned on.

Kind regards,

Bj?rn



- -- 
Dr. Bj?rn Lotz, Instructional Designer, CISSP
SUSE Linux GmbH, Maxfeldstrasse 5, 90409 N?rnberg
Tel: +49 89 8639 9664  Mobil: +49 173 5876724
bjoern.lotz at suse.com       PGP-ID: 0xD437D363
- ------------------
SUSE Linux GmbH, N?rnberg; HRB 21284 (AG N?rnberg)
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlOF3/QACgkQKZToxtQ302MpzgCfSTb1XrC/vdOrxlR1Uml0Ttmr
c8sAoMNSXu35TsNFjnzdzEq2nYT4E2Sm
=7bpS
-----END PGP SIGNATURE-----

From darrent at akurit.com.au  Wed May 28 07:19:48 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 28 May 2014 23:19:48 +1000
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <1401279336.31434.44.camel@ibrokeit.suse.de>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
	<1401264901.31434.25.camel@ibrokeit.suse.de>
	<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>
	<1401266203.31434.30.camel@ibrokeit.suse.de>
	<CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>
	<CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>
	<1401279336.31434.44.camel@ibrokeit.suse.de>
Message-ID: <CAEUhfEcPkX5wAa9Caq-zRBc50EvpOCO6aDkej-NnOnG8n488nw@mail.gmail.com>

Richard

yes that did it, the syntax you gace was "nearly correct" which is amzingly
good if from memory.

correct syntax:
lio_node --addnp=TARGET_IQN TPGT IP:PORT <= in my case the TPGT value=1 so
my actual used syntax was:
lio_node --addnp
vmdisk01.iqn.2014-05.sles12source.testlab.akurit.com.au:610ebff1-2e78-4274-b4ce-e85077f6ff4b
1 192.168.100.200:3260
lio_node --addnp
vmdisk01.iqn.2014-05.sles12source.testlab.akurit.com.au:610ebff1-2e78-4274-b4ce-e85077f6ff4b
1 192.168.200.200:3260

which produced (edited to conserve space):
io_node --listendpoints
\------> vmdisk01.iqn.2014-05.sles12source.testlab.akurit.com.au:610
ebff1-2e78-4274-b4ce-e85077f6ff4b
        \-------> tpgt_1  TargetAlias: LIO Target
         TPG Status: ENABLED
         TPG Network Portals:
                 \-------> 192.168.200.200:3260
                 \-------> 192.168.100.200:3260
                 \-------> 192.168.0.200:3260
         TPG Logical Units:
                 \-------> lun_0/dev_DATA_VMDISK01 ->
target/core/iblock_0/dev_DATA_VMDISK01

Thanks again...

BTW this is not "intuitive" or "easily discovered" so will need to be
clearly documented somewhere before release to the "great unwashed masses"
:-)

Regards
Darren


On 28 May 2014 22:15, Richard Brown <rbrown at suse.de> wrote:

> On Wed, 2014-05-28 at 21:44 +1000, Darren Thompson wrote:
>
> > I'm still not able to work out how to bing a single SCSI target to
> > multiple IP addresses (on a mutihomed host). Any hints here on how to
> > do that part (it was easy in SLES11 as it just bound on all configured
> > IP addresses by default).
>
> Darren,
>
> I'm not in a position to test this right now, however I'm 99% sure that
> you can use the following command on your Target server to add
> additional IP addresses to your target
>
> "lio_node --addnp=<target name> <ip address>:<port>"
>
> <target name> is that long string that is shown in YaST in the Targets
> list
> (LIO supports multiple targets, so you might have multiple IP's
> allocated to only 1 or a few of your target..nifty feature..)
>
> eg "lio_node
> --addnp=iqn.2014-05.suse.qa:ca790687-c098-4dcb-9f12-b0aea1c1a899
> 10.122.2.65:3260" will add IP address 10.122.2.65 on Port 3260 to the
> Target named iqn.2014-05.suse.qa:ca790687-c098-4dcb-9f12-b0aea1c1a899
>
> You should then be able to confirm it's working by
>
> "lio_node --listendpoints"
>
> Which should show you the target name, it's status, it's IP addresses
> (aka Network Portals), and it's LUNS
>
> I would be really surprised if YaST didn't co-exist with such manual
> settings, but if you could test that and report back, that would be a
> great help :)
>
> Kind Regards,
>
> - Richard
>
>
> > On 28 May 2014 19:18, Darren Thompson <darrent at akurit.com.au> wrote:
> >         Richard
> >
> >
> >         That leaves a couple of posibilites:
> >         1. I have just got all my configurations wrong at both ends
> >         (sadly, highly possible)
> >         2. The SLES12 initiator is no longer compatible with the
> >         SLES11 target (bad)
> >         3. There is a bug that i have discovered somewhere which you
> >         are not seeing.
> >
> >
> >         I will do some more testing to see which of these is the most
> >         likely cause.
> >
> >
> >         Can you send through screenshots of the "correct
> >         configuration" so i have something to compare against :-)
> >         please.
> >
> >
> >         Darren
> >
> >
> >         On 28 May 2014 18:36, Richard Brown <rbrown at suse.de> wrote:
> >                 On Wed, 2014-05-28 at 18:31 +1000, Darren Thompson
> >                 wrote:
> >                 > Richard
> >                 >
> >                 >
> >                 > That partially explains things at the SLES12B7
> >                 target end but why
> >                 > can't I connect to a "know good" SLES11 SP3 ISCSI
> >                 target?
> >                 >
> >                 >
> >                 > Darren
> >
> >                 For that, I have no clue - I've just tested it, but
> >                 telling you that 'it
> >                 works here' is probably of little comfort.
> >
> >                 Any clues in /var/log/messages from the target or
> >                 initiators?
> >
> >                 - Richard
> >                 >
> >                 >
> >                 > On 28 May 2014 18:15, Richard Brown <rbrown at suse.de>
> >                 wrote:
> >                 >         On Wed, 2014-05-28 at 13:33 +1000, Darren
> >                 Thompson wrote:
> >                 >         > Team
> >                 >         >
> >                 >         >
> >                 >         >
> >                 >         > The ISCSI "initiator" does not seem to
> >                 login/connect to a
> >                 >         working
> >                 >         > ISCSI Target (I tested both a SLES12B7
> >                 trarget server and a
> >                 >         "know
> >                 >         > good/working" SLES11SP3 server).
> >                 >         >
> >                 >         >
> >                 >         > The ISCSI "discovery" works but I cannot
> >                 then connect/login
> >                 >         to the
> >                 >         > actual targer.
> >                 >         >
> >                 >         >
> >                 >         > Regards
> >                 >         > Darren
> >                 >         >
> >                 _______________________________________________
> >                 >         > sleha-beta mailing list
> >                 >         > sleha-beta at lists.suse.com
> >                 >         >
> >                 http://lists.suse.com/mailman/listinfo/sleha-beta
> >                 >
> >                 >         Hi Darren,
> >                 >
> >                 >         In SLE 12 we have only the iSCSI LIO Target
> >                 and not the ietd
> >                 >         iSCSI
> >                 >         Target also available in previous versions
> >                 >
> >                 >         One of the new features of the LIO Target is
> >                 that it supports
> >                 >         proper LUN
> >                 >         mapping - the ability to decide which LUNs
> >                 are presented to
> >                 >         which
> >                 >         Clients/Initiators as which LUN numbers
> >                 >
> >                 >         This *requires* you to fill in the LUN
> >                 mapping section of the
> >                 >         iSCSI LIO
> >                 >         Target in YaST on your target - it pops up
> >                 after you configure
> >                 >         a target,
> >                 >         but if you're not aware of why it's so
> >                 important, I understand
> >                 >         you might
> >                 >         just click next and leave the Initiator/LUN
> >                 mapping table
> >                 >         blank (I did
> >                 >         the same first time round..)
> >                 >
> >                 >         Failure to do this, results in the behaviour
> >                 you're noticing.
> >                 >
> >                 >         You'll need the 'initiator name' for each
> >                 iSCSI initiator
> >                 >         connecting to
> >                 >         your target, that can be found
> >                 in /etc/iscsi/initiatorname on
> >                 >         each of
> >                 >         your initiators.
> >                 >
> >                 >         Hope this helps,
> >                 >
> >                 >         - Richard
> >                 >
> >                 >         --
> >                 >
> >
> -------------------------------------------------------------------
> >                 >           Richard Brown, QA Engineer
> >                 >           Phone +4991174053-361,  Fax
> >                 +4991174053-483
> >                 >           SUSE LINUX Products GmbH,  Maxfeldstr. 5,
> >                  D-90409 Nuernberg
> >                 >           Geschaeftsfuehrer: Jeff Hawn, Jennifer
> >                 Guild, Felix
> >                 >         Imendoerffer,
> >                 >           HRB 16746 (AG Nuernberg)
> >                 >
> >
> -------------------------------------------------------------------
> >                 >
> >                 >
> >                 >
> >                 >
> >                 >
> >                 >
> >                 > --
> >                 > Darren Thompson
> >                 >
> >                 > Professional Services Engineer / Consultant
> >                 >
> >                 >  cid:image001.jpg at 01CB7C0C.6C6A2AE0
> >                 >
> >                 > Level 3, 60 City Road
> >                 >
> >                 > Southgate, VIC 3006
> >                 >
> >                 > Mb: 0400 640 414
> >                 >
> >                 > Mail: darrent at akurit.com.au
> >                 > Web: www.akurit.com.au
> >                 >
> >                 >
> >
> >
> >                 --
> >
> -------------------------------------------------------------------
> >                   Richard Brown, QA Engineer
> >                   Phone +4991174053-361,  Fax +4991174053-483
> >                   SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409
> >                 Nuernberg
> >                   Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix
> >                 Imendoerffer,
> >                   HRB 16746 (AG Nuernberg)
> >
> -------------------------------------------------------------------
> >
> >
> >
> >
> >
> >
> >         --
> >         Darren Thompson
> >
> >         Professional Services Engineer / Consultant
> >
> >          cid:image001.jpg at 01CB7C0C.6C6A2AE0
> >
> >         Level 3, 60 City Road
> >
> >         Southgate, VIC 3006
> >
> >         Mb: 0400 640 414
> >
> >         Mail: darrent at akurit.com.au
> >         Web: www.akurit.com.au
> >
> >
> >
> >
> >
> >
> > --
> > Darren Thompson
> >
> > Professional Services Engineer / Consultant
> >
> >  cid:image001.jpg at 01CB7C0C.6C6A2AE0
> >
> > Level 3, 60 City Road
> >
> > Southgate, VIC 3006
> >
> > Mb: 0400 640 414
> >
> > Mail: darrent at akurit.com.au
> > Web: www.akurit.com.au
> >
> >
>
>
> --
> -------------------------------------------------------------------
>   Richard Brown, QA Engineer
>   Phone +4991174053-361,  Fax +4991174053-483
>   SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
>   Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
>   HRB 16746 (AG Nuernberg)
> -------------------------------------------------------------------
>
>
>


-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/2256bac3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140528/2256bac3/attachment.jpg>

From S.M.Flood at ucs.cam.ac.uk  Wed May 28 07:40:01 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Wed, 28 May 2014 14:40:01 +0100
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <5385DFFE.2010807@suse.com>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>	<1401264901.31434.25.camel@ibrokeit.suse.de>	<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>	<1401266203.31434.30.camel@ibrokeit.suse.de>	<CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>	<CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>	<1401279336.31434.44.camel@ibrokeit.suse.de>
	<5385DFFE.2010807@suse.com>
Message-ID: <5385E731.1060201@ucs.cam.ac.uk>

On 28/05/2014 14:09, Bjoern Lotz wrote:

> Is there some documentation on this somewhere? lio_node --help brings
> up a log of options, but there is no manual page for it.

In searching for some docs I came across 
http://linux-iscsi.org/wiki/Lio-utils which notes

--begin--
Use targetcli[1] instead.
lio-utils are deprecated and have been superseded by targetcli, please 
see the RTS OS Admin Manual.
---end---

and essentially just gives the --help output whereas the targetcli page 
seems more useful and targetcli is included with SLES12 Beta 7.

HTH,
Simon

[1] http://linux-iscsi.org/wiki/Targetcli
[2] http://www.linux-iscsi.org/Doc/RTS%20OS%20Admin%20Manual.pdf
-- 
Simon Flood
Senior Systems Specialist
University of Cambridge
United Kingdom

Novell/SUSE/NetIQ Knowledge Partner

From wendy at cray.com  Wed May 28 08:01:02 2014
From: wendy at cray.com (Wendy Palm)
Date: Wed, 28 May 2014 14:01:02 +0000
Subject: [sles-beta] static libraries
In-Reply-To: <20140528082150.GB6568@linux-w520.guibland.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
Message-ID: <D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>

I think this is incorrect.  It's in the libbz2-devel rpm in SLE 11-SP3-SDK.

# mount -o loop SLE-11-SP3-SDK-DVD-x86_64-GM-DVD1.iso /mnt1
# rpm -q -p /mnt1/suse/x86_64/libbz2-devel-1.0.5-34.253.1.x86_64.rpm --filesbypkg
libbz2-devel              /usr/include/bzlib.h
libbz2-devel              /usr/lib64/libbz2.a
libbz2-devel              /usr/lib64/libbz2.so

> -----Original Message-----
> From: Antoine Ginies [mailto:aginies at suse.com]
> Sent: Wednesday, May 28, 2014 3:22 AM
> To: Wendy Palm
> Cc: sles-beta at lists.suse.com
> Subject: Re: [sles-beta] static libraries
> 
> Wendy Palm:
> > Ok, what about libbz2.a?
> >
> > It's not included in glibc-devel-static (at least as of beta 6.  We're still in the
> process of downloading beta7).
> 
> We do not provide bzip2-devel-static libraries in SLE12. I have done a check in
> SLE11SP3 and it seems we don't provide it also.
> 
> Regards.
> 
> Antoine
> 
> > > -----Original Message-----
> > > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> > > bounces at lists.suse.com] On Behalf Of Wendy Palm
> > > Sent: Tuesday, May 27, 2014 3:39 PM
> > > To: Antoine Ginies
> > > Cc: sles-beta at lists.suse.com
> > > Subject: Re: [sles-beta] static libraries
> > >
> > > Thanks.  we hadn't noticed those.
> > >
> > > > -----Original Message-----
> > > > From: Antoine Ginies [mailto:aginies at suse.com]
> > > > Sent: Tuesday, May 27, 2014 3:31 PM
> > > > To: Wendy Palm
> > > > Cc: sles-beta at lists.suse.com
> > > > Subject: Re: [sles-beta] static libraries
> > > >
> > > > Wendy Palm:
> > > > > We ran into a problem trying to build some of our internal tests.
> > > > > It looks like SLES12 no longer includes libc.a or libpthread.a.
> > > > >
> > > > > Is it planned that static libraries will no longer be provided?
> > > >
> > > > hello,
> > > > static libraries are provided in the SLE-12-SDK-DVD iso.
> > > > "glibc-devel-static*.rpm" will provide you libc.a and libpthread.a.
> > > >
> > > > Regards.
> > > >
> > > > Antoine
> > > >
> > > >
> > > >
> > > > --
> > > > Antoine Ginies <aginies at suse.com>
> > > > Project Manager
> > > > SUSE France
> > > _______________________________________________
> > > sles-beta mailing list
> > > sles-beta at lists.suse.com
> > > http://lists.suse.com/mailman/listinfo/sles-beta
> >
> 
> --
> Antoine Ginies <aginies at suse.com>
> Project Manager
> SUSE France

From kukuk at suse.de  Wed May 28 08:11:12 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Wed, 28 May 2014 16:11:12 +0200
Subject: [sles-beta] static libraries
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
Message-ID: <20140528141112.GA28787@suse.de>

On Wed, May 28, Wendy Palm wrote:

> I think this is incorrect.  It's in the libbz2-devel rpm in SLE 11-SP3-SDK.

Static linking, especially with glibc, creates a lot of problems.
The biggest ones are, that dynamic loading doesn't work correct
anymore (which means that glibc NSS modules used by getXXnam() and
similar functions don't function correct anymore) and that you 
need to recompile everything for every single bug fix or security
update.
For that reason we decided already 5 years ago to not ship
static libraries anymore for a lot of packages, including libbz2.

  Thorsten

-- 
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)

From rbrown at suse.de  Wed May 28 08:15:32 2014
From: rbrown at suse.de (Richard Brown)
Date: Wed, 28 May 2014 16:15:32 +0200
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <5385E731.1060201@ucs.cam.ac.uk>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>
	<1401264901.31434.25.camel@ibrokeit.suse.de>
	<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>
	<1401266203.31434.30.camel@ibrokeit.suse.de>
	<CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>
	<CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>
	<1401279336.31434.44.camel@ibrokeit.suse.de>
	<5385DFFE.2010807@suse.com> <5385E731.1060201@ucs.cam.ac.uk>
Message-ID: <1401286532.31434.55.camel@ibrokeit.suse.de>

On 28/05/2014 14:09, Bjoern Lotz wrote:
> > Is there some documentation on this somewhere? lio_node --help
brings
> > up a log of options, but there is no manual page for it.

lio_node is what YaST is using 'under the hood' to interact with the LIO
target - I came to know about it working on some bugs in earlier betas,
but my knowledge is not exhaustive and I can't point you in the
direction of any documentation, sorry.

On Wed, 2014-05-28 at 14:40 +0100, Simon Flood wrote:
> In searching for some docs I came across 
> http://linux-iscsi.org/wiki/Lio-utils which notes
> 
> --begin--
> Use targetcli[1] instead.
> lio-utils are deprecated and have been superseded by targetcli, please 
> see the RTS OS Admin Manual.
> ---end---
> 
> and essentially just gives the --help output whereas the targetcli page 
> seems more useful and targetcli is included with SLES12 Beta 7.

It's included, but it certainly isn't working on my Beta 7 test
machines.. Reporting that bug, nice catch :)

Regards,

- Richard

-- 
-------------------------------------------------------------------
  Richard Brown, QA Engineer
  Phone +4991174053-361,  Fax +4991174053-483
  SUSE LINUX Products GmbH,  Maxfeldstr. 5,  D-90409 Nuernberg
  Geschaeftsfuehrer: Jeff Hawn, Jennifer Guild, Felix Imendoerffer,
  HRB 16746 (AG Nuernberg)
-------------------------------------------------------------------



From wendy at cray.com  Wed May 28 08:19:29 2014
From: wendy at cray.com (Wendy Palm)
Date: Wed, 28 May 2014 14:19:29 +0000
Subject: [sles-beta] static libraries
In-Reply-To: <20140528141112.GA28787@suse.de>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
	<20140528141112.GA28787@suse.de>
Message-ID: <D5048769A89C5C40BAC8CD7E108BF5E8240B7A80@CFWEX01.americas.cray.com>

Hence my earlier question about not providing the static libraries.

Could we get a list of what static libraries aren't being provided anymore?


> -----Original Message-----
> From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> bounces at lists.suse.com] On Behalf Of Thorsten Kukuk
> Sent: Wednesday, May 28, 2014 9:11 AM
> To: sles-beta at lists.suse.com
> Subject: Re: [sles-beta] static libraries
> 
> On Wed, May 28, Wendy Palm wrote:
> 
> > I think this is incorrect.  It's in the libbz2-devel rpm in SLE 11-SP3-SDK.
> 
> Static linking, especially with glibc, creates a lot of problems.
> The biggest ones are, that dynamic loading doesn't work correct
> anymore (which means that glibc NSS modules used by getXXnam() and
> similar functions don't function correct anymore) and that you
> need to recompile everything for every single bug fix or security
> update.
> For that reason we decided already 5 years ago to not ship
> static libraries anymore for a lot of packages, including libbz2.
> 
>   Thorsten
> 
> --
> Thorsten Kukuk, Senior Architect SLES & Common Code Base
> SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
> GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta

From Joel.Barbieri at merge.com  Wed May 28 08:44:16 2014
From: Joel.Barbieri at merge.com (Joel Barbieri)
Date: Wed, 28 May 2014 14:44:16 +0000
Subject: [sles-beta] static libraries
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
Message-ID: <1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>

- mount "source" or "sources" [as you show below]
- create a report of the files available from all rpms.
-- find /mnt1 -name "*.rpm" -exec rpm -qp '{}' --qf '[%{NAME} %{FILENAMES}\n]' \; > ~/rpm.pkgfiles
- search or grep for the objects you need...best to place objects in a file and ask grep to find the objects.
-- add regexes for objects interested in to the file "~/objects"  e.g. "libbz"
-- grep --color -f objects ~/rpm.pkgfiles

You can get fancier with awk if you want and report just the filenames after matching on the second field, but the above should help you pinpoint what you have or need.

You can even consider using tools to analyze your source objects to create your search object list, but I digress.  That, and I don't recall if ldd or nm or ar, or what would actually tear a statically linked file apart for its pieces.  ldd definitely tells you your dynamic library requirements, but for static...it's been too long and there are not many left for me to give you an answer to that question.

-Joel

-----Original Message-----
From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Wendy Palm
Sent: Wednesday, May 28, 2014 9:01 AM
To: Antoine Ginies
Cc: sles-beta at lists.suse.com
Subject: Re: [sles-beta] static libraries

I think this is incorrect.  It's in the libbz2-devel rpm in SLE 11-SP3-SDK.

# mount -o loop SLE-11-SP3-SDK-DVD-x86_64-GM-DVD1.iso /mnt1
# rpm -q -p /mnt1/suse/x86_64/libbz2-devel-1.0.5-34.253.1.x86_64.rpm --filesbypkg
libbz2-devel              /usr/include/bzlib.h
libbz2-devel              /usr/lib64/libbz2.a
libbz2-devel              /usr/lib64/libbz2.so

> -----Original Message-----
> From: Antoine Ginies [mailto:aginies at suse.com]
> Sent: Wednesday, May 28, 2014 3:22 AM
> To: Wendy Palm
> Cc: sles-beta at lists.suse.com
> Subject: Re: [sles-beta] static libraries
> 
> Wendy Palm:
> > Ok, what about libbz2.a?
> >
> > It's not included in glibc-devel-static (at least as of beta 6.  We're still in the
> process of downloading beta7).
> 
> We do not provide bzip2-devel-static libraries in SLE12. I have done a check in
> SLE11SP3 and it seems we don't provide it also.
> 
> Regards.
> 
> Antoine
> 
> > > -----Original Message-----
> > > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> > > bounces at lists.suse.com] On Behalf Of Wendy Palm
> > > Sent: Tuesday, May 27, 2014 3:39 PM
> > > To: Antoine Ginies
> > > Cc: sles-beta at lists.suse.com
> > > Subject: Re: [sles-beta] static libraries
> > >
> > > Thanks.  we hadn't noticed those.
> > >
> > > > -----Original Message-----
> > > > From: Antoine Ginies [mailto:aginies at suse.com]
> > > > Sent: Tuesday, May 27, 2014 3:31 PM
> > > > To: Wendy Palm
> > > > Cc: sles-beta at lists.suse.com
> > > > Subject: Re: [sles-beta] static libraries
> > > >
> > > > Wendy Palm:
> > > > > We ran into a problem trying to build some of our internal tests.
> > > > > It looks like SLES12 no longer includes libc.a or libpthread.a.
> > > > >
> > > > > Is it planned that static libraries will no longer be provided?
> > > >
> > > > hello,
> > > > static libraries are provided in the SLE-12-SDK-DVD iso.
> > > > "glibc-devel-static*.rpm" will provide you libc.a and libpthread.a.
> > > >
> > > > Regards.
> > > >
> > > > Antoine
> > > >
> > > >
> > > >
> > > > --
> > > > Antoine Ginies <aginies at suse.com>
> > > > Project Manager
> > > > SUSE France
> > > _______________________________________________
> > > sles-beta mailing list
> > > sles-beta at lists.suse.com
> > > http://lists.suse.com/mailman/listinfo/sles-beta
> >
> 
> --
> Antoine Ginies <aginies at suse.com>
> Project Manager
> SUSE France
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

From S.M.Flood at ucs.cam.ac.uk  Wed May 28 09:32:11 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Wed, 28 May 2014 16:32:11 +0100
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <1401286532.31434.55.camel@ibrokeit.suse.de>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>		<1401264901.31434.25.camel@ibrokeit.suse.de>		<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>		<1401266203.31434.30.camel@ibrokeit.suse.de>		<CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>		<CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>		<1401279336.31434.44.camel@ibrokeit.suse.de>
	<5385DFFE.2010807@suse.com>	 <5385E731.1060201@ucs.cam.ac.uk>
	<1401286532.31434.55.camel@ibrokeit.suse.de>
Message-ID: <5386017B.8080800@ucs.cam.ac.uk>

On 28/05/2014 15:15, Richard Brown wrote:

> It's included, but it certainly isn't working on my Beta 7 test
> machines.. Reporting that bug, nice catch :)

Nice catch considering I hadn't at that point tried it! ;-)

So having now tried it's also not working for me (in the same way as 
your bug #880355) on a freshly installed SLES12 Beta 7 test VM although 
I just tried targetcli with no parameters.

I have helped it along a tad by creating the directory 
/var/target/fabric which allowed me to run targetcli but trying to then 
exit caused another traceback error:

--begin--
Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
990, in run_interactive
     self._cli_loop()
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
820, in _cli_loop
     self.run_cmdline(cmdline)
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
934, in run_cmdline
     self._execute_command(path, command, pparams, kparams)
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
909, in _execute_command
     result = target.execute_command(command, pparams, kparams)
   File "/usr/lib/python2.7/site-packages/targetcli/ui_node.py", line 
103, in execute_command
     pparams, kparams)
   File "/usr/lib/python2.7/site-packages/configshell/node.py", line 
1416, in execute_command
     result = method(*pparams, **kparams)
   File "/usr/lib/python2.7/site-packages/targetcli/ui_node.py", line 
115, in ui_command_exit
     config = Config()
   File "/usr/lib/python2.7/site-packages/rtslib/config.py", line 133, 
in __init__
     self._load_policy()
   File "/usr/lib/python2.7/site-packages/rtslib/config.py", line 140, 
in _load_policy
     for path in os.listdir(self.policy_dir)
OSError: [Errno 2] No such file or directory: '/var/target/policy'
---end---

This time creating the directory /var/target/policy does not seem to be 
the instant "fix":

--begin--
Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
990, in run_interactive
     self._cli_loop()
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
820, in _cli_loop
     self.run_cmdline(cmdline)
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
934, in run_cmdline
     self._execute_command(path, command, pparams, kparams)
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
909, in _execute_command
     result = target.execute_command(command, pparams, kparams)
   File "/usr/lib/python2.7/site-packages/targetcli/ui_node.py", line 
103, in execute_command
     pparams, kparams)
   File "/usr/lib/python2.7/site-packages/configshell/node.py", line 
1416, in execute_command
     result = method(*pparams, **kparams)
   File "/usr/lib/python2.7/site-packages/targetcli/ui_node.py", line 
119, in ui_command_exit
     config.load_live()
   File "/usr/lib/python2.7/site-packages/rtslib/config.py", line 549, 
in load_live
     parse_tree = self._parser.parse_string(live)
   File "/usr/lib/python2.7/site-packages/rtslib/config_parser.py", line 
147, in parse_string
     return self._parser.parseString(string, parseAll=True).asList()
   File "/usr/lib/python2.7/site-packages/pyparsing.py", line 1041, in 
parseString
     raise exc
ParseException: Expected end of text (at char 0), (line:1, col:1)
---end---

so I tried removing the directory then creating a file instead. It wants 
a directory:

--begin--
Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
990, in run_interactive
     self._cli_loop()
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
820, in _cli_loop
     self.run_cmdline(cmdline)
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
934, in run_cmdline
     self._execute_command(path, command, pparams, kparams)
   File "/usr/lib/python2.7/site-packages/configshell/shell.py", line 
909, in _execute_command
     result = target.execute_command(command, pparams, kparams)
   File "/usr/lib/python2.7/site-packages/targetcli/ui_node.py", line 
103, in execute_command
     pparams, kparams)
   File "/usr/lib/python2.7/site-packages/configshell/node.py", line 
1416, in execute_command
     result = method(*pparams, **kparams)
   File "/usr/lib/python2.7/site-packages/targetcli/ui_node.py", line 
115, in ui_command_exit
     config = Config()
   File "/usr/lib/python2.7/site-packages/rtslib/config.py", line 133, 
in __init__
     self._load_policy()
   File "/usr/lib/python2.7/site-packages/rtslib/config.py", line 140, 
in _load_policy
     for path in os.listdir(self.policy_dir)
OSError: [Errno 20] Not a directory: '/var/target/policy'
---end---

Over to SUSE to continue the game ... ! ;-)

HTH,
Simon
-- 
Simon Flood
Senior Systems Specialist
University of Cambridge
United Kingdom

Novell/SUSE/NetIQ Knowledge Partner

From S.M.Flood at ucs.cam.ac.uk  Wed May 28 09:35:14 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Wed, 28 May 2014 16:35:14 +0100
Subject: [sles-beta] [Sleha-beta] ISCSI issues with SLES12B7 - part2 (
 ISCSI 'initiator' driver)
In-Reply-To: <5386017B.8080800@ucs.cam.ac.uk>
References: <CAEUhfEf5jL2yQ4DGREkF1MY7UGHZ6puMZQgLJQ=q1ESzZbCkLQ@mail.gmail.com>		<1401264901.31434.25.camel@ibrokeit.suse.de>		<CAEUhfEdvve+ZWmc536i_Hw2b1y=mmUrk=2HypLsCfb5SYP12Ew@mail.gmail.com>		<1401266203.31434.30.camel@ibrokeit.suse.de>		<CAEUhfEekauZi-vCS2oV4Xa+EMhhyJga+cXJiCVEohJysMHofyQ@mail.gmail.com>		<CAEUhfEcuY+nH6ZSppoJP+d8v4N3e+ZJMPVAZWUwd7YcX0QHcCg@mail.gmail.com>		<1401279336.31434.44.camel@ibrokeit.suse.de>	<5385DFFE.2010807@suse.com>	
	<5385E731.1060201@ucs.cam.ac.uk>	<1401286532.31434.55.camel@ibrokeit.suse.de>
	<5386017B.8080800@ucs.cam.ac.uk>
Message-ID: <53860232.5080102@ucs.cam.ac.uk>

On 28/05/2014 16:32, Simon Flood wrote:

> Nice catch considering I hadn't at that point tried it! ;-)
>
> So having now tried it's also not working for me (in the same way as
> your bug #880355) on a freshly installed SLES12 Beta 7 test VM although
> I just tried targetcli with no parameters.

..snip..

> Over to SUSE to continue the game ... ! ;-)

Oh and perhaps it's never worked with SLES11 SP3 (when first included) 
if bug #856490 is any indication.

HTH,
Simon
-- 
Simon Flood
Senior Systems Specialist
University of Cambridge
United Kingdom

Novell/SUSE/NetIQ Knowledge Partner

From wendy at cray.com  Wed May 28 11:27:04 2014
From: wendy at cray.com (Wendy Palm)
Date: Wed, 28 May 2014 17:27:04 +0000
Subject: [sles-beta] static libraries
In-Reply-To: <1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
	<1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>
Message-ID: <D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>

Thanks for the scriptlet - it's what I should have done earlier, but didn't take the time to do.

What I was inadequately getting at is that this is a change in strategy (granted, it's been ongoing for about 5 years) and it would be nice to include that kind of information in some kind of announcement, like in the changelog - that libbz2-devel is no longer going to be provided, or that the glibc static libraries have been moved to .... 
This is the first real beta tests that I've been involved in, and maybe I'm expecting too much, too early.
Maybe it's one of the ChangeLogs and I missed it, in which case I apologize for the waste of bandwidth.



> -----Original Message-----
> From: Joel Barbieri [mailto:Joel.Barbieri at merge.com]
> Sent: Wednesday, May 28, 2014 9:44 AM
> To: Wendy Palm; Antoine Ginies
> Cc: sles-beta at lists.suse.com
> Subject: RE: [sles-beta] static libraries
> 
> - mount "source" or "sources" [as you show below]
> - create a report of the files available from all rpms.
> -- find /mnt1 -name "*.rpm" -exec rpm -qp '{}' --qf '[%{NAME}
> %{FILENAMES}\n]' \; > ~/rpm.pkgfiles
> - search or grep for the objects you need...best to place objects in a file and
> ask grep to find the objects.
> -- add regexes for objects interested in to the file "~/objects"  e.g. "libbz"
> -- grep --color -f objects ~/rpm.pkgfiles
> 
> You can get fancier with awk if you want and report just the filenames after
> matching on the second field, but the above should help you pinpoint what
> you have or need.
> 
> You can even consider using tools to analyze your source objects to create
> your search object list, but I digress.  That, and I don't recall if ldd or nm or ar,
> or what would actually tear a statically linked file apart for its pieces.  ldd
> definitely tells you your dynamic library requirements, but for static...it's
> been too long and there are not many left for me to give you an answer to
> that question.
> 
> -Joel
> 
> -----Original Message-----
> From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> bounces at lists.suse.com] On Behalf Of Wendy Palm
> Sent: Wednesday, May 28, 2014 9:01 AM
> To: Antoine Ginies
> Cc: sles-beta at lists.suse.com
> Subject: Re: [sles-beta] static libraries
> 
> I think this is incorrect.  It's in the libbz2-devel rpm in SLE 11-SP3-SDK.
> 
> # mount -o loop SLE-11-SP3-SDK-DVD-x86_64-GM-DVD1.iso /mnt1
> # rpm -q -p /mnt1/suse/x86_64/libbz2-devel-1.0.5-34.253.1.x86_64.rpm --
> filesbypkg
> libbz2-devel              /usr/include/bzlib.h
> libbz2-devel              /usr/lib64/libbz2.a
> libbz2-devel              /usr/lib64/libbz2.so
> 
> > -----Original Message-----
> > From: Antoine Ginies [mailto:aginies at suse.com]
> > Sent: Wednesday, May 28, 2014 3:22 AM
> > To: Wendy Palm
> > Cc: sles-beta at lists.suse.com
> > Subject: Re: [sles-beta] static libraries
> >
> > Wendy Palm:
> > > Ok, what about libbz2.a?
> > >
> > > It's not included in glibc-devel-static (at least as of beta 6.  We're still in
> the
> > process of downloading beta7).
> >
> > We do not provide bzip2-devel-static libraries in SLE12. I have done a check
> in
> > SLE11SP3 and it seems we don't provide it also.
> >
> > Regards.
> >
> > Antoine
> >
> > > > -----Original Message-----
> > > > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> > > > bounces at lists.suse.com] On Behalf Of Wendy Palm
> > > > Sent: Tuesday, May 27, 2014 3:39 PM
> > > > To: Antoine Ginies
> > > > Cc: sles-beta at lists.suse.com
> > > > Subject: Re: [sles-beta] static libraries
> > > >
> > > > Thanks.  we hadn't noticed those.
> > > >
> > > > > -----Original Message-----
> > > > > From: Antoine Ginies [mailto:aginies at suse.com]
> > > > > Sent: Tuesday, May 27, 2014 3:31 PM
> > > > > To: Wendy Palm
> > > > > Cc: sles-beta at lists.suse.com
> > > > > Subject: Re: [sles-beta] static libraries
> > > > >
> > > > > Wendy Palm:
> > > > > > We ran into a problem trying to build some of our internal tests.
> > > > > > It looks like SLES12 no longer includes libc.a or libpthread.a.
> > > > > >
> > > > > > Is it planned that static libraries will no longer be provided?
> > > > >
> > > > > hello,
> > > > > static libraries are provided in the SLE-12-SDK-DVD iso.
> > > > > "glibc-devel-static*.rpm" will provide you libc.a and libpthread.a.
> > > > >
> > > > > Regards.
> > > > >
> > > > > Antoine
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Antoine Ginies <aginies at suse.com>
> > > > > Project Manager
> > > > > SUSE France
> > > > _______________________________________________
> > > > sles-beta mailing list
> > > > sles-beta at lists.suse.com
> > > > http://lists.suse.com/mailman/listinfo/sles-beta
> > >
> >
> > --
> > Antoine Ginies <aginies at suse.com>
> > Project Manager
> > SUSE France
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta

From kukuk at suse.de  Wed May 28 13:01:18 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Wed, 28 May 2014 21:01:18 +0200
Subject: [sles-beta] static libraries
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
	<1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>
Message-ID: <20140528190118.GA19031@suse.de>

On Wed, May 28, Wendy Palm wrote:

> What I was inadequately getting at is that this is a change in strategy (granted, it's been ongoing for about 5 years) and it would be nice to include that kind of information in some kind of announcement, like in the changelog - that libbz2-devel is no longer going to be provided, or that the glibc static libraries have been moved to .... 

It's written in the Changelog of bzip2 and in the ChangeLog of
the root directory of the first DVD.

  Thorsten
-- 
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)

From mge at suse.com  Wed May 28 12:04:27 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Wed, 28 May 2014 20:04:27 +0200
Subject: [sles-beta] static libraries
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
	<1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>
Message-ID: <20140528180427.GA8730@suse.com>

Hello Wendy and all,

On 2014-05-28 T 17:27 +0000 Wendy Palm wrote:

> Thanks for the scriptlet - it's what I should have
> done earlier, but didn't take the time to do.
> 
> What I was inadequately getting at is that this is a
> change in strategy (granted, it's been ongoing for
> about 5 years) and it would be nice to include that
> kind of information in some kind of announcement,
> like in the changelog - that libbz2-devel is no
> longer going to be provided, or that the glibc static
> libraries have been moved to .... 

the change of moving Development Packages to the SUSE
Linux Enterprise SDK has been introduced with SUSE
Linux Enterprise 11 already, and thus it is not
reflected in the SUSE Linux Enterprise 12 Release Notes
anymore: it is not a change anymore!

> This is the first real beta tests that I've been
> involved in, and maybe I'm expecting too much, too
> early.  Maybe it's one of the ChangeLogs and I missed
> it, in which case I apologize for the waste of
> bandwidth.

See:
https://www.suse.com/releasenotes/x86_64/SUSE-SLES/11-SP3/#id353133
Hope this explains.

so long -
	MgE 

> > -----Original Message-----
> > From: Joel Barbieri [mailto:Joel.Barbieri at merge.com]
> > Sent: Wednesday, May 28, 2014 9:44 AM
> > To: Wendy Palm; Antoine Ginies
> > Cc: sles-beta at lists.suse.com
> > Subject: RE: [sles-beta] static libraries
> > 
> > - mount "source" or "sources" [as you show below]
> > - create a report of the files available from all rpms.
> > -- find /mnt1 -name "*.rpm" -exec rpm -qp '{}' --qf '[%{NAME}
> > %{FILENAMES}\n]' \; > ~/rpm.pkgfiles
> > - search or grep for the objects you need...best to place objects in a file and
> > ask grep to find the objects.
> > -- add regexes for objects interested in to the file "~/objects"  e.g. "libbz"
> > -- grep --color -f objects ~/rpm.pkgfiles
> > 
> > You can get fancier with awk if you want and report just the filenames after
> > matching on the second field, but the above should help you pinpoint what
> > you have or need.
> > 
> > You can even consider using tools to analyze your source objects to create
> > your search object list, but I digress.  That, and I don't recall if ldd or nm or ar,
> > or what would actually tear a statically linked file apart for its pieces.  ldd
> > definitely tells you your dynamic library requirements, but for static...it's
> > been too long and there are not many left for me to give you an answer to
> > that question.
> > 
> > -Joel
> > 
> > -----Original Message-----
> > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> > bounces at lists.suse.com] On Behalf Of Wendy Palm
> > Sent: Wednesday, May 28, 2014 9:01 AM
> > To: Antoine Ginies
> > Cc: sles-beta at lists.suse.com
> > Subject: Re: [sles-beta] static libraries
> > 
> > I think this is incorrect.  It's in the libbz2-devel rpm in SLE 11-SP3-SDK.
> > 
> > # mount -o loop SLE-11-SP3-SDK-DVD-x86_64-GM-DVD1.iso /mnt1
> > # rpm -q -p /mnt1/suse/x86_64/libbz2-devel-1.0.5-34.253.1.x86_64.rpm --
> > filesbypkg
> > libbz2-devel              /usr/include/bzlib.h
> > libbz2-devel              /usr/lib64/libbz2.a
> > libbz2-devel              /usr/lib64/libbz2.so
> > 
> > > -----Original Message-----
> > > From: Antoine Ginies [mailto:aginies at suse.com]
> > > Sent: Wednesday, May 28, 2014 3:22 AM
> > > To: Wendy Palm
> > > Cc: sles-beta at lists.suse.com
> > > Subject: Re: [sles-beta] static libraries
> > >
> > > Wendy Palm:
> > > > Ok, what about libbz2.a?
> > > >
> > > > It's not included in glibc-devel-static (at least as of beta 6.  We're still in
> > the
> > > process of downloading beta7).
> > >
> > > We do not provide bzip2-devel-static libraries in SLE12. I have done a check
> > in
> > > SLE11SP3 and it seems we don't provide it also.
> > >
> > > Regards.
> > >
> > > Antoine
> > >
> > > > > -----Original Message-----
> > > > > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-
> > > > > bounces at lists.suse.com] On Behalf Of Wendy Palm
> > > > > Sent: Tuesday, May 27, 2014 3:39 PM
> > > > > To: Antoine Ginies
> > > > > Cc: sles-beta at lists.suse.com
> > > > > Subject: Re: [sles-beta] static libraries
> > > > >
> > > > > Thanks.  we hadn't noticed those.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Antoine Ginies [mailto:aginies at suse.com]
> > > > > > Sent: Tuesday, May 27, 2014 3:31 PM
> > > > > > To: Wendy Palm
> > > > > > Cc: sles-beta at lists.suse.com
> > > > > > Subject: Re: [sles-beta] static libraries
> > > > > >
> > > > > > Wendy Palm:
> > > > > > > We ran into a problem trying to build some of our internal tests.
> > > > > > > It looks like SLES12 no longer includes libc.a or libpthread.a.
> > > > > > >
> > > > > > > Is it planned that static libraries will no longer be provided?
> > > > > >
> > > > > > hello,
> > > > > > static libraries are provided in the SLE-12-SDK-DVD iso.
> > > > > > "glibc-devel-static*.rpm" will provide you libc.a and libpthread.a.
> > > > > >
> > > > > > Regards.
> > > > > >
> > > > > > Antoine
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Antoine Ginies <aginies at suse.com>
> > > > > > Project Manager
> > > > > > SUSE France
> > > > > _______________________________________________
> > > > > sles-beta mailing list
> > > > > sles-beta at lists.suse.com
> > > > > http://lists.suse.com/mailman/listinfo/sles-beta
> > > >
> > >
> > > --
> > > Antoine Ginies <aginies at suse.com>
> > > Project Manager
> > > SUSE France
> > _______________________________________________
> > sles-beta mailing list
> > sles-beta at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/sles-beta
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
> 

-- 
Matthias G. Eckermann     Senior Product Manager   SUSE? Linux Enterprise
Phone: +49 30 44315731    Mobile: +49 179 2949448    E-Mail: mge at suse.com
SUSE LINUX Products GmbH  Maxfeldstra?e 5          90409 N?rnberg Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)

From S.M.Flood at ucs.cam.ac.uk  Wed May 28 13:48:51 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Wed, 28 May 2014 20:48:51 +0100
Subject: [sles-beta] static libraries
In-Reply-To: <20140528180427.GA8730@suse.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
	<1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>
	<20140528180427.GA8730@suse.com>
Message-ID: <13dbf53f-1982-4e58-baf6-ab3637da5117@email.android.com>

On 28 May 2014 19:04:27 BST, "Matthias G. Eckermann" wrote:

>See:
>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/11-SP3/#id353133

Fourth bullet in chapter 6 of SLES11 (SP0) release notes dated 2009-11-06 might help confirm the history of the decision - see https://www.suse.com/releasenotes/x86_64/SUSE-SLES/11/#rnotes-update

HTH, 
Simon
Simon Flood
Senior Systems Specialist
University of Cambridge
United Kingdom

Novell/SUSE/NetIQ Knowledge Partner

From jrecord at suse.com  Thu May 29 10:25:47 2014
From: jrecord at suse.com (Jason Record)
Date: Thu, 29 May 2014 10:25:47 -0600
Subject: [sles-beta] Supportconfig Analysis Tools with SLE12
Message-ID: <53870B2B020000150029B9AD@prv-mh.provo.novell.com>

Please share any feedback you may have. 

Quick Setup Guide for SLES/SLED 12 Supportconfig Analysis (SCA) Tools

The SCA Tools analyze supportconfig archives for known issues and then create an SCA Report with the analysis results. Novell Technical Support has been using the SCA Appliance internally for years to reduce service request resolution times. Every inbound supportconfig is analyzed with the SCA Appliance, and the SCA Report is attached to the service request for engineers to evaluate. The SCA Tools are now available with SLES/SLED 12.

There are two tools; the data center solution and a command line tool. Both tools analyze supportconfig files and create an HTML report with the result. They both use the same patterns. They both have the ability to save the supportconfig archives they analyze if the archive mode is enabled. The patterns are modular, allowing the SCA Tools to analyze SLE10, SLE11, SLE12, OES, HAE and other products for which patterns have been written. You can write your own custom patterns in any programming language you like. Supportconfig analysis is done off the production server. Only a supportconfig is run on the server.

So, what's the difference between the two tools?

------------------------------------------------------------------------------------------
- SCA Appliance 
------------------------------------------------------------------------------------------
This is the data center solution requiring a Web and LAMP stack to store all the analysis results. It runs as a server-side tool and does not require any user interaction. Simply upload supportconfigs to it, and they get analyzed. View the SCA Reports through a web interface. It is meant to be scalable for analyzing a lot of supportconfigs on a regular basis. Available on SLES media only.

Prerequisites:
1. Web and LAMP Pattern
2. Web and Scripting Module (You must register the server at install time to select this module)

------------------------------------------------------------------------------------------
Install Using Anonymous FTP (Non-interactive, good for cron jobs)
# zypper install sca-appliance-* sca-patterns-* vsftpd
# systemctl enable apache2.service
# systemctl start apache2.service
# systemctl enable vsftpd.service
# systemctl start vsftpd.service
# yast ftp-server (Select Authentication, Enable Upload, Anonymous Can Upload, Finish, Yes to Create /srv/ftp/upload)
# chkconfig mysql on
# rcmysql start
# mysql_secure_installation (Creates a MariaDB root password)
# setup-sca -f

Usage
Upload any supportconfig to the SCA Appliance Server via anonymous FTP. All supportconfigs will be analyzed and stored in the database. Open the http://<your_sca_appliance_ip>/sca/ URL to view the SCA Reports. The Web interface password is set using the setup-sca tool.

Examples:
  supportconfig -U "ftp://<your_sca_appliance_ip>/upload/"
  supportconfig -U "scp://<your_sca_appliance_ip>/srv/ftp/upload/"
  ftp -u "<your_sca_appliance_ip>:/upload/nts_<supportconig_file>.tbz" /path/to/local/nts_<supportconfig_file>.tbz
  scp /path/to/local/nts_<supportconifg_file>.tbz <your_sca_appliance_ip>:/srv/ftp/upload

You could include 'supportconfig -QU "ftp://<your_sca_appliance_ip>/upload/"' in cron jobs on servers to be analyzed on a regular basis.

------------------------------------------------------------------------------------------
Install Using SCP /tmp (Requires supportconfig interaction when typing the SSH password)
# zypper install sca-appliance-* sca-patterns-*
# systemctl enable apache2.service
# systemctl start apache2.service
# chkconfig mysql on
# rcmysql start
# mysql_secure_installation
# setup-sca

Usage
Upload any supportconfig to the /tmp directory on the SCA Appliance Server. All supportconfigs will be analyzed and stored in the database. Open the http://<your_sca_appliance_ip>/sca/ URL to view the SCA Reports. The password is set using the setup-sca tool.

Examples:
  supportconfig -U "scp://<your_sca_appliance_ip>/tmp"
  scp /path/to/local/nts_<supportconifg_file>.tbz <your_sca_appliance_ip>:/tmp


------------------------------------------------------------------------------------------
- SCA Command Line Tool
------------------------------------------------------------------------------------------
This is an end-user, command line tool that does not require a web server or database. It just uses the patterns to analyze a server and generates an HTML report file. It requires user interaction. It is meant to be on your laptop so you can analyze any server you may need to quickly check out. The analysis is done on your server; only the supportconfig runs on the production server. You don't have to wait to start using the SCA Tool. You can download it off of OBS. I have included some instructions below. The SCA Tool is nice when you don't want to have a VM on your laptop just to analyze a server here and there. Available on SLES and SLED media.

Install
# zypper install sca-server-report sca-patterns-*

Examples:

# scatool -s
Runs supportconfig on the local host and analyzes its output. It saves the HTML report file to the same location at the supportconfig with the same name, but ending in .html.

# scatool -a /var/log/nts_localhost_131107_1315.tbz
Analyzes the supportconfig archive file specified. The path can be a tarred compressed supportconfig archive or a suportconfig extracted directory, either will work. The HTML report file is saved in the save location as the supportconfig archive or directory.

# scatool -sk -o /opt/sca/reports/
Runs supportconfig on the local host. It saves the HTML report file in the output path specified instead of the default path of the supportconfig tarball. Keeps the supportconfig tar ball for future reference.

# scatool -a sles_server.company.com
Establishes an ssh connection to sles_server.company.com to run a supportconfig on the server. The supportconfig is then copied back to the local host to be analyzed. The HTML report file is saved to the default /var/log directory.

See scatool(8) and scatool.conf(5)


From aryan at allantgroup.com  Wed May 28 10:48:17 2014
From: aryan at allantgroup.com (genanr)
Date: Wed, 28 May 2014 11:48:17 -0500
Subject: [sles-beta] problems with sssd in beta6 and beta7
Message-ID: <53861351.4030603@allantgroup.com>

     I am using sssd (ldap) for authentication and it works fine with 
the sssd packages from beta5.  However, when I upgraded to beta6, and 
then again to beta7, sssd stops working with ldap based users, claims 
user does not exist.   Configuration files are exactly the same and when 
I downgrade back to the sssd packages from beta5 things start working again.

Andy


From aryan at allantgroup.com  Wed May 28 14:05:40 2014
From: aryan at allantgroup.com (genanr)
Date: Wed, 28 May 2014 15:05:40 -0500
Subject: [sles-beta] Inconsistent startup
Message-ID: <53864194.6020202@allantgroup.com>

     I am seeing some startup issues, but they do not always occur. 
Pacemaker, at least partially dies  after a short time.  This causes the 
server to get fenced and rebooted.  Before the server reboots, I can see 
that /bin/hostname is in the 'D' state.  I believe that because 
/bin/hostname is in the 'D' pacemaker eventually dies. Since this 
problem does not happen all the time, my only guess would be some race 
condition in the startup sequence.  I mainly been testing on beta6 and 
just started upgrading the test servers to beta7.  The problem still 
occurs on beta7, I do not know if the problem existed before beta6.

Thanks,

Andy

From Dick.Waite at softwareag.com  Fri May 30 08:19:35 2014
From: Dick.Waite at softwareag.com (Waite, Dick)
Date: Fri, 30 May 2014 14:19:35 +0000
Subject: [sles-beta] SLES 12 Beta7 on a Physical Machine
In-Reply-To: <53834CFB0200006D00162778@prv-mh.provo.novell.com>
References: <46AC8C81C10B8C48820201DF2AE1D76D53837860@hqmbx6.eur.ad.sag>
	<53834CFB0200006D00162778@prv-mh.provo.novell.com>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D5383AF2B@hqmbx6.eur.ad.sag>

Hi Mark,

        Sorry getting some time this week has proved a problem. I have got Beta7 ready to go but I needed a z/VM chap to make some changes, it?s a big holiday week in Germany...We did have a clean NEW install with Beta5, we tried an Update with Beta6 and that, as with x86_64 needs some manual work, which gave us issues we could not get past. We will go back to a New install with Beta7 and then if that is Okay try an Update, but I'm still getting issues with x86_64 in that area. SR's have been created and as RC1 is some time away lets hope we do get a clean Update, be grand to run some SAG applications...

        I did notice you're scheduled to one of the KVM pitch's at the SHARE Conference in Pittsburgh, I'm hoping to get over, been awhile. Maybe I could offer a User Experience with RHEL v7 and SLES v12 ...

15693          KVM for System z                                                                                           Tues   2014-08-05, 10:00:00     Mark Post

        I'll try and get some input for you next week. Our issues are getting KDE Updated to Gnome, Network and Wicked, Cron and Systemd, the Update still needs hand work and that is what we don?t want. With RHEL v7, Updated from v6 running on many US sites without issues its giving SLES v12 internally not good press. Some of the developers are switching to openSUSE as desktops to access the Development SLES v12 servers, openSUSE still supports KDE, for how much longer?

__R


___________________________________________
Dick Waite
Senior R&D Consultant
Phone:  +49 6151 92-1505
Mobile: +49 171 8393 769
Software AG
Uhlandstr. 12 | 64297 Darmstadt | Germany
www.softwareag.com
___________________________________________



-----Original Message-----
From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Mark Post
Sent: Monday, May 26, 2014 8:18 PM
To: 'sles-beta at lists.suse.com'
Subject: Re: [sles-beta] SLES 12 Beta7 on a Physical Machine

>>> On 5/26/2014 at 11:12 AM, "Waite, Dick" <Dick.Waite at softwareag.com> wrote:
> But we still have issues installing on zLinux and that only has grand
> z/VM under it.

Details?  I've been doing a _lot_ of installs with very little problem.  So, exact parms used, etc., etc.


Mark Post

_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From Dick.Waite at softwareag.com  Fri May 30 08:26:03 2014
From: Dick.Waite at softwareag.com (Waite, Dick)
Date: Fri, 30 May 2014 14:26:03 +0000
Subject: [sles-beta] static libraries
In-Reply-To: <20140528190118.GA19031@suse.de>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
	<1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>
	<20140528190118.GA19031@suse.de>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D5383BF67@hqmbx6.eur.ad.sag>

Grand TGIF Thorsten,

        You do have a grand grasp as to when and where SUSE changes were / are documented. Where was "drop KDE" documented before the v12 Kick-off meeting?

        Have You all a grand weekend.

__R

___________________________________________
Dick Waite
Senior R&D Consultant
Phone:  +49 6151 92-1505
Mobile: +49 171 8393 769
Software AG
Uhlandstr. 12 | 64297 Darmstadt | Germany
www.softwareag.com
___________________________________________




-----Original Message-----
From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Thorsten Kukuk
Sent: Wednesday, May 28, 2014 9:01 PM
To: sles-beta at lists.suse.com
Subject: Re: [sles-beta] static libraries

On Wed, May 28, Wendy Palm wrote:

> What I was inadequately getting at is that this is a change in strategy (granted, it's been ongoing for about 5 years) and it would be nice to include that kind of information in some kind of announcement, like in the changelog - that libbz2-devel is no longer going to be provided, or that the glibc static libraries have been moved to ....

It's written in the Changelog of bzip2 and in the ChangeLog of the root directory of the first DVD.

  Thorsten
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) _______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From mge at suse.com  Fri May 30 10:32:13 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Fri, 30 May 2014 18:32:13 +0200
Subject: [sles-beta] static libraries
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D5383BF67@hqmbx6.eur.ad.sag>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
	<1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>
	<20140528190118.GA19031@suse.de>
	<46AC8C81C10B8C48820201DF2AE1D76D5383BF67@hqmbx6.eur.ad.sag>
Message-ID: <20140530163213.GD23695@suse.com>

Hello Dick and all,

On 2014-05-30 T 14:26 +0000 Waite, Dick wrote:
 
> You do have a grand grasp as to when and where SUSE
> changes were / are documented. Where was "drop KDE"
> documented before the v12 Kick-off meeting?

We (myself and other members of the product management
team) talked about SUSE Linux Enterprise 12 and its
focus at SUSECon 2013, and our annual conference to me
seems the right place for this kind of discussion,
before the product is not even in beta.

See the session overview at:
http://www.susecon.com/archive-2013.html

Or more specifically (starting slide 11):
https://www.suse.com/events/susecon2013/sessions/presentations/FUT1405.pdf
 
> Have You all a grand weekend.
 
For you as well.

so long -
	MgE

-- 
Matthias G. Eckermann     Senior Product Manager   SUSE? Linux Enterprise
Phone: +49 30 44315731    Mobile: +49 179 2949448    E-Mail: mge at suse.com
SUSE LINUX Products GmbH  Maxfeldstra?e 5          90409 N?rnberg Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)

From varkoly at suse.com  Fri May 30 21:44:56 2014
From: varkoly at suse.com (=?iso-8859-1?Q?P=E9ter_Varkoly?=)
Date: Sat, 31 May 2014 05:44:56 +0200
Subject: [sles-beta] problems with sssd in beta6 and beta7
In-Reply-To: <53861351.4030603@allantgroup.com>
References: <53861351.4030603@allantgroup.com>
Message-ID: <4C14D89D-6884-401C-9F03-8D9A00353A9F@suse.com>

Can you provide me your configuration file?
Am 28.05.2014 um 18:48 schrieb genanr <aryan at allantgroup.com>:

>    I am using sssd (ldap) for authentication and it works fine with the sssd packages from beta5.  However, when I upgraded to beta6, and then again to beta7, sssd stops working with ldap based users, claims user does not exist.   Configuration files are exactly the same and when I downgrade back to the sssd packages from beta5 things start working again.
> 
> Andy
> 
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
> 


From Dick.Waite at softwareag.com  Sat May 31 01:09:09 2014
From: Dick.Waite at softwareag.com (Waite, Dick)
Date: Sat, 31 May 2014 07:09:09 +0000
Subject: [sles-beta] static libraries
In-Reply-To: <20140530163213.GD23695@suse.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240B7123@CFWEX01.americas.cray.com>
	<20140527203127.GA24153@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B725F@CFWEX01.americas.cray.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7357@CFWEX01.americas.cray.com>
	<20140528082150.GB6568@linux-w520.guibland.com>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B79F4@CFWEX01.americas.cray.com>
	<1E287A5DDB506E478DE9CAE3C8492D015A8D9D95@BRDC-MBX-1.network.internal>
	<D5048769A89C5C40BAC8CD7E108BF5E8240B7DE6@CFWEX01.americas.cray.com>
	<20140528190118.GA19031@suse.de>
	<46AC8C81C10B8C48820201DF2AE1D76D5383BF67@hqmbx6.eur.ad.sag>,
	<20140530163213.GD23695@suse.com>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D5383E228@hqmbx6.eur.ad.sag>

Grand Sunny Saturday,

Well its there in black and white, wish I had been there but water under bridge now. Like editors, Display Environments are very personal. I have been SuSE and SUSE since the 90's and KDE has been my desktop. I do hope its stays with openSUSE, I have not seen any "dropping" words from that source. We have made use of KDE's features for any years so it will take time to change. Our US customers are more Redhat and KDE is alive and well in v7 so for them its business as usual but in Europe and Asia its more SUSE and KDE, so work to be done, or thinking to be done first then work.
I'm trying to get two samples of our QE and App_Dev machines past the "Update" phases and with Beta7 we are still trying on both zLinux and x86_64.
You did publish SUSE will drop KDE, we missed it and I think a few others did. I follow openSUSE as to what SUSE is going to do next, try out new idea's, new features etc. Fedora seems to lead the way for RHEL.
We have done very little application testing and building with SUSE v12 because we can not get these machine to that level. New install does work, but that is not what we need, we Update the Operating Systems and check all is well, then maybe at nn-SP1 we start compiling the application and check that they work. Working on the idea, never change more than you need to, first the OS then the APP. Customers like to know their database is in safe hands, Evolution not Revolution, but on the Tablet and front Ends there is a fast change.
A gave Google the words "SUSE drop KDE", on .com there is not a lot to see, one entry from Nov 9th 2005 says SuSE exits KDE, and the words are not good words, on .DE that entry is there but very little else. There are a lot of very +ve words from SUSE about KDE ;o)

Okay time to push on, water is under bridge, lets think and plan what we do next.

__R
________________________________________
From: Matthias G. Eckermann [mge at suse.com]
Sent: 30 May 2014 18:32
To: Waite, Dick; 'Thorsten Kukuk'; 'sles-beta at lists.suse.com'
Subject: Re: [sles-beta] static libraries

Hello Dick and all,

On 2014-05-30 T 14:26 +0000 Waite, Dick wrote:

> You do have a grand grasp as to when and where SUSE
> changes were / are documented. Where was "drop KDE"
> documented before the v12 Kick-off meeting?

We (myself and other members of the product management
team) talked about SUSE Linux Enterprise 12 and its
focus at SUSECon 2013, and our annual conference to me
seems the right place for this kind of discussion,
before the product is not even in beta.

See the session overview at:
http://www.susecon.com/archive-2013.html

Or more specifically (starting slide 11):
https://www.suse.com/events/susecon2013/sessions/presentations/FUT1405.pdf

> Have You all a grand weekend.

For you as well.

so long -
        MgE

--
Matthias G. Eckermann     Senior Product Manager   SUSE? Linux Enterprise
Phone: +49 30 44315731    Mobile: +49 179 2949448    E-Mail: mge at suse.com
SUSE LINUX Products GmbH  Maxfeldstra?e 5          90409 N?rnberg Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)

Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com


From gjn at gjn.priv.at  Sat May 31 05:34:26 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Sat, 31 May 2014 13:34:26 +0200
Subject: [sles-beta] HOSTNAME Problem
Message-ID: <3376763.HOEN67kc4n@gjn.priv.at>

Hello,

When I install and configure in YaST2 Networkconfig the Hostname eg. "mein 
gross.at"

and I setup a intern NIC (domain) for a IP 192.xxx.xxx.xxx. "mein.klein.prv"

I have hostname -f "mein.klein.prv" I mean this is wrong ?

What reading yast2 ? in /etc/HOSTNAME is "mein.gross.at"


The YaST2 Module LDAP Kerberos .... afterward have by the configuration the 
wrong hostname. (Doimain)?


PS.:

I mean I found the Problem (?) YaST2 and "hostname -f" read the first entry in 
/etc/host ???
this is

192.xxx.xxx.xxx  mein.klein.prv mein
89.xxx.xxx.xxx    mein gross.at mein

when I change the settings I have the correct Hostname.

89.xxx.xxx.xxx    mein gross.at mein
192.xxx.xxx.xxx  mein.klein.prv mein

But I mean this is a Bug ?

-- 
mit freundlichen Gr??en / best Regards,

  G?nther J. Niederwimmer

From gjn at gjn.priv.at  Sat May 31 07:33:18 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Sat, 31 May 2014 15:33:18 +0200
Subject: [sles-beta] YaST Kerberos Module
Message-ID: <2510441.XA1qnRBBUF@gjn.priv.at>

Hello,

Is the YasT2 Kerberos module deleted?

With auth-server only ldap is configured and started but krb5 is added.
-- 
mit freundlichen Gr??en / best Regards,

  G?nther J. Niederwimmer

From darrent at akurit.com.au  Sun Jun  1 18:54:01 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 2 Jun 2014 10:54:01 +1000
Subject: [sles-beta] Creating XEN VM files to use with HA cluster
In-Reply-To: <CAEUhfEfzY9_KxHjP2BEKK8LsBtVLHE3Q9Rt7oAvSr6DKyv2eHA@mail.gmail.com>
References: <CAEUhfEfzY9_KxHjP2BEKK8LsBtVLHE3Q9Rt7oAvSr6DKyv2eHA@mail.gmail.com>
Message-ID: <CAEUhfEcY9gFL=_fEgbuT++G0_epnA0t9x4=k6=cVQgF8s9qQBw@mail.gmail.com>

Team

Found it, old dog needs to learn some new tricks ;-)

"# virsh dumpxml *GuestID* > *guest.xml"*

From:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html
(Is there updated SLES12 documentation on this yet)

Also, the original Xen OCF cluster resource cannot be used as it's hard
coded to "xm" which is depreciated.

There is a new 'VirtualDomain' OCF file which is used for clustering
'lib-virt' compatible VM's (which seems to support Xen, KVM etc).

Darren


On 31 May 2014 15:58, Darren Thompson <darrent at akurit.com.au> wrote:

> Team
>
> I must be missing something obvious, but how do you get the VM config
> files for HA
>
> In SLES11+ the VM create tool created the configuration file or you could
> run "xm list {vmname} -l <= That;s from memory and my not be correct syntax.
>
> I have created a VM using the new virt-manager but it does not seem to
> have created a config file.
>
> The xl list command does not seem to "find" the VM when it's running and
> does not list it at all when stopped (I can only start it from virt-manager
> itself).
>
> Any hints/tips appreciated as I'm sure that I'm missing something that
> should be obvious.
>
> Darren
>
>
> --
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au <steve at akurit.com.au>
> Web: www.akurit.com.au
>



-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140602/8065a6d3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140602/8065a6d3/attachment.jpg>

From darrent at akurit.com.au  Sun Jun  1 20:08:49 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 2 Jun 2014 12:08:49 +1000
Subject: [sles-beta] Creating XEN VM files to use with HA cluster
In-Reply-To: <CAEUhfEcY9gFL=_fEgbuT++G0_epnA0t9x4=k6=cVQgF8s9qQBw@mail.gmail.com>
References: <CAEUhfEfzY9_KxHjP2BEKK8LsBtVLHE3Q9Rt7oAvSr6DKyv2eHA@mail.gmail.com>
	<CAEUhfEcY9gFL=_fEgbuT++G0_epnA0t9x4=k6=cVQgF8s9qQBw@mail.gmail.com>
Message-ID: <CAEUhfEegQcUTj_4kvcMZ9-pa23wU5ppx3+OVkyV8ifjmAKE=Zg@mail.gmail.com>

Team

OK I now have managed to create a cluster XEN VM (using a OCFS2 shared
file-system and the notes from my previous correspondence).

It looks like the 'live migration/relocation' function is now managed by
'lib-virt' and not xend (there is no xend-config.sxp file for example).

Is there any notes on the configuration steps required for 'live
migration/relocation' now, the YAST2 'relocation server' module does not
seem to do anything and it's setting do not "stick".

Darren



On 2 June 2014 10:54, Darren Thompson <darrent at akurit.com.au> wrote:

> Team
>
> Found it, old dog needs to learn some new tricks ;-)
>
> "# virsh dumpxml *GuestID* > *guest.xml"*
>
> From:
> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html
> (Is there updated SLES12 documentation on this yet)
>
> Also, the original Xen OCF cluster resource cannot be used as it's hard
> coded to "xm" which is depreciated.
>
> There is a new 'VirtualDomain' OCF file which is used for clustering
> 'lib-virt' compatible VM's (which seems to support Xen, KVM etc).
>
> Darren
>
>
> On 31 May 2014 15:58, Darren Thompson <darrent at akurit.com.au> wrote:
>
>> Team
>>
>> I must be missing something obvious, but how do you get the VM config
>> files for HA
>>
>> In SLES11+ the VM create tool created the configuration file or you could
>> run "xm list {vmname} -l <= That;s from memory and my not be correct syntax.
>>
>> I have created a VM using the new virt-manager but it does not seem to
>> have created a config file.
>>
>> The xl list command does not seem to "find" the VM when it's running and
>> does not list it at all when stopped (I can only start it from virt-manager
>> itself).
>>
>> Any hints/tips appreciated as I'm sure that I'm missing something that
>> should be obvious.
>>
>> Darren
>>
>>
>> --
>>
>> Darren Thompson
>>
>> Professional Services Engineer / Consultant
>>
>>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>>
>> Level 3, 60 City Road
>>
>> Southgate, VIC 3006
>>
>> Mb: 0400 640 414
>>
>> Mail: darrent at akurit.com.au <steve at akurit.com.au>
>> Web: www.akurit.com.au
>>
>
>
>
> --
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au <steve at akurit.com.au>
> Web: www.akurit.com.au
>



-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140602/613a8201/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140602/613a8201/attachment.jpg>

From darrent at akurit.com.au  Sun Jun  1 21:41:40 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 2 Jun 2014 13:41:40 +1000
Subject: [sles-beta] Creating XEN VM files to use with HA cluster
In-Reply-To: <CAEUhfEegQcUTj_4kvcMZ9-pa23wU5ppx3+OVkyV8ifjmAKE=Zg@mail.gmail.com>
References: <CAEUhfEfzY9_KxHjP2BEKK8LsBtVLHE3Q9Rt7oAvSr6DKyv2eHA@mail.gmail.com>
	<CAEUhfEcY9gFL=_fEgbuT++G0_epnA0t9x4=k6=cVQgF8s9qQBw@mail.gmail.com>
	<CAEUhfEegQcUTj_4kvcMZ9-pa23wU5ppx3+OVkyV8ifjmAKE=Zg@mail.gmail.com>
Message-ID: <CAEUhfEd1FFUmyC=OqS6jTjUMwfm0MfirJ=Ocy+j2Xo0FiqWMug@mail.gmail.com>

Team

A good day (I have XEN live migration working in a SLES12 HA cluster).

Nothing tels it like a raw log output:

2014-06-02T13:29:22.065250+10:00 node2 crmd[1824]:   notice:
te_rsc_command: Initiating action 32: migrate_to
VM-sles12_migrate_to_0 on node2 (local)
2014-06-02T13:29:22.774946+10:00 node2
VirtualDomain(VM-sles12)[10318]: INFO: sles12: Starting live migration
to node1 (using remote hypervisor URI xen+tcp://node1/ ).
2014-06-02T13:29:47.058146+10:00 node2
VirtualDomain(VM-sles12)[10318]: INFO: sles12: live migration to node1
succeeded.
2014-06-02T13:29:47.071165+10:00 node2 lrmd[1821]:   notice:
operation_finished: VM-sles12_migrate_to_0:10318:stderr [ 2014-06-02
03:29:47.035+0000: 10360: info : libvirt version: 1.2.4 ]
2014-06-02T13:29:47.072310+10:00 node2 lrmd[1821]:   notice:
operation_finished: VM-sles12_migrate_to_0:10318:stderr [ 2014-06-02
03:29:47.035+0000: 10360: warning : virDomainMigrateVersion3Full:4993
: Guest sles12 probably left in &#x27;paused&#x27; state on source ]
2014-06-02T13:29:47.073332+10:00 node2 crmd[1824]:   notice:
process_lrm_event: LRM operation VM-sles12_migrate_to_0 (call=82,
rc=0, cib-update=267, confirmed=true) ok
2014-06-02T13:29:47.082142+10:00 node2 crmd[1824]:   notice:
te_rsc_command: Initiating action 33: migrate_from
VM-sles12_migrate_from_0 on node1
2014-06-02T13:29:47.975935+10:00 node2 crmd[1824]:   notice:
te_rsc_command: Initiating action 29: stop VM-sles12_stop_0 on node2
(local)
2014-06-02T13:29:48.679317+10:00 node2
VirtualDomain(VM-sles12)[10524]: INFO: Domain sles12 already stopped.
2014-06-02T13:29:48.694079+10:00 node2 crmd[1824]:   notice:
process_lrm_event: LRM operation VM-sles12_stop_0 (call=83, rc=0,
cib-update=268, confirmed=true) ok
2014-06-02T13:29:49.269012+10:00 node1
VirtualDomain(VM-sles12)[10813]: INFO: sles12: live migration from
node2 succeeded.
2014-06-02T13:29:49.281838+10:00 node1 crmd[1621]:   notice:
process_lrm_event: LRM operation VM-sles12_migrate_from_0 (call=77,
rc=0, cib-update=85, confirmed=true) ok
2014-06-02T13:31:05.180010+10:00 node2 crmd[1824]:   notice:
te_rsc_command: Initiating action 32: migrate_to
VM-sles12_migrate_to_0 on node1
2014-06-02T13:31:06.941294+10:00 node1
VirtualDomain(VM-sles12)[13060]: INFO: sles12: Starting live migration
to node2 (using remote hypervisor URI xen+tcp://node2/ ).
2014-06-02T13:31:25.198502+10:00 node2 crmd[1824]:   notice:
te_rsc_command: Initiating action 33: migrate_from
VM-sles12_migrate_from_0 on node2 (local)
2014-06-02T13:31:25.745563+10:00 node2
VirtualDomain(VM-sles12)[11467]: INFO: sles12: live migration from
node1 succeeded.
2014-06-02T13:31:25.760436+10:00 node2 crmd[1824]:   notice:
process_lrm_event: LRM operation VM-sles12_migrate_from_0 (call=84,
rc=0, cib-update=271, confirmed=true) ok
2014-06-02T13:31:25.771805+10:00 node2 crmd[1824]:   notice:
te_rsc_command: Initiating action 29: stop VM-sles12_stop_0 on node1
2014-06-02T13:31:26.552432+10:00 node1
VirtualDomain(VM-sles12)[13060]: INFO: sles12: live migration to node2
succeeded.
2014-06-02T13:31:26.570635+10:00 node1 crmd[1621]:   notice:
process_lrm_event: LRM operation VM-sles12_migrate_to_0 (call=80,
rc=0, cib-update=87, confirmed=true) ok
2014-06-02T13:31:27.415782+10:00 node1
VirtualDomain(VM-sles12)[13231]: INFO: Domain sles12 already stopped.
2014-06-02T13:31:27.429105+10:00 node1 crmd[1621]:   notice:
process_lrm_event: LRM operation VM-sles12_stop_0 (call=81, rc=0,
cib-update=88,

If anyone is intersted in doing the same, post a mail to these lists
and I will publish my working config exampes.

Darren






On 2 June 2014 12:08, Darren Thompson <darrent at akurit.com.au> wrote:

> Team
>
> OK I now have managed to create a cluster XEN VM (using a OCFS2 shared
> file-system and the notes from my previous correspondence).
>
> It looks like the 'live migration/relocation' function is now managed by
> 'lib-virt' and not xend (there is no xend-config.sxp file for example).
>
> Is there any notes on the configuration steps required for 'live
> migration/relocation' now, the YAST2 'relocation server' module does not
> seem to do anything and it's setting do not "stick".
>
> Darren
>
>
>
> On 2 June 2014 10:54, Darren Thompson <darrent at akurit.com.au> wrote:
>
>> Team
>>
>> Found it, old dog needs to learn some new tricks ;-)
>>
>> "# virsh dumpxml *GuestID* > *guest.xml"*
>>
>> From:
>> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html
>> (Is there updated SLES12 documentation on this yet)
>>
>> Also, the original Xen OCF cluster resource cannot be used as it's hard
>> coded to "xm" which is depreciated.
>>
>> There is a new 'VirtualDomain' OCF file which is used for clustering
>> 'lib-virt' compatible VM's (which seems to support Xen, KVM etc).
>>
>> Darren
>>
>>
>> On 31 May 2014 15:58, Darren Thompson <darrent at akurit.com.au> wrote:
>>
>>> Team
>>>
>>> I must be missing something obvious, but how do you get the VM config
>>> files for HA
>>>
>>> In SLES11+ the VM create tool created the configuration file or you
>>> could run "xm list {vmname} -l <= That;s from memory and my not be correct
>>> syntax.
>>>
>>> I have created a VM using the new virt-manager but it does not seem to
>>> have created a config file.
>>>
>>> The xl list command does not seem to "find" the VM when it's running and
>>> does not list it at all when stopped (I can only start it from virt-manager
>>> itself).
>>>
>>> Any hints/tips appreciated as I'm sure that I'm missing something that
>>> should be obvious.
>>>
>>> Darren
>>>
>>>
>>> --
>>>
>>> Darren Thompson
>>>
>>> Professional Services Engineer / Consultant
>>>
>>>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>>>
>>> Level 3, 60 City Road
>>>
>>> Southgate, VIC 3006
>>>
>>> Mb: 0400 640 414
>>>
>>> Mail: darrent at akurit.com.au <steve at akurit.com.au>
>>> Web: www.akurit.com.au
>>>
>>
>>
>>
>> --
>>
>> Darren Thompson
>>
>> Professional Services Engineer / Consultant
>>
>>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>>
>> Level 3, 60 City Road
>>
>> Southgate, VIC 3006
>>
>> Mb: 0400 640 414
>>
>> Mail: darrent at akurit.com.au <steve at akurit.com.au>
>> Web: www.akurit.com.au
>>
>
>
>
> --
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
>  *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au <steve at akurit.com.au>
> Web: www.akurit.com.au
>



-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140602/6c1b4bff/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140602/6c1b4bff/attachment.jpg>