System administration features in XL Deploy 5.0.0 (Google Hangout session on Dec 4th!)

Follow

Vincent Partington -

Hi all,

The XL Deploy team is currently working very hard on the next major release of XL Deploy, version 5.0.0, to be shipped in Q1 2015. This release will be a big one:

  • support for microservices deployments,
  • XL Satellite to support deployments in global environments with high-latency and/or low-bandwith network connectivity,
  • a new HTML5 UI to help you create deployment packages and set up environments,
  • a lot of smaller, often requested UI tweaks and enhancements,
  • as well as lot of feature requests!

The feature requests are mostly about what we like to call the "system administration features" of XL Deploy. It's the features that you have requested to help you administer XL Deploy within your organization.

However, we will not be able to fit all of these features into the release. So to make sure that we build the features that are most important to our users,

We want to hear from you!

Based on the posts in this feature request forum and other discussions with our users, we've created a shortlist of features that we want to address in this release. In no particular order:

  1. Export/import (parts of) the repository - Allow the user to export the repository to a (ZIP) file and import it in the same or another XLD instance to allow the administrator to backup or migrate the repository.
  2. Export/import dictionaries as Java properties files - Allow the user to export dictionaries to Java properties file as well as import Java properties files into dictionaries.
  3. Support external artifact stores - Allow XL Deploy to reference artifacts from external repositories (such as Nexus and Artifactory) and download them on demand, i.e. when scanning them for placeholders or deploying them.
  4. Support external dictionaries - Allow XL Deploy to pull dictionaries from external stores (such as Secret Server or Pleasant Password Server).
  5. Run as a service - Provide built-in support for running XL Deploy as a Unix or Windows service.
  6. Maintenance mode/graceful shutdown - Allow the administrator to put XL Deploy into maintenance mode (existing tasks can finish but new ones cannot be started) so that XL Deploy can be gracefully shutdown.
  7. Automated upgrade for XL Deploy - Replace the current process with an automated upgrade so that upgrading XL Deploy is just as easy as installing it.
  8. Automatically run the garbage collector on a schedule - Run the XL Deploy garbage collector automatically on a user-configurable schedule using cron syntax ("once every hour" or "every Monday morning") to keep the size of the XLD repository in check.
  9. Automatically purge packages according to a user defined policy - Allow the user to configure a policy ("purge packages older than 6 months" or "purge all but the 5 newest packages") and a schedule using cron syntax to keep the size of the XLD repository in check.
  10. Automatically purge the task archive according to a user defined policy - Allow the user to configure a policy ("purge (deployment) tasks that happened more than 1 month ago") and a schedule using cron syntax to keep the size of the XLD repository in check.
  11. Expose artifact and package size and _ci_attributes - Expose the size of an artifact and of a complete package in the _ci_attributes property (introduced in XL Deploy 4.5.0) to allow the administrator to know how much storage is used by which applications.
  12. Expose all services in the CLI - Replace the current -expose-proxies option with the ability to invoke all XL Deploy services from the CLI using the same syntax that can be used in rules and UI extensions.

Let us know your personal top 5 from this list by replying to this post!

If you want to know what these features are about in more detail, please join our Google Hangout on Dec 4th 2014 at 10:00 AM EST/16:00 CET: https://plus.google.com/u/0/events/cuhvgb5j0g7ujv7dgekgq75ud28

Looking forward to your top 5's and to talking to you on the 4th!

Kind regards, Vincent Partington.

 

