from:"Guilherme Russi"

[Openstack] Problem with keystone on Debian

2012-12-06 Thread Guilherme Russi

Hello Guys,

 I'm trying to install OpenStack on Debian Wheezy, but i'm getting some
problems with keystone, when i try to create a user in a tenant using
the --tenant-id command, it returns the error: keystone: error:
unrecognized arguments: --service-id .

 Does anybody knows if it is a version problem, I've tried on ubuntu 12.10
and it worked.

Hope someone can help me.

Thank you.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Problem when running nova-manage db sync

2012-12-10 Thread Guilherme Russi

Hi All,

 I'm rying to install OpenStack Essex and when I run the nova-manage db
sync from this doc's part
http://docs.openstack.org/essex/openstack-compute/install/apt/content/compute-db-sync.html,
it
returs these errors:

2012-12-10 10:56:57 DEBUG nova.utils [-] backend  from
(pid=6208) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658

2012-12-10 10:56:58 WARNING nova.utils [-]
/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:683:
SADeprecationWarning: The 'listeners' argument to Pool (and
create_engine()) is deprecated.  Use event.listen().
  Pool.__init__(self, creator, **kw)

2012-12-10 10:56:58 WARNING nova.utils [-]
/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:159:
SADeprecationWarning: Pool.add_listener is deprecated.  Use event.listen()
  self.add_listener(l)

Can anybody help me?

Thank you so much.

Guilherme Russi.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Problem hen running VM instances

2012-12-10 Thread Guilherme Russi

Hi again guys,

 I'm sorry for all these questions, but when I learn how to install it I'll
help people with these same problems, well, I'm trying to run a VM instance
on Essex, a ubuntu image, but when I try to boot it the OS-EXT-STS:vm_state
is error.

What am I missing?

Thank you all again.

Guilherme Russi.


nova --os_tenant_name cloud image-list
+--+---+++
|  ID|Name
  | Status | Server |
+--+---+++
| 31d45bd5-5ba5-45b6-814e-54eef1699074 | tty-linux-ramdisk | ACTIVE |
 |
| b54cd532-20c2-4b48-a735-6d7fd6b083b8 |  tty-linux-kernel   | ACTIVE  |
|
| c16e7a7a-3c21-44db-8a38-5a49fa262ac9 |  tty-linux-kernel   | SAVING  |
   |
| d5220087-89ce-486f-a98e-3eb2c367d7ba | tty-linux  | ACTIVE  |
  |
+--+---+++


nova --os_tenant_name cloud boot --flavor 2 --image
b54cd532-20c2-4b48-a735-6d7fd6b083b8 --security_group default imagem
+-+--+
|   Property  |Value |
+-+--+
|  OS-DCF:diskConfig  |MANUAL
 |
| OS-EXT-SRV-ATTR:host| None
  |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
  |
|OS-EXT-SRV-ATTR:instance_name|  instance-0001
  |
|OS-EXT-STS:power_state   |  0
  |
|OS-EXT-STS:task_state|  scheduling
 |
| OS-EXT-STS:vm_state |error
  |
|  accessIPv4 |
 |
|  accessIPv6 |
 |
|  adminPass  | V4oFZcgLjrYn
  |
| config_drive|
 |
|   created   | 2012-12-10T15:56:44Z
  |
|flavor   |   m1.small
  |
|hostId   |
 |
|  id |
f43f77e7-1e36-4e19-b752-2e4c3ba7c076 |
|image|   tty-linux-kernel
  |
|   key_name  |
 |
|   metadata  |  {}
 |
| name|imagem
 |
|   progress  |  0
  |
|status   |BUILD
  |
|  tenant_id  |   d52768c939ee4a1b8dc82182a29df8d2
  |
|   updated   | 2012-12-10T15:56:44Z
  |
|   user_id   |   830ae8bc830440c28372066bdf20d9bc
  |
+-+--+


nova --os_tenant_name cloud list
+--+++--+
|  ID  |  Name  | Status | Networks |
+--+++--+
| f43f77e7-1e36-4e19-b752-2e4c3ba7c076 | imagem | ERROR  |  |
+--+++--+
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Problem in essex nova-manage service list

2012-12-12 Thread Guilherme Russi

Hi all,

 Can anybody help me with this, when I type nova-manage service list I
cannot see the nova-compute in the processes and the nova-network has this
XXX. What should I do?

Thank you all.

2012-12-12 10:36:53 DEBUG nova.utils
[req-6e9f672a-c484-40be-9796-a9b8b000358f None None] backend  from
(pid=5630) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658

Binary Host
Zone Status State Updated_At
nova-scheduler   mypcnova
enabled:-)   2012-12-12 12:36:51
nova-consoleauth mypcnova
enabled:-)   2012-12-12 12:36:50
nova-console mypcnova
enabled:-)   2012-12-12 12:36:51
nova-certmypcnova
enabled:-)   2012-12-12 12:36:50
nova-network mypcnova
enabledXXX   2012-12-12 12:25:59
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Help with Glance

2013-01-16 Thread Guilherme Russi

Hello Friends,

 I'm trying to import a image into glance using the command: glance
image-create --name="Ubuntu 12.04 UEC" --public --container-format= ovf
--disk-format=qcow2 < precise-server-cloudimg-amd64.img but it doesn't
work. My glance version is 2012.1.1, when I try to execute the command it
returns: glance: error: no such option: --name.

Can anybody help me?

Regards.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Problem with VNC on compute node

2013-01-23 Thread Guilherme Russi

Hello guys,

 I'm installing the folsom version and I have one computer like the
controller and one being the compute node. I can start the VM with cirros
OS but I can't use the VNC, I got the error: "Failed to connect to server
(code: 1006)". I've been following this tutorial:
http://docs.openstack.org/folsom/basic-install/content/basic-install_compute.html
.

Can anybody help me?

Thank you and regards.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Problem with IP on VMs

2013-01-30 Thread Guilherme Russi

Hello all,

 I'm using Folsom on Ubuntu server 12.04 and I'm getting problems with ping
and login ssh. Can anybody help me?

Regards.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem with IP on VMs

2013-01-30 Thread Guilherme Russi

No, how can I do that?

Thank you.


2013/1/30 Rain Li 

> Have you setup the secgroup rules?
>
>
> On Wed, Jan 30, 2013 at 2:02 PM, Ritesh Nanda wrote:
>
>> Can you give more details for your setup.
>>
>> On Thu, Jan 31, 2013 at 12:55 AM, Guilherme Russi <
>> luisguilherme...@gmail.com> wrote:
>>
>>> Hello all,
>>>
>>>  I'm using Folsom on Ubuntu server 12.04 and I'm getting problems with
>>> ping and login ssh. Can anybody help me?
>>>
>>> Regards.
>>>
>>> Guilherme.
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>>
>> * With Regards
>> *
>>
>> * Ritesh Nanda
>> *
>>
>> ***
>> *
>> <http://www.ericsson.com/>
>>
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem with IP on VMs

2013-02-01 Thread Guilherme Russi

Hello Lei,

 When I use the command nova secgroup-list-rules, it returns:

usage: nova secgroup-list-rules 
error: too few arguments

What must I insert with the command, the secgroup name? But I haven't
created an secgroup.

Regards.

Guilherme.


2013/1/31 Lei Zhang 

>  check list
>
>- login the vm through vnc, and check whether it get IP?
>- login in the vm from the host machine to check whether the IP is
>works
>- check the secgroup using command nova secgroup-list-rules
>
>
>
> On Thu, Jan 31, 2013 at 8:20 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> No, how can I do that?
>>
>> Thank you.
>>
>>
>>
>> 2013/1/30 Rain Li 
>>
>>> Have you setup the secgroup rules?
>>>
>>>
>>> On Wed, Jan 30, 2013 at 2:02 PM, Ritesh Nanda 
>>> wrote:
>>>
>>>> Can you give more details for your setup.
>>>>
>>>> On Thu, Jan 31, 2013 at 12:55 AM, Guilherme Russi <
>>>> luisguilherme...@gmail.com> wrote:
>>>>
>>>>> Hello all,
>>>>>
>>>>>  I'm using Folsom on Ubuntu server 12.04 and I'm getting problems with
>>>>> ping and login ssh. Can anybody help me?
>>>>>
>>>>> Regards.
>>>>>
>>>>> Guilherme.
>>>>>
>>>>> ___
>>>>> Mailing list: https://launchpad.net/~openstack
>>>>> Post to : openstack@lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> * With Regards
>>>> *
>>>>
>>>> * Ritesh Nanda
>>>> *
>>>>
>>>> ***
>>>> *
>>>> <http://www.ericsson.com/>
>>>>
>>>>
>>>>
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Lei Zhang
>
> Blog: http://jeffrey4l.github.com
> twitter/weibo: @jeffrey4l
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem with IP on VMs

2013-02-01 Thread Guilherme Russi

Hello Leandro,

 It's looking like that:

nova secgroup-list-rules default
+-+---+-+---+--+
| IP Protocol | From Port | To Port | IP Range  | Source Group |
+-+---+-+---+--+
| icmp   | -1| -1  | 0.0.0.0/0 |  |
| tcp | 22| 22  | 0.0.0.0/0 |  |
| tcp |80| 80  | 0.0.0.0/0 |  |
| tcp |  8080  | 8080| 0.0.0.0/0 |  |
+-+---+-+---+--+



2013/2/1 Leandro Reox 

> If you dont created any secgroup should be :
>
> nova secgroup-list-rules default
>
> Cheerios
>
>
>
> On Fri, Feb 1, 2013 at 8:35 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> Hello Lei,
>>
>>  When I use the command nova secgroup-list-rules, it returns:
>>
>> usage: nova secgroup-list-rules 
>> error: too few arguments
>>
>> What must I insert with the command, the secgroup name? But I haven't
>> created an secgroup.
>>
>> Regards.
>>
>> Guilherme.
>>
>>
>>
>> 2013/1/31 Lei Zhang 
>>
>>>  check list
>>>
>>>- login the vm through vnc, and check whether it get IP?
>>>- login in the vm from the host machine to check whether the IP is
>>>works
>>>- check the secgroup using command nova secgroup-list-rules
>>>
>>>
>>>
>>> On Thu, Jan 31, 2013 at 8:20 AM, Guilherme Russi <
>>> luisguilherme...@gmail.com> wrote:
>>>
>>>> No, how can I do that?
>>>>
>>>> Thank you.
>>>>
>>>>
>>>>
>>>> 2013/1/30 Rain Li 
>>>>
>>>>> Have you setup the secgroup rules?
>>>>>
>>>>>
>>>>> On Wed, Jan 30, 2013 at 2:02 PM, Ritesh Nanda >>>> > wrote:
>>>>>
>>>>>> Can you give more details for your setup.
>>>>>>
>>>>>> On Thu, Jan 31, 2013 at 12:55 AM, Guilherme Russi <
>>>>>> luisguilherme...@gmail.com> wrote:
>>>>>>
>>>>>>> Hello all,
>>>>>>>
>>>>>>>  I'm using Folsom on Ubuntu server 12.04 and I'm getting problems
>>>>>>> with ping and login ssh. Can anybody help me?
>>>>>>>
>>>>>>> Regards.
>>>>>>>
>>>>>>> Guilherme.
>>>>>>>
>>>>>>> ___
>>>>>>> Mailing list: https://launchpad.net/~openstack
>>>>>>> Post to : openstack@lists.launchpad.net
>>>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> * With Regards
>>>>>> *
>>>>>>
>>>>>> * Ritesh Nanda
>>>>>> *
>>>>>>
>>>>>> ***
>>>>>> *
>>>>>> <http://www.ericsson.com/>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Mailing list: https://launchpad.net/~openstack
>>>>>> Post to : openstack@lists.launchpad.net
>>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> Lei Zhang
>>>
>>> Blog: http://jeffrey4l.github.com
>>> twitter/weibo: @jeffrey4l
>>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi

Hello friends,

 I am getting problem when I try to start a VM, it keeps ate Scheduling
task and doesn't start the VM. It is happining after I made a apt-get
update and apt-get upgrade.
 I really don't know what to do, anybody can help me, please?

Thank you.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi

Hello Roni, thank you for returning,

 I don't understand the logs yet, I'm working with that, but here is a
piece of my nova-compute.log:

2013-02-05 10:11:07 11592 DEBUG nova.utils [-] Got semaphore
"compute_resources" for method "update_available_resource"... inner
/usr/lib/python2.7/dist-packages/nova/utils.py:721
2013-02-05 10:11:12 11592 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free ram (MB): 7136 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:470
2013-02-05 10:11:12 11592 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free disk (GB): 88 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:471
2013-02-05 10:11:12 11592 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free VCPUs: 4 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:476
2013-02-05 10:11:12 11592 AUDIT nova.compute.resource_tracker [-] Free ram
(MB): 7354
2013-02-05 10:11:12 11592 AUDIT nova.compute.resource_tracker [-] Free disk
(GB): 93
2013-02-05 10:11:12 11592 AUDIT nova.compute.resource_tracker [-] Free
VCPUS: 4
2013-02-05 10:11:12 11592 INFO nova.compute.resource_tracker [-]
Compute_service record updated for tiresias
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._poll_rebooting_instances periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Skipping
ComputeManager._cleanup_running_deleted_instances, 4 ticks left until next
run periodic_tasks /usr/lib/python2.7/dist-packages/nova/manager.py:167
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._check_instance_build_time periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._heal_instance_info_cache periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._run_image_cache_manager_pass periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._reclaim_queued_deletes periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.compute.manager [-]
FLAGS.reclaim_instance_interval <= 0, skipping... _reclaim_queued_deletes
/usr/lib/python2.7/dist-packages/nova/compute/manager.py:2790
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._report_driver_status periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 INFO nova.compute.manager [-] Updating host status
2013-02-05 10:11:12 11592 DEBUG nova.virt.libvirt.driver [-] Updating host
stats update_status
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py:3063
2013-02-05 10:11:18 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._poll_unconfirmed_resizes periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172

Regards.

Guilherme.


2013/2/5 Ronivon Costa 

> Have you looked the compute.log file? You should really start from there.
> :D
> Also, if you really expect some help, you must provide some information.
> Search in the logs for clues, and if it can't help or you don't understand
> what you see,  then send it along as well.
> Roni.
>  No dia 5 de Fev de 2013 11:59, "Guilherme Russi" <
> luisguilherme...@gmail.com> escreveu:
>
>>  Hello friends,
>>
>>  I am getting problem when I try to start a VM, it keeps ate Scheduling
>> task and doesn't start the VM. It is happining after I made a apt-get
>> update and apt-get upgrade.
>>  I really don't know what to do, anybody can help me, please?
>>
>> Thank you.
>>
>> Guilherme.
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi

I found a solution, I guess, well, I droped the tables from quantum and
create a network range again, and it worked again. Now I'm trying to figure
out how to insert a floating IP to ssh and ping in my VMs. Do you have any
ideas? I can login in the VM, but when I type sudo ifconfig -a it has no IP.

Thank you all.

Guilherme.


2013/2/5 Pranav 

