Hi Matt,
I have addressed your comment on patch and uploaded new patch to master
branch.
Could you please check https://review.openstack.org/#/c/437381
Thanks,
Prashant
On Thu, Feb 23, 2017 at 2:34 PM, Prashant Shetty <
prashantshetty1...@gmail.com> wrote:
> Thanks Matt, I found out there was is
Thanks Matt, I found out there was issue in my nova.conf on controller.
[placement] section was missing on controller nova.conf.
Looks like devstack ignores configuring nova.conf if n-cpu is not running.
I have filed https://bugs.launchpad.net/devstack/+bug/1667219 and posted
fix https://review.op
On 2/22/2017 9:33 AM, Prashant Shetty wrote:
Thanks Matt.
Here are the steps I have performed, I dont see any error related to
cell0 now but n-cond still not able to detect computes after discover as
well :(.
Do we need any cell setting on nova-compute nodes as well?.
vmware@cntr11:~/nsbu_cqe_
Thanks Matt.
Here are the steps I have performed, I dont see any error related to cell0
now but n-cond still not able to detect computes after discover as well :(.
Do we need any cell setting on nova-compute nodes as well?.
vmware@cntr11:~/nsbu_cqe_openstack/devstack$ nova service-list
++---
On 2/21/2017 10:38 AM, Prashant Shetty wrote:
Hi Mark,
Thanks for your reply.
I tried "nova-manage cell_v2 discover_hosts" and it returned nothing and
still I have same issue on the node.
Problem seems be the way devstack is getting configured,
As code suggest below we create cell0 on node whe
Appreciate some help on this issue.
Thanks,
Prashant
On Tue, Feb 21, 2017 at 9:08 PM, Prashant Shetty <
prashantshetty1...@gmail.com> wrote:
> Hi Mark,
>
> Thanks for your reply.
>
> I tried "nova-manage cell_v2 discover_hosts" and it returned nothing and
> still I have same issue on the node.
>
Hi Mark,
Thanks for your reply.
I tried "nova-manage cell_v2 discover_hosts" and it returned nothing and
still I have same issue on the node.
Problem seems be the way devstack is getting configured,
As code suggest below we create cell0 on node where n-api and n-cpu runs.
In my case compute is r
On 2/20/2017 10:31 AM, Prashant Shetty wrote:
Thanks Jay for the response. Sorry I missed out on copying right error.
Here is the log:
2017-02-20 14:24:06.211 TRACE nova.conductor.manager NoValidHost: No
valid host was found. There are not enough hosts available.
2017-02-20 14:24:06.211 TRACE no
Thanks Jay for the response. Sorry I missed out on copying right error.
Here is the log:
2017-02-20 14:24:06.211 TRACE nova.conductor.manager NoValidHost: No valid
host was found. There are not enough hosts available.
2017-02-20 14:24:06.211 TRACE nova.conductor.manager
2017-02-20 14:24:06.211 TRA
On 02/20/2017 09:33 AM, Prashant Shetty wrote:
Team,
I have multi node devstack setup with single controller and multiple
computes running stable/ocata.
On compute:
ENABLED_SERVICES=n-cpu,neutron,placement-api
Both KVM and ESxi compute came up fine:
vmware@cntr11:~$ nova hypervisor-list
war
Team,
I have multi node devstack setup with single controller and multiple
computes running stable/ocata.
On compute:
ENABLED_SERVICES=n-cpu,neutron,placement-api
Both KVM and ESxi compute came up fine:
vmware@cntr11:~$ nova hypervisor-list
warnings.warn(msg)
++---
11 matches
Mail list logo