1 Topic by travis@mylasso.com

  • travis@mylasso.com
  • Member
  • Offline
  • Registered: 2012-01-17
  • Posts: 9

Topic: Change Management

==== Required information ====
- iRedMail version: 0.8.4
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Linux/BSD distribution name and version: ubuntu 12.04 TLS
- Related log if you're reporting an issue:
====

We are currently working through (and have essentially finished) getting iRedMail under change management using Puppet.

We are now running into some issues when iRedMail releases a new version, and are struggling with how to deal with this.

Does iRedMail currently use any form of Puppet or Chef?
Does iRedMail have any future plans for change management?

If we can not address the natural updates to iRedMails packages we will need to move in a different direction with our change management strategy.

Thanks in advance.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,090

Re: Change Management

Sorry, no plan for Puppet/Chef.
May i know what you want to achieve? What changes?

3 Reply by travis@mylasso.com

  • travis@mylasso.com
  • Member
  • Offline
  • Registered: 2012-01-17
  • Posts: 9

Re: Change Management

ZhangHuangbin wrote:

Sorry, no plan for Puppet/Chef.
May i know what you want to achieve? What changes?

What we like to have when we work with a software stack like a mail system and all of its components, is individual control over every piece of that stack. Our needs require us to tweak many of the applications within iRedMail.

So when you released 0.8.4 we realized that your shell scripts touch many different applications for updating/security etc. Since we do not control that process, that would mean our change management software (Puppet) would have to be aware of every change your updates complete, otherwise if we were managing files like dovecot.conf, we would potentially encounter conflicts.

So what we are going to now do is take most of the "pieces" of iRedMail, or essentially of most modern day mail systems, and place them under change management individually. Starting with packages from base repos, and introducing as few changes as possible, only what we need for our application. These modules when complete will be created to work together, and most likely shared when completed.

Thanks for all your hard work with iRedMail, it is a great offering.

Cheers.