> I believe that you have broken your configuration files. Please do make
> sure that your nova confi files are proper. I had similar issue where in i
> had to change the libvirt option to QEMU because some KVM issue and the
> images started spawning.
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi

Guys, I'm trying to create the network to connect my VMs, but they don't
receive the IP, my network configs in the controller node is:

# eth1 - link external with the internet
address 10.3.77.51

# eth0 - link internal to connect the compute nodes
address 192.168.3.1

And in my compute note I have:


# eth1 - link external with the internet
address 10.3.77.52

# eth0 - link internal to connect to the cloud
address 192.168.3.2

What am I doing wrong?

Regards.

Guilherme.


2013/2/5 Guilherme Russi 

> I found a solution, I guess, well, I droped the tables from quantum and
> create a network range again, and it worked again. Now I'm trying to figure
> out how to insert a floating IP to ssh and ping in my VMs. Do you have any
> ideas? I can login in the VM, but when I type sudo ifconfig -a it has no IP.
>
> Thank you all.
>
> Guilherme.
>
>
> 2013/2/5 Pranav 
>
>>  I believe that you have broken your configuration files. Please do make
>> sure that your nova confi files are proper. I had similar issue where in i
>> had to change the libvirt option to QEMU because some KVM issue and the
>> images started spawning.
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] VM doesn't attach IP

2013-02-07 Thread Guilherme Russi

Hello guys,

 My VMs are not attaching IP address, I've been look the VM's log but I
can't realize what is going on. I'm sending my VM's log. Can anybody help
me, please?

Regards.

Guilherme.


LogVM
Description: Binary data
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] VM doesn't attach IP

2013-02-07 Thread Guilherme Russi

Hi Anil,

 I'm trying to find something to fix it, are you using quantum or
nova-network? I'm working with quantum, I have one physical computer with 2
NICs that is the controller and another 4 physical computers with 2 NICs
each that are the node compute, I left the Network node with the Controller
node, at the same physical compute.

Regards.

Guilherme.


2013/2/7 Anil Vishnoi 

> Hi Guilherme,
>
> I reported the same issue just a moment ago here :
> https://answers.launchpad.net/quantum/+question/221283
>
> I think we are facing the same issue here- atleast VM logs shows.
>
> Anil
>
>
> On Thu, Feb 7, 2013 at 5:14 PM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> Hello guys,
>>
>>  My VMs are not attaching IP address, I've been look the VM's log but I
>> can't realize what is going on. I'm sending my VM's log. Can anybody help
>> me, please?
>>
>> Regards.
>>
>> Guilherme.
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Thanks & Regards
> --Anil Kumar Vishnoi
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] VM doesn't attach IP

2013-02-07 Thread Guilherme Russi

By the way, I'm look your post and I saw some things that I don't have at
the ifconfig, like this part:

br-eth1 Link encap:Ethernet HWaddr 00:11:25:8e:a8:2d
  inet addr:10.10.3.1 Bcast:10.10.255.255 Mask:255.255.0.0
  inet6 addr: fe80::211:

br-ex Link encap:Ethernet HWaddr 00:11:25:8e:a8:2c
  inet addr:9.126.108.143 Bcast:9.126.108.255 Mask:255.255.255.0
  inet6 addr: fe80::211:25ff:fe8e:a82c/64 Scope:Link
  UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
  RX packets:435547 errors:0 dropped:16395 overruns:0 frame:0
  TX packets:156208 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:46251450 (46.2 MB) TX bytes:135765850 (135.7 MB)


How did you created these br-* with IP?

Guilherme.


2013/2/7 Guilherme Russi 

