OpenStack Technical Committee Update: Project Reform Progress
Over the last few months, the Technical Committee has been discussing
plans to dissolve the binary concept of the integrated release and adapt
our projects structure to the future needs of collaborative development
in the OpenStack commu
Sorry, that wasn't exactly clear and my memory was a bit foggy, Jay.
max_connections possibly paired with open_files_limit
https://dev.mysql.com/doc/refman/5.6/en/too-many-connections.html
On 02/20/15 10:20, Jay Pipes wrote:
On 02/20/2015 10:39 AM, Sean Lynn wrote:
We finished upgrading to
In our case we are using OpenContrail instead of the default OVS plugin in
Neutron.
It has a feature call VDNS which could resolve names inside your cloud and
for external FQDN resolution, it can be pointed as a delegated DNS in your
primary one.
BTW. I only recommend solutions that are OpenSource
Polombo Daniel wrote:
> I'm wondering how people are usually providing the instances' public
> names (as in the FQDN associated to the floating IP) to the user?
>
> The dashboard provides direct access to the floating IP, obviously,
> but I'm sure there's a better way than asking the user to perfor
On 02/20/2015 10:39 AM, Sean Lynn wrote:
We finished upgrading to Juno about the time you guys did. Just checked
logs across all environments since the time of the Juno upgrade and I'm
*not* seeing the same errors.
For comparison here's what we have (mostly out-of-the-box):
api_workers and
I can report that we do use this option (‘global' setting.) We have to
enforce name uniqueness for instances’ integration with some external
systems (namely AD and Spacewalk) which require unique naming.
However, we also do some external name validation which I think
effectively enforces uniqu
We have memcache enabled on the metadata servers. Part of our load is
because we have a cron job that pulls the metadata and does some stuff on
the server every ~10 minutes. We staggered the start times so that the
requests are spread out over a period of time and in general concurrent
requests a
I have to second Robert. We too are using memcached. Hadn't thought
about that since it wasn't really Juno related for us, but it certainly
solved alot of problems.
Sean Lynn
Time Warner Cable, Inc.
___
OpenStack-operators mailing list
OpenStack-op
We finished upgrading to Juno about the time you guys did. Just checked
logs across all environments since the time of the Juno upgrade and I'm
*not* seeing the same errors.
For comparison here's what we have (mostly out-of-the-box):
api_workers and rpc_workers = 32
metadata_workers = 3
Hi folks,
I'm wondering how people are usually providing the instances' public names
(as in the FQDN associated to the floating IP) to the user?
The dashboard provides direct access to the floating IP, obviously, but I'm
sure there's a better way than asking the user to perform a reverse D
that's a good advice, thanks; I'll give it a try.
A.
On 02/20/2015 05:23 AM, Chris Buccella wrote:
Heat works by calling other OpenStack services. So if you want, you
could try running Heat separately in a VM (with a modern distro). That
should work as long as it has network access to the
11 matches
Mail list logo
