From darrent at akurit.com.au  Mon Jun 23 00:07:48 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 23 Jun 2014 16:07:48 +1000
Subject: [sles-beta] AutoYast Issues SLES12 B9 - with steps and
	screenshots/sample files
Message-ID: <CAEUhfEd=Cdak_smqsphCfbnK7f=3ZGn3TiFVXt6EjrZk0HpQJQ@mail.gmail.com>

Team

I'm having some issues with the SLES12 B9 autoyast workflows:.

I'm doing the following:
1. Create "install server" with all media (Sles12, HA and each of the
modules).
2. Boot from "mini" disk and pass "install=http://{install server}/{repo
name}/CD1"
3. Do "accept all defaults" install.
4. Log into server and run yast/autoinstall module.
5. Open /root/autoinst.xml file (example attached -
B9-autoinst.xml
<https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753c94b3a6fd&attid=0.5&disp=safe&realattid=f_hwrdqpot5&zw>
 ) and get bootloader error (screenshot attached -
Autoyast-error-B9-dogfooding.png
<https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c7513c1f8c36e&attid=0.1&disp=safe&realattid=f_hwrdkw6a0&zw>
).
6. customise auto-yast file and save (example attached -
test01-autoyast-B9.xm
<https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c75482fe3c9b4&attid=0.6&disp=safe&realattid=f_hwrdrq0x6&zw>
  ) and copy resulting autoyast file to "install server"
7.  Boot from "mini" disk and pass "install=http://{install server}/{repo
path}/CD1 autoyast=http://{install server}/{autoyast
path}/{autoyastfile.xml}
8. Install runs but throws bootloader error (screenshot attached -
Autoyast-error-B9.png
<https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c750cb4d85cad&attid=0.2&disp=safe&realattid=f_hwrdmi3a1&zw>
 ), I select "skip/continue"
9. Install appears to complete and goes into "yast - first boot" screen and
gets stuck (screenshot attached -
Autoyast-error-B9-stuck-first-boot.png
<https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c752492fee5b6&attid=0.3&disp=safe&realattid=f_hwrdolsf3&zw>
), I reboot server.
10. Server boots to generic (un-themed) GUI login screen (screenshot
attached -
Autoyast-error-B9-unconfigured-login_screen.png
<https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753016916dc2&attid=0.4&disp=safe&realattid=f_hwrdpm214&zw>
).

Is any of this new issues???? which if any of these are worth raising new
SR's for?

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/20140623/4493dbef/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/20140623/4493dbef/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Autoyast-error-B9-dogfooding.png
Type: image/png
Size: 63687 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/4493dbef/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Autoyast-error-B9.png
Type: image/png
Size: 39509 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/4493dbef/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Autoyast-error-B9-stuck-first-boot.png
Type: image/png
Size: 6559 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/4493dbef/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Autoyast-error-B9-unconfigured-login_screen.png
Type: image/png
Size: 12026 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/4493dbef/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: B9-autoinst.xml
Type: text/xml
Size: 25436 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/4493dbef/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test01-autoyast-B9.xml
Type: text/xml
Size: 92492 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/4493dbef/attachment-0001.xml>

From darrent at akurit.com.au  Mon Jun 23 00:14:39 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 23 Jun 2014 16:14:39 +1000
Subject: [sles-beta] AutoYast Issues SLES12 B9 - with steps and
	screenshots/sample files
In-Reply-To: <CAEUhfEd=Cdak_smqsphCfbnK7f=3ZGn3TiFVXt6EjrZk0HpQJQ@mail.gmail.com>
References: <CAEUhfEd=Cdak_smqsphCfbnK7f=3ZGn3TiFVXt6EjrZk0HpQJQ@mail.gmail.com>
Message-ID: <CAEUhfEcF+wodx=P9VKG3OhKSaU_orT+JL1_PkpDKDRBpjJHKXg@mail.gmail.com>

Team

OK some clarifications...

The "follow the defaults" server build produces (what appears to be) a
fully installed and working server, with the themed login and customised
Gnome desktop. It's only the subsequent "autoyast" workflow that has issues.

The password for the root user in the attached autoyast files is "novell" -
just in case you want to run them...

Darren


On 23 June 2014 16:07, Darren Thompson <darrent at akurit.com.au> wrote:

> Team
>
> I'm having some issues with the SLES12 B9 autoyast workflows:.
>
> I'm doing the following:
> 1. Create "install server" with all media (Sles12, HA and each of the
> modules).
> 2. Boot from "mini" disk and pass "install=http://{install server}/{repo
> name}/CD1"
> 3. Do "accept all defaults" install.
> 4. Log into server and run yast/autoinstall module.
> 5. Open /root/autoinst.xml file (example attached -
> B9-autoinst.xml
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753c94b3a6fd&attid=0.5&disp=safe&realattid=f_hwrdqpot5&zw>
>  ) and get bootloader error (screenshot attached -
> Autoyast-error-B9-dogfooding.png
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c7513c1f8c36e&attid=0.1&disp=safe&realattid=f_hwrdkw6a0&zw>
> ).
> 6. customise auto-yast file and save (example attached -
> test01-autoyast-B9.xm
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c75482fe3c9b4&attid=0.6&disp=safe&realattid=f_hwrdrq0x6&zw>
>   ) and copy resulting autoyast file to "install server"
> 7.  Boot from "mini" disk and pass "install=http://{install server}/{repo
> path}/CD1 autoyast=http://{install server}/{autoyast
> path}/{autoyastfile.xml}
> 8. Install runs but throws bootloader error (screenshot attached -
> Autoyast-error-B9.png
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c750cb4d85cad&attid=0.2&disp=safe&realattid=f_hwrdmi3a1&zw>
>  ), I select "skip/continue"
> 9. Install appears to complete and goes into "yast - first boot" screen
> and gets stuck (screenshot attached -
> Autoyast-error-B9-stuck-first-boot.png
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c752492fee5b6&attid=0.3&disp=safe&realattid=f_hwrdolsf3&zw>
> ), I reboot server.
> 10. Server boots to generic (un-themed) GUI login screen (screenshot
> attached -
> Autoyast-error-B9-unconfigured-login_screen.png
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753016916dc2&attid=0.4&disp=safe&realattid=f_hwrdpm214&zw>
> ).
>
> Is any of this new issues???? which if any of these are worth raising new
> SR's for?
>
> 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/20140623/3ab53998/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/20140623/3ab53998/attachment.jpg>

From jreidinger at suse.cz  Mon Jun 23 00:33:07 2014
From: jreidinger at suse.cz (Josef Reidinger)
Date: Mon, 23 Jun 2014 08:33:07 +0200
Subject: [sles-beta] AutoYast Issues SLES12 B9 - with steps and
 screenshots/sample files
In-Reply-To: <CAEUhfEd=Cdak_smqsphCfbnK7f=3ZGn3TiFVXt6EjrZk0HpQJQ@mail.gmail.com>
References: <CAEUhfEd=Cdak_smqsphCfbnK7f=3ZGn3TiFVXt6EjrZk0HpQJQ@mail.gmail.com>
Message-ID: <20140623083307.20876848@dhcp150.suse.cz>

On Mon, 23 Jun 2014 16:07:48 +1000
"Darren Thompson" <darrent at akurit.com.au> wrote:

> Team
> 
> I'm having some issues with the SLES12 B9 autoyast workflows:.
> 
> I'm doing the following:
> 1. Create "install server" with all media (Sles12, HA and each of the
> modules).
> 2. Boot from "mini" disk and pass "install=http://{install
> server}/{repo name}/CD1"
> 3. Do "accept all defaults" install.
> 4. Log into server and run yast/autoinstall module.
> 5. Open /root/autoinst.xml file (example attached -
> B9-autoinst.xml
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753c94b3a6fd&attid=0.5&disp=safe&realattid=f_hwrdqpot5&zw>
>  ) and get bootloader error (screenshot attached -
> Autoyast-error-B9-dogfooding.png
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c7513c1f8c36e&attid=0.1&disp=safe&realattid=f_hwrdkw6a0&zw>
> ).
> 6. customise auto-yast file and save (example attached -
> test01-autoyast-B9.xm
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c75482fe3c9b4&attid=0.6&disp=safe&realattid=f_hwrdrq0x6&zw>
>   ) and copy resulting autoyast file to "install server"
> 7.  Boot from "mini" disk and pass "install=http://{install
> server}/{repo path}/CD1 autoyast=http://{install server}/{autoyast
> path}/{autoyastfile.xml}
> 8. Install runs but throws bootloader error (screenshot attached -
> Autoyast-error-B9.png
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c750cb4d85cad&attid=0.2&disp=safe&realattid=f_hwrdmi3a1&zw>
>  ), I select "skip/continue"
> 9. Install appears to complete and goes into "yast - first boot"
> screen and gets stuck (screenshot attached -
> Autoyast-error-B9-stuck-first-boot.png
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c752492fee5b6&attid=0.3&disp=safe&realattid=f_hwrdolsf3&zw>
> ), I reboot server.
> 10. Server boots to generic (un-themed) GUI login screen (screenshot
> attached -
> Autoyast-error-B9-unconfigured-login_screen.png
> <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753016916dc2&attid=0.4&disp=safe&realattid=f_hwrdpm214&zw>
> ).
> 
> Is any of this new issues???? which if any of these are worth raising
> new SR's for?
> 

Hi,
I do not see this issue yet, so please report it (at least bootloader
part). It looks like it should be quite easy to fix it.

Josef

> Regards
> Darren
> 
> 
> 


From darrent at akurit.com.au  Mon Jun 23 00:45:49 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 23 Jun 2014 16:45:49 +1000
Subject: [sles-beta] AutoYast Issues SLES12 B9 - with steps and
 screenshots/sample files
In-Reply-To: <20140623083307.20876848@dhcp150.suse.cz>
References: <CAEUhfEd=Cdak_smqsphCfbnK7f=3ZGn3TiFVXt6EjrZk0HpQJQ@mail.gmail.com>
	<20140623083307.20876848@dhcp150.suse.cz>
Message-ID: <CAEUhfEfQOe0VbA_yuZjKrb_aLZyaiGBC=66kr_Jn0mCxEaw6vQ@mail.gmail.com>

OK

Service Request: 10898167161   *Description: Bootloader section of
autoinst.xml causes errors in autoyast modules and during autoyast install*


On 23 June 2014 16:33, Josef Reidinger <jreidinger at suse.cz> wrote:

> On Mon, 23 Jun 2014 16:07:48 +1000
> "Darren Thompson" <darrent at akurit.com.au> wrote:
>
> > Team
> >
> > I'm having some issues with the SLES12 B9 autoyast workflows:.
> >
> > I'm doing the following:
> > 1. Create "install server" with all media (Sles12, HA and each of the
> > modules).
> > 2. Boot from "mini" disk and pass "install=http://{install
> > server}/{repo name}/CD1"
> > 3. Do "accept all defaults" install.
> > 4. Log into server and run yast/autoinstall module.
> > 5. Open /root/autoinst.xml file (example attached -
> > B9-autoinst.xml
> > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753c94b3a6fd&attid=0.5&disp=safe&realattid=f_hwrdqpot5&zw
> >
> >  ) and get bootloader error (screenshot attached -
> > Autoyast-error-B9-dogfooding.png
> > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c7513c1f8c36e&attid=0.1&disp=safe&realattid=f_hwrdkw6a0&zw
> >
> > ).
> > 6. customise auto-yast file and save (example attached -
> > test01-autoyast-B9.xm
> > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c75482fe3c9b4&attid=0.6&disp=safe&realattid=f_hwrdrq0x6&zw
> >
> >   ) and copy resulting autoyast file to "install server"
> > 7.  Boot from "mini" disk and pass "install=http://{install
> > server}/{repo path}/CD1 autoyast=http://{install server}/{autoyast
> > path}/{autoyastfile.xml}
> > 8. Install runs but throws bootloader error (screenshot attached -
> > Autoyast-error-B9.png
> > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c750cb4d85cad&attid=0.2&disp=safe&realattid=f_hwrdmi3a1&zw
> >
> >  ), I select "skip/continue"
> > 9. Install appears to complete and goes into "yast - first boot"
> > screen and gets stuck (screenshot attached -
> > Autoyast-error-B9-stuck-first-boot.png
> > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c752492fee5b6&attid=0.3&disp=safe&realattid=f_hwrdolsf3&zw
> >
> > ), I reboot server.
> > 10. Server boots to generic (un-themed) GUI login screen (screenshot
> > attached -
> > Autoyast-error-B9-unconfigured-login_screen.png
> > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753016916dc2&attid=0.4&disp=safe&realattid=f_hwrdpm214&zw
> >
> > ).
> >
> > Is any of this new issues???? which if any of these are worth raising
> > new SR's for?
> >
>
> Hi,
> I do not see this issue yet, so please report it (at least bootloader
> part). It looks like it should be quite easy to fix it.
>
> Josef
>
> > Regards
> > Darren
> >
> >
> >
>
> _______________________________________________
> 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/20140623/af709945/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/20140623/af709945/attachment.jpg>

From jreidinger at suse.cz  Mon Jun 23 00:45:54 2014
From: jreidinger at suse.cz (Josef Reidinger)
Date: Mon, 23 Jun 2014 08:45:54 +0200
Subject: [sles-beta] AutoYast Issues SLES12 B9 - with steps and
 screenshots/sample files
In-Reply-To: <20140623083307.20876848@dhcp150.suse.cz>
References: <CAEUhfEd=Cdak_smqsphCfbnK7f=3ZGn3TiFVXt6EjrZk0HpQJQ@mail.gmail.com>
	<20140623083307.20876848@dhcp150.suse.cz>
Message-ID: <20140623084554.12662408@dhcp150.suse.cz>

On Mon, 23 Jun 2014 08:33:07 +0200
"Josef Reidinger" <jreidinger at suse.cz> wrote:

> On Mon, 23 Jun 2014 16:07:48 +1000
> "Darren Thompson" <darrent at akurit.com.au> wrote:
> 
> > Team
> > 
> > I'm having some issues with the SLES12 B9 autoyast workflows:.
> > 
> > I'm doing the following:
> > 1. Create "install server" with all media (Sles12, HA and each of
> > the modules).
> > 2. Boot from "mini" disk and pass "install=http://{install
> > server}/{repo name}/CD1"
> > 3. Do "accept all defaults" install.
> > 4. Log into server and run yast/autoinstall module.
> > 5. Open /root/autoinst.xml file (example attached -
> > B9-autoinst.xml
> > <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753c94b3a6fd&attid=0.5&disp=safe&realattid=f_hwrdqpot5&zw>
> >  ) and get bootloader error (screenshot attached -
> > Autoyast-error-B9-dogfooding.png
> > <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c7513c1f8c36e&attid=0.1&disp=safe&realattid=f_hwrdkw6a0&zw>
> > ).
> > 6. customise auto-yast file and save (example attached -
> > test01-autoyast-B9.xm
> > <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c75482fe3c9b4&attid=0.6&disp=safe&realattid=f_hwrdrq0x6&zw>
> >   ) and copy resulting autoyast file to "install server"
> > 7.  Boot from "mini" disk and pass "install=http://{install
> > server}/{repo path}/CD1 autoyast=http://{install server}/{autoyast
> > path}/{autoyastfile.xml}
> > 8. Install runs but throws bootloader error (screenshot attached -
> > Autoyast-error-B9.png
> > <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c750cb4d85cad&attid=0.2&disp=safe&realattid=f_hwrdmi3a1&zw>
> >  ), I select "skip/continue"
> > 9. Install appears to complete and goes into "yast - first boot"
> > screen and gets stuck (screenshot attached -
> > Autoyast-error-B9-stuck-first-boot.png
> > <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c752492fee5b6&attid=0.3&disp=safe&realattid=f_hwrdolsf3&zw>
> > ), I reboot server.
> > 10. Server boots to generic (un-themed) GUI login screen (screenshot
> > attached -
> > Autoyast-error-B9-unconfigured-login_screen.png
> > <https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753016916dc2&attid=0.4&disp=safe&realattid=f_hwrdpm214&zw>
> > ).
> > 
> > Is any of this new issues???? which if any of these are worth
> > raising new SR's for?
> > 
> 
> Hi,
> I do not see this issue yet, so please report it (at least bootloader
> part). It looks like it should be quite easy to fix it.
> 
> Josef
> 

I check source codes and autoyast issue is already fixed in code. So it
will be in next release. If you are interested in hot patching, then
this patch is fix:
https://github.com/yast/yast-bootloader/commit/bb06b11e54488d515837b852fb7cc65f9e257250

Josef


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


From darrent at akurit.com.au  Mon Jun 23 00:51:51 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 23 Jun 2014 16:51:51 +1000
Subject: [sles-beta] AutoYast Issues SLES12 B9 - with steps and
 screenshots/sample files
In-Reply-To: <20140623084554.12662408@dhcp150.suse.cz>
References: <CAEUhfEd=Cdak_smqsphCfbnK7f=3ZGn3TiFVXt6EjrZk0HpQJQ@mail.gmail.com>
	<20140623083307.20876848@dhcp150.suse.cz>
	<20140623084554.12662408@dhcp150.suse.cz>
Message-ID: <CAEUhfEfS3Naehv+sVgyrX24i7DgovniVusmW_0jU59macLOPCQ@mail.gmail.com>

Ok

I can wait for next beta run to test (B10 or RC1?)

Do you want me to get the new SR closed again now?

Darren


On 23 June 2014 16:45, Josef Reidinger <jreidinger at suse.cz> wrote:

> On Mon, 23 Jun 2014 08:33:07 +0200
> "Josef Reidinger" <jreidinger at suse.cz> wrote:
>
> > On Mon, 23 Jun 2014 16:07:48 +1000
> > "Darren Thompson" <darrent at akurit.com.au> wrote:
> >
> > > Team
> > >
> > > I'm having some issues with the SLES12 B9 autoyast workflows:.
> > >
> > > I'm doing the following:
> > > 1. Create "install server" with all media (Sles12, HA and each of
> > > the modules).
> > > 2. Boot from "mini" disk and pass "install=http://{install
> > > server}/{repo name}/CD1"
> > > 3. Do "accept all defaults" install.
> > > 4. Log into server and run yast/autoinstall module.
> > > 5. Open /root/autoinst.xml file (example attached -
> > > B9-autoinst.xml
> > > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753c94b3a6fd&attid=0.5&disp=safe&realattid=f_hwrdqpot5&zw
> >
> > >  ) and get bootloader error (screenshot attached -
> > > Autoyast-error-B9-dogfooding.png
> > > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c7513c1f8c36e&attid=0.1&disp=safe&realattid=f_hwrdkw6a0&zw
> >
> > > ).
> > > 6. customise auto-yast file and save (example attached -
> > > test01-autoyast-B9.xm
> > > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c75482fe3c9b4&attid=0.6&disp=safe&realattid=f_hwrdrq0x6&zw
> >
> > >   ) and copy resulting autoyast file to "install server"
> > > 7.  Boot from "mini" disk and pass "install=http://{install
> > > server}/{repo path}/CD1 autoyast=http://{install server}/{autoyast
> > > path}/{autoyastfile.xml}
> > > 8. Install runs but throws bootloader error (screenshot attached -
> > > Autoyast-error-B9.png
> > > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c750cb4d85cad&attid=0.2&disp=safe&realattid=f_hwrdmi3a1&zw
> >
> > >  ), I select "skip/continue"
> > > 9. Install appears to complete and goes into "yast - first boot"
> > > screen and gets stuck (screenshot attached -
> > > Autoyast-error-B9-stuck-first-boot.png
> > > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c752492fee5b6&attid=0.3&disp=safe&realattid=f_hwrdolsf3&zw
> >
> > > ), I reboot server.
> > > 10. Server boots to generic (un-themed) GUI login screen (screenshot
> > > attached -
> > > Autoyast-error-B9-unconfigured-login_screen.png
> > > <
> https://mail.google.com/mail/u/0/?ui=2&ik=0d2db9dc4c&view=att&th=146c753016916dc2&attid=0.4&disp=safe&realattid=f_hwrdpm214&zw
> >
> > > ).
> > >
> > > Is any of this new issues???? which if any of these are worth
> > > raising new SR's for?
> > >
> >
> > Hi,
> > I do not see this issue yet, so please report it (at least bootloader
> > part). It looks like it should be quite easy to fix it.
> >
> > Josef
> >
>
> I check source codes and autoyast issue is already fixed in code. So it
> will be in next release. If you are interested in hot patching, then
> this patch is fix:
>
> https://github.com/yast/yast-bootloader/commit/bb06b11e54488d515837b852fb7cc65f9e257250
>
> Josef
>
>
> > > Regards
> > > Darren
> > >
> > >
> > >
> >
> > _______________________________________________
> > 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/20140623/30174684/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/20140623/30174684/attachment.jpg>

From fcrozat at suse.com  Mon Jun 23 01:28:25 2014
From: fcrozat at suse.com (Frederic Crozat)
Date: Mon, 23 Jun 2014 09:28:25 +0200
Subject: [sles-beta] [ANNOUNCE] SLES 12 Beta9 is available
In-Reply-To: <e8d353f8-033f-4e27-b274-c82318edc278@email.android.com>
References: <1403278621.2047.66.camel@par-r81vxc7.par.novell.com>
	<2286456.CVRbCipqlm@gjn.priv.at>
	<e8d353f8-033f-4e27-b274-c82318edc278@email.android.com>
Message-ID: <1403508505.20822.0.camel@par-r81vxc7.par.novell.com>

Le vendredi 20 juin 2014 ? 23:31 +0100, Simon Flood a ?crit :
> On 20 June 2014 22:20:35 BST, "G?nther J. Niederwimmer" wrote:
> 
> >I have always a 404 for the download, all other is working
> 
> Apart from the SDK ISO I'm getting a 404 for all other x86_64 DVD1 ISOs. 

