Worked perfectly in the first attempt. Thanks a lot for the help. :)
On Tue, Jul 23, 2013 at 10:41 AM, Gareth wrote:
> the key reason it here:
> https://github.com/openstack/swift/blob/master/swift/common/utils.py#L1047
>
> you have many ways to stop flush IO; I prefer add a line "stdio_files =
Hi Team,
I am able to install Grizzly version ubuntu 12.04 however cannot create volume
it says Error in the status field. I am also unable to ssh instances however
the VNC and login comesup.
Any help would be highly appreciated.
Regards,
Raghavendra Lad
From: Openstack
[mailto:openstack-bou
Eric,
>
> On 22 Jul 2013, at 04:25, 姚牧阳 wrote:
>
> > (1) nova logs:
> > In a productive deployment, as I did before, I can freely read the
> logs from "/var/log/nova". However, it seems that in devstack, I can
> only use the SYSLOG configuration to gather the logs. However, the logs
> of 8 mach
On 23/07/13 03:24, Jake G. wrote:
> Hi All,
>
> Any chance there are other dashboards out there for Openstack besides
> Horizon?
I bet there are, since horizon is just a framework to implement a
dashboard, you're free to implement your own.
Matthias
___
Wish I was a programmer. Would be nice to be able to control and configure all
of openstacks functions from the dashboard.
From: Matthias Runge
To: openstack@lists.launchpad.net
Sent: Tuesday, July 23, 2013 4:45 PM
Subject: Re: [Openstack] Alternative dashb
No matter how I work this I cant seem to create a Centos 6.4 image correctly.
I can create a new instance using the qcow2 image I uploaded to Openstack, but
after booting the instance there is no NICs attached.
Should I be using a different formatting than qcow2?
I used this doc to create the i
On Tue, Jul 23, 2013 at 11:08 AM, Jake G. wrote:
> No matter how I work this I cant seem to create a Centos 6.4 image
> correctly.
>
> I can create a new instance using the qcow2 image I uploaded to Openstack,
> but after booting the instance there is no NICs attached.
> Should I be using a differ
On 23/07/13 09:57, Jake G. wrote:
> Wish I was a programmer. Would be nice to be able to control and
> configure all of openstacks functions from the dashboard.
>
Since the dashboard itself relies on Nova, Glance, and Keystone [1],
that won't be possible. Esp. endpoints to underlying services are
Pandora is another dashboard for openstack. See my blog
http://peter.kingofcoders.com
Thanksfrom Peter
> Date: Tue, 23 Jul 2013 10:21:24 +0200
> From: mru...@redhat.com
> To: dj_dark_jungl...@yahoo.com
> CC: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Alternative dashboards for open
Thanks Katz,
I think it would be nice to let the cloud administrator to see IaaS and PaaS
information in the same screen.He may need to make the decision to kill VMs, so
i think he need to see those information at the same time.
Thanksfrom Peter
From: oren.k...@alcatel-lucent.com
To: laserjety.
nova-manage network list results in no networks found.
I have 2 networks I created via quantum and are usable via the dashboard below.
+--+-+---+
| id | name
hi all:
I use RDO to install openstack , 2 node , one as contrllor node , another as
computer node
I create two VMs , One in contrllor node can get ip from dhcp agent, but vm in
computer node do not get IP from dhcp agent.
No errors can be found in log files.
ttjiang__
Hi all,
I am working with openstack and I want to pin vcpus to pcpus in guest xml. Now,
the pinning operation can be done using
virsh vcpupin guestname vcpu pcpu
But I want to do it using python API. I investigated the openstack code and
found out that get_guest_config function in libvirt/dr
On Tue, Jul 23, 2013 at 11:29 AM, Jake G. wrote:
> nova-manage network list results in no networks found.
>
> I have 2 networks I created via quantum and are usable via the dashboard
> below.
>
> +--+-+
I only have the quantum networks in openstack.
After I create a new instance there is no NIC attached to the instance.
Do I have to configure networking for nova also, so that nova-manage network
list actually displays networks?
From: Cristian Falcas
To: J
On Tue, Jul 23, 2013 at 12:51 PM, Jake G. wrote:
> I only have the quantum networks in openstack.
> After I create a new instance there is no NIC attached to the instance.
>
> Do I have to configure networking for nova also, so that nova-manage network
> list actually displays networks?
>
>
>
>
>
Here's my detailed description for my issue, please help.
Issue Description:
Quantum + OpenVswitch, and use devstack to do all-in-one installation. I
only add these lines into my localrc:
FIXED_RANGE=20.0.0.0/24
NETWORK_GATEWAY=20.0.0.1
FLOATING_RANGE=192.168.0.80/28
This is my trace record:
Ope
Hi,
I've seen something similar:
When you modify flavours (tested in the Dashboard) in Folsom, they where not
using uuid's (just counting upwards) and that >seemed< to mess things up when
you modified flavours.
We have re-created the flavours in Grizzly and the new flavours with UUID's
work fin
Hi all,
New issue here. I have two networks that I created through the OS dashboard,
Private and public.
These seem to be quantum networks because they are listed when using the cmd
quantum net-list
I deploy a new instance on the private network, then associate a floating ip. I
login to the con
StackOps Portal is a Rich Web User Interface solution that can run on
top of any OpenStack-based Cloud:
http://www.stackops.com/products-services/#portal
On Tue, Jul 23, 2013 at 10:25 AM, Peter Cheung wrote:
> Pandora is another dashboard for openstack. See my blog
> http://peter.kingofcoders.co
On Tue, Jul 23, 2013 at 05:31:25PM +0800, Peeyush Gupta wrote:
> Hi all,
>
> I am working with openstack and I want to pin vcpus to pcpus in
> guest xml. Now, the pinning operation can be done using
> virsh vcpupin guestname vcpu pcpu
> But I want to do it using python API. I investigated the open
HI Muhammad
If you’ve got full debug working well, I would love to replicate your
environment (and suspect I’m not the only one). If you have some time, it
would be great if you could detail setup instructions and config options on
this post.
Thx
Paul
From: Openstack
[mailto:openstack-bounc
Hi,
you don't have to create networks in nova too - the ones you created with
quantum should be enough.
First, it might perhpaps good to exclude possible issues with your image.
If you're using KVM you could go and check the libvirt XML which is
generated for your instance. If you see a populated
Hi,
We are running OpenStack Folsom on CentOS 6.4.
Quantum-linuxbridge-agent is used.
Its external network is configured to use VLAN 83 and
its address range is 10.12.83.0/24.
The IP of the Quantum node is 10.12.183.11/24.
The problem is that after reboot, the quantum node cannot
connect to
Hi,
We are running OpenStack Folsom on CentOS 6.4.
Quantum-linuxbridge-agent is used.
By default, the Quantum node has the following entries in its
/etc/sysconfig/iptables file.
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
Wi
Hi,
Please can you look up in the iptables?
Normally on a working openstack host the packets comming in the filter table in
the input chain are directed to the nova-network-INPUT which has a rule to
accept dhcp packets.
On my setup is something like:
-A INPUT -j nova-network-INPUT
.
.
.
-A nova
Thank you for your suggestion.
We are using Quantum/Neutron not nova-network.
So, we don't use br100.
(I believe you are using nova-network.)
And the firewall rules that cause problem reside on the Quantum node
not on the nova-compute node.
I cannot find any rule for "--dport 67" on my Quantu
that will not show the rules for the instance. try this
ip netns exec iptables -nxvL
On Jul 23, 2013, at 09:59 , David Kang wrote:
>
> Thank you for your suggestion.
>
> We are using Quantum/Neutron not nova-network.
> So, we don't use br100.
> (I believe you are using nova-network.)
>
> An
We use CentOS 6.4, which does not support network namespace.
So "ip netns .." fails.
Thanks,
David
- Original Message -
> that will not show the rules for the instance. try this
> ip netns exec iptables -nxvL
>
>
> On Jul 23, 2013, at 09:59 , David Kang wrote:
>
> >
> > Thank you
The user should be created automatically afaik (if it doesn't exist).
From: "Jake G." mailto:dj_dark_jungl...@yahoo.com>>
Reply-To: "Jake G."
mailto:dj_dark_jungl...@yahoo.com>>
Date: Monday, July 22, 2013 11:51 PM
To: "Jake G." mailto:dj_dark_jungl...@yahoo.com>>,
"openstack@lists.launchpad.net
Hi,
This is very interesting..:)
I am using openstack grizzly allinone with quantum/neutron.
Look what I am observing.
-before starting an instance on the server
root@ubuntu1204:~# iptables-save -t filter
# Generated by iptables-save v1.4.12 on Tue Jul 23 20:22:55 2013
*filter
:INPUT ACCEPT [629
What I have observed so far is...
1. nova-compute sends dhcp request
2. dhcp-server running on the Quantum node does not receive the request
because of the firewall setting.
I don't understand why quantum-dhcp-agent does not set up firewall properly.
(Yes, all the openstack components are r
I think I found the solution.
https://bugzilla.redhat.com/show_bug.cgi?id=889868
It was reported as a bug by RedHat.
It also suggests a work-around.
Thank you everyone.
David
- Original Message -
> What I have observed so far is...
>
> 1. nova-compute sends dhcp request
> 2. dhcp
On 07/23/2013 12:22 PM, David Kang wrote:
>
> Hi,
>
> We are running OpenStack Folsom on CentOS 6.4.
> Quantum-linuxbridge-agent is used.
> By default, the Quantum node has the following entries in its
> /etc/sysconfig/iptables file.
>
> -A INPUT -j REJECT --reject-with icmp-host-prohibited
On Tue, Jul 23, 2013 at 1:49 AM, Jake G. wrote:
> I am following the part on how to set up cloud-init from the below guide,
> but I was wondering how to change the user?
> I do not have the default ec2-user on my instance image. Do I just create
> this user in the instance? What permissions do I g
Thank you, Brian.
David
- Original Message -
> On 07/23/2013 12:22 PM, David Kang wrote:
> >
> > Hi,
> >
> > We are running OpenStack Folsom on CentOS 6.4.
> > Quantum-linuxbridge-agent is used.
> > By default, the Quantum node has the following entries in its
> > /etc/sysconfig/ipt
A Redhat manual suggests the following rule to enable forwarding packets
among VMs and external network.
https://access.redhat.com/site/documentation/en-US/Red_Hat_OpenStack/2/pdf/Release_Notes/Red_Hat_OpenStack-2-Release_Notes-en-US.pdf
iptables -t filter -I FORWARD -i qr-+ -o qg-+ -j ACCEPT
ip
37 matches
Mail list logo
