django-orchestra-test/TODO.md

TODO
====

* scape strings before executing scripts in order to prevent exploits: django templates automatically scapes things. Most important is to ensuer that all escape ' to &quot
* Optimize SSH: pool, `UseDNS no`
* Don't store passwords and other service parameters that can be changed by the services i.e. mailman, vps etc. Find an execution mechanism that trigger `change_password()`

* abort transaction on orchestration when `state == TIMEOUT` ?
* filter and other user.is_main refactoring 
* use format_html_join for orchestration email alerts

* generic form for change and display passwords and crack change password form
* enforce an emergency email contact and account to contact contacts about problems when mailserver is down

* add `BackendLog` retry action
* move invoice contact to invoices app?
* PHPbBckendMiixin with get_php_ini
* Apache: `IncludeOptional /etc/apache2/extra-vhos[t]/account-site-custom.con[f]`
* rename account.user to main_user
* webmail identities and addresses
* cached -> cached_property
* user.roles.mailbox its awful when combined with addresses:
    * address.mailboxes filter by account is crap in admin and api
    * address.mailboxes api needs a mailbox object endpoint (not nested user)
    * Its not intuitive, users expect to create mailboxes, not users!
    * Mailbox is something tangible, not a role!
* System user vs virtual user:
    * system user automatically hast @domain.com address :(

* use Code: https://github.com/django/django/blob/master/django/forms/forms.py#L415 for domain.refresh_serial()
* Permissions .filter_queryset()


* git deploy in addition to FTP?
* env vars instead of multiple settings files: https://devcenter.heroku.com/articles/config-vars ?
* optional chroot shell?

* make sure prefetch_related() is used correctly 
Remember that, as always with QuerySets, any subsequent chained methods which imply a different database query will ignore previously cached results, and retrieve data using a fresh database query. 
* profile select_related vs prefetch_related


* Log changes from rest api (serialized objects)
* passlib; nano /usr/local/lib/python2.7/dist-packages/passlib/ext/django/utils.py SortedDict -> collections.OrderedDict
* pip install pyinotify

* create custom field that returns backend python objects

* Timezone awareness on monitoring system (reading server-side logs with different TZ than orchestra) maybe a settings value? (use UTC internally, timezone.localtime() when interacting with servers)

* EMAIL backend operations which contain stderr messages (because under certain failures status code is still 0)


* Settings dictionary like DRF2 in order to better override large settings like WEBSITES_APPLICATIONS.etc


* DOCUMENT: orchestration.middleware: we need to know when an operation starts and ends in order to perform bulk server updates and also to wait for related objects to be saved (base object is saved first and then related)
            orders.signales: we perform changes right away because data model state can change under monitoring and other periodik task, and we should keep orders consistency under any situation.
                             dependency collector with max_recursion that matches the number of dots on service.match and service.metric



* backend logs with hal logo
* Use logs for storing monitored values
* set_password orchestration method?


* make account_link to autoreplace account on change view.

* LAST version of this shit http://wkhtmltopdf.org/downloads.html

* translations
        from django.utils import translation
        with translation.override('en'):
* Plurals!

* help_text on readonly_fields specialy Bill.state. (eg. A bill is in OPEN state when bla bla )

* Transaction states: CREATED, PROCESSED, EXECUTED, COMMITED, ABORTED (SECURED, REJECTED?)
    * bill.send() -> transacction.EXECUTED when source=None
    * transaction.secured() -> bill.paid when bill.total == transaction.value else Error
    * bill.paid() -> transacton.SECURED
    * bill.bad_debt() -> transaction.ABORTED
    * transaction.ABORTED -> bill.bad_debt
    - Issue new transaction when current transaction is ABORTED

* underescore *every* private function

* create log file at /var/log/orchestra.log and rotate

* order.register_at
    @property
    def register_on(self):
        return order.register_at.date()

* mail backend related_models = ('resources__content_type') ??
* ignore orders

* Dropdown menu for Account services/management object-tools

* Domain backend PowerDNS Bind validation support?

* Maildir billing tests/ webdisk billing tests (avg metric)

* move icons to apps, and use appconfig to cleanup config stuff

* when using modeladmin to store shit like self.account, make sure to have a cleanslate in each request

*jabber with mailbox accounts (dovecto mail notification)

* rename accounts register to manager register

* make accounts django auth users
    - when an account is created a mirrored system user is created
    - system users are independent users, so they can have different passwords and all.

* take a look icons from ajenti ;)


* Disable services is_active should be computed on the fly in order to distinguish account.is_active from service.is_active when reactivation.
    * Perhaps it is time to create a ServiceModel ?


* COpy account.main_user.username to account.name for performance

* service backend execution dependency? first create user on NIS master then create directories on service server

* prevent deletion of main user by the user itself



* AccountAdminMixin auto adds 'account__name' on searchfields and handle account_link on fieldsets

* Separate panel from server passwords?  Store passwords on panel? set_password special backend operation?

* be more explicit about which backends are resources and which are service handling


* What fields we really need on contacts? name email phone and what more?


* Redirect junk emails and delete every 30 days?

* DOC: Complitely decouples scripts execution, billing, service definition

* Create SystemUser on account creation. username=username, is_main=True,
    * Exclude is_main=True from queryset filter default is_main=False
    * self referencing group.
    * Unify all users


* backend admin message with link

* delete main user -> delete account or prevent delete main user


APPS app?

* https://blog.flameeyes.eu/2011/01/mostly-unknown-openssh-tricks

* Ansible orchestration *method* (methods.py)
* interdependency user <-> account with the old usermodel


* pip upgrade or install


* disable account triggers save on cascade to execute backends save(update_field=[])