They should be working fine now (as always, propagation across CDN is
taking time :(


-- 
Frederic Crozat
Project Manager Enterprise Desktop
SUSE


From fcrozat at suse.com  Mon Jun 23 01:42:33 2014
From: fcrozat at suse.com (Frederic Crozat)
Date: Mon, 23 Jun 2014 09:42:33 +0200
Subject: [sles-beta] Suggestion to speed up installs/Upgrades/patching
 for "future" SLE
In-Reply-To: <20140623003636.GD9332@suse.com>
References: <CAEUhfEeOVPm2aZoV1YicDwmxou948Ta=QP=gv_1Xi7GSmq6jaw@mail.gmail.com>
	<20140623003636.GD9332@suse.com>
Message-ID: <1403509353.20822.8.camel@par-r81vxc7.par.novell.com>

Le lundi 23 juin 2014 ? 02:36 +0200, Matthias G. Eckermann a ?crit :
> Hello Darren,
> 
> don't you think that we already did consider this?
> 
> The problem with this approach is that it leaves the
> system in an undefinied / inconsistent state for a few
> minutes, and if it crashes then, you have a really bad
> experience.
> 
> Thus we have decided to follow the save way which indeed
> needs a bit more time, but we hope that people appreciate
> consistency and stability over 2-3 minutes of time.

Well, it happens our development team implemented a "sane" way to handle
dracut updates during SLE12 development (Darren, I don't know when you
noticed those dracut "issues), preventing too many dracut initrd
regeneration but ensuring it is called once all packages are updated
(using an RPM feature called "transactions", which was not available
during SLE12). Since it is handled at RPM level, it is safer than trying
to do it at end of installation (ie ? la SuSEConfig like SLE11, which
was not run if you were using only RPM and not zypper, for instance).

However, maybe some packages were not migrated to the new "transaction"
way and are still regenerating initrd more often than needed.

-- 
Frederic Crozat
Project Manager Enterprise Desktop
SUSE


From darrent at akurit.com.au  Mon Jun 23 02:25:52 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Mon, 23 Jun 2014 18:25:52 +1000
Subject: [sles-beta] Suggestion to speed up installs/Upgrades/patching
 for "future" SLE
In-Reply-To: <1403509353.20822.8.camel@par-r81vxc7.par.novell.com>
References: <CAEUhfEeOVPm2aZoV1YicDwmxou948Ta=QP=gv_1Xi7GSmq6jaw@mail.gmail.com>
	<20140623003636.GD9332@suse.com>
	<1403509353.20822.8.camel@par-r81vxc7.par.novell.com>
Message-ID: <CAEUhfEdLEkDcdOyeDcvXQDf8fAP+RRoCKzmuZh38dJUbdwJT1w@mail.gmail.com>

Frederic

I'm seeing the "multiple dracut initrd regenerations" during SLES12 beta9
so it's still very much evident in SLES12.

According to Matthias (you replied to his email), the issue was already
considered and the spedup was rejected in favour of maintaing package
stability (in the event of a crash during upgrades).

Using RPM "transaction" does seem like a good option, perhaps some more
discussion between the 'coders' may be warranted.

Darren



On 23 June 2014 17:42, Frederic Crozat <fcrozat at suse.com> wrote:

> Le lundi 23 juin 2014 ? 02:36 +0200, Matthias G. Eckermann a ?crit :
> > Hello Darren,
> >
> > don't you think that we already did consider this?
> >
> > The problem with this approach is that it leaves the
> > system in an undefinied / inconsistent state for a few
> > minutes, and if it crashes then, you have a really bad
> > experience.
> >
> > Thus we have decided to follow the save way which indeed
> > needs a bit more time, but we hope that people appreciate
> > consistency and stability over 2-3 minutes of time.
>
> Well, it happens our development team implemented a "sane" way to handle
> dracut updates during SLE12 development (Darren, I don't know when you
> noticed those dracut "issues), preventing too many dracut initrd
> regeneration but ensuring it is called once all packages are updated
> (using an RPM feature called "transactions", which was not available
> during SLE12). Since it is handled at RPM level, it is safer than trying
> to do it at end of installation (ie ? la SuSEConfig like SLE11, which
> was not run if you were using only RPM and not zypper, for instance).
>
> However, maybe some packages were not migrated to the new "transaction"
> way and are still regenerating initrd more often than needed.
>
> --
> Frederic Crozat
> Project Manager Enterprise Desktop
> SUSE
>
> _______________________________________________
> 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/20140623/982c7a51/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/20140623/982c7a51/attachment.jpg>

From jreidinger at suse.cz  Mon Jun 23 02:34:13 2014
From: jreidinger at suse.cz (Josef Reidinger)
Date: Mon, 23 Jun 2014 10:34:13 +0200
Subject: [sles-beta] Suggestion to speed up installs/Upgrades/patching
 for "future" SLE
In-Reply-To: <CAEUhfEdLEkDcdOyeDcvXQDf8fAP+RRoCKzmuZh38dJUbdwJT1w@mail.gmail.com>
References: <CAEUhfEeOVPm2aZoV1YicDwmxou948Ta=QP=gv_1Xi7GSmq6jaw@mail.gmail.com>
	<20140623003636.GD9332@suse.com>
	<1403509353.20822.8.camel@par-r81vxc7.par.novell.com>
	<CAEUhfEdLEkDcdOyeDcvXQDf8fAP+RRoCKzmuZh38dJUbdwJT1w@mail.gmail.com>
Message-ID: <20140623103413.0a073d68@dhcp150.suse.cz>

On Mon, 23 Jun 2014 18:25:52 +1000
"Darren Thompson" <darrent at akurit.com.au> wrote:

> Frederic
> 
> I'm seeing the "multiple dracut initrd regenerations" during SLES12
> beta9 so it's still very much evident in SLES12.
> 
> According to Matthias (you replied to his email), the issue was
> already considered and the spedup was rejected in favour of maintaing
> package stability (in the event of a crash during upgrades).
> 
> Using RPM "transaction" does seem like a good option, perhaps some
> more discussion between the 'coders' may be warranted.
> 
> Darren
> 
> 

Well,
let me explain how it works in SLE11. There was a special ENV variable,
that all rpm respect in its post install script. This variable said if
it is run in YaST. If such variable is set, then all such stuff is
skipped and YaST2 itself generate all needed stuff.
It sounds pretty elegant, but there is some nasty drawbacks.

1) YaST runs all post install hooks even if such packages are not
installed or if it is not updated, so YaST was slow for simple install
of single package

2) YaST need to be in sync what packages do, this means YaST have to
have same code as is in rpm post install. It is duplicite and we have
trouble to keep it in sync and what is worse it is quite hard to detect
if such situation happen resulting in nasty bugs. This is main reason
why we drop it.

For me RPM transaction is much nicer solution if it work reliable even
if upgrade failed in middle of install ( I do not know how this exactly
work ).

Josef

From gjn at gjn.priv.at  Mon Jun 23 03:00:55 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Mon, 23 Jun 2014 11:00:55 +0200
Subject: [sles-beta] hostname Beta 9
Message-ID: <20053501.aqX7UJZtx0@gjn.priv.at>

Hello,

Is this a "normal" function in SUSE

The hostname is only set with a "alias"

/etc/host

xxx.xxx.xxx.xxx  aaa.aaaaa.aa  aaa
xxx.xxx.xxx.xxx  aaa.bbbbb.bb  aaa
xxx.xxx.xxx.xxx  aaa.cccccc.cc  aaa

hostname -f
with this setting I have aaa.aaaa.aa as hostname

xxx.xxx.xxx.xxx  aaa.aaaaa.aa 
xxx.xxx.xxx.xxx  aaa.bbbbb.bb  aaa
xxx.xxx.xxx.xxx  aaa.cccccc.cc  aaa

hostname -f
With this setting I have aaa.bbbbb as hostname

xxx.xxx.xxx.xxx  aaa.aaaaa.aa  
xxx.xxx.xxx.xxx  aaa.bbbbb.bb  
xxx.xxx.xxx.xxx  aaa.cccccc.cc  aaa

hostname -f
and with this aaa.cccccc

The hostname in YaST2 can be aaa.dddd.dd

Thanks for a answer,
-- 
mit freundlichen Gr??en / best Regards,

  G?nther J. Niederwimmer

From S.M.Flood at ucs.cam.ac.uk  Mon Jun 23 03:14:02 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Mon, 23 Jun 2014 10:14:02 +0100
Subject: [sles-beta] [ANNOUNCE] SLES 12 Beta9 is available
In-Reply-To: <1403508505.20822.0.camel@par-r81vxc7.par.novell.com>
References: <1403278621.2047.66.camel@par-r81vxc7.par.novell.com>	<2286456.CVRbCipqlm@gjn.priv.at>	<e8d353f8-033f-4e27-b274-c82318edc278@email.android.com>
	<1403508505.20822.0.camel@par-r81vxc7.par.novell.com>
Message-ID: <53A7EFDA.2070403@ucs.cam.ac.uk>

On 23/06/2014 08:28, Frederic Crozat wrote:

> They should be working fine now (as always, propagation across CDN is
> taking time :(

Yes they worked on Saturday (and I meant to report back).

Note that what haven't appeared for the SLES12 download are the SHA1SUMS 
and SHA256SUMS files. Since they're available for the HA download I'm 
guessing that's a mistake but certainly not major as MD5 check sums are 
listed (for me the MD5SUMS files still has Beta8 downloads).

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

Novell/SUSE/NetIQ Knowledge Partner

From mge at suse.com  Mon Jun 23 04:41:34 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Mon, 23 Jun 2014 12:41:34 +0200
Subject: [sles-beta] Suggestion to speed up installs/Upgrades/patching
 for "future" SLE
In-Reply-To: <CAEUhfEfHrYphUSRFc5DyX2LD6JTsb2KN0xzO1VU9+f7KVNpGHg@mail.gmail.com>
References: <CAEUhfEeOVPm2aZoV1YicDwmxou948Ta=QP=gv_1Xi7GSmq6jaw@mail.gmail.com>
	<20140623003636.GD9332@suse.com>
	<CAEUhfEfHrYphUSRFc5DyX2LD6JTsb2KN0xzO1VU9+f7KVNpGHg@mail.gmail.com>
Message-ID: <20140623104134.GB26028@suse.com>

Hello Darren and all,

On 2014-06-23 T 14:44 +1000 Darren Thompson wrote:
 
> In any case, as a beta tester I understood my role was to
> "make observations" and I still feel that this was a
> reasonable suggestion.
 
yes, no doubt: the observation is correct (guess what: I
complained about the same in the SLE 11 SP3 context), and
your suggestion (fresh install != upgrade) is also
reasonable. For now, we'll keep it this way, but for the
Service Packs we will re-evaluate, how we can improve here.

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 michael.baensch at dfs.de  Mon Jun 23 04:49:00 2014
From: michael.baensch at dfs.de (Michael Baensch)
Date: Mon, 23 Jun 2014 10:49:00 +0000
Subject: [sles-beta] AutoYast ask list
Message-ID: <0d15553b10ff4dbfbd26df80f0515912@LGNMSXB02.prod.bk.dfs>

Hello,

we have this AutoYast bug opend in April (Bug  https://bugzilla.novell.com/show_bug.cgi?id=875945).
Maybe one of the SUSE people can say, why there is no work/feedback on it ?

Thanks
Michael




DFS Deutsche Flugsicherung GmbH
Am DFS-Campus
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Michael Odenwald
Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/1a7e1794/attachment.htm>

From schubi at suse.de  Mon Jun 23 05:05:27 2014
From: schubi at suse.de (Stefan Schubert)
Date: Mon, 23 Jun 2014 13:05:27 +0200
Subject: [sles-beta] AutoYast ask list
In-Reply-To: <0d15553b10ff4dbfbd26df80f0515912@LGNMSXB02.prod.bk.dfs>
References: <0d15553b10ff4dbfbd26df80f0515912@LGNMSXB02.prod.bk.dfs>
Message-ID: <53A809F7.7060904@suse.de>

Hallo Michael,
sorry for the late feedback. I will have a look within the next few days 
(2-3).
It is on the top of the list. :-)

Greetings
Stefan

Am 23.06.2014 12:49, schrieb Michael Baensch:
>
> Hello,
>
> we have this AutoYast bug opend in April (Bug 
> https://bugzilla.novell.com/show_bug.cgi?id=875945).
>
> Maybe one of the SUSE people can say, why there is no work/feedback on 
> it ?
>
> Thanks
>
> Michael
>
>
> DFS Deutsche Flugsicherung GmbH
> Am DFS-Campus
> D - 63225 Langen
>
> Tel.: +49-(0)6103-707-0
>
> Sitz der Gesellschaft: Langen/Hessen
> Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
> Vorsitzender des Aufsichtsrates: Michael Odenwald
> Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert 
> Schickling, Dr. Michael Hann
>
> Internet: http://www.dfs.de
> Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc
>
>
>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta


-- 
*******************************************************************************
Stefan Schubert
e-mail: schubi at suse.de
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany


From aschnell at suse.de  Mon Jun 23 03:54:25 2014
From: aschnell at suse.de (Arvin Schnell)
Date: Mon, 23 Jun 2014 11:54:25 +0200
Subject: [sles-beta] autoyast, sshd and snapper
In-Reply-To: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr>
References: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr>
Message-ID: <20140623095425.GA18799@suse.de>

On Mon, Jun 16, 2014 at 10:01:27AM +0000, FOLTIER Julien wrote:
> Hi,
> 
> When I'm trying to install SLES12 beta 8 with an autoyast file, I don't have a snapper configuration after this installation and sshd is not enable and not started.
> How can I implement those 2 parameters in the autoyast file ?

snapper can be enabled now, see
https://bugzilla.novell.com/show_bug.cgi?id=878722

  "The flag is called "enable_snapshots" in the drive section.
   Snapper will be also installed if the flag has not been
   defined in the configuration file."

Should already be included in Beta 9 but I didn't check that.

Regards,
  Arvin

-- 
Arvin Schnell, <aschnell at suse.de>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany

From urs.frey at post.ch  Mon Jun 23 06:21:04 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Mon, 23 Jun 2014 12:21:04 +0000
Subject: [sles-beta] autoyast, sshd and snapper
In-Reply-To: <20140623095425.GA18799@suse.de>
References: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr>
	<20140623095425.GA18799@suse.de>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9B4229@HXMB12.pnet.ch>

Hi
To be transparent for all, I assume you mean an entry like this in the autoinst.xml, correct?

<enable_snapshots config:type="boolean">true</enable_snapshots>

Like this in a btrfs section
        <partition>
          <create config:type="boolean">true</create>
          <crypt_fs config:type="boolean">false</crypt_fs>
          <filesystem config:type="symbol">btrfs</filesystem>
          <format config:type="boolean">true</format>
          <fstopt>defaults</fstopt>
          <loop_fs config:type="boolean">false</loop_fs>
          <enable_snapshots config:type="boolean">true</enable_snapshots>
          <mount>/</mount>
          <mountby config:type="symbol">uuid</mountby>
          <partition_id config:type="integer">131</partition_id>
          <partition_nr config:type="integer">3</partition_nr>
          <resize config:type="boolean">false</resize>
          <size>20GB</size>
          <subvolumes config:type="list">
            <listentry>@</listentry>
            <listentry>boot/grub2/x86_64-efi</listentry>
. . .

Thanks for feedback
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 Arvin Schnell
Gesendet: Monday, June 23, 2014 11:54 AM
An: FOLTIER Julien
Cc: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] autoyast, sshd and snapper

On Mon, Jun 16, 2014 at 10:01:27AM +0000, FOLTIER Julien wrote:
> Hi,
> 
> When I'm trying to install SLES12 beta 8 with an autoyast file, I don't have a snapper configuration after this installation and sshd is not enable and not started.
> How can I implement those 2 parameters in the autoyast file ?

snapper can be enabled now, see
https://bugzilla.novell.com/show_bug.cgi?id=878722

  "The flag is called "enable_snapshots" in the drive section.
   Snapper will be also installed if the flag has not been
   defined in the configuration file."

Should already be included in Beta 9 but I didn't check that.

Regards,
  Arvin

-- 
Arvin Schnell, <aschnell at suse.de>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

From schubi at suse.de  Mon Jun 23 06:30:10 2014
From: schubi at suse.de (Stefan Schubert)
Date: Mon, 23 Jun 2014 14:30:10 +0200
Subject: [sles-beta] autoyast, sshd and snapper
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9B4229@HXMB12.pnet.ch>
References: <02954CD80554BB4AA0977E7110B60C722782BAAB@RPN00150.melposte.log.intra.laposte.fr>	<20140623095425.GA18799@suse.de>
	<40637DBB36AF3941B243A286A432CA0B0F9B4229@HXMB12.pnet.ch>
Message-ID: <53A81DD2.8050601@suse.de>

Hi,
thanks for asking.

No, it is one level above like:

     <drive>
       <device>/dev/vda</device>
       <disklabel>msdos</disklabel>
       <enable_snapshots config:type="boolean">true</enable_snapshots>

But you do not have to set it. The default is "true" as it is in an 
-normal-
installation.

Greetings
Stefan

Am 23.06.2014 14:21, schrieb urs.frey at post.ch:
> Hi
> To be transparent for all, I assume you mean an entry like this in the autoinst.xml, correct?
>
> <enable_snapshots config:type="boolean">true</enable_snapshots>
>
> Like this in a btrfs section
>          <partition>
>            <create config:type="boolean">true</create>
>            <crypt_fs config:type="boolean">false</crypt_fs>
>            <filesystem config:type="symbol">btrfs</filesystem>
>            <format config:type="boolean">true</format>
>            <fstopt>defaults</fstopt>
>            <loop_fs config:type="boolean">false</loop_fs>
>            <enable_snapshots config:type="boolean">true</enable_snapshots>
>            <mount>/</mount>
>            <mountby config:type="symbol">uuid</mountby>
>            <partition_id config:type="integer">131</partition_id>
>            <partition_nr config:type="integer">3</partition_nr>
>            <resize config:type="boolean">false</resize>
>            <size>20GB</size>
>            <subvolumes config:type="list">
>              <listentry>@</listentry>
>              <listentry>boot/grub2/x86_64-efi</listentry>
> . . .
>
> Thanks for feedback
> 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 Arvin Schnell
> Gesendet: Monday, June 23, 2014 11:54 AM
> An: FOLTIER Julien
> Cc: sles-beta at lists.suse.com
> Betreff: Re: [sles-beta] autoyast, sshd and snapper
>
> On Mon, Jun 16, 2014 at 10:01:27AM +0000, FOLTIER Julien wrote:
>> Hi,
>>
>> When I'm trying to install SLES12 beta 8 with an autoyast file, I don't have a snapper configuration after this installation and sshd is not enable and not started.
>> How can I implement those 2 parameters in the autoyast file ?
> snapper can be enabled now, see
> https://bugzilla.novell.com/show_bug.cgi?id=878722
>
>    "The flag is called "enable_snapshots" in the drive section.
>     Snapper will be also installed if the flag has not been
>     defined in the configuration file."
>
> Should already be included in Beta 9 but I didn't check that.
>
> Regards,
>    Arvin
>


-- 
*******************************************************************************
Stefan Schubert
e-mail: schubi at suse.de
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany


From schubi at suse.de  Mon Jun 23 06:32:42 2014
From: schubi at suse.de (Stefan Schubert)
Date: Mon, 23 Jun 2014 14:32:42 +0200
Subject: [sles-beta] SLES12 x86_64 Beta9 autoyast setup Problem
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9B4209@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F9B4209@HXMB12.pnet.ch>
Message-ID: <53A81E6A.2060509@suse.de>

Please open a bug report and attach the configuration and log files.
Thank you !!!

Greetings
Stefan
Am 23.06.2014 14:00, schrieb urs.frey at post.ch:
>
> Hi
>
> When trying to set up SLES12 x86_64 Beta9 as VMware ESXi client using 
> autoyast, I get the yast mask, that automated setup would not be 
> possible. Sources can not be found
>
> When pressing F9 for the console shell I can see this
>
> sh: tset: command not found
>
> tty9(none):/ #
>
> For me this look like a bug
>
> 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


-- 
*******************************************************************************
Stefan Schubert
e-mail: schubi at suse.de
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany


From ohering at suse.de  Mon Jun 23 07:27:15 2014
From: ohering at suse.de (Olaf Hering)
Date: Mon, 23 Jun 2014 15:27:15 +0200
Subject: [sles-beta] SLES12B9 - hostname being reset to "linux" on
 zypper dup
In-Reply-To: <CAEUhfEd-nvrgrd1P-hpHuoZpnu9s=18KqfcC3xHUkqBNwn9FdQ@mail.gmail.com>
References: <CAEUhfEd-nvrgrd1P-hpHuoZpnu9s=18KqfcC3xHUkqBNwn9FdQ@mail.gmail.com>
Message-ID: <20140623132715.GA21331@suse.de>

On Mon, Jun 23, Darren Thompson wrote:

> Caused a little fun and games with my SLES12 cluster before I realised that
> everything was named "linux" ;-)

Looks like systemd is not well integrated into SUSE Linux. Since many
years /etc/HOSTNAME was the config file for the hostname. With Beta9
that file became /etc/hostname, owned by systemd. Tthe old file was
changed to a symlink. It should have been the other way around,
/etc/hostname should be a symlink to /etc/HOSTNAME.
I hope that change was not a mindless "do what upstream does" change...
At least its not mentioned in the release-notes.

Olaf

From schubi at suse.de  Mon Jun 23 07:29:17 2014
From: schubi at suse.de (Stefan Schubert)
Date: Mon, 23 Jun 2014 15:29:17 +0200
Subject: [sles-beta] SLES12 Beta9 x86_64 autoyast post-scripts,
 init-scripts get not invoked
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9B4248@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F9B4248@HXMB12.pnet.ch>
Message-ID: <53A82BAD.8080100@suse.de>

Hi,
sounds like bug. Yes, please open a bug report.

Greetings
Stefan

Am 23.06.2014 15:00, schrieb urs.frey at post.ch:
> Hi
> When trying to install SLES12 Beta9 using autoyast I have two very 
> simple scripts autoyast pst-script and autoyast init-script which do 
> not get invoked.
> At least I cannot find my logfiles under /var/adm/autoinstall/logs, as 
> defined in autoinst.xml
>     <post-scripts config:type="list">
>       <script>
>         <filename>post-script.sh</filename>
>         <interpreter>shell</interpreter>
>         <location/>
>         <feedback config:type="boolean">false</feedback>
>         <source><![CDATA[#!/bin/sh
> logdir=/var/adm/autoinstall/logs
> logf=${logdir}/post-script.sh.log
> #
> ls -l /etc/sysconfig/network
> cat /etc/hosts
> #
> sed -i "s/splash=silent/splash=verbose/g" /etc/default/grub
> sed -i "s/quiet//" /etc/default/grub
> /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg
> sed -i "s/#Port/Port/" /etc/ssh/sshd_config
> sed -i "s/PasswordAuthentication no/PasswordAuthentication yes/" 
> /etc/ssh/sshd_config
> #
> #
> cat /etc/fstab | sort > /etc/fstab_new
> mv -v /etc/fstab_new /etc/fstab
> #
>         ]]></source>
>       </script>
>     </post-scripts>
>     <init-scripts config:type="list">
>       <script>
>         <filename>init-script.sh</filename>
>         <interpreter>shell</interpreter>
>         <location></location>
>         <source><![CDATA[#!/bin/sh
> logdir=/var/adm/autoinstall/logs
> logf=${logdir}/init-script.sh.log
> #
> # initialize snapper here
> echo "configuring snapper for the first time"
> cat /etc/sysconfig/snapper
> ls -lsa /etc/snapper/configs/
> ls -lsa /
> #
> ]]></source>
>       </script>
>     </init-scripts>
>   </scripts>
> With Beta8 this works perfectly, now with Beta9 it does not work anymore.
> I consider this a bug
> Thank for feedback
> 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


-- 
*******************************************************************************
Stefan Schubert
e-mail: schubi at suse.de
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany


From urs.frey at post.ch  Mon Jun 23 07:34:13 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Mon, 23 Jun 2014 13:34:13 +0000
Subject: [sles-beta] SLES12 Beta9 x86_64 autoyast post-scripts,
 init-scripts get not invoked
In-Reply-To: <53A82BAD.8080100@suse.de>
References: <40637DBB36AF3941B243A286A432CA0B0F9B4248@HXMB12.pnet.ch>
	<53A82BAD.8080100@suse.de>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9B4280@HXMB12.pnet.ch>

Hi Stefan

Thank you for your feedback

Service Request  # 10898167643 has been created.  

 SUMMARY OF SR # 10898167643 
  * SR Severity Level: Medium  
  * SR Brief Description: SLES12 Beta9 x86_64 : autoinst.xml scripts are not executed

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 Stefan Schubert
Gesendet: Monday, June 23, 2014 3:29 PM
An: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 Beta9 x86_64 autoyast post-scripts, init-scripts get not invoked

Hi,
sounds like bug. Yes, please open a bug report.

Greetings
Stefan

Am 23.06.2014 15:00, schrieb urs.frey at post.ch:
> Hi
> When trying to install SLES12 Beta9 using autoyast I have two very 
> simple scripts autoyast pst-script and autoyast init-script which do 
> not get invoked.
> At least I cannot find my logfiles under /var/adm/autoinstall/logs, as 
> defined in autoinst.xml
>     <post-scripts config:type="list">
>       <script>
>         <filename>post-script.sh</filename>
>         <interpreter>shell</interpreter>
>         <location/>
>         <feedback config:type="boolean">false</feedback>
>         <source><![CDATA[#!/bin/sh
> logdir=/var/adm/autoinstall/logs
> logf=${logdir}/post-script.sh.log
> #
> ls -l /etc/sysconfig/network
> cat /etc/hosts
> #
> sed -i "s/splash=silent/splash=verbose/g" /etc/default/grub
> sed -i "s/quiet//" /etc/default/grub
> /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg
> sed -i "s/#Port/Port/" /etc/ssh/sshd_config
> sed -i "s/PasswordAuthentication no/PasswordAuthentication yes/" 
> /etc/ssh/sshd_config
> #
> #
> cat /etc/fstab | sort > /etc/fstab_new
> mv -v /etc/fstab_new /etc/fstab
> #
>         ]]></source>
>       </script>
>     </post-scripts>
>     <init-scripts config:type="list">
>       <script>
>         <filename>init-script.sh</filename>
>         <interpreter>shell</interpreter>
>         <location></location>
>         <source><![CDATA[#!/bin/sh
> logdir=/var/adm/autoinstall/logs
> logf=${logdir}/init-script.sh.log
> #
> # initialize snapper here
> echo "configuring snapper for the first time"
> cat /etc/sysconfig/snapper
> ls -lsa /etc/snapper/configs/
> ls -lsa /
> #
> ]]></source>
>       </script>
>     </init-scripts>
>   </scripts>
> With Beta8 this works perfectly, now with Beta9 it does not work anymore.
> I consider this a bug
> Thank for feedback
> 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


-- 
*******************************************************************************
Stefan Schubert
e-mail: schubi at suse.de
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany

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

From jreidinger at suse.cz  Mon Jun 23 07:34:32 2014
From: jreidinger at suse.cz (Josef Reidinger)
Date: Mon, 23 Jun 2014 15:34:32 +0200
Subject: [sles-beta] SLES12B9 - hostname being reset to "linux" on
 zypper dup
In-Reply-To: <20140623132715.GA21331@suse.de>
References: <CAEUhfEd-nvrgrd1P-hpHuoZpnu9s=18KqfcC3xHUkqBNwn9FdQ@mail.gmail.com>
	<20140623132715.GA21331@suse.de>
Message-ID: <20140623153432.776c4f36@dhcp150.suse.cz>

On Mon, 23 Jun 2014 15:27:15 +0200
"Olaf Hering" <ohering at suse.de> wrote:

> On Mon, Jun 23, Darren Thompson wrote:
> 
> > Caused a little fun and games with my SLES12 cluster before I
> > realised that everything was named "linux" ;-)
> 
> Looks like systemd is not well integrated into SUSE Linux. Since many
> years /etc/HOSTNAME was the config file for the hostname. With Beta9
> that file became /etc/hostname, owned by systemd. Tthe old file was
> changed to a symlink. It should have been the other way around,
> /etc/hostname should be a symlink to /etc/HOSTNAME.
> I hope that change was not a mindless "do what upstream does"
> change... At least its not mentioned in the release-notes.
> 
> Olaf

Reason is that other distros(debian, ubuntu, RH, mentioned also in
http://www.gnu.org/software/libc/manual/html_node/Host-Identification.html
in function sethostname) use /etc/hostname and there is no good reason
to be different in this case. I think this is good step, as we should
not diverge from upstream and other distribution unless it provides us
advantage over others that pays increased cost of maintaining such
difference.

Josef


From Dick.Waite at softwareag.com  Mon Jun 23 11:08:48 2014
From: Dick.Waite at softwareag.com (Waite, Dick)
Date: Mon, 23 Jun 2014 17:08:48 +0000
Subject: [sles-beta] SR 10884981671
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D5384F474@hqmbx6.eur.ad.sag>

Grand Evening,

    Update / Upgrade from SLES 11-SP3 to SLES 12-Beta9 running on VMware Workstation 10-0-2 x86_64

"SLES12-Beta9. New Install went Okay on VMware Workstation 10-0-2
Update from SLE11-SP-3 went better but something like "Python-Bonobo* needed a hand job. That did seem to work but I had no mouse control over the display. I could get into text mode with Cntl_Alt_F2 and I took some screenShots. I did try and copy /var/logs/* to a USB but one does not "see" the USB. I have noted the VMware update Tools giving a lot of nags. Should I try and update VMware Tools or is that part of SLES now?"

    I have noted in the past that the Gnome Shell does run with a high CPU usage ... My New Install on the above ran Okay, but while working on another machine I took some screenshots of the SLES 12-Beta9 doing no work but the CPU seems to be very high. maybe that is the way Gnome works, ???? maybe that is Okay but that would cost the users a lot on pennies eating that amount of CPU on a zlinux. It seem to be wanting to do something, but there was nothing to do that I could see. Never used Gnome before so bit of a loss as to what diagnostics to take, comments very welcome, use KDE would be very welcome ;o)

__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/20140623/36eb5667/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rjw02-12-0-0-2014-06-23-11-50-12.PNG
Type: image/png
Size: 516141 bytes
Desc: rjw02-12-0-0-2014-06-23-11-50-12.PNG
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/36eb5667/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rjw02-12-0-0-2014-06-23-11-54-25.PNG
Type: image/png
Size: 516532 bytes
Desc: rjw02-12-0-0-2014-06-23-11-54-25.PNG
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/36eb5667/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rjw02-12-0-0-2014-06-23-12-10-08.PNG
Type: image/png
Size: 515371 bytes
Desc: rjw02-12-0-0-2014-06-23-12-10-08.PNG
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/36eb5667/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rjw02-12-0-0-2014-06-23-12-59-25.PNG
Type: image/png
Size: 519634 bytes
Desc: rjw02-12-0-0-2014-06-23-12-59-25.PNG
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/36eb5667/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rjw02-12-0-0-2014-06-23-13-37-52.PNG
Type: image/png
Size: 517991 bytes
Desc: rjw02-12-0-0-2014-06-23-13-37-52.PNG
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/36eb5667/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rjw02-12-0-0-2014-06-23-13-44-17.PNG
Type: image/png
Size: 517262 bytes
Desc: rjw02-12-0-0-2014-06-23-13-44-17.PNG
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140623/36eb5667/attachment-0005.png>

From mfriesenegger at suse.com  Mon Jun 23 11:39:51 2014
From: mfriesenegger at suse.com (Mike Friesenegger)
Date: Mon, 23 Jun 2014 11:39:51 -0600
Subject: [sles-beta] ruby in the Web and Scripting module
Message-ID: <53A86667.50309@suse.com>

I thought that ruby was going to be part of the Web and Scripting module 
based on the modules beta call presentation.  I have looked at the Web 
and Scripting module for beta8 and beta9 and do not see ruby packages.  
I do see ruby 2.0 packages on the SLES12 install media.  Will ruby be 
part of the Web and Scripting module in the future?

Mike

From kukuk at suse.de  Mon Jun 23 12:04:55 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Mon, 23 Jun 2014 20:04:55 +0200
Subject: [sles-beta] ruby in the Web and Scripting module
In-Reply-To: <53A86667.50309@suse.com>
References: <53A86667.50309@suse.com>
Message-ID: <20140623180455.GA4586@suse.de>


Hi,

On Mon, Jun 23, Mike Friesenegger wrote:

> I thought that ruby was going to be part of the Web and Scripting module 
> based on the modules beta call presentation.  I have looked at the Web and 
> Scripting module for beta8 and beta9 and do not see ruby packages.  I do 
> see ruby 2.0 packages on the SLES12 install media.  Will ruby be part of 
> the Web and Scripting module in the future?

ruby itself will stay on SLES12, the presentation did mention
ruby on rails if I remember correctly.

  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 abonilla at suse.com  Mon Jun 23 12:10:58 2014
From: abonilla at suse.com (Alejandro Bonilla)
Date: Mon, 23 Jun 2014 19:10:58 +0100
Subject: [sles-beta] ruby in the Web and Scripting module
In-Reply-To: <20140623180455.GA4586@suse.de>
References: <53A86667.50309@suse.com> <20140623180455.GA4586@suse.de>
Message-ID: <53A87BC0020000A2000A3297@mail.emea.novell.com>

Right, and wasn't the idea of the modules to provide different versions? I guess it would be through that channel that a
newer version would be provided?

I need to read about this again...

  Original Message  
From: Thorsten Kukuk
Sent: Monday, June 23, 2014 2:05 PM
To: sles-beta at lists.suse.com
Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIHJ1YnkgaW4gdGhlIFdlYiBhbmQgU2NyaXB0aW5nIG1vZHVsZQ====?

Hi,

On Mon, Jun 23, Mike Friesenegger wrote:

> I thought that ruby was going to be part of the Web and Scripting module 
> based on the modules beta call presentation. I have looked at the Web and 
> Scripting module for beta8 and beta9 and do not see ruby packages. I do 
> see ruby 2.0 packages on the SLES12 install media. Will ruby be part of 
> the Web and Scripting module in the future?

ruby itself will stay on SLES12, the presentation did mention
ruby on rails if I remember correctly.

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 tparker at cbnco.com  Mon Jun 23 12:11:51 2014
From: tparker at cbnco.com (Tom Parker)
Date: Mon, 23 Jun 2014 14:11:51 -0400
Subject: [sles-beta] ruby in the Web and Scripting module
In-Reply-To: <20140623180455.GA4586@suse.de>
References: <53A86667.50309@suse.com> <20140623180455.GA4586@suse.de>
Message-ID: <53A86DE7.8000200@cbnco.com>

Hello

Will mod_passenger be included in the ruby on rails packages in the Web
and Scripting module?

Thanks

Tom

On 23/06/14 02:04 PM, Thorsten Kukuk wrote:
> Hi,
>
> On Mon, Jun 23, Mike Friesenegger wrote:
>
>> I thought that ruby was going to be part of the Web and Scripting module 
>> based on the modules beta call presentation.  I have looked at the Web and 
>> Scripting module for beta8 and beta9 and do not see ruby packages.  I do 
>> see ruby 2.0 packages on the SLES12 install media.  Will ruby be part of 
>> the Web and Scripting module in the future?
> ruby itself will stay on SLES12, the presentation did mention
> ruby on rails if I remember correctly.
>
>   Thorsten
>


From mge at suse.com  Mon Jun 23 12:22:27 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Mon, 23 Jun 2014 20:22:27 +0200
Subject: [sles-beta] ruby in the Web and Scripting module
In-Reply-To: <53A87BC0020000A2000A3297@mail.emea.novell.com>
References: <53A86667.50309@suse.com> <20140623180455.GA4586@suse.de>
	<53A87BC0020000A2000A3297@mail.emea.novell.com>
Message-ID: <20140623182227.GD8152@suse.com>

Hello Alejandro and all,

On 2014-06-23 T 19:10 +0100 Alejandro Bonilla wrote:

> Right, and wasn't the idea of the modules to provide
> different versions?

> I guess it would be through that channel that a newer
> version would be provided?

the answer to both questions is: Only for Ruby on Rails,
not for Ruby as a programming language.

> I need to read about this again...

so long -
	MgE


>   Original Message  
> From: Thorsten Kukuk
> Sent: Monday, June 23, 2014 2:05 PM
> To: sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIHJ1YnkgaW4gdGhlIFdlYiBhbmQgU2NyaXB0aW5nIG1vZHVsZQ====?
> 
> Hi,
> 
> On Mon, Jun 23, Mike Friesenegger wrote:
> 
> > I thought that ruby was going to be part of the Web and Scripting module 
> > based on the modules beta call presentation. I have looked at the Web and 
> > Scripting module for beta8 and beta9 and do not see ruby packages. I do 
> > see ruby 2.0 packages on the SLES12 install media. Will ruby be part of 
> > the Web and Scripting module in the future?
> 
> ruby itself will stay on SLES12, the presentation did mention
> ruby on rails if I remember correctly.
> 
> 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
> 
> 
> _______________________________________________
> 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 mfriesenegger at suse.com  Mon Jun 23 12:35:17 2014
From: mfriesenegger at suse.com (Mike Friesenegger)
Date: Mon, 23 Jun 2014 12:35:17 -0600
Subject: [sles-beta] ruby in the Web and Scripting module
In-Reply-To: <20140623182227.GD8152@suse.com>
References: <53A86667.50309@suse.com>
	<20140623180455.GA4586@suse.de>	<53A87BC0020000A2000A3297@mail.emea.novell.com>
	<20140623182227.GD8152@suse.com>
Message-ID: <53A87365.2050300@suse.com>

On 06/23/2014 12:22 PM, Matthias G. Eckermann wrote:
> the answer to both questions is: Only for Ruby on Rails,
> not for Ruby as a programming language.
Will newer versions of Ruby not just Ruby on Rails be made available 
either as a SLES12 update or via a module?

Mike

From mge at suse.com  Mon Jun 23 12:43:03 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Mon, 23 Jun 2014 20:43:03 +0200
Subject: [sles-beta] ruby in the Web and Scripting module
In-Reply-To: <53A87365.2050300@suse.com>
References: <53A86667.50309@suse.com> <20140623180455.GA4586@suse.de>
	<53A87BC0020000A2000A3297@mail.emea.novell.com>
	<20140623182227.GD8152@suse.com> <53A87365.2050300@suse.com>
Message-ID: <20140623184303.GE8152@suse.com>

On 2014-06-23 T 12:35 -0600 Mike Friesenegger wrote:
> On 06/23/2014 12:22 PM, Matthias G. Eckermann wrote:

> >the answer to both questions is: Only for Ruby on
> >Rails, not for Ruby as a programming language.

> Will newer versions of Ruby not just Ruby on Rails be
> made available either as a SLES12 update or via a
> module?

Fully backward compatible ruby versions might be
provided as part of SLES over the years.

If we would ship non-backward compatible ruby versions
for SLES 12 at all has not been decided yet. This
certainly depends on the development in the ruby
(language) community.

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 dbyte at suse.com  Mon Jun 23 12:47:48 2014
From: dbyte at suse.com (David Byte)
Date: Mon, 23 Jun 2014 12:47:48 -0600
Subject: [sles-beta] ruby in the Web and Scripting module
In-Reply-To: <20140623184303.GE8152@suse.com>
References: <53A86667.50309@suse.com> <20140623180455.GA4586@suse.de>
	<53A87BC0020000A2000A3297@mail.emea.novell.com>
	<20140623182227.GD8152@suse.com> <53A87365.2050300@suse.com>
	<20140623184303.GE8152@suse.com>
Message-ID: <53A83004020000050000F023@prv-mh.provo.novell.com>

Is it safe to assume that changes in Ruby have to synced with compatibility with Yast now as well?


David Byte
Sr. Technology Strategist, OEM
SUSE
dbyte at suse.com
(P)918.528.4422
www.suse.com 
https://www.suse.com/partners/integrated-systems/

>>> "Matthias G. Eckermann" <mge at suse.com> 6/23/2014 1:43 PM >>>
On 2014-06-23 T 12:35 -0600 Mike Friesenegger wrote:
> On 06/23/2014 12:22 PM, Matthias G. Eckermann wrote:

> >the answer to both questions is: Only for Ruby on
> >Rails, not for Ruby as a programming language.

> Will newer versions of Ruby not just Ruby on Rails be
> made available either as a SLES12 update or via a
> module?

Fully backward compatible ruby versions might be
provided as part of SLES over the years.

If we would ship non-backward compatible ruby versions
for SLES 12 at all has not been decided yet. This
certainly depends on the development in the ruby
(language) community.

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)
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com 
http://lists.suse.com/mailman/listinfo/sles-beta

From kukuk at suse.de  Mon Jun 23 14:09:19 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Mon, 23 Jun 2014 22:09:19 +0200
Subject: [sles-beta] ruby in the Web and Scripting module
In-Reply-To: <53A83004020000050000F023@prv-mh.provo.novell.com>
References: <53A86667.50309@suse.com> <20140623180455.GA4586@suse.de>
	<53A87BC0020000A2000A3297@mail.emea.novell.com>
	<20140623182227.GD8152@suse.com> <53A87365.2050300@suse.com>
	<20140623184303.GE8152@suse.com>
	<53A83004020000050000F023@prv-mh.provo.novell.com>
Message-ID: <20140623200919.GA14273@suse.de>

On Mon, Jun 23, David Byte wrote:

> Is it safe to assume that changes in Ruby have to synced with compatibility with Yast now as well?

As of today, nobody can say anything how this all will develop,
too much depends on "upstream" we cannot influence.
But there is no problem that YaST will continue to use the current
ruby implementation and modules until the EOL of SUSE Linux Enterprise 12
independent of any ruby updates we will do.

  Thorsten

> David Byte
> Sr. Technology Strategist, OEM
> SUSE
> dbyte at suse.com
> (P)918.528.4422
> www.suse.com 
> https://www.suse.com/partners/integrated-systems/
> 
> >>> "Matthias G. Eckermann" <mge at suse.com> 6/23/2014 1:43 PM >>>
> On 2014-06-23 T 12:35 -0600 Mike Friesenegger wrote:
> > On 06/23/2014 12:22 PM, Matthias G. Eckermann wrote:
> 
> > >the answer to both questions is: Only for Ruby on
> > >Rails, not for Ruby as a programming language.
> 
> > Will newer versions of Ruby not just Ruby on Rails be
> > made available either as a SLES12 update or via a
> > module?
> 
> Fully backward compatible ruby versions might be
> provided as part of SLES over the years.
> 
> If we would ship non-backward compatible ruby versions
> for SLES 12 at all has not been decided yet. This
> certainly depends on the development in the ruby
> (language) community.
> 
> 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)
> _______________________________________________
> 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

-- 
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 darrent at akurit.com.au  Mon Jun 23 14:46:15 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Tue, 24 Jun 2014 06:46:15 +1000
Subject: [sles-beta] SLES12B9 - hostname being reset to "linux" on
	zypper dup
In-Reply-To: <20140623132715.GA21331@suse.de>
References: <CAEUhfEd-nvrgrd1P-hpHuoZpnu9s=18KqfcC3xHUkqBNwn9FdQ@mail.gmail.com>
	<20140623132715.GA21331@suse.de>
Message-ID: <CAEUhfEc73JJ1nOcokMWWUUzzuBik59cZjxf2qV+v5GsHD=t0sg@mail.gmail.com>

Olaf

i suspect its more of a "rpm overwrites a configuration file it shouldn't"
issue.

I believe they were using systemd hostname config from the beginning.

Darren


On 23 June 2014 23:27, Olaf Hering <ohering at suse.de> wrote:

> On Mon, Jun 23, Darren Thompson wrote:
>
> > Caused a little fun and games with my SLES12 cluster before I realised
> that
> > everything was named "linux" ;-)
>
> Looks like systemd is not well integrated into SUSE Linux. Since many
> years /etc/HOSTNAME was the config file for the hostname. With Beta9
> that file became /etc/hostname, owned by systemd. Tthe old file was
> changed to a symlink. It should have been the other way around,
> /etc/hostname should be a symlink to /etc/HOSTNAME.
> I hope that change was not a mindless "do what upstream does" change...
> At least its not mentioned in the release-notes.
>
> Olaf
>



-- 

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/20140624/c56d4278/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/20140624/c56d4278/attachment.jpg>

From tparker at cbnco.com  Mon Jun 23 14:51:08 2014
From: tparker at cbnco.com (Tom Parker)
Date: Mon, 23 Jun 2014 16:51:08 -0400
Subject: [sles-beta] cciss driver for HP hardware
In-Reply-To: <53A58FD8.3070802@cbnco.com>
References: <53A4FFA6.9060407@cbnco.com> <20140621102200.GA18878@suse.com>
	<53A58FD8.3070802@cbnco.com>
Message-ID: <53A8933C.2020808@cbnco.com>

Thanks Matthias.

Why has the cciss driver been removed from the distro?  I assume that it
is still in the linux kernel.  Is there a reason to deliberately stop
compiling it?

I am sure that I am not the only person who has tons of older servers
that still work 100% but will be unable to run SLES 12 because of this
change.

Tom


On 21/06/14 09:59 AM, Tom Parker wrote:
> Has the old cciss driver been removed from the kernel?  On my SP3
> systems I see from lspci that both the hspa and cciss drivers are
> available for this PCIID
>
> 0b:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i
> (SAS Controller)
>         Subsystem: Hewlett-Packard Company Smart Array E200i
>         Kernel driver in use: cciss
>         Kernel modules: hpsa, cciss
>
> I will have to test beta 9 on an old server on Monday
>
> Thanks
>
> Tom
>
> On 21/06/14 06:22 AM, Matthias G. Eckermann wrote:
>> Hello Tom and all,
>>
>> On 2014-06-20 T 23:44 -0400 Tom Parker wrote:
>>  
>>> I see that the cciss driver for older HP hardware is
>>> no longer supported.  Does this mean it has been
>>> removed from the kernel and is no longer available or
>>> just that SLES will not support systems using this
>>> driver?
>> please see the Release Notes, chapter 4.2.2:
>> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#Driver_Updates.Storage
>>  
>> Compared to other recent distributions, SLES 12 has
>> special code in the hpsa driver to support more of the
>> older controllers, i.e. more than the upstream driver.
>>
>>> We still have many HP BL460 G5 servers running in QA
>>> and Development that have many more years of useful
>>> life in them and all of them use the Hewlett-Packard
>>> Company Smart Array E200i Controller which is listed
>>> as not supported
>> However, unfortunately, the E200i is not among those,
>> where we can implement this.
>>
>> I am afraid, this is out of SUSE's control and should be
>> brought up with the hardware vendor, who also maintains
>> the upstream driver(s).
>>
>> so long -
>> 	MgE
>>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta


From mge at suse.com  Mon Jun 23 21:01:00 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Tue, 24 Jun 2014 05:01:00 +0200
Subject: [sles-beta] cciss driver for HP hardware
In-Reply-To: <53A8933C.2020808@cbnco.com>
References: <53A4FFA6.9060407@cbnco.com> <20140621102200.GA18878@suse.com>
	<53A58FD8.3070802@cbnco.com> <53A8933C.2020808@cbnco.com>
Message-ID: <20140624030100.GA5450@suse.com>

Hello Tom and all,

as already said in my last E-Mail about this topic, we
are taking input on drivers also from the vendor of the
respective hardware.

Regressions on this we try to mitigate, and compared to
other recent distributions, SLES 12 has special code in
the hpsa driver to support more of the older
controllers, i.e. more than the upstream driver.

I just realize that this advice is not reflected in the
Release Notes yet (please file an SR!), thus: please
try "hpsa_allow_any=1" as a kernel commandline option.

