[openstack-dev] [all] Ongoing spam in Freenode IRC channels

[Ian Wienand]

Hello,

It seems freenode is currently receiving a lot of unsolicited traffic
across all channels.  The freenode team are aware [1] and doing their
best.

There are not really a lot of options.  We can set "+r" on channels
which means only nickserv registered users can join channels.  We have
traditionally avoided this, because it is yet one more barrier to
communication when many are already unfamiliar with IRC access.
However, having channels filled with irrelevant messages is also not
very accessible.

This is temporarily enabled in #openstack-infra for the time being, so
we can co-ordinate without interruption.

Thankfully AFAIK we have not needed an abuse policy on this before;
but I guess we are the point we need some sort of coordinated
response.

I'd suggest to start, people with an interest in a channel can request
+r from an IRC admin in #openstack-infra and we track it at [2]

Longer term ... suggestions welcome? :)

-i

[1] https://freenode.net/news/spambot-attack
[2] https://etherpad.openstack.org/p/freenode-plus-r-08-2018

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to VF mirroring

[Zhao, Forrest]

Hi Miguel,

I just notice that you’re also in the reviewer list of #57447 ☺ Look forward to 
having more discussion on the design details next week.

We also plan to propose 5~6 new features (which originate from StarlingX 
project [1]) to Stein. So far 2 specs have been uploaded for review: [2] and 
[3].

BTW. Do you know when the PTG etherpad will be created? We’ll first propose our 
specs to PTG etherpad. And hopefully we can have opportunity to attend PTG in 
Denver to have face-to-face discussion with you and other key stakeholders in 
community.

Thanks,
Forrest

[1] https://wiki.openstack.org/wiki/StarlingX
[2] https://review.openstack.org/579410/
[3] https://review.openstack.org/579411


From: Miguel Lavalle [mailto:mig...@mlavalle.com]
Sent: Wednesday, August 1, 2018 1:26 AM
To: Zhao, Forrest 
Cc: OpenStack Development Mailing List 
Subject: Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to VF 
mirroring

Hi Forrest,

Yes, in my email, I was precisely referring to the work around 
https://review.openstack.org/#/c/574477.
 Now that we are wrapping up Rocky, I wanted to raise the visibility of this 
spec. I am glad you noticed. This week we are going to cut our RC-1 and I don't 
anticipate that we will will have a RC-2 for Rocky. So starting next week, 
let's go back to the spec and refine it, so we can start implementing in Stein 
as soon as possible. Depending on how much progress we make in the spec, we may 
need to schedule a discussion during the PTG in Denver, September 10 - 14, in 
case face to face time is needed to reach an agreement. I know that Manjeet is 
going to attend the PTG and he has already talked to me about this spec in the 
recent past. So maybe Manjeet could be the conduit to represent this spec in 
Denver, in case we need to talk about it there

Best regards

Miguel

On Tue, Jul 31, 2018 at 4:12 AM, Zhao, Forrest 
mailto:forrest.z...@intel.com>> wrote:
Hi Miguel,

In your mail “PTL candidacy for the Stein cycle”, it mentioned that “port 
mirroring for SR-IOV VF to VF mirroring” is within Stein goal.

Could you tell where is the place to discuss the design for this feature? 
Mailing list, IRC channel, weekly meeting or others?

I was involved in its spec review at https://review.openstack.org/#/c/574477/; 
but it has not been updated for a while.

Thanks,
Forrest

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][election][tc] Lederless projects.

[Tony Breeds]

On Wed, Aug 01, 2018 at 09:55:13AM +1000, Tony Breeds wrote:
> 
> Hello all,
> The PTL Nomination period is now over. The official candidate list
> is available on the election website[0].
> 
> There are 8 projects without candidates, so according to this
> resolution[1], the TC will have to decide how the following
> projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm,
> RefStack, Searchlight, Trove and Winstackers.

Hello TC,
A few extra details[1]:

---
Projects[1]   :65
Projects with candidates  :57 ( 87.69%)
Projects with election: 2 (  3.08%)
---
Need election : 2 (Senlin Tacker)
Need appointment  : 8 (Dragonflow Freezer Loci Packaging_Rpm RefStack
   Searchlight Trove Winstackers)
===
Stats gathered@ 2018-08-01 00:11:59 UTC

Of the 8 projects that can be considered leaderless, Trove did have a
candidate[2] that doesn't meet the ATC criteria in that they do not
have a merged change.

I also excluded Security due to the governance review[3] to remove it as
a project and the companion email discussion[4]

Yours Tony.

[1] http://paste.openstack.org/show/727002
[2] https://review.openstack.org/587333
[3] https://review.openstack.org/586896
[4] http://lists.openstack.org/pipermail/openstack-dev/2018-July/132595.html


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all][election] PTL voting underway

[Tony Breeds]

Hi folks,
Polls for PTL elections are now open and will remain open for you to
cast your vote until Aug 07, 2018 23:45 UTC.

We are having elections for Senlin and Tacker.

If you are a Foundation individual member and had a commit in
one of the program's projects[0] over the Aug 11, 2017 00:00 UTC to Jul
24, 2018 00:00 UTC timeframe (Queens to Rocky) then you are eligible to
vote. You should find your email with a link to the Condorcet page to
cast your vote in the inbox of your gerrit preferred email[1].

What to do if you don't see the email and have a commit in at
least one of the programs having an election:
* check the trash or spam folders of your gerrit Preferred
Email address, in case it went into trash or spam
* wait a bit and check again, in case your email server is a bit slow
* find the sha of at least one commit from the program
project repos[0] and email the election officials.

If we can confirm that you are entitled to vote, we will add you
to the voters list for the appropriate election.

Our democratic process is important to the health of OpenStack,
please exercise your right to vote!

Candidate statements/platforms can be found linked to Candidate
names on this page:
http://governance.openstack.org/election/#stein-ptl-candidates

Happy voting,

[0] The list of the program projects eligible for electoral status:

https://git.openstack.org/cgit/openstack/governance/plain/reference/projects.yaml?id=aug-2018-elections

[1] Sign into review.openstack.org:
Go to Settings > Contact Information.
Look at the email listed as your Preferred Email.
That is where the ballot has been sent.


Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all][election] PTL nominations are now closed

[Tony Breeds]

Hello all,
The PTL Nomination period is now over. The official candidate list
is available on the election website[0].

There are 8 projects without candidates, so according to this
resolution[1], the TC will have to decide how the following
projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm,
RefStack, Searchlight, Trove and Winstackers.

There are 2 projects that will have elections: Senlin, Tacker. The details
for those will be posted shortly after we setup the CIVS system.

Thank you,

[0] http://governance.openstack.org/election/#stein-ptl-candidates
[1] 
http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.html


Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo][ci][metrics] FFE request for QDR integration in TripleO (Was: Stucked in the middle of work because of RDO CI)

[Alex Schultz]

On Tue, Jul 31, 2018 at 11:31 AM, Pradeep Kilambi  wrote:
> Hi Alex:
>
> Can you consider this our FFE for the QDR patches. Its mainly blocked on CI
> issues. Half the patches for QDR integration are already merged. The other 3
> referenced need to get merged once CI passes. Please consider this out
> formal request for FFE for QDR integration in tripleo.
>

Ok if it's just these patches and there is no further work it should
be OK. I did point out (prior to CI issues) that the patch[0] actually
broke the ovb jobs back in June. It seemed to be related to missing
containers or something to that effect.  So we'll need to be extra
care when merging this to ensure it does not break anything.  If we
get clean jobs prior to the rc1, we can merge it. If not I'd say we
need to hold off.  I don't consider this is a blocking feature.

Thanks,
-Alex

[0] https://review.openstack.org/#/c/578749/

> Cheers,
> ~ Prad
>
> On Tue, Jul 31, 2018 at 7:40 AM Sagi Shnaidman  wrote:
>>
>> Hi, Martin
>>
>> I see master OVB jobs are passing now [1], please recheck.
>>
>> [1] http://cistatus.tripleo.org/
>>
>> On Tue, Jul 31, 2018 at 12:24 PM, Martin Magr  wrote:
>>>
>>> Greetings guys,
>>>
>>>   it is pretty obvious that RDO CI jobs in TripleO projects are broken
>>> [0]. Once Zuul CI jobs will pass would it be possible to have AMQP/collectd
>>> patches ([1],[2],[3]) merged please even though the negative result of RDO
>>> CI jobs? Half of the patches for this feature is merged and the other half
>>> is stucked in this situation, were nobody reviews these patches, because
>>> there is red -1. Those patches passed Zuul jobs several times already and
>>> were manually tested too.
>>>
>>> Thanks in advance for consideration of this situation,
>>> Martin
>>>
>>> [0]
>>> https://trello.com/c/hkvfxAdX/667-cixtripleoci-rdo-software-factory-3rd-party-jobs-failing-due-to-instance-nodefailure
>>> [1] https://review.openstack.org/#/c/578749
>>> [2] https://review.openstack.org/#/c/576057/
>>> [3] https://review.openstack.org/#/c/572312/
>>>
>>> --
>>> Martin Mágr
>>> Senior Software Engineer
>>> Red Hat Czech
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>> --
>> Best regards
>> Sagi Shnaidman
>
>
>
> --
> Cheers,
> ~ Prad

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo][ci][metrics] Stucked in the middle of work because of RDO CI

[Wesley Hayutin]

On Tue, Jul 31, 2018 at 7:41 AM Sagi Shnaidman  wrote:

> Hi, Martin
>
> I see master OVB jobs are passing now [1], please recheck.
>
> [1] http://cistatus.tripleo.org/
>

Things have improved and I see a lot of jobs passing however at the same
time I see too many jobs failing due to node_failures.  We are tracking the
data from [1].  Certainly the issue is NOT ideal for development and we
need to remain focused on improving the situation.

Thanks

[1] https://softwarefactory-project.io/zuul/api/tenant/rdoproject.org/builds



>
>
> On Tue, Jul 31, 2018 at 12:24 PM, Martin Magr  wrote:
>
>> Greetings guys,
>>
>>   it is pretty obvious that RDO CI jobs in TripleO projects are broken
>> [0]. Once Zuul CI jobs will pass would it be possible to have AMQP/collectd
>> patches ([1],[2],[3]) merged please even though the negative result of RDO
>> CI jobs? Half of the patches for this feature is merged and the other half
>> is stucked in this situation, were nobody reviews these patches, because
>> there is red -1. Those patches passed Zuul jobs several times already and
>> were manually tested too.
>>
>> Thanks in advance for consideration of this situation,
>> Martin
>>
>> [0]
>> https://trello.com/c/hkvfxAdX/667-cixtripleoci-rdo-software-factory-3rd-party-jobs-failing-due-to-instance-nodefailure
>> [1] https://review.openstack.org/#/c/578749
>> [2] https://review.openstack.org/#/c/576057/
>> [3] https://review.openstack.org/#/c/572312/
>>
>> --
>> Martin Mágr
>> Senior Software Engineer
>> Red Hat Czech
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best regards
> Sagi Shnaidman
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 

Wes Hayutin

Associate MANAGER

Red Hat



w hayu...@redhat.comT: +1919 <+19197544114>4232509
   IRC:  weshay


View my calendar and check my availability for meetings HERE

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [designate][stable] Stable Core Team Updates

[Sean McGinnis]

On Tue, Jul 31, 2018 at 04:15:16PM -0500, Matt Riedemann wrote:
> On 7/31/2018 12:39 PM, Graham Hayes wrote:
> > I would like to nominate 2 new stable core reviewers for Designate.
> > 
> > * Erik Olof Gunnar Andersson
> > * Jens Harbott (frickler)
> > 
> Looks OK to me on both.
> 
> -- 
> 
> Thanks,
> 
> Matt
> 

+1

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [designate][stable] Stable Core Team Updates

[Matt Riedemann]

On 7/31/2018 12:39 PM, Graham Hayes wrote:

I would like to nominate 2 new stable core reviewers for Designate.

* Erik Olof Gunnar Andersson
* Jens Harbott (frickler)

Erik has been doing a lot of stable reviews recently, and Jens has shown
that he understands the policy in other reviews (and has stable rights
on other repositories (like DevStack) already).

Thanks,

Graham Hayes

1 -
https://review.openstack.org/#/q/(project:openstack/designate+OR+project:openstack/python-designateclient+OR+project:openstack/designate-specs+OR+project:openstack/designate-dashboard+OR+project:openstack/designate-tempest-plugin)+branch:%255Estable/.*+reviewedby:%22Erik+Olof+Gunnar+Andersson+%253Ceandersson%2540blizzard.com%253E%22

2 -
https://review.openstack.org/#/q/(project:openstack/designate+OR+project:openstack/python-designateclient+OR+project:openstack/designate-specs+OR+project:openstack/designate-dashboard+OR+project:openstack/designate-tempest-plugin)+branch:%255Estable/.*+reviewedby:%22Jens+Harbott+(frickler)+%253Cj.harbott%2540x-ion.de%253E%22


Looks OK to me on both.

--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ptg][requiremets] - Stein Etherpad

[Matthew Thode]

https://etherpad.openstack.org/p/stein-PTG-requirements

That is all

-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] deployement fails

[Samuel Monderer]

I used the same host network configuration I used with Ocata (see attached)
Do I need to change them if I'm deploying queens??

Thanks,
Samuel

On Tue, Jul 31, 2018 at 7:06 PM Alex Schultz  wrote:

> On Mon, Jul 30, 2018 at 8:48 AM, Samuel Monderer
>  wrote:
> > Hi,
> >
> > I'm trying to deploy a small environment with one controller and one
> compute
> > but i get a timeout with no specific information in the logs
> >
> > 2018-07-30 13:19:41Z [overcloud.Controller.0.ControllerConfig]:
> > CREATE_IN_PROGRESS  state changed
> > 2018-07-30 13:19:41Z [overcloud.Controller.0.ControllerConfig]:
> > CREATE_COMPLETE  state changed
> > 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3]: CREATE_FAILED  CREATE
> > aborted (Task create from ResourceGroup "ComputeGammaV3" Stack
> "overcloud"
> > [690ee33c-8194-4713-a44f-9c8dcf88359f] Timed out)
> > 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3]: UPDATE_FAILED  Stack
> UPDATE
> > cancelled
> > 2018-07-30 14:04:51Z [overcloud]: CREATE_FAILED  Timed out
> > 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED  Stack
> > CREATE cancelled
> > 2018-07-30 14:04:51Z [overcloud.Controller]: CREATE_FAILED  CREATE
> aborted
> > (Task create from ResourceGroup "Controller" Stack "overcloud"
> > [690ee33c-8194-4713-a44f-9c8dcf88359f] Timed out)
> > 2018-07-30 14:04:51Z [overcloud]: CREATE_FAILED  Timed out
> > 2018-07-30 14:04:51Z [overcloud.Controller]: UPDATE_FAILED  Stack UPDATE
> > cancelled
> > 2018-07-30 14:04:51Z [overcloud.Controller.0]: CREATE_FAILED  Stack
> CREATE
> > cancelled
> > 2018-07-30 14:04:52Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED
> > resources[0]: Stack CREATE cancelled
> >
> >  Stack overcloud CREATE_FAILED
> >
> > overcloud.ComputeGammaV3.0:
> >   resource_type: OS::TripleO::ComputeGammaV3
> >   physical_resource_id: 5755d746-7cbf-4f3d-a9e1-d94a713705a7
> >   status: CREATE_FAILED
> >   status_reason: |
> > resources[0]: Stack CREATE cancelled
> > overcloud.Controller.0:
> >   resource_type: OS::TripleO::Controller
> >   physical_resource_id: 4bcf84c1-1d54-45ee-9f81-b6dda780cbd7
> >   status: CREATE_FAILED
> >   status_reason: |
> > resources[0]: Stack CREATE cancelled
> > Not cleaning temporary directory /tmp/tripleoclient-vxGzKo
> > Not cleaning temporary directory /tmp/tripleoclient-vxGzKo
> > Heat Stack create failed.
> > Heat Stack create failed.
> > (undercloud) [stack@staging-director ~]$
> >
>
> So this is a timeout likely caused by a bad network configuration so
> no response makes it back to Heat during the deployment. Heat never
> gets a response back so it just times out.  You'll need to check your
> host network configuration and trouble shoot that.
>
> Thanks,
> -Alex
>
> > It seems that it wasn't able to configure the OVS bridges
> >
> > (undercloud) [stack@staging-director ~]$ openstack software deployment
> show
> > 4b4fc54f-7912-40e2-8ad4-79f6179fe701
> >
> +---++
> > | Field | Value
> |
> >
> +---++
> > | id| 4b4fc54f-7912-40e2-8ad4-79f6179fe701
>  |
> > | server_id | 0accb7a3-4869-4497-8f3b-5a3d99f3926b
>  |
> > | config_id | 2641b4dd-afc7-4bf5-a2e2-481c207e4b7f
>  |
> > | creation_time | 2018-07-30T13:19:44Z
>  |
> > | updated_time  |
> |
> > | status| IN_PROGRESS
> |
> > | status_reason | Deploy data available
> |
> > | input_values  | {u'interface_name': u'nic1', u'bridge_name': u'br-ex'}
> |
> > | action| CREATE
>  |
> >
> +---++
> > (undercloud) [stack@staging-director ~]$ openstack software deployment
> show
> > a297e8ae-f4c9-41b0-938f-c51f9fe23843
> >
> +---++
> > | Field | Value
> |
> >
> +---++
> > | id| a297e8ae-f4c9-41b0-938f-c51f9fe23843
>  |
> > | server_id | 145167da-9b96-4eee-bfe9-399b854c1e84
>  |
> > | config_id | d1baf0a5-de9b-48f2-b486-9f5d97f7e94f
>  |
> > | creation_time | 2018-07-30T13:17:29Z
>  |
> > | updated_time  |
> |
> > | status| IN_PROGRESS
> |
> > | status_reason | Deploy data available
> |
> > | input_values  | {u'interface_name': u'nic1', u'bridge_name': u'br-ex'}
> |
> > | action| CREATE
>  |
> >
> +---++
> > (undercloud) [stack@staging-director ~]$
> >
> > Regards,
> > Samuel
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not 

Re: [openstack-dev] [requirements][ffe] Critical bug found in python-cinderclient

[Doug Hellmann]

Excerpts from Sean McGinnis's message of 2018-07-31 14:15:08 -0500:
> A critical bug has been found in python-cinderclient that is impacting both
> horizon and python-openstackclient (at least).
> 
> https://bugs.launchpad.net/cinder/+bug/1784703
> 
> tl;dr is, something new was added with a microversion, but support for that 
> was
> done incorrectly such that nothing less than that new microversion would be
> allowed. This patch addresses the issue:
> 
> https://review.openstack.org/587601
> 
> Once that lands we will need a new python-cinderclient release to unbreak
> clients. We may want to blacklist python-cinderclient 4.0.0, but I think at
> least just raising the upper-constraints should get things working again.
> 
> Sean
> 

Both adding the exclusion and changing the upper constraint makes sense,
since it will ensure that bad version never makes it back into the
constraints list.

We don't need to sync the exclusion setting into all of the projects
that depend on the client, so we won't need a new release of any of the
downstream consumers.

We could add the exclusion to OSC on master, just for accuracy's sake.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [requirements][ffe] Critical bug found in python-cinderclient

[Sean McGinnis]

A critical bug has been found in python-cinderclient that is impacting both
horizon and python-openstackclient (at least).

https://bugs.launchpad.net/cinder/+bug/1784703

tl;dr is, something new was added with a microversion, but support for that was
done incorrectly such that nothing less than that new microversion would be
allowed. This patch addresses the issue:

https://review.openstack.org/587601

Once that lands we will need a new python-cinderclient release to unbreak
clients. We may want to blacklist python-cinderclient 4.0.0, but I think at
least just raising the upper-constraints should get things working again.

Sean


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] - TACKER + NETWORKING_SFC + NSH

[william sales]

Hello guys,

is there any version of Tacker that allows the use of networking_sfc with
NSH?

Thankful.

William Sales
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [FFE][requirements] Bump ansible-runner u-c to 1.0.5

[Jakub Libosvar]

On 31/07/2018 18:46, Matthew Thode wrote:
> On 18-07-31 17:30:02, Jakub Libosvar wrote:
>> Hi all,
>>
>> I want to ask for FFE at this time to bump upper-constraint version of
>> ansible-runner library from 1.0.4 to 1.0.5.
>>
>> Reason: ansible-runner 1.0.4 has an issue when running with currently
>> used eventlet version because of missing select.poll() in eventlet [1].
>> The fix [2] is present in 1.0.5 ansible-runner version.
>>
>> Impact: networking-ansible project uses Neutron project and
>> ansible-runner together and Neutron monkey patches code with eventlet.
>> This fails all operations at networking-ansible.
>>
>> Statement: networking-ansible is the only project using ansible-runner
>> in OpenStack world [3] so if we release Rocky with 1.0.4, the only
>> project using it becomes useless. Bumping the version at this later
>> stage will not affect any other project beside networking-ansible.
>>
>> [1] https://github.com/ansible/ansible-runner/issues/90
>> [2]
>> https://github.com/ansible/ansible-runner/commit/5608e786eb96408658604e75ef3db3c9a6b39308
>> [3] http://codesearch.openstack.org/?q=ansible-runner=nope==
> 
> Looks good, you may want to update the minimum in networking-ansible,
> but lgtm otherwise.
> 
> | networking-ansible | requirements.txt|5 | ansible-runner>=1.0.3 
> # Apache-2.0 |

Yep, thanks for reminder. I've done that here
https://review.openstack.org/#/c/587475/ where the workaround was removed.

Jakub
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] [Cyborg] Updates to os-acc proposal

[Eric Fried]

Sundar-

>   * Cyborg drivers deal with device-specific aspects, including
> discovery/enumeration of devices and handling the Device Half of the
> attach (preparing devices/accelerators for attach to an instance,
> post-attach cleanup (if any) after successful attach, releasing
> device/accelerator resources on instance termination or failed
> attach, etc.)
>   * os-acc plugins deal with hypervisor/system/architecture-specific
> aspects, including handling the Instance Half of the attach (e.g.
> for libvirt with PCI, preparing the XML snippet to be included in
> the domain XML).

This sounds well and good, but discovery/enumeration will also be
hypervisor/system/architecture-specific. So...

> Thus, the drivers and plugins are expected to be complementary. For
> example, for 2 devices of types T1 and T2, there shall be 2 separate
> Cyborg drivers. Further, we would have separate plugins for, say,
> x86+KVM systems and Power systems. We could then have four different
> deployments -- T1 on x86+KVM, T2 on x86+KVM, T1 on Power, T2 on Power --
> by suitable combinations of the drivers and plugins.

...the discovery/enumeration code for T1 on x86+KVM (lsdev? lspci?
walking the /dev file system?) will be totally different from the
discovery/enumeration code for T1 on Power
(pypowervm.wrappers.ManagedSystem.get(adapter)).

I don't mind saying "drivers do the device side; plugins do the instance
side" but I don't see getting around the fact that both "sides" will
need to have platform-specific code.

> One secondary detail to note is that Nova compute calls os-acc per
> instance for all accelerators for that instance, not once for each
> accelerator.

You mean for getVAN()? Because AFAIK, os_vif.plug(list_of_vif_objects,
InstanceInfo) is *not* how nova uses os-vif for plugging.

Thanks,
Eric
.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [designate][stable] Stable Core Team Updates

[Graham Hayes]

Hi Stable Team,

I would like to nominate 2 new stable core reviewers for Designate.

* Erik Olof Gunnar Andersson 
* Jens Harbott (frickler) 

Erik has been doing a lot of stable reviews recently, and Jens has shown
that he understands the policy in other reviews (and has stable rights
on other repositories (like DevStack) already).

Thanks,

Graham Hayes

1 -
https://review.openstack.org/#/q/(project:openstack/designate+OR+project:openstack/python-designateclient+OR+project:openstack/designate-specs+OR+project:openstack/designate-dashboard+OR+project:openstack/designate-tempest-plugin)+branch:%255Estable/.*+reviewedby:%22Erik+Olof+Gunnar+Andersson+%253Ceandersson%2540blizzard.com%253E%22

2 -
https://review.openstack.org/#/q/(project:openstack/designate+OR+project:openstack/python-designateclient+OR+project:openstack/designate-specs+OR+project:openstack/designate-dashboard+OR+project:openstack/designate-tempest-plugin)+branch:%255Estable/.*+reviewedby:%22Jens+Harbott+(frickler)+%253Cj.harbott%2540x-ion.de%253E%22



signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo][ci][metrics] FFE request for QDR integration in TripleO (Was: Stucked in the middle of work because of RDO CI)

[Pradeep Kilambi]

Hi Alex:

Can you consider this our FFE for the QDR patches. Its mainly blocked on CI
issues. Half the patches for QDR integration are already merged. The other
3 referenced need to get merged once CI passes. Please consider this out
formal request for FFE for QDR integration in tripleo.

Cheers,
~ Prad

On Tue, Jul 31, 2018 at 7:40 AM Sagi Shnaidman  wrote:

> Hi, Martin
>
> I see master OVB jobs are passing now [1], please recheck.
>
> [1] http://cistatus.tripleo.org/
>
> On Tue, Jul 31, 2018 at 12:24 PM, Martin Magr  wrote:
>
>> Greetings guys,
>>
>>   it is pretty obvious that RDO CI jobs in TripleO projects are broken
>> [0]. Once Zuul CI jobs will pass would it be possible to have AMQP/collectd
>> patches ([1],[2],[3]) merged please even though the negative result of RDO
>> CI jobs? Half of the patches for this feature is merged and the other half
>> is stucked in this situation, were nobody reviews these patches, because
>> there is red -1. Those patches passed Zuul jobs several times already and
>> were manually tested too.
>>
>> Thanks in advance for consideration of this situation,
>> Martin
>>
>> [0]
>> https://trello.com/c/hkvfxAdX/667-cixtripleoci-rdo-software-factory-3rd-party-jobs-failing-due-to-instance-nodefailure
>> [1] https://review.openstack.org/#/c/578749
>> [2] https://review.openstack.org/#/c/576057/
>> [3] https://review.openstack.org/#/c/572312/
>>
>> --
>> Martin Mágr
>> Senior Software Engineer
>> Red Hat Czech
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best regards
> Sagi Shnaidman
>


-- 
Cheers,
~ Prad
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to VF mirroring

[Miguel Lavalle]

Hi Forrest,

Yes, in my email, I was precisely referring to the work around
https://review.openstack.org/#/c/574477. Now that we are wrapping up Rocky,
I wanted to raise the visibility of this spec. I am glad you noticed. This
week we are going to cut our RC-1 and I don't anticipate that we will will
have a RC-2 for Rocky. So starting next week, let's go back to the spec and
refine it, so we can start implementing in Stein as soon as possible.
Depending on how much progress we make in the spec, we may need to schedule
a discussion during the PTG in Denver, September 10 - 14, in case face to
face time is needed to reach an agreement. I know that Manjeet is going to
attend the PTG and he has already talked to me about this spec in the
recent past. So maybe Manjeet could be the conduit to represent this spec
in Denver, in case we need to talk about it there

Best regards

Miguel

On Tue, Jul 31, 2018 at 4:12 AM, Zhao, Forrest 
wrote:

> Hi Miguel,
>
>
>
> In your mail “PTL candidacy for the Stein cycle”, it mentioned that “port
> mirroring for SR-IOV VF to VF mirroring” is within Stein goal.
>
>
>
> Could you tell where is the place to discuss the design for this feature?
> Mailing list, IRC channel, weekly meeting or others?
>
>
>
> I was involved in its spec review at https://review.openstack.org/#
> /c/574477/; but it has not been updated for a while.
>
>
>
> Thanks,
>
> Forrest
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptg] Self-healing SIG meeting moved to Thursday morning

[Adam Spiers]

Thierry Carrez  wrote:

Hi! Quick heads-up:

Following a request[1] from Adam Spiers (SIG lead), we modified the 
PTG schedule to move the Self-Healing SIG meeting from Friday (all 
day) to Thursday morning (only morning). You can see the resulting 
schedule at:


https://www.openstack.org/ptg#tab_schedule

Sorry for any inconvenience this may cause.


It's me who should be apologising - Thierry only deserves thanks for
accommodating my request at late notice ;-)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] The Weekly Owl - 27th Edition

[Emilien Macchi]

Welcome to the twenty-seventh edition of a weekly update in TripleO world!
The goal is to provide a short reading (less than 5 minutes) to learn
what's new this week.
Any contributions and feedback are welcome.
Link to the previous version:
http://lists.openstack.org/pipermail/openstack-dev/2018-July/132448.html

+-+
| General announcements |
+-+

+--> We're preparing the first release candidate of TripleO Rocky, please
focus on Critical / High bugs.
+--> Reminder about PTG etherpad, feel free to propose topics:
https://etherpad.openstack.org/p/tripleo-ptg-stein

+--+
| Continuous Integration |
+--+

+--> Sprint theme: migration to zuul v3, including migrating from legacy
bash to ansible tasks/playbooks (More on
https://trello.com/c/JikmHXSS/881-sprint-17-goals)
+--> The Ruck and Rover for this sprint  are Gabriele Cerami (panda) and
Rafael Folco (rfolco). Please tell them any CI issue.
+--> Promotion on master is 11 days, 0 day on Queens, 3 days on Pike and 4
days on Ocata.
+--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting

+-+
| Upgrades |
+-+

+--> Need review on work for updates/upgrades with external installers:
https://review.openstack.org/#/q/status:open+branch:master+topic:external-update-upgrade
+--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad-status

+---+
| Containers |
+---+

+--> No major update this week, in bug fixing mode.
+--> More: https://etherpad.openstack.org/p/tripleo-containers-squad-status

+--+
| config-download |
+--+

+--> No updates this week..
+--> More:
https://etherpad.openstack.org/p/tripleo-config-download-squad-status

+--+
| Integration |
+--+

+--> No updates this week.
+--> More: https://etherpad.openstack.org/p/tripleo-integration-squad-status

+-+
| UI/CLI |
+-+

+--> config-download support work is landed!
+--> More: https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status

+---+
| Validations |
+---+

+--> Need review on custom validations support.
+--> Efforts around Mistral workflow lookup plugin
+--> More: https://etherpad.openstack.org/p/tripleo-validations-squad-status

+---+
| Networking |
+---+

+--> Policy based routing for os-net-config
+--> Patches for Neutron routed networks support using segments for TripleO
+--> Ansible ML2 driver: good progress on patches and testing.
+--> More: https://etherpad.openstack.org/p/tripleo-networking-squad-status

+--+
| Workflows |
+--+

+--> No updates this week.
+--> More: https://etherpad.openstack.org/p/tripleo-workflows-squad-status

+---+
| Security |
+---+

+--> No updates this week.
+--> Last meeting notes:
http://eavesdrop.openstack.org/meetings/security_squad/2018/security_squad.2018-07-18-12.07.html
+--> More: https://etherpad.openstack.org/p/tripleo-security-squad

++
| Owl fact  |
++
Owls have far-sighted, tubular eyes: instead of spherical eyeballs, owls
have "eye tubes" that go far back into their skulls - which means their
eyes are fixed in place, so they have to turn their heads to see. The size
of their eyes helps them see in the dark, and they're far-sighted, which
allows them to spot prey from yards away. Up close, everything is blurry,
and they depend on small, hair-like feathers on their beaks and feet to
feel their food.

Source: http://mentalfloss.com/article/68473/15-mysterious-facts-about-owls

Thank you all for reading and stay tuned!
--
Your fellow reporter, Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [requirements][ffe] glance_store 0.26.1 (to be released)

[Matthew Thode]

On 18-07-31 16:43:00, Erno Kuvaja wrote:
> Hi all,
> 
> We found a critical bug on glance_store release 0.26.0 (the final
> release for Rocky) preventing us to consume the multihash work for
> Glance Rocky release.
> 
> We would like to include  https://review.openstack.org/#/c/587098
> containing the missing wrappers for the feature to work. And have
> requirement bump to 0.26.1 (once tagged) for Rocky release. The change
> is well isolated and self contained, not affecting the behavior apart
> from the consumption of the multihash feature.
> 

Looks fine, you may consider bumping the min defined in downstream
consumers but lgtm otherwise.

++--+--+---+
| Repository | Filename 
| Line | Text  |
++--+--+---+
| glance | requirements.txt 
|   49 | glance-store>=0.22.0 # Apache-2.0 |
| glare  | requirements.txt 
|   50 | glance-store>=0.22.0 # Apache-2.0 |
| upstream-institute-virtual-environment | 
elements/upstream-training/static/tmp/requirements.txt   |   64 | 
glance-store==0.22.0  |
++--+--+---+


-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [FFE][requirements] Bump ansible-runner u-c to 1.0.5

[Matthew Thode]

On 18-07-31 17:30:02, Jakub Libosvar wrote:
> Hi all,
> 
> I want to ask for FFE at this time to bump upper-constraint version of
> ansible-runner library from 1.0.4 to 1.0.5.
> 
> Reason: ansible-runner 1.0.4 has an issue when running with currently
> used eventlet version because of missing select.poll() in eventlet [1].
> The fix [2] is present in 1.0.5 ansible-runner version.
> 
> Impact: networking-ansible project uses Neutron project and
> ansible-runner together and Neutron monkey patches code with eventlet.
> This fails all operations at networking-ansible.
> 
> Statement: networking-ansible is the only project using ansible-runner
> in OpenStack world [3] so if we release Rocky with 1.0.4, the only
> project using it becomes useless. Bumping the version at this later
> stage will not affect any other project beside networking-ansible.
> 
> [1] https://github.com/ansible/ansible-runner/issues/90
> [2]
> https://github.com/ansible/ansible-runner/commit/5608e786eb96408658604e75ef3db3c9a6b39308
> [3] http://codesearch.openstack.org/?q=ansible-runner=nope==

Looks good, you may want to update the minimum in networking-ansible,
but lgtm otherwise.

| networking-ansible | requirements.txt|5 | ansible-runner>=1.0.3 # 
Apache-2.0 |

-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ptg] Self-healing SIG meeting moved to Thursday morning

[Thierry Carrez]

Hi! Quick heads-up:

Following a request[1] from Adam Spiers (SIG lead), we modified the PTG 
schedule to move the Self-Healing SIG meeting from Friday (all day) to 
Thursday morning (only morning). You can see the resulting schedule at:


https://www.openstack.org/ptg#tab_schedule

Sorry for any inconvenience this may cause.

[1] http://lists.openstack.org/pipermail/openstack-dev/2018-July/132392.html

--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] TripleO CI+Tempest Squad Planning Summary: Sprint 17

[Matt Young]

>From the Halls of CI we greet thee!  HAIL!

# Overview

The CI and Tempest squads have recently completed the planning phase of
Sprint 17.  The Sprint runs from 26-July thru 15-Aug.  The sprint for both
squads is now in the initial design phase (first week) of the sprint.

The epic card and tasks for CI [1][2] and Tempest [3][4] squads are linked
below.

The Ruck and Rover for this sprint  are Gabriele Cerami (panda) and Rafael
Folco (rfolco).  Their notes and current status is tracked in the etherpad
for sprint 17 [5].

Please direct questions or queries to them regarding CI status or issues in
#tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick.

# CI Squad

* The main topic is focused on continuing the migration to zuul v3,
including migrating from legacy bash to ansible tasks/playbooks
* Between planned PTO and training, the team is running at reduced capacity
this sprint.

# Tempest Squad

* clearing out technical debt related to python-tempestconf and
refstack-client integration.
* developing materials for a presentation on implementing a tempest plugin.
* splitting out the validate-tempest role [6] to a discrete repository.
* Due to planned PTO the squad is quite resource constrained this sprint.

More detail on our team and process can be found in the spec [7]

Thanks,

Matt

[1] https://trello.com/c/JikmHXSS/881-sprint-17-goals
[2]
https://trello.com/b/U1ITy0cu/tripleo-and-rdo-ci?menu=filter=label:Sprint%2017%20CI

[3]
https://trello.com/c/yAnDETzJ/878-sprint-17-tempest-clear-technical-debts
[4]
https://trello.com/b/U1ITy0cu/tripleo-and-rdo-ci?menu=filter=label:Sprint%2017%20Tempest
[5] https://review.rdoproject.org/etherpad/p/ruckrover-sprint17
[6]
https://github.com/openstack/tripleo-quickstart-extras/tree/master/roles/validate-tempest
[7]
https://specs.openstack.org/openstack/tripleo-specs/specs/policy/ci-team-structure.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] deployement fails

[Alex Schultz]

On Mon, Jul 30, 2018 at 8:48 AM, Samuel Monderer
 wrote:
> Hi,
>
> I'm trying to deploy a small environment with one controller and one compute
> but i get a timeout with no specific information in the logs
>
> 2018-07-30 13:19:41Z [overcloud.Controller.0.ControllerConfig]:
> CREATE_IN_PROGRESS  state changed
> 2018-07-30 13:19:41Z [overcloud.Controller.0.ControllerConfig]:
> CREATE_COMPLETE  state changed
> 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3]: CREATE_FAILED  CREATE
> aborted (Task create from ResourceGroup "ComputeGammaV3" Stack "overcloud"
> [690ee33c-8194-4713-a44f-9c8dcf88359f] Timed out)
> 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3]: UPDATE_FAILED  Stack UPDATE
> cancelled
> 2018-07-30 14:04:51Z [overcloud]: CREATE_FAILED  Timed out
> 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED  Stack
> CREATE cancelled
> 2018-07-30 14:04:51Z [overcloud.Controller]: CREATE_FAILED  CREATE aborted
> (Task create from ResourceGroup "Controller" Stack "overcloud"
> [690ee33c-8194-4713-a44f-9c8dcf88359f] Timed out)
> 2018-07-30 14:04:51Z [overcloud]: CREATE_FAILED  Timed out
> 2018-07-30 14:04:51Z [overcloud.Controller]: UPDATE_FAILED  Stack UPDATE
> cancelled
> 2018-07-30 14:04:51Z [overcloud.Controller.0]: CREATE_FAILED  Stack CREATE
> cancelled
> 2018-07-30 14:04:52Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED
> resources[0]: Stack CREATE cancelled
>
>  Stack overcloud CREATE_FAILED
>
> overcloud.ComputeGammaV3.0:
>   resource_type: OS::TripleO::ComputeGammaV3
>   physical_resource_id: 5755d746-7cbf-4f3d-a9e1-d94a713705a7
>   status: CREATE_FAILED
>   status_reason: |
> resources[0]: Stack CREATE cancelled
> overcloud.Controller.0:
>   resource_type: OS::TripleO::Controller
>   physical_resource_id: 4bcf84c1-1d54-45ee-9f81-b6dda780cbd7
>   status: CREATE_FAILED
>   status_reason: |
> resources[0]: Stack CREATE cancelled
> Not cleaning temporary directory /tmp/tripleoclient-vxGzKo
> Not cleaning temporary directory /tmp/tripleoclient-vxGzKo
> Heat Stack create failed.
> Heat Stack create failed.
> (undercloud) [stack@staging-director ~]$
>

So this is a timeout likely caused by a bad network configuration so
no response makes it back to Heat during the deployment. Heat never
gets a response back so it just times out.  You'll need to check your
host network configuration and trouble shoot that.

Thanks,
-Alex

> It seems that it wasn't able to configure the OVS bridges
>
> (undercloud) [stack@staging-director ~]$ openstack software deployment show
> 4b4fc54f-7912-40e2-8ad4-79f6179fe701
> +---++
> | Field | Value  |
> +---++
> | id| 4b4fc54f-7912-40e2-8ad4-79f6179fe701   |
> | server_id | 0accb7a3-4869-4497-8f3b-5a3d99f3926b   |
> | config_id | 2641b4dd-afc7-4bf5-a2e2-481c207e4b7f   |
> | creation_time | 2018-07-30T13:19:44Z   |
> | updated_time  ||
> | status| IN_PROGRESS|
> | status_reason | Deploy data available  |
> | input_values  | {u'interface_name': u'nic1', u'bridge_name': u'br-ex'} |
> | action| CREATE |
> +---++
> (undercloud) [stack@staging-director ~]$ openstack software deployment show
> a297e8ae-f4c9-41b0-938f-c51f9fe23843
> +---++
> | Field | Value  |
> +---++
> | id| a297e8ae-f4c9-41b0-938f-c51f9fe23843   |
> | server_id | 145167da-9b96-4eee-bfe9-399b854c1e84   |
> | config_id | d1baf0a5-de9b-48f2-b486-9f5d97f7e94f   |
> | creation_time | 2018-07-30T13:17:29Z   |
> | updated_time  ||
> | status| IN_PROGRESS|
> | status_reason | Deploy data available  |
> | input_values  | {u'interface_name': u'nic1', u'bridge_name': u'br-ex'} |
> | action| CREATE |
> +---++
> (undercloud) [stack@staging-director ~]$
>
> Regards,
> Samuel
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 

[openstack-dev] [requirements][ffe] glance_store 0.26.1 (to be released)

[Erno Kuvaja]

Hi all,

We found a critical bug on glance_store release 0.26.0 (the final
release for Rocky) preventing us to consume the multihash work for
Glance Rocky release.

We would like to include  https://review.openstack.org/#/c/587098
containing the missing wrappers for the feature to work. And have
requirement bump to 0.26.1 (once tagged) for Rocky release. The change
is well isolated and self contained, not affecting the behavior apart
from the consumption of the multihash feature.

Best,
Erno jokke Kuvaja

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] TripleO Tempest squad status: Sprint 16

[Matt Young]

Greetings,

The TripleO Tempest squad has recently completed Sprint 16 (5-July -
25-July).

This sprint was focused on tasks related to python-tempestconf and
integration with the refstack client.  Some of this work will continue in
Sprint 17.

For a list of the completed and items for the sprint please refer to the
Epic card [1] and the task cards [2].

Thanks,

Matt

[1]
https://trello.com/c/1v1dYRnP/144-sprint-16-closing-python-tempestconf-items-out
[2]
https://trello.com/b/BjcIIp0f/tripleo-and-rdo-ci-archive?menu=filter=label:Sprint%2016%20Tempest
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FFE][requirements] Bump ansible-runner u-c to 1.0.5

[Jakub Libosvar]

Hi all,

I want to ask for FFE at this time to bump upper-constraint version of
ansible-runner library from 1.0.4 to 1.0.5.

Reason: ansible-runner 1.0.4 has an issue when running with currently
used eventlet version because of missing select.poll() in eventlet [1].
The fix [2] is present in 1.0.5 ansible-runner version.

Impact: networking-ansible project uses Neutron project and
ansible-runner together and Neutron monkey patches code with eventlet.
This fails all operations at networking-ansible.

Statement: networking-ansible is the only project using ansible-runner
in OpenStack world [3] so if we release Rocky with 1.0.4, the only
project using it becomes useless. Bumping the version at this later
stage will not affect any other project beside networking-ansible.

Thanks for consideration.

Jakub


[1] https://github.com/ansible/ansible-runner/issues/90
[2]
https://github.com/ansible/ansible-runner/commit/5608e786eb96408658604e75ef3db3c9a6b39308
[3] http://codesearch.openstack.org/?q=ansible-runner=nope==

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] TripleO CI squad status: Sprint 16

[Matt Young]

Greetings,

The TripleO CI squad has recently completed Sprint 16 (5-July - 25-July).

The Sprint was focused on the migration to Zuul v3.  For a list of the
completed items for the sprint please refer to the Epic card [1] and the
task cards [2].

The Ruck & Rover roles this sprint were filled by Chandan Kumar and Sagi
Shnaidman.  Thanks to them for their efforts!

Detailed notes concerning bugs filed and issues worked on are available in
the etherpad [3]

Thanks,

Matt

[1] https://trello.com/c/vyWXcKOB/143-ci-squad-sprint-16-goals
[2]
https://trello.com/b/BjcIIp0f/tripleo-and-rdo-ci-archive?menu=filter=label:SPRINT%2016%20CI
[3] https://review.rdoproject.org/etherpad/p/ruckrover-sprint16
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] overcloud deployment fails with during keystone configuration

[Samuel Monderer]

Hi,

My overcloud deployment fails with the following error

2018-07-31 14:20:23Z
[overcloud.AllNodesDeploySteps.ControllerDeployment_Step3]: CREATE_FAILED
Resource CREATE failed: Error: resources[0]: Deployment to server failed:
deploy_status_code : Deployment exited with non-zero status code: 2
2018-07-31 14:20:24Z
[overcloud.AllNodesDeploySteps.ControllerDeployment_Step3]: CREATE_FAILED
Error: resources.ControllerDeployment_Step3.resources[0]: Deployment to
server failed: deploy_status_code: Deployment exited with non-zero status
code: 2
2018-07-31 14:20:24Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED
Resource CREATE failed: Error:
resources.ControllerDeployment_Step3.resources[0]: Deployment to server
failed: deploy_status_code: Deployment exited with non-zero status code: 2
2018-07-31 14:20:25Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED  Error:
resources.AllNodesDeploySteps.resources.ControllerDeployment_Step3.resources[0]:
Deployment to server failed: deploy_status_code: Deployment exited with
non-zero status code: 2
2018-07-31 14:20:25Z [overcloud]: CREATE_FAILED  Resource CREATE failed:
Error:
resources.AllNodesDeploySteps.resources.ControllerDeployment_Step3.resources[0]:
Deployment to server failed: deploy_status_code: Deployment exited with
non-zero status code: 2

 Stack overcloud CREATE_FAILED

overcloud.AllNodesDeploySteps.ControllerDeployment_Step3.0:
  resource_type: OS::Heat::StructuredDeployment
  physical_resource_id: 69fd1d02-7e20-4d91-a7b4-552cdf4e42f2
  status: CREATE_FAILED
  status_reason: |
Error: resources[0]: Deployment to server failed: deploy_status_code :
Deployment exited with non-zero status code: 2
  deploy_stdout: |
...
"+ exit 1",
"2018-07-31 17:20:19,292 INFO: 74435 -- Finished processing
puppet configs for keystone_init_tasks",
"2018-07-31 17:20:19,293 ERROR: 74434 -- ERROR configuring
keystone_init_tasks"
]
}
to retry, use: --limit
@/var/lib/heat-config/heat-config-ansible/2fa9a52f-7e15-43fc-b67e-1ae358468790_playbook.retry

PLAY RECAP
*
localhost  : ok=9changed=2unreachable=0
failed=1

(truncated, view all with --long)
  deploy_stderr: |

Not cleaning temporary directory /tmp/tripleoclient-D67O5V
Not cleaning temporary directory /tmp/tripleoclient-D67O5V
Heat Stack create failed.
Heat Stack create failed.
(undercloud) [stack@staging-director ~]$


In the director keystone log I get the following

2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi
[req-22ee40c6-6daa-428d-aa39-06a96a4d5d3d - - - - -]
(pymysql.err.ProgrammingError) (1146, u"Table 'keystone.project' doesn't
exist") [SQL: u'SELECT project.id
 AS project_id, project.name AS project_name, project.domain_id AS
project_domain_id, project.description AS project_description,
project.enabled AS project_enabled, project.extra AS project_extra,
project.parent_
id AS project_parent_id, project.is_domain AS project_is_domain \nFROM
project \nWHERE project.is_domain = true'] (Background on this error at:
http://sqlalche.me/e/f405): ProgrammingError: (pymysql.err.Programmin
gError) (1146, u"Table 'keystone.project' doesn't exist") [SQL: u'SELECT
project.id AS project_id, project.name AS project_name, project.domain_id
AS project_domain_id, project.description AS project_description,
project.enabled AS project_enabled, project.extra AS project_extra,
project.parent_id AS project_parent_id, project.is_domain AS
project_is_domain \nFROM project \nWHERE project.is_domain = true']
(Background on t
his error at: http://sqlalche.me/e/f405)
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi Traceback (most
recent call last):
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi   File
"/usr/lib/python2.7/site-packages/keystone/common/wsgi.py", line 226, in
__call__
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi result =
method(req, **params)
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi   File
"/usr/lib/python2.7/site-packages/keystone/common/controller.py", line 126,
in wrapper
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi return f(self,
request, filters, **kwargs)
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi   File
"/usr/lib/python2.7/site-packages/keystone/resource/controllers.py", line
54, in list_domains
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi refs =
PROVIDERS.resource_api.list_domains(hints=hints)
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi   File
"/usr/lib/python2.7/site-packages/keystone/common/manager.py", line 116, in
wrapped
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi __ret_val =
__f(*args, **kwargs)
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi   File
"/usr/lib/python2.7/site-packages/keystone/common/manager.py", line 68, in
wrapper
2018-07-31 17:17:25.592 32 ERROR keystone.common.wsgi return f(self,
*args, **kwargs)
2018-07-31 17:17:25.592 32 

[openstack-dev] [ptg] Post-lunch presentations in Denver

[Thierry Carrez]

Hi everyone,

At the last PTG in Dublin we introduced the concept of post-lunch 
presentations -- a 30-min segment during the second half of the lunch 
break during which we communicate and do Q on topics that are 
generally interesting to a crowd of contributors.


In Dublin, you may remember we did a "Welcome to the PTG" session on 
Monday, a Zuul v3 session on Tuesday and an OpenStackSDK session on 
Wednesday. Due to the snow storm, we had to cancel the release 
management presentation on Thursday and the lightning talks scheduled 
for Friday.


We do not *have to* fill every available slot -- but if we find content 
that is generally useful and can be consumed while people start their 
digestion process, then we can use one of those slots for that. 
Interesting topics include development tricks, code review etiquette, 
new libraries features you should adopt, upgrade horror stories... The 
content should generally fit within 20 min to leave room for Q


If you have ideas, please fill:

https://etherpad.openstack.org/p/PTG4-postlunch

In a few weeks the TC will review suggestions there and pick things that 
fit the bill.


Cheers,

--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] [FFE] Teach ironic about ppc64le boot requirements

[Jim Rollenhagen]

On Tue, Jul 31, 2018 at 9:51 AM, Julia Kreger 
wrote:

> Given that the ironic-lib version in question is already in
> upper-constraints, I think it may be fine. Realistically we do want
> people to be running the latest version of ironic-lib when deploying
> anyway. That being said, I'm +1 for this, however we need a second
> ironic-core to be willing to review this over the next few days.
>

Happy to help, I'm +2 on the IPA patch. Ironic patch just needs some unit
tests.

// jim


> On Mon, Jul 30, 2018 at 1:55 PM, Michael Turek
>  wrote:
> > I would like to request a FFE for this RFE
> > https://storyboard.openstack.org/#!/story/1749057
> >
> > The implementation should be complete and is currently passing CI, but
> does
> > need more reviews. I'd also like to test this locally ideally.
> >
> > pros
> > ---
> > - Improves ppc64le support
> >
> > cons
> > ---
> > - Bumps ironic-lib version for both IPA and Ironic
> >
> > risk
> > ---
> > - There are other deployment methods for ppc64le, including wholedisk and
> > netboot. However, this feature is desired to improve parity between x86
> and
> > ppc64le for tripleo. The feature should not affect any current working
> > deployment methods, but please review closely.
> >
> > Please let me know if you'd like more detail on this or have any
> questions!
> > Thanks!
> >
> > -Mike  Turek
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [kuryr] SRIOV and Multi-Vif meeting

[Daniel Mellado]

Hi everyone,

As discussed in last meeting, we'll get to use next week's one to go
over the multi-vif blueprint [1] and some discussions about its
implementation and remaining patches.

Feel free to join us at [2]

Best!

Daniel

[1] https://blueprints.launchpad.net/kuryr-kubernetes/+spec/multi-vif-pods
[2] https://bluejeans.com/4944951842


0xC905561547B09777.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ironic] [FFE] Teach ironic about ppc64le boot requirements

[Julia Kreger]

Given that the ironic-lib version in question is already in
upper-constraints, I think it may be fine. Realistically we do want
people to be running the latest version of ironic-lib when deploying
anyway. That being said, I'm +1 for this, however we need a second
ironic-core to be willing to review this over the next few days.

On Mon, Jul 30, 2018 at 1:55 PM, Michael Turek
 wrote:
> I would like to request a FFE for this RFE
> https://storyboard.openstack.org/#!/story/1749057
>
> The implementation should be complete and is currently passing CI, but does
> need more reviews. I'd also like to test this locally ideally.
>
> pros
> ---
> - Improves ppc64le support
>
> cons
> ---
> - Bumps ironic-lib version for both IPA and Ironic
>
> risk
> ---
> - There are other deployment methods for ppc64le, including wholedisk and
> netboot. However, this feature is desired to improve parity between x86 and
> ppc64le for tripleo. The feature should not affect any current working
> deployment methods, but please review closely.
>
> Please let me know if you'd like more detail on this or have any questions!
> Thanks!
>
> -Mike  Turek
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo][ci][metrics] Stucked in the middle of work because of RDO CI

[Sagi Shnaidman]

Hi, Martin

I see master OVB jobs are passing now [1], please recheck.

[1] http://cistatus.tripleo.org/

On Tue, Jul 31, 2018 at 12:24 PM, Martin Magr  wrote:

> Greetings guys,
>
>   it is pretty obvious that RDO CI jobs in TripleO projects are broken
> [0]. Once Zuul CI jobs will pass would it be possible to have AMQP/collectd
> patches ([1],[2],[3]) merged please even though the negative result of RDO
> CI jobs? Half of the patches for this feature is merged and the other half
> is stucked in this situation, were nobody reviews these patches, because
> there is red -1. Those patches passed Zuul jobs several times already and
> were manually tested too.
>
> Thanks in advance for consideration of this situation,
> Martin
>
> [0] https://trello.com/c/hkvfxAdX/667-cixtripleoci-rdo-software-
> factory-3rd-party-jobs-failing-due-to-instance-nodefailure
> [1] https://review.openstack.org/#/c/578749
> [2] https://review.openstack.org/#/c/576057/
> [3] https://review.openstack.org/#/c/572312/
>
> --
> Martin Mágr
> Senior Software Engineer
> Red Hat Czech
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition

[Pradeep Kilambi]

On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau  wrote:

> On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote:
> >
> >
> > On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz 
> > wrote:
> > > On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr 
> > > wrote:
> > > >
> > > >
> > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi  > > m> wrote:
> > > >>
> > > >> Your fellow reporter took a break from writing, but is now back
> > > on his
> > > >> pen.
> > > >>
> > > >> Welcome to the twenty-fifth edition of a weekly update in TripleO
> > > world!
> > > >> The goal is to provide a short reading (less than 5 minutes) to
> > > learn
> > > >> what's new this week.
> > > >> Any contributions and feedback are welcome.
> > > >> Link to the previous version:
> > > >> http://lists.openstack.org/pipermail/openstack-dev/2018-June/1314
> > > 26.html
> > > >>
> > > >> +-+
> > > >> | General announcements |
> > > >> +-+
> > > >>
> > > >> +--> Rocky Milestone 3 is next week. After, any feature code will
> > > require
> > > >> Feature Freeze Exception (FFE), asked on the mailing-list. We'll
> > > enter a
> > > >> bug-fix only and stabilization period, until we can push the
> > > first stable
> > > >> version of Rocky.
> > > >
> > > >
> > > > Hey guys,
> > > >
> > > >   I would like to ask for FFE for backup and restore, where we
> > > ended up
> > > > deciding where is the best place for the code base for this
> > > project (please
> > > > see [1] for details). We believe that B support for overcloud
> > > control
> > > > plane will be good addition to a rocky release, but we started
> > > with this
> > > > initiative quite late indeed. The final result should the support
> > > in
> > > > openstack client, where "openstack overcloud (backup|restore)"
> > > would work as
> > > > a charm. Thanks in advance for considering this feature.
> > > >
> > >
> > > Was there a blueprint/spec for this effort?  Additionally do we have
> > > a
> > > list of the outstanding work required for this? If it's just these
> > > two
> > > playbooks, it might be ok for an FFE. But if there's additional
> > > tripleoclient related changes, I wouldn't necessarily feel
> > > comfortable
> > > with these unless we have a complete list of work.  Just as a side
> > > note, I'm not sure putting these in tripleo-common is going to be
> > > the
> > > ideal place for this.
>
> Was it this review? https://review.openstack.org/#/c/582453/
>
> For Stein we'll have an ansible role[0] and playbook repo[1] where these
> types of tasks should live.
>
> [0] https://github.com/openstack/ansible-role-openstack-operations
> [1] https://review.openstack.org/#/c/583415/


Thanks Jill! The issue is, we want to be able to backport this to Queens
once merged. With the new repos you're mentioning would this be possible?
If no, then this wont work for us unfortunately.




>
>
> >
> > Thanks Alex. For Rocky, if we can ship the playbooks with relevant
> > docs we should be good. We will integrated with client in Stein
> > release with restore logic included. Regarding putting tripleo-common,
> > we're open to suggestions. I think Dan just submitted the review so we
> > can get some eyes on the playbooks. Where do you suggest is better
> > place for these instead?
> >
> > >
> > > Thanks,
> > > -Alex
> > >
> > > > Regards,
> > > > Martin
> > > >
> > > > [1] https://review.openstack.org/#/c/582453/
> > > >
> > > >>
> > > >> +--> Next PTG will be in Denver, please propose topics:
> > > >> https://etherpad.openstack.org/p/tripleoci-ptg-stein
> > > >> +--> Multiple squads are currently brainstorming a framework to
> > > provide
> > > >> validations pre/post upgrades - stay in touch!
> > > >>
> > > >> +--+
> > > >> | Continuous Integration |
> > > >> +--+
> > > >>
> > > >> +--> Sprint theme: migration to Zuul v3 (More on
> > > >> https://trello.com/c/vyWXcKOB/841-sprint-16-goals)
> > > >> +--> Sagi is the rover and Chandan is the ruck. Please tell them
> > > any CI
> > > >> issue.
> > > >> +--> Promotion on master is 4 days, 0 days on Queens and Pike and
> > > 1 day on
> > > >> Ocata.
> > > >> +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meet
> > > ing
> > > >>
> > > >> +-+
> > > >> | Upgrades |
> > > >> +-+
> > > >>
> > > >> +--> Good progress on major upgrades workflow, need reviews!
> > > >> +--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad
> > > -status
> > > >>
> > > >> +---+
> > > >> | Containers |
> > > >> +---+
> > > >>
> > > >> +--> We switched python-tripleoclient to deploy containerized
> > > undercloud
> > > >> by default!
> > > >> +--> Image prepare via workflow is still work in progress.
> > > >> +--> More:
> > > >> https://etherpad.openstack.org/p/tripleo-containers-squad-status
> > > >>
> > > >> +--+
> > > >> | config-download |
> > > >> 

[openstack-dev] [tc] [all] TC Report 18-31

[Chris Dent]

HTML: https://anticdent.org/tc-report-18-31.html

Welcome to this week's TC Report. Again a slow week. A small number
of highlights to report.

[Last
Thursday](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-26.log.html#t2018-07-26T15:03:57)
there was some discussion of the health of the Trove project and how
one of the issues that may have limited their success were struggles
to achieve a [sane security
model](https://review.openstack.org/#/c/438134/). That and other
struggles led to lots of downstream forking and variance which
complicates presenting a useful tool.

[On
Monday](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-30.log.html)
there was talk about the nature of the PTL role and whether it needs
to change somewhat to help break down the silos between projects and
curtail burnout. This was initially prompted by some concern that
PTL nominations were lagging. As usual, there were many last minute
nominations.

The volume of work that continues to consolidate on individuals is
concerning. We must figure out how to let some things drop. This is
an area where the TC must demonstrate some leadership, but it's
very unclear at this point how to change things.

Based on [this
message](http://lists.openstack.org/pipermail/openstack-dev/2018-July/132651.html)
from Thierry on a slightly longer Stein cycle, the idea that the
first PTG in 2019 is going to be co-located with the Summit is, if
not definite, near as. There's more on that in the second paragraph
of the [Vancouver Summit Joint Leadership Meeting
Update](http://lists.openstack.org/pipermail/foundation/2018-June/002598.html).

If you have issues that you would like the TC to discuss—or to discuss
with the TC—at the [PTG coming in
September](https://www.openstack.org/ptg), please add to the
[planning etherpad](https://etherpad.openstack.org/p/tc-stein-ptg).

--
Chris Dent   ٩◔̯◔۶   https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Blazar] PTL non candidacy

[Masahito MUROI]

Hi Blazar folks,

I just want to announce that I'm not running the PTL for the Stein 
cycle. I have been running this position from the Ocata cycle when we 
revived the project.  We've been done lots of successful activities in 
the last 4 cycles.


I think it's time to change the position to someone else to move the 
Blazar project further forward. I'll still be around the project and try 
to make the Blazar project great.


Thanks for lots of your supports.

best regards,
Masahito


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] [nova] [os-vif] [vif_plug_ovs] Support for OVS DB tcp socket communication.

[pranab boruah]

>Hello Pranab,

>Makes sense for me. This is really related to the OVS plugin that we
>are maintaining. I guess you will have to add a new config option for
>it as we have with 'network_device_mtu' and 'ovs_vsctl_timeout'.

>Don't hesitate to add me as reviewer when patch is ready.

Thanks Sahid.
Here is the proposed patch: https://review.openstack.org/#/c/587378/

Please review.

Regards,
Pranab
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [puppet] [PTL] [Election] PTL candidacy for the Stein cycle

[Tobias Urdin]

Hello Stackers,

I'm submitting myself as PTL candidate for the Puppet OpenStack project. [0]

I've been active in the OpenStack community since late 2014 early 2015
and have had a lot of focus on the
Puppet OpenStack project since about 2016. I've been a core reviewer for
about five months now and it's
been really cool to be able to give something back to the community.

We have had a lot of progress this cycle.

* Remove a lot of deprecate parameters
* Improved testing of Puppet 5
* Added Debian 9 support (Python 3 only)
* Added Ubuntu 18.04 Bionic support
* Fixed some bugs
* Moved to more usage of the shared openstacklib resources
* Added neutron-dynamic-routing support
* Added horizon dashboard installation support
* Changed keystone to use port 5000 and deprecated usage of port 35357
(still deploys both)

I could ramble up a lot more in that list but I really think we've done
a good job but we still have some major things
moving forward that we'll have to work on. Here is some major things I
think we'll need to work on or discuss.

* Python 3 will be a big one, I know people are working on Fedora for
testing here, but we also have Debian9 here
   which is python3-only so thanks to Thomas (zigo) we have somebody
that has paved the way here.

* Puppet 5 data types for parameters and removing validate_* functions
is a big one which we also have an open blueprint
   and PoC for but will require a lot of interaction with the TripleO
team. [1] [2]

* CI stability and maintenance will be a reoccurring thing we'll need to
focus on.

* Puppet providers are usually slow due to CLI utilies, we need to work
together to improve the performance of
   the CLI tooling or consider the move to API calls, this has been up
before but there hasn't been anybody there
   that has sponsored such work.

I want to really thank all of you for your huge amounts of work, all
across the OpenStack board and the Puppet OpenStack team.
Thank you for considering me.

Best regards
Tobias (tobasco @ IRC)

[0] https://review.openstack.org/#/c/587372/
[1] https://review.openstack.org/#/c/568929/
[2] https://review.openstack.org/#/c/569566/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [release] Stein: a slightly longer release cycle

[Thierry Carrez]

Hi everyone,

As we approach the final stages of the Rocky release, it's time to start 
planning Stein work. The Stein release schedule is available here:


https://releases.openstack.org/stein/schedule.html

As discussed[1] during the Vancouver Board+TC+UC meeting, the Foundation 
will be holding the first PTG in 2019 immediately after the Denver 
summit in April, 2019 (in the same venue). Since we want to place the 
PTG close to the cycle start, this results in a slightly-longer release 
cycle, with the Stein release set to April 10, 2019.


That makes Stein 4 weeks longer than Havana or Kilo, our longest cycles 
so far. That said, with the Berlin summit, Thanksgiving, the long 
end-of-year holiday break, and Chinese new year, there will be a lot of 
work time lost during this cycle (like during all of our 
Northern-hemisphere winter cycles), so the release management team 
doesn't really expect Stein to feel that much longer, or work planning 
to be significantly impacted.


Cheers,

[1] http://lists.openstack.org/pipermail/foundation/2018-June/002598.html

--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

[Frank Kloeker]

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with 
XML-Parsing of the term AT Don't know how to escape this. Maybe you 
will see the warning during import too.


kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper) apologizes
on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker  wrote:


Hi Jimmy,

from the GUI I'll get this link:


https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

[1]

paper version  are only in container whitepaper:



https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata API:


https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

[3]

As a result, we can't pull the po files.  Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:


https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF.  Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations.  It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have.  As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors.  I indicated that we
would also be moving the Edge paper to HTML so that we could prevent
that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in the
same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation.  At the moment, it's just not usable for
the reasons mentioned above.
On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML
based translation is more difficult.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and publish
translated whitepapers locally:

- How to build translated container whitepaper using original
Silverstripe-based repository?
https://docs.openstack.org/i18n/latest/tools.html [5] describes
well how to build translated artifacts for RST-based OpenStack
repositories
but I could not find the way how to build translated container
whitepaper with translated resources on Zanata.
This is a little tricky.  It's possible to set up a local version
of the OpenStack website


(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md

[6]).  However, we have to manually ingest the po files as they are
completed and then push them out to production, so that wouldn't do
much to help with your local build.  I'm open to suggestions on how
we can make this process easier for the i18n team.

Thank you,
Jimmy

With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:
Frank,

I'm sorry to hear about the displeasure around the Edge paper.  As
mentioned in a prior thread, the RST format that Akihiro worked did
not work with the  Zanata process that we have been 

[openstack-dev] [tripleo][ci][metrics] Stucked in the middle of work because of RDO CI

[Martin Magr]

Greetings guys,

  it is pretty obvious that RDO CI jobs in TripleO projects are broken [0].
Once Zuul CI jobs will pass would it be possible to have AMQP/collectd
patches ([1],[2],[3]) merged please even though the negative result of RDO
CI jobs? Half of the patches for this feature is merged and the other half
is stucked in this situation, were nobody reviews these patches, because
there is red -1. Those patches passed Zuul jobs several times already and
were manually tested too.

Thanks in advance for consideration of this situation,
Martin

[0]
https://trello.com/c/hkvfxAdX/667-cixtripleoci-rdo-software-factory-3rd-party-jobs-failing-due-to-instance-nodefailure
[1] https://review.openstack.org/#/c/578749
[2] https://review.openstack.org/#/c/576057/
[3] https://review.openstack.org/#/c/572312/

-- 
Martin Mágr
Senior Software Engineer
Red Hat Czech
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron] Port mirroring for SR-IOV VF to VF mirroring

[Zhao, Forrest]

Hi Miguel,

In your mail "PTL candidacy for the Stein cycle", it mentioned that "port 
mirroring for SR-IOV VF to VF mirroring" is within Stein goal.

Could you tell where is the place to discuss the design for this feature? 
Mailing list, IRC channel, weekly meeting or others?

I was involved in its spec review at https://review.openstack.org/#/c/574477/; 
but it has not been updated for a while.

Thanks,
Forrest
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][Election] Last days for PTL nomination

[Thierry Carrez]

Luke Hinds wrote:
On Mon, 30 Jul 2018, 21:19 Jeremy Stanley, > wrote:


On 2018-07-30 15:23:57 +0700 (+0700), Luke Hinds wrote:
 > Security is a SIG and no longer a project (changed as of rocky
cycle).

Technically it's still both at the moment, which is why I proposed
https://review.openstack.org/586896 yesterday (tried to give you a
heads up in IRC about that as well). A +1 from the current PTL of
record on that change would probably be a good idea.


I am on PTO for the next two weeks,  is +1 in this email ok? I don't 
have my launchpad credentials with me to SSO login to Gerrit.


Sure, I'll reference this email there. Thanks Luke, have a great PTO!

--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] deployement fails

[Samuel Monderer]

Removing it just made it longer to time out

On Mon, Jul 30, 2018 at 7:51 PM, Remo Mattei  wrote:

> Take it off and check :)
>
>
>
> On Jul 30, 2018, at 09:46, Samuel Monderer 
> wrote:
>
> Yes
> I tried eith 60 and 120
>
> On Mon, Jul 30, 2018, 19:42 Remo Mattei  wrote:
>
>> Do you have a timeout set?
>>
>> > On Jul 30, 2018, at 07:48, Samuel Monderer <
>> smonde...@vasonanetworks.com> wrote:
>> >
>> > Hi,
>> >
>> > I'm trying to deploy a small environment with one controller and one
>> compute but i get a timeout with no specific information in the logs
>> >
>> > 2018-07-30 13:19:41Z [overcloud.Controller.0.ControllerConfig]:
>> CREATE_IN_PROGRESS  state changed
>> > 2018-07-30 13:19:41Z [overcloud.Controller.0.ControllerConfig]:
>> CREATE_COMPLETE  state changed
>> > 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3]: CREATE_FAILED  CREATE
>> aborted (Task create from ResourceGroup "ComputeGammaV3" Stack "overcloud"
>> [690ee33c-8194-4713-a44f-9c8dcf88359f] Timed out)
>> > 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3]: UPDATE_FAILED  Stack
>> UPDATE cancelled
>> > 2018-07-30 14:04:51Z [overcloud]: CREATE_FAILED  Timed out
>> > 2018-07-30 14:04:51Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED  Stack
>> CREATE cancelled
>> > 2018-07-30 14:04:51Z [overcloud.Controller]: CREATE_FAILED  CREATE
>> aborted (Task create from ResourceGroup "Controller" Stack "overcloud"
>> [690ee33c-8194-4713-a44f-9c8dcf88359f] Timed out)
>> > 2018-07-30 14:04:51Z [overcloud]: CREATE_FAILED  Timed out
>> > 2018-07-30 14:04:51Z [overcloud.Controller]: UPDATE_FAILED  Stack
>> UPDATE cancelled
>> > 2018-07-30 14:04:51Z [overcloud.Controller.0]: CREATE_FAILED  Stack
>> CREATE cancelled
>> > 2018-07-30 14:04:52Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED
>> resources[0]: Stack CREATE cancelled
>> >
>> >  Stack overcloud CREATE_FAILED
>> >
>> > overcloud.ComputeGammaV3.0:
>> >   resource_type: OS::TripleO::ComputeGammaV3
>> >   physical_resource_id: 5755d746-7cbf-4f3d-a9e1-d94a713705a7
>> >   status: CREATE_FAILED
>> >   status_reason: |
>> > resources[0]: Stack CREATE cancelled
>> > overcloud.Controller.0:
>> >   resource_type: OS::TripleO::Controller
>> >   physical_resource_id: 4bcf84c1-1d54-45ee-9f81-b6dda780cbd7
>> >   status: CREATE_FAILED
>> >   status_reason: |
>> > resources[0]: Stack CREATE cancelled
>> > Not cleaning temporary directory /tmp/tripleoclient-vxGzKo
>> > Not cleaning temporary directory /tmp/tripleoclient-vxGzKo
>> > Heat Stack create failed.
>> > Heat Stack create failed.
>> > (undercloud) [stack@staging-director ~]$
>> >
>> > It seems that it wasn't able to configure the OVS bridges
>> >
>> > (undercloud) [stack@staging-director ~]$ openstack software deployment
>> show 4b4fc54f-7912-40e2-8ad4-79f6179fe701
>> > +---+---
>> -+
>> > | Field | Value
>>   |
>> > +---+---
>> -+
>> > | id| 4b4fc54f-7912-40e2-8ad4-79f6179fe701
>>|
>> > | server_id | 0accb7a3-4869-4497-8f3b-5a3d99f3926b
>>|
>> > | config_id | 2641b4dd-afc7-4bf5-a2e2-481c207e4b7f
>>|
>> > | creation_time | 2018-07-30T13:19:44Z
>>  |
>> > | updated_time  |
>>   |
>> > | status| IN_PROGRESS
>>   |
>> > | status_reason | Deploy data available
>>   |
>> > | input_values  | {u'interface_name': u'nic1', u'bridge_name':
>> u'br-ex'} |
>> > | action| CREATE
>>  |
>> > +---+---
>> -+
>> > (undercloud) [stack@staging-director ~]$ openstack software deployment
>> show a297e8ae-f4c9-41b0-938f-c51f9fe23843
>> > +---+---
>> -+
>> > | Field | Value
>>   |
>> > +---+---
>> -+
>> > | id| a297e8ae-f4c9-41b0-938f-c51f9fe23843
>>|
>> > | server_id | 145167da-9b96-4eee-bfe9-399b854c1e84
>>|
>> > | config_id | d1baf0a5-de9b-48f2-b486-9f5d97f7e94f
>>|
>> > | creation_time | 2018-07-30T13:17:29Z
>>  |
>> > | updated_time  |
>>   |
>> > | status| IN_PROGRESS
>>   |
>> > | status_reason | Deploy data available
>>   |
>> > | input_values  | {u'interface_name': u'nic1', u'bridge_name':
>> u'br-ex'} |
>> > | action| CREATE
>>  |
>> > +---+---
>> -+
>> > (undercloud) [stack@staging-director ~]$
>> >
>> > Regards,
>> > Samuel
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> 
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> 
>> __