ur own decision here. If we can pair magnum-api
>>>> with magnum-conductor as a unit, we can remove the indirection API and
>>>> allow both binaries to access DB. This could mitigate the potential
>>>> performance bottleneck of message queue. On the other hand, if
ss DB. This could mitigate the potential
>>> performance bottleneck of message queue. On the other hand, if we stay with
>>> the current design, we would allow magnum-api and magnum-conductor to scale
>>> independently. Thoughts?
>>>
>>>
>>>
>>&
queue. On the other hand, if we stay with
>> the current design, we would allow magnum-api and magnum-conductor to scale
>> independently. Thoughts?
>>
>>
>>
>> [1] https://review.openstack.org/#/c/184791/
>>
>>
>>
>> Best regards,
>>
&
hould display proper error message. M-api service should only
> have read permission.
>
>
>
> Regards,
>
> Madhuri
>
>
>
> *From:* Corey O'Brien [mailto:coreypobr...@gmail.com
> ]
> *Sent:* Wednesday, February 3, 2016 6:50 PM
> *To:* OpenStack Development
(not for usage questions)
Subject: Re: [openstack-dev] [Magnum] API service won't work if conductor down?
Corey the one you are talking about has changed to coe-service-*.
Eli, IMO we should display proper error message. M-api service should only have
read permission.
Regards,
Madhuri
F
Stack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] API service won't work if conductor down?
The service-* commands aren't related to the magnum services (e.g.
magnum-conductor). The service-* commands are for services on the bay that the
user crea
The service-* commands aren't related to the magnum services (e.g.
magnum-conductor). The service-* commands are for services on the bay that
the user creates and deletes.
Corey
On Wed, Feb 3, 2016 at 2:25 AM Eli Qiao wrote:
> hi
> Whey I try to run magnum service-list to list all services (see
hi
Whey I try to run magnum service-list to list all services (seems now we
only have m-cond service), it m-cond is down(which means no conductor at
all),
API won't response and will return a timeout error.
taget@taget-ThinkStation-P300:~/devstack$ magnum service-list
ERROR: Timed out waiting
