I proposed a solution (https://review.openstack.org/#/c/172522/)
But i have no idea how to push it.
btw. As i see, glanceclient developers decided to just remove these jobs (
https://review.openstack.org/#/c/172999/)
On Tue, Apr 14, 2015 at 11:47 AM, Andrey Kurilin
wrote:
> >Given that, is it
Robert Collins wrote:
> On 13 April 2015 at 22:04, Thierry Carrez wrote:
>> How does this proposal affect stable branches ? In order to keep the
>> breakage there under control, we now have stable branches for all the
>> OpenStack libraries and cap accordingly[1]. We planned to cap all other
>> li
Greetings,
Currently, there is a docker-swarm bay in magnum, but the problem is after
this swarm bay was created, how to let user use this bay? Still using swarm
CLI? The magnum do not have API/CLI to interact with swarm bay now.
--
Thanks,
Jay Lau (Guangya Liu)
Indeed image pull be time-consuming.
Is it much better to supply a magnum api let end-user can clean image that not
used?
Clean or not clean is decide by the end-user. Or we can supply a method let
end-user can decide whether or not clean image.
Date: Mon, 13 Apr 2015 14:51:05 +0800
F
+1
On Tue, Apr 14, 2015 at 10:41 AM, Yuriy Shamray
wrote:
> +1.
>
> On Mon, Apr 13, 2015 at 10:15 PM, Igor Kalnitsky
> wrote:
>
>> +1.
>>
>> On Mon, Apr 13, 2015 at 4:09 PM, Sergii Golovatiuk
>> wrote:
>> > Strong +1
>> >
>> > Nastya forgot to mention Andey's participation in "Ubuntu 14.04"
>>
3/ +1
On Tue, Apr 14, 2015 at 11:49 AM, Sergii Golovatiuk <
sgolovat...@mirantis.com> wrote:
> +1 for separating.
>
> Let's follow the formal well established process.
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> On Tue, Apr 14, 2015 at 10:32 AM, Igor Kalnitsky
On 18 March 2015 at 03:03, Doug Hellmann wrote:
> Now that we have good processes in place for the other Oslo libraries, I
> want to bring pbr into the fold so to speak and start putting it through
> the same reviews and release procedures. We also have some open bugs
> that I'd like to find someo
Hello,
We'll have the weekly EC2 API sub team meeting [1] at 1400UTC in
#openstack-meeting-3 today. We'll likely spend the majority of the
time going over current status along with critical bugs, as well as
covering BPs.
Please feel free to add other items in the agenda [2] section.
Thanks!
Swa
+1 for separating.
Let's follow the formal well established process.
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Tue, Apr 14, 2015 at 10:32 AM, Igor Kalnitsky
wrote:
> Dmitry,
>
> 1/ +1
>
> 2/ +1
>
> 3/ +1
>
> P.S: Dmitry, please send one mail per nomination next time. I
>Given that, is it okay if I propose a patch to remove the
'stable-compat-jobs-{name}' build jobs for python-novaclient in
project-config?
I suppose we should remove 'stable-compat-jobs-{name}', since novaclient is
already blocked for one week and it looks like there are no another
solutions for n
Ok, after one week, looks like the most popular time slot is B,
that is 14:00 UTC / Wednesdays.
I’m proposing first meeting for Wednesday / Apr 22th 14:00 UTC /
#openstack-meeting-2.
Tomorrow (Apr 15th / 14:00 UTC) It’s a been early since the announcement, so
I will join #openstack-meeting-2 wh
- Original Message -
> From: "Wangbibo"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Monday, April 13, 2015 10:51:39 AM
> Subject: [openstack-dev] 答复: [neutron] Neutron scaling datapoints?
>
>
>
> Hi Kevin,
>
>
>
> Totally agree with you that
Hi Gordon and Ceilometer folks,
I'm newbie in Ceilometer, but would like to get involved the contribution of
"alerting on events".
> in Liberty, we intend on support action/alerting on events so maybe it's
> something we should collaborate on to ensure
> the right functionality is provided.
C
Dear PTLs, cross-project liaisons and anyone else interested,
We'll have a cross-project meeting today at 21:00 UTC, with the
following agenda:
* Any Kilo release red flags ?
* openstack-specs discussion
* Return request ID to caller [1]
* OpenStack wide Error Codes for Log Messages [2]
* Des
Dmitry,
1/ +1
2/ +1
3/ +1
P.S: Dmitry, please send one mail per nomination next time. It's much
easier to vote for each candidate in separate threads. =)
Thanks,
Igor
On Mon, Apr 13, 2015 at 4:24 PM, Dmitry Pyzhov wrote:
> Hi,
>
> 1) I want to nominate Vladimir Sharshov to fuel-astute core.
There's also, where relevant, 'fix up the object code so that it does
something sensible before the migration is run'. The value of 'something
sensible' depends very heavily on your code.
On 13 April 2015 at 22:33, Ivan Kolodyazhny wrote:
> Hi Deepak,
>
> Your steps look good for e except #3.1 -
Hi all,
I'll attend the next L3 meeting this Thurdsay so we can revive the BGP
work for Liberty. Sorry for being absent for many weeks.
Thanks for your interest on it.
Regards,
On Mon, 13 Apr 2015 11:32, Carl Baldwin wrote:
> Hi, I'm getting back from a little time off over the weekend.
>
> Ar
Hello everyone,
It's Ironic turn to produce a release candidate. The RC1 tarball, as
well as a list of last-minute features and fixed bugs since kilo-3 are
available at:
https://launchpad.net/ironic/kilo/kilo-rc1
Unless release-critical issues are found that warrant a release
candidate respin, t
101 - 118 of 118 matches
Mail list logo
