Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix client mode and clean-up #5

Merged
merged 18 commits into from
May 10, 2017
Merged

Fix client mode and clean-up #5

merged 18 commits into from
May 10, 2017

Conversation

imobachgs
Copy link
Contributor

@imobachgs imobachgs commented May 5, 2017

This PR tries to address some issues:

  • Fix client mode (at least for Salt provisioner).
  • The module configuration is not written to disk anymore because all happens now during the 1st stage. Less code to maintain and break :)
  • Merge CFA classes to handle minions configuration into a single class.

Anyway, it is still a work in progress.

* It is not needed anymore because all happens now during
  the 1st stage.
* When configuring or running the provisioners, it should use the
  "chrooted" path.
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 454b63f on merge-minion-config into ** on master**.

@imobachgs imobachgs changed the title [WIP] Fix client mode and clean-up Fix client mode and clean-up May 9, 2017
@imobachgs imobachgs requested a review from schubi2 May 9, 2017 15:52
@schubi2
Copy link
Member

schubi2 commented May 10, 2017

Great improvements ! Just a little thought about the stored settings but feel free to ignore it :-) LGTM

# Path to configuration file
PATH = "/etc/salt/minion".freeze
PATH = "/etc/salt/minion.d/yast-configuration-management.conf".freeze
Copy link
Member

Choose a reason for hiding this comment

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

Very nice to concentrate all YaST specific stuff to one own configuration file.

- Fix Puppet package installation
- Handle libzypp's lock to allow installation of packages
through Salt/Puppet
- Do not write configuration to disk as it is not needed anymore
Copy link
Member

Choose a reason for hiding this comment

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

I have also thought about it some time ago. Do we have all information for a "yast clone_system" and the coming up UI in
/etc/salt/minion.d/yast-configuration-management.conf or would some additional information needed for it ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, we do not have all the details. The configuration that was written, contained some specific details to allow running the provisioner after YaST finished.

IMHO, the yast clone_system and UI can be slightly different to the original intention (some information like the path where states/recipes were downloaded are not needed at all). So probably we'll have to bring back part of that code, but I would do it when we implement such features.

@imobachgs imobachgs merged commit 56e8ebe into master May 10, 2017
@imobachgs imobachgs deleted the merge-minion-config branch May 10, 2017 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants