[Added tripleo]
It would be nice to have this situation verified/improved for
containerized libvirt for compute nodes deployed with TripleO as well.
On 7/12/18 11:02 PM, Clint Byrum wrote:
Greetings! We've been deploying with Kolla on CentOS 7 now for a while, and
we've recently noticed a rat
Thanks for the feedback, John and Emilien.
On 13.7.2018 01:35, Emilien Macchi wrote:
+1 for Option A as well, I feel like it's the one which would give us the
more of flexibility and also I'm not a big fan of the usage of Anchors for
this use case.
Some folks are currently working on extracting
env:
openstack queen version on centos7
latest vmware_nsx plugin rpm installed: python-networking-vmware-nsx-12.0.1
when i modify 'core_plugin' value in [default] section of
/etc/neutron/neutron.conf from ml2 to vmware_nsx.plugin.NsxDvsPlugin, then
try to start neutron-server with command 'system
On Thu, Jul 12, 2018 at 8:17 PM, Lars Kellogg-Stedman wrote:
> I've had a few operators complain about the permissive rule tripleo
> creates for ssh. The current alternatives seems to be to either disable
> tripleo firewall management completely, or move from the default-deny
> model to a set of
On Fri, Jul 13, 2018 at 1:54 AM, Bogdan Dobrelya wrote:
> [Added tripleo]
>
> It would be nice to have this situation verified/improved for containerized
> libvirt for compute nodes deployed with TripleO as well.
>
> On 7/12/18 11:02 PM, Clint Byrum wrote:
>>
>> Greetings! We've been deploying wit
On Fri, Jul 13, 2018 at 07:47:17AM -0600, Alex Schultz wrote:
> I think we should update the default rule to allow access over the
> control plane but there must be at least 1 rule that we're enforcing
> exist so the deployment and update processes will continue to
> function.
That's makes sense.
On Thu, Jul 12, 2018 at 11:07 AM Bogdan Dobrelya
wrote:
[...]
> > -
> https://blueprints.launchpad.net/tripleo/+spec/containerized-undercloud
>
> This needs FFE please. [...]
No i don't think we need FFE for containerized undercloud. Most of the code
has merged and we're switching the default
On 07/12/2018 04:29 PM, Eric Fried wrote:
Here it is for nova.
https://review.openstack.org/#/c/582392/
also don't love that immediately bumping the lower bound for tox is
going to be kind of disruptive to a lot of people.
By "kind of disruptive," do you mean:
$ tox -e blah
ERROR: Min
Hi Octavia folks!
I have created an etherpad [1] for topics at the Stein PTG in Denver.
Please indicate if you will be attending or not and any topics you
think we should cover.
Michael
[1] https://etherpad.openstack.org/p/octavia-stein-ptg
__
Hi Enoch,
There are two issues here.
1. Plugin 'vmware_nsx.plugin.NsxDvsPlugin' cannot be found.
This could be resolved by changing core_plugin to 'vmware_nsxv' as the
entry point for vmware_nsxv is defined as vmware_nsxv.
2. No module named neutron_fwaas.db.firewall
It looks like you are missing
Ben-
On 07/13/2018 10:12 AM, Ben Nemec wrote:
>
>
> On 07/12/2018 04:29 PM, Eric Fried wrote:
>> Here it is for nova.
>>
>> https://review.openstack.org/#/c/582392/
>>
also don't love that immediately bumping the lower bound for tox is
going to be kind of disruptive to a lot of people.
>
Greetings,
We have been supporting both Keepalived and Pacemaker to handle VIP
management.
Keepalived is actually the tool used by the undercloud when SSL is enabled
(for SSL termination).
While Pacemaker is used on the overcloud to handle VIPs but also services
HA.
I see some benefits at removin
# Keystone Team Update - Week of 9 July 2018
## News
### New Core Reviewer
We added a new core reviewer[1]: thanks to XiYuan for stepping up to take this
responsibility and for all your hard work on keystone!
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-July/132123.html
### Rel
The deadline for releasing non-client libraries for Rocky is coming up
next week on 19 July (https://releases.openstack.org/rocky/schedule.html).
We have a few libraries that have no releases at all this cycle,
which makes creating the stable branch problematic. Therefore, if
the PTL or release li
Sounds good to me. Even if pacemaker is heavier, less options and
consistency is better.
Greetings from Mexico :D
On Fri, 13 Jul 2018, 13:33 Emilien Macchi, wrote:
> Greetings,
>
> We have been supporting both Keepalived and Pacemaker to handle VIP
> management.
> Keepalived is actually the to
Hey all,
As noted in the weekly report [0], today is feature freeze for
keystone-related specifications. I wanted to elaborate on each
specification so that our plan is clear moving forward.
*Unified Limits**
**
*I propose that we issue a feature freeze exception for this work.
Mainly because the
On Fri, Jul 13, 2018 at 3:20 PM Lance Bragstad wrote:
>
> Hey all,
>
> As noted in the weekly report [0], today is feature freeze for
> keystone-related specifications. I wanted to elaborate on each specification
> so that our plan is clear moving forward.
>
> Unified Limits
>
> I propose that w
On 7/11/2018 8:14 PM, Ghanshyam Mann wrote:
4. Volume multiattach enhancements:
-https://blueprints.launchpad.net/nova/+spec/volume-multiattach-enhancements
-https://review.openstack.org/#/q/topic:bp/volume-multiattach-enhancements+(status:open+OR+status:merged)
- Weekly Progress: mriedem men
On 7/11/2018 9:03 PM, Zhenyu Zheng wrote:
2. Abort live migration in queued state:
-https://blueprints.launchpad.net/nova/+spec/abort-live-migration-in-queued-status
-https://review.openstack.org/#/q/topic:bp/abort-live-migration-in-queued-status+(status:open+OR+status:merged)
Hello,
just wondering there was not Wiki page for the upcoming PTG in Denver,
so I've just created [1] and put in the links what I found here. Please
check and update if required.
thx
Frank
[1] https://wiki.openstack.org/wiki/PTG/Stein/Etherpads
There are currently no open changes for the nova-network API removal
tracked here [1] but there are at least two low-hanging fruit APIs to
remove:
* os-floating-ips-bulk
* os-floating-ips-dns
It would be nice to at least get those removed yet before the feature
freeze. See one of the existing
Hello,
the Docs and I18n team will also present during the PTG in Denver. The
rough plan told us on Monday/Tuesday. As usually we're in the same room
and will use also the same Etherpad on [1],
which I have shameless copied from the last PTG in Denver, so we have
all this usefull links for Sta
Hello,
On Fri, Jul 13, 2018 at 02:19:35PM -0500, Lance Bragstad wrote:
> *Capability Lists**
> *
> The capability lists involves a lot of work, not just within keystone,
> but also keystonemiddleware, which will freeze next week. I think it's
> reasonable to say that this will be something that ha
On 7/13/2018 3:16 PM, Frank Kloeker wrote:
Hello,
just wondering there was not Wiki page for the upcoming PTG in Denver,
so I've just created [1] and put in the links what I found here. Please
check and update if required.
thx
Frank
[1] https://wiki.openstack.org/wiki/PTG/Stein/Etherpads
On 18-07-13 14:57:58, Doug Hellmann wrote:
> The deadline for releasing non-client libraries for Rocky is coming up
> next week on 19 July (https://releases.openstack.org/rocky/schedule.html).
>
> We have a few libraries that have no releases at all this cycle,
> which makes creating the stable br
On 07/13/2018 03:37 PM, Johannes Grassler wrote:
> Hello,
>
> On Fri, Jul 13, 2018 at 02:19:35PM -0500, Lance Bragstad wrote:
>> *Capability Lists**
>> *
>> The capability lists involves a lot of work, not just within keystone,
>> but also keystonemiddleware, which will freeze next week. I think
On 07/13/2018 02:37 PM, Harry Rybacki wrote:
> On Fri, Jul 13, 2018 at 3:20 PM Lance Bragstad wrote:
>> Hey all,
>>
>> As noted in the weekly report [0], today is feature freeze for
>> keystone-related specifications. I wanted to elaborate on each specification
>> so that our plan is clear mov
Hello,
On Fri, Jul 13, 2018 at 03:50:33PM -0500, Lance Bragstad wrote:
> On 07/13/2018 03:37 PM, Johannes Grassler wrote:
> > On Fri, Jul 13, 2018 at 02:19:35PM -0500, Lance Bragstad wrote:
> >> *Capability Lists**
> >> *
> >> The capability lists involves a lot of work, not just within keystone,
Hi Amy,
First, I want to confirm which version of devstack you were using? (go to
the devstack folder and type "git log -1").
If possible, I would suggest to do the following steps:
* Run ./unstack
* Run ./clean
* Pull down the latest version of devstack (if it is too old)
* Pull down the latest
29 matches
Mail list logo
