On 17/04/2018 23.52, [email protected] wrote:
Thanks for the input Jussi.
The reprovision just hung around for five minutes then failed. Looking at the
log sent me cross-eyed on this notebook.
The longer term plan was to document a process for the reprovision for future
automation with Ansible. Because of the scant documentation on reprovisioning,
I wasn't sure of the best way to keep my data intact. I wanted to get the zone
in a state where I had to do as little with Ansible as possible which is why
I'd like a best practices document.
I'm kind of new to configuration management tools and this is probably a bit
off-topic, but do you use Ansible to configure your zone from scratch or do you
manually configure your zone and then work with Ansible to get it back to a
functional state?
At the moment I do everything with Ansible, even the repvosioning bit by
leveraging vmadm through Ansible Playbook :-)
So all I basically need to do is change the image_uuid in Ansible
variables and the Zone get's reprovisioned with newer image.
I run separate dev and prod environments so every new image get's "QA
tested" first in dev environment prior to running the Playbook against Prod.
For example with Postfix & Dovecot I do 'rolling upgrade', reprovision
instance at a time and when the reprovision & Ansible finishes the
instance syncs messages & changed flags from other instances using
Dovecot's built-in dsync replication.
The actual email data resides in a delegated dataset mounted on /data.
Ps. This setup isn't built for massive scale fore sure ;-)
-Jussi
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
