Hi,
I am trying to run Openstack on ARM64 architecture. ARM64 architecture
with KVM hypervisor needs GIC version(generic interrupt controller)
as a property for the image when we are creating/uploading an image. I
would like to include this property in the glance code. I am new to
glance, Can som
On 12/30/2015 11:27 PM, Clark Boylan wrote:
The problem with using a tox target is that we use privileged Jenkins
machines to do the extraction and don't want arbitrary code to run on
them. It would be possible to run arbitrary code if we used a tox
target.
Clark, we run already "run_messages.s
Hi Emillien,
> I think we would love having this module part of OpenStack, if it's ok
> for you.
>
> The process to move it is documented [1] but I can take care of it if
> you prefer, just let me know.
>
> Thanks for your collaboration, we're looking forward to have
> puppet-rally part of our fo
The problem with using a tox target is that we use privileged Jenkins
machines to do the extraction and don't want arbitrary code to run on
them. It would be possible to run arbitrary code if we used a tox
target.
Clark
On Wed, Dec 30, 2015, at 10:07 AM, Akihiro Motoki wrote:
> I haven't looked i
Hi Mikhail,
Unfortunately I completely agree that using Glance with the XenServer plugin is
painful. As Keven pointed out, the current release of XenServer includes
python 2.4 in dom0 (where the plugin runs) so having a dependency on nova.image
or glanceclient is likely to introduce more pain
All,
Please reply or send me an email if you are using the ConfKeyManager
(fixed-key key manager) in deployment for volume encryption or
ephemeral storage encryption. You can check this by looking at the
[keymgr] section, api_class entry of nova.conf or cinder.conf. The
ConfKeyManager was only int
We are thrilled to announce the release of:
os-client-config 1.13.1: OpenStack Client Configuation Library
This release is part of the mitaka release series.
With package available at:
https://pypi.python.org/pypi/os-client-config
For more details, please see below.
Changes in os-client
Excerpts from George Shuklin's message of 2015-12-29 09:16:52 -0800:
> Hello.
>
> I'm trying add a small feature to one of the elements in
> diskimage-builder (https://github.com/openstack/diskimage-builder/pull/10/)
>
> I have experience with gerrit and openstack bugfix workflow, but I have
>
I haven't looked into the code detail, but as far as I read
https://docs.djangoproject.com/en/1.9/topics/i18n/translation/#specialties-of-django-translation
it is enforced by django framework.
How django searches message catalogs is described at
https://docs.djangoproject.com/en/1.9/topics/i18n/tr
On Wed, Dec 30, 2015 at 8:37 AM, Sofer Athlan-Guyot
wrote:
> Hi,
>
> I have added neutron people as they may help to find a solution.
>
> After banging my head against the wall for a whole afternoon I
> discovered a serious bug in puppet neutron module.
>
> I not going to repeat here the detail o
Hi,
I have added neutron people as they may help to find a solution.
After banging my head against the wall for a whole afternoon I
discovered a serious bug in puppet neutron module.
I not going to repeat here the detail of the bug report[1]. Basically:
- neutron_port
- neutron_subnet
- neut
I'm currently looking into simplifying and consolidation of translation
setup for projects (draft spec at [1]) and have a question for dashboard
translations. Right now, horizon uses django.pot and djangojs.pot - and
most *-dashboard projects use the same names. Are these names enforced
by the
Cinder already emits events on all volume actions, and there are a few
projects that do various things with this info (e.g. stacktach). What do
you think the advantages of doing this inside cinder would be?
On 30 December 2015 at 16:54, SCHVENINGER, DOUGLAS P wrote:
> I was looking into a suppor
I was looking into a support issue and noticed that Nova has an instance and
instance_action table. I was wondering if this is something that cinder would
consider adding a volume_action table to track changes to a volume?
I looked in the specs and I could not see anything like this.
Has this b
Alexander,
Thanks for the response.
As for tasks hanging bug, I removed "deadlock" from its title: there is
another exception, which I didn't find due to huge number of traces from
deadlock detector.
As for random test failures bugs, I totally agree we should focus on them.
Just look at this: ht
On 2015-12-30 02:34:32 + (+), wuwenbin wrote:
> Repo of fuel-plugin-onos has something wrong because of uploading
> big file. Though codes are reverted while history still contains
> the pack which results in big downloading and unsync with github.
[...]
The OpenStack Project does not offi
On 12/30/2015 11:07 AM, Canonical Calendar wrote:
The Mitaka 1 update is still in progress - it ran into the start of the
holiday period so right now will be a mix of releases.
I'd expect that to be sorted out by the end of next week when the
packaging team get back post new year
For reference
Hi, guys.
Igor is absolutelly right - there are no deadlocks. We have only warnings
from detector, but they caused by difference between actual locking order
in the code and allowed by detector. It is annoying, but detection is used
only in development environment, thus it is not high bug.
When D
On 2015-12-30 11:11:50 +0300 (+0300), Evgeniy L wrote:
> You should probably talk to infra team on this issue #openstack-infra
> channel.
> I see several ways what can be done here:
> 1. recreate the repo
> 2. create a repo with different name
>
> Also there is possibility to remove from the commi
Hey Vitaly,
Are you the problem is in deadlock? I see the deadlock detecter
traceback, but not an actual deadlock.
I'm not sure could it be a reason for failure or not, it's better to
ask Alexander Kislitsky.
Thanks,
Igor
On Wed, Dec 30, 2015 at 2:57 PM, Vitaly Kramskikh
wrote:
> Hi,
>
> We ha
Hi,
We have a long-living issue with deadlocks in nailgun which used to almost
harmless and caused rare test failures. But test failures become more
frequent and today there is ~20% probability that they will fail on a
working code, which is really annoying. Moreover, a few weeks ago it
started to
Dear colleagues,
The spec for this feature is ready for review [0], so I'd like to encourage
all the parties concerned in Fuel modularization to participate.
Thanks
[0] https://review.openstack.org/#/c/254270/
On Fri, Dec 11, 2015 at 9:45 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wro
> On 30 Dec 2015, at 07:25, Michal Rostecki wrote:
>
>> On 12/30/2015 03:17 AM, Lei Zhang wrote:
>> Why the package is still the nova 12.0.0 rather than 13.0.0 ? [0]
>> Most the package is updated at Nov 9, 2015. But it is almost 2016 now.
>>
>> [0]
>> http://ppa.launchpad.net/ubuntu-cloud-arc
Hi,
You should probably talk to infra team on this issue #openstack-infra
channel.
I see several ways what can be done here:
1. recreate the repo
2. create a repo with different name
Also there is possibility to remove from the commit those files and push
using --force,
but it's a very bad practi
24 matches
Mail list logo
