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

unable to install only clients package without daemon and qemu stuff #27

Open
vtolstov opened this issue Sep 5, 2017 · 3 comments
Open

Comments

@vtolstov
Copy link

vtolstov commented Sep 5, 2017

I need only libvirt lib and virsh binary, with current formula i can't do that by providing
qemu_pkg: ~
extra_pkgs: ~

@baby-gnu
Copy link
Contributor

I'm now ready to split components into sub-directories.

It seems that we have:

  • the libvirt server
  • the libvirt client
  • the qemu for the server (since libvirt server could manage other things)
  • the tools could be used independently of server/client (qemu-img, libguestfs)

Here is the directory hierarchy I'm planing to define:

libvirt/
├── client
│   ├── clean.sls
│   ├── config
│   │   ├── clean.sls
│   │   ├── file.sls
│   │   └── init.sls
│   ├── files
│   │   └── default
│   ├── init.sls
│   ├── package
│   │   ├── clean.sls
│   │   ├── init.sls
│   │   └── install.sls
│   └── tls
│       ├── cert.sls
│       ├── clean.sls
│       └── init.sls
├── python
│   ├── clean.sls
│   ├── init.sls
│   └── library.sls
├── qemu
│   ├── clean.sls
│   ├── config
│   │   ├── clean.sls
│   │   ├── file.sls
│   │   └── init.sls
│   ├── files
│   │   └── default
│   ├── init.sls
│   └── package
│       ├── clean.sls
│       ├── init.sls
│       └── install.sls
├── server
│   ├── clean.sls
│   ├── config
│   │   ├── clean.sls
│   │   ├── file.sls
│   │   └── init.sls
│   ├── files
│   │   └── default
│   ├── init.sls
│   ├── package
│   │   ├── clean.sls
│   │   ├── init.sls
│   │   └── install.sls
│   ├── service
│   │   ├── clean.sls
│   │   ├── init.sls
│   │   └── running.sls
│   └── tls
│       ├── cert.sls
│       ├── clean.sls
│       └── init.sls
└── tools
    ├── clean.sls
    ├── config
    │   ├── clean.sls
    │   ├── file.sls
    │   └── init.sls
    ├── files
    │   └── default
    ├── init.sls
    └── package
        ├── clean.sls
        ├── init.sls
        └── install.sls

This way:

  • state.apply libvirt will install and configure everything
  • state.apply libvirt.server will only manage the server part
  • state.apply libvirt.client will only manage the client part
  • state.apply libvirt.tools.clean will only unconfigure/remove the tools

This the sub-component scheme as describe in https://github.com/saltstack-formulas/template-formula/blob/develop/docs/TOFS_pattern.rst#using-sub-directories-for-components

Does someone have any comment? (@myii, @Aboe, @vtolstov)

@baby-gnu
Copy link
Contributor

I'm now ready to split components into sub-directories.

It seems that we have:
[…]

  • the tools could be used independently of server/client (qemu-img,
    libguestfs)

Actually, this is the extra_pkgs. I will provide an extra directory instead of a tools.

@myii
Copy link
Member

myii commented Aug 23, 2019

@baby-gnu Sounds like an excellent plan to me, always nice to see all of our template-formula structures being applied.

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

No branches or pull requests

3 participants