> Hi Anil,
>
>  I'm trying to find something to fix it, are you using quantum or
> nova-network? I'm working with quantum, I have one physical computer with 2
> NICs that is the controller and another 4 physical computers with 2 NICs
> each that are the node compute, I left the Network node with the Controller
> node, at the same physical compute.
>
> Regards.
>
> Guilherme.
>
>
>
> 2013/2/7 Anil Vishnoi 
>
>> Hi Guilherme,
>>
>> I reported the same issue just a moment ago here :
>> https://answers.launchpad.net/quantum/+question/221283
>>
>> I think we are facing the same issue here- atleast VM logs shows.
>>
>> Anil
>>
>>
>> On Thu, Feb 7, 2013 at 5:14 PM, Guilherme Russi <
>> luisguilherme...@gmail.com> wrote:
>>
>>> Hello guys,
>>>
>>>  My VMs are not attaching IP address, I've been look the VM's log but I
>>> can't realize what is going on. I'm sending my VM's log. Can anybody help
>>> me, please?
>>>
>>> Regards.
>>>
>>> Guilherme.
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Thanks & Regards
>> --Anil Kumar Vishnoi
>>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Fwd: [Question #221283]: VM instance is not able to get IP address

2013-02-08 Thread Guilherme Russi

I'm getting a similar problem in my deploy. If someone could help, I
appreciate it.

Regards.

Guilherme.


2013/2/8 Anil Vishnoi 

> Hi All,
>
> I posted below question on launchpad -quantum, but i didn't get any
> response from the team, may be its not that active as openstack mailing
> list.
>
> I am facing an issue detailed in this question [
> https://answers.launchpad.net/quantum/+question/221283] and did some
> analysis and shared it on the same question. You can find my analysis in
> the below mail as well.
>
> I am looking for suggestion from the openstack networking expert on how to
> further debug this issue. My deployment is stuck because of this issue. I
> really appreciate your help.
>
> Thanks
> Anil
>
> -- Forwarded message --
> From: Anil Vishnoi 
> Date: Fri, Feb 8, 2013 at 3:41 AM
> Subject: Re: [Question #221283]: VM instance is not able to get IP address
> To: vishnoia...@gmail.com
>
>
> Your question #221283 on quantum changed:
> https://answers.launchpad.net/quantum/+question/221283
>
> You gave more information on the question:
> Hi Team,
>
> I further debugged this issue, and figure out one workaround. I really
> don't want to say it a "workaround" but moreover its a hack.
>
> As i mentioned in the above description that because of the action=drop,
> DHCP packets were getting dropped and not reaching to the DHCP agent,
> and hence it was not able to respond with the DHCPOFFER response.
>
> First i resolve this error [Feb 07
> 17:32:40|1|netdev_linux|WARN|/sys/class/net/tap9fdb5c15-26/carrier:
> open failed: ] with the following steps :
> 1. disable the network namespace for l3_agent and dhcp agent by modifying
> the use_namespace=false in the respective configuration file.
> 2. Delete the port (tap9fdb5c15-26) from the br-int bridge.
> [Quick instructions :
> root@management:~# ovs-vsctl del-port tap9fdb5c15-26
> root@management:~# ovs-vsctl add-port br-int tap9fdb5c15-26
> root@management:~# ovs-vsctl set port tap9fdb5c15-26 tag=1
> root@management:~# ovs-vsctl set Interface tap9fdb5c15-26 type=internal
> ]
> 3. Restart both the services and it will create tap devices outside the
> network name space.
>
> If network namespace is enabled, ifconfig will not show this tap device
> in its output, but if you fire command 'ip netns exec dhcpns ip -d
> link' it will show you the device.
>
> In my setup i followed the above step, but even if you don't want to
> disable namespace, you can stop dhcp agent, delete the port from br-int
> and restart the service. It possibly will resolve this error ( it did
> worked in my setup).
>
> So in my setup, namespace is disabled. And following is the output of
> ovs-dpctl
>
> root@management:~# ovs-dpctl show
> system@br-eth1:
> lookups: hit:151651 missed:37759 lost:0
> flows: 3
> port 0: br-eth1 (internal)
> port 1: eth1
> port 3: phy-br-eth1
> system@br-int:
> lookups: hit:1183 missed:23283 lost:0
> flows: 1
> port 0: br-int (internal)
> port 6: tap9fdb5c15-26 (internal)
> port 7: int-br-eth1
> system@br-ex:
> lookups: hit:96895 missed:67156 lost:0
> flows: 16
> port 0: br-ex (internal)
> port 1: eth0
>
> DHCP request packet is broadcast packet and it takes following path to
> reach the br-intport 1: eth1 (br-eth1) --> port 7: int-br-eth1(br-
> int) and this packet gets drop here because of the following rule
> installed on br-int bridge
>
>  cookie=0x0, duration=11422.615s, table=0, n_packets=16711,
> n_bytes=1178562, priority=2,in_port=7 actions=drop
>
> Ideally it should be forwarded to port 6: tap9fdb5c15-26 (internal) (br-
> int) and that way it can reach DHCP agent. So i modified above flow to
> following flow
>
> cookie=0x0, duration=3169.501s, table=0, n_packets=2562, n_bytes=228241,
> priority=2,in_port=7 actions=output:6
>
> and also installed following rule to route back the DHCPOFFER packet
>
> cookie=0x0, duration=4536.551s, table=0, n_packets=233, n_bytes=28896,
> priority=2,in_port=6 actions=output:7
>
> So after installing these two flow rules, DHCP agent got the request and
> responded with the DHCPOFFER response.
>
> root@management:~# tail -f /var/log/syslog
> Feb  8 03:26:16 management dnsmasq-dhcp[25811]:
> DHCPREQUEST(tap9fdb5c15-26) 192.168.0.3 fa:16:3e:93:74:73
> Feb  8 03:26:16 management dnsmasq-dhcp[25811]: DHCPACK(tap9fdb5c15-26)
> 192.168.0.3 fa:16:3e:93:74:73 192-168-0-3
>
> DHCP response packet will take following path  port 6: tap9fdb5c15-26
> (internal)(br-int) ---> port 7: int-br-eth1(br-int) ---> port 3: phy-br-
> eth1 (br-eth1) ---> port 1: eth1 (br-eth1)  and that way this packet
> will go out of controller node. But on br-eth1 bridge another rule was
> installed which was dropping the response
>
> cookie=0x0, duration=2669.22s, table=0, n_packets=173, n_bytes=18144,
> priority=2,in_port=3 actions=drop
>
> and i changed this flow to
>
> cookie=0x0, duration=2669.22s, table=0,

Re: [Openstack] Cant ping private or floating IP

2013-02-15 Thread Guilherme Russi

Hello guys,

 I got the same problem, I have enabled the SSH and Ping policies, when I
type "sudo ifconfig -a" inside my VM (Through VNC) the only IP showed is
the lo IP.
 What am I missing?

Regards.

Guilherme.


2013/2/15 Jean-Baptiste RANSY 

>  Hello Chathura;
>
> It's normal that your compute node have no route to the tenant network.
> Quantum and openvswitch provide Layer2 link and as i can see, the VM
> obtain a IP address.
> So we can assume that quantum and openvswitch are setup correctly.
>
> Same question as JuanFra : Have you enabled PING and SSH in 'Access and
> security policies'?
>
> Other things :
>
> Cloud-init (in VM) is unable to retrive metadata, does nova-api-metadata
> is running on your Compute Node ?
> If yes, check you nova.conf.
>
> Regards,
>
> Jean-Baptiste RANSY
>
>
>
> On 02/14/2013 11:58 PM, Chathura M. Sarathchandra Magurawalage wrote:
>
>  Hello,
>
>  I followed the folsom basic install instructions in
> http://docs.openstack.org/folsom/basic-install/content/basic-install_operate.html
>
>  But now I am not able to ping either the private or the floating ip of
> the instances.
>
>  Can someone please help?
>
>  Instance log:
>
>  [0.00] Initializing cgroup subsys cpuset
> [0.00] Initializing cgroup subsys cpu
> [0.00] Linux version 3.2.0-37-virtual (buildd@allspice) (gcc version 
> 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #58-Ubuntu SMP Thu Jan 24 15:48:03 UTC 
> 2013 (Ubuntu 3.2.0-37.58-virtual 3.2.35)
> [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-virtual 
> root=LABEL=cloudimg-rootfs ro console=ttyS0
> [0.00] KERNEL supported cpus:
> [0.00]   Intel GenuineIntel
> [0.00]   AMD AuthenticAMD
> [0.00]   Centaur CentaurHauls
> [0.00] BIOS-provided physical RAM map:
> [0.00]  BIOS-e820:  - 0009bc00 (usable)
> [0.00]  BIOS-e820: 0009bc00 - 000a (reserved)
> [0.00]  BIOS-e820: 000f - 0010 (reserved)
> [0.00]  BIOS-e820: 0010 - 7fffd000 (usable)
> [0.00]  BIOS-e820: 7fffd000 - 8000 (reserved)
> [0.00]  BIOS-e820: feffc000 - ff00 (reserved)
> [0.00]  BIOS-e820: fffc - 0001 (reserved)
> [0.00] NX (Execute Disable) protection: active
> [0.00] DMI 2.4 present.
> [0.00] No AGP bridge found
> [0.00] last_pfn = 0x7fffd max_arch_pfn = 0x4
> [0.00] x86 PAT enabled: cpu 0, old 0x70406, new 0x7010600070106
> [0.00] found SMP MP-table at [880fdae0] fdae0
> [0.00] init_memory_mapping: -7fffd000
> [0.00] RAMDISK: 3776c000 - 37bae000
> [0.00] ACPI: RSDP 000fd980 00014 (v00 BOCHS )
> [0.00] ACPI: RSDT 7fffd7b0 00034 (v01 BOCHS  BXPCRSDT 
> 0001 BXPC 0001)
> [0.00] ACPI: FACP 7f80 00074 (v01 BOCHS  BXPCFACP 
> 0001 BXPC 0001)
> [0.00] ACPI: DSDT 7fffd9b0 02589 (v01   BXPC   BXDSDT 
> 0001 INTL 20100528)
> [0.00] ACPI: FACS 7f40 00040
> [0.00] ACPI: SSDT 7fffd910 0009E (v01 BOCHS  BXPCSSDT 
> 0001 BXPC 0001)
> [0.00] ACPI: APIC 7fffd830 00072 (v01 BOCHS  BXPCAPIC 
> 0001 BXPC 0001)
> [0.00] ACPI: HPET 7fffd7f0 00038 (v01 BOCHS  BXPCHPET 
> 0001 BXPC 0001)
> [0.00] No NUMA configuration found
> [0.00] Faking a node at -7fffd000
> [0.00] Initmem setup node 0 -7fffd000
> [0.00]   NODE_DATA [7fff8000 - 7fffcfff]
> [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00
> [0.00] kvm-clock: cpu 0, msr 0:1cf7681, boot clock
> [0.00] Zone PFN ranges:
> [0.00]   DMA  0x0010 -> 0x1000
> [0.00]   DMA320x1000 -> 0x0010
> [0.00]   Normal   empty
> [0.00] Movable zone start PFN for each node
> [0.00] early_node_map[2] active PFN ranges
> [0.00] 0: 0x0010 -> 0x009b
> [0.00] 0: 0x0100 -> 0x0007fffd
> [0.00] ACPI: PM-Timer IO Port: 0xb008
> [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> [0.00] ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0])
> [0.00] IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-23
> [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
> [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
> [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
> [0.00] Using ACPI (MADT) for SMP configuration information
> [0.00] ACPI: HPET id: 0

[Openstack] Doubt with apt-get

2013-02-18 Thread Guilherme Russi

Hello guys,

 I got a message from my Ubuntu Server 12.04 about upgrade somethings, the
upgrades include Linux Headers and some upgrades for openstack's
components. My question is, if I apply the upgrades, my openstack system
can break off?

Thank you.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Cant ping private or floating IP

2013-02-18 Thread Guilherme Russi

Hello Chathura,

 Have succeeded with your network? I'm having problems with mine too.

Thanks.

Guilherme.


2013/2/17 Chathura M. Sarathchandra Magurawalage <77.chath...@gmail.com>

> Hope you had a good night sleep :)
>
> Yes sure I will be on irc. my nickname is chathura77
>
> Thanks
>
> On 17 February 2013 13:15, Jean-Baptiste RANSY <
> jean-baptiste.ra...@alyseo.com> wrote:
>
>>  ping
>>
>> Are you on IRC ?
>>
>> JB
>>
>>
>>
>> On 02/17/2013 04:07 AM, Jean-Baptiste RANSY wrote:
>>
>> 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 a static route to the subnet of your VM. (ip route add
>> 10.5.5.0/24 gw 192.168.2.151)
>> (192.168.2.151 is the quantum gateway)
>>
>> I'm going to sleep, we will continue tomorrow.
>>
>> JB
>>
>> PS : You also should get some sleep :)
>>
>>
>> On 02/17/2013 03:53 AM, Chathura M. Sarathchandra Magurawalage wrote:
>>
>>  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.0.0.0   .
>>
>> ci-info: eth0  : 1 10.5.5.3255.255.255.0   fa:16:3e:a7:28:25
>>
>> ci-info: route-0: 0.0.0.0 10.5.5.10.0.0.0 eth0   UG
>>
>> ci-info: route-1: 10.5.5.00.0.0.0 255.255.255.0   eth0   U
>>
>> cloud-init start running: Sun, 17 Feb 2013 02:45:35 +. up 3.51 seconds
>>
>> 2013-02-17 02:48:25,840 - util.py[WARNING]: 
>> 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: 
>> url error [timed out]
>>
>> 2013-02-17 02:49:16,893 - util.py[WARNING]: 
>> 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: 
>> url error [timed out]
>>
>> 2013-02-17 02:49:34,912 - util.py[WARNING]: 
>> 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: 
>> url error [timed out]
>>
>> 2013-02-17 02:49:35,913 - DataSourceEc2.py[CRITICAL]: giving up on md after 
>> 120 seconds
>>
>>
>>
>> no instance data found in start
>>
>> Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
>>
>>  * Starting AppArmor profiles   [80G
>> [74G[ OK ]
>>
>>
>>
>>  On 17 February 2013 02:41, Jean-Baptiste RANSY <
>> jean-baptiste.ra...@alyseo.com> wrote:
>>
>>>  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://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 -n -v
>>> Chain INPUT (policy ACCEPT 59009 packets, 22M bytes)
>>>  pkts bytes target prot opt in out source
>>> destination
>>> 59493   22M quantum-l3-agent-INPUT  all  --  *  *   0.0.0.0/0
>>>  0.0.0.0/0
>>> 59493   22M nova-api-INPUT  all  --  *  *   0.0.0.0/0
>>>  0.0.0.0/0
>>>   484 73533 ACCEPT 47   --  *  *   0.0.0.0/0
>>> 0.0.0.0/0
>>>
>>>  Chain FORWARD (policy ACCEPT 707 packets, 47819 bytes)
>>>  pkts bytes target prot opt in out source
>>> destination
>>>   707 47819 quantum-filter-top  all  --  *  *   0.0.0.0/0
>>>  0.0.0.0/0
>>>   707 47819 quantum-l3-agent-FORWARD  all  --  *  *   0.0.0.0/0
>>> 0.0.0.0/0
>>>   707 47819 nova-filter-top  all  --  *  *   0.0.0.0/0
>>>0.0.0.0/0
>>>   707 47819 nova-api-FORWARD  all  --  *  *   0.0.0.0/0
>>>0.0.0.0/0
>>>
>>>  Chain OUTPUT (policy ACCEPT 56022 packets, 22M bytes)
>>>  pkts bytes target prot opt in out source
>>> destination
>>> 56022   22M quantum-filter-top  all  --  *  *   0.0.0.0/0
>>>  0.0.0.0/0
>>> 56022   22M quantum-l3-agent-OUTPUT  all  --  *  *   0.0.0.0/0
>>> 0.0.0.0/0
>>> 56022   22M nova-filter-top  all  --  *  *   0.0.0.0/0
>>>0.0.0.0/0
>>> 56022   22M nova-api-OUTPUT  all  --  *  *   0.0.0.0/0
>>>0.0.0.0/0
>>>
>>>  Chain nova-api-FORWARD (1 references)
>>>  pkts bytes target prot opt in out source
>>> destination
>>>
>>>  Chain nova-api-INPUT (1 references)
>>>  pkts bytes target prot opt in out source
>>> destination
>>> 0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
>>> 192.168.2.225tcp dpt:8775

Re: [Openstack] Cant ping private or floating IP

2013-02-18 Thread Guilherme Russi

How did you install your controller node? I mean, mine I have 2 NICs and I
installed the network node at the same physical machine.


2013/2/18 Chathura M. Sarathchandra Magurawalage <77.chath...@gmail.com>

> Hello Guilherme,
>
> No, I am still having the problem :(
>
>
> On 18 February 2013 13:01, Guilherme Russi wrote:
>
>> Hello Chathura,
>>
>>  Have succeeded with your network? I'm having problems with mine too.
>>
>> Thanks.
>>
>> Guilherme.
>>
>>
>> 2013/2/17 Chathura M. Sarathchandra Magurawalage <77.chath...@gmail.com>
>>
>> Hope you had a good night sleep :)
>>>
>>> Yes sure I will be on irc. my nickname is chathura77
>>>
>>> Thanks
>>>
>>> On 17 February 2013 13:15, Jean-Baptiste RANSY <
>>> jean-baptiste.ra...@alyseo.com> wrote:
>>>
>>>>  ping
>>>>
>>>> Are you on IRC ?
>>>>
>>>> JB
>>>>
>>>>
>>>>
>>>> On 02/17/2013 04:07 AM, Jean-Baptiste RANSY wrote:
>>>>
>>>> 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 a static route to the subnet of your VM. (ip route add
>>>> 10.5.5.0/24 gw 192.168.2.151)
>>>> (192.168.2.151 is the quantum gateway)
>>>>
>>>> I'm going to sleep, we will continue tomorrow.
>>>>
>>>> JB
>>>>
>>>> PS : You also should get some sleep :)
>>>>
>>>>
>>>> On 02/17/2013 03:53 AM, Chathura M. Sarathchandra Magurawalage wrote:
>>>>
>>>>  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.0.0.0   .
>>>>
>>>> ci-info: eth0  : 1 10.5.5.3255.255.255.0   fa:16:3e:a7:28:25
>>>>
>>>> ci-info: route-0: 0.0.0.0 10.5.5.10.0.0.0 eth0   UG
>>>>
>>>> ci-info: route-1: 10.5.5.00.0.0.0 255.255.255.0   eth0   U
>>>>
>>>> cloud-init start running: Sun, 17 Feb 2013 02:45:35 +. up 3.51 seconds
>>>>
>>>> 2013-02-17 02:48:25,840 - util.py[WARNING]: 
>>>> 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
>>>> [50/120s]: url error [timed out]
>>>>
>>>> 2013-02-17 02:49:16,893 - util.py[WARNING]: 
>>>> 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
>>>> [101/120s]: url error [timed out]
>>>>
>>>> 2013-02-17 02:49:34,912 - util.py[WARNING]: 
>>>> 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
>>>> [119/120s]: url error [timed out]
>>>>
>>>> 2013-02-17 02:49:35,913 - DataSourceEc2.py[CRITICAL]: giving up on md 
>>>> after 120 seconds
>>>>
>>>>
>>>>
>>>> no instance data found in start
>>>>
>>>> Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
>>>>
>>>>  * Starting AppArmor profiles   [80G
>>>> [74G[ OK ]
>>>>
>>>>
>>>>
>>>>  On 17 February 2013 02:41, Jean-Baptiste RANSY <
>>>> jean-baptiste.ra...@alyseo.com> wrote:
>>>>
>>>>>  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://169.254.169.2

Re: [Openstack] Cant ping private or floating IP

2013-02-18 Thread Guilherme Russi

Got it, I have one virtual interface too, to make the management and VM
conf part. If you find anything, let me know, please.

Thanks.


2013/2/18 Chathura M. Sarathchandra Magurawalage <77.chath...@gmail.com>

> I have only got 1 NIC but got two virtual interface for two different
> networks. I have got network node in the same physical machine too.
>
>
> On 18 February 2013 13:15, Guilherme Russi wrote:
>
>> How did you install your controller node? I mean, mine I have 2 NICs and
>> I installed the network node at the same physical machine.
>>
>>
>> 2013/2/18 Chathura M. Sarathchandra Magurawalage <77.chath...@gmail.com>
>>
>> Hello Guilherme,
>>>
>>> No, I am still having the problem :(
>>>
>>>
>>> On 18 February 2013 13:01, Guilherme Russi 
>>> wrote:
>>>
>>>> Hello Chathura,
>>>>
>>>>  Have succeeded with your network? I'm having problems with mine too.
>>>>
>>>> Thanks.
>>>>
>>>> Guilherme.
>>>>
>>>>
>>>> 2013/2/17 Chathura M. Sarathchandra Magurawalage <77.chath...@gmail.com
>>>> >
>>>>
>>>> Hope you had a good night sleep :)
>>>>>
>>>>> Yes sure I will be on irc. my nickname is chathura77
>>>>>
>>>>> Thanks
>>>>>
>>>>> On 17 February 2013 13:15, Jean-Baptiste RANSY <
>>>>> jean-baptiste.ra...@alyseo.com> wrote:
>>>>>
>>>>>>  ping
>>>>>>
>>>>>> Are you on IRC ?
>>>>>>
>>>>>> JB
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 02/17/2013 04:07 AM, Jean-Baptiste RANSY wrote:
>>>>>>
>>>>>> 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 a static route to the subnet of your VM. (ip route add
>>>>>> 10.5.5.0/24 gw 192.168.2.151)
>>>>>> (192.168.2.151 is the quantum gateway)
>>>>>>
>>>>>> I'm going to sleep, we will continue tomorrow.
>>>>>>
>>>>>> JB
>>>>>>
>>>>>> PS : You also should get some sleep :)
>>>>>>
>>>>>>
>>>>>> On 02/17/2013 03:53 AM, Chathura M. Sarathchandra Magurawalage wrote:
>>>>>>
>>>>>>  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.0.0.0   .
>>>>>>
>>>>>> ci-info: eth0  : 1 10.5.5.3255.255.255.0   fa:16:3e:a7:28:25
>>>>>>
>>>>>> ci-info: route-0: 0.0.0.0 10.5.5.10.0.0.0 eth0   
>>>>>> UG
>>>>>>
>>>>>> ci-info: route-1: 10.5.5.00.0.0.0 255.255.255.0   eth0   
>>>>>> U
>>>>>>
>>>>>> cloud-init start running: Sun, 17 Feb 2013 02:45:35 +. up 3.51 
>>>>>> seconds
>>>>>>
>>>>>> 2013-02-17 02:48:25,840 - util.py[WARNING]: 
>>>>>> 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
>>>>>> [50/120s]: url error [timed out]
>>>>>>
>>>>>> 2013-02-17 02:49:16,893 - util.py[WARNING]: 
>>>>>> 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
>>>>>> [101/120s]: url error [timed out]
>>>>>>
>>>>>> 2013-02-17 02:49:34,912 - util.py[WARNING]: 
>>>>>> 'http://169.254.169.254

Re: [Openstack] Doubt with apt-get

2013-02-18 Thread Guilherme Russi

Thanks for the support guys. The way is keep a backup :)



2013/2/18 Razique Mahroua 

> That what I would say also - never sure. Dump your database and save your
> configuration files, depending on when you run an upgrade for the last time
> :)
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 18 févr. 2013 à 20:05, Aaron Rosen  a écrit :
>
> Anything is possible with upgrading but hopefully not :P
>
> On Mon, Feb 18, 2013 at 4:18 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> Hello guys,
>>
>>  I got a message from my Ubuntu Server 12.04 about upgrade somethings,
>> the upgrades include Linux Headers and some upgrades for openstack's
>> components. My question is, if I apply the upgrades, my openstack system
>> can break off?
>>
>> Thank you.
>>
>> Guilherme.
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
<>___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] VM doesnt get IP

2013-02-21 Thread Guilherme Russi

Hello guys,

 I'm getting problem in my VMs' creation, they don't get IP, the log piece
shows:


Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed


 Do you have any idea how I can solve it?

Thank you so much.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] VM doesnt get IP

2013-02-21 Thread Guilherme Russi

Sorry about that, I'm using Folsom release with quantum, I'm installing the
controller node and the network node in the same physical machine, I'm
following this tutorial:

http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html

Which config files do you need?

Thanks.

Guilherme.


2013/2/21 Aaron Rosen 

> Hi,
>
> You'll have to provide more information than this for anyone to help you:
> i.e are you using quantum or nova-network, if your using quantum which
> plugin, config files etc.
>
> Aaron
>
> On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> Hello guys,
>>
>>  I'm getting problem in my VMs' creation, they don't get IP, the log
>> piece shows:
>>
>>
>>
>> Starting network...
>> udhcpc (v1.18.5) started
>> Sending discover...
>> Sending discover...
>> Sending discover...
>> No lease, failing
>> WARN: /etc/rc3.d/S40-network failed
>>
>>
>>  Do you have any idea how I can solve it?
>>
>> Thank you so much.
>>
>> Guilherme.
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] VM doesnt get IP

2013-02-22 Thread Guilherme Russi

Hello Aaron,

 Here are the outputs.

Thanks.

Guilherme.


2013/2/21 Aaron Rosen 

> The output to the following would be a good start:
>
> quantum net-list
> quantum port-list
> ovs-dpctl show (on all nodes)
>
> Also make sure the quantum-dhcp-agent is running on your network node.
>
> Aaron
>
> On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> Sorry about that, I'm using Folsom release with quantum, I'm installing
>> the controller node and the network node in the same physical machine, I'm
>> following this tutorial:
>>
>>
>> http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html
>>
>> Which config files do you need?
>>
>> Thanks.
>>
>> Guilherme.
>>
>>
>> 2013/2/21 Aaron Rosen 
>>
>>> Hi,
>>>
>>> You'll have to provide more information than this for anyone to help
>>> you: i.e are you using quantum or nova-network, if your using quantum which
>>> plugin, config files etc.
>>>
>>> Aaron
>>>
>>> On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi <
>>> luisguilherme...@gmail.com> wrote:
>>>
>>>> Hello guys,
>>>>
>>>>  I'm getting problem in my VMs' creation, they don't get IP, the log
>>>> piece shows:
>>>>
>>>>
>>>>
>>>> Starting network...
>>>> udhcpc (v1.18.5) started
>>>> Sending discover...
>>>> Sending discover...
>>>> Sending discover...
>>>> No lease, failing
>>>> WARN: /etc/rc3.d/S40-network failed
>>>>
>>>>
>>>>  Do you have any idea how I can solve it?
>>>>
>>>> Thank you so much.
>>>>
>>>> Guilherme.
>>>>
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>


outputs
Description: Binary data
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] VM doesnt get IP

2013-02-22 Thread Guilherme Russi

So guys, any idea about what am i missing?

Thanks.



2013/2/22 Guilherme Russi 

> Hello Aaron,
>
>  Here are the outputs.
>
>
> Thanks.
>
> Guilherme.
>
>
> 2013/2/21 Aaron Rosen 
>
>> The output to the following would be a good start:
>>
>> quantum net-list
>> quantum port-list
>> ovs-dpctl show (on all nodes)
>>
>> Also make sure the quantum-dhcp-agent is running on your network node.
>>
>> Aaron
>>
>> On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi <
>> luisguilherme...@gmail.com> wrote:
>>
>>> Sorry about that, I'm using Folsom release with quantum, I'm installing
>>> the controller node and the network node in the same physical machine, I'm
>>> following this tutorial:
>>>
>>>
>>> http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html
>>>
>>> Which config files do you need?
>>>
>>> Thanks.
>>>
>>> Guilherme.
>>>
>>>
>>> 2013/2/21 Aaron Rosen 
>>>
>>>> Hi,
>>>>
>>>> You'll have to provide more information than this for anyone to help
>>>> you: i.e are you using quantum or nova-network, if your using quantum which
>>>> plugin, config files etc.
>>>>
>>>> Aaron
>>>>
>>>> On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi <
>>>> luisguilherme...@gmail.com> wrote:
>>>>
>>>>> Hello guys,
>>>>>
>>>>>  I'm getting problem in my VMs' creation, they don't get IP, the log
>>>>> piece shows:
>>>>>
>>>>>
>>>>>
>>>>> Starting network...
>>>>> udhcpc (v1.18.5) started
>>>>> Sending discover...
>>>>> Sending discover...
>>>>> Sending discover...
>>>>> No lease, failing
>>>>> WARN: /etc/rc3.d/S40-network failed
>>>>>
>>>>>
>>>>>  Do you have any idea how I can solve it?
>>>>>
>>>>> Thank you so much.
>>>>>
>>>>> Guilherme.
>>>>>
>>>>>
>>>>> ___
>>>>> Mailing list: https://launchpad.net/~openstack
>>>>> Post to : openstack@lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] VM doesnt get IP

2013-02-22 Thread Guilherme Russi

Hello Aaron,

 Sorry about attaching the infos, about the quantum agent, is it the
quantum-plugin-openvswitch-agent? If i was, the job is already ruunning at
the controller and the compute nodes:

service quantum-plugin-openvswitch-agent start
start: Job is already running: quantum-plugin-openvswitch-agent

 Is there another thing i should do? I'm running my controller node and the
network node at the same machine with 2 NICs, maybe can be a problem how i
am making my network config?

Thanks again.

Guilherme.

2013/2/22 Aaron Rosen 

> Hi Guilherme,
>
> (next time please paste these in the email rather than attaching, thx).
>
> From the text in the attachment (show below). It seems like you are not
> running the quantum-openvswitch-agent on your network node as there is no
> GRE tunnel from that to your compute node. Once you have
>  quantum-openvswitch-agent running on all your machines you should be able
> to run ovs-dpctl looking under br-tun and see a tunnel between each host.
>
> Aaron
>
> CONTROLLER + NETWORK NODE:
> system@br-tun:
> lookups: hit:0 missed:0 lost:0
> flows: 0
>  port 0: br-tun (internal)
> port 1: patch-int (patch: peer=patch-tun)
> system@br-int:
>  lookups: hit:0 missed:0 lost:0
> flows: 0
> port 0: br-int (internal)
>  port 1: tap817d2f70-a0 (internal)
> port 2: qr-ea64e9aa-31 (internal)
> port 3: patch-tun (patch: peer=patch-int)
> system@br-ex:
> lookups: hit:0 missed:0 lost:0
> flows: 0
> port 0: br-ex (internal)
>  port 2: qg-95fe3fa1-d1 (internal)
>
>
> COMPUTE NODES
>
> COMPUTE NODE 01:
> ovs-dpctl show
> system@br-int:
> lookups: hit:380 missed:7590 lost:0
> flows: 0
> port 0: br-int (internal)
>  port 2: patch-tun (patch: peer=patch-int)
> port 3: qvo981ae82e-d4
> port 6: qvoc9df3a96-5f
>  port 7: qvoc153ac28-ae
> port 8: qvo722a5d05-e4
> system@br-tun:
> lookups: hit:381 missed:7589 lost:0
>  flows: 0
> port 0: br-tun (internal)
> port 1: patch-int (patch: peer=patch-tun)
>  port 2: gre-1 (gre: key=flow, remote_ip=10.10.10.1)
>
>
> On Fri, Feb 22, 2013 at 8:47 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> So guys, any idea about what am i missing?
>>
>> Thanks.
>>
>>
>>
>>
>> 2013/2/22 Guilherme Russi 
>>
>>> Hello Aaron,
>>>
>>>  Here are the outputs.
>>>
>>>
>>> Thanks.
>>>
>>> Guilherme.
>>>
>>>
>>> 2013/2/21 Aaron Rosen 
>>>
>>>> The output to the following would be a good start:
>>>>
>>>> quantum net-list
>>>> quantum port-list
>>>> ovs-dpctl show (on all nodes)
>>>>
>>>> Also make sure the quantum-dhcp-agent is running on your network node.
>>>>
>>>> Aaron
>>>>
>>>> On Thu, Feb 21, 2013 at 11:23 AM, Guilherme Russi <
>>>> luisguilherme...@gmail.com> wrote:
>>>>
>>>>> Sorry about that, I'm using Folsom release with quantum, I'm
>>>>> installing the controller node and the network node in the same physical
>>>>> machine, I'm following this tutorial:
>>>>>
>>>>>
>>>>> http://docs.openstack.org/folsom/basic-install/content/basic-install_controller.html
>>>>>
>>>>> Which config files do you need?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Guilherme.
>>>>>
>>>>>
>>>>> 2013/2/21 Aaron Rosen 
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> You'll have to provide more information than this for anyone to help
>>>>>> you: i.e are you using quantum or nova-network, if your using quantum 
>>>>>> which
>>>>>> plugin, config files etc.
>>>>>>
>>>>>> Aaron
>>>>>>
>>>>>> On Thu, Feb 21, 2013 at 11:13 AM, Guilherme Russi <
>>>>>> luisguilherme...@gmail.com> wrote:
>>>>>>
>>>>>>> Hello guys,
>>>>>>>
>>>>>>>  I'm getting problem in my VMs' creation, they don't get IP, the log
>>>>>>> piece shows:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Starting network...
>>>>>>> udhcpc (v1.18.5) started
>>>>>>> Sending discover...
>>>>>>> Sending discover...
>>>>>>> Sending discover...
>>>>>>> No lease, failing
>>>>>>> WARN: /etc/rc3.d/S40-network failed
>>>>>>>
>>>>>>>
>>>>>>>  Do you have any idea how I can solve it?
>>>>>>>
>>>>>>> Thank you so much.
>>>>>>>
>>>>>>> Guilherme.
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Mailing list: https://launchpad.net/~openstack
>>>>>>> Post to : openstack@lists.launchpad.net
>>>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] VM does not get IP address

