Puppetizing Yast2 Configuration
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Background
I have a requirement to use SUSE Enterprise Server 12 SP3 across a new cluster of servers. Previously I have used ubuntu and redhat, and have managed their configuration using Puppet. I am now in the process of updating and adding new puppet code to support SUSE. I understand SUSE makes heavy use of the Yast2 configuration utility, while this seems good for configuring a single server it doesn't seem very scalable. I also understand that there is a utility called autoyast which can be used for initial building/configuration, but this certainly doesn't seem like a replacement for puppet.
Question
Almost all the configuration documentation for SUSE seems to refer to using Yast2 for configuration, rather than adding lines to a file, installing packages etc. What approach do people take to automating/puppetizing configuration when the documentation is just telling you how to run through a GUI?
Other than reading the source code, all I can think of is snapshotting and diffing the filesystem before and after running Yast to see what has changed, but some of the Yast modules are doing things like configuring users in databases, which would not be easy to identify from filesystem changes.
suse puppet yast
asked Jul 12 at 12:35
rusty shackleford
1,135115
add a comment |Â
up vote
0
down vote
favorite
Background
I have a requirement to use SUSE Enterprise Server 12 SP3 across a new cluster of servers. Previously I have used ubuntu and redhat, and have managed their configuration using Puppet. I am now in the process of updating and adding new puppet code to support SUSE. I understand SUSE makes heavy use of the Yast2 configuration utility, while this seems good for configuring a single server it doesn't seem very scalable. I also understand that there is a utility called autoyast which can be used for initial building/configuration, but this certainly doesn't seem like a replacement for puppet.
Question
Almost all the configuration documentation for SUSE seems to refer to using Yast2 for configuration, rather than adding lines to a file, installing packages etc. What approach do people take to automating/puppetizing configuration when the documentation is just telling you how to run through a GUI?
Other than reading the source code, all I can think of is snapshotting and diffing the filesystem before and after running Yast to see what has changed, but some of the Yast modules are doing things like configuring users in databases, which would not be easy to identify from filesystem changes.
suse puppet yast
asked Jul 12 at 12:35
rusty shackleford
1,135115
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Background
I have a requirement to use SUSE Enterprise Server 12 SP3 across a new cluster of servers. Previously I have used ubuntu and redhat, and have managed their configuration using Puppet. I am now in the process of updating and adding new puppet code to support SUSE. I understand SUSE makes heavy use of the Yast2 configuration utility, while this seems good for configuring a single server it doesn't seem very scalable. I also understand that there is a utility called autoyast which can be used for initial building/configuration, but this certainly doesn't seem like a replacement for puppet.
Question
Almost all the configuration documentation for SUSE seems to refer to using Yast2 for configuration, rather than adding lines to a file, installing packages etc. What approach do people take to automating/puppetizing configuration when the documentation is just telling you how to run through a GUI?
Other than reading the source code, all I can think of is snapshotting and diffing the filesystem before and after running Yast to see what has changed, but some of the Yast modules are doing things like configuring users in databases, which would not be easy to identify from filesystem changes.
suse puppet yast
asked Jul 12 at 12:35
rusty shackleford
1,135115
Background
I have a requirement to use SUSE Enterprise Server 12 SP3 across a new cluster of servers. Previously I have used ubuntu and redhat, and have managed their configuration using Puppet. I am now in the process of updating and adding new puppet code to support SUSE. I understand SUSE makes heavy use of the Yast2 configuration utility, while this seems good for configuring a single server it doesn't seem very scalable. I also understand that there is a utility called autoyast which can be used for initial building/configuration, but this certainly doesn't seem like a replacement for puppet.
Question
Almost all the configuration documentation for SUSE seems to refer to using Yast2 for configuration, rather than adding lines to a file, installing packages etc. What approach do people take to automating/puppetizing configuration when the documentation is just telling you how to run through a GUI?
Other than reading the source code, all I can think of is snapshotting and diffing the filesystem before and after running Yast to see what has changed, but some of the Yast modules are doing things like configuring users in databases, which would not be easy to identify from filesystem changes.
suse puppet yast
asked Jul 12 at 12:35
rusty shackleford
1,135115
edited Jul 12 at 12:41
asked Jul 12 at 12:35
rusty shackleford
1,135115
asked Jul 12 at 12:35
rusty shackleford
1,135115
asked Jul 12 at 12:35
rusty shackleford
1,135115
1,135115
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f454885%2fpuppetizing-yast2-configuration%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
