Hi stackers,
Unfortunately what was discussed in other thread (situation in glance is
critical) happened.
Glance stopped working and Rally team is forced to disable checking of it
in Rally gates.
P.S. Seems like this patch is casing the problems:
https://github.com/openstack-dev/devstack/commit/
On 13/07/17 00:56 -0700, Boris Pavlovic wrote:
Hi stackers,
Unfortunately what was discussed in other thread (situation in glance is
critical) happened.
Glance stopped working and Rally team is forced to disable checking of it
in Rally gates.
P.S. Seems like this patch is casing the problems:
On 12 July 2017 at 22:23, Emilien Macchi wrote:
> Hey folks,
>
> Derek, it seems like you want to deploy Ironic on scenario006
> (https://review.openstack.org/#/c/474802). I was wondering how it
> would work with multinode jobs.
The idea was that we would create a libvirt domain on the overcloud
On 12 July 2017 at 22:33, Emilien Macchi wrote:
> On Wed, Jul 12, 2017 at 2:23 PM, Emilien Macchi wrote:
> [...]
>> Derek, it seems like you want to deploy Ironic on scenario006
>> (https://review.openstack.org/#/c/474802). I was wondering how it
>> would work with multinode jobs.
>
> Derek, I al
Hi Flavio,
2017-07-13 11:16 GMT+03:00 Flavio Percoco :
> On 13/07/17 00:56 -0700, Boris Pavlovic wrote:
>
>> Hi stackers,
>>
>>
>> Unfortunately what was discussed in other thread (situation in glance is
>> critical) happened.
>> Glance stopped working and Rally team is forced to disable checking
Someone has reported this issue in glance recently.
Please refer, https://bugs.launchpad.net/glance/+bug/1703856
I think it is same kind of failure which Andrey was mentioning.
As mentioned in the bug temporary solution is to enable the v1 api using the v1
parameter, --location instead of using
On Tue, Jul 11, 2017 at 11:40 PM, Ben Nemec wrote:
>
>
> On 07/11/2017 10:17 AM, Numan Siddique wrote:
>>
>> Hello Tripleo team,
>>
>> I have few questios regarding migration from neutron ML2OVS to OVN. Below
>> are some of the requirements
>>
>> - We want to migrate an existing depoyment from N
On Thu, 13 Jul 2017, Balazs Gibizer wrote:
/placement/allocation_candidates?resources=CUSTOM_MAGIC%3A512%2CMEMORY_MB%3A64%2CVCPU%3A1"
but placement returns an empty response. Then nova scheduler falls back to
legacy behavior [4] and places the instance without considering the custom
resource r
hi,
today i managed to play with l3 flavors.
i wrote a crude patch to implement midonet flavor. [1]
[1] https://review.openstack.org/#/c/483174/
a good news is it's somehow working.
a bad news is it has a lot of issues, as you can see in TODO comments
in the patch.
given these issues, now i ten
Just a reminder for all that we'll be having a security meeting today at
the usual time.
Meeting agenda: https://etherpad.openstack.org/p/security-agenda
Cheers
-Rob
__
OpenStack Development Mailing List (not for usage questi
Initial finding:
This is something related to uwsgi socket timeout. Default value for
socket-timeout is 30 in /etc/glance/glance-uwsgi.ini file.
For testing purpose I have tried to create 10 GB image using create command:
$ time glance --debug image-create --name dsl --file gentoo_root.img
--dis
On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins wrote:
> On 12 July 2017 at 22:33, Emilien Macchi wrote:
>> On Wed, Jul 12, 2017 at 2:23 PM, Emilien Macchi wrote:
>> [...]
>>> Derek, it seems like you want to deploy Ironic on scenario006
>>> (https://review.openstack.org/#/c/474802). I was wonder
os-vif has been integrated into nova since the newton cycle. With the
integration of os-vif, the expectation is that all the old, non-os-vif
plugging/unplugging code found in [1] will be replaced by code that harnesses
os-vif plugins [2]. This has happened for a few of the VIF types, and newer
VIFs
On Wed, Jul 12, 2017 at 1:21 AM, Monty Taylor wrote:
> On 07/11/2017 06:47 AM, Flavio Percoco wrote:
>>
>> On 11/07/17 14:20 +0300, Mikhail Fedosin wrote:
>>>
>>> On Tue, Jul 11, 2017 at 1:43 AM, Monty Taylor
>>> wrote:
>>>
On 07/10/2017 04:31 PM, Mikhail Fedosin wrote:
>
> Third, al
Hi everyone,
Earlier this year we discussed areas we could collectively come together as
a community and be better. One area identified was getting unanswered
requirements simply put, answered[1]. After some small and larger
conversations the goal of adopting the SIG model, as touted by other
Open
Some of the stuff like '802.1qbh' isn't particularly vendor specific so I'm
not sure who will host it and a repo just for that seems like a bit much.
Should we just bite the bullet and convert them in the nova tree or put
them in os-vif?
On Thu, Jul 13, 2017 at 7:26 AM, Stephen Finucane
wrote:
Hi Volodymyr,
I believe that this change[1] will fix your problem.
[1] https://review.openstack.org/#/c/482212/
Best Regards,
Ifat.
From: "Mytnyk, VolodymyrX"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, 11 July 2017 at 12:48
To: "OpenStack Developm
We [1] have started work on implementing support for
https://blueprints.launchpad.net/tripleo/+spec/container-healthchecks in
tripleo-common. I would like to describe the approach we're taking in the
short term, as well as explore some ideas for longer-term implementations.
## Our current approac
- Original Message -
> From: "joehuang"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, July 11, 2017 8:12:16 PM
> Subject: Re: [openstack-dev] TR: [tricircle]
>
> Hi Meher,
>
> Yes, as Victor pointed out, it should be done by the devstack script
Welcome to our regular release countdown email!
Development Focus
-
Teams should be wrapping up Pike feature work, prioritizing non-client
libraries first, then everything else (services, client libraries...)
General Information
---
Next week is the deadline for
On 07/13/2017 08:42 AM, Erno Kuvaja wrote:
On Wed, Jul 12, 2017 at 1:21 AM, Monty Taylor wrote:
On 07/11/2017 06:47 AM, Flavio Percoco wrote:
On 11/07/17 14:20 +0300, Mikhail Fedosin wrote:
On Tue, Jul 11, 2017 at 1:43 AM, Monty Taylor
wrote:
On 07/10/2017 04:31 PM, Mikhail Fedosin wrote
Hi!
With a few hours in advance (blame Bastille Day!) this is the weekly
update on Technical Committee initiatives. You can find the full list of
all open topics at:
https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
== Recently-approved changes ==
* Add Queens goal: policy and docs i
As discussed in the nova meeting today [1] I have started an etherpad of
blueprint changes up for review [2] broken down into categories to help
focus reviews.
I did something similar in the Newton release and use this to help
myself organize my TODO list, sort of like a Kanban board. As thing
Greetings OpenStack community,
If you missed our meeting today, well, you didn't miss much. Not a lot of new
things going on. The bulk of the meeting was taken up with ideas for what we'd
like to accomplish at the upcoming Denver PTG. We thought that it might be
useful to have an informal "what
As discussed at today's Glance meeting, here are the priorities for
the coming week.
(1) The uwsgi problem that abhishekk is working on:
https://bugs.launchpad.net/glance/+bug/1703856
Keep an eye on #openstack-glance in case he needs help, and keep an
eye on the bug to see what patches need to be
Excerpts from Melvin Hillsman's message of 2017-07-13 08:51:16 -0500:
>1. Start the openstack-sigs mailing list
You can subscribe by visiting
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
Doug
__
Op
On 29/06/17 10:55, Monty Taylor wrote:
(Incidentally, I think it's unworkable to have an IaaS without DNS.
Other people have told me that having an IaaS without LBaaS or a message
queuing service is unworkable, while I neither need nor want either of
those things from my IaaS - they seem like P
Excerpts from Thierry Carrez's message of 2017-07-13 17:44:13 +0200:
> glance-store and instack haven't made a Pike release yet: if nothing is
> done by July 20, one release will be forced (on master HEAD) so that we
> have something to cut a stable branch from.
I have prepared a patch for a glan
On 07/12/2017 02:02 AM, Flavio Percoco wrote:
On 11/07/17 19:21 -0500, Monty Taylor wrote:
On 07/11/2017 06:47 AM, Flavio Percoco wrote:
On 11/07/17 14:20 +0300, Mikhail Fedosin wrote:
On Tue, Jul 11, 2017 at 1:43 AM, Monty Taylor
wrote:
On 07/10/2017 04:31 PM, Mikhail Fedosin wrote:
Third,
On Thu, Jul 13, 2017 at 4:43 PM, Monty Taylor wrote:
> On 07/13/2017 08:42 AM, Erno Kuvaja wrote:
>>
>> On Wed, Jul 12, 2017 at 1:21 AM, Monty Taylor
>> wrote:
>>>
>>> On 07/11/2017 06:47 AM, Flavio Percoco wrote:
On 11/07/17 14:20 +0300, Mikhail Fedosin wrote:
>
>
> On
On Thu, Jul 13, 2017 at 01:35:00PM -0400, Doug Hellmann wrote:
> Excerpts from Thierry Carrez's message of 2017-07-13 17:44:13 +0200:
>
> > glance-store and instack haven't made a Pike release yet: if nothing is
> > done by July 20, one release will be forced (on master HEAD) so that we
> > have s
We have recovered old tagged content from
https://docs.openstack.org/developer/$project and moved them to
https://docs.openstack.org/$project/$version. As part of this process,
we also kept any builds from the tip of the mitaka, newton, and ocata
branches using those names as $version. And finally,
On 2017-07-13 13:03:26 -0400 (-0400), Zane Bitter wrote:
[...]
> This is pretty much the same argument as I would make for DNSaaS.
> Without it you're developing your own orchestration and/or
> manually updating stuff every time you make a change in your
> infrastructure, which pretty much negates
Hi everyone,
Since we still have a few days to present presentation proposals for Summit, I
was wondering if anyone would like to join me on a diversity panel or BoF for
women (specifically WOC) in OpenStack?
<3 Trilliams
Sent from my iPhone
<3 Trilliams
Sent from my iPhone
_
Resending... I found out that Gmail messed up my message with its HTML format...
Hopefully this time it will be more readable on the online archive interface.
On Tue, Jul 11, 2017 at 10:28 PM, Mathieu Gagné wrote:
> Hi,
>
> So this email is relevant to my interests as an operator. =)
>
> On Tue,
Colleen found out today while doing a backport that both of our stable
branches are broken. After doing some digging, it looks like bug 1687593
is the culprit [0]. The fix to that bug merged in master and the author
added some nicely written functional tests using the
keystone-tempest-plugin. The f
Oh - the original issues with the stable branches were reported here:
https://bugs.launchpad.net/keystone/+bug/1704148
On 07/13/2017 06:00 PM, Lance Bragstad wrote:
> Colleen found out today while doing a backport that both of our stable
> branches are broken. After doing some digging, it looks
I agree with Zane for most of the parts. But one thing I don't really
understand is, why OpenStack community is still confusing at the IaaS,
PaaS and SaaS, does the classification really mater at nowadays? Do we
really need a label/tag for OpenStack to limit it as an IaaS, PaaS or
SaaS? I never see
Kevin,
In interests of 'keeping it simple', I'm going to try and prioritize the
use-cases and pick implementation strategies which target the higher
priority ones without needlessly excluding other (lower priority) ones.
Thanks,
-amrith
--
Amrith Kumar
P.S. Verizon is hiring OpenStack engine
Hello rpm-packaging team and folks,
I got trouble with packaging OpenStack project(karbor), which depends on two
packages: icalendar and abclient.
icalendar has pip package and RPM package, but RPM package can not be found
by RDO CI.
While abclient only has pip package but no RPM package.
Hello Jiong,
Thank you for packaging karbor.
On Fri, Jul 14, 2017 at 11:49 AM, Jiong Liu wrote:
> Hello rpm-packaging team and folks,
>
>
>
> I got trouble with packaging OpenStack project(karbor), which depends on two
> packages: icalendar and abclient.
>
> icalendar has pip package and RPM pac
41 matches
Mail list logo
