Hi
When I create a new firewall and add rules and policies the Firewall stays in
Pending Create state
http://docs.openstack.org/admin-guide-cloud/content/install_neutron-fwaas-agent.html
Once I create a router and attach an interface to it it moves to Active state.
But when I delete this interfa
tune_items = ['disk_read_bytes_sec', 'disk_read_iops_sec',
'disk_write_bytes_sec', 'disk_write_iops_sec',
'disk_total_bytes_sec', 'disk_total_iops_sec']
# Note(yaguang): Currently, the only tuning available is Block I/O
# throttling for qemu.
Compute node do not support QEMU hypervisor from Juno. So, you should not
deploy a compute node on VM.
Guo Jinwei
发件人: Nikesh Kumar Mahalka [mailto:nikeshmaha...@vedams.com]
发送时间: 2014年8月29日 2:22
收件人: openstack@lists.openstack.org
主题: [Openstack] Launch of a instance failed
Hi
I dont see eth0 ip addr disapper . And what's the ip addr of your first VM
? You are using Nova-network , not Neutron, right ?
And why are you using different route to the same network ?
watrous@watrous-helion:~$ ip route
default via 16.85.144.1 dev eth1
10.11.12.0/24 dev br100 proto kernel sc
Hi,
I’ve been trying to get DevStack working to the point that I could use it
to explore CloudFoundry (
http://docs.cloudfoundry.org/deploying/openstack/validate_openstack.html).
I keep getting stuck with networking glitches. Sometimes it works, but most
of the time it doesn’t. Hopefully you can
Hi i am deploying a devstack juno on ubuntu 14.04 server virtual machine.
After installation,when i am trying to launch a instance,its failed.
I am getting "host not found" error.
Below is part of /opt/stack/logs/screen/screen-n-cond.log
Below is ther error
2014-08-28 23:44:59.448 ERROR nova.sche
Roberto,
It sounds like you disagree. Let's keep this constructive. Could you file
a bug and/or a change request for how you would like to see this part of
the book improved? Then we can focus on that specific change that you have
in mind, rather than expressing discontent at the motivation for
Are we improving the verbiage of log messages themselves or providing a set
of docs that explain the log errors and notifications?
On Aug 28, 2014 8:13 AM, "Theresa Huth" wrote:
> Hi Kurt,
>
> https://wiki.openstack.org/wiki/SystemUsageData is the best that I'm
> aware of.
>
> There's also http:/
Hello Stuart,
That does seem to do the trick. Thank you!
-Mike
On 08/28/2014 10:47 AM, stuart.mcla...@hp.com wrote:
Hi Mike,
Does it work if you put this at the very bottom of the file?
[.*]
create = @
read = @
update = @
delete = @
-Stuart
On Thu, 28 Aug 2014, Michael Turek wrote:
Hello
Hi Kurt,
https://wiki.openstack.org/wiki/SystemUsageData is the best that I'm aware of.
There's also http://docs.openstack.org/developer/glance/notifications.html for
Glance.
I'd love better docs around the types, content, and work flows of the
notifications.
-Theresa
-Original Message
Hi Mike,
Does it work if you put this at the very bottom of the file?
[.*]
create = @
read = @
update = @
delete = @
-Stuart
On Thu, 28 Aug 2014, Michael Turek wrote:
Hello,
I was wondering if the following behavior that I'm seeing with protected
properties is intended.
My setup is a ubu
Hello,
I was wondering if the following behavior that I'm seeing with protected
properties is intended.
My setup is a ubuntu guest running devstack.
with the following protections file:
[admin]
create = admin
read = admin
update = admin
delete = admin
[protected]
create = test
read = test
u
If anyone had similiar problem; CentOS 6 have retarded default settings
in /etc/sysctl.conf that disable iptables on bridges, change it to
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-arptables = 1
and it will work
On Mon, 25 Aug 2014
Hi folks,
I'm working on a program which receives all error/warn notifications from
openstack and translate them into human readable notifications. So I
desperately need a document describing all notifications. I've found one
document on wiki (https://wiki.openstack.org/wiki/SystemUsageData) but i
Hello,
Unfortunatelly now I have no possibility to check it on newer release (but I
will try). Those ports exists in neutron and IMHO it is correct because
instance is not deleted but only shutdown (or suspended) so IP is still
"reserver" for this vm - am I correct?
Second thing is that IMHO pr
Hi,
After sorting this out, I found out that my VMs weren't able to get
an IP via DHCP.
After a lot of troubleshooting, I fixed it by enabling IP forwarding
(net.ipv4.ip_forward=1) in the compute node (which is actually not
mentioned in the documentation:
http://docs.openstack.org/icehouse/insta
On 27 August 2014 01:28, David Hill wrote:
> Hi Kieran,
>
> Sorry I typed too fast! The patch I applied wasn't the good one
> (that's what happens when you have so many tabs in a browser).
> This fixed my problem (and many bugs) ! Perhaps this patch should be
> backported to Iceh
Hi,
it would be good if you can confirm whether this behaviour affects icehouse
or trunk as well.
Several bugs concerning nova/neutron communication as well as ovs agent
handling of ports have been fixed during the last two release cycle.
While the stable team did a great job in back-porting those
18 matches
Mail list logo