Have more questions? Submit a request
  • Avatar
    Michiel Sens

    Hello! In order:

    1. *Support external artifact stores *- Allow XL Deploy to reference artifacts from external repositories (such as  Nexus and  Artifactory) and download them on demand, i.e. when scanning them for placeholders or deploying them.
    2. Run as a service - Provide built-in support for running XL Deploy as a Unix or Windows service.
    3. Export/import (parts of) the repository
    4. Automatically purge packages according to a user defined policy
    5. Automatically run the garbage collector on a schedule
  • Avatar
    Bart Beemsterboer

    Our top 5 in order:

    1. Automated upgrade for XL Deploy - Replace the current process with an automated upgrade so that upgrading XL Deploy is just as easy as installing it.
    2. *Support external artifact stores *- Allow XL Deploy to reference artifacts from external repositories (such as  Nexus and  Artifactory) and download them on demand, i.e. when scanning them for placeholders or deploying them.                                 *** DON'T FORGET NUGET ***
    3. Support external dictionaries - Allow XL Deploy to pull dictionaries from external stores (such as Secret Server or Pleasant Password Server).
    4. Run as a service - Provide built-in support for running XL Deploy as a Unix or Windows service.

    And a request regarding the UI

          5. Make all lists searchable (hosts attached to an environment, dictionaries, etc)

     

  • Avatar
    Eelco Maljaars

    My top five looks like this : 

    1. Automated upgrade for XL Deploy 
    2. Run as a service (with respawn option) 
    3. Automatically purge packages according to a user defined policy
    4. Expose all services in the CLI
    5. Support external dictionaries

     

          6* Get rid of Flash ASAP 

    Best wishes, 

     

    Eelco 

     

  • Avatar
    Bernie Durfee

    1. Support external artifact stores

    2. Automatically purge packages according to a user defined policy

    3. Expose all services in the CLI

    4. Support external dictionaries

    5. Automated upgrade for XL Deploy

     

     

  • Avatar
    Mohamed El Hossary

    Hello

    1-Export/import (parts of) the repository

    2-Automated upgrade for XL Deploy

    3-Automatically purge packages according to a user defined policutdown

    4-Maintenance mode/graceful shutdown

    5-Run as a service 

  • Avatar
    Pierre-Gildas MILLON

    Export/import dictionaries as Java properties files

    Maintenance mode/graceful shutdown

    Expose all services in the CLI

    Automatically purge packages according to a user defined policy

    Automatically purge the task archive according to a user defined policy

  • Avatar
    Alexandre Victoor

    Export/import (parts of) the repository

    Support external dictionaries

    Automatically purge packages according to a user defined policy

    Maintenance mode/graceful shutdown

    Automated upgrade for XL Deploy

     

     

     

  • Avatar
    Fouzi BOUKEZZOULA

    *Hello, My Top 5 :

    *

    Support external artifact stores

    Automatically purge packages according to a user defined policutdown

    Export/import (parts of) the repository

    Support external dictionaries 

    Expose all services in the CLI

  • Avatar
    Laurent COUCHEZ
    1. Export/import (parts of) the repository 
    2. Maintenance mode/graceful shutdown 
    3. Expose artifact and package size and _ci_attributes
    4. Support external dictionaries 
    5. Export/import dictionaries as Java properties files 
  • Avatar
    Axel Reinders
    1. Automatically purge the task archive according to a user defined policy
    2. Automatically purge packages according to a user defined policy
    3. Expose all services in the CLI
    4. Maintenance mode/graceful shutdown
    5. Run as a service
  • Avatar
    Michael Herrera

    In no particular order:

    1. Automated upgrade.
    2. Run as a service.
    3. Export/import parts of the repository.
    4. Automatically purge packages based on user-defined policy.
    5. External artifact stores.
  • Avatar
    mohamed lakhdari

    Hello,

    1. Automatically purge packages according to a user defined policy
    2. Automatically purge the task archive according to a user defined policy
    3. Run as a service
    4. Support external dictionaries
    5. Export/import (parts of) the repository

     

  • Avatar
    Dany Garnier
    1. Export/import (parts of) the repository  2.

    Automatically purge packages according to a user defined policy

    1. Expose artifact and package size and _ci_attributes 4.

    Automated upgrade for XL Deploy

    1. Maintenance mode/graceful shutdown 

     

  • Avatar
    Chantelly

    1- Automatically purge the task archive according to a user defined policy

    2- Expose artifact and package size and _ci_attributes

    3- Maintenance mode/graceful shutdown 

    4- Export/import (parts of) the repository 

    5- Automatically purge the task archive according to a user defined policy

  • Avatar
    Chantelly

    1.

    Automatically purge packages according to a user defined policy

    1. Expose artifact and package size and _ci_attributes 3.

    Automated upgrade for XL Deploy

    1. Maintenance mode/graceful shutdown 
    2. Automatically purge the task archive according to a user defined policy
  • Avatar
    daniel kachaner
    • Export/import (parts of) the repository - Allow the user to export the repository to a (ZIP) file and import it in the same or another XLD instance to allow the administrator to backup or migrate the repository.
    • Run as a service - Provide built-in support for running XL Deploy as a Unix or Windows service.
    • Maintenance mode/graceful shutdown - Allow the administrator to put XL Deploy into maintenance mode (existing tasks can finish but new ones cannot be started) so that XL Deploy can be gracefully shutdown.
    • Automated upgrade for XL Deploy - Replace the current process with an automated upgrade so that upgrading XL Deploy is just as easy as installing it.
    • Automatically **purge packages according to a user defined policy** - Allow the user to configure a policy ("purge packages older than 6 months" or "purge all but the 5 newest packages") and a schedule using cron syntax to keep the size of the XLD repository in check.
  • Avatar
    Dave Roberts

    External artifact stores (Nexus)

    Run XLD as a service

    Auto-upgrade

    Export/import dictionaries as Java properties files

    Maintenance mode/graceful shutdown with options (when all executing tasks complete or when all executing steps complete)

  • Avatar
    Mark Ravech

     

    1. Run as a service - Provide built-in support for running XL Deploy as a Unix or Windows service.

    2. Maintenance mode/graceful shutdown - Allow the administrator to put XL Deploy into maintenance mode (existing tasks can finish but new ones cannot be started) so that XL Deploy can be gracefully3. Automated upgrade for XL Deploy - Replace the current process with an automated upgrade so that upgrading XL Deploy is just as easy as installing it.

    4. Expose all services in the CLI - Replace the current -expose-proxies option with the ability to invoke all XL Deploy services from the CLI using the same syntax that can be used in rules and UI extensions.

    5. Expose artifact and package size and _ci_attributes - Expose the size of an artifact and of a complete package in the _ci_attributes property (introduced in XL Deploy 4.5.0) to allow the administrator to know how much storage is used by which applications.

     

  • Avatar
    Eric Cornet

    1.

    Automated upgrade for XL Deploy

    2.

    Export/import dictionaries as Java properties files

    3.

    Expose all services in the CLI

    4.

    Export/import (parts of) the repository

    5.

    Automatically purge packages according to a user defined policy

  • Avatar
    Guillaume Thomas

    Hello,

    1 / Export/import (parts of) the repository

    2/ Maintenance mode/graceful shutdown

    3/ Expose all services in the CLI

    4/ Expose artifact and package size and _ci_attributes

    5/Support external dictionaries

  • Avatar
    Andrew Boswell

    Unfortunately I missed the hangout so here are some comments on the features.

    Although all of them are a good plus, the most important from your list in order are the following:

    3   - Support external artifact stores This means the repo can have an immense amount of versions without taking Terrabytes of space.

    NOT LISTED - Defining multiple pipelines for an application - please see https://support.xebialabs.com/entries/23292183-Defining-multiple-pipelines-for-an-application

    **NOT LISTED - REST API  select response format **Ability to receive json over xml, or at least to be able to choose with an html header; see https://support.xebialabs.com/entries/49197497-Select-REST-API-responses-format

    **9   - Automatically purge packages according to a user defined policy  **However for this functionality to be useful in a production environment, we would need this in a little more advanced form. i.e. specifying to keep the 5 most recent from the older currently deployed: (we do this currently with scripts that are a little twisted... it would be nice to have this integrated)

    versions: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15

    currently deployed versions on different environments: 10,13,14

    if you only keep the 5 most recent: 11,12,13,14,15 (this means that there is no rollback version available for 10 in the repo!)

    if you keep -5 from the lowest deployed: 5,6,7,8,9,10,11,12,13,14,15 (rollback to previous versions is possible, danger averted)

    *1   - Export/import (parts of) the repository **This would be incredibly useful for upgrades, backups etc. I would be interested in hearing what you mean by *parts of **?

     

  • Avatar
    Julien CHARIER

    Hello,

    1.  Automatically purge packages according to a user defined policy

    2.  Automatically run the garbage collector on a schedule

    3.  Export/import dictionaries as Java properties files

    4.  Expose artifact and package size and _ci_attributes

    5.  Automatically purge the task archive according to a user defined policy

  • Avatar
    A.F. van den Heuvel

    Great initiative, here my votes:

    1. Automatically purge packages according to a user defined policy

    2. Automatically run the garbage collector on a schedule

    3. Maintenance mode/graceful shutdown 

    4. Expose all services in the CLI

    5. Export/import (parts of) the repository 

     

     

  • Avatar
    T.j. Randall

    My Top 5:

    1. *Support external artifact stores *- Allow XL Deploy to reference artifacts from external repositories (such as  Nexus and  Artifactory) and download them on demand, i.e. when scanning them for placeholders or deploying them.
    2. Support external dictionaries - Allow XL Deploy to pull dictionaries from external stores (such as Secret Server or Pleasant Password Server).
    3. Run as a service - Provide built-in support for running XL Deploy as a Unix or Windows service.
    4. Automated upgrade for XL Deploy - Replace the current process with an automated upgrade so that upgrading XL Deploy is just as easy as installing it.
    5. Automatically purge packages according to a user defined policy - Allow the user to configure a policy ("purge packages older than 6 months" or "purge all but the 5 newest packages") and a schedule using cron syntax to keep the size of the XLD repository in check.

     

  • Avatar
    Aidin Zahedi Pour

    1 Automatically purge packages according to a user defined policy

    2 Automatically run the garbage collector on a schedule

    3 Export/import dictionaries as Java properties files -

    4 Automated upgrade for XL Deploy

    5 Automatically purge the task archive according to a user defined policy

  • Avatar
    Adé Mochtar
    1. Automatically purge packages according to a user defined policy
    2. Maintenance mode/graceful shutdown
    3. Automated upgrade for XL Deploy
    4. Support external dictionaries
    5. Export/import (parts of) the repository
  • Avatar
    Teo Dubbeldam

    My top 5:

    1. Maintenance mode/graceful shutdown 

    2. Export/import (parts of) the repository 

    3. Automatically run the garbage collector on a schedule

    4. Expose all services in the CLI

    5. Automatically purge the task archive according to a user defined policy

  • Avatar
    Vincent Partington

    Hi,

    Voting has closed. Have a look at the results!

    Kind regards, Vincent Partington.

     

Powered by Zendesk