2013-02-22 Thread Guilherme Russi

Hello Lukas,

 We can share our problems at the same thread, i saw a post of yours there
and, apparently, we have the same problem with the VM's IP.

Regards.

Guilherme.

2013/2/22 Salvatore Orlando 

> The other thread currently active at the moment is titled "[Openstack]
> VM doesnt get IP".
> Aaron Rosen, Quantum core developer, is assisting a member of the
> community who's apparently having exactly the same problem as you are.
>
> Please note that 169.254.169.254 is the metadata address. In order for
> metadata access to work, with the Folsom Quantum release, you also
> need to create a Quantum router and connect your network to it (and,
> of course, ensure the l3-agent is running with the appropriate IP and
> port configured for the metadata server).
>
> Salvatore
>
> On 22 February 2013 19:08, Anil Vishnoi  wrote:
> > Hi  Lukas,
> >
> > There few threads on openstack mailing list where people discussed this
> > issue. You can search with "wget: can't connect to remote host
> > (169.254.169.254): Network is unreachable" and you will see most of those
> > threads. These threads will give you some insight on how to debug this
> issue
> > to find the root cause. If you get stuck and have queries please feel
> free
> > to drop a mail to the list.
> >
> > Anil
> >
> >
> > On Fri, Feb 22, 2013 at 2:57 PM, Lukáš Vízner 
> wrote:
> >>
> >> Hi,
> >>
> >> I am following this manual
> >>
> >>
> https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/cbc6c95e749dea86fb4c77fcbf485e55c37a297d/OpenStack_Folsom_Install_Guide_WebVersion.rst
> >> to install OpenStack Folsom
> >>
> >> I have created one tenant net called "net1". When I launch an
> >> instance, there is this error:
> >>
> >> nitializing random number generator... done.
> >> Starting network...
> >> udhcpc (v1.18.5) started
> >> Sending discover...
> >> Sending discover...
> >> Sending discover...
> >> No lease, failing
> >> WARN: /etc/rc3.d/S40-network failed
> >> cloud-setup: checking
> >> http://169.254.169.254/2009-04-04/meta-data/instance-id
> >> wget: can't connect to remote host (169.254.169.254): Network is
> >> unreachable
> >> cloud-setup: failed 1/30: up 10.09. request failed
> >> wget: can't connect to remote host (169.254.169.254): Network is
> >> unreachable
> >> cloud-setup: failed 2/30: up 11.10. request failed
> >> wget: can't connect to remote host (169.254.169.254): Network is
> >> unreachable
> >>
> >> Here are outputs:
> >> root@folsom-controller:/etc/init.d# quantum net-list
> >>
> >>
> +--+--+--+
> >> | id   | name | subnets
> >>   |
> >>
> >>
> +--+--+--+
> >> | 3c2eed52-969b-44a2-bd33-790999c5da5c | net1 |
> >> a82109bf-5777-4730-b44a-5dceebc835cb |
> >>
> >>
> +--+--+--+
> >>
> >> root@folsom-controller:/etc/init.d#quantum port-list
> >>
> >>
> +--+--+---+-+
> >> | id   | name | mac_address   |
> >> fixed_ips
> >>  |
> >>
> >>
> +--+--+---+-+
> >> | 0a410916-ce92-4d41-9085-1358f6493269 |  | fa:16:3e:4e:d9:40 |
> >> {"subnet_id": "a82109bf-5777-4730-b44a-5dceebc835cb", "ip_address":
> >> "10.5.5.2"} |
> >> | eea126e8-8661-4d55-b3e0-655d758a9203 |  | fa:16:3e:ff:7e:ab |
> >> {"subnet_id": "a82109bf-5777-4730-b44a-5dceebc835cb", "ip_address":
> >> "10.5.5.1"} |
> >>
> >>
> +--+--+---+-+
> >>
> >> Please could you help me solve this problem?
> >> What configuration files do you need?
> >>
> >> Thank you!!!
> >>
> >>
> >> --
> >> Lukáš Vízner
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to : openstack@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~openstack
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> >
> > --
> > Thanks
> > Anil
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing

Re: [Openstack] VM doesnt get IP

2013-02-22 Thread Guilherme Russi

.
#
# Default: enable_tunneling = False
enable_tunneling = True

# (ListOpt) Comma-separated list of : tuples
# enumerating ranges of GRE tunnel IDs that are available for tenant
# network allocation if tenant_network_type is 'gre'.
#
# Default: tunnel_id_ranges =
# Example: tunnel_id_ranges = 1:1000
tunnel_id_ranges = 1:1000

# Do not change this parameter unless you have a good reason to.
# This is the name of the OVS integration bridge. There is one per
hypervisor.
# The integration bridge acts as a virtual "patch bay". All VM VIFs are
# attached to this bridge and then "patched" according to their network
# connectivity.
#
# Default: integration_bridge = br-int
integration_bridge = br-int

# Only used for the agent if tunnel_id_ranges (above) is not empty for
# the server.  In most cases, the default value should be fine.
#
# Default: tunnel_bridge = br-tun
tunnel_bridge = br-tun

# Uncomment this line for the agent if tunnel_id_ranges (above) is not
# empty for the server. Set local-ip to be the local IP address of
# this hypervisor.
#
# Default: local_ip = 10.0.0.3
local_ip = 192.168.3.3

The 10.10.10.1 is the Data Network from network controller (following the
tutorial), and it is in the eth0:0 (I'm not pretty sure, but i guess the
data from the VMs should communicate with this IP).




2013/2/22 Aaron Rosen 

> Running with two nics for this should be fine for tunneling as ip routing
> would handle which nic the packets should go out. From what you pasted I
> see that one HV has a gre tunnel setup to 10.10.10.1 <-- Who is that host?
> Can you attach your /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
> on your nodes.
>
> I suspect the issue is a configuration issue in the [OVS] section. You'll
> need something along the lines of this in that section:
> [OVS]
> local_ip = 
> enable_tunneling = True
> tunnel_id_ranges = 1:1000
> tenant_network_type = gre
>
>
>
>
> On Fri, Feb 22, 2013 at 9:54 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> Hello Aaron,
>>
>>  Sorry about attaching the infos, about the quantum agent, is it the
>> quantum-plugin-openvswitch-agent? If i was, the job is already ruunning at
>> the controller and the compute nodes:
>>
>> service quantum-plugin-openvswitch-agent start
>> start: Job is already running: quantum-plugin-openvswitch-agent
>>
>>  Is there another thing i should do? I'm running my controller node and
>> the network node at the same machine with 2 NICs, maybe can be a problem
>> how i am making my network config?
>>
>> Thanks again.
>>
>> Guilherme.
>>
>>
>> 2013/2/22 Aaron Rosen 
>>
>>> Hi Guilherme,
>>>
>>> (next time please paste these in the email rather than attaching, thx).
>>>
>>> From the text in the attachment (show below). It seems like you are not
>>> running the quantum-openvswitch-agent on your network node as there is no
>>> GRE tunnel from that to your compute node. Once you have
>>>  quantum-openvswitch-agent running on all your machines you should be able
>>> to run ovs-dpctl looking under br-tun and see a tunnel between each host.
>>>
>>> Aaron
>>>
>>> CONTROLLER + NETWORK NODE:
>>> system@br-tun:
>>> lookups: hit:0 missed:0 lost:0
>>> flows: 0
>>>  port 0: br-tun (internal)
>>> port 1: patch-int (patch: peer=patch-tun)
>>> system@br-int:
>>>  lookups: hit:0 missed:0 lost:0
>>> flows: 0
>>> port 0: br-int (internal)
>>>  port 1: tap817d2f70-a0 (internal)
>>> port 2: qr-ea64e9aa-31 (internal)
>>> port 3: patch-tun (patch: peer=patch-int)
>>> system@br-ex:
>>> lookups: hit:0 missed:0 lost:0
>>> flows: 0
>>> port 0: br-ex (internal)
>>>  port 2: qg-95fe3fa1-d1 (internal)
>>>
>>>
>>> COMPUTE NODES
>>>
>>> COMPUTE NODE 01:
>>> ovs-dpctl show
>>> system@br-int:
>>> lookups: hit:380 missed:7590 lost:0
>>> flows: 0
>>> port 0: br-int (internal)
>>>  port 2: patch-tun (patch: peer=patch-int)
>>> port 3: qvo981ae82e-d4
>>> port 6: qvoc9df3a96-5f
>>>  port 7: qvoc153ac28-ae
>>> port 8: qvo722a5d05-e4
>>> system@br-tun:
>>> lookups: hit:381 missed:7589 lost:0
>>>  flows: 0
>>> port 0: br-tun (internal)
>>> port 1: patch-int (patch: peer=patch-tun)
>>>  port 2: gre-1 (gre: key=flow, remote_ip=10.10.10.1)
>>>
>>>
>>> On Fri, Feb 22, 2013 at 8:47 AM, Guilherme Russi <
>>> luisguilherme...@gmail

Re: [Openstack] VM doesnt get IP

2013-02-25 Thread Guilherme Russi

Hello Aaron, I can ping to 192.168.3.3

ping 192.168.3.3
PING 192.168.3.3 (192.168.3.3) 56(84) bytes of data.
64 bytes from 192.168.3.3: icmp_req=1 ttl=64 time=0.237 ms
64 bytes from 192.168.3.3: icmp_req=2 ttl=64 time=0.193 ms

What am I missing?

Regards.

Guilherme.


2013/2/23 Rahul Sharma 

> In one config, you have specified local_ip as 10.10.10.1 and in other as
> 192.168.3.3 . Doesn't they should belong to same network? As per the doc,
> it should be 10.10.10.3? Plus, these both belong to Data-Network, which is
> not controller-network communication but compute-network communication.
>
> -Regards
> Rahul
>
>
> On Sat, Feb 23, 2013 at 12:53 AM, Aaron Rosen  wrote:
>
>> >From the network+controller node can you ping to 192.168.3.3 (just to
>> confirm there is ip connectivity between those).
>>
>> Your configs look fine to me. The issue you are having is that your
>> network+controller node doesn't have a tunnel to your HV node. I'd suggest
>> restarting  the quantum-plugin-openvswitch-agent service on both nodes and
>> see if that does the trick in order to get the agent to add the tunnel for
>> you. Perhaps you edited this file and didn't restart the agent?
>>
>> Aaron
>>
>> On Fri, Feb 22, 2013 at 10:55 AM, Guilherme Russi <
>> luisguilherme...@gmail.com> wrote:
>>
>>> Here is my controller + network node:
>>>
>>> cat /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
>>> [DATABASE]
>>> # This line MUST be changed to actually run the plugin.
>>> # Example:
>>> # sql_connection = mysql://root:nova@127.0.0.1:3306/ovs_quantum
>>> # Replace 127.0.0.1 above with the IP address of the database used by the
>>> # main quantum server. (Leave it as is if the database runs on this
>>> host.)
>>> sql_connection = mysql://quantum:password@localhost:3306/quantum
>>> # Database reconnection retry times - in event connectivity is lost
>>> # set to -1 implies an infinite retry count
>>> # sql_max_retries = 10
>>> # Database reconnection interval in seconds - in event connectivity is
>>> lost
>>> reconnect_interval = 2
>>>
>>> [OVS]
>>> # (StrOpt) Type of network to allocate for tenant networks. The
>>> # default value 'local' is useful only for single-box testing and
>>> # provides no connectivity between hosts. You MUST either change this
>>> # to 'vlan' and configure network_vlan_ranges below or change this to
>>> # 'gre' and configure tunnel_id_ranges below in order for tenant
>>> # networks to provide connectivity between hosts. Set to 'none' to
>>> # disable creation of tenant networks.
>>> #
>>> # Default: tenant_network_type = local
>>> # Example: tenant_network_type = gre
>>> tenant_network_type = gre
>>>
>>> # (ListOpt) Comma-separated list of
>>> # [::] tuples enumerating ranges
>>> # of VLAN IDs on named physical networks that are available for
>>> # allocation. All physical networks listed are available for flat and
>>> # VLAN provider network creation. Specified ranges of VLAN IDs are
>>> # available for tenant network allocation if tenant_network_type is
>>> # 'vlan'. If empty, only gre and local networks may be created.
>>> #
>>> # Default: network_vlan_ranges =
>>> # Example: network_vlan_ranges = physnet1:1000:2999
>>>
>>> # (BoolOpt) Set to True in the server and the agents to enable support
>>> # for GRE networks. Requires kernel support for OVS patch ports and
>>> # GRE tunneling.
>>> #
>>> # Default: enable_tunneling = False
>>> enable_tunneling = True
>>>
>>> # (ListOpt) Comma-separated list of : tuples
>>> # enumerating ranges of GRE tunnel IDs that are available for tenant
>>> # network allocation if tenant_network_type is 'gre'.
>>> #
>>> # Default: tunnel_id_ranges =
>>> # Example: tunnel_id_ranges = 1:1000
>>> tunnel_id_ranges = 1:1000
>>>
>>> # Do not change this parameter unless you have a good reason to.
>>> # This is the name of the OVS integration bridge. There is one per
>>> hypervisor.
>>> # The integration bridge acts as a virtual "patch bay". All VM VIFs are
>>> # attached to this bridge and then "patched" according to their network
>>> # connectivity.
>>> #
>>> # Default: integration_bridge = br-int
>>> integration_bridge = br-int
>>>
>>> # Only used

[Openstack] Doubt quantum script

2013-03-04 Thread Guilherme Russi

Hello guys,

 I'm installing the openstack folsom again, but now I have a controller
node in a proper physical machine and the network node in another one, but
which of them I execute the quantum-networking script? I'm following this
manual
http://docs.openstack.org/folsom/basic-install/content/basic-install_network.htmland
I'm trying to execute at the network node, but I got error when
execute
it. When I type keystone tenant-list and quantum net-list I got the error
[Errno 111] Unable to communicate with identity service.
 My novarc is configured at the network node too.

Thanks.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Doubt quantum script

2013-03-04 Thread Guilherme Russi

Found the problem, when I did the step: ovs-vsctl add-port br-ex eth2, it
stopped my lan communication.

Any idea?



2013/3/4 Guilherme Russi 

> Hello guys,
>
>  I'm installing the openstack folsom again, but now I have a controller
> node in a proper physical machine and the network node in another one, but
> which of them I execute the quantum-networking script? I'm following this
> manual
> http://docs.openstack.org/folsom/basic-install/content/basic-install_network.htmland
>  I'm trying to execute at the network node, but I got error when execute
> it. When I type keystone tenant-list and quantum net-list I got the error
> [Errno 111] Unable to communicate with identity service.
>  My novarc is configured at the network node too.
>
> Thanks.
>
> Guilherme.
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Doubt quantum script

2013-03-04 Thread Guilherme Russi

Thanks for answering, now I need to realise why my instances aren't being
created.


2013/3/4 Gary Kotton 

>  On 03/04/2013 05:45 PM, Guilherme Russi wrote:
>
> Found the problem, when I did the step: ovs-vsctl add-port br-ex eth2, it
> stopped my lan communication.
>
>
> The l3 agent makes changes to the routing table. This may cause a conflict
> with the default gateway. I would suggest having a static route for the
> management traffic (I guess that your could have been received via DHCP).
> Thanks
> Gary
>
>
> Any idea?
>
>
>
> 2013/3/4 Guilherme Russi 
>
>> Hello guys,
>>
>>  I'm installing the openstack folsom again, but now I have a controller
>> node in a proper physical machine and the network node in another one, but
>> which of them I execute the quantum-networking script? I'm following this
>> manual
>> http://docs.openstack.org/folsom/basic-install/content/basic-install_network.htmland
>>  I'm trying to execute at the network node, but I got error when execute
>> it. When I type keystone tenant-list and quantum net-list I got the error
>> [Errno 111] Unable to communicate with identity service.
>>  My novarc is configured at the network node too.
>>
>> Thanks.
>>
>> Guilherme.
>>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Doubt quantum script

2013-03-04 Thread Guilherme Russi

How do I move it?

Thanks.

2013/3/4 Dan Wendlandt 

>
>
> On Mon, Mar 4, 2013 at 7:49 AM, Gary Kotton  wrote:
>
>>  On 03/04/2013 05:45 PM, Guilherme Russi wrote:
>>
>> Found the problem, when I did the step: ovs-vsctl add-port br-ex eth2, it
>> stopped my lan communication.
>>
>>
>> The l3 agent makes changes to the routing table. This may cause a
>> conflict with the default gateway. I would suggest having a static route
>> for the management traffic (I guess that your could have been received via
>> DHCP).
>> Thanks
>> Gary
>>
>
> It seems like you had an IP address on eth2.  When you add an interface
> with an IP address to a bridge, you need to move that IP address from the
> interface device to the bridge device.
>
> Dan
>
>
>
>
>>
>>
>> Any idea?
>>
>>
>>
>> 2013/3/4 Guilherme Russi 
>>
>>> Hello guys,
>>>
>>>  I'm installing the openstack folsom again, but now I have a controller
>>> node in a proper physical machine and the network node in another one, but
>>> which of them I execute the quantum-networking script? I'm following this
>>> manual
>>> http://docs.openstack.org/folsom/basic-install/content/basic-install_network.htmland
>>>  I'm trying to execute at the network node, but I got error when execute
>>> it. When I type keystone tenant-list and quantum net-list I got the error
>>> [Errno 111] Unable to communicate with identity service.
>>>  My novarc is configured at the network node too.
>>>
>>> Thanks.
>>>
>>> Guilherme.
>>>
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> ~~~
> Dan Wendlandt
> Nicira, Inc: www.nicira.com
> twitter: danwendlandt
> ~~~
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Doubt quantum script

2013-03-04 Thread Guilherme Russi

I make my configs manually, so I need to set auto br-ex and declare the
iface br-ex inet static inserting the IP?

Thanks again.


2013/3/4 Dan Wendlandt 

> if manually, you can just use ifconfing.  If you use system tools for
> configuring the IP address, make sure those tools set the IP on br-ex, not
> eth2.
>
> dan
>
>
> On Mon, Mar 4, 2013 at 10:55 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> How do I move it?
>>
>> Thanks.
>>
>>
>> 2013/3/4 Dan Wendlandt 
>>
>>>
>>>
>>> On Mon, Mar 4, 2013 at 7:49 AM, Gary Kotton  wrote:
>>>
>>>>  On 03/04/2013 05:45 PM, Guilherme Russi wrote:
>>>>
>>>> Found the problem, when I did the step: ovs-vsctl add-port br-ex eth2,
>>>> it stopped my lan communication.
>>>>
>>>>
>>>> The l3 agent makes changes to the routing table. This may cause a
>>>> conflict with the default gateway. I would suggest having a static route
>>>> for the management traffic (I guess that your could have been received via
>>>> DHCP).
>>>> Thanks
>>>> Gary
>>>>
>>>
>>> It seems like you had an IP address on eth2.  When you add an interface
>>> with an IP address to a bridge, you need to move that IP address from the
>>> interface device to the bridge device.
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>> Any idea?
>>>>
>>>>
>>>>
>>>> 2013/3/4 Guilherme Russi 
>>>>
>>>>> Hello guys,
>>>>>
>>>>>  I'm installing the openstack folsom again, but now I have a
>>>>> controller node in a proper physical machine and the network node in
>>>>> another one, but which of them I execute the quantum-networking script? 
>>>>> I'm
>>>>> following this manual
>>>>> http://docs.openstack.org/folsom/basic-install/content/basic-install_network.htmland
>>>>>  I'm trying to execute at the network node, but I got error when execute
>>>>> it. When I type keystone tenant-list and quantum net-list I got the error
>>>>> [Errno 111] Unable to communicate with identity service.
>>>>>  My novarc is configured at the network node too.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Guilherme.
>>>>>
>>>>
>>>>
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> ~~~
>>> Dan Wendlandt
>>> Nicira, Inc: www.nicira.com
>>> twitter: danwendlandt
>>> ~~~
>>>
>>
>>
>
>
> --
> ~~~
> Dan Wendlandt
> Nicira, Inc: www.nicira.com
> twitter: danwendlandt
> ~~~
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Error when creating second VM

2013-03-06 Thread Guilherme Russi

Hello guys, I need some help here, I was in trouble with the VM's IP
attachment (Folsom with Quantum) but the Chathura's solution worked fine to
me, but now I have my compute node with one VM running fine, with right IP
from DHCP, the problem is when I create another VMs, my dashboard list the
second, third, etc, with error, here is my Computer's log to nova-compute.
Anybody can help me to solve it, i'm really confuse, because I have one VM
running.

