Hello.
My name is Rucia for Samsung SDS.
I had in truouble in volume deleting.
I am developing for supporting big data storage such as hadoop in lvm.
it use as a full disk io for deleting of cinder lvm volume because of dd
the high disk I/O affects the other hadoop instance on same host.
If
70% means we reached the quorum. That's cool !
OK, let's wait until the end of the poll then...
Le 26 déc. 2013 06:00, "Sergey Lukjanov" a écrit :
> Hey Sylvain,
>
> That's why I've already added several more days (Dec 25 - Jan 4). Are you
> expecting that someone will not be available for this
Hi,
In Icehouse development, do we have some guidelines for nova api change? If
I want to make some changes for nova api, do I need to update both v2 and
v3 or just v3?
There are some patches related to this, hope can get some comments from you.
https://review.openstack.org/#/c/52733/
https://re
On Tue, Dec 24 2013, Jay Pipes wrote:
> I think you may have switched the above? Do you mean POST for sanity (short
> URLs) and GET for compatibility/standards?
I don't think so, but maybe my sentence wasn't clear, sorry.
I meant that in theory, the right verb to use would be GET as you
pointed
Hello All,
I have to attach new exrenal volumes(CloudByte's Elastistore volume) in
OpenStack, can you guys please tell me, where I have to make changes in
OpenStack???
Thanks & Regards,
Mardan
___
OpenStack-dev mailing list
OpenStack-dev@lists
Hi,
thanks for the pointers! That's a good (re-)start indeed. Actually,we've
been working for a while on different blueprints related to the idea to
centrally store the quota information in keystone. Apparently, the
interest in this was weak, and all related blue prints (store quota,
domain q
Hi all,
I requested to review code about no hpet option.
https://blueprints.launchpad.net/nova/+spec/add-no-hpet-option-into-guest-clock
I expected that the code is verified.
However, the code was failed for verifying tempest test.
https://review.openstack.org/#/c/63769/
Actually, this is bec
On 12/26/2013 04:24 AM, Julien Danjou wrote:
On Tue, Dec 24 2013, Jay Pipes wrote:
I think you may have switched the above? Do you mean POST for sanity (short
URLs) and GET for compatibility/standards?
I don't think so, but maybe my sentence wasn't clear, sorry.
I meant that in theory, the r
On Tue, Dec 24, 2013 at 4:49 AM, Sebastien Han
wrote:
> Hello everyone,
>
> I’ve been working on a new feature for Devstack that includes a native
> support for Ceph.
> The patch includes the following:
>
> * Ceph installation (using the ceph.com repo)
> * Glance integration
> * Cinder integratio
Hi Ulrich,
I already discussed with Tim during last Swiss meetup at CERN about how
Climate could maybe help you on your use cases. There are still many things
to discuss and a demo to run out so we could see if it match your needs.
Basically, Climate is a new Stackforge project planning to impleme
Hi all,
I'm surprised there is no common ssh library in oslo so I filed this
blueprint[0]. I would be happy to address any comments/suggestions.
[0] https://blueprints.launchpad.net/oslo/+spec/common-ssh-client
--
Regards,
Sergey Skripnick
___
Op
Hi, in my experience, if it not caused by your code, recheck more times.
在 2013年12月26日，21:29，한승진 写道：
> Hi all,
>
> I requested to review code about no hpet option.
>
> https://blueprints.launchpad.net/nova/+spec/add-no-hpet-option-into-guest-clock
>
> I expected that the code is verified.
>
Unfortunately this approach leads to forcing in code that may increase
the bug in question, which will affect all developers.
I suggest you evaluate the Jenkins logs carefully, and link to the
timestamp in the logs were the failure occurred, in a comment on your
patch. This enables reviewers to ev
On Thu, Dec 26, 2013 at 10:50 AM, Anita Kuno wrote:
> Unfortunately this approach leads to forcing in code that may increase
> the bug in question, which will affect all developers.
>
> I suggest you evaluate the Jenkins logs carefully, and link to the
> timestamp in the logs were the failure occu
On 12/26/2013 02:09 PM, Clark Boylan wrote:
On Thu, Dec 26, 2013 at 10:50 AM, Anita Kuno wrote:
Unfortunately this approach leads to forcing in code that may increase
the bug in question, which will affect all developers.
I suggest you evaluate the Jenkins logs carefully, and link to the
times
The motivation for Ceph support in my case was for my company to work on
nova/glance RBD support and horizon integration with Ceph storage. The nova
support for RBD backing store is not currently mature, and subject to a
great deal of debate. Also boot from volume support used by Cinder/Ceph in
the
That quota staff has been following me from summit where we discussed that
with Tim. Also, Ulrich, Sylvain is right - speaking about one piece of cake
for one customer, our Climate (Reservation-as-a-Service) might help that.
That piece might be some amount of hosts with specific (customer specific)
Hi,
In Solum project we decided to write functional\integration tests from the
very beginning. Initially we used pecan testing framework, but after
discussion we moved to standard HTTP client approach used in other
projects. In order to simplify further integration with Tempest when Solum
will app
From: Vipul Sabhaya mailto:vip...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, December 24, 2013 3:42 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists
On 12/26/2013 03:34 PM, Georgy Okrokvertskhov wrote:
Hi,
In Solum project we decided to write functional\integration tests from
the very beginning.
++! :)
> Initially we used pecan testing framework, but after
discussion we moved to standard HTTP client approach used in other
projects. In or
Hello all,
When looking at a Solum patch in review [1], I wondered why Georgy
needed to move fixtures, testresources, and httplib2 into
requirements.txt [2] instead of test-requirements.txt, when those
aforementioned dependencies are not for Solum itself, but rather the
newly-introduced funct
On Thu, Dec 26, 2013 at 3:49 PM, Jay Pipes wrote:
> Hello all,
>
> When looking at a Solum patch in review [1], I wondered why Georgy needed to
> move fixtures, testresources, and httplib2 into requirements.txt [2] instead
> of test-requirements.txt, when those aforementioned dependencies are not
I put together all the patches which we prepared for making parallel
testing work, and ran a few times 'check experimental' on the gate to see
whether it worked or not.
With parallel testing, the only really troubling issue are the scenario
tests which require to access a VM from a floating IP, an
On 12/26/2013 07:06 PM, Clark Boylan wrote:
On Thu, Dec 26, 2013 at 3:49 PM, Jay Pipes wrote:
Hello all,
When looking at a Solum patch in review [1], I wondered why Georgy needed to
move fixtures, testresources, and httplib2 into requirements.txt [2] instead
of test-requirements.txt, when thos
On Fri, Dec 27, 2013 at 7:30 AM, Jay Pipes wrote:
> On 12/26/2013 07:06 PM, Clark Boylan wrote:
>>
>> On Thu, Dec 26, 2013 at 3:49 PM, Jay Pipes wrote:
>>>
>>> Hello all,
>>>
>>> When looking at a Solum patch in review [1], I wondered why Georgy needed
>>> to
>>> move fixtures, testresources, and
Hi,
We are developing a neutron plugin that works with our network controller.
Do we need to have 2 sets of tests for the plugin
i) tests that can be run against the network controller in our third party
test setup (to vote on changes to the plugin)
ii) tests that can be run in the OpenStack test
This might be completely off, in "isolated creds", a private network is created
for each tenant, while the test already creates its own private tenant network,
thereby changing the behavior from how it was intended to, and how it is in
"simple" mode. Could this be related?
I have this patch addr
Anita,
Did you get my email with my confirmation?
Thanks,
Edgar
On Thu, Dec 19, 2013 at 4:02 PM, Edgar Magana wrote:
> Anita,
>
> Fawad and Myself will be also attending.
>
> BTW. Fawad will require an invitation letter for visa. He will email you
> directly with that request.
>
> Thanks,
>
Mark,
We do not disagree with you. The main reason was indeed to onboard new
developers in Neutron. I will help Fawad on his introduction before and
after the sprint, therefore you should start seeing some code reviews and
code commitments from him ASAP.
Thanks,
Edgar
On Fri, Dec 20, 2013 at 1
Hi all,
We’ve created another etherpad https://etherpad.openstack.org/p/mistral-poc
where we proposed additional Mistral features that are going to be reflected in
DSL. One of the most important things is Data Flow, it’s main idea, how it
matches to the initial workflow model and how it affects
At Fri, 27 Dec 2013 01:53:59 +0100,
Salvatore Orlando wrote:
>
> [1 ]
> [1.1 ]
> I put together all the patches which we prepared for making parallel
> testing work, and ran a few times 'check experimental' on the gate to see
> whether it worked or not.
>
> With parallel testing, the only reall
Hi, stackers,
In review patch: https://review.openstack.org/64099, I found that if we use
kwargs detail instead of explanation when we raise that WSGIHTTPException,
the http response body will generate 'message' using default explanation,
instead of what we expected which is detail=msg.
So I regi
Hi,
This is an additional email to continue discussion about new Mistral DSL
capabilities. This time about conditional transitions and task dependencies.
Here’s the link to the corresponding etherpad:
https://etherpad.openstack.org/p/mistral-poc.
For convenience, I’m providing the snippet abou
On Thu, Dec 26, 2013 at 1:03 AM, Jay Lau wrote:
> Hi,
>
> In Icehouse development, do we have some guidelines for nova api change?
> If I want to make some changes for nova api, do I need to update both v2
> and v3 or just v3?
>
For every new extension to the v2 API we require the equivalent cha
34 matches
Mail list logo
