Re: [openstack-dev] [cinder][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

[Eduard Matei]

Hi Duncan,
here is the review: https://review.openstack.org/#/c/241174

Thanks,
Eduard
__
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][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

[Eduard Matei]

Hi,

Thanks for the quick reply.
What do you mean a review? Should i resubmit the driver code to the cinder
repo? Do i need also the driver certification tests?

Thanks,
Eduard
__
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][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

[Eduard Matei]

Hi,

Trying to get more attention to this ...

We had our driver removed by commit:
https://github.com/openstack/cinder/commit/f0ab819732d77a8a6dd1a91422ac183ac4894419
 due to no CI.

Pls let me know if there is something wrong so we can fix it asap so we can
have the driver back in M.

The CI is commenting using the name "Open vStorage CI" instead of
"CloudFounders OpenvStorage CI".

Thanks,

Eduard

On Thu, Sep 3, 2015 at 10:33 AM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

>
> Hi,
>
> Trying to get more attention to this ...
>
> We had our driver removed by commit:
> https://github.com/openstack/cinder/commit/f0ab819732d77a8a6dd1a91422ac183ac4894419
> due to no CI.
>
> Pls let me know if there is something wrong so we can fix it asap so we
> can have the driver back in Liberty (if possible).
>
> The CI is commenting using the name "Open vStorage CI" instead of
> "CloudFounders OpenvStorage CI".
>
> Thanks,
>
> Eduard
>
>
>


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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]Behavior when one cinder-volume service is down

[Eduard Matei]

Thanks Scott,
But the question remains: if the "hacks" are not recommended then how can i
perform Evacuate when the c-vol service of the volumes i need evacuated is
"down", but there are two more controller node with c-vol services running?

Thanks,

Eduard
__
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]Behavior when one cinder-volume service is down

[Eduard Matei]

Hi,

Let me see if i got this:
- running 3 (multiple) c-vols won't automatically give you failover
- each c-vol is "master" of a certain number of volumes
-- if the c-vol is "down" then those volumes cannot be managed by another
c-vol

What i'm trying to achieve is making sure ANY volume is managed
(manageable) by WHICHEVER c-vol is running (and gets the call first) - sort
of A/A - so this means i need to look into Pacemaker and virtual-ips, or i
should try first the "same name".

Thanks,

Eduard

PS. @Michal: Where are volumes physically in case of your driver? <-
similar to ceph, on a distributed object storage service (whose disks can
be anywhere even on the same compute host)
__
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]Behavior when one cinder-volume service is down

[Eduard Matei]

Hi,

This all started when we were testing Evacuate with our storage driver.
We thought we found a bug (https://bugs.launchpad.net/cinder/+bug/1491276)
then Scott replied that we should be running cinder-volume service separate
from nova-compute.
For some internal reasons we can't do that - yet, but we have some
questions regarding the behavior of the service:

- on our original test setup we have 3 nodes (1 controller + compute +
cinder, 2 compute + cinder).
-- when we shutdown the second node and tried to evacuate, the call was
routed to cinder-volume of the halted node instead of going to other nodes
(there were still 2 cinder-volume services up) - WHY?
- on the new planned setup we will have 6 nodes (3 dedicated controller +
cinder-volume, 3 compute)
-- in this case which cinder-volume will manage which volume on which
compute node?
-- what if: one compute node and one controller go down - will the Evacuate
still work if one of the cinder-volume services is down? How can we tell -
for sure - that this setup will work in case ANY 1 controller and 1 compute
nodes go down?

Hypothetical:
- if 3 dedicated controller + cinder-volume nodes work can perform evacuate
when one of them is down (at the same time with one compute), WHY can't the
same 3 nodes perform evacuate when compute services is running on the same
nodes (so 1 cinder is down and 1 compute)
- if the answer to above question is "They can't " then what is the purpose
of running 3 cinder-volume services if they can't handle one failure?
- and if the answer to above question is "You only run one cinder-volume"
then how can it handle failure of controller node?

Thanks,

Eduard
__
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] Devstack broken - third party CI broken

[Eduard Matei]

Line
export DEVSTACK_LOCAL_CONFIG="disable_service ceilometer-acompute
ceilometer-acentral ceilometer-collector ceilometer-api"
in the job config did the trick.

Thanks,
Eduard
__
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] [Openstack-dev] Devstack broken - third party CI broken

[Eduard Matei]

Hi,

Our Jenkins CI has been failing consistently last night during devstack
install:


2015-09-08 21:56:33.585 | Error: Service ceilometer-acentral is not running
2015-09-08 21:56:33.585 | + for service in '$failures'
2015-09-08 21:56:33.586 | ++ basename
/opt/stack/status/stack/ceilometer-acompute.failure
2015-09-08 21:56:33.587 | + service=ceilometer-acompute.failure
2015-09-08 21:56:33.587 | + service=ceilometer-acompute
2015-09-08 21:56:33.587 | + echo 'Error: Service ceilometer-acompute is not
running'
2015-09-08 21:56:33.587 | Error: Service ceilometer-acompute is not running
2015-09-08 21:56:33.587 | + '[' -n
'/opt/stack/status/stack/ceilometer-acentral.failure
2015-09-08 21:56:33.587 |
/opt/stack/status/stack/ceilometer-acompute.failure' ']'
2015-09-08 21:56:33.587 | + die 1467 'More details about the above errors
can be found with screen, with ./rejoin-stack.sh'
2015-09-08 21:56:33.587 | + local exitcode=0


Screen logs for ceilometer show:

stack@d-p-c-local-01-2592:~/devstack$
/usr/local/bin/ceilometer-agent-central --
config-file /etc/ceilometer/ceilometer.conf & echo $!
>/opt/stack/status/stack/c
eilometer-acentral.pid; fg || echo "ceilometer-acentral failed to start" |
tee "
/opt/stack/status/stack/ceilometer-acentral.failure"
[1] 3837
/usr/local/bin/ceilometer-agent-central --config-file
/etc/ceilometer/ceilometer.conf
bash: /usr/local/bin/ceilometer-agent-central: No such file or directory
ceilometer-acentral failed to start
stack@d-p-c-local-01-2592:~/devstack$

Anyone any idea how to fix this?

Thanks,
-- 

*Eduard Biceri Matei*
__
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] Fwd: [cinder][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

[Eduard Matei]

Hi,

Trying to get more attention to this ...

We had our driver removed by commit:
https://github.com/openstack/cinder/commit/f0ab819732d77a8a6dd1a91422ac183ac4894419
due to no CI.

Pls let me know if there is something wrong so we can fix it asap so we can
have the driver back in Liberty (if possible).

The CI is commenting using the name "Open vStorage CI" instead of
"CloudFounders OpenvStorage CI".

Thanks,

Eduard
__
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][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

[Eduard Matei]

Hi,

Trying to get more attention to this ...

We had our driver removed by commit:
https://github.com/openstack/cinder/commit/f0ab819732d77a8a6dd1a91422ac183ac4894419
due to no CI.

Pls let me know if there is something wrong so we can fix it asap so we can
have the driver back in Liberty (if possible).

The CI is commenting using the name "Open vStorage CI" instead of
"CloudFounders OpenvStorage CI".

Thanks,

Eduard
__
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][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

[Eduard Matei]

Hi,

Trying to get more attention to this ...

Also,

The CI will (starting next week) be commenting using the name "Open
vStorage CI" instead of "CloudFounders OpenvStorage CI".

Thanks,

Eduard

On Mon, Aug 17, 2015 at 5:44 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi,
>
> We had our driver removed by commit:
> https://github.com/openstack/cinder/commit/f0ab819732d77a8a6dd1a91422ac183ac4894419
>  due to no CI.
>
> Last week we got it working again and it's been commenting for the last 3
> days continuously.
>
> A normal run looks like this:
>
> *08:40:37* Ran: 1265 tests in 2338. sec.*08:40:37*  - Passed: 
> 1156*08:40:37*  - Skipped: 109*08:40:37*  - Expected Fail: 0*08:40:37*  - 
> Unexpected Success: 0*08:40:37*  - Failed: 0*08:40:37* Sum of execute time 
> for each test: 3300.1602 sec.
>
> for this review:
>
> https://review.openstack.org/#/c/212144/
>
> and logs:
>
> http://packages.cloudfounders.com/ci_logs/44/212144/3/check/dsvm-tempest-full/f1c6f6a/
>
>
>
>
> Pls let me know if there is something wrong so we can fix it asap so we can 
> have the driver back in Liberty (if possible).
>
>
> Thanks,
>
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
>
>


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Hi,

In case someone is still interested, 32768 is the fix. The number of PEs
must be multiple of 1024 (not sure why).

Eduard
__
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-deb] Devstack stable/juno fails to install

[Eduard Matei]

Hi,

ATM our workaround is to manually pip install futures==2.2.0 before running
stack.sh

Any idea when an "official" fix will be available?

Thanks,
Eduard
__
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] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Hi,

Might be because volume backing size of 32G results in 8191 PE instead of
8192, so last volume create attempt sees only 1023 free extents.

Will retry with 32768M

Eduard
__
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] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Hi,

Further investigation shows there might be a relation between a test
failing because it can't upload an image (most likely because there's not
enough space left) and another test failing because lvm doesn't have enough
extents - at the same time (due to tests running on two workers). So if
these tests run at the same time, they will both fail.

I increased VOLUME_BACKING_FILE_SIZE to 32G but still same error.

Any idea how to fix this?
Can i increase the number of "extents"? (how?) Or can i increase the disk
size of the image? (again how?)

Thanks,

Eduard
__
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][ThirdPartyCI]CloudFounders OpenvStorage CI - request to re-add the cinder driver

[Eduard Matei]

Hi,

We had our driver removed by commit:
https://github.com/openstack/cinder/commit/f0ab819732d77a8a6dd1a91422ac183ac4894419
 due to no CI.

Last week we got it working again and it's been commenting for the last 3
days continuously.

A normal run looks like this:

*08:40:37* Ran: 1265 tests in 2338. sec.*08:40:37*  - Passed:
1156*08:40:37*  - Skipped: 109*08:40:37*  - Expected Fail: 0*08:40:37*
 - Unexpected Success: 0*08:40:37*  - Failed: 0*08:40:37* Sum of
execute time for each test: 3300.1602 sec.

for this review:

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

and logs:

http://packages.cloudfounders.com/ci_logs/44/212144/3/check/dsvm-tempest-full/f1c6f6a/




Pls let me know if there is something wrong so we can fix it asap so
we can have the driver back in Liberty (if possible).


Thanks,


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.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

Re: [openstack-dev] [openstack-deb] Devstack stable/juno fails to install

[Eduard Matei]

Hi,

It doesn't seem to help, install still fails with same error.

Thanks,
Eduard
__
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] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Hi,

I can't find any way to change the image size of the vm used for testing
(it's been created using nodepool-dib and managed by nodepoold).

Anyway, tests are still (randomly) failing with lvm error (Volume group
"stack-volumes-lvmdriver-1" has insufficient free space (1023 extents):
1024 required.\n')

Any idea how to fix this?

Thanks,

Eduard
__
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] [openstack-deb] Devstack stable/juno fails to install

[Eduard Matei]

Hi,

I noticed that devstack stable/juno fails to install on our CI with error:

2015-08-17 01:55:59.794 | + /usr/local/bin/cinder-manage db sync
2015-08-17 01:55:59.911 | Traceback (most recent call last):
2015-08-17 01:55:59.911 |   File "/usr/local/bin/cinder-manage", line
4, in 
2015-08-17 01:55:59.911 |
__import__('pkg_resources').require('cinder==2014.2.3')
2015-08-17 01:55:59.911 |   File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 3084, in 
2015-08-17 01:55:59.911 | @_call_aside
2015-08-17 01:55:59.911 |   File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 3070, in _call_aside
2015-08-17 01:55:59.911 | f(*args, **kwargs)
2015-08-17 01:55:59.911 |   File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 3097, in _initialize_master_working_set
2015-08-17 01:55:59.912 | working_set = WorkingSet._build_master()
2015-08-17 01:55:59.912 |   File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 653, in _build_master
2015-08-17 01:55:59.912 | return cls._build_from_requirements(__requires__)
2015-08-17 01:55:59.912 |   File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 666, in _build_from_requirements
2015-08-17 01:55:59.912 | dists = ws.resolve(reqs, Environment())
2015-08-17 01:55:59.912 |   File
"/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 839, in resolve
2015-08-17 01:55:59.912 | raise DistributionNotFound(req, requirers)
2015-08-17 01:55:59.912 | pkg_resources.DistributionNotFound: The
'futures<=2.2.0,>=2.1.6' distribution was not found and is required by
taskflow


Local.conf:
[[local|localrc]]
HOST_IP=*
FLAT_INTERFACE=eth0
FIXED_RANGE=*
FIXED_NETWORK_SIZE=62
FLOATING_RANGE=*
MULTI_HOST=1
LOGFILE=/opt/stack/logs/stack.sh.log
ADMIN_PASSWORD=*
MYSQL_PASSWORD=*
RABBIT_PASSWORD=*
SERVICE_PASSWORD=*
SERVICE_TOKEN=*



CINDER_BRANCH=2014.2.3
GLANCE_BRANCH=2014.2.3
HEAT_BRANCH=2014.2.3
HORIZON_BRANCH=2014.2.3
KEYSTONE_BRANCH=2014.2.3
NEUTRON_BRANCH=2014.2.3
NOVA_BRANCH=2014.2.3
SWIFT_BRANCH=2014.2.3
TROVE_BRANCH=2014.2.3
REQUIREMENTS_BRANCH=stable/juno


Thanks,
Eduard
-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.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

Re: [openstack-dev] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Thanks,
I will try to increase the size of the dsvm disk, maybe that will help.

No idea about the image size.
The problem is that not all test runs fail, so it's not easy to trace.

Eduard
__
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] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Thanks,
I didn't see that errror, seems to be caused by swift:
2015-08-17 03:13:43.940 2312 ERROR glance.api.v1.upload_utils
BackendException: Failed to add object to Swift.

I'll investigate further.
But what about the lvmdriver-1 error? Isn't that related.

Thanks,
Eduard
__
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] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Hi,

Not sure what snippet you mean but here are all the logs for the failed
test run:
http://packages.cloudfounders.com/ci_logs/01/213501/3/check/dsvm-tempest-full/37aa6fe/
(console.html and c-vol.txt show more details).

Thanks,
Eduard
__
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] [third-party-ci]Tests randomly failing because of lvm

[Eduard Matei]

Hi,

I'm working on getting our CI working again, and i left it running over the
weekend.
Of the 50 jobs it ran. 6 of them failed because of different tests failed,
but all with the same cause
"tempest.exceptions.VolumeBuildErrorException"

Looking in c-vol log i see "Volume group "stack-volumes-lvmdriver-1" has
insufficient free space (1023 extents): 1024 required.\n'" (for that test)

I have VOLUME_BACKING_FILE_SIZE=32G
and i checked vgdisplay and it shows:

sudo vgdisplay

--- Volume group ---

VG Name   stack-volumes-lvmdriver-1

...

VG Size   32.00 GiB

Total PE  8191


How can i fix this?


Thanks,


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.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

Re: [openstack-dev] ][third-party-ci]Running custom code before tests

[Eduard Matei]

Hi,

I think you pointed me to the wrong file, the devstack-gate yaml (and line
2201 contains "timestamps").
I need an example of how to configure tempest to use my driver.

I tried EXPORT in the jenkins job (before executing dsvm shell script) but
looking at the tempest.txt (log) it shows that it still uses the defaults.
How do i overwrite those defaults?

Thanks,

Eduard
__
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] ][third-party-ci]Running custom code before tests

[Eduard Matei]

Hi,

Found some more info (finally): i added a function in the script part in
the jenkins job and an export -f and it seems it's being called, so now my
backend is installed and configured.

I'm now trying to configure cinder to use my driver when running but i
couldn't find a way to configure it.
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#How_do_I_configure_DevStack_so_my_Driver_Passes_Tempest.3F
mentions "Sample local.conf". How do i edit that file?

I tried exporting TEMPEST_VOLUME_DRIVER... but still the tests seem to use
the default driver.

Thanks,

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.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

Re: [openstack-dev] ][third-party-ci]Running custom code before tests

[Eduard Matei]

Hi,

Replying to my own post... i found how/where to put the "pre_test_hook" (in
the jenkins job, in the step that executes the devstack-vm script)

The problem is that now i need to execute code BETWEEN installation of
devstack and start of tests.

Is there a hook i can define that will be executed after devstack installed
but before tests start?

Thanks,

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.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] ][third-party-ci]Running custom code before tests

[Eduard Matei]

Hi,

I managed to get the jobs triggered, i read
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers but i can't
figure out where to put the code for pre_test_hook so i can setup my
backend.

Thanks,

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*
__
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] [third-party-ci]Issue with running "noop-check-communication"

[Eduard Matei]

Thanks,
Indeed running on a slave did the trick.

Strange how i missed that part in the README.

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.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] [third-party-ci]Issue with running "noop-check-communication"

[Eduard Matei]

Hi,

We're in the process of rebuilding the Jenkins CI for Cinder and i'm stuck
at testing the "noop" job.
I've setup using the latest changes from os-ext-testing and
os-ext-testing-data using project-config, jjb and dib and i have a jenkins
running which has the 2 jobs defined and i have 3 slaves attached (from a
devstack - cloud provider).

Now when i make changes to sandbox (to test it) i see jobs being triggered
but they hang in Jenkins:
pending—There are no nodes with the label ‘’


I checked the job config and it shows "Restrict where this project can be
run/Label expression "master" / Slaves in label: 1" and i can trigger it
manually and it shows "Waiting for next available executor on master"  -
although there are 4 executors in "Idle".

Any ideas?

Thanks,
-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*
__
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]Restrict volume creation based on type

[Eduard Matei]

Hi,

Thanks for your replies.
Got back to the team and tried to get more input:
- the volume is created correctly (i misunderstood that part)
- the problem is that (sometimes) the instance gets spawned on the 3rd node
(which doesn't have the driver configured).
This might be because of the availability zone (volume has AZ nova,
instance has AZ nova, which refers to all 3 nodes).
I was not able to reproduce this on L, team tried with J, i will retry with
J and K and get back to you.

@Gorka: no, the hostnames are different
@Duncan: the extra-specs are "volume_backend_name: swift200"

Thanks,

Eduard
__
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]Restrict volume creation based on type

[Eduard Matei]

Hi,

Forgot to mention, indeed we configured extra_specs: volume_backend_name.
The problem is that a volume of this type can get scheduled on a node where
c-vol is not configured with this backend.

F.e.: I have 3 storage nodes (c-vol) and two have the driver configured,
the third one doesn't have it; when i try to create a volume of this type,
sometimes the c-vol on third node gets the call, and it fails because the
driver is not configured.

Maybe we didn't configure something properly, i tried looking at c-sch but
i can't figure out why the third node got chosen.

Thanks,

Eduard
__
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]Cinder services issues after add/remove/add driver

[Eduard Matei]

Hi,

Potential bug, but still investigating:
- configured a driver on cinder (besides lvm) - all ok
[service1]
volume_driver = cinder.volume.drivers.openvstorage.OVSVolumeDriver
volume_backend_name = service1
vpool_name = service1
- removed it, restarted services - all ok (cinder service-list shows the
service as enabled and down)
- configured ANOTHER driver on cinder (similar to first) - new volumes
stuck in status "creating"

Tried "cinder service-disable", service showed "disabled" and "up" (?) then
later "disabled" and "down".
Tried changing in mysql (deleted = 1, then actually deleted).

Cinder-scheduler logs:
- Choosing NODE1@service2#service2
- Flow 'volume_create_scheduler' (737556d0-a096-4639-899a-4bfd1c5bf166)
transitioned into state 'SUCCESS' from state 'RUNNING'
but the volume remains in status "creating", nothing is logged in c-vol on
any node

Details:
- 3 nodes setup, Devstack 2014.2.2, Ubuntu 14.04
- c-api, c-sch and c-vol running on all 3 nodes

Any help appreciated.

Thanks,

Eduard
__
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]Restrict volume creation based on type

[Eduard Matei]

Hi,

We've been testing a multi-node setup with our driver and ended up in a
strange situation:
- having a driver configured on multiple cinder nodes (But not all)
- having a volume type (available)
- creating a volume with specified volume type causes the volume to be
created (attempted) on a node where the driver is not configured.

We found something called "storage_availability_zone" but not quite
understood it, and it looks like an extra choice in the "Create volume
wizard" (which can be skipped/forgotten).

So, question:
- can we "force" a volume type to be tied to specific nodes? (something
like availability zones, but determined based on volume type, not a
separate setting)


Thanks,

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.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

Re: [openstack-dev] ThirdPartyCI: Tempest job fails with "Unexpected termination of the channel"

[Eduard Matei]

Hi,

After some more tests i was able to link the failure of the jenkins job
with the errors in dmesg :
[Fri Jun 12 11:04:37 2015] br100: port 2(vnet1) entered disabled state
[Fri Jun 12 11:04:37 2015] device vnet1 left promiscuous mode
[Fri Jun 12 11:04:37 2015] br100: port 2(vnet1) entered disabled state
[Fri Jun 12 11:04:39 2015] type=1400 audit(1434100171.300:3539):
apparmor="STATUS" operation="profile_remove" profile="unconfined"
name="libvirt-a0bc3c23-288b-4e68-9687-bdbc9f254ecc" pid=37045
comm="apparmor_parser"
[Fri Jun 12 11:04:50 2015] type=1400 audit(1434100182.384:3540):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="libvirt-48989eef-c01f-40f4-a711-426728d42043" pid=37114
comm="apparmor_parser"
[Fri Jun 12 11:04:50 2015] device vnet1 entered promiscuous mode
[Fri Jun 12 11:04:50 2015] br100: port 2(vnet1) entered forwarding state
[Fri Jun 12 11:04:50 2015] br100: port 2(vnet1) entered forwarding state
[Fri Jun 12 11:04:52 2015] kvm [37307]: vcpu0 disabled perfctr wrmsr: 0xc1
data 0x

Syslog shows different times (5 minutes difference)

Jun 12 11:09:30 ovs-ci01 kernel: [1305189.753332] br100: port 2(vnet1)
entered disabled state
Jun 12 11:09:30 ovs-ci01 kernel: [1305189.753532] device vnet1 left
promiscuous mode
Jun 12 11:09:30 ovs-ci01 kernel: [1305189.753538] br100: port 2(vnet1)
entered disabled state

Jun 12 11:09:42 ovs-ci01 kernel: [1305202.152199] br100: port 2(vnet1)
entered forwarding state
Jun 12 11:09:42 ovs-ci01 kernel: [1305202.152205] br100: port 2(vnet1)
entered forwarding state

Job failed at ~ 11:08.

All VMs (the devstack slave) are connected to br100
Jenkins master uses vnet0 but the public ip is manually added to br100 and
NATed using iptables while the devstack vm uses vnet1 (which is bridged
with eth0).

6: br100:  mtu 1500 qdisc noqueue state UP
group default
link/ether 00:1e:67:4f:71:a5 brd ff:ff:ff:ff:ff:ff
inet 10.140.0.1/24 brd 10.140.0.255 scope global br100  <- HOST private
IP
   valid_lft forever preferred_lft forever
inet 10.100.128.2/16 brd 10.100.255.255 scope global br100  <- HOST
public IP
   valid_lft forever preferred_lft forever
inet 10.100.128.129/32 scope global br100  <- Guest (devstack vm,
managed by n-net) public IP (floating)
   valid_lft forever preferred_lft forever
inet 10.100.128.3/16 scope global secondary br100 <- Jenkins master,
NATed to private ip (via virbr0 through iptables)
   valid_lft forever preferred_lft forever
inet6 fe80::494:ccff:fe72:8015/64 scope link
   valid_lft forever preferred_lft forever

bridge name bridge id STP enabled interfaces
br100 8000.001e674f71a5 no eth0
vnet1

Thanks,
Eduard
__
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] ThirdPartyCI: Tempest job fails with "Unexpected termination of the channel"

[Eduard Matei]

Short story:
- all runs of the tempest job are failing after ~ 1,5 - 2 hrs with  "FATAL:
java.io.IOException: Unexpected termination of the channel" and jenkins
logs "SEVERE: I/O error in channel d-p-c-local_01-1655 java.io.IOException:
Unexpected termination of the channel"

Long story:
- Host is 4 core Intel Xeon, 32GB RAM, 3x1TB HDD
-- devstack is 2015.1.1, networking is done via n-net
- Jenkins master is a VM, 2 core, 8 GB RAM, 500 GB disk
-- not managed through devstack, but using virsh, networking done manually
via iptables
- test slaves are VMs, m1.large (4 VCPU, 8 GB RAM, trusty), managed by
nodepool

Load on master is usually around 6-7, memory usage around 90%, little
swapping.

I tried increasing ClientAliveInterval/ServerAliveInterval and
ClientAliveCountMax/ServerAliveCountMax on both the Jenkins VM and on the
test vm (using the job to configure), but it still fails with the above
mentioned error.

On the host, dmesg is full of: (not sure if directly related to this)
[1037245.231196] br100: port 2(vnet1) entered disabled state
followed by
[1037259.147672] br100: port 2(vnet1) entered forwarding state

I think it might be something related to networking on the host itself but
i couldn't figure it yet.

Any suggestion on what to try next?

Thanks,
Eduard
__
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] Nodepool: puppet puts wrong key in authorized_keys in slave

[Eduard Matei]

Hi,

Seems i missed a step, NODEPOOL_SSH_KEY was not exported so the image was
not properly configured.
Now i got an instance that is added to the jenkins master as slave and it's
online.

Thanks.
Eduard
__
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] Nodepool: puppet puts wrong key in authorized_keys in slave

[Eduard Matei]

Hi Ramy,

I tried the disk-image-builder and now i can't ssh with any user with any
key.
Everytime i get  "Permission denied (publickey).".

Here's my nodepool.yaml:


script-dir: /etc/nodepool/scripts
elements-dir: /etc/nodepool/elements
images-dir: /opt/nodepool_dib
dburi: 'mysql://nodepool:changeme@localhost/nodepool'

cron:
  cleanup: '*/1 * * * *'
  check: '*/15 * * * *'
  image-update: '14 14 * * *'

zmq-publishers:
  - tcp://localhost:

gearman-servers:
  - host: 127.0.0.1

labels:
  - name: d-p-c
image: dpc
min-ready: 1
providers:
  - name: local_01

diskimages:
- name: dpc
  elements:
- ubuntu
- vm
- openstack-repos
- puppet
- nodepool-base
- node-devstack
  release: trusty
  env-vars:
TMPDIR: /opt/dib_tmp
DIB_IMAGE_CACHE: /opt/dib_cache

providers:
  - name: local_01
username: 'admin'
password: '**'
auth-url: 'http://10.100.128.2:5000/v2.0'
project-id: 'admin'
max-servers: 1
keypair: 'jenkins'
images:
  - name: dpc
min-ram: 8192
diskimage: dpc
username: jenkins
private-key: '/home/nodepool/.ssh/id_rsa'

targets:
  - name: local-jenkins
jenkins:
  url: 'http://localhost:8080/'
  user: 'jenkins'
  apikey: '*'
  credentials-id: '*'


Thanks,
Eduard
__
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] Nodepool: puppet puts wrong key in authorized_keys in slave

[Eduard Matei]

Hi,

Recently i updated nodepool and the devstack where it's supposed to create
slaves.
After some minor issues i managed to get it running, and it is able to
create an image and i can login to an instance created from that image
using user "ubuntu" (image is trusty).

While trying to add the slave to jenkins it fails with ssh error.
After a little debugging i found that in the authorized_keys of user ubuntu
is the correct key (so i can ssh as user ubuntu) - the one i put in the
Key-pair, but for user jenkins there is another key which i can't find for
any user in the jenkins master.

The authorized_keys for user jenkins contains:
# HEADER: This file was autogenerated at 2015-05-29 12:35:49 +
# HEADER: by puppet.  While it can still be managed manually, it
# HEADER: is definitely not recommended.
... then the key... and at the end: jenkins-master-2014-04-24

While for user ubuntu:
... the key from user jenkins on the master... and at the
end: jenkins@jenkins-cinderci

I didn't make any changes to nodepool.yaml or the keys themselves.

I've been looking inside nodepool's scripts, but this looks like a puppet
script and i don't know how to debug those.

Thanks,

Eduard
__
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] Nodepool: puppet fails to create image

[Eduard Matei]

Thanks,
I updated nodepool and nodepool scripts and now it seems the image is
building.

Eduard


On Thu, May 28, 2015 at 6:39 PM, Jeremy Stanley  wrote:

> On 2015-05-28 11:58:43 +0300 (+0300), Eduard Matei wrote:
> > We had some issues with jenkins/devstack so i updated both the jenkins
> > version and the devstack.
> > When starting nodepool it tries to create a new image but it fails after
> ~5
> > minutes:
> >
> > 2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: + sudo
> > puppet apply --detailed-exitcodes
> --modulepath=/root/system-config/modules:/
> > etc/puppet/modules -e 'class
> {'\''openstack_project::single_use_slave'\'':
> > sudo => true, thin => true, python3 => false, include_pypy => false,
> all_my
> > sql_privs => false, }'
> [...]
> > 2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: Error:
> > Invalid parameter python3 on Class[Openstack_project::Single_use_slave]
> at l
> > ine 1 on node d-p-c-1432802582.template.openstack.org
> [...]
> > Anyone has any idea how to fix this?
> >
> > Nodepool was not updated.
> > Jenkins is 1.596.3
> > Devstack is 2015.1.1
>
> Looks like you've pulled in a new version of our openstack_project
> Puppet module which includes https://review.openstack.org/151714 but
> have not updated your nodepool prep scripts since
> https://review.openstack.org/151715 went in almost 4 months ago to
> support it.
> --
> Jeremy Stanley
>
> __
> 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
>



-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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] Nodepool: puppet fails to create image

[Eduard Matei]

Hi,

We had some issues with jenkins/devstack so i updated both the jenkins
version and the devstack.
When starting nodepool it tries to create a new image but it fails after ~5
minutes:

2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: + sudo
puppet apply --detailed-exitcodes --modulepath=/root/system-config/modules:/
etc/puppet/modules -e 'class {'\''openstack_project::single_use_slave'\'':
sudo => true, thin => true, python3 => false, include_pypy => false, all_my
sql_privs => false, }'
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: Warning:
Setting templatedir is deprecated. See http://links.puppetlabs.com/env-set
tings-deprecations
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c:(at
/usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warn
ing')
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: Error:
Invalid parameter python3 on Class[Openstack_project::Single_use_slave] at l
ine 1 on node d-p-c-1432802582.template.openstack.org
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: Error:
Invalid parameter python3 on Class[Openstack_project::Single_use_slave] at l
ine 1 on node d-p-c-1432802582.template.openstack.org
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: +
PUPPET_RET_CODE=1
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: + '[' 1
-eq 4 ']'
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: + '[' 1
-eq 6 ']'
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: + set -e
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: + cat
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: + sudo
mv /tmp/forwarding.conf /etc/unbound/
2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: mv:
cannot move ‘/tmp/forwarding.conf’ to ‘/etc/unbound/’: Not a directory
2015-05-28 10:49:21,509 ERROR nodepool.SnapshotImageUpdater: Exception
updating image d-p-c in local_01:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/nodepool/nodepool.py", line
862, in _run
self.updateImage(session)
  File "/usr/local/lib/python2.7/dist-packages/nodepool/nodepool.py", line
995, in updateImage
self.bootstrapServer(server, key, use_password=use_password)
  File "/usr/local/lib/python2.7/dist-packages/nodepool/nodepool.py", line
1091, in bootstrapServer
(set_path, env_vars, self.image.setup, server['name']))
  File "/usr/local/lib/python2.7/dist-packages/nodepool/sshclient.py", line
55, in ssh
% (action, command, out, err))
Exception: Unable to run setup script
command: export
PATH=/usr/local/sbin:/sbin:/usr/sbin:/usr/local/bin:/bin:/usr/bin; cd
/opt/nodepool-scripts &&  NODEPOOL_NO_PROXY="" NODEPOOL_HTTPS_PROXY=""
NODEPOOL_SSH_KEY="" NODEPOOL_HTTP_PROXY="" ./prepare_node_devstack.sh
d-p-c-1432802582.template.openstack.org
stdout:
stderr:

Anyone has any idea how to fix this?

Nodepool was not updated.
Jenkins is 1.596.3
Devstack is 2015.1.1

Thanks,
Eduard
__
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][oslo_messaging]Enabling notifications from nova

[Eduard Matei]

Thanks Swann, that did the trick.

Ed

On Thu, Apr 16, 2015 at 2:44 PM, Swann Croiset  wrote:

> Hi,
> try to configure nova.conf:
>
> [DEFAULT]
> notification_driver=messaging
>
> BR
>
>
> 2015-04-16 11:04 GMT+02:00 Eduard Matei :
>
>>
>>
>> Hi,
>>
>> I've been trying to enable nova notifications on various actions, but
>> nothing is actually sent.
>> I found the cause in the _notify method
>> of /usr/local/lib/python2.7/dist-packages/oslo_messaging/notify/notifier.py.
>> There it performs a check "if self._driver_mgr.extensions" which always
>> returns False.
>> I removed the check and i found the following traceback in n-api:
>>
>>
>> 2015-04-16 10:58:17.955 ERROR nova.notifications
>> [req-2909db4c-30f4-4278-8472-ec5c9440778f admin admin] [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05
>> f] Failed to send state update notification
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f] Traceback (most recent call last):
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f]   File
>> "/opt/stack/nova/nova/notifications.py", line
>>  151, in send_update
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f] old_display_name=old_display_name)
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f]   File
>> "/opt/stack/nova/nova/notifications.py", line
>>  253, in _send_instance_update_notification
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f] 'compute.instance.update',
>> payload)
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f]   File
>> "/usr/local/lib/python2.7/dist-packages/oslo_
>> messaging/notify/notifier.py", line 231, in info
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f] self._notify(ctxt, event_type,
>> payload, 'INFO')
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f]   File
>> "/usr/local/lib/python2.7/dist-packages/oslo_
>> messaging/notify/notifier.py", line 313, in _notify
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f] super(_SubNotifier,
>> self)._notify(ctxt, event_ty
>> pe, payload, priority)
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f]   File
>> "/usr/local/lib/python2.7/dist-packages/oslo_
>> messaging/notify/notifier.py", line 186, in _notify
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f] self._driver_mgr.map(do_notify)
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f]   File
>> "/usr/local/lib/python2.7/dist-packages/steve
>> dore/extension.py", line 221, in map
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f] raise RuntimeError('No %s
>> extensions found' % se
>> lf.namespace)
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f] RuntimeError: No
>> oslo.messaging.notify.drivers exten
>> sions found
>> 2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
>> a902da95-6b42-4f71-a55e-818c1d02c05f]
>>
>>
>>
>> Looking in oslo directory and trying to import that module
>> (oslo.messaging.notify.drivers) but no success, that module doesn't exist.
>>
>> Anyone knows how to enable the notifications ?
>>
>> I found also in the Notifier __init__ the following:
>>
>>  self._driver_mgr = named.NamedExtensionManager(
>> 'oslo.messaging.notify.drivers',
>>
>> What should i put there so that the extensions can be loaded ? ( i tried
>> with oslo.messaging._drivers but same error: No oslo.messaging._drivers
>> extensions found).
>>
>> Thanks,
>> Eduard
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin

[openstack-dev] [nova][oslo_messaging]Enabling notifications from nova

[Eduard Matei]

Hi,

I've been trying to enable nova notifications on various actions, but
nothing is actually sent.
I found the cause in the _notify method
of /usr/local/lib/python2.7/dist-packages/oslo_messaging/notify/notifier.py.
There it performs a check "if self._driver_mgr.extensions" which always
returns False.
I removed the check and i found the following traceback in n-api:


2015-04-16 10:58:17.955 ERROR nova.notifications
[req-2909db4c-30f4-4278-8472-ec5c9440778f admin admin] [instance:
a902da95-6b42-4f71-a55e-818c1d02c05
f] Failed to send state update notification
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f] Traceback (most recent call last):
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f]   File
"/opt/stack/nova/nova/notifications.py", line
 151, in send_update
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f] old_display_name=old_display_name)
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f]   File
"/opt/stack/nova/nova/notifications.py", line
 253, in _send_instance_update_notification
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f] 'compute.instance.update',
payload)
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f]   File
"/usr/local/lib/python2.7/dist-packages/oslo_
messaging/notify/notifier.py", line 231, in info
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f] self._notify(ctxt, event_type,
payload, 'INFO')
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f]   File
"/usr/local/lib/python2.7/dist-packages/oslo_
messaging/notify/notifier.py", line 313, in _notify
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f] super(_SubNotifier,
self)._notify(ctxt, event_ty
pe, payload, priority)
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f]   File
"/usr/local/lib/python2.7/dist-packages/oslo_
messaging/notify/notifier.py", line 186, in _notify
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f] self._driver_mgr.map(do_notify)
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f]   File
"/usr/local/lib/python2.7/dist-packages/steve
dore/extension.py", line 221, in map
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f] raise RuntimeError('No %s
extensions found' % se
lf.namespace)
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f] RuntimeError: No
oslo.messaging.notify.drivers exten
sions found
2015-04-16 10:58:17.955 TRACE nova.notifications [instance:
a902da95-6b42-4f71-a55e-818c1d02c05f]



Looking in oslo directory and trying to import that module
(oslo.messaging.notify.drivers) but no success, that module doesn't exist.

Anyone knows how to enable the notifications ?

I found also in the Notifier __init__ the following:

 self._driver_mgr = named.NamedExtensionManager(
'oslo.messaging.notify.drivers',

What should i put there so that the extensions can be loaded ? ( i tried
with oslo.messaging._drivers but same error: No oslo.messaging._drivers
extensions found).

Thanks,
Eduard
__
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]Driver broken

[Eduard Matei]

Thanks,

Indeed, our CI doesn't test this code path, we focused mainly on our
internal functionality tests (which don't test for this), and the tempest
tests are not running.
This will be fixed asap.

Thanks everyone,
Eduard
__
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]Driver broken

[Eduard Matei]

Hi,

Indeed our CI runs, and it reported SUCCESS, but it didn't run the tempest
tests, only the openvstorage tests (my bad, looking into it as we speak).

Meanwhile i'll create a patch to fix this.

Thanks,
Eduard
__
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]Driver broken

[Eduard Matei]

Hi,

Just reported an issue: https://bugs.launchpad.net/cinder/+bug/1436367
Seems to be related to https://review.openstack.org/#/c/85847/ which
introduced another parameter to be passed to the driver, but our driver
didn't get updated so detach_volume fails for us.

How can we get this fixed asap?

Thanks,
Eduard
__
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][Cinder] Questions re progress

[Eduard Matei]

Hi Adam,

Disclaimer: i work for a company interested in providing solutions based on
openstack, but this email should not be considered marketing/promotional

Regarding your second question "Using Swift as a back-end for Cinder", we
already have a solution for this, a part of which is a Cinder driver
(already merged), and another part is our custom middle layer between swift
and fuse (available partially open-source, for free).
This solution allows you to use your swift cluster as shared storage for
your nova compute nodes (using cinder volume driver) so all nodes can see
all the volumes.

If you would like more details you can contact me at this email address.

*Eduard *
__
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] [devstack]Specific Juno version

[Eduard Matei]

Hi,
Indeed CINDER_BRANCH=2014.2.2 did the trick.
Will properly report the issues once we start testing on 2014.2.3.

Eduard
__
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] [devstack]Specific Juno version

[Eduard Matei]

Hi Ihar,
This is the error i see in c-vol screen:
2015-03-03 18:39:34.060 DEBUG taskflow.engines.action_engine.runner
[req-87db2771-5c25-4c9b-a3bc-f7a504468315 4af0a30fe2c14deb9f9cf341a97daa9f
1fbab1e235ff414abf249c741fb3c6c9] Exiting old state 'WAITING' in response
to event 'analyze' from (pid=29710) on_exit
/usr/local/lib/python2.7/dist-packages/taskflow/engines/action_engine/runner.py:156
2015-03-03 18:39:34.060 DEBUG taskflow.engines.action_engine.runner
[req-87db2771-5c25-4c9b-a3bc-f7a504468315 4af0a30fe2c14deb9f9cf341a97daa9f
1fbab1e235ff414abf249c741fb3c6c9] Entering new state 'ANALYZING' in
response to event 'analyze' from (pid=29710) on_enter
/usr/local/lib/python2.7/dist-packages/taskflow/engines/action_engine/runner.py:160
2015-03-03 18:39:34.061 CRITICAL cinder [-] TypeError: an integer is
required

2015-03-03 18:39:34.061 TRACE cinder Traceback (most recent call last):
2015-03-03 18:39:34.061 TRACE cinder   File
"/opt/stack/devstack/cinder/bin/cinder-volume", line 79, in 
2015-03-03 18:39:34.061 TRACE cinder launcher.wait()
2015-03-03 18:39:34.061 TRACE cinder   File
"/opt/stack/devstack/cinder/cinder/openstack/common/service.py", line 393,
in wait
2015-03-03 18:39:34.061 TRACE cinder self._respawn_children()
2015-03-03 18:39:34.061 TRACE cinder   File
"/opt/stack/devstack/cinder/cinder/openstack/common/service.py", line 381,
in _respawn_children
2015-03-03 18:39:34.061 TRACE cinder self._start_child(wrap)
2015-03-03 18:39:34.061 TRACE cinder   File
"/opt/stack/devstack/cinder/cinder/openstack/common/service.py", line 327,
in _start_child
2015-03-03 18:39:34.061 TRACE cinder os._exit(status)
2015-03-03 18:39:34.061 TRACE cinder TypeError: an integer is required
2015-03-03 18:39:34.061 TRACE cinder
2015-03-03 18:39:34.375 INFO cinder.openstack.common.service [-] Child
29710 exited with status 1
2015-03-03 18:39:34.378 INFO cinder.openstack.common.service [-] Started
child 29948
2015-03-03 18:39:34.380 INFO cinder.service [-] Starting cinder-volume node
(version 2014.2.3)

Regarding the disclaimer, that's the standard signature we have to use in
the company.

Thanks,
Eduard
__
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] [oslo_messaging]Notification listener for nova

[Eduard Matei]

Hi,
I'm trying to listen to events of type "compute.instance.*" (e.g.
compute.instance.update).
I tried the following code:

from oslo_config import cfg
import oslo_messaging

class NotificationEndpoint(object):
filter_rule =
oslo_messaging.NotificationFilter(publisher_id='compute.*',

event_type='compute.instance.update',
context={'ctxt_key':
'regexp'})

def info(self, ctxt, publisher_id, event_type, payload, metadata):
print(payload)

def warn(self, ctxt, publisher_id, event_type, payload, metadata):
print(payload)

transport = oslo_messaging.get_transport(cfg.CONF)
targets = [oslo_messaging.Target(topic='notifications'),
   oslo_messaging.Target(topic='notifications_bis')]
endpoints = [NotificationEndpoint()]
pool = "listener-workers"
server = oslo_messaging.get_notification_listener(transport=transport,
  targets=targets,
  endpoints=endpoints,
  pool=pool)
server.start()
server.wait()

then, from Horizon i changed an instance name (which should call
_send_instance_update_notification)  but i didn't get any notification.

Any ideas?
Thanks,

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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] [devstack]Specific Juno version

[Eduard Matei]

Hi,

Is there a way to specify the Juno version to be installed using devstack.
For now we can only specify stable/juno
*git clone -b stable/juno https://github.com/openstack-dev/devstack.git
 /opt/stack/devstack*
but this installs 2014.2.3 which appears to be still under development (it
gives some errors).
How can we specify 2014.2.2 for components (e.g. cinder)?

Thanks,
Eduard

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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][horizon]Proper error handling/propagation to UI

[Eduard Matei]

Thanks Avishay.
In our case the middle layer (our storage appliance) doesn't allow a
snapshot to be deleted if it has clones due to an internal implementation
that tries to optimize storage by using a "Dependency tree" where the base
volume is the root of the tree and snapshots or clones are nodes and their
clones are leaves of. So deleting a middle point (node) is impossible
without deleting all the "children".

Eduard

On Mon, Mar 2, 2015 at 8:10 PM, Avishay Traeger 
wrote:

> Sorry, I meant to say that the expected behavior is that volumes are
> independent entities, and therefore you should be able to delete a snapshot
> even if it has volumes created from it (just like you should be able to
> delete a volume that has clones from it).  The exception is that Cinder
> will not permit you to delete a volume that has snapshots.
>
> On Mon, Mar 2, 2015 at 3:22 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>> @Duncan:
>> I tried with lvmdriver-1, fails with error:
>> ImageCopyFailure: Failed to copy image to volume: qemu-img:
>> /dev/mapper/stack--volumes--lvmdriver--1-volume--e8323fc5--8ce4--4676--bbec--0a85efd866fc:
>> error while converting raw: Could not open device: Permission denied
>>
>> It's been configured with 2 drivers (ours, and lvmdriver), but our driver
>> works, so not sure where it fails.
>>
>> Eduard
>>
>> On Mon, Mar 2, 2015 at 8:23 AM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>> Thanks
>>> @Duncan: I'll try with the lvm driver.
>>> @Avishay, i'm not trying to delete a volume created from a snapshot, i'm
>>> trying to delete a snapshot that has volumes created from it (actually i
>>> need to prevent this action and properly report the cause of the failure:
>>> SnapshotIsBusy).
>>>
>>>
>>> Eduard
>>>
>>> On Mon, Mar 2, 2015 at 7:57 AM, Avishay Traeger >> > wrote:
>>>
>>>> Deleting a volume created from a snapshot is permitted.  Performing
>>>> operations on a volume created from snapshot should have the same behavior
>>>> as volumes created from volumes, images, or empty (no source).  In all of
>>>> these cases, the volume should be deleted, regardless of where it came
>>>> from.  Independence from source is one of the differences between volumes
>>>> and snapshots in Cinder.  The driver must take care to ensure this.
>>>>
>>>> As to your question about propagating errors without changing an
>>>> object's state, that is unfortunately not doable in Cinder today (or any
>>>> other OpenStack project as far as I know).  The object's state is currently
>>>> the only mechanism for reporting an operation's success or failure.
>>>>
>>>> On Sun, Mar 1, 2015 at 6:07 PM, Duncan Thomas 
>>>> wrote:
>>>>
>>>>> I thought that case should be caught well before it gets to the
>>>>> driver. Can you retry with the LVM driver please?
>>>>>
>>>>> On 27 February 2015 at 10:48, Eduard Matei <
>>>>> eduard.ma...@cloudfounders.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We've been testing our cinder driver extensively and found a strange
>>>>>> behavior in the UI:
>>>>>> - when trying to delete a snapshot that has clones (created volume
>>>>>> from snapshot) and error is raised in our driver which turns into
>>>>>> "error_deleting" in cinder and the UI; further actions on that snapshot 
>>>>>> are
>>>>>> impossible from the ui, the user has to go to CLI and do cinder
>>>>>> snapshot-reset-state to be able to delete it (after having deleted the
>>>>>> clones)
>>>>>> - to help with that we implemented a check in the driver and now we
>>>>>> raise exception.SnapshotIsBusy; now the snapshot remains available (as it
>>>>>> should be) but no error "bubble" is shown in the UI (only the green one:
>>>>>> Success. Scheduled deleting of...). So the user has to go to c-vol screen
>>>>>> and check the cause of the error
>>>>>>
>>>>>> So question: how should we handle this so that
>>>>>> a. The snapshot remains in state "available"
>>>>>> b. An error bubble is shown in the UI stating the cause.
>>>>>>
>>

Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI

[Eduard Matei]

@Duncan:
I tried with lvmdriver-1, fails with error:
ImageCopyFailure: Failed to copy image to volume: qemu-img:
/dev/mapper/stack--volumes--lvmdriver--1-volume--e8323fc5--8ce4--4676--bbec--0a85efd866fc:
error while converting raw: Could not open device: Permission denied

It's been configured with 2 drivers (ours, and lvmdriver), but our driver
works, so not sure where it fails.

Eduard

On Mon, Mar 2, 2015 at 8:23 AM, Eduard Matei  wrote:

> Thanks
> @Duncan: I'll try with the lvm driver.
> @Avishay, i'm not trying to delete a volume created from a snapshot, i'm
> trying to delete a snapshot that has volumes created from it (actually i
> need to prevent this action and properly report the cause of the failure:
> SnapshotIsBusy).
>
>
> Eduard
>
> On Mon, Mar 2, 2015 at 7:57 AM, Avishay Traeger 
> wrote:
>
>> Deleting a volume created from a snapshot is permitted.  Performing
>> operations on a volume created from snapshot should have the same behavior
>> as volumes created from volumes, images, or empty (no source).  In all of
>> these cases, the volume should be deleted, regardless of where it came
>> from.  Independence from source is one of the differences between volumes
>> and snapshots in Cinder.  The driver must take care to ensure this.
>>
>> As to your question about propagating errors without changing an object's
>> state, that is unfortunately not doable in Cinder today (or any other
>> OpenStack project as far as I know).  The object's state is currently the
>> only mechanism for reporting an operation's success or failure.
>>
>> On Sun, Mar 1, 2015 at 6:07 PM, Duncan Thomas 
>> wrote:
>>
>>> I thought that case should be caught well before it gets to the driver.
>>> Can you retry with the LVM driver please?
>>>
>>> On 27 February 2015 at 10:48, Eduard Matei <
>>> eduard.ma...@cloudfounders.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> We've been testing our cinder driver extensively and found a strange
>>>> behavior in the UI:
>>>> - when trying to delete a snapshot that has clones (created volume from
>>>> snapshot) and error is raised in our driver which turns into
>>>> "error_deleting" in cinder and the UI; further actions on that snapshot are
>>>> impossible from the ui, the user has to go to CLI and do cinder
>>>> snapshot-reset-state to be able to delete it (after having deleted the
>>>> clones)
>>>> - to help with that we implemented a check in the driver and now we
>>>> raise exception.SnapshotIsBusy; now the snapshot remains available (as it
>>>> should be) but no error "bubble" is shown in the UI (only the green one:
>>>> Success. Scheduled deleting of...). So the user has to go to c-vol screen
>>>> and check the cause of the error
>>>>
>>>> So question: how should we handle this so that
>>>> a. The snapshot remains in state "available"
>>>> b. An error bubble is shown in the UI stating the cause.
>>>>
>>>> Thanks,
>>>> Eduard
>>>>
>>>> --
>>>>
>>>> *Eduard Biceri Matei, Senior Software Developer*
>>>> www.cloudfounders.com
>>>>  | eduard.ma...@cloudfounders.com
>>>>
>>>>
>>>>
>>>> *CloudFounders, The Private Cloud Software Company*
>>>>
>>>> Disclaimer:
>>>> This email and any files transmitted with it are confidential and intended 
>>>> solely for the use of the individual or entity to whom they are addressed.
>>>> If you are not the named addressee or an employee or agent responsible for 
>>>> delivering this message to the named addressee, you are hereby notified 
>>>> that you are not authorized to read, print, retain, copy or disseminate 
>>>> this message or any part of it. If you have received this email in error 
>>>> we request you to notify us by reply e-mail and to delete all electronic 
>>>> files of the message. If you are not the intended recipient you are 
>>>> notified that disclosing, copying, distributing or taking any action in 
>>>> reliance on the contents of this information is strictly prohibited.
>>>> E-mail transmission cannot be guaranteed to be secure or error free as 
>>>> information could be intercepted, corrupted, lost, destroyed, arrive late 
>>>> or incomplete, or contain viruses. The sender therefore does not accept 
>>>> liability

Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI

[Eduard Matei]

Thanks
@Duncan: I'll try with the lvm driver.
@Avishay, i'm not trying to delete a volume created from a snapshot, i'm
trying to delete a snapshot that has volumes created from it (actually i
need to prevent this action and properly report the cause of the failure:
SnapshotIsBusy).


Eduard

On Mon, Mar 2, 2015 at 7:57 AM, Avishay Traeger 
wrote:

> Deleting a volume created from a snapshot is permitted.  Performing
> operations on a volume created from snapshot should have the same behavior
> as volumes created from volumes, images, or empty (no source).  In all of
> these cases, the volume should be deleted, regardless of where it came
> from.  Independence from source is one of the differences between volumes
> and snapshots in Cinder.  The driver must take care to ensure this.
>
> As to your question about propagating errors without changing an object's
> state, that is unfortunately not doable in Cinder today (or any other
> OpenStack project as far as I know).  The object's state is currently the
> only mechanism for reporting an operation's success or failure.
>
> On Sun, Mar 1, 2015 at 6:07 PM, Duncan Thomas 
> wrote:
>
>> I thought that case should be caught well before it gets to the driver.
>> Can you retry with the LVM driver please?
>>
>> On 27 February 2015 at 10:48, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>> Hi,
>>>
>>> We've been testing our cinder driver extensively and found a strange
>>> behavior in the UI:
>>> - when trying to delete a snapshot that has clones (created volume from
>>> snapshot) and error is raised in our driver which turns into
>>> "error_deleting" in cinder and the UI; further actions on that snapshot are
>>> impossible from the ui, the user has to go to CLI and do cinder
>>> snapshot-reset-state to be able to delete it (after having deleted the
>>> clones)
>>> - to help with that we implemented a check in the driver and now we
>>> raise exception.SnapshotIsBusy; now the snapshot remains available (as it
>>> should be) but no error "bubble" is shown in the UI (only the green one:
>>> Success. Scheduled deleting of...). So the user has to go to c-vol screen
>>> and check the cause of the error
>>>
>>> So question: how should we handle this so that
>>> a. The snapshot remains in state "available"
>>> b. An error bubble is shown in the UI stating the cause.
>>>
>>> Thanks,
>>> Eduard
>>>
>>> --
>>>
>>> *Eduard Biceri Matei, Senior Software Developer*
>>> www.cloudfounders.com
>>>  | eduard.ma...@cloudfounders.com
>>>
>>>
>>>
>>> *CloudFounders, The Private Cloud Software Company*
>>>
>>> Disclaimer:
>>> This email and any files transmitted with it are confidential and intended 
>>> solely for the use of the individual or entity to whom they are addressed.
>>> If you are not the named addressee or an employee or agent responsible for 
>>> delivering this message to the named addressee, you are hereby notified 
>>> that you are not authorized to read, print, retain, copy or disseminate 
>>> this message or any part of it. If you have received this email in error we 
>>> request you to notify us by reply e-mail and to delete all electronic files 
>>> of the message. If you are not the intended recipient you are notified that 
>>> disclosing, copying, distributing or taking any action in reliance on the 
>>> contents of this information is strictly prohibited.
>>> E-mail transmission cannot be guaranteed to be secure or error free as 
>>> information could be intercepted, corrupted, lost, destroyed, arrive late 
>>> or incomplete, or contain viruses. The sender therefore does not accept 
>>> liability for any errors or omissions in the content of this message, and 
>>> shall have no liability for any loss or damage suffered by the user, which 
>>> arise as a result of e-mail transmission.
>>>
>>>
>>>
>>> __
>>> 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
>>>
>>>
>>
>>
>> --
>> Duncan Thomas
>>
>> __
>> OpenStack Developm

[openstack-dev] [cinder][horizon]Proper error handling/propagation to UI

[Eduard Matei]

Hi,

We've been testing our cinder driver extensively and found a strange
behavior in the UI:
- when trying to delete a snapshot that has clones (created volume from
snapshot) and error is raised in our driver which turns into
"error_deleting" in cinder and the UI; further actions on that snapshot are
impossible from the ui, the user has to go to CLI and do cinder
snapshot-reset-state to be able to delete it (after having deleted the
clones)
- to help with that we implemented a check in the driver and now we raise
exception.SnapshotIsBusy; now the snapshot remains available (as it should
be) but no error "bubble" is shown in the UI (only the green one: Success.
Scheduled deleting of...). So the user has to go to c-vol screen and check
the cause of the error

So question: how should we handle this so that
a. The snapshot remains in state "available"
b. An error bubble is shown in the UI stating the cause.

Thanks,
Eduard

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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] [thirdpartyCI][cinder] Question about certification

[Eduard Matei]

Thanks Duncan.
It's commenting and it works (meaning it runs and it's able to detect
errors). Sometimes it gives a FAILURE but that's either due to the patch
(rare) or due to devstack (often).

Also logs are visible and included in the comment.

Eduard

On Tue, Feb 24, 2015 at 2:31 PM, Duncan Thomas 
wrote:

> If it is commenting (and not failing all the time) then you're fine.
>
> On 24 February 2015 at 12:47, Eduard Matei  > wrote:
>
>> Hi,
>>
>> With the deadline for ThirdPartyCI coming we were wondering what should
>> we do next to ensure our CI is validated.
>>
>> One of the requirements of having a driver accepted in the repo is to
>> provide proof of a working CI.
>>
>> The question is: does the CI need voting rights (validated) , or just
>> check/comment to be considered "working"? If it needs validation, how do we
>> do that (i've asked a couple of mailing lists but either got no response or
>> got redirected to IRC - which due to timezone differences i found mostly
>> empty).
>>
>> Thanks,
>>
>> Eduard
>>
>> --
>>
>> *Eduard Biceri Matei, Senior Software Developer*
>> www.cloudfounders.com
>>  | eduard.ma...@cloudfounders.com
>>
>>
>>
>> *CloudFounders, The Private Cloud Software Company*
>>
>> Disclaimer:
>> This email and any files transmitted with it are confidential and intended 
>> solely for the use of the individual or entity to whom they are addressed.
>> If you are not the named addressee or an employee or agent responsible for 
>> delivering this message to the named addressee, you are hereby notified that 
>> you are not authorized to read, print, retain, copy or disseminate this 
>> message or any part of it. If you have received this email in error we 
>> request you to notify us by reply e-mail and to delete all electronic files 
>> of the message. If you are not the intended recipient you are notified that 
>> disclosing, copying, distributing or taking any action in reliance on the 
>> contents of this information is strictly prohibited.
>> E-mail transmission cannot be guaranteed to be secure or error free as 
>> information could be intercepted, corrupted, lost, destroyed, arrive late or 
>> incomplete, or contain viruses. The sender therefore does not accept 
>> liability for any errors or omissions in the content of this message, and 
>> shall have no liability for any loss or damage suffered by the user, which 
>> arise as a result of e-mail transmission.
>>
>>
>> __
>> 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
>>
>>
>
>
> --
> Duncan Thomas
>
> __
> 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
>
>


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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] [Devstack] Devstack Install broken

[Eduard Matei]

Hi,

Seems to be fixed now, your comments gave me an idea and i included a "cd
/opt/devstack" in the command for stack.sh, now it looks like this:
"HOME=/opt/stack && cd /opt/devstack && sudo -u stack
/opt/devstack/stack.sh"

Just as a side note, it was working yesterday, without cd /opt/devstack,
and it has been working for at least 1 month, so not sure what changed, but
it was on devstack side.

Thanks,
Eduard

On Fri, Feb 20, 2015 at 3:48 PM, M Ranga Swami Reddy 
wrote:

> I too got this problem very frequently.
>
>
>
> On Fri, Feb 20, 2015 at 4:32 PM, Eduard Matei
>  wrote:
> >
> > Hi,
> >
> > I'm trying to install devstack and it keeps failing with:
> >
> > 2015-02-20 07:26:12.693 | ++ is_fedora
> > 2015-02-20 07:26:12.693 | ++ [[ -z Ubuntu ]]
> > 2015-02-20 07:26:12.693 | ++ '[' Ubuntu = Fedora ']'
> > 2015-02-20 07:26:12.693 | ++ '[' Ubuntu = 'Red Hat' ']'
> > 2015-02-20 07:26:12.693 | ++ '[' Ubuntu = CentOS ']'
> > 2015-02-20 07:26:12.693 | ++ '[' Ubuntu = OracleServer ']'
> > 2015-02-20 07:26:12.693 | + [[ -d /var/cache/pip ]]
> > 2015-02-20 07:26:12.693 | + [[ ! -d /opt/stack/.wheelhouse ]]
> > 2015-02-20 07:26:12.693 | + source tools/build_wheels.sh
> > 2015-02-20 07:26:12.693 | /opt/devstack/stack.sh: line 688:
> > tools/build_wheels.sh: No such file or directory
> > 2015-02-20 07:26:12.693 | ++ exit_trap
> > 2015-02-20 07:26:12.693 | ++ local r=1
> > 2015-02-20 07:26:12.693 | +++ jobs -p
> > 2015-02-20 07:26:12.693 | ++ jobs=
> > 2015-02-20 07:26:12.693 | ++ [[ -n '' ]]
> > 2015-02-20 07:26:12.694 | ++ kill_spinner
> > 2015-02-20 07:26:12.694 | ++ '[' '!' -z '' ']'
> > 2015-02-20 07:26:12.694 | ++ [[ 1 -ne 0 ]]
> > 2015-02-20 07:26:12.694 | ++ echo 'Error on exit'
> > 2015-02-20 07:26:12.694 | Error on exit
> > 2015-02-20 07:26:12.694 | ++ [[ -z /opt/stack/logs ]]
> > 2015-02-20 07:26:12.694 | ++ /opt/devstack/tools/worlddump.py -d
> > /opt/stack/logs
> > 2015-02-20 07:26:12.767 | ++ exit 1
> >
> >
> > Any ideas how to get around this?
> >
> >
> > Eduard
> >
> > --
> >
> > Eduard Biceri Matei, Senior Software Developer
> > www.cloudfounders.com
> >  | eduard.ma...@cloudfounders.com
> >
> >
> >
> > CloudFounders, The Private Cloud Software Company
> >
> > Disclaimer:
> > This email and any files transmitted with it are confidential and
> intended
> > solely for the use of the individual or entity to whom they are
> addressed.
> > If you are not the named addressee or an employee or agent responsible
> for
> > delivering this message to the named addressee, you are hereby notified
> that
> > you are not authorized to read, print, retain, copy or disseminate this
> > message or any part of it. If you have received this email in error we
> > request you to notify us by reply e-mail and to delete all electronic
> files
> > of the message. If you are not the intended recipient you are notified
> that
> > disclosing, copying, distributing or taking any action in reliance on the
> > contents of this information is strictly prohibited.
> > E-mail transmission cannot be guaranteed to be secure or error free as
> > information could be intercepted, corrupted, lost, destroyed, arrive
> late or
> > incomplete, or contain viruses. The sender therefore does not accept
> > liability for any errors or omissions in the content of this message, and
> > shall have no liability for any loss or damage suffered by the user,
> which
> > arise as a result of e-mail transmission.
> >
> >
> >
> __
> > 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
>



-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the in

[openstack-dev] [Devstack] Devstack Install broken

[Eduard Matei]

Hi,

I'm trying to install devstack and it keeps failing with:

2015-02-20 07:26:12.693 | ++ is_fedora
2015-02-20 07:26:12.693 | ++ [[ -z Ubuntu ]]
2015-02-20 07:26:12.693 | ++ '[' Ubuntu = Fedora ']'
2015-02-20 07:26:12.693 | ++ '[' Ubuntu = 'Red Hat' ']'
2015-02-20 07:26:12.693 | ++ '[' Ubuntu = CentOS ']'
2015-02-20 07:26:12.693 | ++ '[' Ubuntu = OracleServer ']'
2015-02-20 07:26:12.693 | + [[ -d /var/cache/pip ]]
2015-02-20 07:26:12.693 | + [[ ! -d /opt/stack/.wheelhouse ]]
2015-02-20 07:26:12.693 | + source tools/build_wheels.sh
2015-02-20 07:26:12.693 | /opt/devstack/stack.sh: line 688:
tools/build_wheels.sh: No such file or directory
2015-02-20 07:26:12.693 | ++ exit_trap
2015-02-20 07:26:12.693 | ++ local r=1
2015-02-20 07:26:12.693 | +++ jobs -p
2015-02-20 07:26:12.693 | ++ jobs=
2015-02-20 07:26:12.693 | ++ [[ -n '' ]]
2015-02-20 07:26:12.694 | ++ kill_spinner
2015-02-20 07:26:12.694 | ++ '[' '!' -z '' ']'
2015-02-20 07:26:12.694 | ++ [[ 1 -ne 0 ]]
2015-02-20 07:26:12.694 | ++ echo 'Error on exit'
2015-02-20 07:26:12.694 | Error on exit
2015-02-20 07:26:12.694 | ++ [[ -z /opt/stack/logs ]]
2015-02-20 07:26:12.694 | ++ /opt/devstack/tools/worlddump.py -d /opt/stack/logs
2015-02-20 07:26:12.767 | ++ exit 1


Any ideas how to get around this?


Eduard

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] Feature Freeze Exception request

[Eduard Matei]

Hi,

I would like to request a FFE for
https://review.openstack.org/#/c/134134/

It is a change that allows a driver to use type "file" instead of "block"
for local volumes.
It was blocked because at that time there was no use for it.
Now, we have a driver merged which currently returns "loca" for
driver_volume_type; we would like to return "driver_volume_type": file
(which is the correct type) which will then result (via this change) in a
disk type = file in the xml being generated.

Also, this changeset doesn't remove any code, doesn't overwrite any code,
only adds a new type of LibvirtVolumeDriver.

Thanks,

Eduard
-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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] [devstack]Cannot install devstack on CI slave

[Eduard Matei]

Hi,
For two days i've been trying to install devstack.
It keeps failing at configuring neutron, i figured out that it needs two
new params in localrc: PUBLIC_NETWORK_GATEWAY and NETWORK_GATEWAY
On my dev machine i managed to install it manually with these params, but
on the CI slave it fails with error:

2015-02-05 12:05:39.329 | + sudo route add -net 10.150.11.0/16 gw 10.140.0.1
2015-02-05 12:05:39.440 | route: netmask doesn't match route address


Localrc:

[[local|localrc]]
HOST_IP=10.140.0.2
FLAT_INTERFACE=eth0
FIXED_RANGE=10.150.11.0/16
FIXED_NETWORK_SIZE=255
FLOATING_RANGE=10.140.0.0/16
PUBLIC_NETWORK_GATEWAY=10.140.0.2
NETWORK_GATEWAY=10.150.11.1
MULTI_HOST=0
SYSLOG=False
SCREEN_LOGDIR=/opt/stack/logs/screen-logs
LOGFILE=/opt/stack/logs/stack.sh.log
ADMIN_PASSWORD=*
MYSQL_PASSWORD=*
RABBIT_PASSWORD=*
SERVICE_PASSWORD=*
SERVICE_TOKEN=*


Anyone seen this error or has any idea what i should put in the config?


Similar log (different values for localrc):

http://packages.cloudfounders.com/ci_logs/33/130733/40/check/openvstorage-cinder-functionality/ad97bc5/console.html


Thanks,

Eduard


PS. Why did nobody report this issue so far? Either i'm doing
something wrong in the localrc or nobody is installing the latest
devstack. https://bugs.launchpad.net/devstack/+bug/1417635


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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]Questions about Gerrit workflow

[Eduard Matei]

Hi team,

We have some questions regarding the Gerrit workflow and what should we do
next for our patch to be merged:
1. Once we have a CodeReview +2 and a Jenkins Verified +1 what should we do
next to get the patch merged?
2. If we have a CodeReview +2 and we want to fix an issue, does the next
patchset keep the CR +2 ?
3. Once the patch is merged, if we have further changes do we have to
create a new patch (blueprint/bug report)?

Thanks,
Eduard

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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] Request for clarification regarding deadline for new drivers in Kilo

[Eduard Matei]

Hi,

Any update on this?
I added comments to the review.
Meanwhile the nova review got abandoned, but i'll resubmit that once this
is approved.

Thanks,
Eduard

On Wed, Jan 21, 2015 at 7:31 PM, Mike Perez  wrote:

> On 11:24 Wed 21 Jan , Eduard Matei wrote:
> > Hi,
> >
> > This weekend our driver [https://review.openstack.org/#/c/130733/] got
> a -2
> > stating that "This is past the deadline for release of new drivers in
> > Kilo." and "the deadline for new drivers passed at the end of Kilo-1.
> This
> > needs to wait for the L release."
> >
> > But, in another mail on the mailing list we were informed:
> > "
> > If your driver is submitted *LATE* in k-1, and meets *all* the items
> above,
> > but isn't merged, it will be still be considered for merge in k-2 or k-3.
> > "
> > The items above being that the blueprint is submitted, together with cert
> > tests and the code is submitted to gerrit and that a CI is working.
> >
> > We had the blueprint, cert tests and code on gerrit *EARLY* in k-1 (first
> > patchset was on Oct 24), blueprint was approved for k-1 and cert tests
> were
> > posted.
> > CI is under construction, and will be ready by March deadline.
> >
> >
> > So, can someone from cinder core clarify why the driver is delayed to L
> > when all items are met?
>
> Would like to take this off the list. I replied to your review.
>
> --
> Mike Perez
>
> __
> 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
>



-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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] Request for clarification regarding deadline for new drivers in Kilo

[Eduard Matei]

Hi,

