I would like to update this patch on a standard deployment of Newton. After
applying patch (copying over diffs) are there any steps needed for db sync?
There are a number of changes in ovn_db_sync.py
https://github.com/openstack/networking-ovn/commit/b8af082e326d1294ec3110a1d4ac266da84868b8
__
Hi Jay,
2016-11-13 3:12 GMT+09:00 Jay Pipes :
> On 11/12/2016 09:31 AM, Akira Yoshiyama wrote:
>>
>> Hi Stackers,
>>
>> In TripleO, Ironic provides physical servers for an OpenStack
>> deployment but we have to configure physical storages manually, or
>> with any tool, if required. It's better tha
Thanks,
I have done exactly as you recommended.
Regards
-steve
On 11/12/16, 10:49 AM, "Andreas Jaeger" wrote:
>On 11/12/2016 11:15 AM, Steven Dake (stdake) wrote:
>> The proposal I think you made is what I was thinking we would do, so just to
>> clarify:
>> Kolla keeps all branches/tags
Excerpts from Jeremy Stanley's message of 2016-11-05 14:08:29 +:
> On 2016-11-04 16:38:45 -0700 (-0700), Clint Byrum wrote:
> [...]
> > Modules are not plugins.
> [...]
> > This only refers to dynamic inventory, which is hardly even a plugin
> > interface.
> >
> > Strategy plugins run in ansib
At the Ocata summit we held a design summit session covering several
security-related specs from Dane Fichter and Peter Hamilton. The full
etherpad is here:
https://etherpad.openstack.org/p/ocata-nova-summit-security
Dane was present and the majority of the discussion was on the cert
validati
On 11/12/2016 09:31 AM, Akira Yoshiyama wrote:
Hi Stackers,
In TripleO, Ironic provides physical servers for an OpenStack
deployment but we have to configure physical storages manually, or
with any tool, if required. It's better that an OpenStack service
manages physical storages as same as Iron
On 11/12/2016 11:15 AM, Steven Dake (stdake) wrote:
The proposal I think you made is what I was thinking we would do, so just to
clarify:
Kolla keeps all branches/tags
When kolla-ansible is created with an upstream tag in PC, the project-config
will include no post jobs so no artifacts will b
On 11/12/2016 8:19 AM, Amrith Kumar wrote:
I'm adding [trove] to the subject as we're interested in where this ends up.
Matt, it may make sense to include other projects that use service VM's if they
are using file injection/configDrive/...
-amrith
Amrith, is that list of projects defined a
Hi Stackers,
In TripleO, Ironic provides physical servers for an OpenStack
deployment but we have to configure physical storages manually, or
with any tool, if required. It's better that an OpenStack service
manages physical storages as same as Ironic for servers.
IMO, there are 2 plans to manage
I'm adding [trove] to the subject as we're interested in where this ends up.
Matt, it may make sense to include other projects that use service VM's if they
are using file injection/configDrive/...
-amrith
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
Sent
The proposal I think you made is what I was thinking we would do, so just to
clarify:
Kolla keeps all branches/tags
When kolla-ansible is created with an upstream tag in PC, the project-config
will include no post jobs so no artifacts will be created
Kolla-ansible will have all branches deleted
Hi all
Currently, neutron model supports one router with one external network,
which is used to connect router to outside world. FIP can be allocated from
external network which is gateway of a router. One private fixed ip of one
port(usually it is a vm port ) can only associate one floating
12 matches
Mail list logo
