iate. We will continue our
> efforts to make them reasonably efficient.
>
>
>
> Thanks,
>
>
>
> Adrian
>
>
>
>
>
> Regards
>
> -steve
>
>
>
>
>
> Note that it will take a thoughtful approach (subject to discussion) to
> balance these i
e
>
> From: Hongbin Lu
> Reply-To: "openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> Date: Monday, February 29, 2016 at 9:40 AM
> To: "openstack-dev@lists.openstack.org" >
> Subject: [openstack-dev] [magnum] Discussion of
gt; [1] https://review.openstack.org/#/c/184791/
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Hongbin
>>>
>>>
>>>
>>> *From:* Kumari, Madhuri [mailto:madhuri.kum...@intel.com]
>>> *Sent:* February-03-16 10:5
Hi all,
A few thoughts to add:
I like the idea of isolating the masters so that they are not
tenant-controllable, but I don't think the Magnum control plane is the
right place for them. They still need to be running on tenant-owned
resources so that they have access to things like isolated tenant
d, since
> it is hard to work with a gate that takes several hours to complete. Thanks.
>
>
>
> Best regards,
>
> Hongbin
>
>
>
> *From:* Corey O'Brien [mailto:coreypobr...@gmail.com]
> *Sent:* February-05-16 12:04 AM
>
>
> *To:* OpenStack Development
an disallow those users
> who can not login into nodes to access some limited APIs.
>
> Regards,
> Wanghua
>
> On Fri, Feb 5, 2016 at 12:24 PM, Corey O'Brien
> wrote:
>
>> There currently isn't a way to distinguish between user who creates the
>> bay a
So as we're all aware, the gate is a mess right now. I wanted to sum up
some of the issues so we can figure out solutions.
1. The functional-api job sometimes fails because bays timeout building
after 1 hour. The logs look something like this:
magnum.tests.functional.api.v1.test_bay.BayTest.test_c
There currently isn't a way to distinguish between user who creates the bay
and the nodes in the bay because the user is root on those nodes. Any
credential that the node uses to communicate with Magnum is going to be
accessible to the user.
Since we already have the trust, that seems like the bes
version of etcd ? Is it
> documented somewhere for the team to have a look ?
>
> -Vilobh
>
> On Wed, Feb 3, 2016 at 8:11 AM, Corey O'Brien
> wrote:
>
>> Hey team,
>>
>> I've been looking into https://bugs.launchpad.net/magnum/+bug/1541105 which
>&
otify-heat
(see bug for patch)?
I'm personally in favor of updating the image, but there is presumably some
small risk with using a newer version of etcd.
Thanks,
Corey O'Brien
__
OpenStack Development Mailing List
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
I think this is an excellent idea. I noticed this endpoint last week for
the first time and was really confused about it. Since Heat is managing all
the nodes, I agree Magnum shouldn't be tracking them.
Corey
On Mon, Feb 1, 2016 at 1:48 AM 王华 wrote:
> Hi all,
>
> I want to remove node object fr
12 matches
Mail list logo