This weekend our driver [https://review.openstack.org/#/c/130733/] got a -2
stating that "This is past the deadline for release of new drivers in
Kilo." and "the deadline for new drivers passed at the end of Kilo-1. This
needs to wait for the L release."

But, in another mail on the mailing list we were informed:
"
If your driver is submitted *LATE* in k-1, and meets *all* the items above,
but isn't merged, it will be still be considered for merge in k-2 or k-3.
"
The items above being that the blueprint is submitted, together with cert
tests and the code is submitted to gerrit and that a CI is working.

We had the blueprint, cert tests and code on gerrit *EARLY* in k-1 (first
patchset was on Oct 24), blueprint was approved for k-1 and cert tests were
posted.
CI is under construction, and will be ready by March deadline.


So, can someone from cinder core clarify why the driver is delayed to L
when all items are met?

Thanks,
Eduard
-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
__
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-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi Ramy,
That didn't fix it, zuul-server still gets stuck Looking for lost builds,
but zuul user can read gerrit event-stream.

Any other ideas?

Thanks,
Eduard

On Mon, Jan 19, 2015 at 9:09 AM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi Ramy, indeed user zuul could not read the event-stream (permission
> denied).
> The question is then how it could start zuul-server and read some events?
> Anyway, i copied over .ssh from user jenkins, and now user zuul can run
> that command.
> I restarted zuul-server and will keep an eye on it.
>
> Thanks,
> Eduard
>
> On Fri, Jan 16, 2015 at 8:32 PM, Asselin, Ramy 
> wrote:
>
>>  Hi Eduard,
>>
>>
>>
>> Looking at the zuul code, it seems that is just a periodic task:
>> https://github.com/openstack-infra/zuul/blob/master/zuul/launcher/gearman.py#L50
>>
>>
>>
>> So the issue is not likely those log messages, but rather the lack of
>> other log messages.
>>
>> It seems somehow zuul lost its connection to gerrit even stream…those are
>> the obvious log messages that are missing.
>>
>> And without that, no jobs will trigger a run, so I’d look there.
>>
>>
>>
>> Zuul Manual is here: http://ci.openstack.org/zuul/
>>
>> Zuul conf files is documented here:
>> http://ci.openstack.org/zuul/zuul.html#zuul-conf
>>
>> And the gerrit configurations are here:
>> http://ci.openstack.org/zuul/zuul.html#gerrit
>>
>>
>>
>> Double check you can manually read the event stream as the zuul user
>> (sudo su - zuul) using those settings and this step:
>>
>> http://ci.openstack.org/third_party.html#reading-the-event-stream
>>
>>
>>
>> Ramy
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Friday, January 16, 2015 6:57 AM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Punith,
>>
>> That's the whole log :) Not a lot happening after restart, just default
>> initialization.
>>
>> Zuul-merger is not restarted.
>>
>> Layout.yaml is default.
>>
>> Gearman plugin tested in Jenkins, reports success.
>>
>>
>>
>> I disabled now the restart job to see how long it will "Look for lost
>> builds".
>>
>>
>>
>> Have a nice weekend,
>>
>>
>>
>> Eduard
>>
>>
>>
>> On Fri, Jan 16, 2015 at 1:15 PM, Punith S  wrote:
>>
>>   Hi eduard,
>>
>>
>>
>> can you post the whole zuul.log or debug.log after the zuul and
>> zuul-merger restart along with your layout.yaml
>>
>> did you test the connection of gearman pulgin in jenkins ?
>>
>>
>>
>> thanks
>>
>>
>>
>> On Fri, Jan 16, 2015 at 4:20 PM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>  Hi Ramy,
>>
>> Still couldn't get my custom code to execute between installing devstack
>> and starting tests... i'll try with some custom scripts and skip devstack-*
>> scripts.
>>
>>
>>
>> Meanwhile i see another issue:
>>
>> 2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
>> queue processor: patch (changed: False)
>>
>> 2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
>>
>> 2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
>>
>> 2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds
>>
>>
>>
>> Zuul is stuck in "Looking for lost builds" and it misses comments so it
>> doesn't trigger jobs on patches.
>>
>> Any idea how to fix this? (other than restart it every 30 mins, in which
>> case it misses the results of running jobs so it doesn't post the results).
>&

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi Ramy, indeed user zuul could not read the event-stream (permission
denied).
The question is then how it could start zuul-server and read some events?
Anyway, i copied over .ssh from user jenkins, and now user zuul can run
that command.
I restarted zuul-server and will keep an eye on it.

Thanks,
Eduard

On Fri, Jan 16, 2015 at 8:32 PM, Asselin, Ramy  wrote:

>  Hi Eduard,
>
>
>
> Looking at the zuul code, it seems that is just a periodic task:
> https://github.com/openstack-infra/zuul/blob/master/zuul/launcher/gearman.py#L50
>
>
>
> So the issue is not likely those log messages, but rather the lack of
> other log messages.
>
> It seems somehow zuul lost its connection to gerrit even stream…those are
> the obvious log messages that are missing.
>
> And without that, no jobs will trigger a run, so I’d look there.
>
>
>
> Zuul Manual is here: http://ci.openstack.org/zuul/
>
> Zuul conf files is documented here:
> http://ci.openstack.org/zuul/zuul.html#zuul-conf
>
> And the gerrit configurations are here:
> http://ci.openstack.org/zuul/zuul.html#gerrit
>
>
>
> Double check you can manually read the event stream as the zuul user (sudo
> su - zuul) using those settings and this step:
>
> http://ci.openstack.org/third_party.html#reading-the-event-stream
>
>
>
> Ramy
>
>
>
>
>
>
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, January 16, 2015 6:57 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Punith,
>
> That's the whole log :) Not a lot happening after restart, just default
> initialization.
>
> Zuul-merger is not restarted.
>
> Layout.yaml is default.
>
> Gearman plugin tested in Jenkins, reports success.
>
>
>
> I disabled now the restart job to see how long it will "Look for lost
> builds".
>
>
>
> Have a nice weekend,
>
>
>
> Eduard
>
>
>
> On Fri, Jan 16, 2015 at 1:15 PM, Punith S  wrote:
>
>   Hi eduard,
>
>
>
> can you post the whole zuul.log or debug.log after the zuul and
> zuul-merger restart along with your layout.yaml
>
> did you test the connection of gearman pulgin in jenkins ?
>
>
>
> thanks
>
>
>
> On Fri, Jan 16, 2015 at 4:20 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi Ramy,
>
> Still couldn't get my custom code to execute between installing devstack
> and starting tests... i'll try with some custom scripts and skip devstack-*
> scripts.
>
>
>
> Meanwhile i see another issue:
>
> 2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
> queue processor: patch (changed: False)
>
> 2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
>
> 2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
>
> 2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds
>
>
>
> Zuul is stuck in "Looking for lost builds" and it misses comments so it
> doesn't trigger jobs on patches.
>
> Any idea how to fix this? (other than restart it every 30 mins, in which
> case it misses the results of running jobs so it doesn't post the results).
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Fri, Jan 16, 2015 at 1:43 AM, Asselin, Ramy 
> wrote:
>
>  Hi Eduard,
>
>
>
> Glad you’re making progress.
>
>
>
> $BASE/new/devstack/ is available at the time pre_test_hook is called, so
> you should be able to make all the changes you need there.
>
>
>
> The sample shows how to configure the driver using local.conf devstack
> hooks.
>
> See here for more details: [1] [2]
>
>
>
> Regarding test, you can do both.
>
> Cinder requires you run tempest.api.volume[3]
>
>
>
> And you can setup a 2nd job that runs your internal functional tests as
> well.
>
>
>
> Ramy
>
>
>
> [1] http://docs.openstack.org/developer/devstack/configuration.html
>
> [2] http://docs.openstack.org/developer/devstack/plugi

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi Punith,
That's the whole log :) Not a lot happening after restart, just default
initialization.
Zuul-merger is not restarted.
Layout.yaml is default.
Gearman plugin tested in Jenkins, reports success.

I disabled now the restart job to see how long it will "Look for lost
builds".

Have a nice weekend,

Eduard

On Fri, Jan 16, 2015 at 1:15 PM, Punith S  wrote:

>  Hi eduard,
>
> can you post the whole zuul.log or debug.log after the zuul and
> zuul-merger restart along with your layout.yaml
> did you test the connection of gearman pulgin in jenkins ?
>
> thanks
>
> On Fri, Jan 16, 2015 at 4:20 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>> Hi Ramy,
>> Still couldn't get my custom code to execute between installing devstack
>> and starting tests... i'll try with some custom scripts and skip devstack-*
>> scripts.
>>
>> Meanwhile i see another issue:
>> 2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
>> queue processor: patch (changed: False)
>> 2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
>> 2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
>> 2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds
>>
>> Zuul is stuck in "Looking for lost builds" and it misses comments so it
>> doesn't trigger jobs on patches.
>> Any idea how to fix this? (other than restart it every 30 mins, in which
>> case it misses the results of running jobs so it doesn't post the results).
>>
>> Thanks,
>> Eduard
>>
>> On Fri, Jan 16, 2015 at 1:43 AM, Asselin, Ramy 
>> wrote:
>>
>>>  Hi Eduard,
>>>
>>>
>>>
>>> Glad you’re making progress.
>>>
>>>
>>>
>>> $BASE/new/devstack/ is available at the time pre_test_hook is called, so
>>> you should be able to make all the changes you need there.
>>>
>>>
>>>
>>> The sample shows how to configure the driver using local.conf devstack
>>> hooks.
>>>
>>> See here for more details: [1] [2]
>>>
>>>
>>>
>>> Regarding test, you can do both.
>>>
>>> Cinder requires you run tempest.api.volume[3]
>>>
>>>
>>>
>>> And you can setup a 2nd job that runs your internal functional tests as
>>> well.
>>>
>>>
>>>
>>> Ramy
>>>
>>>
>>>
>>> [1] http://docs.openstack.org/developer/devstack/configuration.html
>>>
>>> [2] http://docs.openstack.org/developer/devstack/plugins.html
>>>
>>> [3]
>>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Third_Party_CI_Requirements
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>>> *Sent:* Thursday, January 15, 2015 4:57 AM
>>>
>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>>> help setting up CI
>>>
>>>
>>>
>>> Hi Ramy,
>>>
>>>
>>>
>>> The issue with disconnect/abort no longer happens, so i guess it was
>>> some issues with networking.
>>>
>>>
>>>
>>> Regarding the ssh keys i finally used Jenkins Configuration Provider
>>> Plugin to inject ssh keys as a pre-build step, then i added a manual
>>> execution step to scp the logs to the server, so now everything appears to
>>> be working.
>>>
>>>
>>>
>>> Now for the REAL tests:
>>>
>>> looking at
>>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>>> it seems i need to put the code to install my "third party libs" in the
>>> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
>>> B

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi Ramy,
Still couldn't get my custom code to execute between installing devstack
and starting tests... i'll try with some custom scripts and skip devstack-*
scripts.

Meanwhile i see another issue:
2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
queue processor: patch (changed: False)
2015-01-16 11:02:26,283 DEBUG zuul.Scheduler: Run handler sleeping
2015-01-16 11:06:06,873 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:11:06,873 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:16:06,874 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:21:06,874 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:26:06,875 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:31:06,875 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:36:06,876 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:41:06,876 DEBUG zuul.Gearman: Looking for lost builds
2015-01-16 11:46:06,877 DEBUG zuul.Gearman: Looking for lost builds

Zuul is stuck in "Looking for lost builds" and it misses comments so it
doesn't trigger jobs on patches.
Any idea how to fix this? (other than restart it every 30 mins, in which
case it misses the results of running jobs so it doesn't post the results).

Thanks,
Eduard

On Fri, Jan 16, 2015 at 1:43 AM, Asselin, Ramy  wrote:

>  Hi Eduard,
>
>
>
> Glad you’re making progress.
>
>
>
> $BASE/new/devstack/ is available at the time pre_test_hook is called, so
> you should be able to make all the changes you need there.
>
>
>
> The sample shows how to configure the driver using local.conf devstack
> hooks.
>
> See here for more details: [1] [2]
>
>
>
> Regarding test, you can do both.
>
> Cinder requires you run tempest.api.volume[3]
>
>
>
> And you can setup a 2nd job that runs your internal functional tests as
> well.
>
>
>
> Ramy
>
>
>
> [1] http://docs.openstack.org/developer/devstack/configuration.html
>
> [2] http://docs.openstack.org/developer/devstack/plugins.html
>
> [3]
> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Third_Party_CI_Requirements
>
>
>
>
>
>
>
>
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Thursday, January 15, 2015 4:57 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Ramy,
>
>
>
> The issue with disconnect/abort no longer happens, so i guess it was some
> issues with networking.
>
>
>
> Regarding the ssh keys i finally used Jenkins Configuration Provider
> Plugin to inject ssh keys as a pre-build step, then i added a manual
> execution step to scp the logs to the server, so now everything appears to
> be working.
>
>
>
> Now for the REAL tests:
>
> looking at
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
> it seems i need to put the code to install my "third party libs" in the
> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
> BEFORE installing devstack. The problem is we need our "third party libs"
> to be installed (actually configured) AFTER installing devstack, since they
> install on top of devstack and do some configuration on devstack.
>
>
>
> How could i integrate my code into devstack-vm-gate-wrap.sh so that my
> libs are installed after devstack but before running tempest.
>
> Also, as a side question, do i need to run all the test (since they
> already run in dsvm-tempest-full) or can i run only our internal
> functionality tests? (in this case i don't need devstack-vm-gate-wrap.sh
> and i can run custom code directly from jenkins job).
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy 
> wrote:
>
>  Double check your ssh public/private key, authorized keys configuration
> in the slave & log server.
>
> They should all match up. No passwords should be requested.
>
> Try doing a manual scp as Jenkins user from the slave to the log server
> (as Jenkins user there too).
>
>
>
> Regarding manually setting up the publisher, I don’t know. Jenkins Job
> Builder configuration I referenced below should work correctly.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Wednesday, January 14, 2015 6:56 AM
>
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Ramy,
>
>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi Amit,
This is the only logging i see:
2015-01-15 14:48:28,034 DEBUG zuul.Gerrit: Change  status: NEW
2015-01-15 14:48:28,035 INFO zuul.Gerrit: Updating information for 146460,5
2015-01-15 14:51:07,851 DEBUG zuul.Gearman: Looking for lost builds
2015-01-15 14:56:07,852 DEBUG zuul.Gearman: Looking for lost builds
2015-01-15 15:01:00,627 DEBUG zuul.Scheduler: Prepare to exit
2015-01-15 15:01:00,627 DEBUG zuul.Scheduler: Waiting for exit
2015-01-15 15:01:00,627 DEBUG zuul.Scheduler: Run handler awake
2015-01-15 15:01:00,627 DEBUG zuul.Scheduler: Checking if all builds are
complete
2015-01-15 15:01:00,628 DEBUG zuul.Scheduler: All builds are complete
2015-01-15 15:01:00,628 DEBUG zuul.Scheduler: Exiting


At 15.01 it was restarted by jenkins and between 14:48 and 15:01 there was
a job that finished but Gerrit didn't post the results.

Eduard

On Thu, Jan 15, 2015 at 3:06 PM, Amit Das  wrote:

> Hi Eduard,
>
> Can you put the logs or details for below comment:
>
> it seems that sometimes Zuul gets stuck (sometimes in Looking for lost
>> builds, sometimes doing nothing) and it misses notifications.
>
>
> I guess, we too have been facing the same issue with Zuul.
>
>
> Regards,
> Amit
> *CloudByte Inc.* <http://www.cloudbyte.com/>
>
> On Thu, Jan 15, 2015 at 6:29 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>> Hi,
>> Just so i don't start another thread: it seems that sometimes Zuul gets
>> stuck (sometimes in Looking for lost builds, sometimes doing nothing) and
>> it misses notifications.
>> I added a Jenkins timer job to restart it every 30 minutes. Is there a
>> fix for this or something to change in config?
>>
>> Thanks,
>> Eduard
>>
>> On Thu, Jan 15, 2015 at 2:56 PM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>> Hi Ramy,
>>>
>>> The issue with disconnect/abort no longer happens, so i guess it was
>>> some issues with networking.
>>>
>>> Regarding the ssh keys i finally used Jenkins Configuration Provider
>>> Plugin to inject ssh keys as a pre-build step, then i added a manual
>>> execution step to scp the logs to the server, so now everything appears to
>>> be working.
>>>
>>> Now for the REAL tests:
>>> looking at
>>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>>> it seems i need to put the code to install my "third party libs" in the
>>> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
>>> BEFORE installing devstack. The problem is we need our "third party libs"
>>> to be installed (actually configured) AFTER installing devstack, since they
>>> install on top of devstack and do some configuration on devstack.
>>>
>>> How could i integrate my code into devstack-vm-gate-wrap.sh so that my
>>> libs are installed after devstack but before running tempest.
>>> Also, as a side question, do i need to run all the test (since they
>>> already run in dsvm-tempest-full) or can i run only our internal
>>> functionality tests? (in this case i don't need devstack-vm-gate-wrap.sh
>>> and i can run custom code directly from jenkins job).
>>>
>>> Thanks,
>>>
>>> Eduard
>>>
>>> On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy 
>>> wrote:
>>>
>>>>  Double check your ssh public/private key, authorized keys
>>>> configuration in the slave & log server.
>>>>
>>>> They should all match up. No passwords should be requested.
>>>>
>>>> Try doing a manual scp as Jenkins user from the slave to the log server
>>>> (as Jenkins user there too).
>>>>
>>>>
>>>>
>>>> Regarding manually setting up the publisher, I don’t know. Jenkins Job
>>>> Builder configuration I referenced below should work correctly.
>>>>
>>>>
>>>>
>>>> Ramy
>>>>
>>>>
>>>>
>>>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>>>> *Sent:* Wednesday, January 14, 2015 6:56 AM
>>>>
>>>> *To:* OpenStack Development Mailing List (not for usage questions)
>>>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>>>> help setting up CI
>>>>
>>>>
>>>>
>>>> Hi Ramy,
>>>>
>>>>
>>>>
>>>> I think i managed to setup SCP plugin and updated zuul.conf

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi,
Just so i don't start another thread: it seems that sometimes Zuul gets
stuck (sometimes in Looking for lost builds, sometimes doing nothing) and
it misses notifications.
I added a Jenkins timer job to restart it every 30 minutes. Is there a fix
for this or something to change in config?

Thanks,
Eduard

On Thu, Jan 15, 2015 at 2:56 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi Ramy,
>
> The issue with disconnect/abort no longer happens, so i guess it was some
> issues with networking.
>
> Regarding the ssh keys i finally used Jenkins Configuration Provider
> Plugin to inject ssh keys as a pre-build step, then i added a manual
> execution step to scp the logs to the server, so now everything appears to
> be working.
>
> Now for the REAL tests:
> looking at
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
> it seems i need to put the code to install my "third party libs" in the
> pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
> BEFORE installing devstack. The problem is we need our "third party libs"
> to be installed (actually configured) AFTER installing devstack, since they
> install on top of devstack and do some configuration on devstack.
>
> How could i integrate my code into devstack-vm-gate-wrap.sh so that my
> libs are installed after devstack but before running tempest.
> Also, as a side question, do i need to run all the test (since they
> already run in dsvm-tempest-full) or can i run only our internal
> functionality tests? (in this case i don't need devstack-vm-gate-wrap.sh
> and i can run custom code directly from jenkins job).
>
> Thanks,
>
> Eduard
>
> On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy 
> wrote:
>
>>  Double check your ssh public/private key, authorized keys configuration
>> in the slave & log server.
>>
>> They should all match up. No passwords should be requested.
>>
>> Try doing a manual scp as Jenkins user from the slave to the log server
>> (as Jenkins user there too).
>>
>>
>>
>> Regarding manually setting up the publisher, I don’t know. Jenkins Job
>> Builder configuration I referenced below should work correctly.
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Wednesday, January 14, 2015 6:56 AM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Ramy,
>>
>>
>>
>> I think i managed to setup SCP plugin and updated zuul.conf but it only
>> uploads the console.html not the logs
>>
>> I have an SCP site pointing to the apache server and the root location is
>> /srv/static, and in the dsvm job manually added a post-build step, Publish
>> Artifacts to SCP Repository, with source: logs/** and destination
>> logs/${LOG_PATH} and also checked Copy Console Log.
>>
>>
>>
>> The destination path is created, but it only contains console.html.
>>
>>
>>
>> I tried to manually scp the directory, but the jenkins user in the
>> devstack_slave asks for a password when trying to ssh to apache server.
>>
>>
>>
>> Thanks,
>>
>> Eduard
>>
>>
>>
>> On Wed, Jan 14, 2015 at 10:40 AM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>  Thanks Ramy, i'll try to set it up manually.
>>
>>
>>
>> Meanwhile i found another problem: jobs are failing because of error or
>> are being aborted.
>>
>> FATAL: java.io.IOException: Unexpected termination of the channel
>>
>> hudson.remoting.RequestAbortedException 
>> <http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
>>  java.io.IOException: Unexpected termination of the channel
>>
>>
>>
>> Is this related to another warning i got:
>>
>> WARNING: devstack run took > 15 minutes, this is a very slow node.
>>
>>
>>
>> Is there a timeout for how long a job is allowed to run?
>>
>> Most jobs take between 40 and 60 minutes, some are able to run successfully, 
>> some are aborted or get this error.
>>
>>
>>
>> Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.
>>
>> Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB 
>> vHDD).
>>
>>
>>
>> Thanks,
>&g

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi Ramy,

The issue with disconnect/abort no longer happens, so i guess it was some
issues with networking.

Regarding the ssh keys i finally used Jenkins Configuration Provider Plugin
to inject ssh keys as a pre-build step, then i added a manual execution
step to scp the logs to the server, so now everything appears to be working.

Now for the REAL tests:
looking at
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
it seems i need to put the code to install my "third party libs" in the
pre_test_hook which appears in devstack-vm-gate-wrap.sh to be executing
BEFORE installing devstack. The problem is we need our "third party libs"
to be installed (actually configured) AFTER installing devstack, since they
install on top of devstack and do some configuration on devstack.

How could i integrate my code into devstack-vm-gate-wrap.sh so that my libs
are installed after devstack but before running tempest.
Also, as a side question, do i need to run all the test (since they already
run in dsvm-tempest-full) or can i run only our internal functionality
tests? (in this case i don't need devstack-vm-gate-wrap.sh and i can run
custom code directly from jenkins job).

Thanks,

Eduard

On Wed, Jan 14, 2015 at 6:49 PM, Asselin, Ramy  wrote:

>  Double check your ssh public/private key, authorized keys configuration
> in the slave & log server.
>
> They should all match up. No passwords should be requested.
>
> Try doing a manual scp as Jenkins user from the slave to the log server
> (as Jenkins user there too).
>
>
>
> Regarding manually setting up the publisher, I don’t know. Jenkins Job
> Builder configuration I referenced below should work correctly.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Wednesday, January 14, 2015 6:56 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Ramy,
>
>
>
> I think i managed to setup SCP plugin and updated zuul.conf but it only
> uploads the console.html not the logs
>
> I have an SCP site pointing to the apache server and the root location is
> /srv/static, and in the dsvm job manually added a post-build step, Publish
> Artifacts to SCP Repository, with source: logs/** and destination
> logs/${LOG_PATH} and also checked Copy Console Log.
>
>
>
> The destination path is created, but it only contains console.html.
>
>
>
> I tried to manually scp the directory, but the jenkins user in the
> devstack_slave asks for a password when trying to ssh to apache server.
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Wed, Jan 14, 2015 at 10:40 AM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Thanks Ramy, i'll try to set it up manually.
>
>
>
> Meanwhile i found another problem: jobs are failing because of error or
> are being aborted.
>
> FATAL: java.io.IOException: Unexpected termination of the channel
>
> hudson.remoting.RequestAbortedException 
> <http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
>  java.io.IOException: Unexpected termination of the channel
>
>
>
> Is this related to another warning i got:
>
> WARNING: devstack run took > 15 minutes, this is a very slow node.
>
>
>
> Is there a timeout for how long a job is allowed to run?
>
> Most jobs take between 40 and 60 minutes, some are able to run successfully, 
> some are aborted or get this error.
>
>
>
> Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.
>
> Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB 
> vHDD).
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Tue, Jan 13, 2015 at 5:34 PM, Asselin, Ramy 
> wrote:
>
>  Hi Eduard,
>
>
>
> Apache logs server address is set here (should probably add some
> comment/doc for that)
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10
>
>
>
> Jenkins will get configured here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
>
> Note that you need to restart Jenkins for those changes to take effect.
> After it’s set, you can use the Jenkins UI to ‘test’ the connection.
>
>
>
> Jenkins Job Builder publishers are here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110
>
>
>
> Use the publishers as 

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi Ramy,

I think i managed to setup SCP plugin and updated zuul.conf but it only
uploads the console.html not the logs
I have an SCP site pointing to the apache server and the root location is
/srv/static, and in the dsvm job manually added a post-build step, Publish
Artifacts to SCP Repository, with source: logs/** and destination
logs/${LOG_PATH} and also checked Copy Console Log.

The destination path is created, but it only contains console.html.

I tried to manually scp the directory, but the jenkins user in the
devstack_slave asks for a password when trying to ssh to apache server.

Thanks,
Eduard

On Wed, Jan 14, 2015 at 10:40 AM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Thanks Ramy, i'll try to set it up manually.
>
> Meanwhile i found another problem: jobs are failing because of error or
> are being aborted.
>
> FATAL: java.io.IOException: Unexpected termination of the 
> channelhudson.remoting.RequestAbortedException 
> <http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
>  java.io.IOException: Unexpected termination of the channel
>
>
> Is this related to another warning i got:
>
> WARNING: devstack run took > 15 minutes, this is a very slow node.
>
>
> Is there a timeout for how long a job is allowed to run?
>
> Most jobs take between 40 and 60 minutes, some are able to run successfully, 
> some are aborted or get this error.
>
>
> Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.
>
> Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB 
> vHDD).
>
>
> Thanks,
>
> Eduard
>
>
> On Tue, Jan 13, 2015 at 5:34 PM, Asselin, Ramy 
> wrote:
>
>>  Hi Eduard,
>>
>>
>>
>> Apache logs server address is set here (should probably add some
>> comment/doc for that)
>>
>>
>> https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10
>>
>>
>>
>> Jenkins will get configured here:
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
>>
>> Note that you need to restart Jenkins for those changes to take effect.
>> After it’s set, you can use the Jenkins UI to ‘test’ the connection.
>>
>>
>>
>> Jenkins Job Builder publishers are here:
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110
>>
>>
>>
>> Use the publishers as shown here:
>>
>>
>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>>
>>
>>
>> Zuul will then use this url when commenting in gerrit:
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/manifests/master.pp#L18
>>
>>
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Tuesday, January 13, 2015 2:31 AM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set
>> before starting first time nodepool, so template got incorrect key)
>>
>> Next question: where do i configure the apache logs server address? I
>> have a separate vm with jenkins account and running apache2 exposing
>> /srv/static/logs, but where do i enter its ip address ? (in jenkins,
>> nodepool or... )
>>
>>
>>
>> Thanks,
>>
>> Eduard
>>
>>
>>
>> On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy 
>> wrote:
>>
>>  You are correct to run nodepoold as nodepool user.
>>
>> I didn’t see any issues…
>>
>> Could you double check the public keys listed in .ssh/authorized_keys in
>> the template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Monday, January 12, 2015 5:30 AM
>>
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi,
>>
>> Regarding the last issue, i fixed it by logging in and manually "pip
>> install docutils". Image was created successfully.
>>
>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Thanks Ramy, i'll try to set it up manually.

Meanwhile i found another problem: jobs are failing because of error or are
being aborted.

FATAL: java.io.IOException: Unexpected termination of the
channelhudson.remoting.RequestAbortedException
<http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
java.io.IOException: Unexpected termination of the channel


Is this related to another warning i got:

WARNING: devstack run took > 15 minutes, this is a very slow node.


Is there a timeout for how long a job is allowed to run?

Most jobs take between 40 and 60 minutes, some are able to run
successfully, some are aborted or get this error.


Hardware is Xeon E3-1220 Quad core 3.10 Ghz, 32 GB RAM and 3x 1TB sata HDD.

Devstack slaves are configured as m1.large (4 vCPUs, 8 GB vRAM and 80 GB vHDD).


Thanks,

Eduard


On Tue, Jan 13, 2015 at 5:34 PM, Asselin, Ramy  wrote:

>  Hi Eduard,
>
>
>
> Apache logs server address is set here (should probably add some
> comment/doc for that)
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/vars.sh.sample#L10
>
>
>
> Jenkins will get configured here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb
>
> Note that you need to restart Jenkins for those changes to take effect.
> After it’s set, you can use the Jenkins UI to ‘test’ the connection.
>
>
>
> Jenkins Job Builder publishers are here:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/templates/jenkins_job_builder/config/macros.yaml.erb#L110
>
>
>
> Use the publishers as shown here:
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L7
>
>
>
> Zuul will then use this url when commenting in gerrit:
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/modules/os_ext_testing/manifests/master.pp#L18
>
>
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Tuesday, January 13, 2015 2:31 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set before
> starting first time nodepool, so template got incorrect key)
>
> Next question: where do i configure the apache logs server address? I have
> a separate vm with jenkins account and running apache2 exposing
> /srv/static/logs, but where do i enter its ip address ? (in jenkins,
> nodepool or... )
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy 
> wrote:
>
>  You are correct to run nodepoold as nodepool user.
>
> I didn’t see any issues…
>
> Could you double check the public keys listed in .ssh/authorized_keys in
> the template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Monday, January 12, 2015 5:30 AM
>
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
> Regarding the last issue, i fixed it by logging in and manually "pip
> install docutils". Image was created successfully.
>
>
>
> Now the problem is that nodepool is not able to login into instances
> created from that image.
>
> I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running,
> and also i am able to login to the instance from user nodepool, but
> nodepoold gives error:
>
> 2015-01-12 14:19:03,095 DEBUG paramiko.transport: Switch to new keys ...
>
> 2015-01-12 14:19:03,109 DEBUG paramiko.transport: Trying key
> c03fbf64440cd0c2ecbc07ce4ed59804 from /home/nodepool/.ssh/id_rsa
>
> 2015-01-12 14:19:03,135 DEBUG paramiko.transport: userauth is OK
>
> 2015-01-12 14:19:03,162 INFO paramiko.transport: Authentication
> (publickey) failed.
>
> 2015-01-12 14:19:03,185 DEBUG paramiko.transport: Trying discovered key
> c03fbf64440cd0c2ecbc07ce4ed59804 in /home/nodepool/.ssh/id_rsa
>
> 2015-01-12 14:19:03,187 DEBUG paramiko.transport: userauth is OK
>
> ^C2015-01-12 14:19:03,210 INFO paramiko.transport: Authentication
> (publickey) failed.
>
> 2015-01-12 14:19:03,253 DEBUG paramiko.transport: EOF in transport thread
>
> 2015-01-12 14:19:03,254 INFO nodepool.utils: Password auth exception. Try
> number 4...
>
>
>
>
>
> echo $NODEPOOL_SSH_KEY
>

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Thanks Ramy, i got it now working (the NODEPOOL_SSH_KEY was not set before
starting first time nodepool, so template got incorrect key)
Next question: where do i configure the apache logs server address? I have
a separate vm with jenkins account and running apache2 exposing
/srv/static/logs, but where do i enter its ip address ? (in jenkins,
nodepool or... )

Thanks,
Eduard

On Mon, Jan 12, 2015 at 6:09 PM, Asselin, Ramy  wrote:

>  You are correct to run nodepoold as nodepool user.
>
> I didn’t see any issues…
>
> Could you double check the public keys listed in .ssh/authorized_keys in
> the template for Ubuntu and Jenkins users match $NODEPOOL_SSH_KEY?
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Monday, January 12, 2015 5:30 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
> Regarding the last issue, i fixed it by logging in and manually "pip
> install docutils". Image was created successfully.
>
>
>
> Now the problem is that nodepool is not able to login into instances
> created from that image.
>
> I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running,
> and also i am able to login to the instance from user nodepool, but
> nodepoold gives error:
>
> 2015-01-12 14:19:03,095 DEBUG paramiko.transport: Switch to new keys ...
>
> 2015-01-12 14:19:03,109 DEBUG paramiko.transport: Trying key
> c03fbf64440cd0c2ecbc07ce4ed59804 from /home/nodepool/.ssh/id_rsa
>
> 2015-01-12 14:19:03,135 DEBUG paramiko.transport: userauth is OK
>
> 2015-01-12 14:19:03,162 INFO paramiko.transport: Authentication
> (publickey) failed.
>
> 2015-01-12 14:19:03,185 DEBUG paramiko.transport: Trying discovered key
> c03fbf64440cd0c2ecbc07ce4ed59804 in /home/nodepool/.ssh/id_rsa
>
> 2015-01-12 14:19:03,187 DEBUG paramiko.transport: userauth is OK
>
> ^C2015-01-12 14:19:03,210 INFO paramiko.transport: Authentication
> (publickey) failed.
>
> 2015-01-12 14:19:03,253 DEBUG paramiko.transport: EOF in transport thread
>
> 2015-01-12 14:19:03,254 INFO nodepool.utils: Password auth exception. Try
> number 4...
>
>
>
>
>
> echo $NODEPOOL_SSH_KEY
>
>
> B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v
>
>
>
>  cat /home/nodepool/.ssh/id_rsa.pub
>
> ssh-rsa
> B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v
> jenkins@jenkins-cinderci
>
>
>
> ssh ubuntu@10.100.128.136 -v
>
> OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
>
> debug1: Reading configuration data /home/nodepool/.ssh/config
>
> debug1: Reading configuration data /etc/ssh/ssh_config
>
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>
> debug1: Connecting to 10.100.128.136 [10.100.128.136] port 22.
>
> debug1: Connection established.
>
> 
>
> debug1: Offering RSA public key: /home/nodepool/.ssh/id_rsa
>
> debug1: Server accepts key: pkalg ssh-rsa blen 279
>
> debug1: key_parse_private2: missing begin marker
>
> debug1: read PEM private key done: type RSA
>
> debug1: Authentication succeeded (publickey).
>
> Authenticated to 10.100.128.136 ([10.100.128.136]:22).
>
> ...
>
>
>
> I was able to login into the "template" instance and also am able to login
> into the "slave" instances.
>
> Also nodepoold was able to login into "template" instance but now it fails
> loging in into "slave".
>
>
>
> I tried running it as either nodepol or jenkins users, same result.
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Mon, Jan 12, 2015 at 2:09 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi,
>
> Back with another error during image creation with nodepool:
>
> 2015-01-12 13:05:17,775 INFO nodepool.image.build.local_01.d-p-c:
> Downloading python-daemon-2.0.1.tar.gz (62kB)
>
> 2015-01-12 13:05:18,022 INFO nodepool.image.build.local_01.d-p-c:
> Traceback (most recent call last):
>
> 2015-01

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi,
Regarding the last issue, i fixed it by logging in and manually "pip
install docutils". Image was created successfully.

Now the problem is that nodepool is not able to login into instances
created from that image.
I have NODEPOOL_SSH_KEY exported in the screen where nodepool is running,
and also i am able to login to the instance from user nodepool, but
nodepoold gives error:
2015-01-12 14:19:03,095 DEBUG paramiko.transport: Switch to new keys ...
2015-01-12 14:19:03,109 DEBUG paramiko.transport: Trying key
c03fbf64440cd0c2ecbc07ce4ed59804 from /home/nodepool/.ssh/id_rsa
2015-01-12 14:19:03,135 DEBUG paramiko.transport: userauth is OK
2015-01-12 14:19:03,162 INFO paramiko.transport: Authentication (publickey)
failed.
2015-01-12 14:19:03,185 DEBUG paramiko.transport: Trying discovered key
c03fbf64440cd0c2ecbc07ce4ed59804 in /home/nodepool/.ssh/id_rsa
2015-01-12 14:19:03,187 DEBUG paramiko.transport: userauth is OK
^C2015-01-12 14:19:03,210 INFO paramiko.transport: Authentication
(publickey) failed.
2015-01-12 14:19:03,253 DEBUG paramiko.transport: EOF in transport thread
2015-01-12 14:19:03,254 INFO nodepool.utils: Password auth exception. Try
number 4...


echo $NODEPOOL_SSH_KEY
B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v

 cat /home/nodepool/.ssh/id_rsa.pub
ssh-rsa
B3NzaC1yc2EDAQABAAABAQC9gP6qui1fmHrj02p6OGvnz7kMTJ2rOC3SBYP/Ij/6yz+SU8rL5rqL6jqT30xzy9t1q0zsdJCNB2jExD4xb+NFbaoGlvjF85m12eFqP4CQenxUOdYAepf5sjV2l8WAO3ylspQ78ipLKec98NeKQwLrHB+xon6QfAHXr6ZJ9NRZbmWw/OdpOgAG9Cab+ELTmkfEYgQz01cZE22xEAMvPXz57KlWPvxtE7YwYWy180Yib97EftylsNkrchbSXCwiqgKUf04qWhTgNrVuRJ9mytil6S82VNDxHzTzeCCxY412CV6dDJNLzJItpf/CXQelj/6wJs1GgFl5GWJnqortMR2v
jenkins@jenkins-cinderci

ssh ubuntu@10.100.128.136 -v
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /home/nodepool/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 10.100.128.136 [10.100.128.136] port 22.
debug1: Connection established.

debug1: Offering RSA public key: /home/nodepool/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
Authenticated to 10.100.128.136 ([10.100.128.136]:22).
...

I was able to login into the "template" instance and also am able to login
into the "slave" instances.
Also nodepoold was able to login into "template" instance but now it fails
loging in into "slave".

I tried running it as either nodepol or jenkins users, same result.

Thanks,
Eduard

On Mon, Jan 12, 2015 at 2:09 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi,
> Back with another error during image creation with nodepool:
> 2015-01-12 13:05:17,775 INFO nodepool.image.build.local_01.d-p-c:
> Downloading python-daemon-2.0.1.tar.gz (62kB)
> 2015-01-12 13:05:18,022 INFO nodepool.image.build.local_01.d-p-c:
> Traceback (most recent call last):
> 2015-01-12 13:05:18,023 INFO nodepool.image.build.local_01.d-p-c:
> File "", line 20, in 
> 2015-01-12 13:05:18,023 INFO nodepool.image.build.local_01.d-p-c:
> File "/tmp/pip-build-r6RJKq/python-daemon/setup.py", line 27, in 
> 2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
> import version
> 2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
> File "version.py", line 51, in 
> 2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
> import docutils.core
> 2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
> ImportError: No module named docutils.core
> 2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
> Complete output from command python setup.py egg_info:
> 2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
> Traceback (most recent call last):
> 2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
> 2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
> File "", line 20, in 
> 2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
> 2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
> File "/tmp/pip-build-r6RJKq/python-daemon/setup.py", line 27, in 
> 2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
> 2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
> import version
> 2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi,
Back with another error during image creation with nodepool:
2015-01-12 13:05:17,775 INFO nodepool.image.build.local_01.d-p-c:
Downloading python-daemon-2.0.1.tar.gz (62kB)
2015-01-12 13:05:18,022 INFO nodepool.image.build.local_01.d-p-c:
Traceback (most recent call last):
2015-01-12 13:05:18,023 INFO nodepool.image.build.local_01.d-p-c:
File "", line 20, in 
2015-01-12 13:05:18,023 INFO nodepool.image.build.local_01.d-p-c:
File "/tmp/pip-build-r6RJKq/python-daemon/setup.py", line 27, in 
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
import version
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
File "version.py", line 51, in 
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
import docutils.core
2015-01-12 13:05:18,024 INFO nodepool.image.build.local_01.d-p-c:
ImportError: No module named docutils.core
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
Complete output from command python setup.py egg_info:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
Traceback (most recent call last):
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
File "", line 20, in 
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
File "/tmp/pip-build-r6RJKq/python-daemon/setup.py", line 27, in 
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,025 INFO nodepool.image.build.local_01.d-p-c:
import version
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
File "version.py", line 51, in 
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
import docutils.core
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
ImportError: No module named docutils.core
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:
2015-01-12 13:05:18,026 INFO nodepool.image.build.local_01.d-p-c:

2015-01-12 13:05:18,054 INFO nodepool.image.build.local_01.d-p-c:
Command "python setup.py egg_info" failed with error code 1 in
/tmp/pip-build-r6RJKq/python-daemon

Python-daemon pip package fails to install due to ImportError.

Any ideas how to fix this?

Thanks,
Eduard

On Fri, Jan 9, 2015 at 10:00 PM, Patrick East 
wrote:

> Thanks for the links!
>
> After digging around in my configs I figured out the issue, I had a typo
> in my JENKINS_SSH_PUBLIC_KEY_NO_WHITESPACE (copy pasta cut off a
> character...). But I managed to put the right one in the key for nova to
> use so it was able to log in to set up the instance, but didn't end up with
> the right thing in the NODEPOOL_SSH_KEY variable.
>
> -Patrick
>
> On Fri, Jan 9, 2015 at 9:25 AM, Asselin, Ramy  wrote:
>
>>
>>
>> Regarding SSH Keys and logging into nodes, you need to set the
>> NODEPOOL_SSH_KEY variable
>>
>> 1.   I documented my notes here
>> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/nodepool/nodepool.yaml.erb.sample#L48
>>
>> 2.   This is also documented ‘officially’ here:
>> https://github.com/openstack-infra/nodepool/blob/master/README.rst
>>
>> 3.   Also, I had an issue getting puppet to do the right thing with
>> keys, so it gets forced here:
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L197
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Friday, January 09, 2015 8:58 AM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Thanks Patrick,
>>
>> Indeed it seems the cloud provider was setting up vms on a bridge whose
>> eth was DOWN so the vms could not connect to the outside world so the
>> prepare script was failing.
>>
>> Looking into that.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Eduard
>>
>>
>>
>> On Fri, Jan 9, 2015 at 6:44 PM, Patrick East <
>> patrick.e...@purestorage.com> wrote:
>>
>>  Ah yea, sorry, should have specified; I am having it run
>> the prepare_node_devstack.sh from the infra repo. I see it adding the same
>> public key to the user specified in my nodepool.yaml. The strange part (and
>> I need to double check.. feel like it can't be 

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Thanks Patrick,
Indeed it seems the cloud provider was setting up vms on a bridge whose eth
was DOWN so the vms could not connect to the outside world so the prepare
script was failing.
Looking into that.

Thanks,

Eduard

On Fri, Jan 9, 2015 at 6:44 PM, Patrick East 
wrote:

> Ah yea, sorry, should have specified; I am having it run
> the prepare_node_devstack.sh from the infra repo. I see it adding the same
> public key to the user specified in my nodepool.yaml. The strange part (and
> I need to double check.. feel like it can't be right) is that on my master
> node the nodepool users id_rsa changed at some point in the process.
>
>
> -Patrick
>
> On Fri, Jan 9, 2015 at 8:38 AM, Jeremy Stanley  wrote:
>
>> On 2015-01-09 08:28:39 -0800 (-0800), Patrick East wrote:
>> [...]
>> > On a related note, I am having issues with the ssh keys. Nodepool
>> > is able to log in to the node to set up the template and create an
>> > image from it, but then fails to log in to a build node. Have you
>> > run into any issues with that?
>>
>> Your image build needs to do _something_ to make SSH into the
>> resulting nodes possible. We accomplish that by applying a puppet
>> manifest which sets up an authorized_keys file for the account we
>> want it to use, but there are countless ways you could go about it
>> in your environment.
>> --
>> Jeremy Stanley
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi all,
Back with the same error.
Did a complete (clean) install based on rasselin's tutorial, now i have a
working jenkins master + a dedicated cloud provider.
Testing with noop looks ok, but dsvm-tempest-full returns NOT_REGISTERED.

Here is some debug.log:

2015-01-09 14:08:06,772 DEBUG zuul.IndependentPipelineManager: Found job
dsvm-tempest-full for change 
2015-01-09 14:08:06,773 INFO zuul.Gearman: Launch job dsvm-tempest-full for
change  with dependent changes []
2015-01-09 14:08:06,773 DEBUG zuul.Gearman: Custom parameter function used
for job dsvm-tempest-full, change: ,
params: {'BASE_LOG_PATH': '85/139585/15/check', 'ZUUL_PIPELINE': 'check',
'OFFLINE_NODE_WHEN_COMPLETE': '1', 'ZUUL_UUID':
'fa4ca39e02b14d1d864725441e301eb0', 'LOG_PATH':
'85/139585/15/check/dsvm-tempest-full/fa4ca39', 'ZUUL_CHANGE_IDS':
u'139585,15', 'ZUUL_PATCHSET': '15', 'ZUUL_BRANCH': u'master', 'ZUUL_REF':
u'refs/zuul/master/Z4efb72c817fb4ab39b67eb93fa8177ea', 'ZUUL_COMMIT':
u'97c142345b12bdf6a48c89b00f0d4d7811ce4a55', 'ZUUL_URL': u'
http://10.100.128.3/p/', 'ZUUL_CHANGE': '139585', 'ZUUL_CHANGES':
u'openstack-dev/sandbox:master:refs/changes/85/139585/15', 'ZUUL_PROJECT':
'openstack-dev/sandbox'}
...
2015-01-09 14:08:06,837 DEBUG zuul.Gearman: Function
build:dsvm-tempest-full is not registered
2015-01-09 14:08:06,837 ERROR zuul.Gearman: Job  is not registered with Gearman
2015-01-09 14:08:06,837 INFO zuul.Gearman: Build  complete, result NOT_REGISTERED
2015-01-09 14:08:06,837 DEBUG zuul.Scheduler: Adding complete event for
build: >
2015-01-09 14:08:06,837 DEBUG zuul.Scheduler: Done adding complete event
for build: >
2015-01-09 14:08:06,837 DEBUG zuul.IndependentPipelineManager: Adding build
> of job dsvm-tempest-full to item  in check>

So it seems that Zuul sees the job, but Gearman returns "is not registered".

Any idea how to register it? I see it in Jenkins GUI.
The only warning i see in Jenkins GUI is:
There’s no slave/cloud that matches this assignment. Did you mean ‘master’
instead of ‘devstack_slave’?

On the cloud provider gui i see instances with names like (
d-p-c-TIMESTAMP.template.openstack.org) spawning and running and some
deleting.

Thanks,

Eduard


On Tue, Jan 6, 2015 at 7:29 PM, Asselin, Ramy  wrote:

>  Gearman worker threads is what is needed to actually run the job. You
> need to type ‘status’ to get the results. It shouldn’t be empty since you
> stated the job actually ran (and failed tempest)
>
> Publishing the result is controlled here in the zuul layout.yaml file [1].
> Make sure you’re not using the ‘silent’ pipeline which (obviously) won’t
> publish the result. Manual is here [2]
>
> You’ll need a log server to host the uploaded log files. You can set one
> up like –infra’s using this [3] or WIP [4]
>
>
>
> Ramy
>
>
>
> [1]
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/zuul/layout.yaml#L22
>
> [2] http://ci.openstack.org/zuul/index.html
>
> [3]
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_log_server.sh
>
> [4] https://review.openstack.org/#/c/138913/
>
>
>
> *From:* Punith S [mailto:punit...@cloudbyte.com]
> *Sent:* Monday, January 05, 2015 10:22 PM
> *To:* Asselin, Ramy
> *Cc:* Eduard Matei; OpenStack Development Mailing List (not for usage
> questions)
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> thanks ramy :)
>
> i have setup the CI , but our dsvm-tempest-full job is failing due to some
> failures on running tempest.
> but how do we publish these failures to sandbox project.
> my gearman service is not showing any worker threads
>
> root@cimaster:/# telnet 127.0.0.1 4730
>
> Trying 127.0.0.1...
>
> Connected to 127.0.0.1.
>
> Escape character is '^]'.
>
>
>
> thanks
>
>
>
> On Sun, Jan 4, 2015 at 10:23 PM, Asselin, Ramy 
> wrote:
>
>  Did you try asking the friendly folks on IRC freenode #openstack-infra?
>
>
>
> You can also try:
>
> Rebooting.
>
> Delete all the Jenkins jobs and reloading them.
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, December 26, 2014 1:30 AM
> *To:* Punith S
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> Asselin, Ramy
>
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> @Asselin:
>
> Regarding the "few items you can try": i tried eve

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

@Asselin:
Regarding the "few items you can try": i tried everything, the job still
appears NOT_REGISTERED.
I'll see next week if i can do a clean install on another jenkins master.

Thanks for your help,
Eduard

On Fri, Dec 26, 2014 at 11:23 AM, Punith S  wrote:

> hello,
>
> i have setup the CI environment for our cloudbyte storage, running a
> master jenkins vm and a slave node vm running devstack.
>
> i have followed the jay's blog using asselin's scripts from github.
>
> all i need to do is to test our cloudbyte cinder driver against the cinder
> tempest suit.
>
> currently the noop-check-communication job is coming of successfully on
> openstack-dev/sandbox project
>
> but the *dvsm full tempest *job is failing due to an error in failing to
> upload the images to the glance service from swift.
>
> how can i hack the dsvm tempest full job so that it only installs my
> required services like cinder,nova,horizon etc. ?
>
> does modifying the devstack gate scripts help ?
>
> i'm attaching the links for the failure of dsvm-tempest-full job
>
> devstacklog.txt - http://paste.openstack.org/show/154779/
> devstack.txt.summary - http://paste.openstack.org/show/154780/
>
> thanks
>
>
>
>
> On Tue, Dec 23, 2014 at 8:46 PM, Asselin, Ramy 
> wrote:
>
>>  You should use 14.04 for the slave. The limitation for using 12.04 is
>> only for the master since zuul’s apache configuration is WIP on 14.04 [1],
>> and zuul does not run on the slave.
>>
>> Ramy
>>
>> [1] https://review.openstack.org/#/c/141518/
>>
>> *From:* Punith S [mailto:punit...@cloudbyte.com]
>> *Sent:* Monday, December 22, 2014 11:37 PM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Asselin,
>>
>>
>>
>> i'm following your readme https://github.com/rasselin/os-ext-testing
>>
>> for setting up our cloudbyte CI on two ubuntu 12.04 VM's(master and slave)
>>
>>
>>
>> currently the scripts and setup went fine as followed with the document.
>>
>>
>>
>> now both master and slave have been connected successfully, but in order
>> to run the tempest integration test against our proposed cloudbyte cinder
>> driver for kilo, we need to have devstack installed in the slave.(in my
>> understanding)
>>
>>
>>
>> but on installing the master devstack i'm getting permission issues in
>> 12.04 in executing ./stack.sh since master devstack suggests the 14.04 or
>> 13.10 ubuntu. and on contrary running install_slave.sh is failing on 13.10
>> due to puppet modules on found error.
>>
>>
>>
>>  is there a way to get this work ?
>>
>>
>>
>> thanks in advance
>>
>>
>>
>> On Mon, Dec 22, 2014 at 11:10 PM, Asselin, Ramy 
>> wrote:
>>
>>  Eduard,
>>
>>
>>
>> A few items you can try:
>>
>> 1.   Double-check that the job is in Jenkins
>>
>> a.   If not, then that’s the issue
>>
>> 2.   Check that the processes are running correctly
>>
>> a.   ps -ef | grep zuul
>>
>>i.  Should
>> have 2 zuul-server & 1 zuul-merger
>>
>> b.  ps -ef | grep Jenkins
>>
>>        i.  Should
>> have 1 /usr/bin/daemon --name=jenkins & 1 /usr/bin/java
>>
>> 3.   In Jenkins, Manage Jenkins, Gearman Plugin Config, “Test
>> Connection”
>>
>> 4.   Stop and Zuul & Jenkins. Start Zuul & Jenkins
>>
>> a.   service Jenkins stop
>>
>> b.  service zuul stop
>>
>> c.   service zuul-merger stop
>>
>> d.  service Jenkins start
>>
>> e.  service zuul start
>>
>> f.service zuul-merger start
>>
>>
>>
>> Otherwise, I suggest you ask in #openstack-infra irc channel.
>>
>>
>>
>> Ramy
>>
>>
>>
>> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
>> *Sent:* Sunday, December 21, 2014 11:01 PM
>>
>>
>> *To:* Asselin, Ramy
>> *Cc:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Thanks Ramy,
>>
>>
>>
>> Unfortunately i don'

Re: [openstack-dev] [OpenStack-dev][nova-net]Floating ip assigned as /32 from the start of the range

[Eduard Matei]

Thanks,
I managed to get it working by deleting the public pool (which was the
whole 10.100.X.X subnet) and creating a new pool 10.100.129.X.
This gives me control over which ips are assignable to the vms.

Eduard.

On Mon, Dec 22, 2014 at 7:30 PM, Vishvananda Ishaya 
wrote:
>
> Floating ips are always added to the host as a /32. You will need one ip
> on the
> compute host from the floating range with the /16 prefix (which it will
> use for
> natting instances without floating ips as well).
>
> In other words you should manually assign an ip from 10.100.130.X/16 to
> each
> compute node and set that value as routing_source_ip=10.100.130.X (or
> my_ip) in
> nova.conf.
>
> Vish
> On Dec 19, 2014, at 7:00 AM, Eduard Matei 
> wrote:
>
> Hi,
> I'm trying to create a vm and assign it an ip in range 10.100.130.0/16.
> On the host, the ip is assigned to br100 as  inet 10.100.0.3/32 scope
> global br100
> instead of 10.100.130.X/16, so it's not reachable from the outside.
>
> The localrc.conf :
> FLOATING_RANGE=10.100.130.0/16
>
> Any idea what to change?
>
> Thanks,
> Eduard
>
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
>
>
>
> *CloudFounders, The Private Cloud Software Company*
>
> Disclaimer:
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed.
> If you are not the named addressee or an employee or agent responsible for 
> delivering this message to the named addressee, you are hereby notified that 
> you are not authorized to read, print, retain, copy or disseminate this 
> message or any part of it. If you have received this email in error we 
> request you to notify us by reply e-mail and to delete all electronic files 
> of the message. If you are not the intended recipient you are notified that 
> disclosing, copying, distributing or taking any action in reliance on the 
> contents of this information is strictly prohibited.
> E-mail transmission cannot be guaranteed to be secure or error free as 
> information could be intercepted, corrupted, lost, destroyed, arrive late or 
> incomplete, or contain viruses. The sender therefore does not accept 
> liability for any errors or omissions in the content of this message, and 
> shall have no liability for any loss or damage suffered by the user, which 
> arise as a result of e-mail transmission.
>
>  ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Thanks Ramy,

Unfortunately i don't see dsvm-tempest-full in the "status" output.
Any idea how i can get it "registered"?

Thanks,
Eduard

On Fri, Dec 19, 2014 at 9:43 PM, Asselin, Ramy  wrote:
>
>  Eduard,
>
>
>
> If you run this command, you can see which jobs are registered:
>
> >telnet localhost 4730
>
>
>
> >status
>
>
>
> There are 3 numbers per job: queued, running and workers that can run job.
> Make sure the job is listed & last ‘workers’ is non-zero.
>
>
>
> To run the job again without submitting a patch set, leave a “recheck”
> comment on the patch & make sure your zuul layout.yaml is configured to
> trigger off that comment. For example [1].
>
> Be sure to use the sandbox repository. [2]
>
> I’m not aware of other ways.
>
>
>
> Ramy
>
>
>
> [1]
> https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L20
>
> [2] https://github.com/openstack-dev/sandbox
>
>
>
>
>
>
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Friday, December 19, 2014 3:36 AM
> *To:* Asselin, Ramy
> *Cc:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi all,
>
> After a little struggle with the config scripts i managed to get a working
> setup that is able to process openstack-dev/sandbox and run
> noop-check-comunication.
>
>
>
> Then, i tried enabling dsvm-tempest-full job but it keeps returning
> "NOT_REGISTERED"
>
>
>
> 2014-12-19 12:07:14,683 INFO zuul.IndependentPipelineManager: Change
>  depends on changes []
>
> 2014-12-19 12:07:14,683 INFO zuul.Gearman: Launch job
> noop-check-communication for change  with
> dependent changes []
>
> 2014-12-19 12:07:14,693 INFO zuul.Gearman: Launch job dsvm-tempest-full
> for change  with dependent changes []
>
> 2014-12-19 12:07:14,694 ERROR zuul.Gearman: Job  handle: None name: build:dsvm-tempest-full unique:
> a9199d304d1140a8bf4448dfb1ae42c1> is not registered with Gearman
>
> 2014-12-19 12:07:14,694 INFO zuul.Gearman: Build  handle: None name: build:dsvm-tempest-full unique:
> a9199d304d1140a8bf4448dfb1ae42c1> complete, result NOT_REGISTERED
>
> 2014-12-19 12:07:14,765 INFO zuul.Gearman: Build  handle: H:127.0.0.1:2 name: build:noop-check-communication unique:
> 333c6ea077324a788e3c37a313d872c5> started
>
> 2014-12-19 12:07:14,910 INFO zuul.Gearman: Build  handle: H:127.0.0.1:2 name: build:noop-check-communication unique:
> 333c6ea077324a788e3c37a313d872c5> complete, result SUCCESS
>
> 2014-12-19 12:07:14,916 INFO zuul.IndependentPipelineManager: Reporting
> change , actions: [ , {'verified': -1}>]
>
>
>
> Nodepoold's log show no reference to dsvm-tempest-full and neither
> jenkins' logs.
>
>
>
> Any idea how to enable this job?
>
>
>
> Also, i got the "Cloud provider" setup and i can access it from the
> jenkins master.
>
> Any idea how i can manually trigger dsvm-tempest-full job to run and test
> the cloud provider without having to push a review to Gerrit?
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Thu, Dec 18, 2014 at 7:52 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Thanks for the input.
>
>
>
> I managed to get another master working (on Ubuntu 13.10), again with some
> issues since it was already setup.
>
> I'm now working towards setting up the slave.
>
>
>
> Will add comments to those reviews.
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Thu, Dec 18, 2014 at 7:42 PM, Asselin, Ramy 
> wrote:
>
>  Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that
> the referenced script is just a wrapper that pulls all the latest from
> various locations in openstack-infra, e.g. [2].
>
> Ubuntu 14.04 support is WIP [3]
>
> FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please
> add your comments if this interests you.
>
>
>
> [1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
>
> [2]
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
>
> [3] https://review.openstack.org/#/c/141518/
>
> [4] https://review.openstack.org/#/c/139745/
>
>
>
>
>
> *From:* Punith S [mailto:punit...@cloudbyte.com]
> *Sent:* Thursday, December 18, 2014 3:12 AM
> *To:* OpenStack Development Mailing List (not for usage questions);
> Eduard Matei
>
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help

[openstack-dev] [OpenStack-dev][nova-net]Floating ip assigned as /32 from the start of the range

[Eduard Matei]

Hi,
I'm trying to create a vm and assign it an ip in range 10.100.130.0/16.
On the host, the ip is assigned to br100 as  inet 10.100.0.3/32 scope
global br100
instead of 10.100.130.X/16, so it's not reachable from the outside.

The localrc.conf :
FLOATING_RANGE=10.100.130.0/16

Any idea what to change?

Thanks,
Eduard


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi all,
After a little struggle with the config scripts i managed to get a working
setup that is able to process openstack-dev/sandbox and run
noop-check-comunication.

Then, i tried enabling dsvm-tempest-full job but it keeps returning
"NOT_REGISTERED"

2014-12-19 12:07:14,683 INFO zuul.IndependentPipelineManager: Change
 depends on changes []
2014-12-19 12:07:14,683 INFO zuul.Gearman: Launch job
noop-check-communication for change  with
dependent changes []
2014-12-19 12:07:14,693 INFO zuul.Gearman: Launch job dsvm-tempest-full for
change  with dependent changes []
2014-12-19 12:07:14,694 ERROR zuul.Gearman: Job  is not registered with Gearman
2014-12-19 12:07:14,694 INFO zuul.Gearman: Build  complete, result NOT_REGISTERED
2014-12-19 12:07:14,765 INFO zuul.Gearman: Build  started
2014-12-19 12:07:14,910 INFO zuul.Gearman: Build  complete, result SUCCESS
2014-12-19 12:07:14,916 INFO zuul.IndependentPipelineManager: Reporting
change , actions: [, {'verified': -1}>]

Nodepoold's log show no reference to dsvm-tempest-full and neither jenkins'
logs.

Any idea how to enable this job?

Also, i got the "Cloud provider" setup and i can access it from the jenkins
master.
Any idea how i can manually trigger dsvm-tempest-full job to run and test
the cloud provider without having to push a review to Gerrit?

Thanks,
Eduard

On Thu, Dec 18, 2014 at 7:52 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:
>
> Thanks for the input.
>
> I managed to get another master working (on Ubuntu 13.10), again with some
> issues since it was already setup.
> I'm now working towards setting up the slave.
>
> Will add comments to those reviews.
>
> Thanks,
> Eduard
>
> On Thu, Dec 18, 2014 at 7:42 PM, Asselin, Ramy 
> wrote:
>
>>  Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that
>> the referenced script is just a wrapper that pulls all the latest from
>> various locations in openstack-infra, e.g. [2].
>>
>> Ubuntu 14.04 support is WIP [3]
>>
>> FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please
>> add your comments if this interests you.
>>
>>
>>
>> [1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
>>
>> [2]
>> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
>>
>> [3] https://review.openstack.org/#/c/141518/
>>
>> [4] https://review.openstack.org/#/c/139745/
>>
>>
>>
>>
>>
>> *From:* Punith S [mailto:punit...@cloudbyte.com]
>> *Sent:* Thursday, December 18, 2014 3:12 AM
>> *To:* OpenStack Development Mailing List (not for usage questions);
>> Eduard Matei
>>
>> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
>> help setting up CI
>>
>>
>>
>> Hi Eduard
>>
>>
>>
>> we tried running
>> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
>>
>> on ubuntu master 12.04, and it appears to be working fine on 12.04.
>>
>>
>>
>> thanks
>>
>>
>>
>> On Thu, Dec 18, 2014 at 1:57 PM, Eduard Matei <
>> eduard.ma...@cloudfounders.com> wrote:
>>
>>  Hi,
>>
>> Seems i can't install using puppet on the jenkins master using
>> install_master.sh from
>> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
>> because it's running Ubuntu 11.10 and it appears unsupported.
>>
>> I managed to install puppet manually on master and everything else fails
>>
>> So i'm trying to manually install zuul and nodepool and jenkins job
>> builder, see where i end up.
>>
>>
>>
>> The slave looks complete, got some errors on running install_slave so i
>> ran parts of the script manually, changing some params and it appears
>> installed but no way to test it without the master.
>>
>>
>>
>> Any ideas welcome.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Eduard
>>
>>
>>
>> On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy 
>> wrote:
>>
>>   Manually running the script requires a few environment settings. Take
>> a look at the README here:
>>
>> https://github.com/openstack-infra/devstack-gate
>>
>>
>>
>> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
>> jaypipes).
>>
>> https://github.com/rasselin/os-ext-testing
>>
>>
>>
>> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
>> but zuul.
>>
>>
>>

Re: [openstack-dev] [OpenStack-dev][Cinder] Driver stats return value: infinite or unavailable

[Eduard Matei]

Thanks John,
I updated to unknown.

Eduard

On Thu, Dec 18, 2014 at 8:09 PM, John Griffith 
wrote:

> On Thu, Dec 18, 2014 at 1:56 AM, Eduard Matei
>  wrote:
> > Hi everyone,
> >
> > We're in a bit of a predicament regarding review:
> > https://review.openstack.org/#/c/130733/
> >
> > Two days ago it got a -1 from John G asking to change infinite to
> > unavailable although the docs clearly say that "If the driver is unable
> to
> > provide a value for free_capacity_gb or total_capacity_gb, keywords can
> be
> > provided instead. Please use ‘unknown’ if the array cannot report the
> value
> > or ‘infinite’ if the array has no upper limit."
> > (http://docs.openstack.org/developer/cinder/devref/drivers.html)
> >
> > After i changed it, came Walter A. Boring IV and gave another -1 saying
> we
> > should return infinite.
> >
> > Since we use S3 as a backend and it has no upper limit (technically
> there is
> > a limit but for the purposes of our driver there's no limit as the
> backend
> > is "elastic") we could return infinite.
> >
> > Anyway, the problem is that now we missed the K-1 merge window although
> the
> > driver passed all tests (including cert tests).
> >
> > So please can someone decide which is the correct value so we can use
> that
> > and get the patched approved (unless there are other issues).
> >
> > Thanks,
> > Eduard
> > --
> >
> > Eduard Biceri Matei, Senior Software Developer
> > www.cloudfounders.com
> >  | eduard.ma...@cloudfounders.com
> >
> >
> >
> > CloudFounders, The Private Cloud Software Company
> >
> > Disclaimer:
> > This email and any files transmitted with it are confidential and
> intended
> > solely for the use of the individual or entity to whom they are
> addressed.
> > If you are not the named addressee or an employee or agent responsible
> for
> > delivering this message to the named addressee, you are hereby notified
> that
> > you are not authorized to read, print, retain, copy or disseminate this
> > message or any part of it. If you have received this email in error we
> > request you to notify us by reply e-mail and to delete all electronic
> files
> > of the message. If you are not the intended recipient you are notified
> that
> > disclosing, copying, distributing or taking any action in reliance on the
> > contents of this information is strictly prohibited.
> > E-mail transmission cannot be guaranteed to be secure or error free as
> > information could be intercepted, corrupted, lost, destroyed, arrive
> late or
> > incomplete, or contain viruses. The sender therefore does not accept
> > liability for any errors or omissions in the content of this message, and
> > shall have no liability for any loss or damage suffered by the user,
> which
> > arise as a result of e-mail transmission.
> >
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> Hi Eduard,
>
> First, I owe you an apology; I stated "unavailable" in the review, but
> should've stated "unknown".  We're in the process of trying to
> eliminate the reporting of infinite as it screwed up the weighing
> scheduler.
>
> Note that Zhiteng adjusted the scheduler so this isn't such a big deal
> anymore by down-grading the handling of infinite and unknown [1].
>
> Anyway, my suggestion to not use infinite is because in the coming
> weeks I'd like to remove infinite from the stats reporting altogether,
> and for those backends that for whatever reason don't know how much
> capacity they have use a more accurate report of "unknown".
>
> Sorry for the confusion, I think the comments on your review have been
> updated to reflect this, if not I'll do that next.
>
> Thanks,
> John
>
> [1]:
> https://github.com/openstack/cinder/commit/ee9d30a73a74a2e1905eacc561c1b5188b62ca75
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If 

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Thanks for the input.

I managed to get another master working (on Ubuntu 13.10), again with some
issues since it was already setup.
I'm now working towards setting up the slave.

Will add comments to those reviews.

Thanks,
Eduard

On Thu, Dec 18, 2014 at 7:42 PM, Asselin, Ramy  wrote:

>  Yes, Ubuntu 12.04 is tested as mentioned in the readme [1]. Note that
> the referenced script is just a wrapper that pulls all the latest from
> various locations in openstack-infra, e.g. [2].
>
> Ubuntu 14.04 support is WIP [3]
>
> FYI, there’s a spec to get an in-tree 3rd party ci solution [4]. Please
> add your comments if this interests you.
>
>
>
> [1] https://github.com/rasselin/os-ext-testing/blob/master/README.md
>
> [2]
> https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L29
>
> [3] https://review.openstack.org/#/c/141518/
>
> [4] https://review.openstack.org/#/c/139745/
>
>
>
>
>
> *From:* Punith S [mailto:punit...@cloudbyte.com]
> *Sent:* Thursday, December 18, 2014 3:12 AM
> *To:* OpenStack Development Mailing List (not for usage questions);
> Eduard Matei
>
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi Eduard
>
>
>
> we tried running
> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
>
> on ubuntu master 12.04, and it appears to be working fine on 12.04.
>
>
>
> thanks
>
>
>
> On Thu, Dec 18, 2014 at 1:57 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi,
>
> Seems i can't install using puppet on the jenkins master using
> install_master.sh from
> https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
> because it's running Ubuntu 11.10 and it appears unsupported.
>
> I managed to install puppet manually on master and everything else fails
>
> So i'm trying to manually install zuul and nodepool and jenkins job
> builder, see where i end up.
>
>
>
> The slave looks complete, got some errors on running install_slave so i
> ran parts of the script manually, changing some params and it appears
> installed but no way to test it without the master.
>
>
>
> Any ideas welcome.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy 
> wrote:
>
>   Manually running the script requires a few environment settings. Take a
> look at the README here:
>
> https://github.com/openstack-infra/devstack-gate
>
>
>
> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
> jaypipes).
>
> https://github.com/rasselin/os-ext-testing
>
>
>
> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
> but zuul.
>
>
>
> There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample
>
>
>
> You can ask more questions in IRC freenode #openstack-cinder. (irc#
> asselin)
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Tuesday, December 16, 2014 12:41 AM
> *To:* Bailey, Darragh
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> OpenStack
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
>
>
> Can someone point me to some working documentation on how to setup third
> party CI? (joinfu's instructions don't seem to work, and manually running
> devstack-gate scripts fails:
>
> Running gate_hook
>
> Job timeout set to: 163 minutes
>
> timeout: failed to run command 
> ‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory
>
> ERROR: the main setup script run by this job failed - exit code: 127
>
> please look at the relevant log files to determine the root cause
>
> Cleaning up host
>
> ... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
>
>  Build step 'Execute shell' marked build as failure.
>
>
>
> I have a working Jenkins slave with devstack and our internal libraries, i
> have Gerrit Trigger Plugin working and triggering on patches created, i
> just need the actual job contents so that it can get to comment with the
> test results.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi Darragh, thanks for your input
>
>
>
> I double

[openstack-dev] [OpenStack-dev][Cinder] Driver stats return value: infinite or unavailable

[Eduard Matei]

Hi everyone,

We're in a bit of a predicament regarding review:
https://review.openstack.org/#/c/130733/

Two days ago it got a -1 from John G asking to change infinite to
unavailable although the docs clearly say that "If the driver is unable to
provide a value for free_capacity_gb or total_capacity_gb, keywords can be
provided instead. Please use ‘unknown’ if the array cannot report the value
or ‘infinite’ if the array has no upper limit." (
http://docs.openstack.org/developer/cinder/devref/drivers.html)

After i changed it, came Walter A. Boring IV and gave another -1 saying we
should return infinite.

Since we use S3 as a backend and it has no upper limit (technically there
is a limit but for the purposes of our driver there's no limit as the
backend is "elastic") we could return infinite.

Anyway, the problem is that now we missed the K-1 merge window although the
driver passed all tests (including cert tests).

So please can someone decide which is the correct value so we can use that
and get the patched approved (unless there are other issues).

Thanks,
Eduard
-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi,
Seems i can't install using puppet on the jenkins master using
install_master.sh from
https://raw.githubusercontent.com/rasselin/os-ext-testing/master/puppet/install_master.sh
because it's running Ubuntu 11.10 and it appears unsupported.
I managed to install puppet manually on master and everything else fails
So i'm trying to manually install zuul and nodepool and jenkins job
builder, see where i end up.

The slave looks complete, got some errors on running install_slave so i ran
parts of the script manually, changing some params and it appears installed
but no way to test it without the master.

Any ideas welcome.

Thanks,

Eduard

On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy  wrote:

>  Manually running the script requires a few environment settings. Take a
> look at the README here:
>
> https://github.com/openstack-infra/devstack-gate
>
>
>
> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
> jaypipes).
>
> https://github.com/rasselin/os-ext-testing
>
>
>
> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
> but zuul.
>
>
>
> There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample
>
>
>
> You can ask more questions in IRC freenode #openstack-cinder. (irc#
> asselin)
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Tuesday, December 16, 2014 12:41 AM
> *To:* Bailey, Darragh
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> OpenStack
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
>
>
> Can someone point me to some working documentation on how to setup third
> party CI? (joinfu's instructions don't seem to work, and manually running
> devstack-gate scripts fails:
>
> Running gate_hook
>
> Job timeout set to: 163 minutes
>
> timeout: failed to run command 
> ‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory
>
> ERROR: the main setup script run by this job failed - exit code: 127
>
> please look at the relevant log files to determine the root cause
>
> Cleaning up host
>
> ... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
>
>  Build step 'Execute shell' marked build as failure.
>
>
>
> I have a working Jenkins slave with devstack and our internal libraries, i
> have Gerrit Trigger Plugin working and triggering on patches created, i
> just need the actual job contents so that it can get to comment with the
> test results.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi Darragh, thanks for your input
>
>
>
> I double checked the job settings and fixed it:
>
> - build triggers is set to Gerrit event
>
> - Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin
> and tested separately)
>
> - Trigger on: Patchset Created
>
> - Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
> Type: Path, Pattern: ** (was Type Plain on both)
>
> Now the job is triggered by commit on openstack-dev/sandbox :)
>
>
>
> Regarding the Query and Trigger Gerrit Patches, i found my patch using
> query: status:open project:openstack-dev/sandbox change:139585 and i can
> trigger it manually and it executes the job.
>
>
>
> But i still have the problem: what should the job do? It doesn't actually
> do anything, it doesn't run tests or comment on the patch.
>
> Do you have an example of job?
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh  wrote:
>
> Hi Eduard,
>
>
> I would check the trigger settings in the job, particularly which "type"
> of pattern matching is being used for the branches. Found it tends to be
> the spot that catches most people out when configuring jobs with the
> Gerrit Trigger plugin. If you're looking to trigger against all branches
> then you would want "Type: Path" and "Pattern: **" appearing in the UI.
>
> If you have sufficient access using the 'Query and Trigger Gerrit
> Patches' page accessible from the main view will make it easier to
> confirm that your Jenkins instance can actually see changes in gerrit
> for the given project (which should mean that it can see the
> corresponding events as well). Can also use the same page to re-trigger
> for Patchse

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Thanks, i'll have a look.

Eduard

On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy  wrote:

>  Manually running the script requires a few environment settings. Take a
> look at the README here:
>
> https://github.com/openstack-infra/devstack-gate
>
>
>
> Regarding cinder, I’m using this repo to run our cinder jobs (fork from
> jaypipes).
>
> https://github.com/rasselin/os-ext-testing
>
>
>
> Note that this solution doesn’t use the Jenkins gerrit trigger pluggin,
> but zuul.
>
>
>
> There’s a sample job for cinder here. It’s in Jenkins Job Builder format.
>
>
> https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample
>
>
>
> You can ask more questions in IRC freenode #openstack-cinder. (irc#
> asselin)
>
>
>
> Ramy
>
>
>
> *From:* Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
> *Sent:* Tuesday, December 16, 2014 12:41 AM
> *To:* Bailey, Darragh
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> OpenStack
> *Subject:* Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help
> setting up CI
>
>
>
> Hi,
>
>
>
> Can someone point me to some working documentation on how to setup third
> party CI? (joinfu's instructions don't seem to work, and manually running
> devstack-gate scripts fails:
>
> Running gate_hook
>
> Job timeout set to: 163 minutes
>
> timeout: failed to run command 
> ‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory
>
> ERROR: the main setup script run by this job failed - exit code: 127
>
> please look at the relevant log files to determine the root cause
>
> Cleaning up host
>
> ... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)
>
>  Build step 'Execute shell' marked build as failure.
>
>
>
> I have a working Jenkins slave with devstack and our internal libraries, i
> have Gerrit Trigger Plugin working and triggering on patches created, i
> just need the actual job contents so that it can get to comment with the
> test results.
>
>
>
> Thanks,
>
>
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>  Hi Darragh, thanks for your input
>
>
>
> I double checked the job settings and fixed it:
>
> - build triggers is set to Gerrit event
>
> - Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin
> and tested separately)
>
> - Trigger on: Patchset Created
>
> - Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
> Type: Path, Pattern: ** (was Type Plain on both)
>
> Now the job is triggered by commit on openstack-dev/sandbox :)
>
>
>
> Regarding the Query and Trigger Gerrit Patches, i found my patch using
> query: status:open project:openstack-dev/sandbox change:139585 and i can
> trigger it manually and it executes the job.
>
>
>
> But i still have the problem: what should the job do? It doesn't actually
> do anything, it doesn't run tests or comment on the patch.
>
> Do you have an example of job?
>
>
>
> Thanks,
>
> Eduard
>
>
>
> On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh  wrote:
>
> Hi Eduard,
>
>
> I would check the trigger settings in the job, particularly which "type"
> of pattern matching is being used for the branches. Found it tends to be
> the spot that catches most people out when configuring jobs with the
> Gerrit Trigger plugin. If you're looking to trigger against all branches
> then you would want "Type: Path" and "Pattern: **" appearing in the UI.
>
> If you have sufficient access using the 'Query and Trigger Gerrit
> Patches' page accessible from the main view will make it easier to
> confirm that your Jenkins instance can actually see changes in gerrit
> for the given project (which should mean that it can see the
> corresponding events as well). Can also use the same page to re-trigger
> for PatchsetCreated events to see if you've set the patterns on the job
> correctly.
>
> Regards,
> Darragh Bailey
>
> "Nothing is foolproof to a sufficiently talented fool" - Unknown
>
> On 08/12/14 14:33, Eduard Matei wrote:
> > Resending this to dev ML as it seems i get quicker response :)
> >
> > I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
> > Patchset Created", chose as server the configured Gerrit server that
> > was previously tested, then added the project openstack-dev/sandbox
> > and saved.
> >

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi,

Can someone point me to some working documentation on how to setup third
party CI? (joinfu's instructions don't seem to work, and manually running
devstack-gate scripts fails:

Running gate_hook
Job timeout set to: 163 minutes
timeout: failed to run command
‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or
directory
ERROR: the main setup script run by this job failed - exit code: 127
please look at the relevant log files to determine the root cause
Cleaning up host
... this takes 3 - 4 minutes (logs at logs/devstack-gate-cleanup-host.txt.gz)

Build step 'Execute shell' marked build as failure.

I have a working Jenkins slave with devstack and our internal libraries, i
have Gerrit Trigger Plugin working and triggering on patches created, i
just need the actual job contents so that it can get to comment with the
test results.

Thanks,

Eduard

On Tue, Dec 9, 2014 at 1:59 PM, Eduard Matei  wrote:

> Hi Darragh, thanks for your input
>
> I double checked the job settings and fixed it:
> - build triggers is set to Gerrit event
> - Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin
> and tested separately)
> - Trigger on: Patchset Created
> - Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
> Type: Path, Pattern: ** (was Type Plain on both)
> Now the job is triggered by commit on openstack-dev/sandbox :)
>
> Regarding the Query and Trigger Gerrit Patches, i found my patch using
> query: status:open project:openstack-dev/sandbox change:139585 and i can
> trigger it manually and it executes the job.
>
> But i still have the problem: what should the job do? It doesn't actually
> do anything, it doesn't run tests or comment on the patch.
> Do you have an example of job?
>
> Thanks,
> Eduard
>
> On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh  wrote:
>
>> Hi Eduard,
>>
>>
>> I would check the trigger settings in the job, particularly which "type"
>> of pattern matching is being used for the branches. Found it tends to be
>> the spot that catches most people out when configuring jobs with the
>> Gerrit Trigger plugin. If you're looking to trigger against all branches
>> then you would want "Type: Path" and "Pattern: **" appearing in the UI.
>>
>> If you have sufficient access using the 'Query and Trigger Gerrit
>> Patches' page accessible from the main view will make it easier to
>> confirm that your Jenkins instance can actually see changes in gerrit
>> for the given project (which should mean that it can see the
>> corresponding events as well). Can also use the same page to re-trigger
>> for PatchsetCreated events to see if you've set the patterns on the job
>> correctly.
>>
>> Regards,
>> Darragh Bailey
>>
>> "Nothing is foolproof to a sufficiently talented fool" - Unknown
>>
>> On 08/12/14 14:33, Eduard Matei wrote:
>> > Resending this to dev ML as it seems i get quicker response :)
>> >
>> > I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
>> > Patchset Created", chose as server the configured Gerrit server that
>> > was previously tested, then added the project openstack-dev/sandbox
>> > and saved.
>> > I made a change on dev sandbox repo but couldn't trigger my job.
>> >
>> > Any ideas?
>> >
>> > Thanks,
>> > Eduard
>> >
>> > On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei
>> > > > <mailto:eduard.ma...@cloudfounders.com>> wrote:
>> >
>> > Hello everyone,
>> >
>> > Thanks to the latest changes to the creation of service accounts
>> > process we're one step closer to setting up our own CI platform
>> > for Cinder.
>> >
>> > So far we've got:
>> > - Jenkins master (with Gerrit plugin) and slave (with DevStack and
>> > our storage solution)
>> > - Service account configured and tested (can manually connect to
>> > review.openstack.org <http://review.openstack.org> and get events
>> > and publish comments)
>> >
>> > Next step would be to set up a job to do the actual testing, this
>> > is where we're stuck.
>> > Can someone please point us to a clear example on how a job should
>> > look like (preferably for testing Cinder on Kilo)? Most links
>> > we've found are broken, or tools/scripts are no longer working.
>> > Also, we cannot change the Jenkins master too much (it's owned by
>> >

Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Hi Darragh, thanks for your input

I double checked the job settings and fixed it:
- build triggers is set to Gerrit event
- Gerrit trigger server is "Gerrit" (configured from Gerrit Trigger Plugin
and tested separately)
- Trigger on: Patchset Created
- Gerrit Project: Type: Path, Pattern openstack-dev/sandbox, Branches:
Type: Path, Pattern: ** (was Type Plain on both)
Now the job is triggered by commit on openstack-dev/sandbox :)

Regarding the Query and Trigger Gerrit Patches, i found my patch using
query: status:open project:openstack-dev/sandbox change:139585 and i can
trigger it manually and it executes the job.

But i still have the problem: what should the job do? It doesn't actually
do anything, it doesn't run tests or comment on the patch.
Do you have an example of job?

Thanks,
Eduard

On Tue, Dec 9, 2014 at 1:13 PM, Bailey, Darragh  wrote:

> Hi Eduard,
>
>
> I would check the trigger settings in the job, particularly which "type"
> of pattern matching is being used for the branches. Found it tends to be
> the spot that catches most people out when configuring jobs with the
> Gerrit Trigger plugin. If you're looking to trigger against all branches
> then you would want "Type: Path" and "Pattern: **" appearing in the UI.
>
> If you have sufficient access using the 'Query and Trigger Gerrit
> Patches' page accessible from the main view will make it easier to
> confirm that your Jenkins instance can actually see changes in gerrit
> for the given project (which should mean that it can see the
> corresponding events as well). Can also use the same page to re-trigger
> for PatchsetCreated events to see if you've set the patterns on the job
> correctly.
>
> Regards,
> Darragh Bailey
>
> "Nothing is foolproof to a sufficiently talented fool" - Unknown
>
> On 08/12/14 14:33, Eduard Matei wrote:
> > Resending this to dev ML as it seems i get quicker response :)
> >
> > I created a job in Jenkins, added as Build Trigger: "Gerrit Event:
> > Patchset Created", chose as server the configured Gerrit server that
> > was previously tested, then added the project openstack-dev/sandbox
> > and saved.
> > I made a change on dev sandbox repo but couldn't trigger my job.
> >
> > Any ideas?
> >
> > Thanks,
> > Eduard
> >
> > On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei
> >  > <mailto:eduard.ma...@cloudfounders.com>> wrote:
> >
> > Hello everyone,
> >
> > Thanks to the latest changes to the creation of service accounts
> > process we're one step closer to setting up our own CI platform
> > for Cinder.
> >
> > So far we've got:
> > - Jenkins master (with Gerrit plugin) and slave (with DevStack and
> > our storage solution)
> > - Service account configured and tested (can manually connect to
> > review.openstack.org <http://review.openstack.org> and get events
> > and publish comments)
> >
> > Next step would be to set up a job to do the actual testing, this
> > is where we're stuck.
> > Can someone please point us to a clear example on how a job should
> > look like (preferably for testing Cinder on Kilo)? Most links
> > we've found are broken, or tools/scripts are no longer working.
> > Also, we cannot change the Jenkins master too much (it's owned by
> > Ops team and they need a list of tools/scripts to review before
> > installing/running so we're not allowed to experiment).
> >
> > Thanks,
> > Eduard
> >
> > --
> >
> > *Eduard Biceri Matei, Senior Software Developer*
> > www.cloudfounders.com
> > <http://www.cloudfounders.com/> | eduard.ma...@cloudfounders.com
> > <mailto:eduard.ma...@cloudfounders.com>
> >
> >
> >
> > *CloudFounders, The Private Cloud Software Company*
> >
> > Disclaimer:
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom
> > they are addressed.If you are not the named addressee or an
> > employee or agent responsible for delivering this message to the
> > named addressee, you are hereby notified that you are not
> > authorized to read, print, retain, copy or disseminate this
> > message or any part of it. If you have received this email in
> > error we request you to notify us by reply e-mail and to delete
> > all electronic files of the message. If you are not the intended
> > 

Re: [openstack-dev] [OpenStack-Infra][ThirdPartyCI] Need help setting up CI

[Eduard Matei]

Resending this to dev ML as it seems i get quicker response :)

I created a job in Jenkins, added as Build Trigger: "Gerrit Event: Patchset
Created", chose as server the configured Gerrit server that was previously
tested, then added the project openstack-dev/sandbox and saved.
I made a change on dev sandbox repo but couldn't trigger my job.

Any ideas?

Thanks,
Eduard

On Fri, Dec 5, 2014 at 10:32 AM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hello everyone,
>
> Thanks to the latest changes to the creation of service accounts process
> we're one step closer to setting up our own CI platform for Cinder.
>
> So far we've got:
> - Jenkins master (with Gerrit plugin) and slave (with DevStack and our
> storage solution)
> - Service account configured and tested (can manually connect to
> review.openstack.org and get events and publish comments)
>
> Next step would be to set up a job to do the actual testing, this is where
> we're stuck.
> Can someone please point us to a clear example on how a job should look
> like (preferably for testing Cinder on Kilo)? Most links we've found are
> broken, or tools/scripts are no longer working.
> Also, we cannot change the Jenkins master too much (it's owned by Ops team
> and they need a list of tools/scripts to review before installing/running
> so we're not allowed to experiment).
>
> Thanks,
> Eduard
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
>
>
>
> *CloudFounders, The Private Cloud Software Company*
>
> Disclaimer:
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed.
> If you are not the named addressee or an employee or agent responsible for 
> delivering this message to the named addressee, you are hereby notified that 
> you are not authorized to read, print, retain, copy or disseminate this 
> message or any part of it. If you have received this email in error we 
> request you to notify us by reply e-mail and to delete all electronic files 
> of the message. If you are not the intended recipient you are notified that 
> disclosing, copying, distributing or taking any action in reliance on the 
> contents of this information is strictly prohibited.
> E-mail transmission cannot be guaranteed to be secure or error free as 
> information could be intercepted, corrupted, lost, destroyed, arrive late or 
> incomplete, or contain viruses. The sender therefore does not accept 
> liability for any errors or omissions in the content of this message, and 
> shall have no liability for any loss or damage suffered by the user, which 
> arise as a result of e-mail transmission.
>
>


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [git] Rebase failed

[Eduard Matei]

Indeed, it started again the review process.
Thanks for your input.

Eduard

On Mon, Dec 8, 2014 at 10:56 AM, Gary Kotton  wrote:

>  Hi,
> The whole review process starts again from scratch :). You can feel free
> to reach out the guys who originally reviewed and then go from there. Good
> luck!
> Thanks
> Gary
>
>   From: Eduard Matei 
> Reply-To: OpenStack List 
> Date: Monday, December 8, 2014 at 10:25 AM
> To: OpenStack List 
> Subject: Re: [openstack-dev] [git] Rebase failed
>
>   Thanks guys,
> It seems one of the files i was trying to merge was actually removed by
> remote (?).
> So i removed it locally (git rm ... ) and now rebase worked, but now i had
> an extra patchset.
> Will this be merged automatically or does it need again reviewers ?
>
>  Thanks,
> Eduard
>
> On Mon, Dec 8, 2014 at 10:18 AM, Sylvain Bauza  wrote:
>
>>
>> Le 08/12/2014 09:13, Eli Qiao a écrit :
>>
>>
>> 在 2014年12月08日 16:05, Eduard Matei 写道:
>>
>> Hi,
>> My review got approved and it was ready to merge but automatic merge
>> failed.
>> I tried to rebase manually but it still fails.
>>
>>  I'm not very familiar with git, can someone give a hand?
>>
>>   git rebase -i master
>> error: could not apply db4a3bb... New Cinder volume driver for
>> openvstorage.
>>
>>   hi Eduard
>> yeah, you need to manually rebase the changes.
>> git status check which files should be changes (file name in red) and
>> find <<< in
>> the file , modify it. after doing that , git add , all
>> conflict files need to
>> be done, then git reabase --continue.
>>
>>
>>
>> Or you can just raise the magical wand and invoke "git mergetool" with
>> your favourite editor (vimdiff, kdiff3 or whatever else) and leave this
>> tool show you the difference in between the base branch (when the code
>> branched), the local branch (the master branch) and the remote branch (your
>> changes)
>>
>> My USD0.02
>>
>> -Sylvain
>>
>>
>>   When you have resolved this problem, run "git rebase --continue".
>> If you prefer to skip this patch, run "git rebase --skip" instead.
>> To check out the original branch and stop rebasing, run "git rebase
>> --abort".
>> Could not apply db4a3bb3645b27de7b12c0aa405bde3530dd19f8... New Cinder
>> volume driver for openvstorage.
>>  git rebase --continue
>> etc/cinder/cinder.conf.sample: needs merge
>> You must edit all merge conflicts and then
>> mark them as resolved using git add
>>
>>  Review is: https://review.openstack.org/#/c/130733/
>>
>>  Thanks,
>> Eduard
>>
>>  --
>>
>> *Eduard Biceri Matei, Senior Software Developer*
>> www.cloudfounders.com 
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cloudfounders.com_&d=AAMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=pEpAxsW74PTDHIs_rhDI9kuiQfsCjXLpYCYCIk64q1Y&s=IQjj8aQTsdRbn4yQZWNRU5pM3Ef5P6vSvRO4kruZtWg&e=>
>>  | eduard.ma...@cloudfounders.com
>>
>>
>> *CloudFounders, The Private Cloud Software Company*
>>
>> Disclaimer:
>> This email and any files transmitted with it are confidential and intended 
>> solely for the use of the individual or entity to whom they are addressed.If 
>> you are not the named addressee or an employee or agent responsible for 
>> delivering this message to the named addressee, you are hereby notified that 
>> you are not authorized to read, print, retain, copy or disseminate this 
>> message or any part of it. If you have received this email in error we 
>> request you to notify us by reply e-mail and to delete all electronic files 
>> of the message. If you are not the intended recipient you are notified that 
>> disclosing, copying, distributing or taking any action in reliance on the 
>> contents of this information is strictly prohibited.
>> E-mail transmission cannot be guaranteed to be secure or error free as 
>> information could be intercepted, corrupted, lost, destroyed, arrive late or 
>> incomplete, or contain viruses. The sender therefore does not accept 
>> liability for any errors or omissions in the content of this message, and 
>> shall have no liability for any loss or damage suffered by the user, which 
>> arise as a result of e-mail transmission.
>>
>>
>>
>> ___
>> OpenStack-dev mailing 
>> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailm

Re: [openstack-dev] [git] Rebase failed

[Eduard Matei]

Thanks guys,
It seems one of the files i was trying to merge was actually removed by
remote (?).
So i removed it locally (git rm ... ) and now rebase worked, but now i had
an extra patchset.
Will this be merged automatically or does it need again reviewers ?

Thanks,
Eduard

On Mon, Dec 8, 2014 at 10:18 AM, Sylvain Bauza  wrote:

>
> Le 08/12/2014 09:13, Eli Qiao a écrit :
>
>
> 在 2014年12月08日 16:05, Eduard Matei 写道:
>
> Hi,
> My review got approved and it was ready to merge but automatic merge
> failed.
> I tried to rebase manually but it still fails.
>
>  I'm not very familiar with git, can someone give a hand?
>
>   git rebase -i master
> error: could not apply db4a3bb... New Cinder volume driver for
> openvstorage.
>
>   hi Eduard
> yeah, you need to manually rebase the changes.
> git status check which files should be changes (file name in red) and find
> <<< in
> the file , modify it. after doing that , git add , all conflict
> files need to
> be done, then git reabase --continue.
>
>
>
> Or you can just raise the magical wand and invoke "git mergetool" with
> your favourite editor (vimdiff, kdiff3 or whatever else) and leave this
> tool show you the difference in between the base branch (when the code
> branched), the local branch (the master branch) and the remote branch (your
> changes)
>
> My USD0.02
>
> -Sylvain
>
>
>   When you have resolved this problem, run "git rebase --continue".
> If you prefer to skip this patch, run "git rebase --skip" instead.
> To check out the original branch and stop rebasing, run "git rebase
> --abort".
> Could not apply db4a3bb3645b27de7b12c0aa405bde3530dd19f8... New Cinder
> volume driver for openvstorage.
>  git rebase --continue
> etc/cinder/cinder.conf.sample: needs merge
> You must edit all merge conflicts and then
> mark them as resolved using git add
>
>  Review is: https://review.openstack.org/#/c/130733/
>
>  Thanks,
> Eduard
>
>  --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com | eduard.ma...@cloudfounders.com
>
>
> *CloudFounders, The Private Cloud Software Company*
>
> Disclaimer:
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed.If 
> you are not the named addressee or an employee or agent responsible for 
> delivering this message to the named addressee, you are hereby notified that 
> you are not authorized to read, print, retain, copy or disseminate this 
> message or any part of it. If you have received this email in error we 
> request you to notify us by reply e-mail and to delete all electronic files 
> of the message. If you are not the intended recipient you are notified that 
> disclosing, copying, distributing or taking any action in reliance on the 
> contents of this information is strictly prohibited.
> E-mail transmission cannot be guaranteed to be secure or error free as 
> information could be intercepted, corrupted, lost, destroyed, arrive late or 
> incomplete, or contain viruses. The sender therefore does not accept 
> liability for any errors or omissions in the content of this message, and 
> shall have no liability for any loss or damage suffered by the user, which 
> arise as a result of e-mail transmission.
>
>
>
> ___
> OpenStack-dev mailing 
> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> Thanks,
> Eli (Li Yong) Qiao
>
>
>
> ___
> OpenStack-dev mailing 
> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended

[openstack-dev] [git] Rebase failed

[Eduard Matei]

Hi,
My review got approved and it was ready to merge but automatic merge failed.
I tried to rebase manually but it still fails.

I'm not very familiar with git, can someone give a hand?

 git rebase -i master
error: could not apply db4a3bb... New Cinder volume driver for openvstorage.

When you have resolved this problem, run "git rebase --continue".
If you prefer to skip this patch, run "git rebase --skip" instead.
To check out the original branch and stop rebasing, run "git rebase
--abort".
Could not apply db4a3bb3645b27de7b12c0aa405bde3530dd19f8... New Cinder
volume driver for openvstorage.
 git rebase --continue
etc/cinder/cinder.conf.sample: needs merge
You must edit all merge conflicts and then
mark them as resolved using git add

Review is: https://review.openstack.org/#/c/130733/

Thanks,
Eduard

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova]Can't run tests

[Eduard Matei]

Aha, didn't catch that.
I just wanted to run the tests, didn't look at setting up a development
environment.

Thanks,
Eduard

On Tue, Nov 18, 2014 at 12:24 PM, Sylvain Bauza  wrote:

>
> Le 18/11/2014 10:11, Eduard Matei a écrit :
>
> Thanks Vineet.
> Indeed missing packages was the problem, for completeness here are the
> packages i needed in order to get virtual env running on Ubuntu 14.04.1 LTS
> -  libmysqlclient-dev
> - pkg-config
> - libvirt-dev
>
>  Maybe they can be included in the script that sets up the virtual env.
>
>
> No, please. This script is distro-agnostic, we don't need to carry all the
> dependencies issues.
> Actually, these installation instructions are already documented...
>
>
> http://git.openstack.org/cgit/openstack/nova/tree/doc/source/devref/development.environment.rst
>
> -Sylvain
>
>
>  Thanks,
> Eduard
>
> On Tue, Nov 18, 2014 at 10:27 AM, Vineet Menon 
> wrote:
>
>>  Hi,
>>
>>  You should install mysql-dev for your distro using apt-get or yum.
>>
>>  Regards,
>>
>> Vineet Menon
>>
>>
>>  On 18 November 2014 09:16, Eduard Matei 
>> wrote:
>>
>>>
>>> Hi,
>>> I'm trying to run nova's unittests to validate some changes we made for
>>> a LibvirtVolumeDriver class, but i only got errors:
>>>
>>>  with virtual env:
>>> ...
>>>  Downloading/unpacking MySQL-python (from -r
>>> /opt/stack/nova/test-requirements.txt (line 13))
>>>   Downloading MySQL-python-1.2.5.zip (108kB): 108kB downloaded
>>>   Running setup.py
>>> (path:/opt/stack/nova/.venv/build/MySQL-python/setup.py) egg_info for
>>> package MySQL-python
>>> sh: 1: mysql_config: not found
>>> Traceback (most recent call last):
>>>   File "", line 17, in 
>>>   File "/opt/stack/nova/.venv/build/MySQL-python/setup.py", line 17,
>>> in 
>>> metadata, options = get_config()
>>>   File "setup_posix.py", line 43, in get_config
>>> libs = mysql_config("libs_r")
>>>   File "setup_posix.py", line 25, in mysql_config
>>> raise EnvironmentError("%s not found" % (mysql_config.path,))
>>> EnvironmentError: mysql_config not found
>>> Complete output from command python setup.py egg_info:
>>> sh: 1: mysql_config: not found
>>>
>>>  Traceback (most recent call last):
>>>
>>>File "", line 17, in 
>>>
>>>File "/opt/stack/nova/.venv/build/MySQL-python/setup.py", line 17,
>>> in 
>>>
>>>  metadata, options = get_config()
>>>
>>>File "setup_posix.py", line 43, in get_config
>>>
>>>  libs = mysql_config("libs_r")
>>>
>>>File "setup_posix.py", line 25, in mysql_config
>>>
>>>  raise EnvironmentError("%s not found" % (mysql_config.path,))
>>>
>>>  EnvironmentError: mysql_config not found
>>>
>>>  
>>> Cleaning up...
>>> Command python setup.py egg_info failed with error code 1 in
>>> /opt/stack/nova/.venv/build/MySQL-python
>>> Storing debug log for failure in /root/.pip/pip.log
>>> Command "tools/with_venv.sh pip install --upgrade -r
>>> /opt/stack/nova/requirements.txt -r /opt/stack/nova/test-requirements.txt"
>>> failed.
>>> None
>>>
>>>  without virtual env:
>>>  :/opt/stack/nova# ./run_tests.sh -N
>>> Running ` python -m nova.openstack.common.lockutils python setup.py
>>> testr --testr-args='--subunit --concurrency 0  '`
>>> Non-zero exit code (2) from test listing.
>>> error: testr failed (3)
>>>
>>>
>>>  Ran 0 tests in 4.792s
>>>
>>>  OK
>>> Running flake8 ...
>>> **WARNING**:
>>> Running flake8 without virtual env may miss OpenStack HACKING detection
>>> bash: flake8: command not found
>>>
>>>  nova-manage --version
>>> 2014.2.1
>>>
>>>
>>>  Any idea how to fix this?
>>>
>>>  Thanks, Eduard
>>> --
>>>
>>> *Eduard Biceri Matei, Senior Software Developer*
>>> www.cloudfounders.com | eduard.ma...@cloudfounders.com 
>>> 
>>>
>>>
>>> *CloudFounders, The Private Cloud Software Company*
>>>
>>> Disclaimer:
>>

Re: [openstack-dev] [nova]Can't run tests

[Eduard Matei]

Thanks Vineet.
Indeed missing packages was the problem, for completeness here are the
packages i needed in order to get virtual env running on Ubuntu 14.04.1 LTS
-  libmysqlclient-dev
- pkg-config
- libvirt-dev

Maybe they can be included in the script that sets up the virtual env.

Thanks,
Eduard

On Tue, Nov 18, 2014 at 10:27 AM, Vineet Menon 
wrote:

> Hi,
>
> You should install mysql-dev for your distro using apt-get or yum.
>
> Regards,
>
> Vineet Menon
>
>
> On 18 November 2014 09:16, Eduard Matei 
> wrote:
>
>>
>> Hi,
>> I'm trying to run nova's unittests to validate some changes we made for a
>> LibvirtVolumeDriver class, but i only got errors:
>>
>> with virtual env:
>> ...
>> Downloading/unpacking MySQL-python (from -r
>> /opt/stack/nova/test-requirements.txt (line 13))
>>   Downloading MySQL-python-1.2.5.zip (108kB): 108kB downloaded
>>   Running setup.py
>> (path:/opt/stack/nova/.venv/build/MySQL-python/setup.py) egg_info for
>> package MySQL-python
>> sh: 1: mysql_config: not found
>> Traceback (most recent call last):
>>   File "", line 17, in 
>>   File "/opt/stack/nova/.venv/build/MySQL-python/setup.py", line 17,
>> in 
>> metadata, options = get_config()
>>   File "setup_posix.py", line 43, in get_config
>> libs = mysql_config("libs_r")
>>   File "setup_posix.py", line 25, in mysql_config
>> raise EnvironmentError("%s not found" % (mysql_config.path,))
>> EnvironmentError: mysql_config not found
>> Complete output from command python setup.py egg_info:
>> sh: 1: mysql_config: not found
>>
>> Traceback (most recent call last):
>>
>>   File "", line 17, in 
>>
>>   File "/opt/stack/nova/.venv/build/MySQL-python/setup.py", line 17, in
>> 
>>
>> metadata, options = get_config()
>>
>>   File "setup_posix.py", line 43, in get_config
>>
>> libs = mysql_config("libs_r")
>>
>>   File "setup_posix.py", line 25, in mysql_config
>>
>> raise EnvironmentError("%s not found" % (mysql_config.path,))
>>
>> EnvironmentError: mysql_config not found
>>
>> 
>> Cleaning up...
>> Command python setup.py egg_info failed with error code 1 in
>> /opt/stack/nova/.venv/build/MySQL-python
>> Storing debug log for failure in /root/.pip/pip.log
>> Command "tools/with_venv.sh pip install --upgrade -r
>> /opt/stack/nova/requirements.txt -r /opt/stack/nova/test-requirements.txt"
>> failed.
>> None
>>
>> without virtual env:
>> :/opt/stack/nova# ./run_tests.sh -N
>> Running ` python -m nova.openstack.common.lockutils python setup.py testr
>> --testr-args='--subunit --concurrency 0  '`
>> Non-zero exit code (2) from test listing.
>> error: testr failed (3)
>>
>>
>> Ran 0 tests in 4.792s
>>
>> OK
>> Running flake8 ...
>> **WARNING**:
>> Running flake8 without virtual env may miss OpenStack HACKING detection
>> bash: flake8: command not found
>>
>> nova-manage --version
>> 2014.2.1
>>
>>
>> Any idea how to fix this?
>>
>> Thanks, Eduard
>> --
>>
>> *Eduard Biceri Matei, Senior Software Developer*
>> www.cloudfounders.com
>>  | eduard.ma...@cloudfounders.com
>>
>>
>>
>> *CloudFounders, The Private Cloud Software Company*
>>
>> Disclaimer:
>> This email and any files transmitted with it are confidential and intended 
>> solely for the use of the individual or entity to whom they are addressed.
>> If you are not the named addressee or an employee or agent responsible for 
>> delivering this message to the named addressee, you are hereby notified that 
>> you are not authorized to read, print, retain, copy or disseminate this 
>> message or any part of it. If you have received this email in error we 
>> request you to notify us by reply e-mail and to delete all electronic files 
>> of the message. If you are not the intended recipient you are notified that 
>> disclosing, copying, distributing or taking any action in reliance on the 
>> contents of this information is strictly prohibited.
>> E-mail transmission cannot be guaranteed to be secure or error free as 
>> information could be intercepted, corrupted, lost, destroyed, arrive late or 
>> incomplete, or contain viruses. The sender therefore does not accept 
>> liabi

[openstack-dev] [nova]Can't run tests

[Eduard Matei]

Hi,
I'm trying to run nova's unittests to validate some changes we made for a
LibvirtVolumeDriver class, but i only got errors:

with virtual env:
...
Downloading/unpacking MySQL-python (from -r
/opt/stack/nova/test-requirements.txt (line 13))
  Downloading MySQL-python-1.2.5.zip (108kB): 108kB downloaded
  Running setup.py (path:/opt/stack/nova/.venv/build/MySQL-python/setup.py)
egg_info for package MySQL-python
sh: 1: mysql_config: not found
Traceback (most recent call last):
  File "", line 17, in 
  File "/opt/stack/nova/.venv/build/MySQL-python/setup.py", line 17, in

metadata, options = get_config()
  File "setup_posix.py", line 43, in get_config
libs = mysql_config("libs_r")
  File "setup_posix.py", line 25, in mysql_config
raise EnvironmentError("%s not found" % (mysql_config.path,))
EnvironmentError: mysql_config not found
Complete output from command python setup.py egg_info:
sh: 1: mysql_config: not found

Traceback (most recent call last):

  File "", line 17, in 

  File "/opt/stack/nova/.venv/build/MySQL-python/setup.py", line 17, in


metadata, options = get_config()

  File "setup_posix.py", line 43, in get_config

libs = mysql_config("libs_r")

  File "setup_posix.py", line 25, in mysql_config

raise EnvironmentError("%s not found" % (mysql_config.path,))

EnvironmentError: mysql_config not found


Cleaning up...
Command python setup.py egg_info failed with error code 1 in
/opt/stack/nova/.venv/build/MySQL-python
Storing debug log for failure in /root/.pip/pip.log
Command "tools/with_venv.sh pip install --upgrade -r
/opt/stack/nova/requirements.txt -r /opt/stack/nova/test-requirements.txt"
failed.
None

without virtual env:
:/opt/stack/nova# ./run_tests.sh -N
Running ` python -m nova.openstack.common.lockutils python setup.py testr
--testr-args='--subunit --concurrency 0  '`
Non-zero exit code (2) from test listing.
error: testr failed (3)


Ran 0 tests in 4.792s

OK
Running flake8 ...
**WARNING**:
Running flake8 without virtual env may miss OpenStack HACKING detection
bash: flake8: command not found

nova-manage --version
2014.2.1


Any idea how to fix this?

Thanks, Eduard
-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [OpenStack-dev][Nova] Migration stuck - resize/migrating

[Eduard Matei]

Hi,

I'm testing our cinder volume driver in the following setup:
- 2 nodes, ubuntu, devstack juno (2014.2.1)
- shared storage (common backend), our custom software solution + cinder
volume on shared storage
- 1 instance running on node 1, /instances directory on shared storage
- kvm, libvirt (with live migration flags)

Live migration of instance between nodes works perfectly.
Migrate simply blocks. The instance in in status Resize/Migrate, no errors
in n-cpu or n-sch, and it stays like that for over 8 hours (all night). I
thought it was copying the disk, but it's a 20GB sparse file with approx.
200 mb of data, and the nodes have 1Gbps link, so it should be a couple of
seconds.

Any difference between live migration and "migration"?
As i said, we use a "shared filesystem"-like storage solution so the volume
files and the instance files are visible on both nodes, so no data needs
copying.

I know it's tricky to debug since we use a custom cinder driver, but anyone
has any ideas where to start looking?

Thanks,
Eduard

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

[Eduard Matei]

Thanks Amit,

I'll do this as well.

Eduard

On Thu, Oct 30, 2014 at 3:09 PM, Amit Das  wrote:

> Hey Eduard,
>
> We posted our driver cert result by creating a new bugzilla ticket &
> tagging that as driver-cert.
>
> https://bugs.launchpad.net/cinder/+bug/1380126
>
>
>
> Regards,
> Amit
> *CloudByte Inc.* <http://www.cloudbyte.com/>
>
> On Thu, Oct 30, 2014 at 5:55 PM, Eduard Matei <
> eduard.ma...@cloudfounders.com> wrote:
>
>> Hi Mike,
>> I saw your comment on my review, but i need some more info regarding
>> "Your driver passes the cert test and the results are posted."
>> I assume you mean running cinder_driver_cert.sh - this is already passing
>> - but how do i get the results posted, and where?
>> I've been looking through some documentation and couldn't find a
>> definitive answer.
>>
>> Thanks
>> Eduard
>>
>>
>> On Thu, Oct 30, 2014 at 9:03 AM, Mike Perez  wrote:
>>
>>> On 19:41 Thu 04 Sep , Duncan Thomas wrote:
>>> > Hi
>>> >
>>> > during this week's cinder weekly meeting [1], we discussed plans for
>>> > Kilo, a discussion that started at the mid-cycle meetup [2]. The
>>> > outcome is that we (the cinder core team and extended community) want
>>> > to focus on stability and code clean-up in the Kilo release, and
>>> > paying off some of the technical debt we've built up over the past
>>> > couple of years [3]. In order to facilitate this, for the Kilo cycle:
>>> >
>>> > 1. New drivers must be submitted before K1 in order to be considered.
>>> > Any driver submitted after this date will be deferred until the L
>>> > cycle. We encourage submitters to get in early, even if you make K1
>>> > there is no guarantee of getting enough reviewer attention to get
>>> > merged.
>>> >
>>> > 2. New features are limited and ideally merged by K2.
>>> >
>>> > 3. K3 is dedicated to stability and bug fixing. (Much of this work
>>> > will happen before K3, but K3 is dedicated to testing and reviewing of
>>> > it, in preference to anything else. Any driver enhancements required
>>> > to support pre-existing features will also be considered, but please
>>> > get them in as early as possible).
>>> >
>>> > 4. PoC required before the summit, for any summit session related to
>>> > new features.
>>> >
>>> > 5. There will be a continuing drive for 3rd party CI of every driver
>>> > in cinder during the Kilo cycle.
>>> >
>>> >
>>> > I'll repost these guidelines and any follow-up clarifications shortly
>>> > before the summit. Comments / feedback welcome.
>>> >
>>> > [1]
>>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-09-03-16.01.log.html
>>> >
>>> > [2] https://etherpad.openstack.org/p/cinder-meetup-summer-2014
>>> >
>>> > [3] https://etherpad.openstack.org/p/cinder-kilo-stabilisation-work
>>>
>>>
>>> Just reiterating points here. From the September 23rd Cinder meeting
>>> [1], and
>>> verified in the Oct 29th Cinder meeting [2], the community has agreed
>>> that new
>>> drivers must be submitted *before* K-1 ends.
>>>
>>> K-1 is expected to end on 12/18, according to the launchpad page [3].
>>>
>>> Submitted and qualified for merge means:
>>> * Your blueprint for your driver was submitted and approved before 11/15.
>>> * Your driver code is posted to gerrit.
>>> * Your driver passes the cert test and the results are posted. [4]
>>> * Your driver fulfills minimum features. [5]
>>> * You have spoken to Duncan (DuncanT- on #openstack-cinder) about your
>>> third
>>>   party ci. [6]
>>>
>>> To be clear:
>>> * Your driver submission must meet *all* the items before the end of k-1.
>>> * If your driver is submitted *LATE* in k-1, and meets *all* the items
>>> above,
>>>   but isn't merged, it will be still be considered for merge in k-2 or
>>> k-3.
>>>   However, expect low priority in reviews and not guaranteed for merge
>>> in Kilo.
>>> * If your driver is submitted after k-1, expect me to reference this
>>> email and
>>>   will request the driver to be submitted in the L release.
>>> * This does not include backup drivers.
>>>
>>> And yes,

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

[Eduard Matei]

Hi Mike,
I saw your comment on my review, but i need some more info regarding
"Your driver passes the cert test and the results are posted."
I assume you mean running cinder_driver_cert.sh - this is already passing -
but how do i get the results posted, and where?
I've been looking through some documentation and couldn't find a definitive
answer.

Thanks
Eduard


On Thu, Oct 30, 2014 at 9:03 AM, Mike Perez  wrote:

> On 19:41 Thu 04 Sep , Duncan Thomas wrote:
> > Hi
> >
> > during this week's cinder weekly meeting [1], we discussed plans for
> > Kilo, a discussion that started at the mid-cycle meetup [2]. The
> > outcome is that we (the cinder core team and extended community) want
> > to focus on stability and code clean-up in the Kilo release, and
> > paying off some of the technical debt we've built up over the past
> > couple of years [3]. In order to facilitate this, for the Kilo cycle:
> >
> > 1. New drivers must be submitted before K1 in order to be considered.
> > Any driver submitted after this date will be deferred until the L
> > cycle. We encourage submitters to get in early, even if you make K1
> > there is no guarantee of getting enough reviewer attention to get
> > merged.
> >
> > 2. New features are limited and ideally merged by K2.
> >
> > 3. K3 is dedicated to stability and bug fixing. (Much of this work
> > will happen before K3, but K3 is dedicated to testing and reviewing of
> > it, in preference to anything else. Any driver enhancements required
> > to support pre-existing features will also be considered, but please
> > get them in as early as possible).
> >
> > 4. PoC required before the summit, for any summit session related to
> > new features.
> >
> > 5. There will be a continuing drive for 3rd party CI of every driver
> > in cinder during the Kilo cycle.
> >
> >
> > I'll repost these guidelines and any follow-up clarifications shortly
> > before the summit. Comments / feedback welcome.
> >
> > [1]
> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-09-03-16.01.log.html
> >
> > [2] https://etherpad.openstack.org/p/cinder-meetup-summer-2014
> >
> > [3] https://etherpad.openstack.org/p/cinder-kilo-stabilisation-work
>
>
> Just reiterating points here. From the September 23rd Cinder meeting [1],
> and
> verified in the Oct 29th Cinder meeting [2], the community has agreed that
> new
> drivers must be submitted *before* K-1 ends.
>
> K-1 is expected to end on 12/18, according to the launchpad page [3].
>
> Submitted and qualified for merge means:
> * Your blueprint for your driver was submitted and approved before 11/15.
> * Your driver code is posted to gerrit.
> * Your driver passes the cert test and the results are posted. [4]
> * Your driver fulfills minimum features. [5]
> * You have spoken to Duncan (DuncanT- on #openstack-cinder) about your
> third
>   party ci. [6]
>
> To be clear:
> * Your driver submission must meet *all* the items before the end of k-1.
> * If your driver is submitted *LATE* in k-1, and meets *all* the items
> above,
>   but isn't merged, it will be still be considered for merge in k-2 or k-3.
>   However, expect low priority in reviews and not guaranteed for merge in
> Kilo.
> * If your driver is submitted after k-1, expect me to reference this email
> and
>   will request the driver to be submitted in the L release.
> * This does not include backup drivers.
>
> And yes, the Cinder wiki will be updated with this information.
>
> [1] -
> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-09-03-16.01.log.html
> [2] -
> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-29-16.00.log.html
> [3] - https://launchpad.net/cinder/+milestone/kilo-1
> [4] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
> [5] -
> http://docs.openstack.org/developer/cinder/devref/drivers.html#minimum-features
> [6] -
> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testing_requirements_for_Kilo_release_and_beyond
>
> --
> Mike Perez
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distri

Re: [openstack-dev] Writing a cinder volume driver

[Eduard Matei]

Hi Darshan,
Having just finished writing a volume driver i can say you need a lot of
patience.
First, to quickly answer your questions:
1. Read ALL the drivers in the official repo: (
https://github.com/openstack/cinder/tree/master/cinder/volume/drivers) and
how they relate to the cinder-api (
https://github.com/openstack/cinder/tree/master/cinder/api); then look into
(https://wiki.openstack.org/wiki/Cinder), especially the part about plugins
and "configuring devstack to user your driver and backend);
2. As far as i could tell, python is the only way.
3. You should try devstack (it's easier to setup, quicker, and always gives
you latest code so you can develop against the latest version).

After that, the rest is just "bureaucracy" :) (become a contributor, sign
up for some services, get your code reviewed on gerrit, etc).

Hope this helps,

Eduard

On Thu, Oct 30, 2014 at 1:37 PM, Darshan Ghumare 
wrote:

> Hi All,
>
> I need to write a volume driver so that I can integrate our storage
> product into openstack.
> I have following questions about the sane,
> 1. How should I go about it?
> 2. I donnot know python. Is the python only way to write a driver?
> 3. I have setup openstack by following  steps mentioned at
> http://docs.openstack.org/icehouse/install-guide/install/apt/content/. To
> test the drive do I also need to have a development environment (
> http://docs.openstack.org/developer/cinder/devref/development.environment.html
> )?
>
> Thanks,
> Darshan
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova]Instance console.log

[Eduard Matei]

Hi,

Is there a way to disable "console.log" or redirect it to a custom location?
Use-case: we have a "custom" distributed storage-solution, and to enable
faster migration we symlinked the /opt/stack/dara/nova/instances to a
directory on our mountpoint (which is backed by our shared storage).
The problem is that "console.log" is placed here and during boot it's
writing more data than our storage solution can send to backend so
throttling occurs, which slows down the instance.

So, any ideas how to disable console.log or redirect it?
Thanks,
Eduard

-- 

*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
 | eduard.ma...@cloudfounders.com



*CloudFounders, The Private Cloud Software Company*

Disclaimer:
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev