Re: [openstack-dev] [ironic] Stepping down from Ironic core

2018-02-23 Thread John Villalovos 
Very sorry to see you go :( You have been a great contributor to Ironic!
And a pleasure to work with.

Best of luck for you and your future :)

John

On Fri, Feb 23, 2018 at 1:02 AM, Vasyl Saienko 
wrote:

> Hey Ironic community!
>
> Unfortunately I don't work on Ironic as much as I used to any more, so i'm
> stepping down from core reviewers.
>
> So, thanks for everything everyone, it's been great to work with you
> all for all these years!!!
>
>
> Sincerely,
> Vasyl Saienko
>
> __
> 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] 答复: [self-healing][PTG] etherpad for PTG session onself-healing

2018-02-23 Thread liu.xuefeng1 
Hi AdamSpiers,






Here is a brief summary about Senlin project


Senlin Project (Clustering service: https://wiki.openstack.org/wiki/Senlin  )

   summary: 

Deploy Clusters/nodes with profile

Profile manager, Policy manager for the cluster.Policy examples:Scaling, 
Health, Load-Balancing, Affinity,Region Placement,Zone Placemenet etc.

Cluster/Node Manage( openstack cluster --help):scale out/in, resize, recover, 
member manager, cluster/node operation. node adopt, event manager, action 
manager etc.

Create Standby/Active Cluster by move node among different clusters

Cluster supported node types:Nova server, Heat stack, NFV VDU, K8s[1][2][3] 
.etc.

Receivers:Messaging(eg. Zaqar), Webhook

Drivers:Nova, Cinder, Neutron,Glance,Octaiva etc. by Openstacksdk ...


Intergation with other project:Aodh, Zaqar, (Discussion)Vitrage


...


  


A part of Senlin's self-healing presentations in Openstack Summit:



 
https://www.openstack.org/videos/austin-2016/deploy-an-elastic-resilient-load-balanced-cluster-in-5-minutes-with-senlin
 


 
https://www.openstack.org/videos/barcelona-2016/on-building-an-auto-healing-resource-cluster-using-senlin
 


 
https://www.openstack.org/videos/boston-2017/integration-of-enterprise-monitoring-product-senlin-and-mistral-for-auto-healing
 


 ...







[1]https://v.qq.com/x/page/i05125sfonh.html


[2]https://v.qq.com/x/page/t0512vo6tw1.html


[3]https://v.qq.com/x/page/y0512ehqiiq.html







原始邮件



发件人：AdamSpiers 
收件人：OpenStack SIGs list openstack-dev 
mailing list openstack-operators mailing 
list 
日 期 ：2018年02月23日 05:31
主 题 ：[openstack-dev] [self-healing][PTG] etherpad for PTG session onself-healing


Hi all,

Yushiro kindly created an etherpad for the self-healing SIG session at
the Dublin PTG on Tuesday afternoon next week, and I've fleshed it outa bit:

https://etherpad.openstack.org/p/self-healing-ptg-rocky

Anyone with an interest in self-healing is of course very welcome to
attend (or keep an eye on it remotely!)  This SIG is still very young,
so it's a great chance for you to shape the direction it takes :-)  If
you are able to attend, please add your name, and also feel free to
add topics which you would like to see covered.

It would be particularly helpful if operators could participate and
share their experiences of what is or isn't (yet!) working with
self-healing in OpenStack, so that those of us on the development side
can aim to solve the right problems :-)

Thanks, and see some of you in Dublin!

Adam

__
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] [placement] resource providers update 18-07

2018-02-23 Thread Matt Riedemann 

On 2/16/2018 7:54 AM, Chris Dent wrote:

Before I get to the meat of this week's report, I'd like to request
some feedback from readers on how to improve the report. Over its
lifetime it has grown and it has now reached the point that while it
tries to give the impression of being complete, it never actually is,
and is a fair chunk of work to get that way.

So perhaps there is a way to make it a bit more focused and thus bit
more actionable. If there are parts you can live without or parts you
can't live without, please let me know.

One idea I've had is to do some kind of automation to make it what
amounts to a dashboard, but I'm not super inclined to do that because
the human curation has been useful for me. If it's not useful for
anyone else, however, then that's something to consider.


-1 on a dashboard unless it's just something like a placement-specific 
review dashboard, but you'd have to star or somehow label 
placement-specific patches. I appreciate the human thought/comments on 
the various changes for context.


I don't think I'd remove anything. One thing to maybe add is work on the 
osc-placement plugin:


https://review.openstack.org/#/q/status:open+project:openstack/osc-placement+branch:master+topic:bp/placement-osc-plugin-rocky

We did a grind through a bunch of those in Queens and made good progress 
on providing a minimal useful set of CLIs in osc-placement 1.0.0, so I'd 
like to see that continue, especially as deployments are upgrading to 
the point of needing to interact with placement from an ops perspective.


--

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

Re: [openstack-dev] [ openstack-dev ][ tripleo ] unplanned outtage in RDO-Cloud

2018-02-23 Thread David Moreau Simard 
Please be wary of approving changes since the Third Party CI is out of
order until this is resolved.

David Moreau Simard
Senior Software Engineer | OpenStack RDO

dmsimard = [irc, github, twitter]


On Fri, Feb 23, 2018 at 5:40 PM, Wesley Hayutin  wrote:
>
>
> On Fri, Feb 23, 2018 at 12:09 PM, Wesley Hayutin 
> wrote:
>>
>> Greetings,
>>
>> The TripleO CI in RDO-Cloud has experienced an unplanned outage and is
>> down at this time.  We will update this thread with more information
>> regarding when the CI will be brought back online as it becomes available.
>>
>>
>> Thank you!
>> Wes Hayutin
>
>
> FYI..
> The latest estimate for the unplanned outtage to TripleO-CI in RDO-Cloud is
> that it will take a number of business days to resolve the issues.
>
> Thank you!
>
>
> __
> 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]Testing ironic in the overcloud

2018-02-23 Thread Emilien Macchi 
On Fri, Feb 23, 2018 at 2:48 PM, Derek Higgins  wrote:

>
>
> On 1 February 2018 at 16:18, Emilien Macchi  wrote:
>
>> On Thu, Feb 1, 2018 at 8:05 AM, Derek Higgins  wrote:
>> [...]
>>
>>> o Should I create a new tempest test for baremetal as some of the
> networking stuff is different?
>

 I think we would need to run baremetal tests for this new featureset,
 see existing files for examples.

>>> Do you mean that we should use existing tests somewhere or create new
>>> ones?
>>>
>>
>> I mean we should use existing tempest tests from ironic, etc. Maybe just
>> a baremetal scenario that spawn a baremetal server and test ssh into it,
>> like we already have with other jobs.
>>
> Done, the current set of patches sets up a new non voting job
> "tripleo-ci-centos-7-scenario011-multinode-oooq-container" which setup up
> ironic in the overcloud and run the ironic tempest job
> "ironic_tempest_plugin.tests.scenario.test_baremetal_basic_
> ops.BaremetalBasicOps.test_baremetal_server_ops"
>
> its currently passing so I'd appreciate a few eyes on it before it becomes
> out of date again
> there are 4 patches starting here https://review.openstack.
> org/#/c/509728/19
>

Nice!
http://logs.openstack.org/28/509728/21/check/tripleo-ci-centos-7-scenario011-multinode-oooq-container/68cb9f4/logs/tempest.html.gz

Thanks for this work!
We'll make sure that lands soon.


>
>
>>
>> o Is running a script on the controller with NodeExtraConfigPost the best
> way to set this up or should I be doing something with quickstart? I don't
> think quickstart currently runs things on the controler does it?
>

 What kind of thing do you want to run exactly?

>>> The contents to this file will give you an idea, somewhere I need to
>>> setup a node that ironic will control with ipmi
>>> https://review.openstack.org/#/c/485261/19/ci/common/vbmc_setup.yaml
>>>
>>
>> extraconfig works for me in that case, I guess. Since we don't productize
>> this code and it's for CI only, it can live here imho.
>>
>> Thanks,
>> --
>> Emilien Macchi
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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
>
>


-- 
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] 答复: [tripleo][vitrage] Draft schedule for PTG

2018-02-23 Thread Emilien Macchi 
On Fri, Feb 23, 2018 at 9:05 AM,  wrote:

> Hi EmilienMacchi,
>
>
> I added a topic about 'support Vitrage(Root Cause Analysis project)
> service' in the etherpad for PTG.
>
> Can you please help to schedule a time slot? Maybe after the topic of
> 'Upgrades and Updates',  half an hour is enough.
>
> We want to support the feature in the TripleO roadmap for Rocky.
>

Cool, let's have this on Friday. (Schedule updated)


> Thanks~
>
>
> BR,
>
> dwj
>
>
>
>
>
> 原始邮件
> *发件人：* ;
> *收件人：* ;
> *日 期 ：*2018年02月20日 00:38
> *主 题 ：**[openstack-dev] [tripleo] Draft schedule for PTG*
> __
> 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
>
> Alex and I have been working on the agenda for next week, based on what
> people proposed in topics.
> The draft calendar is visible here:
> https://calendar.google.com/calendar/embed?src=tgpb5tv12mlu7kge5oqertje78%
> 40group.calendar.google.com=Europe%2FDublin
>
> Also you can import the ICS from:
> https://calendar.google.com/calendar/ical/tgpb5tv12mlu7kge5oqertje78%
> 40group.calendar.google.com/public/basic.ics
>
> Note this is a draft - we would love your feedback about the proposal.
>
> Some sessions might be too short or too long? You to tell us. (Please look
> at event details for descriptions).
> Also, for each session we need a "driver", please tell us if you volunteer
> to do it.
>
> Please let us know here and we'll make adjustment, we have plenty of room
> for it.
>
> Thanks!
> --
> Emilien Macchi
>
>
>


-- 
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] [tripleo] Draft schedule for PTG

2018-02-23 Thread Emilien Macchi 
On Fri, Feb 23, 2018 at 10:28 AM, Juan Antonio Osorio 
wrote:

> Could we change the Security talk to a day before Friday (both Thursday
> and Wednesday are fine)? Luke Hinds, the leader of the OpenStack Security
> group would like to join that discussion, but is not able to join that day.
>

Done, moved to Thursday afternoon. Hope it works for you!


>
> On Mon, Feb 19, 2018 at 6:37 PM, Emilien Macchi 
> wrote:
>
>> Alex and I have been working on the agenda for next week, based on what
>> people proposed in topics.
>>
>> The draft calendar is visible here:
>> https://calendar.google.com/calendar/embed?src=tgpb5tv12mlu7
>> kge5oqertje78%40group.calendar.google.com=Europe%2FDublin
>>
>> Also you can import the ICS from:
>> https://calendar.google.com/calendar/ical/tgpb5tv12mlu7kge5o
>> qertje78%40group.calendar.google.com/public/basic.ics
>>
>> Note this is a draft - we would love your feedback about the proposal.
>>
>> Some sessions might be too short or too long? You to tell us. (Please
>> look at event details for descriptions).
>> Also, for each session we need a "driver", please tell us if you
>> volunteer to do it.
>>
>> Please let us know here and we'll make adjustment, we have plenty of room
>> for it.
>>
>> Thanks!
>> --
>> Emilien Macchi
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Juan Antonio Osorio R.
> e-mail: jaosor...@gmail.com
>
>
> __
> 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
>
>


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

[openstack-dev] [cinder][ptg] Cinder Dinner and Ghost Tour Night ...

2018-02-23 Thread Jay S. Bryant 

Team,

There are a couple of events I am setting up that I would like you aware of:

First, is more details on the dinner Thursday night we already planned.  
Dinner will be at 7:45 at J. Sheehan's Irish Pub: 
http://sheehanspub.com/  I had dinner there tonight and it was 
wonderful.  Think it will work great for our group.  I have made 
reservations for those who have responded on the Etherpad. 
https://etherpad.openstack.org/p/cinder-ptg-rocky  If you want to add 
your name, please do so by EOD Tuesday as I need to confirm the number 
of people.


Second, I am putting together a Ghost tour night on Wednesday 2/28/18.  
The Gravedigger Ghost Tour comes highly recommended and is with a tour 
group that we have had very good experience with. I have not made 
official arrangements here, but anyone who wants to join me that night 
is more than welcome.  You can book tickets here: 
https://www.viator.com/tours/Dublin/Dublin-Gravedigger-Ghost-Tour/d503-5299GRAVE?_redirect=no=02=gdsarlsa=28353=true=52446860344=kl=s=216090288444=1t1=c=g=aud-298992519106:dsa-348108672214=1007850==EAIaIQobChMIxO6o5pq92QIVqLvtCh2vYgdcEAAYASAAEgLPWPD_BwE


Look forward to seeing you all next week!

Ping me on IRC if you have any questions.

Jay


__
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-dev ][ tripleo ] unplanned outtage in RDO-Cloud

2018-02-23 Thread Wesley Hayutin 
On Fri, Feb 23, 2018 at 12:09 PM, Wesley Hayutin 
wrote:

> Greetings,
>
> *The TripleO CI in RDO-Cloud has experienced an unplanned outage and is
> down at this time.  We will update this thread with more information
> regarding when the CI will be brought back online as it becomes available.*
>
> Thank you!
> Wes Hayutin
>

FYI..
The latest estimate for the unplanned outtage to TripleO-CI in RDO-Cloud is
that it will take a number of business days to resolve the issues.

Thank you!
__
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] Please abandon new stable/newton patches

2018-02-23 Thread Sean McGinnis 
On Fri, Feb 23, 2018 at 01:07:19PM -0600, Sean McGinnis wrote:
> It appears some cleanup work being done in the openstack/releases repo
> incorrectly recreated stable/newton branches for many projects. Along with the
> branch creation are the three patches to update reno in master and update
> .gitreview and constraints in the stable branch.
> 
> This was not intentional, and none of these patches should be merged. If you
> see them for any of your repos, please just abandon those patches. We will 
> work
> on cleaning up the old branches ASAP.
> 
> Thanks for your help.
> 
> Sean

Just for closure - all patches on the erroneous branches were abandoned and the
branches have been deleted. All should be back to normal now. Please let us
know in #openstack-release if you see anything to indicate otherwise.

Thanks!

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] [ironic] this week's priorities and subteam reports

2018-02-23 Thread Yeleswarapu, Ramamani 
Hi,

We are glad to present this week's priorities and subteam report for Ironic. As 
usual, this is pulled directly from the Ironic whiteboard[0] and formatted.

This Week's Priorities (as of the weekly ironic meeting)


Weekly priorities
-
- Fix the multitenant grenade - https://bugs.launchpad.net/ironic/+bug/1744139 
- Testing another possibility
- Disable .pyc file creation https://review.openstack.org/544750 MERGED
- Avoids library incompatibility issue by disabling .pyc files from 
being written to disk in the scenario.
- backport to stable/queens: https://review.openstack.org/#/c/545089/ 
MERGED
- The nova issue noted under critical bugs is also needed to make 
multitenant grenade reliable again.
- CI and docs work for classic drivers deprecation (see status below)
- Required Backports/Nice to haves below
- CRITICAL bugs (must be fixed and backported to queens before the release)
- ironic port list fix: https://review.openstack.org/545069 MERGED
- backport: https://review.openstack.org/#/c/545892/MERGED
- Nova
- Placement has issues after upgrade if ironic is unreachable for too 
long - Current WIP: https://review.openstack.org/#/c/545479/
- https://bugs.launchpad.net/nova/+bug/1750450
- Prepare for the PTG - https://etherpad.openstack.org/p/ironic-rocky-ptg

Required Queens Backports
-
- Fix for incorrect query during timeout check: 
https://review.openstack.org/545041 MERGED
- queens: https://review.openstack.org/#/c/545806/ MERGED
- Problem with traits and cleaning: 
https://bugs.launchpad.net/ironic/+bug/1750027
- https://review.openstack.org/#/c/545830/ MERGED
- backport to stable/queens: https://review.openstack.org/#/c/546830/ MERGED
- Problem with unrescue and netboot: https://review.openstack.org/#/c/544278/ 
MERGED
- https://review.openstack.org/#/c/546026/ MERGED
- rescue and UEFI: https://review.openstack.org/#/c/545186/ MERGED
- backport: https://review.openstack.org/#/c/546955/ MERGED
- configdrive overflow: https://review.openstack.org/#/c/334967/ MERGED
- backport: https://review.openstack.org/#/c/546551/ MERGED
- detached VIF reappearing: https://bugs.launchpad.net/ironic/+bug/1750785
- workaround: https://review.openstack.org/546584 abandoned
- decided to revert the original patch: https://review.openstack.org/546705 
MERGED
- backport to stable/queens: https://review.openstack.org/546719 
APPROVED

Nice to have backports
--
- Ansible docs - https://review.openstack.org/#/c/525501/ MERGED
- backport https://review.openstack.org/#/c/546079/ MERGED
- inspector: do not try passing non-MACs as switch_id: 
https://review.openstack.org/542214 APPROVED
- stable/queens - https://review.openstack.org/543961 MERGED
- Fix for CLEANING on conductor restart: https://review.openstack.org/349971 
MERGED
- backport: https://review.openstack.org/#/c/545893/ MERGED
- Reset reservations on take over: https://review.openstack.org/546273

Vendor priorities
-
cisco-ucs:
Patches in works for SDK update, but not posted yet, currently rebuilding 
third party CI infra after a disaster...
idrac:
RFE and first several patches for adding UEFI support will be posted by 
Tuesday, 1/9
ilo:
https://review.openstack.org/#/c/530838/ - OOB Raid spec for iLO5
irmc:
None

oneview:

Subproject priorities
-
bifrost:

ironic-inspector (or its client):

networking-baremetal:

networking-generic-switch:

sushy and the redfish driver:


Bugs (dtantsur, vdrok, TheJulia)

- Stats (diff between  12 Feb 2018 and 19 Feb 2018)
- Ironic: 208 bugs (-1) + 243 wishlist items (-4). 3 new (+1), 155 in progress 
(-2), 1 critical, 33 high (+4) and 23 incomplete (+3)
- Inspector: 13 bugs (-4) + 26 wishlist items (+1). 0 new, 12 in progress (-2), 
0 critical (-2), 2 high (-1) and 4 incomplete
- Nova bugs with Ironic tag: 16 (+2). 2 new (+1), 0 critical, 0 high
- via http://dashboard-ironic.7e14.starter-us-west-2.openshiftapps.com/
- the dashboard was abruptly deleted and needs a new home :(
- use it locally with `tox -erun` if you need to
- HIGH bugs with patches to review:
- Clean steps are not tested in gate 
https://bugs.launchpad.net/ironic/+bug/1523640: Add manual clean step ironic 
standalone test https://review.openstack.org/#/c/429770/15
- Needs to be reproposed to the ironic tempest plugin repository.
- prepare_instance() is not called for whole disk images with 'agent' deploy 
interface https://bugs.launchpad.net/ironic/+bug/1713916:
- Fix ``agent`` deploy interface to call ``boot.prepare_instance`` 
https://review.openstack.org/#/c/499050/
- (TheJulia) Currently WF-1, as revision is required for deprecation.

CI refactoring and missing test coverage

- not

[openstack-dev] [all] Please abandon new stable/newton patches

2018-02-23 Thread Sean McGinnis 
It appears some cleanup work being done in the openstack/releases repo
incorrectly recreated stable/newton branches for many projects. Along with the
branch creation are the three patches to update reno in master and update
.gitreview and constraints in the stable branch.

This was not intentional, and none of these patches should be merged. If you
see them for any of your repos, please just abandon those patches. We will work
on cleaning up the old branches ASAP.

Thanks for your help.

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

Re: [openstack-dev] [TripleO][ui] Network Configuration wizard

2018-02-23 Thread Liz Blanchard 
Hi All,

I've made some additional updates to my wireframes[1] and I think they are
in a good spot now for a discussion/review at the PTG next week.

Please feel free to reach out with any questions or feedback!

Thanks,
Liz

[1]
https://lizsurette.github.io/OpenStack-Design/tripleo-ui/3-tripleo-ui-edge-cases/7.advancednetworkconfigurationandtopology

On Thu, Feb 22, 2018 at 7:55 PM, Dan Sneddon  wrote:

>
>
> On Thu, Feb 15, 2018 at 2:00 AM, Jiri Tomasek  wrote:
>
>>
>> On Wed, Feb 14, 2018 at 11:16 PM, Ben Nemec 
>> wrote:
>>
>>>
>>>
>>> On 02/09/2018 08:49 AM, Jiri Tomasek wrote:
>>>
 *Step 2. network-environment -> NIC configs*

 Second step of network configuration is NIC config. For this
 network-environment.yaml is used which references NIC config templates
 which define network_config in their resources section. User is currently
 required to configure these templates manually. We would like to provide
 interactive view which would allow user to setup these templates using
 TripleO UI. A good example is a standalone tool created by Ben Nemec [3].

 There is currently work aimed for Pike to introduce jinja templating
 for network environments and templates [4] (single-nic-with-vlans,
 bond-with-vlans) to support composable networks and roles (integrate data
 from roles_data.yaml and network_data.yaml) It would be great if we could
 move this one step further by using these samples as a starting point and
 let user specify full NIC configuration.

 Available information at this point:
 - list of roles and networks as well as which networks need to be
 configured at which role's NIC Config template
 - os-net-config schema which defines NIC configuration elements and
 relationships [5]
 - jinja templated sample NIC templates

 Requirements:
 - provide feedback to the user about networks assigned to role and have
 not been configured in NIC config yet

>>>
>>> I don't have much to add on this point, but I will note that because my
>>> UI is standalone and pre-dates composable networks it takes the opposite
>>> approach.  As a user adds a network to a role, it exposes the configuration
>>> for that network.  Since you have the networks ahead of time, you can
>>> obviously expose all of those settings up front and ensure the correct
>>> networks are configured for each nic-config.
>>>
>>> I say this mostly for everyone's awareness so design elements of my tool
>>> don't get copied where they don't make sense.
>>>
>>> - let user construct network_config section of NIC config templates for
 each role (brigdes/bonds/vlans/interfaces...)
 - provide means to assign network to vlans/interfaces and automatically
 construct network_config section parameter references

>>>
>>> So obviously your UI code is going to differ, but I will point out that
>>> the code in my tool for generating the actual os-net-config data is
>>> semi-standalone: https://github.com/cybertron/t
>>> ripleo-scripts/blob/master/net_processing.py
>>>
>>> It's also about 600 lines of code and doesn't even handle custom roles
>>> or networks yet.  I'm not clear whether it ever will at this point given
>>> the change in my focus.
>>>
>>> Unfortunately the input JSON schema isn't formally documented, although
>>> the unit tests do include a number of examples.
>>> https://github.com/cybertron/tripleo-scripts/blob/master/tes
>>> t-data/all-the-things/nic-input.json covers quite a few different cases.
>>>
>>> - populate parameter definitions in NIC config templates based on
 role/networks assignment
 - populate parameter definitions in NIC config templates based on
 specific elements which use them e.g. BondInterfaceOvsOptions in case when
 ovs_bond is used

>>>
>>> I guess there's two ways to handle this - you could use the new jinja
>>> templating to generate parameters, or you could handle it in the generation
>>> code.
>>>
>>> I'm not sure if there's a chicken-and-egg problem with the UI generating
>>> jinja templates, but that's probably the simplest option if it works. The
>>> approach I took with my tool was to just throw all the parameters into all
>>> the files and if they're unused then oh well.  With jinja templating you
>>> could do the same thing - just copy a single boilerplate parameter header
>>> that includes the jinja from the example nic-configs and let the templating
>>> handle all the logic for you.
>>>
>>> It would be cleaner to generate static templates that don't need to be
>>> templated, but it would require re-implementing all of the custom network
>>> logic for the UI.  I'm not sure being cleaner is sufficient justification
>>> for doing that.
>>>
>>> - store NIC config templates in deployment plan and reference them from
 network-environment.yaml

 Problems to solve:
 As a biggest problem to solve I

[openstack-dev] [ openstack-dev ][ tripleo ] unplanned outtage in RDO-Cloud

2018-02-23 Thread Wesley Hayutin 
Greetings,

*The TripleO CI in RDO-Cloud has experienced an unplanned outage and is
down at this time.  We will update this thread with more information
regarding when the CI will be brought back online as it becomes available.*

Thank you!
Wes Hayutin
__
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] Developer Mailing List Digest February 17-23rd

2018-02-23 Thread Mike Perez 
HTML version: https://www.openstack.org/blog/?p=8332

Contribute to the Dev Digest by summarizing OpenStack Dev List threads:

* https://etherpad.openstack.org/p/devdigest
* http://lists.openstack.org/pipermail/openstack-dev/
* http://lists.openstack.org/pipermail/openstack-sigs

Helpful PTG links
==
PTG is around the corner. Here are some helpful links:

* Main welcome email 
http://lists.openstack.org/pipermail/openstack-dev/2018-February/127611.html
* Quick links: http://ptg.openstack.org/
* PDF schedule: 
http://lists.openstack.org/pipermail/openstack-dev/attachments/20180221/5c279bb3/attachment-0002.pdf
* PDf map for PTG venue: 
http://lists.openstack.org/pipermail/openstack-dev/attachments/20180221/5c279bb3/attachment-0003.pdf


Success Bot Says

* mhayden: got centos OSA gate under 2h today
* thingee: we have an on-boarding page and documentation for new contributors! 
[0]
* Tell us yours in OpenStack IRC channels using the command "#success "
* More: https://wiki.openstack.org/wiki/Successes

[0] - https://www.openstack.org/community


Thanks Bot Says
===
* Thanks pkovar for keep the Documentation team going!
* Thanks pabelanger and infra for getting ubuntu mirrors repaired and backup 
quickly!
* Thanks lbragstad for helping troubleshoot an intermittent fernet token 
validation failure in puppet gates
* Thanks TheJulia for helping me with a problem last week, it was really a 
networking problem issue, like you said so :)
* Thanks tosky for backporting devstack ansible changes to pike!
* Thanks thingee for Thanks Bot
* Thanks openstackstatus for logging our things
* Thanks strigazi for the v1.9.3 image
* Thanks smcginnis for not stopping this.
* Tell us yours in OpenStack IRC channels using the command "#thanks "
* More: https://wiki.openstack.org/wiki/Thanks


Community Summaries
===
* TC report [0]
* POST /api-sig/news [1]
* Release countdown [2]

[0] - 
http://lists.openstack.org/pipermail/openstack-dev/2018-February/127584.html
[1] - 
http://lists.openstack.org/pipermail/openstack-dev/2018-February/127651.html
[2] - 
http://lists.openstack.org/pipermail/openstack-dev/2018-February/127465.html


Vancouver Community Contributor Awards
==
The Community contributor awards gives recognition to those that are
undervalued, don't know they're appreciated, bind the community together, keep
things fun, or challenge some norm. There are a lot of people out there that
could use a pat on the back and affirmation that they do good work in the
community.

Nomination period is open now [0] until May 14th. Winners will be announced in
feedback session at Vancouver.

[0] - https://openstackfoundation.formstack.com/forms/cca_nominations_vancouver

Full message: 
http://lists.openstack.org/pipermail/openstack-dev/2018-February/127634.html


Release Naming For S - time to suggest a name!
==
It's time to pick a name for our "S" release! Since the associated Summit will
be in Berlin, the Geographic location has been chosen as "Berlin" (state).
Nominations are now open [0]. Rules and processes can be seen on the Governance
site [1].

[0] - https://wiki.openstack.org/wiki/Release_Naming/S_Proposals
[1] - https://governance.openstack.org/tc/reference/release-naming.html

Full message: 
http://lists.openstack.org/pipermail/openstack-dev/2018-February/127592.html


Final Queens RC Deadline

Thursday 22nd of April is the deadline for any final Queens release candidates.
We'll enter a quiet period for a week in preparation of tagging the final
Queens release during the PTG week. Make sure if  you have patches merged to
stable/queens that you propose a new RC before the deadline. PTLs should watch
for a patch from the release management team tagging the final release. While
not required, an acknowledgement on the patch would be appreciated.

Full message: 
http://lists.openstack.org/pipermail/openstack-dev/2018-February/127540.html


Do Not Import oslo_db.tests.*
=
Deprecations were made on oslo_db.sqlalchemy.test_base package of DbFixture and
DbTestCase. In a patch [0], and assumption was made to that these should be
imported from oslo_db.tests.sqlalchemy. Cinder, Ironic and Glance have been
found with this issue [1].

Unfortunately these were not prefixed with underscores to comply with naming
conventions for people to recognize private code. The tests module was included
for consumers to run those tests on their own packages easily.

[0] - https://review.openstack.org/#/c/522290/
[1] - http://codesearch.openstack.org/?q=oslo_db.tests=nope==

Full thread: 
http://lists.openstack.org/pipermail/openstack-dev/2018-February/thread.html#127531


Some New Zuul Features
==
Default timeout is 30 minutes for "post-run" phase of the job. A new attribute
"timeout" [0] can set this to something else, which could be useful for

Re: [openstack-dev] [tripleo] rdo cloud tenant reach 100 stacks

2018-02-23 Thread Paul Belanger 
On Fri, Feb 23, 2018 at 02:20:34PM +0100, Arx Cruz wrote:
> Just an update, we cleaned up the stacks with more than 10 hours, jobs
> should be working properly now.
> 
> Kind regards,
> Arx Cruz
> 
> On Fri, Feb 23, 2018 at 12:49 PM, Arx Cruz  wrote:
> 
> > Hello,
> >
> > We just notice that there are several jobs failing because the
> > openstack-nodepool tenant reach 100 stacks and cannot create new ones.
> >
> > I notice there are several stacks created > 10 hours, and I'm manually
> > deleting those ones.
> > I don't think it will affect someone, but just in case, be aware of it.
> >
> > Kind regards,
> > Arx Cruz
> >

Give that multinode jobs are first class citizen in zuulv3, I'd like to take
some time at the PTG to discuss what would be needed to stop using heat for OVB
and switch to nodepool.

There are a number of reasons to do this, remove te-broker, remove heat
dependency for testing, use common tooling, etc. I believe there is a CI session
for tripelo one day, I was thinking of bringing it up then. Unless there is a
better time.

Paul

__
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] Stepping down from Ironic core

2018-02-23 Thread Jim Rollenhagen 
Thank you for all of your good work, Vasyl. Sorry to see you go, but
hopefully you'll still be around IRC and such :)


// jim

On Fri, Feb 23, 2018 at 4:02 AM, Vasyl Saienko 
wrote:

> Hey Ironic community!
>
> Unfortunately I don't work on Ironic as much as I used to any more, so i'm
> stepping down from core reviewers.
>
> So, thanks for everything everyone, it's been great to work with you
> all for all these years!!!
>
>
> Sincerely,
> Vasyl Saienko
>
> __
> 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] [all] [QA] [interop] [keystone] [glance] [cinder] [tc] [ptg] QA Sessions for related cross projects

2018-02-23 Thread Lance Bragstad 
On Fri, Feb 23, 2018 at 2:24 AM, Ghanshyam Mann 
wrote:

> Hi All,
>
> QA team is planning to discuss few topics in Dublin PTG which need
> discussion and attention from related projects. If you can plan or ask
> someone from your team to present your projects, it will be more
> productive discussions.
>
> I am listing 2 such topic:
>
> 1. "Interop test for adds-on project": Wed 1.30 -2.00 PM
>  Related projects are interop, heat, designate, TC. This is open
> discussion topic in last cycle [1] and i do not think we have final
> consensus for this. Let's discuss it f2f and hopefully close this one
> with most agreed approach.
>
> 2. "Remove Deprecated APIs tests from Tempest." Wed 2.00 - 3.00 PM
> Related projects are glance, cinder, keystone. This is to remove the
> testing of Deprecated APIs. We have been discussing this over last
> couple of cycle but not finished yet. I would like to get related
> project agreement on removing their deprecated API testing and the
> best way to do that. I will prepare some sample patches to hava a
> glance of what is going to be removed and the approach of removal.
>

++

We have a couple open slots on Wednesday and Thursdays - so I moved our
libraries session to give the keystone team more flexibility to attend the
QA session [0].

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


>
> More details on those sessions can be found on QA PTG etherpad -
> https://etherpad.openstack.org/p/qa-rocky-ptg
>
> ..1 http://lists.openstack.org/pipermail/openstack-dev/2018-
> January/126146.html
>
> Have a safe travel and see you all in Dublin.
>
> -gmann
>
> __
> 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]Testing ironic in the overcloud

2018-02-23 Thread Derek Higgins 
On 1 February 2018 at 16:18, Emilien Macchi  wrote:

> On Thu, Feb 1, 2018 at 8:05 AM, Derek Higgins  wrote:
> [...]
>
>> o Should I create a new tempest test for baremetal as some of the
 networking stuff is different?

>>>
>>> I think we would need to run baremetal tests for this new featureset,
>>> see existing files for examples.
>>>
>> Do you mean that we should use existing tests somewhere or create new
>> ones?
>>
>
> I mean we should use existing tempest tests from ironic, etc. Maybe just a
> baremetal scenario that spawn a baremetal server and test ssh into it, like
> we already have with other jobs.
>
Done, the current set of patches sets up a new non voting job
"tripleo-ci-centos-7-scenario011-multinode-oooq-container" which setup up
ironic in the overcloud and run the ironic tempest job
"ironic_tempest_plugin.tests.scenario.test_baremetal_basic_ops.BaremetalBasicOps.test_baremetal_server_ops"

its currently passing so I'd appreciate a few eyes on it before it becomes
out of date again
there are 4 patches starting here https://review.openstack.org/#/c/509728/19


>
> o Is running a script on the controller with NodeExtraConfigPost the best
 way to set this up or should I be doing something with quickstart? I don't
 think quickstart currently runs things on the controler does it?

>>>
>>> What kind of thing do you want to run exactly?
>>>
>> The contents to this file will give you an idea, somewhere I need to
>> setup a node that ironic will control with ipmi
>> https://review.openstack.org/#/c/485261/19/ci/common/vbmc_setup.yaml
>>
>
> extraconfig works for me in that case, I guess. Since we don't productize
> this code and it's for CI only, it can live here imho.
>
> Thanks,
> --
> 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
>
>
__
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] heat 10.0.0.0rc2 (queens)

2018-02-23 Thread no-reply 

Hello everyone,

A new release candidate for heat for the end of the Queens
cycle is available!  You can find the source code tarball at:

https://tarballs.openstack.org/heat/

Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally released as the
final Queens release. You are therefore strongly
encouraged to test and validate this tarball!

Alternatively, you can directly test the stable/queens release
branch at:

http://git.openstack.org/cgit/openstack/heat/log/?h=stable/queens

Release notes for heat can be found at:

http://docs.openstack.org/releasenotes/heat/




__
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] Retirement of astara repos?

2018-02-23 Thread Andreas Jaeger 
On 2018-01-11 22:55, Mark McClain wrote:
> Sean, Andreas-
> 
> Sorry I missed Andres’ message earlier in December about retiring astara. 
> Everyone is correct that development stopped a good while ago.  We attempted 
> in Barcelona to find others in the community to take over the day-to-day 
> management of the project. Unfortunately, nothing sustained resulted from 
> that session. 
> 
> I’ve intentionally delayed archiving the repos because of background 
> conversations around restarting active development for some pieces bubble up 
> from time-to-time.  I’ll contact those I know were interested and try for a 
> resolution to propose before the PTG.

Mark, any update here?

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] [tripleo] rdo cloud tenant reach 100 stacks

2018-02-23 Thread Arx Cruz 
Just an update, we cleaned up the stacks with more than 10 hours, jobs
should be working properly now.

Kind regards,
Arx Cruz

On Fri, Feb 23, 2018 at 12:49 PM, Arx Cruz  wrote:

> Hello,
>
> We just notice that there are several jobs failing because the
> openstack-nodepool tenant reach 100 stacks and cannot create new ones.
>
> I notice there are several stacks created > 10 hours, and I'm manually
> deleting those ones.
> I don't think it will affect someone, but just in case, be aware of it.
>
> Kind regards,
> Arx Cruz
>
__
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] [gate][devstack][neutron][qa][release] Switch to lib/neutron in gate

2018-02-23 Thread Andrea Frittoli 
On Fri, Jan 19, 2018 at 8:36 PM Ihar Hrachyshka  wrote:

> Hi Andrea,
>
> thanks for taking time to reply. I left some answers inline.
>
> On Fri, Jan 19, 2018 at 9:08 AM, Andrea Frittoli
>  wrote:
> >
> >
> > On Wed, Jan 17, 2018 at 7:27 PM Ihar Hrachyshka 
> wrote:
> >>
> >> Hi all,
> >
> >
> > Hi!
> >>
> >>
> >> tl;dr I propose to switch to lib/neutron devstack library in Queens. I
> >> ask for buy-in to the plan from release and QA teams, something that
> >> infra asked me to do.
>

Hello Ihar,

I'm coming back to this thread after a while, since I'm writing zuulv3
native devstack jobs,
and I think this is the perfect opportunity for starting to using
lib/neutron, since we easily
decide to limit the change to the branches we want, e.g. start with master
and then
go back to stable/queens if we want to.

Zuulv3 native jobs run on master, queens and they're being ported to Pike.
Starting from Queens on I plan to stop using the test-matrix from
devstack-gate, and define
the list of required services in jobs instead. This is made possible by the
job inheritance
capability introduced by Zuul v3. For the single node job I proposed a
change already [0],
and I'm working on the same for multinode. I would like if possible to
start using new service
and variable names as part of [0] but I need some help on that.

This change in the zuulv3 jobs should replace the existing in progress
devstack-gate patch [1].

If you are at the PTG I would be happy to chat / hack on this topic there.

Andrea Frittoli (andreaf)

[0] https://review.openstack.org/#/c/545633/
[1] https://review.openstack.org/#/c/436798


> >>
> >> ===
> >>
> >> Last several cycles we were working on getting lib/neutron - the new
> >> in-tree devstack library to deploy neutron services - ready to deploy
> >> configurations we may need in our gates.
> >
> >
> > May I ask the reason for hosting this in the neutron tree?
>
> Sorry for wording it in a misleading way. The lib/neutron library is
> in *devstack* tree:
> https://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/neutron
> So in terms of deployment dependencies, there are no new repositories
> to fetch from or gate against.
>
> >
> >>
> >> Some pieces of the work
> >> involved can be found in:
> >>
> >> https://review.openstack.org/#/q/topic:new-neutron-devstack-in-gate
> >>
> >> I am happy to announce that the work finally got to the point where we
> >> can consistently pass both devstack-gate and neutron gates:
> >>
> >> (devstack-gate) https://review.openstack.org/436798
> >
> >
> > Both legacy and new style (zuulv3) jobs rely on the same test matrix
> code,
> > so your change would impact both worlds consistently, which is good.
> >
> >>
> >>
> >> (neutron) https://review.openstack.org/441579
> >>
> >> One major difference between the old lib/neutron-legacy library and
> >> the new lib/neutron one is that service names for neutron are
> >> different. For example, q-svc is now neutron-api, q-dhcp is now
> >> neutron-dhcp, etc. (In case you wonder, this q- prefix links us back
> >> to times when Neutron was called Quantum.) The way lib/neutron is
> >> designed is that whenever a single q-* service name is present in
> >> ENABLED_SERVICES, the old lib/neutron-legacy code is triggered to
> >> deploy services.
> >>
> >> Service name changes are a large part of the work. The way the
> >> devstack-gate change linked above is designed is that it changes names
> >> for deployed neutron services starting from Queens (current master),
> >> so old branches and grenade jobs are not affected by the change.
> >
> >
> > Any other change worth mentioning?
> >
>
> The new library is a lot more simplified and opinionated and has fewer
> knobs and branching that is not very useful for majority of users.
> lib/neutron-legacy was always known for its complicated configuration.
> We hope that adopting the new library will unify and simplify neutron
> configuration across different jobs and setups.
>
> From consumer perspective, nothing should change expect service names.
> Some localrc files may need adoption if they rely on old arcane knobs.
> It can be done during transition phase since old service names are
> expected to work.
>
> >>
> >>
> >> While we validated the change switching to new names against both
> >> devstack-gate and neutron gates that should cover 90% of our neutron
> >> configurations, and followed up with several projects that - we
> >> induced - may be affected by the change - there is always a chance
> >> that some job in some project gate would fail because of it, and we
> >> would need to push a (probably rather simple) follow-up to unbreak the
> >> affected job. Due to the nature of the work, the span of impact, and
> >> the fact that infra repos are not easily gated against with Depends-On
> >> links, we may need to live with the risk.
> >>
> >> Of course, there are several aspects of the project life involved,
> >>

Re: [openstack-dev] [ironic] Stepping down from Ironic core

2018-02-23 Thread Dmitry Tantsur 

Hi Vasyl,

I'm sad to hear it :( Thank YOU for everything! The only thing in the world more 
valuable than your contributions to ironic is the joy of hanging out with you at 
the events :) Good luck and do not disappear.


Dmitry

On 02/23/2018 10:02 AM, Vasyl Saienko wrote:

Hey Ironic community!

Unfortunately I don't work on Ironic as much as I used to any more, so i'm
stepping down from core reviewers.

So, thanks for everything everyone, it's been great to work with you
all for all these years!!!


Sincerely,
Vasyl Saienko


__
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] [tripleo] rdo cloud tenant reach 100 stacks

2018-02-23 Thread Arx Cruz 
Hello,

We just notice that there are several jobs failing because the
openstack-nodepool tenant reach 100 stacks and cannot create new ones.

I notice there are several stacks created > 10 hours, and I'm manually
deleting those ones.
I don't think it will affect someone, but just in case, be aware of it.

Kind regards,
Arx Cruz
__
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] [ptl][all][python3] collecting current status of python 3 support in projects

2018-02-23 Thread Bedyk, Witold 
Hi Doug,

I have added Monasca client, monasca-statsd library (green).
I have also updated and added other Monasca components still not supporting 
Python 3.

Best greetings
Witek


> -Original Message-
> From: Doug Hellmann [mailto:d...@doughellmann.com]
> Sent: Freitag, 23. Februar 2018 00:29
> To: openstack-dev 
> Subject: [openstack-dev] [ptl][all][python3] collecting current status of
> python 3 support in projects
> 
> I am trying to update the wiki document with the current state of support for
> Python 3 projects as part of preparing for a discussion about moving from
> "Python 2 first, then 3" to "Python 3 first, then 2" development.
> 
> I have added the missing libraries and services (at least those managed by
> the release team) and done my best to figure out if there are unit and
> functional/integration test jobs for each project.
> 
> I need your help to verify the information I have collected and fill in any 
> gaps.
> 
> Please look through the tables in [1] and if your projects' status is out of 
> date
> either update the page directly or email me (off
> list) with the updates.
> 
> Thanks!
> Doug
> 
> [1]
> https://wiki.openstack.org/wiki/Python3#Python_3_Status_of_OpenStack_
> projects
> 
> __
> 
> 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] Draft schedule for PTG

2018-02-23 Thread Juan Antonio Osorio 
Could we change the Security talk to a day before Friday (both Thursday and
Wednesday are fine)? Luke Hinds, the leader of the OpenStack Security group
would like to join that discussion, but is not able to join that day.

On Mon, Feb 19, 2018 at 6:37 PM, Emilien Macchi  wrote:

> Alex and I have been working on the agenda for next week, based on what
> people proposed in topics.
>
> The draft calendar is visible here:
> https://calendar.google.com/calendar/embed?src=tgpb5tv12mlu7kge5oqertje78%
> 40group.calendar.google.com=Europe%2FDublin
>
> Also you can import the ICS from:
> https://calendar.google.com/calendar/ical/tgpb5tv12mlu7kge5oqertje78%
> 40group.calendar.google.com/public/basic.ics
>
> Note this is a draft - we would love your feedback about the proposal.
>
> Some sessions might be too short or too long? You to tell us. (Please look
> at event details for descriptions).
> Also, for each session we need a "driver", please tell us if you volunteer
> to do it.
>
> Please let us know here and we'll make adjustment, we have plenty of room
> for it.
>
> Thanks!
> --
> 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
>
>


-- 
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
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][vitrage] Draft schedule for PTG

2018-02-23 Thread dong.wenjuan 
Hi EmilienMacchi,







I added a topic about 'support Vitrage(Root Cause Analysis project) service' in 
the etherpad for PTG.


Can you please help to schedule a time slot? Maybe after the topic of 'Upgrades 
and Updates',  half an hour is enough.


We want to support the feature in the TripleO roadmap for Rocky.


Thanks~






BR,


dwj



















原始邮件



发件人： ;
收件人： ;
日 期 ：2018年02月20日 00:38
主 题 ：[openstack-dev] [tripleo] Draft schedule for PTG


__
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

Alex and I have been working on the agenda for next week, based on what people 
proposed in topics.
The draft calendar is visible here:
https://calendar.google.com/calendar/embed?src=tgpb5tv12mlu7kge5oqertje78%40group.calendar.google.com=Europe%2FDublin

Also you can import the ICS from:
https://calendar.google.com/calendar/ical/tgpb5tv12mlu7kge5oqertje78%40group.calendar.google.com/public/basic.ics

Note this is a draft - we would love your feedback about the proposal.

Some sessions might be too short or too long? You to tell us. (Please look at 
event details for descriptions).
Also, for each session we need a "driver", please tell us if you volunteer to 
do it.

Please let us know here and we'll make adjustment, we have plenty of room for 
it.

Thanks!
-- 


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

[openstack-dev] [ironic] Stepping down from Ironic core

2018-02-23 Thread Vasyl Saienko 
Hey Ironic community!

Unfortunately I don't work on Ironic as much as I used to any more, so i'm
stepping down from core reviewers.

So, thanks for everything everyone, it's been great to work with you
all for all these years!!!


Sincerely,
Vasyl Saienko
__
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] [heat] heat-dashboard is non-free, with broken unit test env

2018-02-23 Thread Xinni Ge 
Hi there,

We are aware of the javascript embedded issue, and working on it now, the
patch will be summited later.

As for the unittest failure, we are still investigating it. We will contant
you as soon as we find out the cause.

Sorry to bring troubles to you. We will be grateful if you could wait for a
little longer.

Best Regards,

Xinni

On Thu, Feb 22, 2018 at 5:41 AM, Thomas Goirand  wrote:

> On 02/21/2018 05:54 PM, Corey Bryant wrote:
> >
> >
> > On Wed, Feb 21, 2018 at 9:35 AM, Thomas Goirand  > > wrote:
> >
> > Hi there!
> >
> > I'm having big trouble package heat-dashboard for Debian. I hope I
> can
> > get help through this list.
> >
> > In here:
> >
> > heat_dashboard/static/dashboard/project/heat_
> dashboard/template_generator/js/
> >
> > we have minified *only* versions of Javascript.
> >
> >
> > There's also a bug open for this:
> > https://bugs.launchpad.net/heat-dashboard/+bug/1747687
> >
> > Regards,
> > Corey
>
> Thanks for the link and filing this bug.
>
> Cheers,
>
> Thomas Goirand (zigo)
>
> __
> 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
>



-- 
葛馨霓 Xinni Ge
__
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] [QA] [interop] [keystone] [glance] [cinder] [tc] [ptg] QA Sessions for related cross projects

2018-02-23 Thread Ghanshyam Mann 
Hi All,

QA team is planning to discuss few topics in Dublin PTG which need
discussion and attention from related projects. If you can plan or ask
someone from your team to present your projects, it will be more
productive discussions.

I am listing 2 such topic:

1. "Interop test for adds-on project": Wed 1.30 -2.00 PM
 Related projects are interop, heat, designate, TC. This is open
discussion topic in last cycle [1] and i do not think we have final
consensus for this. Let's discuss it f2f and hopefully close this one
with most agreed approach.

2. "Remove Deprecated APIs tests from Tempest." Wed 2.00 - 3.00 PM
Related projects are glance, cinder, keystone. This is to remove the
testing of Deprecated APIs. We have been discussing this over last
couple of cycle but not finished yet. I would like to get related
project agreement on removing their deprecated API testing and the
best way to do that. I will prepare some sample patches to hava a
glance of what is going to be removed and the approach of removal.

More details on those sessions can be found on QA PTG etherpad -
https://etherpad.openstack.org/p/qa-rocky-ptg

..1 http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html

Have a safe travel and see you all in Dublin.

-gmann

__
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