You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Mitaka OpenStack-Ansible Deployment uses a combination of Ansible and Linux Containers (LXC) to install and manage OpenStack. Ansible provides an automation platform to simplify system and application deployment.
OpenStack-Ansible is now the official OpenStack Foundation deployment tool.
While Docker OpenStack nodes may model correctly under OpenStack-Ansible they are all treated as separate entities and show up as separate servers generally without an IP address to connect to which produces a lot of alerts.
This is predominate on the Controllers but likely to occur on the other node types as well.
There's code and a zproperty to check for the presence of docker containers so can code be added to check of LXC containers?
The text was updated successfully, but these errors were encountered:
Since Mitaka OpenStack-Ansible Deployment uses a combination of Ansible and Linux Containers (LXC) to install and manage OpenStack. Ansible provides an automation platform to simplify system and application deployment.
OpenStack-Ansible is now the official OpenStack Foundation deployment tool.
While Docker OpenStack nodes may model correctly under OpenStack-Ansible they are all treated as separate entities and show up as separate servers generally without an IP address to connect to which produces a lot of alerts.
This is predominate on the Controllers but likely to occur on the other node types as well.
There's code and a zproperty to check for the presence of docker containers so can code be added to check of LXC containers?
The text was updated successfully, but these errors were encountered: