Skip to content
This repository has been archived by the owner on Jul 9, 2020. It is now read-only.

update autoyast for SLES 12 and OpenSuSE 13 #125

Merged
merged 1 commit into from Nov 18, 2014
Merged

update autoyast for SLES 12 and OpenSuSE 13 #125

merged 1 commit into from Nov 18, 2014

Conversation

mmoll
Copy link
Contributor

@mmoll mmoll commented Nov 4, 2014

some updates to the autoyast templates, tested and working with:

  • SLES 11 SP3
  • SLES 12
  • OpenSuSE 13.1
  • OpenSuSE 13.2

On OpenSuSE 11.4 (really EOL now: http://www.rosenauer.org/blog/2014/09/27/opensuse-11-4-has-reached-end-of-evergreen-support/) installing with Puppet seems to trigger a bug and one has to press "OK" one time.

On OpenSuSE 12.3 (EOL 2015-01-04), bug 801878 (https://bugzilla.novell.com/show_bug.cgi?id=801878) is triggered, I'm not sure if that should taken into account or not...

@mattiasgiese @lazyfrosch - comments welcome!

@mattiascockburn
Copy link
Contributor

Heya,

Looks good so far :-) Which version of SLES12 did you test? With GMC2 i observed that the configured hostname is not set in the chroot (before the first reboot) and the machine would register itself with a hostname of linux-$randomfoo. I hacked around that with the following inside the chroot-script:

/bin/hostname <%= @host.name %>

Will test SLES12 GA today.

IMHO the SDK addon should be commented out by default. Yes, i know that most users with a Web workload would add it anyways, but it is nicer if the profile works OOB.

I will test your changed profiles (the SLES one at least) and provide you with additional feedback.

@mmoll
Copy link
Contributor Author

mmoll commented Nov 5, 2014

That was SLES 12 GA. I did see "linux-iw42" as hostname one time, but all the other tests didn't show that, so I thought it might have been something with packet loss while resolving or something like that.

The SDK repo will be enabled for SLES 11 when Puppet is enabled, as (at least when I updated the SLES template about a year ago) there were dependencies to packages in the SDK, but I can re-check this if you tell me, that's not the case anymore. :)

@mattiascockburn
Copy link
Contributor

Well, SLES12 ships with the Advanced Management Module which i am using in order to provision Puppet. I am not sure if you still need SDK packages in order to install the publicy available packages from build.opensuse.org.

@mmoll
Copy link
Contributor Author

mmoll commented Nov 5, 2014

I did read about that "Advanced Management" stuff, but couldn't find any puppet packages on the DVD. Do you have any resources handy how this could work without tapping a 3rd party repo?

@@ -164,8 +167,9 @@ rm /etc/resolv.conf
</import_gpg_key>
</signature-handling>
</listentry>
<% if os_major < 12 -%>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mattiasgiese SLES12 does not use SDK at all.

@mattiascockburn
Copy link
Contributor

Unfortunately not. The Advanced Management Module is only available if the machine is registered with SCC or an internal SMT.

@mmoll
Copy link
Contributor Author

mmoll commented Nov 5, 2014

Then using the OBS repo for the general case is IMHO fine.

@mattiascockburn
Copy link
Contributor

Yeah, we cannot depend on internal/closed repositories. Maybe an alternative method should be introduced to the AutoYaST profiles for SLES (automatic SMT registration whould be nice).

@mmoll
Copy link
Contributor Author

mmoll commented Nov 5, 2014

@mattiasgiese we will be more than happy to review such PRs ;)

@mattiascockburn
Copy link
Contributor

I see what you did there ;)

<service_name>sshd</service_name>
<service_status>enable</service_status>
</service>
</services>
</runlevel>
<software>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A leaner package selection would be:

�  <software>
  <patterns config:type="list">
  <pattern>Minimal</pattern>
  </patterns>
    <packages config:type="list">
      <package>less</package>
      <package>openssh</package>
      <package>vim</package>
<% if puppet_enabled %>
      <package>puppet</package>
<% end -%>
<% if salt_enabled %>
      <package>salt-minion</package>
<% end -%>
    </packages>
  </software>

@mattiascockburn
Copy link
Contributor

Install works fine with provision_sles.rb and SLES12.0

@mmoll
Copy link
Contributor Author

mmoll commented Nov 17, 2014

@mattiasgiese I included most of your recommendations, please review again and we're good to go, IMHO. Tested with SLES 12.0 and 11.3 with and without Puppet.

@mattiascockburn
Copy link
Contributor

provision_sles.rb: Tested with SLES12, with and without Puppet enabled. Works for me.

- OpenSUSE:
  * install more software to get a working system

- SLES:
  * use Minimal software pattern
  * no additional repositories are needed for Puppet on SLES 12
  * implement logic to tap the correct repositories for versions
    without Service Pack
  * set hostname in chroot script to (hopefuly) workaround sporadic
    problems on SLES 12

- OpenSuSE and SLES
  * start sshd explicitly
@mmoll mmoll merged commit e721f4e into theforeman:master Nov 18, 2014
@mmoll
Copy link
Contributor Author

mmoll commented Nov 18, 2014

thanks @mattiasgiese for review, merged.

@mmoll mmoll deleted the suse_updates branch November 18, 2014 12:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants