-
Notifications
You must be signed in to change notification settings - Fork 0
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
Config management module #33
Comments
added 10m of time spent |
@jasonpagetas, can you add your wishlist to this ticket for any config management related items |
added 16m of time spent |
marked this issue as related to #35 |
added 2m of time spent |
marked this issue as blocked by #42 |
marked this issue as related to #43 |
removed the relation with #43 |
marked this issue as blocked by #43 |
removed the relation with #42 |
marked this issue as blocked by #42 |
marked this issue as blocked by #44 |
marked the checklist item #42 Group based configuration as completed |
marked this issue as related to #47 |
added 2m of time spent |
added 2m of time spent |
marked this issue as blocked by #58 |
marked this issue as blocked by #59 |
marked this issue as related to #62 |
marked the checklist item Config stored as JSON as completed |
marked this issue as blocked by #64 |
added 5m of time spent |
marked the checklist item Group precedence of conflicting settings is that of the lowest group in the hierarchy. as completed |
marked the checklist item A devices setting that conflicts with a group setting takes precedence. as completed |
marked the checklist item Group precedence of conflicting settings is that of the lowest group in the hierarchy. as incomplete |
marked the checklist item A devices setting that conflicts with a group setting takes precedence. as incomplete |
marked this issue as related to #70 |
marked the checklist item Group precedence of conflicting settings is that of the lowest group in the hierarchy. as completed |
marked this issue as related to #98 |
marked this issue as related to #115 |
marked this issue as related to #140 |
marked this issue as related to #113 |
closing as most work done or migrated to own issue. |
added 20m of time spent |
Add a new module configuration management that's intended to serve the purpose of config management.
Details
Be able to configure devices based of of locations and groups. The configuration will be designed to work with Ansible and Ansible Modules.
For nested configuration priority is that of the lowest within the hierarchy of groups or last in the groups. if a device itself has a setting applied, then that setting will take precedence over that of a group.
Device Lifecycle Stages
OS provisioning
SOE Setup
Role deployment
maintenance
This config management module is intended to target
SOE Setup
andRole deployment
.Device roles #64moved to ~"module::itam" #70Be able to assign a role to a device that serves the purpose of denoting what the device is.#### Features[ ] Can have config assigned[ ] API endpoint available to pull device role config[ ] role config is rendered as part of device configGroups
All devices must be able to be assigned to a group with groups being able to be nested. Groups must also be able to have settings applied to it.
Locations #62
Locations are to be setup as a common item within the core app as these settings can/may be used within other modules. Location awareness is nested and in the following order:
Regions
A region is the first level of location awareness. It's the setting of geographical locations. i.e. continent, country, state etc. Regions contains sites. Regions can be nested.
Sites
A Site is the second level of location awareness and contains Locations. A site is generally below a city (a region). Sites are not nested.
Locations
A location is a physical location at a site. Locations can be nested
configuration needs to be settable based off of a location.
AWX Integration #113
Integrating AWX into the configuration management module will be ideal as it will allow the scheduling and immediate deployment of any changed configuration.
potential requirements for the AWX Integration to be viable:
not an issue if the inventory is pull as part of the same project where another system has it. However if this app is to operate independently, this app will require these settings stored somewhere
AWX Integration Wishlist
Devices details page contains list of AWX jobs run against the device
Statistics collection of jobs run on devices
AWX Inventory from ITSM APP
Wishlist / Features
Requirements
Config stored as JSON
UI has option to format as either JSON or YAML
Either UI setting to be converted to JSON for storage
Location based configuration (added as model to core and configured in settings) Location Management #62
Regions Location Management #62
Site Location Management #62
Location Location Management #62
Config Groups #42 Group based configuration
A devices setting that conflicts with a group setting takes precedence.
Group precedence of conflicting settings is that of the lowest group in the hierarchy.
Software deployment via config groups #43 Can assign software to a group to be installed/removed ⚡ will be completed as part of v1.0.0
Host Config #44 hosts can have config added to it
The text was updated successfully, but these errors were encountered: