>
>
> 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
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
Hello Brian,
Thanks for the info.
I looked into the code for the metering agent and discovered the following:
1. The metering agent on compute nodes doesn't get notified about DVR
routers running on the node.
2. For DVR routers it tries to meter the rfp- interface(for floating
ips) on the
On 11/30/18 6:06 AM, Matthew Booth wrote:
I have a request to do $SUBJECT in relation to a V2V workflow. The use
case here is conversion of a VM/Physical which was previously powered
off. We want to move its data, but we don't want to be powering on
stuff which wasn't previously on.
This
Still confused by:
[base] -> [service] -> [+ puppet]
not:
[base] -> [puppet]
and
[base] -> [service]
?
Thanks,
Kevin
From: Bogdan Dobrelya [bdobr...@redhat.com]
Sent: Friday, November 30, 2018 5:31 AM
To: Dan Prince; openstack-dev@lists.openstack.org;
On 11/30/18 6:06 AM, Matthew Booth wrote:
I have a request to do $SUBJECT in relation to a V2V workflow. The use
case here is conversion of a VM/Physical which was previously powered
off. We want to move its data, but we don't want to be powering on
stuff which wasn't previously on.
This
On Fri, 2018-11-30 at 09:40 -0500, Mohammed Naser wrote:
>
>
> On Fri, Nov 30, 2018 at 7:07 AM Matthew Booth wrote:
> > I have a request to do $SUBJECT in relation to a V2V workflow. The use
> > case here is conversion of a VM/Physical which was previously powered
> > off. We want to move its
On Fri, 2018-11-30 at 09:40 -0500, Mohammed Naser wrote:
>
>
> On Fri, Nov 30, 2018 at 7:07 AM Matthew Booth wrote:
> > I have a request to do $SUBJECT in relation to a V2V workflow. The use
> > case here is conversion of a VM/Physical which was previously powered
> > off. We want to move its
On 11/29/18 6:42 PM, Jiří Stránský wrote:
On 28. 11. 18 18:29, Bogdan Dobrelya wrote:
On 11/28/18 6:02 PM, Jiří Stránský wrote:
Reiterating again on previous points:
-I'd be fine removing systemd. But lets do it properly and not via 'rpm
-ev --nodeps'.
-Puppet and Ruby *are* required for
I have a request to do $SUBJECT in relation to a V2V workflow. The use
case here is conversion of a VM/Physical which was previously powered
off. We want to move its data, but we don't want to be powering on
stuff which wasn't previously on.
This would involve an api change, and a hopefully very
On Fri, 2018-11-30 at 10:31 +0100, Bogdan Dobrelya wrote:
> On 11/29/18 6:42 PM, Jiří Stránský wrote:
> > On 28. 11. 18 18:29, Bogdan Dobrelya wrote:
> > > On 11/28/18 6:02 PM, Jiří Stránský wrote:
> > > >
> > > >
> > > > > Reiterating again on previous points:
> > > > >
> > > > > -I'd be fine
On 11/30/18 1:52 PM, Dan Prince wrote:
On Fri, 2018-11-30 at 10:31 +0100, Bogdan Dobrelya wrote:
On 11/29/18 6:42 PM, Jiří Stránský wrote:
On 28. 11. 18 18:29, Bogdan Dobrelya wrote:
On 11/28/18 6:02 PM, Jiří Stránský wrote:
Reiterating again on previous points:
-I'd be fine removing
On Fri, Nov 30, 2018 at 7:07 AM Matthew Booth wrote:
> I have a request to do $SUBJECT in relation to a V2V workflow. The use
> case here is conversion of a VM/Physical which was previously powered
> off. We want to move its data, but we don't want to be powering on
> stuff which wasn't
On Fri, Nov 30, 2018 at 7:07 AM Matthew Booth wrote:
> I have a request to do $SUBJECT in relation to a V2V workflow. The use
> case here is conversion of a VM/Physical which was previously powered
> off. We want to move its data, but we don't want to be powering on
> stuff which wasn't
14 matches
Mail list logo