On 2018-08-30 18:08:56 -0500 (-0500), Melvin Hillsman wrote:
[...]
> I also recall us discussing having some documentation or way of
> notifying net new signups of how to interact with the ML
> successfully. An example was having some general guidelines around
> tagging. Also as a maintainer for at
On Thu, Aug 30, 2018 at 09:12:57PM +, Jeremy Stanley wrote:
> On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote:
> [...]
> > What needs to be done for this is full topic categories support
> > under `options` page so people get to filter emails properly.
> [...]
>
> Unfortunately, topic fil
I think the more we can reduce the ML sprawl the better. I also recall us
discussing having some documentation or way of notifying net new signups of
how to interact with the ML successfully. An example was having some
general guidelines around tagging. Also as a maintainer for at least one of
the
Jeremy Stanley wrote:
On 2018-08-30 22:49:26 +0200 (+0200), Thomas Goirand wrote:
[...]
I really don't want this. I'm happy with things being sorted in
multiple lists, even though I'm subscribed to multiples.
IMO this is easily solved by tagging. If emails are properly tagged
(which they typ
On 2018-08-30 22:49:26 +0200 (+0200), Thomas Goirand wrote:
[...]
> I really don't want this. I'm happy with things being sorted in
> multiple lists, even though I'm subscribed to multiples.
I understand where you're coming from, and I used to feel similarly.
I was accustomed to communities where
On 2018-08-30 12:57:31 -0600 (-0600), Chris Friesen wrote:
[...]
> Do we want to merge usage and development onto one list? That
> could be a busy list for someone who's just asking a simple usage
> question.
A counterargument though... projecting the number of unique posts to
all four lists combi
On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote:
[...]
> What needs to be done for this is full topic categories support
> under `options` page so people get to filter emails properly.
[...]
Unfortunately, topic filtering is one of the MM2 features the
Mailman community decided nobody used (o
On 08/30/2018 10:54 AM, Eugen Block wrote:
Hi Jay,
You need to set your ram_allocation_ratio nova.CONF option to 1.0 if
you're running into OOM issues. This will prevent overcommit of memory
on your compute nodes.
I understand that, the overcommitment works quite well most of the time.
It j
On 08/30/2018 11:03 AM, Jeremy Stanley wrote:
The proposal is simple: create a new openstack-discuss mailing list
to cover all the above sorts of discussion and stop using the other
four.
Do we want to merge usage and development onto one list? That could be a busy
list for someone who's jus
Thank you so much Brian.
I was not using "address scope". After your indication I've read about this
feature working together with "subnet pool". However the official
documentation is not so clear. For those looking for something else about
usage of address scope and subnet pool, I recommend this
Absolutely support merging.
Jeremy Stanley wrote:
The openstack, openstack-dev, openstack-sigs and openstack-operators
mailing lists on lists.openstack.org see an increasing amount of
cross-posting and thread fragmentation as conversants attempt to
reach various corners of our community with top
Excerpts from Jeremy Stanley's message of 2018-08-30 17:03:50 +:
> The openstack, openstack-dev, openstack-sigs and openstack-operators
> mailing lists on lists.openstack.org see an increasing amount of
> cross-posting and thread fragmentation as conversants attempt to
> reach various corners o
On 08/30/2018 08:54 AM, Eugen Block wrote:
Hi Jay,
You need to set your ram_allocation_ratio nova.CONF option to 1.0 if you're
running into OOM issues. This will prevent overcommit of memory on your
compute nodes.
I understand that, the overcommitment works quite well most of the time.
It ju
The openstack, openstack-dev, openstack-sigs and openstack-operators
mailing lists on lists.openstack.org see an increasing amount of
cross-posting and thread fragmentation as conversants attempt to
reach various corners of our community with topics of interest to
one or more (and sometimes all) of
Hi, from the logs I think is something missing in mistral executor images
from tacker.
What distribution and install type are you using, latest kolla and kolla
ansible from git?
Regards
On Thu, Aug 30, 2018, 5:09 PM pablo brunetti
wrote:
> Hi,
>
>
> I installed OpenStack Rocky Multinode with K
Hi Jay,
You need to set your ram_allocation_ratio nova.CONF option to 1.0 if
you're running into OOM issues. This will prevent overcommit of
memory on your compute nodes.
I understand that, the overcommitment works quite well most of the time.
It just has been an issue twice when I booted
Hi,
I installed OpenStack Rocky Multinode with Kolla-Ansible. In the Tacker module,
I am having trouble creating the VIM, the status is pending and the VNFFG does
not work because of this. I've activated all the modules that Tacker needs
(Barbican, Mistral, Networking-SFC, Ceilometer, Heat).
Sorry. I was to quick with the send button...
Hi *,
I posted my question in [1] a week ago, but no answer yet.
When does Nova apply its filters (Ram, CPU, etc.)?
Of course at instance creation and (live-)migration of existing
instances. But what about existing instances that have been shutdown
On 08/30/2018 10:19 AM, Eugen Block wrote:
When does Nova apply its filters (Ram, CPU, etc.)?
Of course at instance creation and (live-)migration of existing
instances. But what about existing instances that have been shutdown and
in the meantime more instances on the same hypervisor have been
Hi *,
I posted my question in [1] a week ago, but no answer yet.
When does Nova apply its filters (Ram, CPU, etc.)?
Of course at instance creation and (live-)migration of existing
instances. But what about existing instances that have been shutdown
and in the meantime more instances on the s
20 matches
Mail list logo
