This is fallout from a new upstream release of pip that went out earlier in
the week. It looks like no formal bug ever got filed, tho the same problem
discovered in devstack and trove's integration testing repository. Added
some comments comments to the bug.
On Thu, Dec 25, 2014 at 10:59 PM,
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.
@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 punit...@cloudbyte.com wrote:
hello,
i
Hi Srinivasa,
This section is related to cpu affinity in instance xml file.
vcpu placement='static' cpuset='1-12'4/vcpu
Regards,
Joe Chiang
At 2014-12-26 12:25:29, Srinivasa Rao Ragolu srag...@mvista.com wrote:
Hi All,
I have been working on CPU Pinning feature validation.
I could
On Fri, Dec 26, 2014 at 11:01 AM, Adam Gandelman ad...@ubuntu.com wrote:
This is fallout from a new upstream release of pip that went out earlier
in the week. It looks like no formal bug ever got filed, tho the same
problem discovered in devstack and trove's integration testing repository.
Hi Joejing,
Thanks for quick reply. Above xml is getting generated fine if I set
vcpu_pin_set=1-12 in /etc/nova/nova.conf.
But how to pin each vcpu with pcpu something like below
cputune
vcpupin vcpu=‘0’ cpuset=‘1-5,12-17’/
vcpupin vcpu=‘1’ cpuset=‘2-3,12-17’/
/cputune
One more
as I've said on https://bugs.launchpad.net/tripleo/+bug/1405732, suspecting
this comes from sudo pip is a good pointer - but as far as I can tell our
tripleo-ci scripts never run sudo pip.
This seems to be something that's happening before the testenv gets handed
to the tripleo-ci scripts. I've
Hello stackers and magnetians,
I suggest nominating Andrey Ostapenko [1] to MagnetoDB cores.
During last months he has made huge contribution to MagnetoDB [2]
Andrey drives Tempest and python-magnetodbclient successfully.
Please rise your hands.
Thank you,
Ilya Sviridov
[1]
Andrey is very active contributor, good team player and very helps us at
previous development cycle. +1 from my side.
On Fri, Dec 26, 2014 at 4:16 PM, isviridov isviri...@mirantis.com wrote:
Hello stackers and magnetians,
I suggest nominating Andrey Ostapenko [1] to MagnetoDB cores.
During
Hi, all!
Unexpectedly I met a pretty significant issue when I have been solving a
small bug
https://bugs.launchpad.net/ubuntu/+source/oslo.messaging/+bug/1367614. The
problem is in several parts:
* Topics used for several purposes: to set subscriptions and to determine a
type of sockets.
*
Actually with JJB in place we create jobs slower than without it.
Because we cannot just click through Jenkins web ui but have to
properly describe and test the job and make it pass the review
process. JJB helps to manage jobs but doesn't simplify job creation.
But let me point out that Jenkins
Hi all,
I agree with Alexandra about importance of the feature info on early
implementation stage,
And seems devops need to take part in review of specs too, clarify scenarios
here and other data, that they need.
Отправлено с iPhone
26 дек. 2014, в 19:36, Aleksandra Fedorova
What you’re saying is that whatever is under “$.env” is just the exact same
environment that we passed when we started the workflow? If yes then it
definitely makes sense to me (it just allows to explicitly access
environment, not through the implicit variable lookup). Please confirm.
Yes.
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Motohiro/Yuanying Otsuka (ootsuka)
Please let me know your votes by replying to this message.
Thanks,
Adrian
[1] https://review.openstack.org/#/admin/groups/473,members Current Members
+1
Cheers,
Ajaya
On Fri, Dec 26, 2014 at 8:22 PM, Dmitriy Ukhlov dukh...@mirantis.com
wrote:
Andrey is very active contributor, good team player and very helps us at
previous development cycle. +1 from my side.
On Fri, Dec 26, 2014 at 4:16 PM, isviridov isviri...@mirantis.com wrote:
Hello
- Original Message -
From: Srinivasa Rao Ragolu srag...@mvista.com
To: joejiang ifz...@126.com
Hi Joejing,
Thanks for quick reply. Above xml is getting generated fine if I set
vcpu_pin_set=1-12 in /etc/nova/nova.conf.
But how to pin each vcpu with pcpu something like below
On 12/26/2014 01:44 PM, Adrian Otto wrote:
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Motohiro/Yuanying Otsuka (ootsuka)
Please let me know your votes by replying to this message.
Thanks,
Adrian
[1] https://review.openstack.org/#/admin/groups/473,members
+1 welcome!
On Dec 26, 2014 3:48 PM, Adrian Otto adrian.o...@rackspace.com wrote:
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Motohiro/Yuanying Otsuka (ootsuka)
Please let me know your votes by replying to this message.
Thanks,
Adrian
[1]
On 12/26/2014 01:44 PM, Adrian Otto wrote:
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Motohiro/Yuanying Otsuka (ootsuka)
Please let me know your votes by replying to this message.
Thanks,
Adrian
[1] https://review.openstack.org/#/admin/groups/473,members
Solum cores,
I propose the following addition to the solum-core group[1]:
+ Ed Cranford (ed--cranford)
Please reply to this email to indicate your votes.
Thanks,
Adrian Otto
[1] https://review.openstack.org/#/admin/groups/229,members Current Members
+1
--
Best regards,
Illia Khudoshyn,
Software Engineer, Mirantis, Inc.
38, Lenina ave. x-apple-data-detectors://1 Kharkov, Ukraine
www.mirantis.com http://www.mirantis.ru/
www.mirantis.ru
Skype: gluke_work
ikhudos...@mirantis.com
26 дек. 2014 г., в 15:16, isviridov
21 matches
Mail list logo
