Hi Sinh,
Thanks for the update.
Its already started and showing up in command
neutron agent list
Not sure why the peer ports not created. Its created by plugin or l3-agent?
I am using ml2 plugin.
On Wed, Sep 30, 2015 at 11:51 PM, Sinh Lam wrote:
> can
I'd recommend a few things. The first is you need to disable notifications
in your services including nova. You just set the notifications driver to
noop. Second, you should have some monitoring in place that looks for
queues that go over a certain threshold. There's not a lot of queues that
Hi all, I followed openstack.ork kilo deployment documentation to install
ceilometer for centos 7.
I presume there is some errors in documumentation because "mongo --host
..." command does not create the ceilometer db.
Must I create the db before launching the command ?
Regards
Ignazio
Hi Assaf,
Thanks for that information. Let me check it again.
On Thu, Oct 1, 2015 at 1:36 AM, Assaf Muller wrote:
>
>
> On Wed, Sep 30, 2015 at 3:18 PM, Geo Varghese wrote:
>
>> Hi Sinh,
>>
>> Thanks for the update.
>>
>> Its already started and
Hi Sinh,
Thanks again for that information. Let me check with it.
On Thu, Oct 1, 2015 at 12:55 AM, Sinh Lam
wrote:
> here's my config of my ml2_conf.ini.
>
> [ml2]
>
> type_drivers=vlan
>
> tenant_network_types=vlan
>
> mechanism_drivers=openvswitch
>
>
FYI, we've got a bit of a gate snafu this morning in cutting the
devstack / grenade branches for stable/liberty, as devstack-gate did not
yet have the support for stable/liberty in it.
That patch is up at - https://review.openstack.org/#/c/229363/
With any luck this all gets resolved in the next
> On 30 Sep 2015, at 3:48 pm, John Dewey wrote:
>
> Why not run neutron dhcp agents on both nodes?
Yeah have tried this too.
We don’t do this due to metadata, DHCP adds a static route to the metadata
agent (which is the same as the network node running DHCP). If the network
We run nova-metadata on all the compute nodes, then bind 169.254.169.254 to lo
on each HV. This usually works with the standard iptables rule that
nova-metadata add's. Worse case you just add it to the the default rules set
for the compute node. Inside the images I think all you need to do
Thanks for summarizing this Mark. What's the best way to get feedback about
this to the TC? I'd love to see some of the items which I think are common
sense for anyone who can't just blow away devstack and start over to get
added for consideration.
On Tue, Sep 29, 2015 at 11:32 AM, Mark Voelker
Yup. We periodically consume the queue. You can also turn off ceilometer
reporting in the service publishing the notifications, iirc.
> On Sep 30, 2015, at 1:13 PM, Chris Friesen
> wrote:
>
> Hi,
>
> We've recently run into an issue where the notifications.info
Yes, we using swift as backend, and swift running as separate
installation (own keystone, etc).
I can't find any logs about any problems with backend. They should be
logged by glance?
On 09/29/2015 01:21 AM, David Wahlstrom wrote:
George,
What is your storage backend using
Hi Team,
I need a help with following issue
patch-int port is not created in br-tun. I am using kilo version of
openstack in ubuntu 14.04. It was working in icehouse ubuntu 12.04.
Its not created in both controller and compute.
root@Node4:~/compute# ovs-vsctl show
12 matches
Mail list logo