[openstack-dev] [heat] Design Summit Summary

Hi All, We had number of very productive sessions at the summit last week. I thought it would be good to summarize them in ML thread, for us to be able to prioritize and work on them. As Ocata cycle is shorter than usual, we may not be able to finish lot of them. More detail on the discussions

Re: [openstack-dev] [Ceilometer]: Instance creation and deletion metrics in ceilometer !

Been vaguely following this thread and I have a question. Just to confirm, as I haven't touched ceilometer code in ages, the instance metric still exists? Or at least something like it? We're currently using ceilometer as the data collection for our billing, and the instance metric is our

Re: [openstack-dev] [neutron][oslo] proposal to resolve a rootwrap problem for XenServer

Ihar and Tony, Thanks for the input. In order to run command in dom0, it uses XenAPI to create a session which can be used to remotely call a plugin - netwrap which is located in dom0. The netwrap plugin is executed as root. It will validate the command basing on the allowed command list and

Re: [openstack-dev] [devstack][mitaka] Unable stack.sh on ubuntu 14.04.5LTS (TypeError: 'Documentation' object is not iterable)

Hi, Your logs says that it failed during installation of "rcssmin" package. Did you tried installing it manually, or removing it completely and re-installing? It may be because of version conflict across the dependencies for this package. Regards, Ganpat On Tue, Nov 1, 2016 at 8:10 PM,

Re: [openstack-dev] [Ceilometer]: Instance creation and deletion metrics in ceilometer !

That's correct. We can have meters only for those things which we can measure like cpu, memory etc. If we want to keep a count of instance creation and deletion, you will need to monitor the events and look for specific event types like compute.instance.create.end or compute.instance.delete.end.

[openstack-dev] [Horizon] Summit recap

Hi folks, We had several very productive Horizon sessions at the summit last week. Thanks to everyone who was able to contribute, especially the folks from the Keystone project for the combined session. A summary of the discussions and outcomes: == Project Organisation == We will be

[openstack-dev] [FaaS] Function as a service in OpenStack

Hi, all, Recently when I was talking with some customers of our OpenStack based public cloud, some of them are expecting to see a service similar to AWS Lambda in OpenStack ecosystem (so such service could be invoked by Heat, Mistral, Swift, etc.). Coincidently, I happened to see an introduction

Re: [openstack-dev] [neutron] proposal to resolve a rootwrap problem for XenServer

On Tue, Nov 01, 2016 at 12:45:43PM +0100, Ihar Hrachyshka wrote: > I suggested in the bug and the PoC review that neutron is not the right > project to solve the issue. Seems like oslo.rootwrap is a better place to > maintain privilege management code for OpenStack. Ideally, a solution would > be

Re: [openstack-dev] [keystone] new keystone core (breton)

Congrats Boris, Great to have new people on board. Well earned. On 1 November 2016 at 15:53, Brad Topol wrote: > Congratulations Boris!!! Very well deserved!!! > > --Brad > > > Brad Topol, Ph.D. > IBM Distinguished Engineer > OpenStack > (919) 543-0646 > Internet:

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

On Tue, 2016-11-01 at 13:17 +0100, Ihar Hrachyshka wrote: > Armando M. wrote: > > > > Slight variation, call it option 6: > > > > 1) Identify the most impacted (coupled) project affected by these > > changes. > > 2) Fix it in order to provide folks with a recipe for how to >

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

On Tue, 2016-11-01 at 13:13 +0100, Ihar Hrachyshka wrote: > Brandon Logan wrote: > > > Hello Neutrinos, > > I've come across an issue that I'd like to get input/opinions > > on.  I've > > been reviewing some of the centralize config options reviews and > > have > >

[openstack-dev] [Cinder] Ocata Design Summit Recap

The Cinder team had a very productive week at the Design Summit, IMO. There were a lot of great discussions throughout the week, both in Cinder sessions and in the hallways. A huge thank you to all who were able to participate, and a reminder for those that couldn't attend that the PTG is coming

