: [openstack-dev] [magnum] Discuss the
blueprint"support-private-registry"
Hi.
On Wed, Mar 30, 2016 at 4:20 PM, Kai Qiang Wu
mailto:wk...@cn.ibm.com>> wrote:
I agree to that support-private-registry should be secure. As insecure seems
not much useful for production use.
Also
ao
30, 2016 at 3:59 AM, Eli Qiao wrote:
From: Ricardo Rocha
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 30/03/2016 09:09 pm
Subject: Re: [openstack-dev] [magnum] Discuss the blueprint
"sup
o wrote:
>
> From: Ricardo Rocha
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: 30/03/2016 09:09 pm
> Subject: Re: [openstack-dev] [magnum] Discuss the blueprint
> "support-private-registry"
&g
heart. You are miracle!
From: Ricardo Rocha
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 30/03/2016 09:09 pm
Subject: Re: [openstack-dev] [magnum] Discuss the
blueprint "support-private-registry"
Hi.
On
Hi.
On Wed, Mar 30, 2016 at 3:59 AM, Eli Qiao wrote:
>
> Hi Hongbin
>
> Thanks for starting this thread,
>
>
>
> I initial propose this bp because I am in China which is behind China great
> wall and can not have access of gcr.io directly, after checking our
> cloud-init script, I see that
>
> lo
Hi Hongbin
Thanks for starting this thread,
I initial propose this bp because I am in China which is behind China
great wall and can not have access of gcr.io directly, after checking
our cloud-init script, I see that
lots of code are *hard coded* to using gcr.io, I personally though this
Hi team,
This is the item we didn't have time to discuss in our team meeting, so I
started the discussion in here.
Here is the blueprint:
https://blueprints.launchpad.net/magnum/+spec/support-private-registry . Per my
understanding, the goal of the BP is to allow users to specify the url of th