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 tmpfs,
You would know all this at install time as that's when this would be
determined. If that information is not available to you currently, you can
look at some other service's config files I suppose. You'll need enough
rabbit creds to create a Congress rabbit user unless you are just going to
re-use a
Hi everyone - I'm relatively new to OpenStac and am working on a bash
script to install OpenStack Congress. I'm having trouble finding CLI or
API commands to determine the Rabbit userID, password, host, and port
from a running OpenStack installation so I can configure the Rabbit
transport_url in t
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 be worth asking in th
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 LC
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
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 me
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 que
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
t
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 the
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 that
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
> package
12 matches
Mail list logo