2013-03-06 14:33:37 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager._publish_service_capabilities periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-03-06 14:33:37 6954 DEBUG nova.manager [-] Notifying Schedulers of
capabilities ... _publish_service_capabilities
/usr/lib/python2.7/dist-packages/nova/manager.py:231
2013-03-06 14:33:37 6954 DEBUG nova.openstack.common.rpc.amqp [-] Making
asynchronous fanout cast... fanout_cast
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py:385
2013-03-06 14:33:37 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager._poll_rescued_instances periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-03-06 14:33:37 6954 DEBUG nova.manager [-] Skipping
ComputeManager._sync_power_states, 5 ticks left until next run
periodic_tasks /usr/lib/python2.7/dist-packages/nova/manager.py:167
2013-03-06 14:33:37 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager._poll_bandwidth_usage periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-03-06 14:33:37 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager._instance_usage_audit periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-03-06 14:33:37 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager.update_available_resource periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-03-06 14:33:37 6954 DEBUG nova.utils [-] Got semaphore
"compute_resources" for method "update_available_resource"... inner
/usr/lib/python2.7/dist-packages/nova/utils.py:765
2013-03-06 14:33:47 6954 DEBUG nova.utils [-] Running cmd (subprocess): env
LC_ALL=C LANG=C qemu-img info
/var/lib/nova/instances/instance-0012/disk execute
/usr/lib/python2.7/dist-packages/nova/utils.py:187
2013-03-06 14:33:47 6954 DEBUG nova.utils [-] Result was 0 execute
/usr/lib/python2.7/dist-packages/nova/utils.py:203
2013-03-06 14:33:47 6954 DEBUG nova.utils [-] Running cmd (subprocess): env
LC_ALL=C LANG=C qemu-img info
/var/lib/nova/instances/instance-0012/disk execute
/usr/lib/python2.7/dist-packages/nova/utils.py:187
2013-03-06 14:33:47 6954 DEBUG nova.utils [-] Result was 0 execute
/usr/lib/python2.7/dist-packages/nova/utils.py:203
2013-03-06 14:33:47 6954 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free ram (MB): 15248 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:470
2013-03-06 14:33:47 6954 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free disk (GB): 369 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:471
2013-03-06 14:33:47 6954 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free VCPUs: 7 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:476
2013-03-06 14:33:47 6954 AUDIT nova.compute.resource_tracker [-] Free ram
(MB): 14932
2013-03-06 14:33:47 6954 AUDIT nova.compute.resource_tracker [-] Free disk
(GB): 372
2013-03-06 14:33:47 6954 AUDIT nova.compute.resource_tracker [-] Free
VCPUS: 7
2013-03-06 14:33:47 6954 INFO nova.compute.resource_tracker [-]
Compute_service record updated for baco
2013-03-06 14:33:47 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager._poll_rebooting_instances periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-03-06 14:33:47 6954 DEBUG nova.manager [-] Skipping
ComputeManager._cleanup_running_deleted_instances, 10 ticks left until next
run periodic_tasks /usr/lib/python2.7/dist-packages/nova/manager.py:167
2013-03-06 14:33:47 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager._check_instance_build_time periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-03-06 14:33:47 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager._heal_instance_info_cache periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-03-06 14:33:47 6954 DEBUG nova.network.quantumv2.api [-]
get_instance_nw_info() for 01 _get_instance_nw_info
/usr/lib/python2.7/dist-packages/nova/network/quantumv2/api.py:190
2013-03-06 14:33:48 6954 DEBUG nova.compute.manager [-] [instance:
64e0e53d-0477-4354-89df-15967e67ee9b] Updated the info_cache for instance
_heal_instance_info_cache
/usr/lib/python2.7/dist-packages/nova/compute/manager.py:2484
2013-03-06 14:33:48 6954 DEBUG nova.manager [-] Running periodic task
ComputeManager._run_image_cache_manager_pass periodic_tasks
/usr/lib/python2.7/dist-packages/nova/ma

Re: [Openstack] Allocating dynamic IP to the VMs

2013-03-18 Thread Guilherme Russi

Hello Chathura, I'm getting error when allocating floating IPs, can you
allocate them? I'm creating my networking following this script:

https://raw.github.com/EmilienM/openstack-folsom-guide/master/scripts/quantum-networking.sh

Thank you.

Guilherme.


2013/3/18 Chathura M. Sarathchandra Magurawalage <77.chath...@gmail.com>

> Thanks Sylvain,
>
> There must be a way of doing this without having to do anything with my
> default gateway of my physical network? . Even if I have to I do not wan to
> do anything to the physical gateway. All I need is a way to let the VMs get
> a dynamic IP from the physical network. How can I do this. For example this
> can be done on virtual box using a bridge adapter which maps the VM in to
> the physical network.
>
> On 18 March 2013 16:05, Sylvain Bauza  wrote:
>
>>  Could you please tell me your "physical network" CIDR ?
>> Anyway, what you need is not requiring having a floating IP pool inside
>> the same network, you can also play with static routing : if your physical
>> host does have a default gw, you can create a static route from this gw to
>> the VM network gateway. And on the VM network gateway, do the same...
>>
>> -Sylvain
>>
>> Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit :
>>
>>   Hey Sylvain,
>>
>>  Basically what I need is to have the VMs mapped to my physical network
>> so that my physical hosts can directly access the VMs. How can I do this?
>>
>>  Thanks.
>>
>>
>> On 18 March 2013 15:50, Sylvain Bauza  wrote:
>>
>>>  Hi,
>>>
>>> I don't understand your business. Should you have a 192.168.1.0/24network 
>>> for management, you could also assign an external network with
>>> Quantum based on the same subnet (ie. 192.168.1.0/24).
>>> When creating a floating IP pool, Quantum does require at least 3 things
>>> :
>>>  - the CIDR
>>>  - the beginning and ending IPs
>>>  - the external gateway
>>>
>>> So, based on what I previously said, you only need to create a
>>> 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254
>>> being the external gateway.
>>>
>>> Thanks,
>>> -Sylvain
>>>
>>> Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit :
>>>
>>>  anyone?
>>>
>>> On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage <
>>> 77.chath...@gmail.com> wrote:
>>>
 After reading a little bit more, I think I have found what I need. It
 is  a provider network that I need for the VMs so that they can get access
 to the other resources in my main network ( such as other physical hosts
 that are connected to the same network ).

  My question is, is it possible to do this alongside the use case that
 I have followed ( Provider router with private networks)?

  If so how can I do this?

  Thanks.


   On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage <
 77.chath...@gmail.com> wrote:

>  Hello,
>
>  I want to know how I can allocate a dynamic IP to the VM from the
> same network as the openstack hosts (controller/network-node/compute node)
> network/management network . For example, in virtual box you can give your
> VM an IP from the host's network using a Bridge adapter. How can I do this
> in openstack?
>
>  From what I understand floating IP's are used when you have a public
> IP
>  (which is static) to be allocated to VM's.
>
> My openstack installation architecture:
>
> http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html
>
>  Quantum use case:
>
> http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html
>


>>>
>>>
>>>  ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Guilherme Russi

Hello Steve, I had a lot of troubles deploying my openstack and putting my
controller node at the same physical machine with my network node, I have 2
NICs in my controller + network node, if you need help, I can help you.

Regards.

Guilherme.


2013/4/12 Steve Heistand 

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> mostly Im concerned about the quantum/OVS/qre settings.
> there are distinct difference in the values in the ovs_quantum_plugin.ini
> file depending on what type of node the agent is running on.
> I wasnt sure if it going to work.
> The problems Ive been having are all network related all centered around
> getting VMs on compute nodes to be able to see something besides another
> VM in their tenant. ie the outside world.
> But my network/ovs-fu is limited so its entirely possible its my fault.
> just wanted to see if it was even possible in the first place.
>
> s
>
>
> On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote:
> > Hi Steve,
> >
> > Why do you say that? I am curious to learn about the difficulties you
> have had.
> >
> > I also tried to have controller node and network node running on the
> same machine but
> > I have never managed to ping a running VM in this configuration with
> FOLSOM release.
> >  Everything was working fine but impossible to ping a VM.
> >
> > Amine.
> >
> >
> > On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand  > > wrote:
> >
> > so Im beginning to think my attempts at getting a controller node and a
> network node
> > to be on the same physical machines/OS are doomed.
> >
> > is it even possible to have all the controller and network node features
> on the same
> > box? Aside from one of them being in a VM that is.
> >
> > thanks
> >
> > s
> >
> > --
> 
> Steve
> > Heistand   NASA Ames Research Center SciCon Group
> > Mail Stop 258-6 steve.heist...@nasa.gov 
> (650)
> > 604-4369   Moffett Field, CA 94035-1000
> > 
> "Any
> > opinions expressed are those of our alien overlords, not my own."
> >
> > # For Remedy# #Action: Resolve
>  #
> > #Resolution: Resolved   # #Reason: No Further Action
> Required # #Tier1:
> > User Code   # #Tier2: Other   #
> #Tier3:
> > Assistance  # #Notification: None #
> >
> >
> >
> > ___ Mailing list:
> > https://launchpad.net/~openstack Post to :
> openstack@lists.launchpad.net
> >  Unsubscribe :
> > https://launchpad.net/~openstack More help   :
> https://help.launchpad.net/ListHelp
> >
> >
>
> - --
> 
>  Steve Heistand  NASA Ames Research Center
>  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
>  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
>  Scientific & HPC ApplicationP.O. Box 1
>  Development/OptimizationMoffett Field, CA 94035-0001
> 
>  "Any opinions expressed are those of our alien overlords, not my own."
>
> # For Remedy#
> #Action: Resolve#
> #Resolution: Resolved   #
> #Reason: No Further Action Required #
> #Tier1: User Code   #
> #Tier2: Other   #
> #Tier3: Assistance  #
> #Notification: None #
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iEYEARECAAYFAlFoDYAACgkQoBCTJSAkVrEXDACeMBENxoBLL4OdayOsSHHDfjgg
> juUAoMzQCTR2DVk1+usy3SV3yENkrtmP
> =3vok
> -END PGP SIGNATURE-
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Problem when allocating IP

2013-04-30 Thread Guilherme Russi

 Hello guys, I'm getting problem when my VMs are allocating IPs. I create
the first VM and it works, it gets the IP 10.0.0.4 and I can ssh and ping,
but when I create the second, the third and so on VMs the don't get IP.
 Can anybody guide me where to look to fix it? I'm using Ubuntu 12.04
server, and my openstack version is folsom, and my network plugin is
quantum.

Thank you.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Quantum + Ryu on Folsom

2013-05-07 Thread Guilherme Russi

Hello Guys,

 I'm here again with some doubt, have anybody already installed the Ryu
plugin with Quantum? I'm trying to follow this page:
http://osrg.github.io/ryu/doc/using_with_openstack.html but it's not
working. Can anybody help me with some doubts about the installation?

Thank you so much.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Quantum + Ryu on Folsom

2013-05-07 Thread Guilherme Russi

Hello Kyle, The doubts are, If I install the ryu plugin, my current working
openstack will broken, I mean, only installing ryu by the step python
./setup.py install, another thing, and the part to configure nova.conf, I
don't have nova-network, I must install it?

Thanks.

Guilherme.


2013/5/7 Kyle Mestery (kmestery) 

> On May 7, 2013, at 7:57 AM, Guilherme Russi 
> wrote:
> >
> > Hello Guys,
> >
> >  I'm here again with some doubt, have anybody already installed the Ryu
> plugin with Quantum? I'm trying to follow this page:
> http://osrg.github.io/ryu/doc/using_with_openstack.html but it's not
> working. Can anybody help me with some doubts about the installation?
> >
> > Thank you so much.
> >
> What exactly is happening with Ryu on Folsom here? I've run this before
> and had no issues, so I can try to provide some help here.
>
> Kyle
>
> > Guilherme.
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Quantum + Ryu on Folsom

2013-05-07 Thread Guilherme Russi

Hello again Kyle, thank you for answering, how do I update the Openstack
version, from Folsom to Grizzly?

Regards.

Guilherme.


2013/5/7 Kyle Mestery (kmestery) 

> You don't want to run nova-network with OpenStack Networking (Quantum) at
> the same time. If you're running Folsom, I think upstream Ryu has changed
> such that the Folsom version of the Quantum plugin may not work. Running
> Grizzly will solve this, or alternatively if you want to try Folsom, look
> at the github page here for instructions on which branch of Ryu to pull to
> get it working with Folsom Quantum:
>
> https://github.com/osrg/ryu/wiki/RYU-Openstack-Folsom-environment-HOWTO
>
> Thanks,
> Kyle
>
> On May 7, 2013, at 8:21 AM, Guilherme Russi 
> wrote:
>
> > Hello Kyle, The doubts are, If I install the ryu plugin, my current
> working openstack will broken, I mean, only installing ryu by the step
> python ./setup.py install, another thing, and the part to configure
> nova.conf, I don't have nova-network, I must install it?
> >
> > Thanks.
> >
> > Guilherme.
> >
> >
> > 2013/5/7 Kyle Mestery (kmestery) 
> > On May 7, 2013, at 7:57 AM, Guilherme Russi 
> wrote:
> > >
> > > Hello Guys,
> > >
> > >  I'm here again with some doubt, have anybody already installed the
> Ryu plugin with Quantum? I'm trying to follow this page:
> http://osrg.github.io/ryu/doc/using_with_openstack.html but it's not
> working. Can anybody help me with some doubts about the installation?
> > >
> > > Thank you so much.
> > >
> > What exactly is happening with Ryu on Folsom here? I've run this before
> and had no issues, so I can try to provide some help here.
> >
> > Kyle
> >
> > > Guilherme.
> > > ___
> > > Mailing list: https://launchpad.net/~openstack
> > > Post to : openstack@lists.launchpad.net
> > > Unsubscribe : https://launchpad.net/~openstack
> > > More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Quantum + Ryu on Folsom

2013-05-07 Thread Guilherme Russi

I'm not using devstack, I have installed each component and put a
repository in my ubuntu, I need to purge all of them or just change the
repository and run an apt-get update / apt-get upgrade?

Regards.

Guilherme.


2013/5/7 Kyle Mestery (kmestery) 

> If you are using devstack, it's as simple as adding a "stable/grizzly" for
> each component you are running, similar to this:
>
> NOVA_BRANCH=stable/grizzly
>
> Repeat that for the services you are running, (e.g. Quantum, Glance, etc.).
>
> Thanks,
> Kyle
>
> On May 7, 2013, at 10:20 AM, Guilherme Russi 
> wrote:
>
> > Hello again Kyle, thank you for answering, how do I update the Openstack
> version, from Folsom to Grizzly?
> >
> > Regards.
> >
> > Guilherme.
> >
> >
> > 2013/5/7 Kyle Mestery (kmestery) 
> > You don't want to run nova-network with OpenStack Networking (Quantum)
> at the same time. If you're running Folsom, I think upstream Ryu has
> changed such that the Folsom version of the Quantum plugin may not work.
> Running Grizzly will solve this, or alternatively if you want to try
> Folsom, look at the github page here for instructions on which branch of
> Ryu to pull to get it working with Folsom Quantum:
> >
> > https://github.com/osrg/ryu/wiki/RYU-Openstack-Folsom-environment-HOWTO
> >
> > Thanks,
> > Kyle
> >
> > On May 7, 2013, at 8:21 AM, Guilherme Russi 
> wrote:
> >
> > > Hello Kyle, The doubts are, If I install the ryu plugin, my current
> working openstack will broken, I mean, only installing ryu by the step
> python ./setup.py install, another thing, and the part to configure
> nova.conf, I don't have nova-network, I must install it?
> > >
> > > Thanks.
> > >
> > > Guilherme.
> > >
> > >
> > > 2013/5/7 Kyle Mestery (kmestery) 
> > > On May 7, 2013, at 7:57 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
> > > >
> > > > Hello Guys,
> > > >
> > > >  I'm here again with some doubt, have anybody already installed the
> Ryu plugin with Quantum? I'm trying to follow this page:
> http://osrg.github.io/ryu/doc/using_with_openstack.html but it's not
> working. Can anybody help me with some doubts about the installation?
> > > >
> > > > Thank you so much.
> > > >
> > > What exactly is happening with Ryu on Folsom here? I've run this
> before and had no issues, so I can try to provide some help here.
> > >
> > > Kyle
> > >
> > > > Guilherme.
> > > > ___
> > > > Mailing list: https://launchpad.net/~openstack
> > > > Post to : openstack@lists.launchpad.net
> > > > Unsubscribe : https://launchpad.net/~openstack
> > > > More help   : https://help.launchpad.net/ListHelp
> > >
> > >
> > >
> >
> >
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Quantum + Ryu on Folsom

2013-05-07 Thread Guilherme Russi

Well, thank you for your support, I'll try to do this and I'll let you know
if it worked, or not.

Regards.


2013/5/7 Kyle Mestery (kmestery) 

> I would have to defer to the normal Ubuntu OpenStack install/upgrade
> procedures here, I'm not an expert in that area.
>
> On May 7, 2013, at 12:01 PM, Guilherme Russi 
> wrote:
>
> > I'm not using devstack, I have installed each component and put a
> repository in my ubuntu, I need to purge all of them or just change the
> repository and run an apt-get update / apt-get upgrade?
> >
> > Regards.
> >
> > Guilherme.
> >
> >
> > 2013/5/7 Kyle Mestery (kmestery) 
> > If you are using devstack, it's as simple as adding a "stable/grizzly"
> for each component you are running, similar to this:
> >
> > NOVA_BRANCH=stable/grizzly
> >
> > Repeat that for the services you are running, (e.g. Quantum, Glance,
> etc.).
> >
> > Thanks,
> > Kyle
> >
> > On May 7, 2013, at 10:20 AM, Guilherme Russi 
> wrote:
> >
> > > Hello again Kyle, thank you for answering, how do I update the
> Openstack version, from Folsom to Grizzly?
> > >
> > > Regards.
> > >
> > > Guilherme.
> > >
> > >
> > > 2013/5/7 Kyle Mestery (kmestery) 
> > > You don't want to run nova-network with OpenStack Networking (Quantum)
> at the same time. If you're running Folsom, I think upstream Ryu has
> changed such that the Folsom version of the Quantum plugin may not work.
> Running Grizzly will solve this, or alternatively if you want to try
> Folsom, look at the github page here for instructions on which branch of
> Ryu to pull to get it working with Folsom Quantum:
> > >
> > >
> https://github.com/osrg/ryu/wiki/RYU-Openstack-Folsom-environment-HOWTO
> > >
> > > Thanks,
> > > Kyle
> > >
> > > On May 7, 2013, at 8:21 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
> > >
> > > > Hello Kyle, The doubts are, If I install the ryu plugin, my current
> working openstack will broken, I mean, only installing ryu by the step
> python ./setup.py install, another thing, and the part to configure
> nova.conf, I don't have nova-network, I must install it?
> > > >
> > > > Thanks.
> > > >
> > > > Guilherme.
> > > >
> > > >
> > > > 2013/5/7 Kyle Mestery (kmestery) 
> > > > On May 7, 2013, at 7:57 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
> > > > >
> > > > > Hello Guys,
> > > > >
> > > > >  I'm here again with some doubt, have anybody already installed
> the Ryu plugin with Quantum? I'm trying to follow this page:
> http://osrg.github.io/ryu/doc/using_with_openstack.html but it's not
> working. Can anybody help me with some doubts about the installation?
> > > > >
> > > > > Thank you so much.
> > > > >
> > > > What exactly is happening with Ryu on Folsom here? I've run this
> before and had no issues, so I can try to provide some help here.
> > > >
> > > > Kyle
> > > >
> > > > > Guilherme.
> > > > > ___
> > > > > Mailing list: https://launchpad.net/~openstack
> > > > > Post to : openstack@lists.launchpad.net
> > > > > Unsubscribe : https://launchpad.net/~openstack
> > > > > More help   : https://help.launchpad.net/ListHelp
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Quantum + Ryu on Folsom

2013-05-08 Thread Guilherme Russi

Hello Daniele, thank you for your support, I will install in my lab too.

Regards.

Guilherme.


2013/5/8 Stroppa Daniele (strp) 

> Guilherme,
>
> If you do upgrade to Grizzly (either with Devstack or Ubuntu packages)
> check these pages https://github.com/osrg/ryu/wiki/OpenStack
>
> They are quite complete, we used them as a reference for our lab
> installation.
>
> Regards,
> --
> Daniele Stroppa
> Researcher
> Institute of Information Technology
> Zürich University of Applied Sciences
> http://www.cloudcomp.ch<http://www.cloudcomp.ch/>
>
>
> From: Guilherme Russi  luisguilherme...@gmail.com>>
> Date: Tue, 7 May 2013 14:23:41 -0300
> To: "Kyle Mestery (kmestery)"  kmest...@cisco.com>>
> Cc: "openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>"
> mailto:openstack@lists.launchpad.net>>
> Subject: Re: [Openstack] Quantum + Ryu on Folsom
>
> Well, thank you for your support, I'll try to do this and I'll let you
> know if it worked, or not.
>
> Regards.
>
>
> 2013/5/7 Kyle Mestery (kmestery)  kmest...@cisco.com>>
> I would have to defer to the normal Ubuntu OpenStack install/upgrade
> procedures here, I'm not an expert in that area.
>
> On May 7, 2013, at 12:01 PM, Guilherme Russi  <mailto:luisguilherme...@gmail.com>> wrote:
>
> > I'm not using devstack, I have installed each component and put a
> repository in my ubuntu, I need to purge all of them or just change the
> repository and run an apt-get update / apt-get upgrade?
> >
> > Regards.
> >
> > Guilherme.
> >
> >
> > 2013/5/7 Kyle Mestery (kmestery)  kmest...@cisco.com>>
> > If you are using devstack, it's as simple as adding a "stable/grizzly"
> for each component you are running, similar to this:
> >
> > NOVA_BRANCH=stable/grizzly
> >
> > Repeat that for the services you are running, (e.g. Quantum, Glance,
> etc.).
> >
> > Thanks,
> > Kyle
> >
> > On May 7, 2013, at 10:20 AM, Guilherme Russi  <mailto:luisguilherme...@gmail.com>> wrote:
> >
> > > Hello again Kyle, thank you for answering, how do I update the
> Openstack version, from Folsom to Grizzly?
> > >
> > > Regards.
> > >
> > > Guilherme.
> > >
> > >
> > > 2013/5/7 Kyle Mestery (kmestery)  kmest...@cisco.com>>
> > > You don't want to run nova-network with OpenStack Networking (Quantum)
> at the same time. If you're running Folsom, I think upstream Ryu has
> changed such that the Folsom version of the Quantum plugin may not work.
> Running Grizzly will solve this, or alternatively if you want to try
> Folsom, look at the github page here for instructions on which branch of
> Ryu to pull to get it working with Folsom Quantum:
> > >
> > >
> https://github.com/osrg/ryu/wiki/RYU-Openstack-Folsom-environment-HOWTO
> > >
> > > Thanks,
> > > Kyle
> > >
> > > On May 7, 2013, at 8:21 AM, Guilherme Russi <
> luisguilherme...@gmail.com<mailto:luisguilherme...@gmail.com>> wrote:
> > >
> > > > Hello Kyle, The doubts are, If I install the ryu plugin, my current
> working openstack will broken, I mean, only installing ryu by the step
> python ./setup.py install, another thing, and the part to configure
> nova.conf, I don't have nova-network, I must install it?
> > > >
> > > > Thanks.
> > > >
> > > > Guilherme.
> > > >
> > > >
> > > > 2013/5/7 Kyle Mestery (kmestery)  kmest...@cisco.com>>
> > > > On May 7, 2013, at 7:57 AM, Guilherme Russi <
> luisguilherme...@gmail.com<mailto:luisguilherme...@gmail.com>> wrote:
> > > > >
> > > > > Hello Guys,
> > > > >
> > > > >  I'm here again with some doubt, have anybody already installed
> the Ryu plugin with Quantum? I'm trying to follow this page:
> http://osrg.github.io/ryu/doc/using_with_openstack.html but it's not
> working. Can anybody help me with some doubts about the installation?
> > > > >
> > > > > Thank you so much.
> > > > >
> > > > What exactly is happening with Ryu on Folsom here? I've run this
> before and had no issues, so I can try to provide some help here.
> > > >
> > > > Kyle
> > > >
> > > > > Guilherme.
> > > > > ___
> > > > > Mailing list: https://launchpad.net/~openstack
> > > > > Post to : openstack@lists.launchpad.net openstack@lists.launchpad.net>
> > > > > Unsubscribe : https://launchpad.net/~openstack
> > > > > More help   : https://help.launchpad.net/ListHelp
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net
> <mailto:openstack@lists.launchpad.net> Unsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] horizon dashboard error 500

2013-05-08 Thread Guilherme Russi

Hello Rajesh, where should I change this COMPRESS_OFFLINE?

Thank you.

Guilherme.


2013/5/3 Rajesh Upadhayay 

> This has issue has been fixed by changing False as false.
> COMPRESS_OFFLINE = false
>
> -Original Message-
> From: Julie Pichon [mailto:jpic...@redhat.com]
> Sent: Friday, May 03, 2013 8:29 PM
> To: Rajesh Upadhayay
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] horizon dashboard error 500
>
> Hi,
>
> "Rajesh Upadhayay"  wrote:
> > I have just installed Openstack Grizzly on Ubuntu 12.04 LTS..
> > Everything was fine but after server reboot, I lost dashboard and
> > getting error 500 "Internal Server Error".
> >
> > I have verified all configuration but didn't get any idea.
>
> Have a look in the Apache error logs, there should be more information
> about the error.
>
> If this is a dev or test environment (not production), you could also set
> DEBUG to True in your local_settings.py to display more information when
> the error occurs.
>
> Regards,
>
> Julie
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] horizon dashboard error 500

2013-05-08 Thread Guilherme Russi

But where is the path that I can find this file?


2013/5/8 Gabriel Hurley 

> There's something very wrong is "false" doesn't raise an exception. In
> Python "False" is a Boolean value, "false" is a variable name which should
> be undefined.
>
> That aside, you should set COMPRESS_OFFLINE=False in your
> openstack_dashboard/local/local_settings.py file.
>
> - Gabriel
>
> > -Original Message-
> > From: Openstack [mailto:openstack-
> > bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
> > Rajesh Upadhayay
> > Sent: Friday, May 03, 2013 10:18 AM
> > To: Julie Pichon
> > Cc: openstack@lists.launchpad.net
> > Subject: Re: [Openstack] horizon dashboard error 500
> >
> > This has issue has been fixed by changing False as false.
> > COMPRESS_OFFLINE = false
> >
> > -Original Message-
> > From: Julie Pichon [mailto:jpic...@redhat.com]
> > Sent: Friday, May 03, 2013 8:29 PM
> > To: Rajesh Upadhayay
> > Cc: openstack@lists.launchpad.net
> > Subject: Re: [Openstack] horizon dashboard error 500
> >
> > Hi,
> >
> > "Rajesh Upadhayay"  wrote:
> > > I have just installed Openstack Grizzly on Ubuntu 12.04 LTS..
> > > Everything was fine but after server reboot, I lost dashboard and
> > > getting error 500 "Internal Server Error".
> > >
> > > I have verified all configuration but didn't get any idea.
> >
> > Have a look in the Apache error logs, there should be more information
> > about the error.
> >
> > If this is a dev or test environment (not production), you could also set
> > DEBUG to True in your local_settings.py to display more information when
> > the error occurs.
> >
> > Regards,
> >
> > Julie
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] horizon dashboard error 500

2013-05-08 Thread Guilherme Russi

: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] return
node.render(context), referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/django/template/loader_tags.py", line
155, in render, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] return
self.render_template(self.template, context), referer:
http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/django/template/loader_tags.py", line
137, in render_template, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] output =
template.render(context), referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/django/template/base.py", line 140, in
render, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] return
self._render(context), referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/django/template/base.py", line 134, in
_render, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] return
self.nodelist.render(context), referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/django/template/base.py", line 823, in
render, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] bit =
self.render_node(node, context), referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/django/template/base.py", line 837, in
render_node, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] return
node.render(context), referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/compressor/templatetags/compress.py",
line 147, in render, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] return
self.render_compressed(context, self.kind, self.mode, forced=forced),
referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/compressor/templatetags/compress.py",
line 88, in render_compressed, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] cached_offline
= self.render_offline(context, forced=forced), referer:
http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]   File
"/usr/lib/python2.7/dist-packages/compressor/templatetags/compress.py",
line 72, in render_offline, referer: http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1] 'You may need
to run "python manage.py compress".' % key), referer:
http://192.168.3.1/horizon
[Wed May 08 19:48:01 2013] [error] [client 192.168.3.1]
OfflineGenerationError: You have offline compression enabled but key
"3ddd89d27fa2e162d4efd30c103a072b" is missing from offline manifest. You
may need to run "python manage.py compress"., referer:
http://192.168.3.1/horizon

I made the upgrade from Folsom to Grizzly, maybe I'm missing something?

Regards.

Guilherme.


2013/5/8 Guilherme Russi 

> But where is the path that I can find this file?
>
>
> 2013/5/8 Gabriel Hurley 
>
>> There's something very wrong is "false" doesn't raise an exception. In
>> Python "False" is a Boolean value, "false" is a variable name which should
>> be undefined.
>>
>> That aside, you should set COMPRESS_OFFLINE=False in your
>> openstack_dashboard/local/local_settings.py file.
>>
>> - Gabriel
>>
>> > -Original Message-
>> > From: Openstack [mailto:openstack-
>> > bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
>> > Rajesh Upadhayay
>> > Sent: Friday, May 03, 2013 10:18 AM
>> > To: Julie Pichon
>> > Cc: openstack@lists.launchpad.net
>> > Subject: Re: [Openstack] horizon dashboard error 500
>> >
>> > This has issue has been fixed by changing False as false.
>> > COMPRESS_OFFLINE = false
>> >
>> > -Original Message-
>> > From: Julie Pichon [mailto:jpic...@redhat.com]
>> > Sent: Friday, May 03, 2013 8:29 PM
>> > To: Rajesh Upadhayay
>> > Cc: openstack@lists.launchpad.net
>> > Subject: Re: [Openstack] hori

Re: [Openstack] Updating OpenStack

2013-07-03 Thread Guilherme Russi

Hello Claudio,

 1 - Yes, they are synced with my network node
 2 - I put the configuration on my nova.conf rabbit_host=my_host and
rabbit_password=my_pass, are they the only parameters?

Thank you.

Regards.


2013/7/3 claudio marques 

> Hi
>
> 1 - Do you have your time on your  new compute nodes synchronized with
> network node?
>
> 2 - Have you paste the correct credentials to your rabbit MQ server?
>
> Cheers
>
>
> clau...@onesource.pt
> http://www.onesource.pt/
>
>
> --
> From: luisguilherme...@gmail.com
> Date: Wed, 3 Jul 2013 14:07:04 -0300
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Updating OpenStack
>
>
> Hello guys, I have a Controller node and a Compute node with grizzly
> installed and working fine, but the problem is, I'm installing two more
> computes nodes but at both I'm getting error at nova (error attached). I
> made some researches through the google and I saw some people talking about
> running an apt-get update / apt-get upgrade at the Controller node and
> Compute node. My point is, is safe to run this update/upgrade steps? My
> working controller and compute can stop working (break?)
>
> Thank you all.
>
> Guilherme.
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Updating OpenStack

2013-07-03 Thread Guilherme Russi

Yes, that's the point, if a make an apt-get update / apt-get upgrade, my
running compute node can break? And more, do I need to run an apt-get
update / apt-get upgrade at my Controller node too?


2013/7/3 claudio marques 

> Probably you have an older nova version running in one of the compute-nodes,
> and probably that's  why you have *UnsupportedRpcVersion exception!*
> *
> *
> Cheers
>
> *
> *
> clau...@onesource.pt
> http://www.onesource.pt/
>
> --
> From: clau...@onesource.pt
> To: openstack@lists.launchpad.net
> Date: Wed, 3 Jul 2013 17:20:47 +
> Subject: Re: [Openstack] Updating OpenStack
>
>
> Hi
>
> 1 - Do you have your time on your  new compute nodes synchronized with
> network node?
>
> 2 - Have you paste the correct credentials to your rabbit MQ server?
>
> Cheers
>
>
> clau...@onesource.pt
> http://www.onesource.pt/
>
>
> --
> From: luisguilherme...@gmail.com
> Date: Wed, 3 Jul 2013 14:07:04 -0300
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Updating OpenStack
>
> Hello guys, I have a Controller node and a Compute node with grizzly
> installed and working fine, but the problem is, I'm installing two more
> computes nodes but at both I'm getting error at nova (error attached). I
> made some researches through the google and I saw some people talking about
> running an apt-get update / apt-get upgrade at the Controller node and
> Compute node. My point is, is safe to run this update/upgrade steps? My
> working controller and compute can stop working (break?)
>
> Thank you all.
>
> Guilherme.
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Updating OpenStack

2013-07-03 Thread Guilherme Russi

Ok Calvin, I'll do that, thank you.


2013/7/3 Calvin Austin 

> I experienced the same thing just yesterday. the python-nova package (on
> ubuntu) has api changes in dot dot versions, 1.47 brought in a new db call
> that the server doesn't know about.
>
> I ended up downloading the same python-nova package on the new compute
> node so they could talk
>
> python-nova_2013.1-0ubuntu1_all.deb
>
> regards
> calvin
>
>
> On Wed, Jul 3, 2013 at 10:32 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> Yes, that's the point, if a make an apt-get update / apt-get upgrade, my
>> running compute node can break? And more, do I need to run an apt-get
>> update / apt-get upgrade at my Controller node too?
>>
>>
>> 2013/7/3 claudio marques 
>>
>>> Probably you have an older nova version running in one of the compute-nodes,
>>> and probably that's  why you have *UnsupportedRpcVersion exception!*
>>> *
>>> *
>>> Cheers
>>>
>>> *
>>> *
>>> clau...@onesource.pt
>>> http://www.onesource.pt/
>>>
>>> --
>>> From: clau...@onesource.pt
>>> To: openstack@lists.launchpad.net
>>> Date: Wed, 3 Jul 2013 17:20:47 +
>>> Subject: Re: [Openstack] Updating OpenStack
>>>
>>>
>>> Hi
>>>
>>> 1 - Do you have your time on your  new compute nodes synchronized with
>>> network node?
>>>
>>> 2 - Have you paste the correct credentials to your rabbit MQ server?
>>>
>>> Cheers
>>>
>>>
>>> clau...@onesource.pt
>>> http://www.onesource.pt/
>>>
>>>
>>> --
>>> From: luisguilherme...@gmail.com
>>> Date: Wed, 3 Jul 2013 14:07:04 -0300
>>> To: openstack@lists.launchpad.net
>>> Subject: [Openstack] Updating OpenStack
>>>
>>> Hello guys, I have a Controller node and a Compute node with grizzly
>>> installed and working fine, but the problem is, I'm installing two more
>>> computes nodes but at both I'm getting error at nova (error attached). I
>>> made some researches through the google and I saw some people talking about
>>> running an apt-get update / apt-get upgrade at the Controller node and
>>> Compute node. My point is, is safe to run this update/upgrade steps? My
>>> working controller and compute can stop working (break?)
>>>
>>> Thank you all.
>>>
>>> Guilherme.
>>>
>>> ___ Mailing list:
>>> https://launchpad.net/~openstack Post to : 
>>> openstack@lists.launchpad.netUnsubscribe :
>>> https://launchpad.net/~openstack More help :
>>> https://help.launchpad.net/ListHelp
>>>
>>> ___ Mailing list:
>>> https://launchpad.net/~openstack Post to : 
>>> openstack@lists.launchpad.netUnsubscribe :
>>> https://launchpad.net/~openstack More help :
>>> https://help.launchpad.net/ListHelp
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Updating OpenStack

2013-07-03 Thread Guilherme Russi

Hello Trevor, I did that :)


2013/7/3 Trevor Roberts Jr 

> Hi Guilherme,
>
> To ensure that all settings match up correctly, it's advised to copy the
> nova.conf from your Controller node, or the Compute Node that works, to
> each new Nova node
>
> -Trevor
>
> Sent from my iPad
>
> On Jul 3, 2013, at 7:30 AM, Guilherme Russi 
> wrote:
>
> Hello Claudio,
>
>  1 - Yes, they are synced with my network node
>  2 - I put the configuration on my nova.conf rabbit_host=my_host and
> rabbit_password=my_pass, are they the only parameters?
>
> Thank you.
>
> Regards.
>
>
> 2013/7/3 claudio marques 
>
>> Hi
>>
>> 1 - Do you have your time on your  new compute nodes synchronized with
>> network node?
>>
>> 2 - Have you paste the correct credentials to your rabbit MQ server?
>>
>> Cheers
>>
>>
>> clau...@onesource.pt
>> http://www.onesource.pt/
>>
>>
>> --
>> From: luisguilherme...@gmail.com
>> Date: Wed, 3 Jul 2013 14:07:04 -0300
>> To: openstack@lists.launchpad.net
>> Subject: [Openstack] Updating OpenStack
>>
>>
>> Hello guys, I have a Controller node and a Compute node with grizzly
>> installed and working fine, but the problem is, I'm installing two more
>> computes nodes but at both I'm getting error at nova (error attached). I
>> made some researches through the google and I saw some people talking about
>> running an apt-get update / apt-get upgrade at the Controller node and
>> Compute node. My point is, is safe to run this update/upgrade steps? My
>> working controller and compute can stop working (break?)
>>
>> Thank you all.
>>
>> Guilherme.
>>
>> ___ Mailing list:
>> https://launchpad.net/~openstack Post to : 
>> openstack@lists.launchpad.netUnsubscribe :
>> https://launchpad.net/~openstack More help :
>> https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Updating OpenStack

2013-07-03 Thread Guilherme Russi

I made the download from python-nova_2013.1-0ubuntu2_all.deb and installed
it, then I made the apt-get install nova-compute-kvm but I'm still getting
the same error, am I doing something wrong?

Thank you guys.


2013/7/3 claudio marques 

> In your place I just download the same nova packages to your new compute
> nodes as you got on the first one as Calvin said!
> Upgrading your existing network node and compute node can result in
> disaster :)
>
> Good luck
>
> Cheers
>
> Claudio Marques
>
> clau...@onesource.pt
> http://www.onesource.pt/
>
> --
> Date: Wed, 3 Jul 2013 10:41:37 -0700
> From: caus...@bitglass.com
> To: luisguilherme...@gmail.com
> CC: clau...@onesource.pt; openstack@lists.launchpad.net
>
> Subject: Re: [Openstack] Updating OpenStack
>
> I experienced the same thing just yesterday. the python-nova package (on
> ubuntu) has api changes in dot dot versions, 1.47 brought in a new db call
> that the server doesn't know about.
>
> I ended up downloading the same python-nova package on the new compute
> node so they could talk
>
> python-nova_2013.1-0ubuntu1_all.deb
>
> regards
> calvin
>
>
> On Wed, Jul 3, 2013 at 10:32 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
> Yes, that's the point, if a make an apt-get update / apt-get upgrade, my
> running compute node can break? And more, do I need to run an apt-get
> update / apt-get upgrade at my Controller node too?
>
>
> 2013/7/3 claudio marques 
>
> Probably you have an older nova version running in one of the compute-nodes,
> and probably that's  why you have *UnsupportedRpcVersion exception!*
> *
> *
> Cheers
>
> *
> *
> clau...@onesource.pt
> http://www.onesource.pt/
>
> --
> From: clau...@onesource.pt
> To: openstack@lists.launchpad.net
> Date: Wed, 3 Jul 2013 17:20:47 +
> Subject: Re: [Openstack] Updating OpenStack
>
>
> Hi
>
> 1 - Do you have your time on your  new compute nodes synchronized with
> network node?
>
> 2 - Have you paste the correct credentials to your rabbit MQ server?
>
> Cheers
>
>
> clau...@onesource.pt
> http://www.onesource.pt/
>
>
> --
> From: luisguilherme...@gmail.com
> Date: Wed, 3 Jul 2013 14:07:04 -0300
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Updating OpenStack
>
> Hello guys, I have a Controller node and a Compute node with grizzly
> installed and working fine, but the problem is, I'm installing two more
> computes nodes but at both I'm getting error at nova (error attached). I
> made some researches through the google and I saw some people talking about
> running an apt-get update / apt-get upgrade at the Controller node and
> Compute node. My point is, is safe to run this update/upgrade steps? My
> working controller and compute can stop working (break?)
>
> Thank you all.
>
> Guilherme.
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___ Mailing list:
> https://launchpad.net/~openstack Post to : 
> openstack@lists.launchpad.netUnsubscribe :
> https://launchpad.net/~openstack More help :
> https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Updating OpenStack

2013-07-03 Thread Guilherme Russi

It is showing the 1.47, i'm lokking through the internet how to install the
packages that match with my working compute node. I still have no clue how
to do that :(

Regards.


2013/7/3 Calvin Austin 

> downgrading to python-nova was the last thing I did, apt-get might fix you
> to the latest one.
>
> You can check file
> /usr/lib/python2.7/dist-packages/nova/conductor/rpcapi.py
>
> If it mentions 1.47 in the API version history you have the later
> python-nova, when you downgrade it will ask you if its ok.
>
> regards
> calvin
>
>
> On Wed, Jul 3, 2013 at 11:23 AM, Guilherme Russi <
> luisguilherme...@gmail.com> wrote:
>
>> I made the download from python-nova_2013.1-0ubuntu2_all.deb and
>> installed it, then I made the apt-get install nova-compute-kvm but I'm
>> still getting the same error, am I doing something wrong?
>>
>> Thank you guys.
>>
>>
>> 2013/7/3 claudio marques 
>>
>>> In your place I just download the same nova packages to your new compute
>>> nodes as you got on the first one as Calvin said!
>>> Upgrading your existing network node and compute node can result in
>>> disaster :)
>>>
>>> Good luck
>>>
>>> Cheers
>>>
>>> Claudio Marques
>>>
>>> clau...@onesource.pt
>>> http://www.onesource.pt/
>>>
>>> --
>>> Date: Wed, 3 Jul 2013 10:41:37 -0700
>>> From: caus...@bitglass.com
>>> To: luisguilherme...@gmail.com
>>> CC: clau...@onesource.pt; openstack@lists.launchpad.net
>>>
>>> Subject: Re: [Openstack] Updating OpenStack
>>>
>>> I experienced the same thing just yesterday. the python-nova package (on
>>> ubuntu) has api changes in dot dot versions, 1.47 brought in a new db call
>>> that the server doesn't know about.
>>>
>>> I ended up downloading the same python-nova package on the new compute
>>> node so they could talk
>>>
>>> python-nova_2013.1-0ubuntu1_all.deb
>>>
>>> regards
>>> calvin
>>>
>>>
>>> On Wed, Jul 3, 2013 at 10:32 AM, Guilherme Russi <
>>> luisguilherme...@gmail.com> wrote:
>>>
>>> Yes, that's the point, if a make an apt-get update / apt-get upgrade, my
>>> running compute node can break? And more, do I need to run an apt-get
>>> update / apt-get upgrade at my Controller node too?
>>>
>>>
>>> 2013/7/3 claudio marques 
>>>
>>> Probably you have an older nova version running in one of the compute-nodes,
>>> and probably that's  why you have *UnsupportedRpcVersion exception!*
>>> *
>>> *
>>> Cheers
>>>
>>> *
>>> *
>>> clau...@onesource.pt
>>> http://www.onesource.pt/
>>>
>>> --
>>> From: clau...@onesource.pt
>>> To: openstack@lists.launchpad.net
>>> Date: Wed, 3 Jul 2013 17:20:47 +
>>> Subject: Re: [Openstack] Updating OpenStack
>>>
>>>
>>> Hi
>>>
>>> 1 - Do you have your time on your  new compute nodes synchronized with
>>> network node?
>>>
>>> 2 - Have you paste the correct credentials to your rabbit MQ server?
>>>
>>> Cheers
>>>
>>>
>>> clau...@onesource.pt
>>> http://www.onesource.pt/
>>>
>>>
>>> --
>>> From: luisguilherme...@gmail.com
>>> Date: Wed, 3 Jul 2013 14:07:04 -0300
>>> To: openstack@lists.launchpad.net
>>> Subject: [Openstack] Updating OpenStack
>>>
>>> Hello guys, I have a Controller node and a Compute node with grizzly
>>> installed and working fine, but the problem is, I'm installing two more
>>> computes nodes but at both I'm getting error at nova (error attached). I
>>> made some researches through the google and I saw some people talking about
>>> running an apt-get update / apt-get upgrade at the Controller node and
>>> Compute node. My point is, is safe to run this update/upgrade steps? My
>>> working controller and compute can stop working (break?)
>>>
>>> Thank you all.
>>>
>>> Guilherme.
>>>
>>> ___ Mailing list:
>>> https://launchpad.net/~openstack Post to : 
>>> openstack@lists.launchpad.netUnsubscribe :
>>> https://launchpad.net/~openstack More help :
>>> https://help.launchpad.net/Lis

[Openstack] Configuring Live Migration

2013-07-24 Thread Guilherme Russi

Hello guys, I'm following this manual
http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html,
and I'm trying to configure live migration on my openstack grizzly. I did
all the configurations, mounted the disks, but when I put migration in
action through the dashboard, it shows status with error.

Can anybody give me some help, and which informations I need to send to
provide more explanation?

Thank you all.

Best regards.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Configuring Live Migration

2013-07-24 Thread Guilherme Russi

Hello Wangpan, where can I find these logs?

Thank you.


2013/7/24 Wangpan 

> **
> Hi Guilherme,
> What error the compute log says? you may check both the source compute and
> destination compute node.
>
> 2013-07-25
>  --
>  Wangpan
>  ------
>  *发件人：*Guilherme Russi 
> *发送时间：*2013-07-25 03:38
> *主题：*[Openstack] Configuring Live Migration
> *收件人：*"openstack@lists.launchpad.net"
> *抄送：*
>
>  Hello guys, I'm following this manual
> http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html,
> and I'm trying to configure live migration on my openstack grizzly. I did
> all the configurations, mounted the disks, but when I put migration in
> action through the dashboard, it shows status with error.
>
> Can anybody give me some help, and which informations I need to send to
> provide more explanation?
>
> Thank you all.
>
> Best regards.
>
> Guilherme.
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

58 matches

Mail list logo