It seems that nova and horizon are not communicating on my controller node.
Acces and security objects created with nova are not seen by Horizon and
vice versa. This includes key pairs and secgroup rules. For example, if I
create a keypair with the nova client, it isn't visible in horizon, and i
Add Cirros Image to Glance :)
Username: cirros
Password: cubswin:)
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/uploading-to-glance.html
to join your VM, it's a bit dirty but you can :
- put your computer in the same subnet as your controller (192.168.2.0/24)
- then adds
oh that's weird.
I still get this error. couldnt this be because I cannot ping the VM in the
first place?. Because as far as I know metadata takes care of ssh keys. But
what if you cant reach the VM in the first place?
no instance data found in start-local
ci-info: lo: 1 127.0.0.1 255.
For me, it's normal that you are not able to curl 169.254.169.254 from
your compute and controller nodes : Same thing on my side, but my VM get
their metadata.
Try to lunch an instance.
JB
On 02/17/2013 03:35 AM, Chathura M. Sarathchandra Magurawalage wrote:
> root@computernode:~# curl -v http
root@computernode:~# curl -v http://169.254.169.254
* About to connect() to 169.254.169.254 port 80 (#0)
* Trying 169.254.169.254...
root@controller:~# curl -v http://169.254.169.254
* About to connect() to 169.254.169.254 port 80 (#0)
* Trying 169.254.169.254...
root@athena:~# iptables -L
Controller node :
# iptables -L -n -v
# iptables -L -n -v -t nat
On 02/17/2013 03:18 AM, Chathura M. Sarathchandra Magurawalage wrote:
> You should be able to curl 169.254.169.254 from compute node, which I
> cant at the moment.
>
> I have got the bridge set up in the l3_agent.ini
__
On 02/14/2013 09:38 AM, Heiko Krämer wrote:
Heyho Guys,
i'm testing Swift and Keystone (Grizzly).
!NOTE!
I'm posting only the importent stuff (output, responses, configs)
I've upgraded and migrate the database, the migration are working not
correct (kyestone-manage db_sync) because in the role
Thanks Ransy,
I have created a tar file with the configuration and log files in it.
Please download it using the following URL. I have pasted the output of the
commands below.
https://www.dropbox.com/s/qyfcsn50060y304/confilesnlogs.tar
*Controller node:*
*root@controller:~# keystone endpoint-lis
Hi all,
When i installed Openstack by devstack, i was stucking in following
condition.
[...]
Downloading/unpacking prettytable (from -r
python_keystoneclient.egg-info/requires.txt (line 2))
It just got stuck here... and not moving forward.
Has anyone ever got the same problem? How did you solv
Please provide files listed bellow :
Controller Node :
/etc/nova/nova.conf
/etc/nova/api-paste.ini
/etc/quantum/l3_agent.ini
/etc/quantum/quantum.conf
/etc/quantum/dhcp_agent.ini
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
/etc/quantum/api-paste.ini
/var/log/nova/*.log
/var/log/quantum
Hello Jean,
Thanks for your reply.
I followed the instructions in
http://docs.openstack.org/folsom/basic-install/content/basic-install_network.html.
And my Controller and the Network-node is installed in the same physical
node.
I am using Folsom but without Network namespaces.
But in the websit
Hello Chathura,
Are you using Folsom with Network Namespaces ?
If yes, have a look here :
http://docs.openstack.org/folsom/openstack-network/admin/content/ch_limitations.html
Regards,
Jean-Baptsite RANSY
On 02/16/2013 05:01 PM, Chathura M. Sarathchandra Magurawalage wrote:
> Hello guys,
>
>
Hello guys,
The problem still exists. Any ideas?
Thanks
On 15 February 2013 14:37, Sylvain Bauza wrote:
> Metadata API allows to fetch SSH credentials when booting (pubkey I mean).
> If a VM is unable to reach metadata service, then it won't be able to get
> its public key, so you won't be abl
13 matches
Mail list logo
