Re: [Openstack-operators] Trove Shadow Tenant

Sergio, Sounds like I may have been replying only to you, not the list. A couple of things to recap from the emails I’d sent you. 1. From the description of what you are doing, I’m not sure that single tenant remote (or shadow tenant) would be my first choice. 2. If you go the route of

Re: [Openstack-operators] Trove Shadow Tenant

I'm going to use tmpfs. I found many errors when using this feature ( https://bugs.launchpad.net/trove/+bug/1662300). Thank you all for your time. El dom., 5 feb. 2017 a las 23:50, Sam Morrison () escribió: > Hi Sergio, > > I’m very interested in this feature too, it might

Re: [Openstack-operators] [openstack-dev] Large Contributing OpenStack Operators working group?

Thanks for the response, Andrew! Some replies inline. On 02/03/2017 06:47 PM, UKASICK, ANDREW wrote: Hi Jay It seems like I blinked and 10 more emails flew by since last night. ;-) No worries, happens all the time :) One of the difficulties for people like myself, and I think most of the

Re: [Openstack-operators] OSA Newton Release Deployment in test environment

LXC will setup eth0 in the container which will NAT through the host to access the internet. Clearly there’s something wrong with that traffic path, so step through it like you would with any environment by validating that it is able to reach its gateway (host), then next hop, etc. From: Amit

Re: [Openstack-operators] [LCOO] Intro to Large Contributing OpenStack Operators working group

On 2017-02-03 21:50:25 + (+), MCCABE, JAMEY A wrote: [...] > The LCOO is a group of Multi-cloud Operators who are also > development contributors (read we have staff who are project > members and desire to jointly increase our participation in the > project teams). [...] It's unclear to

Re: [Openstack-operators] [openstack-dev] Large Contributing OpenStack Operators working group?

Jay, I don’t see a reference to the wiki page in your email and don’t immediately see the LCOO working group wiki. From what you describe this working group is not working within the framework of the 4 opens which is one of OpenStack’s fundamental philosophies. Thanks for bringing up your

Re: [Openstack-operators] [openstack-ansible] configuration to use nfs for glance and cinder

Hi Andy, Yes it probably does not matter if the variables are visible in other containers (you get a working system up and running anyway) but it is not the expected behavior when using limit_container_types. I did manage to get the variables limited to cinder_volume containers when I typed

[Openstack-operators] about VISA to Italy for Ops Midcycle in Milano

Hello Ops, the ops midcycle is in a about 1 month: https://etherpad.openstack.org/p/MIL-ops-meetup If you need a invitation letter for VISA to Italy please send an email to egiannu...@enter.eu and Cc: ziopr...@gmail.com . We will help you will the Italian forms to fill. ENTER that is hosting

Re: [Openstack-operators] OSA Newton Release Deployment in test environment

Error is because LXC repo container on infra node is not having connectivity to internet and is unable to download these packages. Thing is that why containers are not having connectivity to internet whereas infra node is having connectivity to internet. Any idea if this is a general behavior

Re: [Openstack-operators] OSA Newton Release Deployment in test environment

On Sat, Feb 04, 2017 at 11:52:10PM +0530, Amit Kumar wrote: > Hi All, > > used.\nWARNING: The following packages cannot be authenticated!\n dpkg/apt are telling you what the problem is, go to the server and fix apt > python-pkg-resources python-setuptools\n", "stdout_lines": ["Reading >