Our logs server seems to be down and thus tests cannot publish their job
results and fail with POST_FAILURE.
For now, there's no sense in rechecking a change, pushing it again, or
approving anything - everything will fail.
Please wait until you hear that everything is fine again.
This needs an i
Hi Sam,
nova-lxc is not recommended in production [1]. And LXD is built on top of LXC
AFAIK. But I will investigate nova-lxd in detail, thank you.
If nova-docker will be retired at the end of the day, we will need to choose a
similar service.
[1]
http://docs.openstack.org/newton/config-refe
Hi all
I was trying to setup a Devstack environment within an OpenStack VM(it's host
also neutron enabled), saying nested VM
My OpenStack VM is configure with IP (192.168.77.37 and floating IP
192.168.1.121) on eth0 , I can ping it from HOST namespace, or ping the
floating IP, it has internet
I'd be remiss if I didn't point out that the nova LXC driver is much better
supported than the nova-docker driver.
Michael
On Thu, Dec 29, 2016 at 8:01 PM, Esra Celik
wrote:
>
> Hi Sam,
>
> nova-lxc is not recommended in production [1]. And LXD is built on top of
> LXC AFAIK. But I will investi
hi all,
Thanks for joining the IRC team meeting!
According to the result of the vote, we need to change the project name
from Nimble to Mogan[1], and the renaming process can be found here[2].
[1] https://en.wikipedia.org/wiki/Mount_Mogan
[2] https://etherpad.openstack.org/p/nimble-renaming
On
On 12/29/2016 09:19 AM, Andreas Jaeger wrote:
> Our logs server seems to be down and thus tests cannot publish their job
> results and fail with POST_FAILURE.
>
> For now, there's no sense in rechecking a change, pushing it again, or
> approving anything - everything will fail.
> Please wait until
Hi folks, happy holidays from the placement team :)
I created a bug/feature request today for some new API functionality in
the placement REST API:
https://bugs.launchpad.net/nova/+bug/1653122
It's low-hanging fruit and should be a relatively straightforward way
for a newcomer to the placeme
Hi Esra,
Take a look at Virtuozzo, which is supported in Nova via libvirt virt_type=parallels. It provides both VMs and OS
Containers similar to lxc except our containers have beed in production for more than 10 years already. Though
http://docs.openstack.org/developer/nova/support-matrix.html
On 12/29/2016 8:25 AM, Maxim Nestratov wrote:
Hi Esra,
Take a look at Virtuozzo, which is supported in Nova via libvirt
virt_type=parallels. It provides both VMs and OS Containers similar to
lxc except our containers have beed in production for more than 10 years
already. Though
http://docs.open
Based on this logs. I can tell you that problem is with plugging VIP address.
You need to show us also n-cpu logs. There should be some info what happened
because we can see in logs in line 22 that client failed with error 500 on
attaching network adapter. Maybe you’re out of IP’s in this subnet
owned !
Rafael Folco
OpenStack Continuous Integration
IBM Linux Technology Center
> On Dec 29, 2016, at 11:55 AM, Jay Pipes wrote:
>
> Hi folks, happy holidays from the placement team :)
>
> I created a bug/feature request today for some new API functionality in the
> placement REST API:
>
Recently, centos 7.3 is release. libvirt is upgrade to 2.0 version.
But in kolla's gate. the nova_libvirt container failed now and then.
What i found is:
1. Simple start nova_libvirt container is OK.
2. When launching a new instance, libvirt is killed without any logs in
libvirtd.log file.
3. in
Found this nova bug[0] and another talk in openstack-dev[1].
The question is: why this happens now and then? sometimes the gate is OK.
and others not.
[0] https://bugs.launchpad.net/nova/+bug/1649527
[1]
http://lists.openstack.org/pipermail/openstack-dev/2016-December/109401.html
On Fri, Dec 30,
13 matches
Mail list logo
