i like your idea, as an operator, it gives me new features while keep my
core running fine.
only one think i didn't like it
why all url,api, etc has to include the word 'preview'?
i imagine that i would be consuming the new feature using heat, puppet,
local scripts, custom horizon, whatever. Why
On 08/22/2014 02:13 PM, Michael Chapman wrote:
We try to target puppet module master at upstream OpenStack master, but
without CI/CD we fall behind. The missing piece is building packages and
creating a local repo before doing the puppet run, which I'm working on
slowly as I want a single
On 02/24/2014 01:10 AM, Liuji (Jeremy) wrote:
Hi, Boris and all other guys:
I have found a BP about USB device passthrough in
I have also read the latest nova code and make sure it doesn't support USB
passthrough by now.
On 11/08/2013 06:09 PM, Chris Jones wrote:
I'm going to be staying in the Tsim Sha Tsui area of Hong Kong until
late Monday - just wondering if any other folks are staying on and
want to do interesting things?
On 11/27/2013 01:50 PM, Maru Newby wrote:
Just a heads up, the console output for neutron gate jobs is about to get a
lot noisier. Any log output that contains 'ERROR' is going to be dumped into
the console output so that we can identify and eliminate unnecessary error
logging. Once we've
On 08/06/2014 06:10 PM, Michael Still wrote:
We also talked about tweaking the ratio of tech debt runways vs
'feature runways. So, perhaps every second release is focussed on
burning down tech debt and stability, whilst the others are focussed
on adding features. I would suggest if we do
On 04/07/2014 10:49 AM, Roman Podoliaka wrote:
Perhaps, we should file a design session for Neutron-specific questions?
1. Define a neutron node (tripleo-image-elements/disk-image-builder) and
make sure it deploys and scales ok (tripleo-heat-templates/tuskar). This
On 05/02/2014 11:09 AM, Mark McClain wrote:
To throw something out, what if moved to using config-dir for optional
configs since it would still support plugin scoped configuration files.
Neutron Servers/Network Nodes
neutron.conf (Common Options)
On 05/04/2014 01:22 PM, Mark McClain wrote:
On May 4, 2014, at 8:08, Sean Dague s...@dague.net wrote:
Question (because I honestly don't know), when would you want more than
1 l3 agent running on the same box?
For the legacy case where there are multiple external networks connected to a
On 01/28/2015 01:13 AM, Fischer, Matt wrote:
Our keystone database is clustered across regions, so we have this job
running on node1 in each site on alternating hours. I don’t think you’d
want a bunch of cron jobs firing off all at once to cleanup tokens on
multiple clustered nodes. That’s
On 2015-03-21 02:57, Assaf Muller wrote:
The use_namespaces option in the L3 and DHCP Neutron agents controls if you
can create multiple routers and DHCP networks managed by a single L3/DHCP agent,
or if the agent manages only a single resource.
Are the setups out there *not*
On 2015-06-06 03:26, Michael Krotscheck wrote:
Right now, there are several JS linters in use in OpenStack: JSHint,
JSCS, and Eslint. I really would like to only use one of them, so that I
can figure out how to sanely share the configuration between projects.
Can all those who have a strong
I see that
is empty and no email thread about the topic, will be any more or less
formal keysigning party in Tokyo?
is it too late?
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
Mail list logo