Re: [openstack-dev] [tripleo] Ocata specs

On 1 Nov 2016, at 14:46, Zane Bitter wrote: > On 01/11/16 15:13, James Slagle wrote: >> On Tue, Nov 1, 2016 at 7:21 PM, Emilien Macchi wrote: >>> Hi, >>> >>> TripleO (like some other projects in OpenStack) have not always done >>> good job in merging specs on time during a

Re: [openstack-dev] [tripleo] Ocata specs

On 01/11/16 15:13, James Slagle wrote: On Tue, Nov 1, 2016 at 7:21 PM, Emilien Macchi wrote: Hi, TripleO (like some other projects in OpenStack) have not always done good job in merging specs on time during a cycle. I would like to make progress on this topic and for that,

Re: [openstack-dev] [Ceilometer]: Instance creation and deletion metrics in ceilometer !

On 01/11/16 05:30 AM, Raghunath D wrote: > My requirement is to get sample/counter with "instance" name ,with > event_type *compute.instance.** we don't build instance meter anymore because it's not a meter as it's not measuring anything. -- gord

Re: [openstack-dev] [ptl][release] ocata release management communication

On 11/1/2016 2:45 PM, Doug Hellmann wrote: 4. Reply to this message, off-list, so I know that you have received it. A simple “ack” is enough. Got it. :) -- Thanks, Matt Riedemann __ OpenStack Development Mailing

[openstack-dev] [ptl][release] ocata release management communication

PTLs, As we did for the Mitaka and Newton cycles, I want to start this cycle by making sure the expectations for communications with the release team are clear to everyone so there is no confusion or miscommunication about any of the process or deadlines. This email is being sent to the

[openstack-dev] [ironic] weakly subteam report

Hi, Here is this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff between 17 Oct 2016 and 31 Oct 2016) - Ironic: 233 bugs (+9) + 211 wishlist items (+2). 33 new (+10), 175 in

Re: [openstack-dev] [tripleo] Ocata specs

On Tue, Nov 1, 2016 at 7:21 PM, Emilien Macchi wrote: > Hi, > > TripleO (like some other projects in OpenStack) have not always done > good job in merging specs on time during a cycle. > I would like to make progress on this topic and for that, I propose we > set a deadline to

[openstack-dev] [new][horizon] XStatic-D3 3.5.17.0 release

We are mirthful to announce the release of: XStatic-D3 3.5.17.0: D3 3.5.17 (XStatic packaging standard) This is the first release of XStatic-D3. Download the package from: https://pypi.python.org/pypi/XStatic-D3 For more details, please see below. Changes in XStatic-D3

[openstack-dev] [new][horizon] XStatic-Angular 1.5.8.0 release

We are satisfied to announce the release of: XStatic-Angular 1.5.8.0: Angular 1.5.8 (XStatic packaging standard) Download the package from: https://pypi.python.org/pypi/XStatic-Angular For more details, please see below. Changes in XStatic-Angular 1.4.10.1..1.5.8.0

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On 2016-11-01 14:10:44 -0400 (-0400), Ben Swartzlander wrote: > On 11/01/2016 12:03 PM, Jeremy Stanley wrote: [...] > > into it the kernel's process space. This is the closest analogue we > > have to our drivers importing proprietary Python modules. > > I'm not talking about python code here. I'm

[openstack-dev] [tripleo] Ocata specs

Hi, TripleO (like some other projects in OpenStack) have not always done good job in merging specs on time during a cycle. I would like to make progress on this topic and for that, I propose we set a deadline to get a spec approved for Ocata release. This deadline would be Ocata-1 which is week

Re: [openstack-dev] [neutron] Cloud Provider Security Groups

On 31 October 2016 at 22:28, David G. Bingham wrote: > Yo Neutron devs :-) > > I was wondering if something like the following subject has come up: > "Cloud-provider Security Groups”. > > *Goal of this email*: Gauge the community’s need and see if this has come > up in

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On 11/01/2016 12:03 PM, Jeremy Stanley wrote: On 2016-11-01 00:26:11 -0400 (-0400), Ben Swartzlander wrote: [...] As usual I'd like to point to the Linux project as a good example for how to handle such things. Linux is older than us and has been dealing with drivers and proprietary code for a

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On 2016-11-01 12:29:27 -0500 (-0500), Sean McGinnis wrote: [...] > Is importing proprietary libs really a legal issue? If it happens at > runtime based on how the user configured the system, and they have > whatever licensing rights _they_ need to use that library/CLI, I > don't see an issue with

[openstack-dev] [nova] The road to removing nova-network

Starts with cleaning up our CI situation. I spent some time today sorting out which jobs are running against the nova repo which use nova-network, that's documented here: https://etherpad.openstack.org/p/removing-nova-network I've got some actions defined in there to start moving forward. If

[openstack-dev] [new][cinder] os-brick 1.7.0 release (ocata)

We are ecstatic to announce the release of: os-brick 1.7.0: OpenStack Cinder brick library for managing local volume attaches This release is part of the ocata release series. The source is available from: http://git.openstack.org/cgit/openstack/os-brick Download the package from:

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On Tue, Nov 01, 2016 at 03:47:11PM +, Jeremy Stanley wrote: > On 2016-10-31 13:23:48 -0500 (-0500), Sean McGinnis wrote: > > Last Tuesday we had a cross-project session around the use of > > proprietary code/libs/binaries in OpenStack drivers. The challenge > > we are running into is where to

[openstack-dev] [new][nova] os_vif 1.3.0 release (ocata)

We are chuffed to announce the release of: os_vif 1.3.0: A library for plugging and unplugging virtual interfaces in OpenStack. This release is part of the ocata release series. Download the package from: https://pypi.python.org/pypi/os_vif For more details, please see below. Changes in

[openstack-dev] [new][horizon] django_openstack_auth 3.0.0 release (ocata)

We are grateful to announce the release of: django_openstack_auth 3.0.0: Django authentication backend for use with OpenStack Identity This release is part of the ocata release series. The source is available from: http://git.openstack.org/cgit/openstack/django_openstack_auth/ Download

[openstack-dev] [new][keystone] keystoneauth1 2.15.0 release (ocata)

We are enthusiastic to announce the release of: keystoneauth1 2.15.0: Authentication Library for OpenStack Identity This release is part of the ocata release series. The source is available from: http://git.openstack.org/cgit/openstack/keystoneauth Download the package from:

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On Tue, Nov 01, 2016 at 12:26:11AM -0400, Ben Swartzlander wrote: > On 10/31/2016 02:23 PM, Sean McGinnis wrote: > >Last Tuesday we had a cross-project session around the use of proprietary > >code/libs/binaries in OpenStack drivers. The challenge we are running into > >is where to draw the line

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On 2016-11-01 00:26:11 -0400 (-0400), Ben Swartzlander wrote: [...] > As usual I'd like to point to the Linux project as a good example > for how to handle such things. Linux is older than us and has been > dealing with drivers and proprietary code for a very long time. > > Linux does a few

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

Nate Johnston wrote: On Tue, Nov 01, 2016 at 01:17:25PM +0100, Ihar Hrachyshka wrote: Armando M. wrote: Slight variation, call it option 6: 1) Identify the most impacted (coupled) project affected by these changes. 2) Fix it in order to

Re: [openstack-dev] [All] Cross project prorietary driver code recap

On 2016-10-31 13:23:48 -0500 (-0500), Sean McGinnis wrote: > Last Tuesday we had a cross-project session around the use of > proprietary code/libs/binaries in OpenStack drivers. The challenge > we are running into is where to draw the line with these drivers. > What is the appropriate policy to

Re: [openstack-dev] [nova] Moving storage placement out of the driver

On 11/01/2016 10:41 AM, Matthew Booth wrote: For context, this is a speculative: should we, shouldn't we? The VMware driver currently allows the user to specify what storage their instance will use, I believe using a flavor extra-spec. We've also got significant interest in adding the same to

[openstack-dev] [kolla] Tomorrows (2/11/16) meeting canceled

Hello, I'll cancel tomorrows meeting as we have seen each other just last week:) Also many of us is using this week to get well deserved rnr. See you all on next meeting! (9/11) Cheers, Michal __ OpenStack Development

Re: [openstack-dev] [puppet] weekly meeting #95

tomorrow at 3pm UTC on > #openstack-meeting-4. > > Here's the current agenda: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20161101 > > Thanks, > -Alex __ OpenStack Development M

[openstack-dev] kolla-kubernetes Ocata goals [kolla][kubernetes]

Hey folks, I wanted to highlight some of the discussion that was held at summit and outline goals for kolla-kubernetes in the Ocata cycle. The number one goal for the kolla-kubernetes project in the Ocata cycle is to have a 1.0 release. As discussed at summit, the community is going to pursue

Re: [openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes

Lee That change is in my test version or was till I reverted it with https://review.openstack.org/#/c/391418, If you live migrate with the change you mentioned the instance goes to error when you try to hard reboot Paul Carlton Software Engineer Cloud Services Hewlett Packard

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

On Tue, Nov 01, 2016 at 01:17:25PM +0100, Ihar Hrachyshka wrote: > Armando M. wrote: > > > >Slight variation, call it option 6: > > > >1) Identify the most impacted (coupled) project affected by these changes. > >2) Fix it in order to provide folks with a recipe for how to

Re: [openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes

On 01-11-16 12:02:55, Carlton, Paul (Cloud Services) wrote: > Daniel > > Yes, thanks, but the thing is this does not occur with regular volumes! > The process seems to be you need to connect the volume then the encryptor. > In pre migration at the destination I connect the volume and then setup

[openstack-dev] [tripleo] meeting notes - November 1st

TripleO team did their weekly meeting, and you can find the notes here: http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-11-01-14.00.html Some actions were taken: EmilienM / shardy to release newton-2 and ocata-1 during Nov 14th week EmilienM or slagle to submit patch to nodepool

Re: [openstack-dev] [keystone] new keystone core (breton)

Congratulations Boris!!! Very well deserved!!! --Brad Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Steve Martinelli To: "OpenStack Development Mailing List

Re: [openstack-dev] [devstack][mitaka] Unable stack.sh on ubuntu 14.04.5LTS (TypeError: 'Documentation' object is not iterable)

Hi One quick update on this issue: For some reason I see this issue only with devstack mitaka on vagrant VM spawned using virtualbox provider(Ubuntu/trusty64 box). It used to work before though... On the same vagrant VM, I installed devstack Liberty which is working without any issues. Also

[openstack-dev] [nova] Moving storage placement out of the driver

For context, this is a speculative: should we, shouldn't we? The VMware driver currently allows the user to specify what storage their instance will use, I believe using a flavor extra-spec. We've also got significant interest in adding the same to the libvirt driver, but we've got some

[openstack-dev] [nova][neutron] nova/neutron cross-project ocata summit session recap

The Nova and Neutron teams had two cross-project sessions in Barcelona at the Ocata summit, the full etherpad is here: https://etherpad.openstack.org/p/ocata-nova-neutron-session The entire first session was spent discussing a proposal to change how Nova and Neutron handle port binding

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

[openstack-dev] [nova] About doing the migration claim with Placement API

Currently we only update the resource usage with Placement API in the instance claim and the available resource update periodic task. But there is no claim for migration with placement API yet. This works is tracked by https://bugs.launchpad.net/nova/+bug/1621709. In newton, we only fix one bit

Re: [openstack-dev] [cinder] consistency groups in ceph

Hi Victor, Please see my answers inline below. In Newton, we added support for Generic Volume Groups. See doc below. CGs will be migrated to Generic Volume Groups gradually. Drivers should not implement CGs any more. Instead, it can add CG support using Generic Volume Group interfaces.

Re: [openstack-dev] [neutron] neutron-lib

Gary Kotton wrote: > Would it be possible to cut a new version of neutron-lib. This will enable us > to proceed with the integration into the various projects? https://review.openstack.org/392009 __

[openstack-dev] [neutron] neutron-lib

Hi, Would it be possible to cut a new version of neutron-lib. This will enable us to proceed with the integration into the various projects? Thanks Gary __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

Excerpts from Ihar Hrachyshka's message of 2016-11-01 13:13:41 +0100: > Brandon Logan wrote: > > > Hello Neutrinos, > > I've come across an issue that I'd like to get input/opinions on. I've > > been reviewing some of the centralize config options reviews and have >

Re: [openstack-dev] [neutron] Cloud Provider Security Groups

Hi, This is actually something that we have implemented within the VMware NSX plugins(s). We actually called it provider rules. This was done as an extension to the plugin. We have seen a large number of people ask for this functionality. It basically gives an admin the option of having ‘deny’

Re: [openstack-dev] [nova] Functional tests

Hi Paul, For me, it looks like keystone auth error, AFAIK neither cinder nor keystone are run in nova functional tests. Test "nova.tests.functional.test_servers.ServerTestV220.test_ attach_detach_vol_to_shelved_offloaded_server" calls os-volume_attachments and there is no mock for

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

Armando M. wrote: Slight variation, call it option 6: 1) Identify the most impacted (coupled) project affected by these changes. 2) Fix it in order to provide folks with a recipe for how to address the breakages. ^ the step depends on how far we want to go with the

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

