Dune Documentation¶
Welcome to the Dune documentation
Please use the navigation or the powerful search function to find what you are looking for.
If you are new to Dune, there is a short summary about the platform right below the image. It's also recommended to peek into the concepts section which explains the main building blocks of Dune.
About Dune¶
Dune is an infrastructure management platform. It supports its users through the whole lifecycle from provisioning to management and operations to decomissioning of the infrastructure needed for an application or other use cases. It's especially useful to manage large scale infrastructure with processes and tasks applying to many resources.
Dune is not only oriented torwards technical users (System Engineers, System Admins, etc.) but also torwards business users (Application Owner, CISOs, etc.). No matter if you use the Dune Portal (Website) or the API, there are technical views and actions like Search a VM by hostname, Initiate patching, Get all test resources, etc. but there are also more business oriented views and actions like Search for applications, Define expiry dates and more.
By using this composite approach and through its extensive technical CMDB, Dune is able to give you an excellent overview of your infrastructure, to make collaboration between teams and different roles easier by using the same tool and to improve compliancy by using templated (IaC), repeatable deployments and configuration management.
Provisioning¶
Deploy your application infrastructure by using composable, reusable yaml Templates. The templates not only describe infrastructure resources like VirtualMachines but they also contain configuration management elements which configure the internals (hardening, packages, etc.) of a resource like a VM. Additionally external dependencies like AD Service Accounts, AD Groups, etc. can be templated as well.
Management & Operations¶
After your application infrastructure (resources) are deployed through Dune, they will be visible and properly grouped in the Portal. Users now have a toolset at their hands to do operations at scale. They can not only do an operation for one resource but for groups of resources. For example: restart all VMs of the application Bookings or Set the patch schedule for all 20 VMs of the application TradingApp. There are reports to check for critical updates or vulnerable resources all taking into account the grouping by Application.
Decomissioning¶
When an application infrastructure is decomissioned, not only the typical resources like VirtualMachines are getting deleted but also service accounts, ad groups and dns aliases, etc. (Everything which was defined in the template). Dune has the concept of expiry dates. So whenever something gets deployed it will get an expiry date, which will remind the user after some time to either extend it or if the application infrastructure is not needed anymore to stop and later delete it. This helps in keeping the footprint of unused systems low.
Support¶
To report an issue please send an email to support@duneframework.com