actually want to do
and care about.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
very much for getting this rolling. A very promising
start.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin
On Fri, 26 Jun 2015, Chris Dent wrote:
Please provide your input soon. We will close the voting at the end
of Wednesday, July 3rd and will be posting a proposed schedule soon
thereafter. Note that due to time constraints the mid-cycle could
happen as soon as the following Monday, July 6th
6th.
If you have any questions please either respond here or find cdent or
prad in IRC.
Thanks for your help making a fun and productive mid-cycle.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-operators
evaluate as we go.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
to make this happen
but at least we know we'll be trying to make progress in the right
direction.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-operators mailing list
OpenStack-operators
and
volunteer to lead if you like.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
On Thu, 2 Jul 2015, Chris Dent wrote:
The voting related to the ceilometer mid-cylce is now closed. Prad and I
will work to come up with a proposed schedule.
Can interested participants please make sure they are up to date on
http://doodle.com/6vfksdu38wcwqqd3 with two consecutive days where
On Fri, 26 Jun 2015, Chris Dent wrote:
Ceilometer contributors and other interested parties,
It's been pointed out that the topic titles at
https://etherpad.openstack.org/p/ceilometer-liberty-midcycle
and the agenda items and descriptions at
https://etherpad.openstack.org/p
://etherpad.openstack.org/p/ceilometer-liberty-midcycle.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
On Fri, 26 Jun 2015, Chris Dent wrote:
Ceilometer contributors and other interested parties,
To keep people in the loop:
The Ceilometer virtual mid-cycle will be held next week, the 9th and
10th of July. The schedule is being worked out.
The topics that will be covered include:
* Getting
with each session _in advance_ of the sessions.
This will help make sure we focus on the stuff that people actually
care about.
Some sessions currently have neither leader nor etherpad. We need to
fix that.
See you there.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
On Wed, 8 Jul 2015, Chris Dent wrote:
The ceilometer mid-cycle is virtual and starts tomorrow (Thursday
9th of July) at 0700 UTC. The topical agenda is here:
https://wiki.openstack.org/wiki/Meetings/Ceilometer/Liberty_Virtual_Mid-Cycle
and the daily schedule is here:
https
unnecessary cruft and load for artificial value:
it doesn't actually protect against the problem in any real way.
--
Chris Dent (╯°□°)╯︵┻━┻http://anticdent.org/
freenode: cdent tw: @anticdent___
ional configuration" do you mean "add more
things to nova.conf"? If so, then please don't do that. There is far
too much of that.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
d to the users, should always be 80 and 443 (so no need to
define a port, just a scheme) and the internal ports, if necessary,
should be up to the deployer and their own internal plans. If we
define a default port, people will use it and expose it to users.
imho, iana(deployer), ymmv, etc
--
Chris Dent
g we
intuitively knew.
[1] http://lists.openstack.org/pipermail/openstack-dev/2017-April/115061.html
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw: @anticdent___
/ host with the service on a path
prefix: https://api.mycloud.example.com/compute/,
https://api.mycould.example.com/block-storage, etc
--
Chris Dent (⊙＿⊙') https://anticdent.org/
freenode: cdent tw
to accept (please, let's) some form of
control plane downtime data migration issues can be vastly eased.
Getting agreement on how that might work is one of the goals of the
session.
Your input very appreciated.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode
.
Thanks.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http
On Wed, 9 May 2018, Chris Dent wrote:
I've started an etherpad for the forum session in Vancouver devoted
to discussing the possibility of tracking and allocation resources
in Cinder using the Placement service. This is not a done deal.
Instead the session is to discuss if it could work and how
effectively in that kind of setup. If they can't I'd
like to help make it possible.
In any case: processes 3, threads 1 for WSGIDaemonProcess for the
placement service for a deployment of any real size errs on the
side of too conservative and I hope we can make some adjustments
there.
--
Chris Dent
they are configured, but it does control the flexibility with which
apache itself will scale to accept initial connections. That's not a
problem you're yet seeing at your scale, but is an issue when the
number of compute nodes gets much bigger.
--
Chris Dent ٩◔̯◔۶ https
f instance state going to both placement and
the nova-scheduler. The number of calls from nova-compute to
placement reduces a bit as you updgrade to newer releases. It's
still more than we'd prefer.
--
Chris Dent ٩◔̯◔۶ https://
st was that with a properly tuned placement service it was
other parts of the system that suffered first.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent___
Op
the web server is essentially operating as a proxy to another
process which is being the WSGI server, nginx has a history of being
very effective.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw
26 matches
Mail list logo
