On 2016-04-29 08:41:46 -0600 (-0600), Mark Carlson wrote:
> OpenStack could request a port number be assigned for default use:
> https://tools.ietf.org/html/rfc6335
As discovered when Keystone did this several years ago, the port
numbers being assigned at this stage have tipped over into the
defau
...and we just landed a patch to use the 6200 range for examples.
https://review.openstack.org/#/c/274840/
--John
On 29 Apr 2016, at 9:26, John Dickinson wrote:
> The "bind_port" setting in Swift's config files is required to be explicitly
> set. It doesn't matter what the number is. If yo
OpenStack could request a port number be assigned for default use:
https://tools.ietf.org/html/rfc6335
-- mark
> On Apr 29, 2016, at 8:26 AM, John Dickinson wrote:
>
> The "bind_port" setting in Swift's config files is required to be explicitly
> set. It doesn't matter what the number is. If y
Hi ALL
I am currently testing openstack liberty in my centos 7 environment.
I am planning to boot vm from volume using ceph backend.
all the instances volumes are shared among all the compute nodes and I am
able to do the nova migrate and nova live-migration.
when I was testing the nova evacuat
The "bind_port" setting in Swift's config files is required to be explicitly
set. It doesn't matter what the number is. If you have a port conflict with
another service, feel free to change it.
As to why port 6000 was used initially... The truth is probably lost to the
mists of time. However, I
That looks like a bug. We've faced with the same problem, but after
RabbitMQ failover usually. Try to restart compute agents. If the situation
is the same - please send the logs here (at least about the start).
Nadya
On Fri, Apr 29, 2016 at 2:24 PM, Florian Rommel <
florian.rom...@datalounges.com
Hi, they are started and nothing in the logs.. actually…
thats the weird part and there are about 450 VMs running currently in this
environment.
//Florian
> On 29 Apr 2016, at 13:25, Nadya Shakhat wrote:
>
> OK, so as you see there are no cpu-samples from computes. Make sure that
> Ceilom
OK, so as you see there are no cpu-samples from computes. Make sure that
Ceilometer compute service is running. If it is, I would recommend to check
the logs on compute nodes. I assume that there is at least one instance
running, is that right?
Nadya
On Fri, Apr 29, 2016 at 1:12 PM, Florian Romme
Hi Florian,
Could you please provide the output of the following commands:
1. ceilometer meter-list
2. ceilometer sample-list -m cpu_util -l 1
3. ceilometer sample-list -m cpu -l 1
One more question: do you use the default pipeline.yaml?
Nadya
On Fri, Apr 29, 2016 at 12:43 PM, Florian Rommel <
Hi Nadya, here it is:
output from ceilometer sample-list -m cpu_util -l 1
+-+--+--++--+---+
| Resource ID | Name | Type | Volume | Unit | Timestamp |
+-+--+--++--+---+
+-+--+--++--+———
On 29/04/2016 10:12, Peter Brouwer wrote:
Hello All,
When looking at the ports used by the system I noticed port 6000 is
already in use before starting the swift services.
In the swift object-server.conf file the default port setting is 6000
to, so yes when starting the swift object serve
Hi, I have Openstack Liberty running and I have ceilometer running as well..
all good but certain meters like cpu_util are not coming up after days of
running.
Its weird because i have quite a few other meters.. like the ones that come
from the compute agent but not the ones from the notifier a
Hello All,
When looking at the ports used by the system I noticed port 6000 is
already in use before starting the swift services.
In the swift object-server.conf file the default port setting is 6000
to, so yes when starting the swift object server there is an error
message in the correspon
Hi,
Are you sure I need to make a new Fuel plugin? I assumed this feature
handles the physnet generation already.
This part is ok, I guesse.
But, as stated in my previous mail, when 2 external networks are
configured, then the network_scheme section assigns 2 different values
to the roles neu
14 matches
Mail list logo
