On 17/05/16 17:43, Mark Kirkwood wrote:
I'm seeing some replication errors in the object server log:
May 17 05:27:36 markir-dev-ostor001 object-server: Starting object
replication pass.
May 17 05:27:36 markir-dev-ostor001 object-server: 1/1 (100.00%)
partitions replicated in 0.03s (38.19/sec,
On 18/05/16 16:46, Mark Kirkwood wrote:
On 17/05/16 17:43, Mark Kirkwood wrote:
I've figured out one case:
Adding some debugging code and traceback gives more interesting output
(see attached diff):
May 18 04:31:17 markir-dev-ostor002 object-server: object replication
failure 4, detail Trac
On 17/05/16 17:43, Mark Kirkwood wrote:
(snippage)
I'm seeing some replication errors in the object server log:
May 17 05:27:36 markir-dev-ostor001 object-server: Starting object
replication pass.
May 17 05:27:36 markir-dev-ostor001 object-server: 1/1 (100.00%)
partitions replicated in 0.03s
I would suggest you check the log to see if there is any detail
information. Without that, it is difficult for a community to help you out
of a local issue.
--
Yujun
On Wed, May 18, 2016 at 9:11 AM Yajun wrote:
> Can someone give some advices?
> Thanks in advance.
>
>
>
> Best Regards,
> Junsti
Can someone give some advices?
Thanks in advance.
Best Regards,
Junstin
在2016年05月17日 08:36 ，沈亚军写道：
Hi Team,
I created a OpenStack env in my company, it worked, and I can create VMs. (I
follewed Liberty version CentOS 7 installation guide. My OS is Centos 7; For
network, I selected option
Dear OpenStack Team
May I ask you some questions about the Openstakc Mitaka Horizon Dashboard?
I have followed the Openstack online installation document and your
installation guide http://docs.openstack.org/mitaka/install-guide-ubuntu/
But after I installed the horizon, I cannot access the H
Hi Florian,
great to hear that your problem is solved.
As I pointed out, in Liberty you actually do not need the
"heat_stack_owner" role at all. Just make sure that in your heat.conf the
following option is set to empty value (which AFAIK is default in Liberty):
# Subset of trustor roles to be d
Hello,
According to the documentation [1], it is possible to refer to the name of
a completed task from within DSL by using the *task().name *syntax.
Is it possible to refer to the name of the workflow in a similar way? This
does not seem to be an execution property and is not documented as such.
Hi, thank you for pointing it out, apparently you need to have one of the roles
applied in Liberty (which is what we used), but my demo user had both applied.
If then chooses the lower level access, hence no access. Once I gave the user
only heat_stack_owner i could deploy stacks within the norm
Hi,
are you sure that's "heat_stack_owner" and _not_ "heat_stack_user" role
that is assigned to your normal, non-admin user? These are frequently
confused, but there's a great deal of difference between them, the latter
role indeed has almost no access to Heat API.
Also, what OpenStack version ar
Hi, all, most of our major hurdles are now gone with Openstack and it looks
almost all great now..
Now the tricky part. I have gotten into HEAT and have written many templates
and actually very complex ones too and I would love for normal users and other
tenants to be able to use them but I ke
Solved.
I should remove these entries
net.ipv4.ip_forward=1
net.ipv4.conf.all.rp_filter=0
net.ipv4.conf.default.rp_filter=0
net.bridge.bridge-nf-call-iptables=1
net.bridge.bridge-nf-call-ip6tables=1
from sysctl.conf on compute nodes. I was previously testing the DVR
scenarios and these entries s
HI ALL,
Now, in Aodh CLI, when create a threshold alarm, the
-m/--meter-name must be required.
But, if the user is not familiar with ceilometer or aodh, the user
is not sure what value should give to -m/--meter-name.
So the command "aodh meter list", I think, is needed.
13 matches
Mail list logo
