Re: [openstack-dev] [openstack][Magnum] ways to get CA certificate in make-cert.sh from Magnum

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

[openstack-dev] [Magnum] gate issues

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:

Re: [openstack-dev] [Magnum] gate issues

be greatly appreciated, 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:

Re: [openstack-dev] [openstack][Magnum] ways to get CA certificate in make-cert.sh from Magnum

. We can not avoid that, but by this way we can 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 <coreypobr...@gmail.com> > wrote: > >> There currently isn't a way to disting

Re: [openstack-dev] [Magnum]Remove node object from Magnum

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

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 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

[openstack-dev] [Magnum] Bug 1541105 options

-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 (not for usage

Re: [openstack-dev] [Magnum] Bug 1541105 options

? Is it > documented somewhere for the team to have a look ? > > -Vilobh > > On Wed, Feb 3, 2016 at 8:11 AM, Corey O'Brien <coreypobr...@gmail.com> > wrote: > >> Hey team, >> >> I've been looking into https://bugs.launchpad.net/magnum/+bug/1541105 which >

Re: [openstack-dev] [Magnum] API service won't work if conductor down?

>>> independently. Thoughts? >>> >>> >>> >>> [1] https://review.openstack.org/#/c/184791/ >>> >>> >>> >>> Best regards, >>> >>> Hongbin >>> >>> >>> >>> *From:* Kumar

Re: [openstack-dev] [magnum]swarm + compose = k8s?

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

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

gt; > > Note that it will take a thoughtful approach (subject to discussion) to > balance these interests. Please take a moment to review the interest above. > Do you or others disagree with these? If so, why? > > > > Adrian > > > > On Mar 4, 2016, at 9:09 AM, Ho

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

ck.org > > > Subject: [openstack-dev] [magnum] Discussion of supporting > single/multiple OS distro > > Hi team, > > > > This is a continued discussion from a review [1]. Corey O'Brien suggested > to have Magnum support a single OS distro (Atomic). I disagreed. I think