Sean McGinnis wrote:
> On Thu, Dec 10, 2015 at 06:20:44PM +, Flavio Percoco wrote:
>>
>> With the new home for the release schedule, and it being a good place
>> for projects to add their own deadlines as well, I believe it would be
>> good for people that use calendars to have these .ics being
Tox 2.3.1 was released on pypi a few minutes ago, and it fixes this issue.
Jordan
On Mon, Dec 14, 2015 at 12:55 AM, Robert Collins
wrote:
> On 13 December 2015 at 03:20, Yuriy Taraday wrote:
> > Tempest jobs in all our projects seem to become broken after tox 2.3.0
> > release yesterday. It's
Marian Horban said on Thu, Dec 10, 2015 at 03:33:26PM +0200:
> Are there some progress with reloading configuration?
> Could we restore oslo-config review https://review.openstack.org/#/c/213062/
> ?
Hi Marian,
I'm also working on this, you might find
https://review.openstack.org/#/c/251471/ inte
Hi,
+1 from me to Bulat.
On Mon, Dec 14, 2015 at 1:03 PM, Igor Kalnitsky
wrote:
> Hi Fuelers,
>
> I'd like to nominate Bulat Gaifulin [1] for
>
> * fuel-web-core [2]
> * fuel-mirror-core [3]
>
> Bulat's doing a really good review with detailed feedback and he's a
> regular participant in IRC. H
Hi, Vladimir,
Please be informed that we'll have to also make an appropriate changes on
the fuel-agent side. But yes, it's possible to do it before SCF.
2015-12-11 20:05 GMT+03:00 Vladimir Kozhukalov :
> If there are no any objections, let's do fix fuel-menu ASAP. As Fedor said
> this approach w
Hi Fuelers,
I'd like to nominate Bulat Gaifulin [1] for
* fuel-web-core [2]
* fuel-mirror-core [3]
Bulat's doing a really good review with detailed feedback and he's a
regular participant in IRC. He's co-author of packetary and
fuel-mirror projects, and he made valuable contribution to fuel-web
On 11/12, mtanino wrote:
> Hi Thang, Vincent,
>
> I guess the root cause is that finish_volume_migration() still
> handles a volume as a dictionary instead of volume object and
> the method returns dict volume.
>
> And then, 'rpcapi.delete_volume()' in migrate_volume_completion()
> tries to delet
Vladimir,
Thanks for raising this question. I totally support idea of separating
provisioning and deployment steps. I believe it'll simplify a lot of
things.
However I have some comments regarding this topic, see them inline. :)
> For a package it is absolutely normal to throw a user dialog.
It
+1 It's really good job folks.
On Sat, Dec 12, 2015 at 2:25 AM, Vladimir Kuklin
wrote:
> Fuelers
>
> I am thrilled to announce that task based deployment engine [0] has been
> just merged into Fuel master. We checked it against existing BVT test cases
> for regressions as well as against functio
On Thu, Dec 10, 2015 at 4:46 PM, Galo Navarro wrote:
>
>
> On 10 December 2015 at 04:35, Sandro Mathys wrote:
>>
>> On Thu, Dec 10, 2015 at 12:48 AM, Galo Navarro wrote:
>> > Hi,
>> >
>> >> I think the goal of this split is well explained by Sandro in the first
>> >> mails of the chain:
>> >>
>>
... and back to this thread after a few weeks :)
The conclusions I saw were:
* Audience for openstack-announce should be "users/non-dev"
* Service project releases announcements are good
* Client library release announcements good
* Security announcements are good
* Internal library (particularly
On 12/14/2015 10:01 AM, Steve Martinelli wrote:
While I was trying to submit patches for projects that had old
keystoneclient references (distil was one of the projects), I noticed
that there hasn't been much action on this project [0]. It's been a year
since a commit [1], no releases [2], and I
While I was trying to submit patches for projects that had old
keystoneclient references (distil was one of the projects), I noticed that
there hasn't been much action on this project [0]. It's been a year since a
commit [1], no releases [2], and I can't submit a patch since
the .gitreview file d
Hi,
I am wondering whether "domain" is a mapping to a real-world cloud tenant
(not the counterpart of "project" in v2 Identity API) because recently I
read a paper that describes "domain" as a fit for the abstract concept
"cloud tenant". Does this saying stay in line with community's purpose?
Hi All,
When I was looking at bugs related to race conditions of scheduler [1-3], it
feels like nova scheduler lacks sanity checks of schedule decisions according
to different situations. We cannot even make sure that some fixes successfully
mitigate race conditions to an acceptable scale. For
> -Original Message-
> From: McLellan, Steven
> Sent: Friday, December 11, 2015 6:37 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog
> name for Glance Artifact Repository API
>
> Hi Alex,
>
> -Original Message-
> From: Ian Cordasco [mailto:ian.corda...@rackspace.com]
> Sent: Friday, December 11, 2015 8:13 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog
> name for Glance Artifact
101 - 117 of 117 matches
Mail list logo
