Releases: mantl/mantl
1.3.0
After a long hiatus...
The Mantl team is proud to announce a maintenance release for Mantl. The list of changes is quite exhaustive (223+ closed issues and pull requests), you can see all of them here: https://github.com/mantl/mantl/issues?q=is%3Aclosed+milestone%3A1.4 https://github.com/mantl/mantl/issues?q=is%3Aclosed+milestone%3A1.3
Unfortunately, there is not likely a clean upgrade path from 1.3 so we are calling this a pre-release. We also have a great deal of documentation to update. This is our half-way point to getting to Mantl 2.0 which will contain many breaking changes; however 2.0 will be deemed stable and up to date with the bleeding-edge releases.
We are also starting work on Mantl3 which will be a complete rewrite of Mantl orchestration and deployment. You can learn more about the plans for Mantl3 here: #1947
Notable Changes
- Calico has been upgraded to the latest version
- mantl-dns has been upgraded
- Kubernetes dashboard is working
New Team Members
The Mantl project has undergone some serious org restructuring, being that nearly all of the current team members are new to the project.
Please welcome the following team members to the Mantl project:
... and maybe even @Zogg
Come and join us!
We invite you to join us on Mattermost or Gitter; Gitter and Mattermost channels are bridged so there is almost always someone in there ready and willing to help.
If you are interested in contributing to the Mantl project, please post in the Mantl chat channel with your intent and start committing! 👍
We are excited about this endeavor and look forward to working with the community toward a common goal of easy and seamless immutable infrastructure deployment and management!
DISCLAIMER: This is a pre-release and has no guarantee for stability in production. Use at your own risk.
1.2.0
Mantl 1.2 is primarily about bringing in newer releases of core components like Mesos, Marathon, Vault, and Traefik. In addition, we are excited to introduce Kubernetes integration with Consul — now your Kubernetes services will be registered in Consul. This release also includes a number of enhancements and fixes.
New Features
- Mesos 0.28.2 and Marathon 1.1.1.
- Traefik 1.0
- Kubernetes and Consul integration. Kubernetes services are now automatically registered in Consul for service discovery purpose.
- Mantl now has a dedicated RPM repository for each release. This will make upgrades safer.
- Vault 0.5.3 is now installed.
Other improvements and bug fixes
- Mesos log rotation has been improved.
- AWS and GCE providers are more configurable and consistent.
- The ELK addon has been split into individual roles. You can now choose to install each component separately or all at once.
- Calico has been upgraded and has better support for Mesos and Kubernetes.
- Our Vault configuration has been made more secure.
- The Kafka addon is now more easily configured and can create topics at install time.
- Mantl 1.2 includes many more improvements and fixes. Check the changelog for more details.
Known Issues
- In some cases, the etcd service may report a failing health check on one or more nodes. This is an intermittent problem and we are still working to track down the cause. Usually, the failing etcd member will eventually join the cluster and become healthy but please let us know if you are seeing different behavior. #1372
- Mantl 1.2 requires, at minimum, Centos 7.2 (1511). Please run playbooks/upgrade-packages.yml before installing.
- There have been a few additions to the security.yml file. It is important to re-run ./security-setup if you already have a Mantl security.yml file.
- The Marathon UI was updated in version 1.1.1. It now provides the ability to view stderr/stdout logs for tasks that are running. However, this feature is not working at this time. As a workaround, you can view the logs using the Mesos UI. See issue #1530 for more information.
Getting Support
If you encounter any issues, please open a Github Issue against the project. We review issues daily.
We also have a gitter chat room. Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
Cisco Intercloud Services provides support for OpenStack based deployments of Mantl.
1.2.0-RC2
The Mantl 1.2 is primarily about bringing in newer releases of core components like Mesos, Marathon, Vault, and Traefik. In addition, we are excited to introduce Kubernetes integration with Consul — now your Kubernetes services will be registered in Consul. This release also includes a number of enhancements and fixes.
New Features
- Mesos 0.28.2 and Marathon 1.1.1.
- Traefik 1.0
- Kubernetes and Consul integration. Kubernetes services are not automatically registered in Consul for service discovery purpose.
- Mantl now has a dedicated RPM repository for each release. This will make upgrades safer.
- Vault 0.5.3 is now installed.
Other improvements and bug fixes
- Mesos log rotation has been improved.
- AWS and GCE providers are more configurable and consistent.
- The ELK addon has been split into individual roles. You can now choose to install each component separately or all at once.
- Calico has been upgraded and has better support for Mesos and Kubernetes.
- Our Vault configuration has been made more secure.
- The Kafka addon is now more easily configured and can create topics at install time.
- Mantl 1.2 includes many more improvements and fixes. Check the changelog for more details.
Known Issues
- In some cases, the etcd service may report a failing health check on one or more nodes. This is an intermittent problem and we are still working to track down the cause. Usually, the failing etcd member will eventually join the cluster and become healthy but please let us know if you are seeing different behavior. #1372
- Mantl 1.2 requires, at minimum, Centos 7.2 (1511). Please run playbooks/upgrade-packages.yml before installing.
- There have been a few additions to the security.yml file. It is important to re-run ./security-setup if you already have a Mantl security.yml file.
- The Marathon UI was updated in version 1.1.1. It now provides the ability to view stderr/stdout logs for tasks that are running. However, this feature is not working at this time. As a workaround, you can view the logs using the Mesos UI. See issue #1530 for more information.
Getting Support
If you encounter any issues, please open a Github Issue against the project. We review issues daily.
We also have a gitter chat room. Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
Cisco Intercloud Services provides support for OpenStack based deployments of Mantl.
1.2.0-RC1
The Mantl 1.2 is primarily about bringing in newer releases of core components like Mesos, Marathon, Vault, and Traefik. In addition, we are excited to introduce Kubernetes integration with Consul — now your Kubernetes services will be registered in Consul. This release also includes a number of enhancements and fixes.
New Features
- Mesos 0.28.2 and Marathon 1.1.1.
- Kubernetes and Consul integration. Kubernetes services are not automatically registered in Consul for service discovery purpose.
- Mantl now has a dedicated RPM repository for each release. This will make upgrades safer.
- Vault 0.5.3 is now installed.
Other improvements and bug fixes
- Mesos log rotation has been improved.
- AWS and GCE providers are more configurable and consistent.
- The ELK addon has been split into individual roles. You can now choose to install each component separately or all at once.
- Calico has been upgraded and has better support for Mesos and Kubernetes.
- Our Vault configuration has been made more secure.
- The Kafka addon is now more easily configured and can create topics at install time.
- Mantl 1.2 includes many more improvements and fixes. Check the changelog for more details.
Known Issues
- In some cases, the etcd service may report a failing health check on one or more nodes. This is an intermittent problem and we are still working to track down the cause. Usually, the failing etcd member will eventually join the cluster and become healthy but please let us know if you are seeing different behavior. #1372
- Mantl 1.2 requires, at minimum, Centos 7.2 (1511). Please run playbooks/upgrade-packages.yml before installing.
- There have been a few additions to the security.yml file. It is important to re-run ./security-setup if you already have a Mantl security.yml file.
- The Marathon UI was updated in version 1.1.1. It now provides the ability to view stderr/stdout logs for tasks that are running. However, this feature is not working at this time. As a workaround, you can view the logs using the Mesos UI. See issue #1530 for more information.
Getting Support
If you encounter any issues, please open a Github Issue against the project. We review issues daily.
We also have a gitter chat room. Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
Cisco Intercloud Services provides support for OpenStack based deployments of Mantl.
1.2.0-BETA1
docs: 1.2 upgrade instructions
1.1.0
Mantl 1.1 is a huge release that includes major additions like Kubernetes support along with a large number of smaller improvements and fixes. We continue to work on stabilizing the platform and improving the documentation.
New Features
- Kubernetes! Mantl now includes a technical preview for running Kubernetes
alongside Mesos in your Mantl cluster. Dedicated Kubernetes worker nodes are
provisioned to run your Kubernetes pods and services. - Docker 1.11.1. Mantl now ships with the latest Docker release.
- We've updated Consul to the 0.6.4 release.
- Joyent Triton and
CenturyLinkCloud are welcome additions to the list of
cloud providers that work with Mantl. The vSphere, AWS, and Openstack
providers have also undergone improvements. We are grateful to the community
who have contributed much of the provider support. - The ELK framework addon has been improved in several ways. Kibana now runs in
Mesos instead of on control nodes. Kibana is also configured to use an
Elasticsearch client node instead of one the data nodes that are managed by
the Elasticsearch Mesos framework. The client node can also be used by other
applications as a smart load balancer for the Elasticsearch cluster. - Thanks to excellent contributions from the community, we now have
documentation for installing Mantl in on-premise, bare-metal environments. - Apache Kafka is now available as a Mantl addon. It
runs via the Kafka Mesos Framework.
Other improvements and bug fixes
- Mantl 1.1 includes major logging improvements. Unnecessary verbosity has been
reduced across various services and Mesos logging has been completely reworked
to be simpler and easier to manage. - We've made several improvements to the configurability, stability, and
maintenance of Zookeeper on Mantl clusters. - The nginx proxies for Consul, Marathon, and Mesos have been consolidated into
a single Docker container. - Our multi-cloud automated testing suite continues to improve and we are
building across the AWS, GCE, and Digitalocean platforms. Work is ongoing to
increase the resiliency of the test suite. We are also using a new version of
the Mantl Docker image in the automated build system. - We've introduced the Mantl-DNS package to normalize the DNS configuration of
Mantl clusters across cloud providers and solve some common DNS resolution
problems. - Chronos and Collectd are now optional and can be installed as addons.
- NTP synchronization via chrony is now part of the default installation.
- A new Spark example has been included.
- Mantl 1.1 includes many more improvements and fixes. Check the
changelog for
more details.
Known Issues
- Kubernetes support is currently problematic in the Vagrant install. We
recommend that you use a supported cloud provider to run Kubernetes on Mantl
at this time. #1365 - In some cases, the etcd service may report a failing health check on one or
more nodes. This is an intermittent problem and we are still working to track
down the cause. Usually, the failing etcd member will eventually join the
cluster and become healthy but please let us know if you are seeing different
behavior. #1372 - Mantl 1.1 requires Centos 7.2 (1511). Please run
playbooks/upgrade-packages.yml before installing. - There have been a few additions to the security.yml file. It is important to
re-run ./security-setup if you already have a Mantl security.yml file.
Getting Support
If you encounter any issues, please open a Github Issue against the project. We review issues daily.
We also have a gitter chat room. Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
Cisco Intercloud Services provides support for OpenStack based deployments of Mantl.
1.0.3
The Mantl 1.0.3 release includes an improved ELK stack experience, more stable and reliable system packaging, and a number of other improvements, bug fixes, and documentation updates.
New Features
- Mantl system packages are now installed from yum repositories which helps to improve reliability during the provisioning process.
- ELK Stack: The ELK stack was made available as an addon in the Mantl 1.0 release. Mantl 1.0.3 improves this experience by integrating the Elasticsearch Framework and Kibana UIs directly into Mantl UI. No more security group or firewall tweaks required.
- A sample Kibana dashboard is imported by default when the ELK addon is installed.
- Jupyter notebook example (community contribution — thanks @mcapuccini!).
- iptables addon to secure traffic within the cluster (community contribution — thanks @eirslett!).
Security
- The Elasticsearch Framework and Kibana UIs are behind SSL and Basic Authentication by default.
- Optional iptables role to secure traffic within a Mantl cluster.
Other improvements and bug fixes
- Mantl rename: we replaced all references to "microservices-infrastructure" with "Mantl". Let us know if we missed any!
- The Docker and Collectd roles are no longer so tightly entangled.
- The sample Ansible provisioning playbook has been renamed from
terraform.sample.ymlto justsample.yml. - We are continuing to work on hardening our multi-cloud integration testing via Travis CI. Automated testing is currently occurring on GCE, AWS, and DigitalOcean. OpenStack is coming soon.
- Mantl API will now run correctly again on clusters with Mesos authentication disabled.
- GCE Terraform modules now work with the most recent releases of Terraform (0.6.11+).
- We've made a lot of documentation updates. Please let us know what's unclear or missing.
Known Issues
- Mantl 1.0.3 requires Centos 7.2 (1511). Please run
playbooks/upgrade-packages.ymlbefore installing. - There have been a few additions to the security.yml file. It is important to re-run
./security-setupif you already have a pre-1.0 Mantl security.yml file.
Getting Support
If you encounter any issues, please open a Github Issue against the project. We review issues daily.
We also have a gitter chat room. Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
Cisco Intercloud Services provides support for OpenStack based deployments of Mantl.
1.0.2
The Mantl 1.0 release includes a number of upgraded components, improvements, and bug fixes.
New Features
- ELK Stack. The ELK addon combines Elasticsearch, Logstash, and Kibana to provide automatic log shipping and metrics collection from all Mantl nodes to an Elasticsearch cluster. Kibana is available to visualize and analyze this data.
Upgraded packages
- Mesos 0.25 and Marathon 0.13.
- Consul 0.6.3, consul-template 0.12.2, and consul-cli 0.1.1.
- Vault has been upgraded to 0.4.1 and SSL configuration has been simplified.
Deployment improvements
- Multi-node Vagrant support has been added to allow more realistic Mantl testing and evaluation scenarios.
- Terraform configurations have been refactored into modules on AWS, OpenStack and GCE
- Docker storage has been significantly improved with the option of using OverlayFS (default), Devicemapper or Btrfs (experimental) on an LVM volume.
- Documentation and ansible playbooks are provided for upgrading an existing Mantl 0.5.1 cluster to 1.0. This is considered a preview — use with caution on production clusters.
Security
- Go binaries have been upgraded to 1.5.3 to address CVE-2015-8618
- Consul ACLs are now set to default deny
- Marathon file permissions have been tightened
Other improvements and bug fixes
- The Kong API gateway backed by Cassandra is included as an example app.
- Mantl is now performing multi-cloud integration testing on Amazon AWS, Google Cloud and Digital Ocean via Travis CI.
- There have been a number of documentation improvements.
Known Issues
- Mantl 1.0 requires Centos 7.2 (1511). Please run
playbooks/upgrade-packages.ymlbefore installing. - There have been a few additions to the security.yml file. It is important to re-run
./security-setupif you already have a Mantl security.yml file. - If you have a previous version of the CiscoCloud/microservices-infrastructure vagrant box, you will need to remove it before you are able to build a Vagrant-based Mantl cluster.
Getting Support
If you encounter any issues, please open a Github Issue against the project. We review issues daily.
We also have a gitter chat room. Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
Cisco Intercloud Services provides support for OpenStack based deployments of Mantl.
1.0.1
The Mantl 1.0 release includes a number of upgraded components, improvements, and bug fixes.
New Features
Upgraded packages
- Mesos 0.25 and Marathon 0.13.
- Consul 0.6.3, consul-template 0.12.2, and consul-cli 0.1.1.
- Vault has been upgraded to 0.4.1 and SSL configuration has been simplified.
Deployment improvements
- Multi-node Vagrant support has been added to allow more realistic Mantl testing and evaluation scenarios.
- Terraform configurations have been refactored into modules on AWS, OpenStack and GCE
- Docker storage has been significantly improved with the option of using OverlayFS (default), Devicemapper or Btrfs (experimental) on an LVM volume.
- Documentation and ansible playbooks are provided for upgrading an existing Mantl 0.5.1 cluster to 1.0. This is considered a preview — use with caution on production clusters.
Security
- Go binaries have been upgraded to 1.5.3 to address CVE-2015-8618
- Consul ACLs are now set to default deny
- Marathon file permissions have been tightened
Other improvements and bug fixes
- The Kong API gateway backed by Cassandra is included as an example app.
- Mantl is now performing multi-cloud integration testing on Amazon AWS, Google Cloud and Digital Ocean via Travis CI.
- There have been a number of documentation improvements.
Known Issues
- Mantl 1.0 requires Centos 7.2 (1511). Please run
playbooks/upgrade-packages.ymlbefore installing. - There have been a few additions to the security.yml file. It is important to re-run
./security-setupif you already have a Mantl security.yml file. - If you have a previous version of the CiscoCloud/microservices-infrastructure vagrant box, you will need to remove it before you are able to build a Vagrant-based Mantl cluster.
Getting Support
If you encounter any issues, please open a Github Issue against the project. We review issues daily.
We also have a gitter chat room. Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
Cisco Intercloud Services provides support for OpenStack based deployments of Mantl.
1.0
The Mantl 1.0 release includes a number of upgraded components, improvements, and bug fixes.
New Features
Upgraded packages
- Mesos 0.25 and Marathon 0.13.
- Consul 0.6.3, consul-template 0.12.2, and consul-cli 0.1.1.
- Vault has been upgraded to 0.4.1 and SSL configuration has been simplified.
Deployment improvements
- Multi-node Vagrant support has been added to allow more realistic Mantl testing and evaluation scenarios.
- Terraform configurations have been refactored into modules on AWS, OpenStack and GCE
- Docker storage has been significantly improved with the option of using OverlayFS (default), Devicemapper or Btrfs (experimental) on an LVM volume.
- Documentation and ansible playbooks are provided for upgrading an existing Mantl 0.5.1 cluster to 1.0. This is considered a preview — use with caution on production clusters.
Security
- Go binaries have been upgraded to 1.5.3 to address CVE-2015-8618
- Consul ACLs are now set to default deny
- Marathon file permissions have been tightened
Other improvements and bug fixes
- The Kong API gateway backed by Cassandra is included as an example app.
- Mantl is now performing multi-cloud integration testing on Amazon AWS, Google Cloud and Digital Ocean via Travis CI.
- There have been a number of documentation improvements.
Known Issues
- Mantl 1.0 requires Centos 7.2 (1511). Please run
playbooks/upgrade-packages.ymlbefore installing. - There have been a few additions to the security.yml file. It is important to re-run
./security-setupif you already have a Mantl security.yml file. - If you have a previous version of the CiscoCloud/microservices-infrastructure vagrant box, you will need to remove it before you are able to build a Vagrant-based Mantl cluster.
Getting Support
If you encounter any issues, please open a Github Issue against the project. We review issues daily.
We also have a gitter chat room. Drop by and ask any questions you might have. We'd be happy to walk you through your first deployment.
Cisco Intercloud Services provides support for OpenStack based deployments of Mantl.