(Migrated) Zato 2.0 feature freeze

(This message has been automatically imported from the retired mailing list)

Hello,

I’m very happy to announce the feature freeze for Zato 2.0.

Not all of what was originally planned made it in but the list of what
2.0 will contain is still impressive and includes, among others:

  • REST services
  • Redis-based REST publish/subscribe
  • RESTful HTTP channels
  • OAuth
  • XPath-based security
  • API Keys-based security
  • NTLM security
  • Amazon AWS security
  • SSL/TLS for channels and outgoing connections
  • Role-based access control (RBAC) for HTTP channels
  • OpenID in web admin
  • Cassandra connections and pre-compiled query templates
  • Cloud OpenStack Swift connections
  • Cloud Amazon S3
  • Solr
  • ElasticSearch
  • Odoo/OpenERP connections
  • Support for SQLite
  • Support for MySQL
  • HTTP GUI Audit Log for requests and responses
  • SMTP
  • IMAP
  • JSON Pointers
  • XPath and XML namespaces
  • JSON serialization in HTTP outconns
  • SOAP invocations with suds and WSDL prefetching
  • Outgoing JSON adapters
  • Outgoing HTTP timeouts
  • SQL notifications
  • OpenStack Swift notifications
  • New Relic integration
  • Redis clustering
  • Statistics in Redis pruned periodically
  • New SIO types: CSV, Dict, Float, ForceType, List, ListOfDicts, Opaque
  • Bash completion
  • Ability to specify user locale in servers (i.e. en_GB.UTF-8)
  • Startup scripts to start Zato environments when an OS starts
  • Framework for API testing (https://github.com/zatosource/zato-apitest)
  • Ability to output HTML in services using Django templates
  • Message mappers
  • Distributed locks
  • Logging configuration migrated to YAML
  • Ability to hot-deploy code directly from a repository checkout (i.e.
    from GitHub)
  • Improved logging - components have their own log files
  • Web-admin’s logs showing IP of the user connecting to it
  • Apache-like HTTP access log for servers, compatible with popular log
    parsing tools
  • Ability for users to store config in their own ini-like files
  • zato --version is clearer what exact git commit was used to build it
  • Removing of stale pid files in quickstart scripts
  • Started using async Postgres driver to improve performance
  • Made ‘zato start’ work much faster
  • Alembic migrations to ease with upgrades across releases
  • Ability to run servers in Python shell
  • Made service listings in web admin much faster
  • Ability to dump threads on a user signal
  • New tests prior to starting of components make sure they are correctly
    configured
  • Command to run ipython with Zato-related packages on PYTHONPATH
  • Startup services invoked when a server is starting

What next?

Only documentation and fixes for any issues spotted will now be seen to.
For anyone tracking the progress on GitHub, please use the dedicated
support/2.0 branch available over here:

Installation for buildone one’s own packages are here -
https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2014-November/000650.html

For now, support/2.0 and master will be identical but at one point they
will inevitably diverge and the final release will be built from
support/2.0.

This is very impressive congrats.
On Nov 4, 2014 2:36 AM, “Dariusz Suchojad” dsuch@zato.io wrote:

Hello,

I’m very happy to announce the feature freeze for Zato 2.0.

Not all of what was originally planned made it in but the list of what
2.0 will contain is still impressive and includes, among others:

  • REST services
  • Redis-based REST publish/subscribe
  • RESTful HTTP channels
  • OAuth
  • XPath-based security
  • API Keys-based security
  • NTLM security
  • Amazon AWS security
  • SSL/TLS for channels and outgoing connections
  • Role-based access control (RBAC) for HTTP channels
  • OpenID in web admin
  • Cassandra connections and pre-compiled query templates
  • Cloud OpenStack Swift connections
  • Cloud Amazon S3
  • Solr
  • ElasticSearch
  • Odoo/OpenERP connections
  • Support for SQLite
  • Support for MySQL
  • HTTP GUI Audit Log for requests and responses
  • SMTP
  • IMAP
  • JSON Pointers
  • XPath and XML namespaces
  • JSON serialization in HTTP outconns
  • SOAP invocations with suds and WSDL prefetching
  • Outgoing JSON adapters
  • Outgoing HTTP timeouts
  • SQL notifications
  • OpenStack Swift notifications
  • New Relic integration
  • Redis clustering
  • Statistics in Redis pruned periodically
  • New SIO types: CSV, Dict, Float, ForceType, List, ListOfDicts, Opaque
  • Bash completion
  • Ability to specify user locale in servers (i.e. en_GB.UTF-8)
  • Startup scripts to start Zato environments when an OS starts
  • Framework for API testing (https://github.com/zatosource/zato-apitest)
  • Ability to output HTML in services using Django templates
  • Message mappers
  • Distributed locks
  • Logging configuration migrated to YAML
  • Ability to hot-deploy code directly from a repository checkout (i.e.
    from GitHub)
  • Improved logging - components have their own log files
  • Web-admin’s logs showing IP of the user connecting to it
  • Apache-like HTTP access log for servers, compatible with popular log
    parsing tools
  • Ability for users to store config in their own ini-like files
  • zato --version is clearer what exact git commit was used to build it
  • Removing of stale pid files in quickstart scripts
  • Started using async Postgres driver to improve performance
  • Made ‘zato start’ work much faster
  • Alembic migrations to ease with upgrades across releases
  • Ability to run servers in Python shell
  • Made service listings in web admin much faster
  • Ability to dump threads on a user signal
  • New tests prior to starting of components make sure they are correctly
    configured
  • Command to run ipython with Zato-related packages on PYTHONPATH
  • Startup services invoked when a server is starting

What next?

Only documentation and fixes for any issues spotted will now be seen to.
For anyone tracking the progress on GitHub, please use the dedicated
support/2.0 branch available over here:

https://github.com/zatosource/zato/tree/support/2.0

Installation for buildone one’s own packages are here -

https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2014-November/000650.html

For now, support/2.0 and master will be identical but at one point they
will inevitably diverge and the final release will be built from
support/2.0.

Hi,

Congratulations on reaching this significant milestone!

Regards,

Myroslav Opyr

On Tue, Nov 4, 2014 at 12:36 PM, Dariusz Suchojad dsuch@zato.io wrote:

Hello,

I’m very happy to announce the feature freeze for Zato 2.0.

Not all of what was originally planned made it in but the list of what
2.0 will contain is still impressive and includes, among others:

  • REST services
  • Redis-based REST publish/subscribe
  • RESTful HTTP channels
  • OAuth
  • XPath-based security
  • API Keys-based security
  • NTLM security
  • Amazon AWS security
  • SSL/TLS for channels and outgoing connections
  • Role-based access control (RBAC) for HTTP channels
  • OpenID in web admin
  • Cassandra connections and pre-compiled query templates
  • Cloud OpenStack Swift connections
  • Cloud Amazon S3
  • Solr
  • ElasticSearch
  • Odoo/OpenERP connections
  • Support for SQLite
  • Support for MySQL
  • HTTP GUI Audit Log for requests and responses
  • SMTP
  • IMAP
  • JSON Pointers
  • XPath and XML namespaces
  • JSON serialization in HTTP outconns
  • SOAP invocations with suds and WSDL prefetching
  • Outgoing JSON adapters
  • Outgoing HTTP timeouts
  • SQL notifications
  • OpenStack Swift notifications
  • New Relic integration
  • Redis clustering
  • Statistics in Redis pruned periodically
  • New SIO types: CSV, Dict, Float, ForceType, List, ListOfDicts, Opaque
  • Bash completion
  • Ability to specify user locale in servers (i.e. en_GB.UTF-8)
  • Startup scripts to start Zato environments when an OS starts
  • Framework for API testing (https://github.com/zatosource/zato-apitest)
  • Ability to output HTML in services using Django templates
  • Message mappers
  • Distributed locks
  • Logging configuration migrated to YAML
  • Ability to hot-deploy code directly from a repository checkout (i.e.
    from GitHub)
  • Improved logging - components have their own log files
  • Web-admin’s logs showing IP of the user connecting to it
  • Apache-like HTTP access log for servers, compatible with popular log
    parsing tools
  • Ability for users to store config in their own ini-like files
  • zato --version is clearer what exact git commit was used to build it
  • Removing of stale pid files in quickstart scripts
  • Started using async Postgres driver to improve performance
  • Made ‘zato start’ work much faster
  • Alembic migrations to ease with upgrades across releases
  • Ability to run servers in Python shell
  • Made service listings in web admin much faster
  • Ability to dump threads on a user signal
  • New tests prior to starting of components make sure they are correctly
    configured
  • Command to run ipython with Zato-related packages on PYTHONPATH
  • Startup services invoked when a server is starting

What next?

Only documentation and fixes for any issues spotted will now be seen to.
For anyone tracking the progress on GitHub, please use the dedicated
support/2.0 branch available over here:

https://github.com/zatosource/zato/tree/support/2.0

Installation for buildone one’s own packages are here -

https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2014-November=
/000650.html

For now, support/2.0 and master will be identical but at one point they
will inevitably diverge and the final release will be built from
support/2.0.

Nice to hear
Congrats!!

On Tue, Nov 4, 2014 at 2:24 PM, Danilo Chilene bicofino@gmail.com wrote:

Good job!

On Tue, Nov 4, 2014 at 4:19 PM, Ivan Villareal ivaano@gmail.com wrote:

This is very impressive congrats.
On Nov 4, 2014 2:36 AM, “Dariusz Suchojad” dsuch@zato.io wrote:

Hello,

I’m very happy to announce the feature freeze for Zato 2.0.

Not all of what was originally planned made it in but the list of what
2.0 will contain is still impressive and includes, among others:

  • REST services
  • Redis-based REST publish/subscribe
  • RESTful HTTP channels
  • OAuth
  • XPath-based security
  • API Keys-based security
  • NTLM security
  • Amazon AWS security
  • SSL/TLS for channels and outgoing connections
  • Role-based access control (RBAC) for HTTP channels
  • OpenID in web admin
  • Cassandra connections and pre-compiled query templates
  • Cloud OpenStack Swift connections
  • Cloud Amazon S3
  • Solr
  • ElasticSearch
  • Odoo/OpenERP connections
  • Support for SQLite
  • Support for MySQL
  • HTTP GUI Audit Log for requests and responses
  • SMTP
  • IMAP
  • JSON Pointers
  • XPath and XML namespaces
  • JSON serialization in HTTP outconns
  • SOAP invocations with suds and WSDL prefetching
  • Outgoing JSON adapters
  • Outgoing HTTP timeouts
  • SQL notifications
  • OpenStack Swift notifications
  • New Relic integration
  • Redis clustering
  • Statistics in Redis pruned periodically
  • New SIO types: CSV, Dict, Float, ForceType, List, ListOfDicts, Opaque
  • Bash completion
  • Ability to specify user locale in servers (i.e. en_GB.UTF-8)
  • Startup scripts to start Zato environments when an OS starts
  • Framework for API testing (https://github.com/zatosource/zato-apitest)
  • Ability to output HTML in services using Django templates
  • Message mappers
  • Distributed locks
  • Logging configuration migrated to YAML
  • Ability to hot-deploy code directly from a repository checkout (i.e.
    from GitHub)
  • Improved logging - components have their own log files
  • Web-admin’s logs showing IP of the user connecting to it
  • Apache-like HTTP access log for servers, compatible with popular log
    parsing tools
  • Ability for users to store config in their own ini-like files
  • zato --version is clearer what exact git commit was used to build it
  • Removing of stale pid files in quickstart scripts
  • Started using async Postgres driver to improve performance
  • Made ‘zato start’ work much faster
  • Alembic migrations to ease with upgrades across releases
  • Ability to run servers in Python shell
  • Made service listings in web admin much faster
  • Ability to dump threads on a user signal
  • New tests prior to starting of components make sure they are correctly
    configured
  • Command to run ipython with Zato-related packages on PYTHONPATH
  • Startup services invoked when a server is starting

What next?

Only documentation and fixes for any issues spotted will now be seen to.
For anyone tracking the progress on GitHub, please use the dedicated
support/2.0 branch available over here:

https://github.com/zatosource/zato/tree/support/2.0

Installation for buildone one’s own packages are here -

https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2014-November/000650.html

For now, support/2.0 and master will be identical but at one point they
will inevitably diverge and the final release will be built from
support/2.0.

Good job!

On Tue, Nov 4, 2014 at 4:19 PM, Ivan Villareal ivaano@gmail.com wrote:

This is very impressive congrats.
On Nov 4, 2014 2:36 AM, “Dariusz Suchojad” dsuch@zato.io wrote:

Hello,

I’m very happy to announce the feature freeze for Zato 2.0.

Not all of what was originally planned made it in but the list of what
2.0 will contain is still impressive and includes, among others:

  • REST services
  • Redis-based REST publish/subscribe
  • RESTful HTTP channels
  • OAuth
  • XPath-based security
  • API Keys-based security
  • NTLM security
  • Amazon AWS security
  • SSL/TLS for channels and outgoing connections
  • Role-based access control (RBAC) for HTTP channels
  • OpenID in web admin
  • Cassandra connections and pre-compiled query templates
  • Cloud OpenStack Swift connections
  • Cloud Amazon S3
  • Solr
  • ElasticSearch
  • Odoo/OpenERP connections
  • Support for SQLite
  • Support for MySQL
  • HTTP GUI Audit Log for requests and responses
  • SMTP
  • IMAP
  • JSON Pointers
  • XPath and XML namespaces
  • JSON serialization in HTTP outconns
  • SOAP invocations with suds and WSDL prefetching
  • Outgoing JSON adapters
  • Outgoing HTTP timeouts
  • SQL notifications
  • OpenStack Swift notifications
  • New Relic integration
  • Redis clustering
  • Statistics in Redis pruned periodically
  • New SIO types: CSV, Dict, Float, ForceType, List, ListOfDicts, Opaque
  • Bash completion
  • Ability to specify user locale in servers (i.e. en_GB.UTF-8)
  • Startup scripts to start Zato environments when an OS starts
  • Framework for API testing (https://github.com/zatosource/zato-apitest)
  • Ability to output HTML in services using Django templates
  • Message mappers
  • Distributed locks
  • Logging configuration migrated to YAML
  • Ability to hot-deploy code directly from a repository checkout (i.e.
    from GitHub)
  • Improved logging - components have their own log files
  • Web-admin’s logs showing IP of the user connecting to it
  • Apache-like HTTP access log for servers, compatible with popular log
    parsing tools
  • Ability for users to store config in their own ini-like files
  • zato --version is clearer what exact git commit was used to build it
  • Removing of stale pid files in quickstart scripts
  • Started using async Postgres driver to improve performance
  • Made ‘zato start’ work much faster
  • Alembic migrations to ease with upgrades across releases
  • Ability to run servers in Python shell
  • Made service listings in web admin much faster
  • Ability to dump threads on a user signal
  • New tests prior to starting of components make sure they are correctly
    configured
  • Command to run ipython with Zato-related packages on PYTHONPATH
  • Startup services invoked when a server is starting

What next?

Only documentation and fixes for any issues spotted will now be seen to.
For anyone tracking the progress on GitHub, please use the dedicated
support/2.0 branch available over here:

https://github.com/zatosource/zato/tree/support/2.0

Installation for buildone one’s own packages are here -

https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2014-November/000650.html

For now, support/2.0 and master will be identical but at one point they
will inevitably diverge and the final release will be built from
support/2.0.