All the openstack management API communication will be done via host only network. So in your setup change NAT mode to bridge mode for the interface and assign the ip address as per your setup and try accessing the Dashboard. Specify the IP address of host only interface in the answers file for your respective nodes. Basically You can keep two interfaces for each node( Host-only and bridge). You can access the each node and dashboard from the outside using bridge interface ip address.

Swift is a distributed scale-out that is highly available and provides for eventual consistency of data. Swift can be used to store lots of data efficiently, safely, and cheaply. Swift is OpenStack’s object service. Swift is also OpenStack’s default backup store.

Another great OpenStack resource comes from OpenSource. Com, which is perhaps best known for its regular and frequent OpenStack tutorials, a regular blog, and pointers to guides and free training materials of all kinds. It takes a while to dig through the information on this site, but the time and effort involved is usually well repaid with lots of useful stuff.

The primary goal of DCI is to help Red Hat ship the best quality OpenStack software in the industry, by automating the deployment, testing, and feedback loop with customers and partners for pre- and post-product releases. Today, DCI automatically delivers actionable logs to Red Hat’s quality engineering teams, reducing the amount of time it takes to identify, patch, and introduce fixes back into the community. This allows Red Hat to test real-world use cases, validating each with customer and partner-driven configurations.

Typically, each Swift node handles account, container, and object services. HAproxy and Pacemaker are configured to monitor availability and keep necessary Swift services active and online for high availability. In this solution, each controller system hosts account, container, object, and proxy services.

But looking over the pods that are running, the proxy sees that it can’t handle requests for the mongo service. In this diagram, the proxy knows about three services. On the other hand, it’s got two running pods that match the ‘nginx’ label, so it will handle the routing and traffic management to those pods.