>
>
> Presuming you are deploying Rocky or Queens,
>
Yep, it's Queens.
>
> It goes in the nova.conf file under the [placement] section:
>
> randomize_allocation_candidates = true
>
In triple-o land it seems like the config may need to be somewhere like
nova-scheduler.yaml and laid down via a re
On 11/30/2018 05:52 PM, Mike Carden wrote:
Have you set the placement_randomize_allocation_candidates CONF option
and are still seeing the packing behaviour?
No I haven't. Where would be the place to do that? In a nova.conf
somewhere that the nova-scheduler containers on the controlle
>
>
> Have you set the placement_randomize_allocation_candidates CONF option
> and are still seeing the packing behaviour?
>
>
No I haven't. Where would be the place to do that? In a nova.conf somewhere
that the nova-scheduler containers on the controller hosts could pick it up?
Just about to depl
On 11/30/2018 02:53 AM, Mike Carden wrote:
I'm seeing a similar issue in Queens deployed via tripleo.
Two x86 compute nodes and one ppc64le node and host aggregates for
virtual instances and baremetal (x86) instances. Baremetal on x86 is
working fine.
All VMs get deployed to compute-0. I can
I'm seeing a similar issue in Queens deployed via tripleo.
Two x86 compute nodes and one ppc64le node and host aggregates for virtual
instances and baremetal (x86) instances. Baremetal on x86 is working fine.
All VMs get deployed to compute-0. I can live migrate VMs to compute-1 and
all is well,
On 11/28/2018 02:50 AM, Zufar Dhiyaulhaq wrote:
Hi,
Thank you. I am able to fix this issue by adding this configuration into
nova configuration file in controller node.
driver=filter_scheduler
That's the default:
https://docs.openstack.org/ocata/config-reference/compute/config-options.html
Hi,
Thank you. I am able to fix this issue by adding this configuration into
nova configuration file in controller node.
driver=filter_scheduler
Best Regards
Zufar Dhiyaulhaq
On Tue, Nov 27, 2018 at 5:01 PM Zufar Dhiyaulhaq
wrote:
> Hi Smooney,
> sorry for the last reply. I am attaching wron
Hi Smooney,
sorry for the last reply. I am attaching wrong configuration files. This is
my nova configuration (added randomization from your suggestion) from the
master node (Template jinja2 based).
[DEFAULT]
osapi_compute_listen = {{
hostvars[inventory_hostname]['ansible_ens3f1']['ipv4']['address
Hi Smooney,
thank you for your help. I am trying to enable randomization but not
working. The instance I have created is still in the same node. Below is my
nova configuration (added randomization from your suggestion) from the
master node (Template jinja2 based).
[DEFAULT]
enabled_apis = osapi_c
On Mon, 2018-11-26 at 17:45 +0700, Zufar Dhiyaulhaq wrote:
> Hi,
>
> I am deploying OpenStack with 3 compute node, but I am seeing an abnormal
> distribution of instance, the instance is
> only deployed in a specific compute node, and not distribute among other
> compute node.
>
> this is my n
Hi,
I am deploying OpenStack with 3 compute node, but I am seeing an abnormal
distribution of instance, the instance is only deployed in a specific
compute node, and not distribute among other compute node.
this is my nova.conf from the compute node. (template jinja2 based)
[DEFAULT]
osapi_compu
11 matches
Mail list logo
