TripleO QuickStart Ocata branch Deployment with feature sets and nodes configuration (topology) seperated

Posted by dba477 on Apr 11, 2017 7:33 AM EDT; By Boris Derzhavets
Mail this story
Print this story

In general,Ocata overcloud deployment is more memory consuming then Newton. Minimal memory requirements highlighted bellow. Also minor trobleshooting step was undertaken several times right after overcloud deployment. Command `pcs resource cleanup` was issued after detecting resources failed to start after original deployment completed. The problem above would be gone in case when VIRTHOST (48GB) would allow to allocate 8192 MB for each PCS Cluster's Controller. Sshuttle command line was also modified to provide access to control plane and external network from workstation at a time.

Full Story

» Read more about: Story Type: Tutorial; Groups: Red Hat, Virtualization

« Return to the newswire homepage

This topic does not have any threads posted yet!

You cannot post until you login.