+1 the entire brainstorm session on what they should be called besides tags is
rather demeaning. There is obvious disagreement between what the TC wants to
implement and what the ops folks want to implement. Discussions that stoop to
this level increase the divide instead of shrinking it. Ple
> On Jun 4, 2015, at 6:12 PM, JJ Asghar wrote:
>
> I have cut a new release of the knife-openstack[1] gem today. We have a
> couple new features[2] which has been asked for a while.
I have pushed another pre-release (1.2.0.rc2) of knife-openstack.
The main change is support for the `—bootst
Forgive the top posting.
Thank you Jay for your clarification and apology.
I wrote the piece below **before** you sent out your email this
afternoon, so again this is nothing personal and not targeted at any
**specific** person.
With that said, I still think that what I have to say is still
Following on from the HPC Ops meetup in Vancouver
(https://etherpad.openstack.org/p/YVR-ops-hpc), Alvaro has been working on the
spot market proposal for the nova backlog.
Comments are welcome on https://review.openstack.org/#/c/104883/
Tim
___
Open
Hello,
(cross-posting from openst...@lists.openstack.org)
I am reaching out in the hopes that someone may have seen this issue before
or have some ideas on what might be going wrong. Apologies if this has
already been discussed elsewhere, I did search quite a bit but only found
mention of a simil
Jay Pipes wrote:
In short, I would love it if the Ops Tags team would stick with binary
tag definitions -- a tag should mean one thing and one thing only.
I absolutely agree Jay. I think the path that is currently being pursued
adds a lot of challenges without appropriate offsetting benefits.
Cross-posting to -operators and -dev because this involves *packagers*
of OpenStack, as well as operators who use those packages.
Hello Operators,
First, let me start out by saying if you were offended by my snarky
comments at yesterday's TC meeting [1] regarding the direction of the
Ops Tags
On Tue, 9 Jun 2015, gordon chung wrote:
i still like the idea of splitting polling and processing task.
pros:
- it moves load off poll agents and onto notificaiton agent
- we essentially get free healthcheck events by doing this
con:
to play devil's advocate. the one down side is that now ther
On Tue, 9 Jun 2015, Luo Gangyi wrote:
In current, ceilometer load pollsters by agent namespace, So do you
mean you want load pollsters one by one through their name(maybe
defined in pipeline.yaml)?
If loading all pollsters in one time do not cost much, I think your
change is bit unnecessary. Bu
The router-interface-add commands attaches a subnet to a router.
To add a route (or routes) to a router, try the following:
Syntax: neutron router-update --routes type=dict list=true
destination=,nexthop=
To add multiple routes:
Syntax: neutron router-update --routes type=dict list=true
des
Hi james,
Thanks for the reply
Through Neutron command "neutron router-create / router-update" we can't
add routes to a router, right ?
I could not find any way to add routes to a router.
I think. "#neutron router-interface-add" command internally add routes to
router, right ?
Could you please sh
There are two kinds of live migration, with shared storage and without
shared storage. If you don't have shared storage (like CEPH or glusterfs or
NFS) you need to pass in the --block-migrate flag to manually copy the
volumes across. (It can be slow.)
For info on doing this with CEPH:
http://ceph.
Hi Folks,I have done a multinode Kilo installation (with controller node, network node, 2 compute nodes). Now I am trying for a live-migration from one host to the other. But I am getting an error :
ERROR
(BadRequest): host1 is not on shared storage: Live
migration can not be used with
Hi Saju,
Host routes added to a subnet get pushed to the instances in that subnet via
dhcp.
A route added to a router via router-create or router-update is added to the
routing table within the qrouter namespace and affects all connected
subnets/instances.
James
Sent from my iPhone
> On Ju
Hi James.
I replaced the external gre with flat and everything works like a charm.
Thanks
Miguel.
El 09/06/15 14:14, James Denton escribió:
Hi Miguel,
An external network should really be a vlan or flat network that has
some external gateway in your environment. Although sometimes gre and
v
First of all, apologies if this belongs strictly to openstack-docs,
based on multiple discussions in Vancouver I'd like more people to be aware of
this.
As announced in April and at the summit in May, RabbitMQ
team at Pivotal would like to help with OpenStack documentation and operations
experie
Hi,
Can we add static routes to the router which created by "#neutron
router-create" command ?
What is the defference static routes of router and --host_routes of subnet ?
I also would like to know use case of static routes of router and
--host_routes of subnet ?
Regards
Saju Madhavan
+91 095351
17 matches
Mail list logo
