Re: [openstack-dev] [tripleo] containers-multinode is broken, what's our plan

[Wesley Hayutin]

On Tue, Jan 2, 2018 at 11:05 PM, Emilien Macchi  wrote:

> Mistral broke us with https://review.openstack.org/#/c/506185/ and we
> had a promotion yesterday so now our CI deploy Mistral with this
> patch.
> It breaks some Mistral actions, including the ones needed by
> config-download (in featureset010).
>
> Steve has a fix: https://review.openstack.org/#/c/530781 but there is
> no core review yet so we decided to proceed this way:
>
> 1) Carry Steve's patch in Mistral distgit:
> https://review.rdoproject.org/r/#/c/11140/ - DONE
> 2) Remove featureset010 from promotion requirements - DONE
> 3) Once we have a promotion, we'll be able to land
> https://review.openstack.org/#/c/530783/ - IN PROGRESS
> 4) Once https://review.openstack.org/#/c/530783/ is landed, and the
> upstream patch is landed, revert
> https://review.rdoproject.org/r/#/c/11140/ (otherwise RDO will become
> inconsistent) and failing to build on master)
> 5) Re-add featureset010 in promotion requirements (revert
> https://review.rdoproject.org/r/#/c/11142) so we'll catch the issue
> next time.
>
> Thanks,
> --
> Emilien Macchi
>

Thanks for all your hardwork and direction here.  You kept the lights on
while we were all out.
We'll be monitoring the zuul queue for any errors, thanks!

The TripleO-CI team is also working on the tools we'll need moving forward
to help bring the jobs that were moved to non-voting back to voting.
If anyone is interested or has suggestions our sprint work is spec'd out
here [1].  We have a planning meeting tomorrow to work through the details.
We'll also be taking on any unfinished work from the end of last year.

Thanks

[1]
https://trello.com/b/U1ITy0cu/tripleo-ci-squad?menu=filter&filter=label:Sprint%206



>
> __
> 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] about backup instance booted from volume

[Matt Riedemann]

On 12/27/2017 9:52 PM, Jaze Lee wrote:

2017-12-28 10:56 GMT+08:00 Jaze Lee :

Hello,
This is the spec about backup a instance booted from volume, anyone
who is interested on booted from volume can help to review this. Any
suggestion is welcome.

The spec is here.
https://review.openstack.org/#/c/530214/2


Thanks a lot...





--
谦谦君子






I dug up this old change from Fei Long Wang about the same thing:

https://review.openstack.org/#/c/164494/

As I mentioned in the bug and the spec, you should reference, or we can 
restore, that change and you can take ownership of it if Fei Long 
doesn't plan on working on it.


It will require a new microversion which should be called out in the 
spec review.


This is something to discuss for the Rocky release at this point since 
we're past spec freeze for Queens.


--

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] [nova] Working toward Queens feature freeze and RC1

[Matt Riedemann]

Now that most people are getting back into work after the holiday break, 
I thought I'd try and recap some of where we're at in the release, and 
what to look forward to in the next few weeks.


Schedule


https://wiki.openstack.org/wiki/Nova/Queens_Release_Schedule

We have two big dates coming up:

1. Thursday, Jan 18 - non-client release freeze: This is the final 
release date for libraries like os-vif and os-traits. I'll be on 
vacation the week of the 15th so I'll actually be pushing for these 
releases on the 11th. *Let me know if you have work that depends on an 
os-vif or os-traits release so I can be sure it's in.*


2. Thursday, Jan 25 - queens-3 milestone, feature freeze and final 
novaclient release: We'll only have two weeks until RC1 (Feb 8) so I 
don't expect much in the way of feature freeze exceptions since we need 
that time to focus on stabilizing everything that made it in by the 
feature freeze, plus docs and upgrade work to prepare for Rocky.


I've started building a list of things that need to be done by the time 
we get to RC1:


https://etherpad.openstack.org/p/nova-queens-release-candidate-todo

Blueprints
--

Looking at the priorities for Queens:

https://specs.openstack.org/openstack/nova-specs/priorities/queens-priorities.html

* Alternate hosts is nearly done, but hit a snag today: 
https://bugs.launchpad.net/nova/+bug/1741125


* Nested resource providers: I'm going to need someone closer to this 
work like Jay or Eric to provide an update on where things are at in the 
series of changes and what absolutely needs to get done. I have 
personally found it hard to track what the main focus items are for the 
nested resource providers / traits / granular resource provider request 
changes so I need someone to summarize and lay out the review goals for 
the next two weeks.


* Volume multiattach support: There are some lower-hanging fruit changes 
up for review at the bottom of the series. Steve Noyes and I are working 
on getting the integration testing in place for this [1]. We're going to 
need to figure out what to do, if anything, about checking the new 
microversion in the compute API for multiattach and failing in the API 
vs failing in the compute. See my thoughts in the API patch [2]. There 
are also changes on the Cinder side that need to happen for multiattach 
to work (in the volume drivers, volume type and policy rules).


The rest of the blueprints are tracked here:

https://etherpad.openstack.org/p/nova-queens-blueprint-status

I've been trying to keep the stuff that has had a decent amount of 
review and progress sorted toward the top of the list since I'd like to 
focus on what can still get completed in Queens versus spreading the 
review load across everything that's still open.


Reminders
-

* Our list of untriaged bugs is growing, we're up to 53. [3]

* As mentioned earlier, I'm going to be on vacation the week of the 
15th. I made the mistake of taking my laptop with me to Mexico last year 
around the Ocata FF/RC1 and I don't plan on doing that this time around. 
So if you need something from me, please be sure to bring it up before 
Friday the 12th at the latest. Once I'm back I'll be focusing on 
wrapping up for feature freeze and then RC1 and PTG planning.


[1] https://review.openstack.org/#/c/266633/
[2] https://review.openstack.org/#/c/271047/37
[3] http://tiny.cc/psmwpy

--

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] [keystone] [ptg] Rocky PTG planning

[Lance Bragstad]

Hey all,

It's about that time to start our pre-PTG planning activities. I've
started an etherpad and bootstrapped it with some basic content [0].
Please take the opportunity to add topics to the schedule. It doesn't
matter if it is cross-project or keystone specific. The sooner we get
ideas flowing the easier it will be to coordinate cross-project tracks
with other groups. We'll organize the content into a schedule after a
couple week. Let me know if you have any questions.

Thanks,

Lance

[0] https://etherpad.openstack.org/p/keystone-rocky-ptg




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] [Zun] Containers in privileged mode

[Hongbin Lu]

On Wed, Jan 3, 2018 at 10:41 AM, João Paulo Sá da Silva <
joao-sa-si...@alticelabs.com> wrote:

> Hello,
>
>
>
> I created the BP: https://blueprints.launchpad.
> net/zun/+spec/add-capacities-to-containers .
>
Thanks for creating the BP.


>
>
> About the clear containers, I’m not quite sure how using them solves my
> capabilities situation. Can you elaborate on that?
>
What I was trying to say is that Zun offers choice of container runtime:
runc or clear container. I am not sure how clear container deal with
capabilities and privilege escalation. I will leave this question to others.


>
>
> Will zun ever be able to launch LXD containers?
>
Not for now. Only Docker is supported.


>
>
> Kind regards,
>
> João
>
> __
> 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] [designate] need help with managed resource tenant ID

[Graham Hayes]

On 03/01/18 17:50, Ritesh Anand wrote:
> Hi Stackers,
> 
> Happy new year!!
> 
> I am working around Designate service and have been seeing this warning
> in designate-central.log:
> 2017-12-12 06:25:47.022 31171 WARNING designate.central.service [-]
> Managed Resource Tenant ID is not properly configured
> 
> Looks like the config options:
> [service:central]/managed_resource_tenant_id = "" and
> managed_resource_email = ""
> are being used to hold resources internally created by Designate (namely
> PTR records for FIPs, etc.).
> 
> I need your help in finding a good value for these configurations to
> support in our deployments.
> What are you using?

We have previously used the project ID for the designate service
project. As long as it is an actual unique project, it is fine.

The email is used in the SOA record for reverse DNS zones, and as a
temporary email while we import secondary zones. This means that it
should be a per customer thing, and usually would be the email for the
team running the DNS service.

Thanks,

Graham

> Any suggestions welcome!
> 
> Thanks,
> Ritesh
> 
> 
> __
> 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
> 



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

[openstack-dev] [designate] need help with managed resource tenant ID

[Ritesh Anand]

Hi Stackers,

Happy new year!!

I am working around Designate service and have been seeing this warning in 
designate-central.log:
2017-12-12 06:25:47.022 31171 WARNING designate.central.service [-] Managed 
Resource Tenant ID is not properly configured

Looks like the config options: [service:central]/managed_resource_tenant_id = 
"" and managed_resource_email = ""
are being used to hold resources internally created by Designate (namely PTR 
records for FIPs, etc.).

I need your help in finding a good value for these configurations to support in 
our deployments.
What are you using?

Any suggestions welcome!

Thanks,
Ritesh
__
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] [Release-job-failures][kuryr][release] Tag of openstack/kuryr-kubernetes failed

[mdulko]

On Wed, 2018-01-03 at 17:59 +0100, Andreas Jaeger wrote:
> On 2018-01-03 16:46, Doug Hellmann wrote:
> > Excerpts from zuul's message of 2018-01-03 14:46:48 +:
> > > Build failed.
> > > 
> > > - publish-openstack-releasenotes 
> > > http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/
> > >  : FAILURE in 5m 04s
> > > 
> > 
> > Based on
> > http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/ara/result/43697d56-2d99-457f-b8e8-44d6d7fcba33/
> > it looks like the issue is an incomplete list of dependencies:
> > 
> > Running Sphinx v1.6.5
> > making output directory...
> > 
> > Exception occurred:
> >   File "conf.py", line 60, in 
> > ImportError: No module named kuryr_kubernetes
> > The full traceback has been saved in /tmp/sphinx-err-iNXwM7.log, if you 
> > want to report the issue to the developers.
> > Please also report this if it was a user error, so that a better error 
> > message can be provided next time.
> > A bug report can be filed in the tracker at 
> > . Thanks!
> 
> Fix is available since End of November:
> https://review.openstack.org/#/c/523290/ but not reviewed yet ;(
> 
> Andreas

Thanks for the notice, I've informed #openstack-kuryr and will make
sure to push this through once core reviewers will be available. It
probably won't be today though.

__
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] [Release-job-failures][kuryr][release] Tag of openstack/kuryr-kubernetes failed

[Andreas Jaeger]

On 2018-01-03 16:46, Doug Hellmann wrote:
> Excerpts from zuul's message of 2018-01-03 14:46:48 +:
>> Build failed.
>>
>> - publish-openstack-releasenotes 
>> http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/
>>  : FAILURE in 5m 04s
>>
> 
> Based on
> http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/ara/result/43697d56-2d99-457f-b8e8-44d6d7fcba33/
> it looks like the issue is an incomplete list of dependencies:
> 
> Running Sphinx v1.6.5
> making output directory...
> 
> Exception occurred:
>   File "conf.py", line 60, in 
> ImportError: No module named kuryr_kubernetes
> The full traceback has been saved in /tmp/sphinx-err-iNXwM7.log, if you want 
> to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!

Fix is available since End of November:
https://review.openstack.org/#/c/523290/ but not reviewed yet ;(

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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] [Release-job-failures][kuryr][release] Tag of openstack/kuryr-kubernetes failed

[Doug Hellmann]

Excerpts from zuul's message of 2018-01-03 14:46:48 +:
> Build failed.
> 
> - publish-openstack-releasenotes 
> http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/
>  : FAILURE in 5m 04s
> 

Based on
http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/ara/result/43697d56-2d99-457f-b8e8-44d6d7fcba33/
it looks like the issue is an incomplete list of dependencies:

Running Sphinx v1.6.5
making output directory...

Exception occurred:
  File "conf.py", line 60, in 
ImportError: No module named kuryr_kubernetes
The full traceback has been saved in /tmp/sphinx-err-iNXwM7.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!

__
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] [Zun] Containers in privileged mode

[João Paulo Sá da Silva]

Hello,

I created the BP: 
https://blueprints.launchpad.net/zun/+spec/add-capacities-to-containers .

About the clear containers, I'm not quite sure how using them solves my 
capabilities situation. Can you elaborate on that?

Will zun ever be able to launch LXD containers?

Kind regards,
João
__
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] [ironic-inspector] Resigning my core-reviewer duties

[milanisko k]

Folks,

as announced already on the Ironic upstream meeting, I'm hereby resigning
my core-reviewer duties. I've changed my downstream occupation recently and
I won't be able to keep up anymore.

Thank you all, I really enjoyed collaborating with the wonderful Ironic
community!

Best regards,
milan
__
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] Ohayo! Q1 2018

[Melvin Hillsman]

https://etherpad.openstack.org/p/TYO-ops-meetup-2018


​

Hey everyone,

What do you think about the new logo! Just a friendly reminder that the Ops
Meetup for Spring 2018 is approaching March 7-8, 2018 in Tokyo and we are
looking for additional topics.

Spring 2018 will have NFV+General on day one and Enterprise+General on day
two. Add additional topics to the etherpad or +/- 1 those already proposed.

Additionally if you are attending and would like to moderate a session, add
your name to the moderator list near the bottom of the etherpad.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] Which type of traffic can be collect by Metering.

[wenran xiao]

Hey,
When I create label rule for ingress, it need a remote_ip, and it will be
source address in neutron-meter-xxx's rule, I don't konw why here is
remote_ip, It just can collect the traffic between namespce qg-xxx and
remote_ip, If I want to get one of my vm's traffic, how can I do it?
excluded others and give remote_ip 0.0.0.0/0?  Which type of traffic can be
collect by Metering?
Any suggestions is welcome.


Bests，
Wenran Xiao
__
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] [publiccloud-wg] Reminder for todays meeting

[Tobias Rydberg]

Hi all,

Time again for a meeting for the Public Cloud WG - today at 1400 UTC in 
#openstack-meeting-3


Agenda and etherpad at: https://etherpad.openstack.org/p/publiccloud-wg

See you later!

Tobias Rydberg




smime.p7s
Description: S/MIME Cryptographic 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] [tc] [all] TC Report Review

[Chris Dent]

I haven't done a TC Report for this week, but I have written a sort
of review of the many reports written last year. Find it at 
https://anticdent.org/tc-report-2017-in-review.html


Thanks and Happy New Year.

--
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

Re: [openstack-dev] Tempest plugin for Neutron Stadium projects

[Bernard Cafarelli]

That makes sense, thanks! I will add the topic to the next
networking-sfc meeting

On 2 January 2018 at 17:06, Miguel Lavalle  wrote:
> Hi Neutron community,
>
> During the last Neutron drivers meeting, we discussed whether all the
> Neutron Stadium projects should have their Tempest code in
> https://github.com/openstack/neutron-tempest-plugin/. It was decided to
> allow Stadium projects to get their tests in the consolidated plugin but it
> will not be a requirement. The assumption is that many projects might be
> stretched in resources and we don't want to create more work for them.
>
> Best regards
>
> Miguel
>
>
>
> __
> 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
>



-- 
Bernard Cafarelli

__
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] [heat]No meeting this week

[Rico Lin]

Hi all
These few weeks seems to have some amount members on vacation, let's skip
meeting this week (will hold our next meeting in next week)

Feel free to connect to me if any question or needs any help:)
Happy New Year everyone!

-- 
May The Force of OpenStack Be With You,

*Rico Lin*irc: ricolin
__
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] [qa][all] QA Office Hours on 04th Jan, 2018

[Chandan kumar]

Hello All,

a kind reminder that tomorrow at 9:00 UTC we'll start office hours for
the QA team in the #openstack-qa channel.
Please join us with any question/comment you may have related to
tempest plugin split community goal, tempest and others QA tools.

We'll triage bugs for QA projects from the past 7 days and then extend
the time frame if there is time left.

Thanks,

Chandan Kumar

__
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