Brandon Logan wrote: Hello Neutrinos, I've come across an issue that I'd like to get input/opinions on. I've been reviewing some of the centralize config options reviews and have come across a few that would cause issues with other projects that are importing

Re: [openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes

Daniel Yes, thanks, but the thing is this does not occur with regular volumes! The process seems to be you need to connect the volume then the encryptor. In pre migration at the destination I connect the volume and then setup the encryptor and that works fine, but in post migration at

Re: [openstack-dev] [neutron] proposal to resolve a rootwrap problem for XenServer

Jianghua Wang wrote: Hi Neutron guys, I’m trying to explain a problem with the XenServer rootwrap and give a proposal to resolve it. I need some input on how to proceed with this proposal: e.g. if requires a spec? Any concerns need further discussion or

Re: [openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes

On Tue, Nov 01, 2016 at 11:22:25AM +, Carlton, Paul (Cloud Services) wrote: > I'm working on a bug https://bugs.launchpad.net/nova/+bug/1633033 with the > live migration of > > instances with encrypted volumes. I've submitted a work in progress version > of a patch > >

[openstack-dev] [ironic] ironic-specs core team update

Hi friends, At the summit we discussed making the ironic-specs core team the same as the ironic core team. This proposal had unanimous support from the existing specs core team, so I've made the changes in gerrit now. https://review.openstack.org/#/admin/groups/352,members Happy +2'ing! // jim

[openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes

I'm working on a bug https://bugs.launchpad.net/nova/+bug/1633033 with the live migration of instances with encrypted volumes. I've submitted a work in progress version of a patch https://review.openstack.org/#/c/389608 but I can't overcome an issue with an iscsi command failure that only

Re: [openstack-dev] [neutron] [neutron-lbaas][octavia] Error in installing octavia via devstack on ubuntu stable/mitaka

Michael Johnson wrote: Hi Wanjing, I responded to you in IRC but you may have logged off by the time I was able to respond. You are correct that this is an issue. We just this week noticed it. It was an oversight that is causing the amphora agent to clone the master

Re: [openstack-dev] [magnum]Is internet-access necessary for Magnum + CoreOS?

Hi, Rikimaru. Currently, k8s-CoreOS driver dosen’t have way to disable internet access. But k8s-fedora driver has. See, below blueprint. * https://blueprints.launchpad.net/magnum/+spec/support-insecure-registry Maybe you can bring this feature to k8s-coreos driver. Thanks -yuanying

[openstack-dev] [nova] Functional tests

Hi I've inherited a series of changes from a co-worker who has moved on and have rebased them but now I'm hitting some issues with functional tests which I can't figure out how to resolve. The changes are https://review.openstack.org/#/c/268053 and https://review.openstack.org/#/c/326899.

Re: [openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

Hi, shihanzhang and Neil, Thanks for your comments. In your comments. I think that Neutron router or physical network should provide routing these two subnets, doesn't it? Does my thought was right? I tried to connect these two subnets with a Neutron router but I met a strange problem. I did

Re: [openstack-dev] [Ceilometer]: Instance creation and deletion metrics in ceilometer !

Hi, what meters are you looking for specifically? as Ganpat mentioned, we only derive a few meters from Nova notifications[1]. i don't understand your comment about being able to see events on kafka. by 'events' do you mean Ceilometer Events[2]? [1]

Re: [openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

agree with Neil. thanks shihanzhang 在 2016-11-01 17:13:54，"Neil Jerram" 写道： Hi Zhi Chang, I believe the answer is that the physical network (aka fabric) should provide routing between those two subnets. This routing between segments is implicit in the idea of a

Re: [openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

Hi Zhi Chang, You also need to connect these two subnets to a router. Thanks, shihanzhang 在 2016-11-01 15:47:57，"zhi" 写道： Hi, shihanzhang. I still have a question about routed network. I have two subnets. One is 10.1.0.0/24 and the other is 10.1.1.0/24. I create two

Re: [openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

Hi Zhi Chang,I believe the answer is that the physical network (aka fabric) should provide routing between those two subnets. This routing between segments is implicit in the idea of a multi-segment network, and

Re: [openstack-dev] [searchlight] Propose Zhenyu Zheng for Searchlight core

+1 for me On Thu, Oct 20, 2016 at 5:13 PM, Brian Rosmaita < brian.rosma...@rackspace.com> wrote: > +1 from me, I'll be happy to see Kevin on the core list. > > On 10/19/16, 10:10 AM, "McLellan, Steven" wrote: > > Hi, > > I'd like to propose Zhenyu Zheng (Kevin_Zheng on

Re: [openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

Hi, shihanzhang. I still have a question about routed network. I have two subnets. One is 10.1.0.0/24 and the other is 10.1.1.0/24. I create two instances in each host. Such as 10.1.0.10 and 10.1.1.10. My question is, how does 10.1.0.10 connect to 10.1.1.10 ? There is no any gateway( 10.1.0.1

[openstack-dev] Unit Conversion in Administrator Guide

Hi all, I have a docs bug for the admin-guide that concerns the conversion from Mbps to kilobytes per second (https://bugs.launchpad.net/openstack-manuals/+bug/1617450: "1 Mbit/s would be 1,000,000 bits/s. 1 Gbit/s would be 1000 times 1 Mbit/s... The example below sets network traffic

Re: [openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

Hi, shihanzhang. Thanks for your advice. Now I can created ports successfully by your advice. Thanks Zhi Chang 2016-11-01 12:50 GMT+08:00 shihanzhang : > Hi Zhi Chang, > Maybe you should add a config option in [ovs] section: bridge_mappings = > public:br-ex,

[openstack-dev] [magnum]Is internet-access necessary for Magnum + CoreOS?

Hi all, Can I use magnum + CoreOS on the environment which is not able to access the internet? I'm trying it, but CoreOS often accesses to "quay.io". Please share the knowledge if you know about it. I'm using CoreOS, kubernetes, Magnum 2.0.1. Regards, -- Rikimaru Honjo