This will put the hpsa driver in a mode not supported by
HP (and subsequently not us, see:
https://www.kernel.org/doc/Documentation/scsi/hpsa.txt),
but at least you are able use the device for testing.

I apologize for any inconvenience, but as also said,
this is out of SUSE's control.

so long -
	MgE


On 2014-06-23 T 16:51 -0400 Tom Parker wrote:
> Thanks Matthias.
> 
> Why has the cciss driver been removed from the distro?  I assume that it
> is still in the linux kernel.  Is there a reason to deliberately stop
> compiling it?
> 
> I am sure that I am not the only person who has tons of older servers
> that still work 100% but will be unable to run SLES 12 because of this
> change.
> 
> Tom
> 
> 
> On 21/06/14 09:59 AM, Tom Parker wrote:
> > Has the old cciss driver been removed from the kernel?  On my SP3
> > systems I see from lspci that both the hspa and cciss drivers are
> > available for this PCIID
> >
> > 0b:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i
> > (SAS Controller)
> >         Subsystem: Hewlett-Packard Company Smart Array E200i
> >         Kernel driver in use: cciss
> >         Kernel modules: hpsa, cciss
> >
> > I will have to test beta 9 on an old server on Monday
> >
> > Thanks
> >
> > Tom
> >
> > On 21/06/14 06:22 AM, Matthias G. Eckermann wrote:
> >> Hello Tom and all,
> >>
> >> On 2014-06-20 T 23:44 -0400 Tom Parker wrote:
> >>  
> >>> I see that the cciss driver for older HP hardware is
> >>> no longer supported.  Does this mean it has been
> >>> removed from the kernel and is no longer available or
> >>> just that SLES will not support systems using this
> >>> driver?
> >> please see the Release Notes, chapter 4.2.2:
> >> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#Driver_Updates.Storage
> >>  
> >> Compared to other recent distributions, SLES 12 has
> >> special code in the hpsa driver to support more of the
> >> older controllers, i.e. more than the upstream driver.
> >>
> >>> We still have many HP BL460 G5 servers running in QA
> >>> and Development that have many more years of useful
> >>> life in them and all of them use the Hewlett-Packard
> >>> Company Smart Array E200i Controller which is listed
> >>> as not supported
> >> However, unfortunately, the E200i is not among those,
> >> where we can implement this.
> >>
> >> I am afraid, this is out of SUSE's control and should be
> >> brought up with the hardware vendor, who also maintains
> >> the upstream driver(s).
> >>
> >> so long -
> >> 	MgE
> >>
> > _______________________________________________
> > 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 tparker at cbnco.com  Mon Jun 23 21:18:15 2014
From: tparker at cbnco.com (Tom Parker)
Date: Mon, 23 Jun 2014 23:18:15 -0400
Subject: [sles-beta] cciss driver for HP hardware
In-Reply-To: <20140624030100.GA5450@suse.com>
References: <53A4FFA6.9060407@cbnco.com> <20140621102200.GA18878@suse.com>
	<53A58FD8.3070802@cbnco.com> <53A8933C.2020808@cbnco.com>
	<20140624030100.GA5450@suse.com>
Message-ID: <53A8EDF7.2020008@cbnco.com>

Thanks Matthias. 

The hpsa_allow_any=1 does not work on the G5 HP hardware. 

What I do find interesting is that openSuSE 13.1 which is running
3.11.10 has no problem on these systems and has both the cciss driver
and the hpsa driver available.  It uses the cciss driver on the old
hardware and the hpsa driver on the new.  My frustration is that I don't
see a reason for a mainline kernel driver to be removed.  If there are
conflicts with the pciids between these two drivers then it would seem
that a relatively simple patch should be able to remove any pciids that
should go to the hpsa kernel module from the cciss module

I guess for my older servers I will have to stick to SLES 11 SP3.  Sadly
this means that for my Dev and QA labs I will have to make a significant
investment to upgrade our physical infrastructure to run SLES 12.

Does anyone else on this list still use HP G5 servers?

Tom

On 23/06/14 11:01 PM, Matthias G. Eckermann wrote:
> Hello Tom and all,
>
> as already said in my last E-Mail about this topic, we
> are taking input on drivers also from the vendor of the
> respective hardware.
>
> Regressions on this we try to mitigate, and compared to
> other recent distributions, SLES 12 has special code in
> the hpsa driver to support more of the older
> controllers, i.e. more than the upstream driver.
>
> I just realize that this advice is not reflected in the
> Release Notes yet (please file an SR!), thus: please
> try "hpsa_allow_any=1" as a kernel commandline option.
>
> This will put the hpsa driver in a mode not supported by
> HP (and subsequently not us, see:
> https://www.kernel.org/doc/Documentation/scsi/hpsa.txt),
> but at least you are able use the device for testing.
>
> I apologize for any inconvenience, but as also said,
> this is out of SUSE's control.
>
> so long -
> 	MgE
>
>
> On 2014-06-23 T 16:51 -0400 Tom Parker wrote:
>> Thanks Matthias.
>>
>> Why has the cciss driver been removed from the distro?  I assume that it
>> is still in the linux kernel.  Is there a reason to deliberately stop
>> compiling it?
>>
>> I am sure that I am not the only person who has tons of older servers
>> that still work 100% but will be unable to run SLES 12 because of this
>> change.
>>
>> Tom
>>
>>
>> On 21/06/14 09:59 AM, Tom Parker wrote:
>>> Has the old cciss driver been removed from the kernel?  On my SP3
>>> systems I see from lspci that both the hspa and cciss drivers are
>>> available for this PCIID
>>>
>>> 0b:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i
>>> (SAS Controller)
>>>         Subsystem: Hewlett-Packard Company Smart Array E200i
>>>         Kernel driver in use: cciss
>>>         Kernel modules: hpsa, cciss
>>>
>>> I will have to test beta 9 on an old server on Monday
>>>
>>> Thanks
>>>
>>> Tom
>>>
>>> On 21/06/14 06:22 AM, Matthias G. Eckermann wrote:
>>>> Hello Tom and all,
>>>>
>>>> On 2014-06-20 T 23:44 -0400 Tom Parker wrote:
>>>>  
>>>>> I see that the cciss driver for older HP hardware is
>>>>> no longer supported.  Does this mean it has been
>>>>> removed from the kernel and is no longer available or
>>>>> just that SLES will not support systems using this
>>>>> driver?
>>>> please see the Release Notes, chapter 4.2.2:
>>>> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#Driver_Updates.Storage
>>>>  
>>>> Compared to other recent distributions, SLES 12 has
>>>> special code in the hpsa driver to support more of the
>>>> older controllers, i.e. more than the upstream driver.
>>>>
>>>>> We still have many HP BL460 G5 servers running in QA
>>>>> and Development that have many more years of useful
>>>>> life in them and all of them use the Hewlett-Packard
>>>>> Company Smart Array E200i Controller which is listed
>>>>> as not supported
>>>> However, unfortunately, the E200i is not among those,
>>>> where we can implement this.
>>>>
>>>> I am afraid, this is out of SUSE's control and should be
>>>> brought up with the hardware vendor, who also maintains
>>>> the upstream driver(s).
>>>>
>>>> so long -
>>>> 	MgE
>>>>
>>> _______________________________________________
>>> sles-beta mailing list
>>> sles-beta at lists.suse.com
>>> http://lists.suse.com/mailman/listinfo/sles-beta
>>


From darrent at akurit.com.au  Mon Jun 23 23:37:54 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Tue, 24 Jun 2014 15:37:54 +1000
Subject: [sles-beta] cciss driver for HP hardware
In-Reply-To: <53A8EDF7.2020008@cbnco.com>
References: <53A4FFA6.9060407@cbnco.com> <20140621102200.GA18878@suse.com>
	<53A58FD8.3070802@cbnco.com> <53A8933C.2020808@cbnco.com>
	<20140624030100.GA5450@suse.com> <53A8EDF7.2020008@cbnco.com>
Message-ID: <CAEUhfEdynXMmhrbWn01n4kD9XmZ8gT_6YRvFdipf_fEQqya9dw@mail.gmail.com>

Tom

Most of my customers would have "some" of the G5 hardware still in use.

In most cases it's a test/dev type setup.

You could run SLES11SP3 - XEN or VMWARE on the hardware and still use it
for SLES12 VMs

Darren


On 24 June 2014 13:18, Tom Parker <tparker at cbnco.com> wrote:

> Thanks Matthias.
>
> The hpsa_allow_any=1 does not work on the G5 HP hardware.
>
> What I do find interesting is that openSuSE 13.1 which is running
> 3.11.10 has no problem on these systems and has both the cciss driver
> and the hpsa driver available.  It uses the cciss driver on the old
> hardware and the hpsa driver on the new.  My frustration is that I don't
> see a reason for a mainline kernel driver to be removed.  If there are
> conflicts with the pciids between these two drivers then it would seem
> that a relatively simple patch should be able to remove any pciids that
> should go to the hpsa kernel module from the cciss module
>
> I guess for my older servers I will have to stick to SLES 11 SP3.  Sadly
> this means that for my Dev and QA labs I will have to make a significant
> investment to upgrade our physical infrastructure to run SLES 12.
>
> Does anyone else on this list still use HP G5 servers?
>
> Tom
>
> On 23/06/14 11:01 PM, Matthias G. Eckermann wrote:
> > Hello Tom and all,
> >
> > as already said in my last E-Mail about this topic, we
> > are taking input on drivers also from the vendor of the
> > respective hardware.
> >
> > Regressions on this we try to mitigate, and compared to
> > other recent distributions, SLES 12 has special code in
> > the hpsa driver to support more of the older
> > controllers, i.e. more than the upstream driver.
> >
> > I just realize that this advice is not reflected in the
> > Release Notes yet (please file an SR!), thus: please
> > try "hpsa_allow_any=1" as a kernel commandline option.
> >
> > This will put the hpsa driver in a mode not supported by
> > HP (and subsequently not us, see:
> > https://www.kernel.org/doc/Documentation/scsi/hpsa.txt),
> > but at least you are able use the device for testing.
> >
> > I apologize for any inconvenience, but as also said,
> > this is out of SUSE's control.
> >
> > so long -
> >       MgE
> >
> >
> > On 2014-06-23 T 16:51 -0400 Tom Parker wrote:
> >> Thanks Matthias.
> >>
> >> Why has the cciss driver been removed from the distro?  I assume that it
> >> is still in the linux kernel.  Is there a reason to deliberately stop
> >> compiling it?
> >>
> >> I am sure that I am not the only person who has tons of older servers
> >> that still work 100% but will be unable to run SLES 12 because of this
> >> change.
> >>
> >> Tom
> >>
> >>
> >> On 21/06/14 09:59 AM, Tom Parker wrote:
> >>> Has the old cciss driver been removed from the kernel?  On my SP3
> >>> systems I see from lspci that both the hspa and cciss drivers are
> >>> available for this PCIID
> >>>
> >>> 0b:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i
> >>> (SAS Controller)
> >>>         Subsystem: Hewlett-Packard Company Smart Array E200i
> >>>         Kernel driver in use: cciss
> >>>         Kernel modules: hpsa, cciss
> >>>
> >>> I will have to test beta 9 on an old server on Monday
> >>>
> >>> Thanks
> >>>
> >>> Tom
> >>>
> >>> On 21/06/14 06:22 AM, Matthias G. Eckermann wrote:
> >>>> Hello Tom and all,
> >>>>
> >>>> On 2014-06-20 T 23:44 -0400 Tom Parker wrote:
> >>>>
> >>>>> I see that the cciss driver for older HP hardware is
> >>>>> no longer supported.  Does this mean it has been
> >>>>> removed from the kernel and is no longer available or
> >>>>> just that SLES will not support systems using this
> >>>>> driver?
> >>>> please see the Release Notes, chapter 4.2.2:
> >>>>
> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#Driver_Updates.Storage
> >>>>
> >>>> Compared to other recent distributions, SLES 12 has
> >>>> special code in the hpsa driver to support more of the
> >>>> older controllers, i.e. more than the upstream driver.
> >>>>
> >>>>> We still have many HP BL460 G5 servers running in QA
> >>>>> and Development that have many more years of useful
> >>>>> life in them and all of them use the Hewlett-Packard
> >>>>> Company Smart Array E200i Controller which is listed
> >>>>> as not supported
> >>>> However, unfortunately, the E200i is not among those,
> >>>> where we can implement this.
> >>>>
> >>>> I am afraid, this is out of SUSE's control and should be
> >>>> brought up with the hardware vendor, who also maintains
> >>>> the upstream driver(s).
> >>>>
> >>>> so long -
> >>>>    MgE
> >>>>
> >>> _______________________________________________
> >>> 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/20140624/6a46153c/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/20140624/6a46153c/attachment.jpg>

From sbahling at suse.com  Tue Jun 24 00:25:14 2014
From: sbahling at suse.com (Scott Bahling)
Date: Tue, 24 Jun 2014 08:25:14 +0200
Subject: [sles-beta] cciss driver for HP hardware
In-Reply-To: <53A8EDF7.2020008@cbnco.com>
References: <53A4FFA6.9060407@cbnco.com> <20140621102200.GA18878@suse.com>
	<53A58FD8.3070802@cbnco.com> <53A8933C.2020808@cbnco.com>
	<20140624030100.GA5450@suse.com> <53A8EDF7.2020008@cbnco.com>
Message-ID: <1403591114.4675.40.camel@z620>

Hi Tom,

On Mon, 2014-06-23 at 23:18 -0400, Tom Parker wrote:
> Thanks Matthias. 
> 
> The hpsa_allow_any=1 does not work on the G5 HP hardware. 
> 
> What I do find interesting is that openSuSE 13.1 which is running
> 3.11.10 has no problem on these systems and has both the cciss driver
> and the hpsa driver available.  It uses the cciss driver on the old
> hardware and the hpsa driver on the new.  My frustration is that I don't
> see a reason for a mainline kernel driver to be removed.

In our enterprise product we try to only carry drivers that we can
guarantee full support for - this is especially true and critical for
storage devices. With cciss and hpsa we rely on our partnership with HP
as the developer, maintainer, and true expert of the hardware and
associated drivers to provide full, mission critical level support to
our mutual end users. HP has indicated that will no longer be supporting
the cciss driver in the future and therefore it's been deprecated from
our future products.

openSUSE, on the other hand, comes without any support commitments, so
is "safe" to carry the cciss as well as many other drivers that are
considered "unsupportable" in the enterprise sense.

> If there are
> conflicts with the pciids between these two drivers then it would seem
> that a relatively simple patch should be able to remove any pciids that
> should go to the hpsa kernel module from the cciss module
> 
> I guess for my older servers I will have to stick to SLES 11 SP3.  Sadly
> this means that for my Dev and QA labs I will have to make a significant
> investment to upgrade our physical infrastructure to run SLES 12.

> Does anyone else on this list still use HP G5 servers?

You might want to contact your HP representative to find out their plans
certify and support G5's with SUSE Linux Enterprise Server 12. 

> Tom

Best Regards,

Scott

> On 23/06/14 11:01 PM, Matthias G. Eckermann wrote:
> > Hello Tom and all,
> >
> > as already said in my last E-Mail about this topic, we
> > are taking input on drivers also from the vendor of the
> > respective hardware.
> >
> > Regressions on this we try to mitigate, and compared to
> > other recent distributions, SLES 12 has special code in
> > the hpsa driver to support more of the older
> > controllers, i.e. more than the upstream driver.
> >
> > I just realize that this advice is not reflected in the
> > Release Notes yet (please file an SR!), thus: please
> > try "hpsa_allow_any=1" as a kernel commandline option.
> >
> > This will put the hpsa driver in a mode not supported by
> > HP (and subsequently not us, see:
> > https://www.kernel.org/doc/Documentation/scsi/hpsa.txt),
> > but at least you are able use the device for testing.
> >
> > I apologize for any inconvenience, but as also said,
> > this is out of SUSE's control.
> >
> > so long -
> > 	MgE
> >
> >
> > On 2014-06-23 T 16:51 -0400 Tom Parker wrote:
> >> Thanks Matthias.
> >>
> >> Why has the cciss driver been removed from the distro?  I assume that it
> >> is still in the linux kernel.  Is there a reason to deliberately stop
> >> compiling it?
> >>
> >> I am sure that I am not the only person who has tons of older servers
> >> that still work 100% but will be unable to run SLES 12 because of this
> >> change.
> >>
> >> Tom
> >>
> >>
> >> On 21/06/14 09:59 AM, Tom Parker wrote:
> >>> Has the old cciss driver been removed from the kernel?  On my SP3
> >>> systems I see from lspci that both the hspa and cciss drivers are
> >>> available for this PCIID
> >>>
> >>> 0b:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i
> >>> (SAS Controller)
> >>>         Subsystem: Hewlett-Packard Company Smart Array E200i
> >>>         Kernel driver in use: cciss
> >>>         Kernel modules: hpsa, cciss
> >>>
> >>> I will have to test beta 9 on an old server on Monday
> >>>
> >>> Thanks
> >>>
> >>> Tom
> >>>
> >>> On 21/06/14 06:22 AM, Matthias G. Eckermann wrote:
> >>>> Hello Tom and all,
> >>>>
> >>>> On 2014-06-20 T 23:44 -0400 Tom Parker wrote:
> >>>>  
> >>>>> I see that the cciss driver for older HP hardware is
> >>>>> no longer supported.  Does this mean it has been
> >>>>> removed from the kernel and is no longer available or
> >>>>> just that SLES will not support systems using this
> >>>>> driver?
> >>>> please see the Release Notes, chapter 4.2.2:
> >>>> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#Driver_Updates.Storage
> >>>>  
> >>>> Compared to other recent distributions, SLES 12 has
> >>>> special code in the hpsa driver to support more of the
> >>>> older controllers, i.e. more than the upstream driver.
> >>>>
> >>>>> We still have many HP BL460 G5 servers running in QA
> >>>>> and Development that have many more years of useful
> >>>>> life in them and all of them use the Hewlett-Packard
> >>>>> Company Smart Array E200i Controller which is listed
> >>>>> as not supported
> >>>> However, unfortunately, the E200i is not among those,
> >>>> where we can implement this.
> >>>>
> >>>> I am afraid, this is out of SUSE's control and should be
> >>>> brought up with the hardware vendor, who also maintains
> >>>> the upstream driver(s).
> >>>>
> >>>> so long -
> >>>> 	MgE
> >>>>
> >>> _______________________________________________
> >>> 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
> 



From ohering at suse.de  Tue Jun 24 01:18:55 2014
From: ohering at suse.de (Olaf Hering)
Date: Tue, 24 Jun 2014 09:18:55 +0200
Subject: [sles-beta] SLES12B9 - hostname being reset to "linux" on
 zypper dup
In-Reply-To: <CAEUhfEc73JJ1nOcokMWWUUzzuBik59cZjxf2qV+v5GsHD=t0sg@mail.gmail.com>
References: <CAEUhfEd-nvrgrd1P-hpHuoZpnu9s=18KqfcC3xHUkqBNwn9FdQ@mail.gmail.com>	<20140623132715.GA21331@suse.de>
	<CAEUhfEc73JJ1nOcokMWWUUzzuBik59cZjxf2qV+v5GsHD=t0sg@mail.gmail.com>
Message-ID: <53A9265F.8040904@suse.de>

Am 23.06.2014 22:46, schrieb Darren Thompson:
> Olaf
>
> i suspect its more of a "rpm overwrites a configuration file it
> shouldn't" issue.

Please open a SR for it.
In my case netcfg was upgraded before systemd, so its post install 
scripts should preserve the content of the hostname config file.

Olaf


From urs.frey at post.ch  Tue Jun 24 02:23:22 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Tue, 24 Jun 2014 08:23:22 +0000
Subject: [sles-beta] cciss driver for HP hardware
In-Reply-To: <53A8EDF7.2020008@cbnco.com>
References: <53A4FFA6.9060407@cbnco.com> <20140621102200.GA18878@suse.com>
	<53A58FD8.3070802@cbnco.com> <53A8933C.2020808@cbnco.com>
	<20140624030100.GA5450@suse.com> <53A8EDF7.2020008@cbnco.com>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9B43C7@HXMB12.pnet.ch>

Hi all
Just some data about DL380-G5:
The Proliant DL380-G5 was released June 19th 2008. End-of-Life has been reached, it has been retired by HP
HP Proliant DL380-G5 has been the most successful model in sales numbers.

So running hardware which cannot be repaired anymore is a risk
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_ba847bafb2a2d782fcbb0710b053ce01=wsrp-navigationalState%3DdocId%253Demr_na-c00712808-51%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.tpst=ba847bafb2a2d782fcbb0710b053ce01&ac.admitted=1403597119390.876444892.199480143 

I agree there are costs coming up in terms of investments.
Maybe there is a chance to do it the way I did here:
When production changed from G7 to Gen8 I "recycled" two DL380-G7 for me to use as test-servers and then I retired my old DL380-G5 servers

Anyway there is no way to upgrade from cciss to hpsa driver in an automated way.
Of course one can do so manually, by editing device-map, bootloader settings, initd and fstab.
One just needs to know, on which partition which filesystem was mounted.
http://www.novell.com/support/kb/doc.php?id=7012465 
http://h10032.www1.hp.com/ctg/Manual/c02677069.pdf 

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 Tom Parker
Gesendet: Tuesday, June 24, 2014 5:18 AM
An: Matthias G. Eckermann; sles-beta at lists.suse.com
Betreff: Re: [sles-beta] cciss driver for HP hardware

Thanks Matthias. 

The hpsa_allow_any=1 does not work on the G5 HP hardware. 

What I do find interesting is that openSuSE 13.1 which is running
3.11.10 has no problem on these systems and has both the cciss driver
and the hpsa driver available.  It uses the cciss driver on the old
hardware and the hpsa driver on the new.  My frustration is that I don't
see a reason for a mainline kernel driver to be removed.  If there are
conflicts with the pciids between these two drivers then it would seem
that a relatively simple patch should be able to remove any pciids that
should go to the hpsa kernel module from the cciss module

I guess for my older servers I will have to stick to SLES 11 SP3.  Sadly
this means that for my Dev and QA labs I will have to make a significant
investment to upgrade our physical infrastructure to run SLES 12.

Does anyone else on this list still use HP G5 servers?

Tom

On 23/06/14 11:01 PM, Matthias G. Eckermann wrote:
> Hello Tom and all,
>
> as already said in my last E-Mail about this topic, we
> are taking input on drivers also from the vendor of the
> respective hardware.
>
> Regressions on this we try to mitigate, and compared to
> other recent distributions, SLES 12 has special code in
> the hpsa driver to support more of the older
> controllers, i.e. more than the upstream driver.
>
> I just realize that this advice is not reflected in the
> Release Notes yet (please file an SR!), thus: please
> try "hpsa_allow_any=1" as a kernel commandline option.
>
> This will put the hpsa driver in a mode not supported by
> HP (and subsequently not us, see:
> https://www.kernel.org/doc/Documentation/scsi/hpsa.txt),
> but at least you are able use the device for testing.
>
> I apologize for any inconvenience, but as also said,
> this is out of SUSE's control.
>
> so long -
> 	MgE
>
>
> On 2014-06-23 T 16:51 -0400 Tom Parker wrote:
>> Thanks Matthias.
>>
>> Why has the cciss driver been removed from the distro?  I assume that it
>> is still in the linux kernel.  Is there a reason to deliberately stop
>> compiling it?
>>
>> I am sure that I am not the only person who has tons of older servers
>> that still work 100% but will be unable to run SLES 12 because of this
>> change.
>>
>> Tom
>>
>>
>> On 21/06/14 09:59 AM, Tom Parker wrote:
>>> Has the old cciss driver been removed from the kernel?  On my SP3
>>> systems I see from lspci that both the hspa and cciss drivers are
>>> available for this PCIID
>>>
>>> 0b:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i
>>> (SAS Controller)
>>>         Subsystem: Hewlett-Packard Company Smart Array E200i
>>>         Kernel driver in use: cciss
>>>         Kernel modules: hpsa, cciss
>>>
>>> I will have to test beta 9 on an old server on Monday
>>>
>>> Thanks
>>>
>>> Tom
>>>
>>> On 21/06/14 06:22 AM, Matthias G. Eckermann wrote:
>>>> Hello Tom and all,
>>>>
>>>> On 2014-06-20 T 23:44 -0400 Tom Parker wrote:
>>>>  
>>>>> I see that the cciss driver for older HP hardware is
>>>>> no longer supported.  Does this mean it has been
>>>>> removed from the kernel and is no longer available or
>>>>> just that SLES will not support systems using this
>>>>> driver?
>>>> please see the Release Notes, chapter 4.2.2:
>>>> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#Driver_Updates.Storage
>>>>  
>>>> Compared to other recent distributions, SLES 12 has
>>>> special code in the hpsa driver to support more of the
>>>> older controllers, i.e. more than the upstream driver.
>>>>
>>>>> We still have many HP BL460 G5 servers running in QA
>>>>> and Development that have many more years of useful
>>>>> life in them and all of them use the Hewlett-Packard
>>>>> Company Smart Array E200i Controller which is listed
>>>>> as not supported
>>>> However, unfortunately, the E200i is not among those,
>>>> where we can implement this.
>>>>
>>>> I am afraid, this is out of SUSE's control and should be
>>>> brought up with the hardware vendor, who also maintains
>>>> the upstream driver(s).
>>>>
>>>> so long -
>>>> 	MgE
>>>>
>>> _______________________________________________
>>> 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

From jsmeix at suse.de  Tue Jun 24 04:27:01 2014
From: jsmeix at suse.de (Johannes Meixner)
Date: Tue, 24 Jun 2014 12:27:01 +0200 (CEST)
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
Message-ID: <alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>


Hello,

On Jun 24 08:31 Michael Baensch wrote (excerpt):
> ... the generated file /root/autoinst.xml does not contain ...

See
https://bugzilla.novell.com/show_bug.cgi?id=882982

How was /root/autoinst.xml generated?

Automatically at the end of the installation
or
manually by calling "yast2 --ncurses clone_system" (or any
equivalent GUI way you like and know that it works ;-)

That makes a huge difference - at least for me, see
https://bugzilla.novell.com/show_bug.cgi?id=882982#c4


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

From michael.baensch at dfs.de  Tue Jun 24 05:46:35 2014
From: michael.baensch at dfs.de (Michael Baensch)
Date: Tue, 24 Jun 2014 11:46:35 +0000
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
Message-ID: <f2c3878ae91646759a43bba6c6c1348c@LGNMSXB02.prod.bk.dfs>

Hello,

the /root/autoinst.xml was generated automatically at the end of the installation.

Regards
 Michael


-----Urspr?ngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Johannes Meixner
Gesendet: Dienstag, 24. Juni 2014 12:27
An: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 Beta9 autoyast tmpfs bug


Hello,

On Jun 24 08:31 Michael Baensch wrote (excerpt):
> ... the generated file /root/autoinst.xml does not contain ...

See
https://bugzilla.novell.com/show_bug.cgi?id=882982

How was /root/autoinst.xml generated?

Automatically at the end of the installation or manually by calling "yast2 --ncurses clone_system" (or any equivalent GUI way you like and know that it works ;-)

That makes a huge difference - at least for me, see
https://bugzilla.novell.com/show_bug.cgi?id=882982#c4


Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer _______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

DFS Deutsche Flugsicherung GmbH
Am DFS-Campus
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Michael Odenwald
Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>


From jsrain at suse.cz  Tue Jun 24 06:07:55 2014
From: jsrain at suse.cz (Jiri Srain)
Date: Tue, 24 Jun 2014 14:07:55 +0200
Subject: [sles-beta] Installation with SMT
In-Reply-To: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>
References: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>
Message-ID: <53A96A1B.4040000@suse.cz>

Hello,

On 06/23/2014 01:29 PM, Datacenter/DFS wrote:
> Hello List,
>
> we had installed the new SMT (beta) on a SLES11 SP3. We configured SMT to mirror SLES12 pool+updates.
>
> Now we are about to install a fresh SLES12 beta8 and want to register it to the SMT _before_ installation (that's a new sles12 feature).
>
> Therefore the Registration Page in Yast provides the ability to configure network (ip, dns, gateway) right at the beginning of the installation process (Button upper right "Network Configuration").
>
> The Registration Page further asks for "Email" and "Registration Code".
> When proceeding with or without entering any Email/RegCode the system seems to try to contact nu.novell.com (though I did not confirm this) - popup "Contacting Registration Server". After a timeout I get an error since our systems do not have internet access - popup "Error Registration Failed".
>
> Following Questions:
> How can one enter a local SMT server?

Just put the registratioan URL, like

regurl=http://<hostname>/connect

to the AutoYaST profile to the registration section, see

https://github.com/yast/yast-registration/blob/master/src/autoyast-rnc/registration.rnc#L22

> How would one configure a proxy to contact either local SMT or nu.novell.com?

Don't understand this question...

> How is the network PRE-configured with autoyast.xml?

You can put the network configuration to the AutoYaST profile, via the 
<networking> section.

> How is the SMT registration configured with autoyast.xml?

See above.

Jiri

>
>
> Ronny Pretzsch
>
>
>
>
> DFS Deutsche Flugsicherung GmbH
> Am DFS-Campus
> D - 63225 Langen
>
> Tel.: +49-(0)6103-707-0
>
> Sitz der Gesellschaft: Langen/Hessen
> Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
> Vorsitzender des Aufsichtsrates: Michael Odenwald
> Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann
>
> Internet: http://www.dfs.de
> Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
>
>
>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com

From S.M.Flood at ucs.cam.ac.uk  Tue Jun 24 07:30:56 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Tue, 24 Jun 2014 14:30:56 +0100
Subject: [sles-beta] Installation with SMT
In-Reply-To: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>
References: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>
Message-ID: <53A97D90.1040806@ucs.cam.ac.uk>

On 23/06/2014 12:29, Datacenter/DFS wrote:

> we had installed the new SMT (beta) on a SLES11 SP3. We configured SMT to mirror SLES12 pool+updates.
>
> Now we are about to install a fresh SLES12 beta8 and want to register it to the SMT _before_ installation (that's a new sles12 feature).
>
> Therefore the Registration Page in Yast provides the ability to configure network (ip, dns, gateway) right at the beginning of the installation process (Button upper right "Network Configuration").
>
> The Registration Page further asks for "Email" and "Registration Code".
> When proceeding with or without entering any Email/RegCode the system seems to try to contact nu.novell.com (though I did not confirm this) - popup "Contacting Registration Server". After a timeout I get an error since our systems do not have internet access - popup "Error Registration Failed".
>
> Following Questions:

> How would one configure a proxy to contact either local SMT or nu.novell.com?

For a manual install try entering "proxy=http://<server>:<port>/" in the 
Boot Options field.

For an automated install via AutoYaST see 
http://users.suse.com/~ug/autoyast_doc/configuration.html#Configuration.Network.Proxy

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  Tue Jun 24 08:36:55 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Tue, 24 Jun 2014 15:36:55 +0100
Subject: [sles-beta] SCC not finding any systems
Message-ID: <53A98D07.6050701@ucs.cam.ac.uk>

I've just logged into SCC and it's not finding any systems under any of 
the organisations with which I'm associated - it has previously done so.

Note SUSEConnect has worked post-install.

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

Novell/SUSE/NetIQ Knowledge Partner

From schubi at suse.de  Tue Jun 24 09:13:51 2014
From: schubi at suse.de (Stefan Schubert)
Date: Tue, 24 Jun 2014 17:13:51 +0200
Subject: [sles-beta] Installation with SMT
In-Reply-To: <dfa6a334abf442e6b6923e129d957af6@LGNMSXA01.prod.bk.dfs>
References: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>	<53A96A1B.4040000@suse.cz>
	<dfa6a334abf442e6b6923e129d957af6@LGNMSXA01.prod.bk.dfs>
Message-ID: <53A995AF.2080407@suse.de>


<This does not seem to work (perhaps a bug?). The items in the <networking/> section are ignored in YaST's early stage.
<
<The network settings also do not work after the installation is finished but that's another story.
<The problem seems to be that systemd does not start wicked by default.
<I do not know whether wicked and system are also used in YaST's early stage.

Yes, you are right. This is a bug which has been fixed in yast2-network today:

-------------------------------------------------------------------
Tue Jun 24 10:00:47 CEST 2014 - schubi at suse.de

- bnc#883718
   Taking wicked as default in autoyast installation.
- 3.1.67

So, I fear that the registration cannot work at all without network.

Greetings
Stefan




-- 
*******************************************************************************
Stefan Schubert
e-mail: schubi at suse.de
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany


From jreidinger at suse.cz  Tue Jun 24 09:32:40 2014
From: jreidinger at suse.cz (Josef Reidinger)
Date: Tue, 24 Jun 2014 17:32:40 +0200
Subject: [sles-beta] Installation with SMT
In-Reply-To: <a9780bc3fe734f5f9bbd5ad2d556b41e@LGNMSXA01.prod.bk.dfs>
References: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>
	<53A96A1B.4040000@suse.cz>
	<dfa6a334abf442e6b6923e129d957af6@LGNMSXA01.prod.bk.dfs>
	<53A995AF.2080407@suse.de>
	<a9780bc3fe734f5f9bbd5ad2d556b41e@LGNMSXA01.prod.bk.dfs>
Message-ID: <20140624173240.0a290e2d@dhcp150.suse.cz>

On Tue, 24 Jun 2014 15:23:40 +0000
"Datacenter/DFS" <Datacenter at dfs.de> wrote:

> Hello,
> 
> > <This does not seem to work (perhaps a bug?). The items in the
> > <networking/> section are ignored in YaST's early stage.
> > <
> > <The network settings also do not work after the installation is
> > finished but that's another story.
> > <The problem seems to be that systemd does not start wicked by
> > default. <I do not know whether wicked and system are also used in
> > YaST's early stage.
> > 
> > Yes, you are right. This is a bug which has been fixed in
> > yast2-network today:
> > 
> > -------------------------------------------------------------------
> > Tue Jun 24 10:00:47 CEST 2014 - schubi at suse.de
> > 
> > - bnc#883718
> >    Taking wicked as default in autoyast installation.
> > - 3.1.67
> 
> I would have tried to tell autoyast to use wicked but I could not
> find the autoyast.xml option in any docu. I assume it is the same
> option that chose between "ifup/ifdown" and "network manager" in
> sles11. Is there a way to configure "use wicked" this in autoyast.xml
> - Otherwise I'll have to wait until beta10 ...
> 
> Did you also assure that the network is configured in early stage
> before registration? And did you assure that the proxy settings are
> configured in early stage before registration?
> 
> 
> > So, I fear that the registration cannot work at all without network.
> 
> Luckily when installing manually and configuring the network in the
> early stage, networking works. Yet I cannot enter a local SMT
> manually.

It is possible with boot parameter. Just when DVD came up and you
choose installation write to parameter line (similar like you specify
e.g. autoyast profile): regurl=http://<mysmt>



Josef

> 
> 
> Greetings,
> Ronny
> 
> > 
> > Greetings
> > Stefan


From jreidinger at suse.cz  Tue Jun 24 09:55:24 2014
From: jreidinger at suse.cz (Josef Reidinger)
Date: Tue, 24 Jun 2014 17:55:24 +0200
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <cd8f45b78ce443e79bfda5a126a5f5d2@LGNMSXA01.prod.bk.dfs>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
	<cd8f45b78ce443e79bfda5a126a5f5d2@LGNMSXA01.prod.bk.dfs>
Message-ID: <20140624175524.4f0a0887@dhcp150.suse.cz>

On Tue, 24 Jun 2014 15:43:39 +0000
"Datacenter/DFS" <Datacenter at dfs.de> wrote:

> Hello,
> 
> > 
> > On Jun 24 08:31 Michael Baensch wrote (excerpt):
> > > ... the generated file /root/autoinst.xml does not contain ...
> > 
> > See
> > https://bugzilla.novell.com/show_bug.cgi?id=882982
> > 
> > How was /root/autoinst.xml generated?
> > 
> > Automatically at the end of the installation or manually by calling
> > "yast2 --ncurses clone_system" (or any equivalent GUI way you like
> > and know that it works ;-)
> > 
> > That makes a huge difference - at least for me, see
> > https://bugzilla.novell.com/show_bug.cgi?id=882982#c4
> 
> For the tmpfs issue it makes no difference how the xml file is
> created. I manually installed sles12 beta9 and configured /tmp as
> tmpfs. This works fine.
> Then I called yast2 --ncurses clone_system
> The resulting xml file does not contain any tmpfs entry.
> 
> What I actually want to achieve: I want the xml "example" file for a
> tmpfs partition. Maybe someone can post an autoyast.xml extract with
> a tmpfs partition. I was unable to find a tmpfs example in the
> documentation.
> 
> 
> Ronny
> 

This looks like bug in autoyast partitioning export. Please report it.

Thanks
Josef

From darrent at akurit.com.au  Tue Jun 24 14:15:08 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 25 Jun 2014 06:15:08 +1000
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
Message-ID: <CAEUhfEe0jKSCsqRQF1Ns5j2YzKOn4_mC8Z+i+d9uTj1sP-x0Xg@mail.gmail.com>

Johannes

Does running "yast2 --ncurses clone_system" produce a viable autoint.xml?
the "autogenerated" one de not work very well in SLES12B9.

If it does work, that would be a useful tip.

Darren


On 24 June 2014 20:27, Johannes Meixner <jsmeix at suse.de> wrote:

>
> Hello,
>
> On Jun 24 08:31 Michael Baensch wrote (excerpt):
>
>> ... the generated file /root/autoinst.xml does not contain ...
>>
>
> See
> https://bugzilla.novell.com/show_bug.cgi?id=882982
>
> How was /root/autoinst.xml generated?
>
> Automatically at the end of the installation
> or
> manually by calling "yast2 --ncurses clone_system" (or any
> equivalent GUI way you like and know that it works ;-)
>
> That makes a huge difference - at least for me, see
> https://bugzilla.novell.com/show_bug.cgi?id=882982#c4
>
>
> Kind Regards
> Johannes Meixner
> --
> SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
> HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
> _______________________________________________
> 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/20140625/5c081bdf/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/20140625/5c081bdf/attachment.jpg>

From darrent at akurit.com.au  Tue Jun 24 14:45:12 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 25 Jun 2014 06:45:12 +1000
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <cd8f45b78ce443e79bfda5a126a5f5d2@LGNMSXA01.prod.bk.dfs>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
	<cd8f45b78ce443e79bfda5a126a5f5d2@LGNMSXA01.prod.bk.dfs>
Message-ID: <CAEUhfEfusS4BOFDj+dBXy707rZ7V8VQqyffta1OyCQNKctX=Eg@mail.gmail.com>

Team

Just speculating...

Wouldn't it be easier to setup the /tmp tmpfs thing in a 'post install'
autoyast script?

forgive my crude example:
echo "tmpfs /tmp tmpfs rw,nosuid,nodev,relatime,mode=755 0 0" >> /etc/fstab

Just a thought..

Darren


On 25 June 2014 01:43, Datacenter/DFS <Datacenter at dfs.de> wrote:

> Hello,
>
> >
> > On Jun 24 08:31 Michael Baensch wrote (excerpt):
> > > ... the generated file /root/autoinst.xml does not contain ...
> >
> > See
> > https://bugzilla.novell.com/show_bug.cgi?id=882982
> >
> > How was /root/autoinst.xml generated?
> >
> > Automatically at the end of the installation or manually by calling
> "yast2 --ncurses
> > clone_system" (or any equivalent GUI way you like and know that it works
> ;-)
> >
> > That makes a huge difference - at least for me, see
> > https://bugzilla.novell.com/show_bug.cgi?id=882982#c4
>
> For the tmpfs issue it makes no difference how the xml file is created.
> I manually installed sles12 beta9 and configured /tmp as tmpfs.
> This works fine.
> Then I called yast2 --ncurses clone_system
> The resulting xml file does not contain any tmpfs entry.
>
> What I actually want to achieve: I want the xml "example" file for a tmpfs
> partition. Maybe someone can post an autoyast.xml extract with a tmpfs
> partition. I was unable to find a tmpfs example in the documentation.
>
>
> Ronny
>
>
>
> DFS Deutsche Flugsicherung GmbH
> Am DFS-Campus
> D - 63225 Langen
>
> Tel.: +49-(0)6103-707-0
>
> Sitz der Gesellschaft: Langen/Hessen
> Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
> Vorsitzender des Aufsichtsrates: Michael Odenwald
> Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling,
> Dr. Michael Hann
>
> Internet: http://www.dfs.de
> Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <
> http://www.dfs.de/dfs/public_key.asc>
> _______________________________________________
> 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/20140625/62bcdcfb/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/20140625/62bcdcfb/attachment.jpg>

From darrent at akurit.com.au  Tue Jun 24 14:47:22 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Wed, 25 Jun 2014 06:47:22 +1000
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <20140624175524.4f0a0887@dhcp150.suse.cz>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
	<cd8f45b78ce443e79bfda5a126a5f5d2@LGNMSXA01.prod.bk.dfs>
	<20140624175524.4f0a0887@dhcp150.suse.cz>
Message-ID: <CAEUhfEdmsA_doL=zLfnvgrPiiHWGaE0k48crN+LpBmiYcWGQpQ@mail.gmail.com>

Team

I understand why it does not export tempfs entries as systemd sets up a
large numeber of autofs mounts automatically so it would confuse the
configuration if yast were to export them to the autoyast file.

Darren


On 25 June 2014 01:55, Josef Reidinger <jreidinger at suse.cz> wrote:

> On Tue, 24 Jun 2014 15:43:39 +0000
> "Datacenter/DFS" <Datacenter at dfs.de> wrote:
>
> > Hello,
> >
> > >
> > > On Jun 24 08:31 Michael Baensch wrote (excerpt):
> > > > ... the generated file /root/autoinst.xml does not contain ...
> > >
> > > See
> > > https://bugzilla.novell.com/show_bug.cgi?id=882982
> > >
> > > How was /root/autoinst.xml generated?
> > >
> > > Automatically at the end of the installation or manually by calling
> > > "yast2 --ncurses clone_system" (or any equivalent GUI way you like
> > > and know that it works ;-)
> > >
> > > That makes a huge difference - at least for me, see
> > > https://bugzilla.novell.com/show_bug.cgi?id=882982#c4
> >
> > For the tmpfs issue it makes no difference how the xml file is
> > created. I manually installed sles12 beta9 and configured /tmp as
> > tmpfs. This works fine.
> > Then I called yast2 --ncurses clone_system
> > The resulting xml file does not contain any tmpfs entry.
> >
> > What I actually want to achieve: I want the xml "example" file for a
> > tmpfs partition. Maybe someone can post an autoyast.xml extract with
> > a tmpfs partition. I was unable to find a tmpfs example in the
> > documentation.
> >
> >
> > Ronny
> >
>
> This looks like bug in autoyast partitioning export. Please report it.
>
> Thanks
> Josef
> _______________________________________________
> 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/20140625/dc43b817/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/20140625/dc43b817/attachment.jpg>

From Datacenter at dfs.de  Wed Jun 25 00:52:05 2014
From: Datacenter at dfs.de (Datacenter/DFS)
Date: Wed, 25 Jun 2014 06:52:05 +0000
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <CAEUhfEfusS4BOFDj+dBXy707rZ7V8VQqyffta1OyCQNKctX=Eg@mail.gmail.com>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
	<cd8f45b78ce443e79bfda5a126a5f5d2@LGNMSXA01.prod.bk.dfs>
	<CAEUhfEfusS4BOFDj+dBXy707rZ7V8VQqyffta1OyCQNKctX=Eg@mail.gmail.com>
Message-ID: <c3278b52a4c044c2bb644b560473daf3@LGNMSXA01.prod.bk.dfs>

Hello again,

the other tmpfs?s created by systemd do not show up in /etc/fstab.
Perhaps the exporter shall export only those tmpfs?s from /etc/fstab

Ronny


Von: Darren Thompson [mailto:darrent at akurit.com.au]
Gesendet: Dienstag, 24. Juni 2014 22:45
An: Datacenter/DFS
Cc: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 Beta9 autoyast tmpfs bug

Team

Just speculating...

Wouldn't it be easier to setup the /tmp tmpfs thing in a 'post install' autoyast script?

forgive my crude example:
echo "tmpfs /tmp tmpfs rw,nosuid,nodev,relatime,mode=755 0 0" >> /etc/fstab

Just a thought..

Darren

On 25 June 2014 01:43, Datacenter/DFS <Datacenter at dfs.de<mailto:Datacenter at dfs.de>> wrote:
Hello,

>
> On Jun 24 08:31 Michael Baensch wrote (excerpt):
> > ... the generated file /root/autoinst.xml does not contain ...
>
> See
> https://bugzilla.novell.com/show_bug.cgi?id=882982
>
> How was /root/autoinst.xml generated?
>
> Automatically at the end of the installation or manually by calling "yast2 --ncurses
> clone_system" (or any equivalent GUI way you like and know that it works ;-)
>
> That makes a huge difference - at least for me, see
> https://bugzilla.novell.com/show_bug.cgi?id=882982#c4

For the tmpfs issue it makes no difference how the xml file is created.
I manually installed sles12 beta9 and configured /tmp as tmpfs.
This works fine.
Then I called yast2 --ncurses clone_system
The resulting xml file does not contain any tmpfs entry.

What I actually want to achieve: I want the xml "example" file for a tmpfs partition. Maybe someone can post an autoyast.xml extract with a tmpfs partition. I was unable to find a tmpfs example in the documentation.


Ronny



DFS Deutsche Flugsicherung GmbH
Am DFS-Campus
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Michael Odenwald
Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
http://lists.suse.com/mailman/listinfo/sles-beta



--

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/>

DFS Deutsche Flugsicherung GmbH
Am DFS-Campus
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Michael Odenwald
Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140625/c717fa50/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/20140625/c717fa50/attachment.jpg>

From Datacenter at dfs.de  Wed Jun 25 00:53:57 2014
From: Datacenter at dfs.de (Datacenter/DFS)
Date: Wed, 25 Jun 2014 06:53:57 +0000
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <CAEUhfEfusS4BOFDj+dBXy707rZ7V8VQqyffta1OyCQNKctX=Eg@mail.gmail.com>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
	<cd8f45b78ce443e79bfda5a126a5f5d2@LGNMSXA01.prod.bk.dfs>
	<CAEUhfEfusS4BOFDj+dBXy707rZ7V8VQqyffta1OyCQNKctX=Eg@mail.gmail.com>
Message-ID: <1efae8bbb289452cb6dc1f3bcff6bfd2@LGNMSXA01.prod.bk.dfs>

Hello Darren,

If creating the /tmp partition in the post install script there might be leftover files from the installation in the /tmp directory on the ROOT partition. (No real problem but not nice anyway)

Thus it would be safer to create the tmpfs partition together with all other partitions before installing any files/rpms. As far as I know there is no script that runs right after yast?s partitioning and before installing.

Anyway the script is a good workaround. Thank you

Ronny


Von: Darren Thompson [mailto:darrent at akurit.com.au]
Gesendet: Dienstag, 24. Juni 2014 22:45
An: Datacenter/DFS
Cc: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 Beta9 autoyast tmpfs bug

Team

Just speculating...

Wouldn't it be easier to setup the /tmp tmpfs thing in a 'post install' autoyast script?

forgive my crude example:
echo "tmpfs /tmp tmpfs rw,nosuid,nodev,relatime,mode=755 0 0" >> /etc/fstab

Just a thought..

Darren

On 25 June 2014 01:43, Datacenter/DFS <Datacenter at dfs.de<mailto:Datacenter at dfs.de>> wrote:
Hello,

>
> On Jun 24 08:31 Michael Baensch wrote (excerpt):
> > ... the generated file /root/autoinst.xml does not contain ...
>
> See
> https://bugzilla.novell.com/show_bug.cgi?id=882982
>
> How was /root/autoinst.xml generated?
>
> Automatically at the end of the installation or manually by calling "yast2 --ncurses
> clone_system" (or any equivalent GUI way you like and know that it works ;-)
>
> That makes a huge difference - at least for me, see
> https://bugzilla.novell.com/show_bug.cgi?id=882982#c4

For the tmpfs issue it makes no difference how the xml file is created.
I manually installed sles12 beta9 and configured /tmp as tmpfs.
This works fine.
Then I called yast2 --ncurses clone_system
The resulting xml file does not contain any tmpfs entry.

What I actually want to achieve: I want the xml "example" file for a tmpfs partition. Maybe someone can post an autoyast.xml extract with a tmpfs partition. I was unable to find a tmpfs example in the documentation.


Ronny



DFS Deutsche Flugsicherung GmbH
Am DFS-Campus
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Michael Odenwald
Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
http://lists.suse.com/mailman/listinfo/sles-beta



--

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/>

DFS Deutsche Flugsicherung GmbH
Am DFS-Campus
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Michael Odenwald
Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140625/507f2095/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/20140625/507f2095/attachment.jpg>

From jsmeix at suse.de  Wed Jun 25 01:34:05 2014
From: jsmeix at suse.de (Johannes Meixner)
Date: Wed, 25 Jun 2014 09:34:05 +0200 (CEST)
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <CAEUhfEe0jKSCsqRQF1Ns5j2YzKOn4_mC8Z+i+d9uTj1sP-x0Xg@mail.gmail.com>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
	<CAEUhfEe0jKSCsqRQF1Ns5j2YzKOn4_mC8Z+i+d9uTj1sP-x0Xg@mail.gmail.com>
Message-ID: <alpine.LNX.2.00.1406250915130.3655@nelson.suse.de>


Hello Darren,

On Jun 25 06:15 Darren Thompson wrote (excerpt):
> Does running "yast2 --ncurses clone_system" produce
> a viable autoint.xml?
> the "autogenerated" one de not work very well in SLES12B9.
...
> On 24 June 2014 20:27, Johannes Meixner <jsmeix at suse.de> wrote:
>> See
>> https://bugzilla.novell.com/show_bug.cgi?id=882982

I assume you cannot access that bug report because it seems
we keep our SLE12 bug reports closed from general access
for SLE12 beta testers.

I added darrent at akurit.com.au to CC to that bug because I assume
that this way you can access it to get the full information directly
from its original source and you could even post comments there
so that we can avoid having to play some kind of "Chinese Whispers"
via continuous back and forth e-mail forwarding.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

From Joerg.Reisenweber at btc-it-services.com  Wed Jun 25 04:54:37 2014
From: Joerg.Reisenweber at btc-it-services.com (Joerg.Reisenweber at btc-it-services.com)
Date: Wed, 25 Jun 2014 12:54:37 +0200
Subject: [sles-beta] SLES12 Beta9 autoyast tmpfs bug
In-Reply-To: <1efae8bbb289452cb6dc1f3bcff6bfd2@LGNMSXA01.prod.bk.dfs>
References: <01af00e3a6074a6d891e1cc9bc59f7f5@LGNMSXB02.prod.bk.dfs>
	<alpine.LNX.2.00.1406241222390.4756@nelson.suse.de>
	<cd8f45b78ce443e79bfda5a126a5f5d2@LGNMSXA01.prod.bk.dfs>
	<CAEUhfEfusS4BOFDj+dBXy707rZ7V8VQqyffta1OyCQNKctX=Eg@mail.gmail.com>
	<1efae8bbb289452cb6dc1f3bcff6bfd2@LGNMSXA01.prod.bk.dfs>
Message-ID: <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0DC7ABFF@OLCA9095.btcnet.btc-ag.com>

Hi Ronny,

isn?t postpartitioning-scripts ?(after partitioning and mounting to /mnt but before RPM installation?since openSUSE 11.2 and SLES11 SP3)? just what you were looking for? http://doc.opensuse.org/projects/autoyast/configuration.html#postpartitioning-install.scripts

J?rg

Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Datacenter/DFS
Gesendet: Mittwoch, 25. Juni 2014 08:54
Cc: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 Beta9 autoyast tmpfs bug

Hello Darren,

If creating the /tmp partition in the post install script there might be leftover files from the installation in the /tmp directory on the ROOT partition. (No real problem but not nice anyway)

Thus it would be safer to create the tmpfs partition together with all other partitions before installing any files/rpms. As far as I know there is no script that runs right after yast?s partitioning and before installing.

Anyway the script is a good workaround. Thank you

Ronny


Von: Darren Thompson [mailto:darrent at akurit.com.au]
Gesendet: Dienstag, 24. Juni 2014 22:45
An: Datacenter/DFS
Cc: sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
Betreff: Re: [sles-beta] SLES12 Beta9 autoyast tmpfs bug

Team

Just speculating...

Wouldn't it be easier to setup the /tmp tmpfs thing in a 'post install' autoyast script?

forgive my crude example:
echo "tmpfs /tmp tmpfs rw,nosuid,nodev,relatime,mode=755 0 0" >> /etc/fstab

Just a thought..

Darren

On 25 June 2014 01:43, Datacenter/DFS <Datacenter at dfs.de<mailto:Datacenter at dfs.de>> wrote:
Hello,

>
> On Jun 24 08:31 Michael Baensch wrote (excerpt):
> > ... the generated file /root/autoinst.xml does not contain ...
>
> See
> https://bugzilla.novell.com/show_bug.cgi?id=882982
>
> How was /root/autoinst.xml generated?
>
> Automatically at the end of the installation or manually by calling "yast2 --ncurses
> clone_system" (or any equivalent GUI way you like and know that it works ;-)
>
> That makes a huge difference - at least for me, see
> https://bugzilla.novell.com/show_bug.cgi?id=882982#c4

For the tmpfs issue it makes no difference how the xml file is created.
I manually installed sles12 beta9 and configured /tmp as tmpfs.
This works fine.
Then I called yast2 --ncurses clone_system
The resulting xml file does not contain any tmpfs entry.

What I actually want to achieve: I want the xml "example" file for a tmpfs partition. Maybe someone can post an autoyast.xml extract with a tmpfs partition. I was unable to find a tmpfs example in the documentation.


Ronny



DFS Deutsche Flugsicherung GmbH
Am DFS-Campus
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Michael Odenwald
Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
http://lists.suse.com/mailman/listinfo/sles-beta



--

Darren Thompson

Professional Services Engineer / Consultant

 [cid:image001.jpg at 01CF9074.9F605390]

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/>

DFS Deutsche Flugsicherung GmbH
Am DFS-Campus
D - 63225 Langen

Tel.: +49-(0)6103-707-0

Sitz der Gesellschaft: Langen/Hessen
Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
Vorsitzender des Aufsichtsrates: Michael Odenwald
Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann

Internet: http://www.dfs.de
Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140625/39f0d616/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/20140625/39f0d616/attachment.jpg>

From gahorvath at novell.com  Wed Jun 25 10:12:00 2014
From: gahorvath at novell.com (Gabor K Horvath)
Date: Wed, 25 Jun 2014 18:12:00 +0200
Subject: [sles-beta] SLES12 beta9 setting default runlevel to 3
Message-ID: <53AAF4D0.6030105@novell.com>

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

Hi All,

I was trying to get rid of the running X11.

# systemctl set-default runlevel3.target
# Failed to set default target: No such file or directory
# cd /etc/systemd
# ln -sf /usr/lib/systemd/system/runlevel3.target default.target

Then back to graphical:

# systemctl set-default graphical.target
Failed to set default target: File exists
# rm /etc/systemd/default.target
# systemctl set-default graphical.target
#

Umm... Am I missing something?
Also the runlevel modul in yast doesn't show the runlevel targets.

g.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTqvTQAAoJEJG2j9wDrSONpKIH+QFIM163Hum+mZttKy+X7xCF
n7bCXihZWxwxYWiPV7faGc8adU6WJ/zPtemELucqkHF2TELWJhME51JYXSSohTUp
yn03fa0qHwMoOBsyZ6GJxTYzJXjm37hPjNkVWR/Cl1krpW9n7GOppm1oMBZYWcZI
6IZZCfjXTQZNCThBoidLIBzk8dVcGztVhPx8zdTlBD6tfYI+YL8QrqSXnjgCVmMU
JVg/8krfl3KU+5Uw1/HLFC5GE8bb+mBiMzYioHCw0wwOfmYZzSSZVcu02li9jNSe
30E8/Wde6ZjpjLfd3P/RLpICHYc8z1HIxNlF1RjfEfsJHYy4axFLNMEpPpNNFB0=
=nAjK
-----END PGP SIGNATURE-----

From fcrozat at suse.com  Wed Jun 25 10:16:52 2014
From: fcrozat at suse.com (Frederic Crozat)
Date: Wed, 25 Jun 2014 18:16:52 +0200
Subject: [sles-beta] SLES12 beta9 setting default runlevel to 3
In-Reply-To: <53AAF4D0.6030105@novell.com>
References: <53AAF4D0.6030105@novell.com>
Message-ID: <1403713012.7716.6.camel@par-r81vxc7.par.novell.com>

Le mercredi 25 juin 2014 ? 18:12 +0200, Gabor K Horvath a ?crit :
> Hi All,
> 
> I was trying to get rid of the running X11.
> 
> # systemctl set-default runlevel3.target
> # Failed to set default target: No such file or directory
> # cd /etc/systemd
> # ln -sf /usr/lib/systemd/system/runlevel3.target default.target

use systemctl -f set-default runlevel3.target

-- 
Frederic Crozat
Project Manager Enterprise Desktop
SUSE


From darrent at akurit.com.au  Wed Jun 25 14:07:21 2014
From: darrent at akurit.com.au (Darren Thompson (AkurIT))
Date: Thu, 26 Jun 2014 06:07:21 +1000
Subject: [sles-beta] SLES12 beta9 setting default runlevel to 3
In-Reply-To: <53AAF4D0.6030105@novell.com>
References: <53AAF4D0.6030105@novell.com>
Message-ID: <9EFA2F6E-11B1-4604-81C2-8429A4DC9906@akurit.com.au>

It's not the cause of the fault but the correct target to use for non GUI is multiple-user.target

I sent a few emails about how to change between default targets fairly recently.

Sent from my iPhone

On 26/06/2014, at 2:12, Gabor K Horvath <gahorvath at novell.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi All,
> 
> I was trying to get rid of the running X11.
> 
> # systemctl set-default runlevel3.target
> # Failed to set default target: No such file or directory
> # cd /etc/systemd
> # ln -sf /usr/lib/systemd/system/runlevel3.target default.target
> 
> Then back to graphical:
> 
> # systemctl set-default graphical.target
> Failed to set default target: File exists
> # rm /etc/systemd/default.target
> # systemctl set-default graphical.target
> #
> 
> Umm... Am I missing something?
> Also the runlevel modul in yast doesn't show the runlevel targets.
> 
> g.
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQEcBAEBAgAGBQJTqvTQAAoJEJG2j9wDrSONpKIH+QFIM163Hum+mZttKy+X7xCF
> n7bCXihZWxwxYWiPV7faGc8adU6WJ/zPtemELucqkHF2TELWJhME51JYXSSohTUp
> yn03fa0qHwMoOBsyZ6GJxTYzJXjm37hPjNkVWR/Cl1krpW9n7GOppm1oMBZYWcZI
> 6IZZCfjXTQZNCThBoidLIBzk8dVcGztVhPx8zdTlBD6tfYI+YL8QrqSXnjgCVmMU
> JVg/8krfl3KU+5Uw1/HLFC5GE8bb+mBiMzYioHCw0wwOfmYZzSSZVcu02li9jNSe
> 30E8/Wde6ZjpjLfd3P/RLpICHYc8z1HIxNlF1RjfEfsJHYy4axFLNMEpPpNNFB0=
> =nAjK
> -----END PGP SIGNATURE-----
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta

From allen at ua.edu  Wed Jun 25 14:47:12 2014
From: allen at ua.edu (Beddingfield, Allen)
Date: Wed, 25 Jun 2014 20:47:12 +0000
Subject: [sles-beta] Support status for Citrix XenServer?
Message-ID: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>

Will SLES 12 be supported by SUSE as a guest operating system on Citrix XenServer?  SLES 11 works beautifully.  I have not been able to get a working installation of any of the betas on there using a SLES template. If I use the "other install media" template, I can get a functioning HVM install, but if I use one of the proper templates for paravirtualization, I cannot get a working install.  Obviously, the HVM is an inefficient virtualization method on Xen, and is not recommended.

So my questions are:
1.  Will XenServer be supported, either officially or best-effort?
2.  Has any effort been put into testing SLES 12 as a XenServer guest?
3.  Has anyone gotten it to work as a paravirtualized guest? (I can make it work HVM)

I have a full multi-node XenServer configuration running 6.2.x, and would be glad to offer whatever assistance is needed with testing/troubleshooting this.

Thanks.
Allen B.

--
Allen Beddingfield
Systems Engineer
The University of Alabama

From darrent at akurit.com.au  Wed Jun 25 14:55:05 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Thu, 26 Jun 2014 06:55:05 +1000
Subject: [sles-beta] Support status for Citrix XenServer?
In-Reply-To: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>
References: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>
Message-ID: <CAEUhfEeDJTefZ30k5i38ctJWnHoOJdMNV7aConSA5ZpYAnfBYA@mail.gmail.com>

Allen

That is an odd/interesting result since I have been testing SLES12B7+ on
it's included XEN hypervisor and it works fine, so it's not an intrinsic
problem with running under a XEN hypervisor.

Darren


On 26 June 2014 06:47, Beddingfield, Allen <allen at ua.edu> wrote:

> Will SLES 12 be supported by SUSE as a guest operating system on Citrix
> XenServer?  SLES 11 works beautifully.  I have not been able to get a
> working installation of any of the betas on there using a SLES template. If
> I use the "other install media" template, I can get a functioning HVM
> install, but if I use one of the proper templates for paravirtualization, I
> cannot get a working install.  Obviously, the HVM is an inefficient
> virtualization method on Xen, and is not recommended.
>
> So my questions are:
> 1.  Will XenServer be supported, either officially or best-effort?
> 2.  Has any effort been put into testing SLES 12 as a XenServer guest?
> 3.  Has anyone gotten it to work as a paravirtualized guest? (I can make
> it work HVM)
>
> I have a full multi-node XenServer configuration running 6.2.x, and would
> be glad to offer whatever assistance is needed with testing/troubleshooting
> this.
>
> Thanks.
> Allen B.
>
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> _______________________________________________
> 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/20140626/6a1899bf/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/20140626/6a1899bf/attachment.jpg>

From darrent at akurit.com.au  Wed Jun 25 15:02:14 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Thu, 26 Jun 2014 07:02:14 +1000
Subject: [sles-beta] Opinion: It's too soon to leave beta and go to RC level
Message-ID: <CAEUhfEcZo6enN+ZRsn_EhjTuM+5_whupuU_JpfHwBC-0sd5qkA@mail.gmail.com>

Team

The next release of SLES12 is meant to be the first RC.

Personally I think it's still too early to go to an RC (Yes I know that
they have already extended the Beta cycle once).

For me personally, I am still focused on Install/setup issues (and still
finding serious bugs there)
- Autoyast
- Booting
- ISCSI (particularly the new target service).

I have not yet begun testing migration sceneries or done any
sociability/stability testing of at the application level.

I am EXPECTING to find serious bugs in the migration from SLES11 => SLES12
area in ISCSI, XEN and HA.

I also would like to spend more time on BTRFS/SAMBA integration and SAMBA
active/active HA on OCFS2.

Is just that I'm a laggard or are other finding that SLES12 is still not
ready for testing furter up the application stack yet?

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/20140626/07beeb89/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/20140626/07beeb89/attachment.jpg>

From jdouglas at suse.com  Wed Jun 25 15:29:39 2014
From: jdouglas at suse.com (Jason Douglas)
Date: Wed, 25 Jun 2014 15:29:39 -0600
Subject: [sles-beta] Support status for Citrix XenServer?
In-Reply-To: <AAD7066EC17A5541BF5145CD44BEFA72010046006D@EX10MBN02.ua-net.ua.edu>
References: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>,
	<CAEUhfEeDJTefZ30k5i38ctJWnHoOJdMNV7aConSA5ZpYAnfBYA@mail.gmail.com>
	<AAD7066EC17A5541BF5145CD44BEFA72010046006D@EX10MBN02.ua-net.ua.edu>
Message-ID: <53AAEAE80200006F000FF8EF@prv-mh.provo.novell.com>

Hi Allen,

The goal is to fully support SLES 12 as a guest on Citrix XenServer. However, I don't know if any testing has been done internally yet. 

Where are you encountering issues? Is it before, during, or after the installation? There are few things that immediately come to mind if the issue  is trying to start the VM following the install: 

1.  SLES 12 uses grub2 as it's bootloader. I'm not sure if Citrix XenServer supports that in a PV VM. 

2. The default root file system is btrfs. I'm fairly confident that Citrix XenServer doesn't support that. 

Could either of these issues be the problem you're seeing? If it's grub2 that's causing the problem, I'm not sure how to workaround the issue, but if it's btrfs, you should be able to select a different root file system, or create a separate boot partition, to see if that allows the VM to boot. 

It's probably a good idea to formalize this issue via your normal beta processes so that the appropriate bugzilla entries get created. 

Thanks!

Jason

> On Jun 25, 2014, at 2:58 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
> 
> I think it is specific to Citrix XenServer, and not an issue with running as a XEN guest, as I have also been able to get it to function on XEN that ships with SLES.
> 
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> ________________________________
> From: Darren Thompson [darrent at akurit.com.au]
> Sent: Wednesday, June 25, 2014 3:55 PM
> To: Beddingfield, Allen
> Cc: sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?> 
> Allen
> 
> That is an odd/interesting result since I have been testing SLES12B7+ on it's included XEN hypervisor and it works fine, so it's not an intrinsic problem with running under a XEN hypervisor.
> 
> Darren
> 
> 
> On 26 June 2014 06:47, Beddingfield, Allen <allen at ua.edu<mailto:allen at ua.edu>> wrote:
> Will SLES 12 be supported by SUSE as a guest operating system on Citrix XenServer?  SLES 11 works beautifully.  I have not been able to get a working installation of any of the betas on there using a SLES template. If I use the "other install media" template, I can get a functioning HVM install, but if I use one of the proper templates for paravirtualization, I cannot get a working install.  Obviously, the HVM is an inefficient virtualization method on Xen, and is not recommended.
> 
> So my questions are:
> 1.  Will XenServer be supported, either officially or best-effort?
> 2.  Has any effort been put into testing SLES 12 as a XenServer guest?
> 3.  Has anyone gotten it to work as a paravirtualized guest? (I can make it work HVM)
> 
> I have a full multi-node XenServer configuration running 6.2.x, and would be glad to offer whatever assistance is needed with testing/troubleshooting this.
> 
> Thanks.
> Allen B.
> 
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
> http://lists.suse.com/mailman/listinfo/sles-beta
> 
> 
> 
> --
> 
> 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/>
> <image003.jpg>
> <Part.002>


From allen at ua.edu  Wed Jun 25 15:33:56 2014
From: allen at ua.edu (Beddingfield, Allen)
Date: Wed, 25 Jun 2014 21:33:56 +0000
Subject: [sles-beta] Support status for Citrix XenServer?
In-Reply-To: <53AAEAE80200006F000FF8EF@prv-mh.provo.novell.com>
References: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>,
	<CAEUhfEeDJTefZ30k5i38ctJWnHoOJdMNV7aConSA5ZpYAnfBYA@mail.gmail.com>
	<AAD7066EC17A5541BF5145CD44BEFA72010046006D@EX10MBN02.ua-net.ua.edu>,
	<53AAEAE80200006F000FF8EF@prv-mh.provo.novell.com>
Message-ID: <AAD7066EC17A5541BF5145CD44BEFA7201004600E0@EX10MBN02.ua-net.ua.edu>

The installation goes off with no problem.  There are no errors or issues.  
On final reboot, the last three lines seen on the screen are:

Linux agpgart interface v0.103
Xen virtual console successfully install on ttyS0
i8042:  PNP:  No PS/2 controller found.  Probing ports directly.

At this point, it not only stops, but the VM actually powers off.  

Allen B.
--
Allen Beddingfield
Systems Engineer
The University of Alabama

________________________________________
From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Jason Douglas [jdouglas at suse.com]
Sent: Wednesday, June 25, 2014 4:29 PM
To: sles-beta at lists.suse.com
Subject: Re: [sles-beta] Support status for Citrix XenServer?

Hi Allen,

The goal is to fully support SLES 12 as a guest on Citrix XenServer. However, I don't know if any testing has been done internally yet.

Where are you encountering issues? Is it before, during, or after the installation? There are few things that immediately come to mind if the issue  is trying to start the VM following the install:

1.  SLES 12 uses grub2 as it's bootloader. I'm not sure if Citrix XenServer supports that in a PV VM.

2. The default root file system is btrfs. I'm fairly confident that Citrix XenServer doesn't support that.

Could either of these issues be the problem you're seeing? If it's grub2 that's causing the problem, I'm not sure how to workaround the issue, but if it's btrfs, you should be able to select a different root file system, or create a separate boot partition, to see if that allows the VM to boot.

It's probably a good idea to formalize this issue via your normal beta processes so that the appropriate bugzilla entries get created.

Thanks!

Jason

> On Jun 25, 2014, at 2:58 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
>
> I think it is specific to Citrix XenServer, and not an issue with running as a XEN guest, as I have also been able to get it to function on XEN that ships with SLES.
>
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> ________________________________
> From: Darren Thompson [darrent at akurit.com.au]
> Sent: Wednesday, June 25, 2014 3:55 PM
> To: Beddingfield, Allen
> Cc: sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
> Allen
>
> That is an odd/interesting result since I have been testing SLES12B7+ on it's included XEN hypervisor and it works fine, so it's not an intrinsic problem with running under a XEN hypervisor.
>
> Darren
>
>
> On 26 June 2014 06:47, Beddingfield, Allen <allen at ua.edu<mailto:allen at ua.edu>> wrote:
> Will SLES 12 be supported by SUSE as a guest operating system on Citrix XenServer?  SLES 11 works beautifully.  I have not been able to get a working installation of any of the betas on there using a SLES template. If I use the "other install media" template, I can get a functioning HVM install, but if I use one of the proper templates for paravirtualization, I cannot get a working install.  Obviously, the HVM is an inefficient virtualization method on Xen, and is not recommended.
>
> So my questions are:
> 1.  Will XenServer be supported, either officially or best-effort?
> 2.  Has any effort been put into testing SLES 12 as a XenServer guest?
> 3.  Has anyone gotten it to work as a paravirtualized guest? (I can make it work HVM)
>
> I have a full multi-node XenServer configuration running 6.2.x, and would be glad to offer whatever assistance is needed with testing/troubleshooting this.
>
> Thanks.
> Allen B.
>
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
> http://lists.suse.com/mailman/listinfo/sles-beta
>
>
>
> --
>
> 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/>
> <image003.jpg>
> <Part.002>

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

From allen at ua.edu  Wed Jun 25 15:41:35 2014
From: allen at ua.edu (Beddingfield, Allen)
Date: Wed, 25 Jun 2014 21:41:35 +0000
Subject: [sles-beta] Support status for Citrix XenServer?
In-Reply-To: <AAD7066EC17A5541BF5145CD44BEFA7201004600E0@EX10MBN02.ua-net.ua.edu>
References: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>,
	<CAEUhfEeDJTefZ30k5i38ctJWnHoOJdMNV7aConSA5ZpYAnfBYA@mail.gmail.com>
	<AAD7066EC17A5541BF5145CD44BEFA72010046006D@EX10MBN02.ua-net.ua.edu>,
	<53AAEAE80200006F000FF8EF@prv-mh.provo.novell.com>,
	<AAD7066EC17A5541BF5145CD44BEFA7201004600E0@EX10MBN02.ua-net.ua.edu>
Message-ID: <AAD7066EC17A5541BF5145CD44BEFA72010046010F@EX10MBN02.ua-net.ua.edu>

Oh, I forgot to mention - the filesystem is partitioned as follows:

1 gb ext3 /boot
2 gb swap
remainder XFS / filesystem
--
Allen Beddingfield
Systems Engineer
The University of Alabama

________________________________________
From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Beddingfield, Allen [allen at ua.edu]
Sent: Wednesday, June 25, 2014 4:33 PM
To: Jason Douglas; sles-beta at lists.suse.com
Subject: Re: [sles-beta] Support status for Citrix XenServer?

The installation goes off with no problem.  There are no errors or issues.
On final reboot, the last three lines seen on the screen are:

Linux agpgart interface v0.103
Xen virtual console successfully install on ttyS0
i8042:  PNP:  No PS/2 controller found.  Probing ports directly.

At this point, it not only stops, but the VM actually powers off.

Allen B.
--
Allen Beddingfield
Systems Engineer
The University of Alabama

________________________________________
From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Jason Douglas [jdouglas at suse.com]
Sent: Wednesday, June 25, 2014 4:29 PM
To: sles-beta at lists.suse.com
Subject: Re: [sles-beta] Support status for Citrix XenServer?

Hi Allen,

The goal is to fully support SLES 12 as a guest on Citrix XenServer. However, I don't know if any testing has been done internally yet.

Where are you encountering issues? Is it before, during, or after the installation? There are few things that immediately come to mind if the issue  is trying to start the VM following the install:

1.  SLES 12 uses grub2 as it's bootloader. I'm not sure if Citrix XenServer supports that in a PV VM.

2. The default root file system is btrfs. I'm fairly confident that Citrix XenServer doesn't support that.

Could either of these issues be the problem you're seeing? If it's grub2 that's causing the problem, I'm not sure how to workaround the issue, but if it's btrfs, you should be able to select a different root file system, or create a separate boot partition, to see if that allows the VM to boot.

It's probably a good idea to formalize this issue via your normal beta processes so that the appropriate bugzilla entries get created.

Thanks!

Jason

> On Jun 25, 2014, at 2:58 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
>
> I think it is specific to Citrix XenServer, and not an issue with running as a XEN guest, as I have also been able to get it to function on XEN that ships with SLES.
>
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> ________________________________
> From: Darren Thompson [darrent at akurit.com.au]
> Sent: Wednesday, June 25, 2014 3:55 PM
> To: Beddingfield, Allen
> Cc: sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
> Allen
>
> That is an odd/interesting result since I have been testing SLES12B7+ on it's included XEN hypervisor and it works fine, so it's not an intrinsic problem with running under a XEN hypervisor.
>
> Darren
>
>
> On 26 June 2014 06:47, Beddingfield, Allen <allen at ua.edu<mailto:allen at ua.edu>> wrote:
> Will SLES 12 be supported by SUSE as a guest operating system on Citrix XenServer?  SLES 11 works beautifully.  I have not been able to get a working installation of any of the betas on there using a SLES template. If I use the "other install media" template, I can get a functioning HVM install, but if I use one of the proper templates for paravirtualization, I cannot get a working install.  Obviously, the HVM is an inefficient virtualization method on Xen, and is not recommended.
>
> So my questions are:
> 1.  Will XenServer be supported, either officially or best-effort?
> 2.  Has any effort been put into testing SLES 12 as a XenServer guest?
> 3.  Has anyone gotten it to work as a paravirtualized guest? (I can make it work HVM)
>
> I have a full multi-node XenServer configuration running 6.2.x, and would be glad to offer whatever assistance is needed with testing/troubleshooting this.
>
> Thanks.
> Allen B.
>
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
> http://lists.suse.com/mailman/listinfo/sles-beta
>
>
>
> --
>
> 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/>
> <image003.jpg>
> <Part.002>

_______________________________________________
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

From Dick.Waite at softwareag.com  Wed Jun 25 15:49:33 2014
From: Dick.Waite at softwareag.com (Waite, Dick)
Date: Wed, 25 Jun 2014 21:49:33 +0000
Subject: [sles-beta] [Sleha-beta] Opinion: It's too soon to leave beta
 and go to RC level
In-Reply-To: <53AB39BB.4030805@cbnco.com>
References: <CAEUhfEcZo6enN+ZRsn_EhjTuM+5_whupuU_JpfHwBC-0sd5qkA@mail.gmail.com>
	<53AB39BB.4030805@cbnco.com>
Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D53851521@hqmbx6.eur.ad.sag>

Grand Evening,
          I have not run any of our applications on SLES12 yet. I can not get even a simple SLE11-SP3 to Update / Upgrade to SLES12 and until a clean update works, until the new Gnome Display Manager works, until what ever will replace the CRON functions work, until what ever is eating CPU in the Gnome Shell etc etc etc
          Maybe we are odd balls, we don?t use New Installs, we Upgrade and will continue to do so. I?m away from the Beta for a couple of weeks; I?d like to come back to Beta10 that can do the basic functions running on a VMware Workstation, with a Display Manager that works, VMware Tools that work and then maybe we can start to check applications. As we were 99% KDE I think we will have a lot of work to do once we have a stable working enviroment, but you can not start if you can not update working SLE11-SP3 environments without having to throw the bones on the table to see what to try next. If you think x86_64 is an issue try zLinux where we have very interesting issues, but that is for another day.

          Back in a couple of weeks, and that would also be a good reason to keep on Beta. It?s the start of the holiday season in Europe and even if I?m there, the person you need to do ?xyz? is with the family by the sea.

__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/>
___________________________________________


From: sleha-beta-bounces at lists.suse.com [mailto:sleha-beta-bounces at lists.suse.com] On Behalf Of Tom Parker
Sent: Wednesday, June 25, 2014 11:06 PM
To: Darren Thompson; sles-beta at lists.suse.com; SUSE Linux Enterprise High Availability Authorized Beta Program
Subject: Re: [Sleha-beta] Opinion: It's too soon to leave beta and go to RC level

We use iSCSI boot for our servers and since that doesn't work and the cciss driver is gone so I can't install locally on my test cluster, we are also behind in our HA and application testing.

Tom
On 25/06/14 05:02 PM, Darren Thompson wrote:
Team

The next release of SLES12 is meant to be the first RC.

Personally I think it's still too early to go to an RC (Yes I know that they have already extended the Beta cycle once).

For me personally, I am still focused on Install/setup issues (and still finding serious bugs there)
- Autoyast
- Booting
- ISCSI (particularly the new target service).

I have not yet begun testing migration sceneries or done any sociability/stability testing of at the application level.

I am EXPECTING to find serious bugs in the migration from SLES11 => SLES12 area in ISCSI, XEN and HA.

I also would like to spend more time on BTRFS/SAMBA integration and SAMBA active/active HA on OCFS2.

Is just that I'm a laggard or are other finding that SLES12 is still not ready for testing furter up the application stack yet?

Regards
Darren

--

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/>




_______________________________________________

sleha-beta mailing list

sleha-beta at lists.suse.com<mailto:sleha-beta at lists.suse.com>

http://lists.suse.com/mailman/listinfo/sleha-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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140625/65ff9877/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/20140625/65ff9877/attachment.jpg>

From jdouglas at suse.com  Wed Jun 25 16:59:36 2014
From: jdouglas at suse.com (Jason Douglas)
Date: Wed, 25 Jun 2014 16:59:36 -0600
Subject: [sles-beta] Support status for Citrix XenServer?
In-Reply-To: <AAD7066EC17A5541BF5145CD44BEFA72010046010F@EX10MBN02.ua-net.ua.edu>
References: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>,
	<CAEUhfEeDJTefZ30k5i38ctJWnHoOJdMNV7aConSA5ZpYAnfBYA@mail.gmail.com>
	<AAD7066EC17A5541BF5145CD44BEFA72010046006D@EX10MBN02.ua-net.ua.edu>,
	<53AAEAE80200006F000FF8EF@prv-mh.provo.novell.com>,
	<AAD7066EC17A5541BF5145CD44BEFA7201004600E0@EX10MBN02.ua-net.ua.edu>
	<AAD7066EC17A5541BF5145CD44BEFA72010046010F@EX10MBN02.ua-net.ua.edu>
Message-ID: <53AAFFFF0200006F000FF900@prv-mh.provo.novell.com>

To me it seems like grub2 is the most likely culprit. We will need to work with Citrix to see what support they can add to accommodate it. 

Jason

> On Jun 25, 2014, at 3:41 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
> 
> Oh, I forgot to mention - the filesystem is partitioned as follows:
> 
> 1 gb ext3 /boot
> 2 gb swap
> remainder XFS / filesystem
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> 
> ________________________________________
> From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Beddingfield, Allen [allen at ua.edu]
> Sent: Wednesday, June 25, 2014 4:33 PM
> To: Jason Douglas; sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?> 
> The installation goes off with no problem.  There are no errors or issues.
> On final reboot, the last three lines seen on the screen are:
> 
> Linux agpgart interface v0.103
> Xen virtual console successfully install on ttyS0
> i8042:  PNP:  No PS/2 controller found.  Probing ports directly.
> 
> At this point, it not only stops, but the VM actually powers off.
> 
> Allen B.
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> 
> ________________________________________
> From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Jason Douglas [jdouglas at suse.com]
> Sent: Wednesday, June 25, 2014 4:29 PM
> To: sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?> 
> Hi Allen,
> 
> The goal is to fully support SLES 12 as a guest on Citrix XenServer. However, I don't know if any testing has been done internally yet.
> 
> Where are you encountering issues? Is it before, during, or after the installation? There are few things that immediately come to mind if the issue  is trying to start the VM following the install:
> 
> 1.  SLES 12 uses grub2 as it's bootloader. I'm not sure if Citrix XenServer supports that in a PV VM.
> 
> 2. The default root file system is btrfs. I'm fairly confident that Citrix XenServer doesn't support that.
> 
> Could either of these issues be the problem you're seeing? If it's grub2 that's causing the problem, I'm not sure how to workaround the issue, but if it's btrfs, you should be able to select a different root file system, or create a separate boot partition, to see if that allows the VM to boot.
> 
> It's probably a good idea to formalize this issue via your normal beta processes so that the appropriate bugzilla entries get created.
> 
> Thanks!
> 
> Jason
> 
>> On Jun 25, 2014, at 2:58 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
>> 
>> I think it is specific to Citrix XenServer, and not an issue with running as a XEN guest, as I have also been able to get it to function on XEN that ships with SLES.
>> 
>> --
>> Allen Beddingfield
>> Systems Engineer
>> The University of Alabama
>> ________________________________
>> From: Darren Thompson [darrent at akurit.com.au]
>> Sent: Wednesday, June 25, 2014 3:55 PM
>> To: Beddingfield, Allen
>> Cc: sles-beta at lists.suse.com
>> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
>> Allen
>> 
>> That is an odd/interesting result since I have been testing SLES12B7+ on it's included XEN hypervisor and it works fine, so it's not an intrinsic problem with running under a XEN hypervisor.
>> 
>> Darren
>> 
>> 
>> On 26 June 2014 06:47, Beddingfield, Allen <allen at ua.edu<mailto:allen at ua.edu>> wrote:
>> Will SLES 12 be supported by SUSE as a guest operating system on Citrix XenServer?  SLES 11 works beautifully.  I have not been able to get a working installation of any of the betas on there using a SLES template. If I use the "other install media" template, I can get a functioning HVM install, but if I use one of the proper templates for paravirtualization, I cannot get a working install.  Obviously, the HVM is an inefficient virtualization method on Xen, and is not recommended.
>> 
>> So my questions are:
>> 1.  Will XenServer be supported, either officially or best-effort?
>> 2.  Has any effort been put into testing SLES 12 as a XenServer guest?
>> 3.  Has anyone gotten it to work as a paravirtualized guest? (I can make it work HVM)
>> 
>> I have a full multi-node XenServer configuration running 6.2.x, and would be glad to offer whatever assistance is needed with testing/troubleshooting this.
>> 
>> Thanks.
>> Allen B.
>> 
>> --
>> Allen Beddingfield
>> Systems Engineer
>> The University of Alabama
>> _______________________________________________
>> sles-beta mailing list
>> sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
>> http://lists.suse.com/mailman/listinfo/sles-beta
>> 
>> 
>> 
>> --
>> 
>> 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/>
>> <image003.jpg>
>> <Part.002>
> 
> _______________________________________________
> 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
> 


From allen at ua.edu  Wed Jun 25 22:29:23 2014
From: allen at ua.edu (Beddingfield, Allen)
Date: Thu, 26 Jun 2014 04:29:23 +0000
Subject: [sles-beta] Support status for Citrix XenServer?
In-Reply-To: <53AAFFFF0200006F000FF900@prv-mh.provo.novell.com>
References: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>,
	<CAEUhfEeDJTefZ30k5i38ctJWnHoOJdMNV7aConSA5ZpYAnfBYA@mail.gmail.com>
	<AAD7066EC17A5541BF5145CD44BEFA72010046006D@EX10MBN02.ua-net.ua.edu>,
	<53AAEAE80200006F000FF8EF@prv-mh.provo.novell.com>,
	<AAD7066EC17A5541BF5145CD44BEFA7201004600E0@EX10MBN02.ua-net.ua.edu>
	<AAD7066EC17A5541BF5145CD44BEFA72010046010F@EX10MBN02.ua-net.ua.edu>,
	<53AAFFFF0200006F000FF900@prv-mh.provo.novell.com>
Message-ID: <AAD7066EC17A5541BF5145CD44BEFA7201004603E8@EX10MBN02.ua-net.ua.edu>

I would have thought that a grub issue would stop it cold before anything was loaded from disk...maybe just presenting a blinking cursor.  With this, it looks like it is getting past the bootloader.
If there are any logs/info I can provide from the XenServer host or if I can figure out how to get them off of the guest os, I will be glad to.
Should I open an SR for this?
Allen B.
--
Allen Beddingfield
Systems Engineer
The University of Alabama

________________________________________
From: Jason Douglas [jdouglas at suse.com]
Sent: Wednesday, June 25, 2014 5:59 PM
To: Beddingfield, Allen
Cc: sles-beta at lists.suse.com
Subject: Re: [sles-beta] Support status for Citrix XenServer?

To me it seems like grub2 is the most likely culprit. We will need to work with Citrix to see what support they can add to accommodate it.

Jason

> On Jun 25, 2014, at 3:41 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
>
> Oh, I forgot to mention - the filesystem is partitioned as follows:
>
> 1 gb ext3 /boot
> 2 gb swap
> remainder XFS / filesystem
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
>
> ________________________________________
> From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Beddingfield, Allen [allen at ua.edu]
> Sent: Wednesday, June 25, 2014 4:33 PM
> To: Jason Douglas; sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
> The installation goes off with no problem.  There are no errors or issues.
> On final reboot, the last three lines seen on the screen are:
>
> Linux agpgart interface v0.103
> Xen virtual console successfully install on ttyS0
> i8042:  PNP:  No PS/2 controller found.  Probing ports directly.
>
> At this point, it not only stops, but the VM actually powers off.
>
> Allen B.
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
>
> ________________________________________
> From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Jason Douglas [jdouglas at suse.com]
> Sent: Wednesday, June 25, 2014 4:29 PM
> To: sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
> Hi Allen,
>
> The goal is to fully support SLES 12 as a guest on Citrix XenServer. However, I don't know if any testing has been done internally yet.
>
> Where are you encountering issues? Is it before, during, or after the installation? There are few things that immediately come to mind if the issue  is trying to start the VM following the install:
>
> 1.  SLES 12 uses grub2 as it's bootloader. I'm not sure if Citrix XenServer supports that in a PV VM.
>
> 2. The default root file system is btrfs. I'm fairly confident that Citrix XenServer doesn't support that.
>
> Could either of these issues be the problem you're seeing? If it's grub2 that's causing the problem, I'm not sure how to workaround the issue, but if it's btrfs, you should be able to select a different root file system, or create a separate boot partition, to see if that allows the VM to boot.
>
> It's probably a good idea to formalize this issue via your normal beta processes so that the appropriate bugzilla entries get created.
>
> Thanks!
>
> Jason
>
>> On Jun 25, 2014, at 2:58 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
>>
>> I think it is specific to Citrix XenServer, and not an issue with running as a XEN guest, as I have also been able to get it to function on XEN that ships with SLES.
>>
>> --
>> Allen Beddingfield
>> Systems Engineer
>> The University of Alabama
>> ________________________________
>> From: Darren Thompson [darrent at akurit.com.au]
>> Sent: Wednesday, June 25, 2014 3:55 PM
>> To: Beddingfield, Allen
>> Cc: sles-beta at lists.suse.com
>> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
>> Allen
>>
>> That is an odd/interesting result since I have been testing SLES12B7+ on it's included XEN hypervisor and it works fine, so it's not an intrinsic problem with running under a XEN hypervisor.
>>
>> Darren
>>
>>
>> On 26 June 2014 06:47, Beddingfield, Allen <allen at ua.edu<mailto:allen at ua.edu>> wrote:
>> Will SLES 12 be supported by SUSE as a guest operating system on Citrix XenServer?  SLES 11 works beautifully.  I have not been able to get a working installation of any of the betas on there using a SLES template. If I use the "other install media" template, I can get a functioning HVM install, but if I use one of the proper templates for paravirtualization, I cannot get a working install.  Obviously, the HVM is an inefficient virtualization method on Xen, and is not recommended.
>>
>> So my questions are:
>> 1.  Will XenServer be supported, either officially or best-effort?
>> 2.  Has any effort been put into testing SLES 12 as a XenServer guest?
>> 3.  Has anyone gotten it to work as a paravirtualized guest? (I can make it work HVM)
>>
>> I have a full multi-node XenServer configuration running 6.2.x, and would be glad to offer whatever assistance is needed with testing/troubleshooting this.
>>
>> Thanks.
>> Allen B.
>>
>> --
>> Allen Beddingfield
>> Systems Engineer
>> The University of Alabama
>> _______________________________________________
>> sles-beta mailing list
>> sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
>> http://lists.suse.com/mailman/listinfo/sles-beta
>>
>>
>>
>> --
>>
>> 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/>
>> <image003.jpg>
>> <Part.002>
>
> _______________________________________________
> 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
>


From jdouglas at suse.com  Wed Jun 25 23:47:35 2014
From: jdouglas at suse.com (Jason Douglas)
Date: Wed, 25 Jun 2014 23:47:35 -0600
Subject: [sles-beta] Support status for Citrix XenServer?
In-Reply-To: <AAD7066EC17A5541BF5145CD44BEFA7201004603E8@EX10MBN02.ua-net.ua.edu>
References: <AAD7066EC17A5541BF5145CD44BEFA72010046003C@EX10MBN02.ua-net.ua.edu>,
	<CAEUhfEeDJTefZ30k5i38ctJWnHoOJdMNV7aConSA5ZpYAnfBYA@mail.gmail.com>
	<AAD7066EC17A5541BF5145CD44BEFA72010046006D@EX10MBN02.ua-net.ua.edu>,
	<53AAEAE80200006F000FF8EF@prv-mh.provo.novell.com>,
	<AAD7066EC17A5541BF5145CD44BEFA7201004600E0@EX10MBN02.ua-net.ua.edu>
	<AAD7066EC17A5541BF5145CD44BEFA72010046010F@EX10MBN02.ua-net.ua.edu>,
	<53AAFFFF0200006F000FF900@prv-mh.provo.novell.com>
	<AAD7066EC17A5541BF5145CD44BEFA7201004603E8@EX10MBN02.ua-net.ua.edu>
Message-ID: <53AB5FB10200006F000FF912@prv-mh.provo.novell.com>

Ok, so I misread your explanation. You're right that it's not likely a grub error. Opening an SR sounds like the right next step. We can figure out which logs to grab as part of that process. Thanks. 

Jason

> On Jun 25, 2014, at 10:29 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
> 
> I would have thought that a grub issue would stop it cold before anything was loaded from disk...maybe just presenting a blinking cursor.  With this, it looks like it is getting past the bootloader.
> If there are any logs/info I can provide from the XenServer host or if I can figure out how to get them off of the guest os, I will be glad to.
> Should I open an SR for this?
> Allen B.
> --
> Allen Beddingfield
> Systems Engineer
> The University of Alabama
> 
> ________________________________________
> From: Jason Douglas [jdouglas at suse.com]
> Sent: Wednesday, June 25, 2014 5:59 PM
> To: Beddingfield, Allen
> Cc: sles-beta at lists.suse.com
> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?> 
> To me it seems like grub2 is the most likely culprit. We will need to work with Citrix to see what support they can add to accommodate it.
> 
> Jason
> 
>> On Jun 25, 2014, at 3:41 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
>> 
>> Oh, I forgot to mention - the filesystem is partitioned as follows:
>> 
>> 1 gb ext3 /boot
>> 2 gb swap
>> remainder XFS / filesystem
>> --
>> Allen Beddingfield
>> Systems Engineer
>> The University of Alabama
>> 
>> ________________________________________
>> From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Beddingfield, Allen [allen at ua.edu]
>> Sent: Wednesday, June 25, 2014 4:33 PM
>> To: Jason Douglas; sles-beta at lists.suse.com
>> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
>> The installation goes off with no problem.  There are no errors or issues.
>> On final reboot, the last three lines seen on the screen are:
>> 
>> Linux agpgart interface v0.103
>> Xen virtual console successfully install on ttyS0
>> i8042:  PNP:  No PS/2 controller found.  Probing ports directly.
>> 
>> At this point, it not only stops, but the VM actually powers off.
>> 
>> Allen B.
>> --
>> Allen Beddingfield
>> Systems Engineer
>> The University of Alabama
>> 
>> ________________________________________
>> From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Jason Douglas [jdouglas at suse.com]
>> Sent: Wednesday, June 25, 2014 4:29 PM
>> To: sles-beta at lists.suse.com
>> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
>> Hi Allen,
>> 
>> The goal is to fully support SLES 12 as a guest on Citrix XenServer. However, I don't know if any testing has been done internally yet.
>> 
>> Where are you encountering issues? Is it before, during, or after the installation? There are few things that immediately come to mind if the issue  is trying to start the VM following the install:
>> 
>> 1.  SLES 12 uses grub2 as it's bootloader. I'm not sure if Citrix XenServer supports that in a PV VM.
>> 
>> 2. The default root file system is btrfs. I'm fairly confident that Citrix XenServer doesn't support that.
>> 
>> Could either of these issues be the problem you're seeing? If it's grub2 that's causing the problem, I'm not sure how to workaround the issue, but if it's btrfs, you should be able to select a different root file system, or create a separate boot partition, to see if that allows the VM to boot.
>> 
>> It's probably a good idea to formalize this issue via your normal beta processes so that the appropriate bugzilla entries get created.
>> 
>> Thanks!
>> 
>> Jason
>> 
>>> On Jun 25, 2014, at 2:58 PM, "Beddingfield, Allen" <allen at ua.edu> wrote:
>>> 
>>> I think it is specific to Citrix XenServer, and not an issue with running as a XEN guest, as I have also been able to get it to function on XEN that ships with SLES.
>>> 
>>> --
>>> Allen Beddingfield
>>> Systems Engineer
>>> The University of Alabama
>>> ________________________________
>>> From: Darren Thompson [darrent at akurit.com.au]
>>> Sent: Wednesday, June 25, 2014 3:55 PM
>>> To: Beddingfield, Allen
>>> Cc: sles-beta at lists.suse.com
>>> Subject: =?utf-8?B?UmU6IFtzbGVzLWJldGFdIFN1cHBvcnQgc3RhdHVzIGZvciBDaXRyaXggWGVuU2VydmVyPw====?>
>>> Allen
>>> 
>>> That is an odd/interesting result since I have been testing SLES12B7+ on it's included XEN hypervisor and it works fine, so it's not an intrinsic problem with running under a XEN hypervisor.
>>> 
>>> Darren
>>> 
>>> 
>>> On 26 June 2014 06:47, Beddingfield, Allen <allen at ua.edu<mailto:allen at ua.edu>> wrote:
>>> Will SLES 12 be supported by SUSE as a guest operating system on Citrix XenServer?  SLES 11 works beautifully.  I have not been able to get a working installation of any of the betas on there using a SLES template. If I use the "other install media" template, I can get a functioning HVM install, but if I use one of the proper templates for paravirtualization, I cannot get a working install.  Obviously, the HVM is an inefficient virtualization method on Xen, and is not recommended.
>>> 
>>> So my questions are:
>>> 1.  Will XenServer be supported, either officially or best-effort?
>>> 2.  Has any effort been put into testing SLES 12 as a XenServer guest?
>>> 3.  Has anyone gotten it to work as a paravirtualized guest? (I can make it work HVM)
>>> 
>>> I have a full multi-node XenServer configuration running 6.2.x, and would be glad to offer whatever assistance is needed with testing/troubleshooting this.
>>> 
>>> Thanks.
>>> Allen B.
>>> 
>>> --
>>> Allen Beddingfield
>>> Systems Engineer
>>> The University of Alabama
>>> _______________________________________________
>>> sles-beta mailing list
>>> sles-beta at lists.suse.com<mailto:sles-beta at lists.suse.com>
>>> http://lists.suse.com/mailman/listinfo/sles-beta
>>> 
>>> 
>>> 
>>> --
>>> 
>>> 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/>
>>> <image003.jpg>
>>> <Part.002>
>> 
>> _______________________________________________
>> 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
> 
> 


From jsrain at suse.cz  Thu Jun 26 00:23:51 2014
From: jsrain at suse.cz (Jiri Srain)
Date: Thu, 26 Jun 2014 08:23:51 +0200
Subject: [sles-beta] Installation with SMT
In-Reply-To: <dfa6a334abf442e6b6923e129d957af6@LGNMSXA01.prod.bk.dfs>
References: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>
	<53A96A1B.4040000@suse.cz>
	<dfa6a334abf442e6b6923e129d957af6@LGNMSXA01.prod.bk.dfs>
Message-ID: <53ABBC77.6040406@suse.cz>

On 06/24/2014 04:36 PM, Datacenter/DFS wrote:
> Hello again,
>
> thank you Jiri.
>
>>> we had installed the new SMT (beta) on a SLES11 SP3. We configured SMT to
>> mirror SLES12 pool+updates.
>>>
>>> Now we are about to install a fresh SLES12 beta8 and want to register it to the
>> SMT _before_ installation (that's a new sles12 feature).
>
> we moved on to beta9 but the issue is the same.

With Beta9, you cannot register against SMT at all (yet). I'm preparing 
another update of SMT as well as a DUD for Beta9, which will allow that. 
The reason is an update of the registration protocol.

>>> Therefore the Registration Page in Yast provides the ability to configure network
>> (ip, dns, gateway) right at the beginning of the installation process (Button upper
>> right "Network Configuration").
>>>
>>> The Registration Page further asks for "Email" and "Registration Code".
>>> When proceeding with or without entering any Email/RegCode the system seems
>> to try to contact nu.novell.com (though I did not confirm this) - popup "Contacting
>> Registration Server". After a timeout I get an error since our systems do not have
>> internet access - popup "Error Registration Failed".
>>>
>>> Following Questions:
>>> How can one enter a local SMT server?
>>
>> Just put the registratioan URL, like
>> regurl=http://<hostname>/connect
>> to the AutoYaST profile to the registration section, see
>>
>> https://github.com/yast/yast-registration/blob/master/src/autoyast-
>> rnc/registration.rnc#L22
>
> Sorry, that Link does not help. I'm not a YaST developer :-)

You should be able to access that URL - it is public accessible.

> Where exactly do I put the regurl=... line? On the boot prompt or in the xml file (see also last question below)?

You should add the regurl=... to the kernel command-lien at boot.

> I think for a *manual* installation the YaST "Registration Page" shall have the ability to enter a local SMT.

We are aware of this request and according to bzilla, it should be 
possible from RC1 (not reviewed the real status yet, though)

> As I saw with Wireshark Yast tries to find a local SMT by sending SLP requests. But in our environment (as well as in many others) this fails due no multicast routing.
>
>
>>> How would one configure a proxy to contact either local SMT or nu.novell.com?
>>
>> Don't understand this question...
>
> With the ability to configure network at the beginning of the (manual) installation there should also be the ability to configure a proxy server for http requests (to the internet (e.g. nu.novell.com) or the SMT - whatever is desired).
>
> Simon Flood pointed out that the proxy can be configured either on boot prompt or per autoyast.xml but it should also to be done by the interactive YaST installation, otherwise the "Network Configuration" button on the register page makes only half sense - consider this a feature request ;-)
>
> I am going to test if the proxy settings from autoyast.xml are configured before registering.
>
>
>>> How is the network PRE-configured with autoyast.xml?
>>
>> You can put the network configuration to the AutoYaST profile, via the
>> <networking> section.
>
> This does not seem to work (perhaps a bug?). The items in the <networking/> section are ignored in YaST's early stage.
>
> The network settings also do not work after the installation is finished but that's another story.
> The problem seems to be that systemd does not start wicked by default.
> I do not know whether wicked and system are also used in YaST's early stage.
>
>
> This is my autoyast.xml <networking/> extract:
>
> <networking>
> <dhcp_options>
> <dhclient_client_id/><dhclient_hostname_option>AUTO</dhclient_hostname_option>
> </dhcp_options>
> <dns>
> <dhcp_hostname config:type="boolean">false</dhcp_hostname>
> <domain>ddddddddd</domain>
> <!-- hostname wird ggf durch ask ersetzt -->
> <hostname>vm11</hostname>
> <nameservers config:type="list"><nameserver>10.247.64.11</nameserver><nameserver>10.247.160.1</nameserver></nameservers>
> <resolv_conf_policy>auto</resolv_conf_policy>
> <searchlist config:type="list"><search>ddddddddd</search></searchlist>
> </dns>
> <interfaces config:type="list">
> <interface>
> <bootproto>static</bootproto>
> <device>eth0</device>
> <!-- ipaddr wird ggf durch ask ersetzt -->
> <ipaddr>10.247.74.41</ipaddr>
> <netmask>255.255.255.0</netmask>
> <startmode>auto</startmode>
> </interface>
> [...loopback...]
> </interfaces>
> <ipv6 config:type="boolean">true</ipv6>
> <keep_install_network config:type="boolean">false</keep_install_network>
> <managed config:type="boolean">false</managed>
> <routing>
> <ipv4_forward config:type="boolean">false</ipv4_forward>
> <ipv6_forward config:type="boolean">false</ipv6_forward>
> <routes config:type="list">
> <route>
> <destination>default</destination><device>-</device>
> <!-- gateway wird ggf durch ask ersetzt -->
> <gateway>10.247.127.254</gateway>
> <netmask>-</netmask>
> </route>
> </routes>
> </routing>
> </networking>
>
>
>>> How is the SMT registration configured with autoyast.xml?
>>
>> See above.
>
> Could you provide an example autoyast.xml extract? Thank you very much.

I don't have any available, Ladislav, could you, please, help and 
provide a registration snippet for AutoYaST?

Thanks,
   Jiri

>
> Regards,
> Ronny
>
>
>
>
> DFS Deutsche Flugsicherung GmbH
> Am DFS-Campus
> D - 63225 Langen
>
> Tel.: +49-(0)6103-707-0
>
> Sitz der Gesellschaft: Langen/Hessen
> Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977
> Vorsitzender des Aufsichtsrates: Michael Odenwald
> Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann
>
> Internet: http://www.dfs.de
> Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc <http://www.dfs.de/dfs/public_key.asc>
>


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com

From fcrozat at suse.com  Thu Jun 26 02:05:16 2014
From: fcrozat at suse.com (Frederic Crozat)
Date: Thu, 26 Jun 2014 10:05:16 +0200
Subject: [sles-beta] SR 10884981671
In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D5384F474@hqmbx6.eur.ad.sag>
References: <46AC8C81C10B8C48820201DF2AE1D76D5384F474@hqmbx6.eur.ad.sag>
Message-ID: <1403769916.7716.18.camel@par-r81vxc7.par.novell.com>

Le lundi 23 juin 2014 ? 17:08 +0000, Waite, Dick a ?crit :
> Grand Evening,
> 
>     Update / Upgrade from SLES 11-SP3 to SLES 12-Beta9 running on
> VMware Workstation 10-0-2 x86_64
> 
> "SLES12-Beta9. New Install went Okay on VMware Workstation 10-0-2
> Update from SLE11-SP-3 went better but something like "Python-Bonobo*
> needed a hand job. That did seem to work but I had no mouse control
> over the display. I could get into text mode with Cntl_Alt_F2 and I
> took some screenShots. I did try and copy /var/logs/* to a USB but one
> does not "see" the USB. I have noted the VMware update Tools giving a
> lot of nags. Should I try and update VMware Tools or is that part of
> SLES now?"

VMare tools are now part of SLES12. 

For upgrade, "default" install upgrade should work out of the box.
Upgrade with SDK or with full installation are still being fixed.

>     I have noted in the past that the Gnome Shell does run with a high
> CPU usage ... My New Install on the above ran Okay, but while working
> on another machine I took some screenshots of the SLES 12-Beta9 doing
> no work but the CPU seems to be very high. maybe that is the way Gnome
> works, ???? maybe that is Okay but that would cost the users a lot on
> pennies eating that amount of CPU on a zlinux. It seem to be wanting
> to do something, but there was nothing to do that I could see. Never
> used Gnome before so bit of a loss as to what diagnostics to take,
> comments very welcome, use KDE would be very welcome ;o)

You are running both top and gnome-system-monitor on the same system you
are measuring, which are causing the compositor to be activate. It would
be better to run top using ssh and check on a "inactive" (nothing
refreshing the screen) desktop, to check if it is using CPU or not. And
you are not giving any hint on which system you are using. 

(Hint: try to use a descriptive subject to your email, I almost missed
your email due to its subject).
> 
> __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
>                                    
>                                    
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta


-- 
Frederic Crozat
Project Manager Enterprise Desktop
SUSE


From jsmeix at suse.de  Thu Jun 26 03:28:04 2014
From: jsmeix at suse.de (Johannes Meixner)
Date: Thu, 26 Jun 2014 11:28:04 +0200 (CEST)
Subject: [sles-beta] Who had tested SLE12 at the application level?
Message-ID: <alpine.LNX.2.00.1406261051400.4291@nelson.suse.de>


Hello,

in general I would like to know to what extent SLE12 was tested
at the application level and in particular I am interested in
the base printing system (CUPS, Ghostscript, printer drivers,...).

On Thu, 26 Jun 2014 07:02:14 +1000 Darren Thompson wrote (excerpt):
---------------------------------------------------------------------
Subject: ... Opinion: It's too soon to leave beta and go to RC level
...
I have not yet begun testing migration sceneries or done any
sociability/stability testing of at the application level.
..
Is just that I'm a laggard or are other finding that SLES12 is still
not ready for testing furter up the application stack yet?
---------------------------------------------------------------------
and
on Wed, 25 Jun 2014 21:49:33 +0000 Waite Dick wrote (excerpt):
---------------------------------------------------------------------
I have not run any of our applications on SLES12 yet.
---------------------------------------------------------------------

I am a bit worried now because I am in particular interested
that the base printing system was tested to get at least feedback
by real users "out there".

There are major incompatible changes in the printing system.
See the SLE12 release notes and for details see in particular
https://bugzilla.novell.com/show_bug.cgi?id=735404
and follow the links therein.

You cannot "just upgrade" a SLE11 CUPS server to SLE12 and
expect that afterwards printing "just works as before".

Or am I overanxious and "Printing" is not (or not yet?)
of real importance?


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

From gahorvath at novell.com  Thu Jun 26 03:48:17 2014
From: gahorvath at novell.com (Gabor K Horvath)
Date: Thu, 26 Jun 2014 11:48:17 +0200
Subject: [sles-beta] SLES12 beta9 setting default runlevel to 3
In-Reply-To: <9EFA2F6E-11B1-4604-81C2-8429A4DC9906@akurit.com.au>
References: <53AAF4D0.6030105@novell.com>
	<9EFA2F6E-11B1-4604-81C2-8429A4DC9906@akurit.com.au>
Message-ID: <53ABEC61.2020502@novell.com>

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


Thanks for the info.
It actually works with -f and multi-user.target

It still doesn't change the fact that yast2 services shows none of
these potential targets, except when they are the default.

le12:~ # systemctl -f set-default graphical.target
sle12:~ # yast2 services
# now graphical target show up in the selection list of default targets
sle12:~ # systemctl -f set-default multi-user.target
sle12:~ # yast2 services
# now multi user target show up in the selection list of default
targets, but graphical target is gone.

This effectively means you can't switch to multi-user using Yast.

g.



On 06/25/2014 10:07 PM, Darren Thompson (AkurIT) wrote:
> It's not the cause of the fault but the correct target to use for
> non GUI is multiple-user.target
> 
> I sent a few emails about how to change between default targets
> fairly recently.
> 
> Sent from my iPhone
> 
> On 26/06/2014, at 2:12, Gabor K Horvath <gahorvath at novell.com>
> wrote:
> 
> Hi All,
> 
> I was trying to get rid of the running X11.
> 
> # systemctl set-default runlevel3.target # Failed to set default
> target: No such file or directory # cd /etc/systemd # ln -sf
> /usr/lib/systemd/system/runlevel3.target default.target
> 
> Then back to graphical:
> 
> # systemctl set-default graphical.target Failed to set default
> target: File exists # rm /etc/systemd/default.target # systemctl
> set-default graphical.target #
> 
> Umm... Am I missing something? Also the runlevel modul in yast
> doesn't show the runlevel targets.
> 
> g.
> 
>> _______________________________________________ sles-beta mailing
>> list sles-beta at lists.suse.com 
>> http://lists.suse.com/mailman/listinfo/sles-beta
> 

- -- 
Horv?th G?bor K?lm?n
vezet? konzult?ns
H-1124 Budapest, Cs?rsz u. 45., MOM Park, Sas torony
+36 1 489 4600, +36 30 326 1064
gabor.horvath at npsh.hu
NetIQ - Novell - SUSE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTq+xhAAoJEJG2j9wDrSONyIsH/2uUnwpf5TQ3crmFg7/utJa8
i80dJ7OGGwRb9+Its3fqEFdTd3MUGNjhmaTFdm21T5/IgpbD3+sdCWeI0NvG0zaJ
t/NTR54UxdfUu/nSHVFqoXTT79YU4wboPG23wX14AHXIXfsRNWaewMSY2Uokix8/
GMoZsHIay334v6SwKs1R7TxVmXs+wDpI5jmFCWs3CUFmhyPjYF2wLEB9kXMyRMWy
+HZtcDf4xKqzGBvVpODN91If4Xj7zzrDO1/8uKRDfUQ5gZraFbAdCYRoqKtSga5e
vixV0+dRkkXuTCFdzkKN6WuFwAKN/3UK7Or719d2XKWxMlMg75QdzMrLgt5Dwkc=
=IFoq
-----END PGP SIGNATURE-----

From S.M.Flood at ucs.cam.ac.uk  Thu Jun 26 04:26:39 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Thu, 26 Jun 2014 11:26:39 +0100
Subject: [sles-beta] SLES 12 for VMware?
Message-ID: <53ABF55F.5090700@ucs.cam.ac.uk>

Given VMware's End of Availability announcement of SLES for VMware[1] am 
I right in thinking that there won't be a SLES 12 for VMware?

I'm also guessing that the upgrade path from SLES 11 for VMware to SLES 
12 will be via SLES 11 (not for VMware) in which case TID 7015096[2] 
would seem applicable.

Thanks,
Simon

[1] 
http://blogs.vmware.com/vsphere/2014/06/sles-vmware-end-availability-announcement.html
[2] https://www.novell.com/support/kb/doc.php?id=7015096
-- 
Simon Flood
Senior Systems Specialist
University of Cambridge
United Kingdom

Novell/SUSE/NetIQ Knowledge Partner

From fcrozat at suse.com  Thu Jun 26 04:45:43 2014
From: fcrozat at suse.com (Frederic Crozat)
Date: Thu, 26 Jun 2014 12:45:43 +0200
Subject: [sles-beta] SLES12 beta9 setting default runlevel to 3
In-Reply-To: <53ABEC61.2020502@novell.com>
References: <53AAF4D0.6030105@novell.com>
	<9EFA2F6E-11B1-4604-81C2-8429A4DC9906@akurit.com.au>
	<53ABEC61.2020502@novell.com>
Message-ID: <1403779543.7716.32.camel@par-r81vxc7.par.novell.com>

Le jeudi 26 juin 2014 ? 11:48 +0200, Gabor K Horvath a ?crit :
> Thanks for the info.
> It actually works with -f and multi-user.target
> 
> It still doesn't change the fact that yast2 services shows none of
> these potential targets, except when they are the default.

> le12:~ # systemctl -f set-default graphical.target
> sle12:~ # yast2 services
> # now graphical target show up in the selection list of default targets
> sle12:~ # systemctl -f set-default multi-user.target
> sle12:~ # yast2 services
> # now multi user target show up in the selection list of default
> targets, but graphical target is gone.
> 
> This effectively means you can't switch to multi-user using Yast.

We have a bug report for that (bnc#867759) which is targeted for being
fixed for RC1.


-- 
Frederic Crozat
Project Manager Enterprise Desktop
SUSE


From Joerg.Reisenweber at btc-it-services.com  Thu Jun 26 04:49:05 2014
From: Joerg.Reisenweber at btc-it-services.com (Joerg.Reisenweber at btc-it-services.com)
Date: Thu, 26 Jun 2014 12:49:05 +0200
Subject: [sles-beta] Installation with SMT
In-Reply-To: <53ABBC77.6040406@suse.cz>
References: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>
	<53A96A1B.4040000@suse.cz>
	<dfa6a334abf442e6b6923e129d957af6@LGNMSXA01.prod.bk.dfs>
	<53ABBC77.6040406@suse.cz>
Message-ID: <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0DC7AC07@OLCA9095.btcnet.btc-ag.com>

Hi,

here's our SMT registration snippet:

  <suse_register>
    <do_registration config:type="boolean">true</do_registration>
    <reg_server>https://IPADDR/center/regsvc/</reg_server>
    <reg_server_cert></reg_server_cert>
    <register_regularly config:type="boolean">true</register_regularly>
    <registration_data/>
    <submit_hwdata config:type="boolean">true</submit_hwdata>
    <submit_optional config:type="boolean">true</submit_optional>
  </suse_register>

I don't know if this is still compatible with SLES 12. Give it a try.

J?rg

-----Urspr?ngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Jiri Srain
Gesendet: Donnerstag, 26. Juni 2014 08:24
An: Datacenter/DFS; sles-beta at lists.suse.com; Ladislav Slezak
Betreff: Re: [sles-beta] Installation with SMT

On 06/24/2014 04:36 PM, Datacenter/DFS wrote:

>>> How is the SMT registration configured with autoyast.xml?
>>
>> See above.
>
> Could you provide an example autoyast.xml extract? Thank you very much.

I don't have any available, Ladislav, could you, please, help and provide a registration snippet for AutoYaST?



From lslezak at suse.cz  Thu Jun 26 05:23:03 2014
From: lslezak at suse.cz (Ladislav Slezak)
Date: Thu, 26 Jun 2014 13:23:03 +0200
Subject: [sles-beta] Installation with SMT
In-Reply-To: <20140624173240.0a290e2d@dhcp150.suse.cz>
References: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>	<53A96A1B.4040000@suse.cz>	<dfa6a334abf442e6b6923e129d957af6@LGNMSXA01.prod.bk.dfs>	<53A995AF.2080407@suse.de>	<a9780bc3fe734f5f9bbd5ad2d556b41e@LGNMSXA01.prod.bk.dfs>
	<20140624173240.0a290e2d@dhcp150.suse.cz>
Message-ID: <53AC0297.4090200@suse.cz>

Dne 24.6.2014 17:32, Josef Reidinger napsal(a):
> On Tue, 24 Jun 2014 15:23:40 +0000
> "Datacenter/DFS" <Datacenter at dfs.de> wrote:
[...]
>> Luckily when installing manually and configuring the network in the
>> early stage, networking works. Yet I cannot enter a local SMT
>> manually.
>
> It is possible with boot parameter. Just when DVD came up and you
> choose installation write to parameter line (similar like you specify
> e.g. autoyast profile): regurl=http://<mysmt>

JFYI: In RC1 there will be a new "Local Registration Server" button in the 
registration dialog which allows to enter the SMT URL without need for using
an extra boot parameter.


--

Best Regards

Ladislav Slez?k
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o.                              e-mail: lslezak at suse.cz
Lihovarsk? 1060/12                              tel: +420 284 028 960
190 00 Prague 9                                 fax: +420 284 028 951
Czech Republic                                  http://www.suse.cz/

From meissner at suse.de  Thu Jun 26 05:30:26 2014
From: meissner at suse.de (Marcus Meissner)
Date: Thu, 26 Jun 2014 13:30:26 +0200
Subject: [sles-beta] SLES 12 for VMware?
In-Reply-To: <53ABF55F.5090700@ucs.cam.ac.uk>
References: <53ABF55F.5090700@ucs.cam.ac.uk>
Message-ID: <20140626113026.GC9105@suse.de>

On Thu, Jun 26, 2014 at 11:26:39AM +0100, Simon Flood wrote:
> Given VMware's End of Availability announcement of SLES for VMware[1] am I 
> right in thinking that there won't be a SLES 12 for VMware?
>
> I'm also guessing that the upgrade path from SLES 11 for VMware to SLES 12 
> will be via SLES 11 (not for VMware) in which case TID 7015096[2] would 
> seem applicable.
>
> Thanks,
> Simon
>
> [1] 
> http://blogs.vmware.com/vsphere/2014/06/sles-vmware-end-availability-announcement.html
> [2] https://www.novell.com/support/kb/doc.php?id=7015096

Judging that vm-tools etc are in the regular SLES 12 betas, VMWare support
will be directly in SLES 12 and not in a seperate product.

But I let the officials fill in.

Ciao, Marcus

From jreidinger at suse.cz  Thu Jun 26 05:31:58 2014
From: jreidinger at suse.cz (Josef Reidinger)
Date: Thu, 26 Jun 2014 13:31:58 +0200
Subject: [sles-beta] Installation with SMT
In-Reply-To: <6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0DC7AC07@OLCA9095.btcnet.btc-ag.com>
References: <d3ed21ed5fd04a1fa6db1f479241d540@LGNMSXA02.prod.bk.dfs>
	<53A96A1B.4040000@suse.cz>
	<dfa6a334abf442e6b6923e129d957af6@LGNMSXA01.prod.bk.dfs>
	<53ABBC77.6040406@suse.cz>
	<6FCF9F3FA7310B4B9AA1A975F4C4A54B4C0DC7AC07@OLCA9095.btcnet.btc-ag.com>
Message-ID: <20140626133158.58222d6f@dhcp150.suse.cz>

On Thu, 26 Jun 2014 12:49:05 +0200
<Joerg.Reisenweber at btc-it-services.com> wrote:

> Hi,
> 
> here's our SMT registration snippet:
> 
>   <suse_register>
>     <do_registration config:type="boolean">true</do_registration>
>     <reg_server>https://IPADDR/center/regsvc/</reg_server>
>     <reg_server_cert></reg_server_cert>
>     <register_regularly
> config:type="boolean">true</register_regularly> <registration_data/>
>     <submit_hwdata config:type="boolean">true</submit_hwdata>
>     <submit_optional config:type="boolean">true</submit_optional>
>   </suse_register>
> 
> I don't know if this is still compatible with SLES 12. Give it a try.
> 
> J?rg

Hi,
I compare it with our schema in yast2-registration and few keys are not
longer handled:
- register_regularly
- submit_hwdata
- submit_optional
- registration_data

and the other hand there is new keys:
- email ( email you pass in dialog )
- reg_code ( regcode for base product )
- install_updates ( boolean to provide answer for dialog if install
  with online update repositories )
- slp_discovery ( if yast should use slp to discover server )
- addons ( to specify addons )


so snippet can look like ( note that we are still in beta and can be
changed. We will definitivelly change addon subtree part as there is still some missing attributes )

  <suse_register>
    <do_registration config:type="boolean">true</do_registration>
    <reg_server>https://mysmt</reg_server>
    <reg_server_cert>text of our own certificate</reg_server_cert>
    <email>jreidinger at suse.com</email>
    <regcode>my secret SLES regcode</regcode>
    <install_updates config:type="boolean">true</install_updates>
    <slp_discovery config:type="boolean">false</slp_discovery>
    <addons>
      <addon>
        <name>addon name</name>
        <regcode>addon regcode</regcode>
      </addon>
    </addons>
  </suse_register>


if you have trouble do not hesitate to write it.

Thanks
Josef

From kukuk at suse.de  Thu Jun 26 05:47:44 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Thu, 26 Jun 2014 13:47:44 +0200
Subject: [sles-beta] SLES 12 for VMware?
In-Reply-To: <53ABF55F.5090700@ucs.cam.ac.uk>
References: <53ABF55F.5090700@ucs.cam.ac.uk>
Message-ID: <20140626114744.GA10541@suse.de>

On Thu, Jun 26, Simon Flood wrote:

> Given VMware's End of Availability announcement of SLES for VMware[1] am I 
> right in thinking that there won't be a SLES 12 for VMware?

Correct.

> I'm also guessing that the upgrade path from SLES 11 for VMware to SLES 12 
> will be via SLES 11 (not for VMware) in which case TID 7015096[2] would 
> seem applicable.

Direct upgrade from SLES 11 for VMware SP3 to SLES 12 should
work.

  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 kdupke at suse.com  Thu Jun 26 06:03:27 2014
From: kdupke at suse.com (Kai Dupke)
Date: Thu, 26 Jun 2014 14:03:27 +0200
Subject: [sles-beta] SLES 12 for VMware?
In-Reply-To: <53ABF55F.5090700@ucs.cam.ac.uk>
References: <53ABF55F.5090700@ucs.cam.ac.uk>
Message-ID: <53AC0C0F.9050106@suse.com>

On 06/26/2014 12:26 PM, Simon Flood wrote:
> Given VMware's End of Availability announcement of SLES for VMware[1] am
> I right in thinking that there won't be a SLES 12 for VMware?

We will continue to work with VMware with respect to technical and
business cooperation, but yes, we will not do a SLES 12 for VMware.

> I'm also guessing that the upgrade path from SLES 11 for VMware to SLES
> 12 will be via SLES 11 (not for VMware) in which case TID 7015096[2]
> would seem applicable.

You should be able to upgrade a SLES 11 SP3 for VMware system to SLES 12
just by using the SLES 12 media.

Of course you need a SLES activation code to get access to the SLES
channels.

greetings
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 allen at ua.edu  Thu Jun 26 13:44:28 2014
From: allen at ua.edu (Beddingfield, Allen)
Date: Thu, 26 Jun 2014 19:44:28 +0000
Subject: [sles-beta] Question about submitting an SR
Message-ID: <AAD7066EC17A5541BF5145CD44BEFA720100461B2E@EX10MBN02.ua-net.ua.edu>

When I go to submit an SR, I'm only presented with the options for our entitled products purchased from SUSE.  There is not a separate drop down option for SLE 12 beta.  Should there be, or should I just put it under our regular SLES listing?
Thanks.
Allen B.

--
Allen Beddingfield
Systems Engineer
The University of Alabama

From mpost at suse.com  Thu Jun 26 14:26:54 2014
From: mpost at suse.com (Mark Post)
Date: Thu, 26 Jun 2014 14:26:54 -0600
Subject: [sles-beta] LVM commands in SLES12 doesn't print any message
 after successful exection
In-Reply-To: <E88C7447D32D254EBA7AA7789F2D2A4A145AE72D4D@APJ1XCHEVSPIN35.SYMC.SYMANTEC.COM>
References: <E88C7447D32D254EBA7AA7789F2D2A4A145AE72D4D@APJ1XCHEVSPIN35.SYMC.SYMANTEC.COM>
Message-ID: <53AC49CE0200006D00166CD6@prv-mh.provo.novell.com>

>>> On 6/26/2014 at 05:05 AM, Nikita Kodkani <Nikita_Kodkani at symantec.com> wrote: 
> Hi,
> 
> I want to create the physical volumes using pvcreate command & then view them 
> using pvscan command.

The pvscan command was never intended to _display_ physical volumes.  It was intended to discover them.  The pvdisplay command, or "pvs" command should be used to display the physical volume(s).

s390vsl210:~ # pvdisplay 
  "/dev/dasdb1" is a new physical volume of "210.84 MiB"
  --- NEW Physical volume ---
  PV Name               /dev/dasdb1
  VG Name               
  PV Size               210.84 MiB
  Allocatable           NO
  PE Size               0   
  Total PE              0
  Free PE               0
  Allocated PE          0
  PV UUID               GHS9GV-Nkg3-MFQW-aCo0-DWoq-c1QX-CFBYp5
   
s390vsl210:~ # pvs
  PV          VG   Fmt  Attr PSize   PFree  
  /dev/dasdb1      lvm2 a--  210.84m 210.84m

-snip-
> Just a query, will these changes made in LVM commands be persistent in 
> SLES12 GA as well?

I would have to say yes.

> [root ~]# pvcreate /dev/sdc
>   Physical volume "/dev/sdc" successfully created
> [root ~]# pvscan /dev/sdc
>   Found duplicate PV a07tWNxVkvsmQ1hsSXAmn5VmjqLND0Ay: using /dev/sdb1 not 
> /dev/sdb
>   Found duplicate PV a07tWNxVkvsmQ1hsSXAmn5VmjqLND0Ay: using /dev/sdb3 not 
> /dev/sdb1
>   Found duplicate PV 8OZWF8UtIPQRXH3EqkNHu7LdnFZ3xZhp: using /dev/sdc3 not 
> /dev/sdc
>   Found duplicate PV a07tWNxVkvsmQ1hsSXAmn5VmjqLND0Ay: using /dev/sdo not 
> /dev/sdb3
>   Found duplicate PV a07tWNxVkvsmQ1hsSXAmn5VmjqLND0Ay: using /dev/sdo3 not 
> /dev/sdo
>   Found duplicate PV 8OZWF8UtIPQRXH3EqkNHu7LdnFZ3xZhp: using /dev/sdp not 
> /dev/sdc3
>   Found duplicate PV 8OZWF8UtIPQRXH3EqkNHu7LdnFZ3xZhp: using /dev/sdp3 not 
> /dev/sdp
>   PV /dev/sdo3                      lvm2 [2.00 GiB]
>   PV /dev/sdp3                      lvm2 [2.00 GiB]
>   Total: 2 [4.00 GiB] / in use: 0 [0   ] / in no VG: 2 [4.00 GiB]

This isn't something you asked about, but it seems pretty clear you have a multipathing environment, but you're not using the multipath names to the PVs.  You should probably fix that.


Mark Post



From uwedr at suse.com  Fri Jun 27 00:06:25 2014
From: uwedr at suse.com (Uwe Drechsel)
Date: Fri, 27 Jun 2014 08:06:25 +0200
Subject: [sles-beta] Question about submitting an SR
In-Reply-To: <AAD7066EC17A5541BF5145CD44BEFA720100461B2E@EX10MBN02.ua-net.ua.edu>
References: <AAD7066EC17A5541BF5145CD44BEFA720100461B2E@EX10MBN02.ua-net.ua.edu>
Message-ID: <20140627060625.GU7146@suse.de>

Allen,

On Thu, Jun 26, Allen Beddingfield wrote:

> When I go to submit an SR, I'm only presented with the options for our
> entitled products purchased from SUSE.  There is not a separate drop
> down option for SLE 12 beta.  Should there be, or should I just put it
> under our regular SLES listing?

Please try again now.

In case of any issues with the SR system, anybody can contact me
directly at beta-programs at lists.suse.com and I work with the support
team to get this fixed.

Thanks
Uwe

--
Uwe Drechsel
Project Manager              
SUSE Linux Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)

From jsrain at suse.cz  Fri Jun 27 05:56:25 2014
From: jsrain at suse.cz (Jiri Srain)
Date: Fri, 27 Jun 2014 13:56:25 +0200
Subject: [sles-beta] Testing SLES12 Beta9 with SMT
Message-ID: <53AD5BE9.9070609@suse.cz>

Dear SLES12 testers,

testing version of SMT, which allows registration of SLES12 Beta9, is 
now available at

   http://beta.suse.com/private/SMT-Beta/

Due to a bug in Beta9, enclosed driver update disk needs to be applied 
in order to register extensions and modules. The instructions are 
included in the README-SCC file, which is available at the URL above.

If you are upgrading from the previous snapshot of SMT, be aware that 
the repository URL has changed and that you need to add the new 
repository and update SMT from it.

The driver update disk is only available for x86_64 clients.

Happy testing and thanks for your feedback!

     The SUSE SMT team.


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com

From urs.frey at post.ch  Fri Jun 27 06:05:53 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Fri, 27 Jun 2014 12:05:53 +0000
Subject: [sles-beta] Testing SLES12 Beta9 with SMT
In-Reply-To: <53AD5BE9.9070609@suse.cz>
References: <53AD5BE9.9070609@suse.cz>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9B5510@HXMB12.pnet.ch>

Hi
Are there only rpm packages?
No ISO one could use as add-on product to install from scratch on SLES11-SP3?
When having only smt-rpm's there will only be a RPM -U possible, no add-on product installation and ssl-certs generation etc.
SMT installation can not be tested.

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 Jiri Srain
Gesendet: Friday, June 27, 2014 1:56 PM
An: sles-beta at lists.suse.com; smt-beta at lists.suse.com
Betreff: [sles-beta] Testing SLES12 Beta9 with SMT

Dear SLES12 testers,

testing version of SMT, which allows registration of SLES12 Beta9, is 
now available at

   http://beta.suse.com/private/SMT-Beta/

Due to a bug in Beta9, enclosed driver update disk needs to be applied 
in order to register extensions and modules. The instructions are 
included in the README-SCC file, which is available at the URL above.

If you are upgrading from the previous snapshot of SMT, be aware that 
the repository URL has changed and that you need to add the new 
repository and update SMT from it.

The driver update disk is only available for x86_64 clients.

Happy testing and thanks for your feedback!

     The SUSE SMT team.


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta

From jsrain at suse.cz  Fri Jun 27 06:21:05 2014
From: jsrain at suse.cz (Jiri Srain)
Date: Fri, 27 Jun 2014 14:21:05 +0200
Subject: [sles-beta] Testing SLES12 Beta9 with SMT
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9B5510@HXMB12.pnet.ch>
References: <53AD5BE9.9070609@suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F9B5510@HXMB12.pnet.ch>
Message-ID: <53AD61B1.4070009@suse.cz>

On 06/27/2014 02:05 PM, urs.frey at post.ch wrote:
> Hi
> Are there only rpm packages?

Yes, there are only RPM packages.

We will not release any ISO even as the final version, there will only 
be an on-line update released for the existing one.

> No ISO one could use as add-on product to install from scratch on SLES11-SP3?
> When having only smt-rpm's there will only be a RPM -U possible, no add-on product installation and ssl-certs generation etc.
> SMT installation can not be tested.

Not really. The README-SCC file describes how to install SMT including 
the update on a fresh SLES installation.

Jiri

>
> 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 Jiri Srain
> Gesendet: Friday, June 27, 2014 1:56 PM
> An: sles-beta at lists.suse.com; smt-beta at lists.suse.com
> Betreff: [sles-beta] Testing SLES12 Beta9 with SMT
>
> Dear SLES12 testers,
>
> testing version of SMT, which allows registration of SLES12 Beta9, is
> now available at
>
>     http://beta.suse.com/private/SMT-Beta/
>
> Due to a bug in Beta9, enclosed driver update disk needs to be applied
> in order to register extensions and modules. The instructions are
> included in the README-SCC file, which is available at the URL above.
>
> If you are upgrading from the previous snapshot of SMT, be aware that
> the repository URL has changed and that you need to add the new
> repository and update SMT from it.
>
> The driver update disk is only available for x86_64 clients.
>
> Happy testing and thanks for your feedback!
>
>       The SUSE SMT team.
>
>


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com

From S.M.Flood at ucs.cam.ac.uk  Fri Jun 27 06:35:37 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Fri, 27 Jun 2014 13:35:37 +0100
Subject: [sles-beta] Testing SLES12 Beta9 with SMT
In-Reply-To: <53AD61B1.4070009@suse.cz>
References: <53AD5BE9.9070609@suse.cz>	<40637DBB36AF3941B243A286A432CA0B0F9B5510@HXMB12.pnet.ch>
	<53AD61B1.4070009@suse.cz>
Message-ID: <53AD6519.7010404@ucs.cam.ac.uk>

On 27/06/2014 13:21, Jiri Srain wrote:

> Yes, there are only RPM packages.
>
> We will not release any ISO even as the final version, there will only
> be an on-line update released for the existing one.

So unlike with SMT11 SP3 it won't be possible to install SLES and then 
SMT to manage SLES12 without jumping through another hoop?

You also seem to suggest that we'll need SLES11 SP3 to host SMT for 
SLES12 and there won't be SMT12 as an add-on for SLES12 like there is 
SMT11 SP3 for SLES11 SP3. Or am I missing something?

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

Novell/SUSE/NetIQ Knowledge Partner

From urs.frey at post.ch  Fri Jun 27 06:45:26 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Fri, 27 Jun 2014 12:45:26 +0000
Subject: [sles-beta] Testing SLES12 Beta9 with SMT
In-Reply-To: <53AD61B1.4070009@suse.cz>
References: <53AD5BE9.9070609@suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F9B5510@HXMB12.pnet.ch>
	<53AD61B1.4070009@suse.cz>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9B554D@HXMB12.pnet.ch>

Hi Jiri
Sorry disagree. 
In the file README_SSC I cannot find anything about an fresh installation of SMT 2-0 on a SLES11-SP3 which does not have any element of SMT installed yet.
SMT-SLES11-SP3 connected to NCC is an add-on product.
To have the wizard running and the ability to register sles11-sp3 enabled one needs to get through the entire configuration and connection stuff including all ssl certs and database.

I know what I am talking about, because I had to newly install an SLE11-SMT-SP3 in a new network zone
And I fell on my nose by first adding only the RPMs in YaST instead of selecting the Subscription Management Tool pattern.
No wizards, no correct ssl certificates, only weird ssl-messages.

To be precise: "from the pdf delivered with SLES11-SP3-smt_en.pdf on the Repository SLE11-SMT-SP3-Pool
 ====
1.2 Installation on Top of an Already Installed System
To install SMT on top of an already-installed base system, follow these steps:

1 Start YaST and select Software > Add-On Product. Then click Add.

2 If you are installing SMT from a local ISO image, select Local ISO Image as the
media type (repository). If you are installing from a different source, such as CD,
NFS, or HTTP, choose the appropriate type. Then click Next.

3 If you are installing from a CD, insert the SMT add-on product CD. If you are
installing from a different source, provide the necessary repository information.

4 Confirm the SMT license agreement and click Next.

5 Click Accept to install the SMT: Subscription Management Tool for SLE pattern.
Depending on the scope of already installed packages, the software manager will
add more packages to resolve all dependencies. Confirm these Automatic Changes
to perform the installation.

6 The SMT Configuration Wizard is launched. See Section 1.3, "SMT Configuration
Wizard" (page 3).
=======

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: Jiri Srain [mailto:jsrain at suse.cz] 
Gesendet: Friday, June 27, 2014 2:21 PM
An: Frey Urs, IT222; sles-beta at lists.suse.com; smt-beta at lists.suse.com
Betreff: Re: AW: [sles-beta] Testing SLES12 Beta9 with SMT

On 06/27/2014 02:05 PM, urs.frey at post.ch wrote:
> Hi
> Are there only rpm packages?

Yes, there are only RPM packages.

We will not release any ISO even as the final version, there will only 
be an on-line update released for the existing one.

> No ISO one could use as add-on product to install from scratch on SLES11-SP3?
> When having only smt-rpm's there will only be a RPM -U possible, no add-on product installation and ssl-certs generation etc.
> SMT installation can not be tested.

Not really. The README-SCC file describes how to install SMT including 
the update on a fresh SLES installation.

Jiri

>
> 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 Jiri Srain
> Gesendet: Friday, June 27, 2014 1:56 PM
> An: sles-beta at lists.suse.com; smt-beta at lists.suse.com
> Betreff: [sles-beta] Testing SLES12 Beta9 with SMT
>
> Dear SLES12 testers,
>
> testing version of SMT, which allows registration of SLES12 Beta9, is
> now available at
>
>     http://beta.suse.com/private/SMT-Beta/
>
> Due to a bug in Beta9, enclosed driver update disk needs to be applied
> in order to register extensions and modules. The instructions are
> included in the README-SCC file, which is available at the URL above.
>
> If you are upgrading from the previous snapshot of SMT, be aware that
> the repository URL has changed and that you need to add the new
> repository and update SMT from it.
>
> The driver update disk is only available for x86_64 clients.
>
> Happy testing and thanks for your feedback!
>
>       The SUSE SMT team.
>
>


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com

From jsrain at suse.cz  Fri Jun 27 06:49:53 2014
From: jsrain at suse.cz (Jiri Srain)
Date: Fri, 27 Jun 2014 14:49:53 +0200
Subject: [sles-beta] Testing SLES12 Beta9 with SMT
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9B554D@HXMB12.pnet.ch>
References: <53AD5BE9.9070609@suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F9B5510@HXMB12.pnet.ch>
	<53AD61B1.4070009@suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F9B554D@HXMB12.pnet.ch>
Message-ID: <53AD6871.50700@suse.cz>

Hi Urs,

the README-SCC file says following:

Installation of SCC-enabled SMT
===============================

Install and register SLES11-SP3. Afterwards, add the beta repository
e.g. via zypper:

   zypper ar <url> SMT-BETA

You can verify that the repository is added correctly and can be
refreshed via

   zypper ref

Then you can follow either via standard installation of SMT (YaST add-on
module, you will need the standard SMT media) or install the packages
manually via zypper. Remember that to satisfy all dependencies, the
standard SMT media is necessary, the BETA repository is not sufficient..
If needed, add it also via zypper for manual installation. If you
install SMT via zypper, run the YaST smt-server module to perform
initial configuration, which includes selecting the registration server
(SCC or NCC).




In other words, you can just add the BETA repository and then follow the 
installation work-flow as described in the SMT documentation.

I will improve the README.

Jiri



On 06/27/2014 02:45 PM, urs.frey at post.ch wrote:
> Hi Jiri
> Sorry disagree.
> In the file README_SSC I cannot find anything about an fresh installation of SMT 2-0 on a SLES11-SP3 which does not have any element of SMT installed yet.
> SMT-SLES11-SP3 connected to NCC is an add-on product.
> To have the wizard running and the ability to register sles11-sp3 enabled one needs to get through the entire configuration and connection stuff including all ssl certs and database.
>
> I know what I am talking about, because I had to newly install an SLE11-SMT-SP3 in a new network zone
> And I fell on my nose by first adding only the RPMs in YaST instead of selecting the Subscription Management Tool pattern.
> No wizards, no correct ssl certificates, only weird ssl-messages.
>
> To be precise: "from the pdf delivered with SLES11-SP3-smt_en.pdf on the Repository SLE11-SMT-SP3-Pool
>   ====
> 1.2 Installation on Top of an Already Installed System
> To install SMT on top of an already-installed base system, follow these steps:
>
> 1 Start YaST and select Software > Add-On Product. Then click Add.
>
> 2 If you are installing SMT from a local ISO image, select Local ISO Image as the
> media type (repository). If you are installing from a different source, such as CD,
> NFS, or HTTP, choose the appropriate type. Then click Next.
>
> 3 If you are installing from a CD, insert the SMT add-on product CD. If you are
> installing from a different source, provide the necessary repository information.
>
> 4 Confirm the SMT license agreement and click Next.
>
> 5 Click Accept to install the SMT: Subscription Management Tool for SLE pattern.
> Depending on the scope of already installed packages, the software manager will
> add more packages to resolve all dependencies. Confirm these Automatic Changes
> to perform the installation.
>
> 6 The SMT Configuration Wizard is launched. See Section 1.3, "SMT Configuration
> Wizard" (page 3).
> =======
>
> 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: Jiri Srain [mailto:jsrain at suse.cz]
> Gesendet: Friday, June 27, 2014 2:21 PM
> An: Frey Urs, IT222; sles-beta at lists.suse.com; smt-beta at lists.suse.com
> Betreff: Re: AW: [sles-beta] Testing SLES12 Beta9 with SMT
>
> On 06/27/2014 02:05 PM, urs.frey at post.ch wrote:
>> Hi
>> Are there only rpm packages?
>
> Yes, there are only RPM packages.
>
> We will not release any ISO even as the final version, there will only
> be an on-line update released for the existing one.
>
>> No ISO one could use as add-on product to install from scratch on SLES11-SP3?
>> When having only smt-rpm's there will only be a RPM -U possible, no add-on product installation and ssl-certs generation etc.
>> SMT installation can not be tested.
>
> Not really. The README-SCC file describes how to install SMT including
> the update on a fresh SLES installation.
>
> Jiri
>
>>
>> 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 Jiri Srain
>> Gesendet: Friday, June 27, 2014 1:56 PM
>> An: sles-beta at lists.suse.com; smt-beta at lists.suse.com
>> Betreff: [sles-beta] Testing SLES12 Beta9 with SMT
>>
>> Dear SLES12 testers,
>>
>> testing version of SMT, which allows registration of SLES12 Beta9, is
>> now available at
>>
>>      http://beta.suse.com/private/SMT-Beta/
>>
>> Due to a bug in Beta9, enclosed driver update disk needs to be applied
>> in order to register extensions and modules. The instructions are
>> included in the README-SCC file, which is available at the URL above.
>>
>> If you are upgrading from the previous snapshot of SMT, be aware that
>> the repository URL has changed and that you need to add the new
>> repository and update SMT from it.
>>
>> The driver update disk is only available for x86_64 clients.
>>
>> Happy testing and thanks for your feedback!
>>
>>        The SUSE SMT team.
>>
>>
>
>


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com

From urs.frey at post.ch  Fri Jun 27 06:56:21 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Fri, 27 Jun 2014 12:56:21 +0000
Subject: [sles-beta] Testing SLES12 Beta9 with SMT
In-Reply-To: <53AD6871.50700@suse.cz>
References: <53AD5BE9.9070609@suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F9B5510@HXMB12.pnet.ch>
	<53AD61B1.4070009@suse.cz>
	<40637DBB36AF3941B243A286A432CA0B0F9B554D@HXMB12.pnet.ch>
	<53AD6871.50700@suse.cz>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9B5578@HXMB12.pnet.ch>

Hi Jiri

I have no internet access from my server.
My SLE11-SMT-SP3 is registered to NCC
So I cannot see an SMT-BETA Repository

v04yf4:~ # smt-catalogs | grep SMT |grep sle-11-x86_64
| No      | 477 | nu   | SLE11-SMT-SP2-Pool                          | sle-11-x86_64           | SLE11-SMT-SP2-Pool for sle-11-x86_64                          | Yes             | No      |
| No      | 480 | nu   | SLE11-SMT-SP2-Updates                       | sle-11-x86_64           | SLE11-SMT-SP2-Updates for sle-11-x86_64                       | Yes             | No      |
| Yes     | 483 | nu   | SLE11-SMT-SP3-Pool                          | sle-11-x86_64           | SLE11-SMT-SP3-Pool for sle-11-x86_64                          | Yes             | No      |
| Yes     | 486 | nu   | SLE11-SMT-SP3-Updates                       | sle-11-x86_64           | SLE11-SMT-SP3-Updates for sle-11-x86_64                       | Yes             | No      |
| No      | 489 | nu   | SLE11-SMT-Updates                           | sle-11-x86_64           | SLE11-SMT-Updates for sle-11-x86_64                           | Yes             | No      |
| No      | 509 | nu   | SLE11-SP1-SMT-Pool                          | sle-11-x86_64           | SLE11-SP1-SMT-Pool for sle-11-x86_64                          | Yes             | No      |
| No      | 512 | nu   | SLE11-SP1-SMT-Updates                       | sle-11-x86_64           | SLE11-SP1-SMT-Updates for sle-11-x86_64                       | Yes             | No      |
v04yf4:~ #

This is why I say, RPM packages for me do not work

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: Jiri Srain [mailto:jsrain at suse.cz] 
Gesendet: Friday, June 27, 2014 2:50 PM
An: Frey Urs, IT222; sles-beta at lists.suse.com; smt-beta at lists.suse.com
Betreff: Re: AW: AW: [sles-beta] Testing SLES12 Beta9 with SMT

Hi Urs,

the README-SCC file says following:

Installation of SCC-enabled SMT
===============================

Install and register SLES11-SP3. Afterwards, add the beta repository
e.g. via zypper:

   zypper ar <url> SMT-BETA

You can verify that the repository is added correctly and can be
refreshed via

   zypper ref

Then you can follow either via standard installation of SMT (YaST add-on
module, you will need the standard SMT media) or install the packages
manually via zypper. Remember that to satisfy all dependencies, the
standard SMT media is necessary, the BETA repository is not sufficient..
If needed, add it also via zypper for manual installation. If you
install SMT via zypper, run the YaST smt-server module to perform
initial configuration, which includes selecting the registration server
(SCC or NCC).




In other words, you can just add the BETA repository and then follow the 
installation work-flow as described in the SMT documentation.

I will improve the README.

Jiri



On 06/27/2014 02:45 PM, urs.frey at post.ch wrote:
> Hi Jiri
> Sorry disagree.
> In the file README_SSC I cannot find anything about an fresh installation of SMT 2-0 on a SLES11-SP3 which does not have any element of SMT installed yet.
> SMT-SLES11-SP3 connected to NCC is an add-on product.
> To have the wizard running and the ability to register sles11-sp3 enabled one needs to get through the entire configuration and connection stuff including all ssl certs and database.
>
> I know what I am talking about, because I had to newly install an SLE11-SMT-SP3 in a new network zone
> And I fell on my nose by first adding only the RPMs in YaST instead of selecting the Subscription Management Tool pattern.
> No wizards, no correct ssl certificates, only weird ssl-messages.
>
> To be precise: "from the pdf delivered with SLES11-SP3-smt_en.pdf on the Repository SLE11-SMT-SP3-Pool
>   ====
> 1.2 Installation on Top of an Already Installed System
> To install SMT on top of an already-installed base system, follow these steps:
>
> 1 Start YaST and select Software > Add-On Product. Then click Add.
>
> 2 If you are installing SMT from a local ISO image, select Local ISO Image as the
> media type (repository). If you are installing from a different source, such as CD,
> NFS, or HTTP, choose the appropriate type. Then click Next.
>
> 3 If you are installing from a CD, insert the SMT add-on product CD. If you are
> installing from a different source, provide the necessary repository information.
>
> 4 Confirm the SMT license agreement and click Next.
>
> 5 Click Accept to install the SMT: Subscription Management Tool for SLE pattern.
> Depending on the scope of already installed packages, the software manager will
> add more packages to resolve all dependencies. Confirm these Automatic Changes
> to perform the installation.
>
> 6 The SMT Configuration Wizard is launched. See Section 1.3, "SMT Configuration
> Wizard" (page 3).
> =======
>
> 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: Jiri Srain [mailto:jsrain at suse.cz]
> Gesendet: Friday, June 27, 2014 2:21 PM
> An: Frey Urs, IT222; sles-beta at lists.suse.com; smt-beta at lists.suse.com
> Betreff: Re: AW: [sles-beta] Testing SLES12 Beta9 with SMT
>
> On 06/27/2014 02:05 PM, urs.frey at post.ch wrote:
>> Hi
>> Are there only rpm packages?
>
> Yes, there are only RPM packages.
>
> We will not release any ISO even as the final version, there will only
> be an on-line update released for the existing one.
>
>> No ISO one could use as add-on product to install from scratch on SLES11-SP3?
>> When having only smt-rpm's there will only be a RPM -U possible, no add-on product installation and ssl-certs generation etc.
>> SMT installation can not be tested.
>
> Not really. The README-SCC file describes how to install SMT including
> the update on a fresh SLES installation.
>
> Jiri
>
>>
>> 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 Jiri Srain
>> Gesendet: Friday, June 27, 2014 1:56 PM
>> An: sles-beta at lists.suse.com; smt-beta at lists.suse.com
>> Betreff: [sles-beta] Testing SLES12 Beta9 with SMT
>>
>> Dear SLES12 testers,
>>
>> testing version of SMT, which allows registration of SLES12 Beta9, is
>> now available at
>>
>>      http://beta.suse.com/private/SMT-Beta/
>>
>> Due to a bug in Beta9, enclosed driver update disk needs to be applied
>> in order to register extensions and modules. The instructions are
>> included in the README-SCC file, which is available at the URL above.
>>
>> If you are upgrading from the previous snapshot of SMT, be aware that
>> the repository URL has changed and that you need to add the new
>> repository and update SMT from it.
>>
>> The driver update disk is only available for x86_64 clients.
>>
>> Happy testing and thanks for your feedback!
>>
>>        The SUSE SMT team.
>>
>>
>
>


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com

From jsrain at suse.cz  Fri Jun 27 07:10:03 2014
From: jsrain at suse.cz (Jiri Srain)
Date: Fri, 27 Jun 2014 15:10:03 +0200
Subject: [sles-beta] Testing SLES12 Beta9 with SMT
In-Reply-To: <53AD6519.7010404@ucs.cam.ac.uk>
References: <53AD5BE9.9070609@suse.cz>	<40637DBB36AF3941B243A286A432CA0B0F9B5510@HXMB12.pnet.ch>	<53AD61B1.4070009@suse.cz>
	<53AD6519.7010404@ucs.cam.ac.uk>
Message-ID: <53AD6D2B.1000904@suse.cz>

On 06/27/2014 02:35 PM, Simon Flood wrote:
> On 27/06/2014 13:21, Jiri Srain wrote:
>
>> Yes, there are only RPM packages.
>>
>> We will not release any ISO even as the final version, there will only
>> be an on-line update released for the existing one.
>
> So unlike with SMT11 SP3 it won't be possible to install SLES and then
> SMT to manage SLES12 without jumping through another hoop?

I don't understand what you mean. There will be no new product, only 
on-line update of a previously released product.

> You also seem to suggest that we'll need SLES11 SP3 to host SMT for
> SLES12 and there won't be SMT12 as an add-on for SLES12 like there is
> SMT11 SP3 for SLES11 SP3. Or am I missing something?

Yes, we are working on releasing an on-line update of SMT11-SP3, which 
runs on top of SLES11-SP3.

Jiri


-- 
Regards,

Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o.                            e-mail: jsrain at suse.com
Lihovarska 1060/12                            tel: +420 284 084 659
190 00 Praha 9                                fax: +420 284 084 001
Czech Republic                                http://www.suse.com

From jsmeix at suse.de  Fri Jun 27 10:14:09 2014
From: jsmeix at suse.de (Johannes Meixner)
Date: Fri, 27 Jun 2014 18:14:09 +0200 (CEST)
Subject: [sles-beta] default btrfs subvolumes under / in SLES 12
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240DA900@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240DA900@CFWEX01.americas.cray.com>
Message-ID: <alpine.LNX.2.00.1406271801170.6593@nelson.suse.de>


Hello,

On Jun 27 15:25 Wendy Palm wrote (excerpt):
>        <partition>
...
>          <filesystem config:type="symbol">btrfs</filesystem>
...
>          <subvolumes config:type="list">

I added you to CC of
https://bugzilla.novell.com/show_bug.cgi?id=882982
because some comments therein about AutoYaST and btrfs subvolumes
might be of interest for you, for example
https://bugzilla.novell.com/show_bug.cgi?id=882982#c2
(excerpt):
----------------------------------------------------------------------
Somehow the normal btrfs subvolumes in the AutoYaST installed system
have our special '/@/' subvolume regardless that this is not
mentioned in autoinst.xml.
I wonder how to specify in autoinst.xml when one wants to have
plain btrfs subvolumes without our special '/@/' subvolume?
----------------------------------------------------------------------

But I am not at all a btrfs expert so that I cannot provide background
information about the SLE12 default btrfs subvolume structure.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

From mge at suse.com  Fri Jun 27 11:19:17 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Fri, 27 Jun 2014 19:19:17 +0200
Subject: [sles-beta] default btrfs subvolumes under / in SLES 12
In-Reply-To: <D5048769A89C5C40BAC8CD7E108BF5E8240DA900@CFWEX01.americas.cray.com>
References: <D5048769A89C5C40BAC8CD7E108BF5E8240DA900@CFWEX01.americas.cray.com>
Message-ID: <20140627171916.GE9142@suse.com>

Hello Wendy and all,

On 2014-06-27 T 15:25 +0000 Wendy Palm wrote:

> In the default installation of SLES 12, these btrfs
> subvolumes are created underneath /.  Where can I find
> information about why these were chosen to be
> subvolumes?

These have been chosen to not risk anybody to rollback
files which should not be rolled back. Example: rolling
back any file in /var/log/ would lead to compliance
violations with most customers and partners.

That said:
 
> For my use, I have another subvolume to add, 

That depends what you want to add. Can you tell us?

> but also will be removing some of these, 

You really should _not_ remove any of those subvolumes.
If you feel, you need need to, my advice is not to use
rollback at all, as you will run into issues most
probably.

Or to be more strict: if you are removing pre-chosen
subvolumes, your setup will be unsupported for the
rollback usecase - as a general rule. Please be more
specific, what you feel to not have in a subvolume.

> so I would like to understand why these directories
> are in the subvolume list.
 
As said above, these subvolumes contain files which
should not be snapshotted (e.g. /var/crash, /tmp,
/var/tmp) or should be prevented from accidentially been
rolled back (e.g.  /var/log, /var/pgsql, /var/mailman,
/var/spool), directories where third-party data are
stored (/srv, /opt, /var/opt, /var/local) or
directories which contain "static" executables
(/opt/grub2/...). I think I have covered all now.

Can you send some details about your requirements?

so long -
	MgE



>         <partition>
>           <create config:type="boolean">true</create>
>           <crypt_fs config:type="boolean">false</crypt_fs>
>           <filesystem config:type="symbol">btrfs</filesystem>
>           <format config:type="boolean">true</format>
>           <loop_fs config:type="boolean">false</loop_fs>
>           <mount>/</mount>
>           <mountby config:type="symbol">uuid</mountby>
>           <partition_id config:type="integer">131</partition_id>
>           <partition_nr config:type="integer">2</partition_nr>
>           <resize config:type="boolean">false</resize>
>           <size>42944593408</size>
>           <subvolumes config:type="list">
>             <listentry>boot/grub2/i386-pc</listentry>
>             <listentry>boot/grub2/x86_64-efi</listentry>
>             <listentry>opt</listentry>
>             <listentry>srv</listentry>
>             <listentry>tmp</listentry>
>             <listentry>usr/local</listentry>
>             <listentry>var/crash</listentry>
>             <listentry>var/lib/mailman</listentry>
>             <listentry>var/lib/named</listentry>
>             <listentry>var/lib/pgqsl</listentry>
>             <listentry>var/log</listentry>
>             <listentry>var/opt</listentry>
>             <listentry>var/spool</listentry>
>             <listentry>var/tmp</listentry>
>           </subvolumes>
>         </partition>



-- 
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)