-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I ran into similar behavior once, and it turned out I was running out
of space on the system. This blog post helped me track down the
problem:
http://porkrind.org/missives/libvirt-based-qemu-vm-pausing-by-itself/
Not sure whether it's relevant to
These VMs that are running devstack are 50GB disk, so there is plenty of disk
space. I don’t have cinder set up with this devstack setup.
I looked in the log for the instance and in the failing case the same message
was displayed (with different MAC and uuid), and then on the next line, I see
On 02/01/15 06:15, A mailing list for the OpenStack Stable Branch test
reports. wrote:
Build failed.
- periodic-horizon-docs-icehouse
http://logs.openstack.org/periodic-stableperiodic-horizon-docs-icehouse/b0d18a6/
: SUCCESS in 4m 35s
- periodic-horizon-python26-icehouse
Hello Kolla folks (et al),
I've refactored the heat-kubernetes templates at
https://github.com/larsks/heat-kubernetes to work with Centos Atomic
Host and Fedora 21 Atomic, and to replace the homegrown overlay
network solution with Flannel.
These changes are available on the master branch.
The
On Jan 2, 2015, at 4:53 AM, Paul Michali (pcm) p...@cisco.com wrote:
I don’t see what the difference is between a working and non-working setup. :(
One other time I’ve seen this happen is if the compute node is low (or out) of
disk space. If there’s connectivity problems with a cinder device,
Hi Stackers,
I observe that this commit is present in master branch.
commit 6ec66bb3d1354062ec70be972dba990e886084d5
Install prettytable=0.7 to satisfy pip 6/PEP 440
...
However, I am facing the issues due to PEP 440 in devstack's
stable/icehouse branch. Is devstack icehouse still
On 16:42 Thu 01 Jan , Timur Nurlygayanov wrote:
Hi all,
I have the strange error with Cinder: I have several volumes (with 30-100
Gb size) and I want to create Glance images based on these volumes, but
when I execute
snip
How I can debug this issue? (I have no any errors/exceptions in
Ah, doesn't seem to be a Neutron issue then since the
'network-vif-plugged' event is showing up and it's attempting to
resume.
The red flag looks like that Instance is paused unexpectedly.
Ignore.. If you grep the nova code base for that, it brings up a note
linking to bug 1097806.[1] The VM is
No other tools. Running a stock Ubuntu 14.04 server, installed devstack,
created local.conf, stacked, and tried to create a VM. I’ve since seen this on
another VM I have running with Kilo code, so it is not specifically a Juno
issue.
I don’t see what the difference is between a working and
To summarize what I’m trying to do with option (A)…
I want to test VPN in DevStack by setting up two private networks, two routers,
and a shared public network. The VMs created in the private networks should be
able to access the public network, but not the other private network (e.g. VM
on
I checked and the disk has plenty of space:
Filesystem Size Used Avail Use% Mounted on
/dev/vda150G 6.2G 41G 14% /
none4.0K 0 4.0K 0% /sys/fs/cgroup
udev3.9G 12K 3.9G 1% /dev
tmpfs 799M 408K 799M 1% /run
none5.0M
On 24/12/14 05:17, Steven Hardy wrote:
On Mon, Dec 22, 2014 at 03:42:37PM -0500, Zane Bitter wrote:
On 22/12/14 13:21, Steven Hardy wrote:
Hi all,
So, lately I've been having various discussions around $subject, and I know
it's something several folks in our community are interested in, so I
On 01/02/2015 08:39 AM, Lars Kellogg-Stedman wrote:
Hello Kolla folks (et al),
I've refactored the heat-kubernetes templates at
https://github.com/larsks/heat-kubernetes to work with Centos Atomic
Host and Fedora 21 Atomic, and to replace the homegrown overlay
network solution with Flannel.
Hi Marco
I think the current design is wrong because it is mixing up access
control with service endpoint location. The endpoint of a service should
be independent of the access control rules determining who can contact
the service. Any entity should be able to contact a service endpoint
(subject
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Jay Lau (jay-lau-513)
Please let me know your votes by replying to this message.
Thanks,
Adrian
[1] https://review.openstack.org/#/admin/groups/473,members Current Members
Hi all,
HAPPY NEW YEAR.
Starting Monday (Jan 5th, 2015) we will be kicking of bi-weekly meetings
for L2 Gateway discussions.
We are hoping to come up with an initial version of L2 Gateway API in Kilo
cycle. The intent of these bi-weekly meetings is to discuss issues related
to L2 Gateway API.
+1 from me. Welcome Jay!
On Jan 2, 2015 7:02 PM, Adrian Otto adrian.o...@rackspace.com wrote:
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Jay Lau (jay-lau-513)
Please let me know your votes by replying to this message.
Thanks,
Adrian
[1]
17 matches
Mail list logo
