Re: [openstack-dev] [architecture] First meeting happened -- Regularly scheduled Thursdays at 1900

[Nikhil Komawar]

Thanks for this email Clint!

I added a courtesy reminder section where people who wish to join and be
notified prior to start of the meeting can do so. I encourage everyone
to consider adding their nicks and the meeting chair to ping them. This
will help everyone avoid maintain another meeting on the calendar and
get notified on irc just when the meeting is about to start.

On 9/11/16 6:27 PM, Clint Byrum wrote:
> FYI, we had our first Architecture WG meeting this past Thursday. I want
> to thank everyone who was able to make it. I hope that we'll see
> increased attendance and be able to begin selecting specifications to
> discuss and work on starting with our next meeting.
>
> The agenda is available here:
>
> https://wiki.openstack.org/wiki/Meetings/Arch-WG
>
> Important topics we're expecting this week:
>
> * Whether or not to have an alternative meeting time for better time
>   zone coverage.
> * Whether or not to abandon the cross-project spec and instead just
>   adopt what is available now as an internal charter.
> * What to start focusing on designing/documenting/working
>
> I hope to see more of you there on #openstack-meeting-alt this Thursday.
> 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

-- 

Thanks,
Nikhil


__
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] [opentack-dev][tacker]Manual install Tacker fails

[zhi]

hi,

I downloaded the code from the master branch and installed Tacker manual by
the document[1]. I met an error when I started the tacker-server by "python
/usr/bin/tacker-server --config-file /etc/tacker/tacker.conf
--log-file /var/log/tacker/tacker.log".

The error message is "
2016-09-12 11:20:48.427 ERROR stevedore.extension
[req-4799662d-a606-4337-802f-d94c44b35a50 None None] Could not load 'noop':
Can't instantiate abstract class DeviceNoop with abstract methods
get_resource_info
2016-09-12 11:20:48.428 ERROR stevedore.extension
[req-4799662d-a606-4337-802f-d94c44b35a50 None None] Could not load 'nova':
Can't instantiate abstract class DeviceNova with abstract methods
get_resource_info
"

Did anyone meet the same error as me?

Hope for your reply.


Thanks


[1].
http://docs.openstack.org/developer/tacker/install/manual_installation.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] [puppet] Puppet OpenStack PTL non-candidacy

[Xingchao Yu]

Emilien,
   Thank you for your hard work and efforts to make Puppet-Openstack so
great!


2016-09-11 9:53 GMT+08:00 Emilien Macchi :

> Thank you all for all the kind words! I appreciate them a lot :-)
> Just a note to avoid confusion, I'm not going anywhere, and I'll keep
> focus on Puppet modules + TripleO like before.
> Sorry but I'll still bother you when something breaks in OpenStack :-P
>
> Thanks again,
>
> On Sat, Sep 10, 2016 at 10:23 AM, Amrith Kumar  wrote:
> > Emilien,
> >
> > Great work over the past 18 months, it was a pleasure to work with you.
> Thanks for all you've done!
> >
> > -amrith
> >
> >> -Original Message-
> >> From: Emilien Macchi [mailto:emil...@redhat.com]
> >> Sent: Friday, September 09, 2016 12:06 PM
> >> To: OpenStack Development Mailing List  openstack.org>
> >> Subject: [openstack-dev] [puppet] Puppet OpenStack PTL non-candidacy
> >>
> >> Hi,
> >>
> >> I wrote a little blog post about the last cycle in PuppetOpenStack:
> >> http://my1.fr/blog/puppet-openstack-achievements-during-newton-cycle/
> >>
> >> I can't describe how much I liked to be PTL during the last 18 months
> >> and I wouldn't imagine we would be where we are today when I started
> >> to contribute on this project.
> >> Working on it is something I really enjoy because we have interactions
> >> with all OpenStack community and I can't live without it.
> >>
> >> However, I think it's time to pass the PTL torch for Ocata cycle.
> >> Don't worry, I'll still be around and bother you when CI is broken ;-)
> >>
> >> Again, a big thank you for those who work with me,
> >> --
> >> 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
>
>
>
> --
> 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

Re: [openstack-dev] [all][Elections] Nominations for OpenStack PTLs (Program Team Leads) are now open

[Tristan Cacqueray]

On 09/12/2016 12:01 AM, Tristan Cacqueray wrote:
> Nominations for OpenStack PTLs (Program Team Leads) are now open and
> will remain open until March 18, 23:45 UTC.

Oops, nominations are actually only open until September 18, 23:45 UTC.

-Tristan



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] [Cinder] FFE request for RBD replication

[Huang Zhiteng]

+1 for this long-waited feature to land in Newton.

On Sun, Sep 11, 2016 at 1:09 AM, Jay S. Bryant <
jsbry...@electronicjungle.net> wrote:

> +1 from me.  It is making good progress and is low risk.
>
> -Jay
>
>
>
> On 09/09/2016 02:32 PM, Gorka Eguileor wrote:
>
>> Hi,
>>
>> As some of you may know, Jon Bernard (jbernard on IRC) has been working
>> on the RBD v2.1 replication implementation [1] for a while, and we would
>> like to request a Feature Freeze Exception for that work, as we believe
>> it is a good candidate being a low risk change for the integrity of
>> the existing functionality in the driver:
>>
>> - It's non intrusive if it's not enabled (enabled using
>>replication_device configuration option).
>> - It doesn't affect existing deployments (disabled by default).
>> - Changes are localized to the driver itself (rbd.py) and the driver
>>unit tests file (test_rbd.py).
>>
>> Jon would have liked to make this request himself, but due to the
>> untimely arrival of his newborn baby this is not possible.
>>
>> For obvious reasons Jon will not be available for a little while, but
>> this will not be a problem, as I am well acquainted with the code -and
>> I'll be able to reach Jon if necessary- and will be taking care of the
>> final steps of the review process of his patch: replying to comments in
>> a timely fashion, making changes to the code as required, and answering
>> pings on IRC regarding the patch.
>>
>> Since some people may be interested in testing this functionality during
>> the reviewing process -or just for fun- I'll be publishing a post with
>> detailed explanation on how to deploy and test this feature as well as
>> an automated way to deploy 2 Ceph clusters -linked to be mirroring one
>> another-, and one devstack node with everything ready to test the
>> functionality (configuration and keys for the Ceph clusters, cinder
>> configuration, the latest upstream patch, and a volume type with the
>> right configuration).
>>
>> Please, do not hesitate to ask if there are any questions to or concerns
>> related to this request.
>>
>> Thank you for taking the time to evaluate this request.
>>
>> Cheers,
>> Gorka.
>>
>> [1]: https://review.openstack.org/333565
>>
>> 
>> __
>> 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
>



-- 
Regards
Huang Zhiteng
__
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 PTL candidacy

[Emilien Macchi]

This is my candidacy for PTL role in the TripleO team for the Ocata cycle.

https://review.openstack.org/368509

I had the immense pleasure [1] to lead Puppet OpenStack team during 18 months
and we succeeded in improving Continuous Integration with more coverage,
accelerating Release management, growing our Community, bringing more
consistency in the way to configure OpenStack and staying the most-used project
to deploy OpenStack in production [2]. I plan to re-use this experience for
TripleO project.

I see the PTL role as a catalyst for the team:

- Release projects early and often. Continue to delegate the release management
  task to team members, like we did during Newton cycle.
- Never stop to increase testing coverage and keep finding solutions to
  scale-up Continuous Integration system. TripleO scenarios were a start,
  let's continue the efforts and improve it during Ocata [3].
- Animate collaboration with OpenStack vendors who provide backends and
  drivers in TripleO [4] to bring testing scenarios so we can actually test
  their drivers.
- Continue the efforts to find a consensus on which tool TripleO CI should
  use with regard to TripleO Quickstart vs tripleo-ci.
- Welcome new contributors by keeping regular TripleO deep-dive sessions,
  organizing documentation sprints and making sure help is provided on
  mailing-lists and IRC channel.
- Enforcing our feature freeze exception policy and improve communications
  to better understand the feature we want in a release, and try to stick
  on it.
- Help to scale the TripleO team by investigating the creation of upstream
  squads (similar to Neutron stadium but for TripleO) with different areas
  of focus (e.g. UI / CLI / upgrades / CI tools / Workflows / ...).
  PTL role would also be to coordinate the squads together.
- Being a proxy for OpenStack Technical Committee, Release managers
  and other OpenStack projects in general, with good communications and
  open discussions.

We will succeed in all these tasks with advanced teamwork and I would be
honored to serve our group as PTL.

Thank you for your consideration,


[1] http://my1.fr/blog/puppet-openstack-achievements-during-newton-cycle/
[2] https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf
[3] http://my1.fr/blog/scaling-up-tripleo-ci-coverage-with-scenarios/
[4] http://lists.openstack.org/pipermail/openstack-dev/2016-August/102205.html
-- 
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] [all][Elections] Nominations for OpenStack PTLs (Program Team Leads) are now open

[Tristan Cacqueray]

Nominations for OpenStack PTLs (Program Team Leads) are now open and
will remain open until March 18, 23:45 UTC.

All candidates must be submitted as a text file to the
openstack/election repository as explained at
http://governance.openstack.org/election/#how-to-submit-your-candidacy
Note that starting with this round, candidates lists shall include IRC
name, thus please make sure to follow the new candidacy file naming
convention: $cycle_name/$project_name/$ircname.txt.

In order to be an eligible candidate (and be allowed to vote) in a given
PTL election, you need to have contributed an accepted patch to one of
the corresponding program's projects[0] during the Mitaka-Newton
timeframe (September 5, 2015 00:00 UTC to September 4, 2016 23:59 UTC))

Additional information about the nomination process can be found here:
https://governance.openstack.org/election/

As the election officials  approve candidates, they will be listsed
here: http://governance.openstack.org/election/#ocata-ptl-candidates
Elections will begin at 00:00 September 19, 2016 (UTC) and run until
23:45 September 25, 2016 (UTC).

The electorate is requested to confirm their email address in gerrit,
review.openstack.org > Settings > Contact Information >  Preferred
Email, prior to September 18, 2016 so that the emailed ballots are
mailed to the correct email address.

Happy running,
Tristan



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] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Matthew Mosesohn]

+1

On Sun, Sep 11, 2016 at 10:20 PM, Alexey Shtokolov
 wrote:
> +1
>
> Stanislaw made a great contribution!
> I would like to mention SSL-support, YAQL expressions for data-driven
> orchestration
> and his awesome live YAQL evaluator for Fuel Master node [0]
>
> [0] https://github.com/sorrowless/fuyaql
>
> ---
> WBR, Alexey Shtokolov
> Fuel Development Lead
>
> On Thu, Sep 8, 2016 at 1:17 PM, Denis Egorenko 
> wrote:
>>
>> +1
>>
>> 2016-09-08 13:06 GMT+03:00 Aleksandr Didenko :
>>>
>>> +1
>>>
>>> On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko
>>>  wrote:

 +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

>>>
>>>
>>>
>>> __
>>> 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,
>> Egorenko Denis,
>> Senior Deployment Engineer
>> Mirantis
>>
>> __
>> 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] [architecture] First meeting happened -- Regularly scheduled Thursdays at 1900

[Clint Byrum]

FYI, we had our first Architecture WG meeting this past Thursday. I want
to thank everyone who was able to make it. I hope that we'll see
increased attendance and be able to begin selecting specifications to
discuss and work on starting with our next meeting.

The agenda is available here:

https://wiki.openstack.org/wiki/Meetings/Arch-WG

Important topics we're expecting this week:

* Whether or not to have an alternative meeting time for better time
  zone coverage.
* Whether or not to abandon the cross-project spec and instead just
  adopt what is available now as an internal charter.
* What to start focusing on designing/documenting/working

I hope to see more of you there on #openstack-meeting-alt this Thursday.
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] [Congress] Stack trace returned to end user bug

[Tim Hinrichs]

The Api node on Oslo-messaging sends a request to the policy node asking
for say policy alpha. The policy node raises an exception, which Oslo
returns to the API node. I'd imagine there is some way to have the Ali node
extract the original exception or tell Oslo to return the only the original
exception.

Tim
On Thu, Sep 8, 2016 at 2:04 PM Aimee Ukasick 
wrote:

> All --
>
> https://bugs.launchpad.net/congress/+bug/1620868
>
> I stepped through the code with the pdb. I can't find anything wrong
> in the CongressException
> code.
>
> The traceback is being added by oslo_messaging/rpc/server.py  in
> _process_incoming
> This call that is throwing an exception: res =
> self.dispatcher.dispatch(message) but I haven't
> determined why.
>
> https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/server.py#L134
>
> https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/server.py#L142
>
> console output here:  http://paste.openstack.org/show/569334/
>
>
> I can't figure out why oslo.messaging is throwing an exception, I
> assume I should go into the API and CLI cod and prevent the traceback
> from being displayed.
>
> Thoughts? Suggestions? Epiphanies?
>
> aimee
>
> __
> 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] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Alexey Shtokolov]

+1

Stanislaw made a great contribution!
I would like to mention SSL-support, YAQL expressions for data-driven
orchestration
and his awesome live YAQL evaluator for Fuel Master node [0]

[0] https://github.com/sorrowless/fuyaql

---
WBR, Alexey Shtokolov
Fuel Development Lead

On Thu, Sep 8, 2016 at 1:17 PM, Denis Egorenko 
wrote:

> +1
>
> 2016-09-08 13:06 GMT+03:00 Aleksandr Didenko :
>
>> +1
>>
>> On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko <
>> svasile...@mirantis.com> wrote:
>>
>>> +1
>>>
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.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:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best Regards,
> Egorenko Denis,
> Senior Deployment Engineer
> Mirantis
>
> __
> 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] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Alexey Shtokolov]

My strong +1

Ilya made and keeps making a great contribution to the development of Fuel
Plugins Framework
on both sides (nailgun and plugins) especially during the Newton release
cycle!

---
WBR, Alexey Shtokolov
Fuel Development Lead

On Sun, Sep 11, 2016 at 5:41 PM, Aleksey Kasatkin 
wrote:

> +1
>
>
> Aleksey Kasatkin
>
>
> On Sat, Sep 10, 2016 at 4:49 PM, Sergey Vasilenko  > wrote:
>
>> +1
>>
>> 
>> __
>> 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
>
>
__
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] Broken CI, overcloud.yaml not found

[Emilien Macchi]

Hopefully Heïkel was also online :-)

Here's the short term workaround: https://review.rdoproject.org/r/#/c/2186/
For long term, we need to backport what we want from master to
tripleoclient, specially all the recent mistral changes.

So please, if you have a patch in tripleoclient that has been merged
since August 30th, please backport it to stable/newton.

Thanks,

On Sun, Sep 11, 2016 at 12:54 PM, Emilien Macchi  wrote:
> So I found the reason, python-tripleoclient looks like downgraded in
> RDO since yesterday. See the bug report for more context.
>
> I investigated all recent changes in packaging and projects, I can't
> find yet the root cause of this downgrade, any hint is welcome!
>
> On Sun, Sep 11, 2016 at 12:27 PM, Emilien Macchi  wrote:
>> I'm not sure how yet but it looks like
>> https://review.openstack.org/#/c/315679/ broke CI (even if it passed
>> jobs).
>> I'm seeing a high number of failures all related to this error:
>>
>> 6:19:49.979948 | Deploying templates in the directory
>> /usr/share/openstack-tripleo-heat-templates
>> 2016-09-11 16:19:53.927301 | The following errors occurred:
>> 2016-09-11 16:19:53.927537 | [Errno 2] No such file or directory:
>> '/usr/share/openstack-tripleo-heat-templates/overcloud-without-mergepy.yaml'
>> 2016-09-11 16:19:53.927609 | [Errno 2] No such file or directory:
>> '/usr/share/openstack-tripleo-heat-templates/overcloud.yaml'
>>
>> See 
>> http://logs.openstack.org/18/347918/5/check/gate-tripleo-ci-centos-7-nonha-multinode/e7c4b3b/console.html#_2016-09-11_16_19_53_927537
>>
>> I reported the bug here: https://bugs.launchpad.net/tripleo/+bug/1622353
>>
>> I'll investigate a bit today, but continue tomorrow. Please use this
>> bug report if you have any thoughts.
>>
>> Thanks,
>> --
>> Emilien Macchi
>
>
>
> --
> 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] Broken CI, overcloud.yaml not found

[Emilien Macchi]

So I found the reason, python-tripleoclient looks like downgraded in
RDO since yesterday. See the bug report for more context.

I investigated all recent changes in packaging and projects, I can't
find yet the root cause of this downgrade, any hint is welcome!

On Sun, Sep 11, 2016 at 12:27 PM, Emilien Macchi  wrote:
> I'm not sure how yet but it looks like
> https://review.openstack.org/#/c/315679/ broke CI (even if it passed
> jobs).
> I'm seeing a high number of failures all related to this error:
>
> 6:19:49.979948 | Deploying templates in the directory
> /usr/share/openstack-tripleo-heat-templates
> 2016-09-11 16:19:53.927301 | The following errors occurred:
> 2016-09-11 16:19:53.927537 | [Errno 2] No such file or directory:
> '/usr/share/openstack-tripleo-heat-templates/overcloud-without-mergepy.yaml'
> 2016-09-11 16:19:53.927609 | [Errno 2] No such file or directory:
> '/usr/share/openstack-tripleo-heat-templates/overcloud.yaml'
>
> See 
> http://logs.openstack.org/18/347918/5/check/gate-tripleo-ci-centos-7-nonha-multinode/e7c4b3b/console.html#_2016-09-11_16_19_53_927537
>
> I reported the bug here: https://bugs.launchpad.net/tripleo/+bug/1622353
>
> I'll investigate a bit today, but continue tomorrow. Please use this
> bug report if you have any thoughts.
>
> 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

[openstack-dev] [tripleo] Broken CI, overcloud.yaml not found

[Emilien Macchi]

I'm not sure how yet but it looks like
https://review.openstack.org/#/c/315679/ broke CI (even if it passed
jobs).
I'm seeing a high number of failures all related to this error:

6:19:49.979948 | Deploying templates in the directory
/usr/share/openstack-tripleo-heat-templates
2016-09-11 16:19:53.927301 | The following errors occurred:
2016-09-11 16:19:53.927537 | [Errno 2] No such file or directory:
'/usr/share/openstack-tripleo-heat-templates/overcloud-without-mergepy.yaml'
2016-09-11 16:19:53.927609 | [Errno 2] No such file or directory:
'/usr/share/openstack-tripleo-heat-templates/overcloud.yaml'

See 
http://logs.openstack.org/18/347918/5/check/gate-tripleo-ci-centos-7-nonha-multinode/e7c4b3b/console.html#_2016-09-11_16_19_53_927537

I reported the bug here: https://bugs.launchpad.net/tripleo/+bug/1622353

I'll investigate a bit today, but continue tomorrow. Please use this
bug report if you have any thoughts.

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

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

[Thierry Carrez]

Matt Riedemann wrote:
>> [...]
>> Here is mine: it would fail to take into account that preparation for a
>> development cycle starts a few months /before/ PTG, not a just few weeks
>> before.
> 
> Do we really expect the next cycle PTL to be planning for the next cycle
> midway through the current cycle? That seems pretty extreme to me, when
> we're still crunching to the 3rd milestone and trying to wrap things up
> for feature freeze, which will determine a lot of what spills over into
> the next cycle.

There is /some/ expectation that by the middle of the cycle you start
listening to users and start thinking about what you won't be able to
accomplish this cycle and should definitely prioritize for the next.

It doesn't impact development yet, since as you said most people are
crunching to the 3rd milestone. But you are already past your "priority
feature freeze", and you can use the Summit to seed your thinking for
the next cycle.

I totally agree with you that it's difficult for even a single person to
switch focus to the next cycle that early. It is precisely why having
one specific person starting to think about the next cycle while almost
all the others are still wrapping up things can help. That person would
gradually involve more and more people (past feature freeze, past
RC1...) so that the next cycle doesn't start from nothing.

>> Talking with operators at the recent Ops midcycle, they were pretty
>> enthusiastic with the idea of having someone take responsibility for a
>> release cycle from day 0 (when you start collecting priorities) through
>> the development cycle, to release, up to early stable branch backports
>> and communication about the work that has been accomplished. The best
>> way to achieve that is to have that person designated in the middle of
>> the previous cycle, not just a few weeks before the development branches
>> open.
> 
> Are there specific bad acting projects that operators are having a
> problem with? Like, are there just terrible transitions happening
> somewhere in the community that the rest of us don't know about and it's
> impacting release-to-release development of major projects?

At the current design summit, operators and users trying to communicate
their priorities to some projects are routinely turned down by
developers saying that the slate is already full or the priorities are
already set. And that's fair -- eight weeks into the development cycle
is not the best moment to add priorities, so the timing of that feedback
was actively preventing it from happening.

That is why we are moving most of the feedback dialog to the "Forum"
event at the Summit in the middle of the cycle in the future --
sufficiently before the start of the "development" part of the next
release cycle that it's still time to listen. But we need someone there
to collect their feedback and start thinking about the next cycle,
otherwise you're just pretending to listen. That's why I think it's a
good idea to have someone more obviously focused on the next cycle
designated by then, to coordinate that feedback. But then, each team is
free to ignore that suggestion and handle user feedback differently.

-- 
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] [OpenStack-I18n] What's Up, Doc? 9 September

[Akihiro Motoki]

2016-09-09 12:43 GMT+09:00 Lana Brindley :
> Hi everyone,
>
> Only four weeks to go until Newton! Andreas, Brian, Olga, and I met with our 
> new release managers Olena and Alex a few days ago, and we're all ready and 
> waiting with bated breath to get started on the release. Don't forget that 
> you can contact any of us (or just send mail to the docs mailing list) if you 
> have any questions about the Newton docs release.
>
> This week, I've also done a core team review, and we bid farewell to two core 
> team members. More on that in this newsletter.
>
> == Progress towards Newton ==
>
> 26 days to go!
>
> Bugs closed so far: 428
>
> Release managers: Olena Logvinova and Alexandra Settle
>
> Release tasks are being tracked here: 
> https://etherpad.openstack.org/p/NewtonRelease
>
> Install Guide testing is being tracked here: 
> https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting
>
> == The Road to Barcelona ==
>
> * If there's something you want to make sure we discuss at Summit, please put 
> your ideas here: https://etherpad.openstack.org/p/Ocata-DocsSessions When we 
> get our room allocations, I'll organise it into a schedule.
> * If you require a visa invitation letter to travel to Spain, then you need 
> to fill out the form here: 
> https://www.openstack.org/summit/barcelona-2016/travel/#visa
>
> Looking a little further forward, Foundation have now announced that the 
> first Project Team Gathering (PTG) will be held in Atlanta, US, on Feb 20-24: 
> http://www.openstack.org/ptg
>
> == Core Team Review ==
>
> The core team have completed their review for August, and I'm a bit sad to 
> announce that both Atsushi Sakai and Gauvain Pocontek are no longer core team 
> members.
>
> Gauvain has been committing to OpenStack manuals since well before my time, 
> and has been an invaluable resource for many people (including myself!) over 
> the years. He is currently working on some new projects, but we hope to still 
> see him around from time to time.
>
> Atsushi-san joined the core team last year, and during that time has proven 
> an extremely effective reviewer. He is still very busy on OpenStack, with an 
> increased focus on cross-project tasks, so we will be sure to still see him 
> around. I wish you well on your endeavours!
>
> I thank you both for your commitment to being core team members, and for all 
> your contributions. We are better because of your effort.
>
> == Speciality Team Reports ==
>
> '''HA Guide: Andrew Beekhof'''
> Organizing a HA meetup at summit
> Intention is get an update plan finalized shortly
>
> '''Install Tutorials: Lana Brindley'''
> Core Guide testing is underway! Check out progress and sign up here: 
> https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Next meeting: 
> 13 September August 0600UTC.

I think the correct URL of the wiki page is
https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting .

>
> '''Networking Guide: Edgar Magana'''
> No report this week.
>
> '''Security Guide: Nathaniel Dillon'''
> No report this week.
>
> '''User Guides: Joseph Robinson'''
> No report this week.
>
> '''Ops Guide: Shilla Saebi, Darren Chan'''
> No report this week.
>
> '''API Guide: Anne Gentle'''
> Working on an article for Super User describing the switchover in API guide 
> sources to project repos and the new navigation.
>
> '''Config/CLI Ref: Tomoyuki Kato'''
> Consolidating the OSC command reference into the OSC specific doc.
>
> '''Training labs: Pranav Salunke, Roger Luethi'''
> No report this week.
>
> '''Training Guides: Matjaz Pancur'''
> Finished first day of our virtual sprint series (6 Sep): Common items: 
> https://etherpad.openstack.org/p/upstream-uni-common-items (coordinated by 
> Ildiko Vancsa, ildikov), Code contribution: 
> https://etherpad.openstack.org/p/upstream-uni-code-contribution (coordinated 
> by Kendall Nelson, diablo_rojo)
> Next virtual sprint dates: 12,13 and 16 September 
> (https://wiki.openstack.org/wiki/VirtualSprints#Upstream_training_Sprint)
>
> '''Hypervisor Tuning Guide: Blair Bethwaite
> No report this week.
>
> '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero'''
> No report this week.
>
> == Doc team meeting ==
>
> Next meetings:
>
> The APAC meeting was held this week, you can read the minutes here: 
> https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-09-07
>
> Next meetings:
> US: Wednesday 14 September, 19:00 UTC
> APAC: Wednesday 21 September, 00:30 UTC
>
> Please go ahead and add any agenda items to the meeting page here: 
> https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
>
> --
>
> Keep on doc'ing!
>
> Lana
>
> https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#9_September_2016
>
> --
> Lana Brindley
> Technical Writer
> Rackspace Cloud Builders Australia
> http://lanabrindley.com
>
>
> ___
> OpenStack-I18n mailing list
> openstack-i...@lists.openstack.org
> 

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Aleksey Kasatkin]

+1


Aleksey Kasatkin


On Sat, Sep 10, 2016 at 4:49 PM, Sergey Vasilenko 
wrote:

> +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
>
>
__
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] [Karbor] Thoughts on Decoupling Checkpoint API from the current Provider API

[Leon Wang]

I've added this item to the agenda of the next team meeting. link: 
https://wiki.openstack.org/wiki/Meetings/Karbor
 
 
-- Original --
From:  "王辉";
Date:  Sun, Sep 11, 2016 08:24 PM
To:  "openstack-dev"; 
Cc:  "yuval.brik"; 
Subject:  [Karbor] Thoughts on Decoupling Checkpoint API from the current 
Provider API

 
Hi Team,


I'm new to Karbor and stumbled upon the Provider API recently. I find it more 
intuitive that if we could decouple the Checkpoint API out users could directly 
operate on Checkpoint related actions.


I've filled out a BP about it 
(https://blueprints.launchpad.net/karbor/+spec/checkpoint-decouple) and I'm 
looking forward to the coming weekly Karbor meeting.__
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] [Karbor] Thoughts on Decoupling Checkpoint API from the current Provider API

[王辉]

Hi Team,


I'm new to Karbor and stumbled upon the Provider API recently. I find it more 
intuitive that if we could decouple the Checkpoint API out users could directly 
operate on Checkpoint related actions.


I've filled out a BP about it 
(https://blueprints.launchpad.net/karbor/+spec/checkpoint-decouple) and I'm 
looking forward to the coming weekly Karbor meeting.__
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