Re: [openstack-dev] [Release-job-failures] Release of openstack/glance failed

2016-12-11 Thread Andreas Jaeger 
On 2016-12-12 08:34, Andreas Jaeger wrote:
> On 2016-12-12 06:20, Tony Breeds wrote:
>> On Mon, Dec 12, 2016 at 04:44:18AM +, jenk...@openstack.org wrote:
>>> Build failed.
>>>
>>> - glance-docs-ubuntu-xenial 
>>> http://logs.openstack.org/38/38f199507aff8bfcaf81ad9ea58ea326224faf5f/release/glance-docs-ubuntu-xenial/de7d73e/
>>>  : FAILURE in 1m 44s
>>
>> This boils down to [1] which is a known problem with newer cryptography (and
>> the interaction with openssl).  What I don't understand is how we got there
>> with constratints working[2].  Perhaps it's the openssl on the release 
>> sigining
>> node is "newer" than general nodepool nodes?
> 
> glance does not use constraints in venv environment.
> 
> It can be used since a few months. I'll send a change for master,

I expect this needs backporting to stable branches - stable or glance
team, please review and backport yourself:

https://review.openstack.org/409642

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


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

Re: [openstack-dev] [Release-job-failures] Release of openstack/glance failed

2016-12-11 Thread Andreas Jaeger 
On 2016-12-12 06:20, Tony Breeds wrote:
> On Mon, Dec 12, 2016 at 04:44:18AM +, jenk...@openstack.org wrote:
>> Build failed.
>>
>> - glance-docs-ubuntu-xenial 
>> http://logs.openstack.org/38/38f199507aff8bfcaf81ad9ea58ea326224faf5f/release/glance-docs-ubuntu-xenial/de7d73e/
>>  : FAILURE in 1m 44s
> 
> This boils down to [1] which is a known problem with newer cryptography (and
> the interaction with openssl).  What I don't understand is how we got there
> with constratints working[2].  Perhaps it's the openssl on the release 
> sigining
> node is "newer" than general nodepool nodes?

glance does not use constraints in venv environment.

It can be used since a few months. I'll send a change for master,

Andreas

> Yours Tony.
> 
> [1] 
> http://logs.openstack.org/38/38f199507aff8bfcaf81ad9ea58ea326224faf5f/release/glance-docs-ubuntu-xenial/de7d73e/console.html#_2016-12-12_04_44_02_872311
> [2] 
> http://logs.openstack.org/38/38f199507aff8bfcaf81ad9ea58ea326224faf5f/release/glance-docs-ubuntu-xenial/de7d73e/console.html#_2016-12-12_04_44_02_863766
> 
> 
> 
> __
> 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
> 


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

[openstack-dev] [cinder] drbdmanage is no more GPL2

2016-12-11 Thread Mehdi Abaakouk 

Hi,

I have recently seen that drbdmanage python library is no more GPL2 but
need a end user license agreement [1]. 


Is this compatible with the driver policy of Cinder ?

[1] 
http://git.drbd.org/drbdmanage.git/commitdiff/441dc6a96b0bc6a08d2469fa5a82d97fc08e8ec1

Regards

--
Mehdi Abaakouk
mail: sil...@sileht.net
irc: sileht

__
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] [vitrage] how to use mock driver

2016-12-11 Thread Yujun Zhang 
Is there any documentation on how to use mock driver for unit testing?

It seems it generates fake events from json spec but what is the different
between

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

Re: [openstack-dev] [Release-job-failures] Release of openstack/glance failed

2016-12-11 Thread Tony Breeds 
On Mon, Dec 12, 2016 at 04:44:18AM +, jenk...@openstack.org wrote:
> Build failed.
> 
> - glance-docs-ubuntu-xenial 
> http://logs.openstack.org/38/38f199507aff8bfcaf81ad9ea58ea326224faf5f/release/glance-docs-ubuntu-xenial/de7d73e/
>  : FAILURE in 1m 44s

This boils down to [1] which is a known problem with newer cryptography (and
the interaction with openssl).  What I don't understand is how we got there
with constratints working[2].  Perhaps it's the openssl on the release sigining
node is "newer" than general nodepool nodes?

Yours Tony.

[1] 
http://logs.openstack.org/38/38f199507aff8bfcaf81ad9ea58ea326224faf5f/release/glance-docs-ubuntu-xenial/de7d73e/console.html#_2016-12-12_04_44_02_872311
[2] 
http://logs.openstack.org/38/38f199507aff8bfcaf81ad9ea58ea326224faf5f/release/glance-docs-ubuntu-xenial/de7d73e/console.html#_2016-12-12_04_44_02_863766


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

Re: [openstack-dev] [glance] priorities for the coming week (12/09-12/15)

2016-12-11 Thread Brian Rosmaita 
On 12/10/16 12:56 PM, Andrey Pavlov wrote:
> Hello,
> 
> Can you also review this - https://review.openstack.org/#/c/401277/
> for bug - https://bugs.launchpad.net/glance-store/+bug/1644177

Hi Andrey.  If you review some of the priority items below, I'm sure
someone will take a look at your patch.

cheers,
brian


> And please consider backport to Newton.
> 
> This bug is very annoying for deployments with several controllers and
> glance over cinder...
> 
> On Fri, Dec 9, 2016 at 3:14 PM, Brian Rosmaita 
> wrote:
> 
>> As discussed at the Glance weekly meeting yesterday, the priorities for
>> 12/1 through 12/8, unfortunately look very similar to last week's
>> priorities.  Some core reviewers need to step up.  The priorities are:
>>
>> Highest priority
>> 
>>
>> (1) database strategy for rolling upgrades:
>> https://review.openstack.org/#/c/331740/
>> This one has a video to enhance your reviewing pleasure and demonstrate
>> that the approach described actually is workable:
>> https://www.youtube.com/watch?v=Z4iwJRlPqOw
>>
>> (2) glance expand/contract migrations with alembic:
>> https://review.openstack.org/#/c/374278/
>> We need another +2 on this one, preferably from a non-Rackspace person.
>>
>> (3) community images spec update:
>> https://review.openstack.org/#/c/396919/
>> New to the list.  The latest patch includes the migration strategy for
>> which Erno said indicated on the patch he'd change his -2 to a +2, so
>> don't let the -2 on the patch stop you from reviewing it.
>>
>> The above three specs need to be reviewed as soon as possible.  We are
>> blocking Alex and Hemanth, because the Ocata database migration will
>> handle the community images changes.
>>
>>
>> Really high priority
>> 
>> (would be highest if the specs were already approved)
>>
>> (4) Patch to fix a glance_store regression:
>> https://review.openstack.org/#/c/387719/
>> and patch to prevent a related backend misconfiguration:
>> https://review.openstack.org/#/c/388944/
>>
>> (5) Patch to enable better request-id tracking:
>> https://review.openstack.org/#/c/352892/
>> This will be nice for operators, let's get it reviewed and merged!
>>
>> (6) Request for some insights and opinions for bug
>> https://bugs.launchpad.net/glance/+bug/1585917
>>
>>
>> Please take a look
>> ==
>>
>> (7) glanceclient problem: https://review.openstack.org/#/c/319960/
>>
>> thanks,
>> brian
>>
>> __
>> 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

Re: [openstack-dev] [heat] On allowing null as a parameter default

2016-12-11 Thread Rico Lin 
>
> I'd actually be fine with this just failing in all cases where null isn't
> a valid input to the function. We want it to fail as early as possible
> though, and the currently handling for get_attr is going to get in the way
> of that. (We currently try to delay checking for None as long as possible,
> because get_attr may not start returning a non-None value until runtime.)
> Maybe that means we should tackle this after the placeholder stuff is
> implemented, so that we can enforce earlier detection of errors?
>

I think we can let placeholder as a solution when null becomes an input to
the function. We will have a placeholder as the input (instead of null),
and check type with the placeholder to make sure we get to fail as soon as
we can. If the type is correct, we will check the real value when we
actually got one. With this part of spec in placeholder, I think we can
avoid blind check (and parse) with null value (which is the main reason of
bug [1]).
Worth mention that when dealing with null input value, parameter will parse
it to the `default value` of that type (0 for number, '' for string),
 which will allow as to pass the check, but miss a chance to find out the
error of why the input value is null (it just accept `default value` as the
input, but it might not be the what we design in the template). Also
`default value` not always the correct input (for some number properties, 0
is not allowed). I think with placeholder, we will never need to replace
null with `default value`.

+1 for gain enforce earlier detection of errors with placeholder. We can
make it as part of placeholder spec, or the one right next.
Any feedbacks to the spec [2] are welcome.

[1] https://bugs.launchpad.net/heat/+bug/1559807
[2] https://review.openstack.org/#/c/392499/
__
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] [docs][badges][all] Docs gate broken for projects that include README.rst in docs

2016-12-11 Thread Flavio Percoco 

On 09/12/16 17:20 +0100, Flavio Percoco wrote:

Greetings,

Some docs jobs seem to be broken by the latest (or not?) docutils release. The
breakage seems to be related to the latest addition of the bages patch. The docs
generation doesn't like to have remote images. It used to be a warning but it
seems to have turned into an error now. While this is reported and fixed
upstream, we can workaround the issue by tagging the image as remote.

An example of this fix can be found here: 
https://review.openstack.org/#/q/topic:readme-badge-fix

Note that this is mostly relevant for projects that include the readme files in
their documentation. If your project doesn't do it, you can ignore this email.
That said, I'd recommend all projects to do it.



Apparently this "fix" doesn't render the image, which is far from the ideal
solution. Hang on while we find a better fix.

Flavio

--
@flaper87
Flavio Percoco


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

Re: [openstack-dev] New comer to Openstack.

2016-12-11 Thread Gary Kotton 
Welcome aboard. Please see http://www.openstack.org/. A lot of the projects 
have developer guidelines. Maybe start there…

From: akula nagaraj reddy 
Reply-To: OpenStack List 
Date: Sunday, December 11, 2016 at 8:36 AM
To: OpenStack List 
Subject: [openstack-dev] New comer to Openstack.

Hi All,

Please let someone give how to start the things. I have moderate experience in 
Python .



Thanks and Regards
 Nagaraj R
+919538750652
__
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